9.1 - SOAP Header Insertion - Need to turn off CorrelationID

[Anon Anon]

I recently put a 9.1 WebLogic agent on some Oracle Service Bus JVM's and although cross-process tracing is completed turned off, somehow the agent keeps hijacking the SOAP headers and the requests are being rejected. Oddly, the documentation shows the following:

There are four agent configuration properties that control the handling of the correlation identifier on the client and the server.
With these properties, you can specify whether the identifier should be inserted into the SOAP header, the HTTP header, both header protocols, or not inserted at all.
These properties start with the standard agent prefix com.wily.introscope.agent:

The funny thing about that is the IntroscopeAgent.profile file has no mention of these settings. I've looked in the Agent.jar file as well and can't find this setting.

Additionally, the doc says regarding correlation identification:
Because most services use SOAP messaging, the correlation identifiers are inserted and read from SOAP headers by default.
In certain situations, however, you may prefer to pass the correlation identifier using HTTP headers.
For example, in rare cases, adding the correlation identifier to the SOAP header can cause the message to be rejected because the correlation ID changes the SOAP payload.

The above is exactly what is happening but I can't for the life of me figure out how to turn it off.

Please Help!

Thank you in advance.

[Legacy User]

Here is what the documentation has regarding the properties (from the SOA-Specific Agent Configuration Properties section of the APM for SOA Implementation Guide):

You can set the following SOA-specific properties in the IntroscopeAgent.profile.

Note: For information about other agent properties, see the CA APM Java Agent Implementation Guide or the CA APM .NET Agent Implementation Guide.

com.wily.introscope.agent.httpheaderinsertion.enabled
Enables or disables the insertion of client-side correlation information in HTTP headers.

com.wily.introscope.agent.httpheaderread.enabled
Enables or disables the server-side retrieval of correlation information from HTTP headers.

com.wily.introscope.agent.soapheaderinsertion.enabled
Enables or disables the insertion of client-side correlation information in SOAP headers.

com.wily.introscope.agent.soapheaderread.enabled
Enables or disables the server-side retrieval of correlation information from SOAP headers.

com.wily.introscope.agent.soa.metricNameFormatting
Modifies CA APM for SOA metric names to replace any specified character or characters with an underscore [_].

com.wily.introscope.agent.transactiontrace.boundaryTracing.cacheFlushFrequency
Specifies the number of days to hold dependency data in the agent memory before flushing the cache.

com.wily.introscope.agent.transactiontrace.boundaryTracing.enable
Enables or disables boundary tracing for transactions.

com.wily.introscope.soa.client.prependhandler
Controls the insertion point of the SOAP header on the client-side.

com.wily.introscope.soa.server.appendhandler
Controls the retrieval and removal of the SOAP header on the server-side.

In most cases, changing an agent property requires that you restart the application server for the property change to take effect.

Additionally, if you want to turn off correlation tracing, you can also disable the correlation tracing directives. In APM 9.1, you can disable the use of the spm-correlation.pbd (in spm.pbl). In some cases, you can disable the specific tracing group in webservices.pbd, e.g.
[font=Courier New]#TurnOn: Axis2ClientCorrTracing
#TurnOn: JBOSS_CLIENT_JAXWS_TRACING_CORR
#TurnOn: WL_ClientCorrelationTracing2[font]

In other cases, you can simply disable the correlation trace directive (also in webservices.pbd), e.g.
[font=Courier New]#TraceOneMethodWithParametersIfFlagged: WL_SERVER_JAXWS_TRACING runSync WL_SERVER_JAXWS103_CORR_SOAP_TRACER "WEBSERVICE"
#TraceOneMethodWithParametersIfFlagged: WL_CLIENT_JAXWS_TRACING doProcessAsync WL_CLIENT_JAXWS_SOAP_CorrelationTracer "WebServices"[font]

[Anon Anon]

Thank you for your response.

I should have mentioned that out of desperation I removed the spm.pbl directive in the INtroscopeAgent.profile file so there was no way it got directions to look at webservices.pbd.

Any other ideas (thank you in advance)

[Legacy User]

The only other thing I can think of is the [font=Courier New]ServletHeaderDecorator[font]. Make sure it is turned off in your toggles pbl (e.g. [font=Courier New]weblogic-typical.pbl[font]):
[font=Courier New]#ServletHeaderDecorator.pbd[font]

as well as in your [font=Courier New]IntroscopeAgent.profile[font]:
[font=Courier New]#introscope.agent.decorator.enabled=true[font]

To be on the safe side, can you provide a sanitized example of the hijacked SOAP message, particularly the header(s)? That may shed some light on its origin.

[Legacy User]

Nick,

Did this help answer your question at all or were you able to figure it out on your own?

[Anon Anon]

We run WebMethods+Introscope9.0.8 SOA PPack and this helped us with resolve the SOAP header modification issue -

com.wily.introscope.agent.transactiontrace.boundaryTracing.enable=true
com.wily.introscope.agent.soapheaderread.enabled=false
com.wily.introscope.agent.httpheaderread.enabled=true
com.wily.introscope.agent.soapheaderinsertion.enabled=false
com.wily.introscope.agent.httpheaderinsertion.enabled=true

[Manish Parikh]

Hallett_German

Can you put Norri's reply as the correct answer, please (instead of Jak's)?

 

Thanks

Manish

[Hallett German]

Manish, I made this as a new branch. Javk's is answered in teh old branch and Norris in the new one.

[Manish Parikh]

Hallett_German

Can you provide the link to the new thread please?

 

Thanks

Manish

[Hallett German]

Searching on the above title in the Community search returned quickly https://communities.ca.com/message/241980643-re-91-soap-header-insertion-need-to-turn-off-correlationid?commentID=241980…