If you create your own technical catalogs in the backend, you replicate these catalogs
to the frontend system using a single system alias.
Procedure
Perform the following steps on the front-end server:
- Launch the program
/UI2/GET_APP_DESCR_REMOTE_DEV.
- In the System Alias field, enter the name of the system alias for
which the catalogs should be replicated.
- In the Catalog ID field, enter the name of the technical catalog
which you want to replicate.
- Choose an extraction mode:
- Delta extraction: The selected catalogs are only replicated if changes were made since
the last replication.
- Full extraction: All selected catalogs are replicated.
- Mark the Test mode checkbox and choose
Execute.
The catalogs will not be replicated. A log is displayed.
- If the log does not contain any errors, unmark the Test
mode checkbox and choose Execute.
Results
On the frontend server, the program creates a catalog with the following naming
convention:
X-SAP-UI2-ADCAT:<ID of technical catalog in
BE>:<System Alias of BE>
Example:
X-SAP-UI2-ADCAT:SAP_TC_FIN1:S4FIN.
Based on the application descriptor which you
defined in the mass maintenance tool (see
Create Application Descriptors Using the Mass Maintenance Tool), each application contained in
the backend catalog produces the following:
-
An app launcher tile containing the intent, the texts (title, subtitle,
keywords and information) and the icon maintained in the mass
maintainance tool
- A target mapping containg the intent, the parameters and the title
maintained in the mass maintainance tool. The HTTP connection, which is
associated with the system alias is entered in the System
Alias f ield.
You can display the replicated catalogs in the launchpad designer but
you cannot edit them there since the original data is located in the
back-end.
You create business catalogs based on the technical catalogs. See
Integrating Web Dynpro and SAP GUI Applications Using Mass Maintenance.