1.3 Operations involved in the Application Stage

This topic explains the different operations involved in the Application Stage.

The different operations involved are:

Apply and Test Connection Buttons

On click of Apply button, the necessary operation which is selected against Application Stage field will get executed.

If the user has modified any value once after the successful Test Connection, the Apply button will get disabled once again. Test Connection needs to be tested once again to validate the current values and Apply button will get enabled on successful connection.

Install Begin and Install End Operations

In a root application setup, Install Begin should be executed as initial setup. After the execution of Install Begin, the application status will be available as INSTALLING.

Now the database setup for all the FCIS schemas can be done at application root level as usual.

Once the necessary database setup are done, then Install End should be executed. This will update the PDB application status as NORMAL.

This Install Begin and Install End should be executed only once in an installation.

Once the Install End executed at root application, then Sync operation can be executed in the required application PDBs.

Upgrade Begin and Upgrade End Operations

Upgrade Begin and Upgrade End can be used for further changes in that application.

After executing Upgrade Begin and Upgrade End, the application status will be UPGRADING and NORMAL respectively.

In the application root enabled deployment, the database setup can be done only when the application status as INSTALLING or UPGRADING.

Once the Install End or Upgrade End is completed, then only that application version can be synced to the required application PDB.

Sync Operation

Once the Sync operation has been completed then, it cannot be rolled back. It will be irreversible.

Proper backup needs to be maintained. In case of any sync failure, then it should be restored based on the backup only.

The database setup through installer will be allowed only in application root when the application status as INSTALLING or UPGRADING. The database changes from application root will be propagated to application PDB only by sync operation.

Note:

• All the common application database objects will be compiled only in the application root PDB.
• The compiled objects will be propagated from application root container to required application PDB during sync operation. The application will be created for the synchronized application PDB.
• Objects created in the application root PDB cannot be dropped/altered in application PDB. So the dynamically creating sequences for transactiontbl and referencetbl will be dropped from DDL tool. For fresh installation, these sequences will be created during each FMG module setup. For incremental version, the sequences for transactiontbl and referenceable should be created manually by calling sprecreatesequences and migration needs to be done.
• To reduce the number of invalids, the criteria load functions will be dropped and the same will be replaced by packages. Anyone of the criteria load for each criteria type should get unlock and authorize the same to reflect the criteria changes into the corresponding criteria packages.