Filter
Top Products
Note: You can also shut down adapters using the graceful adapter shutdown
tool. For more information, see Graceful Adapter Shutdown.
11. The JVM is exited.
Note: When you run the interactive soft stop process, it should continue until
the JVM is exited. You should not try to undo any of the soft stop actions to
bring back the system.
Important: The soft stop only stops the noapp and ops JVMs. To stop the
remaining Sterling B2B Integrator JVMs and stop the system processing, you
must manually run a hard stop after the soft stop is complete.
12. After a cluster node restarts, processes that are saved in the database as
HALTED_SOFTSTOP are started/resumed automatically.
Completing a Soft Stop of Sterling B2B Integrator from the
System Troubleshooter
You can perform a soft stop from the system troubleshooter in the UI.
About this task
To perform this procedure from the command line, see “Completing a Soft Stop of
Sterling B2B Integrator from the Command Line” on page 115.
Important: A soft stop of Sterling B2B Integrator using the system troubleshooter
is not subject to timeout values and the soft stop will run as long as necessary for
all current process to finish processing.
To complete a soft stop of Sterling B2B Integrator from the system troubleshooter:
Procedure
1. Log in to the system troubleshooter (Operations > System > Troubleshooter).
2. If running a cluster, select a node to shut down at the Select Node field. If you
need to shut down the container node along with the ASI node, you must first
shut down the container node and then the ASI node, because shutting down
the ASI node first will disable the soft stop UI for the container node.
In a clustered installation, you also can soft stop the container node by going to
the Troubleshooter UI of the other live ASI node in the cluster and soft
stopping the container node from there.
3. Click Soft Stop.
The soft stop page opens in a new popup window.
Performance Management 111