PI to PI communication

[Former Member]

Dear Experts,

We have a scenario from PI to PI .

R3 ---> Cust PI ---> Local PI ---> R3

We have to change the namepace, and message interface names. what are the changes to be made from our side to ensure that

the changes we make do not affect the soap header send to to cust PI. changes cannot be made in cust PI .

Thanks,

Aju

[Former Member]

why don't you use the normal soap to soap communication and then you can change the namespace on your side and the only thing they need to change when you do a change is the url in the comm channel.

[Former Member]

Hi ,

thank you for your suggestion.

now we are using xi adapter with rfc desitination of type h pointing to cutomer pi integration engine.it does not have a query string. If we add query string with interfacename, namepace and buisness system will it overwrite the header with the values from the query string .. will this approach work ?

Thanks,

Aju

[stefan_grube]

> If we add query string with interfacename, namepace and buisness system will it overwrite the header with the values from the query string .. will this approach work ?

No, the XI adapter will always use header fields if XI message

If you want to have different values, you need SOAP or HTTP adapter.

[Former Member]

Hi Stefan,

Thank you for your reply.

which one would be the better approach between http and soap adapter?

1. in http reciever adapter if we specify the namespace, interface name and buisness system will it overwrite the soap header from pi and use the one in the url ?

2. in soap sender adapter if we use the the default namepace and interface name will it create a header based on that ?

pls give suggestions

Thanks,

Aju

[Former Member]

sorry to intervene although your question was for Stefan:

1. for http you have quite some parameters that you can set check this link [http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm]

2. for soap in the new system you will have new sender, receiver, interface, and namespace (check this link [http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm])

as with regards to which one is the best Stefan can probably give you a better answer. My 2 cents are that soap would be your choice for security reasons, it is java so on an adapter engine, and you probably (should) have a de-central adapter engine in the dmz of your network landscape.

[stefan_grube]

the best approach would be reusing interface and namespace and sender and receiver systems in second PI system.

With HTTP you cannot use attachments, with SOAP no dynamic EOIO handling, both adapters do not allow acknowledgments.

HTTP adapter needs no conversion to SOAP message, so it might run faster.

[Former Member]

Hi Stefan,

thank you for your reply ..

1. if we consider the option of http to http communication using http adapters ,

can we dynamically change the service, namespace interfacename, namespace in the path given in the http reciever adapter.

the idea is to have these values from a lookup table and use it so that we don't have to create as many channels as the no of interfaces ..

and is it possible to have the values changes from lookup outside the mapping before the adapter call , so that it need not be repeated in all the mappings ?

2. if we use soap to soap communication can we use a single soap sender adapter in the cutomer pi so it can be used for all the interfaces .. ?

and it possible to change the header values dynamically and use a single soap receiver from our side ?

thanking you in advance

Aju

[stefan_grube]

> 1. if we consider the option of http to http communication using http adapters ,

>

> can we dynamically change the service, namespace interfacename, namespace in the path given in the http reciever adapter.

> the idea is to have these values from a lookup table and use it so that we don't have to create as many channels as the no of interfaces ..

You can use dynamic URL parameters.

> and is it possible to have the values changes from lookup outside the mapping before the adapter call , so that it need not be repeated in all the mappings ?

I don't understand this.

> 2. if we use soap to soap communication can we use a single soap sender adapter in the cutomer pi so it can be used for all the interfaces .. ?

>

> and it possible to change the header values dynamically and use a single soap receiver from our side ?

No. SOAP adapter does not support dynamic URL parameters.

[Former Member]

Dear Stefan ,

Thank you for the reply. Here we have a situtation where we have to change the interface names, namespaces and buisness system names in our PI system. But we cannot change these in the customer PI system. So the idea is change these values when we send it to the cutomer PI. In the case of buisness systems we can assign the values using header mappping.

the same concept has to be extended to include namepace and interface names. can we include the query string in the connection to customer PI using http connection .. or the query string parameters when we connect to the customer Pi intergraion engine.

Pls help ..

Regards,

Aju

[Former Member]

Dear Experts,

Could you please suggest different options to modify the query string when the message is send to integration engine,

http adapter and soap adapter ?

Thanks,

Aju

[stefan_grube]

Use XI adapter for this scenario and use same interfaces in both PI systems.

This is the only useful approach for connecting different PI systems.