Novell ZENworks Orchestrator 1.3 Developer Guide and Reference

The Novell® ZENworks Orchestrator Job Development Guide is a component of the Novell ZENworks Orchestrator documentation library. While Orchestrator provides the broad framework and networking tools to manage complex virtual machines and high performance computing resources in a datacenter, this guide explains how to develop grid application jobs and polices that form the basis of Orchestrator functionality. This guide provides developer information to create and run custom Orchestrator jobs. It also helps provides the basis to build, debug, and maintain policies using Orchestrator.

This guide contains the following sections:

Audience

This guide is intended for use by application developers and technically advanced datacenter technicians assigned to write Job Description Language (JDL) jobs to manage all resources in a Orchestrator-enabled environment. It assumes that users have the following background:

Documentation Updates

For the most recent version of this Installation and Getting Started Guide, visit the ZENworks Orchestrator 1.3 Web site.

Additional Documentation

For additional documentation that might assist you in developing Orchestrator jobs, see the following guides:

Documentation Conventions

In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux or UNIX, should use forward slashes as required by your software.

Other typographical conventions used in this guide include the following:

Convention

Description

Italics

Indicates variables, new terms and concepts, and book titles. For example, a job is a piece of work that describes how an application can be run in Grid Management on multiple computers.

Boldface

Used for advisory terms such as Note, Tip, Important, Caution, and Warning.

Keycaps

Used to indicate keys on the keyboard that you press to implement an action. If you must press two or more keys simultaneously, keycaps are joined with a hyphen. For example,

Ctrl-C. Indicates that you must press two or more keys to implement an action.

Simultaneous keystrokes (in which you press down the first key while you type the second character) are joined with a hyphen; for example, press Stop-a.

Consecutive keystrokes (in which you press down the first key, then type the second character) are joined with a plus sign; for example, press F4+q.

Fixed-width

Used to indicate various types of items. These include:

Commands that you enter directly, code examples, user type-ins in body text, and options. For example,

cd mydir

System.out.println("Hello World");

Enter abc123 in the Password box, then click Next.

-keep option

Jobs and policy keywords and identifiers. For example,

<run>

</run>

File and directory names. For example,

/usr/local/bin

Note: UNIX path names are used throughout and are indicated with a forward slash (/). If you are using the Windows platform, substitute backslashes (\) for the forward slashes (/).

Fixed-width italic

and

<Fixed-width italic>

Indicates variables in commands and code. For example,

zos login <servername> [--user=] [--passwd=] [--port=]

Note: Angle brackets (< >) are used to indicate variables in directory paths and command options.

| (pipe)

Used as a separator in menu commands that you select in a graphical user interface (GUI), and to separate choices in a syntax line. For example,

File|New

{a|b|c}

[a|b|c]

{ } (braces)

Indicates a set of required choices in a syntax line. For example,

{a|b|c}

means you must choose a, b, or c.

[ ] (brackets)

Indicates optional items in a syntax line. For example,

[a|b|c]

means you can choose a, b, c, or nothing.

< > (angle brackets)

Used for XML content elements and tags, and to indicate variables in directory paths and command options. For example,

<template>

<DIR>

-class <class>

. . . (horizontal ellipses)

Used to indicate that portions of a code example have been omitted to simplify the discussion, and to indicate that an argument can be repeated several times in a command line. For example,

zosadmin [options|optfile.xmlc ...] docfile

plain text

Used for URLs, generic references to objects, and all items that do not require special typography. For example,

http://www.novell.com/documentation/index.html

The presentation object is in the presentation layer.

ALL CAPS

Used for SQL statements and HTML elements. For example,

CREATE statement

<INPUT>

lowercase

Used for XML elements. For example,

<onevent>

Note: XML is case-sensitive. If an existing XML element uses mixed-case or uppercase, it is shown in that case. Otherwise, XML elements are in lowercase.

ZENworks Orchestrator Server root directory

Where the ZENworks Orchestrator Server is installed. The Orchestrator executables and libraries are in a directory. This directory is referred to as the ZENworks Orchestrator Server root directory or <ZENworks Orchestrator Server_root>.

Paths

UNIX path names are used throughout and are indicated with a forward slash (/). If you are using the Windows platform, substitute backslashes (\) for the forward slashes (/). For example,

UNIX: /usr/local/bin

Windows: \usr\local\bin

URLs

URLs are indicated in plain text and are generally fully qualified. For example,

http://www.novell.com/documentation/index.html

Screen shots

Most screen shots reflect the Microsoft Windows look and feel.

Feedback

We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.

Novell Support

Novell offers a support program designed to assist with technical support and consulting needs. The Novell support team can help with installing and using the Novell product, developing and debugging code, maintaining the deployed applications, providing onsite consulting services, and delivering enterprise-level support.