Installation Guide › Deploying the Product › Deploying the Product for the First Time › Step 3. Allocate Resources for Production Use › SSI Environment Allocation

SSI Environment Allocation

Perform the steps in this section, only if you are allocating resources for an SSI environment. You must modify the sample server definition created by VMALLOC to re-define it as an IDENTITY entry rather than a USER entry. This enables the server instance to run on each node in the SSI cluster simultaneously. Perform the following actions:

1. Enter the following command to create the standard product USER directory entry files:

   VMALLOC SERVER name (DIRECT
   

   name

   Specifies the user ID of the product server machine to be deployed.

2. Change the USER directory statement to an IDENTITY directory statement in the product server directory entry file.
3. Add a BUILD directory statement for each node in your SSI cluster to the IDENTITY directory entry file.
4. Create a SUBCONFIG directory entry file corresponding to each BUILD directory statement added to the IDENTITY directory entry.
5. The minidisk definitions corresponding to the LOCAL, COMMON, DRCT, BKUP, HOLD, IPLDISK, RULE, and LOG tags in the VMSERVER NAMES file entry for CA VM:Secure must remain within the IDENTITY directory entry. The first CA VM:Secure server in the SSI cluster that logs on will obtain Read/Write access to these minidisks and initialize as the Master CA VM:Secure server. All other CA VM:Secure servers in the SSI cluster will obtain Read/Only access to these minidisks when they are logged on; they will initialize as Agent CA VM:Secure servers. These minidisks must have the following characteristics:
   • The minidisks must be defined with MR link modes.
   • The minidisks must be defined on shared volumes accessible by all nodes in the SSI cluster.
6. Read/Only minidisk definitions and links defined on shared volumes, accessible by all nodes in the SSI cluster, remain in the IDENTITY directory entry.
7. Two specific minidisk definitions are removed from the IDENTITY entry and defined in the SUBCONFIG entries you created for each member node. Those disks are:
   • The minidisk corresponding to the AUDT tag. A unique Read/Write disk is required to hold the audit data specific to each member.
   • The full volume minidisk defined to cover the Object Directory volume on each member node. Alternatively, you may use a LINK to a full volume minidisk defined within another virtual machine definition (like MAINT) to access the Object Directory
8. Incorporate the IDENTITY and SUBCONFIG entries into your Object Directory using your directory management procedures.