Shut Down Old Products Manually
The table below lists how to shut down specific products.
Product | Shut Down Instructions |
API Portal | If the old and new API Portal are on the same machine: ![*](chapterTOC_bullet.png) Run this command in the old API Portal Cloud Controller: acc> stopall ![*](chapterTOC_bullet.png) Stop the cloud agent by going to the old_Software AG_directory/API_Portal/server/bin directory and running this command: CloudAgentApp.{bat|sh} stop |
CentraSite | If the old and new CentraSite are on the same machine, shut down all old Application Server Tiers by stopping the Software AG Runtime services, then shut down the old Registry Repository by stopping its service. |
EntireX | Shut down EntireX as instructed in the previous table, then shut down all Brokers, RPC Servers, and customer applications that use EntireX libraries. For instructions, see the product documentation for your old release. |
Terracotta | Shut down all non-webMethods clients. |
To shut down the other products on a Windows system.
![*](chapterTOC_bullet.png)
If the product is running as a service, shut down from the Windows Services window. Services are listed as Software AG
product release.
![*](chapterTOC_bullet.png)
If the product is running as an application, shut down from the Windows start menu. Applications are listed as
Software AG > Stop Servers > product .
On a UNIX system, use the instructions in the product documentation for your old release.
Note: It is especially important to shut down all old ActiveTransfer, Integration Server, Microservices Runtime, My webMethods Server, OneData, and Optimize instances that connect to database components you are going to migrate.