-
Process Integration - Readiness Check
Andreas Boehme,Frederic Carius,Tim Hensel,Jason Yang
Active Global Support
Readiness CheckA compilation of simple and advanced checks
forSAP NW Process Integration 7.3x / 7.4 includingAEX
installations
Version 1.6
23. Januar 2014
-
Process Integration - Readiness Check
Page 2
Table of Content
Introduction
........................................................................................................................
4
1 Basic Checks
..................................................................................................................
6
1.1 Tests for Java
........................................................................................................................................
61.1.1 Java Component Check
......................................................................................................................
61.1.2 Testing the availability of the PI JAVA applications
..............................................................................
81.1.3 Checking Java Caches
.......................................................................................................................
91.1.4 Connectivity tests between development
tools...................................................................................
121.1.5 Configuration & Monitoring Home (PIMON)
.......................................................................................
151.1.6 Communication Channel Monitoring
..................................................................................................
161.1.7 Message Monitoring via Status Overview Page
.................................................................................
17
1.2 Tests for ABAP dual stack Systems
...................................................................................................
181.2.1 Basic Test for the Integration Engine
.................................................................................................
181.2.2 Testing of the Web Service Runtime
.................................................................................................
211.2.3 Connection Test for Integration Server
..............................................................................................
221.2.4 Cross-component Business Process Management
(ccBPM)..............................................................
261.2.5 Caches on the ABAP stack
...............................................................................................................
28
2 Configuration and Monitoring
.....................................................................................
31
2.1 NetWeaver Administrator (NWA)
........................................................................................................
31
2.2 Service Registry
..................................................................................................................................
32
2.3 Background Job Monitoring
...............................................................................................................
332.3.1 Background jobs running on the SAP Web AS ABAP
..................................................................
332.3.2 Background jobs running on the SAP Web AS Java
....................................................................
33
2.4 TREX (Optional)
...................................................................................................................................
35
2.5 Readiness Check on Advanced Adapter Engine Extended (AEX)
.................................................... 36
3 Solution Manager Diagnostics and Wily Introscope
................................................. 37
3.1 Solution Manager Diagnostics
............................................................................................................
37
3.2 Wily Introscope Agent(s) Procedure
..................................................................................................
38
4 Advanced
Checks.........................................................................................................
39
4.1 SLD Associations
................................................................................................................................
39
4.2 Configuration of HTTP Load Distribution with more than one
Application Server .......................... 39
4.3 Small
Scenario.....................................................................................................................................
41
-
Process Integration - Readiness Check
Page 3
4.4 Configuration Test of scenarios in Integration Directory
..................................................................
42
4.5 Using SAPMMC
...................................................................................................................................
43
5 Automated Checks
.......................................................................................................
44
-
Process Integration - Readiness Check
Page 4
Introduction
The following graphic shows the components that make up the SAP
Process Integration 7.3 and higher. TheSAP Process Integration
consists of the following functional components (for double stack
installation):x Integration Builder consist of:
o Enterprise Service Repository (ESR)o Service Registry (SR)o
Integration Directory
x System Landscape Directory (SLD)x Integration Server
o Central Adapter Engine (Advanced Adapter Engine)o Integration
Engineo Business Process Engine (ccBPM)
x Runtime Workbenchx SAP NetWeaver Administrator (NWA)x Load
Balancer Tool (e.g. SAP Web Dispatcher)x Solution Manager (not
integral part of PI)
In PI 7.3 (and later versions), 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 readinesscheck on AEX, please refer to chapter 1.14.
Most of the components listed above have to exchange information
during runtime of the Process Integrationscenarios. Thus, it is
essential that each component can be accessed and that the
communication betweenthem is set up correctly. However, major
changes of the PI infrastructure, especially when applying
patchesor when changing 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:
x The first group is meant to be carried out by everyone and
requires little to no knowledge about PI.x 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.
-
Process Integration - Readiness Check
Page 5
Before you start you should gather some information about your
installation to answer the followingquestions:
x What is the hostname and port of the PI system?o Note the Host
and the Port
x How many application servers your PI system consists of? (some
indicated checks must be done onevery application server)
x Do you use a Load Balancer tool and if yes under which host
and port the load balancer tool isavailable?
o Note the Host and the Portx Does the environment include a
Solution Manager installation?
o Note the Host and ICM Port/ Java Portx 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
x Do you have set up a Non-Central Adapter Engine?o Note the
Host and Port
x Do you have set up an Advanced Adapter Engine Extended?o Note
the Host and Port
x Where is the Enterprise Service Registry located?o Note the
Host and Port
x 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 chapterwhich are relevant for High Availability
(HA)
x 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?
-
Process Integration - 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 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 or you use
transaction SXMB_IFR instead to open the browserautomatically. Then
the load balancer (e.g. Web Dispatcher) URL should be opened
automatically ifconfigured correctly:
http://:/startPage (if you use a HTTP load balancer replace Host
and Port with the one ofthe 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 runningand this specific
application is started. This does not mean that the PI System is
fully configured forprocessing messages.
On this page you will find links to important applications.
Among others a link to the NetWeaverAdministrator (NWA) page. Enter
the page by clicking on the link. A Logon window appears. To Logon
youneed j2ee_admin rights.
-
Process Integration - Readiness Check
Page 7
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 inthis case can be
ignored. Green indicates that the component is up and running.
Yellow and Grey should beinvestigated.
TroubleshootingIn case you have to analyze problems please refer
to SAP Note 1095476 - Information for Troubleshooting ofthe 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. Inmany 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 theAS Java , e.g., std_serverX.out.
-
Process Integration - Readiness Check
Page 8
1.1.2 Testing the availability of the PI JAVA applications
Procedure:Open a Browser Window and type in the URL:
http://:/dir/start/index.jsp (if you use aHTTP load balancer
replace Host and Port with the one of the load balancer). This will
bring up a browserwindow with 5 links:
x Enterprise Service Builder, Web UI and Service Registryx
Integration Directory with the Integration Builderx System
Landscape Directory (SLD)x Configuration and Monitoring
o Configuration and Monitoring Homeo Runtime Workbench
The Service Registry is not an integral part of PI but it can
run on AS Java of PI. Please see chapter: ServiceRegistry.
And for 7.31 systems:
Procedure:
Open a Browser Window and type in the URL:
http://:/dir/start/index.jsp (if you usea 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 andthen to the Component Monitor. If one
of the components is not available the component monitor
willdisplay this with traffic lights. Furthermore you can perform a
cache connectivity test (see chapter 1.5.1Cache Connectivity Test)
to verify if all steps for updating the runtime cache are working
correctly.
-
Process Integration - Readiness Check
Page 9
1.1.3 Checking Java CachesIn 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 (Java) runtime
caches are:x Mapping Runtime Cache (Central Adapter Engine)x CPA
Cache (Central Adapter Engine)x SLD Cache (covered by SLD
Check)
1.1.3.1 Cache Connectivity Test
The Runtime Workbench / PIMON tool offers a Cache Connectivity
Test with a comprehensive view on themost important runtime caches.
You use this function to check whether both steps for updating the
runtimecache 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, 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.
ProcedureOpen a Browser Window and type in the URL:
http://:/dir/start/index.jsp (if you usea HTTP load balancer
replace Host and Port with the one of the load balancer). This will
bring up a browserwindow with a link to the Configuration and
Monitoring Home. Once logged in, go to the Testing tab andopen the
Cache Connectivity Test tool. To start the test hit the Button
Start Test. Please note that you willat 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.
9 Check if all Cache Refreshes could be carried out, that is all
components with cache data show agreen light. Clicking on them
allows troubleshooting of the problem.
-
Process Integration - Readiness Check
Page 10
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
onecan 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
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. 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://:/CPACache/refresh (if you use a HTTPload balancer replace
Host and Port with the one of the load balancer). Choose Mode =
delta from the dropdown box:
Attention: Be aware not to trigger a full cache refresh during
processing of messages in production as it willimpact message
processing.
To trigger the test the user which you use to logon using the
browser needs to have permission for
actioncom.sap.aii.af.cpa.app*xi_af_cpa_cache_refresh which is by
default assigned to the roleSAP_XI_ADMINISTRATOR_J2EE. With the
default configuration your user needs to have that role assignedin
order to perform this check.
9 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:
-
Process Integration - Readiness Check
Page 11
http://:/CPACache (if you use a HTTP load balancer replace Host
an Port with the one ofthe 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 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.
Please keep in mind that errors of type HTTP 503: Service
Unavailable during startup can be considered asnormal.
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
-
Process Integration - Readiness Check
Page 12
1.1.4 Connectivity tests between development tools
The following tests should be carried out to test the
connectivity between the tools needed duringdevelopment:
x Enterprise Service Repository SLDx Integration Directory
Enterprise Service Repositoryx 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 Componentby clicking in
the SWC navigation frame
A new Pop Up window appears. Here choose Import from SLD
-
Process Integration - Readiness Check
Page 13
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 ESRepository.
Then use the Help for the Field Name.
9 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.
-
Process Integration - Readiness Check
Page 14
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 atruntime:
x Central Adapter Engine (CPA Cache)x Integration Server
(SXI_CACHE)x 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. Ifyou
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 Interface
DeterminationData in the Integration Server Cache (SXI_CACHE).
Depending on the object you change the correspondingcache is
notified.
-
Process Integration - Readiness Check
Page 15
9 Check if the corresponding notification is executed
successfully, that is they show a green light.9 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 as of version 7.31 & 7.4 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 PIcomponents:
Integration Server, SLD; Adapter Framework, J2SE Adapter Engines,
Integrated BusinessSystems, Proxy Runtimes and Mapping Runtime.
Procedure:Open a Browser Window and type in the URL:
http://:/dir/start/index.jsp. This will bringup a browser window
with a link to the PIMON. Once logged in, go to the Component
Monitor.
9 In the list of components mark the individual components one
by one and check the self-test entriesfor green lights displayed
next to them.
9 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 basistechnologies (ABAP
& Java) works properly. In addition, authorizations of the
service users (e.g.PIRWBUSER) are being checked. The important
links are:
-
Process Integration - Readiness Check
Page 16
x Monitoring - Adapter Engine: Message Monitor, Communication
Channel Monitor,Performance Monitoring, Cache Monitor, IDOC Adapter
Monitor, Alert Configuration,Alert Inbox and Cache Monitoring.
x Monitoring - Processes & Tasks: Manage Processes, Manage
Tasksx Configuration and Administration Adapter Engine: Message
Priorization, Background
Processes, User-defined Message Search Configuration
x Configuration and Administration Processes & Tasks:
Process Repositoryx Testing: Cache Connectivity Test
1.1.6 Communication Channel MonitoringMessages enter and leave
the Process Integration via adapters. Some of them run on the
AdapterFramework (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-CentralAdapter 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 deprecated
adapter monitor. For all standard adapters the Communication
Channel monitor is thetool to be used and no information will be
displayed in the Adapter Monitor.
Procedure:9 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 ChannelMonitoring. 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 lightin the Communication Channel (CC)
monitoring this already indicates that there is CC in error.
9 In the Component Monitoring of the PIMON for a selected
Adapter Engine you can navigate to theCommunication Channel
Monitoring by clicking the corresponding link and hit Go. Check
that theCommunication Channels that are in use, display a green
light. If you observe a red light, have alook at the error messages
displayed on the bottom of the page and inform the
respectiveApplication People/ Administrator/ Developer.
-
Process Integration - Readiness Check
Page 17
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 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, Cancelled with Errors
Procedure:9 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 ProxyRuntime) and from the
drop down menu: From the Entry Database (Overview) and push the
Displaybutton.
9 From this screen you can directly navigate to the messages in
the different status groups by clickingon the provided link. This
will open the message monitoring and display the selected
messages.From there you can analyze or troubleshoot individual.
9 Furthermore you restart or cancel a group of messages directly
in the overview screen - if permittedby the relevant status. For
this you can simply click the Cancel or Repeat button in the
StatusOverview section on the bottom of the screen. The action is
executed in the background; the newvalues are displayed when you
refresh the screen. Note: This may take some time depending onhow
many messages are selected.
Attention: Please be aware that messages in error have to be
cancelled or resend to set them to a finalstate. Only then the
messages can be removed from the system.
-
Process Integration - Readiness Check
Page 18
1.2 Tests for ABAP dual stack Systems
This chapter covers tests for components running on the ABAP
stack. Please note that the PI installationoptions AEX & PO are
Java-only installations and do not have an ABAP stack. For that
reason the chaptershould 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 showany errors.
Procedure:9 Log on to the Integration Engine9 Execute
transaction: SMICM9 Check the status of the ICM by verifying the
traffic light
9 Execute GoTo Trace File and check for problems (e.g. errors in
the log file)
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
aSAP customer message on component: BC-CST-IC.
-
Process Integration - Readiness Check
Page 19
1.2.1.2 Queue Registration
This test checks if all inbound queues relevant for message
processing are register at the InboundScheduler.
Procedure9 Log On to the Integration Server9 Execute
Transaction: SMQR
9 Here you can see an overview about all registered Queues in
PI9 If you do not see the necessary queues register the queues via
transaction SXMB_ADM Manage
Queues
9 Register all Queues
-
Process Integration - Readiness Check
Page 20
Important: Check also the connected ABAP Proxy Systems whether
the Queues are registered. In theproxy systems other queue prefixes
are used for message processing and should beactivated as well.
Please refer for further information to the online help.
-
Process Integration - Readiness Check
Page 21
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 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.
Procedure9 Log On to the Integration Engine9 Call transaction
se38 and execute the program: SRT_ADMIN_CHECK9 Check if you have
any errors
In case you observe an error please refer to the online help and
to SAP Note 1110741 - Web serviceconfiguration can only be executed
using SE37 as well as SAP Note 1043195 - Configuration of the
Webservice runtime.
-
Process Integration - Readiness Check
Page 22
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:
x Do the RFC connections SAPSLDAPI and LCRSAPRFC work?x Are the
server access settings in transaction SLDAPICUST correct?x Is it
possible to read data from the SLD and the Exchange Profile?x 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:
9 In the section Properties of RFC destination SAPSLDAPI there
should be the statement RFC Pingsuccessful
9 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
9 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.
9 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
9 In the section Properties of RFC destination LCRSAPRFC there
should be the statement RFCPing successful
9 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 toSAP Note 1143810 -
Troubleshooting SLDCHECK - Releases 71X.
HA relevant: High Availability Set Up
9 Check also if the URLs of the RFC connection SAPSLDAPI and
LCRSAPRFC are maintained asdescribed in SAP Note 1052984 - Process
Integration 7.1 - High Availability
9 Check settings in transaction SLDAPICUST ad described in SAP
Note 1052984
-
Process Integration - Readiness Check
Page 23
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 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.9 Choose as Hierarchy Type:
Service9 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 toSAP Note 1075166 -
Activating the ICF services for XI). After execution, please check
again.
9 Choose sap bc srt for the Web Service Runtimeo All services
should be active as shown in the screenshot (refer to SAP 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.
-
Process Integration - Readiness Check
Page 24
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.
1.2.3.3 RFC Connections
Only two RFC connections are tested during the SLDCHECK, which
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:
9 AI_RUNTIME_JCOSERVER (TCP/IP connection)9
INTEGRATION_DIRECTORY_HMI (HTTP connection) (only up to 7.11)9
AI_VALIDATION_JCOSERVER (TCP/IP connection)
A successful test of the connections should look like this:
9 INTEGRATION_DIRECTORY_HMI (HTTP connection, use the XIISUSER
with XI3.0 and thePIISUSER with PI 7.0 above to authenticate). Is
the Path Prefix set to /dir/CacheRefresh asrecommended since SP1 of
XI 3.0? The normal response for INTEGRATION_DIRECTORY_HMIshould be
HTTP200.
9 The connections SAPSLDAPI and LCRSAPRFC have already been
checked with transactionSLDCHECK.
HA relevant: High Availability Setup
9 Check also if the URLs are maintained as described in note:
Note 1052984 - Process Integration 7.1- High Availability
9 In case of an AEX installation check Note 1614690 - Process
Integration 7.3 AEX - High Availability
-
Process Integration - Readiness Check
Page 25
1.2.3.4 Testing the connection to the Integration Builder
The following aspects are tested:
x The address of the Integration Builderx The HTTP connection of
the Integration Serverx The Integration Builder is runningx The
data of the Integration Builder is understood
ProcedureLog into the client of the Integration Server and
execute the below mentioned programs in transaction se38Call
transaction SE38. This will give you a pop-up in which the tests
can be started by clicking on theprogram names highlighted in
red.
9 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 SAP Note 1052984 - Process Integration 7.1 - High
Availability
9 The test SPROX_CHECK_HTTP_COMMUNICATION should give you the
information that thecommunication is working.
Note: This will only be successful if HTTP is configured in
cases where plain HTTP is disabled thischeck will fail.
9 The test SPROX_CHECK_IFR_RESPONSE should give you a
confirmation that the communicationis working:
-
Process Integration - Readiness Check
Page 26
1.2.4 Cross-component Business Process Management (ccBPM)
An Integration Process is an executable cross-system process for
processing messages. In an IntegrationProcess you define all the
process steps to be executed and the parameters relevant for
controlling theprocess. You apply Integration Processes when you
want to define, control, and monitor complex businessprocesses that
extend across enterprise and application boundaries. The design and
processing ofIntegration Processes is also known as cross-component
Business Process Management (ccBPM) orservice orchestration.
1.2.4.1 ccBPM customizing
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, andmessages
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:
9 Log on as user with SAP_ALL rights (you cannot use DDIC or
SAP*).9 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.
9 Make sure that the Maintain Runtime Environment node has a
green check (not a red cross). If thereis a red cross, do the
following:
x Select the Maintain Runtime Environment node.x Choose Perform
Automatic Workflow Customizing. The system now performs the
automatic
customizing including all sub nodes.
x Choose Maintain Definition Environment o Maintain Prefix
Numbers.x Choose Execute. The Prefix Numbers for Workflow and
Organizational Management screen
appears.
x Choose Display Change to activate the edit mode.x In the
Available Prefix Numbers for Workflow and Organizational Management
box, choose
Create.
x In the dialog box, enter a Prefix number equal to or higher
than 900 and choose Save.
-
Process Integration - Readiness Check
Page 27
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 SAP 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 fromtransaction
SXMB_MONI_BPEIntegration Process Monitoring (also available in
Configuration andMonitoring Home on PI start page). This is new
browser based view that allows a simplified and aggregatedview on
the PI Integration Processes. On the initial screen you get an
overview about all the IntegrationProcesses executed in the
selected time interval. Therefore you can immediately see the
volume of eachIntegration Process.
From there you can navigate to the relevant Integration Process
and look at the individual process instancesand the start and end
time. Furthermore there is a direct entry point to see the PI
messages that areassigned to this process.
-
Process Integration - Readiness Check
Page 28
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. 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:
x Connection to the SLD and the Integration Builderx 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 Delta Cache Refresh.Attention: Be aware not triggering
a full cache refresh during processing of messages in production as
it willimpact message processing.
Once this is finished check transaction SXI_CACHE for (be aware
that a full cache refresh can take a whileuntil be finished):
9 A green light for the PI Runtime Cache status, saying cache
contents are up-to date
-
Process Integration - Readiness Check
Page 29
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.
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 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
9 The test is successful if you find the URL of your Adapter
Engine and see the correct URL beingdisplayed. Bear in mind that
the cache is filled when a first message has been processed and
sent tothe 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 )
-
Process Integration - Readiness Check
Page 30
TroubleshootingThe Adapter Engine URL is taken from the SLD
where the Adapter Engine is registered. The Adapter
Engineregistration is done automatically during startup. For HA
setup it has to be configured in the NetWeaverAdministrator. For
more information refer to Note: Note 1052984 - 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.
-
Process Integration - Readiness Check
Page 31
2 Configuration and MonitoringStarting with PI 7.31 there will
be a new monitoring tool called PIMon (Configuration and Monitoring
Home).
Open a Browser Window and type in the URL:
http://:/dir/start/index.jsp. This will bring upa 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 thenew link Configuration
and Monitoring Home. This makes it possible for administrators to
use a single toolfor monitoring both ABAP and Java components.
2.1 NetWeaver Administrator (NWA)
Starting with PI 7.1 the SAP Visual Administrator as
Administration tool was replaced by the NetWeaverAdministrator
(NWA). The NetWeaver Administrator represents a Web-based tool for
monitoring andadministration of your SAP NetWeaver system. You can
perform administration tasks, such as, starting andstopping
instances, checking and modifying configuration settings, analyzing
logs and traces and ensuringthe 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.
Use the local SAP NetWeaver Administrator to monitor and
administer its own local system. No additionalconfiguration is
required to do this. You can call the local SAP NetWeaver
Administrator with the URLhttp://:/nwa. (If you use a HTTP load
balancer replace Host and Port with the one of theload
balancer)
Procedure:Open the Browser Window and type URL http://:/nwa (if
you use a HTTP load balancerreplace Host an Port with the one of
the load balancer)
A Logon window appears. To logon you need to have J2EE_ADMIN
rights assigned to your User-ID.
-
Process Integration - Readiness Check
Page 32
The management functions included in the SAP NWA are grouped in
work centers according to the type offunctionality that they
provide. The following work centers are available:
x Availability and Performance Managementx Operations
Managementx Configuration Managementx Troubleshooting Managementx
SOA Management
2.2 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. Open yourbrowser with
URL: http://:/dir/start/index.jsp
Click on Service Registry. A new log on window pops up. Then you
should see a screen like this one:
-
Process Integration - Readiness Check
Page 33
2.3 Background Job MonitoringThe housekeeping jobs for PI ensure
a smoothly running of Process Integration. They do not only carry
outthe archiving and deletion, but also care for performance data
and retry mechanisms. Even you should havenot 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 thebackground jobs need to be
scheduled manually. You can find a good overview which jobs might
need to bescheduled 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.
ProcedureLog in to your Integration Server and call transaction
SM37. If you have used a dedicated user for allhousekeeping jobs,
enter this user. If you have used different users, search for the
job names or ABAPprogram names provided in the following checklist.
For each job have a quick glance at the job log.
9 SAP_BC_XMB_DELETE_ (deletion of XML messages if not archived)9
SAP_BC_XMB_HIST_DELETE_ (deletion of history entries)9
RSXMB_RESTART_MESSAGES (automatic restart of erroneous,
asynchronous messages).9 ARV_WORKITEM_WRP (archiving of work items,
only if ccBPM used)9 ARV_WORKITEM_DEL (deletion of archived work
items, only if ccBPM used)9 RSWWWIDE (deletion of work items if not
archived, only for ccBPM)9 RSWF_XI_INSTANCES_DELETE (deletion of
archived work items, only if ccBPM used)9 SXMS_PF_REORG
(reorganizes performance data)9 SXMS_PF_AGGREGATE (aggregates
performance data)9 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 JavaIn the J2EE
engine a number of background jobs are scheduled during the
installation process. It should bechecked if they run smoothly.
ProcedureLog onto PIMON via URL: http://:/pimon. Once logged in,
navigate to Configuration andAdministration Adapter Engine -
Background Processing.A new window opens displaying the background
processes being executed in your Java environment.
9 Check if a default Deletion Job is scheduled and in status
green9 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 other Adapter Engine (Non-Central Adapter
Engine).
-
Process Integration - Readiness Check
Page 34
In addition, there might be another job scheduling required on
your SAP PI system, if you have enabledadditional persistence for
the IDoc_AAE (Java IDoc adapter). When the regular Adapter
Framework DeletionJob from above is executing, it also notifies the
IDoc_AAE adapter which XI messages are being deleted.When the
IDoc_AAE adapter receives an event for XI message deletion it also
deletes the correspondingpersisted IDoc_AAE entries from the
database. However, there might be some situations when theIDoc_AAE
adapter cannot be notified for the deletion of XI messages. In
order to apply the solution, first youshould apply the patch
matching your support package version as listed in SAP Note
1769638(IdocDBTableCleanup job to clean up IDoc_AAE adapter). Then
you have to configure the new AS Java JobIdocDBTableCleanup.
Procedure1. Navigate to SAP NetWeaver Administrator >
Operations > Jobs > Java Scheduler > Tasks
2. Press the Add button to add a new task;
3. Follow the wizard to configure the task according to your
needs:
3.1. Select IdocDBTableCleanup from the list of displayed
jobs;
3.2. You may change the Retention Period of the task so that the
task logs are kept for shorter or longer timethan the default of 30
days;
3.3. You have to enter a start and end time for the entries to
be deleted from the IDoc_AAE database tables.You can also select
whether consistency check against the existing XI messages in the
Adapter EngineMessaging System will be executed. The check is
enabled by default. This means that only entriescorresponding to
deleted XI messages will be removed from the IDoc_AAE tables. If
the check is disabledthen all entries processed between the set
start and end time will be deleted from the IDoc_AAE tables.
3.4. If you want to execute the job only once for the specified
input parameters you can configure a simpleexecution time.
-
Process Integration - Readiness Check
Page 35
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 ofthis component. The SAP NetWeaver search and
classification engine TREX was required for this purposein previous
PI versions (has been replaced by user-defined message search in PI
7.3x/7.4 meanwhile).
You should check if you have done following settings when you
run TREX for PI:
For ABAP:
9 Call transaction SXMB_ADM.9 Choose Integration Engine
Configuration.9 Choose Change Specific Configuration Data.9 Is the
parameter TREX_RFC_DESTINATION to the category MONITOR set?9 Repeat
this check for every Proxy System which is supposed to be connected
to TREX.
For Java:
9 Start the SAP NetWeaver Administrator.9 Choose
ConfigurationoInfrastructureo Java System Propertieso Detailso
Services.9 Select the service TREX Service.9 Is TCP/IP connection
data for the property nameserver.address entered?9 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.
-
Process Integration - Readiness Check
Page 36
2.5 Readiness Check on Advanced Adapter Engine Extended
(AEX)
In PI 7.3x & 7.4, you have a new option to install Advanced
Adapter Engine Extended (AEX) only. AEX is afully independent,
single-stack solution based on SAP NetWeaver AS Java. Since AEX is
based on AS Javaalone, 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
(dual-stack).
In the above picture you can see all the components of an AEX.
For more information please refer to theOnline Help.
ProcedureMost of the checks for AEX are as same as the ones on
traditional PI dual-stack installation. Please gothrough 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 (NWA)
3.3 SLD Associations
-
Process Integration - Readiness Check
Page 37
3 Solution Manager Diagnostics and Wily Introscope
SAP introduced additional 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
3.1 Solution Manager Diagnostics
Start your Solution Manager Diagnostics. Choose your Solution
Landscape and the system to be monitoredand navigate to Root Cause
Analysis End-To-End Analysis Workload Analysis Java JavaMemory
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:
9 Check if GC Memory Usage graphs are displayed for all server
nodes on all available instances.9 Check that there are no gaps in
the data collection.9 If the data cannot be displayed or is missing
for some period of time troubleshoot your SMD agent.
-
Process Integration - Readiness Check
Page 38
3.2 Wily Introscope Agent(s) Procedure
You can log on to Wily Introscope via Solution Manager
Diagnostics. First choose your Solution Landscapeand 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.
9 Check if the data is collected and some of the queues actually
indicate activity on all the availableJ2EE server nodes.
9 Check that there are no gaps in the data collection.9 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.
-
Process Integration - Readiness Check
Page 39
4 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.
4.1 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:Open SLD page via URL: http://:/sld. Once logged in go
to the link Technical System andchoose Process Integration from the
drop down menu.
9 Check if the Integration Server has a Domain assigned (in the
screenshot below the Domain of thePI 7.3 Process Integration system
PIU is vmw4194).
9 Check if for the above Domain there are all components
registered as well: Adapter Engine,Integration Directory,
Integration Repository.
9 Check if there are other Domains that are no longer used.
Troubleshooting:See note SAP 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
oneApplication Server
This check describes the setting you should check if you have
set up an environment with more than oneapplication server. From
7.1 the High Availability concept has changed. Starting with 7.1 it
is default to havethe Message Server and the Enqueue Server
installed separated from the Central Instance. During this setup
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 servers.
Thischeck only verifies that the Load Balancing configuration has
been done successful. For the configuration ofHA 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) 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.
-
Process Integration - Readiness Check
Page 40
Procedure:The check can be separated into two parts dependent on
the direction of message communication:
x (1) Integration Engine Adapter Enginex (2) Adapter Engine
Integration Engine
(1) Integration Engine > Adapter EngineThis check is related
to the prior check in this document: Adapter Engine Cache
9 Log into the client of the Integration Server and call
transaction SXI_CACHE9 Navigate to: GoTo -> Adapter Engine
Cache
9 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 the SCN guideHow to
Scale Up SAP NetWeaver Process Integration
(http://scn.sap.com/docs/DOC-16241).
(2) Adapter Engine > Integration EngineThe URL taken to send
messages from the Adapter Engine to the Integration Engine is read
from the SLD.
9 Logon to the SLD via URL: http://:/sld9 Once logged in go to
the link Business Systems and filter for Integration_Server9 Choose
Tab Integration and verify the values in field: Pipeline URL of
Integration tab:
http://:/sap/xi/engine?type=entry
-
Process Integration - Readiness Check
Page 41
Troubleshooting:9 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 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.
With PI 7.3 and later versions there is a CTC script available
for the demo scenarios: Note 1304208 -Configuration Wizard: PI Demo
Client
-
Process Integration - Readiness Check
Page 42
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 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).
9 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.
-
Process Integration - Readiness Check
Page 43
4.5 Using SAPMMC
SAPMMC is a powerful tool for monitoring and operation of SAP
application server. You can use it to checkthe system availability
as well as the traces/logs. It is also possible to use SAPMMC to
trigger Java systemdump, etc.
Procedure:9 Logon to the SAPMMC via URL: http://:513/ (port 13
is the default SAPMMC port) and
expand the tree structure
9 Navigate to the (dialog) instances of the system Process List
You should see all the entries arein green.
9 Navigate to the (dialog) instances of the system AS Java
Process Table You can see allconfigured J2EE server nodes and their
status. Please also check for Restart count > 0 that
mightindicate potential error situations
9 Navigate to the instances of the system AS Java Threads You
can see all threads and theirstatus.
-
Process Integration - Readiness Check
Page 44
5 Automated ChecksStarting from SAP PI version 7.10 (and above)
a CTC Configuration Wizard has been introduced providing aset of
automatic checks that can be performed any time after a new
installation, during runtime or afterapplying a Support Package or
Patch. It is only applicable if the system was setup by a 7.10 or
higherinstaller. Systems that have been upgraded from 6.40 or 7.0
are not supported. For further details, pleaserefer to SAP Note
1286149 - Configuration Wizard: PI Self Test for NetWeaver
Procedure:Use the NWA and browse to > Configuration >
Scenarios > Configuration Wizard. Use the CTC Template PISelf
Test for NetWeaver to trigger a series of self-tests.