HCL Workload Automation, Version 9.4

Registering the master domain manager on SAP Solution Manager

The first step to run the integration is to register the master domain manager on the SAP Solution Manager system.

To register master domain manager on the SAP Solution Manager system, you must:

Have established a connection based on RFC or Web Services between the master and the Solution Manager system.
Have the SAP JCo 3.0.2 libraries (dll and jar files) installed in the TWS_home/methods/smseadapter/lib directory on the master. To download JCo 3.0.2, visit the Sap Service Marketplace.
Attention: The libraries require the Microsoft Visual C++ Redistributable Package (vcredist) installed.
Configure the smseadapter.properties file located in the TWS_home/methods/smseadapter/lib directory on the master.
The file contains a SMSE_ADAPTER_CONNECTION_n section that can be duplicated depending on the number of connections that you want to define. You can in fact set more connection definitions for the same master, where, for example, the following can vary:
- The SAP Solution Manager system.
- The agent that is to run the workload.
- The SAP user name.
Note, however, that a master domain manager can have only one active connection at a time via the smseadpter. If the adapter finds more that one section with the startAdapter property set to true (or not set to false), it uses the first section of properties and ignores the others.

[SMSE_ADAPTER_CONNECTION_1]
startAdapter = 
ashost =  
sysnr = 
client = 
sid = 
user =  
passwd = 
lang = 
destination = 
setDestinationAsDefault =
jobStreamNamePrefix =
agentName =
notificationThreadCheckInterval =
adminConsoleHost = 
adminConsolePort = 	
adminConsoleUser = 
adminConsoleUserPassword =

This section can be repeated as many times as needed in the smseadapter.properties file.

The properties are:

Table 1. Properties for the `smseadapter.properties` file.
Property	Description	Required	Notes
SMSE_ADAPTER_CONNECTION_1	This is the section header. If you have more sections the last digit should differ from one section and another. If two sections contain identical property values, only the first section read is considered, the other is ignored.	✓
startAdapter	Specifies whether to connect or not to SAP Solution Manager. Can be true or false. Must be set to true to make the connection work. Set to false to temporarily suspend the connection.	✓	The default is true.
ashost	The host name of the SAP Solution Manager server on which the master domain manager registers. For example, /H/7.142.153.8/H/7.142.154.114.	✓	The master domain manager can connect to one Solution Manager system at a time.
sysnr	The SAP system number of the system that the master registers on. This value must have two digits. For example, 00.	✓
client	The SAP client number. For example, 001.	✓
sid	The SAP system identifier (SID) that the master registers on. For example, SM1.	✓
user	The SAP user name that will be used during the notification process to log into SAP Solution Manager. For example, twsadmin.	✓
passwd	The SAP password that will be used during the notification process to log into SAP Solution Manager. You can enter it in clear or in encrypted forms.	✓	To encrypt the password use the `enigma` program located in the `methods` folder on the master.
lang	The SAP logon language. For example, EN.	✓
destination	A name entered here to identify the RFC Destination that will be used to connect to SAP Solution Manager. For example, IWSM2.	✓	This name defines the logical connection between the Solution Manager system and the master domain manager, referred to in Solution Manager as the `external scheduler`. The complete destination name will then be formed by: `destination@mdm_name` For example: IWSM2@MAS93WIN
setDestinationAsDefault	Set to `true` to make this destination the default one. The default is `false`.		Use this property in a context where a Solution Manager system has more than one active destination defined (that is, more registered masters), to set the default external scheduler. If you do not set a default, and you have more external schedulers registered on an SM system, you will have to specify the destination at scheduling time.
jobStreamNamePrefix	A prefix of at least four letters that is to be added to the names of the job streams created when jobs are submitted. The first character must be a letter while the remaining characters can be alphanumeric.		The default prefix is SOLMAN.
agentName	The name of the IWS agent that will run the jobs. When you search for the job definition in the Scheduling dialog, the Search utility returns the names of the jobs defined to run on this agent.		If no agent name is specified, the Search utility returns the names of the jobs defined to run on all the agents attached to the master domain manager (unless you use filtering).
notificationThreadCheckInterval	The time interval, in seconds, between checks made by the notification thread on the status changes of a job. The default is 5 seconds.		The thread notifies Solution Manager with the status changes of a job.
adminConsoleURL	The protocol used (http or https) and the host name and port of the Dynamic Workload Console attached to the master. For example, `https://mydwc:port_number/abc/console`.		The next four properties, all related to the Dynamic Workload Console, are optional, but if you specify one, you must specify all.
adminConsoleUser	The username that logs onto the Dynamic Workload Console attached to the master.
adminConsoleUserPassword	The password of the username that logs onto the Dynamic Workload Console attached to the master.

Note that if the language configured for the master domain manager is different from the language configured for the Solution Manager system, the messages issued in the Solution Manager user interface may be displayed in mixed languages.