Unable to Call a SOAP Provider in a Clustered Setup

Situation: A SOAP provider created in a single node environment "DEV" could not be called when the same PF & Webservice provider is deployed to the clustered/staging environment (2 node cluster) with staging LB URL. Following are the endpoints:

DEV endpoint - https://adeptiadev/wsx/Adeptia_WS_CreateDraftOrder_DocumentType

Staging endpoint - https://adeptiastg/wsx/Adeptia_WS_CreateDraftOrder_DocumentType

This issue had further findings

  1. WSDL exists in serverkernel/wsdl (Note: WSDL is a shared folder for both staging nodes in a cluster).
  2. server-config.wsdd is the same for both nodes.
  3. Synchronized the SOAP provider from UI.

Solution: There are certain points that are needed to check in order to make the SOAP WS work. In a clustered environment it is important to check the zip is deployed both the environments. If not, then you can check the below points to resolve this issue:-

  1. Check sun-jaxws.xml file in both nodes found under location “.\AdeptiaSuite-6.x\AdeptiaServer\ServerKernel\wsx\WEB-INF”, to see if you have begun points added on both the nodes.
  2. In case, if point 1 is not valid (the begun point is not added in both the nodes), then you zip should be deployed. If you don’t want to deploy the zip on the other node then please add the End point in the above file in a similar way to Node 1.
  3. Edit, Save and Synchronize the WS provider and then try to hit the WS Provider.
  4. Try to execute using SoapUI to see what response you are getting.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.