Application development teams can use the option of pre-identifying the message receiver available in the Integration Engine. This can improve performance when sending large messages. The application development team decides whether to use this function, which enables it to identify the potential receiver of a message before the message is created.
To identify a receiver in advance, you have to create a fixed RFC destination AI_INTEGRATION_SERVER, which is used to call the Integration Server. The application program can then use the routing rules of the Integration Directory to decide whether a message will find a receiver, and then trigger the creation of a message.
The Integration Engine requires the fixed RFC destination AI_INTEGRATION_SERVER to identify receivers in advance. Proceed as follows:
1. Call transaction SM59, and create the type 3 RFC destination AI_INTEGRATION_SERVER (ABAP connection).
2. Enter the Integration Server as the Target Host.
3. Enter PIAPPLUSER and password as the user.
The PIAPPLUSER user and password are specified here as an example. This user, or any other user you may specify instead, must exist on the Integration Server with the role SAP_XI_APPL_SERV_USER (service user role for application systems).
For more information, see Receiver Pre-Identification. See also the documentation that can be displayed by choosing the Info button in transaction Integration Engine: Administration (SXMB_ADM), menu item Integration Engine Configuration, configuration data category Runtime.
If your application requires maintenance of the value mapping table on the Integration Server, you have to use the same RFC destination (AI_INTEGRATION_SERVER) as for the receiver pre-identification described in the previous section.
For more information, see Value Mapping. See also the documentation that can be displayed by choosing the Info button in transaction Integration Engine: Administration (SXMB_ADM), menu item Integration Engine Configuration, configuration data category Runtime.