Prepare the Old Integration Server

1. If you are using webMethods Broker, shut down the new Broker Monitor if it is running. Restart the old Broker Monitor, and then start the old Broker Server.

3. Suspend document retrieval for all triggers and make sure all guaranteed messages have finished processing, as follows:

a. Open Integration Server Administrator and point to the old Integration Server.

b. Go to Packages > Management. Click View Locked Elements, click Unlock Elements, select all elements of triggers, and then click Unlock Selected Elements.

c. 9.0 upgrade: Go to the Settings > Messaging > Broker/Local Trigger Management page. In the Individual Trigger Controls area, in the Active column under Document Retrieval, click edit all and set Retrieval State to Suspended. Refresh the page until the Persisted Queue Counts field shows 0 for every trigger.

d. 9.5, 9.6, 9.7, or 9.8 upgrade: Go to the Settings > Messaging > webMethods Trigger Management page. In the Individual Trigger Controls area, in the Active column under Document Retrieval, click edit all and set Retrieval State to Suspended. Refresh the page until the Current Queue Counts field shows 0 for every trigger.

4. If you are using webMethods Broker, make sure all outbound Broker messages in the client side queue have been sent, as follows:

a. Make sure Integration Server is connected to the Broker.

b. 9.0 or 9.5 upgrade: Go to the Settings > Resources > Store Settings page. In the Outbound Document Store area, make sure the Current Documents in Outbound Store field shows 0.

c. 9.6, 9.7, or 9.8 upgrade: Go to the Settings > Messaging > webMethods Messaging Settings page. Make sure the CSQ Count field shows 0 for the Broker connection alias.

Note:

The CSQ Count field contains the same information as the Current Documents in Outbound Store field on the Settings > Resources > Store Settings page. You need only check the CSQ Count field.

5. 9.6, 9.7, or 9.8 upgrade: If you are using Universal Messaging, make sure all outbound Universal Messaging messages in the client side queue have been sent, as follows:

a. Make sure Integration Server is connected to each Universal Messaging server that is acting as a webMethods Messaging provider.

b. Go to the Settings > Messaging > webMethods Messaging Settings page. Make sure the CSQ Count field shows 0 for the Universal Messaging connection aliases.

6. Make sure all outbound JMS messages in the client side queue have been sent, as follows:

a. Make sure Integration Server is connected to the JMS providers.

b. Go to the Settings > Messaging > JMS Settings page. In the JMS Connection Alias Definitions area, make sure the CSQ Count field shows 0 for every JMS connection alias.

7. If you are going to upgrade business processes, and you have business process models that use volatile transition documents and process instances of those models are in a Started state, allow the Started processes instances to complete or suspend them before you upgrade.

Important:

If you do not allow Started process instances to complete or suspend before you upgrade, you could lose data.

Note:

Started process instances of models that use guaranteed transition documents do not have to complete or be suspended before you upgrade.