Accepted Solutions (1)
Answers (5)
After configuring your scenarion in PI.....
Generating WSDL in SAP PI
There are two ways to generate WSDL in SAP PI.
- Open IB->Go to Tools-> Display WSDL
Complete the wizard steps and save generated WSDL.
- Open Sender agreement of your configuration scenario. Click on Sender agreement-> Display WSDL
Note: if it's ICO, use ICO->display wsdl
Save your WSDL from here.
Providing WSDL to third Party:
Save your WSDL from either of steps, mentioned above and provide it to sender application.
Sometimes third party expects WSDL URL instead of entire WSDL.
Extracting WSDL URL from WSDL:
In above steps a WSDL URL will be generated automatically. But it is recommended to provide WSDL URL in following standard format.
https://<server>:<port>/XISOAPAdapter/MessageServlet?senderParty=<sender party>&senderService=<sender component>&receiverParty=<receiver party>&receiverService=<receiver component>&interface=<outbound service interface>&interfaceNamespace=<interface namespace>
Best way to find your WSDL URL is,
Open your WSDL, find end point URL. It should be within <wsdl:port name>tag, under <soap:address location> tag at end of WSDL.
Replace “/ XISOAPAdapter/MessageServlet?” Or “/xi/engine” with “/dir/wsdl?”
And provide this URL to your sender application.
For example, your WSDL end point URL is,
https://abcd.nam.efgh.com:51101/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_XYZ &receiverParty=&receiverService=&interface=SI_AA_XYZ_OUT_Sync_SL&interfaceNamespace=aaa:bb.ccc.com:crm:xyz
So your WSDL URL would be,
https://abcd.nam.efgh.com:51101/dir/wsdl?senderParty=&senderService=BC_XYZ &receiverParty=&receiverService=&interface=SI_AA_XYZ_OUT_Sync_SL&interfaceNamespace=aaa:bb.ccc.com:crm:xyz
Issues while consuming your WSDL in third party application
Authentication failures:
If your PI server is password protected, sender needs to provide credential along with request message.
Otherwise it will give authentication failure as below.
Invalid WSDL:
Your WSDL URL or WSDL is not properly generated. Correct the WSDL or WSDL URL and provide it to sender application.
Otherwise it will give error while importing WSDL or WSDL URL as below.
Inbound Security Checks / Certificate issues:
In sender communication channel there are 3 options for HTTP security level.
It depends on sender application, what level of security it wants to be implemented between sender and PI.
HTTP
Simple HTTP request will be send to PI server.
HTTP doesn’t incorporate any security over outgoing and incoming request and response. It's like sending plain text over internet.
That means any third party can interfere our message. Though it uses encoding techniques like UTF-8 etc. but it can be easily decoded.
HTTPS
HTTPS provide transport level security along with message level security.
Normally it creates a secure session between client and server and transfer request and response message through it in an encrypted format.
HTTPS uses SSL (secure socket layer) certificates to provide security between client and server communication.
In simple language, using certificates means your client knows on which server it's sending data and server knows from which client data is being received. So that it cannot be tampered in between by any third person.
HTTPS always required client side authentication at least. It doesn't matter that you provide it by exporting server certificate or by using self-signed certificate. Depends on your server configuration whether it allows without client authenticated request or not.
There are two options in SAP PI to communicate using HTTPS connection.
HTTPS without client authentication
Sender application needs to trust our WSDL URL in order to communicate with PI.
In this approach client don’t have to authenticate its self to server. Only client needs to know, where it's sending data by exporting server certificate or by using self-signed certificate, if server certificate is not available.
It ensures only transport level security
HTTPS with client authentication
In this approach you need to exchange SSL certificates between client and server. Without authentication between both, communication is not possible and you will get certification or SSL error at sender application.
These certificates are generated and provided by some authentic vendors. You can also create these certificates at client and server application if it allows.
It also ensures message level security if you use digitally signed certificates along with transport level security.
This is the most secured way to communicate over internet.
| User | Count |
|---|---|
| 85 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.