readiness check for 73 v 2

Process Integration - Readiness Check

Frederic Carius, Tim Hensel, Jason Yang Active Global Support

Readiness Check A compilation of simple and advanced checks for Process Integration 7.3x (PI 7.3 & 7.31) including AEX installations Version 1.3 11. März 2013


Content:

Introduction ........................................................................................................................ 4

1 Basic Checks .................................................................................................................. 6

1.1 Tests for Java .............................................................................................................................................. 6

1.1.1 Java Component Check ........................................................................................................................... 6

1.1.2 Testing the availability of the PI JAVA applications ................................................................................. 8

1.1.3 Checking Java Caches ............................................................................................................................. 9

1.1.4 Connectivity tests between development tools ...................................................................................... 12

1.1.5 Configuration & Monitoring Home (PIMON) ........................................................................................... 16

1.1.6 Communication Channel Monitoring ...................................................................................................... 16

1.1.7 Message Monitoring via Status Overview Page..................................................................................... 19

1.2 Tests for ABAP dual stack Systems ....................................................................................................... 20

1.2.1 Basic Test for the Integration Engine ..................................................................................................... 20

1.2.2 Testing of the Web Service Runtime ...................................................................................................... 23

1.2.3 Connection Test for Integration Server .................................................................................................. 24

1.2.4 ccBPM .................................................................................................................................................... 29

1.2.5 Caches on the ABAP stack .................................................................................................................... 31

2 Configuration and Monitoring ..................................................................................... 34

2.1 Netweaver Administrator ......................................................................................................................... 35

2.2 Service Registry ........................................................................................................................................ 36

2.3 Background Job Monitoring .................................................................................................................... 37

2.3.1 Background jobs running on the SAP Web AS ABAP ..................................................................... 37

2.3.2 Background jobs running on the SAP Web AS Java ....................................................................... 37

2.4 TREX (Optional) ......................................................................................................................................... 39

2.5 Readiness Check on Advanced Adapter Engine Extended (AEX) ....................................................... 40

3 Solution Manager Diagnostics and Wily Introscope ................................................. 42

3.1 Solution Manager Diagnostics ................................................................................................................ 42

3.2 Wily Introscope Agent(s) Procedure ....................................................................................................... 43

4 Advanced Checks......................................................................................................... 44

4.1 SLD Associations...................................................................................................................................... 44

4.2 Configuration of HTTP Load Distribution with more than one Application Server ........................... 45

4.3 Small Scenario .......................................................................................................................................... 46

4.4 Configuration Test of scenarios in Integration Directory ..................................................................... 48


4.5 Using SAPMMC ......................................................................................................................................... 49


Introduction

The following graphic shows the components that make up the SAP Process Integration 7.3. The SAP Process Integration consists of the following functional components (for double stack installation):

Integration Builder consist of: o Enterprise Service Repository (ESR) o Service Registry (SR) o Integration Directory

System Landscape Directory (SLD)

Integration Server o Central Adapter Engine (Advanced Adapter Engine) o Integration Engine o Business Process Engine (ccBPM)

Runtime Workbench

SAP Netweaver Administrator (NWA)

Load Balancer Tool (e.g. SAP Web Dispatcher)

Solution Manager (not integral part of PI)

In PI 7.3, you have a new option to install Advanced Adapter Engine Extended (AEX) only. AEX is a fully independent, single-stack solution based on SAP NetWeaver AS Java. For readiness check on AEX, please refer to chapter 1.14.

Most of the components listed above have to exchange information during runtime of the Process Integration scenarios. Thus, it is essential that each component can be accessed and that the communication between them is set up correctly. However, major changes of the PI infrastructure, especially when applying patches or when changing hostnames in the context of a High Availability setup, are potentially critical for the correct collaboration of the PI components.

Therefore we recommend to carry out a set of simple checks that test the basic communication paths between the PI components to ensure a smooth runtime after a software patch or HA setup. These checks are divided into 2 groups:

The first group is meant to be carried out by everyone and requires little to no knowledge about PI.

The second group of checks is addressed to PI experts, e. g. developers or PI system administrators, and require a basic understanding of the Process Integration system.


Before you start you should gather some information about your installation to answer the following questions:

What is the hostname and port of the PI system?

o Note the Host and the Port

How many application servers your PI system consists of? (some indicated checks must be done on every application server)

Do you use a Load Balancer tool and if yes under which host and port the load balancer tool is available?

o Note the Host and the Port

Does the environment include a Solution Manager installation?

o Note the Host and ICM Port/ Java Port

Do you have set up a local System Landscape Directory (SLD) or a central SLD located on another host?

o A local SLD is the SLD running on the local PI System.

o If a central SLD is used note the Host and the Port

Do you have set up a Non Central Adapter Engine?

o Note the Host and Port

Do you have set up an Advanced Adapter Engine Extended?


Where is the Enterprise Service Registry located?


What kind of High Availability set up you have chosen?

o Did you separate the ABAP Central Services (ASCS) and the Java Central Services (SCS) from the Central Instance?

o If you answer this question with yes then also do the checks mentioned in every chapter which are relevant for High Availability (HA)

Do you use a TREX for index based messages search in your installation?

o Are there other Proxy Systems which should be connected to TREX?

o Are there other Non Central Adapter Engines which should be connected to TREX?


1 Basic Checks

This group of checks can be carried out easily, with a small expenditure of time and does not require extended PI know how.

1.1 Tests for Java

The following tests check basic functionalities of the Java part.

1.1.1 Java Component Check

The purpose of the check is to ensure that the java part is up and running from a technical perspective. If this check fails most of the subsequent checks will also fail.

Procedure:

Open a Browser Window and type in the URL or you use transaction SXMB_IFR instead to open the browser automatically. Then the load balancer (e.g. Web Dispatcher) URL should be opened automatically if configured correctly:

http://<Host>:<ICM Port>/startPage (if you use a HTTP load balancer replace Host and Port with the one of the load balancer)

If you can enter the page then this is the first hint that the ICM and at least one server node is up and running and this specific application is started. This does not mean that the PI System is fully configured for processing messages.

On this page you will find links to important applications. Among others a link to the “NetWeaver Administrator” (NWA) page. Enter the page by clicking on the link. A Logon window appears. To Logon you need j2ee_admin rights.


When you enter the page choose Operation Management Systems.

Choose Start&Stop

Further below you find information to the ICM and server nodes as well as to the Debug Proxy mode which in this case can be ignored. Green indicates that the component is up and running. Yellow and Grey should be investigated.

Troubleshooting

In case you have to analyze problems please refer to SAP Note 1095476 - Information for Troubleshooting of the AS Java and SAP Note 1452440 - PI Troubleshooting Guide 7.30.

Please check the following trace files for any errors: std_serverX.out, dev_serverX.out, default traces. In many cases It is very useful to have a full thread dump of the AS Java Engine. See SAP Note 1095473 - How to Get a Full Thread Dump in AS Java.

In case you cannot solve the problem by yourself please open a SAP customer message on component BC-JAS and provide relevant trace files mention in SAP Note 1095476 - Information for Troubleshooting of the AS Java , e.g., std_serverX.out.

https://service.sap.com/sap/support/notes/1095476








1.1.2 Testing the availability of the PI JAVA applications

Procedure:

Open a Browser Window and type in the URL: http://<Host>:<ICM Port>/dir/start/index.jsp (if you use a HTTP load balancer replace Host and Port with the one of the load balancer). This will bring up a browser window with 5 links:

Enterprise Service Builder, Web UI and Service Registry

Integration Directory with the Integration Builder

System Landscape Directory (SLD)

Configuration and Monitoring

o Configuration and Monitoring Home

o Runtime Workbench

The Service Registry is not an integral part of PI but it can run on AS Java of PI. Please see chapter: Service Registry.

Procedure: Open a Browser Window and type in the URL: http://<Host>:<ICM HTTP Port>/dir/start/index.jsp (if you use a HTTP load balancer replace Host and Port with the one of the load balancer). Navigate to the „Configuration and Monitoring Home‟. Once logged in, go to Monitoring – Adapter Engine and then to the „Component Monitor‟. If one of the components is not available the component monitor will display this with traffic lights. Furthermore you can perform a cache connectivity test (see chapter 1.5.1 Cache Connectivity Test) to verify if all steps for updating the runtime cache are working correctly.


1.1.3 Checking Java Caches

In SAP NetWeaver Process Integration information is often cached to speed up the input help of the tools or improve performance of the runtime. Here different caches are used during design and during runtime. Important runtime caches are:

Adapter Engine Connection Data Cache

Mapping Runtime Cache (Central Adapter Engine)

CPA Cache (Central Adapter Engine)

SLD Cache (covered by SLD Check)

1.1.3.1 Cache Connectivity Test

The Runtime Workbench offers a Cache Connectivity Test with a comprehensive view on the most important runtime caches. You use this function to check whether both steps for updating the runtime cache are working correctly:

1) Notification of the components with cache data (consumers) using a cache refresh and

2) Retrieval and update of cache data by the consumer.

In this procedure, a change list with a test object is created in the Integration Repository and released, and the Integration Directory is notified. The Integration Directory in turn notifies the relevant consumers, who then retrieve the test data and update their runtime cache accordingly.

Procedure

Open a Browser Window and type in the URL: http://<Host>:<ICM HTTP Port>/dir/start/index.jsp (if you use a HTTP load balancer replace Host and Port with the one of the load balancer). This will bring up a browser window with a link to the „Configuration and Monitoring Home‟. Once logged in, go to the „Testing‟ tab and open the “Cache Connectivity Test” tool. To start the test hit the Button “Start Test”. Please note that you will at first see yellow triangles that indicate that the test is still ongoing (the cache notifications and updates need some time) and that you will have to hit “Refresh Display”.

Check if all Cache Refreshes could be carried out, that is all components with cache data show a green light. Clicking on them allows troubleshooting of the problem.

Troubleshooting: In case of any error check the following documents (not available yet for 7.10/7.30, but the XI 3.0/7.0 one can still be used) by clicking on the link.

- “How to handle Caches with XPI Caches in SAP Netweaver 7.0” - “How to handle Caches with in SAP XI 3.0”

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290


1.1.3.2 Testing the CPA Cache

The cache of the Adapter Engine is called CPA Cache. It contains configuration information as e.g. adapter IDs that run on the J2EE Engine. Thus, it is important that the refresh of this cache is working correctly.

Procedure:

Open a browser window and call the URL: http://<Host>:<ICM Port>/CPACache/refresh (if you use a HTTP load balancer replace Host and Port with the one of the load balancer). Choose Mode = “delta” from the drop down box:

Attention: Be aware not to trigger a full cache refresh during processing of messages in production as it will impact message processing.

To trigger the test the user which you use to logon using the browser needs to have permission for action com.sap.aii.af.cpa.app*xi_af_cpa_cache_refresh which is by default assigned to the role SAP_XI_ADMINISTRATOR_J2EE. With the default configuration your user needs to have that role assigned in order to perform this check.

The test is successful if you get the message that the cache refresh has been carried out in xyz milliseconds. Please note that any additional text. e. g. “The XML page cannot be displayed” or “invalid at the top level of the document”, points to an error.

You can also see the content/ history of cache refreshes in a browser window by calling the following URL:

http://<Host>:<ICM Port>/CPACache (if you use a HTTP load balancer replace Host an Port with the one of the load balancer) Choose Display CPA Cache Content or View Cache Update History.


Troubleshooting:

1) Note 741214 - Troublesh. during cache update of the J2EE CPACache service gives valuable hints about possible reasons for errors. 2) In case of the error message “invalid at the top level of the document” the viewing of the source code of the respective Explorer page gives detailed information about the error.

Please keep in mind that errors of type “HTTP 503: Service Unavailable” during startup can considered as normal.

For more information regarding caches check the following documentation:


http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=00741214&_NLANG=E




1.1.4 Connectivity tests between development tools

The following tests should be carried out to test the connectivity between the tools needed during development:

Enterprise Service Repository – SLD

Integration Directory – Enterprise Service Repository

Integration Directory - Caches

1.1.4.1 Testing the connectivity between Enterprise Service Repository and SLD

Procedure:

Start the Enterprise Service Builder as described in the previous chapter. Create a new Software Component by clicking in the SWC navigation frame

A new Pop Up window appears. Here choose “Import from SLD”


This test is successful if you can see a list of Software Component Versions.

1.1.4.2 Testing the connectivity between Integration Directory and Enterprise Service Repository

Procedure:

Start the Integration Directory as described in the previous chapter. Go to „Tools‟ -> „Apply Model from ES Repository‟. Then use the Help for the Field „Name‟.

This test is successful if you can see a list of Integration Scenarios from the ES Repository. Cancel the Transfer once you have made sure that the list can be displayed properly.


1.1.4.3 Advanced Check: Testing cache notifications of the Integration Directory

For the development of scenarios it has to be ensured that the newly created information about objects (interface determinations, mappings etc.) is transmitted to the three caches that need the information at runtime:

Central Adapter Engine (CPA Cache)

Integration Server (SXI_CACHE)

Mapping Runtime (Central Adapter Engine)

The Integration Directory provides you with a Notification Service that is available via the menu entry “Environment” at the top of the user interface. This notification shows green/red status lights of cache notifications to the mentioned caches.

Since the creation or the change of an existing object is required to carry out this test, it is NOT recommended for productive systems.

Procedure:

Log into the Integration Directory and open an existing object. You may also create a new one if you prefer. If you choose to open an existing object, go into the edit mode afterwards and make a small change (like removing and subsequently adding a character in the description of the object). This small change is needed to be able to save and activate the object again. After saving and activating the cache notifications are started automatically. Take into account that specific objects are hold in specific caches. The adapter information is maintained in the Central Adapter Engine Cache (CPA_Cache) and the Interface Determination Data in the Integration Server Cache (SXI_CACHE). Depending on the object you change the corresponding cache is notified.


Check if the corresponding notification is executed successfully, that is they show a green light.

Check in tab Problems for possible failures


1.1.5 Configuration & Monitoring Home (PIMON)

The Runtime Workbench (RWB) has been replaced by the “Configuration & Monitoring Home” (PIMON) especially in java single-stack systems while the RWB can still be used in dual-stack installations. The new „Configuration & Monitoring Home‟ now serves as the central monitoring & administration tool of the Process Integration system. It offers self and status tests for most of the PI components: Integration Server, SLD; Adapter Framework, J2SE Adapter Engines, Integrated Business Systems, Proxy Runtimes and Mapping Runtime.

Procedure:

Open a Browser Window and type in the URL: http://<Host>:<HTTP Port>/dir/start/index.jsp. This will bring up a browser window with a link to the PIMON. Once logged in, go to the „Component Monitor‟.

In the list of components mark the individual components one by one and check the self-test entries for green lights displayed next to them.

Click on every link in the PIMON and check if they open up without error messages. For each link, carry out the specific action, e. g. try to display existing mapping programs in the Cache Monitoring. This test ensures that the connectivity between different components, running on different basis technologies (ABAP & Java) works properly. In addition, authorizations of the service users (e.g. PIRWBUSER) are being checked. The important links are:

Monitoring - Adapter Engine: „Message Monitor‟, „Communication Channel Monitor‟, „Performance Monitoring‟, „Cache Monitor‟, „IDOC Adapter Monitor‟, „Alert Configuration‟, „Alert Inbox‟ and „Cache Monitoring‟.

Monitoring - Processes & Tasks: „Manage Processes‟, „Manage Tasks‟

Configuration and Administration – Adapter Engine: „Message Priorization‟, „Background Processes‟, „User-defined Message Search Configuration‟

Configuration and Administration – Processes & Tasks: „Process Repository‟

Testing: „Cache Connectivity Test‟

1.1.6 Communication Channel Monitoring

Messages enter and leave the Process Integration via adapters. Some of them run on the Adapter Framework (typically JDBC, File, JMS, SOAP Adapter) and some of them also run on the integration server (IDoc Adapter, HTTP plain adapter). You may also use the J2SE standalone adapter engine or non-central adapter engines. The communication channel monitor provides current runtime information about the communication channels of individual adapters, as long as they are registered for communication channel monitoring.


To monitor adapters that do not provide runtime information to communication channel monitoring, continue to use the deprecated adapter monitor. For all standard adapters the Communication Channel monitor is the tool to be used and no information will be displayed in the Adapter Monitor.

Procedure:

Logon to the PIMON start page (e. g. by running transaction SXMB_IFR and using the link in the browser window) and navigate to Monitoring – Adapter Engine – Communication Channel Monitoring. For a first indicator about the status of the communication channels you can use the self-test in the Component Monitoring of the PIMON for a selected Adapter Engine. If you see a red light in the Communication Channel (CC) monitoring this already indicates that there is CC in error.


In the Component Monitoring of the PIMON for a selected Adapter Engine you can navigate to the “Communication Channel Monitoring” by clicking the corresponding link. Check that the Communication Channels that are in use, display a green light. If you observe a red light, have a look at the error messages displayed on the bottom of the page and inform the respective Application People/ Administrator/ Developer.


1.1.7 Message Monitoring via Status Overview Page

Use the message overview to get an overview of the number of messages that are in a certain processing status in a specific time period. This time period always refers to the receipt of the message.

These are the various status groups:

Scheduled, Successful, With Errors, Cancelled with Errors

Procedure:

Logon to the PIMON start page (e. g. by running transaction SXMB_IFR and using the link in the browser window) and navigate to message monitoring. Choose from the drop down menu: Messages from component: the component (Integration Engine, Adapter Engine, and Proxy Runtime) and from the drop down menu: From the Entry Database (Overview) and push the Display button.

From this screen you can directly navigate to the messages in the different status groups by clicking on the provided link. This will open the message monitoring and display the selected messages. From there you can analyze or troubleshoot individual.

Furthermore you restart or cancel a group of messages directly in the overview screen - if permitted by the relevant status. For this you can simply click the Cancel or Repeat button in the Status Overview section on the bottom of the screen. The action is executed in the background; the new values are displayed when you refresh the screen. Note: This may take some time depending on how many messages are selected.

Attention: Please be aware that messages in error have to be cancelled or resend to set them to a final state. Only then the messages can be removed from the system.


1.2 Tests for ABAP dual stack Systems

This chapter covers tests for components running on the ABAP stack. Please note that the PI installation options AEX & PO are java-only installations and do not have an ABAP stack. For that reason the chapter should only be used for dual-stack systems.

1.2.1 Basic Test for the Integration Engine

1.2.1.1 Testing of Internet Communication Manager

This test should verify that the Internet Communication Manager (ICM) is up and running and does not show any errors.

Procedure:

Log on to the Integration Engine

Execute transaction: SMICM

Check the status of the ICM by verifying the traffic light

Execute GoTo Trace File and check for problems (e.g. errors in the log file)

Important: Execute this check for every application server.

Troubleshooting

If you should experience errors while carrying out this check, please refer to the ICM help page or open a SAP customer message on component: BC-CST-IC.

http://help.sap.com/saphelp_nw73/helpdata/en/b8/2a8d65be7eee4eb66067f8a33d1c8b/content.htm


1.2.1.2 Queue Registration

This test checks if all inbound queues relevant for message processing are register at the Inbound Scheduler.

Procedure

Log On to the Integration Server

Execute Transaction: SMQR

Here you can see an overview about all registered Queues in PI

If you do not see the necessary queues register the queues via transaction SXMB_ADM Manage Queues

Register all Queues


Important: Check also the connected ABAP Proxy Systems whether the Queues are registered. In the

proxy systems other queue prefixes are used for message processing and should be activated as well.

Please refer for further information to the online help.

http://help.sap.com/saphelp_nw73/helpdata/en/7b/94553b4d53273de10000000a114084/content.htm


1.2.2 Testing of the Web Service Runtime

This test checks the Web Service Runtime (WS-RM) on the Integration Engine. To be able to use Web Services and Web Service Reliable Messaging you must have the Web Service Runtime configured. The configuration of the Web service runtime is client-specific and must be performed in each productive client and in client 000.

Procedure

Log On to the Integration Engine

Call transaction se38 and execute the program: SRT_ADMIN_CHECK

Check if you have any errors

In case you observe an error please refer to the online help and to note: Note 1110741 - Web service configuration can only be executed using SE37 as well as note: Note 1043195 - Configuration of the Web service runtime.

http://help.sap.com/saphelp_nw73/helpdata/en/46/abbc05ba0c2a7fe10000000a1553f6/content.htm

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1110741





1.2.3 Connection Test for Integration Server

Following tests are related to check the components, connections from and to the Integration Engine.

1.2.3.1 SLDCHECK

The SLDCHECK is a useful transaction that tests several things:

Do the RFC connections SAPSLDAPI and LCRSAPRFC work?

Are the server access settings in transaction SLDAPICUST correct?

Is it possible to read data from the SLD and the Exchange Profile?

Does the Integration Server have a Business System defined?

Procedure

Log into the client of the Integration Server and call transaction SLDCHECK. This will open up a browser window which allows you to log into the SLD and thereby check if the SLD can be accessed by a dialog user. After verifying that you can logon to the SLD, go back to the R/3 window and check for the following successful checks:

In the section “Properties of RFC destination SAPSLDAPI” there should be the statement “RFC Ping successful”

In the section “Calling function LCR_LIST_BUSINESS_SYSTEMS” there should be the statement “Function call terminated successfully” and you should be able to see a list of a few business systems

In the section “Calling function LCR_GET_OWN_BUSINESS_SYSTEM” there should be a statement “Function call terminated successfully” and you should see the business system of the integration server.

In the section “Calling function LCR_GET_BS_DETAILS” there should be a statement “Function call terminated successfully”. Check if the URL given in this section corresponds to http://<host>:500<sysnr>/sap/xi/engine?type=entry

In the section “Properties of RFC destination LCRSAPRFC” there should be the statement “RFC Ping successful”

In the section “Calling function EXCHANGE_PROFILE_GET_PARAMETER” there should be the statement “Function call terminated successfully”.

Important: Execute this check for every application server.

Troubleshooting

If you should experience errors while carrying out this check, use the online help for the SLD which provides a detailed problem analysis scenario. Use the link: Access To SLD From ABAP Fails. Additionally refer to Note 1143810 - Troubleshooting SLDCHECK - Releases 71X.

HA relevant: High Availability Set Up

Check also if the URLs of the RFC connection SAPSLDAPI and LCRSAPRFC are maintained as described in SAP Note 1052984 - Process Integration 7.1 - High Availability

Check settings in transaction SLDAPICUST ad described in SAP Note 1052984

http://help.sap.com/saphelp_nw73/helpdata/en/78/20244134a56532e10000000a1550b0/content.htm




1.2.3.2 Testing the HTTP services on the Integration Server

If an HTTP service is not running on the Integration Server, this can cause connection problems, which in turn can cause the notification of the cache on the Integration Server to fail or messages which not arrive in the Integration Engine. This check controls the availability of important PI specific services for the cache and for the pipeline.

Procedure: 1. Start transaction SICF.

Choose as Hierarchy Type: Service

Choose default_host sap xi.

o All services should be active, particularly the services: - cache - cache_ssl - engine (for pipeline processing) - adapter_plain (for HTTP Adapter) - wsdl*

Hint: You can execute job RSXMB_ACTIVATE_ICF_SERVICES to activate PI relevant services (refer to note: Note 1075166 - Activating the ICF services for XI). After execution, please check again.



Choose sap bc srt for the Web Service Runtime

o All services should be active as shown in the screenshot (refer to note: Note 1124553 - Inaktive ICF services of Web Service runtime)

2. Start transaction SICF. Choose default_host sap bc ping (connection test) and then choose Test service in the context menu of the entry.

A browser should then open, prompting a logon. If the browser does not open, this indicates a possible problem with the HTTP service of the SAP system and needs to be examined.




1.2.3.3 RFC Connections

Only two RFC connections are tested during the SLDCHECK, which is SAPSLDAPI and LCRSAPRFC. The remaining RFC connections can be tested via transaction SM59. The AI_RUNTIME_JCOSERVER connection is used to connect to the Java Mapping Runtime. The connection Integration_Directory_HMI is used to get data from the specific cache tables which contain the configuration data.

Procedure

Log into the client of the Integration Server and call transaction SM59. Test the following connections one at a time by double clicking on them and then pressing the button “Test connection”:

AI_RUNTIME_JCOSERVER (TCP/IP connection)

INTEGRATION_DIRECTORY_HMI (HTTP connection)

AI_VALIDATION_JCOSERVER (TCP/IP connection)

A successful test of the connections should look like this:

INTEGRATION_DIRECTORY_HMI (HTTP connection, use the XIISUSER with XI3.0 and the PIISUSER with PI 7.0 above to authenticate). Is the Path Prefix set to “/dir/CacheRefresh” as recommended since SP1 of XI 3.0? The normal response for INTEGRATION_DIRECTORY_HMI should be HTTP200.

The connections SAPSLDAPI and LCRSAPRFC have already been checked with transaction SLDCHECK.

HA relevant: High Availability Set Up

Check also if the URLs are maintained as described in note: Note 1052984 - Process Integration 7.1 - High Availability

In case of an AEX installation check Note 1614690 - Process Integration 7.3 AEX - High Availability





1.2.3.4 Testing the connection to the Integration Builder

The following aspects are tested:

The address of the Integration Builder

The HTTP connection of the Integration Server

The Integration Builder is running

The data of the Integration Builder is understood

Procedure

Log into the client of the Integration Server and execute the below mentioned programs in transaction se38 Call transaction se38. This will give you a pop-up in which the tests can be started by clicking on the program names highlighted in red.

The test SPROX_CHECK_IFR_ADDRESS should give you the status: OK: address maintained.

o HA relevant: High Availability Set Up

Check if the URL in the Exchange Profile / Actually Used is the one from the HTTP Load Balancer tool

o Refer to note: : Note 1052984 - Process Integration 7.1 - High Availability

The test SPROX_CHECK_HTTP_COMMUNICATION should give you the information that the communication is working.

The test SPROX_CHECK_IFR_RESPONSE should give you a confirmation that the communication is working:




1.2.4 ccBPM

An integration process is an executable cross-system process for processing messages.

In an integration process you define all the process steps to be executed and the parameters relevant for controlling the process.

You apply integration processes when you want to define, control, and monitor complex business processes that extend across enterprise and application boundaries. The design and processing of integration processes is also known as cross-component Business Process Management (cross-component BPM, ccBPM), or service orchestration.

1.2.4.1 ccBPM customizing

Cross-Component Business Process Management is integrated in SAP Business Workflow and runs in the Business Process Engine (BPE): an integration process can be sent messages to a workflow, and messages from a workflow can be processed in an integration process.

You have to perform automatic customizing to be able to use the Business Process Engine.

Procedure:

Perform the following steps in your AS ABAP system:

Log on as user with SAP_ALL rights (you cannot use DDIC or SAP*).

Call transaction SWF_XI_CUSTOMIZING to perform basic customizing. Executing this transaction will set all the required technical settings. The screen Automatic Workflow Customizing appears.


Make sure that the Maintain Runtime Environment node has a green check (not a red cross). If there is a red cross, do the following:

Select the Maintain Runtime Environment node.

Choose Perform Automatic Workflow Customizing. The system now performs the automatic customizing including all sub nodes.

Choose Maintain Definition Environment Maintain Prefix Numbers.

Choose Execute. The Prefix Numbers for Workflow and Organizational Management screen appears.

Choose Display <-> Change to activate the edit mode.

In the Available Prefix Numbers for Workflow and Organizational Management box, choose Create.

In the dialog box, enter a Prefix number equal to or higher than 900 and choose Save.

Note the following

1) For the customizing activity “Maintain Workflow System Administrator” the person responsible for the workflow definition from a technical point of view (system administrator) should be entered.

The workflow administrator is automatically notified of errors that occur during runtime.

2) Check your process in transaction SXI_CACHE. The return code for the Integration Processes already deployed must be show 0.

Troubleshooting

In case of problems check the Troubleshooting Guide under following Notes:

1) Note 807640 - BPE-TS: Troubleshooting Guide

2) Note 1143732 - BPE-TS: Troubleshooting Guide ccBPM in PI 7.1

1.2.4.2 ccBPM monitoring Starting from PI 7.3 a new monitoring for ccBPM processes is available. This monitor can be started from transaction SXMB_MONI_BPE Integration Process Monitoring (also available in “Configuration and Monitoring Home” on PI start page). This is new browser based view that allows a simplified and aggregated view on the PI Integration Processes.

On the initial screen you get an overview about all the Integration Processes executed in the selected time interval. Therefore you can immediately see the volume of each Integration Process.




From there you can navigate to the relevant Integration process and look at the individual process instances and the start and end time. Furthermore there is a direct entry point to see the PI messages that are assigned to this process.

1.2.5 Caches on the ABAP stack

1.2.5.1 SXI_CACHE

Transaction SXI_CACHE lists most of the content of the ES Repository and Integration Directory. This information is used by the Integration Server during runtime and it is thus critical that this information is


always up to date. A cache refresh is usually carried out automatically, but for testing purposes it can also be started manually. By carrying out a manual cache refresh several things can be tested, the most important being:

Connection to the SLD and the Integration Builder

Correct entries in the SLD

Procedure

Log into the client of the Integration Server and call transaction SXI_CACHE. Start a manual cache refresh via XI Runtime Cache Start Delta Cache Refresh.

Attention: Be aware not triggering a full cache refresh during processing of messages in production as it will impact message processing.

Once this is finished check transaction SXI_CACHE for (be aware that a full cache refresh can take a while until be finished):

a green light for the PI Runtime Cache status, saying “cache contents are up-to date”

Troubleshooting

If you should observe a red light or a warning, navigate to the reported problems/errors.



In case the exception does not make sense to you, open an OSS ticket on component BC-XI.

1.2.5.2 Adapter Engine Connection Data Cache

The Adapter Engine Cache contains the URL of the Adapter Engine. The information is used when a message is sent from the Integration Engine to the Adapter Engine.

Procedure:

Log into the client of the Integration Server and call transaction SXI_CACHE.

Navigate to: GoTo Adapter Engine Cache




The test is successful if you find the URL of your Adapter Engine and see the correct URL being displayed. Bear in mind that the cache is filled when a first message has been processed and sent to the Adapter Engine.

o Bear also in mind that in case you use a HTTP Load Balancer (WebDispatcher) you would see the Host and the Port of the Load Balancer here. (HA SetUp Note: Note 1052984 - Process Integration 7.1 - High Availability )

Troubleshooting

The Adapter Engine URL is taken from the SLD where the Adapter Engine is registered. The Adapter Engine registration is done automatically during startup. For HA setup it has to be configured in the Netweaver Administrator. For more information refer to Note: Note 1052984 - Process Integration 7.1 - High Availability



In case the exception does not make sense to you, open an OSS ticket on component BC-XI.








2 Configuration and Monitoring

Starting with PI 7.3 there will be a new monitoring tool called PIMon (Configuration and Monitoring Home).

Open a Browser Window and type in the URL: http://<Host>:<ICM Port>/dir/start/index.jsp. This will bring up a browser window with a link to the “Configuration and Monitoring Home”.

All the monitoring and administrative functionalities provided by NWA for PI are also accessible through the new link “Configuration and Monitoring Home”. This makes it possible for administrators to use a single tool for monitoring both ABAP and Java components.


2.1 Netweaver Administrator

Starting with PI 7.1 the SAP Visual Administrator as Administration tool was replaced by the Netweaver Administrator. The Netweaver Administrator represents a Web-based tool for monitoring and administration of your SAP NetWeaver system. You can perform administration tasks, such as, starting and stopping instances, checking and modifying configuration settings, analyzing logs and traces and ensuring the error-free functioning of all system components by continuous system monitoring.

The purpose of this check is to verify if the Netweaver Administrator is ready to use.

The SAP NetWeaver Administrator runs as an application on AS Java:

● SAP NetWeaver Administrator

Use the local SAP NetWeaver Administrator to monitor and administer its own local system. No additional configuration is required to do this. You can call the local SAP NetWeaver Administrator with the URL http://<host>:<port>/nwa. (If you use a HTTP load balancer replace Host and

Port with the one of the load balancer)

Procedure:

Open the Browser Window and type URL http://<host>:<port>/nwa (if you use a HTTP load balancer

replace Host an Port with the one of the load balancer)

A LogOn window appears. To LogOn you need j2ee_admin rights.

The management functions included in the SAP NWA are grouped in work centers according to the type of functionality that they provide. The following work centers are available:

Availability and Performance Management

Operations Management

Configuration Management

Troubleshooting Management

SOA Management


2.2 Service Registry

Setup a central Services Registry in your system landscape. It is recommended to setup one AS Java server as your Service Registry. The Service Registry can run on the PI AS Java server. In the Registry you can publish Web services coming from different systems. It gives you an overview of Web services in your landscape.

Please see the following link for configuring the Service Registry for your system. To configure your ABAP Backend System please see the following link.

The check controls if the link to the Service Registry is pointing to the Central Service Registry. Open your browser with URL: http://<host>:<port>/dir/start/index.jsp

Click on Service Registry. A new log on window pops up. Then you should see a screen like this one:

http://help.sap.com/saphelp_nw73/helpdata/en/45/c1ea61a1194432e10000000a155369/content.htm

http://help.sap.com/saphelp_nw73/helpdata/de/44/b7f7e1354135e7e10000000a1553f7/content.htm


2.3 Background Job Monitoring

The housekeeping jobs for PI ensure a smoothly running of Process Integration. They do not only carry out the archiving and deletion, but also care for performance data and retry mechanisms. Even you should have not scheduled any jobs up to now there are some standard jobs which are scheduled during installation.

2.3.1 Background jobs running on the SAP Web AS ABAP

When you have set up a PI System you will not find PI specific jobs running. On the ABAP part the background jobs need to be scheduled manually. You can find a good overview which jobs might need to be scheduled under the following link: Periodical Tasks. Please also refer to the report of your SAP Going Live Analysis Check service if already delivered for this installation.

Procedure Log in to your Integration Server and call transaction SM37. If you have used a dedicated user for all housekeeping jobs, enter this user. If you have used different users, search for the job names or ABAP program names provided in the following checklist. For each job have a quick glance at the job log.

SAP_BC_XMB_DELETE_<client> (deletion of XML messages if not archived)

SAP_BC_XMB_HIST_DELETE_<client> (deletion of history entries)

RSXMB_RESTART_MESSAGES (automatic restart of erroneous, asynchronous messages).

ARV_WORKITEM_WRP<date> (archiving of work items, only if ccBPM used)

ARV_WORKITEM_DEL<date> (deletion of archived work items, only if ccBPM used)

RSWWWIDE (deletion of work items if not archived, only for ccBPM)

RSWF_XI_INSTANCES_DELETE (deletion of archived work items, only if ccBPM used)

SXMS_PF_REORG (reorganizes performance data)

SXMS_PF_AGGREGATE (aggregates performance data)

SXMS_REFRESH_ADAPTER_STATUS (refresh of outbound adapter status, only if Idoc adapter and BPE is used)

For the Webservice Runtime make sure that the following job has been scheduled: SAP_SOAP_RUNTIME_MANAGEMENT.

2.3.2 Background jobs running on the SAP Web AS Java

In the J2EE engine a number of background jobs are scheduled during the installation process. It should be checked if they run smoothly. Procedure

Log onto PIMON via URL: http://<host>:<port>/pimon. Once logged in, navigate to „Configuration and Administration‟ – Adapter Engine - „Background Processing‟. A new window opens displaying the background processes being executed in your Java environment.

Check if a default Deletion Job is scheduled and in status green

Check if a default Recover Job is scheduled and in status green

Additional jobs to be monitored here could be the automatic message restart job or the archiving job if scheduled. Repeat that step for every adapter engine (non central adapter engine).

http://help.sap.com/saphelp_nw73/helpdata/en/48/aeb19e5bb5356be10000000a421937/frameset.htm

http://help.sap.com/saphelp_nw73/helpdata/en/46/abbc05ba0c2a7fe10000000a1553f6/content.htm


2.4 TREX (Optional)

For each component of an integration landscape that creates and persists messages (Integration Server, Adapter Engines and Integration Engines), a unique index can be created that contains all the messages of this component. The SAP NetWeaver search and classification engine TREX is required for this purpose.

You should check if you have done following settings when you run TREX for PI:

For ABAP:

Call transaction SXMB_ADM.

Choose Integration Engine Configuration.

Choose Change Specific Configuration Data.

Is the parameter TREX_RFC_DESTINATION to the category MONITOR set?

Repeat this check for every Proxy System which is supposed to be connected to TREX.

For Java:

Start the SAP NetWeaver Administrator.

Choose ConfigurationInfrastructure Java System Properties Details Services.

Select the service TREX Service.

Is TCP/IP connection data for the property nameserver.address entered?

Repeat this check for every Non Central Adapter Engine which is supposed to be connected to TREX.

Did you to set up and maintain the indexing of messages on your integration landscape components via the Indexing Administration in the Runtime Workbench?

For more information regarding set up and configuration of TREX please refer to the Online Help.

http://help.sap.com/saphelp_nw73/helpdata/en/43/6030fae92f5f87e10000000a1553f6/content.htm


2.5 Readiness Check on Advanced Adapter Engine Extended (AEX)

In PI 7.3, you have a new option to install Advanced Adapter Engine Extended (AEX) only. AEX is a fully independent, single-stack solution based on SAP NetWeaver AS Java.

Since AEX is based on AS Java alone, it is easier to install and maintain as it needs less memory and data storage. Therefore, AEX is a cost-saving option compared to a full installation of SAP NetWeaver PI.

In the above picture, you can see all the components of an AEX.

Procedure

Most of the checks for AEX are as same as the ones on traditional PI dual-stack installation. Please go through all steps in the following chapters for those checks:

Chapter Content

1.1.1 Java Component Check

1.1.2 Testing the availability of the PI-JAVA applications

1.5.4 Testing the CPA Cache

1.6 Connectivity tests between development tools

1.10 Netweaver Administrator


3.3 SLD Associations

For more information regarding AEX, please refer to the Online Help.

http://help.sap.com/saphelp_nw73/helpdata/en/a5/f6e04bdc1d4cdbbb32fa52ccdcc419/content.htm


3 Solution Manager Diagnostics and Wily Introscope

SAP introduced additional monitoring tools that can be used to monitor your solution landscape. Solution Manager Diagnostics (SMD) and Wily Introscope are two important tools for monitoring the J2EE stack of your PI solution. Both tools are connected to PI via so called agents which collect the data required for analysis. Therefore it is essential to check if the agents are correctly configured and delivering data to the monitoring tools. This can be done best by logging into the corresponding systems and checking the collected data. The SMD is integrated in the Solution Manager. To set up a Solution Manager SAP offers an SAP Solution Manager Starter Pack service. Information regarding that service and much more information about End to End Root Cause Analysis you can find on the Service Marketplace -> http://service.sap.com/solutionmanager SAP Solution Manager Details End to End Root Cause Analysis

3.1 Solution Manager Diagnostics

Start your Solution Manager Diagnostics. Choose your Solution Landscape and the system to be monitored and navigate to Root Cause Analysis End-To-End Analysis Workload Analysis Java Java Memory Analysis. This path might differ depending on the SP used. Select all instances of your installation. Choose a suitable timeframe as for instance the last week and press the Analyze button:

Check if GC Memory Usage graphs are displayed for all server nodes on all available instances.

Check that there are no gaps in the data collection.

If the data cannot be displayed or is missing for some period of time troubleshoot your SMD agent.

http://service.sap.com/solutionmanager


3.2 Wily Introscope Agent(s) Procedure

You can log on to Wily Introscope via Solution Manager Diagnostics. First choose your Solution Landscape and corresponding system. Navigate to Root Cause Analysis -> Workload -> Wily Introscope. In Wily Introscope choose for instance from the drop down menu the PI Adapter Framework Queue Overview page.

Check if the data is collected and some of the queues actually indicate activity on all the available J2EE server nodes.

Check that there are no gaps in the data collection.

If the data cannot be displayed or is missing for some period of time troubleshoot your Wily agent installation and configuration. Please refer to http://service.sap.com/diagnostics for more information.

http://service.sap.com/diagnostics


4 Advanced Checks

The following tests take up more time and require a certain degree of insight into the architecture of the SAP Process Integration, especially for the last check of this chapter.

4.1 SLD Associations

For several application processes it is required that the PI components all belong to the same „domain‟. This domain and the associations of this domain are set during start-up of the system. However, when changing the hostname of the Integration Server the associations may become inconsistent and it is necessary to recheck / recreate them.

Procedure:

Open SLD page via URL: http://<host>:<port>/sld. Once logged in go to the link “Technical System” and choose “Process Integration” from the drop down menu.

Check if the Integration Server has a Domain assigned (in the screenshot below the Domain of the PI 7.3 Process Integration system PIU is vmw4194).

Check if for the above Domain there are all components registered as well: Adapter Engine, Integration Directory, Integration Repository.

Check if there are other Domains that are no longer used.

Troubleshooting:

See note Note 764176 - Error in XI due to inconsistent SLD contents if you find any inconsistencies.



4.2 Configuration of HTTP Load Distribution with more than one Application Server

This check describes the setting you should check if you have set up an environment with more than one application server. From 7.1 the High Availability concept has changed. Starting with 7.1 it is default to have the Message Server and the Enqueue Server installed separated from the Central Instance. During this set up you should consider to install an additional application server. If you do so you need a HTTP Load Balancer like the SAP Web Dispatcher to distribute the Workload between the application servers. This check only verifies that the Load Balancing configuration has been done successful. For the configuration of HA please refer to Note 1052984 - Process Integration 7.1 - High Availability

Load Balancing has to be done when messages are sent to the Adapter Engine (from Integration Server) or to the Integration Server (from Adapter Engine) and several application servers are configured. Furthermore HTTP Load Balancing should also be considered for all adapters sending via HTTP (e.g. plain HTTP, SOAP). That is important in terms of performance and High Availability. This is not in scope of this check.

Procedure:

The check can be separated into two parts:

Integration Engine – Adapter Engine

Adapter Engine - Integration Engine

Integration Engine – Adapter Engine

This check is related to the prior check in this document: Adapter Engine Cache

Log into the client of the Integration Server and call transaction SXI_CACHE

Navigate to: GoTo -> Adapter Engine Cache

The test is successful if you find the Host and port of your HTTP Load Balancer (e.g. SAP WebDispatcher) for your central adapter engine. Bear in mind that the cache is filled when a first message has been processed and sent to the Adapter Engine.

Troubleshooting

The Adapter Engine URL is taken from the SLD where the Adapter Engine is registered. The Adapter Engine registration can be configured in the NetWeaver Administrator. For more information refer to Note 1052984 - Process Integration 7.1 - High Availability.





Adapter Engine – Integration Engine

The URL taken to send messages from the Adapter Engine to the Integration Engine is read from the SLD.

Logon to the SLD via URL: http://<hostname>:<ICM HTTP port>/sld

Once logged in go to the link “Business Systems” and filter for “Integration_Server”

Choose Tab Integration and verify the values in field: Pipeline URL of Integration tab: http://<Hostload balancer>:<Portload balancer>/sap/xi/engine?type=entry

Troubleshooting:

If that is not the case review Note 1052984 - Process Integration 7.1 - High Availability.

4.3 Small Scenario

The ultimate test to ensure that the PI landscape is working correctly is to create a little scenario and carry it out. In this way all development tools as well as the runtime is tested. This does not require as much time as the development of scenarios for your business processes since a very easy set-up can be chosen and since this procedure could be documented within your company.

A suggestion would be to create a File Communication Channel. This File Communication Channel would poll a *.txt file from a test folder, convert it into an XML and send it to the PI Integration Server. Create a simple mapping, for example rename the XML tags of your test file, that is then carried out in the Integration Server. The endpoint can again be a simple File Adapter that would store the mapped file into an archive folder.



If you need a more detailed description about how to set up a scenario, we recommend to implement the demo scenario for which SAP provides a detailed documentation as well as delivers the relevant objects in the Enterprise Service Repository. The demo scenario can be found at help.sap.com under following link: Demo Examples.

With PI 7.3 there is a CTC script available for the demo scenarios: Note 1304208 - Configuration Wizard: PI Demo Client

http://help.sap.com/saphelp_nwpi71/helpdata/en/50/26414d5f462f4fb384094056d46175/frameset.htm




4.4 Configuration Test of scenarios in Integration Directory

For PI there is the opportunity to test the configuration of your scenarios. The test is called “configuration test” and is part of the Integration Builder Directory. During the configuration test, the individual pipeline services of the Integration Server are called, and the change to the message in each case is simulated in the individual processing steps.

The advantage of this test is the detailed test report after having executed the test. If there are errors, it is possible to navigate to the relevant configuration objects and to see the errors on the “Error Log” tab page. Detailed information can be found in the online documentation.

Procedure:

Log on to the Integration Builder Directory and go to Tools Test Configuration. Define the input parameters like header data and a payload if required. Then start the test for the either the whole pipeline (”Run”) or for single pipeline steps (“Step Over”).

Check if all pipeline steps are executed successfully, that is they show a green light for a single step and that the status is the black/white flag for a successful processing of the whole pipeline.

http://help.sap.com/saphelp_nw73/helpdata/en/6b/874a4273bb3830e10000000a155106/frameset.htm


4.5 Using SAPMMC

SAPMMC is a powerful tool for monitoring and operation of SAP application server. You can use it to check the system availability as well as the traces/logs. It is also possible to use SAPMMC to trigger Java system dump, etc.

Procedure:

Logon to the SAPMMC via URL: http://<host>:5<sysnr>13/ (port 13 is the default SAPMMC port)

Navigate to the instances of the system AS Java Process Table You should see all the java nodes are in green

Navigate to the instances of the system Process List You should see all the entries are in green


Navigate to the instances of the system AS Java Threads You can see all threads and their status

readiness check for 73 v 2

Documents