Changing Exactly-Once-in-Order Processing in the Adapter Engine 

Use

The Adapter Engine processes messages with quality of service Exactly Once in Order serialized according to the queue in which they arrive. The Integration Server, on the other hand, processes messages that are sent to different receivers in parallel in one queue.

You can display the processing type of the Adapter Engine for messages with quality of service Exactly Once in Order and change it once to the processing type of the Integration Server.

We recommend that you make this change.

Prerequisites

●      To make the change, you must have the role SAP_XI_ADMINISTRATOR_J2EE.

●      Before the change, make sure that as few messages as possible with quality of service Exactly Once in Order are in the database of the Adapter Engine.

●      To reduce the number of messages, you can define archive or delete jobs.

More information: Background Processing

●      Make the change at a time when you do not expect a large volume of messages with quality of service Exactly Once in Order.

During the change, the Integration Server does not accept any messages with quality of service Exactly Once in Order.

Procedure

...

       1.      Call the following page: http://<host><port>/MessagingSystem/migration.jsp.

The migration status is Never started.

The system displays the logs that have their own event handler.

       2.      To start the change, choose Start Migration.

You cannot interrupt the change.

       3.      To update the display, choose Refresh Status.

Result

Once the change has been made, the Adapter Engine processes messages with quality of service Exactly Once in Order for a queue with different receivers in parallel.

If the change is interrupted by an external problem, it is automatically continued when the Adapter Engine is started until it has been completed successfully.

The status display is Migration Status:complete.