Control-M for OEBS Installation
The following procedures describe how to install Control-M for OEBS on Control-M/Agent on UNIX and Windows, 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 computers 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 Control-M/Agent on UNIX
This procedure describes how to install Control-M for OEBS on Control-M/Agent on UNIX.
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
-
Verify that all jobs running on the Control-M/Agent have ended.
-
Verify that you have met Java requirements, as described in Control-M External Java Installation.
Begin
-
Log in as the Control-M/Agent user.
-
Type the following command to stop the Control-M/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 Control-M/Agent throughout this procedure.
-
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.
-
-
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
-
-
Do one of the following:
-
Interactive Install: Continue with the on-screen instructions until the installation is complete.
-
Automatic Install: Do the following:
-
Continue with the on-screen instructions until the Summary window.
-
Click Generate and select the location to create the XML parameter file.
-
Click Yes.
-
Copy the automatic installation parameters file to a network location that is accessible to all computers where you want to perform an automatic installation.
-
Type 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>
-
-
-
The installation log is saved to the following location:
$HOME/BMCINSTALL/log/cmoebs/BMC_Control-M_For_OEBS_Install_<date-time>.log
-
Log out of the Control-M/Agent.
-
Log in and start the Control-M/Agent with the following command:
$CONTROLM/scripts/start-ag -u <agentUser> -p all
Installing Control-M for OEBS on Control-M/Agent on Windows
This procedure describes how to install Control-M for OEBS on Control-M/Agent on Windows.
Before You Begin
-
Verify that all jobs running on the Control-M/Agent have ended.
-
Verify that you have met Java requirements, as described in Control-M External Java Installation.
Begin
-
Log in as a user with Administrator privileges and stop the Control-M/Agent.
-
Do one of the following:
-
From the installation path, double-click the OAC.9.0.21.000_windows_x86_64.exe file.
-
Open the command prompt as Administrator and type the following command:
<install_source_path>\OAC.9.0.21.000_windows_x86_64.exe.
-
-
Do one of the following:
-
Interactive Install: Continue with the on-screen instructions until the installation is complete.
-
Automatic Install: Do the following:
-
Continue with the on-screen instructions until the Summary window.
-
Click Generate and select the location to create the XML parameter file.
-
Click Yes.
The automatic installation XML parameters file created (<filename>.xml) is relevant only for computers with the same Control-M/Agent instance name. A separate <filename>.xml file must be created or modified manually for each Control-M/Agent instance name.
-
Copy the automatic installation parameters file to a network location that is accessible to all Control-M/Agent computers where you want to perform an automatic installation.
-
Run the installation script, as follows:
<install_source_path>\OAC.9.0.21.000_windows_x86_64.exe -silent <silent.xml>
-
-
-
Restart the Control-M/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
-
Stop all jobs running on Control-M/Agent.
-
Verify that all jobs have ended.
Begin
-
From a Control-M/Agent computer, log in as a Control-M/Agent user, and type the following command to shut down Control-M/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 Control-M/Agent throughout this procedure.
-
Set your DISPLAY environment variable according to the computer name, as described in Setting Environment Variables in UNIX.
-
Navigate to the following directory:
$HOME/BMCINSTALL/uninstall/DROAC.<version>/
-
Type one of the following commands:
-
Interactive Uninstall: ./uninstall.sh
-
Automatic Uninstall: ./uninstall.sh -silent
-
-
To restart Control-M/Agent, type the following command:
$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
-
Stop all jobs running on Control-M/Agent.
-
Verify that all jobs have ended.
Begin
-
From the Start menu, select Control Panel.
-
Double-click Uninstall a program.
-
Select Control-M for OEBS
-
Click OK to continue.
The uninstallation log is saved to the following location:
BMCINSTALL\log\cmdb\BMC_ControlM_OEBS_Uninstall_<timestamp>.log
Peforming an Automatic Uninstall from Windows
This procedure describes how to perform an automatic uninstall of Control-M for OEBS from Windows.
Before You Begin
-
Stop all jobs running on Control-M/Agent.
-
Verify that all jobs have ended.
Begin
-
Log in to the computer using a user ID that has Administrator authorizations.
-
From a command line, run the following command using the full path:
<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:
-
Edit the external_java_path.dat file in the <HOME>/BMCINSTALL/ directory.
-
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.
-
-
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:
-
Edit the external_java_path.dat file in the <AGENT_HOME>\BMCINSTALL\ directory.
-
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.
-
-
-