This is working fine in our development/UAT instances where as in production we do not get any request messages in PeopleSoft server. We have checked in errorLog.HTML as well as msgLog.HTML. No entry found on that.
Our Production server has multiple app sever domains. It has load balancing mechanisms also. This is the only difference between DVL and Prod instances.
Did you Provide the service in your Production environment and did you supply this WSDL to the 3rd party, because this will contain the endpoint to your Production environment Listening Connector.
Does the 3rd party receive any response?
Is this a sync or async service operation.
If async, PUB/SUB servers need to be defined on the appserver and the domain should be active.
Also check if queues are running that handle this service.
Have multiple appserver is not the issue, the appserver defined in the Gateway Configurtion will be the one that will handle the message.
In addition to previous post, what is the gateway url, is this the regular PIA gateway or the loadbalancer url?
This url will be places as the endpoint in the wsdl, and 3rd party systems will try to invoke the service operation at this url.
This could also explain why 3rd party are not able to reach your server, because they are not addressing the loadbalancer.
We have the load balancer URL in the WSDL end point. Finally we got a break through. We have tried hitting our PeopleSoft server with http url which worked out. When we try with the https url its not getting in.
I found following video "tutorial" very helpful is the past, perhaps it will help you too.
How To : E-WL: How to Setup/Renew SSL Certificate on WebLogic 9.2 or WebLogic 10.3? [Video]
We have imported the certificate as specified in the doc, but still we are getting the same error. For a third party application to consume a peoplesoft webservice through SSL, what should be done at the third-party side?
3rd party application should not do anything other that they are doing now.
Did you bounce the webserver?
Are you able to access the gateway locally through https?
If so maybe, you haven't correctly concatenated the root certificate an the certificate as described in the doc.
Not knowing the 3rd party system, maybe security of their site is withholding the certificate from being downloaded.
First make sure you are able to connect through https locally.
Import the WSDL file into a project in SoapUI en try to send an XML message (make sure you use the HTTPS endpoint). This program is the best for analyzing messaging through webservices. You'll find out soon enough if you're hitting a timeout.
I didn't see this step on the link mentioned above (didn't check the video though) so you might have missed this one which hopefully woiuld solve your ssl problem:
add the rootca and concatenated certificates online by navigating to Peopletools> security objects>digital certificates. restart your webserver afterwards.
we missed this step as well when we were setting up thirdparty connection through https. I agree with soapui as well, we use that to test our messages locally first.