Nolio ASAP 3 2 User Guide

© 2011 Nolio Ltd. All rights reserved

The information contained herein is proprietary and confidential. No part of this document may be reproduced without explicit prior written permission from Nolio Ltd.

Contents

Nolio Automation Center iii

Conten ts Preface ........................................................................................................................ viii

Introducing the Nolio Automation Center ....................................................................... 1

How Nolio Works .......................................................................................................... 1 A Typical Workflow........................................................................................................ 1

Getting Started with Nolio Automation Center ............................................................... 3

Logging in to Nolio Automation Center ............................................................................. 3 Using Nolio Automation Center ....................................................................................... 4

Main Screen ............................................................................................................ 4 Navigation Panel ...................................................................................................... 5

Revealing and Hiding the Navigation Panel ............................................................. 5 Navigating between Nolio Automation Center Screens .............................................. 5

Menu Bar ................................................................................................................ 6 Status Bar ............................................................................................................... 6

Saving Changes ............................................................................................................ 6 Searching for Items ...................................................................................................... 6 Changing Your Account Settings ..................................................................................... 7 Switching the Current User ............................................................................................ 8 Logging Out of Nolio Automation Center .......................................................................... 9 Quitting Nolio Automation Center .................................................................................... 9 Getting Help ................................................................................................................. 9

Setting Up Processes .................................................................................................... 11

Using the Processes Screen ........................................................................................... 11 Revealing and Hiding the Parameters Browser ............................................................ 12 Filtering the View .................................................................................................... 12

Using the Components Tab ........................................................................................... 13 Components Tab Navigation Panel ............................................................................ 13

Applications Components Tree ............................................................................. 14 Components Tab Central Pane .................................................................................. 14 Browsing the Components Tab Parameters ................................................................. 15

Working with Applications and Components .................................................................... 15 Adding Applications ................................................................................................. 16 Editing Applications ................................................................................................. 16 Deleting Applications ............................................................................................... 17 Adding Components ................................................................................................ 17 Editing Components ................................................................................................ 18 Deleting Components .............................................................................................. 19

Elaborating Component Actions .................................................................................... 20

Overview .................................................................................................................... 20 Working with Actions .................................................................................................... 21

Using Component Categories .................................................................................... 21

User's Guide Contents

iv Nolio Automation Center

Adding Component Categories ............................................................................. 21 Editing Component Categories ............................................................................. 22 Deleting Component Categories ........................................................................... 22

Defining Actions ...................................................................................................... 23 Adding Actions ................................................................................................... 23 Viewing and Editing Actions ................................................................................. 25 Reverting Actions ............................................................................................... 26 Copying, Cutting, and Pasting an Action ................................................................ 27 Deleting Actions ................................................................................................. 29

Defining Parameters for Actions ..................................................................................... 30 Using Parameters Folders ......................................................................................... 30

Adding and Editing Parameter Folders ................................................................... 30 Editing Parameter Folders.................................................................................... 31 Deleting Parameter Folders .................................................................................. 31

Adding Parameters .................................................................................................. 32 Editing Parameters .................................................................................................. 33 Overriding Parameters ............................................................................................. 34

Reverting an Overridden Process Parameter .......................................................... 34 Copying, Cutting, and Pasting a Parameter ................................................................. 35 Deleting Parameters ................................................................................................ 36 Action Parameter Types and Properties ...................................................................... 36 Testing Actions ....................................................................................................... 37

Debugging Using the Conflicts Browser ................................................................. 38 Creating Action Flows ................................................................................................... 40

Overview .................................................................................................................... 40 Methodology ............................................................................................................... 41 Working with Flows ...................................................................................................... 41

Adding Flows .......................................................................................................... 41 Editing Flows .......................................................................................................... 42 Copying, Cutting, and Pasting a Flow ......................................................................... 43 Viewing Flows ......................................................................................................... 44

Overview a Flow Diagram .................................................................................... 44 Resizing the Flow Diagram................................................................................... 44 Displaying Definitions of Actions Instantiated within a Flow ..................................... 44

Deleting Flows ........................................................................................................ 45 Assembling Flow Steps ................................................................................................. 45

Adding Flow Steps ................................................................................................... 45 Deleting Flow Steps ................................................................................................. 48 Step-related Icons and Symbols ............................................................................... 48 Linking Steps in a Flow Sequence .............................................................................. 48

Manually Adding Flow Lines ................................................................................. 49 Changing the Step from which a Flow Line Exits ..................................................... 50 Deleting Flow Lines ............................................................................................. 51

Setting Step Transition Conditions ............................................................................. 51

Contents

Nolio Automation Center v

Sample Flow ........................................................................................................... 53 Defining Loops ............................................................................................................ 53 Testing Flows .............................................................................................................. 54

Designing Applications Processes ................................................................................. 55

Overview .................................................................................................................... 55 Using the Processes Tab ............................................................................................... 56

Processes Tab Navigation Panel ................................................................................ 57 Processes Tab Central Pane ...................................................................................... 57 Processes Tab Parameters Browser ........................................................................... 58

Declaring Application Server Types ................................................................................ 59 Adding Server Types to Applications .......................................................................... 59 Editing Server Types for Applications ......................................................................... 60 Deleting Server Types from Applications .................................................................... 61

Working with Architectures ........................................................................................... 61 Adding Architectures ............................................................................................... 62 Editing Architectures ............................................................................................... 63 Deleting Architectures ............................................................................................. 63 Declaring Architecture Server Types .......................................................................... 63

Adding Server Types to Architectures.................................................................... 64 Editing Server Types for Architectures .................................................................. 64 Deleting Server Types from Architectures .............................................................. 65 Assigning the Multi-Server Type Agent .................................................................. 65 Defining a Server Type to Run Multiple Processes Concurrently from an Architecture .. 66

Working with Processes ................................................................................................ 66 Using Process Categories ......................................................................................... 66

Adding Process Categories ................................................................................... 66 Editing Process Categories ................................................................................... 67 Deleting Process Categories ................................................................................. 67

Defining and Developing Processes ............................................................................ 68 Adding Processes ............................................................................................... 68 Editing Processes ............................................................................................... 69 Deleting Processes ............................................................................................. 69

Defining a Server Type to Run Multiple Processes Concurrently from a Process ............... 70 Process Workspace .................................................................................................. 70 Assembling Processes .............................................................................................. 70

Instantiating Flows and Actions in Processes .......................................................... 71 Integrating Component-Consistent Steps in Processes ....................................... 71 Inconsistent Example ..................................................................................... 72

Sequencing Process Steps ................................................................................... 72 Sequencing Operations Between Different Servers ............................................. 73 Specifying Which Server to Wait For ................................................................ 73

Publishing Processes ................................................................................................ 73 Publishing Processes ........................................................................................... 74 Viewing Published Processes ................................................................................ 74

User's Guide Contents

vi Nolio Automation Center

Promoting Published Process ................................................................................ 75 Unpublishing Published Processes ......................................................................... 75

Automating Applications Processes .............................................................................. 76

Using the Run Environment Screen ................................................................................ 76 Defining Environments ............................................................................................. 77

Creating New Environments ................................................................................. 77 Environment Fields ........................................................................................ 79

Editing Environments .......................................................................................... 79 Managing Instances and Links.............................................................................. 79 Assigning Processes to an Environment ................................................................. 80 Deleting an Environment ..................................................................................... 80

Environments Central Pane ...................................................................................... 80 Viewing an Environment ...................................................................................... 81

Instance Views and Layout Views .................................................................... 81 Quantifying Server Instances .......................................................................... 81 Linking Servers to an Environment .................................................................. 82 Linking Servers in the Instance View ................................................................ 83

Viewing Activity Information ................................................................................ 83 Current Activity ............................................................................................. 84 Recent Activity .............................................................................................. 84 Schedules ..................................................................................................... 85 Notifications .................................................................................................. 88

Process Execution Pane ....................................................................................... 90 Creating a New Process Run............................................................................ 93 Viewing a Process Run ................................................................................... 93 Viewing the Process Summary......................................................................... 94 Viewing the Events Log .................................................................................. 95 Events Log Filters .......................................................................................... 95 Viewing an Agent Execution Log ...................................................................... 96

Creating a Process Run ................................................................................................. 96 Generating Reports ...................................................................................................... 97

Overview .................................................................................................................... 97 Accessing the Reports Screen ........................................................................................ 97 Generating Audit Reports .............................................................................................. 97

Audit Report Filters ................................................................................................. 98 Generating Management Reports ................................................................................... 98

Management Report Filters ....................................................................................... 99 Viewing Reports......................................................................................................... 100

Viewing an Audit Report ......................................................................................... 100 Viewing the Process Run ................................................................................... 100 Events Log Filters ............................................................................................. 101

Viewing a Management Report ................................................................................ 101 Deleting Reports ........................................................................................................ 101

Contents

Nolio Automation Center vii

Server Definition Operations ...................................................................................... 102

Running a Process ..................................................................................................... 102 Setting Required Input Values ................................................................................ 102 Controlling a Process Run ....................................................................................... 104 Viewing the Process Run Progress ........................................................................... 104

Individual Agents Definition Operations ........................................................................ 104 Adding Agents to the Agents List ............................................................................. 105 Modifying an Agent's Definition ............................................................................... 105 Removing an Agent from the Agents List .................................................................. 105

Agents Group Operations ............................................................................................ 105 Adding an Agent Group .......................................................................................... 105 Modifying an Agent Group ...................................................................................... 106 Removing an Agent Group ..................................................................................... 106 Assigning Agents to an Agent Group ........................................................................ 106 Removing Agents from an Agent Groups .................................................................. 107

Exporting and Importing ............................................................................................ 108

Exporting .................................................................................................................. 108 Importing ................................................................................................................. 109

Appendix - Action Parameter Types ............................................................................ 111

String Parameters ...................................................................................................... 111 Password Parameters ................................................................................................. 112 Boolean Parameters ................................................................................................... 114 File Parameters ......................................................................................................... 114 Predefined Options Parameters .................................................................................... 115 General Parameters ................................................................................................... 117 Numerical Parameters ................................................................................................ 117 Array Parameters ....................................................................................................... 118

Glossary ..................................................................................................................... 120

Index ....................................................................................................................... 122

User's Guide Preface

viii Nolio Automation Center

Preface The Nolio Automation Center User Guide accompanies Nolio Automation Center in its V3.2 release.

About th is Document This document describes how to use Nolio Automation Center to automate the implementation of server-based applications.

The information contained in this document should be read by current users of Nolio Automation Center, as well as potential or trial customers of Nolio Automation Center.

The material covered in this document is the sole property of Nolio Ltd., and may not be copied or reproduced in any fashion without explicit written permission from Nolio Ltd.

At the same time, Nolio Ltd. is not liable for any information, correct or incorrect, appearing in this document that may result in damages incurred by the user regardless of whether or not such damages resulted from the information provided herein, in conjunction with or totally independent from use of Nolio Automation Center.

In tended Audience This documentation is intended for the following audience:

• Development and/or QA personnel who will work in Nolio Automation Center and design the application and its various components that will be implemented (deployed, maintained, and cleaned, etc.) by means of the automated processes generated by Nolio Automation Center.

• System Administrators responsible for the ongoing use and maintenance of your company's application servers.

System administrators responsible for the installation of software on all workstations should refer to the Nolio Automation Center Installation Guide supplied with this release.

Technica l Support If you have any questions, please feel free to contact Nolio technical support.

• Telephone:

USA/Canada Toll free number: 1-888-869-8485

United Kingdom Toll free number: 0-800-680-0429

• Email: [email protected]

mailto:[email protected]?subject=Nolio%20Automation%20Center%20User's%20Guide�

Introducing the Nolio Automation Center

Nolio Automation Center 1

Chapte r 1

In This Chapter How Nolio Works ..................................................................................................................................................... 1 A Typical Workflow .................................................................................................................................................. 1

A number of relatively recent technological developments have brought about a significant expansion in the sale and distribution of software systems as server-based applications. These developments include:

• Multi-user operating systems that support the concurrent running of applications by numerous users on the same server, while providing each user with a protected session;

• The freeing of application performance from bandwidth constraints by implementing an efficient separation of the application's logic from its user interface (keystrokes, mouse clicks, and screen updates);

• Networking infrastructures, both hardware and software, that enable the centralized and secure management of server applications and their communication with client stations.

Not only have these technological developments made this model of marketing software feasible, in most cases this approach has resulted in a significant decrease in cost and an increase in return on investment (ROI) for the companies involved.

Therefore, the major impediment to a truly efficient, timely, and profitable deployment of server-based applications is the time-intensive involvement of the personnel required to frequently redeploy them.

Nolio Automation Center by Nolio directly addresses and effectively eliminates this problem by automating the deployment of server-based applications.

How Nolio Works Nolio Automation Center works as follows:

1. Nolio Automation Center is used to model the deployment of any number of server-based applications owned by the organization.

2. Applications are then published, making them accessible to the operations personnel responsible for application implementation.

3. When applications are implemented, Nolio Automation Center passes the appropriate instructions to the dedicated Nolio Agents on the relevant servers.

4. The Nolio Agents then implement the instructions on the servers.

A Typica l Workflow The following table details in sequential order the general workflow that is involved in designing a server-based application with Nolio Automation Center and its automated implementation.

Table 1: Nolio Automatio n Center Workflow

No. Work Phase Tab(s) > Command Designing Applications

In troduc ing the Nolio Automation Cente r

User's Guide Introducing the Nolio Automation Center

2 Nolio Automation Center

No. Work Phase Tab(s) > Command 1 Invoke Nolio Automation Center (see "Logging in

to Nolio Automation Center" on page 3) Run from Windows desktop

2 Define Applications (see "Adding Applications" on page 16)

Components tab > Navigation View

3 Define Components for Applications (see "Elaborating Component Actions" on page 20)

Components tab > Navigation View

4 Make predefined Actions available for use by application Components (see "Working with Actions" on page 21)

Components tab > Center pane

5 Design sequential flows of Actions that subsequently can be instantiated by Processes (see "Creating Action Flows" on page 40)

Components tab > Center pane (Flows)

6 Define Architectures for Applications being designed (see "Adding Architectures" on page 62)

Processes tab > Navigation View > New Architecture command

7 Assign abstract Servers that can be used to handle the Processes defined for an Architecture (see "Declaring Architecture Server Types" on page 63)

Processes tab > Architecture View > Add New Server Type button

8 Define an Architecture's Processes by instantiating Actions and Flows of Actions previously defined for Application Components (see "Working with Processes" on page 66)

Processes tab > Process View > Add Action button

Running Designed Applications 1 Go to Environment View (see "Using the Run

Environment Screen" on page 76)

2 Create a new Environment in which an available Process is to be implemented on a specific Architecture defined for an Application Component (see "Defining Environments" on page 77)

Navigation View > Add New Environment command; in pop-up dialog, select the architecture to be used in the implementation of the process

3 Map the real physical Servers that are to be used for each of the Servers (and instances) in the given Environment (see "Instance Views and Layout Views" on page 81)

Environment view > Instances tab > click on IP or "empty" Server

4 From the Processes that are available for an architecture, select those that are to be run in the current Environment. When you select a Process, its flow is displayed in the window. From here you decide if it is a selective run and define parameters as necessary (see "Assigning Processes to an Environment" on page 80)

Environment view > right-click the Environment and select Manage Process

5 Run the Process (see "Running a Process" on page 102)

Getting Started with Nolio Automation Center


Chapte r 2

In This Chapter Logging in to Nolio Automation Center .................................................................................................................... 3 Using Nolio Automation Center ............................................................................................................................... 4 Saving Changes ...................................................................................................................................................... 6 Searching for Items .................................................................................................................................................. 6 Changing Your Account Settings ............................................................................................................................. 7 Switching the Current User ...................................................................................................................................... 8 Logging Out of Nolio Automation Center ................................................................................................................. 9 Quitting Nolio Automation Center ............................................................................................................................ 9 Getting Help ............................................................................................................................................................. 9

This section contains all the information necessary to start using Nolio Automation Center.

Logging in to Nolio Automation Center To log in to Nolio Automation Center:

1. After you have completed installation, on the desktop, double-click .

OR

(If installation has not been performed from your client machine) Open a Web browser and connect to the Data Management Server: http://<IP>:<port>,

where <IP> is the IP address of the Data Management Server, and

<port> is the port setup during installation. The default <port> is 8080.

The Data Management Server Web page appears.

2. Click the Nolio Automation Center button. The Login dialog appears.

3. In the Nolio Application Center Details field:

Type the URL of the Nolio Automation Center server.

OR

Select the desired URL from the drop-down list.

4. In the User Name field, type your user name.

5. In the Password field, type your password.

Getting S ta rted with Nolio Automation Cente r

User's Guide Getting Started with Nolio Automation Center


6. Click Login. Nolio Automation Center opens displaying the Environments tab of the Processes screen.

Us ing Nolio Automation Center The Nolio Automation Center interface includes the following components:

• Main Screen (on page 4)

• Navigation Panel (on page 5)

• Menu Bar (on page 6)

• Status Bar (on page 6)

Main Screen There are three different main screens in Nolio Automation Center:

• The Processes screen, in which users with Design Processes access level can design any number of server-based deployment applications required by the organization, and users with Publishing Processes access level can publish these applications to the Run Processes screen

• The Reports screen, in which all users can generate and view reports

• The Administration screen, in which users with Superuser role can perform administrative tasks, including managing Nolio Automation Center users, permissions, available actions, published processes, agents, test agents, and system settings

Each of these screens is explained in detail in the relevant sections of this guide.



Note: If you do not have the required role or access level to view a specific screen, the screen will not appear in Nolio Automation Center. To find out which user role and access level you have, consult with the Nolio Automation Center administrator. For information on user roles and access levels, see the Users Management section in the Installation and Administration Guide.

Navigation Panel The Navigation Panel appears on the left side of the Nolio Automation Center window.

The top part of this panel contains an Applications drop-down menu listing the names of the applications. In the area below it, the Application tree appears, displaying all the components that make up the application. The exact contents of the tree vary per screen displayed in Nolio Automation Center.

The bottom of the panel contains a set of buttons that enable you to navigate between screens.

Note: If you are using the trial version, these buttons do not appear.

Revea ling and Hiding the Naviga tion Pane l The Navigation Panel initially appears as a pane on the left side of the Nolio Automation Center window.

If desired, it can be hidden, in which case its location is marked by the vertically aligned Navigation Panel tab situated at the left edge of the Nolio Automation Center window.

To hide the Naviga tion Panel:

• In the upper-right corner of the Navigation Panel, click . The Navigation Panel is hidden, and a tab appears on the left edge of the Nolio Automation Center window.

To dis p lay the Naviga tion Panel: 1. Position the mouse pointer over the Navigation Panel tab. The Navigation Panel appears.

2. In the upper-right corner of the Navigation Panel, click . The Navigation Panel remains in view.

Naviga ting be tween Nolio Automation Center Screens To navigate to a Nolio Automation Center screen, you must have the appropriate user role and access level. For example, only users with Design Processes access level can access the Processes screen, and only users with Superuser role can access the Administration screen. If you do not have the required role and access level for a screen, the relevant button will not appear in the Navigation Panel.

For information on the required role and access level for each screen, see the Users Management section in the Installation and Administration Guide.

Note: The following instructions explain how to navigate between screens using the Navigation Panel. However, Superusers can also use the Administration menu to navigate between screens.

To naviga te to the Proces s es s creen:

• At the bottom of the Navigation Panel, click .

To naviga te to the Reports s creen:


To naviga te to the Adminis tra tion s creen:




Menu Bar The Menu Bar enables you to perform various actions in Nolio Automation Center, such as viewing notifications, logging out, and more.

The Menu Bar content depends on your user role:

• File - Provides links for:

Account settings

Notifications

Exporting and importing your application data

Logging out of your ASAP session and quitting the session

• Activity - Provides an additional way of navigating between the Nolio Automation Center main screens:

Components

Processes

Environment

• Administration - Appears only for users with the role of Superuser; provides links to ASAP administration functions.

• Help - Offers three groups of help links:

Open the logs folder

Online help for:

Automation Center

Administration

Actions

Nolio Support Website

Status Bar The status bar displays the server name to which the Nolio Automation Center is connected.

S aving Changes In most Nolio Automation Center screens, pages, and lists, any changes you make are immediately saved to the database.

S earch ing for Items Nolio Automation Center lists and trees enable you to search for a particular item using the Filter field. The following procedure explains how to perform a search.

Note: Some search options may not appear in all Nolio Automation Center lists and trees.

To s earch for an item: 1. In the Filter field at the top of the desired list or tree, type the name (or part of the name) of the item you want

to find.

The first item matching the specified search parameters is highlighted.



2. To set specific filter parameters, click in the Filter field. The following pop-up menu appears enabling you to set parameters by which you can filter your search.

Tab le 2: Filte r Paramete rs

Click this option To do this

Case sensitive Display only nodes that match the case of the filter string. Case insensitive Display all nodes that match the filter criteria, regardless of case. Use wild cards Allow using wildcards (*) in the filter string.

For example, to display only nodes containing "App" in them, click this option and type the filter string "*App*" (without the quotation marks). Results will include nodes with names such as "CompanyApp1".

Match from start Display only nodes whose names start with the filter string. Match anywhere Display all nodes that match the filter criteria, regardless of where the filter string

appears in the node name. Match leaf node only Display only leaf nodes (nodes without children) that match the filter criteria. Hide nodes without children Do not display nodes without child nodes. Keep the children if parent node matches

If a parent node matches the filter criteria, display its child nodes.

Changing Your Account Se ttings You can change your contact details and password.



To change your accounts s ettings : 1. In the Menu Bar, click File > Account Settings. The Edit User details dialog appears.

2. Modify the fields as desired, using the following table.

3. Click Save.

Table 3: Account Se tting Fie lds

In this field Do this For example

First Name Type your first name John Last Name Type your last name Smith Email Address Type your email address [email protected] Password Type your password mypassword Confirm Password Type your password mypassword

Switch ing the Curren t Us er To s witch to a diffe rent us er account

1. Log off of Nolio Automation Center by clicking at the top of the screen.

2. Log on again as a different user.



Logging Out o f Nolio Automation Center To log out of Nolio Automation Center: 1. In the Menu Bar, click File > Logout. The Logout from Nolio Automation Center dialog appears.

2. Click Yes. The Login - Nolio Automation Center dialog appears.

3. Log in to Nolio Automation Center following the instructions in Logging in to Nolio Automation Center (on page 3).

Qu itting Nolio Automation Center To quit Nolio Automation Center: 1. In the Menu Bar, click File > Quit. The Quit Nolio Automation Center dialog appears.

2. Click Yes. The Nolio Automation Center closes.

Ge tting Help Help is readily available from within the ASAP application.

To ge t he lp us ing Web he lp : 1. On the Menu bar, click Help.

The Help submenu displays.

2. In the submenu, select one of the following options, which will bring you to the Help pages at the Nolio application Web site:



Automation Center Help

Administration Help

Actions Help

3. If you do not see the topic you need help with in the Contents or Index, enter the topic in the Search box and

click . The search results will display in the left-hand search panel.

To s ubmit a s upport ticke t direc tly to Nolio: 1. In the Menu bar Help submenu, select Nolio Support Web Site.

2. In the Nolio Support page, click [email protected].

To ge t he lp from within AS AP Proces s es and Adminis tration tab pages :

Click .

You will be sent to the appropriate Help page for the screen at the Nolio application Web site.

Setting Up Processes


Chapte r 3

In This Chapter Using the Processes Screen ................................................................................................................................. 11 Using the Components Tab ................................................................................................................................... 13 Working with Applications and Components ......................................................................................................... 15

This section introduces the Processes screen and discusses the first stages of designing your server-based application: defining the application and its components.

These tasks are performed in the Processes screen Components tab and require you to have Design Processes access level. For information on navigating to the Processes screen, see Getting Started with Nolio Automation Center (on page 3).

Us ing the Proces s es Screen All modeling is performed in the Processes screen. This screen includes the following components:

• Navigation Panel: As in all Nolio Automation Center screens, the Navigation Panel appears on the left; however, in the Processes screen, the panel contains the following tabs: Components, Processes and Environments. All of these tabs primarily display trees, the nodes of which can either be expanded to display the children nodes, or collapsed.

• Central Pane: The content of the central pane is determined by the selected Navigation Panel tab, and the selected item in the tree view of that Navigation Panel tab.

Setting Up Proces s es

User's Guide Setting Up Processes


• Parameters Browser: The content of the Parameters browser is determined by the selected item in the tree view of the Navigation Panel tab.

Revealing and Hiding the Parameters Brows er The Parameters browser initially appears as a tab on the right side of the Processes screen. If desired, it can be separated from the Processes screen.

To revea l or h ide the Parameters brows er:

• Follow the instructions described in Revealing and Hiding the Navigation Panel (on page 5). Note that the Parameters browser tab is situated at the right edge of the Nolio Automation Center window.

To s epara te the Parameters brows er from the Proces s es s creen:

1. Make sure the Parameters browser is pinned down with the icon.

2. In the upper-right corner of the Parameters browser, click . The Parameters browser becomes a separate dialog, and the icon disappears from the Parameters browser's upper-right corner.

To in tegra te the Parameters brows er as a pane in the Proces s es s creen:

• In the upper-right corner of the Parameters browser, click . The Parameters browser becomes a pane in the Processes screen, and the icon appears in the upper-right corner of the Parameters browser.

Filtering the View The Processes screen allows you to filter the view in several of its trees, including the Components tree, the Processes tree, the Actions browser, and the Parameters browser pane.



Note: For information on using the Filter field to perform a search, see Searching for Items (on page 6).

Tab le 4: Filte r Paramete rs

Click this option To do this

Case sensitive Display only nodes that match the case of the filter string. Case insensitive Display all nodes that match the filter criteria, regardless of case. Use wild cards Allow using wildcards (*) in the filter string.

For example, to display only nodes containing "App" in them, click this option and type the filter string "*App*" (without the quotation marks). Results will include nodes with names such as "CompanyApp1".

Match from start Display only nodes whose names start with the filter string. Match anywhere Display all nodes that match the filter criteria, regardless of where the filter string

appears in the node name. Match leaf node only Display only leaf nodes (nodes without children) that match the filter criteria. Hide nodes without children Do not display nodes without child nodes. Keep the children if parent node matches

If a parent node matches the filter criteria, display its child nodes.

Us ing the Components Tab Designing an application process is performed in the Components tab of the Processes screen Navigation Panel. Selecting this tab affects the contents of all three elements of the Processes screen: Navigation Panel, central pane, and Parameters browser.

Components Tab Navigation Panel When the Components tab is selected in the Navigation Panel, the Navigation Panel displays the following:

• The Navigation Panel displaying a tree of components.

• The Components browser in the central pane.



• When a Component is selected, the Parameters browser appears as a tab at the upper-right of the

Components browser. If the Parameters browser is pinned , then it appears as a separate pane on the right, as shown in the following example.

Applica tions Components Tree When the Components tab is selected in the Navigation Panel, the Navigation Panel displays a tree of the selected application, its components, component categories, and flows.

Each element in the tree is marked with one of the following icons.

Table 5: Components Tab Tree Icons

This icon Indicates

An application

A component

A component category

The flow component category

A flow

Components Tab Central Pane When the Components tab is selected in the Navigation Panel, the Central Pane is used to define the various elements of the components that comprise the application being designed:

• The actions that can be made available to the component (including preliminary checks, and actions related to the component's configuration, installation, verification, as well as miscellaneous additional actions)



• The "flows" or sequences of actions that can be constructed for a component

Note: To create a new actions category from the Central Pane, see Adding Component Categories (on page 21).

Brows ing the Components Tab Parameters In the context of Nolio Automation Center Components tab, action parameters can be defined for specific applications or specific components. The Parameters browser appears when a node that has parameters is selected in the Components tab.

When the Parameters browser is open, it displays the parameters of the item currently selected in the Components tab:

• If an application is selected, the Parameters browser displays all parameters defined for this application.

• If a component is selected, the Parameters browser displays the parameters for the selected component and its parent application.

The parameter name is marked on the left by an internal

parameter icon. On the right of the parameter name appears the parameter type (in gray font and parentheses).

When a parameter is selected in the Parameters browser, the bottom area of the Parameters browser displays information about the selected parameter.

Working with Applica tions and Components The primary task in achieving a fully-automated server-based system involves designing the implementation as an application in Nolio Automation Center.

In the context of Nolio Automation Center, an application comprises all components that participate in automating the deployment of processes from an organization's server farm across a network of client stations.

Before starting the design process, it is critical to correctly analyze the system to be designed and to clearly define what these components are.

For example, if you were to create an application in Nolio Automation Center named "JPetStore" that would deploy and execute all tasks required to maintain this system, three components could be identified:

• Tomcat, Apache's Web server

• MySQL relational database



• JPetStore application

This example will be referred to later in this guide to illustrate how an application is actually designed in Nolio Automation Center.

Adding Applications To add an applica tion: 1. In the Processes screen Navigation Panel, click the Components tab.

2. Click at the top of the tree, and click New Application. The following dialog appears.

3. Fill in the fields using the information in the following table.

4. Click Continue.

Table 6: Applica tion Fie ld s


Process Name Type a name for a process in this application. Deploy JPetStore Application Application Name Type a name for the application. JPetStore

Editing Applications To edit an applica tion: 1. In the Processes screen Navigation Panel, click the Components tab.

2. Select an application from the Applications drop-down menu.



3. Right-click the application in the tree, and select in the pop-up menu. Alternatively, press F2. The Application dialog appears.

4. Fill in the fields using the information in the Application Fields (see "Adding Applications" on page 16) table.

5. Click Save.

Deleting Applications To de le te an applica tion: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Right-click the application in the tree, and select in the pop-up menu. Alternatively, press Delete. A confirmation dialog appears.

4. Click Yes. The application is deleted.

Adding Components An application comprises all components involved in allowing client stations to display and interact with a server-based software product residing on an organization's host machines.

To add a component: 1. In the Processes screen Navigation Panel, click the Components tab.




3. Right-click the desired application in the tree, and select > in the pop-up menu.

OR

Click in the Central Pane.

The Component dialog appears.


5. Click Save.

Table 7: Component Fie ld s


Name Type a name for the component. Tomcat Description Type a description for the component. Tomcat component of the JPetStore application

Editing Components To edit a component: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Right-click the component in the tree, and select in the pop-up menu. Alternatively, press F2. The Component dialog appears.

4. Fill in the fields using the information in the Component Fields table (on page 17).



5. Click Save.

Deleting Components To de le te a component: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Select the components in the tree.

4. Right-click the selected components, and select in the pop-up menu that appears. Alternatively, press Delete. A confirmation dialog appears.

5. Click Yes. The component is deleted.

User's Guide Elaborating Component Actions


Chapte r 4

In This Chapter Overview ................................................................................................................................................................ 20 Working with Actions ............................................................................................................................................. 21 Defining Parameters for Actions ............................................................................................................................ 30

This section explains how to elaborate component actions.

This task is performed in the Processes screen Components tab and requires you to have Design Processes access level. For information on navigating to the Processes screen, see Getting Started with Nolio Automation Center (on page 3).

Ove rview For each component defined for the designed application, one or more flows or processes will ultimately be assembled. For more information, see Creating Flows (see "Creating Action Flows" on page 40).

However, before a flow can be created, the actions that will be available for designing the deployment of each application component must be selected and more specifically defined (see "Defining Actions" on page 23). In addition, where appropriate, parameters (whether those requesting user input from the Run Processes screen or private parameters) also need to be defined for the actions.

After the components and actions have been selected and defined, a chronological flow of operations is created by assembling the actions and defining a flow sequence between them.

The following figure shows a schematic diagram of the incremental and iterative definition and elaboration of components and assembly as flows.

Elabora ting Component Actions

Elaborating Component Actions


Working with Ac tions This section describes how to define Actions and add them to Component Categories.

Us ing Component Categories To define an action for a component, you must add the action to one of the component's categories. A category is a convenient way of organizing a component's actions, much like a folder. Each category represents a group of actions that can be performed on a component, and which have something in common.

Each category of actions can subsequently be used as an "actions bank" for building flows and/or processes.

Nolio Automation Center automatically includes the following predefined categories for each component:

• Actions, for actions that perform a number of miscellaneous tasks not included in the other categories

• Flows, for flows

If desired, you can add new categories, modify existing categories, or delete categories as needed.

Adding Component Categories To add a component ca tegory: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Right-click the component in the tree, click > in the pop-up menu that appears.

OR

click in the Central Pane.



The Category dialog appears.


5. Click Save.

Table 8: Component Category Fie ld s


Name Type a name for the component category Preliminary Checks Description Type a description of the component category Actions related to preliminary checks

Ed iting Component Categories To edit a component ca tegory: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Right-click the category in the tree, and select in the pop-up menu that appears. Alternatively, press F2. The Category dialog appears.

4. Fill in the fields using the information in the Component Category Fields (see "Adding Component Categories" on page 21) table.

5. Click Save.

De le ting Component Ca tegories Note: You cannot delete a component category which contains actions that are currently in use. If you attempt to delete such a category, a message appears indicating where the actions are used.

To de le te a component ca tegory: 1. In the Processes screen Navigation Panel, click the Components tab.




3. Select the categories in the tree.

4. Right-click the selected categories, and select in the pop-up menu that appears. Alternatively, press F2. A confirmation dialog appears.

5. Click Yes. The category is deleted.

Defining Actions For each component, you must define the available actions for the component, and add them to the component's relevant component category. Defining an action is performed by selecting a predefined action template from the Nolio Automation Center Actions browser and then modifying the action as desired.

For information on modifying the list of action templates available in the Actions browser, refer to the Installation and Administration Guide.

Adding Actions To add a new ac tion for a component: 1. In the Processes screen Navigation Panel, click the Components tab.


3. In the tree, select the category to which you want to add the action.

4. Click in the Central Pane, and double-click the desired action template in the dialog that appears. The Edit action dialog appears, displaying three tabs:

Input values for specifying the actions input parameters

Output values for specifying the actions return values

The Input values and Output values tabs include a two-columned table listing all of the relevant values.



Properties tab displaying the properties of the action.

5. Fill in the desired input and output values in both tabs using the information in the Action Fields (on page

24)table. The available value type varies per the type of action. For detailed information on configuring values for different action types, see the Actions Reference Guide.

6. Click Save.

Tab le 9: Action Fie lds


Action Type The action template's name. This field is read-only. Access URL Name Type a name for the action. Access MyCompany

Website Description Type a description of the action. Accesses the company

Website This action must succeed

Select this option to specify that the continued progress of the designed implementation is conditional upon the successful execution of the current action.

Target OS Select the operating system on which this action should be executed. If you select ANY, the action will be executed on any target host, regardless of this host's operating system. If you select a specific operating system, the action will only run on target hosts of the specified operating system.

ANY



Table 10: Action Value Fie lds

In this field Do this

Click this button to specify a null value.

Click this button to specify a plain value. A field appears in which you must select or type a literal value.

Click this button to specify a parameter value.

The button appears. Click this button to open the Parameters List, which displays all available parameters for the application and component. Select the desired parameter, and then click Choose.

Click this button to specify an expression that utilizes parameters defined for the component or its parent application. A field appears in which you can type the desired expression.

In addition, the and buttons appear. In this field Do this

Click this button to open the Parameters List, which displays all available parameters for the application and component. Select the desired parameter, and then click Choose.

Click this button to edit the expression in full view. The Edit expression dialog appears.

Click the button to select desired parameters, and then click Save.

Viewing and Editing Actions To view or edit an action: 1. In the Processes screen Navigation Panel, click the Components tab.




3. Select the relevant category in the tree. The Central Pane displays all defined actions for the category.

4. Click the desired Action in the Central Pane. Information about the Action's input values, output values, and

properties appear. Controls for the action appear.

5. To edit information about the Action, double-click the Action's name or click . The Edit Action dialog appears.

To edit this dialog, refer to instructions in the Adding Actions (on page 23).

Reverting Actions Changes made in an action's input and output values can be reverted to the source values. In the Graph View, the Revert icon indicates the revertible actions (with at least one input and/or output value that differs from the source value). When editing the action, clicking the Revert button will restore source values.

If an action has a value that has been modified, changing the source value will not affect the action until the revert operation is performed.

To revert an ac tion: 1. Click the Components tab, and create a new action.

2. Choose a "Delay" action from the Actions browser.

3. In the Input values tab of the Edit action dialog, set the value of "Time For Delay" parameter to be "6", and click Save. This value will be the source for future actions that will be created by using this action.

4. Click the Processes tab, and create a new process. Add twice the "Delay" action you have previously created.



5. Edit one of the two "Delay" actions, and change the value of "Time For Delay" to be "7". The Revert icon appears.

6. Click the Components tab, and edit the "Delay" action you have created. Change the value of "Time For

Delay" to be "8" instead of "6".

7. Click the Processes tab, and notice that the value of the "Time For Delay" value in the edited action is still "7", but the value in the other action is now "8".

8. Edit the action that has the value "7", and click the Revert icon to revert its values. Notice that the value is now "8".

Copying, Cutting , and Pas ting an Ac tion To copy, cu t, and pas te an action: 1. In the Processes screen Navigation Panel, click the Components tab.



4. Select the desired actions in the Central Pane:

a. To copy, click , or press CTRL+C.

b. To cut, click , or press CTRL+X. The actions will be deleted from the source location.

5. Select the desired destination category in the tree.

The Central Pane displays all defined actions for the category.

6. Press CTRL+V, or right-click the category in the tree, and select in the pop-up menu that appears.

Alternatively, in the Central Pane, press CTRL+V or click . The actions appear in the destination category.

7. If there is an action or category with the same name in the destination, the following dialog appears:



a. To abort the copy operation, click Don't copy.

b. To copy and rename the copied action, as suggested, click Copy, but keep both actions.

c. If several actions are copied together in single paste operation, you may apply the same options to all copied actions in the copy operation by selecting the Apply to all actions check box before clicking the desired option.

8. In the case where an action uses a parameter that already exists in the destination location, if the existing parameter is the same as in the original action, that parameter is also used for the copied action.



If the existing parameter is not the one used by the original action, the following dialog appears:

a. To create a new parameter that will be used by the copied action, click Create new parameter.

b. To use the existing parameter, click Use existing parameter.

c. To copy the action without input or output values that contain a reference to that parameter, click Don't copy parameter.

d. One of the above parameter options may be applied to all parameter references in the current copy action by selecting the Apply to all parameters in this action check box before selecting the copy action.

e. To cancel the action copy operation, click Don't copy action.

f. Any of the four options listed in the dialog may be applied to all parameters and to all actions copied within this paste operation by selecting the Apply to all actions check box.

De le ting Actions Note: You cannot delete an action that is currently in use. If you attempt to delete such an action, a message appears indicating where it is used.

To de le te an ac tion: 1. In the Processes screen Navigation Panel, click the Components tab.





4. Click the desired Actions in the Central Pane.

5. Click in the toolbar at the top, or press Delete. A confirmation dialog appears.

6. Click Yes. The actions are deleted.

Defin ing Parameters fo r Ac tions In addition to the operation performed by a given action, each action is characterized by the variable parameters that enable the same data to be reused across several Actions/Flows/Processes or that can be used while the Process is running to input data at a specific point, and the output associated with it.

Where appropriate, the input and output can and should be parameterized. In this way, input and output can be designed generally, while specific values will only be assigned to these parameters just prior to and during the actual physical implementation of the design in a specified environment.

Each defined parameter may be specified as either a:

• Private parameter that can be integrated in the definition of actions, but which does not require any user input prior to implementation of an application.

• User input parameter that must be assigned appropriate values from the Run Processes screen when an application is to be implemented.

In addition, a few predefined parameters may be utilized in the definition of actions. These are:

• hostname

• IP

These predefined parameters may be used only as private parameters (i.e. they cannot be assigned user input). They are supplied with Nolio Automation Center and cannot be modified or deleted.

Us ing Parameters Folders To define a parameter for an application or component, you must add the parameter to a folder in the Parameters browser. Nolio Automation Center automatically creates the following folders:

• Application Parameters, for global parameters available in all of the application's components

• A folder for each component

The parameters displayed in the Parameters browser are always ordered alphabetically within their respective folder, whether for the displayed application or displayed component.

When numerous parameters are defined for a component or application, you may find it more efficient to organize parameters by some other criteria, such as type. To this end, you can create additional parameter folders.

Adding and Editing Parameter Folders To add a parameter folder: 1. In the Processes screen Navigation Panel, click the Components or Processes tab. The following steps

relate to the selection of the Components tab.


3. To add a new parameters folder:

For an application, select any of the application's components in the tree, and then select the Application Parameters folder or one of its sub-folders in the Parameters browser.

For a component, select the desired component in the tree, and then select the component's parameter folder or one of its sub-folders in the Parameters browser.



4. Click , and then click . The Parameters Folder dialog appears.

5. Fill in the fields using the information in the Parameters Folder Fields (on page 31) table.

6. Click Save.

Tab le 11: Pa ram eters Fo lder Fie ld s

In this field Do this For example Name Type a name for the folder. Login Parameters Description Type a description of the folder. Parameters related to login

Ed iting Parameter Folders To add or ed it a parameter fo lder: 1. In the Processes screen Navigation Panel, click the Components tab.

2. Select the application from the Applications drop-down menu.

3. In the tree, select the desired component.

4. In the Parameters browser, select the desired folder.

5. Right-click the folder, and select in the pop-up menu that appears. Alternatively, press F2. The Parameters Folder dialog appears.

6. Fill in the fields using the information in the Parameters Folder Fields (on page 31) table.

7. Click Save.

De le ting Parameter Folders To de le te a parameter fo lder: 1. In the Processes screen Navigation Panel, click the Components tab.


3. In the tree, select the desired component.

4. In the Parameters browser, select the desired folders.



5. Right-click the folders and click in the pop-up menu that appears. Alternatively, press Delete. A confirmation dialog appears.

6. Click Yes. The folder is deleted.

Adding Parameters To add a parameter: 1. In the Processes screen Navigation Panel, click the Components tab.


3. To add a global parameter for an application, in the Navigation Panel select any of the application's components in the tree, and then select Application Parameters or one of its sub-folders in the Parameters browser.

OR

To add a local parameter for a component, in the Navigation Panel select the desired component in the tree, then select the folder of the component by the same name or one of its sub-folders in the Parameters browser.

4. Click .

5. Choose the desired parameter type in the pop-up menu that appears. For information on the available parameter types, see Parameter Types and Properties. (on page 36) The Parameter dialog appears.

6. Fill in the fields using the information in the Parameters Fields (on page 33) table.

7. Click Save. The new parameter appears in the Parameters browser in the relevant folder.

8. Select the new parameter. The parameter's properties appear at the bottom of the Parameters browser, in the Parameter Properties pane.



9. Click . Additional fields appear.

10. Fill in the fields using the information in Parameter Types and Properties. (see "Action Parameter Types and

Properties" on page 36)

11. Click Save.

Tab le 12: Pa ram eter Fie ld s

In this field Do this For example Name Type a name for the parameter. UserName Description Type a description of the parameter. The user's username

Editing Parameters To edit a parameter: 1. In the Processes screen Navigation Panel, click the Components tab.


3. To edit the parameter's name and description:

a. Right-click the desired parameter in the Parameter browser, click in the pop-up menu that appears. Alternatively, press F2. The Parameter dialog appears.

b. Fill in the fields using the information in the Parameter Fields (on page 33) table.

c. Click Save.

4. To edit the parameter's properties:

a. Select the desired parameter in the Parameters browser. The parameter's properties appear at the bottom of the Parameters browser, in the Parameter Properties pane.

b. Click . Additional fields appear.

c. Fill in the fields using the information in Parameter Types and Properties. (see "Action Parameter Types and Properties" on page 36)

d. Click Save.



Overriding Parameters You can override a given value for parameters to change it for a specific process, server type, or environment.

For example, if you have Component parameters that represent a directory and you want this value to be different in a specific process, you can edit the parameter in the parameter’s tree of the specific process and this value will affect only the given process. (All processes, components, and environments have the initial value.)

To override a parameter in a s pecific proces s 1. Create the parameter in the component.

2. Click the Processes tab and select the process.

3. Open the parameters tree and select the relevant parameter that you want to edit.

4. Edit the parameter (on page 33). The value is changed only for the process.

While in the Processes tab, you can revert parameter values that were overridden in a specific process. See Reverting an Overridden Process Parameter (on page 34).

Note: File parameters and Predefined parameters cannot be overridden. If you do change them, they will be changed globally.

To override a parameter in a s pecific environment: 1. Create the parameter in a component or process.

2. Click the Environment tab and select the environment.

3. Open the parameters tree and select the relevant parameter that you want to edit.

4. Edit the parameter (on page 33). The value is changed only for the specific environment.

Note: Environment parameters restrictions include:

Only applications Parameters can be changed in the environment.

You must have Administrative privileges on the given environment in order to change the values.

Reverting an Overridden Proces s Parameter While working in the Processes tab, it is possible to revert the value of a parameter in the Parameters browser that was overridden during the design process. There are two scenarios for the result of reverting a parameter, depending on the source of the original parameter assignment:

• If the process parameter was assigned at the Component level and overridden at the Process level, the revert option will replace the current value with the value assigned at the Component level.

• If the process parameter was assigned at the Process level and overridden at the Process level, the revert option will replace the current value with ‘No Value’.

To revert an overridden proces s parameter: 1. In the Processes screen Navigation Panel, click the Processes tab.


3. Select an architecture in the application tree.

4. Select the target process.

5. Select the desired parameter in the Parameters browser.

The parameter's properties appear at the bottom of the Parameters browser, in the Parameter Properties pane.

6. Click . Additional fields appear.



If the Revert icon appears as , then the option is not available as the parameter was not changed.

7. Click .

A confirmation dialog appears.

8. To revert to the parameter value, as described at the beginning of the topic, click Yes, or click No to cancel.

Copying, Cutting, and Pas ting a Parameter The following conditions apply to the parameter operations:

Note: Predefined parameters cannot be copied or cut.

Note: A cut parameter can only be pasted to a folder in the same category.

Note: Parameters containing values which are not copied parameters cannot be copied with their values to a location from which the value parameter is inaccessible since it is another component. In other words, a nested parameter value may not be copied because the value may not be allowed in the paste location.

For example: Parameter "A" has a value that is parameter "B" which is not selected for copying. If the parameters in the paste location are not allowed to have parameter "B" as their value, because parameters in the copy from location are not visible to parameters in the paste location, then parameter "A" may be copied alone, without its value, which is parameter "B".

To copy, cu t, and pas te a parameter: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Select the desired parameters in the Parameters browser.

4. To copy, press CTRL+C. Alternatively, right-click the selection in the Parameters browser and select

in the pop-up menu.

5. To cut, press CTRL+X. Alternatively, right-click the selection in the Parameters browser and select in the pop-up menu. The parameter will be deleted from the original location.

6. Right-click the desired destination folder in the Parameters browser, and select in the pop-up menu. Alternatively, select the desired folder, and press CTRL+V. The parameters appear in the destination folder.



7. If a parameter or folder with the same name already exists in the destination folder, the following dialog appears:

a. To abort the copy operation of the parameter, click Don't copy.

b. To copy and rename the copied parameter, as suggested, click Copy, but keep both parameters.

c. To apply the selected option to all parameters copied within the paste operation, select the Apply to all parameters check box.

Deleting Parameters To de le te a parameter: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Select the desired parameters in the Parameters browser.

4. Press Delete or right-click the selection, and select in the pop-up menu. A confirmation dialog appears.

5. Click Yes. The parameter is deleted.

Note: Predefined parameters cannot be deleted.

Action Parameter Types and Properties You can define the following types of parameters:

• String (on page 111)

• Password (on page 112)

• Boolean (on page 114)

• File (on page 114)



• Predefined Options (on page 115)

• General (on page 117)

• Numerical (on page 117)

• Array (on page 118)

To view and modify a parameter's properties in the Parameter Properties pane :

Click the parameter's name in the Parameters browser, and click . The displayed properties and definable values vary per parameter type, as described in the following topics.

Note: The property name and description are configured separately from the parameter properties.

Tes ting Actions You can test run an action to determine whether it has invalid properties, or if it has invalid or missing parameters.

To tes t an ac tion: 1. In the Processes screen Navigation Panel, click the Components tab.



4. Click the desired action's name.

5. Click .

If there is a problem with the action's properties and/or parameters, an error message appears. Do the following:

a. Click OK to close the message.

If there is a problem with a parameter, the Conflicts Browser opens at the bottom of the central pane. The browser provides information about problematic parameters.

b. To debug the specific step, or steps, involved in the conflict, see Debugging Using the Conflicts Browser (on page 38).

c. Fix the problems specified in the error message and/or from the Conflicts Browser debugging.

d. Restart this procedure to test the action again.



If there are no problems with the action's properties and parameters, the Test Run dialog appears.

6. From the drop-down list, select the desired test agent on which to run the action and click Choose.

7. Click . The Starting Test area appears with a progress bar. At the end of the test, a message appears indicating whether the test succeeded or not.

8. Click Close.

Debugging Us ing the Conflic ts Brows er When the Conflicts check determines that there are errors within the process, the conflicts are listed in the Conflicts Browser.

Use the messages to locate and fix the errors.

If the error is an Action Conflict, you can locate and fix the conflict using the following procedure.

To fix an ac tion conflic t: 1. Click (Locate this action and double click it to fix this conflict) at the end of the conflict error message line.



The action will be located within the process and an overview of that portion of the process will display in the process workspace with the conflicted action highlighted.

2. Double-click the highlighted action to open a dialog to fix the conflict.

3. To close the browser, click .

User's Guide Creating Action Flows


Chapte r 5

In This Chapter Overview ................................................................................................................................................................ 40 Methodology .......................................................................................................................................................... 41 Working with Flows ................................................................................................................................................ 41 Assembling Flow Steps ......................................................................................................................................... 45 Defining Loops ....................................................................................................................................................... 53 Testing Flows ......................................................................................................................................................... 54

This section explains how to create action flows.

This task is performed in the Processes screen Components tab and requires you to have Design Processes access level. For information on navigating to the Processes screen, see Getting Started with Nolio Automation Center (on page 3).

Ove rview In the previous section, the selection of predefined action templates was explained, as were the means by which these actions may be elaborated, customized, and made available to the application processes' components. These actions are the building blocks used in designing the automated implementation of server applications. However, in order for an action to become part of an automated process, it must be made part of what is referred to by Nolio Automation Center as a flow.

A flow is the grouping together of actions, which is then made available to an application's component. This grouping together of actions specifies the chronological sequence in which two or more actions will occur. In addition, it may specify the conditional nature of the transition made from the completion of one action to the start of the next action in the sequence. When an action is instantiated into the context of a flow, it is referred to as a step in that flow.

For the convenience of design, flows can also depict the parallel execution of two or more sequences of separate but similar actions: on the same server; on different servers running under the same operating system; and on different servers running on different platforms (Windows as opposed to Linux, for example).

In such a strictly parallel flow, each of the two or more sequences of actions may indeed be unaffected by the progress of the others.

On the other hand, where applicable, you can design a flow so that an action commonly used by each of the two or more types of platforms share the common action. In such a case, the graphic depiction of the previously parallel sequence of actions might converge at the common action, only to diverge once again following this action. Such common, shared actions might be designed at the very beginning, in the middle, or at the end of the otherwise parallel sequences of actions.

Note: In addition to instantiating actions made available to a component, a flow may also instantiate a previously constructed flow for this same component. In principal, you can create a hierarchy of nested flows as deep as required. However, in practice it is recommended to nest flows only to a single level, so that the resulting assembly will not become overly complex.

Crea ting Ac tion Flows

Creating Action Flows


Methodology The selection of actions, the development of these actions (including the definition of parameters), and the assembling of flows is most often an iterative process. This is depicted in the figure in Overview (on page 20).

Specifically, you might decide to, and even be able to perform, the various phases of designing your application in a purely sequential order; that is:

1. Establish each of the components involved in the application.

2. Decide which actions are to be made available for each component.

3. Select and customize each of these actions.

4. Create the various flows in which the appropriate actions are to be integrated.

5. Move on to the next stages of the design, as described in subsequent sections in this guide.

However, while there are phases in which you will undoubtedly work sequentially, in practice this is neither necessary, nor absolutely good methodology. This is because, as you develop your application, you may decide upon changing the design to simplify it, for example, in order to make it more modular and efficient.

To make such iterative work more feasible and productive, the Nolio Automation Center interface has been designed to enable you to access controls for defining and modifying elements that, strictly speaking, might have been defined in previous phases of the design process.

Working with Flows This section deals with adding, editing, viewing and deleting Flows.

Adding Flows To add a flow: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Right-click the desired component's Flows category in the tree, and select > in the pop-up menu.



The Flow dialog appears.

4. Fill in the fields using the information in the Flow Fields (on page 42) table.

5. Click Save.

6. Assemble the flow's steps, as described in Assembling Flow Steps (on page 45).

Tab le 13: Flow Fie lds

In this field Do this For example Name Type a name for the flow. Generate Monitoring Report Description Type a description of the flow. Generates a monitoring report

Editing Flows To edit a flow: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Select the relevant category in the tree. The Central Pane displays all defined flows for the category.

4. To edit the flow's name and description:

a. Right-click the relevant flow in the tree, and select in the pop-up menu that appears.



The Flow dialog appears.

b. Fill in the fields using the information in the Flow Fields (on page 42) table.

c. Click Save.

5. To edit the flow's steps:

a. Add or delete flow steps, link the steps, or set step transition conditions as desired. See Assembling Flow Steps (on page 45).

b. To refresh the view, click .

c. To save your changes, above the Central Pane, Click .

Note: It is possible at any time to cancel all editing changes and revert to the original flow graph, simply by clicking on another tree element and declining the confirmation dialog.

Copying, Cutting, and Pas ting a Flow Note: Flows can only be copied within the same component.

To copy, cu t, and pas te a flow: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Select the relevant Component.


5. Right-click the desired flow in the navigation tree, and select or in the pop-up menu. Alternatively, press CTRL+C to copy, or press CTRL+X to cut.

a. If was selected, the flow is deleted.

6. Right-click the desired destination category in the navigation tree, and select in the pop-up menu. Alternatively, press CTRL+V. The flow appears in the destination category.

7. If there already is a flow with the same name in the target destination, a copy of the flow will be created.



Viewing Flows This section details navigating and resizing flow diagrams, and the display of Action definitions within a flow.

Overview a Flow Diagram Often when a Flow diagram is displayed in the Central Pane, you are viewing a subsection of the entire diagram. The overview feature allows you to view the entire diagram as a thumbnail.

When the thumbnail appears, the entire diagram is visible. The subsections of the flow not currently displayed in the Central Pane are shaded.

To us e the overview fea ture : 1. In the Processes screen Navigation Panel, click the Components tab.


3. In the tree, select the relevant flow. The flow is displayed in the Central Pane.

4. In the Central Pane, click . The overview thumbnail appears.

5. To view a subsection that is currently shaded, click the subsection in the shaded area of the thumbnail. The

subsection is displayed in the Central Pane.

Res izing the Flow Diagram Once you have assembled flow steps (see Assembling Flow Steps (on page 45)), you can resize the flow diagram in the Central Pane.

To res ize a flow diagram: 1. In the Processes screen Navigation Panel, click the Components tab.


3. In the tree, select the relevant flow. The flow is displayed in the Central Pane.

4. To change the zoom:

To increase the zoom, in the Central Pane, click .

To decrease the zoom, in the Central Pane, click .

To revert to the default zoom, in the Central Pane, click .

Dis p laying Defin itions of Actions Ins tantia ted within a Flow As you develop a flow, you can display the definitions of individual actions that have been instantiated as steps within the flow, by double-clicking the step. This opens the Action Editor. For details, see Viewing and Editing Actions (on page 25).



Deleting Flows To de le te a flow: 1. In the Processes screen Navigation Panel, click the Components tab.



4. Right-click the desired flow in the tree, and select in the pop-up menu. A confirmation dialog appears.

5. Click Yes. The flow is deleted.

Note: Deleting a flow only deletes it, but not the actions and nested flows that it instantiated, from the data stored for component.

As s embling Flow Steps Once you have created a flow, you must add steps to it. A step may be an action or a previously assembled flow that is defined for the component.

Note: A flow may comprise a single action. Recall that in order for any action to be implemented, it must be integrated as a step in a flow. Thus, you might create a single-step flow to implement an action which stands on its own.

Adding Flow Steps To add a s tep to a flow: 1. In the Processes screen Navigation Panel, click the Components tab.




3. In the tree, select the relevant flow. The relevant flow is displayed in the Central Pane.

4. To add an action or flow:

To automatically link the new action or flow to the source step, right-click the source step and select

from the pop-up menu. (This is the option demonstrated in this example).

To create an orphaned action or flow that is not linked to another step, right-click the Central Pane's

background and select from the pop-up menu. To link an orphaned action or flow, see Manually Adding Flow Lines (on page 49).

An orphaned action or flow is used to create a separate parallel flow within the current flow; for example, an installation flow that depicts two parallel sequences for Windows and Linux. Use this method to create tasks to be run in parallel on the same platform.



The Actions Dialog appears.

5. In the Actions dialog, select the action or flow to be added and click . The added action or flow appears in the central pane as a flow step.

6. Set the step transition conditions as described in Setting Step Transition Conditions (on page 51).



7. Click .

Deleting Flow Steps To de le te a s tep from a flow: 1. In the Processes screen Navigation Panel, click the Components tab.


3. In the tree, select the relevant flow.

4. Click on the step you want to delete. A confirmation dialog appears.

5. Click Yes. The step is deleted.

Step-related Icons and Symbols Step-related icons and symbols pertain to the individual actions that have been integrated as steps in a flow. They appear in or adjacent to the rectangle that represents each step.

Icon Step-related Indicators

Indicates that Windows is the operating system of the server for which this action was defined.

Indicates that Linux is the operating system of the server for which this action was defined.

This icon appears only when the This action must succeed check box has been selected for the action. For further information, see Adding Actions (on page 23).

Indicates that the action has mandatory input fields that are not satisfied.

The color of the bubble, or bubbles displayed here indicate the conditions upon which the transition to the next step will be made.

• (green): the transition should be made only when the current step is completed successfully (On Pass).

• (red): the transition to the next step should be made when the current step fails (On Fail).

• (gray): the transition will be made if the execution terms are not fulfilled (On Cancel). Note that both On pass and On Fail may be displayed together with On Cancel (a logical OR). How these conditions are set is described in Setting Step Transition Conditions (on page 51).

Each arrow points to the next step to be executed following the completion of the current step.

Linking Steps in a Flow Sequence Steps in a flow must be linked in order to indicate their sequence. Linking is done by adding arrowed flow lines between the steps. The arrow indicates the sequence in which the various actions comprising the flow steps will be executed.

There are two ways to link steps:



• When adding a flow step, you can automatically add flow lines between a previously added step and the new step, as described in Adding Flow Steps (on page 45).

• You can manually add flow lines between steps, as described in Manually Adding Flow Lines (on page 49).

Manually Adding Flow Lines Manually adding flow lines is often performed to merge two steps on a shared subsequent step.

Yet another use might be to create a junction at which two flows that previously ran parallel to one another can now be designed to use commonly defined steps.

In this example, execution of the flow will depend on the server platform on which it is running. Any steps that are not applicable to the server (for example a Windows-specific step when the flow is run on a Linux-based server) will not be executed. This is why there are links with the On Cancel condition from the last step of each platform type to the general step that runs on any platform: even if the previous step was not executed, the next step will be run.

To add a flow line between two previous ly unlinked s teps : 1. In the Processes screen Navigation Panel, click the Components tab.

2. In the tree, select the relevant flow. The relevant flow appears in the central pane.



3. Place the mouse pointer in the rectangle of the source (earlier) step and right-click to view the pop-up menu.

4. Select Create Link in the pop-up menu and drag the link to the target (subsequent) step.

5. Release the left mouse button. The flow line that is now displayed creates a sequential link between the two steps.

6. Right-click in each link to set step transition conditions for this link as required (the default is On Passed).

Changing the S tep from which a Flow Line Exits To change the step that leads to a subsequent step while still retaining all steps instantiated in the flow, shift the flow line.

For example, in the flow depicted in the following figure, the goal is to change the step that leads to Step D from Step C to Step A.

To s h ift a flow line: 1. Click the flow line.

Black dots appear at either end of the line.

2. Click the black dot located in the step from which to shift. (In the above case, Step C.)



3. Holding down the left mouse key, drag the dot from the source step (Step C) to the destination (Step A).

4. When the mouse pointer reaches the destination (Step A), release the left mouse button.

De le ting Flow Lines To de le te a flow line : 1. In the Processes screen Navigation Panel, click the Components tab.


3. Right-click the flow line, and select in the pop-up menu that appears, or press Delete on your keyboard. The flow line is deleted.

Setting Step Trans ition Conditions When you link a new step to one that precedes it, by default the following icon appears at the base of the flow

arrow: .

This indicates that the transition from the preceding step to the next step will take place when the earlier step is executed successfully (On Passed).

However, you can change the transition conditions between one step and the next, specifying that the transition should be made:



Icon Transition Condition

• On Failed - When execution of the earlier step fails.

• On Cancel - When execution terms are not met. In this case, the transition will be made even if the previous step is not implemented; for example, a Windows-specific step that will not be implemented because the flow is being run on a Linux machine.

• On Passed OR On Cancel - When execution either succeeds or the execution terms are not met.

• On Failed OR On Cancel - When execution either fails or the execution terms are not met.

The icon displayed next to each of the above possibilities indicates what will appear on the flow line arrow when the respective conditions are set.

To modify the trans ition conditions be tween two s teps : 1. In the Processes screen Navigation Panel, click the Components tab.


3. Right-click the flow line being modified, and select the appropriate new condition in the pop-up menu: On Passed, On Failed, or On Cancel. The new condition is indicated by a check mark in the pop-up menu.

Note: As indicated above, both On Passed and On Failed can be logically OR with On Cancel. Therefore, if either On Passed or On Failed is selected in the pop-up menu, you can also select the On Cancel condition.

You can also create a flow line for which no condition is defined for the transition to the next step. In the graphic display of the flow, such an arrow will have no colored bubble.

To modify a flow line s o tha t it has no trans ition condition: 1. In the Processes screen Navigation Panel, click the Components tab.


3. Right-click the flow line being modified, and deselect any condition that is currently selected in the pop-up menu.

Note: In order for this unconditional transition to take place, the This action must succeed check box must be cleared, for the action from which the flow arrow exits. This is done in the Action Editor. See Viewing and Editing Actions (on page 25).



Sample Flow The following flow was created for the MySQL component of the JPetStore-AppServer application and depicts two parallel flows: the flow to the left is for Windows and the one on the right is for Linux. Each of these series of steps is designed to create a sequence of actions that are involved when installing and configuring MySQL on the two respective platforms. (As described in subsequent sections, a flow can also model steps running in parallel on the same platform.)

As previously described, the steps themselves are all instantiations of the predefined actions supplied with Nolio Automation Center. Each of these actions had previously been made available to the MySQL component of the JPetStore-AppServer application, as described in Making Actions Available for Components (on page 21).

Furthermore, each of these generic actions was customized for the current task at hand (installing and configuring MySQL on Windows and Linux servers) by defining one or more input values, as well as return values (where appropriate) and execution terms; see Defining and Developing Actions (on page 23). In addition, when defining these values, the input values and return values may have been specified literally or using parameters as determined by the modeler, as described in Defining Parameters for Actions (on page 30).

Defin ing Loops To define a loop in a flow: 1. In the Processes screen Navigation Panel, click the Components tab.


3. In the Advanced menu on top of the Central Pane, click .



4. The Edit Loop dialog appears.

5. Enter the Input and Output values and select the Loop type from the drop-down menu.

6. Click Save.

Tes ting Flows You can test run a flow to determine whether it has invalid or missing parameters.

To tes t a flow: 1. In the Processes screen Navigation Panel, click the Components tab.

2. Select the Flows category in the tree.

3. Click the desired flow's name. The desired flow is displayed in the Central Pane.

4. Above the Central Pane, click . The Test area appears under . At the end of the test, a message appears, indicating whether the test succeeded.

5. Click Close.

Designing Applications Processes


Chapte r 6

In This Chapter Overview ................................................................................................................................................................ 55 Using the Processes Tab....................................................................................................................................... 56 Declaring Application Server Types ...................................................................................................................... 59 Working with Architectures .................................................................................................................................... 61 Working with Processes ........................................................................................................................................ 66

Until now the design cycle has been somewhat abstract, insofar as not addressing the array of servers on which an application is to be executed.

This section discusses the design of the server types to be used when implementing an application, or rather the various possible configurations to be designed.

The related tasks are performed in the Processes screen Processes tab and requires you to have Design Processes access level. For information on navigating to the Processes screen, see Getting Started with Nolio Automation Center (on page 3).

Ove rview By this point in the design cycle, this guide has described how to:

• Define an application that will be used to automatically implement various tasks involving the deployment and maintenance of a server-based software system

• Specify the components that are involved in this implementation

• Determine which predefined actions are to be made available for each of these components, including customizing the use of these actions by defining input values and, where applicable, return values and execution terms for them

• Create flows, chronological sequences of instantiated actions, for each of the various components participating in the implementation of an application

The next phase is to design possible physical configurations in which the application could be implemented. Such a configuration is referred to as an architecture.

For example, you might create an architecture in which the implementation of all components of an application is handled by a single server. A second architecture then might handle the same application using a pair of servers. Yet another architecture could add a third or more servers.

The various tasks to be handled by any architecture, tasks that will involve most or all of the components, are referred to as processes.

Processes are sequences of planned activity involving one, more, or all of an application's components, and they are assembled by instantiating the flows that were previously created per component.

Des igning Applica tions Proces s es

User's Guide Designing Applications Processes


Note: Even though architectures are used to develop various possible configurations of server utilization, architectures are still only design concepts. As such, they are unrelated at this stage of the Nolio Automation Center development cycle to the actual physical servers that will ultimately handle your server-based applications. The linking of these architectures to real machines is executed from the Run Processes screen. See Automating Applications Processes (on page 76).

Us ing the Proces s es Tab Architectures and processes are designed in the Processes screen in the Navigation Panel Processes tab.

Selecting this tab affects the contents of all three elements of the Processes screen (Navigation Panel, Central Pane, and Parameters browser).



Proces s es Tab Navigation Panel When the Processes tab is selected in the Navigation Panel, the Navigation Panel displays a tree of all applications, architectures, categories, and processes. The following icons indicate the type of tree element.

Table 14: Pro ces s es Tab Tree Icons

This icon Indicates

An application

An architecture

A process category

A process

Proces s es Tab Central Pane One of two work areas is displayed here, depending on whether an architecture or a process is selected in the navigation tree.

Architecture

When an architecture is selected in the navigation tree, you define its logical structure by specifying the server type or types that are included in these architectures.

The graphic display represents each architecture as a rectangle whose name, and resident components are shown.

To begin defining an architecture, you must initially designate at least one server for it, as described in Declaring Architecture Server Types (on page 63).



Process When a process is selected in the navigation tree, it is displayed in the graphics pane as a high-level sequencing of operations. The process instantiates flows defined for the current application's components and, in fact, uses the same graphical syntax used to assemble flows from actions. The process that is thus assembled can be executed by the server architecture for which it is created.

Proces s es Tab Parameters Brows er In the Processes screen Processes tab, you can modify for a specific architecture the parameters that were previously defined for an application and its individual components.

When the Parameters browser is open, it displays the parameters of the relevant application and architecture:

• The parameters defined for the application as a whole are displayed at the top of the browser tree.

• The branch divisions of parameters are displayed by server.

• Beneath each server appear the parameters that have been defined for use by the application components assigned to this server in the architecture.

To the left of each parameter, an internal parameter icon appears. After the parameter name on the right, the parameter type appears (in gray font in parentheses).

For information about editing parameters, refer to Elaborating Component Actions (on page 20).

The Parameters browser includes the following predefined parameters which may be utilized in the definition of processes:

• hostname

• IP

Predefined parameters may be used only as private parameters and cannot be assigned user input. Predefined parameters are supplied with Nolio Automation Center and cannot be modified or deleted.

For information about revealing and hiding the Parameters browser, refer to Using the Processes Screen (on page 11).



Decla ring App lica tion Serve r Types Before defining architectures and processes, you must declare the server types on which the application is to be implemented. The server types will then be available for selection when defining architectures.

Note: The server types you declare are abstract design elements. They are presently unconnected to the actual physical machines on which a Web-based application will ultimately run. Only later, in the Run Processes screen, will actual servers be allocated to the design you create.

Adding Server Types to Applications To add a s erver type to an application: 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Select the desired application in the tree.

3. Choose a method for opening the Server Type dialog:

To select in the Navigation Panel from the right-click pop-up menu, click > .

To select from the Central Pane, click .



The Server Type dialog appears.

4. Fill in the fields using the information in the Server Type Fields (on page 60) table.

5. Click Save.

Tab le 15: Se rver Typ e Fie lds


Name Type a name for the server type. DB Server Description Type a description of the server type. Database server Is Utility server Select the check box if the server type is designated as a

server type for running multiple processes concurrently.

Assign Components Select the check box(es) to assign components to the server type.

Editing Server Types for Applications Edit a server type for an application to change the following:

• Rename the server type

• Change the assigned components

• Assign or deassign the server type as a Utility server for running multiple processes concurrently



To edit a s e rver type for an application: 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Select the application in the tree.

3. Right-click the desired Server Type in the central pane, and select from the pop-up menu.


5. Click Save.

Deleting Server Types from Applications To de le te a s e rver type from an application: 1. In the Processes screen Navigation Panel, click the Processes tab.


3. Right-click the desired Server Type in the Central Pane, and select from the pop-up menu. A confirmation dialog appears.

4. Click Yes. The Server Type is deleted.

Working with Arch itec tures You must define at least one architecture for an application.



Adding Architectures To add an a rchitec ture : 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Right-click the desired application in the tree, and select > in the popup menu.

The Architecture dialog appears.

3. Fill in the fields using the information in the Architecture Fields (on page 63) table.



4. Click Save. The Assign Server Type dialog appears.

5. Select the Server Types you wish to assign to this Architecture.

6. Click Save.

Tab le 16: Arch itec tu re Fie lds


Name Type a name for the architecture. Single Server Description Type a description of the architecture. Architecture consisting of a single server

Editing Architectures To edit an a rchitec ture : 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Right-click the desired architecture in the tree, and select in the pop-up menu. The Architecture dialog appears.

3. Fill in the fields using the information in the Architecture Fields (on page 63) table.

4. Click Save.

Deleting Architectures To de le te an a rchitecture : 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Right-click the desired architecture in the tree, and select in the pop-up menu. A confirmation dialog appears.

3. Click Yes. The Architecture is deleted.

Declaring Architecture Server Types Any architecture you define for an application must be assigned at least one server type.



Note: The server types you declare are abstract design elements. They are presently unconnected to the actual physical machines on which a Web-based application will ultimately run. Only later, in the Run Processes screen, will actual servers be allocated to the design you create.

Adding Server Types to Architec tures To add a s erver type to an a rchitecture: 1. In the Processes screen Navigation Panel, click the Processes tab.

2. In the tree, select the desired architecture. The Architecture design appears with a list of Server Types above the pane. Server Types already assigned to the Architecture are bolded.

3. Click in the Server Types section. The Assign Server Type dialog appears.

4. Check the Server Types you wish to assign to this Architecture.

5. Click Save.

Ed iting Server Types for Architec tures Edit a server type for an architecture to change the following:

• Rename the server type

• Change the assigned components

• Assign or deassign the server type as a Utility server for running multiple processes concurrently

To edit a s e rver type for an architec ture : 1. In the Processes screen Navigation Panel, click the Processes tab.


3. In the tree, select the desired architecture.



4. In the Central Pane, click on the desired Server Type. The Server Type dialog appears.


6. Click Save.

De le ting Server Types from Architec tures To de le te a s e rver type from an architec ture : 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Select the architecture in the tree.

3. In the tree, select the desired architecture.

4. In the Central Pane, click on the desired Server Type. A confirmation dialog appears.

5. Click Yes. The Server Type is deleted.

As s igning the Multi-Server Type Agent You can assign a specific or multiple Server Agents to a specific Server Type. The Server Types are abstract design elements within the architecture.

When assigning agents to Server Types, it is possible to assign:

• Multiple Agents to one Server Type

• One Agent to multiple Server Types

You can assign multiple agents and Server Types in either a test or production run.

Being able to assign an agent to more than one Server Type allows a specific agent to perform different types of tasks.

To as s ign multip le agents to a s ingle Server Type: 1. In the Environments tab, select an environment.

Server Types defined for the environment display in the right panel.

2. Click the Instances View tab.

3. In the Instances column, double-click on either a specific Server Type or an "empty" agent.

The Edit Environment window will display.

4. In the Edit Environment window, select the Servers tab.

5. For a Server Type, double-click the "Double-click to choose server".

The Available Servers window will display.

To add multiple agents to the Server Type, select the multiple agents in the list while pressing CTRL.

6. Click Choose.

The selected agents will be added to the server type.

To as s ign a s ingle agent to multip le Server Type 1. In the Environments tab, select an environment.

Server Types defined for the environment display in the right panel.

2. Click the Instances View tab.

3. In the Instances column, double-click on either a specific Server Type or an "empty" agent.

The Edit Environment window will display.



4. In the Edit Environment window, select the Servers tab.

5. For a Server Type, double-click the "Double-click to choose server".

The Available Servers window will display.

6. In the Available Servers window, select an agent, and click Choose.

The agent is assigned to the original Server Type.

7. Click Save.

8. To assign the same agent to another Server Type, repeat the procedure.

De fin ing a Server Type to Run Multip le Proces s es Concurrently from an Architec ture You can define a Server Type as a server designated to execute two, or more, processes in parallel. Server types designated as running processes in parallel are called ‘Utility’ servers.

You can define a Utility server from a Process and from an Architecture.

To define a Server Type as a Utility s e rver from an Architec ture : 1. In the Processes tab, select an Architecture.

2. In the selected architecture, select a Server Type.

3. Click the Edit ( ) icon.

The Edit Server Type window opens.

4. Select the Is Utility server check box.

5. Click Save.

Defining a Server Type as a Utility server is for identification purposes only.

Working with Proces s es Processes are sequences of planned activity involving one, some, or all components of an application, and they are themselves assembled by instantiating the lower-level flows and/or actions that have previously been created per component.

Note: Processes are architecture-specific, meaning that they are created in the context of a given architecture that has been defined. Furthermore, in this context they make use of the server type(s) that you have added to the architecture, as described in Declaring Architecture Server Types (on page 63).

Us ing Proces s Categories To define a process for an architecture, you must add the process to one of the architecture's categories. A category is a convenient way of organizing an architecture's processes, much like a folder. Each category represents a group of processes that can be performed within the context of the architecture, and which have something in common.

Nolio Automation Center automatically creates a Processes category.

If desired, you can add new categories, modify existing categories, or delete categories as needed.

Adding Proces s Categories To add a proces s ca tegory to an architec ture : 1. In the Processes screen Navigation Panel, click the Processes tab.



2. Right-click the desired architecture in the tree, and select > in the pop-up menu.

The Processes Category dialog appears.

3. Fill in the fields using the information in the Process Category Fields (on page 67) table.

4. Click Save.

Tab le 17: Pro ces s Catego ry Fie lds


Name Type a name for the category. Monitoring

Description Type a description of the category. Processes related to monitoring

Ed iting Proces s Categories To edit a proces s ca tegory: 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Right-click the desired category in the tree, and select in the pop-up menu. The Processes Category dialog appears.

3. Fill in the fields using the information in the Process Category Fields (on page 67) table.

4. Click Save.

De le ting Proces s Categories Note: You cannot delete a process category if it contains processes that are currently in use. If you attempt to delete such a category, a message appears indicating where the processes are used.



To de le te a proces s ca tegory: 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Right-click the desired category in the tree, and select in the pop-up menu. A confirmation dialog appears.

3. Click Yes. The Category is deleted.

Defining and Developing Proces s es For each architecture, you must define the processes that should be available for the architecture, and add them to the architecture's relevant process categories. Defining a process is performed by creating the process in a process category and then editing the process as desired.

For information on modifying the list of action templates available in the Actions browser, refer to the Actions Reference Guide.

Adding Proces s es To add a proces s : 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Right-click the desired category in the tree, and select > in the pop-up menu.

The Process dialog appears.

3. Fill in the fields using the information in the Process Fields (on page 69) table.



4. Click Save. The Add Server Type dialog appears.

5. Click the check box next to each Server Type that is to be added to the process.

6. Click Save.

7. Assemble the process, as described in Assembling Processes (on page 70).

Tab le 18: Pro ces s Fie ld s


Name Type a name for the process. Monitor Installation Description Type a description of the process. Process to monitor the installation

Ed iting Proces s es To edit a proces s : 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Right-click the desired process in the tree, and select in the pop-up menu. The Process dialog appears.

3. Fill in the fields using the information in the Process Fields (on page 69) table.

4. Click Save.

De le ting Proces s es Note: You cannot delete a process if it is currently in use. If you attempt to delete such a process, a message appears indicating where the process is used.

To de le te a proces s : 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Right-click the desired process in the tree, and select in the pop-up menu. A confirmation dialog appears.

3. Click Yes. The Process is deleted.



Defining a Server Type to Run Multiple Proces s es Concurrently from a Proces s You can define a Server Type as a server specifically chosen to execute two, or more, processes in parallel. Server types designated as running processes in parallel are called ‘Utility’ servers.

To define a Server Type as a Utility s e rver from a Proces s : 1. In the Processes tab, select a Process.

In the selected process, select a Server Type.

2. Right-click on the Server Type, and select Edit from the pop-up menu.

The Edit Server Type window opens.

3. Select the Is Utility server check box.

4. Click Save.

Defining a Server Type as a Utility server is for identification purposes only.

Proces s Works pace Since you define a new process in the context of an architecture that you previously defined, the servers that have been defined and allotted to this architecture are automatically displayed as soon as you open the Process Workspace.

For example, say that for the JPetStore-AppServ demo application, there is defined an architecture that utilizes two generic server definitions. App Server is assigned Tomcat and JPetStore, and DB Server is assigned MySQL.

When a new process is defined for the Two-Server architecture created for the JPetStore-AppServ application, the following template is displayed when you access the Process Workspace.

In this Process Workspace, you can now begin assembling the steps of the new process, in a similar manner to the one you used to create flows by consecutively adding available actions to create the flow sequence, as described in Adding Flow Steps (on page 45).

As s embling Proces s es As indicated, the method by which you create a process sequence is virtually identical to that used for creating flows from actions.

Processes are assembled by instantiating the lower-level flows and/or actions that have previously been created per component.

Note: Processes are architecture-specific, meaning that they are created in the context of a given architecture that has been defined. Furthermore, in this context they make use of the server type(s) that you have added to the architecture.



Ins tantia ting Flows and Actions in Proces s es To add ac tions and flows for a s e rver:

1. For each server, click within the server's workspace.

For example, to add an action or flow to DB Server's workspace, click in the DB Server workspace.

The Actions dialog appears.

2. To view flows, check the Show Application Actions and Flows option at the bottom of the Actions dialog.

3. To filter the actions for selection, enter filter criteria in the 'Type here to filter' box.

4. Select an action or flow to instantiate within the process, and click Add.

However, you should note two things regarding what may be selected from this Actions dialog:

• First, as in the case of constructing flows, you may instantiate within a process both individual actions as well as constructed flows. (However, because processes are designed at a higher level than flows, good design methodology dictates that in most cases you will be instantiating flows in a process, and not actions. Nevertheless, the possibility does exist of instantiating individual actions that have been made available for a given component handled by a server.)

• Second, since all of the components defined for your application are displayed in the browser, technically you can instantiate any of the component flows and actions to a given server. However, methodologically, this instantiation should be consistent with which component(s) you assigned to a given server type when it was defined.

In tegra ting Component-Cons is ten t S teps in Proces s es For example, in the Two-Server architecture defined for the JPetStore-AppServ application, recall that two different servers have been defined:

• App Server is assigned Tomcat and JPetStore.

• DB Server is assigned MySQL.



Therefore, when you assemble this process, you should take care to create process steps only from those components that have been assigned to a given server.

Incons is ten t Example If, for example, you attempt to add a MySQL flow or action to App Server (which was only assigned the Tomcat and JPetStore components), Nolio Automation Center will issue a warning.

This warning will indicate that App Server cannot accept the added flow or action, because MySQL is not listed in the server's Assigned Components List. You will be asked if you would like to add MySQL to the App Server's Assigned Components List.

• If you click No, the added flow or action will not be placed in the process.

• If you click Yes, the added step will be integrated in the process, after the required changes have been automatically made to the Assigned Components List for the App Server.

After clicking Yes, you will note that the App Server is now displayed with the additional MySQL component assigned to it. This also means that during the execution of the process that you are now designing, all Preliminary Checks that have been defined for MySQL will be performed on App Server.

So, if you inadvertently clicked Yes in response to the Nolio Automation Center query, you can undo the modification made to the Assigned Components List.

S equenc ing Proces s S teps Processes make use of the same sequencing convention used to create flows from steps of available actions, as shown in the following figure.

The first three steps in the modeled process that implements the JPetStore-AppServ on a single server are depicted. Each of these steps is an instance of a flow created for a particular component: the first two steps will execute operations related to the installation and invocation of Tomcat; the third step handles the removal of the previous installation of MySQL. (Remember, contrary to the example examined previously, this process was designed for a single server.)

Note: The sequencing of the steps is created by the same flow lines used when creating flows, as described in Linking Steps in a Flow Sequence (on page 48). The same procedures and rules that applied there, are applicable here.



Sequenc ing Opera tions Be tween Diffe ren t Se rvers Within an architecture, when application components have been assigned to different servers, designing the sequence of the process activities will almost always move back and forth between the different servers. This is illustrated in the following figure.

The process depicted here illustrates a simple two-server architecture process.

Execution of the first process step defined for each of the servers begins in parallel. However, the DB Server's first step (Get File From Remote Agent), can only take place after the successful completion of Add Text to a File on App Server. This process sequence is designed by the flow line defined from left to right in the diagram.

Flow lines between sequential steps to be executed on different servers are created just like for flows, as described in Adding a Flow Line between Two Previously Unlinked Steps (on page 49).

Spec ifying Which Server to Wait For When the process that you create is run in your server environment, the activities defined for the different components of the application may in fact be implemented on multiple instances of the same server.

When you design a process, flow lines are extended between different servers, you must define which of the multiple instances of a server should be waited for before moving on to the next step.

To define which s erver to wait for: 1. Select the flow line which links two servers.

2. Right-click and choose the Link Type command.

3. Select from the three available options:

Specific

All

First

If you select Specific, during the actual implementation of the process, user-input will be requested to determine which instance of the server is to be waited for.

Publis hing Proces s es You must publish each process before it can be assigned to an environment and subsequently run.



A process can be published for Sandbox or Public use. The only difference between them is that by publishing to the Sandbox, you can test and review the process in a controlled environment prior to moving it into production.

Once a process is published, it appears bolded in the list of processes.

Note: A process that is not published can only be run as a Test.

Publis h ing Proces s es To publis h a proces s : 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Click the desired process in the tree. The Process appears in the Central Pane.

3. At the top of the Central Pane, click the button (adjacent to Advanced). A confirmation dialog appears.

4. Click Yes. The process appears bolded in the list of processes.

Viewing Publis hed Proces s es To view publis hed proces s es :

• In the Menu Bar, click Administration and select from the pop-up menu. The list of published processes appears in the Central Pane.



Promoting Publis hed Proces s To promote a publis hed proces s from the s andbox to public us e:

1. In the Menu Bar, click Administration and select from the pop-up menu. The list of published processes appears in the Central Pane.

2. In the Central Pane Sandbox Processes list, select the process that you want to promote.

3. In the Central Pane, click to promote the process to Public use. The process moves from the list of Sandbox Processes to the list of Public Processes.

Unpublis h ing Publis hed Proces s es To unpublis h a publis hed proces s :

1. In the Menu Bar, click Administration and select from the pop-up menu. The list of published processes appears in the Central Pane.

2. In the Central Pane, select the process that you want to unpublish.

3. Click . The process is unpublished and removed from the list.

Note: The process will not appear bolded in the list of processes.

User's Guide Automating Applications Processes


Chapte r 7

In This Chapter Using the Run Environment Screen ...................................................................................................................... 76 Creating a Process Run......................................................................................................................................... 96

To automate your design processes, you need to define your environment.

Process environments are designed to run on specific server types.

Nolio Automation Center enables you to specify which servers to use in order to design processes.

Once an application has been published, the automated implementation of this application (i.e. running one, some, or all of the processes you created for a given architecture) can be executed.

This task is performed in the Environments screen and requires you to have Run Processes access level. For information on navigating to the Run Processes screen, see Getting Started with Nolio Automation Center (on page 3).

Us ing the Run Environment Screen Automating applications processes is performed in the Environments screen. This screen includes the following components:

• Navigation Panel

As in all Nolio Automation Center screens, the Navigation Panel appears on the left, displaying trees, the nodes of which can be expanded to display the children nodes, or collapsed.

• Environments pane

The content of the Environments pane is determined by the selected Navigation Panel tree node.

The Environments pane displays the following:

Instances View, Layout View and Activity Information tabs of the selected environment.

Current Activity, Recent Activity, Schedules and Notifications of the selected application.

Current Activity and Recent Activity of the selected process category.

Automating Applica tions Proces s es

Automating Applications Processes


Process progress and Preview tabs, Events Log and Activity Information of the selected process.

Defining Environments The environments defined in Nolio Automation Center specify the real, physical implementation of a specific architecture that was designed for the application. Included in this definition are:

• the number of instances of this architecture that are to be used, and

• the mapping or allocation of real physical servers to the abstract server configurations defined in the architecture.

The Navigation Panel on the left displays the Environments browser tree.

Use the Environments browser tree to add, edit, or remove environments from the Environments screen.

Beneath each application in the Environments browser tree are displayed the environments that are created for the implementation of this application are displayed.

Each environment that is added is designated by the environment icon next to its name.

Note: Only users having Environment Admin permissions, or Superuser role, may modify the definitions of environments other than environments they created.

Crea ting New Environments To crea te a new environment for an application: 1. In the Processes screen Navigation Panel, click the Environments tab.

2. Choose the method to open the New Environment dialog:

In the Navigation Panel tree, right-click an application, and select > from the pop-up menu.

In the Navigation Panel, above the tree, click the button.



The New Environment dialog appears.

3. Fill in the fields using the information in the Environment Fields (on page 79) table.

4. Click Save. The New Environment dialog appears.



5. Select an architecture from the tree for your new environment.

6. Click Save.

Note: The architecture that you select is now fixed for this environment.

You can edit the name and description of this environment, but you cannot edit the architecture for this environment. If you need to change or modify the architecture you must create a new environment. More than one environment can be created per application.

Environment Fie lds Table 19: Environment Fie lds


Name Type a name for the environment. Environment for JPStore Application Description Type a description of the environment. JPStore application environment setup

Ed iting Environments To edit an environment for an application: 1. In the Processes screen Navigational Panel, click the Environments tab.

2. Right-click the desired environment and select from the pop-up menu. The Edit Environment dialog appears.

3. Fill in the fields using the information in the Environment Fields (on page 79) table.

4. Click Save.

Managing Ins tances and Links An environment consists of a physical server that has a Nolio Agent assigned to it.

A process cannot run unless the links between the server types and the physical servers are specified.



As s igning Proces s es to an Environment To as s ign a proces s to an environment: 1. In the Processes screen Navigation Panel, click the Environments tab.

2. Right-click the desired environment in the tree, and select from the pop-up menu. The Assign Processes for Environment dialog appears.

3. Select the check boxes next to the desired processes in the Sandbox Processes and/or the Public

Processes trees.

4. Click Save.

De le ting an Environment To de le te an environment: 1. In the Processes screen Navigation Panel, click the Environments tab.

2. Right-click the desired environment in the tree, and select from the pop-up menu. A confirmation dialog appears.

3. Click Yes. The environment is deleted.

Environments Central Pane The central pane in the Environments screen is devoted to two main activities:

• Linking actual servers to one or more instances of an architecture for which a process or processes were created. (The number of instances is also set in this pane.)



• Running all or a selected subset of the processes that have been defined for a given architecture and which were included in the processes published in Nolio Automation Center.

Viewing an Environment When you initially create or open an already existing environment, as described in Defining Environments, this environment is displayed in the Run Processes screen (see "Instance Views and Layout Views" on page 81).

In s tance Views and La you t Views In the Run Processes screen, you can toggle between the two views of the base architecture in an environment, Instances View and Layout View, by clicking the appropriate tab.

The following figures respectively display the Instances View and the Layout View of the environment defined for this architecture.

The Instances View, shown in the following figure, displays the total number and specific IPs of actual physical servers allocated to this environment.

The Layout View, shown in the following figure, displays a graphical view of the types of servers and the dependencies between them.

For further information, see Managing Instances and Links (on page 79).

Quantifying Server Ins tances In any environment, the number of real machines (instances) that are specified for a server type indicates the maximum number that may be allocated during implementation. In fact, fewer servers may also be used.

The number of instances of a server type is set in the Processes screen Process tab. Initially a single instance is specified for each server type.

Note: Only users having permission status of Manager, Administrator, or Superuser may modify the number of instances of a server type that is usable in a given architecture.



To modify the number of ins tances s pec ified per s e rver: 1. In the Processes screen Navigation Panel, click the Processes tab.

2. Select the desired application in the tree.

3. Select the desired architecture in the tree.

4. At the top of the central pane, click as shown in the following figure.

The Assign Server Type dialog appears.

5. Check the Server Types that you want to assign to this Architecture.

6. Click Save.

Linking Servers to an Environment After the number of instances of a given server that are available for allocation during implementation of an application is defined, you need to map real physical servers in your system to the servers specified in the current Nolio Automation Center environment.

This can be done in the Instances View of the Environment pane.

Note: Only users having permission status of Manager, Administrator, or Superuser may link real physical servers to a given Nolio Automation Center environment.



Linking Servers in the Ins tance View To link s ervers in the Ins tance View: 1. Double-click the IP (or the Empty label) inside the instance rectangle. The Edit Environment dialog appears.

2. For each server, double-click the Double-click to choose server label.

3. In the Available Servers dialog, select the physical server to be allocated to the current instance. (Servers that have already been allocated appear crossed out in the list, indicating that they are not available). Click Choose.

When you have finished, click Save. The IP of the mapped server is displayed in the instance section.

Viewing Activity Information The lower area of the Environments screen central pane displays the Activity Information, detailing current activity, recent activity, schedules, and notifications.

Click to expand the Activity Information to view the various activity tabs:

• Current Activity (on page 84)



• Recent Activity (on page 84)

• Schedules (on page 85)

• Notifications (on page 88)

Note: It is possible to view the activity information for any application, environment, and process category by clicking the specific item in the tree in the Navigation Panel and viewing the Activity Information in the Environments screen central pane.

Curren t Ac tivity Table 20: Curren t Activity Report

Activity Result Displays

Date When the process was run Application From which application Environment From which environment Category From which category Process The process name Run The process run name User The user who ran the process Status The status that the process reached Duration How long the activity took

Recent Ac tivity Recent Activity reporting is limited to the last five processes that were run for this application.

You can double-click the Recent Activity report lines to view further details.

Table 21: Recen t Activity Report

Recent Result Displays

Date When the process was run Application From which application Environment From which environment Category From which category Process The process name Run The process run name User The user who ran the process Status The status that the process reached



Recent Result Displays

Duration How long the activity took

S chedules Schedules can only be defined for processes.

Schedules can be set, edited, deleted and viewed in the Environments screen Activity Information section in the Schedules tab, when a process is selected in the Navigation Panel tree.

S e tting a New Schedule To s e t a new s chedule for a proces s : 1. In the Environments screen, select a process from the tree.

The process is displayed in the central pane.

2. At the top of the central pane, click Advanced.

3. Click to expand the Activity Information, select the Schedules tab. The Schedules tab is displayed.



4. Click to the right-hand side of Schedules tab. The New Schedule dialog appears.

5. Fill in the fields using the information in the Schedule Fields (on page 86) table.

6. Click Save.

Tab le 22: Sch edule Fie lds


Name Type a name for the schedule. Simple Schedule Frequency Number of times: Once, Hourly, Daily, Weekly, Monthly, or Cron

Expression. Daily

Start At Type the start time in the hour:minute:second format. 22:00:00 Start process every Varies according to Frequency setting. 1

Servers Enter the server names or choose the servers from the server list

by clicking .




Parameters Enter parameters or choose predefined parameters from the Parameters list.

Click the to the right of the Parameters field to view and modify predefined parameter values. Note: If you do not provide values at this point, Nolio Automation System will prompt you for parameter values during the process run.

Ed iting a Schedule To edit a s chedule: 1. In the Environments screen Activity Information, select the Schedules tab.

2. Select the Schedule.

3. Click on the right side of the Schedules tab. The Edit Schedule dialog appears.

4. Fill in the fields using the information in the Schedule Fields (on page 86) table.



5. Click Save.

De le ting a Schedule To de le te a s chedule: 1. In the Environments screen Activity Information, select the Schedules tab.

2. Select the Schedule.

3. Click on the right side of the Schedule tab. A confirmation dialog appears.

4. Click Yes. The schedule is deleted.

No tifica tions Notifications are defined before a process run is executed.

Nolio Automation Center sends email notifications about the process run to specified users that were previously set up in the Users Management section in the Administration screen. The email notifications notify the user about the state of the process run.

Notifications created at the process run level are able to notify users with regards to any changes in the execution of the process run only.

Notifications can notify users if a process has been published or republished.

Notifications can also be set to notify users if changes were made to the environment, for example, if changes were made to server environments.

Note: Notifications can be set for either an Environment or a Process according to which is selected in the tree at the time of creating the notification. For the purposes of this section, the notification for an Environment is used.

S e tting a New Notifica tion To s e t a new notification for an environment: 1. In the Environments screen Activity Information, select the Notification tab.



2. Click on the right side of Notification tab. The New Notification dialog appears.

3. Fill in the fields using the information in the Notification Fields (on page 89) table.

4. Click Save.

Tab le 23: Notifica tion Fie lds


Name Type a name for the notification. This is the name that will subsequently be displayed. Notify about Environment Changes. Changes made to environments.



In this field Do this For example Execution Changes. Changes to execution states that will invoke notifications:

• A Process is running • A Process is failed paused • A Process is paused • A Process is stopped • A Process is finished • A Process Run was created • A Process Run is waiting for user input • A Process Run is waiting for parameters

Publishing Changes. Changes made to published processes. Notify these users Select one or more users from

the browser list. This is the user (or users) that will subsequently receive the notification by email.

Ed iting a Notifica tion To edit a new notifica tion for an environment: 1. In the Environments screen Activity Information, select the Notification tab.

2. Select the Notification.

3. Click on the right side of Notification tab. The Edit Notification dialog appears.

4. Fill in the fields using the information in the Notification Fields (on page 89) table.

5. Click Save.

De le ting a Notifica tion To de le te a notifica tion: 1. In the Run Processes screen Activity Information, select the Notification tab.

2. Select the Notification.

3. Click on the right side of Notification tab. A confirmation dialog appears.

4. Click Yes. The notification is deleted.

P roces s Execution Pane Processes are first published and then they are assigned to an environment.

Note: Only users having Operator access level, or Superuser role, and process permissions may run processes other than processes they created.

Processes can be viewed in the tree of the Environments screen Navigation Panel. When selected in the tree, the process is displayed in the Center Pane, as shown in the following figure. By hovering (with the mouse) over the actions, it is possible to select an action and make modifications by editing the action before the process is run. For further information, see Editing Applications (on page 16).



Pre-Run Display

When processes are executed, the Environments pane switches from the pre-run display of processes to a display in which the progress of the run can be followed in different views:

Process View - shows a graphical depiction of the process Flow



Detailed View - Show run status on each server

Events Log - of the steps involved in the process run



Crea ting a New Proces s Run To crea te a new run for a proces s :

1. In the Environments screen, click . The Run Process dialog appears.

2. Enter a Name for this run.

3. In the Servers tab, select the servers for this run.

4. In the Dependencies tab, specify or change the links between the server types and physical servers.

5. Click Run.

Note: Nolio recommends that you accept the automatically generated Name.

Viewing a Proces s Run The Detailed View displays the execution of the process currently being run. It does so using the same process diagram that was designed for a given environment in Nolio Automation Center.



However, the graphic depiction of the process is dynamic, thereby enabling you to visually trace the run's progress.

Viewing the Proces s Summary The Detailed View displays the current status, overall progress, and current step being executed both by server type, and each of the individual instances of each type, involved in the process run.

Process run status Displays

Instance The name of the server type or the name of the server Status Current status of the server




Progress Current progress Current Step Current running action on this server

When a process starts, one of the standard preparation steps that is not contained within the designed process is copying files from the central server to the target agents. The progress of copying files to the agents will be displayed in the Detailed View tab as follows:

• In the Status column, 'File Distribution' will display.

• In the Progress column the percentage of the total files copied will display.

• In the Current Step column, the number of bytes copied and the total number of bytes to be copied will display.

Viewing the Events Log The Events Log displays a table of notifications related to the execution of a process.

To view the events log of a proces s run: Expand the Events Log below the Process run status to display the information shown in the following table.

Table 24: Pro ces s Sta tus Events Log

Process status Displays

Event Any one or more of the event filters Server The server name and IP Step The name of the action Start Start time End End time Comments Results or comments on the current event

Events Log Filte rs The Events Log can be filtered using the information in the following table.

Table 25: Even ts Log Filte rs

Click this filter To do this

Notification Events Filter out Notification events from the events log

Pass Events Filter out Pass events from the events log

Fail Events Filter out Fail events from the events log

Cancel Events Filter out Cancel events from the events log




Fail-Pause Events Filter out Fail-Pause events from the events log

Viewing an Agent Execution Log When a process performs an agent-specific action, information about the execution steps is recorded in the agent execution log. The agent execution log, nolio_action_exe.log, is located with the Nolio file system level logs.

Crea ting a Proces s Run Before actually running an implementation from the Environments pane, a number of preparatory operations must be performed from the console:

1. A user having sufficient permission (i.e. Manager, Administrator, or Super User) must define one or more Environments in which applications will be implemented. Each Environment defines the real, physical implementation of a specific architecture that was designed for a given application. (Recall that, by itself, an architecture still only specifies the abstract server configurations defined for it.)

2. After having made the initial declaration of such an Environment, two main tasks related to its definition must be performed:

a. Specify the number of instances of the architecture to be used in the implementation of the designed application.

b. Link the real, physical servers that are available for the implementation, either individually and/or in server groups, to the server types (abstract server configurations) that were created for implementing the designed processes.

3. Finally, from among the processes that were developed, the processes that are actually to be run must be selected. This last operation can be performed by users with any level of permissions, including Operators.

The above operations are described in more detail in the sections that follow.

Note: Multiple environments can be created for any given architecture. In such cases, the environments vary per the number of architecture instances that they incorporate, and or the linking of physical servers to the architecture's design.

Generating Reports


Chapte r 8

In This Chapter Overview ................................................................................................................................................................ 97 Accessing the Reports Screen .............................................................................................................................. 97 Generating Audit Reports ...................................................................................................................................... 97 Generating Management Reports ......................................................................................................................... 98 Viewing Reports ................................................................................................................................................... 100 Deleting Reports .................................................................................................................................................. 101

This section explains how to generate reports in Nolio Automation Center.

This task is performed in the Reports screen and does not require an access level.

Ove rview Nolio Automation Center allows you to generate the following types of reports:

• Online and Offline Audit Reports (see "Generating Audit Reports" on page 97)

• Management Reports (see "Generating Management Reports" on page 98)

Reports enable you to view the status of processes and their flows within a specified time frame. By using various filters, you can view specific data for each process. You can also quickly generate many different reports using various filter criteria to the same screen, with each report displayed within its own report tab.

Audit Reports and Management Reports can be exported to PDF file format.

Acces s ing the Reports Screen All Nolio Automation Center Reports are generated and viewed in the Reports screen.

For information on navigating to the Reports screen, see Getting Started with Nolio Automation Center (on page 3).

The Reports screen appears displaying the Reports panel on the left, where you can choose the type of report you wish to view, and the Reports pane on the right, where you can set the report filters and view the report results.

Genera ting Audit Reports The Audit reports are divided into the following:

• Online Audit reports: display reports on currently running processes

• Offline Audit reports: display reports on terminated processes

Nolio Automation Center enables you to generate an Audit Report directly to the screen or to a PDF file.

To genera te an audit report: 1. In the Reports screen Navigation Panel, click Online Audit Report or Offline Audit Report.

Genera ting Reports

User's Guide Generating Reports


2. Set the Report Filters using the information in the Report Filters (see "Management Report Filters" on page 99) table.

3. In the central pane:

Click to generate a report on the screen.

Click to generate a report to a PDF file.

Audit Report Filters Table 26: Audit Report Filte rs


Applications Filter the report to contain processes from specific applications Processes Filter the report to contain specific processes Environments Filter the report to contain processes from specific environments Users Filter the report to contain processes run by specific users Categories Filter the report to contain processes from specific categories Status Filter the report to contain processes with specific statuses; not included in the Online Audit

report Time Frame Filter the report to contain processes that were run on a specific time frame

By not selecting any filters, you effectively select all the filter options for the report, as if you had "selected all".

Genera ting Management Reports Nolio Automation Center enables you to generate a Management Report directly to the screen or to a PDF file.

To genera te a management report: 1. In the Reports screen Navigation Panel, click Management Report.

2. Set the Report Filters using the information in the Report Filters (see "Audit Report Filters" on page 98) table.

3. In the central pane:

Generating Reports


Click to generate a report on the screen.

Click to generate a report to a PDF file.

The management reports runs on terminated processes only.

Management Report Filters Table 27: Management Report Filte rs


Applications Filter the report to contain processes from specific applications Processes Filter the report to contain specific processes Environments Filter the report to contain processes from specific environments

Users Filter the report to contain processes run by specific users Categories Filter the report to contain processes from specific categories Status Filter the report to contain processes with specific statuses Time Frame Filter the report to contain processes that were run on a specific time frame

By not selecting any filters, you effectively select all the filter options for the report, as if you had "selected all".

User's Guide Generating Reports


Viewing Reports Nolio Automation Center enables you to view Audit or Management Reports directly on the screen or in a PDF file as soon as you have generated a report.

Viewing an Audit Report To view an audit report: 1. In the Reports screen Navigation Panel, click Online Audit Report or Offline Audit Report.

2. Set the report filters and generate the report as described in Generating Audit Reports (on page 97). Information about the report appears in the Report Result area.

Table 28: Report Res u lts

Report Result Displays

Date When the process was run Application From which application

Environment From which environment Category From which category Process The process name Run The process run name User The user who ran the process Status The status that the process reached Elapse How long it took (the duration)

Viewing the Proces s Run To view the proces s run d is played in an audit report: 1. Double-click the process displayed in the report results line in the Audit Report to open the Process run

view. Information about the process run status is displayed in the Process Run Status table.

2. To view the Events Log, expand the Events Log below the process information. Information about the Events Log is displayed in the Process Run Events Log table.

3. Click Close to close the Process run view.

Table 29: Pro ces s Run Sta tus


Instance The name of the server type or the name of the server Status Current status of the server Progress Current progress Current Step Current running action on this server

Table 30: Pro ces s Run Events Log

Process status Displays

Event Any one or more of the event filters Server The server name and IP Step The name of the action

Generating Reports


Start Start time End End time Comments Results or comments on the current event

The Events Log can be filtered using the information in the Events Log Filters (on page 101) table.

Events Log Filte rs Table 31: Even ts Log Filte rs


Notification Events Filter out Notification events from the events log

Pass Events Filter out Pass events from the events log

Fail Events Filter out Fail events from the events log

Cancel Events Filter out Cancel events from the events log

Fail-Pause Events Filter out Fail-Pause events from the events log

Viewing a Management Report To view a management report: 1. In the Reports screen Navigation Panel, click Management Report.

2. Set the Report Filters and generate the report as described in Generating Management Reports (on page 98). Information about the report appears in the Report Result area.

Table 32: Management Report Res u lts

Report Result Displays

Application From which application Category From which category # How many processes Average Time Average duration

De le ting Reports To de le te a report from the Reports s c reen:

• Click in the report's tab.

Nolio Automation Center automatically saves the generated PDF report files to your desktop.

To de le te a report tha t was genera ted to PDF format: 1. Locate the PDF report file saved on your desktop.

2. Select the PDF report file and press the Delete key. The PDF report file is deleted.

User's Guide Server Definition Operations


Chapte r 9

In This Chapter Running a Process .............................................................................................................................................. 102 Individual Agents Definition Operations ............................................................................................................... 104 Agents Group Operations .................................................................................................................................... 105

The individual, real physical servers that are to be made available to implement an application must be accessible to Nolio Automation Center. This is done by defining them in Agents Managements in the Administration section of Nolio Automation Center.

Once a server has been defined, it can be mapped directly to an architecture. It can also be joined to a group of servers which may then be mapped together.

Note: Only users with permission status of Manager, Administrator, or Superuser may make server-related definitions in Nolio Automation Center.

Running a Proces s After defining the actual physical environment in which one or more automated process runs are to be launched, and having created a new process run, the process of executing a process run can begin.

Setting Required Input Values The designed actions, flows, and processes to be executed often require the entry of input values prior to a run.

Server Defin ition Opera tions

Server Definition Operations


To s e t input va lues :

1. In the Environments screen, click . The Run Process dialog appears.

2. Complete the form (see Creating a New Process Run (on page 93)) and clear the Automatically start the

process check box.

3. Click Run. The Environments screen Central Pane displays the Detailed View.

4. In the Environments screen Central Pane, click .

5. In the Parameters dialog, enter values for the relevant parameters.

Note:

Parameters displayed on a yellow background require input values. However, not entering such a value at this stage will not prevent launching the run.

When, during the course of process execution, a required input value is critical to the continuation of the run, the Parameters dialog will automatically be reopened by Nolio Automation Center, and you will be prompted to enter a value for the parameter. Now, the required input value will be displayed in bold on an orange background. You must enter the required value and click Apply to proceed with execution of the process.



Controlling a Proces s Run The process run is controlled using the icons displayed in the Process Summary tab.

For this Control Name Click this Icon or Button

To distribute the process files to the appropriate Nolio Agents (execution servers) Note: Performing this operation only distributes the files without actually executing the process. You might want to do this if the process to be run involves a very large number of files that could be conveniently distributed at night, for example.

File Distribution

To execute the processes that have been distributed. Run To run a process, which includes distributing and executing files. Run After the Preliminary Checks defined for the process executed and completed, a message appears. You can then:

Immediately proceed with the process execution Proceed Continue Prevent the default, automatic continuation of execution Stop Stop Let execution continue after 10 seconds Continue [do nothing] To pause a process after it has begun executing Pause To resume execution of a process that has been paused Resume To stop the execution of a running process Stop

To completely stop and remove a running process Remove

Viewing the Proces s Run Progres s As already discussed, the Process Run progress can be monitored in one of three views:

• Viewing a Process Run (on page 93)

• Viewing the Process Summary (on page 94)

• Viewing the Process Events Log (see "Viewing the Events Log" on page 95)

Ind ividual Agents Defin ition Opera tions These operations pertain to the adding, modifying, and removing of the definitions of actual servers that are to be made available for the actual implementation of the application.

These tasks are performed via the Agents List located on the left side of the Administration screen Agents Management tab central pane. The list displays each of the actual physical agents which are available for use in implementing the applications that have been developed in Nolio Automation Center.

Note: Nolio Automation Center's Agents List is automatically kept up to date as each Agent on which Nolio Agent is installed will automatically be identified by Nolio Automation Center. Nevertheless, you can use the functionality described in this section to modify the definitions for the servers appearing in Nolio Automation Center's Agents List.



Adding Agents to the Agents Lis t Adding Agents to the Agents List is done automatically once they are installed and connected to Nolio Automation Center.

Modifying an Agent's Definition To modify the defin ition (Name or IP Addres s ) tha t appears in the Agents Lis t: 1. In the Agents List, select the Agent(s) to be modified.

2. In the icon bar located above the Agents List, click . The Agent dialog appears.

3. Modify the Name or IP Address as required.

4. Click Save.

Removing an Agent from the Agents Lis t When you remove an Agent from the Agents List, it will not be available for implementation of the application.

To remove one or more Agents from the Agents Lis t: 1. In the Agents List, select the Agent(s) to be removed from the list.

2. In the icon bar located above the Agents List, click . The Agent is removed from the Agents List.

Agen ts Group Opera tions The Agents in the Agents List can be organized into groups called Agent Groups to facilitate their management and allocation.

The operations related to Agent Groups pertain to how they are created, modified, removed, and how agents are assigned to a given Agent Group.

These tasks are performed via the Agent Groups List located on the right side of the Administration screen Agents Management tab Central Pane.

Note: To manage Test Agent Groups, click the Administration screen's Test Agents Management tab and follow the instructions for Agent Groups Operations.

Adding an Agent Group To add an Agent Group: 1. In the Agent Groups List, select the Agent Group for which you want to define a sub-group.



2. In the icon bar directly above the Agent Groups List, click . The Agents Group dialog appears.

3. Enter a name for the new Agent Group, and an optional description for the group.

4. Click Save. A folder depicting the newly defined sub-group appears in the Agent Groups List.

Note: Once you have defined Agent Groups and sub-groups in the Agent Groups List, the Agents populating these groups may be assigned to the groups. (See Assigning Agents to an Agent Group (on page 106) for further details.)

Modifying an Agent Group To modify an exis ting Agent Group: 1. In the Agent Group List, select the Agent Group to be modified.

2. In the icon bar directly above the Agent Group List, click . The Agents Group dialog appears.

3. Enter the new details for the selected Agent Group.

4. Click Save.

Removing an Agent Group To remove an exis ting Agent Group: 1. In the Agent Groups List, select the Agent Group to be removed.

2. In the icon bar directly above the Agent Groups List, click . A confirmation dialog appears.

3. Click Yes. The Agent Group is removed.

Note: When you remove an Agent Group, the Agents that it contained are not removed from the Agents List.

As s igning Agents to an Agent Group To as s ign one or more Agents to an Agent Group: 1. In the Agents List, select each Agent to be added to the desired Agent Group.



2. In the Agent Group List, select the Agent Group to which the selected Agents are to be added.

3. Click located between the two lists to add the selected Agent(s) to the Agent Group.

Note: A single Agent can simultaneously belong to any number of Agent Groups. This means that the same Agent can participate in as many Agent configurations as you need to define.

Removing Agents from an Agent Groups To remove one or more Agents from an Agent Group: 1. In the Agent Groups List, select each Agent to be removed from the desired Agent Group.

2. Click located between the two lists to remove the selected Agent(s) from the Agent Group.

User's Guide Exporting and Importing


Chapte r 10

In This Chapter Exporting .............................................................................................................................................................. 108 Importing .............................................................................................................................................................. 109

Nolio Automation Center allows you to Export Architectures and/or Components from an Execution Server. The export file can then be imported back to the same or different Execution Server.

By default, the data is stored in "<My Documents>\export.dat".

Exporting To export from Nolio Automation Center: 1. In the Menu Bar, click File > Export. The Export dialog appears.

2. Mark the elements you wish to export.

Exporting and Importing

Exporting and Importing


3. Click Export. The Export in progress dialog appears.

4. When the export is complete, click Close.

Notes:

If you export Components or Architectures without selecting the Application, then when you import them, an Import wizard opens in which you will need to supply the name of the Application.

If one of the Component items uses a global parameter, the parameter is exported with the Component. When the Component is imported, the parameter becomes a Component parameter and is located in a separate parameter folder of the component.

If you export an Architecture which has Server types X, Y, Z defined and then import the Architecture into an existing Application, you will be required to map between the Architectures servers and the Applications servers.

Importing To import to Nolio Automation Center: 1. In the Menu Bar, click File > Import. The Import dialog appears.

2. In the File field, enter the path to, or click File and navigate to, the import file.

3. Mark the elements you wish to import.

4. Click Import. The Import in progress dialog appears.

5. When the import is complete, click Close.

Notes:

Importing a Component also imports the associated Actions, Flows, and Parameters.

User's Guide Exporting and Importing


Importing an Architecture also imports the associated Server Types, Processes, and Process Parameters.

There is difference in behavior when importing Published and Unpublished Processes:

Importing a Published process allows you to edit and run the Process.

Importing an Unpublished process allows you to run the Process, but not to edit or change the Process.

Importing an application when there is already an application with the same name is allowed. A new application will be created with the same name.

Appendix - Action Parameter Types


In This Appendix String Parameters ................................................................................................................................................ 111 Password Parameters ......................................................................................................................................... 112 Boolean Parameters ............................................................................................................................................ 114 File Parameters ................................................................................................................................................... 114 Predefined Options Parameters .......................................................................................................................... 115 General Parameters ............................................................................................................................................ 117 Numerical Parameters ......................................................................................................................................... 117 Array Parameters ................................................................................................................................................. 118

The following topics describe the parameter types available within ASAP Actions.

S tring Parameters View and modify String parameter properties, as shown in the following figure and table.

Table 33: S tring Pa rameter Prope rty Fie ld s


Click this button to assign this parameter a null value.

Click this button to assign this parameter a plain value. Enter the desired string in the field provided.

Click this button to assign this parameter a parameter value.

The button appears. See for further details.

Click this button to specify an expression that utilizes parameters defined for the component or its parent application. A field appears in which you can type the desired expression.

In addition, the and buttons appear. In this field Do this

Click this button to open the Parameters List, which displays


User's Guide Appendix - Action Parameter Types


In this field Do this all available parameters for the application and component. Select the desired parameter, and then click Choose.

Click this button to edit the expression in full view. The Edit expression dialog appears.

Click the button to select desired parameters, and then click Save.

Select this option to indicate that the parameter is a public parameter, meaning that it must be assigned appropriate values during execution. If this option is not selected, the parameter will be a private parameter. Private parameters are used during the execution of the action, but do not require any input from the Run Processes screen. For more information, see Defining Parameters for Actions (on page 30).

P as s word Parameters If you view a password parameter in the Parameter tree, you are able to see if as already been assigned a value:

• A password parameter which does not have a value assigned displays 'No Value' below the Value label:

• A password parameter which has a value assigned displays a row of asterisks ('*') below the Value label:

To modify a parameter va lue

1. Select the target parameter and click to edit.



The password parameter screen opens.

2. Use the following Password Parameter Property Fields table as a guide to adding or editing a password

parameter.

Table 34: Pas s word Pa rameter Prope rty Fie lds



Click this button to assign this parameter a plain value. Enter the desired password in the field provided.

Click this button to revert to the previous parameter value.


Note:

The following is relevant for entered password parameters:

Passwords stored in this parameter are encrypted in the database and can only be decrypted by the agent that will use this parameter for the specific action that will use this parameter.

As passwords are entered, an asterisk (*) will display for each character. However, when viewing an entered password, the number of displayed asterisks will be different than the actual number of password characters.

Passwords are not editable and may only be replaced. When in Edit mode, the password field will be blanked out as soon as a character is modified.



Boolean Parameters View and modify Boolean parameter properties, as shown in the following figure and table.

Table 35: Boolean Pa ram eter Prope rty Fie ld s



Click this button to assign this parameter a plain value. Select TRUE or FALSE in the list provided.




File Paramete rs File parameters may be used to specify the location of executable and other files and dependencies that are to be integrated in the published application.

Note: The files should be located on the Center server or be accessible by it.



View and modify File parameter properties, as shown in the following figure and table.

Table 36: File Pa ramete r Prope rty Fie ld s



Click this button to assign this parameter a plain value. The File Path and Publish Method fields appear.

File Path Type the path to a file located on your storage system that is to be integrated in the published application. This can be either a UNC path of a local path in the Nolio Automation Center server.

Publish method Select the desired publishing method: • Once: to integrate the specified file in the application when the application is published. • Every execution: to integrate the specified file in the application when the application is

published, and again when the application is executed.

P redefined Options Parameters Predefined Options parameters allow creating a parameter that will be assigned one of the possible enumerated values.



View and modify Predefined Options parameter properties, as shown in the following figure and table.

Table 37: Predefined Options Pa rameter Prope rty Fie lds



Click this button to assign this parameter a plain value.

The Selected Value drop-down list and button appear. Select the desired value for this parameter from the list of possible values. Leaving the value blank will assign this parameter a null value.

Click to edit the Selected Value drop-down list's content The Edit List dialog appears.

To add an e lement: 1. Select an element.

2. In the drop-down list beside , select above or below.

3. Click the button.

To remove an element, select the element and click .





Genera l Parameters View and modify General parameter properties, as shown in the following figure and table.

Note: General parameters can be used by actions as outputs/inputs only.

Table 38: Genera l Parame ter P roperty Fie lds





Numerica l Parameters Numerical parameters may be any of the following types: Integer, Long integer, Double integer, or Floating point.

View and modify Numerical (Integer) parameter properties, as shown in the following figure and table.



Table 39: Numerica l Pa rameter Prope rty Fie lds



Click this button to assign this parameter a plain value. Use the up and down arrows to specify the desired value.




Array Parameters A parameter array may be defined for any of the following values: String, Boolean, Integer, Long integer, Double integer, and Floating point.

View and modify String Array parameter properties, as shown in the following figure and table.

Table 40: Array Pa ramete r P roperty Fie lds



Click this button to assign this parameter a plain value.

The button appears. Click this button to edit the specific elements of the array.

The Edit List dialog appears. You can add elements by clicking , and remove them by clicking . When finished, click Save.



Select this option to indicate that the parameter is a public parameter, meaning that it must be assigned appropriate values during execution.



In this field Do this If this option is not selected, the parameter will be a private parameter. Private parameters are used during the execution of the action, but do not require any input from the Run Processes screen. For more information, see Defining Parameters for Actions (on page 30).

User's Guide Index


Ac tion

An action is a predefined operation that may be made available to and customized for application components. In the context of the flows created in Nolio Automation Center, each such action becomes a step in the flow.

Applica tion

In the context of Nolio Automation Center, an application is a high-level design construct whose design and ultimate execution allow achieving a fully-automated implementation of a server-based system. In Nolio Automation Center, applications are developed in the Processes screen's Components tab.

Architec ture

In the context of designing in Nolio Automation Center, an architecture is a generic design of a possible physical configuration for the implementation of an application.

Component

A component is each one of the system-level software modules that is involved in the implementation of a server-based application designed in Nolio Automation Center.

Environment

In Nolio Automation Center, an environment, defined in the Processes screen's Processes tab, is one of any number of real, physical implementations of a specific architecture that was designed for the application. (By itself, an architecture still only specifies the abstract or generic server configurations defined for it.)

Flow

A flow is the grouping together of actions, made available to an application's component. This grouping together of actions specifies the chronological sequence in which two or more actions will occur. In addition, it may specify the conditional nature of the transition made from the completion of one action to the start of the next action in the sequence.

Implementa tion

The fully automated performance of all operations related to the deployment, maintenance, or other activities, on the software components participating in a server-based application. An implementation is achieved by executing some or all of the processes created for an architecture.

Nolio Agent

Nolio Agent is the Nolio Automation Center module that receives the appropriate instructions passed to it by Nolio Automation Center and implements them on the server to which it is linked.

Nolio Cente r

Nolio Automation Center's Nolio Center is the central control mechanism that coordinates the implementation of packaged processes designed in Nolio Automation Center.

When a process is actually executed, the appropriate data and instructions are channeled from the Nolio Center via one or more dedicated Gateways to the Nolio Execution Server that manages a specific Data Center. Handling data propagation for a specific group of servers, each Data Center also includes any number of Nolio Agent modules, each of which controls a specific physical server involved in the execution of a process.

Predefined Parameter

Two parameters supplied by Nolio that can be used only as private parameters: hostname and IP. These predefined parameters cannot be modified or deleted. They are relevant for processes only.

Glos s ary

Index


Priva te Parameter

A parameter that can be integrated in the definition of actions, but which does not require any user input prior to implementation of an application. A parameter is made a private parameter by setting its Public use property to False. This is the default setting.

Proces s

A process is a high-level sequence of planned activity involving one, multiple, or all components of an application. A process is assembled by instantiating the lower-level flows that have previously been created per component.

Public Paramete r

A public parameter must be assigned appropriate values from the Run Processes screen when an application is to be implemented. A parameter is made a public parameter by setting its User Input property to True.

Server Type

An abstract representation of a server specified for a particular architecture.

Step

A step is an action integrated into a flow created for an application component.

User's Guide Index


A A Typical Workflow • 1 About this Document • viii Accessing the Reports Screen • 97 Action • 120 Action Parameter Types and Properties • 32, 33, 36 Adding Actions • 23, 26, 48 Adding Agents to the Agents List • 105 Adding an Agent Group • 105 Adding and Editing Parameter Folders • 30 Adding Applications • 2, 16, 17 Adding Architectures • 2, 62 Adding Component Categories • 15, 21, 22 Adding Components • 17, 18 Adding Flow Steps • 45, 49, 70 Adding Flows • 41 Adding Parameters • 32 Adding Process Categories • 66 Adding Processes • 68 Adding Server Types to Applications • 59 Adding Server Types to Architectures • 64 Agents Group Operations • 105 Appendix - Action Parameter Types • 111 Application • 120 Applications Components Tree • 14 Architecture • 120 Array Parameters • 37, 118 Assembling Flow Steps • 42, 43, 44, 45 Assembling Processes • 69, 70 Assigning Agents to an Agent Group • 106 Assigning Processes to an Environment • 2, 80 Assigning the Multi-Server Type Agent • 65 Audit Report Filters • 98 Automating Applications Processes • 56, 76

B Boolean Parameters • 36, 114 Browsing the Components Tab Parameters • 15

C Changing the Step from which a Flow Line Exits • 50 Changing Your Account Settings • 7 Component • 120 Components Tab Central Pane • 14 Components Tab Navigation Panel • 13 Controlling a Process Run • 104

Copying, Cutting, and Pasting a Flow • 43 Copying, Cutting, and Pasting a Parameter • 35 Copying, Cutting, and Pasting an Action • 27 Creating a New Process Run • 93, 103 Creating a Process Run • 96 Creating Action Flows • 2, 20, 40 Creating New Environments • 77 Current Activity • 83, 84

D Debugging Using the Conflicts Browser • 37, 38 Declaring Application Server Types • 59 Declaring Architecture Server Types • 2, 57, 63, 66 Defining a Server Type to Run Multiple Processes

Concurrently from a Process • 70 Defining a Server Type to Run Multiple Processes

Concurrently from an Architecture • 66 Defining Actions • 20, 23, 53 Defining and Developing Processes • 68 Defining Environments • 2, 77 Defining Loops • 53 Defining Parameters for Actions • 30, 53, 112, 113,

114, 117, 118 Deleting a Notification • 90 Deleting a Schedule • 88 Deleting Actions • 29 Deleting an Environment • 80 Deleting Applications • 17 Deleting Architectures • 63 Deleting Component Categories • 22 Deleting Components • 19 Deleting Flow Lines • 51 Deleting Flow Steps • 48 Deleting Flows • 45 Deleting Parameter Folders • 31 Deleting Parameters • 36 Deleting Process Categories • 67 Deleting Processes • 69 Deleting Reports • 101 Deleting Server Types from Applications • 61 Deleting Server Types from Architectures • 65 Designing Applications Processes • 55 Displaying Definitions of Actions Instantiated within a

Flow • 44

E Editing a Notification • 90

Index

Index


Editing a Schedule • 87 Editing Applications • 16, 90 Editing Architectures • 63 Editing Component Categories • 22 Editing Components • 18 Editing Environments • 79 Editing Flows • 42 Editing Parameter Folders • 31 Editing Parameters • 33, 34 Editing Process Categories • 67 Editing Processes • 69 Editing Server Types for Applications • 60 Editing Server Types for Architectures • 64 Elaborating Component Actions • 2, 20, 58 Environment • 120 Environment Fields • 78, 79 Environments Central Pane • 80 Events Log Filters • 95, 101 Exporting • 108 Exporting and Importing • 108

F File Parameters • 36, 114 Filtering the View • 12 Flow • 120

G General Parameters • 37, 117 Generating Audit Reports • 97, 100 Generating Management Reports • 97, 98, 101 Generating Reports • 97 Getting Help • 9 Getting Started with Nolio Automation Center • 3, 11,

20, 40, 55, 76, 97

H How Nolio Works • 1

I Implementation • 120 Importing • 109 Inconsistent Example • 72 Individual Agents Definition Operations • 104 Instance Views and Layout Views • 2, 81 Instantiating Flows and Actions in Processes • 71 Integrating Component-Consistent Steps in

Processes • 71 Intended Audience • viii Introducing the Nolio Automation Center • 1

L Linking Servers in the Instance View • 83 Linking Servers to an Environment • 82 Linking Steps in a Flow Sequence • 48, 72 Logging in to Nolio Automation Center • 2, 3, 9 Logging Out of Nolio Automation Center • 9

M Main Screen • 4 Management Report Filters • 98, 99 Managing Instances and Links • 79, 81 Manually Adding Flow Lines • 46, 49, 73 Menu Bar • 4, 6 Methodology • 41 Modifying an Agent Group • 106 Modifying an Agent's Definition • 105

N Navigating between Nolio Automation Center

Screens • 5 Navigation Panel • 4, 5 Nolio Agent • 120 Nolio Center • 120 Notifications • 84, 88 Numerical Parameters • 37, 117

O Overriding Parameters • 34 Overview • 20, 40, 41, 55, 97 Overview a Flow Diagram • 44

P Password Parameters • 36, 112 Predefined Options Parameters • 37, 115 Predefined Parameter • 120 Preface • viii Private Parameter • 121 Process • 121 Process Execution Pane • 90 Process Workspace • 70 Processes Tab Central Pane • 57 Processes Tab Navigation Panel • 57 Processes Tab Parameters Browser • 58 Promoting Published Process • 75 Public Parameter • 121 Publishing Processes • 73, 74

Q Quantifying Server Instances • 81 Quitting Nolio Automation Center • 9

User's Guide Index


R Recent Activity • 84 Removing Agents from an Agent Groups • 107 Removing an Agent from the Agents List • 105 Removing an Agent Group • 106 Resizing the Flow Diagram • 44 Revealing and Hiding the Navigation Panel • 5, 12 Revealing and Hiding the Parameters Browser • 12 Reverting Actions • 26 Reverting an Overridden Process Parameter • 34 Running a Process • 2, 102

S Sample Flow • 53 Saving Changes • 6 Schedules • 84, 85 Searching for Items • 6, 13 Sequencing Operations Between Different Servers •

73 Sequencing Process Steps • 72 Server Definition Operations • 102 Server Type • 121 Setting a New Notification • 88 Setting a New Schedule • 85 Setting Required Input Values • 102 Setting Step Transition Conditions • 47, 48, 51 Setting Up Processes • 11 Specifying Which Server to Wait For • 73 Status Bar • 4, 6 Step • 121 Step-related Icons and Symbols • 48 String Parameters • 36, 111 Switching the Current User • 8

T Technical Support • viii Testing Actions • 37 Testing Flows • 54

U Unpublishing Published Processes • 75 Using Component Categories • 21 Using Nolio Automation Center • 4 Using Parameters Folders • 30 Using Process Categories • 66 Using the Components Tab • 13 Using the Processes Screen • 11, 58 Using the Processes Tab • 56 Using the Run Environment Screen • 2, 76

V Viewing a Management Report • 101 Viewing a Process Run • 93, 104 Viewing Activity Information • 83 Viewing an Agent Execution Log • 96 Viewing an Audit Report • 100 Viewing an Environment • 81 Viewing and Editing Actions • 25, 44, 52 Viewing Flows • 44 Viewing Published Processes • 74 Viewing Reports • 100 Viewing the Events Log • 95, 104 Viewing the Process Run • 100 Viewing the Process Run Progress • 104 Viewing the Process Summary • 94, 104

W Working with Actions • 2, 21, 53 Working with Applications and Components • 15 Working with Architectures • 61 Working with Flows • 41 Working with Processes • 2, 66

Date post:	03-Mar-2015
Category:	Documents
Upload:	jim-blair
View:	343 times
Download:	4 times