Page tree
Skip to end of metadata
Go to start of metadata

           HTTP To RFC Synchronous Scenario - FAQs

I have seen so many forum discussions on SDN related to the most common problems while doing the HTTP to RFC synchronous scenario described in Praveen Kumar's blog HTTP to RFC - A Starter Kit

Here are some of the most Frequently Asked Questions and their best possible Answers.

FAQ 1:           How many message interfaces I need to create in this synchronous scenario and why?

Answer:        You need to create only one outbound synchronous message interface, in this you have to specify the output and input message parameters. This message interface will be communicating with RFC function module for sending and receiving message.

FAQ 2:           In Integration Repository, while importing RFC from R/3 server, I am getting an error message Invalid User/Password Combination

Answer:        In most of the cases user knows his correct user name and password, but still he faces this problem. The reason behind is that in some of the XI support packs, you have to enter your password in upper case while importing the RFC from R/3 and while configuring the RFC receiver communication channel.

FAQ 3:           I know that while configuring the HTTP and IDOC scenarios, there is no need to configure the sender communication channel and sender agreement, but why?

Answer:        In Netweaver application platform there are two engines i.e. J2EE Engine and ABAP Engine, Sender Agreements need to be configured only for the adapters those resides on J2EE Engine. The adapters like HTTP and IDOC, which resides on ABAP Engine can directly interact with Integration Engine of XI, hence there is no need to configure the sender communication channel and sender agreement for HTTP and IDOC adapter.

FAQ 4:           How can I test my scenario? What is the HTTP client Tool and where I can find this tool to test my scenario?

Answer:        You can test your scenario using the HTTP Client tool or using RWB (Runtime Workbench). HTTP Client tool is an HTML application, used to test scenarios where message is coming from HTTP side.

Below is a link to James Guanzon's article "HTTP Client Sample Code for Communicating with XI 3.0", you can copy the code from this article and paste it in a notepad, save it with the extension .html. Open this HTML application and fill the details as mentioned in article and press the send button, you will get the response in the result section of the application.

You can also test your scenario using RWB tool. Use Runtime Workbench > Component Monitoring > Integration Server > Integration Engine > Test Message

FAQ 5:           For testing purpose we use HTTP Client tool, but how we can setup this scenario in real time?

Answer:        In real time scenarios, a call will be made from an HTTP/Web page using the HTTP post method. You need to provide the URL (which you will get in URL section of HTTP Client tool after testing your scenario) to your client; this URL will be used to point to XI for sending the message from an HTTP/Web page.

 FAQ 6:          I am getting errors while sending message from HTTP Client Tool

                     e.g. Error 200, 400, 403, 404, 405, 500 etc

Answer:        For all the errors related to HTTP you can refer to Krishna Moorthy's blog HTTP Errors in XI

FAQ 7:           After sending message from HTTP Client tool, I am getting errors in SXMB_MONI                 

Error 1           Error Category            XI_J2EE_ADAPTER_ENGINE

                      Error code                   CHANNEL_DETERMINATION_FAILED

Answer:        There could be couple of reasons behind this problem:

You can check receiver agreement, i.e. your receiver channel.

In Integration Directory, go to Tools -> Configuration Test, here provide the sender and receiver service details and press the run button on upper left corner. It will give you the details about your configuration. Make sure there is no step remaining with red light status.

If every step is showing green light status, then check the status of your receiver communication channel in RWB adapter monitoring. It must be showing the green light status.

If it is ok and still you are facing the same problem then do the cache refresh in full mode.

http://<host>:<J2EE Port>/CPACache/refresh?mode=full

Error 2           Error Category            XIServer

                      Error code                   CANNOT_READ_PAYLOAD

Answer:        Check whether your payload message which you are passing in HTTP Client tool is correct or not, try to copy the payload from Integration Repository while testing your mapping program.

Also check the Integration Engine Configuration runtime parameters,

Open Transaction SXMB_ADM -> Integration Engine Configuration -> Change Specific Configuration

Check the values of below given parameters for runtime category, these values must be maintained:


FAQ 8:           What is the use of SMICM transaction in this scenario?

Answer:        Transaction SMICM can be used to know the HTTP port of your XI system.
SMICM -> Goto -> Administration -> Services, here you will get the HTTP port.

FAQ 9:           Where do I use this HTTP port?

Answer:        While sending the data from the HTTP Client tool, you have to fill the parameters like server name and port. You have to mention the above port there.

FAQ 10:         What is the use of SICF in HTTP to RFC scenario?

Answer:        Transaction SICF is used to maintain the services. Since this is the job of XI Technology consultants, you need not worry about it.

All you need to do is run program RSXMB_ACTIVATE_ICF_SERVICES and make sure all the services are up and running (green flag), if not then contact your admin team.

FAQ 11:         How can I configure secure HTTP connection?

Answer:        Refer to the below mentioned SAP document to configure a secure HTTPS connection.

IF you have any other question, refer to Michal Krawczyk's most popular blog

XI/PI FAQ (Frequently Asked Questions)