Online Tutorials & Training Materials | STechies.com
Register Login

How to Run Remote Services for SAP PI/XI

|| || 0

How to Run Remote Services for SAP PI/XI
Stechies

1. Connection to SAP:

To prepare and deliver a service a network connection between your PI/XI solution and SAP is required. SAP 769478 describes the various remote connections available for PI/XI systems. SAP employees can only log on using servers that are maintained in the system data. Java Web Start tools like the Integration Directory or Enterprise Service Repository are most conveniently accessed using a Windows Terminal Server connection. Setup of WTS connections is described in SAP 605795. Alternative possibilities are described in SAP 800267 - "Integration Repository/directory" service connections. In order to access Wily Introscope for AS Java, a HTTP Remote Connection can be used as described in SAP 1593601. Further steps how to prepare Wily Introscope are described in SAP 797147 - Wily Introscope Installation for SAP Customers.

2. PI/XI services performed on customer Solution Manager systems should use the latest ST-SER version which ensures that service consultants and trained customer personnel use the most up-to-date checks and texts when performing PI/XI services. Older ST-SER versions restrict the ability to analyse the systems severely. For further information on ST-SER strategy, please refer to SAP 569116. You should activate the feature "Service Content Update" as per SAP 1143775 and check for updates to ensure that the most up-to-date checks are implemented for PI/XI services.

3. Improved PI related checks for PI 7.x s were contained in ST-SER 701_2010_1. These checks, with the support of new ABAP collectors and SMD functionality, cover components previously not deeply evaluated in PI remote services. The Adapter Engines (Central and De-central) are checked so recommendations can be provided and also further checks and recommendations for the Business Process Engine. There are further check enhancements to provide load balancing configuration recommendations and optimal parameter recommendations for additional Integration Engines within the PI system. Please that as of ST-SER 701_2010_1, if the SMSY configuration in the Solution manager System is not set properly for the PI system as of basis 7.00, PI/XI related checks will not appear in the PI/XI session or in the PI/XI EarlyWatch Alert as per SAP 1500069. For further information on the SMSY configuration please refer to SAP 1265070.

4. As PI/XI systems uses a Java stack, please review SAP 1498779 which describes the technical prerequisites that must be prepared for an SAP Java stack (both Java standalone and Java add-in for dual stack) in order for SAP remote services to be performed for the Java stack, including PI/XI support services. Also, Solution Manager Diagnostics is required; otherwise the quality of the analysis will be severely restricted. The technical prerequisites for remote service delivery using SAP Solution Manager Diagnostics are described in SAP 1172939.Where Solution Manager Diagnostics are not installed, Wily Introscope is still required for analysis.

5. Users and authorizations

 The SAP employee who performs the PI/XI service checks requires a user with the following specific authorizations:

a) PI 7.0x (dual stack)

Access is required to the Runtime Workbench (RWB), Enterprise Service Repository (ESR), Integration Directory (ID), System Landscape Directory (SLD), AS ABAP, NetWeaver Administrator (NWA), Exchange Profile and Visual Administrator tool.

Required user authorizations:

a) See SAP 1405975 for the minimum required authorizations for AS ABAP.  In addition to the authorizations supplied in SAP 1405975, 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 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) To access 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 performed by ensuring that action sap.com_com.sap.lcr.LcrUser is included in J2EE Engine security role LcrUser and 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 assigned to user group SAP_SLD_SUPPORT.

d) For access to the Visual Administrator tool, the role SAP_J2EE_ADMIN needs to be assigned in AS ABAP user management. that to access and use the Visual Administrator tool, OS access should be available.

e) To access the System Information page, assign the J2EE Engine security role SystemInfo_Support_Role (part of application sap.com/tc~monitoring~systeminfo)to a suitable user group using the Visual Administrator. This can be, e.g., user group "Everyone".

b) PI 7.1x (dual stack)

Access is required to Runtime Workbench (RWB), Enterprise Service Repository (ESR), Integration Directory (ID), System Landscape Directory (SLD), AS ABAP, NetWeaver Administrator (NWA), Exchange Profile

Required user authorizations:

a) See SAP 1405975 for the minimum required authorizations for AS ABAP.  In addition to the authorizations supplied in SAP 1405975, 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 NWA identity management, add 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.

c) PI 7.3x (dual stack)

Access is required to the Enterprise Service Repository, Integration Directory, System Landscape Directory, AS ABAP, NetWeaver Administrator, Exchange Profile

Required user authorizations:

a) See SAP 1405975 for the minimum required authorizations for AS ABAP.  In addition to the authorizations supplied in SAP 1405975, 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 NWA identity management, add 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) The role NWA_READONLY provides also sufficient monitoring authorizations to monitor NetWeaver Business Process Management (BPM) within the NWA. This is of relevance for example, if NetWeaver PI is used in conjunction with BPM.

d) PI 7.3x (single stack), Process Orchestration

Access is required to the Enterprise Service Repository, Integration Directory, System Landscape Directory, AS ABAP, NetWeaver Administrator.

a) For single stack systems (Java only, NetWeaver s 7.3x or higher), the ABAP authorizations are not relevant.

b) Within NWA identity management, add 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) If the single stack system is a non-central Adapter Engine, typically not all of the components SLD, ESR and ID are local objects on the non-central Adapter Engine. In this case, care has to 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 running.

d) For an AEX that is installed together with BPM the role NWA_READONLY provides also sufficient monitoring authorizations to use the same user for monitoring the BPM within NetWeaver Administrator.

For AS Java, the supplied roles and authorizations provide read only access as far as possible. SAP support uses access to AS ABAP and AS Java only without making unauthorized changes in the system. SAP only displays the data. SAP makes no changes to the system. that to access the Enterprise Service Repository and Integration directory remotely additional setup for the remote connection is required as described in SAP 800267 - "Integration Repository/directory" service connections.

6. Current plug-in service ST-A/PI - 69455

Use report RTCCTOOL as per SAP 69455 to ensure that the newest 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. For more detailed information see SAP 69455 (ST-A/PI) and 539977 (ST-PI). Please that at least ST-A/PI 01M* is required for PI 7.x s due to new collectors in the ABAP Stack that are required for the new PI related checks as of the latest ST-SER 701_2010_1.

7. Please that the SDCC(N) data collection for this service must be performed in the Integration Server client. See SAP 820622 regarding information on identifying the Integration Server client.

SDCCN: Job /BDL/TASK_PROCESSOR* /BDL/TASK_PROCESSOR
SDCC: Job AUTO_SESSION_MANAGER must run in the integration server client.

For more information about SDCCN see SAP 763561, for more information about SDCC see SAP 216952.

8. Collectors

As per SAP 91488 ensure that performance collectors (ST03N) and OS collectors (ST06) are running.

9. Report for PI/XI performance statistics - SAP 746088

SAP 746088 may also be required for EarlyWatch and GoingLive Verification services. It describes how to create a report to display performance statistics for PI/XI message processing in the Integration Engine. The report RSXMB_REMOTE_SERVICE is automatically supplied in 6.40 Basis SP19, 7.00 Basis SP10, 7.10 Basis SP07 so if your system is at the appropriate Support Package level, you do not need to implement the SAP .

However, if your system is on lower SP levels then you must implement this SAP for this report to be available. In addition, SAP 820622 must be implemented for the report to provide the PI/XI correct message statistics. See the below point.  The report is only required where the PI/XI performance statistics have not come into the EarlyWatch or GoingLive Verification services or EarlyWatch Alert where SMD is not available. It is an ABAP based report and is not available for Java-only systems. The report can be used where Solution Manager Diagnostics is not implemented. Bear in mind that Solution Manager Diagnostics is recommended for full analysis of PI/XI performance.

10. Collectors for message statistics - SAP 820622 (not for XI 2.0)

With transaction SDCCN the data collectors gather performance statistics about PI/XI message processing. This data is vital to provide a full analysis of PI/XI performance in EarlyWatch and GoingLive Verification service and in the PI/XI EarlyWatch Alert. Use 820622 to check whether the necessary parameters and jobs are correctly set. Parameters should be verified and if necessary corrected at least 15 days prior to the session date. Otherwise it may not be possible to analyze the message processing performance of PI/XI.


Related Articles