ECSAs ECs can be disconnected from the Platform. This allows workflows and services to continue processing throughout the upgrade . The as long as the Execution Contexts are installed in a separate container from the platform. Any standalone workflow can continue executing during the platform container upgrade, the downtime of the workflows will be minimized to the restart upgrade of the individual Execution Contexts.
However, there are certain prerequisites that need to be fulfilled in order to do this:
- The traffic protocol must support failover.
- You cannot keep ECSAs running when there have been changes in the storage models for Aggregation, Inter Workflow, Usage Management, PCRF, or Routing Control. For information about changes in the storage models, see the Release Notes.
For more details about these prerequisites, see the System Administrator's Guide.
| Tip | ||
|---|---|---|
| ||
You can use the Pico viewer in the Desktop or the configuration files in the directory |
To disconnect the ECSAsContainer, and each container can be handled separately.
To disconnect the ECs, run the following command:
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ mzsh mzadmin/<password> disconnect <ecsa<ec name> ... |
| Note | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| title | Note!Disconnected ECSAs ECs may still attempt to contact the Platform. These attempts will fail and cause warning messages (No open connection to | |||||||||||||||
| Scroll ignore | ||||||||||||||||
| ||||||||||||||||
| Next: |