2.2 Getting Started with the User Portal

This section describes how to perform some basic tasks with the ZENworks Orchestrator User Portal. The following content is included:

2.2.1 Starting the Portal

The Orchestrator Server includes a Web server that hosts the User Portal in HTML. This portal is an administration tool that helps users manage the jobs that are deployed to managed computing resources, but it does not provide a facility to run jobs, even if you are logged in as an administrator.

Use the following steps to run the portal and log in at a workstation:

  1. Create a new Orchestrator user account.

    1. Log in to the ZENworks Orchestrator Console, using the steps in Section 1.2.2, Logging in to the Orchestrator Server Console.

    2. In the Explorer view of the console, click the Users container to open it, then right-click all > New User to open the Create a new User dialog box.

    3. In the Create a new User dialog box, enter the name of the new user, then click OK.

    4. On the Info/Groups page of the workspace panel in the console, expand the Personal Information section.

    5. In the Password field of the Personal Information section, enter a password for the new user you created, then click the save icon in the toolbar.

    6. In the Password Confirmation dialog box, re-enter the password in the Confirm New Password field, click OK, then click the save icon again.

  2. Start any Internet browser.

  3. Enter the URL (server name) of the Orchestrator Server to display a page where the user can log in to the server:

    NOTE:You can also enter the name localhost as the address to the server if the browser is running locally on the server where the Orchestrator Server is installed.

  4. Enter the username and password for the user you created.

  5. Click Log In to log into the portal.

The User Portal Interface

After you log in to the portal, you will see the following interface displayed in the browser:

Figure 2-1 The User Portal Interface

The table below provides details about the various labeled areas of the interface.

Table 2-1 Descriptions of the Areas of the User Portal

Area

Description

User Login and Group Roles

This area indicates the user and group logged-in.

Main Menu

This area provides operations categorized under the menus:

  • Jobs include a list of active jobs running on the Orchestrator Server and their correlating job run information and status. The Jobs facility also includes the ability for users to control the running jobs with various functions.

  • Run Job provides a facility to submit a job to the Orchestrator Server with a selection of parameters for the job and policies; the conditions for which the job is to run.

  • Resource Search provides a facility to discover the resources that are available for use, including jobs, policies, and computing resources available for running jobs.

  • Logout provides a facility to end a user session.

View Filters

This area provides a way to filter the view of current running jobs. Depending on the function view, this panel may vary.

View and Function

This area displays jobs. Other functions use this area for displaying computing resources and reports on the requested information. This is the general area of the portal for interacting with the user’s requested data.

Commands

These context-sensitive buttons provide a set of commands for the functions that can be performed on the data in the View and Function area.

Help

This area displays context-sensitive help information.

2.2.2 Identifying Available Jobs

After you log in, you can use the portal for Orchestrator to identify the available jobs that can be run in the ZENworks Orchestrator system. The portal lists the same runnable jobs that are available for viewing in the console for Orchestrator.

IMPORTANT:A job must exist before you can configure it. Creating a job involves the creation of an application executable and a job file. If you want to create your own jobs, see the ZENworks Orchestration Developer’s Toolkit Guide [not available in this release]. The guide has more information about creating and building jobs using the Orchestrator Job Description Language (JDL) and job policies.

ZENworks Orchestrator includes prepackaged jobs for demonstration. Prepackaged jobs are automatically deployed with each new server each time it is started. These jobs include demoIterator, failover, quickie, and subjobs.

To see runnable jobs from the portal command menus, click Run Job in the menu bar to open the Run Job menu screen.

The Select Job tab is listed in the View and Function section of the portal interface. The Available Jobs explorer is located on the left side of this interface. The Job Parameters section is located on the right side. The Job Parameters section is associated with job selections in the Available Jobs explorer. To view all jobs, expand the explorer under Available Jobs > all.

Figure 2-2 The Available Jobs Explorer View Expanded to Show All Jobs

2.2.3 Starting a Local Job from the Server

There are three stages to running an Orchestrator job on managed computing resources. This section uses the example job, “quickie,” to illustrate these stages:

NOTE:Quickie is a demonstration job used primarily to show computing resource utilization. Its purpose is to simply start its executable program on an appropriate computing resource in the grid, wait for a period of time, and then stop to free the computing resource again.

Selecting the Job You Want to Run

When you want to start a job locally from the server, you need to first select the job and its parameters. The portal interface labels this as the What stage of running a job.

Use the following steps to select the job and job parameters you want to run:

  1. From the Select Job Explorer, expand the Available Jobs directory tree to demos.

    This lists the demo jobs highlighted above that come with the server for Orchestrator.

  2. Select the quickie job to display its job parameters in the Job Parameters area of the interface.

    NOTE:If you need more information about a job parameter, click Desc to expand the description of the fields of the Job Parameters area.

  3. Accept the default values for the parameters.

    NOTE:The numbjoblets parameter is an argument for the associated job. The default parameter value for the quickie job is 100.

  4. Click Lock Job (located at the bottom-right of the Function Area of the Portal) to select the job.

The What stage on the interface now lists the quickie job selection. If you want to change the job selection or its parameters, you can click Edit on this stage anytime before you actually run the job.

Selecting Computing Resources to Run the Job

After the job is selected, users need to identify the computing resources where the job is to be run. The portal interface labels this as the Where stage.

Searching for computing resources is possible using the Resource Search facility accessed from the main menu. When the Resource Search page is displayed, users can select computing resource search criteria to use as operators to search for the computing resources they want.

IMPORTANT:The Resource Search tab area shows a set of filters for identifying computing resources. A resource is a computing resource that can run jobs. Your grid might have different kinds of computing resources, identified by a set of facts about that computing resource. A resource fact includes many attributes about that computing resource such as its name, hardware configuration, operating system, and other characteristics. If the grid has uniform resources, the Where stage is less useful, but for a grid with multiple resource characteristics, the Where stage is very important.

Depending on the resources that you have set up with the server for Orchestrator, you might have multiple computing resource operating system types (operating system fact). For example, you could have both Windows and Linux operating system resources available. Some of the sample demo jobs that come with the server for Orchestrator have executables for both operating systems, and others do not. The quickie job can run on both Windows and Linux.

Using Expressions to Identify Appropriate Computing Resources

A simple expression is used for identifying the computing resources appropriate for running a job. Multiple expressions can be applied, but all expressions must be true. Each expression is entered using the expression criteria listed in the following table.

Table 2-2 Expressions Used to Filter Computing Resources Eligible to Run Jobs

Expression

Criteria

Facts

Each computing resource has a set of Facts associated with a resource. A complete list of facts is available from the Select Fact drop-down list for computing resources.

Operator

Each expression requires one operator.

Value

The value criteria indicate the choice associated with the selected fact. The portal generates a list of possible value options based on the selected Fact and the possible values from the current set of resources.

When you select a value, it is entered into the criteria edit field to the right of the value selection field. You can edit the value in this field if necessary.

Multiple criteria may be entered in the same fashion. The selection of computing resources must match all criteria entered. You can alter your choice of expressions using the following functions:

  • To remove criteria, click the minus icon located to the right of the criteria.

  • To start a new search or to start over, click Reset located below the criteria list.

  • To add more criteria, click on the plus icon.

When you have entered all of the search criteria, click Search. The matching resources are listed at the lower part of the page under Search Results.

Sample Job: Selecting Computing Resources for Running a Job

IMPORTANT:If no search facts are selected, the Orchestrator assumes that all computing resources are to be selected.

The following steps demonstrate how the quickie job is configured to run only on Windows XP operating system computing resources:

  1. From the Select Fact drop-down list, select the operating system fact.

  2. Specify the operator to use for the fact. In this case the default, is equal to, is used.

  3. Specify the fact value, Windows XP.

    NOTE:Each of the drop-down items is context sensitive. When a fact is selected, the values update with the valid options for that fact, based on the current set of available computing resources. The values change automatically as computing resources are added or removed in the grid of managed resources.

  4. Click Search to check whether any computing resources match the current search filter criteria. If so, these computing resources are listed at the bottom of the Function area of the portal. See the figure below for an example.

  5. Click Lock Criteria (located at the bottom-right of the Function area of the portal) to select the computing resources.

Notice the Where section (located at the top of the Function area of the portal) now shows the quickie job resource selections. To change the computing resource selection, click Edit before running a job.

Scheduling a Time to Run the Job

After you have selected a job and the computing resource where you want to run it, you need to select a start time for running the job. The portal labels this as the When stage of running a job.

The Reservation tab area shows start and end requirements, as well as a priority setting for running the job. You can set up policies associated with the user’s profile to control when a job can be run. In the When stage, however, the user can add an additional scheduling requirement and job priority for this running this job.

Use the following steps to specify when the job is to be run.

  1. Click the Reservation tab, click the calendar icon located adjacent to the Start field to open a calendar scheduling utility, then select a date and time to run the job. You can accept the default in the Start field: As Soon As Possible if you want to.

  2. (Optional) Click the calendar icon located adjacent to the End field, then select a date and time to complete the job. You can also accept the default in the End field: Job Duration.

  3. (Optional) If the Priority field, click the drop-down list to select a priority for the job, or accept the default.

    Use the Priority parameter to increase or decrease the priority of the job in relation to other jobs that are already running or scheduled to run. This option is used only if computing resources are inadequate at the scheduled job start time to run the job. The options in the drop-down list are context sensitive to the available priorities associated with the user profile.

  4. Click Lock Time (located at the bottom-right of the Function area) to finalize the time to run the job.

The job is now ready to run. The job criteria are displayed in the upper part of the Functional area of the portal.

Figure 2-3 The User Portal Displaying the Job Run Criteria Previously Selected

Running the Job

When you have established the job run criteria in the User Portal, click Go to schedule the job to run. A progress log is displayed in the Progress tab in the Function area of the portal.

Figure 2-4 Progress Message Displayed for the “Quickie” Job

A Done message indicates that the job was successfully submitted to the server for ZENworks Orchestrator.

Click OK to close the Progress log and return to the Home page to monitor the running job.

NOTE:This same job could also be run using the following zos command:

zos run quickie.job -- priority=high -- policy=os.windows/xp

For more information about using the zos command line interface, see Section A.0, The Zos Command Line Tool.

2.2.4 Monitoring a Job

Users can access a list of the Orchestrator jobs that are currently running by clicking the Jobs command menu and then the Jobs submenu on the User Portal.

Figure 2-5 Jobs Command Menu on the User Portal

The Job Status page under the Jobs submenu lists information about jobs submitted to the Orchestrator. Users can use this information to monitor and manage those jobs.

Figure 2-6 Job Status Page Showing the Job Filter Drop Down List

A list of jobs is displayed based on the filter criteria selected. The default filter criteria is all jobs for the current logged-in user. Filter options include:

  • Users: Select a user, or one of the built-in group types: group_all for all user groups, or group_system for all system jobs.

  • Job: Select a specific job, or the built-in group types: group_all for all jobs.

  • History: Select jobs submitted within the last nn hours or nn days from the current date and time. The minimum time you can set is 1 hour. The maximum time you can set is 24 days. If you select none as the history time, all jobs are selected.

When you have selected the filter criteria you want, you can update the current job status. Click Refresh (located at the bottom-right of the interface) to show the status.

Figure 2-7 Status Information for a Current Job

The job status report includes the following columns:

  • The far left column indicates the result for the job status report as sampled at refresh time. The column displays the result with both an icon and text indicators. The job result types are Scheduled, Running, Failed, or Completed.

  • Identification: This column lists job submission information, including User, Job, Name, and Priority.

  • Schedule: This column lists information about when the job is scheduled, or its actual start time. It also includes how long the job has been running. If the job is completed, the column also includes the total elapsed run time for job.

  • Status: This column lists information about the cost and progress of a job. For jobs that are currently running, the progress indicator bar is partially filled with the percentage of job completion. Cost indicates the current cost utilization for a running job, or the total cost for completed and failed jobs. The cost of a job is based on policies set up by administrator for Orchestrator.

  • Misc: This column lists other useful information about a job, including its Subjobs, its Joblets (the number of independent pieces of work running on each computing resource), its Errors.

    If the number of subjobs is greater than 0, a view… link displays in this column. Click this link to show a Job Tree hierarchy under the Filter settings for the job. All of the subjobs in the job hierarchy are shown.

    Figure 2-8 Job Tree Hierarchy Displayed on the Job Status Page

    Click Root in the tree to return to the default Job Status display, which is based on the current filter criteria.

Using the Command Line Interface to Monitor Jobs

Use the following command repeatedly if you want to use the command line interface to monitor the job:

zos status

By default, Orchestrator returns the status of the last job to run.

For more detailed information about using the zos command line interface, see Section A.0, The Zos Command Line Tool.

2.2.5 Viewing the Job Log

From the Jobs menu in the portal interface, some jobs might display a log… link on the Identification column of the Job Status page.

Figure 2-9 Job Identification with an Available Log Link

Selecting this link displays the logging information for the job. The logging display stays current for the job shown running. When the job is completed, its complete log is displayed.

2.2.6 Pausing and Resuming a Running Job

From the Jobs menu in the portal, display the job to pause or resume by including it in the Job Status list using the filters. Select the running job to pause or resume using the check box on the left side. Then click Pause or Resume on the bottom of the page. A new page displays indicating the status of the request. Click OK to return to the Job Status page.

2.2.7 Cancelling a Running Job

Use the following steps to cancel a job that is already running.

  1. From the Jobs menu, display the job to cancel by including it in the Job Status list using the filters.

  2. Select the running Job you want to cancel using the check box on the left side.

  3. Click Cancel.

    A new page displays indicating the status of the cancel request.

  4. Click OK to return to the Job Status page.

2.2.8 Logging Out of the Portal

To log out of the User Portal, click the Logout option under the Main Menu.