![]() |
![]() |
![]() |
![]() |
![]() |
•
•
• Enhanced Tuxedo tlisten daemon.The application package is a user generated .zip file and can have several tiers in it. For example:Figure 17‑2 Application PackageEvery Application Package is required to contain a file named "Properties.xml" in Tier1. This file is a group level's part UBBCONFIG file. It contains some properties in GROUPS, RMS, SERVERS, and SERVICES sections of a complete UBBCONFIG file and is mainly used to describe the relationship and parameters of all the servers within this package's groups. The Properties.xml file will be used to generate the ultimate UBBCONFIG file when decide to deploy this package to a machine using tmcrdom and its content can be modified in the according deployment plan.All the items in the GROUPS, RMS, SERVERS, SERVICES section of UBBCONFIG are divided into four categories:
Table 17‑1 GROUPS Section Properties
Table 17‑2 RMS Section Properties
Table 17‑3 SERVERS Section Properties
Table 17‑4 SERVICES Section Properties
Table 17‑5 Description Information of the Package Users need to use tmcrdom to create and deploy the domain. This command must be run on the master node of the domain which will be created by this command.
• "domain_name" will be checked. If the domain has already existed in the Deployment Repository, it will report error, or it will create this domain in the repository.
• "deployment_plan" is a text file. This feature assumes that it has already been created by the customer before invoking this command. It contains the deployment information needed by this domain. It can be specified in the command as an absolute path or relative path on the master node. Its format is similar to UBBCONFIG.
Note: In some scenarios, although tmcrdom execution fails, it actually has created a domain in the Deployment Repository, thus if you create the domain again you will receive an error message saying the domain already exists. To solve this, you need to delete the domain using the tmdeldom command with -f option before you can create the domain.A deployment_plan file is made up of nine possible specification sections. Allowable section names are:
• It specifies the repository path which the Application Packages will be put on. This parameter is required. The place which is specified by this parameter must be NFS accessible. The string length can't be larger than 256. It must be an absolute path.It specifies the repository path which all the domain deployment information will be put. This parameter is required. The place which is specified by this parameter must be NFS accessible. The string length can't be larger than 256. It must be an absolute path.For every machine, machine address, LMID, TUXCONFIG, TUXDIR and APPDIR are required. For master machine, CONFIGSCRIPT, BOOTSCRIPT and SHUTDOWNSCRIPT are required. For slave machine, BOOTSCRIPT and SHUTDOWNSCRIPT are forbidden.
Note: The scripts specified by CONFIGSCRIPT, BOOTSCRIPT, SHUTDOWNSCRIPT, and UNCONFIGSCRIPT must be able to be found by tmcrdom on the master machine where the command runs.Refer to the same parameter in UBBCONFIG. This group name will be used in the ultimate UBBCONFIG.Refer to the same parameter in UBBCONFIG. This group number will be used in the ultimate UBBCONFIG.Refer to the same parameter in UBBCONFIG. This rms entry name will be used in the ultimate UBBCONFIG.Refer to the same parameter in UBBCONFIG. All the entries in this RMS section which belong to this group must be associated with one Application Package group's all rms entries, or it will report error. The according group in the Application Package is specified by the group's PAKGRPNAME in the deployment plan.TMSNAME = string_value[0..256] can't be specified in the deployment plan. It will be from the properties.xml file.Refer to the same parameters in UBBCONFIG. This value will be used in the ultimate UBBCONFIG.Users can use tmdeldom to shut down and undeploy the domain. This command must be run on the master node of the domain.