Administrative Tasks

Administering and Maintaining SAP NetWeaver PI

More information: Administering and Maintaining SAP NetWeaver Process Integration

Monitoring Integration Scenarios

The central tool for monitoring the integration processes is the PI Monitoring dashboard in the Technical Monitoring Work Center in SAP Solution Manager.

For more information, see the documentation of SAP Solution Manager at SAP Help Portal ( http://help.sap.com) under Application Lifecycle Management . In SAP Solution Manager documentation, choose section Start of the navigation path Technical Operations Next navigation step Technical Monitoring and Alerting Technical Monitoring Work Center End of the navigation path .

You can use it to get an overview of all Integration Engines and Advanced Adapter Engines in your landscape. If you find there are certain processes or messages on a particular engine need to be reviewed more thoroughly, you can navigate to the corresponding local monitor on the system where the engine is running.

Within a local monitor, you can get detailed information about a specific process. Local monitors also allow you to control the process execution.

To access all local monitors in a quick and easy way, you can use the following entry page: http://[host]:[port]/pimon

SAP provides the following local monitoring tools:

You can monitor locally the processes on an Integration Engine using tools in transaction SXMB_MONI and additional monitoring tools. For more information, see Monitoring the Integration Engine .
You can monitor locally the processes on an Advanced Adapter Engine using the tools available in SAP NetWeaver Administrator. For more information, see Monitoring the Advanced Adapter Engine .
You can view the integration processes that run on the Business Process Engine. For more information, see Monitoring Integration Processes using SAP NetWeaver Administrator .

The monitoring frequency depends on the volume of messages processed. We recommend checking the various monitors at least once a day. It is also important that you frequently check the message queues to make sure that the overall message flow is working. If there are problems in a specific queue, no messages in this queue are processed.

Note

The Runtime Workbench cannot be used for monitoring purposes when using the Advanced Adapter Engine Extended.

Saving Message Versions

You can store versions of messages at runtime in the Advanced Adapter Engine (AAE) and the Integration Engine (IE).

More information: Saving Message Versions

Tasks Related to Software Logistics

Transporting Design and Configuration Objects

Process Integration landscapes in general consist of development systems, consolidation or test systems and production systems. Therefore, also several ES Repositories and Integration Directories come into play when you plan and maintain your system landscape and your processes end-to-end. Therefore, setting up transport scenarios and transport paths is a key task for administrators.

More information: Transporting ESR Content and Objects of Integration Directory

Note

Objects are not shipped from the Integration Directory because they reflect the configuration settings in a specific system landscape. However, you can have different Integration Directories installed in your landscape when you differentiate between test landscapes and productive landscapes, for example. In this case, you can transport from the test Integration Directory to the productive Integration Directory.

Change Management for Design and Configuration Objects

You can create different versions of design objects in the ES Repository and configuration objects in the Integration Directory. When you save an object for the first time, you create its first version. The object (still in edit mode) is stored in a user-specific change list (tab Change List in ES Repository or Integration Directory). The version ID is only closed when you activate the object. A new version is created when you start editing the object that is already activated. The ES Repository and the Integration Directory provide different options for version conflict management.

Note

Object versions are treated the same way in both the ES Repository and the Integration Directory.

More information:

Change Lists

(ES Repository)
Working with Change Lists (Integration Directory)

Administering Back-End Systems

To administer the back-end systems involved in an integration scenario, as well as the AS ABAP or AS Java part of the Integration Server, you can use the SOA Manager or SAP NetWeaver Administrator, respectively.

Using these tools, you can perform the following administrative tasks:

Monitoring services locally in the back-end system
Publishing services from the back-end system into the Services Registry (more information Services Registry)

SOA Manager is the administration tool for ABAP-based back-ends involved in integration scenarios.

You can access the SOA Manager by using the transaction code SOAMANAGER in the back-end system.

More information: Working with the SOA Manager

SAP NetWeaver Administrator is the administration tool for Java-based back-ends involved in integration scenarios.

You can access the SAP NetWeaver Administrator by entering the following data in a Web browser:

http://<host>:<port>/nwa

Here the following represents:

<host> the host where the Application Server Java is installed.
<port> the HTTP port of the Internet Communication Manager. It consists of 5<Java instance_number>00. For example, if the instance number of the Java instance is 60, the HTTP port is 56000.