This document covers the following topics:
If you receive message 2000 0007: Incoming XML document is
invalid, there could be a difference between the mapping and the
document, for example an element-preferred mapping (XMM file) does not match
the SOAP document.
Deploying/calling an EntireX web service fails with
com.softwareag.wsstack.ui.deployment.DeploymentException: com.softwareag.entirex.xml.rt.WSSServiceLifeCycle.
For the Listener for XML/SOAP you need to set up a Web server and install Software AG Common Web Services Stack to this Web server. See Installing Web Services Stack in a Web Server.
After successful installation: If entirex.jar was not added to wsstack.war, copy or upload inst_dir/EntireX/classes/entirex.jar to the WEB-INF/lib folder in the Web Services Stack application folder.
Server does not start
Check classpath
If a file is not found:
Check location of property file, configuration file or XMM(s)
RPC Server for XML/SOAP starts but receives an HTTP error for several reasons. Check the received information fault document. If there is no information fault document, start RPC Server for XML/SOAP again with trace (level = ADVANCED) and analyze the trace (look for the fault document).
RPC Server for XML/SOAP gets the following error message: "Caused by:
java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl
cannot be cast to javax.xml.stream.XMLInputFactory". To correct the
error, modify the properties file by redefining the parameter for the XML
stream parser as follows:
entirex.sdk.xml.runtime.xmlparserfactory=com.ctc.wstx.stax.WstxInputFactory
RPC Server for XML/SOAP gets the following error message: "Error 2000 0082: Unknown RPC library or RPC program. ...".
Check that the XMM file containing this library/program is added to the RPC Server for XML/SOAP configuration file,
that is, the required TargetServer section is not commented out.
Note:
The default configuration file (entirex.xmlrpcserver.configuration.xml) contains the sample section TargetServer, which is commented out.
In any case, check the following:
Configuration file: TargetServer attribute "name" is not fully qualified
Name may require a domain specification
Name only contains target without service specification or/and with wrong port (non-default port)
Mapping
Mapping does not match service requirements
SOAPAction value is wrong or undefined
Connection cannot be established or connection failed
Wrong HTTP setting
Change / set Java properties
http.proxyHost,
http.proxyPort,
httpsproxyHost,
https.proxyPort
Application error (service side)
Use file <installation home>/profiles/CTP/configuration/logging/log_config.xml to configure the logging settings. The log file sag-osgi.log or wrapper.log is written to directory <installation home>/profiles/CTP/logs.
To analyse the log, search for lines containing "EXX" and check the status/error:
| EXX: Configuration Error: Reading configuration file fails. | |
| Explanation |
The entirex.servers.properties cannot be loaded. |
| Action |
The file must be located in directory <installation home>\EntireX\etc\exx\workspace and be accessible. |
| EXX: Reading configuration fails: File does not exist. | |
| Explanation |
The file entirex.servers.properties cannot be found. |
| Action |
Validate the installation. |
| EXX: XML/SOAP RPC Server does not start. Reason: :1:". | |
| Explanation |
The server cannot start for reason :1:. |
| Action |
|