Systems Management API Support › Install CA VM:Secure API Components in the Socket SMAPI Server

Previous Topic: Configure the CA VM:Secure Server Environment

Next Topic: Files Provided by CA VM:Secure for the Socket SMAPI Server

Install CA VM:Secure API Components in the Socket SMAPI Server

These instructions refer to the IBM Systems Management Application Programming manual, and they apply only to the Socket version of the SMAPI server. See the separate section, later in this chapter, for information on the RPC Socket server, if you use that version of SMAPI support. To install the CA VM:Secure API components in the Socket SMAPI server, you need to perform the following steps:

To install the CA VM:Secure API components in the VSMWORKn virtual machines

  1. Install the VSMREQIN and VSMWORKn user IDs as described in the chapter “Setting up and Configuring the Server Environment” in the IBM Systems Management Application Programming manual. Install the VSMREQIU server if you plan to use IUCV to perform SMAPI requests.
  2. All CA VM:Secure components needed by the VSMWORKn user IDs are distributed on the CA VM:Secure public files disk, usually the VMANAGER 193 disk. Some CA VM:Secure customers copy the files on the 193 to a public disk such as the MAINT 19E Y-Disk. If your installation does not do this, then:
    1. Add this statement to the directory entry of each VSMWORKn user ID 
      LINK VMANAGER 193 293 RR
    2. Add this statement to the PROFILE EXEC for each VSMWORKn user ID. 
      ACCESS 293 H

    Note: If you have an alternate method of accessing files on the CA VM:Secure PUBLIC disk, implement that method for each VSMWORKn user ID.

  3. Allow each VSMWORKn user ID to issue CP Diagnose code X’D4’. With no External Security Manager, privilege class "B" is needed in each directory entry.. If you are using an External Security Manager then perform the following steps:
    1. For CA VM:Secure, add a SYSTEM rules for each SMAPI worker as follows: 
      ACCEPT DIAGD4 VSMWORKn

      If using the CA VM:Director product with another External Security Manager:

    2. For another ESM, use the appropriate controls in the ESM to allow each SMAPI worker to issue Diagnose code.
  4. Update the SMAPI Server Configuration File as documented in the section “The Server Configuration File” in the chapter “Setting up and Configuring the Server Environment” in the IBM Systems Management Application Programming manual.

    You are changing the value of the configuration file attribute named “DM_Exit” from its default value of “DMSSIXDM” to the value “VMXSIXDM” so that the VMXSIXDM routine supplied by CA VM:Secure will be used as the “Directory Manager Exit Routine”.