Quantcast
Channel: SCN : All Content - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 7030

SHeadercookie in SOAP sender adapter

$
0
0

Hi All,

 

We have a synchronous web service (SOAP to proxy) scenario where there is a requirement to capture the remote user name and pass to the SAP system. When I tried to access this parameter by setting the dynamic configuration, I get the parameter as part of dynamic config parameters. However, there is another parameter SHeaderCOOKIE which gets set and the length of this parameter goes beyond the allowed length of 200 characters (as per following link: http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce299c3a8e5430e10000000a42189b/frameset.htm). This results in the message processing to fail in mapping with the error: "Mapping "<mapping name>" failed to execute: MappingException: Mapping failed, IllegalArgumentException: Value is too long (511/200): $Version=0; com.sap.engine.security.authentication.original_application_url".

 

I would like to understand:

  • Is there a way to handle this using the standard features?
  • If not, do I need to use adapter module to handle this? Or will SOAP axis allow to handle more than 200 characters?

 

Appreciate your inputs on this.

 

Regards,

Sanjeev.


Viewing all articles
Browse latest Browse all 7030

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>