Use the Commands section to set up commands and return codes for the command set. You can manually enter a com- mand, use one of the Skybot Scheduler command builders, or use the copy function (right-click a command and select Copy).
Manual Commands
If you don't want to use a command builder, you can manually add a new command to the command set. 1. Click Add and select Command.
2. Enter the command or script in the Command column. Notes:
The exit system command should be used with caution on Windows. When exit is used in a command, it immediately ends the current process before Skybot Scheduler is finished evaluating the results. Using the parameter /b can help.
The Windows timeout command should be avoided when writing commands in Skybot Scheduler. It will prevent the job from completing. The timeout command waits for user input (even if the '/NOBREAK' option is used) and this interferes with Skybot Scheduler determining when a command has completed. If you're adding a call to vlaunch.exe, consider using theWindows Desktop Application Command window
instead of manually adding it here. The advantage is that the Windows Desktop Application Command win- dow automatically builds the correct syntax for doing the call. However, if you must add it here, use the fol- lowing syntax:
windows path\vlaunch.exe" "command.exe parm1 parm2 parm3
This passes the command string, including all parameters, to the Skybot Agent Transponder for execution, and continues with the next job command without waiting for the results.
windows path\vlaunch.exe" /W "command.exe parm1 parm2 parm3
This stops and waits for the command to execute via the Skybot Agent Transponder, and gets a return code from the command that can be tested.
If your Skybot Scheduler license is bundled with SEQUEL, and you're adding commands for an IBM i agent, click the list icon to see which commands are available to add.
Configuring Command Sets
Skybot Scheduler User Guide - 185 -
3. Click the value in theReturn Codecolumn, then click the pencil ) next to the value to open the Select Return Code window. You can enable and select a shared return code, or create an individual return code for this com- mand. (Return codes don't apply to IBM i commands.)
Clickherefor return code guidelines.
4. Click the value in the Fail Action column, then click the pencil ) next to the value to open the Select Failed Action window. Select an item from the When command fails list. You can choose: Fail Job (the job will end and show a status of Failed), Continue to next Command (this command will fail, but the job will continue to run with the next command), Retry command before Failing Job, and Retry command before continuing to next Command. If you select either of the "retry" choices, you must enter the Number of Retries and the time to Wait Between Retries in seconds.
Click Save when you're finished.
Note: If a job has an IBM i command that doesn't pass validation on the IBM i agent, the command retry settings are ignored (Fail Job/ Continue to next Command settings are still used). The job log will contain messages about the invalid parameter, but no retries will be attempted. An example of an IBM i command that would fail to validate is: SNDMSG MSG(string will not validate) TOUSR(myuser). It contains an unquoted string with a space in it.
5. Repeat for each command you need to add manually.
File Transfer (FTP)
Configuring Command Sets
Select File Transfer from the drop-down list. The File Transfer Command window opens. Note: You must create aFile Transfer Systembefore you can add an FTP command.
File Transfer System: Select a File Transfer System to work with.
Direction: Select file transfer direction. Push means you send a job to the remote system. Pull means you will retrieve a file from the remote system.
Remote File Name: Enter the name of the file on the remote system you want to work with. Agent File Name: Enter the name of the file on the agent system you want to work with.
Replace existing target file: Select if you want to replace an existing file. If you do not select this option, and there is a duplicate file, it causes an error.
Delete the source file after transfer: Select if you want the source file in the FTP directory deleted after the transfer is complete.
Transfer Type: Select the FTP mode. Select Binary when transferring applications or other information you don’t want encoded. Select Text when transferring text.
SITE command: Enter FTP specific commands to the remote FTP server.
Click Save to save your file transfer command. Skybot Scheduler writes the FTP syntax for you automatically. Notes:
Configuring Command Sets
Skybot Scheduler User Guide - 187 -
After you add a command, you should set the Return Code and Fail Action values. SeeManaging the Commands Table
below for instructions.
Informatica Cloud Task
You can use the command builder to create a Skybot Scheduler command that runs an Informatica Cloud task. Select Informatica Cloud Task from the drop-down list. The Informatica Cloud Task Command window displays. Note: You must create anInformatica Cloud server definitionbefore you can add an Informatica Cloud task command.
Server Definition: Select the Informatica Cloud server definition to connect to. Task Type: Select task type code from the list, or type it in the box if it's not listed. Task Name: Type the name of the task or task flow that this command should run.
Continue Immediately: Select this if you want this task started, but don't need Skybot Scheduler to monitor or wait for the task to complete.
Click Save to save your Informatica Cloud Task command.
After you add a command, you should set the Return Code and Fail Action values. SeeManaging the Commands Table
below for instructions.
Informatica Workflow
You can use the command builder to create a Skybot Scheduler command that runs an Informatica workflow. Select Informatica Workflow from the drop-down list. The Informatica Workflow Command window displays.
Note: You must create anInformatica PowerCenter system definitionbefore you can add an Informatica Workflow com- mand.
System Definition: Select the Informatica PowerCenter system definition to connect to. Integration Service Name: Select the Integration Service to use inside the repository. Folder Name: Select the folder within the selected repository.
Workflow: Select the Workflow to execute.
Configuring Command Sets
period delimited, so you may specify tasks that are nested in worklets. For example, "w1.task1" would run 'task1' in worklet 'w1' inside of the selected workflow. If you do not enter a path, the job runs the entire Workflow.
Check the box to only run the task specified above.
Operating System Profile: Enter the operating system user for the Workflow. Run Instance Name: Enter a run instance name for running the Workflow.
Retrieve Log: Select this check box if you want to include the Workflow log in the Skybot job log.
Parameters: To pass parameters to the Workflow, provide the name of an existing parameter file or create a new parameter list.
If you are creating a new parameter list:
You must enter a value in the Scope column.
Do not add [brackets] around the value you enter for the scope. The Informatica web service adds the brack- ets to whatever is passed in for the scope.
Configuring Command Sets
Skybot Scheduler User Guide - 189 -
Click Save to save your Informatica Workflow command.
After you add a command, you should set the Return Code and Fail Action values. SeeManaging the Commands Table
below for instructions.
Oracle Concurrent Request
Configuring Command Sets
Select Oracle Concurrent Request from the drop-down list to add an Oracle concurrent request command. The Oracle Concurrent Request Command window opens.
Note: You must create anOracle System Definitionbefore you can add an Oracle concurrent request command. System Definition: Select an Oracle system definition for this concurrent request.
Wait: Select the Yes check box if you want Skybot Scheduler to wait until the submitted concurrent request is com- pleted before marking the Skybot job as complete.
Program Application Shortname: Enter the application shortname from Oracle.
Concurrent Program: Enter the name of the Oracle concurrent program to be used for this request.
Program Name: Enter the program name you want to give this concurrent request. Or, you can leave this blank to use:Skybot Job Name(run number).
How a job displays in Oracle depends on what, if anything, is entered into this box. If you enter a program name, it will display in Oracle as: "Program Name (Concurrent Program Name)". If you leave this box blank, it will display as: "Skybot Job Name(run number) (Concurrent Program Name)". Notice that the run number is only displayed if you leave this box blank.
To add the parameters for this concurrent request, click Add Parameters. Then, enter the parameter Name (which can be anything because the name is for your reference only) and the Value (which must be a legitimate param- eter value). The order of the parameters must match the requirements for the Oracle application. You can add more than one parameter. To delete a parameter, click the X at the end of the row.
To pass null parameters to CONSUB, use ' " " ' without spaces (single-quote double-quote double-quote single- quote) for each null parameter.
In the following example, FND is the shortname for the Application Object Library, FNDCPPGS is the Concurrent Pro- grams Report, and the parameter value of FND limits the report to Concurrent Programs in the FND (Application Object Library). Once the request in this example is submitted on the Oracle system, it will have a Name of "Skybot Job (Con- current Programs Report)."
Configuring Command Sets
Skybot Scheduler User Guide - 191 -
Click Save to save your Oracle concurrent request command.
After you add a command, you should set the Return Code and Fail Action values. SeeManaging the Commands Table
below for instructions.
SAP NetWeaver Event
You can use the command builder to create a Skybot Scheduler command that raises an event on an SAP system. This allows you create reactivity in your network based on an SAP Event occurring.
Select SAP NetWeaver Event from the drop-down list. The SAP NetWeaver Event Command window opens. Note: You must create anSAP system definitionbefore you can add an SAP NetWeaver Event command.
Configuring Command Sets
System Definition: Select an SAP System Definition.
System Environment: Select an environment to use with the System Definition. If you have not defined an envi- ronment for this definition, it uses the default environment that you set up in the System Definition.
Event ID: Add the ID of the SAP event you want to trigger. Event Parameters: Add event parameters, if necessary.
Note: You can use the Event Parameters option with Skybot variables topass information throughduring a job.
Click Save to save your SAP NetWeaver Event command.
After you add a command, you should set the Return Code and Fail Action values. SeeManaging the Commands Table
below for instructions.
SAP NetWeaver Job
You can use the command builder to create a Skybot Scheduler command that runs an SAP NetWeaver job. Select SAP NetWeaver Job from the drop-down list. The SAP NetWeaver Job Command window opens. Note: You must create anSAP system definitionbefore you can add an SAP NetWeaver Job command.
Filtering Job Definitions: Use System Definition and System Environment to limit the available Job Definitions to choose from.
Configuring Command Sets
Skybot Scheduler User Guide - 193 -
Click Save to save your SAP NetWeaver Job command.
After you add a command, you should set the Return Code and Fail Action values. SeeManaging the Commands Table
below for instructions.
SAP NetWeaver Process Chain
You can use the command builder to create a Skybot Scheduler command that runs a process chain on an SAP system. This allows you create reactivity in your network based on an SAP process chain running.
Select SAP NetWeaver Process Chain from the drop-down list. The SAP NetWeaver Process Chain Command window opens.
Note: You must create anSAP system definitionbefore you can add an SAP NetWeaver Process Chain command. System Definition: Select an SAP System Definition.
System Environment: Select an environment to use with the System Definition. If you have not defined an envi- ronment for this definition, it uses the default environment that you set up in the System Definition.
Process Chain: Type or select the SAP process chain you want to run. Note: This must match the technical name of a process chain in the SAP system selected above.
Long Description: Type or select the long description from the process chain you want to run.
Note: If you begin typing the first few letters of either the process chain or the long description, you can click the down arrow and select from a list of available items that are pulled from SAP based on what you typed. Also, if you enter the name of a process chain, the long description associated with it is automatically pulled from SAP. The reverse is also true; if you enter a valid long description, the corresponding process chain name is pulled from SAP.
Configuring Command Sets
Click Save to save your SAP NetWeaver Process Chain command.
After you add a command, you should set the Return Code and Fail Action values. SeeManaging the Commands Table
below for instructions.
SAP NetWeaver Variant
You can use the command builder to create a Skybot Scheduler command that modifies an SAP ABAP variant. Select SAP NetWeaver Variant from the drop-down list. The SAP NetWeaver Variant Command window opens. Note: You must create anSAP system definitionbefore you can add an SAP NetWeaver Variant command.
System Definition: Select the SAP NetWeaver System Definition to use for this command.
System Environment: Select an environment to use with the System Definition. If you have not defined an envi- ronment for this definition, it uses the default environment that you defined in the System Definition.
Program: Enter the name of the SAP ABAP program.
Variant: Select or enter the variant. If the ABAP program entered doesn't contain any variants, the list will be empty. Parameters: Click Add Parameters to add additional variant parameters to be changed by this command. Click OK to save the parameter. You can add multiple parameters, but only existing parameters may be entered. This com- mand doesn't add new parameters to a variant.
Note: You can use the Event Parameters option with Skybot variables topass information throughduring a job.
Click Save to save your SAP NetWeaver Variant command.
Configuring Command Sets
Skybot Scheduler User Guide - 195 -
Select SQL Server Job from the drop-down list to add a SQL Server Job command. The SQL Server Job Command win- dow displays.
Note: You must create aSQL Server definitionbefore you can add a SQL Server Job command. SQL Server Definition: Select a SQL Server Definition to work with.
Job Name: Enter a SQL Server job name that is valid with the Server Instance defined in the SQL Server Def- inition.
Use Verbose Logging: Select this option to use verbose logging to help with troubleshooting.
Click Save to save your SQL Sever Job command.
After you add a command, you should adjust the Return Code and Fail Action settings. SeeManaging the Commands Tablebelow for instructions.
Web Service Request
You can use the command builder to create a Skybot Scheduler command that runs a web service request.
Select Web Service Request from the drop-down list to add a web service request command. The Web Service Request Command window displays. The information you enter in this window will vary greatly depending on which web service you're trying to access. See the documentation for that web service for additional help.
It is possible to run a web service request command and pass values from the response directly into subsequent com- mands or web service requests. For more information, see "Passing Values from a Web Service Response into a Sub- sequent Web Service Request" under theSkybot Support Self-Service tabon our website.
Note: You mustcreate a web server definitionbefore you can add a web service request command. Web Server Definition: Select the web server definition to which you're going to send the request.
Description: Enter a description of what this request does. Keep in mind that what you enter will be included in the command text.
Runtime Environment Variables: Type the name of a runtime environment variable that you want to use as a parameter in this command and press Enter. You can use system variables, Skybot variables, and agent envi- ronment variables. Repeat for each variable you want to use as a parameter. This allows you to take advantage of variables that have already been created. To remove a variable from the list, click the X next to it.
Base URL: This is automatically displayed when you select a web server definition. If what's showing is incorrect, you mustedit the web server definitionin order to change it.
Configuring Command Sets
Request Method: Select the method (GET, POST, PUT, or DELETE) for this web service request.
Header Properties: Click Add to add a header property for this request. In the Name column, select or type the header name (max length is 128 characters). In the Value column, type the value of this header property (max length is 1024 characters). You can add more than one header. Use the up and down arrows by each row to change the order of the header lines. To remove a header, click the X at the end of the row.
Request Parameters: Click Add to add the parameters for this request. In the Name column, type the parameter name (max length is 128 characters). In the Value column, type the value for this parameter (max length is 1024 characters). You can use the runtime environment variables. Also, you can add more than one parameter. Use the up and down arrows by each row to change the order of the parameters. To remove a parameter, click the X at the