Https on sender http adapter

Hello Gurus,
we have a synchronous XI from HTTP Sender adapter to RFC. The user of the interface would like to call it using the plain HTTP adapter with HTTPS. When we use the http port with the XI user/password as part of the url, it works OK. When we switch to the HTTPS port the interface does not provide a response. When we call the https url directly in Internet Explorer we get a pop-up requesting the user/password. Once
this is entered the interface works OK until the ie session in closed.
So can you please tell me what might be d problem?
If i m calling it from http client it is not giving me response, and if m calling it directly then also it is asking for user id and password.
Any help is appriciated.
Thanks,
Hetal

Thanks Swarup.
I already have configured SSL.
But how i can make sure that what i need to use and how can i specify from below :
HTTP with SSL (= HTTPS), but without client authentication
HTTP with SSL (= HTTPS) and with client authentication
Which i need to use?
And if what shold be the url for that?
right now m using url like :
https://hostname:httpsport/sap/xi/adapter_plain?namespace=xyz&interface=xyz&service=xyz&party=&agency=&scheme=&QOS=BE&sap-user=xyz&sap-password=xyz&sap-client=xyz&sap-language=EN
Can you please tell me how i have to specify that as we do not configure HTTP Sender adapter?
Thanks,
Hetal

Similar Messages

How to use HTTPS with sender SOAP Adapter

Hi,
I am implementing a synchronous SOAP- proxy scenario and on the sender communication channel I have to use the Http Security Level as "HTTPS with client Authentication".
Where from I get the certificates to be used in sender Agreement.
Please give me a step by step approach to achieve this.
Regards,
Nitin

Nitin,
Kindly go through the below links ...
http://help.sap.com/saphelp_nw04/helpdata/en/1f/7e2441509fa831e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
Also, make a search on the SDN as this question has been answered many a times on the forum.
Regards,
Neetesh

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.

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

Sender SOAP Adapter with Https

Hi,
can any one give me information on how my Sender SOAP adapter to be configured with HTTPS port.
please give me the what are all different ways to make my Sender SOAP Adapter secure and give me the steps to achieve the functionality.
Thank You,
Madhav

check this section:
http://help.sap.com/saphelp_nw70/helpdata/EN/14/ef2940cbf2195de10000000a1550b0/frameset.htm
Also some help from SAP note:
https://service.sap.com/sap/support/notes/891877
Regards,
Abhishek.
Edited by: abhishek salvi on May 29, 2009 1:59 PM

Sender http adapter - decoding (URL unescape)

PI 7.0
Incoming http request in XI is URL decoded. Currently I am using java mapping to decode it. Is there a way to set any adapter specific properties in sender http adater so that I can avoid the java mapping for decoding. Or any settings in SICF? In other words, how can XI handle encoded http requests?
When XI makes a external http request, I can set a property "Mask Special Charcters (URL Escaping)" in the receiver http adapter. XI will make a encoded http request, meaning the xml will encoded in UT-8.

Hi Ted,
I'm currently trying to do something like that, but not yet totally successed with a base64 encoded payload.
Here two documents that I really find interresting:
How to Configure Message Level Security in SAP Exchange Infrastructure 7.0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d024ca8e-e76e-2910-c183-8ea4ba681c51
How to handle unstructured source contents for Adapters (with Java mapping or with Module)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/482aae19-0301-0010-3485-8efd618818d0
if you find others... I'm ok to know it also
Cheers.
Mickael

HTTPS sender soap adapter

Hi,
I want to use HTTPS port for one of our SOAP -->RFC sync interface .
currently we are using http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel this url and its working fine,
Here we want to use HTTPS ( HTTPS with client authentication as security level) ,but in our current PI system ( 7.31) is not enabled https/ports.
Please let me know how we can enable HTTPS port ,let me know the process.
once HTTPS port is enabled please let me know the process to use HTTPS with client authentication as security level)
Thanks
Surya

Hi Surya,
Base on your requirement ports like 433, 4022 etc as per availability to Trading partners.
Port mapping should be done in the firewall configuration as your web dispatcher port(This information can be obtained from your basis team / will be managed at the installation time / netweaver administration.)
80* series is for ABAP ports and 50* series i sfor JAVA port.
Also check the below link for more information.
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/09/20/sender-soap-adapter-https-with-client-authentication
Thanks and Regards,
Naveen

How to catch the sender SOAP adapter http response?

Hi eXperts,
I've a sender soap adapter opened to customer as webservice. When customers call this webservice, data is coming into XI and works fine. But the customer is complaining that the expected HTTP 200 response is not sent back to the calling SOAP client.
So my question is: Is there a way to catch the http 200 response from sender adapter, or at least get to know if the sender adapter has sent the response?
Thanks in advance.
Regards
Luis

Hi,
If I understood it correcly... Sender is a Async SOAP call and the sender system is expcting a status back of HTTP 200. Are you sure you had set the quality of effort to Exactly Once? If not please try setting it.
You can also go to Adapter monitoring or Communication channel monitoring in the Runtime workbench and see if the Sender SOAP adapter is fine.
http://help.sap.com/saphelp_nw04/helpdata/en/5e/164442c1a1c353e10000000a1550b0/content.htm
Thanks,
Prakash

Test Http(s) sender adapter

Hi,
I already done all the configuration for ssl and also create a http(s) sender adapter to retrieve data using rfc. May i know normally how you test the https sender?
Thanks.

Hi,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/66dadc6e-0a01-0010-9ea9-bb6d8ca48cc8
The html code in this link works perfectly to send a http request.
Just replace the userID & password in the html code with yours and try it.
Another simplpe method : just send your message via Runtime Workbench, there is a test tool to send messages directly to Integration Engine (the http adapter is doing the same).
Regards,
Divya

PI Sender HTTP adapter restricting access by IP

We have a web service hosted on PI and we would like to limit access to this web service to only one web service client application. This is a high volume interface and not particularly sensitive data so we are not really looking for the SSL overhead. Is there any way other than SSL or using the HTTP logon procedure of AS-ABAP to restrict access to this web service? For example, can we specify anywhere on the AS or in the configuration of the PI Sender HTTP adapter that only requests from a certain IP addresses be processed?

If you do not care about security then pass some basic authentication in the form of userid and password in either the header fields or in the url parameters. These could then be authenticated in the Web Service - though this is not ideal

Sender HTTP Adapter working intermittently

HI ,
My scenarios is HTTP->XI.>ECC,
Sender HTTP Adapter is working intermittently some times data is not reaching to XI though it sent successfully from Source.
We are unable to find the logs in XI where this data went.
This interface is working fine in PI 7.1 and now in migration to PI 7.3 ( have Two application server dispatcher model) this interface is working intermittently .
Please provide any inputs on this intermittent issue for sender HTTP adapter.
Data sent successfully from source side and no message is received to XI MONI. Please guide me where can I check for the logs and error details

Hi Krishna,
If your PI is dual stack and you are not using the http_aae you can trace the http in the ABAP stack. Go to smicm transaction and set the trace level to 2 or 3.
In Quality system you can talk with your sender client in order to prepare a set of requests in oder to find out if the requests are reaching to PI or not and what exception could be.
hope this helps.
Regards.

Sender HTTP Adapter User Authorizations

Someone knows what are the authorizations that must have the user used in a Sender HTTP Adapter?

Hi,
User must have role SAP_XI_APPL_SERV_USER on Integration Server.
This will give you more Idea
http://help.sap.com/saphelp_nw2004s/helpdata/en/ca/fafaf6dbc8b240b1cf4a88c40379b2/frameset.htm
Regards
Agasthuri Doss

HTTPS SOAP Sender Adapter Error

I have a SOAP client connecting to XI through HTTPS. SOAP Channel is configured to receive HTTPS request. We have been receiving messages successfully but the following error message occurs intermittently:
Error text from the Adapter Engine: java.security.AccessControlException: https scheme required
I don't see anything in SXMB_MONI. I don't see anything in RWB on the adapter message monitoring.
This scenarios is synchronous.

hi rodel,
You need to configure the HTTPS security level.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/64dbb0af9f30b4e10000000a11466f/content.htm
regards
Ramesh P

Error while XI and xMII integration (Plain HTTP as sender)

Dear Friends,
   I am doing the scenario XI and xMII integration. While sending the input file from plain HTTP adapter the result comes as follows in *sxmb_moni* :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1/>
<SAP:P2/>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: <xMII server name></SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack/>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In HTTP Client Adapter for XI 3.0 it is shown as follows:
<SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL
</SAP:Code>
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: <xMII server name> </SAP:AdditionalText></SAP:Error>
Please show the way to rectify this error.
Regards,
Jagan.

Dear Sudharshan,
   I'm doing the scenario which is in the following blog.
/people/dhanabal.thangavel/blog/2008/02/07/xi-and-xmii-integration--part-1 ==> XI and xMII Integration - Part 1
This is a synchronous one. So I set QOS as BE in Client Http Adapter for XI 3.0.
Scenario is HTTP <--> XI <--> xMII
The following errors are I found:
1) In RWB -> Message Monitoring
Status : Canceled with Errors
Message Details:
SOAP : call failed
SOAP :error occured: java.net.UnknownHostException: <HOST>
Exception caught by adapter framework: <HOST>
Delivery of the message to the application using connection AFW failed, due to: <HOST>. Setting message to status failed
The message status set to FAIL.
Returning synchronous error message to calling application: <HOST>.
2) Error coming in the Client Http Adapter for XI 3.0 as follows:
*URL:*
http://xxxxxx07:xx10/sap/xi/adapter_plain?namespace=http%3A//www.xxxxxxx.com/XIBatch3/10099/xMII_Integration&interface=xMII_Integration_Sync_Outbound&service=BS_BATCH3&party=&agency=&scheme=&QOS=BE&sap-user=xxxxx&sap-password=xxxxx&sap-client=xx1&sap-language=EN
*Result:*
<SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException:<HOST></SAP:AdditionalText></SAP:Error>
*Input XML file:*
<?xml version="1.0" encoding="UTF-8"?>
<ns1:XacuteRequest xmlns:ns1="http://www.lighthammer.com/Xacute">
   <ns1:LoginName/>
   <ns1:LoginPassword/>
   <ns1:InputParams>
      <ns1:ProductName>ProductA1</ns1:ProductName>
   </ns1:InputParams>
</ns1:XacuteRequest>
*WSDL file (Which is generated using the xMII transaction):*
<?xml version="1.0" encoding="UTF-8"?><definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.lighthammer.com/Xacute" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.lighthammer.com/Xacute">
    
    <types>
        <s:schema elementFormDefault="qualified" targetNamespace="http://www.lighthammer.com/Xacute">
            <s:complexType name="InputParams">
                <s:sequence id="InputSequence">
                <s:element maxOccurs="1" minOccurs="0" name="ProductName" type="s:string"/></s:sequence>
            </s:complexType>
            <s:element name="XacuteRequest">
                <s:complexType>
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="0" name="LoginName" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="LoginPassword" type="s:string"/>
                        <s:element maxOccurs="1" minOccurs="0" name="InputParams" type="s0:InputParams"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
            <s:complexType name="Rowsets">
                <s:sequence>
                    <s:element maxOccurs="1" minOccurs="0" name="FatalError" type="s:string"/>
                    <s:element maxOccurs="1" minOccurs="0" name="Messages" type="s0:Messages"/>
                    <s:element maxOccurs="1" minOccurs="0" name="Rowset" type="s0:Rowset"/>
                </s:sequence>
                <s:attribute name="StartDate" type="s:dateTime" use="required"/>
                <s:attribute name="EndDate" type="s:dateTime" use="required"/>
                <s:attribute name="DateCreated" type="s:dateTime" use="required"/>
                <s:attribute name="Version" type="s:string"/>
            </s:complexType>
            <s:complexType name="Messages">
                <s:sequence>
                    <s:element maxOccurs="unbounded" minOccurs="0" name="Message" type="s:string"/>
                </s:sequence>
            </s:complexType>
            <s:complexType name="Columns">
                <s:sequence>
                    <s:element maxOccurs="unbounded" minOccurs="0" name="Column" type="s0:Column"/>
                </s:sequence>
            </s:complexType>
            <s:complexType name="Column">
                <s:attribute name="Name" type="s:string" use="required"/>
                <s:attribute name="Description" type="s:string" use="required"/>
                <s:attribute name="SourceColumn" type="s:string" use="required"/>
                <s:attribute name="MinRange" type="s:double" use="required"/>
                <s:attribute name="MaxRange" type="s:double" use="required"/>
                <s:attribute name="SQLDataType" type="s:int" use="required"/>
            </s:complexType>
            <s:complexType name="Rowset">
                <s:sequence>
                    <s:element maxOccurs="1" minOccurs="1" name="Columns" type="s0:Columns"/>
                    <s:element maxOccurs="unbounded" minOccurs="0" name="Row" type="s0:Row"/>
                </s:sequence>
            </s:complexType>
            <s:complexType name="Row">
                <s:sequence id="RowSequence">
                <s:element maxOccurs="1" minOccurs="1" name="Quantity" type="s:long"/><s:element maxOccurs="1" minOccurs="1" name="ProductName" type="s:string"/></s:sequence>
            </s:complexType>
            <s:element name="XacuteResponse">
                <s:complexType>
                    <s:sequence>
                        <s:element maxOccurs="1" minOccurs="0" name="Rowsets" type="s0:Rowsets"/>
                    </s:sequence>
                </s:complexType>
            </s:element>
        </s:schema>
    </types>
    
    <message name="XacuteSoapIn">
        <part element="s0:XacuteRequest" name="parameters"/>
    </message>
    <message name="XacuteSoapOut">
        <part element="s0:XacuteResponse" name="parameters"/>
    </message>
    
    <portType name="XacuteWSSoap">
        <operation name="Xacute">
            <input message="s0:XacuteSoapIn"/>
            <output message="s0:XacuteSoapOut"/>
        </operation>
    </portType>
    
    <binding name="XacuteWSSoap" type="s0:XacuteWSSoap">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="Xacute">
            <soap:operation soapAction="http://www.lighthammer.com/Xacute" style="document"/>
            <input>
                <soap:body use="literal"/>
            </input>
            <output>
                <soap:body use="literal"/>
            </output>
        </operation>
    </binding>
    
    <service name="XacuteWS">
        <port binding="s0:XacuteWSSoap" name="XacuteWSSoap">
            <soap:address location="http://<XMII_SERVER_NAME>/Lighthammer/SOAPRunner/Jagan/SDN_Fetch_Product_Qty"/>
        </port>
    </service>
</definitions>
Regards,
Jagan.

HTTPS Port for SOAP Adapter PI 7.1 (XI)

Hello Colleagues,
we plan to configure an Sender SOAP Adapter (without SOAP envelope) as HTTPS message receiver with HTTP Security Level "HTTPS with Client Authentication".
Does anyone know if this works and which port will be used. For my understanding it must be 443.
If not, it's possible to change the port to 443?
Regards,
Jochen

Hi Prateek,
many thanks!
Where can i do the port change?
Many thanks in advance!
Regards,
Jochen

Https on sender http adapter

Similar Messages

Maybe you are looking for