简体   繁体   English

调用 Remedy 时出现 404

[英]404 when calling Remedy

I am calling Remedy from WSO2 ESB and I get the following soap error:我从 WSO2 ESB 调用 Remedy,我收到以下肥皂错误:

<?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><text xmlns="http://ws.apache.org/commons/ns/payload">default backend - 404</text></soapenv:Body></soapenv:Envelope>

I have tested multiples endpoint configurations with no success.我已经测试了多个端点配置但没有成功。 If I call the endpoint with straight forward with SoapUI I get the response, but if I go through ESB I get the error.如果我使用 SoapUI 直接调用端点,我会收到响应,但如果我通过 ESB,我会收到错误。 Any help on this error?对这个错误有什么帮助吗?

Cheers干杯

ESB ports are setup in the <ESB_HOME>/repository/conf/axis2/axis2.xml file: https://docs.wso2.com/display/ESB470/Setting+Up+Host+Names+and+Ports ESB 端口在 <ESB_HOME>/repository/conf/axis2/axis2.xml 文件中设置: https ://docs.wso2.com/display/ESB470/Setting+Up+Host+Names+and+Ports

I don't see an option for no port, but SOAP uses 80 by default: What port number does SOAP use?我没有看到无端口选项,但 SOAP 默认使用 80: SOAP 使用什么端口号?

You can work with your BMC Helix team to setup the ports used by your servers: https://docs.bmc.com/docs/display/public/helixsubscriber/Network+port+configuration您可以与 BMC Helix 团队合作设置服务器使用的端口: https : //docs.bmc.com/docs/display/public/helixsubscriber/Network+port+configuration

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 使用wso2在bmc补救和serviceNow之间进行集成 - integration between bmc remedy and serviceNow using wso2 调用Web服务时保留原始有效负载 - Preserve the original payload when calling a web service 调用wso2 Web服务时的Axisfault 302 - Axisfault 302 when calling wso2 web services 调用数据服务时 WSO2 EI 序列失败 - WSO2 EI Sequence failing when calling a Data Service 第一个使用 WSO2 APIM 4.0.0 的 API,创建似乎很好,但尝试调用 API 时出现 HTTP 404 - First API with WSO2 APIM 4.0.0, creation seem fine but HTTP 404 when trying to call API 调用返回大量数据的端点时 Integration Studio 出错 - Error in Integration Studio when calling endpoint that returns a lot of data 调用不带Header元素的服务时WSO2 ESB中的错误 - Error in WSO2 ESB when calling service without Header element SourceHandler Writer 在调用 informWriterError 时为 null,无法工作 - SourceHandler Writer null when calling informWriterError, fail to work WSO2网关-访问端口8243/8280上的页面但404可以访问时的404,因此所有运行404的API都会破坏我们的整个系统 - WSO2 Gateway - 404 when accessing pages on port 8243/8280 but 9443 working, so all APIs running into 404 breaking our whole system 在WSO2 API管理器上更改管理员密码会导致调用已发布的API时出错 - Changing admin password on wso2 api manager results in errors when calling the published APIs
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM