Sei sulla pagina 1di 38

03/2011

Agenda Part 1
Robot/SCHEDULE Enterprise Overview Demonstration
Enterprise Server Agents Agent Scheduling Objects Agent Reports Agent Output Agent-Specific Security Defining Agent Jobs

Helpful Tips and Examples

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

Clients will become Agents Discussed in Part 2

Agenda Part 2 (for Robot/CLIENT Users)


Planning and Help/FACTS Client and Agent Commands Demonstration
RCLTFRF with Robot/SCHEDULE Enterprise Changing RCLEXEC jobs to Agent jobs

Removing Robot/CLIENT

Robot/SCHEDULE Enterprise Feature Overview


Manage jobs, tasks, and events across your enterprise Run multiple scripts in one agent job Share command sets, environments, and return code objects Secure and TLS-encrypted Monitor agent events
File event Process event Manual event

Manage cross-platform dependencies

Robot/SCHEDULE Enterprise Feature Overview (cont.)


Built-in file transfer function Monitor agent status and send alerts Control agent error logs and copy to System i Track agent job and event history Audit agent job changes Use scheduling tools for Agent jobs
- Calendars - Date Objects - Environments - Reserved Command Variables - OPAL - Blueprints - Schedule Activity Monitor - Job completion history and filters - Forecasts

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

Terminology (cont.)
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.)
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

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
Youll need the Wizard Install on me first Install GUI second Install on us last

(Refer to Helpful Tips)

Required Software
- On a PC for installation and upgrades - On the System i Enterprise Server - On the System i to update Robot/SCHEDULE - On the System i Enterprise Server
This is the Robot/SCHEDULE GUI

- On a Windows server - On Linux, AIX, or Solaris servers

Installation Help/FACTS

(Robot/CLIENT)

(Robot/CLIENT)

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

Live Demonstration using the Robot/SCHEDULE Explorer


1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Enterprise Server Work with Agents Agent Scheduling Objects Agent Reports Agent-Specific Security Jobs by Agent Define an Agent job Built-in Function for file transfer Agent Output Using Groups for cross-platform dependencies

1. Enterprise Server

Highlight and right-click

2. Work with Agent

3. Agent Scheduling Object


(Command Sets)

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

3. Agent Scheduling Object


(Environments) Agent environments Private: Defined at the job level for a single job Shared: Predefined to share with multiple jobs Merged: Combine shared environment with private variable settings

Private define with the job

Shared define before the job

3. Agent Scheduling Object


(Agent Return Codes)

Default Pass

Custom Fail

Custom Pass

Private - single job

10

3. Agent Scheduling Object


(Agent Event Monitors)

Four types of event monitors:

File Directory

Process Manual

4. Agent Reports

11

5. Agent-Specific Security (in System Setup)

FTP Server Identity Map Security Agent Environment Security

6. Jobs by Agent

12

7. Agent Jobs
(Defining) Jobs by Agent / New

Job Creation Wizard

7. Agent Jobs
(Properties)

13

7. Agent Jobs
(Command Entry)

AIX Server

Windows Server

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

8. Built-in FTP Function

Optionally define an FTP Server Identity Map Add a Function from Command Entry

14

9. Agent Output

Defined on the Agent Output tab specific to each job

9. Display Agent Output

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

15

9. Display Agent Output (cont.)

View AGENTLOG after the job ends

10. Cross-Platform Dependencies

1. 2. 3. 4. 5. 6. 7.

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

16

Helpful Tips
1. Supporting Documents 2. Support and Downloads 3. Enterprise Server pre-check and installation 4. Windows agent installation 5. Linux agent installation 6. Switch agent jobs to new agent 7. Switch agents to new Enterprise Server 8. Schedule interactive Windows processes

1. Supporting Documents
Installation Help/FACTS
Robot/SCHEDULE Robot SCHEDULE Enterprise

Robot/SCHEDULE Enterprise User Guide


Hardware and software requirements Getting started: Quick Tours

Robot/SCHEDULE User Guide(s)

17

2. Support and Downloads


(www.helpsystems.com)

System Serial number and Trial authorization code are required for installation

3. Enterprise Server Installation


Robot Product Maintenance Wizard on a PC Robot/SCHEDULE on the System i Robot/SCHEDULE GUI on a PC
Important:You must satisfy all software prerequisite requirements and product dependencies before you install.

18

3. Enterprise Server Installation (cont.)

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

3. Enterprise Server Installation


(with the Wizard)
1

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

19

3. Enterprise Server Installation


(with the Wizard)
4 5

3. Enterprise Server Pre-check


(Prior to Installation)
Option 5 Installation Pre-check: RBTSLEEPER subsystem can be Active

FATAL messages = Not ready to install Warning messages = Check if PTFs are required

20

3. Enterprise Server Installation


(with the Wizard)
8 9

10

11

Press Enter

Congratulations

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

4. WINDOWS Agent Installation

Enterprise Agent Setup Wizard installs the Windows Agent Manager and automatically installs the Java.

21

5. Linux Agent Installation Tips


Determine OS and CPU for Agent: uname -a Determine version of Linux: cat /etc/issue Refer to Installing Robot/SCHEDULE Enterprise Agents Java virtual machine is NOT installed with the agent software, but is required: http://www.helpsystems.com/support/faqs/getjava Determine where the JAVA_HOME environment variable is installed prior to installation. For AIX/Solaris/Linux, Java can be installed anywhere.

5. Linux Agent Installation Tips


Plan to run the agent as a user other 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 you want to customize the agent name in the GUI.) Consider adding an agent startup command to the server startup sequence:
./start.sh & OR /opt/helpsystems/schent/start.sh &

22

5. Linux Agent Installation Tips


Command to easily test a job: ls -alt This 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 from Test Agent to Production Agent

Switch jobs to different agent server

Switch Event monitors to different agent server

23

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 by modifying 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 a hidden command shell Some processes cannot be converted to a batch process and need interactive input requests such as a GUI program that runs on the desktop The following executables work together for a 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.

24

02/2011

Agenda Part 2 (for Robot/CLIENT users)


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

Removing Robot/CLIENT

25

Planning and Help/FACTS

Client and Agent Software on Same Server


During the Test phase, both software applications can co-exist and run in parallel!
Robot/CLIENT software Agent software

26

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

How are the tasks executed? Robot/SCHEDULE jobs that are scheduled
Tip: Run the Job Command List report to find jobs with Robot/CLIENT commands.

Robot/SCHEDULE jobs that are triggered by other 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 as the Client job. Consult with your programmers who may have written or modified the programs that use these commands.

Things to Consider
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 have written or modified the programs that use the RBTRCLLIB commands.

27

Things to Consider
Are the Robot/CLIENT jobs defined to groups or are they reactive? Do you use encrypted passwords with the RCLTFRF 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 the drive specifications.

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

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

28

Things to Consider
Do you own Robot/REPORTS and use Robot/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, but you can still use it at this version.
Note: Some Robot/CLIENT customers have to remove single quotes in the recipient e-mail addresses.

Things to Consider
Do you own Robot/REPORTS and use Robot/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

29

Things to Consider
Do you own Robot/REPORTS and use Robot/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 address
Note: The product Robot/REPORTS has defined to use for e-mail determines what displays on the Maintain Recipient screen. If youre using Robot/CLIENT, it displays a parameter for an e-mail address. If youre using Robot/ALERT, it displays a parameter for an e-mail device.

Robot/CLIENT Commands
RCLEXEC Enter command data into your AGENT type job RCLTFRF Use the new FTP built-in function or commands
to 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

30

Robot/CLIENT Commands (cont.)


RCLSNDMAIL Use Robot/ALERT RBASNDMSG RCLENDCLT Command: stop [-f ] [now] RCLLSTCLT Use Agent Setup Report RCLCOLLECT Agent Properties and Diagnostics can
provide much of this information

RCLSTRWIN Enter the Windows command in a


command 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?

RCLTFRF and RCLEXEC Commands


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 Files

Defining RCLEXEC jobs as Agent jobs


Robot/CLIENT jobs become Agent jobs

31

Move RCLTFRF Command Jobs to Robot/SCHEDULE Enterprise Agent Jobs


The process: Is optional - you can do it manually by defining and scheduling
Agent jobs that use the FTP Built-in Function to replace the Robot/CLIENT jobs

Defines new Agent jobs mapped from existing Robot/SCHEDULE jobs that currently use the RCLTFRF command Does not remove or automatically replace the existing client job
HOLD the Robot/CLIENT jobs when youre ready to use the new Agent jobs so the process doesnt run twice Consider the current client jobs 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: Step 3: Run the command: ROBOTLIB/ADDCAMAPE 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) CALL RBTENTLIB/RBERCLOVR PARAM(*INSTALL)

Step 4: 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 intercept the RCLTFRF command. A permanent Agent job called RCLTFRF is created that uses the FTP Built-in Function defined instead of the RCLTFRF command.

32

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 new agent job to *RBTDFT HOLD one of the jobs so both jobs do not run. Repeat Steps 13 for RCLTFRF type jobs for clients that have been mapped to Agents and rename the RCLTFRF job after each DO override. Turn off the override: CALL RBTENTLIB/RBERCLOVR PARM(*UNINSTALL)

Step 7: Step 8:

Step 9:

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

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


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

33

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


RBTENTLIB/RBERCLOVR program
Redirects the processing of the RCLTFRF command to Robot/SCHEDULE Enterprise

Refer to the Help/FACTS, Using the RCLTFRF Command in Robot/SCHEDULE Enterprise. If youve been using mapped network drives, refer to the Help/FACTS, Using Network Drives with Windows Agents.

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

Robot/CLIENT RCLTFRF Job

RCLTFRF command F4 prompt

34

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


Agent software must be installed and licensed An Agent environment must be defined prior to using this command

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

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

Redirect the RCLTFRF command to Robot/SCHEDULE Enterprise

35

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


If the override is on and the Agent is active:
Robot/SCHEDULE Enterprise intercepts the RCLTFRF command requests for clients that have been mapped to Agents Temporary Agent jobs called RCLTFRF are created and deleted after running the file transfer until you turn off the override: CALL RBTENTLIB/RBECLOVR PARM(*UNINSTALL)

Defining RCLEXEC Jobs as Agent Jobs


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

Manually define an Agent type job based on the RCLEXEC command and parameters Test the command parameters from a command shell Use the Agents Show Active Processes tool to view commands as they are running on the Agent HOLD the RCLEXEC job when youre ready to schedule the new Agent job

36

RCLEXEC Command to Agent Job Command

Removing Robot/CLIENT
Please call or e-mail Technical Support for Robot/CLIENT removal instructions or questions

37

Robot/SCHEDULE
Job Scheduler & Automatic Computer Operator

Robot/SCHEDULE Enterprise
Enterprise Job Scheduler

Robot/REPLAY
Interactive Job Management

Robot/NETWORK
Network Management

Robot/CONSOLE
Message, Resource & Log Management

Robot/SPACE
Disk Space Management

Robot/ALERT
Pager, Text, or E-Mail Messages

Robot/LPAR
Partition Resource Movement & Management

Robot/SAVE
Automatic Backup, Recovery & Tape Management

Robot/AUTOTUNE
Automatic Performance Monitoring & Tuning

Robot/REPORTS
Report Distribution, Archiving & Viewing

02/2011

38

Potrebbero piacerti anche