get started w rs enterprise handout

1

03/2011

Agenda – Part 1

Robot/SCHEDULEEnterprise Overview

Demonstration– Enterprise Server – Agents– Agent Scheduling Objects– Agent Reports– Agent Output – Agent-Specific Security – Defining Agent Jobs

Helpful Tips and Examples

2

If you own Robot/CLIENT…Part 2 is dedicated to YOU!

Clients will become Agents – Discussed in Part 2

Planning and Help/FACTSClient and Agent Commands

Demonstration– RCLTFRF with Robot/SCHEDULE Enterprise– Changing RCLEXEC jobs to Agent jobs

Removing Robot/CLIENT

Agenda – Part 2 (for Robot/CLIENT Users)

3

Robot/SCHEDULE Enterprise Feature Overview

Manage jobs, tasks, and events across your enterpriseRun multiple scripts in one agent jobShare command sets, environments,and return code objectsSecure and TLS-encryptedMonitor agent events – File event– Process event– Manual event

Manage cross-platformdependencies

Built-in file transfer functionMonitor agent status andsend alertsControl agent error logsand copy to System iTrack agent job andevent historyAudit agent job changesUse scheduling tools for Agent jobs

- Calendars- Date Objects- Environments- Reserved Command Variables - OPAL

Robot/SCHEDULE Enterprise Feature Overview (cont.)

- Blueprints- Schedule Activity Monitor- Job completion history and filters- Forecasts

4

Terminology

Enterprise Server software– Installed on the System i; integrates with Robot/SCHEDULE to

manage your enterprise scheduling

Agent Server software– Service or daemon that runs on agent servers and connects to

Robot/SCHEDULE Enterprise on the System i

Agent job – Executes processes on non-System i servers– Has a simultaneous System i job that receives the completion code

Agent event monitors– Trigger a file processing job after a file arrives or is changed– Launch a script to restart a critical daemon that has ended– Trigger events from your programs with API interfaces

Agent Environment User – User account name defined to a job environment that has all the

required permissions to execute the agent job– Some OS user names are case-sensitive

Prompt button (…)– Displays a finder window to select pre-defined valid job attributes

such as agent name, user, working path, shared environments, and so on

Return Codes– Code indicating if an agent command completed successfully or

failed

Built-in Function (for FTP)– Automates file transfers– Replaces the Robot/CLIENT RCLTFRF command

Terminology (cont.)

5

Client– Robot/SCHEDULE client software, which now is agent software

Job logs– AGENTLOG: Logging detail of the processes executed on the agent

server – QPJOBLOG: Logging detail of the System i job that runs

simultaneously with, and corresponds to, the agent processes running on the agent server

Terminology (cont.)

Installation Overview• Review all Help/FACTS installation instructions• Review prerequisite software requirements• Download the Robot Product Maintenance Wizard • Install Enterprise Server software on the System i• Install Robot/SCHEDULE for Windows • Install Agent software on Windows, Linux, AIX, and

Sun Solaris servers

Install GUI second

Install onme first

Install onus last

(Refer to Helpful Tips)

You’ll need the Wizard

6

Required Software

- On the System i Enterprise Server

- On the System i to update Robot/SCHEDULE

- On a Windows server

- On the System i Enterprise ServerThis is the Robot/SCHEDULE GUI

- On Linux, AIX, or Solaris servers

- On a PC for installation and upgrades

Installation Help/FACTS

(Robot/CLIENT)

(Robot/CLIENT)

7

Robot/SCHEDULE for Windows –Required for Agent Job Administration and Job Monitoring

Enterprise Server Options in the Explorer

Optional Software

Robot/CONSOLE, Robot/ALERT & Robot/NETWORK – for monitoring and notification

8

Live Demonstration using the Robot/SCHEDULE Explorer1. Enterprise Server 2. Work with Agents3. Agent Scheduling Objects4. Agent Reports5. Agent-Specific Security 6. Jobs by Agent7. Define an Agent job8. Built-in Function for file transfer9. Agent Output 10. Using Groups for cross-platform dependencies

1. Enterprise Server

Highlight and right-click

9

2. Work with Agent

3. Agent Scheduling Object(Command Sets)

Create the Command Set object, then define it to a job

10

Agent environmentsPrivate: Defined at the job level for a single jobShared: Predefined to share with multiple jobsMerged: Combine shared environment with private variable settings

Private – define with the job Shared – define before the job

3. Agent Scheduling Object(Environments)

Default Pass

Custom Pass

Custom Fail

Private - single job

3. Agent Scheduling Object(Agent Return Codes)

11

Four types of event monitors:

3. Agent Scheduling Object(Agent Event Monitors)

Directory

File

Manual

Process

4. Agent Reports

12

5. Agent-Specific Security (in System Setup)

Agent Environment Security

FTP Server Identity Map Security

6. Jobs by Agent

13

Jobs by Agent / New

Job Creation Wizard

7. Agent Jobs(Defining)

7. Agent Jobs(Properties)

14

AIX Server Windows Server

Click on a command line to access the file browser and Reserved Command Variables.

7. Agent Jobs(Command Entry)

8. Built-in FTP Function

Optionally define an FTPServer Identity Map

Add a Function from Command Entry

15

Defined on the Agent Output tab specific to each job

9. Agent Output

9. Display Agent Output

While a job is running, use the Enterprise Server Properties Diagnostics or Agent Properties Diagnostics

16

9. Display Agent Output (cont.)

View AGENTLOG after the job ends

10. Cross-Platform Dependencies

1. Daily Order Processing runs on a remote System i.2. Accounting and GL Close is triggered at month-end only on the Enterprise Server System i.3. Inventory End of Day runs on the Enterprise Server.4. A file is transferred from the Enterprise Server to a Windows server with an Agent job.5. An Agent Event monitor triggers notification that the FTP completed.6. A QSYSOPR message is sent to a System i message queue from the Windows server.7. A Linux Agent job runs as the final job in the group, if this group member is released.

17

Helpful Tips

1. Supporting Documents2. Support and Downloads3. Enterprise Server pre-check and

installation 4. Windows agent installation 5. Linux agent installation 6. Switch agent jobs to new agent7. Switch agents to new Enterprise Server8. Schedule interactive Windows processes

Installation Help/FACTS– Robot/SCHEDULE– Robot SCHEDULE Enterprise

Robot/SCHEDULE EnterpriseUser Guide– Hardware and software requirements– Getting started: Quick Tours

Robot/SCHEDULE User Guide(s)

1. Supporting Documents

18

2. Support and Downloads(www.helpsystems.com)

System Serial number and Trial authorization code are required for installation

3. Enterprise Server Installation

Robot Product MaintenanceWizard on a PC

Robot/SCHEDULE onthe System i

Robot/SCHEDULE GUIon a PC

Important:You must satisfy all software prerequisite requirements and product dependencies before you install.

19

Remember to install the Wizard.Download files before Installation. We recommend Save rather than Open.

3. Enterprise Server Installation (cont.)

Consider before installing:

– All software requirements are met– End mirroring of Robot/SCHEDULE

– Active if running pre-check– Inactive if installing

– RBTSLEEPER subsystem – Active if running pre-check– Inactive if installing

– Use a *SECOFR profile– Click on the .HS file to begin

3. Enterprise Server Installation(with the Wizard)

2

3

1

20


4 5

6 7

Option 5 Installation Pre-check:RBTSLEEPER subsystemcan be Active

FATAL messages = Not ready to installWarning messages = Check if PTFsare required

3. Enterprise Server Pre-check(Prior to Installation)

21

Repeat: RBTCDRLIB/HLPCDMENU DEV(*SAVF) SAVFLIB(HSSAVF)Option 1 Install: RBTSLEEPER subsystem must be INACTIVE


Press Enter Congratulations

8 9

10 11

4. WINDOWS Agent Installation

Enterprise Agent Setup Wizard installs theWindows Agent Manager and automaticallyinstalls the Java.

22

Determine OS and CPU for Agent: uname -aDetermine version of Linux: cat /etc/issue

Refer to Installing Robot/SCHEDULE Enterprise Agents

Java virtual machine is NOT installed with the agentsoftware, but is required: http://www.helpsystems.com/support/faqs/getjava

Determine where the JAVA_HOME environment variableis installed prior to installation. For AIX/Solaris/Linux, Javacan be installed anywhere.

5. Linux Agent Installation Tips

Plan to run the agent as a userother than root and with appropriate permissions.Agent names, by default, are defined as“agent system name” in the GUI.(Call Technical Support prior to installation if youwant to customize the agent name in the GUI.)Consider adding an agent startup command tothe server startup sequence:– ./start.sh &

OR– /opt/helpsystems/schent/start.sh &


23

Command to easily test a job: ls -altThis lists the contents of a directory in detail.

Where are SYSOUT and SYSERR logs stored?– When a Linux command prompt starts, three files

open automatically: stdin, stdout, and stderr. – File stdin is associated with the user's keyboard – Files stdout and stderr are associated with the user's terminal– Programs can write error or diagnostic messages to stderr


6. Switch Jobs and Events fromTest Agent to Production Agent

Switch jobs todifferent agent server

Switch Eventmonitors to differentagent server

24

7. Switch Agent to Different Enterprise Server

Command – switch [-f ] ipaddress port

• -f – agent if you are not using the default • ipaddress – IP address of the Enterprise

Server port • port – port number of the Enterprise Server

(usually 7472)

Instructs an agent to switch to a different Enterprise Server bymodifying configuration information, including the name of the agent file, port information, and the server address.

8. Schedule Windows Agent Interactive Processes

Most agent jobs execute batch processes from ahidden command shell

Some processes cannot be converted to a batchprocess and need interactive input requests suchas a GUI program that runs on the desktop

The following executables work together fora possible solution:– vlaunch.exe

• Defined to the agent job properties as a command – Robot/SCHEDULE Agent Transponder.exe

• Launched on the desktop to listen for requests

For Windows Agents Only! Call Technical Support for details.

25

02/2011

Planning and Help/FACTS

Client and Agent Commands

Demonstration – Move RCLTFRF Command Jobs to

Robot/SCHEDULE Enterprise Agent Jobs– Defining RCLEXEC Jobs as Agent Jobs


Agenda – Part 2 (for Robot/CLIENT users)

26

Planning and Help/FACTS

Client and Agent Software on Same Server

Robot/CLIENT software Agent software

During the Test phase, both softwareapplications can co-exist and run in parallel!

27

Things to Consider…Which Client tasks (commands) are beingexecuted and from which clients?Tip: SQL or query the RBTRCLLIB/RCLTK1 fileto view Client task history.

How are the tasks executed?– Robot/SCHEDULE jobs that are scheduled

Tip: Run the Job Command List report to findjobs with Robot/CLIENT commands.

– Robot/SCHEDULE jobs that are triggered byother commands, such as:• ROBOTLIB/RBTBCHUPD• ROBOTLIB/SNDRBTDTA• ROBOTLIB/AUTORUN

Tip: These commands may use a Robot job number parameter.The new agent jobs will not have the same Robot job number asthe Client job. Consult with your programmers who may havewritten or modified the programs that use these commands.

How are the tasks executed? (cont.)– Other scheduling tool– CL programs submitted from

Robot/SCHEDULE jobs– Programs executed outside

Robot/SCHEDULE– Menu options

Tip: Consult with your programmers who may havewritten or modified the programs that use theRBTRCLLIB commands.

Things to Consider…

28

Are the Robot/CLIENT jobs defined to groupsor are they reactive?

Do you use encrypted passwords with theRCLTFRF command?Tip: Use the RBTRCLLIB/RCLWRKPWD command, if authorized,to work with this file.

Do you use mapped network drives for Client tasks?Tip: Refer to the Robot/CLIENT command parameters for thedrive specifications.

Does a Robot/CLIENT registered Windows server executetasks that open and run GUI applications on the desktop? Tip: Refer to Helpful Tips – Part 1


Do you rotate the clients among multiple System i servers?Tip: Robot/SCHEDULE Enterprise allows multiple agent instanceson a single server, which can be configured to multiple System IEnterprise Server addresses. Use the Robot/CLIENT Rotation windowto determine if rotation is configured for a client.


29

Do you own Robot/REPORTS and useRobot/CLIENT to e-mail reports?

Robot/REPORTS 7.52 or higher –– Use the new option “R” for E-mail Distribution in

System Setup in Robot/REPORTS. This allows you to use a default Robot/ALERT device

– The e-mail address is pulled from the Recipient record,just like it was for Robot/CLIENT.

– The “C” option no longer displays on the screen, butyou can still use it at this version.

Note: Some Robot/CLIENT customers have to remove singlequotes in the recipient e-mail addresses.


Things to Consider…Do you own Robot/REPORTS and useRobot/CLIENT to e-mail reports?

Robot/REPORTS 7.51 or lower –– Select Option 1, System Defaults, from the System

Setup menu (option 6 on the Robot/REPORTS Main Menu), – Page down until you see Report E-Mail Distribution Option: C

(where A=Robot/ALERT, C=Robot/CLIENT)– Change the C to an A (for Robot/ALERT) and press Enter – Exit the panel and press F21 to display a command line

30

Things to Consider…Do you own Robot/REPORTS and useRobot/CLIENT to e-mail reports?

Robot/REPORTS 7.51 or lower (cont.) –– Run the REPUPDEDST command (Run this one time only) – Enter the Vendor name and press Enter– Press F6 on the Maintain Recipient list to create an Alert

device for each recipient with an e-mail addressNote: The product Robot/REPORTS has defined to use for e-maildetermines what displays on the Maintain Recipient screen. If you’reusing Robot/CLIENT, it displays a parameter for an e-mail address.If you’re using Robot/ALERT, it displays a parameter for an e-mail device.

RCLEXEC – Enter command data into your AGENT type job

RCLTFRF – Use the new FTP built-in function or commandsto transfer files via FTP

RCLENDSVC – Use the NET STOP command in the Agent job

RCLSTRSVC – Use the NET START command in the Agent job

RCLMONAPP – Use Agent Process Event monitor

RCLMONSVC – Use Agent Process Event monitor

RCLQRYSVC – Use Agent Process Event monitor

RCLSRVSTS – Requires a script to retrieve this information

RCLPOLL – Use Agent Off-line notification

RCLSENDMSG – Command: sendmsg

Robot/CLIENT Commands

31

RCLSNDMAIL – Use Robot/ALERT RBASNDMSG

RCLENDCLT – Command: stop [-f ] [now]

RCLLSTCLT – Use Agent Setup Report

RCLCOLLECT – Agent Properties and Diagnostics canprovide much of this information

RCLSTRWIN – Enter the Windows command in acommand entry panel of the Agent type job

RCLCLEANUP – No longer needed

Consider how your Robot/CLIENT commands are being executed!

From Robot/SCHEDULE jobs or another scheduling tool? From CL programs? From Menu options?

Robot/CLIENT Commands (cont.)

RCLTFRF and RCLEXECCommands

Robot/CLIENTjobs becomeAgent jobs

RCLTFRF with Robot/SCHEDULE Enterprise– Help/FACTS: Using the RCLTFRF Command in

Robot/SCHEDULE Enterprise– Help/FACTS: Using Robot/SCHEDULE Enterprise

Agent Jobs to Transfer FilesDefining RCLEXEC jobs as Agent jobs

32

Move RCLTFRF Command Jobs to Robot/SCHEDULE Enterprise Agent JobsThe process:

Is optional - you can do it manually by defining and schedulingAgent jobs that use the FTP Built-in Function to replace theRobot/CLIENT jobsDefines new Agent jobs mapped from existing Robot/SCHEDULE jobs that currently use the RCLTFRF commandDoes not remove or automatically replace the existing client job– HOLD the Robot/CLIENT jobs when you’re ready to use the new

Agent jobs so the process doesn’t run twice– Consider the current client job’s dependencies before you begin:

• If the current Client job is reactive or defined to a group• If the current Client job is triggered by Job name or Robot

job number from a program (Refer to: Things to Consider)You decide when the old Robot/CLIENT job can be removed

How to use the Move RCLTFRF process to create permanent Agent jobs

Before you begin:• Create an Agent Environment for each agent server that executes client RCLTFRF

commands• An Agent job is created with a name of RCLTFRF when the override is on.. The Agent job

also has a different ROBOT job number. HOLD the job that you do not want to run. Remember to check for reactivity, groups, CLs or menus that might trigger the Client job that will no longer be used.

Step 1: Stop the Agent software on the mapped Agent.

Step 2: Run the command: ROBOTLIB/ADDCAMAPE

Step 3: Run the step only if using encrypted passwords with Robot/CLIENT and are authorized to this file.RBTRCLLIB/RBTWRKPWD CALL ROBOTLIB/RBTRCL40 (Shares the PWD information with Enterprise)

Step 4: CALL RBTENTLIB/RBERCLOVR PARAM(*INSTALL)

Step 5: Use a DO override on a Robot/CLIENT RCLTFRF job that has been mapped to an Agent.

Note: The job terminates and the task cannot be executed on the Client because the Agent software is not active. The override program instructs Robot/SCHEDULE Enterprise to interceptthe RCLTFRF command. A permanent Agent job called RCLTFRF is created that uses the FTPBuilt-in Function defined instead of the RCLTFRF command.

33

How to use the Move RCLTFRF process to create permanent Agent jobs

.Step 6: Rename the RCLTFRF Agent job based on your review of job dependencies.

Tip: Change the message queue defined in the Control Options on the newagent job to *RBTDFT

Step 7: HOLD one of the jobs so both jobs do not run.

Step 8: Repeat Steps 1–3 for RCLTFRF type jobs for clients that have been mapped to Agents and rename the RCLTFRF job after each DO override.

Step 9: Turn off the override: CALL RBTENTLIB/RBERCLOVR PARM(*UNINSTALL)

Step 10: Start the Agent software on the remote server.

Step 11: Test the new Agent job before adding to groups and reactivity

Step 12: Remove obsolete RCLTFRF jobs from groups and reactivity and replace with new Agent jobs

Process commands and programs:ROBOTLIB/ADDCAMAPE command– Configures a mapping of registered clients in

Robot/CLIENT to Robot/SCHEDULE Enterprise agents

ROBOTLIB/RBTRCL40 command– Use only if needed to FTP encrypted password information

from Robot/CLIENT to Robot/SCHEDULE Enterprise• Need *ALLOBJ authority• Refer to: Things to Consider on Encrypted passwords• Also refer to the Help/FACTS for more information

Move RCLTFRF Command Jobs to Robot/SCHEDULE Enterprise Agent Jobs (cont.)

34

RBTENTLIB/RBERCLOVR program– Redirects the processing of the RCLTFRF command to

Robot/SCHEDULE Enterprise

Refer to the Help/FACTS, Using the RCLTFRF Command inRobot/SCHEDULE Enterprise. If you’ve been using mappednetwork drives, refer to the Help/FACTS, Using Network Driveswith Windows Agents.



Robot/CLIENT RCLTFRF Job RCLTFRF command – F4 prompt

35

Map a Client to an Agent – ROBOTLIB/ADDCAMAPE, F4 prompt

• Agent softwaremust be installedand licensed

• An Agentenvironment mustbe defined prior tousing this command



Redirect the RCLTFRF command to Robot/SCHEDULE Enterprise

36

If the override is on and the Agent is active:Robot/SCHEDULE Enterprise intercepts theRCLTFRF command requests for clients thathave been mapped to Agents

Temporary Agent jobs called RCLTFRF arecreated and deleted after running the file transferuntil you turn off the override:

CALL RBTENTLIB/RBECLOVR PARM(*UNINSTALL)


Defining RCLEXEC Jobsas Agent Jobs

Review the Job Command List report for jobs thatexecute the RCLEXEC command with the parametersHint: Use Robot query to find all jobs that execute the RCLEXEC command

Manually define an Agent type job based on the RCLEXEC command and parametersTest the command parameters from a command shellUse the Agent’s Show Active Processes tool to viewcommands as they are running on the AgentHOLD the RCLEXEC job when you’re ready to schedulethe new Agent job

37

RCLEXEC Command to Agent Job Command


Please call or e-mail Technical Support forRobot/CLIENT removal instructions or questions

38

Robot/SCHEDULEJob Scheduler & Automatic

Computer Operator

Robot/SAVEAutomatic Backup, Recovery

& Tape Management

Robot/NETWORKNetwork Management

Robot/CONSOLEMessage, Resource& Log Management

Robot/SPACEDisk Space

Management

Robot/REPORTSReport Distribution,Archiving & Viewing

Robot/REPLAYInteractive JobManagement

Robot/AUTOTUNEAutomatic Performance

Monitoring & Tuning

Robot/ALERTPager, Text, or

E-Mail Messages

Robot/LPARPartition Resource

Movement & Management

Robot/SCHEDULE EnterpriseEnterprise Job Scheduler

02/2011