Initiating a Managed Transition

Run the JadeReorgApp application with the initiateManagedTransition value specified for the action parameter to initiate the offline phase of a reorganization on the primary system and schedule the initiation of the transition on a secondary database by replaying the online phases of the reorganization that took place on the primary, stopping before the transition is initiated. The secondary system remains available and the inquiry applications continue to run.

Tracking is restarted at a time scheduled by the administrator on the secondary system. This action automatically shuts down the inquiry applications and server applications, and the offline phases of the schema instantiation are carried out. See "Secondary Database Availability" elsewhere in this chapter for an image of the phases of a managed transition.

For details about running the JadeReorgApp application, see "Reorganizing the Database from the Command Line", in Chapter 3 of the JADE Development Environment User’s Guide.)

Initiate a managed transition to enable the transition to be scheduled on the secondary database of a system that has a secondary database on which inquiry applications are running.

To initiate a managed transition

Load the schema and forms files into the primary database, suppressing any reorganization.
```
jadloadb path=c:\jade\system ini=c:\jade\jade.ini server=multiUser schemaFile=exampleDeploy.mul suppressReorg=true
```
The default loadStyle of latestSchemaVersion is assumed. The system remains available while the schema and forms files are loaded
Initiate the online reorganization phase up to the transition on the primary database.
```
jadclient path=c:\jade\system ini=c:\jade\jade.ini server=multiUser schema=RootSchema app=JadeReorgApp startAppParameters action=initiateReorgAllSchemas initiateTransition=false 
```
The system remains available while the online phase of the instantiation is performed. The primary database remains in dual update mode until the transition is initiated.

The secondary database enters the Seeking Approval state; that is, the replaying is halted until the disposition of the reorganization on the primary is known. The secondary database remains available in this state.
Shut down the primary database. If possible, perform a graceful system shut down, signing off users and so on.

Shut down the database server, to stop server applications.

The primary system is no longer available until the instantiation completes. The secondary system remains available.

Initiate the offline phase on the primary system.

jadclient path=c:\jade\system ini=c:\jade\jade.ini server=singleUser schema=RootSchema app=JadeReorgApp startAppParameters action=initiateManagedTransition

Restart the primary database, which is now available to users.

The secondary database replays the online phases of the reorganization that took place on the primary, stopping before the transition is initiated. The secondary system remains available and the inquiry applications continue to run.
At a time scheduled by the administrator on the secondary system, tracking is restarted. This action automatically shuts down the inquiry applications and server applications, and the offline phases of the schema instantiation are carried out.