Novell PLATESPIN ORCHESTRATE 2.0.2, Installation And Configuration Manual, Page: 111 / 132

First Use of Basic PlateSpin Orchestrate Components 111
no
vd
ocx
(e
n)
13
Ma
y 20
09
To verify this, you can view the resource account that you created earlier in Walkthrough: Creating a
Resource Account (page 103) by selecting its object in the Explorer panel. By default, the Info/
Groups page for the resource opens in the Development Client workspace.
Figure 3-3
Resource Information Page After Discovery Jobs Run
If you scroll down on the Info/Groups page, you see that the discovery jobs have gathered basic data
about the processor and operating system of this computing node. If the jobs had not run at resource
start, this information about the resource would not be ready for use.
Now that you have seen a how jobs are run by the PlateSpin Orchestrate system on resource start,
you can walk through the process of deploying and running a sample job on your own by proceeding
with
Section 3.5, “Walkthrough: Deploying a Sample Job,” on page 111 .
3.5 Walkthrough: Deploying a Sample Job
One of the main functions of the PlateSpin Orchestrate Server is to run application requests, called
jobs, on grid resources. Because the Orchestrate Server is capable of handling multiple application
requests, it uses a policy-based broker and scheduler to decide when and how a job should run on the
resources. These decisions are based on many controlled factors, including the number of resource
nodes, their cost, and a variety of other factors as requested by the application, but managed under
policy constraints set up by the administrator or the job developer.
Developing a job involves the creation of an application executable and a job file. See the PlateSpin
Orchestrate 2.0 Developer Guide and Reference for more information on creating and building jobs
by using the PlateSpin Orchestrate Job Description Language (JDL) and the job policies.
Before a job can run, the PlateSpin Orchestrate administrator must deploy it, which involves moving
it from a development state to a state where it is ready and available for users. Only the
administrator has the necessary rights to deploy a job.