If you have stored value mappings in external tables, you can replicate this data in the runtime cache (on the Integration Server). To do this, you can use special service interfaces (value-mapping replication interfaces) that allow you to implement both synchronous and asynchronous replication scenarios.
The replication of value mappings is particularly suitable for mass data that you manage in separate tables (such as SAP database tables) independent of the Integration Server.
In a replication scenario, the contents of the external value mapping table are read and sent to the Integration Server as an XML message. An inbound interface allows the external data and the data that you previously created using the user interface of the Integration Directory to be stored together in a uniform format.
To avoid overwriting existing value mappings during the replication process, you assign the external data a value mapping context . This needs to be a unique name that identifies that system or application from which the value mappings are taken.
The value mapping context appears in an additional column in the value mapping table. This allows you to differentiate between identical representations of the same object that come from different external data sources.
You cannot display the replicated value mapping data in the Integration Directory user interface (see Displaying/Editing the Value Mapping Table ) since the original runtime data is stored in the application from which the data is copied. The value mappings created in this way using the user interface of the Integration Directory are just one of many possible sources of data.
SAP provides the following objects for the replication of value mappings:
Value-Mapping Replication Interfaces
They are located in the Enterprise Services Repository in the software component SAP BASIS , software component version SAP BASIS 7.11 in the namespace http//sap.com/xi/XI/System .
For the inbound message interfaces, there are inbound proxies on the Integration Server and ABAP outbound proxies in the SAP system in ABAP proxy generation under the software component version SAP Basis 7.11 .
To implement a value-mapping replication scenario, you must also carry out the steps outlined under Activities .
There are the following interface types:
ValueMappingReplication : Asynchronous Inbound Interface
ValueMappingReplicationOut : Asynchronous Outbound Interface
ValueMappingReplicationSynchronous : Synchronous Inbound Interface
ValueMappingReplicationOutSynchronous : Synchronous Outbound Interface
The following message types exist:
ValueMappingReplication : Describes the message for transferring the value mapping data (structure, see below)
ValueMappingReplicationResponse : Describes the message used in the synchronous scenario to return whether the value mapping data was written to the database at the receiver without errors
ValueMappingReplicationFault : Describes the fault message used if errors occur during replication
The message used for transferring the value mapping data has the following fields (data type ValueMappingReplicationList ):
GroupID : Specifies the GUID for the value mapping group
Context : Defines the value mapping context in which a value mapping has been defined (Example: http://<myApplication>).
Identifier/Agency : Specifies the agency for the representation
Identifier/Scheme : Specifies the identification scheme for the representation
To implement a value-mapping replication scenario, proceed as follows:
Register the Java (inbound) proxies.
To do so, call the following URLs in the following order in your Internet browser:
http://<Server>:<Port>/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplication&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplication&method=valueMappingReplication (for the asynchronous replication scenario)
http://<Server>:<Port>/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplicationSynchronous&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplicationSynchronous&method=valueMappingReplicationSynchronous (for the synchronous replication scenario)
You only need to perform this step once (for each installation).
The ABAP program must perform the following tasks:
Read the value mapping data from the external table
Call the outbound proxy used to transfer the data to a message, which is then sent to the Integration Server
Configuration of the replication scenario in the Integration Directory
This involves creating all the configuration objects you need to execute the scenario successfully. One special aspect of the value-mapping replication scenario is that the receiver is predefined (it must be on the Integration Server). The sender, however, is not predefined in the replication scenario and can be defined to meet your individual requirements.
For example, you can use the shipped ABAP proxies.
In the case of the receiver communication channel, choose the adapter type XI . Ensure that you configure a channel for the Java proxy receiver in this case.
Enter the path prefix /MessagingSystem/receive/JPR/XI for this purpose.