8.9.2 Policy-Driven Dynamic Deployment

The following three levels of dynamic deployment are driven by user-defined policies:

• Package-level

  Dynamic deployment or undeployment of one or more application packages on an active Tuxedo machine is triggered under certain conditions (for example, CPU load is low and does not exceed 60%). The final machine where the packages are deployed is selected among the candidate machines according to the predefined filtering policy.

  Before you create a package-level policy, packages should be added from the Package List as candidates (“As Candidate” checkbox is checked). You can modify the imported UBBCONFIG entries detailed configuration by clicking Edit for each entry and then create deployment policies for the candidate packages in the Policy Management console.

  Note:

  Before dynamic deployment of a package, any newly introduced TMS server must be put under the directory referred by the PATH environment variable on Tuxedo boot-up, otherwise, the TMS server will not be able to be found by Tuxedo application runtime, even if it is located in the bin sub-directory of the package.
• Machine-level

  Dynamic deployment or undeployment of machines is triggered when some conditions (incident rules), defined by policy are met.

  You can define policies on the new added machine entries to convert them to candidate machines. The final machine to be deployed is selected among the candidate machines according to the predefined filtering policy.

  Machine-level dynamic deployment is often used together with package-level deployment. When a machine is dynamically deployed, the packages added to the machine are deployed at the same time.

• Server-level

  The number of deployed running Tuxedo servers can be increased or decreased automatically when some conditions (incident rules), defined by policy are met. The minimum and maximum server number depends on the MIN and MAX parameter set in the UBBCONFIG.

For more information, see Policies.