Blog Archive

Thursday, October 19, 2017

SAP PI single stack stop and start in outages or if any patching upgrade hardware switch

Om

Stop Procedure

To stop the AEX, perform the following steps:

    Stop the message flow from your sending systems where possible.

    Stop all sender communication channels on your Advanced Adapter Engine to avoid new messages coming in. Otherwise, messages might still be picked up and lost if a point-in-time recovery of your database is required, for example, for patching, upgrade, or hardware switch.

    Proceed as follows:

        Start SAP NetWeaver Administrator at http://:/nwa .

        Choose Start of the navigation path Monitoring Next navigation step Communication Channel Monitoring End of the navigation path.

        Select Advanced and in the Direction field select Sender .

        In the list of communication channels, select all and choose Stop .


    Monitor the status of your Adapter Engine until all incoming messages are processed successfully. Otherwise these messages might fail and you would have to restart them.

    Proceed as follows:

        Start the SAP NetWeaver Administrator http://:/nwa .

        Choose Start of the navigation path Monitoring Next navigation step Adapter Engine Status  End of the navigation path.

        Refresh the Backlog tab page until the total backlog of the sender services is 0.

    Decide if you want to stop the Adapter Engine (Jave SE) (if used at all).

    This is an optional step that must be performed from a browser running on the Adapter Engine host:

        To stop the Adapter Engine (Java SE), choose Shutdown Adapter Engine in the main menu at http://: .

        To stop adapters running within the Adapter Engine (Java SE), select the adapter in question under Available Adapters at http://: and then choose Stop .

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

        Consequence of stopping

        No errors occur during the downtime of the AEX. However, the sending systems are not able to address the Adapter Engine and no files are polled from the file system. This is especially important if a point-in-time recovery of your database is required, for example, for patching, upgrade, or hardware switch.

        Proceed as described in step 2.

        Consequence 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 AEX. However, they have to be manually restarted afterwards.

    Stop AEX.



Start Procedure


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

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

    Start the AEX.

    Wait until AS Java and all PI-related services are started.

    This process can be monitored with the SAP NetWeaver Administrator.

    Choose Start of the navigation path Operations Management  Next navigation step  Infrastructure Management  Next navigation step  Start & Stop  Next navigation step  Java EE Applications End of the navigation path.

    Restart the Adapter Engine (Jave SE) (if used and stopped at all) as follows:

        In the installation directory of the Adapter Engine, execute run_adapter.bat (Windows) or run_adapter.cmd (Unix).

        To start adapters running within the Adapter Engine (Java SE), select the adapter in question under Available Adapters at http://: and then choose Start .

    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.

    If you have stopped the sender communication channels on your AEX, start them to unlock message processing on the Adapter Engine.

    Proceed as follows:

        Start the SAP NetWeaver Administrator at http://:/nwa .

        Choose Start of the navigation path Monitoring Next navigation step Communication Channel Monitoring End of the navigation path.

        Select Advanced and in the Direction field select Sender .

        Check whether all communication channels have a green status after their restart.

    Check for messages with an error status in the AEX, in the Adapter Engines, and in your business systems (if used) as follows:

        Start the SAP NetWeaver Administrator at http://:/nwa .

        Choose Start of the navigation path Monitoring Next navigation step Message Monitoring End of the navigation path.

        Select Database (Overview) and choose Go .

    Here you can easily identify messages with errors and manually repeat or cancel them where possible. You can also use an automatic restart job. Proceed as follows:

        Start the SAP NetWeaver Administrator at http://:/nwa .

        Choose Start of the navigation path SOA Next navigation step Monitoring Next navigation step PI Background Processing End of the navigation path.

        Use an existing Restart job or create a new one if required.

    If your sending systems were stopped, you need to restart them.

    Check for errors on all sending systems.

Link

1 comment: