on 12-31-2014 6:37 AM
Hi Experts
In the receiver SOAP coomunication channel,I ahve a field where I need to enter the URL address
the 3rd party ahs given me the url of the wsdl
https://x.x.x.x/abc/api/axis/Plugin_us_CustomerService?wsdl
while int he wsdl i could see 2 other url
http://persistence.service.databases.xyz.abc.com
http://model.databases.xyz.abc.com/
1. which URL should i use in the communication channel(other than hit and trial method)?
2. https://x.x.x.x/abc/api/axis/Plugin_us_CustomerService?wsdl
is the axis paramter which is beeing mentioned, has any relation if i have to use soap axias adapter?
Thanks!!
Hi Nunu,
My few cents,
2. https://x.x.x.x/abc/api/axis/Plugin_us_CustomerService?wsdl
is the axis paramter which is beeing mentioned, has any relation if i have to use soap axias adapter?
This means that your endpoint works with AXIS but this doesn't mean that you need to use SOAP (AXIS) adapter, from my experience it is better to avoid to use the AXIS message protocol if you can. The AXIS message protocol is useful for determinated scenarios, for example is you use attachments and you need to convert them to MTOM, to work with Rest services, to work with SOAP 1.2 and so on.
If you decide to work with AXIS in PI, first of all you need to install the libraries, you can check if they are already installed with this URL: http://host:port/XIAxisAdapter/MessageServlet
Hope this helps.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nunu,
As Azhar mentioned.
Using SOAPUI is simple approach.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nunu,
URL of WSDL is different from the Endpoint URL...you need to mention Endpoint URL in CC.
1. The url that needs to be called in the webservice are found in the XML tags <wsdl:port name="HTTP_Port"> and the <wsdl:port name="HTTPS_Port">
Both url mentioned in these tags are the URL's that are needed to call the web service.
2. You can try calling this url from web browser IE, it will check whether the SOAP Message Servlet is working or not. So the response you're getting is a good response.
3. Also you can importing the WSDL in a tool such as SoapUI, it will automatically generate an example message with the correct URL's and you can send a test msg to 3rd Party using SOAP UI tool and check.
Hope it helps.
Regards,
Azhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.