Symptom
You are installing
"SAP NetWeaver 2004s SR1" Usage Type 'NetWeaver Process Integration (PI)' or a higher Service Release.
"SAP NetWeaver for Process Integration (PI) 7.10"
You want to register your new system at a central System Landscape Directory (SLD).
Other terms
Exchange Infrastructure, XI, PI, XPI, CTC, Template Installer, Configuration Wizard
Reason and Prerequisites
With releases 7.0 (also known as 2004s) and 7.1 a PI installation offers the option to register with a central SLD. Only for a local SLD configuration all required steps are executed automatically by the "Configuration Wizard". For a central SLD configuration you have to execute the additional steps described below.
Note: In 7.0 the Configuration Wizard was named "Central Template Configuration (CTC) tool".
Note: With every PI installation you get a so called "local" SLD. This means a SLD that runs on the same Java stack as your PI system. The respective URL is always active. A "central" SLD runs on a different host, possibly a WebAS Java system. Pay attention to this. All steps described below refer to the "central" SLD, not to the "local" one !
Relevant for SAP NetWeaver 7.0 (2004s)
You find a detailed description about all template steps at:
http://help.sap.com/nw2004s/ -> SAP NetWeaver Library -> Technology Consultant's Guide -> SAP NetWeaver Configuration -> Business Process Management -> Configuration of Usage Type Process Integration (PI) -> Template-Based Basic Configuration
In case of a central SLD, manual effort is required. The CTC Tool reports an error in configuration steps 7 and 8. Therefore all needed configuration steps are described in this note.
Note: This is not a coding error. In a distributed landscape the CTC tool has no permission to execute function modules in a central SLD system.
Note: Make sure that all other CTC steps have been executed successfully (steps 9-21). For more details see the referenced note below.
Note: Install the latest Support Package after the installation, as it is recommended in the Installation Guide. This is important since a problem with lost associations in the SLD can arise otherwise.
Relevant for SAP NetWeaver 7.1
You find a detailed description about all template steps at:
http://help.sap.com -> SAP NetWeaver -> SAP NetWeaver 7.1 / language ->
SAP NetWeaver Process Integration Library -> Administrator's Guide -> Configuration of SAP NetWeaver -> Configuration of SAP NetWeaver Systems -> PI (Process Integration) -> Wizard-Based Configuration
In case of a central SLD, manual effort is required.
Solution
The following steps must be executed.
Note: In the following "SAP NetWeaver 2004s" is labeled "7.0".
Steps on Central SLD System (ABAP + Java or plain Java stack)
7.0, 7.1 - Logon to the central SLD ABAP system and create the following PI users with the same ABAP roles they have in the Integration Engine: PIAFUSER, PIAPPLUSER, PIDIRUSER, PIISUSER, PILDUSER, PIREPUSER, PIRWBUSER, PISUPER.
Note: The passwords of these users must be same as in the Exchange Profile. In a default installation this is the Master Password you had entered during the installation.
Note: If you run your SLD on plain Java stack, create the users and groups in the Visual Administrator's "Security Provider" service. See note 768148, second part, for details.
Note: Starting with 'NW04s SR0' installation, all XI user names start with prefix 'PI', e.g. PIAFUSER, PISUPER, etc. The group names are the same as for XI 3.0 (see note 768148 from above for details). If you have upgraded from XI 3.0 or installed 'NW04s SR0', create the users with XI names XIAUFUSER, XISUPER and so on. The reason for the renaming was the introduction of 'Usage Types' with NW04s SR1(avoid conflicts between PI usage and other usages).
7.0 - Logon to the central SLD's Visual Administrator and browse to the SLD Data Supplier Service. Click on "Assign application roles to user groups". After that all PI users have the required SLD permissions.
7.0 - Maintain a product for the technical system in the central SLD. How this is done is explained in the Technology Consultant's Guide, chapter 'Template-Based Basic Configuration' (link see above). In 7.0 this corresponds to template step 7.
7.0 - Maintain a Business System for the Integration Server in the central SLD. How this is done is explained in the 'Technology Consultant's Guide' too. In 7.0 this step corresponds to template step 8.
Steps on Integration Server System (IS) (only required if you install SAP NetWeaver 7.00 Service Release 1)
7.0 - Start ABAP transaction "Configuration of RFC Connections" (SM59) and maintain in the TCP/IP connections LCRSAPRFC and AI_RUNTIME_JCOSERVER the Integration Server's Gateway Host and Gateway Service. Save and execute the 'connection test'. Note: These connections point to the Integration Server, not to the SLD. You find their counterparts (registered server program IDs) in the Visual Administrator's JCo RFC Provider service.
Note: AI_DIRECTORY_JCOSERVER is not used in NW2004s.
7.0 - Start the Exchange Profile http://<IS_host>:<port>/exchangeProfile and logon with PISUPER user. The following connections must point to the central SLD system:
com.sap.aii.connect.cr.name,
com.sap.aii.connect.cr.httpport
com.sap.aii.connect.cr.httpsport
com.sap.aii.connect.landscape.name, com.sap.aii.connect.landscape.httpport com.sap.aii.connect.landscape.httpsport
7.0 - Trigger a full cache refresh. To do this call the URL
http://<IS_host>:<port>/CPACache/refresh?mode=full
with user PIDIRUSER (only this user has the required permission). After that restart the CPA Cache Service. This triggers the self registration of the Adapter Engine in the central SLD. Logon to the central SLD and check this.
Steps on the Central Adapter Engine
7.0 - Restart the central J2EE Engine to trigger the Adapter Engine's and Tool's self registration again.
7.1 - Pay attention to note 1117249.
7.0, 7.1 - Check: Logon to the central SLD and check if the registration was executed successfully.
