Starting and Stopping 

The following table provides you with an overview of where and how to start and stop the various tools and engines required for usage type PI.

Tools for Starting and Stopping

Tool/Engine	Access	Detailed Description
System Landscape Directory (SLD)	Choose Administration ® Start/Stop Server at http://<XI host>:<port>/sld	After you have installed usage type PI, you must configure the SLD and then start it manually. Afterwards it restarts automatically if it stops at any point. You can also start the SLD explicitly, for example, when the SAP NetWeaver J2EE Engine is restarted or when there is a request for the SLD. After the SLD is started, you must ensure that the self registration tool for the technical systems is running.
Integration Server (including Business Process Engine and Integration Engine)	No special tool; started/stopped automatically when its host starts/stops.	When the Integration Server is started, it registers itself in the SLD.
Integration Builder	No special tool; started/stopped automatically when its host starts/stops.	When the Integration Builder is started, it registers itself in the SLD.
Runtime Workbench	No special tool; started/stopped automatically when its host starts/stops.	When the Runtime Workbench is started, it registers itself in the SLD.
Adapter Engine	No special tool; started/stopped automatically when its host starts/stops.	When the J2EE-based Adapter Engine is started, it registers itself in the SLD.

Basic configuration steps are performed during installation. The Installation Guide – SAP NetWeaver 2004s and the Configuration of Usage Type Process Integration (PI) explain these steps and describe checks to verify that the landscape is functioning properly.

Stop Procedure

To stop the various components of your PI system, perform the following steps:

...

       1.      If you use the Business Process Engine (BPE), first see how to start and stop the BPE.

       2.      Stop the message flow from your sending systems where possible. If the sending system uses proxies, you can follow steps 3 to 5 to stop the message flow.

       3.      Deregister the queues of your PI system by calling the transaction Integration Engine – Administration (SXMB_ADM) and choosing Manage Queues. Select Deregister Queues and choose Execute action.

       4.      Monitor the remaining entries in the queues by calling the qRFC Monitor Inbound Queue (transaction SMQ2) until no more queues are listed.

       5.      Check the tRFC entries by calling the transaction Transactional RFC (SM58) until the list is empty.

       6.      Decide if you want to stop the non-central Adapter Engine (if used at all). This is an optional step with the following advantages/disadvantages:

○     Advantage of stopping

No errors occur during the downtime of the Integration Server. However, the sending systems will not be able to address the Adapter Engine and no files will be polled from the file system.

○     Advantage of not stopping

All messages with quality of service EO (Exactly Once) and EOIO (Exactly Once in Order) that enter the non-central Adapter Engine are persisted during the downtime of the Integration Server. However, they have to be manually restarted afterwards.

       7.      Stop the Integration Server.

Start Procedure

To start the various components of your PI system, perform the following steps:

...

       1.      If the SLD is running on a different host and has been stopped for maintenance reasons, you need to start it.

       2.      Start the Integration Server.

       3.      Wait until the J2EE Engine and all PI-related services are started.

This process can be monitored with the Visual Administrator.

                            a.      Choose Server ® Services ® Deploy.

                            b.      Choose Applications on the right-hand side.

       4.      Restart the non-central Adapter Engine (if used and stopped at all). If you did not stop it, access the message monitor and manually restart the messages with errors.

       5.      Register the PI queues by calling the transaction Integration Engine – Administration (SXMB_ADM) and choosing Manage Queues. Select Register Queues and choose Execute action.

       6.      Call the qRFC Monitor Inbound Queue (transaction SMQ2) and check the status of the queues. The correct status is "RUNNING". It might take several minutes before this status appears.

       7.      Check for messages with an error status in the Adapter Engine, in the Integration Server, and in your business systems (if used) as follows:

                            a.      Call the Runtime Workbench from the XI start page.

                            b.      Choose Message Monitoring.

                            c.      Select the following options as required:

■      Adapter Engine <host>

■      Integration Server

■      Proxy Runtime <business_system>

       8.      Check your business processes (if used) by calling the transaction Business Process Engine – Monitoring (SXMB_MONI_BPE) and choosing Restart Process After System Crash.

       9.      If a cache refresh was performed and was still running when the Integration Server was shut down, call the transaction XI Directory Cache (SXI_CACHE) and check for errors by choosing XI Runtime Cache ® Display Refresh Error.

   10.      If your sending systems were stopped, you need to restart them; if they use ABAP proxies, apply steps 5 and 6.

   11.      Check for errors on all sending systems.

   12.      If you use the BPE, see also how to start and stop the BPE.