With the parameter MultiRepository you can manage calls from multiple SAP systems that are set on different repository destinations.
In this way, a resource adapter can process calls from SAP systems that are based on different ABAP Data Dictionaries (DDICs).
To achieve this, you have to connect the system ID of this system (and perhaps also the client) with a destination from which the DDIC information is read. This connection is produced using a rule. You can separate multiple rules using semi-colons. The syntax for this rule is:
● <SID> = System ID of the ABAP backend system
● <Client>= Client of the ABAP backend system
● <Destination>= Destination that is to be used for DDIC queries if an ABAP backend system <SID> and – if specified – the client <Client> call comes in. This destination must be maintained using Destination Provider Service.
The parameter DestinationName is still required and is used as the default destination if no suitable SAP systems are defined in the rule above. The JRA cannot be started if the parameter DestinationNameis not defined.
Both DestinationName and MultiRepository must refer to valid destinations. The logon data of the destination must also be valid. Otherwise the Resource Adapter cannot be started of the call fails, since it is not possible to access the SAP system with the DDIC information.
If the rule defines an SAP system (Client) that does not exist then this does not affect the ability of the Resource Adapter to run. However the relevant destination will never be used.
All calls that do not match the rule are dealt with by the DDIC of the destination DEF. A call of system ABC with client 100 is dealt with by DEST2, all other calls of system ABC are connected with DEST1. DEST3 is used for calls of systems GHI and JKL.