Https Soap Adapter

Hello,
I'm developing scenario Sender Soap Adapter using https.
How to configure o https?
Thanks.

Hi Aroldo,
This might help you
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm
Thanks & Regards,
Agasthuri Doss

Similar Messages

Error Https SOAP Adapter:NoSuchAlgorithmException: No such algorithm: RSA

Hi,
I'm using a SOAP Adapter Receiver to integrate a file to an External WS (with HTTPS). But when I tried to execute It I got the following error:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA: iaik.security.ssl.SSLException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA
SOAP: call failed: iaik.security.ssl.SSLException: Unable to encrypt preMasterSecret: java.security.NoSuchAlgorithmException: No such algorithm: RSA
I think It is a problem with the creation of the secure channel of HTTPS.
Any tip is very welcome!!
Thanks
Martin

http://java.sun.com/j2se/1.4.2/docs/guide/security/jce/JCERefGuide.html#AppA
there is not much info to find about who provides for RSA.RSA is already implemented in the Crypto-Provider by Sun. You don't have to laod a special provider.
The following sample is just enough:
Cipher cipher = Cipher.getInstance("RSA");Jan

Difference between Https & SOAP adapter

Hi Experts
What is the difference between Web srvice and Http request, when do we used each of them
Thanks
RP

Dear PR,
Use of HTTP: communication between website and XI, for example you are sending information from webpage forms via post method.
Use of SOAP: With many sophisticated web application and services and even between two XI system.
HTTP Adatpter Vs Soap Adapter
HTPP Adatpter Vs Soap Adapter ????
Difference between SOAP and Http Sender
Difference between SOAP and Http Sender
Plain HTTP Adapter vs SOAP Adapter with regards to SSL
Plain HTTP Adapter vs SOAP Adapter with regards to SSL
Difference between SOAP and HTTP:
SOAP in background uses XML + http
you expose outbound interface as a webservice and create a SOAP request to access it.
you send http request to ping a integration scenario directly at the integration engine
You can use HTTP adapter for interacting with HTML pages.
SOAP adapter is used for exposing an interface as Web service.
Thanks,
satya Kumar

Http & Soap Adapter

Hi Experts,
1. I am Having a small query in using the SOAP & HTTP Adapters. When to use these adapters and in what type of interfaces.
2. While Using ABAP Mapping, In Interface Mapping we cant see ABAP Mapping, we can see XSLT, JAVA but not ABAP. So where can we get it and how can we use it.
Please let me know ASAP i need to implement them now.
Regards,
Nissi

Hi Nissi,
>> I am Having a small query in using the SOAP & HTTP Adapters. When to use these adapters and in what type of interfaces
SOAP: When you want to consume your client's webservices or you need to host webservice for your clients then you will use SOAP. In first case you use SOAP reciever and second case use SOAP sender.
Note: SOAP internally uses HTTP or HTTPS protocol for the transport purpose.
HTTP: When you want to post data to a web application (example a java application or .net application that is hosted on the web application server and we can use thin client(browser) to utilize it) then we can use HTTP adapter to POST data.
Note; SAP PI 7.3 (latest version) supports both POST as well GET. All previous versions support only POST.
If your client or external system uses web server and host web application , in this case you use HTTP receiver adapter to post data to that system. If they want to post data using HTTP protocol via PI then you will use HTTP sender adapter.
>> ABAP Mapping
ABAP mapping: Default installation comes with java, xslt and message mapping. We need to change exchange profile parameter to achieve this.
Baskar

Error using Sender SOAP adapter over HTTPS

Hi experts,
Few weeks ago, i developed an interface as follows: SOAP <-> XI <-> RFC.
I tested the functionality using Altova and everything went well, with HTTP.
However, when i use HTTPS it fails throwing these error messages (pop ups):
"HTTP error: could not post file"......
"Error sending the soap data"
I have reviewed the SSL certificates installation and everything seems to be ok, but currently i am stuck and do not know how to fix this.
I have also change the ID comm channel from HTTP to HTTPS with client aut.
Is there any special service i have to activate? (XI services and SPIGATE are already done)
Could you please assist?
Thanks in advance and best regards,
David

David,
have a look @ these threads...u may get some help!!!
Sender Soap with HTTPS
https Soap Adapter
Regards
Biplab

HTTP Header fields in SOAP adapter

Hi All,
I have a scenario IDoc to SOAP adapter. In which my receiver given the details as
URL : https://b2b.ecsc.us.gxs.com/invoke/GXSGateway:receiveCTE
Header Name: Header Value
Ent-sender xxxx
Ent-receiver yyyyy
Ent-APRF zzzzz
Ent-filename (not sure what data need to give)
1. I request you to let me know where I need to give these headername and hader values in soap adapter.
2. my client require file as an attachment. Please let me know how I need to send the payload as an file and where the name need to be given in the header name (Ent-filename).
Currently I used MessageTransformBean to conver my XML to text structure(flatfile structure).
Please let me know if any more details required
Regards,
Dhill

Was out for lunch break..
Juz Rechecking
Transport Protocol : HTTP
Message Protocol: Soap 1.1
Adapter Engine -> Adapter Engine on the Integration Server
Connection Parameters
Target URL - > https://b2b.ecsc.us.gxs.com/invoke/GXSGateway:receiveCTE
Sure about no sever authentication required and they are not using any HTTP proxy for webservice >????
Conversion Parameters
Do Not Use SOAP Envelope -> Unchecked
Keep Headers -> Checked.
Keep Attachments -> Unchecked
Use Encoded Headers -> Unchecked
Use Query String -> not so sure might be Unchecked
Authentication Keys
If authentication is required for the receiver system, you can enter a password and a confirmation for each key value. This means that you do not need to write passwords in the enhanced message header.
If you want to specify or display authentication keys, select View Authorization Keys.
You can enter and confirm passwords for each authentication key value (TAuthKey or TproyxAuthKey).
Try once sending the message with Adapter-Specific Message Attributes
Unchecked. See if there is a hit.I knw itz not req but juz testing.
Yeah adapter stat must be active.
Last thing need to go through the whole scenario.
Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*

HTTP Header fields in SOAP adapter - Part 2

Hi All,
With regards to my previous thread HTTP Header fields in SOAP adapter
my header issue is solved and hence I have closed the thread but still I am not able to make the connection successful. The new problem is below
My vendor requirement is to specify the header as "Ent-sender" but when we give the same in XI in communication channel it automatically convets into uppercase "ENT-SENDER". Due to case-sensitive in vendor server the connection is not gettingestablished.
Please help me out how to solve the problem.
Note: Sorry for the new thread as it was created due to new problem and also the previuos thread is already too long.
Regards,
Dhill

Hi Neaves,
Thank you, I jave seen the note and find the below solution will be some what realated to my prblem.
The nosoap mode lets the adapter send the XI payload directly without wrapping it in the SOAP envelope. Although the main use of this mode is to send some plain text content directly to some web server, one can use this mode to send their own SOAP message (e.g., with arbitrary headers) to an external web service (See related questions). In this case, the XI payload must be formatted in the SOAP envelope.
To use the nosoap mode, the channel must be configured to use no SOAP envelope.
If yes, can you please let me know how to use nosoap mode otherise let me the other possibilities. I am already using tcpg2.zip to trace the SOAP adapter in which it was confirmed that XI is changing the header automatically into CAPS whatever case we give,
Regards,
Dhill

Special characters in sender soap adapter provoke HTTP 500 error

Hi,
SAP R3 is sending a SOAP message to PI through SOAP adapter.
When the payload does NOT contain german characters like ü, it works fine.
However, when the payload DOES contain special characters, the SOAP adapter replies with an HTTP 500 code error.
If I use SoapUI to send the soap message, and setting UTF-8 as the encoding in the program options, it will go through fine. If I change to ISO-8859-1 it will fail.
I'm thinking in two options:
- Make sure that SAP R3 sends the message in UTF-8 format (I think this is happening currently), as if SoapUI works, then probably R3 is not using UTF-8.
- Force the adapter to use UTF-8. Is this possible? In the sender SOAP adapter I've added AF_Modules/MessageTransformBean (type local EB), and then Transform.ContentType for parameter name and --> text/plain;charset=utf-8 for parameter value. The sender adapter will fail then for every message, with or without special characters.
Anyway, in this link (http://help.sap.com/saphelp_nwpi71/helpdata/EN/a4/f13341771b4c0de10000000a1550b0/frameset.htm) it seems to say that the sender soap adapter cannot be extended with modules, so maybe that's the reason why it fails when trying to add a module.
Thanks

If I use SoapUI to send the soap message, and setting UTF-8 as the encoding in the program options, it will go through fine. If I change to ISO-8859-1 it will fail.
I'm thinking in two options:
Check the use of option 1 ..... the URL which SAP is using to send the data can containe the encoding information.
Check this SAP note: https://service.sap.com/sap/support/notes/856597
From the above note:
Q: What character encoding is supported by the SOAP sender adapter?
+you can supply the encoding information with the xmlenc variable in the request URL as in+
Regards,
Abhishek.

SOAP adapter: port, logging/tracing, http/https

Hi,
several questions concerning SOAP adapter:
SAP XI 3.0 SP19 used.
Scenario 1:
SOAP request adressing J2EE port
http://host:8000/XISOAPAdapter/MessageServlet?channel=Partner:Service:SOAPSenderChannel
Scenario 2:
SOAP request adressing ABAP port
http://host:50000/XISOAPAdapter/MessageServlet?channel=Partner:Service:SOAPSenderChannel
Question 1:
What happens with a SOAP request adressed to the ABAP port?
Obviously it is forwarded to the J2EE port but where is this forwarding function documented
and is it allowed in every case to send SOAP messages to ABAP port?
Question 2:
What logging and tracing functionalities do i have in both scenarios before the message enters (before RWB)?
E.g. where can i see unsuccessful requests (e.g. if there is mistyping in SenderChannel).
Then it not visible in Runtime Workbench but whereelse?
If the ABAP port is adressed i see something in SMICM trace file, but very cryptic and not conclusive.
Do you know further trace/log files for both scenarios (Visual Admin?) ?
Question 3:
What is the difference if https is used concerning logs and traces?
Do i have more or less possibilities?
Thank you very much in advance for comments.
Michael

Hi
The URL sent to the ABAP port and the J2EE port are different.
The URL to the ABAP port is documented in this blog by Stefan,
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Answering question 1 --> As the URL are different, the Request in case of the ABAP stack hits the Integration Engine directly - into the pipeline of XI and bypassed the Adapter Engine competely.
As stefan's blog states - you cannot post multipart SOAP request to the IE directly.
Question 2 - If the URL is incorrect, if the request hits XI then you will have the log in XI ( in MONI in case of ABAP port ) and in RWB -Message Monitroing ( in case of J2EE port)
Regards
Bhavesh

Enabling HTTPS with Client Authentication for Sender SOAP Adapter on PI7.1

Hello All,
We are currently building up a HTTPS message exchange with an external client.
Our PI 7.1 recieved over HTTPS messages on an already configured Sender SOAP Adapter.
The HTTPS (SSL) connectivity works fine and was completely configured on the ABAP Stack at Trust Manager (TC=STRUSTSSO2)
Login to Message Servlet "com.sap.aii.adapter.soap.web.MessageServlet is required and works fine with user ID and password.
Now we have to configure the addtional Client Authentication.
At SOAP Adapter (Sender Communication Channel) under "HTTP Security Level"you are able to configure "HTTPS with Client Authentication".
But what are the next steps to get this scenario successfully in place?
Many thanks in advance!
Jochen

Hi Colleagues,
following Steps still have to be done:
- Mapping public key to technical user at Java Stack
As preparation you have to activate value "ume.logon.allow.cert" with true under "com.sap.security.core.ume.service" under Config Tool. At NWA under Identity Management at for repecively technical user the public key certificate
- Be sure CA root certivicate at Database under STRUSTSSO2
- Import intermediate Certificate under Certificate List at Trast Manager for the Respecive Server Note
- use Login Module "client_cert" which you have to configure under NWA\Configuration Management\Authentication for Components "sap.com/com.sap.aii.adapter.soap.app*XISOAPAdapter".
Many thanks to all for support!
Regards,
Jochen

SOAP Adapter Sender PI7.1: 400 Bad HTTP request

Hello,
I have a problem with a SOAP adapter sender communication channel.
I'm trying to migrate a scenario from XI 3.0 to PI7.1 SP6 (PI_BASIS 2006_1_710 SAPKIPYN06).
I can send messages successfully to the old system using the URL
    http://host:port/XISOAPAdapter/MessageServlet?channel=:BC_Name:CC_SOAP_Sender
On PI7.1 I get
    400 Bad HTTP request
    Error: -21
    Version: 7010
    Component: HTTP_PLG
    Module: http_plgrt_mt.c
    Line: 5226
    Error Tag:
    Detail: illegal request version
I have created a Sender Agreement, generated the wsdl from that and tried the URL in there.
Surprisingly it has the old format, namely
    http://host:port/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_Name&receiverParty=&receiverService=&interface=myInterface&interfaceNamespace=urn:my.Interface:ns
although the 7.1 documentation describes the ?channel=party:service:channel style only.
Anyway, the result remains the same.
I tried some other approaches like escaping the colons in the URL without success.
The user has the role SAP_XI_DEVELOPER_J2EE assigned.
Any idea what's wrong here?
Thanks in advance
Rainer

>>In RWB the channel appears as "started but inactive".
Yeah,it will be like that because you are posting messages directly to Integration server."Propose URL" does that.You are bypassing the adapter engine when you use the URL generated by "Propose URL" button.
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
The above blog gives the reason for this,if you want to bypass the adapter engine,then generate the URL as given in the above blog
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
This blog explains how to post message to adapter engine,here you need to change the URL,don't click on "Propose URL" button.You can monitor SOAP adapter in RWB only if you generate the URL as given in second blog
The URL which is working for you in XI 3.0 is posting messages to adapter engine,so generate the URL in PI 7.1 in the same way,by following the second blog i have mentioned.
Thanks
Aamir

PI 7.1 receiver SOAP adapter using https

Hi all,
In PI 7.1 receiver SOAP adapter using https, what are the configurations necessary in PI box?
Certification, and key store values, security etc etc
-Michael.

>
Michael Johnson wrote:
> I did n't find anything related to 7.1 version
Some leads are provided by help: http://help.sap.com/saphelp_nwpi71/helpdata/EN/56/992d4142badb2be10000000a1550b0/frameset.htm
Regards,
Abhishek.

Enabling HTTPS level authentication in SOAP adapter (PI 7.1)

Hi,
I am using SOAP to SOAP scenario using HTTPS level authentication in PI 7.11
As per the SAP Note https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=891877
We have enabled HTTPS level authentication in sender communication channel using SOAP adapter (version 7.0).
But We are not able to have the HTTPS level authentication option in sender communication channel using SOAP adapter (version 7.1) while selecting the adapter type.
Please suggest on this

Hello Gabriel,
You are right, that option is still available in PI 7.1
http://help.sap.com/saphelp_nwpi71/helpdata/EN/fc/5ad93f130f9215e10000000a155106/frameset.htm
But disappeared in PI 7.11
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/3555240bea31c3e10000000a42189d/frameset.htm
The closest seems to be under Security Profile S/MIME. And when you use the sender cc in sender agreement, you are given the choice for validation/decryption/decryption and validation/validation and decryption.
Hope this helps,
Mark

HTTP 415 Unsupported Media Type with SOAP adapter ?

Hello All,
Iam getting HTTP 415 Unsupported Media Type with SOAP adapter error while executing the scenario.
i got one thread which have the solution. iam not getting exactly how to write message transform Bean.
HTTP 415 Unsupported Media Type with SOAP adapter trying to put SOAP header
Please tell me where i need to write the MessageTransformBean at sender adapter or receiver file adapter.
Thanks and regards,
chinna

Hi Chinna,
Have you checked this
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
Regards
Ramesh

HTTP 415 Unsupported Media Type with SOAP adapter trying to put SOAP header

Hello,
I am trying to put data into soap header using soap receiver adapter. Seems like building the complete soap message is the right way to go. Thus I wrote a java program to build the complete soap message (soap envelop, soap header and soap body which contains the message PI received from the sender). Mapping program works well. However when I ran the scenario, I got Error "SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type" when calling the receiver's web service (the SOAP receiver adapter CC have the "Do Not use SOAP Envelop" checked). Anyone knows why I got this error? From google, seems like this error is because the http's content-type is set to other type, rather than "text/xml". However in soap CC there is no option to control this.
The message sent to the receiver is (after mapping);
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<SOAP-SEC:Signature xmlns:SOAP-SEC="http://schemas.xmlsoap.org/soap/security/2000-12" MyAttr="value">My Test Value</SOAP-SEC:Signature>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:UpdateEquipment xmlns:ns1="http://mycomp.com/mywebservice">
<ns1:EquipmentNumber>000000012345</ns1:EquipmentNumber>
<ns1:LicensePlate>654321</ns1:LicensePlate>
</ns1:UpdateEquipment>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Anyone can help?
Thanks

When you check "Do Not use SOAP Envelop", the SOAP adapter chooses application/xml instead of text/xml.
You can change the content type with help of the MessageTransformBean. You put the bean in the module chain of the receiver channel and add the parameter Transform.ContentType = text/xml
See
http://help.sap.com/saphelp_nwpi71/helpdata/EN/57/0b2c4142aef623e10000000a155106/frameset.htm

Https Soap Adapter

Similar Messages

Maybe you are looking for