Show TOC

Procedure documentationUsing the Non-Central Adapter Engine in Java Proxy Mode Locate this document in the navigation structure

 

You can run the non-central Adapter Engine in Java proxy mode. Registration of the adapters in the SLD is deactivated in this mode. The collaboration profile agreement service (CPA service) does not read the CPA cache from the Integration Directory.

You define the user that is to send the messages to the Integration Server in a service parameter. When the Integration Server receives the message with this user, it checks the user using the access control list. This check is not performed for the technical user XIAFUSER.

Procedure

  1. In SAP NetWeaver Administrator set the parameter SLDAccess to false under   Configuration Management   Infrastructure   Java System Properties   Design   Services   in service SAP XI AF CPA Cache.

  2. In service SAP XI AF CPA Cache, check that the cacheType parameter has the value DIRECTORY.

  3. In service SAP XI Adapter: XI, enter values for:

    • xiadapter.isconfig.url

    • xiadapter.isconfig.username

    • xiadapter.isconfig.password

    • xiadapter.isconfig.sapClient

    • xiadapter.isconfig.sapLanguage

  4. On the Integration Server, use transaction SMICM to check that you have entered the correct URL for the Integration Server.

  5. On the Integration Server, use transaction SU01 to create a new user.

  6. Assign the role SAP_XI_AF_SERV_USER_MAIN to the user.

    To do this, copy the user XIAFUSER.

  7. In the SAP NetWeaver Administrator, check whether the user synchronization was successful.

  8. Use the new user to log on to the Integration Server and change the initial password.

  9. Call the SLD and choose Content Maintenance.

  10. Under Class, choose Adapter Framework.

  11. Choose the non-central Adapter-Engine and select Remove.