Page Comparison

To shut down execution:

...

workflow groups, workflows and Desktops:

1.  Open Execution Manager, and check the status of all Workflow Groups groups (Enabled / Disabled). This step is necessary to identify which groups need to be resumed after the upgrade is completed.

   1. If there is a mix of enabled and disabled groups, make sure to record all “Enabled” groups, as you will need this information during the Resume Workflow Execution process.

   2. Otherwise if all groups are enabled, you can proceed to the next step.

2. The Workflow Groups can be disabled using either the Execution Manager in Desktop

...

2. or via the command line. The example below shows how to disable all Workflow Groups via command line wfgroupdisable.

   Code Block
   $ mzsh mzadmin/<password> wfgroupdisable \*

...

...

3. Stop all workflows that are not disconnected and let them finish execution.

4. Ensure that all users shut down all connected Desktops.
   If you want to see which Desktops that are connected, you can use the following command:

   Code Block
   $ mzsh mzadmin/<password> pico -view

...

...

...

Shut down all ECs.

 $ mzsh shutdown <ec name> 

<!-- This step is not required when upgrading from 7.0 to 7.1 -->
<!-- 
7.6. Upgrade the Oracle Database Instance

Before performing an upgrade, the Oracle database may require an upgrade by 
running certain patch scripts. Depending on which version you are 
upgrading from and to, you may need to execute different scripts.
 
From 6.3 to 7.0
The core package requires the oracle database to be updated.
 

Run the script for generating a *.tar file containing the patch script(s):
$ ./setup.sh prepare_db_upgrade
The file database-upgrade.tar containing the required patch scripts will be generated.
 

Copy the file to the database server.
 

Exctract the script(s):
$ tar xvf database-upgrade.tar
 

Run the following command sequence:
$ sqlplus
Username: mzowner
Password: <password>
> @database-upgrade.sql
-->

...