This article provides inputs on how APIX-G can identify partners when requests are received over NorthESB_Channel or SOAPJMS_North channels.

How to Identify Partners over JMSChannels.

All supported platforms.

For NorthESB_Channel:

To allow identification of partners through the JMS Channel, add ApiKey to the JMS header when sending a request to a JMS queue. The value of the API Key is used to retrieve the partner configured with the matching Partner API Key. When configuring the Partner API Key, the Identify Partner should be set to TRUE (checked) for the API key to be used to identify the partner.

Note that JMS_TIBCO_SENDER cannot be used on this Channel.

For SOAPJMSNorth_Channel:

Over this Channel APIX-G can Identify Partners based on ApiKey or JMS_TIBCO_SENDER headers.

- To use ApiKey, add ApiKey to the JMS header when sending a request to a JMS queue. The value of the API Key is used to retrieve the partner configured with the matching Partner API Key.

When configuring the Partner API Key, the Identify Partner should be set to TRUE (checked) for the API key to be used to identify the partner and the APIKey mapped in the Facade Access tab.

- To use JMS_TIBCO_SENDER, this header should carry the Serial Number of the Partner. The partner's CAIssuer should be

"O=TR;CN=ASG;CN=SOAPJMS;CN=UserIdentity"

Note that the above header names are case-sensitive.