This tutorial explains preparations required to execute SAP remote and onsite services for SAP Process Orchestration/Process Integration (PI)/Exchange Infrastructure(XI).
Preparations
1. Connection to SAP
SAP is essential for preparing as well as delivering a service a network connection between the user’s PI/XI solution. SAP Document769478 explains the different remote connections available for the PI/XI systems. SAP employees are only able to log on using servers which are maintained in the system data. Java Web Start tools such as the Enterprise Service Repository and Integration Directory are known as the most conveniently accessed utilizing a Windows Terminal Server connection.
2. The PI/XI services which are performed on customer Solution Manager systems should ideally utilize the most upto date ST-SER version, these ensue that the service consultants and trained customer personnel use the latest checks and texts when performing the PI/XI services. The Older ST-SER versions limit the ability for analyzing the systems in a severe manner.
3. The enhanced PI related checks for PI 7.x releases are all contained in ST-SER Release 701_2010_1. The new ABAP collectors and SMD functionality support these checks and cover components which have been not previously evaluated in PI remote services. The Adapter Engines (Central and De-central) are verified so that recommendations can be provided along with the further checks and recommendations for the process of Business Process Engine. Additional checks and enhancements pave the way for load balancing configuration recommendations as well as optimal parameter recommendations for additional Integration Engines within the PI system. Users to keep in mind that as of ST-SER 701_2010_1, incase the SMSY configuration in the Solution manager System has not been set up properly for the PI system as of basis release 7.00, then the PI/XI related checks will not appear in the PI/XI session or in the PI/XI EarlyWatch Alert.
4. A Java stack is used as the PI/XI systems please review SAP Document1498779 which explains the technical prerequisites which should be prepared for an SAP Java stack (both Java standalone and Java add-in for dual stack) for the SAP remote services which are required to be performed for the Java stack, which also encompasses the PI/XI support services. Additionally, the Solution Manager Diagnostics is essential else the overall quality of the analysis will is impacted severely. The technical prerequisites for remote service delivery utilizing the SAP Solution Manager Diagnostics.
5. Users and Authorizations
The SAP employee performing the PI/XI service checks needs a user with the specific authorizations listed below:
i) PI 7.0x (dual stack)
Access is required for the Runtime Workbench (RWB), Visual Administrator tool, System Landscape Directory (SLD), Enterprise Service Repository (ESR), Integration Directory (ID), exchange profits, AS ABAP and NetWeaver Administrator (NWA) .
Listed below are the required user authorizations:
a) Authorizations for transactions SU01, SMMS, /sdf/mon, SLG1, SXMB_MONI_BPE, SMQ1, SMQ2, SMQ3, SMQS, SARFC, TAANA, IDX1, IDX2, IDX5, BD87, SWI1, SWI2_DIAG, SWI2_DURA and SWF_INB_CONF are all required.
b) Within AS ABAP user management, assign roles SAP_SLD_GUEST, SAP_SLD_SUPPORT, SAP_XI_DISPLAY_USER_J2EE, SAP_XI_MONITOR_J2EE, SAP_XI_RWB_SERV_USER and SAP_XI_SUPPORT_J2EE in the Integration Server Client. In the AS Java UME, assign the role SAP_JAVA_NWADMIN_LOCAL_READONLY for accessing SAP NetWeaver Administrator.
c) For accessing the desired SLD functions, the AS Java UME actions sap.com_com.sap.lcr.LcrUser and sap.com_com.sap.lcr.LcrSupport need to be assigned to the user as well. This is all done by making sure that the action sap.com_com.sap.lcr.LcrUser is all encompassed in J2EE Engine security role LcrUser and later assigned to user group SAP_SLD_GUEST. In analogy, action sap.com_com.sap.lcr.LcrSupport is included in J2EE Engine security role LcrSupport and later assigned to user group SAP_SLD_SUPPORT.
d) The role SAP_J2EE_ADMIN should be assigned in AS ABAP user managementfor securing access to the Visual Administrator tool. Please Note that OS access should be made available for accessing and using the Visual Administrator tool.
e) For accessing the System Information page, the user needs to assign the J2EE Engine security role SystemInfo_Support_Role (part of application sap.com/tc~monitoring~systeminfo) to an appropriate user group utilzing the Visual Administrator. This can be, e.g., user group "Everyone".
ii) PI 7.1x (dual stack)
Access is important for Enterprise Service Repository (ESR),Runtime Workbench (RWB), System Landscape Directory (SLD) Integration Directory (ID), AS ABAP, NetWeaver Administrator (NWA), Exchange Profile
Listed below are the required user authorizations:
a) Authorizations for transactions SU01, SMMS, /sdf/mon, SLG1, SXMB_MONI_BPE, SMQ1, SMQ2, SMQ3, SMQS, SARFC, TAANA, IDX1, IDX2, IDX5, BD87, SWI1, SWI2_DIAG, SWI2_DURA and SWF_INB_CONF are required.
b) Within the NWA identity management, adding the UME roles NWA_READONLY, SAP_SLD_GUEST, SAP_SLD_SUPPORT, SAP_XI_DISPLAY_USER_J2EE, SAP_XI_MONITOR_J2EE, SAP_XI_RWB_SERV_USER, SAP_XI_SUPPORT_J2EE, SERVICES_REGISTRY_READ_ONLY, UDDI_TierN.
iii) PI 7.3x (dual stack)
Access is required for the AS ABAP, Enterprise Service Repository, Integration Directory, NetWeaver Administrator, System Landscape Directory, Exchange Profile
Required user authorizations are listed below:
a) In addition to the authorizations supplied in SAP Document1405975, authorizations for transactions SU01, SMMS, /sdf/mon, SLG1, SXMB_MONI_BPE, SMQ1, SMQ2, SMQ3, SMQS, SARFC, TAANA, IDX1, IDX2, IDX5, BD87, SWI1, SWI2_DIAG, SWI2_DURA and SWF_INB_CONF are all required.
b) Within the NWA identity management, adding the UME roles NWA_READONLY, SAP_SLD_GUEST, SAP_SLD_SUPPORT, SAP_XI_DISPLAY_USER_J2EE, SAP_XI_MONITOR_J2EE, SAP_XI_SUPPORT_J2EE, SERVICES_REGISTRY_READ_ONLY, UDDI_TierN.
c) For the Process Orchestration utilizing the Business Process Management (BPM) user to add the roles SAP_BPM_SuperDisplay, SAP_BPM_Navigation, SAP_BPM_Debug, SAP_BPM_CTX_SUPER_ADMIN, NWA_READONLY, NWA_SUPERADMIN.
d) PI 7.3x (single stack), Process Orchestration
Access is required for the Enterprise Service Repository, Integration Directory, System Landscape Directory, AS ABAP, NetWeaver Administrator.
a) For the single stack systems (Java only, NetWeaver releases 7.3x or higher), the ABAP authorizations are not considered relevant.
b) Within the NWA identity management, adding the UME roles NWA_READONLY, SAP_SLD_GUEST, SAP_SLD_SUPPORT, SAP_XI_DISPLAY_USER_J2EE, SAP_XI_MONITOR_J2EE, SAP_XI_SUPPORT_J2EE, SERVICES_REGISTRY_READ_ONLY, UDDI_TierN.
c) Incase the single stack system is a non-central Adapter Engine, the ideally not all of the components SLD, ESR and ID are local objects on the non-central Adapter Engine. In this scenario, proper care should be taken to provide an additional user/users with the roles SAP_SLD_GUEST, SAP_SLD_SUPPORT (for SLD) SAP_XI_DISPLAY_USER_J2EE and SAP_XI_SUPPORT_J2EE (for ESR, ID) for the system/s where the SLD, ESR and ID are functioning running.
d) For an AEX which is installed along with the BPM add the roles SAP_BPM_SuperDisplay, SAP_BPM_Navigation, SAP_BPM_Debug, SAP_BPM_CTX_SUPER_ADMIN, NWA_READONLY, NWA_SUPERADMIN.
For AS Java, the supplied roles and authorizations offer only read access as far as possible. SAP support utilizes the access to AS ABAP and AS Java only without making unauthorized changes in the system. SAP only shows the data and doesn’t makes changes to the system. Please Note that for accessing the Enterprise Service Repository and Integration directory remotely additional setup for the remote connection is very much required
6. Current plug-in service ST-A/PI
Use the report RTCCTOOL as per SAP Document69455 for ensuring that the latest version of both add-ons is implemented. Among other things the add-ons contain function modules and data collectors which ensure the quality of the service data collection. Users to keep in mind that at least ST-A/PI 01M* is mandatory for PI 7.x releases because of the new collectors in the ABAP Stack which is required for the new PI related checks as of the latest ST-SER release 701_2010_1.
7. Please note that the SDCC(N) data collection for this service should be performed in the Integration Server client.
- SDCCN: Job /BDL/TASK_PROCESSOR* /BDL/TASK_PROCESSOR
- SDCC: Job AUTO_SESSION_MANAGER must function in the integration server client.
8. Collectors
As per SAP Document 91488 users to make sure that performance collectors (ST03N) and OS collectors (ST06) are functioning.
9. Report for PI/XI Performance Statistics
SAP Document746088 may be required for EarlyWatch and GoingLive Verification services. It explains describes how to create a report for displaying the performance statistics for PI/XI message processing in the Integration Engine. The report RSXMB_REMOTE_SERVICE is supplied automatically in 6.40 Basis SP19, 7.00 Basis SP10, 7.10 Basis SP07 so incase your system is at the appropriate Support Package level, you are not required to implement the SAP Note.
However, incase your system is on lower SP levels then you should you must implement this SAP Document so that this report can be made available. Additionally, SAP Document 820622 should be implemented for the report to provide the PI/XI correct message statistics. See the below point. The report is only important where the PI/XI performance statistics have not come into the EarlyWatch or GoingLive Verification services or EarlyWatch Alert where SMD is not made available. It is an ABAP based report and is not easily available for only Java systems. The report can be utilized where Solution Manager Diagnostics has not been implemented. Keep in mind that the Solution Manager Diagnostics is advised for a complete analysis of PI/XI performance.
10. Collectors for Message Statistics
With transaction SDCCN the data collectors collect all the performance statistics about PI/XI message processing. This data is critical for providing a complete analysis of PI/XI performance in EarlyWatch and GoingLive Verification service and in the PI/XI EarlyWatch Alert. Use Note 820622 for verifying whether the necessary parameters and jobs have been appropriately set. Parameters are required to be verified and if necessary corrected minimum 15 days before the commencing date of the session. Else it may be impossible to analyze the message processing performance of PI/XI.