HCL Workload Automation, Version 9.4

Determining the role of the user whose password has changed

About this task

Use the following procedure to determine which role or roles the user whose password has changed is playing.

Attention: A user might have more than one role, in which case you must follow more than one procedure to change the password.
1. Check if the user is the HCL Workload Automation instance owner:
Windows
Check if the user whose password is to be changed is the user that owns the HCL Workload Automation for <TWS_user> service.
UNIX
Run the following command: 
ps -ef | grep netman
If the user whose password has changed matches the user ID revealed in this step, then the user is the HCL Workload Automation instance owner.
2. Check if the user is the WebSphere Application Server user or the database user, or both:
  1. Log on to the computer where HCL Workload Automation is installed as the following user:
    UNIX
    root
    Windows
    Any user in the Administrators group.
  2. Access the directory: <TWA_home>/wastools
  3. From that same directory run the following script:
    UNIX
    showSecurityProperties.sh > <output_file.txt>
    Windows
    showSecurityProperties.bat > <output_file.txt>
    Note: This command might display a message from the application server (WASX7357I:) in the output file. You can ignore this message.
  4. Open <output_file.txt> in a text editor.
  5. Run the showSecurityProperties script to check the ServerID associated with the value of the activeUserRegistry key. If the user whose password has changed is the same as the value of the ServerID listed in the Federated Repository Panel, then the user is the WebSphere Application Server user.
  6. Check the value of the key j2cUserid . If the user whose password is to be changed matches this key, the user is the database user.
    Note: If the user is the Oracle schema owner, the password must also be changed within Oracle (see the Oracle documentation).
3. Check if the user is a streamlogon user
Using composer or the Dynamic Workload Console, check if the user is identified as a user. If so, the user is a streamlogon user.

When you have determined which roles the user plays, see Table 1 to determine if and where the password change must be implemented, and then Determining the actions to take.


Scenario: Creating a job definition using a logical resource group
HCL Workload Automation, Version 9.4

Scenario: Creating a job definition using a logical resource group

In this scenario, the target for the job is determined by several requirements defined as logical resources. A resource group has been created to include all the logical resources required for the job.

About this task

To create a job definition that does this, perform the following steps:

Procedure

  1. In the Job Brokering Definition Console selectFile > New > Job brokering definition and create a new job definition named loggroupjob. The job definition opens at the Overview page with the job name assigned.
  2. Open the Application page and define the required information for the application that the job is to run.
  3. Open the Related Resources page and create a requirement for a logical resource, as follows:
    1. In the Resource Requirements pane, click Add. The Resource Requirement Details dialog box is displayed.
    2. In the ID field, specify a meaningful ID, in this example, loggroup.
  4. Open the Resources page and create a relationship to the resource requirement, as follows:
    1. Select the Advanced Requirements tab.
    2. In the Relationships pane, click Add. The Relationship Details dialog box is displayed.
    3. In the Type menu, select Associates with.
    4. In the Target menu, select the resource requirement that you created and click OK.
  5. Switch back to the Related Resources page and add the logical resource group as follows:
    1. In the Resource Group pane, click Add. The Resource Group Details dialog box is displayed.
    2. In the Group Name field, type the resource group name, as defined in the Dynamic Workload Console.
  6. Select File > Save to save the job definition file.

Results

The JSDL file created for this scenario has the following syntax:
<jsdl:jobDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:jsdl="http://www.abc.com/xmlns/prod/scheduling/1.0/jsdl" 
xsi:schemaLocation="http://www.abc.com/xmlns/prod/scheduling/1.0/jsdl JSDL.xsd" 
description="A job whose requirements are defined by a number of logical 
resources. " name="loggroupjob">
  <jsdl:application name="executable">
    <jsdle:executable path="/opt/myExecutable">
    </jsdle:executable>
  </jsdl:application>
  <jsdl:resources>
    <jsdl:relationship target="loggroup" type="AssociatesWith"/>
  </jsdl:resources>
  <jsdl:relatedResources id="loggroup" type="LogicalResource">
    <jsdl:group name="logresgroup"/>
  </jsdl:relatedResources>
</jsdl:jobDefinition>