cancel
Showing results for 
Search instead for 
Did you mean: 

PI 7.3 not able to handle Dynamic Configuration

Former Member
0 Kudos

Hi

I am having a SOAP -->SOAP scenario in PI 7.3(Single stack-Java Only).

It is a Synchronous scenario.

I am trying to save a value from Request mapping using dynamic configuration using the following code.

DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);

DynamicConfigurationKey Source1=DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP","Source");

conf.put( Source1,var1);

But i am not able to use this value in Response message Mapping. The response mapping is not able to recognize this "Source" key at all.

Throwing an exception. The response UDF code is similar to the above one.

Any idea?

Thanks

Dhanish

Accepted Solutions (1)

Accepted Solutions (1)

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

I am trying to save a value from Request mapping using dynamic configuration using the following code.

This is not possible since both the request and response message will contain different SOAP Headers, hence the you cannot retrieve what you set in request SOAP Header in the response message.

What you can do is to save the value in an ABAP/JDBC table and perform a lookup.

Hope this helps,

Mark

Former Member
0 Kudos

Hi Mark

I tried the same in PI 7.3 dual stack and it is working fine !!!!

But when i treid using single stack(Java Only), not working.(I have created an Intergrated Configuration)

Thanks,

Dhanish

Answers (3)

Answers (3)

Former Member
0 Kudos

Dhanish,

Did you determine if this is true or not in the 7.3 version.  Appears dynamic configuration doesn't work in single stack.

Former Member
0 Kudos

FYI - We were just told we need SP14 loaded.

nabendu_sen
Active Contributor
0 Kudos

Hi Steve,

Thanks for the update. After the SP update let us know, whether this is working or not.

Former Member
0 Kudos

Nabendu,

Sorry I had that wrong.  SP14 was to get Soap Lookups working in a UDF.  We are still waiting to hear back on the Dynamic Configuration issue we are having and appears others.  Should hear something in a few days though.

nabendu_sen
Active Contributor
0 Kudos

Hi Steve,

Thanks for the comment, I still not performed SOAP Lookup in PI 7.3 till now. One thing I am thinking that lot of features are missing from one version to its next version of PI. This is very strange. I had the concept that always a new version should come with additional features, the way may be different but at least the old features should not be lost. May be Mentors can come up with some better suggestions.

Former Member
0 Kudos

We have SOAP Lookups working now.  We created a note with SAP and it was a bug.  We had to load the latest patches for both the "Adapter Framework" and "Messaging Component" then SOAP Lookups worked after we installed the latest patches for 7.31 SP03 which is what we are on here.

Former Member
0 Kudos

Hi

What i understood is that dynamic configuration functionality in synchronous messages can't be used fully by using Integrated Configuration.

Where as , for processing messages using IS , it can be.

Thanks,

Dhanish

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

What i understood is that dynamic configuration functionality in synchronous messages can't be used fully by using Integrated Configuration.

I can't comment on that one, it is not stated as a limitation in SAP Help http://help.sap.com/saphelp_nwpi711/helpdata/en/48/cfac399bf23e49e10000000a421937/frameset.htm. Let us wait for the confirmation of others, I'm also curious

Regards,

Mark

stefan_grube
Active Contributor
0 Kudos

> What i understood is that dynamic configuration functionality in synchronous messages can't be used fully by using Integrated Configuration.

> Where as , for processing messages using IS , it can be.

My experience in PI 7.10 is that the SOAP adapter does not transport values from request message to response message, but other adapters do.

But I have no idea how each adapter behaves exactly and I think it would be good to address this via OSS ticket to SAP.

It should be either enabled in each adapter that header values are transported from request to response or clearly stated in online help, that this is not possible.

Former Member
0 Kudos

Hi Stefan

I have tested SOAP- SOAP sync communication by setting a value from dynamic configuration.

Result:-

1)Using Normal Config(IS processing)- Response message contains DynamicConfiguration header node.

2)Using Integrated Config(AAE Processing) - Response header doesn't have DynamicConfiguration header node.

We will try to open an OSS with SAP.

Thanks,

Dhanish

Former Member
0 Kudos

Hi Dhanish,

Dynamic Configuration works fine in PI 7.3 when Classical Configuration is used.

UDF Code :

Request Mapping :

DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);

DynamicConfigurationKey Variable = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "Variable1");

conf.put(Variable, a);

Response Mapping :

DynamicConfigurationKey Variable = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/SOAP", "Variable1" );

string1 = conf.get(Variant);

Note: However the same does not work when Integrated Configuration is used.

http://xxx.xxx.xxx.net:11507/sap/xi/engine?type=entry&version=3.0&Sender.Service=ARIBATHADV&Interfac...

When below URL is used it does not work.

http://xxx.xxx.XXX.net:44507/XISOAPAdapter/MessageServlet?channel=:ARIBATHADV:SOAP_SND_ARIBATHA_Comm...

Also your statement "Using Integrated Config(AAE Processing) - Response header doesn't have DynamicConfiguration header node" is true only with Integrated Configuration , but not with Classical Configuration.

If you got any response for OSS from SAP on this, please share it.

Hope this information is useful.

Regards,

Parimala

Edited by: ParimalaE on Feb 29, 2012 6:27 AM

Former Member
0 Kudos

Hi,

You can access only TServerLocation,TAuthKey,TProxyLocation,TProxyAuthKey,

THeaderSOAPACTION parameters from "http://sap.com/xi/XI/System/SOAP" namespace.

go through this link for more info...

[http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm]

So, in your case its not possible to store "Source" field value.

Regards,

Sunitha