Common issues seen during OMS-WCS Direct integration

Body

•  "org.xml.sax.SAXParseException" exception when testing a SCWC_SDF service on API tester?

        SCWC_SDF services belong to the Sterling OMS Service Definition Framework. These services are responsible for the conversion of the message content  and format between Sterling Order Management and WebSphere Commerce, when they are directly integrated.

When testing these OOB services in API tester, one may encounter “org.xml.sax.SAXParseException" exception.

This issue occurs when the Foundation jars from the Websphere Commerce server are not installed correctly on the SSFS server.

1. Make sure that all the Foundation core and server jars are copied to the SSFS server.

2. Install these jars using the 3rdParty install script.

3. Rebuild the EAR.

• Encountering "SC_INTERNAL_SERVER_ERROR=500" or "HTTP/1.1 403 Forbidden" error after direct integration of OMS with WCS?

After configuring the direct integration between WCS and OMS 9.3, one may encounter the "SC_INTERNAL_SERVER_ERROR=500" or "HTTP/1.1 403 Forbidden" when a WCS request is sent to Sterling OMS.

The above error occurs due to incorrect/missing two-way SSL authentication configuration.

Kindly refer to the below information center link for detailed configuration steps:
http://www-01.ibm.com/support/knowledgecenter/SS6PEW_9.3.0/com.ibm.help.integ.93wcsc.doc/t_ConfiguringTwoWaySSLAuthOnWC_sdf.html?lang=en

Also, the WCS transport URL's should use HTTPS.