NetIQ Doc: PlateSpin Orchestrate 2.6 Developer Guide and Reference - Using Deployable Job Examples Included with Platespin Orchestrate

7.3 Using Deployable Job Examples Included with Platespin Orchestrate

The basic examples delivered with PlateSpin Orchestrate are located in either of two possible installation directories depending on the type of installation. For server installations, look here:

/opt/novell/zenworks/zos/server/examples/

For client installation, look here:

/opt/novell/zenworks/zos/client/examples/

When you unjar or unzip examples from the <path>/examples/<example>.job file or view jobs using the details panel and the JDL and Policy tabs in PlateSpin Orchestrate Development Client, you should see the .jdl and .policy files.

Policy files specify how the job arguments and static attributes are defined. Or, you can use the zos jobinfo command to simply display job arguments and their default values.

All of the examples can be opened and modified using a standard code editor, then redeployed and examined using the procedure explained in Walkthrough: Deploying a Sample Job in the PlateSpin Orchestrate 2.6 Installation and Configuration Guide.

This section includes the following information:

You can find the detailed deployable job example documentation in the following sections:

7.3.1 Preparing to Deploy Job Examples

To run the PlateSpin Orchestrate jobs described in this section, use the following guidelines:

Install and configure PlateSpin Orchestrate properly (see Installing and Configuring All PlateSpin Orchestrate Components Together in the PlateSpin Orchestrate 2.6 Installation and Configuration Guide.
Unless otherwise indicated, install at least one agent on a managed resource and have it running (see Installing the PlateSpin Orchestrate Agent on Other Supported Operating Systems in the PlateSpin Orchestrate 2.6 Installation and Configuration Guide).
Before running zosadmin or zos commands, you must log into the Orchestrate Server.

The zosadmin command is required for administrating jobs. This includes deploying and undeploying a job to the server. The zos command is for job control, including starting a job and viewing a job’s log. As you learn about the PlateSpin Orchestrate job samples, you will use the zosadmin command for deploying a sample job and the zos command for running the sample.
- For an explanation of the zosadmin commands, see The zosadmin Command Line Tool in the PlateSpin Orchestrate 2.6 Command Line Reference.
```
> zosadmin login --user psoadmin
Login to server: skate
Please enter current password for 'psoadmin':
Logged into grid on server 'skate'
```
- For an explanation of zos commands, see The zos Command Line Tool in the PlateSpin Orchestrate 2.6 Command Line Reference.
```
> zos login --user psouser
Please enter current password for 'psouser':
Logged into grid as psouser
```
You should create a user (see Walkthrough: Creating a User Account in the PlateSpin Orchestrate 2.6 Installation and Configuration Guide) before logging in.

7.3.2 Summary of PlateSpin Orchestrate Deployable Job Examples

The following table provides a high-level explanation of the PlateSpin Orchestrate job examples that are delivered with PlateSpin Orchestrate and the job developer concepts you might want to understand:

Table 7-1 PlateSpin Orchestrate Job Development Examples

Example Name	Job Function Capabilities
demoIterator.job	Using policy constraints and job arguments to restrict joblet execution to specific resources. Scheduling joblets using a ParameterSpace. Provides an example of executing a command on a resource.
dgtest.job	Downloading files stored on grid management servers to networked nodes.
failover.job	Managing how joblets failover to enhance the robutsness of your jobs.
instclients.job	Installing an PlateSpin Orchestrate client on multiple machines. Provides an example of executing a command on a resource.
jobargs.job	Understanding the various argument types that jobs can accept (integer, real, Boolean, string, time, date, list, dictionary, and array, which can contain the types integer, real, Boolean, time, date, and String).
notepad.job	Understanding how to launch specific applications on specified resources.
quickie.job	Understanding how jobs can start multiple instances of a joblet on one or more resources.
sweeper.job	Understanding how poll all resources on the grid.an ordered serialized scheduling of the joblets
whoami.job	Sending a command to the operating system’s default command interpreter. On Microsoft Windows, this is cmd.exe. On POSIX systems, this is /bin/sh.