Sender Agreement for http adapter

[Former Member]

Hi

I have a scenario like http-xi-rfc. Here due to security reasons we have

sender agreement. This sender agreement is causing problem and really we can't

test the interface with http test client or from RWB. It always gives the below problem

Error while sending message: 500 Error during Sender Agreement Determination

Could you plz advise how to test this interface with RWB ?

Thanks

kumar

[Former Member · Accepted solution]

Hi....

You can test the scenario by using Microsoft Infopath. Just try that once.

Regards,

Leela

[Former Member]

Now able to test the message...

[prateek]

For option "Security Check for Incoming Messages", what are you using?

Make sure that if SSL is enabled, you are using https protocol to send data from http client.

@Rajiv, Amar - the channel is required in this case as it is already mentioned that some security procedures has been implemented.

Regards,

Prateek

[Former Member]

Hi! Palnati Kumar,

According to my knowledge....I think there are two radio buttons for sender HTTP and Receiver HTTP and the thing is in XI 3.0 sender CC is there Inactive stage in ABAP stack. Hence that is why there is no need of creating Sender Communication Channel for HTTP Adapter and also since IDOC and HTTP are in ABAP stacks no need of Sender CC since they will communicate the message the directly with the Integration Engine that is what it wont pass through first via Adapter Engine.

Since Sender Agreement configures Sender Commnication Channel hence no need of creating sender agreement.

But in Case of PI 7.0 or else 7.1 that option is in ACTIVE and the main purpose is either you can use this sender HTTP or else no need eeven though u are using it will acts as a dummy.

I think in your Scenario you are using PI version and due to some security reasons you are using this Sender HTTP as it is in active and mostly you are using HTTPS protocal due to security purpose.

1.

Now also check in SICF and HTTPS port serive may be the port number is not fine that means actually while installing the PI suppose for HTTP instead of 80 port number they will replace that 80 with PI application port number like 50000 some thing and defalutly the PORT number for HTTPS is 443 but in some projects they wil replace with 50001 or 50002. it means that particula PORT number is linked with the PI application Server host name.

2. Also there is another issue due to your N&S settings FIREWALL settings if suppose if they disable the HTTPS port or some other settings you can allow to use HTTPS protocol even though there is no issue with PI. Hence ask your Network teeam to enable the HTTPS port.

Regards:

Amar Srinivas Eli

[Former Member]

Hi,

HTTP adapter resides on integration server..................so there is no need for a sender agreement for a HTTP req msg..............from your source HTTP application, you will sending your HTTP req msg to your XI integration server using the URL which is defined in your Integration Engine configuration in SXMB_ADM transaction..............so remove your sender agreeement from ID and test your scenario by sending a HTTP req msg from your source HTTP application.

Regards,

Rajeev Gupta

[samiullah_qureshi]

HI,

You can also test your scenarion from RWB. In RWB

go to Component monitoring ---> Adapter Engine -

---

> Test Message.

Also give the credentials there.

This will directly post the message to the integration server.

Regards,

Sami.