Configuration of Key Store

Use

The xslt mapping programs normally execute in the XI context outside of the Web AS. The key store for the key mapping normally resides on one of the connected Web AS systems, and not in XI.

The key store is assigned to a concrete Web AS in the Integration Directory of the XI Integration Builder. A communication channel with adapter type RFC is set up to the Web AS that takes on the role of the key store.

Default Communication Channel

If no other value is defined, a communication channel with a predefined name for the partner, service and channel is used. These include:

• UKMDefaultPartner
• UKMDefaultService
• UKMDefaultChannel

Alternative Communication Channel

The default communication channel is not sufficient if the system group contains multiple key stores or if different key stores are to be addressed in an xslt program depending on the context.

In this case you must set up a communication channel of adapter type RFC for each key store. The relevant triple (partner, service, channel) is passed to the constructors of the API classes.

Example

 Use of multiple communication channels in an xslt program

<!-- Default Key Store -->
 <xsl:variable   name="defaultKeyStore"
  select="AddKeyMapping:new($MappingTrace)"/>
 <!-- Key Store 1 -->
 <xsl:variable   name="keyStorePartner"
   select="AddKeyMapping:new($MappingTrace,
    'Partner-1', 'Service-1', 'Channel-1)"/>
 <!-- Key Store 2 -->
 <xsl:variable   name="keyStoreProduct"
 select="AddKeyMapping:new($MappingTrace,
         'UKMDefaultPartner', 'M7C_100', 'UKMChannel')"/>