Readiness Check

Karsten Blankenstein,Tim Hensel

Solution OperationSupport

Readiness CheckA compilation of simple and advanced checks forProcess Integration 7.1 (PI 7.1)

Version 1

03. September 2008

Readiness Check

Page 2

Content:

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

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

1.1 Basic Tests for Java..............................................................................................................................61.1.1 Java Component Check......................................................................................................................61.1.2 Testing the availability of the PI-JAVA applications..............................................................................8

1.2 Basic Test for the Integration Engine.................................................................................................101.2.1 Testing of Internet Communication Manager .....................................................................................101.2.2 Queue Registration...........................................................................................................................11

1.3 Testing of the Web Service Runtime ..................................................................................................13

1.4 Connection Test for Integration Server..............................................................................................141.4.1 SLDCHECK ......................................................................................................................................141.4.2 Testing the HTTP services on the Integration Server.........................................................................151.4.3 RFC Connections..............................................................................................................................171.4.4 Testing the connection to the Integration Builder ...............................................................................18

1.5 Caches in PI.........................................................................................................................................191.5.1 Cache Connectivity Test ...................................................................................................................191.5.2 SXI_CACHE .....................................................................................................................................201.5.3 Adapter Engine Cache......................................................................................................................221.5.4 Testing the CPA Cache.....................................................................................................................23

1.6 Connectivity tests between development tools.................................................................................251.6.1 Testing the connectivity between Enterprise Service Repository and SLD .........................................251.6.2 Testing the connectivity between Integration Directory and Enterprise Service Repository.................261.6.3 Advanced Check: Testing cache notifications of the Integration Directory..........................................27

1.7 ccBPM..................................................................................................................................................29

1.8 Runtime Workbench (RWB) ................................................................................................................311.8.1 Communication Channel Monitoring..................................................................................................321.8.2 Status Overview Page.......................................................................................................................34

1.9 Netweaver Administrator ....................................................................................................................35

1.10 Service Registry...........................................................................................................................37

1.11 Backgroundjob Monitoring..........................................................................................................381.11.1 Background jobs running on the ABAP.......................................................................................381.11.2 Background jobs running on the SAP Web AS Java ...................................................................38

1.12 Trex...............................................................................................................................................39

2 Solution Manager Diagnostics and Wily/ Introscope ................................................40

2.1 Solution Manager Diagnostics............................................................................................................40

Readiness Check

Page 3

2.2 Wily Introscope Agent(s) Procedure ..................................................................................................41

3 Advanced Checks.........................................................................................................42

3.1 Test message to Integration Server....................................................................................................42

3.2 Test message to Adapter Engine........................................................................................................44

3.3 SLD Associations................................................................................................................................46

3.4 Configuration of HTTP Load Distribution with more then one Application Server ..........................47

3.5 Small Scenario.....................................................................................................................................48

3.6 Configuration Test of scenarios in Integration Directory ..................................................................49

Readiness Check

Page 4

Introduction

The following graphic shows the components that make up the SAP Process Integration 7.1. The SAPProcess Integration consists of the following functional components:? 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 Engineo 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)

Most of these components have to exchange information during runtime of the Process Integration. Thus, itis essential that each component can be accessed and that the communication between them is set upcorrectly. However, major changes of the PI infrastructure, especially when applying patches or whenchanging hostnames in the context of a High Availability setup, are potentially critical for the correctcollaboration of the PI components.

Therefore we recommend to carry out a set of simple checks that test the basic communication pathsbetween the PI components to ensure a smooth runtime after a software patch or HA setup. These checksare 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.

Readiness Check

Page 5

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

? What is the hostname and port of the PI system?o Note the Host and the Port

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

? Do I use a Load Balancer tool and if yes under which host and port the load balancer tool isavailable?

o Note the Host and the Port? Does the environment contains a Solution Manager?

o Note the Host and ICM Port/ Java Port? Is the Netweaver Administrator (NWA) set up as a Central Netweaver Administrator or as a Local

Netweaver Administrator?

o Note the Host and the 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 application of the PI System.o Note the Host and the Port

? Do you have set up a Non Central Adapter Engine?o Note the Host and Port

? Where the Enterprise Service Registry is located?o Note the Host and Port

? What kind of High Availability set up you have chosen?o Did you separated 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 chapterwith HA relevant

? 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?

Readiness Check

Page 6

1 Basic ChecksThis group of checks can be carried out easily, with a small expenditure of time and does not requireextended PI know how.

1.1 Basic 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 thischeck fails most of the subsequent checks will also fail.

Procedure:Open a Browser Window and type in the URL:

http://:/index.html (if you use a HTTP LoadBalancer replace Host an Port with the one ofthe LoadBalancer)

If you can enter the page then this is the first hint that the dispatcher an the at least one server node is upand running and this specific application is started.

On this page you will find important application. 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_adminrights.

Important: Depending on the set up of the Netweaver Administrator (local/ central) it is possible that youhave to access the central NWA via URL: http://:/nwapi.

Readiness Check

Page 7

When you enter the page choose Operation Management -> Systems.

Choose Start&Stop

Further below you find information to the dispatcher and server nodes as well as to the Debug Proxy modewhich in this case can be ignored. Green indicates that the component is up and running. Yellow and Greyshould be investigated.

TroubleshootingFor error troubleshooting please open an OSS message on component BC-JAS.

Readiness Check

Page 8

1.1.2 Testing the availability of the PI-JAVA applications

Procedure:Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with 5 links:

? Enterprise Service Builder and Service Registry? Integration Directory with the Integration Builder? System Landscape Directory (SLD)? Configuration and Monitoring

o Runtime Workbencho Netweaver Administrator

The SLD has already been tested in the first check. The Service Registry is not an integral part of PI but itcan run on AS Java of PI. Please see chapter: Service Registry.

So only the first two components plus the mapping runtime have to be tested at this point.

The following check cover the readiness and availability of the Enterprise Service Repository/ IntegrationDirectory and the Mapping Runtime.

Procedure:

Start a web browser and type in the following URL (if you use a HTTP LoadBalancer replace Host an Portwith the one of the LoadBalancer):

Enterprise Service Repository:http://:/rep/hmidiag/ext?method=info

Integration Directory:http://:/dir/hmidiag/ext?method=info

Mapping Runtime:http://:/run/hmidiag/ext?method=info

(Host name and port can be determined from the SAP Process Integration start page.)

A logon dialog should be displayed. If it is not displayed, this indicates that the Integration Repository (oreven J2EE) is not running and needs to be started.

Readiness Check

Page 9

Readiness Check

Page 10

1.2 Basic Test for the Integration Engine

1.2.1 Testing of Internet Communication Manager

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

Procedure:? Log on to the Integration Engine? Excecute transaction: smicm? Check the status of the ICM by verifying the traffic light

? Execute GoTo -> Trace File and check for problems

Important: Execute this check for every application server.TroubleshootingIf you should experience errors while carrying out this check, please refer to the ICM help page or open anOSS message on component: BC-CST-IC.

Readiness Check

Page 11

1.2.2 Queue Registration

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

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

Readiness Check

Page 12

Important: Check also the connected Proxy Systems if the Queues are registered. In the proxy systemsother queue prefixes are used for message processing and should be activated

Please refer for further information to the Online Help.

Readiness Check

Page 13

1.3 Testing of the Web Service Runtime

This test checks the Web Service Runtime (WS-RM) on the Integration Engine. To be able to use WebServices and Web Service Reliable Messaging you must have the Web Service Runtime configured. Theconfiguration of the Web service runtime is client-specific and must be performed in each productive clientand 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 serviceconfiguration can only be executed using SE37 as well as note: Note 1043195 - Configuration of the Webservice runtime.

Readiness Check

Page 14

1.4 Connection Test for Integration Server

These tests are related to check the components, connections from an to the Integration Engine.

1.4.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?

ProcedureLog into the client of the Integration Server and call transaction SLDCHECK. This will open up a browserwindow 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 followingsuccessful checks:

? In the section Properties of RFC destination SAPSLDAPI there should be the statement RFC Pingsuccessful

? In the section Calling function LCR_LIST_BUSINESS_SYSTEMS there should be the statementFunction call terminated successfully and you should be able to see a list of a few businesssystems

? In the section Calling function LCR_GET_OWN_BUSINESS_SYSTEM there should be a statementFunction call terminated successfully and you should see the business system of the integrationserver.

? In the section Calling function LCR_GET_BS_DETAILS there should be a statement Function callterminated successfully. Check if the URL given in this section corresponds tohttp://:500/sap/xi/engine?type=entry

? In the section Properties of RFC destination LCRSAPRFC there should be the statement RFCPing successful

? In the section Calling function EXCHANGE_PROFILE_GET_PARAMETER there should be thestatement Function call terminated successfully.

Important: Execute this check for every application server.

TroubleshootingIf you should experience errors while carrying out this check, use the online help for the SLD which providesa detailed problem analysis scenario. Use the link: Access To SLD From ABAP Fails. Additionally refer toNote 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 asdescribed in note: 1052984

? Check settings in transaction SLDAPICUST ad described in note: 1052984

Readiness Check

Page 15

1.4.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 inturn can cause the notification of the cache on the Integration Server to fail or messages which not arrive inthe Integration Engine. This check controls the availability of important PI specific services for the cache andfor 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 tonote: Note 1075166 - Activating the ICF services for XI). After execution check again.

Readiness Check

Page 16

? Choose sap -> bc -> srt for the Web Service Runtimeo 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 indicatesa possible problem with the HTTP service of the SAP system and needs to be examined.

Readiness Check

Page 17

1.4.3 RFC Connections

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

ProcedureLog into the client of the Integration Server and call transaction SM59. Test the following connections one ata time by double clicking on them and then pressing the button Test connection:

? AI_RUNTIME_JCOSERVER (TCP/IP connection)? Integration_Directory_HMI? AI_VALIDATION_JCOSERVER

A successful test of the connections should look like this:

? INTEGRATION_DIRECTORY_HMI (HTTP connection, use the XIISUSER with XI3.0 and thePIISUSER with PI 7.0 and PI 7.1 to authenticate). Is the Path Prefix set to /dir/CacheRefresh asrecommended since SP1 of XI 3.0?

Note that a HTTP 500 response is a successful test for this connection.

? The connections SAPSLDAPI and LCRSAPRFC have already been checked with transactionSLDCHECK.

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

Readiness Check

Page 18

Testing the connection to the Integration Builder

Transaction SPROXY (a transaction usually used for the creation of proxies) provides checks that can beused even if no proxies have been created in the PI landscape. 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

ProcedureLog into the client of the Integration Server and call transaction SPROXY -> Button Connection Test. Thiswill 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 thecommunication is working.

Readiness Check

Page 19

? The test SPROX_CHECK_IFR_RESPONSE should give you a valid XML document.For higher SPS of XI 3.0 and also for release 2004s (PI) you should receive a confirmation that thecommunication is working:

1.5 Caches in PIIn SAP NetWeaver Process Integration information is often cached to speed up the input help of the tools orimprove performance of the runtime. Here different caches are used during design and during runtime.Important runtime caches are:? Integration Server ABAP (SXI Cache)? Adapter Engine Cache? Mapping Runtime Cache (Central Adapter Engine)? CPA Cache (Central Adapter Engine)? SLD Cache (covered by SLD Check)

1.5.1 Cache Connectivity Test

The Runtime Workbench offers a Cache Connectivity Test with a comprehensive view on the most importantruntime caches. You use this function to check whether both steps for updating the runtime cache areworking 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, andthe Integration Directory is notified. The Integration Directory in turn notifies the relevant consumers, whothen retrieve the test data and update their runtime cache accordingly.

Readiness Check

Page 20

ProcedureLog into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the RWB. Once logged in, go to the Component Monitoring choose All from thedropdown menu of the field Component with Status and hit the Display button. Navigate to the Test byusing the Cache Connectivity Test Button. To start the test hit the Button Start Test. Please note that youwill at first see yellow triangles that indicate that the test is still ongoing (the cache notifications and updatesneed 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 agreen light. Clicking on them enables troubleshooting of the problem.

Troubleshooting:In case of any error check the following documents (not available yet for 7.10, but the XI 3.0/7.0 one can stillbe 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

1.5.2 SXI_CACHE

Transaction SXI_CACHE lists most of the content of the ES Repository and Integration Directory. Thisinformation is used by the Integration Server during runtime and it is thus critical that this information isalways up to date. A cache refresh is usually carried out automatically, but for testing purposes it can also bestarted manually. By carrying out a manual cache refresh several things can be tested, the most importantbeing:

? Connection to the SLD and the Integration Builder? Correct entries in the SLD

ProcedureLog into the client of the Integration Server and call transaction SXI_CACHE. Start a manual cache refreshvia XI Runtime Cache? Start Complete Cache Refresh (Shift + F6). This will trigger a background job thatcan be seen in transaction SM58 (its name is SAI_CACHE3_REFRESH_BACKGROUND).

Instead of a full cache refresh you can also trigger a delta cache refresh.

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

Readiness Check

Page 21

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

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

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

For more information regarding caches check the following documentation:- How to handle Caches with XPI Caches in SAP Netweaver 7.0- How to handle Caches with in SAP XI 3.0

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

Readiness Check

Page 22

1.5.3 Adapter Engine Cache

The Adapter Engine Cache contains the URL of the Adapter Engine. The information is used when amessage 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. Bear in mind that the cache isfilled 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 wouldsee the Host and the Port of the Load Balancer here. (HA SetUp Note: Note 1052984 -Process Integration 7.1 - High Availability )

TroubleshootingThe Adapter Engine URL is taken from the SLD where the Adapter Engine is registered. The Adapter Engineregistration can be configured in the Netweaver Administrator. For more information refer to Note: Note1052984 - Process Integration 7.1 - High Availability

For more information regarding caches check the following documentation:- How to handle Caches with XPI Caches in SAP Netweaver 7.0- How to handle Caches with in SAP XI 3.0

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

Readiness Check

Page 23

1.5.4 Testing the CPA Cache

The cache of the Adapter Engine is called CPA Cache. It contains configuration information as e.g. adapterIDs 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://:500/CPACache/refresh?mode=delta. (if youuse a HTTP LoadBalancer replace Host an Port with the one of the LoadBalancer)

A full CPA Cache Refresh is triggered by executing the following URL: URL:http://:500/CPACache/refresh?mode=full (if you use a HTTP LoadBalancer replace Host anPort with the one of the LoadBalancer)

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

Use the PIDIRUSER to authenticate yourself, it is the only user that is allowed to carry out a CPA CacheRefresh.

? The test is successful if you get the message that the cache refresh has been carried out in xyzmilliseconds. Please note that any additional text. e. g. The XML page cannot be displayed orinvalid 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://:/CPACache (if you use a HTTP LoadBalancer replace Host an Port with the one of theLoadBalancer)

Choose Display CPA Cache Content or View Cache Update History.

Readiness Check

Page 24

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

For more information regarding caches check the following documentation:- How to handle Caches with XPI Caches in SAP Netweaver 7.0- How to handle Caches with in SAP XI 3.0

Readiness Check

Page 25

1.6 Connectivity tests between development tools

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

? Enterprise Service Repository SLD? Integration Directory Enterprise Service Repository? Integration Directory - Caches

1.6.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 Componentby clicking in the SWC navigation frame

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

Readiness Check

Page 26

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

1.6.2 Testing the connectivity between Integration Directory and Enterprise ServiceRepository

Procedure:Start the Integration Directory as described in the previous chapter. Go to Tools -> Apply Model from ESRepository. 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. Cancelthe Transfer once you have made sure that the list can be displayed properly.

Readiness Check

Page 27

1.6.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 atruntime:

? 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 entryEnvironment at the top of the user interface. This notification shows green/red status lights of cachenotifications to the mentioned caches.

Since the creation or the change of an existing object is required to carry out this test, it is NOTrecommended 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 (likeremoving and subsequently adding a character in the description of the object). This small change is neededto be able to save and activate the object again. After saving and activating the cache notifications arestarted automatically. Take into account that specific objects are hold in specific caches. The adapterinformation is maintained in the Central Adapter Engine Cache (CPA_Cache) and the InterfaceDetermination Data in the Integration Server Cache (SXI_CACHE). Depending on the object you change thecorresponding cache is notified.

Readiness Check

Page 28

? Check if the corresponding notification is executed successfully, that is they show a green light.? Check in tab Problems for possible failures

Readiness Check

Page 29

1.7 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 forcontrolling the process.

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

Cross-Component Business Process Management is integrated in SAP Business Workflow and runs in theBusiness Process Engine (BPE): an integration process can be sent messages to a workflow, and messagesfrom 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.

Readiness Check

Page 30

? Make sure that the Maintain Runtime Environment node has a green check (not a red cross). If thereis 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 theworkflow 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 alreadydeployed 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

Readiness Check

Page 31

1.8 Runtime Workbench (RWB)

The Runtime Workbench is the central monitoring tool of the Process Integration. It offers self and statustests for most of the PI components: Integration Server, SLD; RWB, Adapter Framework, J2SE AdapterEngines, Integrated Business Systems, Proxy Runtimes and Mapping Runtime.

Procedure:Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the RWB. Once logged in, go to the Component Monitoring choose All from thedropdown menu of the field Component with Status and hit the Display button.

? In the list of components mark the radio button of the entries one by one and check if you get greenlights displayed at the bottom of the page

? Click on every link in the Runtime Workbench and check if they open up without error messages.The links are: Message Monitoring, End-to-End Monitoring, Performance Monitoring, IndexAdministration, Configuration, Alert Configuration, Alert Inbox and Cache Monitoring. For eachlink, carry out the specific action, e. g. try to display existing mapping programs in the CacheMonitoring. This test ensures that the connectivity between the RWB and ABAP as well as theconnectivity between the RWB and other JAVA applications works properly. In addition,authorizations of the PIRWBUSER are being checked.

? Under Integration Engines check the connected Proxy Systems? Under Non-Central Adapter Engines check the connected Non-Central Adapter Engine Systems

Readiness Check

Page 32

1.8.1 Communication Channel Monitoring

With very few exceptions messages enter and leave the Process Integration via adapters. Some of them runon the Adapter Framework (typically JDBC, File, JMS, SOAP Adapter), some of them run on the integrationserver (IDoc Adapter, HTTP plain adapter). You may also use the J2SE standalone adapter engine ordecentral adapter engines.

The communication channel monitor provides current runtime information about the communication channelsof 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, continueto use the adapter monitor. For all standard adapters the Communication Channel monitor is the tool to beused and no information will be displayed in the Adapter Monitor.

Procedure:? Logon to the Runtime Workbench start page (e. g. by running transaction SXMB_IFR and using the

link in the browser window) and choose component monitoring. A first indicator about the status ofthe communication channels is already given by the result of the self-test in the ComponentMonitoring of the RWB for a selected Adapter Engine. If you see a read light in the CommunicationChannel (CC) monitoring this already indicates that there are CC in error. When clicking on theDetails link you will see an overview about the status of the Communication Channels as shown inthe screenshot below.

Readiness Check

Page 33

? Check that the Communication Channels that are in use, display a green light. If you observe a redlight, have a look at the Error messages displayed on the bottom of the page and inform therespective Application People/ Administrator/ Developer.

Readiness Check

Page 34

1.8.2 Status Overview Page

Use the message overview to get an overview of the number of messages that are in a certain processingstatus 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, Canceled with Errors

Procedure:? Logon to the Runtime Workbench start page (e. g. by running transaction SXMB_IFR and using the

link in the browser window) and message monitoring. Choose from the drop down menu: Messagesfrom component: the component (Integration Engine, Adapter Engine, Proxy Runtime) and from thedrop down menu: From the Entry Database (Overview) and push the Display button.

? You should get an Output like the one in the picture above. Repeat the steps for every Proxy System(Basis 2004 > SP 19, Basis 2004s > SP 11) and Adapter Engines. If one of the components doesnot show the result refer to note: Note 1031773 - Activating the status overview in RWB messagemonitoring.

Readiness Check

Page 35

1.9 Netweaver Administrator

The Netweaver Administrator becomes more and more important for the administration of an SAP doublestack system. Up to XI 3.0 SP 20 and PI 7.0 SP 13 a lot of functionalities can also be found in other tools butwith upcoming releases the Netweaver Administrator will become the only administration tool.

Starting with PI 7.1 the SAP Visual Administrator as Administration tool was replaced by the NetweaverAdministrator. The Netweaver Administrator represents a single, central tool for administration,troubleshooting, and problem analysis of your SAP NetWeaver system. You can perform administrationtasks, such as, starting and stopping instances, checking and modifying configuration settings, analyzinglogs and traces and ensuring the error-free functioning of all system components by continuous systemmonitoring.

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 and exists in two versions:

? Local SAP NetWeaver Administrator

Use the local SAP NetWeaver Administrator to monitor and administer its own local system. Noadditional configuration is required to do this. You can call the local SAP NetWeaver Administratorwith the URL http://:/nwa. (if you use a HTTP LoadBalancer replace Host an Portwith the one of the LoadBalancer)

? Central SAP NetWeaver Administrator

Use the central SAP NetWeaver Administrator for central monitoring and administration. Thecorresponding system is called CEN. You need to perform various configuration steps both in CENand in the monitored systems to do this. The central SAP Netweaver Administrator requires a double-stack system (ABAP + Java).

You can call the central SAP NetWeaver Administrator with the URLhttp://:/nwapi. (if you use a HTTP LoadBalancer replace Host an Port with theone of the LoadBalancer)

Procedure:Open the Browser Window and type URL http://:/nwa (if you use a HTTPLoadBalancer replace Host an Port with the one of the LoadBalancer)

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

Readiness Check

Page 36

When you access the Administration page? System you should be able to see the status of the connectedsystem.

TroubleshootingIn case of problems check the Monitoring Set Up Guide for SAP NetWeaver in the SDN or underhttp://service.sap.com/operationsnw70? Monitoring and http://service.sap.com/nwa.1) Note 1122868 - Link to nwapi fails after NW PI 7.10 installation gives valuable hints about setting up thecentral SAP Netweaver Administrator.

2) See Note 1143645 Prefetch Job in status ERROR - /nwapi not working if the link to nwapi displays Nodata available to the system collector.

Readiness Check

Page 37

1.10 Service Registry

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

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

The check controls if the link to the Service Registry is pointing to the Central Service Registry.

Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with 5 links: Enterprise Service Repository and Service Registry, Integration Directory, RuntimeWorkbench and System Landscape Directory (SLD).

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

Readiness Check

Page 38

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

1.11.1 Background jobs running on the ABAP

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

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

1.11.2 Background jobs running on the SAP Web AS JavaIn the J2EE engine a number of background jobs are scheduled during the installation process. It should bechecked if they run smoothly.

ProcedureLog into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the RWB. Once logged in, go to the Component Monitoring choose All from thedropdown menu of the field Component with Status and hit the Display button.Click on the Adapter Engine button to get the details.Choose the button Background Processing. A new window opens displaying the background processesbeing 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 ifscheduled. Repeat that step for every adapter engine (non central adapter engine).

Readiness Check

Page 39

1.12 Trex

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 ofthis 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 Configuration Management?Infrastructure Management ? 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 theIndexing Administration in the Runtime Workbench?

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

Readiness Check

Page 40

2 Solution Manager Diagnostics and Wily/ Introscope

SAP introduced a number of monitoring tools that can be used to monitor your solution landscape. SolutionManager Diagnostics (SMD) and Wily Introscope are two important tools for monitoring the J2EE stack ofyour PI solution. Both tools are connected to PI via so called agents which collect the data required foranalysis. Therefore it is essential to check if the agents are correctly configured and delivering data to themonitoring tools. This can be done best by logging into the corresponding systems and checking thecollected data.

The SMD is integrated in the Solution Manager. To set up a Solution Manager SAP offers an SAP SolutionManager Starter Pack service. Information regarding that service and much more information about End toEnd Root Cause Analysis you can find on the Service Marketplace ->http://service.sap.com/solutionmanager -> SAP Solution Manager Details -> End to End Root CauseAnalysis

2.1 Solution Manager Diagnostics

Start your Solution Manager Diagnostics. Choose your Solution Landscape and the system to be monitoredand navigate to Root Cause Analysis -> Workload -> Java -> Java Memory Analysis. This path might differdepending on the SP used. Select all instances of your installation. Choose a suitable timeframe as forinstance 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 can not be displayed or is missing for some period of time troubleshoot your SMD agent.

Readiness Check

Page 41

2.2 Wily Introscope Agent(s) Procedure

Log on to Wily Introscope via Solution Manager Diagnostics. Therefore you first choose your SolutionLandscape and corresponding system. Navigate to Root Cause Analysis -> Workload -> Wily Introscope. InWily Introscope choose for instance from the drop down menu the PI Adapter Framework Queue Overviewpage.

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

? Check that there are no gaps in the data collection.? If the data can not be displayed or is missing for some period of time troubleshoot your Wily agent.

Readiness Check

Page 42

3 Advanced ChecksThe following tests take up more time and require a certain degree of insight into the architecture of the SAPProcess Integration, especially for the last check of this chapter.

3.1 Test message to Integration Server

In this check you test if it works to send a message to the Integration Server. During that test the ICMservices and the pipeline services (until receiver determination) as well as the SXI_CACHE lookup aretested. To do so you will send a test message from the Runtime Workbench Test Tool to the IntegrationServer. You wont need a configured scenario. You will need a valid user and password with enoughauthorization to execute the pipeline services. The message will fail in the Integration Server.

Procedure:Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the RWB. Once logged in, go to the Component Monitoring choose All from thedropdown menu of the field Component with Status and hit the Display button.

? In the list of components mark the radio button of the Integration Engine? Go to Tab: Test Message? Verify that the URL is the correct one (http://:/sap/xi/engine?type=entry) If this is not the

case execute check: SLD Associations.

? Enter arbitrary values into the fields Sender Component, Interface, Interface Namespace? Enter a valid user and password? Choose Quality of Service: Exactly Once? Enter an arbitrary text in the Payload

? Send the message by pressing the Send Message button? You should get an Output like the one in the screen

Readiness Check

Page 43

To verify that the message have been receive by the Integration Engine do the following

? Go to RWB Message Monitoring? Choose in the Drop Down menu: Integration Engine Database (Overview)? Choose the correct time frame and press the Display button? Look for a error message with the interface details you have chosen before

Important: Execute this check for every connected Proxy System.

Readiness Check

Page 44

3.2 Test message to Adapter Engine

In this check you test if it works to send a message to the Adapter Engine. During that test the AdapterEngine is tested in regards of accepting messages, storing messages and doing the look up to the CPAcache. To do so you will send a test message from the Runtime Workbench Test Tool to the Adapter Engine.You wont need a configured scenario. You will need a valid user and password. The message will fail in theAdapter Engine.

Procedure:Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the RWB. Once logged in, go to the Component Monitoring choose All from thedropdown menu of the field Component with Status and hit the Display button.

? In the list of components mark the radio button of the Adapter Engine? Go to Tab: Test Message? Verify that the URL is the correct one (http://:/MessagingSystem/receive/AFW/XI)? Enter arbitrary values into the fields Sender Component, Interface, Interface Namespace? Enter a valid user and password? Choose Quality of Service: Exactly Once? Enter an arbitrary text in the Payload

? Send the message by pressing the Send Message button? You should get an Output like the one in the screen

Readiness Check

Page 45

Important: Execute this check for every connected Non-Central Adapter Engine.

Readiness Check

Page 46

3.3 SLD Associations

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

Procedure:Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up a browserwindow with a link to the SLD. Once logged in go to the link Technical Infrastructure and choose ProcessIntegration from the drop down menu.

? Check if the Integration Server has a Domain assigned (in the screenshot below the Domain of thePI 7.1 Process Integration P71 is is4017n).

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

? 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.

Readiness Check

Page 47

3.4 Configuration of HTTP Load Distribution with more then oneApplication Server

This check describes the setting you should check if you have set up an environment with more then oneapplication server. With 7.1 the High Availability concept has changed. Starting with 7.1 it is mandatory tohave the Message Server and the Enqueue Server installed separated from the Central Instance. During thisset up you should consider to install an additional application server. If you do so you need a HTTP LoadBalancer like the SAP Web Dispatcher to distribute the Workload between the application server. This checkonly verifies that the Load Balancing configuration has been done successful. For the configuration of HAplease refer to Note 1052984 - Process Integration 7.1 - High Availability

Load Balancing has to be done when messages are send to the Adapter Engine (from Integration Server) orto the Integration Server (from Adapter Engine) and several application servers are configured. FurthermoreHTTP 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 EngineThis 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. SAPWebDispatcher) for your central adapter engine. Bear in mind that the cache is filled when a firstmessage has been processed and sent to the Adapter Engine.

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

Readiness Check

Page 48

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

? Log into the client of the Integration Server and call transaction SXMB_IFR. This will bring up abrowser window with a link to the SLD.

? Once logged in go to the link Business Systems and choose Integration_Server? Choose Tab Integration and verify the values in field: Pipeline URL:

http://:/sap/xi/engine?type=entry

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

3.5 Small Scenario

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

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

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

Readiness Check

Page 49

3.6 Configuration Test of scenarios in Integration Directory

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

The advantage of this test is the detailed test report after having executed the test. If there are errors, it ispossible 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 inputparameters 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 stepand that the status is the black/white flag for a successful processing of the whole pipeline.

1 Basic Checks1.1 Basic Tests for Java1.1.1 Java Component Check1.1.2 Testing the availability of the PI-JAVA applications

1.2 Basic Test for the Integration Engine1.2.1 Testing of Internet Communication Manager1.2.2 Queue Registration

1.3 Testing of the Web Service Runtime1.4 Connection Test for Integration Server1.4.1 SLDCHECK1.4.2 Testing the HTTP services on the Integration Server1.4.3 RFC Connections

1.5 Caches in PI1.5.1 Cache Connectivity Test1.5.2 SXI_CACHE1.5.3 Adapter Engine Cache1.5.4 Testing the CPA Cache

1.6 Connectivity tests between development tools1.6.1 Testing the connectivity between Enterprise Service Repository and SLD1.6.2 Testing the connectivity between Integration Directory and Enterprise Service Repository1.6.3 Advanced Check: Testing cache notifications of the Integration Directory

1.7 ccBPM1.8 Runtime Workbench (RWB)1.8.1 Communication Channel Monitoring1.1.11.8.2

1.9 Netweaver Administrator1.10 Service Registry1.11 Backgroundjob Monitoring1.11.1 Background jobs running on the ABAP1.11.2 Background jobs running on the SAP Web AS Java

1.12 Trex

2 Solution Manager Diagnostics and Wily/ Introscope2.1 Solution Manager Diagnostics2.2 Wily Introscope Agent(s) Procedure

3 Advanced Checks3.1 Test message to Integration Server3.2 Test message to Adapter Engine3.3 SLD Associations3.4 Configuration of HTTP Load Distribution with more then one Application Server3.5 Small Scenario3.6 Configuration Test of scenarios in Integration Directory