Control-M for SAP Post-installation
After Control-M for SAP installation, described in Plug-ins, there are a number of post-installation actions you must perform:
-
Start Control-M/Agent services if they were stopped by the installation process when it started.
-
After upgrading, start the SAP CM extractor process if stopped by the installation, as described in Starting and Stopping the Extractor Process.
-
Download the sapjco3.jar and sapjco3 C library files, as described in Downloading the sapjco3.jar and sapjco3 C Library Files.
-
(Optional) Configure Control-M for SAP to work with Secure Network Communications (SNC), as described in Installing the SNC on Control-M for SAP. Use these procedures only if you are using SNC.
-
(Optional) Install the Control-M Option for R/3 jobs conversion utility, which converts Control-M Option for R/3 jobs to Control-M for SAP jobs, as described in Installing Control-M Option for R3 Jobs Conversion Utility.
-
Comply with the SAP authorizations, as described in SAP Authorizations.
-
Create a centralized connection profile, as described in Creating a Centralized Connection Profile.
-
Configure SAP XBP functionality, as described in Control-M for SAP Post-installation.
-
Prepare the authorization transport, as described in Control-M for SAP Post-installation.
Downloading the sapjco3.jar and sapjco3 C Library Files
This procedure describes how to download the required SAP Java Connector files.
Begin
-
Go to http://service.sap.com/connectors, and, using your SAP account details, download the sapjco3.jar and sapjco3 C library files that match your operating system.
-
Copy the sapjco3.jar and sapjco3 C library files to the following path:
-
Linux: $CONTROLM/cm/SAP/exe/sapjco
-
Windows: <Agent_home>\cm\SAP\exe\sapjco
-
-
(Windows only) Obtain and install the Visual Studio .NET C/C++ runtime libraries required by JCo.
For more information about how to obtain and install the Visual Studio runtime libraries, see the Support and Release Strategy section in the SAP Java Connector Download Page.
Installing the SNC on Control-M for SAP
This procedure describes how to install the SNC (Secure Network Communications) protocol on Control-M for SAP, which enables the encryption of data between Control-M for SAP and the SAP system.
Begin
-
Follow the download and installation procedures, as described in the Knowledge Base solution 000111305 on the Customer Support website, located at http://www.bmc.com/support.
-
After the SNC set up is complete, stop Control-M/Agent.
-
Stop Control-M for SAP by typing one of the following commands:
-
Windows: sapcmbe.cmd stop
-
Linux: sapcmbe.sh stop
-
-
(Linux only) Start Control-M for SAP, using the following command:
sapcmbe.sh start &
-
Start the Control-M/Agent.
Maintaining the Control-M for SAP Process
This procedure describes how to start, stop, and view the status of Control-M for SAP process.
Begin
-
Use the following directories:
-
UNIX: $CONTROLM/cm/SAP/exe
-
Windows: <Agent_home>\cm\SAP\exe
-
-
Type the following:
-
Linux: sapcmbe.sh {start|stop|status|change_port|refresh|jco}
-
Windows: sapcmbe.cmd {start|stop|status|change_port|refresh|jco}
-
-
Do one of the following:
-
start: Starts the Control-M for SAP process
-
stop: Stops the Control-M for SAP process
If the Control-M for SAP process was stopped and a new request for the Control-M for SAP process arrives, it starts automatically, as follows:
-
status: Indicates whether the Control-M for SAP process and the Extractor process are running or not.
-
change_port: Updates the TCP/IP port used by the Control-M for SAP
-
refresh: Refreshes the data collected from the XAL interface that is used for load balancing. If you do not run this command, the data is refreshed automatically on a daily basis.
-
jco: Prints the version of the SAP JCo JAR file and the version of the C library file. If one of these files is not installed correctly, an error message appears.
-
Installing Control-M Option for R3 Jobs Conversion Utility
(Windows only) This procedure describes how to install the Control-M Option for R3 jobs conversion utility, which converts Control-M Option for R3 jobs to Control-M for SAP jobs.
Begin
-
Log in to the Control-M/EM.
-
Extract the sap_cm_conv_ut.zip file from the <DVDROM_path>\Tools\conversion folder to a temporary folder on the computer.
SAP Authorizations
The following table describes the authorizations that are necessary for SAP users defined in a connection profile.
Authorization Object |
Authorization |
Values |
---|---|---|
S_BTCH_JOB Object class: BC_A (Basis: Administration) |
JOBACTION |
* |
JOBGROUP |
* |
|
S_BTCH_ADM Object class: BC_A (Basis: Administration) |
BTCADMIN |
* |
S_BTCH_NAM Object class: BC_A (Basis: Administration) |
BTCUNAME |
|
S_RFC Object class: AAAB (Cross-application) |
ACTVT |
* |
RFC_NAME |
* |
|
RFC_TYPE |
* |
|
S_XMI_PROD Object class: BC_A (Basis: Administration)
|
EXTCOMPANY |
BMC Software |
EXTPRODUCT |
Control-M |
|
INTERFACE |
XBP |
|
S_RZL_ADM \Object class: BC_A (Basis: Administration) |
ACTVT To prevent other SAP users (not the Control-M account user) from releasing Intercepted Jobs manually using SAP transaction SM37, BMC Software recommends removing the 01 value for ACTVT in the S_RZL_ADM Authorization Object. |
* |
S_LOG_COM Object class: BC_A (Basis: Administration)
|
COMMAND |
* |
HOST |
* |
|
OPSYSTEM |
* |
|
S_SPO_DEV Object class: BC_A (Basis: Administration) |
SPODEVICE |
* |
S_USER_GRP Object class: BC_A (Basis: Administration)
|
ACTVT |
03, 16, 23, 66 |
RSADMWBOBJ |
* |
|
S_RS_ISOUR Object class: RS (Business Information Warehouse)
|
ACTVT |
03, 23, 49 |
RSAPPLNM |
* |
|
RSISOURCE |
* |
|
RSTSRCOBJ |
* |
|
S_RS_ISRCM Object class: RS (Business Information Warehouse)
|
ACTVT |
23 |
RSAPPLNM |
* |
|
RSTSRCOBJ |
* |
|
RSOSOURCE |
* |
|
S_RS_PC - (Data Warehousing Workbench - Process chains) Object class: RS (Business Information Warehouse)
|
RSPCCHAIN |
* |
RSAPPLNM |
* |
|
RSPCPART |
* |
|
ACTVT |
03, 16, 23 |
|
S_RS_DS
|
Activity |
23, 49 |
DataSource |
* |
|
Sub object for New DataSource |
* |
|
Source System |
* |
|
All BW authorizations under the RS Object Class are required only if you work with Control-M for SAP solution for BW. |
||
S_ARCHIVE Object class: BC_A (Basis: Administration)
|
ACTVT |
* |
APPLIC |
* |
|
ARCH_OBJ |
* |
|
S_DATASET
|
ACTVT |
* |
FILENAME |
* |
|
PROGRAM |
* |
|
The S_ARCHIVE and S_DATASET authorizations are required only if you use Control-M for SAP solution for Data Archiving. |
Changing the JRE Package in Control-M for SAP
This procedure describes how to change the JRE package in Control-M for SAP. The use of JRE is supported only where the major release version is the same as the tested version. For a list of support JRE versions, see Control-M Compatibility with External Java Vendors.
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_SAP_JAVA_HOME to the external Java path.
CM_SAP_JAVA_HOME={new JRE Path}
-
A relative path is not supported.
-
The path can only include alphanumeric, dot, underscore, hyphen and plus characters.
-
-
Stop Control-M for SAP using the following command.
$CONTROLM/cm/SAP/exe/sapcmbe.sh stop
Control-M for SAP 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_SAP_JAVA_HOME to the external Java path.
CM_SAP_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, dot, underscore, hyphen and plus characters.
-
-
Stop Control-M for SAP using the following command.
<AGENT_HOME>\cm\SAP\exe\sapcmbe stop
Control-M for SAP restarts automatically.
-
-