Show TOC

Configuring Business SystemsLocate this document in the navigation structure

Use

In the Integration Directory you can configure business systems that communicate with each other using the Web service runtime based on standard Web Service Reliable Messaging (WS RM). Communication can therefore happen directly from system to system or using the Integration Server.

With this communication mechanism you also distribute the configuration of Component-Based Message Alerting to business systems.

Note

If the systems that communicate with each other are based on AS ABAP (as of 7.10), you can specify the complete configuration settings in the Integration Directory. The configuration settings are then distributed to the back-end systems involved using cache notifications so that local configurations settings are no longer required there.

If the back-end systems involved do not fulfill the condition stated above and additional security settings are to be configured for communication, you will need to use other tools and procedures to complete the security.

If you would like to configure business systems for use in such Web services, you must perform the configuration steps described in this section.

Procedure
Task 1.Setting Up Destination in the Back-End System you perform in the back-end system. Task 2.Defining Business Systems in the System Landscape Directory you perform in the System Landscape Directory (SLD). You perform the remaining tasks in the Integration Directory.

1. Setting Up the Destination in the Back-End System

  1. Create a user with role SAP_XI_ID_SERV_USER_MAIN. You need this later for cache distribution.

  2. Create INTEGRATION_DIRECTORY_HMI.
    1. Log on to the Integration Server Host.
    2. Call transaction SM59.
    3. Choose Create
    4. Enter the following as a minimum:
      • RFC Destination: INTEGRATION_DIRECTORY_HMI

      • Connection Type: H
      • Description: <your description>
    5. Choose Enter.
    6. Choose the following tabs and enter the required data.
      Note

      Save your data before you go to the next tab. If you don't, the system will not save your changes.

      • Technical Settings

        • Target Host: Host name of AS Java

        • Service No. HTTP port number

          The following naming conventions apply: 5<AS_Java_instance_number>00 50000, if your AS Java instance is 00)

        • Path Prefix /dir/CacheRefresh
      • Logon & Security
        • Choose Basic Authentication

        • Enter the client of your integration server and the PIISUSER with a valid password.
      • Special Options
        • Timeout: 30000

        • HTTP Version: HTTP 1.0, compression: Inactive, compressed response: No
        • HTTP Cookies: Accept cookies: Yes (all)

        Save your entries.

  3. Open transaction sxi_cache_config (see SAP Note 1232259 Information published on SAP site)

    This creates a new destination SXICACHE <client> and a new user PICACHEUSER.

  4. Call transaction SICF.
    • Virtual Host: Default_HOST

    • Service Path: Make sure that services /sap/xi/cache/ and/or /sap/xi/cache_ssl/ are active (if you want SSL).
  5. Check connection to SLD

    Call transaction sldcheck. There must be no errors.

  6. Call transaction SICF. There must be no errors.
2. Define Business Systems in the System Landscape Directory
Note

For component-based message alerting the business system in SLD must have at least SAP Basis 7.31 installed.

The involved back-end systems must be defined as business systems in the SLD. You can either create a new business system or use an existing business system.

To enable the configuration settings to be propagated from the Integration Directory to the back-end systems, the URL of the back-end system must be specified in the SLD for every business system.

  • To create a new business system, proceed as follows.

    1. Call the Process Integration start page.

    2. Start the SLD.

    3. On the SLD start page, choose Business Systems.

    4. Choose New Business System.

    5. Select the business system type, and choose Next.

    6. In the next step (Technical System), enter the URL.

    7. Finish defining the business system.

  • To use an existing business system, proceed as follows.

    1. On the SLD start page, choose Business Systems.

    2. Select the required business system from the list.

    3. On the Integration tab page, enter the URL in the Configuration URL field.

    4. Save the business system.

3. Define Business Systems as Communication Components in the Integration Directory

To enable the business systems defined in the SLD to be addressed as senders and receivers of messages, you must define them as communication components in the Integration Directory.
  1. Call the Process Integration start page.

  2. Call the Integration Builder (Integration Directory).

  3. Define the business systems defined in the SLD as communication components.

    More information: Define Business Systems as Communication Component

4. Facilitating Distribution of Configuration Data in the Back-End System

To send the configuration settings that you have made in the Integration Directory (see below) to the back-end system, you must enter a service user (with a password) for each business system which will trigger the cache notifications to the relevant back-end system. Note that this user must be known in the back-end system.

Note

The business system URL is entered in the business system description in the System Landscape Directory (SLD) and must not be reentered in the Integration Directory (description of the business system in the SLD, tab page Start of the navigation path Integration Next navigation step Field Configuration URL End of the navigation path).

Execute the following steps for business systems previously defined as communication components.

  1. Open the communication component in the Integration Directory.

  2. Choose the Logon Data tab.

  3. Select the checkbox Business System Communicates Using Web Service Runtime.

    The configuration settings made in the Integration Directory can only be sent to the back end using cache notifications if you select this checkbox.

  4. Enter the service user (with password) that is to trigger the cache notification in the back end. (This is the user that you created with role SAP_XI_ID_SERV_USER_MAIN, as described in 1.1.)

    The composite role SAP_XI_ID_SERV_USER_MAIN must be assigned to the service user. If not, the missing authorizations prevent you from completing the configuration without errors.

  5. Save and activate the business system component.