Control-M for OEBS Installation

The following procedures describe how to install Control-M for OEBS on a UNIX or Windows Agent, interactively or automatically, in a Control-M/Server self-hosted environment.

If you want to install multiple instances of Control-M for OEBS on several hosts using the same configuration, use the automatic installation, as described in these procedures.

Control-M for OEBS is compatible with Control-M/Agent 9.0.21 or higher.

Installing Control-M for OEBS on a UNIX Agent

This procedure describes how to install Control-M for OEBS on a UNIX Agent.

The default installation is interactive and uses a GUI display. XServer must be running and configured using the DISPLAY environment variable. If you do not have XServer available, BMC recommends that you continue with the console installation or perform an automatic installation.

Before You Begin

Begin

  1. Log in to the account where Control-M/Agent is installed.

  2. Run the following command to stop the Agent:

    $CONTROLM/scripts/shut-ag -u <agentUser> -p all

    If the Control-M/Agent was installed with user root, then log in as user root every time you start up or shut down the Agent throughout this procedure.

  3. Use one of the following modes:

    • Display: If you install using GUI (or XServer), set your DISPLAY environment variable, as described in Setting Environment Variables in UNIX.

    • Console: It is not necessary to set DISPLAY.

  4. Type one of the following command to activate the installation script:

    • Linux: <install_source_path>/OAC.9.0.21.100_Linux-x86_64.BIN

    • AIX: <install_source_path>/OAC.9.0.21.100_AIX.BIN

  5. Do one of the following:

    • Interactive Installation: Continue with the on-screen instructions until the installation is complete.

    • Automatic Installation: Do the following:

      1. Continue with the on-screen instructions until the Summary window.

      2. Click Generate and select the location to create the XML parameter file.

      3. Click Yes.

      4. Copy the automatic installation parameters file to a network location that is accessible to all hosts where you want to perform an automatic installation.

      5. Run the following command to activate the installation script:

        <install_source_path>/<OAC.9.0.21.100_AIX.BIN|OAC.9.0.21.100_Linux-x86_64.BIN> -silent<filename.xml>

  6. The installation log is saved to the following location:

    $HOME/BMCINSTALL/log/cmoebs/BMC_Control-M_For_OEBS_Install_<date-time>.log

  7. Log out of the Agent.

  8. Log in and run the following command to start up the Agent :

    $CONTROLM/scripts/start-ag -u <agentUser> -p all

Installing Control-M for OEBS on a Windows Agent

This procedure describes how to install Control-M for OEBS on a Windows Agent.

Before You Begin

Begin

  1. Log in as an administrator to the account where Control-M/Agent is installed and stop the Agent.

  2. Do one of the following:

    • From the installation path, double-click the OAC.9.0.21.000_windows_x86_64.exe file.

    • From an Administrator-privileged command line run the following command:

      <install_source_path>\OAC.9.0.21.000_windows_x86_64.exe.

  3. Do one of the following:

    • Interactive Installation: Continue with the on-screen instructions until the installation is complete.

    • Automatic Installation: Do the following:

      1. Continue with the on-screen instructions until the Summary window.

      2. Click Generate and select the location to create the XML parameter file.

      3. Click Yes.

        The automatic installation XML parameters file created (<filename>.xml) is relevant only for hosts with the same Agent instance name. A separate <filename>.xml file must be created or modified manually for each Agent instance name.

      4. Copy the automatic installation parameters file to a network location that is accessible to all Agent hosts where you want to perform an automatic installation.

      5. Run the installation script, as follows:

        <install_source_path>\OAC.9.0.21.000_windows_x86_64.exe -silent <silent.xml>

  4. Restart the Agent.

The installation log is available at the following location:

<Control-M Agent instance directory>\BMCINSTALL\log\cmoebs\BMC_Control-M_For_OEBS_Install_<date-time>.log

If the installation fails, the log file is saved to the following location:

%temp%\BMC_Control-M_For_OEBS_Install_<date-time>.log

Uninstalling Control-M for OEBS from UNIX

This procedure describes how to uninstall Control-M for OEBS from UNIX.

Before You Begin

  • Verify that no jobs are executing on the Agent.

Begin

  1. From an Agent host, log in to the account where Control-M/Agent is installed, and run the following command to shut down the Agent:

    $CONTROLM/scripts/shut-ag -u <agentUser> -p all

    If Control-M/Agent was installed with user root, then log in as user root every time you start up or shut down the Agent throughout this procedure.

  2. Set your DISPLAY environment variable according to the hostname, as described in Setting Environment Variables in UNIX.

  3. Navigate to the following directory:

    $HOME/BMCINSTALL/uninstall/DROAC.<version>/

  4. Do one of the following:

    • Interactively Uninstall: Run the following command:

      ./uninstall.sh

    • Automatically Uninstall: Run the following command:

      ./uninstall.sh -silent

  5. Run the following command to restart the Agent:

    $CONTROLM/scripts/start-ag -u <agentUser> -p all

The uninstallation logs is saved to the following location:

$HOME/BMCINSTALL/log/cmdb/BMC_ControlM_OEBS_Uninstall_<timestamp>.log

Uninstalling Control-M for OEBS from Windows

This procedure describes how to uninstall Control-M for OEBS from Windows.

Before You Begin

  • Verify that no jobs are executing on the Agent.

Begin

  1. From the Start menu, select Control Panel.

  2. Double-click Uninstall a program.

  3. Select Control-M for OEBS

  4. Click OK to continue.

The uninstallation log is saved to the following location:

BMCINSTALL\log\cmdb\BMC_ControlM_OEBS_Uninstall_<timestamp>.log

Performing an Automatic Uninstall from Windows

This procedure describes how to perform an automatic uninstall of Control-M for OEBS from Windows.

Before You Begin

  • Verify that no jobs are executing on the Agent.

Begin

  1. Log in to the host using a user ID that has Administrator authorizations.

  2. Run the following command:

    <Agent Install Path>\BMCINSTALL\uninstall\DROAC.<version>\uninstall.exe -silent

The uninstallation log is saved to the following location:

$HOME/BMCINSTALL/log/cmoebs/BMC_Control-M_For_OEBS_Uninstall_<date-time>.log

Changing the JRE Package in Control-M for OEBS

This procedure describes how to change the JRE package in Control-M for OEBS. The use of JRE is supported only where the major release version is the same as the tested version. For more information about Java, see Control-M External Java Installation.

Begin

  • Do one of the following:

    • UNIX: Do the following:

      1. Edit the external_java_path.dat file in the <HOME>/BMCINSTALL/ directory.

      2. Define an alternative Java home directory by modifying the value of the parameter CM_OEBS_JAVA_HOME to the external Java path.

        CM_OEBS_JAVA_HOME={new JRE Path}

        • A relative path is not supported.

        • The path can only include alphanumeric, period, underscore, hyphen and plus characters.

      3. Stop Control-M for OEBS using the following command.

        $CONTROLM/cm/OEBS/exe/sapcmbe.sh stop

        Control-M for OEBS restarts automatically.

    • Windows: Do the following:

      1. Edit the external_java_path.dat file in the <AGENT_HOME>\BMCINSTALL\ directory.

      2. Define an alternative Java home directory by modifying the value of the parameter CM_OEBS_JAVA_HOME to the external Java path.

        CM_OEBS_JAVA_HOME={new JRE Path}

        • The path must be enclosed with quotation marks.

        • A network path is not supported.

        • A relative path is not supported.

        • The path can only include alphanumeric, space, period, underscore, hyphen and plus characters.