85DSR2008 Lab G1

CA Workload Automation DE r11.3:
Foundations 200
Lab Guide
85DSR2008S
85DSR2008LG1

Lab Guide

‐ PROPRIETARY AND CONFIDENTIAL INFORMATION ‐

© 2016 CA. All rights reserved. CA confidential & proprietary information. For CA, CA Partner and CA
Customer use only. No unauthorized use, copying or distribution. All names of individuals or of
companies referenced herein are fictitious names used for instructional purposes only. Any similarity to
any real persons or businesses is purely coincidental. All trademarks, trade names, service marks and
logos referenced herein belong to their respective companies. These Materials are for your
informational purposes only, and do not form any type of warranty. The use of any software or product
referenced in the Materials is governed by the end user’s applicable license agreement. CA is the
manufacturer of these Materials. Provided with “Restricted Rights.”

CA Technologies CA Workload Automation DE r11.3: Foundations 200 ii

© 2016 CA. All rights reserved.

Lab Guide

Table of Contents
Lab 2‐1 Install the Desktop Client ......................................................................................................... 1
Lab 2‐2 Manage Connections for Different Roles and Privileges ........................................................... 9
Lab 2‐3 Navigate Perspectives and Views ........................................................................................... 16
Lab 3‐1 Change the Role of Servers .................................................................................................... 46
Lab 3‐2 Add a User and Grant Agent and Report Permissions ............................................................. 73
Lab 3‐3 Run CLI Commands ................................................................................................................ 82
Lab 4‐1 Create an Application ............................................................................................................ 93
Lab 5‐1 Simulate a CA Workload Automation DE Event .................................................................... 168
Lab 5‐2 Create a CA Workload Automation DE Event ........................................................................ 175
Lab 6‐1 Monitor and Control Active Workload ................................................................................. 188
Lab 6‐2 Manage the Dashboard ........................................................................................................ 241
Lab 7‐1 Add an Agent ....................................................................................................................... 260
Lab 7‐2 Add the DB Plug‐in ............................................................................................................... 271
Lab 7‐3 Run an SQL Job with the DB Plug‐in ..................................................................................... 308
Lab 7‐4 Add an Agent Group ............................................................................................................ 327
Lab 8‐1 Define a Calendar ................................................................................................................ 331
Lab 8‐2 Define a Special Day ............................................................................................................ 339
Lab 9‐1 Define a Variable ................................................................................................................. 367
Lab 9‐2 Define CA Workload Automation DE Resources ................................................................... 373
Lab 10‐1 Define a JavaScript ............................................................................................................. 379
Lab 11‐1 Define Notifications ........................................................................................................... 397
Lab 11‐2 Add an Alert to an Application ........................................................................................... 417
Lab 11‐3 Create a JavaScript Alert .................................................................................................... 426
Lab 11‐4 Generate Forecast Reports ................................................................................................. 459
CA Technologies CA Workload Automation DE r11.3: Foundations 200 i

Lab Guide

Lab 2‐1 Install the Desktop Client
In this lab, you will install the Desktop Client.

Step Action
1. The CA Workload Automation DE Desktop Client is a graphical interface for defining,
monitoring, and controlling enterprise workload. The interface enables you to drag and
drop workload definitions, manage calendars, and monitor and control batch workload,
regardless of the operating system.

The Desktop Client also includes tools for administrators to set up, monitor, and diagnose
problems with CA Workload Automation DE.

The installation file you require has been placed in a folder on the desktop for you.

Double‐click the CAWA‐Client list item.
CA Technologies CA Workload Automation DE r11.3: Foundations 200 1

Lab Guide

Step Action
2. In this scenario, you will install the Windows 64‐bit version for CA Workload Automation
DE r11.3.

The folder containing the required file is located in the InstallMedia folder.

Double‐click the SYSTEM (C:) list item.

Lab Guide

Step Action
3. Double‐click the InstallMedia list item.

4. Double‐click the
CA_Workload_Automation_DE_Desktop_Client_R11_3_SP3_for_Windows list item.

Lab Guide

Step Action
5. To start the installation, you double‐click the Setup.exe file.

Double‐click the Setup.exe list item.

Lab Guide

Step Action
6. Click the Run button.

Lab Guide

Step Action
7. You will close the open folder while the installation starts.

Click the Close button.

Step Action
8. The installation process has started.

The first part of the process is to read through and agree to the EULA.

To advance through the EULA, you scroll down.

Click the scrollbar.
9. For the installation to continue, you must agree to the terms and conditions detailed in
the EULA.

Click the I accept the terms of the License Agreement option.


Lab Guide

Step Action
10. This panel enables you to select the folder in which the installation files are written.

For this scenario, you will accept the default location.

Click the Next button.

11. This panel enables you to select where the Desktop Client shortcuts will appear.

For this scenario, you will accept the default shortcut locations.

Click the Next button.

12. Click the scrollbar.

13. The Pre‐Installation Summary panel appears displaying the information you entered.
Verify the entries and if you need to make changes, to return to the appropriate panel,
click Previous.

In this scenario, the correct information was entered; you will now install the Desktop
Client.

Click the Install button.

14. The Desktop Client has been installed.

Click the Done button.

Lab Guide

Step Action
15. A launch icon now appears on the desktop.

Press [Enter].
16. In this lab, you installed the Desktop Client.
End of Procedure.


Lab Guide

Lab 2‐2 Manage Connections for Different Roles and Privileges
In this lab, you will manage connections for different roles and privileges.

Step Action
1. To perform tasks with CA Workload Automation DE, you will start the Desktop Client.

Double‐click the CA Workload Automation Desktop Client R11.3 SP3 list item.

2. When you start the Desktop Client for the first time, the New Connection dialog appears.

This dialog enables you to create a connection to a specific server with distinct rights.

You begin by defining the new connection name.

Enter the desired information into the Connection name: field. Enter "default".

Lab Guide

Step Action
3. After you begin creating a new connection, a red X appears on all mandatory fields and a
short message stating the required value for the selected field appears at the top of the
dialog.

Next, you must enter the IP address or DNS name of the server.

For this scenario, the DNS name is CAWA‐Server.

Enter the desired information into the IP address: field. Enter "CAWA‐Server".

4. You must now enter the port number.

For this scenario, the port number is 7500.

Enter the desired information into the Port number: field. Enter "7500".

5. By default, two user IDs are available out of the box, ADMIN and SCHEDMASTER.

Each user ID has distinct roles and privileges:
‐ The ADMIN user ID manages administrative, security and topology information. This role
cannot create workloads.
‐ The SCHEDMASTER user ID schedules, controls, and monitors workload. This role cannot
perform administration functions.

It is recommended that you change the default passwords for these default user IDs.

When required, you can create other user IDs.

For this scenario, you will associate the ADMIN user ID to this connection.

Enter the desired information into the User name: field. Enter "ADMIN".

6. Enter the desired information into the Password: field. Enter "admin".

7. When in a high‐availability or failover system, selecting the Prevent auto‐connect on
failover option will stop the connection from being automatically made with the other
server.

Click the Save and Connect button.


Lab Guide

Step Action
8. Click the Close button.

9. After clicking Save and Connect, the Application Workspace view appears displaying the
new connection.

After connecting to the environment, the server tree item font turns green, indicating that
the Desktop Client is connected.

The connections you create enable you to monitor and control many different servers.
Each connection will be visible on the Connections view.

Click the Connections button.

Step Action
10. The options on the Connections view enable you to manage current connections.

When required, you can create connections by using the Create Connection button on the
Connections view, or by using the Connections menu.

Click the Connections menu.



Lab Guide

Step Action
11. Use the New Connection list item to create new connections.

After you are finished using a connection, you can disconnect from the server.

Right‐click the default (CAWA‐Server:7500) [primary] tree item.

12. Click the Disconnect list item.

Step Action
13. Click the Yes button.



Lab Guide

Step Action
14. You can also connect using the same menu.

Notice that after you disconnected from the server, the status now states disconnected
and the font is red.

Right‐click the default (CAWA‐Server:7500) [disconnected] tree item.

15. When a connection is no longer required, you can delete it.

You will reconnect to the server.

Click the Connect... list item.



Lab Guide

Step Action
16. Instead of connecting with the same user ID, you can change it in the Connect to Server
dialog.

By default, the previous user ID appears, which in this scenario is ADMIN.

You can change the user ID to a different one.

Enter the desired information into the User name: field. Enter "SCHEDMASTER".

17. Enter the desired information into the Password: field. Enter "schedmaster".

18. Click the OK button.

19. Because you changed the user ID to SCHEDMASTER, you can now perform different tasks.
You can define, control, and monitor workload.




Lab Guide

Step Action
21. In this lab, you managed connections for different roles and privileges.
End of Procedure.



Lab Guide

Lab 2‐3 Navigate Perspectives and Views
In this lab, you will navigate perspectives and views.

Step Action
1. You will start the Desktop Client.


2. The Connect to Server dialog appears displaying the connection information for the last
logged‐in user.

In this scenario, you will use the displayed connection information, logging in with
SCHEDMASTER rights.

Enter the desired information into the Password: field. Enter "schedmaster".

3. Click the Connect button.


Lab Guide

Step Action
4. After installing the Desktop Client, the Welcome view appears each time you log in.

To prevent the Welcome view from appearing, you can select the Don't show Welcome
View at Startup option.

Click the Don't show Welcome View at Startup option.

5. When you next log in, the Welcome view will not appear.


6. By default, the Application Workspace view appears, displaying the active server
connection.

The Console view enables you to view server messages.

Click the Console button.

7. The Console view appears at the bottom of the right pane.

Viewing server messages in the Console view can help you determine solutions for errors
that might occur.

Press [Enter].


Lab Guide

Step Action
8. Perspectives are visual containers for a set of views or editors. Perspectives control what
appears on certain menus and toolbars.

By default, there are six perspectives available with this connection:
‐ Define
‐ Monitor
‐ Services
‐ CLI
‐ Admin
‐ Report

The Define perspective enables you to manage workload. You can create a new workload
object and open or download existing workload objects.

Using the Define perspective, you will create a workload object called an application.

To create the new workload object, you can click New.

Click the New button.

9. The Application properties dialog appears in which you define the new application.

Mandatory fields have an asterisk at the beginning of the field name. There is only one
mandatory field in this dialog, the Name field.

When determining an application name, it is a good practice to select a name that can
help you identify the type of jobs that the application will consist of.

Because this application is only being created to navigate in the Define perspective and it
will not be saved, you will name the application A.

Enter the desired information into the *Name: field. Enter "A".

10. Because there are no other mandatory fields, you will create the application.

Click the OK button.

11. Notice in the Application Workspace view that you can see the addition of the new
application in the tree under the current connection.

Press [Enter].


Lab Guide

Step Action
12. In the lower section of the left pane, the Application Events view enables you to view
events.

Events cause applications to be scheduled or run.

Events will be discussed further in a later module.

Press [Enter].
13. To create more room to display the view in the right pane, you will minimize the Console
view.

Click the Minimize button.



Lab Guide

Step Action
14. The Application Workspace occupies the right pane.

This view enables you to select the type of objects you require when building an
application.

Objects are selected from the right panel named the Palette and placed on the Application
Workspace.

You can click anywhere in the Application Workspace to place the objects.

By default, the UNIX job is selected.

Click the Application Workspace whitespace.

Step Action
15. To add a different object, you select it from the right panel.

Click the i5/OS list item.


Lab Guide

Step Action
16. Click the Application Workspace whitespace.


Lab Guide

Step Action
17. Click the Tandem NSK list item.


Lab Guide

Step Action


Lab Guide

Step Action
19. Some objects are contained further down in the list.

Click the separator.

20. Click the Windows list item.


Lab Guide

Step Action


Lab Guide

Step Action
22. To open other areas from which to select objects, you can click the area name.

Click the Monitoring list item.

23. Click the File Trigger list item.

Step Action


Lab Guide

Step Action
25. After you define the application, you must save it.

You can save the application to your desktop or another location, for example, a network
drive.

Press [Enter].
26. After you save the application, you must upload it to the database.

If you do not upload the application to the database, any change or modification you
made to the application will not take effect.

Press [Enter].
27. In this scenario, the application will not be saved.


28. Click the No button.


Lab Guide

Step Action
29. Next, you will navigate the Monitor perspective.

Click the Monitor button.

30. To see more views in the left pane, you will resize the pane.

Press the left mouse button on the object.
31. Release the mouse button.


Lab Guide

Step Action
32. In the left pane, the Monitor perspective is defined with three views: Application Monitor,
Custom Views, and Dashboard Views.

The Monitor perspective enables you to look at objects at the application level.

Currently, no information appears because you first need to select the server from which
you will source the information to monitor.

You will now select a server from the tree.

Right‐click the default (CAWA‐Server:7500) [connected] tree item.

33. The menu options that appear after you right‐click a server link enable you to select how
to load information from the server.

You need to select a subscription method to load data.

Subscription methods will be discussed in a later module.

After you select a subscription, data will be visible in the right pane at the application level
or a flowchart version.

Click the Custom Views tab.


Lab Guide

Step Action
34. The Custom Views view displays predefined views to display specific information.

You select the required view from the list to see only information that is specific to the
view name.

The information that appears is the same information that appears on the Application
Monitor view but is displayed in rows and columns where each row is the individual job
and each column is an attribute for the job.

These views can be customized to show information that is specific to your needs.
Customization of these views will be discussed in a later module.

Click the Dashboard View tab.

35. The Dashboard View view displays a dashboard view of the entire system.

Message information is available under Status Message Views, and system information is
available under System Monitor Views.

These views can also be customized.

Click the Services button.


Lab Guide

Step Action
36. The Services perspective enables you to add, modify, create, delete, or control the objects
that appear in the list providing you have the appropriate rights.

To monitor an object from the list, you double‐click the object name.

Double‐click the Events tree item.



Lab Guide

Step Action
37. The Events view appears in the right pane.

You can use the Filter area to populate the view.

The Event prefix and Event name fields permit the use of the asterisk wildcard character to
help search.

Enter the desired information into the Event prefix: field. Enter "*".

38. Click the Arrow button.

39. Currently, only one event satisfies the search criteria.

Click the CLI button.


Lab Guide

Step Action
40. The CLI perspective enables you to issue commands against CA Workload Automation DE.

After clicking CLI, you must select a server from the CLI view before you can issue
commands.

Double‐click the default (CAWA‐Server:7500) [connected] tree item.


Lab Guide

Step Action
41. After you select the required connection, the CLI view appears in the right pane.

To view all the available commands, you can enter help.

Enter the desired information into the Command field. Enter "help".


Lab Guide

Step Action
42. Press [Enter].


Lab Guide

Step Action
43. A list of all commands appears in the view.

To view more commands, you will scroll up.

44. To view the remaining available commands, you will scroll up.

45. It is important to note that some of the CLI commands can only be successfully executed
with the properly assigned security permissions.

Click the Admin button.


Lab Guide

Step Action
46. The Admin perspective enables you to administer security for users and groups and
maintain a topology of servers and agents.

Double‐click the Security tree item.

Step Action
47. The Security view did not appear.

Notice the warning message at the lower‐right area of the page.

To view more information about the warning message, you will open the Console view.

Click the Console button.

48. To view more of the message, you will scroll to the right.




Lab Guide

Step Action
49. The message in the Console view states that you are unable to open the Security view and
must check for adequate security privileges.


Step Action
50. You will now see if the Topology view appears when you are logged in with SCHEDMASTER
rights.

Double‐click the Topology tree item.

51. The Topology view appears, but notice the warning message at the bottom of the view.

With SCHEDMASTER ID permissions, you can see topology, but you are limited in the
actions you can perform.

You will now log in with ADMIN rights.

Right‐click the default (CAWA‐DBHost:7500) [connected] tree item.



Lab Guide

Step Action

Step Action


Lab Guide

Step Action
54. The connection has been disconnected.

You will now log in with the same connection but enter the ADMIN criteria.

Right‐click the default (CAWA‐Server:7500) [disconnected] tree item.

55. Click the Connect... list item.


Lab Guide

Step Action
56. Enter the desired information into the User name: field. Enter "ADMIN".




Lab Guide

Step Action
59. Double‐click the Security tree item.



Lab Guide

Step Action
60. Because you logged in with the ADMIN ID, the Security view appears.

All users and groups in the system appear in the Security view.

The Security view enables you to add, modify, and delete users.

Click the New User button.

61. To create a new user, you complete the fields in the New User view.


62. Click the Groups tab.

Step Action
63. You can also create and maintain user groups.



Lab Guide

Step Action
64. The Topology view appears, but notice that the warning no longer applies because you are
logged in with ADMIN security rights.

With this view, you can monitor servers, start and stop agents, and create agent groups.

You will now disconnect from the server and close the Desktop Client.

Right‐click the default (CAWA‐DBHost:7500) [primary] tree item.


Step Action





Lab Guide

Step Action
69. In this lab, you navigated perspectives and views.
End of Procedure.



Lab Guide

Lab 3‐1 Change the Role of Servers
In this lab, you will change the role of servers.

Step Action
1. In a CA Workload Automation DE high availability configuration, you can change the
server, preferred or standby, that processes workload.

Before changing the role of the servers, you will ensure that the required servers and
agents have been started in their respective environments.

You will begin by opening the environment that is running the preferred server.

Double‐click the CAWA‐Server link.


Lab Guide

Step Action
2. You will use the Terminal to determine the preferred server and agent status.

Double‐click the Terminal list item.


Lab Guide

Step Action
3. You will begin by changing to the CA Workload Automation DE directory.

Enter the desired information into the Command Line field. Enter "cd
/opt/CA/WorkloadAutomation_R11.3_SP3/bin".


Lab Guide

Step Action
4. Press [Enter].


Lab Guide

Step Action
5. You will enter the command to display the server status.

Enter the desired information into the Command Line field. Enter "./status".

Step Action
6. Press [Enter].


Lab Guide

Step Action
7. From the status command response, you can see that the server pid value appears,
meaning the preferred server is running.

Next, you will determine the status of the agent.

You will enter the command to change to the agent directory.

/opt/CA/WorkloadAutomation_R11.3_SP3/ESPSystemAgent".


Lab Guide

Step Action
8. Press [Enter].


Lab Guide

Step Action
9. You will enter the command to display the agent status.

Enter the desired information into the Command Line field. Enter "./cybAgent &".

Step Action
10. Press [Enter].


Lab Guide

Step Action
11. From the status command response, you can see that the agent pid value appears,
meaning the agent is running.

You will now switch to the second server environment, the server designated as the
standby server.

Click the Change Environment menu.


Lab Guide

Step Action
12. Click the CAWA‐DBHost link.


Lab Guide

Step Action
13. You will use the Terminal to determine the standby server and agent status.


Step Action
14. You will begin by changing to the CA Workload Automation DE directory.

/opt/CA/WorkloadAutomation_R11.3_SP3/bin".



Lab Guide

Step Action
15. Press [Enter].


Lab Guide

Step Action
16. You will enter the command to display the server status.

Enter the desired information into the Command Line field. Enter "./status".

Step Action
17. Press [Enter].


Lab Guide

Step Action
18. From the status command response, you can see that the server pid value appears,
meaning the standby server is running.

Next, you will determine the status of the agent.

You will enter the command to change to the agent directory.

/opt/CA/WorkloadAutomation_R11.3_SP3/ESPSystemAgent".


Lab Guide

Step Action
19. Press [Enter].


Lab Guide

Step Action
20. You will enter the command to display the agent status.

Enter the desired information into the Command Line field. Enter "./cybAgent &".

Step Action
21. Press [Enter].


Lab Guide

Step Action
22. From the status command response, you can see that the agent pid value appears,
meaning the agent is running.

You will now switch to the Windows server environment that is running the Desktop Client
to change the server roles.



Lab Guide

Step Action
23. Click the CAWA‐Client link.


Lab Guide

Step Action
24. To perform the server changeover task, you will start the Desktop Client.


25. The Connect to Server dialog appears, displaying the connection information for the last
logged‐in user.

In this scenario, you will use the displayed connection information, logging in with ADMIN
rights and to CAWA‐Server.

Logging in with ADMIN rights enables you to manage the server roles.

Enter the desired information into the Password: field. Enter "admin".



Lab Guide

Step Action
27. Because the last time you were logged in you were viewing the Admin perspective, the
Admin view appears, displaying the active server connection.

Server roles can be changed by issuing the changerole CLI command or by using the
Topology view.

In this scenario, you will use the Topology view.




Lab Guide

Step Action
28. To create more area in the Topology view, you will adjust the size.

Press the left mouse button and drag the mouse to the desired location.


Lab Guide

Step Action
30. The Topology view enables you to manage servers.

In the view, notice the server status. The primary role is assigned to the server named
CAWA‐Server and the standby server role is assigned to the server named CAWA‐DBHost.
Both servers are running.

Also notice that the agent is named PREFERRED_AGENT and is currently active.

You will now change the roles of the servers.

Right‐click the default (CAWA‐Server:7500) (2) tree item.

31. Click the Change Servers Role list item.

Step Action



Lab Guide

Step Action
33. After you click Yes, to verify the change server role request, the Desktop Client will
disconnect the current connection and switch the roles of the servers.

Notice in the Console view that the messages display the tasks that are being performed.

Press [Enter].

Step Action
34. After the reconnection takes place, you can see that the CAWA‐DBHost server, the
standby server, is now the active server.

Point to the default (CAWA‐DBHost:7500) [primary] tree item.


Lab Guide

Step Action
35. After the reconnection takes place, you can see that the server named CAWA‐DBHost, the
standby server, is now the active server.

You can also see server details by moving the mouse over the server row in the Topology
view.

Point to the Status column.

36. The details in the pop‐up message show that the server named CAWA‐DBHost, which is
the standby server, is now running as the primary server.

Point to the Standby (CAWA‐Server:7500) tree item.

37. The details in the pop‐up message show that the server named CAWA‐Server, which is the
preferred server, is now running as the standby server.

You will now reverse the server roles.

Right‐click the default (CAWA‐DBHost:7500) (2) tree item.

38. Click the Change Servers Role list item.



Lab Guide

Step Action

40. The active connection is disconnected because the roles of the servers are reversed.

Press [Enter].


Lab Guide

Step Action
41. Point to the default (CAWA‐Server:7500) [primary] tree item.

42. After the reconnection takes place, you can see that the server named CAWA‐Server, the
preferred server, is now the active server.

Point to the Status column.

43. The details in the pop‐up message also show the change in server roles.

Point to the Name column.



Lab Guide

Step Action


46. In this lab, you changed the role of servers.
End of Procedure.



Lab Guide

Lab 3‐2 Add a User and Grant Agent and Report Permissions
In this lab, you will add a user and grant agent and report permissions.

Step Action
1. To create a new user, you will start the Desktop Client.



Lab Guide

Step Action
logged‐in user.


Logging in with ADMIN rights enables you to manage users.




Lab Guide

Step Action
4. CA Workload Automation DE server security is maintained by a set of security profiles
managed on the Security view.

Double‐click the Security tree item.

Step Action
5. To create more room to display the view in the right pane, you will minimize the Console
view.


6. You can see the two default IDs.

You will now create a new one.

Click the New User button.


Lab Guide

Step Action
7. All fields with an asterisk preceding the field name are mandatory fields and must contain
a value before the new user can be saved.

In this scenario, you will create a new user named USER1.

Enter the desired information into the *User ID: field. Enter "USER1".

8. Next, you will define a password.

In this scenario, the password will be the same as the user ID.

Note: Setting the user ID and password to the same value is not a good practice and is
only being performed in this course for ease of access.

Enter the desired information into the *Password: field. Enter "USER1".

9. You must verify the password.

Enter the desired information into the *Confirm password: field. Enter "USER1".

10. After defining the user ID and password, you need to assign security rights.

User profiles have permissions associated with them. Permissions determine the type of
access a user or group has to a particular element of the CA Workload Automation DE
server. Permissions can be used to restrict access.

Click the Permissions tab.

11. The field at the top of the Permissions tab enables you to copy permissions from another
user, which can save time if you are setting up multiple users with the same rights.

The buttons at the bottom of the view enable you to manage security rights.

You will begin by adding a new right.

Click the Add... button.


Lab Guide

Step Action
12. The Add Permission dialog enables you to add specific permissions and access to users.

You start by selecting the required type of permission from the list.

Click the Permission type: list.

13. A list of all permission types appears.

For this user, you are going to define agent and reporting rights.

You will begin by defining agent rights.

Click the AGENT list item.

14. After you select a permission type, the dialog displays the related property to which the
permission will be defined.

For this right, you will permit the user to only be able to define workload on agents whose
names start with AB.

Click the Value cell.

15. Enter the desired information into the Value field. Enter "ab*".

16. Under Access, you can choose to allow or deny access to the defined permission.

Because you only want this user to access any agent whose name starts with AB, you will
leave the default value of Allow.


17. After you define a permission, the permission appears in the list on the Permissions tab.

Next, you will define permissions for agent control commands.



Lab Guide

Step Action
18. Click the Permission type: list.

19. Click the AGENTMSG list item.

20. Permissions are defined to two properties.


21. You will use the asterisk wildcard value to include any agent control command.

Enter the desired information into the Value field. Enter "*".

22. Next, you need to define which agents the commands defined earlier can be issued by the
user.

For this instance, you will only permit commands to be issued for agents whose names
start with AB.




25. You will now define another agent permission.



27. You will now define agents that can have work submitted on them by a specific user.

Click the AGENTUSER list item.



Lab Guide

Step Action
28. For this instance, you will only permit the user to submit workload on agents whose
names start with AB.



30. Next you will define this permission so that any user ID can submit workload on the
defined agent name.


31. Enter the desired information into the Value field. Enter "*".


33. The next type of permissions you will grant will apply to reporting.



35. You will define the report names that this user can manage.

Click the REPORT_DESIGN list item.

36. Click the Value cell.

37. For this instance, you will only permit the user to access reports whose names start with
AB.

Enter the desired information into the Value field. Enter "ab*".


Lab Guide

Step Action
38. Lastly, you will permit the user to only be able to read the report, not to alter or update it.

Click the Read option.


40. You will add one more permission.



42. You will permit the user to execute or trigger specific reports.

Click the REPORTX list item.

43. Click the Value cell.

44. For this instance, you will only permit the user to execute reports whose names start with
AB.

Enter the desired information into the Value field. Enter "ab*".


46. After you have defined the user, you must save the updates.

Click the Save button.


Lab Guide

Step Action
47. The new user appears in the list.



49. In this lab, you added a user and granted agent and report permissions.
End of Procedure.



Lab Guide

Lab 3‐3 Run CLI Commands
In this lab, you will run CLI commands.

Step Action
1. To run CLI commands, you will start the Desktop Client.



Lab Guide

Step Action
logged‐in user.


Logging in with ADMIN rights enables you to successfully execute all CLI commands.



4. Click the CLI button.


Lab Guide

Step Action
5. The CLI perspective enables you to issue commands against CA Workload Automation DE.

After clicking CLI, you must select a server from the CLI view before you can issue
commands.

Double‐click the default (CAWA‐Server:7500) [primary] tree item.

Step Action
6. You will start by executing the about CLI command to display server information.

Enter the desired information into the Command field. Enter "about".

7. Click the Send button.


Lab Guide

Step Action
8. The information displayed enables you to see server information, CA Workload
Automation DE build information, whether high availability is enabled, and connection
information.

Another useful command is the help CLI command.



10. This command lists all available CLI commands with a short description of them.

To view more available commands, you will scroll up.

12. The help CLI command also enables you to define help for a specific command by entering
help, followed by any CLI command.

Enter the desired information into the Command field. Enter "help help".


14. Information about the help command appears in the view, showing the command syntax
and definition.

Enter the desired information into the Command field. Enter "help uptime".



Lab Guide

Step Action
16. Information about the uptime CLI command appears in the view, showing the command
syntax and definition.

You will now execute the uptime CLI command.

Enter the desired information into the Command field. Enter "uptime".


18. The amount of time the server has been running appears in the view.

You will execute another CLI command.

Enter the desired information into the Command field. Enter "countlist".



Lab Guide

Step Action
20. The countlist CLI command displays a total count for each artifact type in the system.

You will now disconnect the ADMIN user from the server and log in with SCHEDMASTER.



Step Action

23. Click the Connect to the server button.

24. Enter the desired information into the User name: field. Enter "SCHEDMASTER".



Lab Guide

Step Action

Step Action
27. Double‐click the default (CAWA‐Server:7500) [connected] tree item.


Lab Guide

Step Action
28. You will execute the about CLI command again.

Enter the desired information into the Command field. Enter "about".


30. Notice the command result this time.

No information about the system is displayed.

You will execute another CLI command.

Enter the desired information into the Command field. Enter "uptime".



Lab Guide

Step Action
32. Again, no information about the system is displayed.

Privileges define which results are shown when a CLI command is executed.



34. The help CLI command displays properly.

Enter the desired information into the Command field. Enter "help uptime".



Lab Guide

Step Action
36. Even though logged in as SCHEDMASTER, you were not able to see the results when you
issued the uptime CLI command.

Executing the help uptime CLI command displays the syntax and command definition.

You will now disconnect and close the Desktop Client.



Step Action




Lab Guide

Step Action
41. In this lab, you ran CLI commands.
End of Procedure.



Lab Guide

Lab 4‐1 Create an Application
In this lab, you will create an application.

Step Action
1. To create an application, you will start the Desktop Client.


logged‐in user.

SCHEDMASTER rights and to CAWA‐Server.

Logging in with SCHEDMASTER rights enables you to successfully create and manage an
application.



Lab Guide

Step Action

4. To create an application, you use the Define perspective.

The Define perspective is already open.

To create a new application, you click New.


5. The Application properties dialog appears in which you define the application.

For this scenario, you will create an application named PAYROLL.

Enter the desired information into the *Name: field. Enter "PAYROLL".

6. Next, you will define application‐level properties.

When you define application‐level properties, any job that is added to the application will
have the properties defined here by default.

Defining application‐level properties means any job that is added to the application will,
by default, have the application‐level properties.

In a real work environment, it is recommended to select Wait for previous generation.
However, you will not select it for this lab environment.

You will select three other parameters.

Click the Propagate dueout time option.

7. Selecting the Require reason for job commands option forces the user to add a reason why
a job command was executed. This text will appear in logs to help resolve and track issues
that arise.

Click the Require reason for job commands option.


Lab Guide

Step Action
8. If you require critical path processing, you must select Estimate end time.

Click the Estimate end time option.

9. By default, the run frequency is set to run all jobs daily, which is seven days a week. You
will not change the default setting.

Next, you will define the agent to use. You will select the preferred agent.

Click the Agent list.

10. Click the PREFERRED_AGENT list item.



Lab Guide

Step Action
11. The remaining options on the Basic page will not be defined.

Next, you will define a notification.

Click the Notifications tree item.

Step Action
12. You have the option to set three different types of notifications:
‐ Email
‐ Alerts
‐ SNMP Traps

You will create an email notification.

Because the Email tab is selected by default, to create a new notification, you can click
New....

Click the New... button.


Lab Guide

Step Action
13. To set up a notification, in the Monitor states section, you select the states that will trigger
the notification.

In this scenario, you will add four states that will trigger the notification to be sent.

Click the Abandon submission option.

14. Click the Failed option.

15. Click the Suberror option.

16. Click the Unknown option.

17. Next, you complete the email information.

You begin by defining to whom the email is sent.

You can add email addresses in the To: field, separated by semicolons, or you can add an
email group name. In your organization, check with the administrator for valid group
names.

In this scenario, you will add an email group name.

Click in the To: field.

18. Enter the desired information into the To: field. Enter "email group".
19. Click the Add button.

20. The Subject line contains predefined text that includes symbolics defining specific job and
application attributes.

You have the option to not use this text by clearing the Use default subject option.

Press [Enter].


Lab Guide

Step Action
21. You can also append text to the email by entering text in the Message field.

Enter the desired information into the Message: field. Enter "This email was sent to pass
status information for the job named".

22. You are able to include built‐in symbolics in the message text.

Right‐click in the Message: field.

Step Action
23. Click the Built‐in Symbolics list item.

24. You can add application or job symbolics.

Click the Job list item.



Lab Guide

Step Action
25. A list of all built‐in job symbolics appears.

You will begin by adding the name of the job that triggered the notification, based on the
monitor states that you selected in the Monitor states area.

Click the Name list item.

Step Action
26. Press [Enter].
27. You will now add more built‐in symbolics to help define the status, starting with the job
state.



Lab Guide

Step Action

29. Click the Job list item.

30. Click the State list item.

31. Press [Enter].


Lab Guide

Step Action
32. Next, you will add the job status.



Lab Guide

Step Action

34. Click the Job list item.

35. Click the Status list item.



Lab Guide

Step Action
36. Press [Enter].
37. Now, you will add the event name.




Lab Guide

Step Action

39. Click the Application list item.

40. Click the Event Name list item.



Lab Guide

Step Action
41. Press [Enter].
42. Next, you will add the application generation number to the message.




Lab Guide

Step Action

44. Click the Application list item.

45. A list of all built‐in application symbolics appears.

Click the Generation list item.



Lab Guide

Step Action
46. The notification is defined; you will save it.


47. The email that you defined will be sent when any job in the application has one of the
conditions you defined.

Point to the Monitor States cell.

48. When you point the cursor to the notification name, the notification conditions that were
defined appear in the pop‐up message.



Lab Guide

Step Action
49. You will now define the jobs in the application.

The job types that you can add to the application are defined in the right panel named
Palette, under System. By default, UNIX is selected.

There are three methods to add jobs to the Application Workspace area. You can:
‐ Click the job type from the System list and drag it to the Application Workspace area
‐ Copy existing jobs and paste them on the Application Workspace area
‐ Click the Jobs button at the top of the Application Workspace area, select the required
job from the Palette, and then click anywhere in the Application Workspace area

For this scenario, you will add UNIX jobs to the application using the select‐and‐click
method.



Lab Guide

Step Action
50. After you click in the Application Workspace area, a workload object graphic appears
identifying the job type.

Notice the red highlight surrounding the UNIX graphic. This means the job has not been
defined.

You now need to define the job attributes.

Right‐click the Job graphic.

Step Action
51. A list of all available actions that you can perform on the workload object appears.

You will edit this job.

Click the Edit list item.



Lab Guide

Step Action
52. You will begin by replacing the default job name.

Enter the desired information into the *Name: field. Enter "First_Job".

53. Click the Expand button.

54. The Agent area is predefined because you set it up at the application level.

If you need to change the agent, clear the Use Application‐level defaults option and then
enter the correct agent information.

Click the Collapse button.




Lab Guide

Step Action
56. The Run frequency area is predefined because it is defined at the application level.

If you need to change the frequency, clear the Use Application‐level defaults option and
then enter the correct frequency information.


57. Next, in the Specify action to take area, you will define a command to execute.

You also have the option to run a script instead.

Click the Execute a command option.

58. Click in the *Script/command name: field.

59. You will enter a command that is defined in the binary folder, the sleep command.

Enter the desired information into the *Script/command name: field. Enter "/bin/sleep".
60. Next, you need to define an argument to pass to the command. For this job, you will
define a value of 10.

That means the job will go to sleep for 10 seconds after it starts executing.

You define these values so that after the application is triggered, you can monitor the jobs
as they execute and see the jobs change states and statuses in the different view
perspectives.

Click in the Arguments to pass: field.

61. Enter the desired information into the Arguments to pass: field. Enter "10".
62. You will now define the user ID as root.

Click in the User ID: field.

63. Enter the desired information into the User ID: field. Enter "root".


Lab Guide

Step Action
64. The basic job attributes are defined.

You can further define job attributes by selecting other options from the left pane.



Lab Guide

Step Action
65. Notice that the notification alert that you defined at the application level appears in the
list.



Lab Guide

Step Action
66. After the mandatory job definition attributes have been defined, the red highlight no
longer appears around the UNIX graphic.

You will add a second job to the Application Workspace area and then define it.


67. Right‐click the Job graphic.


Lab Guide

Step Action
68. Click the Edit list item.


Lab Guide

Step Action
69. You will change the default name.

Enter the desired information into the *Name: field. Enter "Second_Job".

70. You will define the sleep command to be executed.


71. Enter the desired information into the *Script/command name: field. Enter "/bin/sleep".

72. You will define this job to sleep for 30 seconds.

Enter the desired information into the Arguments to pass: field. Enter "30".

73. The user will be defined as root.

Enter the desired information into the User ID: field. Enter "root".

74. For this job, you will change the run frequency value.

Click the Expand button.

75. Click the Use Application‐level defaults option.

76. To remove the default value from the list, you click Delete.

Click the Delete button.

77. When adding run criteria, you can define the job to run, or not run, during the defined
time.

Click the Add Run button.


Lab Guide

Step Action
78. If you know the frequency keywords that define when this job will run, you can enter
them in the When field.

Otherwise, you can use the Run window to enter the frequency.

Click the ... button.

79. The current frequency is to run the job every day of the week.

You will define this job to run only on workdays.

Click the workday option.

Step Action
80. The new run frequency is defined and appears in the Use generated statement read‐only
field.



Lab Guide

Step Action
81. The attributes of the second job are defined.


82. You will now define dependencies between the two jobs.

Click the Dependencies button.


Lab Guide

Step Action
83. This function uses the drag‐and‐drop method.

To create a dependency, you click and hold on the first job and then drag the mouse to
the second job.



85. A green arrow appears defining the dependency.

By default, the dependency is defined because the second job will not run until the
successful completion of the first job.

You can view other dependency options.

Right‐click the arrow object.


Lab Guide

Step Action
86. Click the Release Conditions... list item.



Lab Guide

Step Action
87. By default, the Successful completion of the predecessor option is selected.

If required, you can change the dependency type.

Click the Any completion of the predecessor option.


Step Action

90. Changing the dependency type changes how the line connecting the jobs appears. It is
now a dashed line.



Lab Guide

Step Action



Lab Guide

Step Action
92. You will now define the dependency so that a specific exit code is required before the
second job will run.

Click the Exit codes option.

93. Enter the desired information into the Exit codes field. Enter "44".


Step Action


Lab Guide

Step Action
96. This dependency type appears as a blue line with the required exit code.

You will now return the dependency type to successful completion.


Step Action



Lab Guide

Step Action
98. Click the Successful completion of the predecessor option.



Lab Guide

Step Action


Lab Guide

Step Action
101. Another method of adding jobs to the Application Workspace area is copying an existing
job and editing it.

To copy a job, you need to use the Select function.

Click the Select button.

Step Action


Lab Guide

Step Action
103. Click the Copy list item.



Lab Guide

Step Action

105. Right‐click the Application Workspace whitespace.

Step Action
106. Click the Paste list item.



Lab Guide

Step Action
107. A third job appears in the Application Workspace area.

You now need to edit the job attributes.



Lab Guide

Step Action



Lab Guide

Step Action
109. You will begin by changing the job name.

Enter the desired information into the *Name: field. Enter "Third_Job".

110. Next, you will change the run frequency.


111. Click the Add Run button.

112. You will define this job to run only Monday, Wednesday, and Friday.

Click the When cell.

113. Enter the desired information into the When field. Enter "mon wed fri".

114. Next, you will define the job to not run on holidays.

The holidays that this job will not run on must be defined in the system calendar.

You will define holidays later in the course.

Click the Add Do Not Run button.

115. Click the When cell.

116. Enter the desired information into the When field. Enter "holidays".

117. You will change the sleep time to seven seconds.



Lab Guide

Step Action
118. You will define a time dependency for the job.

Click the Time Dependencies tree item.


Lab Guide

Step Action
119. You will define this job to wait two minutes before executing from the moment it is
eligible to run.

Click in the Delay submission when eligible by field.

120. Enter the desired information into the Delay submission when eligible by field. Enter "2".


Lab Guide

Step Action
122. You will now define job dependencies using a different method, using the Edit Job
Dependencies dialog.



Lab Guide

Step Action
123. Click the Edit Job Dependencies....


Lab Guide

Step Action
124. All jobs available for creating dependencies with the selected job appear in the Available
jobs section.

You will define the job named First_Job as a predecessor to the third job.

Click the First_Job list item.

125. Click the < Add button.


127. The green arrow appears defining the successful dependency association.

After you place jobs on the Application Workspace area and define dependencies, to
better visualize the path, you can use the layout function.

Click the Layout button.

128. The jobs now appear in the appropriate placement and in the defined flow.

You will add another job to the Application Workspace area using the drag‐and‐drop
method.

You will add another UNIX job from the Palette.




Lab Guide

Step Action
130. You will now edit the job attributes.



Lab Guide

Step Action

132. You will change the default name.

Enter the desired information into the *Name: field. Enter "Fourth_Job".

133. Next, you will change the default run frequency.


134. Click the Use Application‐level defaults option.



Lab Guide

Step Action
136. Press [Backspace].


Lab Guide

Step Action
137. You will use the Run dialog to define the frequency.


138. You will define the job to run on the last workday of every month.

Click the Every option.

139. Click the Last option.

140. Click the workday option.

141. Click the month option.

142. After you define a run frequency, you can test it to help ensure that the job will run on the
required dates.

You can set the number of dates to display by changing the default value of 10 in the
Display results list.

You will leave the default value.

Click the Test button.

143. The Test results pane displays the next 10 dates that the job is scheduled to run.

Notice that because the last workday of the month is defined for the frequency, the days
listed in the Test results: area are not necessarily the last day of the month.



Lab Guide

Step Action
144. If the required dates are not visible, you can further define the run frequency criteria.


145. Click the Collapse button.

146. You will define this job to execute the sleep command with an argument value of 15 and a
user ID value of root.


147. Enter the desired information into the *Script/command name: field. Enter "/bin/sleep".

148. Enter the desired information into the Arguments to pass: field. Enter "15".

149. Enter the desired information into the User ID: field. Enter "root".

150. The required job attributes are defined.


151. You will now define dependencies for the fourth job.



Lab Guide

Step Action
152. You will make First_Job a predecessor to Fourth_Job.




Lab Guide

Step Action
154. Click the Layout button.

155. To make it easier when you are adding multiple jobs that have matching attributes to the
Application Workspace area, you can select the workload object from the Palette and
change the appropriate template definitions.

Right‐click the UNIX list item.


Lab Guide

Step Action
156. Click the Job Defaults list item.



Lab Guide

Step Action
157. You will begin by adding a run statement to the default UNIX workload object.

You will define the frequency with the run daily attribute.

Click the Add Run button.


159. Enter the desired information into the When field. Enter "DAILY".
160. Next, you will define the sleep command to execute.


161. Enter the desired information into the Script/command name: field. Enter "/bin/sleep".

162. You will not define an argument value because each argument will be different for every
job that you add.

You will define the User ID field with a value of root.

Enter the desired information into the User ID: field. Enter "root".

163. The required updates to the template have been made; you will save the changes.


164. Now, you will add four jobs to the Application Workspace area using the redefined UNIX
workload object.

Click the Jobs button.


Lab Guide

Step Action




169. The four jobs have been added; you will now define each of them.



Lab Guide

Step Action


Lab Guide

Step Action
171. You will start by changing the job name.

Enter the desired information into the *Name: field. Enter "Fifth_Job".

172. For this job, you will add a qualifier.

A qualifier is a tag, or prefix, that can be referenced by parameters and JavaScript.

Enter the desired information into the Qualifier: field. Enter "this_is_Job_Five".

173. Lastly, you will define an argument value for the command.


174. The job is defined; you will save the changes.



Lab Guide

Step Action

Step Action



Lab Guide

Step Action

Enter the desired information into the *Name: field. Enter "Sixth_Job".

178. For this job, you will define a different run frequency.

You will begin by deleting the template definition.


179. Click the Add Run button.

180. You will add a frequency that defines the job to only run on Wednesdays, starting in
January, but only every other month.

Enter the desired information into the When field. Enter "wed of jan mar may jul sep
nov".


Lab Guide

Step Action




Step Action


Lab Guide

Step Action



Lab Guide

Step Action

Enter the desired information into the *Name: field. Enter "Seventh_Job".

186. You will leave the run frequency set to DAILY.

Lastly, you will define an argument value for the command.





Lab Guide

Step Action
188. You will now define the last job.


Step Action



Lab Guide

Step Action

Enter the desired information into the *Name: field. Enter "Eighth_Job".


192. For this job, you will define a different run frequency.

You will define the job to run on all workdays.

Enter the desired information into the When field. Enter "workdays".
193. You will now test this new run frequency.


194. Click the Test button.


Lab Guide

Step Action
195. From the results in the Test results area, you can see that Saturday and Sunday are not
present.








200. You will now set job dependencies.



Lab Guide

Step Action
201. You will use the click‐and‐drag method to set a dependency from the fifth job to the sixth
job.




Lab Guide

Step Action


Lab Guide

Step Action
204. You will again use the click‐and‐drag method to set a dependency from the sixth job to the
seventh and eighth jobs.



206. Press the left mouse button and drag the mouse to the desired location.



Lab Guide

Step Action

Step Action
209. Finally, you will use the Edit Job Dependencies dialog to set the remaining job
dependencies.

You will set predecessors to the fifth job.



Lab Guide

Step Action
210. Click the Edit Job Dependencies... list item.


Lab Guide

Step Action
211. You will define the second, third, and fourth jobs as predecessors to the selected job.

Click the Second_Job list item.

212. Press the [Ctrl] key and click the Third_Job list item.

213. Press the [Ctrl] key and click the Fourth_Job list item.

214. Click the < Add button.



217. The application has been defined. You will now save it and upload it to the database.

You can save the application to your local computer or to a shared drive as part of a
change control process.

You will begin by saving the application to your desktop.


218. You will navigate to the desktop.

Click the Favorites list item.

219. Double‐click the Desktop list item.


Lab Guide

Step Action
220. Click the Save button.

221. You will now upload the application to the database.

Click the Upload button.

222. The Upload Application to Repository dialog appears.

By default, the repository will be the database to which you connected.

Because you are able to save multiple versions of applications, it is highly recommended
that you add comments to each version to help differentiate them when you are viewing
the versions.

Enter the desired information into the Comments field. Enter "First application built in CA
Workload Automation DE upload".


224. The application is successfully uploaded to the database.

To download applications from the database, you can click Download.

Click the Download button.

225. The Download Application(s) from Repository dialog appears displaying all applications
that currently reside in the database.

You can see the uploaded PAYROLL application.


226. Notice the Comments column.




Lab Guide

Step Action
227. You will download the application.

Click the PAYROLL list item.


229. Because the application is still open in the Desktop Client, a warning message appears
stating the open application will be closed and any changes you may have made will be
discarded.

If you need to save the open application, you can click No, save the application, and then
use the download function again.

In this scenario, you will click Yes to download the application from the database and
discard the currently opened application.

Click the Yes button.

230. The downloaded application now appears in the Application Workspace area.

You will again save the application locally.


231. You will overwrite the previous version on the desktop.



233. You will again upload the application to the database.



Lab Guide

Step Action
234. Remember to always add a comment to help with version control.

Enter the desired information into the Comment field. Enter "Second upload of
application".


236. You will now view the versions in the database.


237. The current version of the application appears in the dialog.

You will scroll to the right to view the Comments column.


238. From the comment in the Comments cell, you can see that this is the latest version of the
application.

You will now view earlier versions.


240. All previous versions of the application appear in the Archived Versions section.

If needed, you can select an archived version to download.

Click the Cancel button.

241. You will now close the Desktop Client.



Lab Guide

Step Action

243. In this lab, you created an application.
End of Procedure.



Lab Guide

Lab 5‐1 Simulate a CA Workload Automation DE Event
In this lab, you will simulate a CA Workload Automation DE event.

Step Action
1. To simulate an event, you will start the Desktop Client and download an application.


logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully simulate an application.



Lab Guide

Step Action

4. You will now download an application to simulate.



You will download the application named PAYROLL and simulate the event.



7. The downloaded application now appears in the Application Workspace area.

Before simulating the event, you will resize the Application Events view.


8. It is a good practice to always simulate an event, especially after making any change to an
application.

Simulating an event enables you to test an application on a given schedule date.

To simulate an event, you must select an event from the Application Events view.

Click the SCHEDMASTER.PAYROLL list item.

9. Click the Simulate... button.


Lab Guide

Step Action
10. The Simulate Event dialog appears.

When you simulate an event, you can test the application for any given day. You define
the particular day in the Schedule criteria field.

When no schedule criteria are entered, the system simulates the event for the current
day.

Rather than simulating all the jobs in the application, you can select a particular job to
simulate.

Click the Select Jobs button.

11. All available jobs in the application appear in the Select jobs dialog.

To test specific jobs, select them from the Jobs in Application section and then click Add or
Add with Successors.


12. If required, using the User Parameters to pass to Event section, you can pass required
arguments to the event.

When no schedule criteria are entered in the Schedule criteria field, the system simulates
the event for the current day.



Lab Guide

Step Action
13. The simulation window appears displaying the results of simulating the event based on
the jobs scheduled to run today.

The left pane displays the job flow.

In this scenario, six of the eight jobs are scheduled to run.

Press [Enter].
14. The right pane displays the definition for each scheduled job with the results of any
variables in the definition.

The job definitions display commands that will be executed, symbolics that will be
resolved, predecessors and successors for each job, and so on.

If the result is an error, for example, a bad server name or an unavailable agent, an error
message will appear in the right pane with the associated job definition.




Lab Guide

Step Action


18. All jobs scheduled to run appear in the right pane.


19. You will change the simulation date to see which jobs would be scheduled to run.

Click the Simulate... button.

20. You will simulate the event for Saturday.

Enter the desired information into the Schedule criteria: field. Enter "sat".


Lab Guide

Step Action

the jobs running on Saturday.

In this scenario, three of the eight jobs would be scheduled to run.


23. You will change the simulation date again to determine which jobs would be scheduled to
run.


24. Instead of entering simulation criteria in the Schedule criteria field, you can use the
Simulate dialog.

Click the Schedule button.

25. You will simulate the event on the last workday of July.

Click the Last option.

26. Click the workday option.

27. Click the specific month option.

28. Click the specific month list.

29. Click the July list item.



Lab Guide

Step Action

the jobs running on the last workday of July.

In this scenario, seven of the eight jobs would be scheduled to run.


33. Remember, any time you make a change to an application or event, always simulate it.

This is especially true for the days and dates that you know have unique scheduling
requirements.


34. Click the No button.



37. In this lab, you simulated a CA Workload Automation DE event.
End of Procedure.



Lab Guide

Lab 5‐2 Create a CA Workload Automation DE Event
In this lab, you will create a CA Workload Automation DE event.

Step Action
1. To manage events, you will start the Desktop Client and download an application.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully manage events.



4. You will now download an application to manage an event.



You will download the application named PAYROLL and manage the event.



7. The downloaded application now appears in a flowchart version in the Application
Workspace area.

When an application is created, CA Workload Automation DE creates an event, which you
define.

The event appears in the Application Events view.



Lab Guide

Step Action
8. You will open the event and add schedule criteria.

Right‐click the SCHEDMASTER.PAYROLL list item.

Step Action



Lab Guide

Step Action
10. Click the Schedule tree item.


Lab Guide

Step Action
11. The Schedule page is where you define when the event is triggered.

Click the Add Schedule button.

12. You can add schedule criteria directly to the When field, or you can click the ellipsis button
and use the Schedule event dialog.

In this scenario, you will use the Schedule dialog.


13. You will schedule the event to run daily at 7:00 p.m.

Click in the Time field.

14. Click the down arrow next to the Time field.


Lab Guide

Step Action




19. Click in the Time field.


21. The schedule criteria have been entered.

The remaining fields will be left with their default values.

If you entered complex schedule criteria, you can use the test function to verify the run
criteria was entered correctly.



23. The edited event is now ready to be scheduled.

Events can also be created based on criteria other than scheduling.

You can create an event based on a file trigger. The File Trigger event continuously
triggers workload based on file activity.

Click the Create a new File Trigger button.


Lab Guide

Step Action
24. The new event appears in the list.

You will now edit the event to add the triggering file information.

Click the *SCHEDMASTER.PAYROLL1 list item.

25. Click the Edit button.

Step Action
26. Click the Properties tree item.

27. The Properties page displays the mandatory event information.

You will now define the file trigger criteria.

Click the File Trigger tree item.



Lab Guide

Step Action
28. First, you must define the name of the agent.

Click the *Agent name: list.

29. Click the PREFERRED_AGENT list item.

30. Next, you need to define the specific file on the agent server that will be monitored.

Click the Browse button.

31. The File Browser dialog appears, displaying the file structure for the server that is running
the agent you selected.

You will drill down to the folder where the file to be monitored will reside.

Double‐click the / list item.


Lab Guide

Step Action
32. The file will reside in the folder named opt.


33. Double‐click the opt list item.

34. You now need to enter the name of the file.

Click in the File: field.

35. Enter the desired information into the File: field. Enter "abc.txt".

36. Every time the file named abc.txt is created, the event will be triggered.


37. You select Recursive to ensure the entire directory path is read when searching for the
required file.

Click the Recursive option.

38. The File creation trigger conditions section will be left with the default values.

You will now define the owner user ID as root.

Click the Owner user ID: list.

39. Enter the desired information into the Owner user ID: field. Enter "root".


Lab Guide

Step Action
40. The file trigger event is created.


Step Action
41. Now, the application runs two different ways:
‐ At the scheduled time
‐ When a specific file is created

You will now upload the application with the newly defined events.

Right‐click the Application Workspace whitespace.


Lab Guide

Step Action
42. Click the Upload... list item.


Lab Guide

Step Action

Enter the desired information into the Comments field. Enter "Added File Trigger event
for the application".


45. When required, other event types are available:
‐ Database monitor
‐ Database trigger
‐ JMS subscribe
‐ SAP event monitor
‐ Variable dependency monitor
‐ z/OS data set trigger

Press [Enter].

46. You will now trigger the Date‐Time/Manual event.


47. Click the Trigger... button.


Lab Guide

Step Action
48. The Trigger Event dialog appears.

Triggering an event brings a new generation of the application to the active monitor.

Selecting the Submit Application on hold option permits the application to be triggered so
that it will be visible in the monitoring perspective, but places the entire application on
hold so that you will have to manually submit it. In this scenario, because the event
schedule criteria state the application is to run at 7:00 p.m., the jobs will not execute until
the held application is manually released.

Click the Submit Application on hold option.

49. The remaining fields will be left with their default values.




52. In this lab, you created a CA Workload Automation DE event.
End of Procedure.



Lab Guide

Lab 6‐1 Monitor and Control Active Workload
In this lab, you will monitor and control active workload.

Step Action
1. To monitor and control active workload, you will start the Desktop Client and download an
application.

Being able to monitor and control active workload will enable you to regulate your
workload.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully manage events.



4. You will now download an application to manage it during execution time.



You will download the application named PAYROLL.



7. This is the application you created a Date‐Time/Manual and File Trigger event for in a
previous lab.

You will now monitor and control workload for the application.

You monitor and control active workload in the Monitor perspective.



Lab Guide

Step Action
8. To see workload on a server, you must subscribe to it.


9. Subscription options determine what the server sends to the Desktop Client.

After subscribing to the server, job state changes are automatically sent to the Monitor
perspective without refreshing.

In this scenario, you will subscribe to all applications on the server, no matter their state.

Click the Subscribe All list item.




Lab Guide

Step Action
12. Currently, the application named PAYROLL has two generations displayed. One has the
state of Applhold and the other Complete.

Depending on when the previous lab was performed, you may have no completed
generations appearing, or more. The reason is that in the previous lab you added a
schedule to an event that triggers the application every day at 7:00 p.m. Each day that
goes by after the day you added the schedule to the event creates another generation.

To display a generation in a flowchart view, you double‐click the generation name.

Double‐click the PAYROLL.1, Applhold, 6 Jobs tree item.



Lab Guide

Step Action
13. This generation was a result of the manual trigger that
was performed at the end of the previous lab.

The application was triggered on hold, which you can see
because each job has a state of APPLHOLD.

The jobs that appear in the workflow are dependent on the
day that the application was triggered. This is due to
the different schedule criteria that were added to the
jobs when the application was created. You may see
more jobs, or less jobs, but either way, the lab will
work in the required method.

Before releasing the hold on the application, you will
open two custom views that will help you monitor the workflow.



Lab Guide

Step Action
14. Custom views are windows created to display only the information you want, in the
format you want.

You will open the Completed and Running views.

Double‐click the Completed tree item.

15. The Completed view appears displaying a list of the completed jobs.

A custom view looks like a table; it contains rows and columns of information.

The completed jobs that appear in this view are dependent on the day that the application
was triggered. This is due to the different schedule criteria that were added to the jobs
when the application was created. You may see more completed jobs, or less jobs.

Multiple custom views can be opened simultaneously. You will open a second view.

Double‐click the Running tree item.



Lab Guide

Step Action
16. Both views are now open in the right pane.

Views can be configured in the pane so that you can see the workflow with the views.

You will begin by configuring the size and placement of the Running view.

You will click the Running view tab and drag it to the lower right of the view.


18. You will now configure the size and placement of the Completed view.

You will click the Completed view tab and drag it to the bottom half of the Running view.


20. After configuring the views, you can see the workflow with both views.

You will now manually release the held application.

Click the Application Monitor tab.


Lab Guide

Step Action
21. Right‐click the PAYROLL.1, Applhold, 6 Jobs tree item.

22. Click the Release Application list item.



Lab Guide

Step Action
23. You must add a reason why you are issuing the release command because when you set
up the application, you selected the Require reason for job commands option.

Enter the desired information into the Reason: field. Enter "Releasing triggered
application for lab 6‐1".

24. After you click OK, you will watch the application run to completion.


25. Immediately after releasing the held application, the first job started executing.

You can see that the job icon in the workflow view changed from yellow, which means
held, to green, which means executing.

Also, notice that the executing job appears in the Running view.

Press [Enter].


Lab Guide

Step Action
26. After a few seconds, the workflow view updates to show the first job is complete; it is now
visible in the Completed view.

The second job is now executing and appears in the Running view.

Press [Enter].


Lab Guide

Step Action
27. After a few seconds, the workflow view updates to show the second job is complete; it is
now visible in the Completed view.

Because THIRD_JOB is waiting to execute, the application is in a state of Waiting.

Press [Enter].


Lab Guide

Step Action
28. After a few seconds, the workflow view updates to show the third job is executing; it is
now visible in the Running view.

Press [Enter].
29. After a few seconds, the workflow view updates to show the third job is complete; the job
icon is now highlighted in blue.

The next job, FIFTH_JOB, is now executing and appears in the Running view.

Press [Enter].
30. After a few seconds, the workflow view updates to show the job named FIFTH_JOB is
complete; the job icon is now highlighted in blue.

The next jobs, SEVENTH_JOB and EIGHTH_JOB, are now executing and appear in the
Running view.

Press [Enter].
31. After a few seconds, the workflow view updates to show the job named EIGHTH_JOB is
complete; the job icon is now highlighted in blue.

The job named SEVENTH_JOB is still executing.

Press [Enter].


Lab Guide

Step Action
32. All jobs in the application have executed successfully.

Next, you will trigger the application with the File Trigger event. Before triggering the
application, you will modify the application properties.

Click the Define button.


Lab Guide

Step Action


Lab Guide

Step Action
34. Click the Properties list item.

Step Action
35. You will select the option Hold on submission.

Selecting this option means the application can be triggered but requires a manual release
before it executes.

Click the Hold on submission option.



Lab Guide

Step Action
37. After making updates to an application, you must upload it to the database for the
changes to take effect.

You can tell if an application needs to be uploaded by the inclusion of an asterisk before
the application name on the tab.



Lab Guide

Step Action


Lab Guide

Step Action
39. It is best practice to add a comment before uploading a new version.

Enter the desired information into the Comments field. Enter "Updated application for
lab 6‐1; added submit on hold option".


41. You will now navigate to the Monitor view.


42. Recall that the file trigger type event that was created in an earlier lab relies on the
creation of a file named abc.txt on the server that is running the agent that was defined.

You will now navigate to the required server to create the necessary file so that the event
will trigger the application.

Point to the top of the page.
43. Click the Image Tab.

44. Click the Environment button.


Lab Guide

Step Action
45. The agent is running on the server named CAWA‐Server.

Double‐click the CAWA‐Server object.

46. You will open a terminal to create the required file.



Lab Guide

Step Action
47. The file trigger event will be monitoring the folder named opt.

You will create the required file in that folder.

Enter the desired information into the Command Line field. Enter "cd /opt".


Lab Guide

Step Action
48. Press [Enter].


Lab Guide

Step Action
49. You will use the touch command to create a zero‐bit file, which will be all that is required
to trigger the application.

Enter the desired information into the Command Line field. Enter "touch abc.txt".

Step Action
50. Press [Enter].
51. You will now navigate back to the server running the Desktop Client, named CAWA‐Client.

Click the Environment button.



Lab Guide

Step Action
53. A new generation is now listed in the left pane in an Applhold state.

If the generation does not appear, you can re‐subscribe all.


54. Before releasing the application, you will modify the properties of one of the jobs.



Lab Guide

Step Action
55. You will place this job on hold.

Click the Hold list item.


Lab Guide

Step Action
56. Recall that you must add a reason why this command is being issued.

Enter the desired information into the Reason: field. Enter "Controlling lab 6‐1 job flow".


Step Action
58. You will now manually release the held application.

Right‐click the PAYROLL.3, Applhold, 5 Jobs tree item.




Lab Guide

Step Action
60. Again, you must enter a reason as to why you are issuing the command.

Enter the desired information into the Reason: field. Enter "Releasing held application for
lab 6‐1".



Lab Guide

Step Action
62. Immediately after releasing the held application, the first job started executing.

You can see that the job icon in the workflow view changed from yellow, which means
held, to green, which means executing. Also, notice that the executing job appears in the
Running view.

Notice the pink border around the manually held job.

Press [Enter].
63. After a few seconds, the workflow view updates to show the first job is complete; there is
now a blue highlight surrounding the job icon.

The second job is now executing and appears in the Running view.

Press [Enter].


Lab Guide

Step Action
64. After a few seconds, the workflow view updates to show the second job is complete.

In the Completed view, you will scroll down to only show completed jobs from this third
generation.



Lab Guide

Step Action
65. Point to the PAYROLL.3, Manual Intervention, 5 Jobs tree item.

66. The application now has a state of Manual Intervention due to the update performed to
the job named FIFTH_JOB.

Before manually releasing the held job, you will update the job dependency for
SEVENTH_JOB.



Lab Guide

Step Action
67. For this job, you will drop the predecessor, which will permit the job to run without the
predecessor job executing successfully.

Click the Drop Predecessors list item.



Lab Guide

Step Action

Enter the desired information into the Reason: field. Enter "Controlling workflow for lab
6‐1".

69. Before the command can be executed, you must select the job to drop from the Job
predecessors section.

Click the FIFTH_JOB.THIS_IS_JOB_FIVE list item.

70. Click the Drop Selected button.


Lab Guide

Step Action
71. Immediately after dropping the predecessor, the successor job, SEVENTH_JOB, started
executing.

The job appears in the Running view.

Press [Enter].


Lab Guide

Step Action
72. After a few seconds, the workflow view updates to show the job named SEVENTH_JOB is
complete.

You will now release the job that was placed on hold.



Lab Guide

Step Action
73. Click the Release list item.



Lab Guide

Step Action

Enter the desired information into the Reason: field. Enter "Controlling application
workflow for lab 6‐1".


Step Action
76. Immediately after releasing the held job, it started executing.

The job appears in the Running view.

Press [Enter].


Lab Guide

Step Action
77. After a few seconds, the workflow view updates to show the job named FIFTH_JOB is
complete.

The final job is now executing.

Press [Enter].


Lab Guide

Step Action
78. All jobs in the application have executed successfully.

As jobs appear on the custom views, you are able to action them as you did on the
workflow view.

Right‐clicking a job row will open a menu from which you can select an option.

Right‐click the Completed Job list item.

79. You can locate a job from any generation.

Click the Locate Job in Graph list item.

80. The job becomes outlined with a blue border.

Right‐click the Completed Job list item.



Lab Guide

Step Action
81. Click the Locate Job in Graph list item.



Lab Guide

Step Action
82. You will scroll up the list to view jobs from a different generation.


83. Right‐click the Completed Job list item.

Step Action
84. Click the Locate Job in Graph list item.



Lab Guide

Step Action
85. The application containing the requested job appears on a different view. This is a
different generation than the one previously shown.

You now close the open views.





89. You will now remove the Hold on submission option from the application.



Lab Guide

Step Action


Lab Guide

Step Action

Step Action
92. Click the Hold on submission option.


94. You will upload the updated application to the database.


95. It is best practice to add a comment before uploading a new version.

Enter the desired information into the Comments field. Enter "End of lab 6‐1".



Lab Guide

Step Action
97. You will now navigate to the Monitor view.


Step Action
98. After applications successfully complete, the completed generations remain in the tree
view.

Right‐click the PAYROLL, 3 Generations tree item.


Lab Guide

Step Action
99. From the menu at the application level, you have the option to hide the completed
generations for a particular application. This removes all completed generations.

This option will also hide generations that become completed during your monitoring
session.


100. When you subscribe to a serve, you have the option to not show completed generations
and you have the option to hide all completed generations.

You can remove completed generations by issuing a CLI command.

The CLI command cannot be issued when logged in as SCHEDMASTER. You will log out and
then back in with ADMIN rights.

Click the Disconnect list item.


Lab Guide

Step Action

Step Action
102. Right‐click the default (CAWA‐Server:7500) [disconnected] tree item.




Lab Guide

Step Action
104. You will log in with ADMIN rights.




Lab Guide

Step Action

107. Click the CLI button.

108. To run CLI commands on a server, you need to select the required server from the list in
the left pane.

Double‐click the default (CAWA‐Server:7500) [primary] tree item.


Lab Guide

Step Action
109. The purgecompletedjobs CLI command will remove all completed generations from the
server.

Enter the desired information into the Command field. Enter "purgecompletedjobs".



Lab Guide

Step Action
111. The command successfully ran.


112. You will log out and back in with SCHEDMASTER rights to view the application generations.





Lab Guide

Step Action


Lab Guide

Step Action
115. Right‐click the default (CAWA‐Server:7500) [disconnected] tree item.


Step Action
117. Enter the desired information into the User name: field. Enter "SCHEDMASTER".

118. Enter the desired information into the Password: field. Enter "SCHEDMASTER".



Lab Guide

Step Action
120. Right‐click the default (CAWA‐Server:7500) [connected] tree item.

121. Click the Subscribe All list item.



Lab Guide

Step Action
122. The completed generations are no longer present in the server database.




125. In this lab, you monitored and controlled active workload.
End of Procedure.



Lab Guide

Lab 6‐2 Manage the Dashboard
In this lab, you will manage the dashboard.

Step Action
1. To manage the dashboard views, you will start the Desktop Client.

Being able to monitor and control active workload will enable you to regulate your
workload.



Lab Guide

Step Action
logged‐in user.

In this scenario, you will log in with ADMIN rights and to CAWA‐Server.

Logging in with ADMIN rights enables you to successfully manage the dashboards.




5. The custom and dashboard views are located in the Monitor perspective.


6. If the Custom Views and Dashboard Views tabs are not appearing, click Window > Show
Views and then click Custom Views or Dashboard Views.



Lab Guide

Step Action
7. The Custom Views view displays job information in a table.

Double‐click the Cancelled tree item.

8. The Cancelled view appears in the right pane.

The table displays information in rows and columns.

Right‐click the Cancelled tree item.



Lab Guide

Step Action
9. You can create any number of custom views by clicking New, Edit, or Copy.

When editing an existing view, it is recommended to copy the view, rename it, and modify
it as required.


10. Click the Dashboard Views tab.


Lab Guide

Step Action
11. The Dashboard Views view provides status and historical information in predefined status
message and system monitor custom views.

Double‐click the All Messages tree item.


13. Messages can be in the form of warnings or information about a specific component in the
system.



Lab Guide

Step Action

Step Action


Lab Guide

Step Action
16. Double‐click the Summary Dashboard tree item.

17. The Summary Dashboard displays information about the server that you are logged in to.

Double‐click the System Dashboard tree item.



Lab Guide

Step Action
18. The System Dashboard displays information in graphical and chart views.

To view more of the view, you will resize it by dragging the vertical divider to the left.

Press the left mouse button and drag the mouse to select the desired text.
20. To view more information provided in the view, you will scroll to the right.


21. To view more information provided in the view, you will scroll down.


22. To view more information provided in the view, you will scroll to the left.




Lab Guide

Step Action
23. To return to the top of the view, you will scroll up.


24. You will now close the Summary Dashboard view.

Click the Summary Dashboard tab.


Step Action
26. You can also create, edit, or delete views to display the information you need.

Right‐click the System Dashboard tree item.



Lab Guide

Step Action
27. You will copy the System Dashboard view to create a new view.

Click the Copy... list item.


Lab Guide

Step Action
28. The Edit Dashboard View dialog appears.

By default, the name of the dashboard starts with the words Copy of. You can rename the
dashboard as required.

When required, you can also change the layout properties.

To modify the original dashboard to create the new dashboard, you will remove the Agent
Status ‐ Pie Chart control.

Click the Agent Status ‐ Pie Chart list item.

29. Click the < Remove button.

30. You will now move the Agent Status ‐ Bar Chart control to appear in the upper‐left corner
of the view.

Click the Agent Status ‐ Bar Chart list item.

31. Click the Move Up button.



34. Next, you will move the Memory Monitor control to the bottom of the view.

Click the Memory Monitor list item.

35. Click the Move Down button.


Lab Guide

Step Action
36. Click the Move Down button.

37. After you have finished defining the new view, clicking OK will save the changes.


Step Action
38. The new view appears in the left pane.

Double‐click the Copy of System Dashboard tree item.


Lab Guide

Step Action
39. The dashboard appears displaying the content in the manner that you defined.

To view more information provided in the view, you will scroll down.


40. You will scroll up.


41. To view more information provided in the view, you will scroll to the right.




Lab Guide

Step Action
42. You will close the two open views.



Step Action
44. The Topology Status view displays messages from the server that you are logged in to.

Double‐click the Topology Status tree item.

45. The options at the top of the view enable you to define from which time period to display
messages.

To view the messages, you drill down into the server using the Expand buttons.



Lab Guide

Step Action
46. Messages appear in the list.

To view message properties, you double‐click the message row.

Double‐click an entry in the message row.

47. The Status Message Properties area appears.

Right‐click the Topology Status tree item.

48. You will copy this view to create a new view.

Click the Copy... list item.



Lab Guide

Step Action
49. The Edit Status Message View dialog appears.

By default, the name of the dashboard starts with the words Copy of. You can rename the
dashboard as required.

When required, you can change the types of status messages that appear in the view.

You will leave the default status message types, but will modify the columns in the view.

Click the Columns tree item.

Step Action
50. You will change how the status message columns appear in the view.

Click the Severity list item.


Lab Guide

Step Action
51. You will begin by moving the Severity column to appear beside the date column.

Click the Move Up button.

52. Next, you will add the Connection column to the view.

Click the Connection list item.

53. Click the Add > button.

54. The Connection column will now appear in the view.

Lastly, you will move the Connection column to appear beside the Severity column.

Click the Connection list item.



57. After you have finished defining the new view, clicking OK will save the changes.



Lab Guide

Step Action
58. The new view appears in the left pane.

Double‐click the Copy of Topology Status tree item.



Lab Guide

Step Action
60. You will close the message properties area to view the changes you made to the columns
in the view.


61. The columns on this view appear as you set them.





65. In this lab, you managed the dashboard.
End of Procedure.



Lab Guide

Lab 7‐1 Add an Agent
In this lab, you will add an agent.

Step Action
1. To add an agent, you will start the Desktop Client.

Defining CA Workload Automation DE agents enables you to automate workload on
different servers.



Lab Guide

Step Action
logged‐in user.


Logging in with ADMIN rights enables you to successfully add an agent.



4. To work with the server, you add agents using the Topology view.



Lab Guide

Step Action
5. Double‐click the Topology tree item.

6. Agents permit the schedulers to execute jobs across a range of operating systems and
applications.

Currently, there is one agent installed. You will add another.

Click the Agents (1) tree item.

Step Action
7. Click the New Agent button.


Lab Guide

Step Action
8. To add an agent, you must select the agent type from the list.

The agent type that you select will determine the fields that will appear to define the
agent.

Click the Select the agent type to define: list.

9. For this scenario, you will select UNIX for the standby agent that was installed during the
high availability setup.

Click the UNIX list item.

10. To better view the fields in the New Agent view, you will maximize it.

Click the Maximize button.

11. You begin by defining a name for the agent.

Click the *Name Parameter Value cell.

12. Enter the desired information into the *Name Parameter Value field. Enter
"STANDBY_AGENT".

13. The address is the TCP/IP or DNS name of the location where the agent was installed.

Click the *Address Parameter Value cell.

14. Enter the desired information into the *Address Parameter Value field. Enter "CAWA‐
DBHost".



Lab Guide

Step Action
15. Now, you need to enter the unique port number.

Click in the *Port number Parameter Value field.

16. Enter the desired information into the *Port number Parameter Value field. Enter
"17520".

17. Verify that the encryption key value is correct. For this scenario, the value shown is
correct.


You will now save the new agent details.


18. After saving the agent, it appears in the Topology view.

Initially, the agent will appear with an inactive status, but that will change after the server
recognizes it. After the server recognizes the agent, the status will change to active.

If the agent does not connect within a minute, you will need to verify the agentparm.txt
file on the CAWA‐DBHost server has the correct values in the Communications section.

Press [Enter].
19. Decision: Please make a selection from the options listed below.
 Agent Connects
Go to step 20
 Agent Does not Connect
Go to step 23
20. After the server recognized the agent, the status changed to active.

The agent is now ready to have workload run on it.




Lab Guide

Step Action
22. In this lab, you added an agent.
End of Procedure. Remaining steps apply to other paths.

Step Action
23. You need to open the environment that is running the server on which the agentparm.txt
file is located.

Click the Environment menu.

24. Click the Change Environment menu.

25. Click the CAWA‐DBHost link.


Lab Guide

Step Action
26. To verify the agentparm.txt file is configured correctly, you will navigate to the folder
where it resides.

Double‐click the File Browser list item.

27. Double‐click the File System list item.


29. Double‐click the CA list item.


Lab Guide

Step Action
30. Double‐click the WorkloadAutomation_R11.3_SP3 list item.

31. The agentparm.txt file resides in the ESPSystemAgent directory.

Double‐click the ESPSystemAgent list item.

32. To verify the values in the Communication section, you will open the file.

Double‐click the agentparm.txt list item.

33. Click the Display button.

34. You will scroll down the Communications section.



Lab Guide

Step Action
35. The required values appear in the fields in the Communications section.

If a value is missing in your file, add the missing data.



37. You will navigate to the CAWA‐Client environment to finish the agent installation.




Lab Guide

Step Action
39. After the server recognized the agent, the status changed to active.





Lab Guide

Step Action

41. In this lab, you added an agent.
End of Procedure.



Lab Guide

Lab 7‐2 Add the DB Plug‐in
In this lab, you will add the DB plug‐in.

Step Action
1. You can extend the functionality of an agent by installing one or more agent plug‐ins on
the agent installation directory.

Plug‐ins are installed on an existing systems agent on UNIX, Linux, or Windows.

In this scenario, you will install the DB plug‐in on the server named CAWA‐DBHost.
Installing this plug‐in will enable you to run SQL from within CA Workload Automation DE
directly against the database and be able to schedule it.

You will begin by opening the environment that is running the required server.

Double‐click the CAWA‐DBHost link.


Lab Guide

Step Action
2. To install the DB plug‐in, you will navigate to the folder where the database.pak file
resides.

The database.pak file contains the required installation files for the DB plug‐in.

Double‐click the File Browser list item.

3. Double‐click the File System list item.


5. Double‐click the CA list item.

6. Double‐click the Installers list item.

7. The required file resides in the folder named
CA_Workload_Automation_Agent_R11_3_4_for_Databases.

Double‐click the CA_Workload_Automation_Agent_R11_3_4_for_Databases list item.


Lab Guide

Step Action
8. You will copy the file and place it in the folder named ESPSystemAgent.

Right‐click the database.pak list item.

Step Action

10. You will now navigate to the required folder.

Click the Back button.


Lab Guide

Step Action
11. Click the Back button.

12. Double‐click the WorkloadAutomation_R11.3_SP3 list item.

13. Double‐click the ESPSystemAgent list item.

14. Right‐click the whitespace.



Lab Guide

Step Action
16. The required DB plug‐in installation files are now in place. You will install the DB plug‐in.

Because the installation command text requires the path to this folder, you will copy the
Location field value.

Click in the Location field.

17. Right‐click in the Location field.


19. Click the Back button.

20. You will now open the ESPSystemAgent folder in a terminal to install the DB plug‐in.

Right‐click the ESPSystemAgent list item.

21. Click the Open In Terminal list item.


Lab Guide

Step Action
22. Before you install the DB plug‐in, you must determine if the agent is running.

You will enter the agent status command.

Enter the desired information into the Command Line field. Enter "cat status".


Lab Guide

Step Action
23. Press [Enter].


Lab Guide

Step Action
24. From the returned value, you can see that the agent is running.

The agent must be stopped before installing the DB plug‐in.

You will issue the command to stop the agent.

Enter the desired information into the Command Line field. Enter "./cybAgent ‐s".

Step Action
25. Press [Enter].


Lab Guide

Step Action
26. For verification purposes, you will enter the agent status command.




Lab Guide

Step Action
27. Press [Enter].


Lab Guide

Step Action
28. The agent is stopped; you can proceed with the DB plug‐in installation.

You will begin by issuing the clear command to start with a fresh terminal.

Enter the desired information into the Command Line field. Enter "clear".

Step Action
29. Press [Enter].


Lab Guide

Step Action
30. To install the DB plug‐in, you will issue the PluginInstaller command.

The command syntax is:
PluginInstaller [package name] [package location]

You will begin by typing the command and the package name parameter.

Enter the desired information into the Command Line field. Enter "./PluginInstaller
database.pak".


Lab Guide

Step Action
31. To enter the location parameter, you will use the directory path that you copied earlier.

The directory path is:
/opt/CA/WorkloadAutomation_R11.3_SP3/ESPSystemAgent

Right‐click in the Command Line field.


33. Press [Enter].


Lab Guide

Step Action
34. The installation process starts by defining the database type.

In this scenario, the database is Oracle.

Enter the desired information into the Command Line field. Enter "1".


Lab Guide

Step Action
35. Press [Enter].


Lab Guide

Step Action
36. You now need to define the database host name.

In this scenario, the host name is CAWA‐DBHost.

Enter the desired information into the Command Line field. Enter "CAWA‐DBHost".

Step Action
37. Press [Enter].


Lab Guide

Step Action
38. Next, you define the port that the database communication port number.

In this scenario, the database is communicating on Oracle default port number 1521.

Enter the desired information into the Command Line field. Enter "1521".


Lab Guide

Step Action
39. Press [Enter].


Lab Guide

Step Action
40. Now, enter the system ID value.

In this scenario, the ID is orcl.

Enter the desired information into the Command Line field. Enter "orcl".

Step Action
41. Press [Enter].


Lab Guide

Step Action
42. The database default user ID and password must be entered next.

The default user name is DEUSER; the password is caeducation.

Enter the desired information into the Command Line field. Enter "DEUSER".



Lab Guide

Step Action
43. Press [Enter].


Lab Guide

Step Action
44. Enter the desired information into the Command Line field. Enter "caeducation".

Step Action
45. Press [Enter].


Lab Guide

Step Action
46. For verification purposes, the password must be entered again.

Enter the desired information into the Command Line field. Enter "caeducation".


Lab Guide

Step Action
47. Press [Enter].

Step Action
48. The final parameter to define is whether to set up an alias.

In this scenario, you will ensure that an alias is set up.

Enter the desired information into the Command Line field. Enter "y".


Lab Guide

Step Action
49. Press [Enter].


Lab Guide

Step Action
50. The installer ran successfully, the DB plug‐in is installed.

Before restarting the agent, you will update the agentparm.txt file.

Enter the desired information into the Command Line field. Enter "exit".

Step Action
51. Press [Enter].
52. The agentparm.txt file resides in the ESPSystemAgent directory.

Double‐click the ESPSystemAgent list item.

53. Double‐click the agentparm.txt list item.


Lab Guide

Step Action
54. You will scroll down the file to view additions after the DB plug‐in was installed.

55. From the original installation, you can see the plug‐in components that were installed.

56. Under Added by Installer for database, you can see the information that was added when
the DB plug‐in was installed.

The first line shows the default alias name that was added.

You will change the default name to AGENT_SQL.

Click in the communication.alias_1 field.

57. Enter the desired information into the agentparm.txt field. Enter "AGENT_SQL".

58. You will save and close the updated text file.



60. Next, you will open the ESPSystemAgent directory in a terminal to start the agent.

Click the Back button.

61. Right‐click the ESPSystemAgent list item.

62. Click the Open in Terminal list item.


Lab Guide

Step Action
63. You will issue the command to start the agent in its own service.

Enter the desired information into the Command Line field. Enter "./cybAgent ‐a".



Lab Guide

Step Action
64. Press [Enter].


Lab Guide

Step Action
65. You will now verify that the agent successfully started.


Step Action
66. Press [Enter].


Lab Guide

Step Action
67. The returned message verifies that the agent started.

Enter the desired information into the Command Line field. Enter "exit".


Lab Guide

Step Action
68. Press [Enter].


Lab Guide

Step Action
69. The DB plug‐in is installed.

You will now navigate to the CAWA‐Client environment to install the DB agent using the
Desktop Client.



Step Action
71. To add the DB agent to CA Workload Automation DE, you will start the Desktop Client.



Lab Guide

Step Action
logged‐in user.


Logging in with ADMIN rights enables you to successfully add an agent.



Step Action
74. Agents are managed on the Topology view.




Lab Guide

Step Action
75. The Topology view appears displaying server information. Notice that the CAWA‐DBHost
server has a status of Running in standby.

Currently, there are two agents installed; you will add the DB agent.

Click the Agents (2) tree item.

Step Action
76. Click the New Agent button.

77. The agent type that you select will determine the fields that will appear to define the
agent.

Click the Select the agent type to define: list.

78. For this scenario, you will select Database to define a DB agent for the DB plug‐in that you
installed.

Click the Database list item.



Lab Guide

Step Action
79. To better view the New Agent view, you will maximize it.


80. You begin by defining a name for the agent.

Click the *Name Parameter Value cell.

81. You will enter the same agent name that you entered in the agentparm.txt file,
AGENT_SQL.

Enter the desired information into the *Name Parameter Value field. Enter
"AGENT_SQL".

82. The address is the TCP/IP or DNS name of the location where the agent was installed.

Click the *Address Parameter Value cell.

83. Enter the desired information into the *Address Parameter Value field. Enter "CAWA‐
DBHost".

84. Now, you need to enter the unique port number.

Click the *Port Parameter Value cell.

85. Because this agent was installed as a plug‐in and not as a separate agent, you need to use
the same port number as the agent you installed the plug‐in on, 17520.

Enter the desired information into the *Port Parameter Value field. Enter "17520".

86. Verify that the encryption key value is correct. For this scenario, the value shown is
correct.


You will now save the new agent details.



Lab Guide

Step Action
87. After saving the agent, it appears in the Topology view.

Initially, the agent will appear with an inactive status, but that will change after the server
recognizes it.

Press [Enter].
88. After the server recognizes the agent, the status changes to active.




90. In this lab, you added the DB plug‐in.
End of Procedure.



Lab Guide

Lab 7‐3 Run an SQL Job with the DB Plug‐in
In this lab, you will run an SQL job with the DB plug‐in.

Step Action
1. You will use the DB plug‐in that you installed and configured in the previous lab.

The DB plug‐in enables you to perform work on the installed database.

To run an SQL job and then monitor it, you will start the Desktop Client.



Lab Guide

Step Action
logged‐in user.

In this scenario, you will not use the displayed connection information but instead log in
with SCHEDMASTER rights and to CAWA‐Server.

Logging in with SCHEDMASTER rights enables you to successfully manage the job.




5. To manage an application, you use the Define perspective.


6. For this scenario, instead of creating an application for the SQL job, you will open an
application that was created for you.

Click the Open button.


Lab Guide

Step Action
7. The application resides in the InstallMedia folder.

You will navigate to the required folder.

Click the SYSTEM (C:) tree item.



Lab Guide

Step Action
8. Double‐click the InstallMedia list item.

9. The application is contained in the file named SQL_TEST_APP.xml.

The Desktop Client enables you to create an application and export it in .xml format,
which enables other programmers to create the required applications and share them
easily.

Click the SQL_TEST_APP.xml list item.

10. Click the Open button.


Lab Guide

Step Action
11. The application appears in the Application Workspace area. The application contains a
single job, an SQL job.

Also notice the event that was created with the application. You will use the event to
trigger the application.

You will open the application to view the details.



Lab Guide

Step Action



Lab Guide

Step Action
13. If required, when you open an imported job, you can change the details, as you would for
any workload object, to match your requirements.

For example, the application name can be changed, as can most options available in the
Options tree.

You will identify that the correct agent was assigned to the application.


14. The agent name that appears is the same as the one that was defined when the DB plug‐in
was installed.


15. The SQL command that will run appears in the *SQL command: field.

This command will search the database for the version of CA Workload Automation DE.

For this workload object to execute normally and be determined as successful, the
returned version must equal that of the one defined in the Success criteria field.


16. To ensure the required agent is available, you will navigate to the Topology view.



Lab Guide

Step Action

18. The agent that is defined in the application is the same as the one that appears under
Agents in this view.

Because you are logged in with SCHEDMASTER rights, you are not able to determine if the
agent is active.

Right‐click the AGENT_SQL tree item.

19. You are able to view the agent definition.

Click the View Definition list item.



Lab Guide

Step Action
20. To better view the Agent_SQL view, you will maximize it.


21. You can see the agent details and will now return to the application.


22. Click the Define button.


Lab Guide

Step Action
23. You will now save and upload the application before executing it.

To perform actions against the application, you can use the Save and Upload buttons on
the toolbar, or you can click in the Application Workspace whitespace and then right‐click
to display the different options.




Lab Guide

Step Action
25. Click the Save list item.


Lab Guide

Step Action

Step Action
27. Click the Upload list item.


Lab Guide

Step Action
28. It is best practice to add a comment before uploading an application.

Enter the desired information into the Comments field. Enter "Added an SQL job".


30. You will now trigger the Date‐Time/Manual event for the application.

Click the SCHEDMASTER.SQL_TEST_APP list item.



Lab Guide

Step Action
32. The Trigger Event dialog appears.

You will select the Submit Application on hold option to permit the application to be
triggered so that it will be visible in the monitoring perspective, but placed on hold.

Click the Submit Application on hold option.


34. You will now monitor and control workload for the application.

You will monitor and control active workload in the Monitor perspective with the
Application Monitor view.


35. Click the Application Monitor tab.


Lab Guide

Step Action


37. In this scenario, you will subscribe to all applications on the server, no matter their state.



39. One generation of the triggered SQL application appears.

You will open the generation.


40. Double‐click the SQL_TEST_APP.1, Applhold, 1 Jobs tree item.

41. The application was triggered on hold, which you can see as the one job has a state of
APPLHOLD.

You will now manually release the held application.

Right‐click the SQL_TEST_APP.1, Applhold, 1 Jobs tree item.




Lab Guide

Step Action
43. You must add a reason why you are issuing the release command because when the
application was set up, the Require reason for job commands option was selected.

Enter the desired information into the Reason: field. Enter "Time to run job".

44. After you click OK, you will watch the application run to completion.


45. Immediately after releasing the held application, the job starts executing.

You can see the job icon in the workflow view changed from an orange border, which
means held, to yellow, which means ready.

Press [Enter].


Lab Guide

Step Action
46. After a few seconds, the workflow view updates to show the job is complete.

This means the SQL command was executed successfully; the returned valued matched
what was expected.

You will view the job details.



Lab Guide

Step Action
47. Click the Details list item.



Lab Guide

Step Action
48. The Details dialog confirms that the job was successful.





52. In this lab, you ran an SQL job with the DB plug‐in.
End of Procedure.



Lab Guide

Lab 7‐4 Add an Agent Group
In this lab, you will add an agent group.

Step Action
1. To add an agent group, you will start the Desktop Client.

Defining agent groups enables you to distribute workload between similar platforms and
operating systems.



Lab Guide

Step Action
logged‐in user.

In this scenario, you will log in with ADMIN rights and to CAWA‐Server.

Logging in with ADMIN rights enables you to successfully add an agent group.




5. You add agent groups using the Topology view.



Lab Guide

Step Action

7. An agent group is a logical grouping of agents that can be used for workload assignments.
They can be used for load balancing or to run all the agents of the given agent group task.

You will add a new group.

Right‐click the Agent Groups tree item.

8. You can add a new group by clicking the New Agent Group list item or by clicking Add
Agent Group at the top of the Topology view.

Click the New Agent Group list item.


Lab Guide

Step Action
9. To better view the New Agent Group view, you will maximize it.


10. You begin by defining a name for the agent group.

Click in the *Group name: field.

11. Enter the desired information into the *Group name: field. Enter
"CLASS_AGENT_GROUP".

12. In the Type of agents field, you will leave the default value of UNIX. The other option is
Windows.

Because an agent group is a logical grouping of agents, you next need to define which
agents will be included in the group.

For this scenario, there are only two agents from which to select. You will select both.

Click the PREFERRED_AGENT list item.

13. Press the [Ctrl] key and click the STANDBY_AGENT list item.

14. Click the Add > button.

15. The Selection criteria list values enable you to determine load balancing characteristics.

Click the Selection criteria: list.



Lab Guide

Step Action
16. The agent group defined on a job for load balancing supports three algorithms:
‐ CPU
‐ Random
‐ Round Robin

For this scenario, you will leave the default value.

Click the CPU list item.

17. You will now save the new agent group definition details.


18. The agent group is now ready for workload assignments.



20. In this lab, you added an agent group.
End of Procedure.



Lab Guide

Lab 8‐1 Define a Calendar
In this lab, you will define a calendar.

Step Action
1. To work with a calendar, you will start the Desktop Client.


logged‐in user.

In this scenario, you will change the default login information. You will log in as
SCHEDMASTER.

Logging in with SCHEDMASTER rights enables you to successfully manage calendars.



Lab Guide

Step Action


5. Calendar definitions are under the Services perspective in the Calendar view.


6. Calendars enable you to create scheduling criteria that are specific to your scheduling
needs.

Double‐click the Calendars tree item.

7. The CA Workload Automation DE default calendar is named SYSTEM.

Unless otherwise stated, when an application is scheduled to execute, the system
calendar is used to define run times. Because of this, the system calendar can be edited
but not deleted.

All custom calendars can be deleted.

Double‐click the SYSTEM list item.

8. The system calendar appears in edit mode.

By default, workdays in the system calendar are defined as Monday through Friday. If you
define an application to run on all workdays, the days defined in the calendar will be used.

Currently, there are no holidays or special days defined.



Lab Guide

Step Action
9. You will create a new calendar.

User‐defined calendars are used to create unique scheduling criteria.


10. You begin by uniquely naming the calendar.

The name cannot be a keyword that is used in CA Workload Automation DE.

Enter the desired information into the *Calendar name: field. Enter "SCHEDMASTER".

11. The days of the week defined in the calendar are used as workdays when scheduling.

By default, the days of the week defined in the calendar are Monday through Friday.

For this calendar, you will define the workdays as Tuesday through Saturday.

Click the Mon option.

12. Click the Sat option.

13. You will now define a holiday.

A holiday is a non‐workday with a special significance for scheduling. It is generally a day
that is observed company‐wide where no processing will take place.


14. You will define Christmas Day as a holiday in the calendar.

You begin by adding the name of the holiday. The name will be used as a custom
scheduling term when defining an application.

Enter the desired information into the Holiday name field. Enter "CHRISTMAS_DAY".


Lab Guide

Step Action
15. Under Occurrences, you define the holiday date.

Because Christmas Day is always December 25, you will define the specific date.

Click the th option.

16. Enter the desired information into the th field. Enter "25".

17. Under Day of Month, you further define the date and month of the holiday. Rather than
identify a day of the week, you will specify the actual day that the date falls on.

Click the day option.

18. Next, you identify the month that the holiday occurs.

Click the of list.

19. Click the December list item.

20. Under Repeat, you identify how many years you want the holiday repeated. The limit is 99
years.

Click in the years field.


Lab Guide

Step Action
21. You will define the holiday to repeat for the next 10 years.

Enter the desired information into the years field. Enter "10".


23. The new holiday is defined and each occurrence appears in the Holidays area, with the
actual date, month, and year.


24. You will define another holiday in the calendar.


25. You will define a holiday for New Year's Day.

Enter the desired information into the Holiday name field. Enter "NEW_YEARS_DAY".

26. Because the holiday occurs on January 1, under Occurrences, you will leave the default
selection.

Next, you will define the Day of Month attributes.

Click the day option.



28. Enter the desired information into the years field. Enter "10".



Lab Guide

Step Action

You will define one last holiday in the calendar.


31. You will define a holiday for Memorial Day.

Enter the desired information into the Holiday name field. Enter "MEMORIAL_DAY".

32. Memorial Day always falls on the last Monday of May.

Click the Last option.

33. You will leave the default specific day value of Monday and now select the correct month
from the list.

Click the of list.

34. Click the May list item.



36. Enter the desired information into the years field. Enter "10".



Lab Guide

Step Action


39. You will save the calendar.


40. The new calendar appears in the Calendars view.

Now, if you define an application to use the SCHEDMASTER calendar, you can define the
application to run, or not run, on the holidays that you defined.




43. In this lab, you defined a calendar.
End of Procedure.



Lab Guide

Lab 8‐2 Define a Special Day
In this lab, you will define special days in a calendar.

Step Action
1. To work with a calendar, you will start the Desktop Client.


logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully manage calendars.



Lab Guide

Step Action

Step Action
4. Because the Services perspective was opened the last time the SCHEDMASTER user logged
out, it appears by default.

Double‐click the Calendars tree item.


Lab Guide

Step Action
5. You will add special days to the calendar named SCHEDMASTER.

A special day is a user‐defined day with special significance for scheduling.

Double‐click the SCHEDMASTER list item.

6. You will now define a special day.


7. You will create a special day named RANDOMDAY.

Enter the desired information into the Special day name field. Enter "RANDOMDAY".

8. You will use the calendar function to add the date.

Click the Starting Date Calendar button.


Lab Guide

Step Action
9. Click the 20 cell.

10. You will define this date to repeat for 10 years.

Click the Repeat option.

11. Click in the times field.

12. Enter the desired information into the times field. Enter "10".

13. Click the years option.

14. The special day is defined.



Lab Guide

Step Action
15. You can see under Special Days that the date was added and spans 10 years.



Lab Guide

Step Action
16. You will now add another special day.


17. This special day will be named BIRTHDAY and defined as December 13.

Enter the desired information into the Special day name field. Enter "BIRTHDAY".

18. Click the Starting Date Calendar button.

19. Click the Next Month button.

20. Click the Next Month button.



Lab Guide

Step Action

22. You will define this date to repeat for 10 years.




25. Instead of using the predefined time periods beside every, you can add free‐form text to
define the period.

Click the free form option.

26. Click in the free form field.

27. Enter the desired information into the free form field. Enter "yearly".

28. The special day is defined.


29. To create more viewing room, you can maximize the view.



Lab Guide

Step Action
30. You can see under Special Days that the birthday date was added.

You can also add other dates to an existing special day and they are considered as the
same special day.


31. You will add another date to the special day named RANDOMDAY.

Enter the desired information into the Special day name field. Enter "RANDOMDAY".

32. Previously, you defined this special day with a date of October 20 and spanning 10 years.

Now, you will also define August 17 as a special day date.

Click the Starting Date Calendar button.

33. Click the Previous Month button.

34. Click the Previous Month button.


36. You will define this date to repeat five times, every two months.



Lab Guide

Step Action


39. Click in the every field.

40. Enter the desired information into the every field. Enter "2".


Step Action


Lab Guide

Step Action
43. You can see under Special Days that the newly defined RANDOMDAY date was added to
the calendar.

You will scroll down to view all the defined special days.



45. Now that the special days are defined, you will save the calendar.



Lab Guide

Step Action
46. You will close the calendar and then open an application to test the days defined in the
calendar.

Take note of the names of the holidays and special days; the spelling of the names is
important because you will add the names to the scheduling criteria for the application.



48. You will download the application named PAYROLL.


49. Click the PAYROLL list item.




Lab Guide

Step Action
51. The application appears in the Application Workspace area. The application is comprised
of eight UNIX jobs.

Before simulating the application using the new calendar, you will view the current
schedule defined at the application level.



Lab Guide

Step Action



Lab Guide

Step Action
53. The application is defined to run daily.


54. You will now define the new calendar for the Date‐Time/Manual event.

Double‐click the SCHEDMASTER.PAYROLL list item.

55. By default, the System calendar is always used for scheduling unless you define another
calendar.

Click the Calendar 1: list.

56. You will define this event to use the custom calendar.

Click the SCHEDMASTER list item.


58. After you make a change to the application, you must save the application and then
upload it.



Lab Guide

Step Action
59. Click the Save As... list item.


Lab Guide

Step Action
60. You will save the application to the desktop.

Click the Favorites tree item.

Step Action
61. Double‐click the Desktop list item.

62. To view more of the objects on the desktop, you will scroll down.


63. Previously, this application had been saved to the desktop; you will overwrite the file.




Lab Guide

Step Action
65. You will upload the application and then simulate it.



Lab Guide

Step Action


Enter the desired information into the Comments field. Enter "Added SCHEDMASTER
calendar".


69. You will now simulate the Date‐Time/Manual event.




Lab Guide

Step Action
71. You will use the holiday named CHRISTMAS_DAY to simulate the application.

Enter the desired information into the Schedule criteria: field. Enter "CHRISTMAS_DAY".


Step Action
73. Only three jobs are scheduled to run on Christmas Day.

Notice that the job named Third_Job did not run, even though it is defined to run on
Friday's, and the day defined in the simulation is a Friday. The job did not run because it is
also defined to not run on holidays.



Lab Guide

Step Action
74. You will view the schedule criteria defined in the job named Third_Job.

Double‐click the Third_Job graphic.

Step Action
75. The Run Frequency definition identifies when the job will run and not run.

You use holidays and special days to identify when the job will run or not run.


76. You will simulate the application again using different schedule criteria.



Lab Guide

Step Action
77. You will simulate the application to run on Friday.

Enter the desired information into the Schedule criteria: field. Enter "friday".


79. Notice that the job named Third_Job will now run.

This is because it is scheduled to run on Fridays and the schedule criteria defined for the
simulation did not identify that the Friday was a holiday.




Lab Guide

Step Action
80. You will add special day schedule criteria to the job named Seventh_Job.

Double‐click the Seventh_Job graphic.

Step Action
81. Currently, this job is defined to run daily.

You will define a do‐not‐run statement.

Click the Add Do Not Run button.



Lab Guide

Step Action
83. You will define this job to not run on days in the calendar that are defined as
RANDOMDAY.

Enter the desired information into the When field. Enter "RANDOMDAY".


Step Action
85. After making the change to the application, you will save it and then upload it before
simulating it.




Lab Guide

Step Action
87. Click the Save list item.


Lab Guide

Step Action

Step Action


Lab Guide

Step Action
90. Remember, it is good practice to always add a comment that defines the changes made to
an application before uploading it.

Enter the desired information into the Comments field. Enter "Added random day
dependency to job named Seventh_Job".


92. You will now simulate the event.




Lab Guide

Step Action
94. You will add a special day schedule criteria to the event, RANDOMDAY.

Enter the desired information into the Schedule criteria: field. Enter "randomday".


96. The job named Seventh_Job does not appear due to the schedule criteria restraint.


97. You will simulate the event again using different special day criteria.


98. You will add one of the dates that the RANDOMDAY special day was defined as.

Enter the desired information into the Schedule criteria: field. Enter "aug 17th 2015".


100. Again, due to the defined job schedule criteria, the job named Seventh_Job was not
scheduled to run, even though you did not simulate the application using the special day
name. The calendar date you added is defined as a special day.


101. You will close the PAYROLL view and exit the Desktop Client.




Lab Guide

Step Action

104. In this lab, you defined special days in a calendar.
End of Procedure.



Lab Guide

Lab 9‐1 Define a Variable
In this lab, you will define a global variable.

Step Action
1. To work with global variables, you will start the Desktop Client.

By managing variables, you can streamline and simplify applications.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully manage global variables.



4. Global variables are managed in the Services perspective, in the Global Variable view.



Lab Guide

Step Action
5. Double‐click the Global Variables tree item.

Step Action
6. Global variables enable you to store information that you can reuse across applications.
Global variables are stored in the relational database for CA Workload Automation DE.

Currently, there are no global variables defined in the system.

You will create a new global variable.



Lab Guide

Step Action
7. You start by defining the variable name. The name should be meaningful.

Enter the desired information into the *Variable name: field. Enter "agentname".

8. You will leave the default value in the Variable context field.

Next, you need to define the variable value. Changes to the value of a variable are
dynamic.

Enter the desired information into the Value: field. Enter "anyagent".

9. The global variable is defined; you will now save it.


10. The global variable appears in the Global Variables view.

You have defined a global variable that can be changed multiple ways: online, through
JavaScript, or programmatically. When required, users can change the value to whatever
they need it to be.

You will create another global variable.


11. You will start by defining the variable name.

Global variable names can be identical, providing the variable context is different.

You will define this global variable with the same name as the previous global variable.


12. To make the global variable unique, you will define a different variable context value.

Enter the desired information into the Variable context: field. Enter "DEVL".


Lab Guide

Step Action
13. Next, you need to define the variable value.

Enter the desired information into the Value: field. Enter "STANDBY_AGENT".




You will create one final global variable.


16. You will start by defining the variable name.

You will define this global variable with the same name as the previous global variables.


17. To make the global variable unique, you will define a different variable context value.

Enter the desired information into the Variable context: field. Enter "PROD".

18. Lastly, you need to define the variable value.

Enter the desired information into the Value: field. Enter "PREFERRED_AGENT".




Lab Guide

Step Action

You will close the views for the three global variables.




23. With the three global variable definitions, the one global variable name, agentname, will
result in three different values depending on the logged‐in user. If the global variable was
run under the DEFAULT user ID, the value used will be anyagent, which does not exist. If
the agentname variable was to run under the DEVL user ID, the value used would be
STANDBY_AGENT. And if it was run under the PROD ID, the variable would return the
value of PREFERRED_AGENT.

This is how a same‐named global variable can be created but have different values
depending on the context.

You will close the Global Variables view and the Desktop Client.




26. In this lab, you defined global variables.
End of Procedure.



Lab Guide

Lab 9‐2 Define CA Workload Automation DE Resources
In this lab, you will define CA Workload Automation DE resources.

Step Action
1. To work with CA Workload Automation DE resources, you will start the Desktop Client.

Working with CA Workload Automation DE resources enables you to automatically control
and regulate workload.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully manage resources.


Step Action
4. Because the Services perspective was opened the last time the SCHEDMASTER user was
logged in, it appears by default.

Resources are defined in the Services perspective, in the Resources view.

Double‐click the Resources tree item.



Lab Guide

Step Action
5. A resource is a job dependency that can be quantified by specifying its availability count.

Currently, there are no resources defined in the system.

You will define a resource.


6. You start by defining the resource name. The name should be meaningful.

Enter the desired information into the Resource description: field. Enter "DRIVEUNITS".


Lab Guide

Step Action
7. For the Resource type: option, you can define the resource as one of three types:
‐ Depletable
‐ Renewable
‐ Threshold

A depletable resource is a consumed resource. When the server submits a job, the job
permanently removes the consumed units of the depletable resource from the resource
pool. When the resource depletes, it can be replenished for other jobs to use.

A renewable resource is a borrowed resource. When the server submits a job, the job
removes the borrowed units of the renewable resource from the resource pool. The
resource units are not permanently used up, but instead are returned to the resource pool
when the job completes or fails. The job only borrows the resource units so it can run
successfully.

A threshold resource is a sizing resource and works more like a switch.

You will define this resource as Renewable.

Press [Enter].
8. You will define the resource with an availability of one and a maximum availability of five.

The Maximum availability: field, which is only available for renewable resources, sets the
upper limit.

Enter the desired information into the Maximum availability: field. Enter "5".
9. In the Resource description field, you add a description to help define the resource.

Enter the desired information into the Resource description: field. Enter "Renewable
resource".
10. The resource is defined; you will now save it.

Note: After you click Save, you cannot modify the Resource type: option. If you need to
modify the option, you must delete the resource and then create a new one.



Lab Guide

Step Action
11. The resource appears in the Resources view.

Before you create another resource, you will close the DRIVEUNITS view.


12. Click the New button.

13. You start by defining the resource name.

Enter the desired information into the Resource description: field. Enter
"PRODBMPREGION".
14. You will define this resource with the Threshold type.

A threshold resource is used by jobs that use a specific number of resource units to run.

When defined with a Threshold type, a job does not consume or borrow resource units
from the resource pool while it runs. For example, if the resource quantity is set to two,
the server submits all jobs that require two or fewer units.

The server does not submit any job requiring three or more units. It sizes the job against
the current level of the threshold resource. For example, you can use a threshold resource
to represent a period when you run low‐priority jobs.

Click the Threshold option.

15. The availability can be zero or one.

For this resource, you will define it with zero availability.

Enter the desired information into the Availability: field. Enter "0".
16. You will now add a description to help define the resource.

Enter the desired information into the Resource description: field. Enter "Threshold
resource".
17. The resource is defined; you will now save it.



Lab Guide

Step Action
18. The resource appears in the Resources view.

You will close the PRODBMPREGION view.


19. There are now two resources available, a renewable resource named DRIVEUNITS and a
threshold resource named PRODBMPREGION.

To view the resource details, you double‐click a resource row in the view.

Double‐click the DRIVEUNITS list item.

21. You will close the Resources view and the Desktop Client.




24. In this lab, you defined CA Workload Automation DE resources.
End of Procedure.



Lab Guide

Lab 10‐1 Define a JavaScript
In this lab, you will define a JavaScript.

Step Action
1. To work with JavaScripts, you will start the Desktop Client.

To extend the capabilities of CA Workload Automation DE, you need to gain a basic
understanding of the JavaScript components.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully define a JavaScript and
then use the JavaScript in an application.



4. You can create JavaScripts within applications or in the central repository.
‐ Within applications, use the JavaScript tab under Application Properties to define,
import, or export scripts. You then must identify the JavaScript to run, the location, the
specific jobs, and when to run it.
‐ In the central repository, use the JavaScripts link on the Services perspective. Using this
method enables you to reuse the same script in different applications and minimize
maintenance.

Double‐click the JavaScripts tree item.

5. You will begin by searching the system.

Click the Search button.


Lab Guide

Step Action
6. Currently, there are no JavaScripts defined in the system.

By using JavaScript within your applications, you can take advantage of advanced
scheduling features.

You will create a new JavaScript.


7. You will define this JavaScript to cause a change to the job submission time based on the
application running on the last day of the month.

You start by defining the JavaScript name. The name should be meaningful.

Enter the desired information into the *JavaScript name: field. Enter
"EOMTIMECHANGE".

8. You have the option to manually enter a JavaScript or import one into the JavaScript
Editor.

In this lab, you will manually enter a JavaScript.

You will enter a conditional logic statement, which is a set of commands that runs if a
specified condition is true. JavaScript supports two conditional statements:
‐ In an if…else statement, when a specified condition is true, the if statement performs the
block of code defined within the if portion.
‐ A switch statement enables a script to evaluate an expression and then compare it to the
values for each case within the structure.

Press [Enter].
9. You will start by entering the first line of a JavaScript if statement.

The statement you enter will define that on the last workday of the month, the
submission time of a job will change from 18:00 to 20:00.

Enter the desired information into the JavaScript Editor field. Enter "if(today('last
workday of month')) {".

10. Press [Enter].


Lab Guide

Step Action
11. You will now enter the next line of the statement, which uses the CA Workload
Automation DE keyword earlysub, which submits a job at a specified time.

You will define the time as 18:00.

Enter the desired information into the JavaScript Editor field. Enter
"APPL.earlysub='6pm';".

12. Press [Enter].
13. Next, you will enter the else portion of the statement.

Enter the desired information into the JavaScript Editor field. Enter "} else {".

14. Press [Enter].
15. You will begin to enter the second part of the logic statement, which will define the
alternate time the job will be submitted.

Enter the desired information into the JavaScript Editor field. Enter "APPL.".

16. The JavaScript Editor can also help you build scripts. After entering a partial command, a
help list might appear that will list the available commands that match the command you
entered and their syntax.

In this scenario, you will continue to manually enter the script.

Enter the desired information into the JavaScript Editor field. Enter "earlysub=`8pm`;".

17. Press [Enter].


Lab Guide

Step Action
18. You will now add the ending JavaScript statement.

Enter the desired information into the JavaScript Editor field. Enter "};".

19. After you enter a JavaScript statement, you can use the built‐in syntax checker to help
ensure the script was entered correctly.

Keep in mind that this function will only check the syntax of the entered JavaScript, not
the program or function that you want the script to perform.

Click the Check Syntax.. button.

20. The script is syntactically correct.


21. You will now change the script to cause a known error to see how the syntax checker
function performs.

Click in the JavaScript Editor field.

23. Click the Check Syntax.. button.

24. An error message dialog appears stating that there is an error.

Notice that the message states the error resides in line 5. You know that the error exists in
line 3.

You need to keep in mind that the syntax checking function checks the validity of the
complete script, and in this case, the missing brace causes line 5 to be in error.

You will close the message dialog and correct the error.



Lab Guide

Step Action
25. Click in the JavaScript Editor field.

26. Enter the desired information into the JavaScript Editor field. Enter "{".

27. Click the Check Syntax.. button.

28. The JavaScript is now syntactically correct.


29. The JavaScript has been defined and you will now save it.


30. The JavaScript appears in the JavaScripts view, available for use.

You will navigate to the Define perspective and then open an application to execute the
JavaScript.







Lab Guide

Step Action
of eight UNIX jobs.

The first step to test the JavaScript is to add a time dependency to a job in the application.

Because the job named First_Job is scheduled to run daily, which means the job will run
no matter which day you select to simulate the event, you will add the time dependency
to the job.


Step Action



Lab Guide

Step Action
36. Click the Time Dependencies tree item.


Lab Guide

Step Action
37. You will add the APPL.earlysub variable, which defines the time the job will be submitted,
to the Do not submit before field.

Enter the desired information into the Do not submit before: field. Enter
"%APPL.earlysub".


39. Now, you will add the JavaScript that you previously defined to the Date‐Time/Manual
event for this application.

Right‐click the SCHEDMASTER.PAYROLL list item.




Lab Guide

Step Action
41. Click the JavaScript tree item.


Lab Guide

Step Action
42. To specify the JavaScript the event will use, you must click Add.

Click the Add button.

43. Click the JavaScript Name cell.

44. You can enter the name of the JavaScript in the JavaScript Name field, or use the drop‐
down list to view all the scripts defined within the application and the central repository.

Enter the desired information into the JavaScript Name field. Enter "EOMTIMECHANGE".

45. Press [Enter].
46. The definition of the selected JavaScript appears in the Definition of selected JavaScript
pane.



Lab Guide

Step Action
upload it.



Step Action


Lab Guide

Step Action
50. You will save the application to the desktop.

Click the Favorites tree item.



Lab Guide

Step Action
51. Double‐click the Desktop Shortcut list item.

52. Click the PAYROLL.xml list item.

53. Previously, this application was saved to the desktop.

You will overwrite the file.



55. You will upload the application and then simulate it.



Lab Guide

Step Action


Lab Guide

Step Action

Enter the desired information into the Comments field. Enter "Added JavaScript to
application for lab 10‐1".


59. You will now simulate the Date‐Time/Manual event.



61. You will use the first workday of the month to simulate the application.

Enter the desired information into the Schedule criteria: field. Enter "first workday of
month".


63. The job named First_Job has been selected to execute.

Notice the time stamp in the job definition panel, beside the Do not submit before line.

If the application was set to run on the first workday of the month, this job will not be
submitted to execute before 8:00 p.m.

Press [Enter].

65. You will again simulate the event, but with a different day defined.



Lab Guide

Step Action
66. This time, you will use the last workday of the month to simulate the application.

Enter the desired information into the Schedule criteria: field. Enter "last workday of
month".


68. Again, the job named First_Job has been selected to execute.

However, notice the time stamp in the job definition panel, beside the Do not submit
before line.

Because of the JavaScript and the fact the application was set to run on the last workday
of the month, this job will now not be submitted to execute before 6:00 p.m.

Press [Enter].

70. Finally, you will simulate the event with today`s date.



72. Providing today is not the last workday of the month, the Do not submit before time value
will be 8:00 p.m.

If it is the last workday of the month, the Do not submit before time value will be 6:00 p.m.

Press [Enter].




Lab Guide

Step Action


77. In this lab, you defined a JavaScript.
End of Procedure.



Lab Guide

Lab 11‐1 Define Notifications
In this lab, you will define a notification.

Step Action
1. To work with notifications, you will start the Desktop Client.

You can define notifications based on your business requirements, enabling you to
respond properly to workload outages.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully define an email
notification in an application.



4. Notifications enable you to monitor job progress automatically. Then, you can notify users
or take action when the job reaches a certain state or condition.

Notifications can be defined at the application or job level. Job‐level definitions override
the application‐level definitions for that notification type.

Applications or jobs can have multiple notifications defined for more than one monitor
state.

You will open an existing application to create an email notification.






Lab Guide

Step Action
of eight UNIX jobs.

You will open the Application properties dialog to create a notification.



Lab Guide

Step Action


Lab Guide

Step Action
9. Before creating a notification, you will remove the Require reason for job commands
option.

Click the Require reason for job commands option.

Step Action
10. You will now create a notification.



Lab Guide

Step Action
11. CA Workload Automation DE has three default notification types:
‐ Email
‐ Alerts
‐ SNMP Traps

In a previous lab, you defined an email notification for this application. You will select the
notification and then delete it.

Click the Email Notification list item.

12. Click the Remove button.

13. You will set up an alert as an email notification so that if an alert occurs, an email is sent to
notify users.

Because the Email tab is selected by default, to create a new notification, you can click
New.



Lab Guide

Step Action
14. The notification will be set up specifically to monitor for, and respond to, failed jobs.

Click the Failed option.

15. Next, you complete the email information.

You begin by defining to whom the email is sent.

You can add email addresses in the To: field, separated by semicolons, or you can add an
email group name.

In this scenario, you will add an email address.

Enter the desired information into the To: field. Enter "user@CAWADE.org".

16. Click the Add button.

17. The Subject line contains predefined text that includes symbolics defining specific job and
application attributes.

You have the option to not use this text by clearing the Use default subject option.

You can also append text to the email by entering text in the Message field.

Enter the desired information into the Message: field. Enter "The job named,".

18. You are able to include built‐in symbolics in the message text.




Lab Guide

Step Action
19. Point to the Built‐in Symbolics list item.
20. You can add application or job symbolics.

Point to the Job list item.
21. A list of all built‐in job symbolics appears.

You will begin by adding the name of the job that triggered the notification, based on the
monitor state that you selected in the Monitor states area.

Click the Name list item.



Lab Guide

Step Action
22. Enter the desired information into the Message: field. Enter ", has failed due to:".

23. Press [Enter].
24. You will now add more built‐in symbolics to help define the status.

You will add the job state.




Lab Guide

Step Action
26. Point to the Job list item.
27. Click the State list item.



Lab Guide

Step Action
28. Press [Enter].
29. Next, you will add the job status.




Lab Guide

Step Action
31. Point to the Job list item.
32. Click the Status list item.

33. Press [Enter].


Lab Guide

Step Action
34. Lastly, you will add the actual time that the job failed.

Enter the desired information into the Message: field. Enter "This occurred at:".
35. Right‐click in the Message: field.



Lab Guide

Step Action
37. Point to the Application list item.
38. Point to the Date/Time list item.
39. Point to the Actual list item.
40. Click the Time list item.



Lab Guide

Step Action
41. Selecting Attach spool file will include the spool file as an attachment to the email.

Note: The spool file can be large and cause the email to move slowly though your email
system.

The notification is defined; you will save it.




Lab Guide

Step Action
upload it.



Lab Guide

Step Action


Lab Guide

Step Action
45. The Save As... dialog appears and, by default, displays the desktop.

Previously, this application had been saved to the desktop; you will overwrite the file.



Step Action
47. You will now upload the application.



Lab Guide

Step Action


Lab Guide

Step Action

Enter the desired information into the Comments field. Enter "Added email notification
for failed job status".






54. In this lab, you defined an email notification.
End of Procedure.



Lab Guide

Lab 11‐2 Add an Alert to an Application
In this lab, you will add an alert to an application.

Step Action

You can define notifications based on your business requirements, enabling you to
respond properly to workload outages.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully define an alert in an
application.



4. You will open an existing application to create an alert notification.






Lab Guide

Step Action
of eight UNIX jobs.

You will open the Application properties dialog to create a notification.



Lab Guide

Step Action



Lab Guide

Step Action
9. Click the Notifications tree item.

Step Action
10. Click the Alerts tab.

11. You set up an alert notification to trigger additional workload automatically.


12. First, you need to specify a return code or select a monitor state from the job that will
trigger the alert.

You will set the alert to be triggered by a failed job.

Click the Failed option.


Lab Guide

Step Action
13. Then, you type the name of the alert you want to run.

If there are other alerts in the system, you can select one using the Alert name: drop‐
down list.

Because this is the only alert, you will define an alert name.

Enter the desired information into the Alert name: field. Enter "JOBFAILED".

14. The alert notification is defined; you will save it.




Lab Guide

Step Action
upload it.


Step Action


Lab Guide

Step Action
18. The Save As... dialog appears and, by default, displays the desktop.







Enter the desired information into the Comments field. Enter "Added an alert for a failed
state to the application".



Lab Guide

Step Action




26. In this lab, you added an alert notification to an application.
End of Procedure.



Lab Guide

Lab 11‐3 Create a JavaScript Alert
In this lab, you will create a JavaScript alert.

Step Action

Creating CA Workload Automation DE alerts based on your business needs helps ensure
you have a good workload process.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully define a JavaScript for an
alert and then trigger an application to test the alert.



4. In the previous lab, you created an alert notification at the application level.

You will now define the alert to run a JavaScript script when a job reaches the state
defined in the alert, which is failed.

You define alerts with JavaScript on the Services perspective.



Lab Guide

Step Action
5. Double‐click the Alerts tree item.



Lab Guide

Step Action
6. You will begin by searching for alerts in the system.


7. Currently, there are no alerts defined in the system.

You will now define JavaScript for an alert notification.


8. The New Alert view appears on which you will define the function that the application‐
level alert notification will perform.

For the alert to function as expected, it is imperative that the correct application‐level
alert notification name is used.

To help ensure the correct alert notification name is used, you will open the application to
verify the alert name.







Lab Guide

Step Action
12. The application appears in the Application Workspace area.

You will open the Application properties dialog to view the alert notification name.



Lab Guide

Step Action



Lab Guide

Step Action
14. Click the Notifications tree item.

Step Action
15. Click the Alerts tab.

16. Double‐click the FAILED list item.

17. The alert name is JOBFAILED.

This name must be used for the alert to trigger the JavaScript that you will next define.

You will return to the Alerts view on the Services perspective.


18. Click the Cancel button.


Lab Guide

Step Action
19. Click the Services button.

20. You will now define the JavaScript that will execute when the application‐level alert
notification is triggered.

You begin by defining the alert name.

Note: If the same alert name is used, it does not matter which object is created first, the
application‐level alert notification definition or the alert JavaScript definition.

Enter the desired information into the *Alert name: field. Enter "JOBFAILED".

21. There are three options available to define the action that will result when the alert is
triggered.

You can define the alert to:
‐ Trigger an event
‐ Run a JavaScript from the repository (database)
‐ Run JavaScript written for this alert

For this scenario, you will execute a JavaScript that is written specifically for this alert.

Click the Run this JavaScript: option.

22. Using the Run this JavaScript: option means the JavaScript you define is only available to
be used by this alert. The JavaScript is not stored in the repository.

Running JavaScript from the repository means anyone with the proper rights can access
and potentially change the JavaScript.

You need to define a name for this alert notification definition.

Enter the desired information into the Name: field. Enter "jobfailed".


Lab Guide

Step Action
23. You can manually enter a JavaScript or import one in the JavaScript Editor.

In this lab, you will manually enter a JavaScript.

"execTrigger('Cybermation.verify')".

24. The entered JavaScript uses the CA Workload Automation DE keyword trigger to execute a
trigger for the application named verify.

After you enter a JavaScript statement, you can use the built‐in syntax checker to help
ensure the script was entered correctly.




26. The JavaScript for the alert definition is defined; you will now save it.


27. You will close the JOBFAILED view.


28. The JavaScript alert definition appears in the Alerts view.

When the application‐level alert notification named JOBFAILED is triggered by a failed job,
the JavaScript you entered in the alert definition will be executed and the event for the
application named verify will be triggered.

You will now create another alert using a different alert definition option.



Lab Guide

Step Action
29. You begin by defining the alert name.

For this alert, because no matching application‐level alert was created, you can use any
name.

Enter the desired information into the *Alert name: field. Enter "JOBFAILED_SECOND".

30. For this alert definition, you will trigger an event using the Trigger an Event option.

Click the Trigger an Event option.

31. After you select the option, you must define the name of the event that will be triggered.

You start by identifying the event prefix name.

Click the Prefix: list.

32. All event prefix names that you have the rights to view appear in the list.

Click the Prefix: list item.

33. Next, you identify the application name.

Click the Name: list.

34. All application names that you have the rights to view appear in the list.

Click the Name: list item.

35. The event trigger alert definition is defined; you will now save it.


36. You will close the JOBFAILED_SECOND view.



Lab Guide

Step Action
37. The event trigger alert definition appears in the Alerts view.

When an application‐level alert notification that is linked to this definition is triggered by
the criteria you define, the event that you identified will be triggered.

You will now create one more alert using a different alert definition option. This alert
definition will use a JavaScript defined in the repository.

You will begin by adding the required JavaScript to the repository.

Double‐click the JavaScripts tree item.



Lab Guide

Step Action
38. You will define a new JavaScript.


39. You will define this JavaScript to trigger an event.

You start by defining the JavaScript name.

Enter the desired information into the *JavaScript name: field. Enter "JOBFAILED_THIRD".

40. You will manually enter the required JavaScript in the JavaScript Editor.

"execTrigger('Cybermation.verify')".

41. You will use the built‐in syntax checker to help ensure the script was entered correctly.



Lab Guide

Step Action


43. The JavaScript is defined; you will now save it.


Step Action
44. You will close the JOBFAILED_SECOND view.


45. The newly defined JavaScript appears in the JavaScripts view, available for use.

You will open the Alerts view to create a new alert that uses this newly defined JavaScript.

Double‐click the Alerts tree item.



Lab Guide

Step Action
46. Click the New button.

47. You begin by defining the alert name.

For this alert, because no matching application‐level alert has been created, you can use
any name.

Enter the desired information into the *Alert name: field. Enter "JOBFAILED_THIRD".

48. By default, the Run a JavaScript from Repository option is selected.

You will now define which JavaScript to run from the repository.

Click the Name: list.

49. All JavaScripts that you have the rights to view appear in the list.

You will select the JavaScript you defined in this lab.

Click the Name: list item.



Lab Guide

Step Action
50. The Run a JavaScript from Repository alert definition is defined; you will now save it.


51. You will close the JOBFAILED_THIRD view.


52. The newly defined alert appears in the Alerts view, available for use.

You will now close the open views in the Services perspective and then navigate to the
Define perspective to test the application‐level alert notification that you defined with the
alert‐level JavaScript.




55. The application that you downloaded at the beginning of the lab appears in the
Application Workspace area.

The first step to test the alert is to edit the event.

Double‐click the SCHEDMASTER.PAYROLL list item.


Lab Guide

Step Action
56. Click the Schedule tree item.



Lab Guide

Step Action
57. You will add schedule criteria to the event.

You will define the event with the expect daily keywords.

The expect keyword defines the event will be on the schedule but does not schedule the
event. If an event has an expect time, the event appears on the schedule and forecasts for
that time.

Note: No action is required if the event is not triggered by the expected time.

Click the Add Expect button.

58. Enter the desired information into the When field. Enter "daily".

Step Action
59. Click the JavaScript tree item.



Lab Guide

Step Action
60. There is one JavaScript associated to the event. You will remove the JavaScript to help
ensure the event triggers the application with no scheduling conflicts.

Click the JavaScript Name cell.

61. Click the Remove button.

62. The event parameters are now correctly defined.



Lab Guide

Step Action
upload it.



Lab Guide

Step Action


Lab Guide

Step Action
65. The Save As... dialog appears, and by default, displays the desktop.







Enter the desired information into the Comments field. Enter "Added expect daily to the
application".


70. Next, you will trigger the event on hold with today`s date.



72. Click the Submit Application on hold option.



Lab Guide

Step Action
74. The application has been triggered. You will now monitor and control workload for the
application.

You monitor and control active workload in the Monitor perspective.


Step Action


76. You will subscribe to all applications on the server, no matter their state.




Lab Guide

Step Action
77. The application that was triggered, PAYROLL, appears in the list.


78. The application has a state of Applhold.

To display the generation in a flowchart view, you double‐click the generation name.


79. The application was triggered on hold, which you can see as each job has a state of
APPLHOLD.

You will override a job in the workflow to cause it to fail so that the alert will be triggered.

The definition for the job named FIFTH_JOB.THIS_IS_JOB_FIVE will be changed.



Lab Guide

Step Action
80. Click the Reset Definition list item.



Lab Guide

Step Action
81. You will change the Script/command name field value from /bin/sleep to /bin/faults and
then remove the value in the Argument to pass field.

Click in the *Script/command name: field.

82. Enter the desired information into the Script/command name: field. Enter "/bin/false".
83. Click in the Arguments to pass: field.

85. The job definition is amended; you will close the dialog.



Lab Guide

Step Action
86. You will now view the details for the modified job.


Step Action
87. Click the Details list item.



Lab Guide

Step Action
88. By looking at the Execute a command line in the job details, you can verify that the
modification was saved.



Lab Guide

Step Action
89. Before manually releasing the held application, you must clear the Do not submit before:
value that was added to the first job in Lab 10‐1.


90. Click the Reset Times list item.

91. If the value is not cleared, the job will not run until the designated time, 20:00:00.

You will clear the entry from the field.

Click in the Do not submit before: field.

92. Press [Delete].


Lab Guide

Step Action
94. You will manually release the held application.

Right‐click the PAYROLL.4, Applhold, 6 Jobs tree item.


Step Action
96. You must add a reason why you are issuing the release command.

Enter the desired information into the Reason: field. Enter "Start application per
instruction".

97. After you click OK, you will watch the application run.



Lab Guide

Step Action
98. Immediately after releasing the held application, the first job started executing and is now
completed.

The second job is in the process of executing.

Press [Enter].


Lab Guide

Step Action
99. The second job is completed; the third job is now executing.

Press [Enter].


Lab Guide

Step Action
100. The fifth job failed.

Because of the failed job, the JavaScript that was defined in the alert triggered the event
for the VERIFY application, verifying the alert was successfully configured.


101. Double‐click the VERIFY.1, Complete, 4 Jobs tree item.

Step Action
102. You will close the application views and exit the Desktop Client.





Lab Guide

Step Action

106. In this lab, you created a JavaScript alert.
End of Procedure.



Lab Guide

Lab 11‐4 Generate Forecast Reports
In this lab, you will generate forecast reports.

Step Action
1. To work with forecast reports, you will start the Desktop Client.

By generating forecast reports, you are prepared for outages and can plan ahead.



Lab Guide

Step Action
logged‐in user.


Logging in with SCHEDMASTER rights enables you to successfully generate a forecast
report.



4. Forecast reports are managed in the Services perspective, in the Forecasts view.


Step Action
5. Double‐click the Forecasts tree item.



Lab Guide

Step Action
6. Generating forecast reports is very beneficial because the report enables you to plan your
workload.

You will begin by searching for forecast reports in the system.


7. There are two default forecast reports:
‐ A 24‐hour forecast report
‐ A 7‐day forecast report

You will scroll to the right to view the available columns.




Lab Guide

Step Action
8. The final column, Last Modified By, displays the name of the user who last modified the
forecast report.

You will scroll to the left.


9. You will generate the 24‐hour forecast report.

To generate a report, you select one from the view and then click Generate Forecast
Report.

Click the FORECAST24HOUR cell.


Lab Guide

Step Action
10. Click the Generate Forecast Report button.


Lab Guide

Step Action
11. While the report is being generated, the Retrieve report dialog appears.

The options in the dialog enable you to run the report in the background once, or every
time a forecast report is generated.

The Run in Background option is available because depending on the number of
applications and jobs in the system, the report generation can take a while.

In this scenario, you will not select an option to run the report in the background.

Press [Enter].

Step Action
12. The forecast report is generated and appears in the Forecast Report view.

To see more of the report, you will maximize the view.



Lab Guide

Step Action
13. You can generate forecast reports and run forecasts at any time that suits you.

The forecast report displays job names and types, start and end times, execution
durations, agents used, and so on.

To view more of the report, you will scroll down.

14. Nonscheduled events do not appear in the forecast report unless they have an expect
time coded.

You will now scroll up.

15. There are five options at the top of the Forecast Report view that enable you to manage
the report.

Click the Toggle table of contents button.

16. The Toggle table of contents function turns the table of contents on and off.

Click the Toggle table of contents button.

17. Click the Export data button.

18. The Export data function enables you to export specific columns of the report.


19. Click the Export report button.

20. The Export report function enables you to export the entire report in a selected format.


21. Click the Print report button.


Lab Guide

Step Action
22. The Print report function enables you to print the entire report, or specific pages of the
report, in different formats.


23. Click the Print report on the server button.

24. The Print report on the server function enables you to print a copy of the report to a
server.


25. You can also use Gantt charts to display information from a forecast report.

Click the Open Gantt chart for all jobs from report button.


Lab Guide

Step Action
26. Gantt charts show a forecast by an anticipated end time based on an average run time.

To view more of the Gantt chart, you will scroll down.


27. You will scroll up.


28. To view job details, you can move the Gantt chart divider to the right.



Lab Guide

Step Action
30. You will now close the two forecast views.



32. You can create a forecast reports based on your requirements.


33. You begin by defining the report name.

Enter the desired information into the *Forecast name: field. Enter "Shifts".

34. Next, you need to define the time frame that the forecast will report on.

You can add scheduling terms to the *Starting at field. You will leave the default value.

You will define this forecast to report on jobs that will run for the next eight hours.

Enter the desired information into the *Continuing for: field. Enter "8".

35. Click the hours option.

36. The remaining fields in the view enable you to create forecast reports based on
combinations of:
‐ Event names
‐ Application names
‐ Subapplication names
‐ Job names
‐ Threshold frequency

To view more fields, you will scroll down.



Lab Guide

Step Action
37. The remaining fields will be left with their default values.

The forecast report is created; you will now save it.


38. You will close the SHIFTS view.


39. The new forecast report appears in the Forecasts view, available to be run any time that
you require it.

To view more columns, you will scroll to the right.


40. Notice the Last Modified By column value for the new forecast report.

Because you are logged in as SCHEDMASTER, the user ID appears in the cell.




Lab Guide

Step Action
41. You will generate the new report.

Click the SHIFTS tree item.



Lab Guide

Step Action
42. Click the Generate Forecast Report button.

43. While the report is generated, the Retrieve report dialog appears, enabling you to run the
report in the background.

Press [Enter].
44. The forecast report is generated and appears in the Forecast Report view.

To see more of the report, you will maximize the view.


45. The forecast data that is reported is based on the jobs that are scheduled to run starting
now for the next eight hours. Any jobs that are scheduled to run after eight hours will not
appear in this report.



Lab Guide

Step Action
46. You will close the Forecast view and exit the Desktop Client.




49. In this lab, you generated forecast reports.
End of Procedure.


Lab Guide



85DSR2008 Lab G1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

85DSR2008 Lab G1

Uploaded by

Copyright:

Available Formats

CA Technologies CA Workload Automation DE r11.3: Foundations 200 ii

CA Technologies CA Workload Automation DE r11.3: Foundations 200 10

CA Technologies CA Workload Automation DE r11.3: Foundations 200 11

CA Technologies CA Workload Automation DE r11.3: Foundations 200 12

CA Technologies CA Workload Automation DE r11.3: Foundations 200 13

CA Technologies CA Workload Automation DE r11.3: Foundations 200 14

CA Technologies CA Workload Automation DE r11.3: Foundations 200 15

CA Technologies CA Workload Automation DE r11.3: Foundations 200 17

CA Technologies CA Workload Automation DE r11.3: Foundations 200 18

CA Technologies CA Workload Automation DE r11.3: Foundations 200 19

CA Technologies CA Workload Automation DE r11.3: Foundations 200 20

CA Technologies CA Workload Automation DE r11.3: Foundations 200 21

CA Technologies CA Workload Automation DE r11.3: Foundations 200 22

CA Technologies CA Workload Automation DE r11.3: Foundations 200 23

CA Technologies CA Workload Automation DE r11.3: Foundations 200 24

CA Technologies CA Workload Automation DE r11.3: Foundations 200 26

CA Technologies CA Workload Automation DE r11.3: Foundations 200 27

CA Technologies CA Workload Automation DE r11.3: Foundations 200 28

CA Technologies CA Workload Automation DE r11.3: Foundations 200 29

CA Technologies CA Workload Automation DE r11.3: Foundations 200 30

CA Technologies CA Workload Automation DE r11.3: Foundations 200 31

CA Technologies CA Workload Automation DE r11.3: Foundations 200 32

CA Technologies CA Workload Automation DE r11.3: Foundations 200 33

CA Technologies CA Workload Automation DE r11.3: Foundations 200 34

CA Technologies CA Workload Automation DE r11.3: Foundations 200 35

CA Technologies CA Workload Automation DE r11.3: Foundations 200 36

CA Technologies CA Workload Automation DE r11.3: Foundations 200 37

CA Technologies CA Workload Automation DE r11.3: Foundations 200 38

CA Technologies CA Workload Automation DE r11.3: Foundations 200 39

CA Technologies CA Workload Automation DE r11.3: Foundations 200 40

CA Technologies CA Workload Automation DE r11.3: Foundations 200 41

CA Technologies CA Workload Automation DE r11.3: Foundations 200 42

CA Technologies CA Workload Automation DE r11.3: Foundations 200 43

CA Technologies CA Workload Automation DE r11.3: Foundations 200 44

CA Technologies CA Workload Automation DE r11.3: Foundations 200 45

CA Technologies CA Workload Automation DE r11.3: Foundations 200 46

CA Technologies CA Workload Automation DE r11.3: Foundations 200 47

CA Technologies CA Workload Automation DE r11.3: Foundations 200 48

CA Technologies CA Workload Automation DE r11.3: Foundations 200 49

CA Technologies CA Workload Automation DE r11.3: Foundations 200 50

CA Technologies CA Workload Automation DE r11.3: Foundations 200 51

CA Technologies CA Workload Automation DE r11.3: Foundations 200 52

CA Technologies CA Workload Automation DE r11.3: Foundations 200 53

CA Technologies CA Workload Automation DE r11.3: Foundations 200 54

CA Technologies CA Workload Automation DE r11.3: Foundations 200 55

CA Technologies CA Workload Automation DE r11.3: Foundations 200 56

CA Technologies CA Workload Automation DE r11.3: Foundations 200 57

CA Technologies CA Workload Automation DE r11.3: Foundations 200 58

CA Technologies CA Workload Automation DE r11.3: Foundations 200 59

CA Technologies CA Workload Automation DE r11.3: Foundations 200 60

CA Technologies CA Workload Automation DE r11.3: Foundations 200 61

CA Technologies CA Workload Automation DE r11.3: Foundations 200 62

CA Technologies CA Workload Automation DE r11.3: Foundations 200 63

CA Technologies CA Workload Automation DE r11.3: Foundations 200 64

CA Technologies CA Workload Automation DE r11.3: Foundations 200 65

CA Technologies CA Workload Automation DE r11.3: Foundations 200 67

CA Technologies CA Workload Automation DE r11.3: Foundations 200 68

CA Technologies CA Workload Automation DE r11.3: Foundations 200 69

CA Technologies CA Workload Automation DE r11.3: Foundations 200 70

CA Technologies CA Workload Automation DE r11.3: Foundations 200 71

CA Technologies CA Workload Automation DE r11.3: Foundations 200 72

CA Technologies CA Workload Automation DE r11.3: Foundations 200 73

CA Technologies CA Workload Automation DE r11.3: Foundations 200 74