Mapping Logical Systems 
Mapping logical systems allows you to use functions from different back-end systems in a Java Web Dynpro application that is integrated in the SAP Enterprise Portal. More information about this concept is available under Multiple Back-End Support for the Adaptive RFC Model.
Naming Conventions
The target system name must contain the original system name as a prefix and can be extended by a maximum of 3 characters. Furthermore, the URL parameter can only contain the suffix of the new system name and thus only the added maximum of 3 characters. The old system name cannot be used as a parameter.
Procedure
The logical target system name is configured in the Web Dynpro Content Administrator.
With the configuration of the Portal page, you pass the following URL parameters with the Web Dynpro application. These parameters are then taken into account when the application is started.
sap.wdarfc.useSys=<DEFAULT_SYSTEM>:<SUFFIX_OF_MAPPED_SYSTEM> |
If several systems are to be mapped, the parameter sap.wdarfc.useSys can be repeated any number of times within a URL entry. One parameter entry is made for each logical system.
The URL parameters for the Portal page are maintained as described in the Administration Guide of the SAP Enterprise Portal.
Example
You have developed a Web Dynpro self-service application ESSAppthat uses the functions of a back-end system XYZ. The logical system names of the application are WD_MODELDATA_DEST and WD_RFC_METADATA_DEST.
The application is now also to have access to the functions of a second system ABC. The targets for the logical systems are to be named correspondingly – that is, WD_MODELDATA_DESTABC andWD_RFC_METADATA_DESTABC.
In the browser URL, the application call with the parameters is then as follows:
http://<hostname>:<port>/webdynpro/dispatcher/local/ESSProject/ESSApp?
|
Additional Information
When using several back-end systems with mapping, guidelines apply that increase the Security of Logical Systems.