Connector Guides › Connectors Guide › Connecting to Endpoints › SAP R/3 Connector › Migrating SAP Endpoints from the C++ SAP Connector

Migrating SAP Endpoints from the C++ SAP Connector

The Java version of the SAP Connector (installed with Java CS) provides all of the functionality of the previous (eTrust Admin r8.1) C++ version of the SAP Connector with the added benefit of full CUA management, but there are a few things to consider when switching from the C++ version.

• When a SAP CUA master endpoint has already been acquired and explored, the endpoint will be managed as a CUA engine after the switch from the C++ connector to the Java connector. Since all existing SAP roles and account templates are still valid after the migration, existing admin account templates targeting the master directory are still usable. Existing managed objects are valid as well. You must re-explore the endpoint to include the managed objects that exist on child systems.
• When SAP CUA member endpoints have already been acquired and explored, they should be removed. Account templates pointing to these member endpoints should be pointing to the CUA master endpoint.

  Note: Management of local account attributes (for example, default printer) according to the SCUA parameter is still possible by keeping the CUA member endpoint and managing these attributes through this endpoint.

• To add the SAP connector to an existing system:
  1. Run the Provisioning Server install to reconfigure and add the SAP connector.
  2. Run Java CS installer and select Register with the Provisioning Server.

  Doing this will route requests from the Provisioning Server to Java CS for the SAP endpoint type.

• Important! Before migrating from C++ to Java CS, the following must be filled out and selected on the Endpoint Tab of the SAP Endpoint property sheet:
  • The check box for 'Use LogonID' must not be selected.
  • The application server name and number must be entered.