Installing the BMC CIM provider

Use the following procedure to install the BMC CIM provider.

  1. Create two BMC HFS Directories with read/write/execute (rwx) attributes for the owner and read/execute (r-x) attributes for other users or groups as follows:<path>/bmc/cpmcim/providers

    <path>/bmc/cpmcim/mof

    You can choose a <path> or use the default /bmc.

  2. Edit the BBSAMP member MMRCIMJF.

  3. Run the 'Copy CIM providers and MOF to customer's HFS file' option from the Product Customization for MainView for z/OS to install the following objects:BMC.so (Shared Object) provider dll files into USS file path:

    <path>/bmc/cpmcim/providers

    BMC.mof (Managed Object Format) files and make file into USS file path:

    <path>/bmc/cpmcim/mof
  4. Run the CIM Server Started Task.For more information about CIM Server, see the IBM manual z/OS MVS Capacity Provisioning User's Guide.

  5.  Run makefile to unregister IBM RMF CIM providers and register BMC CMF CIM providers.The name of the make file is makeBMCcust. The member is located at <path>/bmc/cpmcim/mof.

    Execute makefile as make -f makeBMCcust.

    Note

    • This step requires a USS command, and you must be at that file path <path>/bmc/cpmcim/mof.
    • To run Step 5, you must have CONTROL access to profile CIMSERV CL(WBEM).
    • The environment for the USS where make is run must be set up with the settings from /usr/lpp/wbem/install/profile.add.

    • The updates that are performed by makefile are contained in the CIM Servers repository that is located in /var/wbem/repository. If you are replacing the active repository /var/wbem/repository from the shipped master repository that is located in /usr/lpp/wbem/repository, the changes made by makefile are lost. Therefore, BMC recommends that you repeat Step 5 every time you replace a repository with a fresh copy.

      For more information, see the IBM Common Information Model User's Guide.

  6. Install and run the MainView host server Started Task.For more information about MainView host server, see Managing MainView Explorer and Starting and stopping the MainView host server.

  7. Edit the /etc/wbem/cimserver.env file.

    1. Update LIBPATH as follows:If you have IBM CIM Server installed, add the following text to the LIBPATH in the file:

      <path>/bmc/cpmcim/providers

      The final LIBPATH looks like this example:

      LIBPATH=/usr/lpp/wbem/lib:/usr/lpp/wbem/provider:/usr/lib:< path>/bmc/cpmcim/providers

    2. Set the RMF_CIM_HOST IP address to the same address as the MainView host server of step 6.For example:

      RMF_CIM_HOST=172.19.164.166

      or

      RMF_CIM_HOST=mvssjsd.bmc.com

    3. Set the RMF_CIM_PORT port number to the same port number as the MainView host server of step 6.For example:

      RMF_CIM_PORT=8813

      Note

      Make sure to add the /etc/wbem/cimserver.env file to the CIMSEVER Started Task STDENV DD step.

      For example:

      STDENV DD PATH='/etc/wbem/cimserver.env'
  8. Run the following USS command:cimconfig -s providerDir=lib:provider:< path >/bmc/cpmcim/providers -p
  9. Restart the CIM Server Started Task.

  10. Run the following USS command:cimprovider -l -s

    The BMC provider list is displayed.

    Note

    BMC assumes that with the installation of the latest release of the product, customers will have all necessary CIM-related views.

    One of the following PTFs is required for the VBAPI UTOKEN fix: BPY9005 or BPY9006.

Related topic

Capacity-Provisioning-Manager-CPM


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*