Overview › VM Product Deployment

Previous Topic: VMALLOC Command Tool

Next Topic: VMDEPLOY Command Tool

VM Product Deployment

The CA Mainframe VM Product Manager architecture separates the product materials installation from the deployment so that the process of applying service is staged, and does not interfere with production server products.

Product deployment is a set of activities that result in the creation of the following items:

  1. User IDs to execute the product code.
  2. Copies of the installed product code for use by the running product. The running product does not have direct access to the product materials loaded from the installation media, but uses copies only.
  3. An initial version of configuration and control files for the product, which are based on the information gathered about the VM system at your site. This information includes elements of your hardware configuration and also values you defined in various VM system configuration files.

The following steps are involved in a typical deployment:

  1. A definition is created for the product deployment as an entry in a standard CMS NAMES file called VMSERVER NAMES. The VMDEFINE command created the initial version of an entry and the VMSERVER command is used to bring up a NAMES file panel for updating the entry.

    Note: For more information about format of an entry, see the section Defining a VMSERVER NAMES File Entry.

  2. A directory entry is created for any server virtual machine, worker virtual machine, or administration virtual machine defined in the VMSERVER NAMES file entry. Disk space is allocated for the new users. The process for allocating resources depends on your specific site procedures.

    Note: For more information, see the section Product Resource Allocation.

  3. Product materials, which were loaded to your system during product installation, are copied to disk space which becomes part of the deployment. Using a copy allows the original materials to be updated during the service process, without impacting a deployed server.
  4. An initial set of configuration files are created, based on the environment on the host VM system.
  5. Any required product specific procedures are executed. Items in this step might include initializing a product database, creating other product control files, or updating configuration files.