Front cover

Draft Document for Review June 22, 2009 4:20 pm SG24-7763-00

Certification Study Guide

Series: Foundations of Tivoli
Process Automation Engine
Helps you achieve Foundations of Tivoli
Process Automation Engine certification

Explains the certification path and

prerequisites

Introduces sample test

questions

Vasfi Gucer
Anantaram Kandukuri
Caio Elias Saad
Dario Sierra
Jonathan Baffa
Julio Madeira
Maamar Ferkoun
Marcel Laurenz

[Link]/redbooks
Draft Document for Review June 16, 2009 12:58 pm [Link]

International Technical Support Organization

Certification Study Guide Series: Foundations of

Tivoli Process Automation Engine

April 2009

SG24-7763-00
[Link] Draft Document for Review June 16, 2009 12:58 pm

Note: Before using this information and the product it supports, read the information in
“Notices” on page xi.

First Edition (April 2009)

This edition applies to Foundations of Tivoli Process Automation Engine Version 7.1.

This document created or updated on June 16, 2009.

© Copyright International Business Machines Corporation 2009. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
Draft Document for Review June 22, 2009 3:02 pm [Link]

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
The team that wrote this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Become a published author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Chapter 1. Certification overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.1 IBM Professional Certification Program . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1 Benefits of certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.2 Tivoli Software Professional Certification . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Test 017: Foundations of Tivoli process automation engine . . . . . . . . . . . . 7
1.2.1 How to receive your 15% discount when taking the test . . . . . . . . . . . 7
1.3 Recommended resources for study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.1 Courses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2. Prerequisites and installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.1 Tivoli process automation engine overview. . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3 Typical deployment environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3.1 Simple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.3.2 Custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 Installation example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4.1 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.4.2 Middleware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.4.3 Solution description and assumptions. . . . . . . . . . . . . . . . . . . . . . . . 16
2.4.4 Middleware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4.5 Tivoli Asset Management for IT 7.1 installation . . . . . . . . . . . . . . . . 21

Chapter 3. Platform Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.1 Working with domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1.1 SYNONYM domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1.2 ALN domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1.3 NUMERIC domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.1.4 NUMERIC RANGE domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.1.5 TABLE domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

© Copyright IBM Corp. 2009. All rights reserved. iii

[Link] Draft Document for Review June 22, 2009 3:02 pm

3.1.6 CROSSOVER domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.2 Configure the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2.1 Creating or modifying an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3 Organizations and sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.1 Working with organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.3.2 Delete an organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.3.3 Working with sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.4 Working with locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.5 Working with the Calendars application . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.6 Working with Classifications application . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.7 Working with E-Mail Listener. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.8 Working with cron tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.9 Working with communication templates . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.10 Working with escalations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.10.1 Maintaining the Escalation application . . . . . . . . . . . . . . . . . . . . . . 46
3.10.2 Escalation components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.10.3 Working with escalation points . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.11 Working with Workflow Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.11.1 Creating workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.12 Workflow Administration application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.12.1 Conditional Expression Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.12.2 Conditional Expression Manager Builder . . . . . . . . . . . . . . . . . . . . 59
3.13 Platform configuration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 4. Financial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4.1 Introduction to Financial configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.2 Currency codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.3 Exchange rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.4 Chart of accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.1 General Ledger Account (GL Account) . . . . . . . . . . . . . . . . . . . . . . . 71
4.4.2 Financial Periods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.5 Cost management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 5. Security Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.1 Security profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.1.1 Security Groups application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.1.2 Adding security groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
5.1.3 The Users application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5.1.4 Start Centers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.1.5 Security group types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.2 Setting up security users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.2.1 Default insert site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.2.2 User statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

iv Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:02 pm [Link]

5.2.3 Managing users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

5.3 Setting up authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.3.1 LDAP authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.3.2 Native authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.3.3 Application server authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.4 Conditional security overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.4.1 Conditional Expression Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Chapter 6. Migration Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

6.1 Integration Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.2 Basic integration configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
6.2.1 Object structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6.2.2 Publish channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.2.3 Invocation channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
6.2.4 Enterprise services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
6.2.5 External systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6.2.6 End Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6.2.7 Importing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
6.2.8 Integration Framework summary . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.3 Migration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
6.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.3.2 Migration Manager concepts and components . . . . . . . . . . . . . . . . 128
6.3.3 Migration objects and migration groups . . . . . . . . . . . . . . . . . . . . . 130
6.3.4 Compiled sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
6.3.5 Migration Manager applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
6.3.6 Migration planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
6.3.7 Migration flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
6.3.8 Migration Manager summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Chapter 7. Start Center configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

7.1 Start Center templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7.1.1 Start Center permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7.1.2 Creating a new Start Center template . . . . . . . . . . . . . . . . . . . . . . . 141
7.1.3 Modifying a portlet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.1.4 Modifying an existing Start Center template . . . . . . . . . . . . . . . . . . 144
7.1.5 Associating a Start Center template to a security group . . . . . . . . . 145
7.2 Key Performance Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.2.1 Creating a Key Performance Indicator . . . . . . . . . . . . . . . . . . . . . . 146
7.2.2 KPI Crontask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Chapter 8. Work management configuration and administration. . . . . . 149

8.1 Work order settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
8.1.1 Organizations application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
8.1.2 Start Center setup for work management . . . . . . . . . . . . . . . . . . . . 155

Contents v
[Link] Draft Document for Review June 22, 2009 3:02 pm

8.2 Setting up job plan templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

8.2.1 Job plan concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
8.3 Work Order module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
8.3.1 Work Order applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
8.3.2 Creating work orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8.4 Work management capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8.4.1 Nested job plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8.4.2 Job plan template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
8.4.3 Work management status flow control . . . . . . . . . . . . . . . . . . . . . . 161

Chapter 9. Reporting configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

9.1 Report administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
9.1.1 Generating the Requests pages . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9.1.2 Adding a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
9.2 Report configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
9.3 Running reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
9.3.1 To schedule a report and send with e-mail . . . . . . . . . . . . . . . . . . . 172
9.3.2 To view and edit scheduled reports . . . . . . . . . . . . . . . . . . . . . . . . 173

Appendix A. Sample certification test questions. . . . . . . . . . . . . . . . . . . 175

Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Answers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
How to get Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

vi Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:02 pm [Link]

Figures

2-1 Tivoli process automation integrated portfolio. . . . . . . . . . . . . . . . . . . . . . 11

2-2 Simple deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2-3 Custom deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2-4 Workspace directory on Computer 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2-5 Features selection on Computer 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2-6 Workspace directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2-7 Workspace local directory on Computer 2 . . . . . . . . . . . . . . . . . . . . . . . . 20
2-8 Features selection on Computer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2-9 Import Middleware Configuration Information . . . . . . . . . . . . . . . . . . . . . . 22
2-10 Database server configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2-11 [Link] file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2-12 DB2 database information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2-13 DB2 tablespace information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2-14 WebSphere remote access authorization screen . . . . . . . . . . . . . . . . . . 25
2-15 WebSphere deployment manager configuration screen . . . . . . . . . . . . . 26
2-16 WebSphere application Server configuration screen . . . . . . . . . . . . . . . 27
3-1 New object screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3-2 Autonumbering Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3-3 New organization screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3-4 Add site screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3-5 Calendars application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3-6 Classification with new attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3-7 E-mail Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3-8 Cron Task Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3-9 Communication Template - Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3-10 Escalation Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3-11 Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3-12 Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3-13 Workflow Designer - Canvas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3-14 Workflow Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3-15 Conditional Expression Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3-16 Error Message (Conditional Expression Manager) . . . . . . . . . . . . . . . . . 61
3-17 Platform Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3-18 Migration Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4-1 Financial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4-2 Creating a currency code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4-3 Exchange Rates main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4-4 Setting up GL Account Configuration.. . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

© Copyright IBM Corp. 2009. All rights reserved. vii

[Link] Draft Document for Review June 22, 2009 3:02 pm

4-5 GL Account Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

4-6 Adding a GL Account into an Organization . . . . . . . . . . . . . . . . . . . . . . . . 73
4-7 Financial Period main screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4-8 Main fields of the Cost Management. application . . . . . . . . . . . . . . . . . . . 75
4-9 Cost Line per each Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5-1 Security Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
5-2 Security Groups list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
5-3 Creating a new Security Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
5-4 Start Center template selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
5-5 Independent of Other Groups selection . . . . . . . . . . . . . . . . . . . . . . . . . . 82
5-6 the Sites tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
5-7 Applications tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
5-8 The Storeroom tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
5-9 The Labor tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5-10 The GL Components tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
5-11 Limits and Tolerances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
5-12 Data Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
5-13 Select Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5-14 Adding users to security groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5-15 Users application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5-16 Synonym Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5-17 Users list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5-18 Assignment to security groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5-19 Security Profile tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5-20 Set Security Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5-21 Set Security Profile options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5-22 Records selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5-23 Assets list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5-24 Conditional Expression Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5-25 Conditional UI for security groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5-26 Conditional expression list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5-27 Signature option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5-28 Security Groups for SIGOPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5-29 Sigoption for Asset tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
6-1 Integration Framework overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
6-2 Integration module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
6-3 Publish channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
6-4 Invocation channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
6-5 Object structure application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
6-6 Migration groups application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
6-7 Content of a migration group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
6-8 Types of packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
6-9 Migration Manager application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

viii Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:02 pm [Link]

6-10 Migration process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

6-11 Migration task flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
7-1 No Start Center to display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
7-2 Layout and Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
7-3 Start Center Portlet Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
7-4 Start Center Portlet Ordering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
7-5 Start Center Edit Portlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7-6 Result Set Setup Color Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7-7 Start Center Modify Existing Template . . . . . . . . . . . . . . . . . . . . . . . . . . 144
7-8 Start Center Modify a Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
7-9 Start Center Security Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
7-10 Multiple Start Center Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
7-11 Start Center Display Settings Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
7-12 Display Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7-13 New KPI Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7-14 Sample KPI Graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
7-15 KPI Cron Task Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
8-1 Work order options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
8-2 Work Type dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8-3 Edit rules dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8-4 Other organization options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
8-5 Site Options dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
8-6 Autonumber setup menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
8-7 Site level autonumber dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
8-8 Save query menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
9-1 Report Administration option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9-2 Generate Request Page notification box . . . . . . . . . . . . . . . . . . . . . . . . 166
9-3 Adding a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
9-4 Report configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
9-5 Report Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
9-6 Select Action Run Reports option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
9-7 Selecting a Report to Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
9-8 Asset Lists report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Figures ix
[Link] Draft Document for Review June 22, 2009 3:02 pm

x Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 16, 2009 12:58 pm [Link]

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.

This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.

© Copyright IBM Corp. 2009. All rights reserved. xi

[Link] Draft Document for Review June 16, 2009 12:58 pm

Trademarks
IBM, the IBM logo, and [Link] are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. These and other IBM trademarked
terms are marked on their first occurrence in this information with the appropriate symbol (® or ™),
indicating US registered or common law trademarks owned by IBM at the time this information was
published. Such trademarks may also be registered or common law trademarks in other countries. A current
list of IBM trademarks is available on the Web at [Link]

The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:

DB2® Lotus® Redbooks (logo) ®

Enterprise Asset Management® Maximo® Tivoli®
IBM® Redbooks® WebSphere®

The following terms are trademarks of other companies:

ITIL is a registered trademark, and a registered community trademark of the Office of Government
Commerce, and is registered in the U.S. Patent and Trademark Office.

Snapshot, and the NetApp logo are trademarks or registered trademarks of NetApp, Inc. in the U.S. and
other countries.

Oracle, JD Edwards, PeopleSoft, Siebel, and TopLink are registered trademarks of Oracle Corporation
and/or its affiliates.

SAP, and SAP logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries.

J2EE, Java, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States,
other countries, or both.

Active Directory, Expression, Microsoft, Windows, and the Windows logo are trademarks of Microsoft
Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

xii Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:45 am [Link]

Preface

This IBM® Redbooks® publication is a study guide for Test 000-017:

Foundations of Tivoli® Process Automation Engine and is aimed at individuals
who want to get an IBM Professional Certification on Tivoli Process Automation
Engine.

The Foundations of Tivoli Process Automation Engine certification exam, offered

through the Professional Certification Program from IBM, is designed to validate
the skills required of technical professionals who works in the implementation
and configuration of Tivoli's process automation engine. Note that this test is a
prerequisite for several other certifications, such as IBM Certified Deployment
Professional - Tivoli Asset Management for IT V7.1.

This book provides a combination of theory and practical experience needed for
a general understanding of the subject matter. It also provides sample questions
that will help in the evaluation of personal progress and provide familiarity with
the types of questions that you will encounter in the exam.

This publication does not replace practical experience, nor is it designed to be a

stand-alone guide for any subject. Instead, it is an effective tool that, when
combined with educational activities and experience, can be an extremely useful
preparation guide for the exam.

For your convenience, we structure the chapters based on the sections of the
Test 000-017: Foundations of Tivoli Process Automation Engine, such as
Prerequisites and Installation, Platform Configuration and so on, so studying
each chapter will help you prepare for one section of the exam.

© Copyright IBM Corp. 2009. All rights reserved. xiii

[Link] Draft Document for Review June 18, 2009 10:45 am

The team that wrote this book

This book was produced by a team of specialists from around the world working
at the International Technical Support Organization, Raleigh Center.

Vasfi Gucer is a Project Leader at the International

Technical Support Organization, Austin Center. He has
been with the ITSO since January 1999. He has more
than 12 years of experience in the areas of systems
management, networking hardware, and software on
mainframe and distributed platforms. He has worked on
various Tivoli® client projects as a systems architect in
the U.S. He writes extensively and teaches IBM classes
worldwide on Tivoli software. Vasfi is also an IBM
Certified Senior IT Specialist, PMP and ITIL® Expert

Anantaram Kandukuri is a Maximo - Sr. Delivery

Manager at Envision Enterprise Solutions Pvt. Ltd,
Hyderabad, India. He has 12 years of production
experience in process industry and more than 13 years
of IT experience in software development,
customization and implementation of ERP, EAI, and
J2EE™ applications. He has wide experience on
Maximo Solutions - 5.1, 5.2,6.2 and 7.1. versions of
Maximo.

Caio Elias Saad is a Software Engineer at IBM Brazil

Software Laboratory, based in São Paulo, Brazil. He
has over 5 years of experience in Java™ Enterprise
development and over 2 years working on IBM Maximo
Asset Management development. The main projects he
has being involved were Maximo Core EAM
development v6.x, v7.x and V8.x and huge Maximo
V7.x implementations using Integration Framework and
other products like Maximo for Oil and Gas, and
Calibration industry solutions.

Dario Sierra is a System Management Integration

coordinator at IBM Argentina. He has worked at IBM for
more than 9 years. He has 8 years of experience
working in Information Technology and Tivoli products
focusing on Configuration manager, TPM and TAMIT.
He holds a degree in Systems from UTN Argentina and
he is ITIL certified

xiv Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:45 am [Link]

Jonathan Baffa is the Director of Information

Technology for SaS, a long term Maximo and IBM
Business Partner. Jonathan is an IBM Certified
Advanced Deployment Professional, ITIL Certified, and
has over 4 years experience with Maximo and its related
products. Jonathan provides strategic direction for
corporate IT and establishes best practices for hosted
and non-hosted solutions as well as their technical
engagements and deployments.

Julio Madeira is a Software Engineer from IBM for the

last 2 years and has 15 years experience with IT. He
has a Bachelor Degree in Computer Sciences by
Catholic University of Santos and also a
Post-Graduation in IT Management by Fundação
Getúlio Vargas in Brazil.

Maamar Ferkoun is a Senior Product Professional with

the IBM worldwide Software Advanced Technology
group. He is based in IBM China and Hong Kong and
has over 20 years experience in the IT industry among
which over 10 years were with IBM. He holds a degree
in computer science, an EXIN ITIL Manager, and a
COBIT certification. Maamar began his career in IBM as
a software field engineer engaged across the Asia
Pacific region. His area of expertise covers the service
management product portfolio and best practices.

Marcel Laurenz is a proven Senior IT Consultant and

Director of LAURENZ-IT, based in northern Germany.
Marcel has more than 10 years experience in leading
international projects and teams, specifically in area of
operations and service management. He is a certified
IBM Lotus®, WebSphere®, Tivoli, Microsoft® and ITIL
expert and holds a degree in Sport Science and
Economy. He is an entrepreneur building high
performance teams.

Thanks to the following people for their contributions to this project:

Wade Wallace
International Technical Support Organization, Austin Center

Preface xv
[Link] Draft Document for Review June 18, 2009 10:45 am

Tamikia Barrow
International Technical Support Organization, Raleigh Center

Kristin Wall Gibson, Emma Jacobs

IBM USA

Become a published author

Join us for a two- to six-week residency program! Help write a book dealing with
specific products or solutions, while getting hands-on experience with
leading-edge technologies. You will have the opportunity to team with IBM
technical professionals, Business Partners, and Clients.

Your efforts will help increase product acceptance and customer satisfaction. As
a bonus, you will develop a network of contacts in IBM development labs, and
increase your productivity and marketability.

Find out more about the residency program, browse the residency index, and
apply online at:
[Link]/redbooks/[Link]

Comments welcome
Your comments are important to us!

We want our books to be as helpful as possible. Send us your comments about

this book or other IBM Redbooks publications in one of the following ways:
 Use the online Contact us review Redbooks form found at:
[Link]/redbooks
 Send your comments in an e-mail to:
redbooks@[Link]
 Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400

xvi Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:07 pm [Link]

Chapter 1. Certification overview

This chapter provides an overview of the skill required to become an IBM
certified Advanced Technical [Link] designed the following sections to
provide a comprehensive review of specific topics that provide essential
information for obtaining the certification:
 “IBM Professional Certification Program” on page 2
 “Test 017: Foundations of Tivoli process automation engine” on page 7
 “Recommended resources for study” on page 8

© Copyright IBM Corp. 2009. All rights reserved. 1

[Link] Draft Document for Review June 22, 2009 3:07 pm

1.1 IBM Professional Certification Program

Having the right skills for the job is critical in the growing global marketplace. IBM
Professional Certification, designed to validate skill and proficiency in the latest
IBM solution and product technology, can help provide that competitive edge.
The IBM Professional Certification Program Web site is available at:
[Link]

The IBM Professional Certification Program offers a business solution for skilled
technical professionals seeking to demonstrate their expertise to the world.

In addition to demonstrating your skill and proficiency in the latest IBM

technology and solutions, professional certification can help you excel at your job
by giving you and your employer confidence that your skills have been tested.
You can deliver higher levels of service and technical expertise than non-certified
employees and move on a faster career track. Professional certification puts your
career in your control.

The certification requirements are difficult but not overwhelming. Certification is a

rigorous process that differentiates you from everyone else.

The mission of the IBM Professional Certification Program is to:

 Provide a reliable, valid, and fair method of assessing skills and knowledge.
 Provide IBM with a method of building and validating the skills of individuals
and organizations.
 Develop a loyal community of highly skilled certified professionals who
recommend, sell, service, support, and use IBM products and solutions.

The IBM Professional Certification Program has developed certification role

names to guide you in your professional development. The certification role
names include IBM Certified Specialist, IBM Certified Solutions/Systems Expert,
and IBM Certified Advanced Technical Expert for technical professionals who
sell, service, and support IBM solutions. For technical professionals in
application development, the certification roles include IBM Certified Developer
Associate and IBM Certified Developer. An IBM Certified Instructor certifies the
professional instructor.

The IBM Professional Certification Program provides a structured program

leading to an internationally recognized qualification. The program is designed
for flexibility by enabling you to select your role, prepare for and take tests at your
own pace, and, in some cases, select from a choice of elective tests best suited
to your abilities and needs. Some roles also offer a shortcut by offering credit for
a certification obtained in other industry certification programs.

2 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:07 pm [Link]

You can be a network administrator, systems integrator, network integrator,

solution architect, solution developer, value-added reseller, technical coordinator,
sales representative, or educational trainer. Regardless of your role, you can
start charting your course through the IBM Professional Certification Program
today.

1.1.1 Benefits of certification

Certification is a tool to help objectively measure the performance of a
professional on a given job at a defined skill level. Therefore, it is beneficial for
individuals who want to validate their own skills and performance levels, those of
their employees, or both. For optimum benefit, the certification tests must reflect
the critical tasks required for a job, the skill levels of each task, and the frequency
a task must be performed. IBM prides itself in designing comprehensive,
documented processes that ensure that IBM certification tests remain relevant to
the work environment of potential certification candidates.

In addition to assessing job skills and performance levels, professional

certification can also provide such benefits as the following:
 For employees:
– Promotes recognition as an IBM certified professional
– Creates advantages in interviews
– Assists in salary increases, corporate advancement, or both
– Increases self-esteem
– Provides continuing professional benefits
 For employers:
– Measures the effectiveness of training
– Reduces course redundancy and unnecessary expenses
– Provides objective benchmarks for validating skills
– Facilitates long-range planning
– Helps to manage professional development
– Aids as a hiring tool
– Contributes to competitive advantage
– Increases productivity
– Increases morale and loyalty
 For IBM Business Partners and consultants:
– Provides independent validation of technical skills
– Creates competitive advantage and business opportunities
– Enhances prestige of the team
– Contributes to meeting IBM requirements for various IBM Business
Partner programs

Chapter 1. Certification overview 3

[Link] Draft Document for Review June 22, 2009 3:07 pm

Specific benefits can vary by country (or region) and role. In general, after you
become certified, you should receive the following benefits:
 Industry recognition
Certification may accelerate your career potential by validating your
professional competency and increasing your ability to provide solid, capable
technical support.
 Program credentials
As a certified professional, you receive through e-mail your certificate of
completion and the certification mark associated with your role for use in
advertisements and business literature. You can also request a hardcopy
certificate, which includes a wallet-size certificate.
IBM Professional Certification acknowledges the individual as a technical
professional. The certification mark is for the exclusive use of the certified
individual.
 Ongoing technical vitality
IBM certified professionals are included in mailings from the IBM Professional
Certification Program.

1.1.2 Tivoli Software Professional Certification

The IBM Tivoli Professional Certification program offers certification testing that
sets the standard for qualified product consultants, administrators, architects,
and partners.

The program also offers an internationally recognized qualification for technical

professionals seeking to apply their expertise in today’s complex business
environment. The program is designed for those who implement, buy, sell,
service, and support IBM Tivoli solutions and want to deliver higher levels of
service and technical expertise.

Whether you are a Tivoli client, partner, or technical professional wanting to put
your career on the fast track, you can start on the road to becoming a Tivoli
Certified Professional today.

Benefits of Tivoli certification

This section describes the benefits of IBM Tivoli certification. Tivoli certification
provides the following benefits:
 For the individual:
– IBM Certified certificate and use of logos on business cards

4 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:07 pm [Link]

Note: Certificates are sent by e-mail. However, a paper copy of the

certificate along with a laminated wallet card can also be requested by
sending an e-mail to [Link]

– Recognition of your technical skills by your peers and management

– Enhanced career opportunities
– Focus for your professional development
 For the IBM Business Partner:
– Confidence in the skills of your employees
– Enhanced partnership benefits from the IBM Business Partner program
– Ability to bill your employees’ services at higher rates
– Strengthens proposals to customers
– Deepens technical skills available to prospective customers
 For the customer:
– Confidence in the services professionals handling your implementation
– Ease of hiring competent employees to manage your Tivoli environment
– Enhanced return on investment (ROI) through more thorough integration
with Tivoli and third-party products
– Ease of selecting a Tivoli Business Partner that meets your specific needs

Certification checklist
This section provides a certification checklist. Follow these steps to pursue
certification:
1. Select the certification that you want to pursue.
2. Determine which test or tests are required by reading the certification role
description.
3. Prepare for the test, using the following resources provided:
– Test objectives
– Recommended educational resources
– Sample assessment test
– Other reference materials
– List of opportunities for gaining experience

Note: These resources are available from each certification description

page, as well as from the test information page.

Chapter 1. Certification overview 5

[Link] Draft Document for Review June 22, 2009 3:07 pm

4. Register to take a test by contacting one of our worldwide testing vendors:

– Thomson Prometric
– Pearson Virtual University Enterprises (VUE)

Note: When providing your name and address to the testing vendor, be
sure to specify your name exactly as you want it to appear on your
certificate.

5. Take the test. Be sure to keep the Examination Score Report provided upon
test completion as your record of taking the test.

Note: After taking a test, your test results and demographic data (including
name, address, e-mail, and phone number) are sent from the testing
vendor to IBM for processing (allow two to three days for transmittal and
processing). After all the tests required for a certification are passed and
received by IBM, your certificate is issued.

6. Repeat steps 3 on page 5 through 5 until all required tests are successfully
completed for the desired certification role. If you must meet additional
requirements (such as an “other vendor” certification or exam), follow the
instructions on the certification description page to submit these requirements
to IBM.
7. After you complete your certification requirements, you are sent an e-mail
asking you to accept the terms of the IBM Certification Agreement before
receiving the certificate.
8. Upon acceptance of the terms of the IBM Certification Agreement, an e-mail
is sent containing the following electronic deliverables:
– A Certification certificate in PDF format, which can be printed in either
color or black and white
– A set of graphic files of the IBM Professional Certification mark associated
with the certification achieved
– Guidelines for the use of the IBM Professional Certification mark
9. To avoid unnecessary delay in receiving your certificate, ensure that your
current e-mail is on file by maintaining an up-to-date profile. If you do not have
an e-mail address on file, your certificate is sent through postal mail.

After you receive a certificate by e-mail, you can also contact IBM at
[Link] to request that a hardcopy certificate be sent by
postal mail.

6 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:07 pm [Link]

Note: IBM reserves the right to change or delete any portion of the program,
including the terms and conditions of the IBM Certification Agreement, at any
time without notice. Some certification roles offered through the IBM
Professional Certification Program require recertification.

1.2 Test 017: Foundations of Tivoli process automation

engine
This section describes the process of obtaining Foundations of Tivoli process
automation engine certification. We can categorize the certification process as
follows:
 Job role description and target audience:
An IBM Certified Deployment Professional - Foundations of Tivoli process
automation engine is a technical professional responsible for planning,
installation, configuration, operations, administration, and maintenance of a
Tivoli process automation engine. This individual is expected to perform these
tasks with limited assistance from peers, product documentation, and support
resources.
 To be certified you must select Test 017: Foundations of Tivoli process
automation engine certification
– Approximate number of questions: 51
– Duration in minutes: 60
– Format: Multiple choice
– Required passing score: 70%
 Test 017 objectives:
For the most updated objectives of the Foundations of Tivoli process
automation engine certification test, refer to the following link:
[Link]

1.2.1 How to receive your 15% discount when taking the test
You can receive a 15% discount on the Foundations of Tivoli process
automation engine certification exam, if taken at any Thomson Prometric
testing center. Just remember to use the code 15T017.

Chapter 1. Certification overview 7

[Link] Draft Document for Review June 22, 2009 3:07 pm

1.3 Recommended resources for study

Courses and publications are offered to help you prepare for the certification
tests. The courses are recommended, but not required, before taking a
certification test. If you want to purchase Web-based training courses or are
unable to locate a Web-based or classroom course at the time and location you
desire, contact one of our delivery management teams at:
 Americas:
[Link]
 EMEA:
[Link]
 AP:
[Link]

Note: Course offerings are continuously being added and updated. If you do
not see the courses listed in your location, contact one of the previously listed
delivery management teams.

1.3.1 Courses
Refer to the following link for a list of courses related to Tivoli process automation
engine:
[Link]

8 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

Chapter 2. Prerequisites and

installation
This chapter provides an overview of IBM Tivoli process automation engine and
the installation steps along with its components. You should consider the
scenarios, topologies, hardware, and software that must be analyzed before
starting the installation.

The following topics are discussed in this chapter:

 “Tivoli process automation engine overview” on page 10
 “Prerequisites” on page 12
 “Typical deployment environments” on page 12
 “Installation example” on page 14

© Copyright IBM Corp. 2009. All rights reserved. 9

[Link] Draft Document for Review June 17, 2009 9:04 am

2.1 Tivoli process automation engine overview

The Tivoli’s process automation engine provides a common foundation to the
Tivoli Service Management products installer

Note: IBM Service Management (ISM) is a comprehensive and integrated

approach for Service Management, integrating technology, information,
processes, and people to deliver service excellence and operational efficiency
and effectiveness for traditional enterprises, service providers, and mid-size
companies.

Tivoli process automation engine provides a user interface, configuration

services, workflows and the common data system needed for IBM Service
Management products and other services. Tivoli process automation engine
records choices you make about your ISM product and configuration parameters
associated with those choices, and then installs and deploys the product based
upon the information you entered.

Tivoli process automation engine, previously known as Tivoli base services, is

provided with Tivoli Maximo Asset Management, Change and Configuration
Manager Database (CCMDB), Tivoli Service Request Manager (SRM) and Tivoli
Asset Management for IT (TAMIT).

Any product that has the Tivoli process automation engine as its foundation can
be installed with any other product that has the Tivoli process automation engine.
The installer will detect that the Tivoli process automation engine is already
installed and just enable the additional applications and features of the product
being installed.

Every product ships with a specific version of the Tivoli process automation
engine. The versions must match up if you are installing more than one product.
 Tivoli Change and Configuration Management Database 7.1

Includes Tivoli process automation engine 7.1

 Tivoli Change and Configuration Management Database 7.1.1

Includes Tivoli process automation engine 7.1.1

 Tivoli Service Request Manager 7.1

Includes Tivoli process automation engine 7.1.1

 Tivoli Asset Management for IT 7.1

10 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

Includes Tivoli process automation engine 7.1.1

 Enterprise Asset Management® and Maximo Asset Management 7.1

Includes Tivoli process automation engine 7.1.1

Once you have installed one of these products, you can install others on top of it.
There is a different install option for each product's launchpad that you must
choose, if you want to install the product on top of another. With this option, the
Tivoli process automation engine will not be reinstalled. The new products
applications will be enabled, as well as the existing applications.

Now we put the Tivoli process automation engine and the Tivoli process
automation engine-based products in the perspective of ISM architecture.
Figure 2-1 shows the Tivoli process automation engine integrated portfolio.

Figure 2-1 Tivoli process automation integrated portfolio

Chapter 2. Prerequisites and installation 11

[Link] Draft Document for Review June 17, 2009 9:04 am

2.2 Prerequisites
Tivoli process automation engine requires multiple software servers that can be
installed on separate, dedicated server machines (for best performance) or the
same physical server (not recommended for production environments). The
different components of the ISM solution environment, called middleware, are as
follows:
 Database: The database serves as the repository for all CI information.
 Application server: Tivoli process automation engine is built using Java 2
Enterprise Edition (J2EE) technology, which requires a commercial
application server, such as IBM WebSphere Application Server.
 HTTP server: A separate, dedicated HTTP server can be configured to work
with the J2EE application server.
 Directory server: A directory server can be configured to work with the ISM
product to maintain lists of users and groups for security purposes.
 Administrative system: The administrative system is not part of the
middleware but is used to deploy the ISM product. After the initial deployment,
the administrative system is used to make updates or changes to the
deployment. This machine has to be a Windows® system.

For specific information about prerequisites of a particular ISM product, refer to

the installation manual of each product.

2.3 Typical deployment environments

There are two installation paths available when installing the Tivoli process
automation engine.

2.3.1 Simple
A simple deployment consists of installing all middleware on one system. You will
not have the option of using existing middleware within your organization. All
middleware used in conjunction with Tivoli process automation engine must be
installed on the system using the Tivoli middleware installer using default values.
The ISM product will be installed using default values provided by the Tivoli
middleware and Tivoli process automation engine installation programs. If you
intend to override default values used by the simple deployment path, you will
have to use the custom deployment path instead.

Figure 2-2 on page 13 shows a simple deployment scenario.

12 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

Figure 2-2 Simple deployment

2.3.2 Custom
A custom deployment typically involves deploying the ISM product across several
systems, some of which probably already host middleware products that you
wish to use with your product deployment. Deploying through the custom
installation path also allows you to modify default installation values. This
deployment option does not require you to spread the ISM product deployment
across several systems. You can enter the name of the local host as the
destination for all the product components that are to be installed using the Tivoli
middleware installer and the Tivoli process automation engine.

Figure 2-3 on page 14 shows a custom deployment scenario.

Chapter 2. Prerequisites and installation 13

[Link] Draft Document for Review June 17, 2009 9:04 am

Figure 2-3 Custom deployment

The Tivoli process automation engine program can automate the configuration of
middleware for use with an ISM product. For example, if you are preparing to
deploy the Tivoli process automation engine and you already have your database
software deployed, and you will reuse this environment, the Tivoli process
automation engine installer will build the schema required.

If you choose not to have the Tivoli process automation engine automatically
configure middleware, configure that piece of middleware manually prior to the
execution of Tivoli process automation engine.

2.4 Installation example

In this section we discuss the installation of the prerequisite middleware and
Tivoli process automation engine on a multiserver topology. Our example is
based on IBM Tivoli Asset Management for IT Version 7.1

2.4.1 Before you begin

There are some steps that you must take before you install middleware or Tivoli
Asset Management for IT, for example disabling the firewall, deleting the TEMP
and TMP user environment variables on Windows systems, Setting the limit, etc.

14 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

2.4.2 Middleware installation

Before you can install the IBM Tivoli Asset Management for IT, there are several
Tivoli Asset Management for IT middleware products that must be deployed. The
Tivoli middleware installer provides an interface for installing and deploying Tivoli
Asset Management for IT middleware
 Database server
 Directory server
 J2EE server

The Tivoli middleware installer deploys software on a single machine. To deploy

Tivoli Asset Management for IT middleware on multiple machines, the Tivoli
middleware installer must be invoked on each machine in the topology
configuration you have chosen.

If you intend to reuse existing Tivoli Asset Management for IT middleware

servers, they must be configured prior to running the Tivoli Asset Management
for IT installation program. You can use the Tivoli Middleware installer to
configure it or you can configure it manually.

For more information about reusing middleware, Tivoli Asset Management for IT
Release 7.1, Installation Guide | IBM WebSphere Application Server at:
[Link]
/[Link]/[Link]

Tivoli middleware installer workspace

The Tivoli middleware installer is designed to record the options you select
during install in a directory referred to as the workspace, and then configure the
components selected as a single deployed application. Once a plan has been
deployed, the Tivoli middleware installer cannot subsequently deploy additional
features and products onto the machine at a later time. The existing plan must
first be completely undeployed through the Tivoli middleware installer before a
different set of features and products can be deployed. The composition and
details of the deployment, as well as any logs generated by the Tivoli middleware
installer process are located in the workspace. By default, the Tivoli middleware
installer workspace is defined as:
 Windows C:\ibm\tivoli\mwi\workspace
 UNIX® /ibm/tivoli/mwi/workspace

The workspace can be defined on a shared resource that is made available to all
the systems that will run the Tivoli middleware installer. Locating the workspace
on a shared resource avoids the need to copy files such as the topology file

Chapter 2. Prerequisites and installation 15

[Link] Draft Document for Review June 17, 2009 9:04 am

manually from one machine to another. The workspace contains the following
items:

Deployment plan
The deployment plan is a collection of installation steps, configuration
parameters for those steps, and target machine information. It is generated
through the Tivoli middleware installer and it resides in the workspace directory.
When deployment steps are changed, the existing deployment plan is deleted
and replaced with the new deployment plan. The deployment plan configuration
files contain information about the deployment plan itself. Whenever a
deployment plan is modified, which includes re-configuring existing deployment
choices, the deployment plan configuration files will be deleted and regenerated
when the deployment plan is redeployed.

Topology file
The topology file is a properties file that describes the configuration parameters
of the Tivoli Asset Management for IT middleware deployment. This file is
created and then updated after every deployment or undeployment. If you have
not defined a workspace that is centrally located and accessible to all the
systems that will be receiving Tivoli Asset Management for IT middleware, this
file will have to be copied to the workspace of each machine where Tivoli Asset
Management for IT middleware is being deployed. The contents of this file can be
used by the Tivoli Asset Management for IT installation program to populate its
panels with meaningful default values. This file is saved in
<workspace>/[Link].

Logs
Log files that contain information about the deployment can be found in the
workspace directory. In addition, log files native to the IBM Tivoli Asset
Management for IT middleware itself are also contained in this directory.

2.4.3 Solution description and assumptions

Our example is based on the following software and hardware components:
 Computer 1: Windows 2003 Server EE. Hostname [Link]

with DB2® Enterprise Server Edition v9.5.1 and Tivoli Directory Server V6.2
 Computer 2: Windows 2003 Server EE. Hostname [Link]

with WebSphere Application Server v6.1.0.19 and other components

16 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

Note: In this example, this computer is a Windows computer so a separate

administrative workstation is not required.

 ISM product: Tivoli Asset Management for IT 7.1

2.4.4 Middleware installation

We'll use the default parameters to install the middleware. For more information
refer to Tivoli Asset Management for IT Release 7.1, Installation Guide | IBM
WebSphere Application Server at:
[Link]
/[Link]/[Link]

Note: WebSphere Application Server must be installed after the directory

server so that you can secure it with the Directory server.

1. Create a middleware workspace in a directory location that is accessible to all

computers in the topology. This is the simplest way to share the installation
data for installed middleware between each computer and the various
installers you will run. We'll create the workspace directory in Computer 2 and
map the network drive from Computer 1.

Note: If you do not use a shared location for the middleware workspace, a
separate [Link] will be saved for each middleware installation
that you perform on each computer. You will need to manually consolidate the
data into a single [Link] file and copy the middleware workspace
to a local directory on each computer in the topology as you perform
installation.

2. On Computer 1, start the Launchpad and run the middleware installer.

3. Select the directory to create the workspace (Figure 2-4 on page 18).

Chapter 2. Prerequisites and installation 17

[Link] Draft Document for Review June 17, 2009 9:04 am

Figure 2-4 Workspace directory on Computer 2

4. Install DB2 and Tivoli Directory Server (Figure 2-5 on page 19).

18 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

Figure 2-5 Features selection on Computer 1

Once you finish the installation note that the workspace directory in Computer 2
has the data of the middleware installation of Computer 1, including the
[Link] file. See Figure 2-6.

Figure 2-6 Workspace directory

5. On Computer 2, start the Launchpad and run the Middleware Installer.

Chapter 2. Prerequisites and installation 19

[Link] Draft Document for Review June 17, 2009 9:04 am

6. Select now the local directory to create the workspace. The installation will
update the workspace including the [Link] file. See Figure 2-7.

Figure 2-7 Workspace local directory on Computer 2

7. Install the WebSphere Application, as shown in Figure 2-8 on page 21.

20 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

Figure 2-8 Features selection on Computer 2

2.4.5 Tivoli Asset Management for IT 7.1 installation

To install Tivoli Asset Management for IT, follow these steps:
1. Login as Administrator on the Tivoli Asset Management for IT administrative
system.
2. Launch the Tivoli Asset Management for IT installation program (Tivoli
process automation engine)
3. Select a language for the installation and click OK.
4. From the Introduction panel, click Next.
5. Select the Import Middleware Configuration Information check box and fill
out the fields, as shown in Figure 2-9 on page 22.

Chapter 2. Prerequisites and installation 21

[Link] Draft Document for Review June 17, 2009 9:04 am

Figure 2-9 Import Middleware Configuration Information

The following are the parameters in this panel:

– Host name: Enter the fully qualified host name of the system where the
Tivoli middleware installer was run.
– User ID: Enter the User ID that was used to run the Tivoli middleware
installer.
– Password: Enter the password of the User ID that was used to run the
Tivoli middleware installer.
– Workspace Location: Enter the location of the topology file that contains
the values entered for the Tivoli middleware installer. This file is found in
the workspace that was defined during the Tivoli Asset Management for IT
middleware installation task. In this example, C:\ibm\tivoli\mwi\workspace.

Important: The minimum level of access required by the installer for

configuring the middleware is Administrator or root.

6. Choose the Deployment Type (Simple or Custom) and click Next.

7. Enter installation location and click Next.
8. Select the Maximo database type as DB2.
9. Enter the Tivoli process automation engine database information as shown in
Figure 2-10 on page 23:
– Host name.

22 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

– Database instance port.

– Database name.
– Database instance.
– Database user ID.
– Database password.
– Confirm password.

Figure 2-10 Database server configuration screen

This information will be placed in the [Link] file, which supplies

database connection parameters for the Tivoli process automation engine. Tivoli
process automation engine is using several other properties files to setup the
system. Figure 2-11 shows an example of the [Link] file.

Figure 2-11 [Link] file

In addition, you can use the [Link] file to specify

datasource information for reporting.

Chapter 2. Prerequisites and installation 23

[Link] Draft Document for Review June 17, 2009 9:04 am

[Link] to automate database creation and click Next.

[Link] the database information and click Next.
– Remote access user id
– Password
– Confirm password.
[Link] the following DB2 administration data and click Next:
– Database software installation directory.
– Instance administrator user ID.
– Instance administrator password,
– Confirm password.
– Windows service user ID.
– Windows service password.
– Confirm password. (Figure 2-12)

Figure 2-12 DB2 database information screen

[Link] in the DB2 tablespace data and click Next:

– Data tablespace name.
– Data tablespace size.
– Temporary tablespace name.
– Temporary tablespace size.

24 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

– Index tablespace name.

– Index tablespace size.(Figure 2-13)

Figure 2-13 DB2 tablespace information screen

[Link] IBM WebSphere application server as the J2EE Application Server.

[Link] in the following WebSphere connectivity data and click Next:
– Deployment manager host name.
– Deployment manager SOAP port (8879).
[Link] the Deployment manager operating system user id, operating system
password, confirm the password and click Next. See Figure 2-14.

Figure 2-14 WebSphere remote access authorization screen

Chapter 2. Prerequisites and installation 25

[Link] Draft Document for Review June 17, 2009 9:04 am

[Link] to automate the creation of WebSphere configuration and click Next.

[Link] in the following WebSphere administrative data (See Figure 2-15) and
click Next:
– WebSphere Application Server installation directory.
– Websphere administrative User ID.
– WebSphere administrative user password.
– Confirm password.
– Profile name.

Figure 2-15 WebSphere deployment manager configuration screen

[Link] in the WebSphere Configuration data, as shown in Figure 2-16 on

page 27 and click Next.
– Web server port.
– Web server name.
– Node name.
– Cluster name.

26 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:04 am [Link]

Figure 2-16 WebSphere application Server configuration screen

[Link] Configure J2EE application security check box and click Next.

Note: This modify the J2EE application so that authentication will be handled
by an external source such as IBM Tivoli Directory Server or Microsoft Active
Directory®.

[Link] whether your environment is using the IBM default schema and
whether the installer should create the required users and click Next.
[Link] JMS Data Source name, Choose Do not persist JMS messages and
click Next.

Note: A JMS messaging engine must be configured with a persistent data

store in order to ensure that any data sent to the Tivoli process automation
engine's Integration Framework for retrieval of financial data into the Tivoli
process automation engine can survive restarts and failures.

[Link] Run Configuration Step now and click Next.

[Link] where to create the product icons and whether to create icons for all
users and click Next.
[Link] Next in the Input Summary window.
[Link] Install in the Pre-Installation Summary window.

For information about other installation options Tivoli Asset Management for IT
Release 7.1, Installation Guide | IBM WebSphere Application Server at:

Chapter 2. Prerequisites and installation 27

[Link] Draft Document for Review June 17, 2009 9:04 am

[Link]
/[Link]/[Link]

28 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

Chapter 3. Platform Configuration

This chapter provides details about the Platform Configuration application. This
application has been developed to collect all platform configuration options in a
single place. After installing the ISM product, you have to configure various
options to meet your business meets. The following chapter will help you to
understand the options. Besides the basic setup, you will find options to
configure your database, tailor workflows to your needs, and define escalations
where needed.

This chapter has the following sections:

 “Working with domains” on page 31
 “Configure the database” on page 33
 “Organizations and sites” on page 35
 “Working with locations” on page 38
 “Working with the Calendars application” on page 38
 “Working with Classifications application” on page 39
 “Working with E-Mail Listener” on page 41
 “Working with cron tasks” on page 43
 “Working with communication templates” on page 44
 “Working with escalations” on page 46
 “Working with Workflow Designer” on page 51

© Copyright IBM Corp. 2009. All rights reserved. 29

[Link] Draft Document for Review June 22, 2009 3:00 pm

 “Workflow Administration application” on page 57

 “Platform configuration summary” on page 61

30 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

3.1 Working with domains

Some fields in the system are associated with select value lists from which users
choose an appropriate value. These lists of defined values are known as
domains (sometimes referred to as value lists). The system uses many domains
in its applications. Also, domains is one of the two possible ways to validate field
values (the other one is Java classes). As an administrator, you use the Domains
application to add, view, modify, or delete domains to fit with your business
practices.

The system uses the following six kinds of domains:

 SYNONYM
 ALN
 NUMERIC
 NUMERIC RANGE
 TABLE
 CROSSOVER

3.1.1 SYNONYM domains

These are special, reserved domains in the system. You cannot add new
SYNONYM domains or delete existing ones. You can add new synonym values.
An example of a SYNONYM domain is work order status. The system has
several values to reflect status: APPR (Approved), CAN (Canceled), CLOSE
(Closed), COMP (Completed), WAPPR (Waiting on Approval), and others. Each
work order status has an internal value, used by the system in its business rules,
and a value that users see and choose from. You cannot add a new internal
value. You can add a synonym, the value presented to the user. For example,
suppose your company procedure requires two people to approve a work order.
You could add synonym values for the internal WAPPR value. You could then
present two different values to the user, for example, WAPPRMAN and
WAPPRVP, to represent approvals at the manager and vice president level.

3.1.2 ALN domains

ALN domains are a simple list of values using one of the alphanumeric data
types.

Chapter 3. Platform Configuration 31

[Link] Draft Document for Review June 22, 2009 3:00 pm

3.1.3 NUMERIC domains

Numeric domains are a simple list of values using one of the numeric data types.

3.1.4 NUMERIC RANGE domains

Numeric Range domains use one of the numeric data types, but which you
specify a range rather than specific values.

You can specify the following two kinds of ranges:

– discrete – a range with a defined interval between values, for example, a
range from 0 to 10, with valid values 0, 2, 4, 6, 8, and 10. The interval in
this example is 2.
– continuous – a range within which any value that satisfies the data type is
valid. For example, in a range of 1 to 6 with a decimal data type and scale
of 2, values such as 1, 1.03, 2.14, 3, 4.73, 5.2, and 6 are all valid. The
interval in this example is null (no value in the Interval field).

Note: You cannot create a lookup for NUMERIC RANGE domains.

3.1.5 TABLE domains

Table domains are a dynamic set of values based on the values of another
[Link] use the TABLE Domain dialog box to add a new domain that draws its
values directly from a column in the database. This is in effect a dynamic value
list because the values it draws from the database may change. It is not a list of
static values that you create.

In this kind of domains you can optionally Specify a group value and a key value
to select an error message to display when domain validation fails.
– In the Error Message Group field, specify the group value of the error
message.
– In the Error Message Key field, specify the key value of the error message.

3.1.6 CROSSOVER domains

Crossover domains are a special type of table domain in which the system brings
back another value (or values) from the specified record.

32 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

3.2 Configure the database

You use the Database Configuration application to create or modify the objects
and attributes in the database used by applications. An object is a self-contained
software entity that consists of both data and functions to manipulate data. Every
application is associated with an object.

When you use the Database Configuration application, you interact at the
business object level. Internally, the application determines the actions to take on
the tables to support the needs of business objects.

A database table stores several objects, and each object has different business
rules. For example, the TICKET table defines Incident, Problem, and Ticket
business objects.

3.2.1 Creating or modifying an object

Use any tab of the Database Configuration application to create or modify an
object. An object can be either a view or a table. Figure 3-1 shows the object
form:

Figure 3-1 New object screen

To create a new object, perform the following:

1. In the Database Configuration application, click New Object.

Chapter 3. Platform Configuration 33

[Link] Draft Document for Review June 22, 2009 3:00 pm

2. Type a name in the Object field.

The Entity field shows the value that you typed in the Object field and
becomes the name of the view on the database.
3. Type a description for the new object.
4. To use Views, specify a value in the Extends Object field.
5. After you specify a value, the View? check box is selected. If the view joins
two tables, you can type the name for the second table in the Join to Object
field.
6. Complete the appropriate fields:
– Level: Specify a value.
– Main Object?: To make the object a main object for Workflow, select this
check box
– Persistent?: If the object is persistent, three attributes are created: ID,
description, and rowstamp (if selected). If the object is non-persistent,
nothing is added for attributes, but you cannot configure the database
without creating at least one attribute for the object.
– Storage Partition: If applicable to your database, click Detail and select a
storage partition for the object
– Optional: Provide additional details.
For more information about objects options see the System Administrator
Guide.
7. Click Save Object

Optionally you can also configure the Autnumbering feature in the attributes area.
To setup the configuration, you have to select the Can Number? field, the
Autonumber field and the you have to set the Default value to
&AUTONUMBER& as shown in Figure 3-2.

Figure 3-2 Autonumbering Attribute

34 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

3.3 Organizations and sites

Organizations and sites are logical divisions of a company determined by what
types of operations are performed at different locations, and what data can be
shared among them.

An organization is a major division of a company that contains one or more sites.

Organizations and sites are logical divisions of a company determined by what

types of operations are performed at different locations, and what data can be
shared among them.

3.3.1 Working with organizations

You use the organizations application to set up the organizations and sites to use
with the system. You have to consider some tips to set up organizations:

Create an organization
Before you can create the first organization you must complete the following
tasks:
 Create at least one currency code. To do this, use the Currency Codes
application.
 Create at least one item set and one company set. To do this, use the Sets
application.

To create an organization, some data elements are required, as shown in

Figure 3-3.

Figure 3-3 New organization screen

Chapter 3. Platform Configuration 35

[Link] Draft Document for Review June 22, 2009 3:00 pm

1. In the Base Currency 1 field, enter the currency code for your base currency
or click Select Value.
2. In the Item Set field, enter the item set you want to associate with this
organization or click Select Value. You cannot change the item set after you
save the record.
3. In the Company Set field, enter the company set you want to associate with
this organization or click Select Value. You cannot change the company set
after you save the record.
4. In the Default Item Status field, click Select Value and select the status you
want new item master, service item, and tool records to have. (question 2.4.a)

When you are creating a new organization, the Clearing Account and Active?
fields are read-only until you save the record. The organization is inactive by
default, the Active? check box is cleared and the organization cannot currently be
used in the system. To activate the organization, you must edit the organization,
check the Active? field and enter a GL account in the Clearing Account field.

You can also add the Autonumbering feature from the Select Action menu. The
Autonumbering is configured in the Autonumbering application, see Figure 3.2
on page 33

Note: You can also configure the Drilldown option in the Organization
application.

Edit an organization
After you create an organization, you may want to edit addresses or other
information but you cannot edit the item or company set after you save an
organization record. You cannot edit base currency 1 after you add a site to the
organization and save the record

3.3.2 Delete an organization

You can delete an organization only if it has no sites associated with it.

You cannot delete sites at all; therefore, you can only delete organizations that
have never had sites associated with them.

More information on organizations is presented in the “Asset Chapter” in

Certification Study Guide Series: IBM Maximo Asset Management for IT,
SG247762.

36 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

3.3.3 Working with sites

A site is a subdivision of an organization that can track inventory and other data
separately from other sites. Certain types of information are unique to a site and
not visible to other sites within the organization.

Sites belonging to the same organization must use the same currency and share
the same options for work orders, assets, labor, and certain other types of data.

You use the Sites tab to add sites within an organization and to specify
associated information. Sites are defined at the organization level. You can add
as many sites to the same organization as needed.

After you add a new site, you cannot delete it, but you can make it inactive. If a
site is inactive, users cannot access site-level records for that site.

You use the Sites tab in the Organizations application to set up the sites to use
with the system. You have to consider some tips to set up sites:

Add a site
:To add a site you only need the site name (site ID). The site name must be
unique for all sites across the system, not just within the organization. See
Figure 3-4.

Figure 3-4 Add site screen

By default, the active status for a new site follows the status for the
organization—selected if the organization is active, cleared if the organization is

Chapter 3. Platform Configuration 37

[Link] Draft Document for Review June 22, 2009 3:00 pm

not active. If the check box is selected and you do not want the site to be used in
the system at this time, clear the check box.

Note: To set a site to active, the organization most be active. If a site and its
organization are both inactive, and you activate the organization, the site is not
automatically activated. However, if you make an organization inactive, then its
sites are automatically inactive.

3.4 Working with locations

The Locations application lets you enter and track locations for assets and
organize these locations into logical hierarchical systems or network systems.
Using hierarchies or systems of locations and specifying the location for assets
on the asset record provides the groundwork for gathering and tracking valuable
information on the history of an asset, including its performance at specific sites,
as it is moved from location to location. With locations organized into systems,
you can quickly find a location on the Drill down page, and identify the asset at
that location.

To open the Application, GoTo → Asset → Location and fill in the appropriate
information. Detailed information on locations is presented in the “Asset Chapter”
in Certification Study Guide Series: IBM Maximo Asset Management for IT,
SG247762.

3.5 Working with the Calendars application

You can use the Calendars application to create and modify calendars
associated with these system records:
 Assets
 Labor
 Locations
 Organizations
 People
 Preventive maintenance records
 Service Level Agreements
 Tools
 Work orders

38 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

Calendar records incorporate start and end dates, shift definitions, and
nonworking time. Holidays are examples of non-working time. Any number of
person, asset, or other records can reference a single calendar.

To open the Calendars application, select Go To → Administration →

Calendars and fill in the appropriate information.

Calendars are an organization level application. You create calendars for

organizations. If you want site-specific calendars, you can create them with
names that refer to the site, and have the site agree to just use those calendars
(see Figure 3-5). You can define shifts with complex repeating patterns using the
Define Pattern dialog box.

Figure 3-5 Calendars application

For more details on Calendars application, please refer to the following link:
[Link]
/[Link]/[Link]

3.6 Working with Classifications application

You use the Classifications application to create classifications and establish an
overall classification hierarchy. Classifications can help you to retrieve historical
data from other applications and to create detailed information about objects that

Chapter 3. Platform Configuration 39

[Link] Draft Document for Review June 22, 2009 3:00 pm

can be classified and retrieved later. These objects include assets, locations,
items, tickets, work orders, solutions, configuration items, purchasing documents,
and job plans. A classification is a word, a number, or an alphanumeric. A
classification can stand alone, or you can group it with other classifications for
further descriptions. Classifications let you store information about many objects,
such as locations, assets, items, and work orders.

For example, you can assign attributes to a classification creating the attribute
and specifying the data type, as shown in Figure 3-6.

Figure 3-6 Classification with new attribute

The system does not provide standard classifications. However, you can apply
industry standards when you create classifications.

Tip: To simplify the implementation process, base your classification structure

on how you currently group things in your business.

You must group information so that you can perform statistical analysis later. For
example, to determine how many customers complained about problem A versus
problem B, classify problem A differently than problem B.

The Classification application allows you specify the following details:

 Using Classifications - Users can search classification structures and
attributes with associated values when they use any object that can be
classified, such as assets, items, locations, configuration items, work orders,
tickets, and so on.
 Classification Structure / Hierachy - The structure consists of parent / child
relationships between individual nodes and is also called Classification
Hierachy. You build a classification structure the same way that you build a

40 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

directory structure: from the top down in parent-child relationships. First, you
create a parent (a classification), and then you add its children (each child is
also a classification), which belong to the parent. Each child then can become
a parent and have its own children. This pattern can continue indefinitely. The
structure from the top-level parent to the child that you are working with is the
classification path.
 Associates Classifications - You can define associations between actual
configuration item classifications and authorized configuration item
classifications. Defining, or mapping, these associations lets you create an
authorized configuration item from a configuration item record, and lets you
include the limited number of attributes that you need for configuration
management and change control.
 Separate Classification Hierachies - You add objects such as assets,
locations, or items in the Use With area of the Classifications tab. You indicate
the objects that you can use with the classification path. Consequently, you
can create one classification path that you can use with multiple objects, such
as assets, locations, and items. For example, you can use one hierarchy to
classify an asset, but a different hierarchy to classify the repair of that asset.
 Attributes - You can use attributes to search for objects that can be classified,
such as assets, locations, items, tickets, work orders, solutions, configuration
items, purchasing documents, and job plans (for example, you can search for
a blue car). Each classification node contains a list of attributes
characteristics of a classification object).
 Sections - You can break attributes into sections. Sections are groupings of
attributes allowing the same attribute to be used multiple times.
 Other Systems - You can integrate classification with other applications in the
system. You can create classifications for activities, assets, changes,
incidents, items, locations, problems, releases, service requests, solutions,
work orders, configuration items, purchasing documents, and job plans (see
the Domains application for more details 3.1, “Working with domains” on
page 31).

To open the Application, GoTo → Administration → Classifications and fill in

the appropriate information.

3.7 Working with E-Mail Listener

The E-mail Listeners application is used to receive and process service requests
and other types of tickets through e-mail in the form of e-mail messages. Using
E-mail Listener function, you can create or update tickets, and indicate whether
the status is changed or queried based on specified criteria. The E-mail Listeners

Chapter 3. Platform Configuration 41

[Link] Draft Document for Review June 22, 2009 3:00 pm

application can monitor multiple e-mail accounts to retrieve messages. The

application supports embedded and normal message attachments.

Note: The E-mail Listeners application cannot process encrypted or digitally

signed E-mail messages. Inform users of this limitation.

The E-mail Listeners application provides to the following features:

 Free form / formatted e-mails

The E-mail Listeners application can process free form e-mail of formatted
e-mails and allows you to send and store attachments. Formatted e-mails can be
composed using XML tags or text typed in the form of attribute-value pairs to
perform specific actions, such as changing the status of a business object or
querying the business object based on criteria.

Note: A built-in workflow process that supports various types of ticket objects
is shipped

 Storing attachments
The E-mail Listeners application processes attachments to an e-mail
message and stores the attachments as attached documents on the
application server.
 Other features
– The E-mail listener cron task
The E-mail listener cron task is used to encapsulates a staging process
which processes inbound E-mail through a staging table.
– Workflow Process
You use Workflow Process to parse e-mail information from the staging
table and process it according to the subject and content of each
message.
– Security
The E-mail Listeners application enables users to create, update, query,
and change the status of tickets, so it is critical to ensure that only
authorized users can run these functions using e-mails. For the sender of
an E-mail, the application checks security authorizations against the
system’s security configuration. This check establishes the ability of the
sender to run each specific function. More information on Tivoli process
automation engine security configuration can be found in Chapter 5,
“Security Configuration” on page 77.

42 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

– Communication templates
The E-mail Listeners application uses numerous communication
templates to generate notifications to end users and administrators.

To open the E-mail Listeners application, select Go To → System

Configuration → Platform Configuration → E-Mail Listener.

You can fill in the appropriate information, as shown in Figure 3-7.

Figure 3-7 E-mail Listener

You can customize the E-mail Listeners application to fit into your needs. For
detailed information about the E-mail Listeners application, you can refer to the
Maximo Online Help.

3.8 Working with cron tasks

You can use the CRON Task Setup application to add cron tasks, CRON Task
instances, remove CRON Tasks or their instances, and to modify CRON Task
parameters. You can also change the Active? status or adjust the schedule of a
CRON Task. The CRON Tasks can be rescheduled and parameter values can be
changed without stopping and restarting the server. The server performs CRON
Tasks a specific number of times, following a schedule, and without user
[Link] tasks are behind-the-scene jobs set to run automatically and on
a fixed schedule. The system contains a set of default cron tasks (e.g LDAP
Sync), but you can also create custom cron tasks to fit your business needs.
Cron tasks include activities like generating preventive maintenance work orders

Chapter 3. Platform Configuration 43

[Link] Draft Document for Review June 22, 2009 3:00 pm

(see Chapter 8, “Work management configuration and administration” on

page 149) and reordering inventory items on a schedule.

To open the CRON Task Setup application, select Go To → System

Configuration → Platform Configuration → CRON Task Setup.

You can fill in the appropriate information, as shown in Figure 3-8.

The Figure 3-8 shows an example of the cron task to be used to synchronize
LDAP data between Tivoli and the IBM Tivoli Directory Server.

Figure 3-8 Cron Task Setup

For more information on creating custom cron tasks, see your SDK

A detailed list about the CRON Task can be found in the MAXIMO Administration
Guide, page 140 under:
[Link]
m.doc_7.1/pdf/mam71_sys_admin_guide.pdf

3.9 Working with communication templates

Communication templates are available in any application that has the Create
Communication action. You use the templates to:
 Create and manage generic communication templates that users can use to
standardize frequently used e-mail communications (notifications).
 Create e-mail notifications for use with workflow and escalation processes.

44 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

 Associate file attachments or document folders to templates. For example to

receive an e-mail triggered by a workflow including a pre defined attachment.

When communications are sent, any attachments to the template are included in
the communication, either in a folder or an individual attachment. For your
convenience this can be send to Roles, Person or even Person Groups.

Tip: To store and track e-mail, you can enable the Com Log Entry? to add the
e-mails to the communication log of your requests.

To create a communication template, select Go To → System Configuration →

Platform Configuration → Communication Templates and fill in the
appropriate information.

The Figure 3-9 shows an example of a communication templates which you can
use to reply to a work order by sending back the work order number.

Figure 3-9 Communication Template - Example

For detailed information about maintaining Communication Templates, you can

refer to the Maximo Online Help.

Chapter 3. Platform Configuration 45

[Link] Draft Document for Review June 22, 2009 3:00 pm

3.10 Working with escalations

The following section will give you an overview about the Escalation application.

An escalation is a mechanism to monitor records which can take actions or send

notifications when a record reaches a defined escalation point. You use the
Escalations Application to create, view, modify, and delete escalation records.
You can create an escalation for any business object. Because all applications
are associated with business objects, you can create escalations for any
application and you can add any related notification to the escalation
configuration. For additional information, see the Maximo Administration Guide
under:

[Link]
m.doc_7.1/pdf/mam71_sys_admin_guide.pdf

You can use escalations with any application. However, you are most likely to use
them with the Service Desk applications, IT Asset Management applications, and
workflow processes. For example
 Service Desk Management - Service level agreements (SLA’s) are contracts
defined between a service provider and the recipient of the services. You can
use escalations to determine how incidents, problems, and service requests
are handled, and work to ensure that you remain compliant with any SLAs by
solving problems in a timely manner.
 IT Asset Management - You can use escalations to monitor IT contracts,
procurement, and inventory. By defining an escalation to alert managers 30
days in advance of a lease contract expiring, the managers can effectively
manage leases and avoid penalties or costly lease extensions.
 Workflow processes - You can use escalations to escalate assignments
before they time out in a recipient's Inbox. When you assign specific steps in a
workflow process to employees, those assignments display in their Inbox. If
the assignments are not completed promptly, they time-out in the recipients'
Inboxes. When this happens, you can use escalations to assign the tasks to
other people. This helps tasks get completed on time and helps to prevent
work backlogs.

Note: You can create escalations at the site, organization, or system level.

3.10.1 Maintaining the Escalation application

To support the daily requirements of your company you can configure the
Escalation Application as follows:

46 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

To open the Escalation Application, select Go To → System Configuration →

Platform Configuration → Escalation.

To create an escalation, you fill in the required data fields, as shown in

Figure 3-10.

Figure 3-10 Escalation Application

3.10.2 Escalation components

An escalation record consists of the following elements:
 Object: (Applies To field) You create escalation records for a specific
business object. The escalation engine retrieves records, from the business
object, that meet the escalation point criteria.

Tip: Select the object for which you are trying to use the Conditional SQL
Expression® Builder.

 SQL Statement - (Condition field) An escalation record can apply to all

application records, or to a specific set of records. You can create an SQL
statement that specifies records to which the escalation is applied. The
conditions can apply to one or more tables associated with the object.
Example 3-1 shows a valid statement about the history flag.

Chapter 3. Platform Configuration 47

[Link] Draft Document for Review June 22, 2009 3:00 pm

Example 3-1 SQL - Statement

historyflag=0 and ticketuid in (select ownerid from slarecords where
ownertable= 'TICKET' and slanum= '1009' )

 Organization and or site - Escalations are at the System level. You can create
escalations for use with a specific organization or site.
 Schedule - A schedule that defines how often the system checks for records
that meet the criteria for the escalation. The polling interval can be seconds,
minutes, hours, days, weeks, or months. You also can specify that the interval
be calendar or date based.
 Escalation Point - Date- and time-based, or other condition criteria for when
the actions or notifications specified on the escalation record are triggered.
An escalation record can have one or more escalation points (see “Working
with escalation points” on page 49.
 Actions - Any actions that must be taken when a record reaches the
conditions of an escalation point. You define actions separately for each
escalation point. You can associate multiple actions for each escalation point.
You use the Actions application to define actions (see “Actions and
notifications” on page 49.
 Notifications - Any notifications that the system must generate when a record
reaches the conditions of an escalation

You can create escalations with the following items:

 Header attributes, which identify the set of records that the escalation
monitors (the global search criteria)
 Escalation points, which define thresholds that must be met before an
escalation occurs
 Actions, which are events you want to occur when the escalation points are
reached
 Notifications, which are e-mails messages that are sent when the escalation
points are reached

In addition the system provides numerous pre defined escalation which can be
tailored to your needs. In addition, you can use the escalation in conjunction with
Workflow application action (APPACTION). For example, you can use the
Workflow Assignment (WFASSIGNMENT object) to be used to reject
(WFREJECT), accept (WFACCEPT) or escalate (WFESCALATE) a workflow
process. For more information about the Escalation configuration, refer to the
Maximo Online Help.

48 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

3.10.3 Working with escalation points

You can define multiple escalation points, and each one can be associated with
one or more actions and/or notifications. Activating an escalation does not trigger
an escalation process.

Typical escalation points include:

 measuring elapsed time against an attribute (time period from now to an
event in the past, this can be defined with a negative values), such as how
many hours an assignment has been untouched in a person's Inbox
 measuring time until lapse (time period from now to an event in the future),
such as how many days until a contract expires
 a standalone condition without a time measurement, such as using the
system to automatically accept or reject an assignment in a workflow process

Note: The system triggers an escalation only when the escalation engine
finds records that meet the criteria defined by the escalation points.

Actions and notifications

You can associate one or more actions to an escalation point, and you can
associate one or more notifications to an escalation point. You must associate at
least one action or notification to an escalation before you can activate the
escalation. You are not required to have both actions and notification.

Action
An action is an event you want the system to trigger when it finds records that
meet the condition(s) defined by the escalation point, such as changing a status
or an owner. When you add an action, you can select a preexisting action and
assign it a sequence number (if multiples). The system defaults the description
and the action type, which is based upon the record and action you chose, e.g in
Figure 3-11 on page 49. You can also go to the Actions application to create a
new action and return it for use with your current escalation.

Figure 3-11 Action

Chapter 3. Platform Configuration 49

[Link] Draft Document for Review June 22, 2009 3:00 pm

The system ships with a number of predefined action types, such as Set Owner,
Status Change, or Create Ticket. You can create new action types, if needed.

Action groups are predefined sets of actions that are grouped together in a
specific sequence. The system associated an escalation point with one or more
actions through the action group. For detailed information, refer to MAXIMO
Online Help.

Notification
A notification is an E-mail that you want the system to send when it finds records
that meet the condition(s) defined by the escalation point. Figure 3-12shows an
example how you can configure the notification.

Figure 3-12 Notification

You can create two types of notification:

 free-form notification - Free-form notifications require you to define only a
role/recipient, subject, and message
 template-based notification - You can pre define several “communications
templates” (see “Working with communication templates” on page 44) to send
the needed information using the Escalation Application.

Tip: You can use the Roles record Broadcast? field to send out a notification
to all people in a person group.

Deletion escalation rules

After you deactivate an escalation, you can delete an escalation point. If you do
delete an escalation point, the system also deletes the links to the actions and
notifications associated with the escalation point. The system will not delete the
actions and notifications themselves. You must have at least one escalation point
in an escalation. If you delete all escalations points, you cannot activate the
escalation.

50 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

You can delete an action or notification associated with an escalation point

without affecting other actions and notifications tied to it.

Validate escalation
When the system validates an escalation, it is only validating the SQL statement
within the Condition field and the escalation points defined for the escalation.
Validating the escalation points ensures that when the criteria that defines the
escalation point is met, the escalation mechanism triggers the associated actions
and/or notifications. The system does not validate the actions or notifications
themselves.

If there is an error in either the SQL statement(s) in the escalation header's

Condition field or in the SQL statement(s) in the Escalation Point Condition field
within an escalation point, you must expand the Validation Results table window
to see information about the specific error(s). If you have more than one
escalation point and the validation fails, the system indicates which escalation
point produced the error(s) by highlighting the row in red.

The validation will be started from the Select Action menu, choose Validate.

Escalation schedule
An Escalation needs to be scheduled to give the right notification at the right
time. From the Set Schedule dialog box, you can choose a date and/or time
interval and preview the first twenty occurrences of the schedule. The schedule
filed in the escalation record will schedule by which the escalation will poll for
conditions. For example, depending on the available fields, a schedule can be as
simple as "every 5 minutes" or as complex as "the fourth Monday of the month at
9:30 PM, every month."

3.11 Working with Workflow Designer

You use the Workflow Designer application to create, view, modify, and delete
Workflow process records that reflect your business process. An active Workflow
process revision defines the different paths that a record can take as it moves
through the business process. The process also defines the different actions and
notifications that should take place at different points in the process.

To open the Workflow Designer application, select Go To → System

Configuration → Platform Configuration → Workflow Designer.

The Workflow Designer application contains the following tabs:

 List - to search for processes

Chapter 3. Platform Configuration 51

[Link] Draft Document for Review June 22, 2009 3:00 pm

 Canvas - The Workflow Canvas tab provides the tools and work space to
create, view, and modify Workflow processes. The Workflow canvas is a
graphical view of a Workflow process. It lets you see the process elements
and how they are connected as shown in Figure 3-13.

Figure 3-13 Workflow Designer - Canvas

You use the canvas to add nodes and connection lines as you construct a
process and configure the properties of each process element.
The Canvas Tab consists of the following sections:
– Record header
– Workflow tool palette
– Workflow canvas

To understand the Workflow Designer Toolbar and the Palette, please refer to:
[Link]
/621_mx_wkfl_imp.pdf
 Process - While the Canvas tab provides a graphical view of the elements in
a process, the Process tab lists the process elements in a pair of table
windows. The Process Nodes table window displays all nodes in the process.
Each row includes the node Title, Description, and Type. The row that you
select in the Process Nodes table window determines the data that the
system displays in the Actions table [Link] Actions table window
displays any actions associated with the connection lines exiting the selected
node. Each row includes the name of the action record, the instructions to the
assignee, the node to which the connection line leads, and whether the
connection is positive or [Link] can click the Edit Properties button for
any node or action to access the Properties dialog box for the node or
connection line.
– Process Node Types - A node is a graphical element that represents a
point in your business process. Workflow Designer includes different types
of nodes that can represent different points in your business process, for
example:

52 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

• the entry of a record into the process

• decision points
• points when a path branches
• manual input from an individual or group
• navigation of the user to a user interface element of an application
• automated actions
• record exit from the process

You can drag and drop nodes from the palette onto the canvas. You can add any
number of nodes to a process. However, if a process exceeds 50 to 100 nodes,
you might want to consider whether you can break the process down into
subprocesses to simplify managing and maintaining it.
• Start Nodes
A Start node indicates the point when a record enters or starts a Workflow
process. The tool palette does not include a Start Node Tool because
when you create a new process, Tivoli process automation engine places
a single Start node on the canvas. Each process can have only one Start
node, and you cannot delete Start nodes.
• Task Nodes
A Task node indicates when a user has two choices, for example, to
approve or reject a record. You use Task nodes when your business
process requires a user to evaluate the record and you want to create a
task assignment that routes the record to one or more individuals.
When Tivoli process automation engine encounters a Task node while
routing a record through the process, it stops the process and
generates one or more task assignments, based on the node
properties. Individuals can receive task assignments via the Workflow
Inbox portlet on their Start Center, or via e-mail. The assignee views
and completes the assignment in the Complete Workflow Assignment
dialog box. You place a new Task node on the canvas by using the Task
Node Tool in the palette. A process can have one or more Task nodes,
but you do not have to include Task nodes in a process.
For example, a client has a workflow requirement on new asset
records. Part of this requirement is that the Contracts representatives
from the Lease and Warranty groups review and validate contracts the
asset may or may not be under. The asset record cannot move to the
next part of the workflow process until all assignments are completed.
You can configure this request when you use a Task node and assign
to the Leasing and Warranty roles. Configure the task to indicate that
the Perform Acceptance Action is for when all assignments are

Chapter 3. Platform Configuration 53

[Link] Draft Document for Review June 22, 2009 3:00 pm

accepted. Configure the Positive connection line coming from this Task
node to indicate an instruction that indicates that Leasing and Warranty
Contracts have been reviewed and this asset is under a contract.
Configure the Negative connection line coming from this Task node to
indicate an instruction that Leasing and Warranty Contracts have been
reviewed and this asset is not under a contract.
• Condition Node
A Condition node indicates an evaluation of the record, based on data
in the record. You use a Condition node to have Tivoli process
automation engine to make a true/false evaluation of the record, then
direct the record based on that evaluation. When Tivoli process
automation engine encounters a Condition node, it evaluates the
record based on the SQL statement defined in the node properties,
then routes the record to either the positive or negative connection line
exiting the node. You place a new Condition node on the canvas by
using the Condition Node Tool in the palette. A process can have one
or more Condition nodes, but you do not have to include Condition
nodes in a process.
• Manual Input Nodes
A Manual Input node indicates a need for user input because there are
multiple directions that a record can take in a process. You use a
Manual Input node to have a person decide what should happen next.
When Tivoli process automation engine encounters a Manual Input
node, it displays a dialog box to the user. The Manual Input dialog box
contains a menu of options for routing the record. When the assignee
selects an option, Tivoli process automation engine triggers any
actions or notifications associated with the option. You place a new
Manual Input node on the canvas by using the Manual Input Node Tool
in the palette. A process can have one or more Manual Input nodes,
but you do not have to include Manual Input nodes in a process.
• Subprocess Nodes
A Subprocess node indicates that a separate Workflow process is
contained within a Workflow process. You use a Subprocess node to
break a complicated business process down into smaller self-contained
units. For example, you might use a different process for different
subcategories of records, such as records from different Sites, or
different classes of work orders. When Tivoli process automation
engine encounters a Subprocess node while routing a record through a
process, it routes the record into the subprocess. When the record
encounters a Stop node within the subprocess, Tivoli process
automation engine returns it to the main process at the same point
where it left the process. You place a new Subprocess node on the

54 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

canvas by using the Subprocess Node Tool. A process can have one or
more Subprocess nodes, but you do not have to include Subprocesses
nodes in a process. A Workflow can have one or more Subprocess
nodes based on the complexity of your business process and how you
choose to design the process.
• Wait Nodes
A Wait node indicates that a record.s progress through a process
should pause until a required condition is met. You use a Wait node to
create a reaction to a database event, for example, a status change, or
a record being updated. You might use a Wait node when Tivoli
process automation engine is integrated with another system, for
example, an external financial system, and must exchange data with
that system. When Tivoli process automation engine encounters a Wait
node it pauses at the node indefinitely, until any event specified in the
node properties occurs. At that point, the record resumes its progress
through the process, and Tivoli process automation engine triggers any
actions or notifications specified on the properties of the connection
line exiting the node. You place a new Wait node on the canvas by
using the Wait Node tool in the palette. A process can have one or
more Wait nodes, but you do not have to include Wait nodes in a
process. A Wait node cannot precede a node that requires user
interaction (Interaction node or Manual Input node).
For example for using the Wait node is: Part of a client's workflow
requirement is that an asset record in a workflow process does not
move to the next part of the workflow until the field Is running? on the
asset record had been updated. You can accomplish this by using a
Wait node. Configure the Wait node event to: [Link].
After the wait node, have a Condition node compare the old and new
values of the field of interest or test for a difference in the data value
conditionally: ISRUNNING = 0.
• Interaction Nodes
An Interaction node provides one option for a user interaction with a
record. You use Interaction Nodes with Manual Input nodes to guide a
user through a structured interaction with a Tivoli process automation
engine record. When Tivoli process automation engine encounters an
Interaction node while routing a record through a process, the result
depends on how the node is configured. In addition, Tivoli process
automation engine can display a message dialog box containing
instructions to the user. You place a new Interaction node on the
canvas by using the Interaction Node Tool in the palette. A process can
have one or more Interaction nodes, but you do not have to include
Interaction nodes in a process. A Manual Input node usually precedes
an Interaction node. If an Interaction node leads to an application not

Chapter 3. Platform Configuration 55

[Link] Draft Document for Review June 22, 2009 3:00 pm

related to the object specified on the process record, a Stop node

should follow the Interaction node.
• Stop Nodes
A Stop node marks the end of a Workflow process, that is, the point
where a record leaves control of the process. When you create a new
process, Tivoli process automation engine places a single Stop node
on the canvas. You can place additional Stop nodes on the canvas by
using the Stop Node Tool in the palette. You use a Stop node to have a
record exit the process. If you are creating a subprocess, you use a
Stop node when you want the record to return to the main process.
When Tivoli process automation engine encounters a Stop node while
routing a record through the process, the record exits the process.
Each process must have at least one Stop node. A process can have
multiple Stop nodes.
– Connection Lines
All nodes in a process must be connected to at least one other node, and
all nodes except Start and Stop nodes must be connected to two other
nodes. You can draw two types of connections between nodes:
• Positive Connections - You use the Connect Nodes Tool to draw a
positive line between nodes. A solid black line on the canvas
represents a positive connection. A positive connection indicates a
positive outcome, for example, that an action was performed, a record
was approved, or that a record meets the condition specified by the
node.
• Negative Connections - You use the Negative Connection Tool to draw
a negative line between nodes. A dashed red line on the canvas
represents a negative connection. A negative connection indicates a
negative outcome, for example, that a record was cancelled, a record
was rejected, or a record does not meet the condition specified by the
node.

To get a detailed overview about the different properties and connection lines for
each node in the Workflow Designer, refer to the MAXIMO Online Help or to
[Link]
/621_mx_wkfl_imp.pdf

3.11.1 Creating workflows

You create a workflow process by inserting nodes and connection lines on a
Workflow canvas. Each Workflow process includes start and stop nodes. Start
and stop nodes do not carry user-defined information. The other nodes carry

56 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

user-defined actions. You use the Workflow Designer tools to place, connect, and
configure the nodes and lines.

For example, your business requires the blocking of status changes when a work
order record is in workflow, unlocking at a certain point to perform a status
change to APPR, and then relocking when the status change occurs. To
configure this define this example in the Workflow Designer, need the implement
the following steps:
1. In the Actions application, create an Action Group for the work order object
with the following members in the following order: OKSTATUS, Work Order
Approval action, NOSTATUS.
2. On the workflow connector line where the status block is to begin use a
NOSTATUS action.
3. To unlock the status change block, prior to the next status change, on a
connector line use the Action Group.
4. Each node except the Start node must have at least one line entering it.
5. Each node except a Stop node must have at least one line exiting it.

You have to configure more examples to get familiarized with the Workflow
Designer.

A complete documentation about creating Workflows has been published in the

IBM Maximo Workflow Implementation Guide, page 77. Refer to:

[Link]
/621_mx_wkfl_imp.pdf

3.12 Workflow Administration application

In addition to the Workflow Designer, you use the Workflow Administration
application to view and manage active instances of Workflow processes. The
Workflow Administration application contains a single table window, which
contains a row for each active instance of workflow, see Figure 3-14 for details. A
single record can show up multiple times if it is controlled by multiple workflow
instances. You can see which version of a revised process was used to create
each instance, the person ID of the individual who routed each record into
Workflow, and the date and time that the process was initiated. The recordkey
(for example, work order number or PO number) is displayed with the Site ID in
the Owner Description field.

Chapter 3. Platform Configuration 57

[Link] Draft Document for Review June 22, 2009 3:00 pm

Figure 3-14 Workflow Administration

You use the Processes table window to view, modify, and stop active process
instances. When a record leaves the control of Workflow, the system removes
the entry from the Processes table window. You can use Workflow Administration
application to perform the following tasks:
 View Workflow assignments.
 Reassign Workflow assignments.
 Delete Workflow assignments.
 Stop active processes, removing the record from the control of the processes.

3.12.1 Conditional Expression Manager

You use the Conditional Expression Manager application to create and maintain
a library of conditions. These conditions can contain expressions and class files.
This files will be stored the directory structure, and must be in a folder under the
root of the product [Link] other applications, such as Application Designer
and Security Groups, you select from predefined conditions to set up conditional
behavior. The Conditional Expression Manager belongs to the Administration
Section but heavily belongs to the overall platform configuration.

To open the Conditional Expression Manager application, select Go To →

Administration → Conditional Expression Manager.

You can add new conditions by adding New Row and fill in the appropriate
information. The Conditional Expression Manager application contains one table

58 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

window only, which displays the list of conditions. You use the table window to
add, view, modify, or delete conditions.

When the expression evaluates to true, conditions let you configure access to
fields, tabs, and other user interface controls within applications. For example,
you can set the following types of conditional access:
 Give read-only access to information displayed in a field.
 Give read-write access to information displayed in a field.
 Give a user group read-only access to a specific field or action in an
application.
 Give all members of a user group read-write access to a specific application.
 Do not display a field or tab in an application to certain users.

You can also set access to application options, controls, or data elements.
Examples include:
 Grant access to application options in the Select Action menu for a security
group.
 Configure any property in a control for a group, such as making a control
hidden, masked, read-only, or required.
 Configure other properties, such as color, label, and application link, to differ
according to group and different conditions.
 Show or hide a data attribute globally or for a security group.

The system uses a syntax like Structured Query Language (SQL). However, the
syntax of this system uses additional variables. For easier evaluation of your
expression, you can use the Conditional Expression Manager Builder.

3.12.2 Conditional Expression Manager Builder

The expression syntax of this system uses a colon (:) to define a variable. The
system uses this syntax to avoid ambiguity when you create expressions that
relate to the current record (business object) or to a specific record. For example,
you can have subselect in the expression, such as:
exists (select 1 from workorder where wonum=:wonum)

The first wonum is the wonum attribute on the workorder object. At run time, the
system replaces the second wonum with the value of the “wonum” attribute for
the current business object.

Detailed information about the Syntax are given in the Maximo Online Help.

Chapter 3. Platform Configuration 59

[Link] Draft Document for Review June 22, 2009 3:00 pm

Figure 3-15 shows the options of the Conditional Expression Manager and the
validation results.

Figure 3-15 Conditional Expression Manager

Formulare which are not correct, will be validated and an error message will be
shown.

Use the Condition Expression Manager and test the following expression by
using the WORKORDER object, as shown in Example 3-2.

Example 3-2 Expression

&owner&.[Link]>&owner&.priority.

The result brings up the following error message as shown in Figure 3-16.

60 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

Figure 3-16 Error Message (Conditional Expression Manager)

3.13 Platform configuration summary

Since this chapter contains various options to customize and configure the
Platform Configuration application, the following bullet point summarizes the
what is included applications as part of the Platform Configuration module.

To open the different applications inside the platform configuration module, you
go to Go To → System Configuration → Platform Configuration, as shown in
Figure 3-17 on page 62.

Chapter 3. Platform Configuration 61

[Link] Draft Document for Review June 22, 2009 3:00 pm

Figure 3-17 Platform Configuration Options

 Platform Configuration
– Actions
• Manage the administrative functions of creating actions and action
groups within escalations.
– Roles
• Manage roles within Tivoli Maximo Asset Management.
– Communication Templates
• Create and manage generic communication templates that users can
leverage to standardize
• Frequently used e-mail communications (also known as notifications).
– Database Configuration
• Create or modify the objects and attributes used by Tivoli Maximo
Asset Management applications.

62 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

– Application Designer
• Create new applications (clones and custom applications) or tailor the
pages of existing applications.
– Escalations
• Automatically monitor critical processes across your enterprise. The
primary goal of Escalation Management is to ensure that critical tasks
are completed on time, such as those defined in service-level
agreements (SLAs).
– Cron Task Setup
• Cron tasks are behind-the-scene jobs set to run automatically and on a
fixed schedule.
– Domains
• Maintain lists of defined values that appear in drop-down lists
(sometimes referred to as value lists).
– Logging
• Manage log settings and configure log files.
– System Properties
• Manage system properties and their values used by various product
components.
– Web Services
• Create, modify, and delete Web services. You also can generate
schema and Web Service Description Language (WSDL) files for any
Web service that you deploy. External applications can use Web
services to query or to send transactions to the Integration Framework.
– Workflow Administrator
• View and modify assignments within the workflow, escalation, and
service-level agreement processes.
– Workflow Designer
• Use this graphical application to create a series of decision paths for
records to flow through, called workflow process.
– E-mail Listener
• Receive and process incoming e-mail messages. This application can
monitor multiple e-mail accounts to retrieve messages, and it supports
embedded and normal message attachments.
– Launch in Context

Chapter 3. Platform Configuration 63

[Link] Draft Document for Review June 22, 2009 3:00 pm

• Create and manage launch entries that open, in the same or a different
browser session, an application that is external to the system.
– Object Structures
• Create, view, modify, and manage the processing logic of an object
structure. An object structure is the common data layer that the
Integration Framework uses for all outbound and inbound application
data processing. An object structure consists of one or more
sub-records that develops their XML content from a particular object.

In addition to the platform configuration, you will find the migration part under the
System Configuration. To open the Migration application, select Go To →
System Configuration → Migration, as shown in Figure 3-18

Figure 3-18 Migration Application

– Migration
• Manager Define, create, distribute, and deploy packages. Packages
are used to transfer and deploy the many configuration changes
possible with the Tivoli Maximo Asset Management configuration tool
set from one environment to another (that is, from a development
environment, to test environment, to production environment).

64 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

– Migration Groups
• Create groups of configuration objects and link related (dependent)
groups to the objects that you create. You group configuration objects
to ensure that all related configuration data is collected from source
environments and distributed to target environments.

Chapter 3. Platform Configuration 65

[Link] Draft Document for Review June 22, 2009 3:00 pm

66 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

Chapter 4. Financial configuration

This chapter introduces Financial configuration and its applications such as
Chart of Accounts, Currency Codes, Exchange Rates and Cost Management.

The following topics are covered in this chapter:

 “Introduction to Financial configuration” on page 68
 “Currency codes” on page 68
 “Exchange rates” on page 69
 “Chart of accounts” on page 71
 “Cost management” on page 74

© Copyright IBM Corp. 2009. All rights reserved. 67

[Link] Draft Document for Review June 22, 2009 3:00 pm

4.1 Introduction to Financial configuration

All Financial Configuration applications can be accessed using the Go To Menu
from the Start Center screen, as shown in Figure 4-1.

Figure 4-1 Financial Configuration

In this chapter, we will cover the functionality of the following applications from
the Financial Configuration:
 Currency Codes
 Exchange Rates
 Chart of Accounts
 Cost Management

4.2 Currency codes

The Currency Codes application is the responsible for creating and maintaining
the list of possible currencies that are used in Maximo. To launch this application,
click on Go To Menu → Financial → Currency Codes.

The Currency Codes application is accessed through the List Tab plus the Select
Action menu. To create a new currency, just click on New Row button, as shown
in Figure 4-2 on page 69, button the fill in the following fields:

68 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

Figure 4-2 Creating a currency code

 Currency: the currency name, like USD for US Dollar

 Description: The currency name, like US Dollar
 Active?: This checkbox will make the currency active to be used for other
applications.

Once you have created all the required currency codes, these codes will be
avaiable to be used in all applications.

The currency codes are considered at the Organization Level. This means that
you can use the same currency code through different organizations, so you
don’t need to create a set of currency codes for each organization you need. This
is important because the Currency Codes application is a very simple
application, but it is the base for all other financial applications.

Note: To use the Currency Code and any other Financial Configuration
applications, you must have Organizations already configured.

4.3 Exchange rates

The Exchange Rates application is used to set up exchange rates to convert
currencies. It is mostly used when dealing with different country sites and
different currencies.

To use the Exchange Rates application, go to the Go To menu, and then select
Financial → Exchange Rates.

The application will show all valid Organizations, as shown in Figure 4-3 on
page 70, and all already existing exchange rates. If the exchange rates for your
site is empty, you can create an exchange rates simply by clicking on the New
Row button.

Chapter 4. Financial configuration 69

[Link] Draft Document for Review June 22, 2009 3:00 pm

Figure 4-3 Exchange Rates main screen

Once you click on New Row, a Detail section will be created in order to allow you
to create the required exchange rate. The fields that you will be using are:
 Convert from Currency: Type here the currency that must be converted, i.e.
EUR for Euros.
 Convert to Currency: Type here in what currency you want to the currency to
be converted to, for example USD, if you want to convert Euros to US Dóllars.
 Exchange Rate: Here you can specify the conversion rate between the two
currencies.
 Active Date: Specify the date when this exchange rate was activated.
 Expiration Date: Specify the last date that this exchange rate can be used by
the system).
 Memo: This field is free for use with administrator’s notes regarding this
operation.

Since the Exchange Rates application is an Organization Level application, you

will need to create separate exchange rates for each organizations that you need
to use this function. They can share the same currency, but the exchange rate
value can be different for each organization that you might have.

70 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

4.4 Chart of accounts

Chart of Account application has two main sub-applications: General Ledger
Account (aka GL Account) and Financial Periods. The General Ledger Account
is responsible for accounting of the organization. The Financial Periods
sub-application defines, from the financial point-of-view, when the fiscal year
begins and ends.

Note: The application Chart of Account is very important since it is used for all
other applications, so you need to plan very well how to implement a good set
of GL Accounting components to avoid major changes in the future.

4.4.1 General Ledger Account (GL Account)

GL Account is used for all other Financial Applications. You can use Chart of
Accounts to perform the following actions:
 Create GL (General Ledger) account codes and components
 Define Financial Periods
 Create default GL Accounts

You first need to specify the format of General Ledger account codes using the
GL Account, then go to Configuration action in the Database Configuration
application to configure the GL Account. The GL Account format includes the
number and length of components and delimiters.

You will define tax codes, rates, and dates using Purchasing Options → Tax
Options in the Organizations application.
General Ledger account codes typically include components (segments) sepa-
rated by delimiters:
Example: 6210-300-000

To start using the GL Account application and Chart of Accounts:

1. From the Go To menu select System Configuration → Platform
Configuration → Database configuration.
2. Once the application Database Configuration is opened, click Select Action
menu and then on GL Account Configuration as shown in Figure 4-4 on
page 72:

Chapter 4. Financial configuration 71

[Link] Draft Document for Review June 22, 2009 3:00 pm

Figure 4-4 Setting up GL Account Configuration.

3. This option will allow you to create the main configuration of GL Account.
Since in this example we are using the format: 6210-300-000 they are related
to a structure like WORKTYPE-OBJECTTYPE-OBJECT, but we can change
this structure as shown in Figure 4-5.

Figure 4-5 GL Account Configuration

4. Once you have specified the fields, Length, Type and the Screen Delimiter for
each of the components (Worktype, Objecttype and Object), you can move to

72 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

the Organizations application and set the Clearing Account by clicking on

Select Value button, as shown in Figure 4-6:

Figure 4-6 Adding a GL Account into an Organization

Important: GL Accounting is defined at the Organization Level and shared by

the children sites and its locations address. Consider always to create another
organization when you need to specify different sets of GL Account for each
site and or location, for example.

4.4.2 Financial Periods

Financial Periods is the application that deals with the business year from
accounting point-of-view. In this application, you specify when the fiscal year is
planned to start and end.

You must define at least one financial period. The system adds a financial period
stamp to all transactions when you generate them. The transactions must occur
during an open, valid financial period. The requirements of the accounting
system you use determine the format of the period.

To open a valid financial period, go to the Go To → Financial → Chart of

Accounts → Select Action menu → Financial Periods.

You can create financial periods by providing the following information

Chapter 4. Financial configuration 73

[Link] Draft Document for Review June 22, 2009 3:00 pm

 Period: Is the name of that financial period that you are creating. Must be
something useful to you.
 From: Is the date when your financial period is beginning.
 To: Is the end date for the financial period.
 Accounting Close Date: Is the planned date to close the financial period.
 Actual Close Date: Is the real date when the financial date was real closed.
 Closed by: Is the username of the person who actually close the financial
period, as shown in Figure 4-7.

Figure 4-7 Financial Period main screen

4.5 Cost management

Cost Management is the application that manages and generates the project cost
information, tracks the financial resources that are required to complete a project
and manages budgets more effectively.

74 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 22, 2009 3:00 pm [Link]

In order to access Cost Management application, go to the Go To menu, and

select Financial → Cost Management.

The application is displayed in its List Tab. The main fields are as shown in
Figure 4-8.

Figure 4-8 Main fields of the Cost Management. application

The most important fields are Project, Budget, Value and Parent Project. In
those fields are specified the enough information in order to track the project’s
budget more effectively and keep tracking of cost of each required task.

To create a relationship between task and the budget’s cost, you need to create a
separate cost line per each task by clicking on New Row, as shown in Figure 4-9.

Figure 4-9 Cost Line per each Task

The application itself is quite small, but very important, when you have to specify
the line items and its costs by project. This information can be used internally for
integration among other applications.

Chapter 4. Financial configuration 75

[Link] Draft Document for Review June 22, 2009 3:00 pm

76 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Chapter 5. Security Configuration

The Security Configuration is used to define the access level for Users and
Groups. It is important to plan your security strategy carefully before you
implement the security configuration. This chapter will guide you thru the needed
steps:

The Security system is used for:

 authentication - to validate the users credentials against the system.
 access - lets the user access various resources based on the identity of the
user.

The Security Groups application defines all groups and their privileges.

This chapter has the following sections:

 “Security profiles” on page 78
 “Conditional security overview” on page 111

© Copyright IBM Corp. 2009. All rights reserved. 77

[Link] Draft Document for Review June 17, 2009 9:59 am

5.1 Security profiles

The Security Group application works together with the Users application. While
the Security Group defines the authorization, the users inherits the
authorizations of the groups to which they belong therefore creating their security
profile.

A user’s security privileges controls a user’s access to modules, applications,

menu options, and data. All security access is based on security groups. A user
name is associated with one or more security groups, and can have different
levels of access to the applications and actions.

The Security Groups application is the building block for the security
infrastructure. You configure security groups, either independent or
non-independent, to provide narrow access or broad access to applications,
Sites, labor, and other settings, such as general ledger components and approval
limits and tolerances.
The security group to which a user belongs controls the user’s level of access
and privileges within the system. The system generates a user’s security profile
from all the groups in which a user is a member, using business rules to
determine how the various security groups combine to build a virtual security
profile. The security profile is like a fingerprint. It uniquely defines a user’s access
rights and privileges.

5.1.1 Security Groups application

In the system, you set up security privileges by group. You use the Security
Groups application to create groups. Then you specify group privileges and
restrictions for applications and options, as well as other settings.
 In the Security Groups application, you assign users to groups.
 In the Users application, you assign groups to users.

The combination of groups to which a user belongs determines an individual

user's security privileges. You can view a user's security privileges graphically on
the Security Profile tab in the Users application.

When you first implement the system, the Security Groups application has four
groups:
 DEFLTREG - allows a user to change his or her password if it expires. It
contains no other rights. When you insert a new Users record, the system
places the user in this default group, though you can specify a different group
to be the default using the Security Controls dialog box.

78 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

 MAXADMIN - provides enough access to the system to add users and

groups.
 MAXREG - a group that allows users to self register. You can use MAXREG to
initiate a workflow process by which the system alerts an administrator to
assign new users to the appropriate security groups.
 EVERYONE - used for global settings that apply to all users in the system.

You must create additional groups, with different sets of rights, to be able to
assign users different sets of privileges.

If you want new user security profiles to start with more rights, you can modify the
DEFLTREG group to include them.

Note: Using LDAP (Lightweight Directory Access Protocol) with the system
entails special consideration. Consult the System Administrator's Guide
([Link]
ic=/[Link]/[Link]) for information on integrating the
system with LDAP.

The Security Groups application contains the following tabs:

 List: to search for group records.
 Group: to add a new group, specify its start center, and specify whether or not
the group rights are independent of other groups.
 Sites: to specify which sites a group has access to in a multisite
implementation.
 Applications: to specify which applications and options a groups has rights
to.
 Storerooms: to specify which storerooms a group has access to.
 Labor: to specify which labor records a group can view.
 GL Components: to specify which GL components a group can change.
 Limits and Tolerances: to specify various purchasing, requisitioning, and
contract limits and invoice, tax, and service tolerances.
 Data Restrictions: to restrict access to certain data fields and certain
functions in applications.
 Users: to assign users to groups and view existing group membership.

Chapter 5. Security Configuration 79

[Link] Draft Document for Review June 17, 2009 9:59 am

Important: If your implementation uses an application server to authenticate

with a directory, you will not use the system to perform some functions.
Instead, these functions will be performed in the directory and synchronized
into the system. These functions may include:
 Adding users (including self-registration)
 Adding security groups
 Associating users with security groups
 Managing password

Note that prior to moving to production the building blocks of your migration will
be:
 Organization
 Users
 Assets

5.1.2 Adding security groups

Proceed as follows to create a new security group:
1. Click on the Go To menu then select Security → Security Groups.

Figure 5-1 Security Groups

2. You are then able to view the existing security groups, as shown in Figure 5-2
on page 81.

80 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Figure 5-2 Security Groups list

3. In the Security Groups window, click on the New Group icon. The system
displays the Group tab. See Figure 5-3.

Figure 5-3 Creating a new Security Group

4. In the Group field, enter a name for the group.

You might name a group after a site, for example, HAMBURG, or for some
functional unit, such as OPERATIONS, MAINTENANCE, and so forth.
5. Add a description in the Group Description field. To enter additional
information type in your description.
6. In the Start Center Template field, enter the name of the start center you
want the system to display when a user in the group logs in.
7. Click the Select Value icon to select from a list. (See Figure 5-4 on page 82)

Chapter 5. Security Configuration 81

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-4 Start Center template selection

By default, the system merges rights when groups that include different sites
are combined.
8. If you do not want rights combined, select the Independent of Other
Groups? check box, as shown in Figure 5-5.

Figure 5-5 Independent of Other Groups selection

Assign sites to a security group

Now your security group is created. Next, you can assign sites to this group, as
follows:
1. Click on the Sites tab (Figure 5-6 on page 83).

82 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Figure 5-6 the Sites tab

You use the Sites tab in the Security Groups application to assign site access
privileges to a group.
2. On the List tab, select the group for which you want to assign site access.
3. Click the Sites tab.
4. If you want the group to have access to all sites, select the Authorize Group
for All Sites? check box.

Note: If you select this check box, you cannot add individual rows in the Sites
table window.

If you want the group to have access to individual sites:

5. Click New Row in the Sites table window. The Row Details opens.
6. In the Site field, enter the name of a site or click the Select Value icon. The
Select Value dialog box lists all sites for all organizations. After you select a
site, the system fills in the information in the remaining fields.
7. Click Save Group.

Notes:
 You can only add sites that you have access to. You can only add inactive
sites to a group if your user record is authorized for inactive sites.
 There is no limit to the number of security groups you can create.

Adding applications to a security groups

You can add applications to a security groups in the following way:
1. On the List tab, select the group for which you want to grant privileges.
1. Click the Applications tab. See Figure 5-7 on page 84.

Chapter 5. Security Configuration 83

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-7 Applications tab

2. In the Applications table window, select the application. To narrow your

search, use the Filter. The Options table window displays the options for the
selected application.
3. In the Applications table window, select the appropriate options using the
Grant Listed Applications button to grant the following privileges to all listed
applications, or use the Revoke Listed Applications button to remove
privileges:
– Read - users can only view records.
– Insert - users can insert new records.
– Save - users can save changes to records.
– Delete - users can delete records.
– All Above - grants or revokes Read, Insert, Save, and Delete
permissions for all listed applications.

84 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Note: You can filter the list of applications in the Applications table window,
which will cause any of the changes you make using the Grant or Revoke
Listed Applications buttons to affect only the applications which appear in the
table window.

The Options table window displays the options, including menu items and the
read, insert, save and delete options for the application you have selected.
4. If you want to set options for a different application, select that application in
the Applications table window.
5. In the Options table window select the check boxes for the options you want to
grant access to, or clear the check boxes to remove privileges. If you want to
select all check boxes, click Grant Listed Options for This Application.

Note: The Grant Listed Options button is not a toggle, so be sure you want
to select all check boxes before using it. To revoke all application options in the
options table window at once, you can simply revoke Read access from the
application.

Adding storerooms to security groups

You use the Storerooms tab in the Security Groups application to authorize a
group to make transactions with storerooms.

Note: In some applications, users can view storerooms even though they are
not authorized for transactions.

To authorize a group's access to storerooms:

1. On the List tab, select the group for which you want to authorize storeroom
transactions.
2. Click on the Storerooms tab (See Figure 5-8 on page 86).

Chapter 5. Security Configuration 85

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-8 The Storeroom tab

3. If you want the group to have access to all storerooms, select the Authorize
Group for All Storerooms? check box.

Note: If you select this check box, you cannot enter individual storerooms in
the Storeroom Authorization table window.

If you want the group to have access to individual storerooms:

4. Click New Row in the Storeroom Authorization table window. The Row Details
open.
5. In the Site field, enter a value or click Select Value. The Select Value dialog
box lists all sites for all organizations.
6. In the Storeroom field, enter a value or click Detail Menu to select an option
and retrieve a value. If you access the Select Value dialog box, it shows only
the storerooms for the site you specified in the Site field.
7. Click Close Details.
8. Click Save Group.
9. Click on the Labor tab (See Figure 5-9 on page 87).

Note: You can only add storerooms that your user ID allows you to access.

86 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Figure 5-9 The Labor tab

Assigning GL Components to security groups

To authorize GL Component Access to as security group perform the following:
1. On the List tab, select the group for which you want to grant GL Component
access.
2. Click the GL Components tab (See Figure 5-10)

Figure 5-10 The GL Components tab

You use the GL Components tab in the Security Groups application to

authorize which GL components a group can insert and edit in a GL account
field.
3. If you want the group to be able to access all GL components, select the
Authorize Group to Change All GL Component Types? check box. If you
select this check box, the check boxes in the GL Components table window
are no longer editable.

Chapter 5. Security Configuration 87

[Link] Draft Document for Review June 17, 2009 9:59 am

4. If you want to grant privileges to access individual GL components:

5. If selected, clear the Authorize Group to Change All GL Component
Types? check box.
6. In the GL Components table window, select the appropriate Authorized?
check box or check boxes.
7. Click Save Group

Adding Limits and Tolerances to security groups

You use the Limits and Tolerances tab in the Security Groups application
(Figure 5-11) to set approval limits for purchase requests, purchase orders,
material requisitions, invoices, and contracts; and to specify for the group how
much invoices, taxes, and services can deviate from an initial agreement.

Figure 5-11 Limits and Tolerances

To set purchasing limits and tolerances:

1. On the List tab, select the group for which you want to set limits and
tolerances.
2. Click the Limits and Tolerances tab.
3. Click New Row to create a new record, or select an organization from the
Organizations table window to edit limits and tolerances for an existing
organization.
4. In the Organization field of the new row, enter the name of an organization or
click Detail Menu to select an option and retrieve a value.

88 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Note: The Base Currency field, which is read-only, shows the Base Currency
1 for each organization. You must use this currency in setting limits.

Values in these fields default to 0 when you create a new record. A value of 0
means that the group has a limit of 0 in that field, while an empty (null) field
means the group has unlimited approval permissions in that field.

– In the Invoice Tolerance section, set as needed the upper and lower
tolerances by amount and/or percent.
– In the Tax Tolerance section, set as needed the upper and lower
tolerances by amount and/or percent.
– In the Service Tolerance section, set as needed the upper and lower
tolerances by amount and/or percent.
5. Click Save Group.

Applying Data Restrictions to security groups

You use the Data Restrictions tab in the Security Groups application to set
restrictions on what records a group can access within the larger set specified by
the privileges you grant on the Applications tab.

You can specify which records that members of a group can access. You do not
use this feature to restrict access to applications and menus, or to prevent a user
from entering data; you control those privileges from the Applications tab.

Object and attribute restrictions can be made conditionally using conditions

created in the Conditional Expression Manager.

For example, you might want to restrict a maintenance group so that they only
have access to their own personal information or to the labor in their same craft
no matter what application they are using to access the information.
– Object Restrictions - to enter a restriction that applies to an object, such as
a database table or view.
– Attribute Restrictions - to set a restriction on one database field.
– Collection Restrictions - to set restrictions on collections of assets,
locations, and configuration items.

You can set restrictions on which records a group can access. You use an
SQL-style expression or a class file to define and apply these restrictions.

To set data restrictions:

Chapter 5. Security Configuration 89

[Link] Draft Document for Review June 17, 2009 9:59 am

1. On the List tab of the Security Groups application, select the group for which
you want to set restrictions.
2. On the Data Restrictions tab, select a tab to set restrictions on either objects
or the attributes.

Note: Three types of Global Data Restrictions can be applied to security

groups:
 Hidden
 Required
 Read Only

In the table window below the tabs, click New Row to open the row details. See
Figure 5-12.

Figure 5-12 Data Restrictions

3. In the Object field, specify the table or view on which to set the restriction. In
the Attribute Restrictions tab, you can also specify the attribute that you want
to restrict.
4. In the Application field, select the application to apply the restriction to.
Leave it blank for the restriction to apply to all applications that use the object
or attribute.
5. In the Type field, select the type of restriction.
6. Select the Reevaluate? check box if you want the system to reevaluate the
restriction condition when the user moves to another field by pressing the Tab
key. If you do not select this check box, the restriction conditions are
evaluated after you save the changes to a field.

90 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

7. In the Condition field, click Detail Menu and choose either Select Value to
pick from a list of existing expressions, or Go To Conditional Expression
Manager to manage your existing expressions or create a new conditional
expression. For more information on building conditional expressions, see
Conditional Expression Manager online help.
8. Click New Row to add more restrictions on the group, or click Save Group to
apply your changes

Adding users to a security group

The Users application works in combination with the security groups when
defining security. Once the users are created you will combine these into security
groups where their security privileges are associated. A user membership to a
group is not limited in number.

To add a user to a group:

On the List tab, select the group to which you want to add a user.
1. Click the Users tab.
2. In the Users table window, click New Row. The Row Details open.
3. In the User field, enter the user ID or click Select Users to select an option
and retrieve a user ID. See Figure 5-13 on page 92.

Chapter 5. Security Configuration 91

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-13 Select Users

4. Click on the Users tab as shown in Figure 5-14.

Figure 5-14 Adding users to security groups

The system enters the associated user information in the other fields.
5. Click New Row again to add another user, or click Close Details.
6. Click Save Group.

92 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Tips:
 To add a user to a group, you must be authorized to reassign users to that
group. You do this using the Authorize Group Reassignment action in the
Select Action menu. If you have created a new group, the system
automatically authorizes you to reassign users to the group.
 If implementation uses an application server to authenticate with a
directory, you may associate users with groups in the directory or the
system, depending on your system settings.
 When you create a group, the system automatically authorizes you to add
users to the group. Users can be added from the Users tab of the Security
Groups application, or from the Users application.
 If implementation uses an application server to authenticate with a
directory, groups may be created in the directory and synchronized into the
system.

You now have a new group with no defined privileges or restrictions. You use the
other tabs and the Select Action menu to define the security for the group.

5.1.3 The Users application

You use the Users applications to add users and to manage their security
privileges. You can perform these tasks in the Users application:
 Manage user status
 Manage user sessions
 View user security profile
 Specify various user defaults, such as default insert site, default storeroom,
default language, and default General Ledger accounts for purchasing (The
default purchasing account is the General Ledger account that will be used for
Desktop Requisitions, but not for all purchasing.)
– Grant users the right to access inactive sites
– Specify which users can access a screen reader to assist in interacting
with the system
– Set system-wide security controls and new user default groups
– Change passwords (if you are using an external directory, this functionality
is not available)

Chapter 5. Security Configuration 93

[Link] Draft Document for Review June 17, 2009 9:59 am

– Create database users (if you are using an external directory, this
functionality is not available)

The Users application and the Security Groups application work together. You
use the Security Groups application to define security groups, then assign users
to one or more groups to create security profiles which control authorizations. A
user record requires a person record.

Note: A user record requires a person record.

In addition to granting rights to individual users, you can add, delete, and replace
group privileges for multiple users at one time. You can also manage user status
for multiple users. The Users application also allows you to grant a user database
access.

The Users application contains these tabs:

List: to search for user records.

User: to add, view, modify, or delete user records, including specifying several
default settings.

Groups: to specify and view the security groups to which a user belongs.

Security Profile: to view a user's security privileges to Sites, applications, and

options.

A user record can have one of the following statuses:

 ACTIVE - Default status for new records. A user record must be ACTIVE to be
able to sign in to the system.
 BLOCKED - When a user is blocked, he or she cannot log in to the system.
 DELETED - User names cannot be reused.

Note: For auditing purposes, most information for a deleted user is

removed; however the user ID is retained.

 INACTIVE - When a user is inactive, he or she cannot log in to the system.

 NEWREG - Default status for user records created by self-registration. This
status is used to identify user records to route into a Workflow process.

94 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Note: If you do chose to use self-registration for user records, a new user
can register without having any existence. A record with a status NEWREG
has a workflow, SELFREG, that notifies the user that the request is being
reviewed.

5.1.4 Start Centers

The Start Center, administrators must have access to the Start Center
customization application within signature security.
Start Centers are assigned to security groups. Therefore, the first time user log
into the system, they see a Start Center based on a template for the security
group.
If a user belongs to more than one security group, the user might see tabs at the
top of the page, where each tab is a Start Center page for a different security
group.

Note: For more information on Start Centers refer to Chapter 7, “Start Center
configuration” on page 139.

You assign or change the start center for a group from the group's record in the
Security Groups application.

To assign or change the Start Center:

1. From the List tab in the Security Groups application,
2. select the group whose start center you want to assign or change.

The system displays the Group tab.

3. In the Start Center Template field, enter the start center or click Select
Value.
4. Click Save Group.

5.1.5 Security group types

There are two types of security groups: independent and non-independent.
When a security group is created, there is an Independent of Other Groups?
option, which lets you specify if a group is independent or non-independent. If
you do not specify a group as independent, the access rights and grants in this
group are combined with access rights and grants in other groups that are also
not independent.

Chapter 5. Security Configuration 95

[Link] Draft Document for Review June 17, 2009 9:59 am

These two types of security groups provide flexibility when you build the security
infrastructure for your organization. Simple organizations might use one or two
security groups; however, larger organizations with many users and a complex
infrastructure might want to build some security groups that reflect varying levels
of application and storeroom access and approval limits.

5.2 Setting up security users

A user record must be associated with a person record. A user can associate an
existing person with a user, or use the Users application to insert a new person
ID. See Figure 5-15.

Figure 5-15 Users application

5.2.1 Default insert site

When a user creates a site-level record, the Site field defaults to the value that is
specified in the Default Insert field in the user record. When a user creates an
organization-level record, the Organization field for that record defaults to the
organization of the site that is specified in the Default Insert field in the record.
 Use the Set Security Profile action
 Specify the default insert site on a user record

96 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

In addition, a user can use the My Profile action to set their own default insert
site

Note: A default insert site is not required. However, as a best practice, assign
a default.

5.2.2 User statuses

A user record can have one of the following statuses:
 ACTIVE – Default status for new records. A user record must be ACTIVE to
log in to the system.
 BLOCKED – User cannot log in to the system. An administrator can choose to
block a user. If login tracking is enabled and the user types their user name or
password incorrectly too many times, the system can also block a user.
 DELETED – User names cannot be reused. If you delete a user record, the
user ID is retained in the database.
 INACTIVE – When a user is inactive, the user cannot log in to the system.
Inactive user records do not appear in select value lists. A user record with a
status of INACTIVE cannot be associated with new records.
 NEWREG – Default status for user records created by self-registration. This
status is used to identify user records to route into a Workflow process.

Note: When you add a user, their default status is ACTIVE.

5.2.3 Managing users

When you insert new users, they are added to a default security group called
DEFLTREG. You can set up and configure the DEFLTREG group with limited
authorizations and privileges out of the box.

The User Name field, which defaults to the new user ID you typed when you
created a user, is the login name the user uses when logging into the system.
The user ID must be unique for all user records in the system. However, you can
change the user name, which is case sensitive, to an employee number or e-mail
address.

The Security Profile tab shows the user’s security profile after the system has
combined all of the user’s security groups. Sorted by site, the security profile is
an expandable tree structure presentation of the user’s virtual profile.

Chapter 5. Security Configuration 97

[Link] Draft Document for Review June 17, 2009 9:59 am

You use the Users applications to add users and to manage their security
privileges. You can perform these tasks in the Users application:
 Manage user status
 Manage user sessions
 View user security profile
 Specify various user defaults, such as default insert site, default storeroom,
default language, and default General Ledger accounts for purchasing (The
default purchasing account is the General Ledger account that will be used for
Desktop Requisitions, but not for all purchasing.)
 Grant users the right to access inactive sites
 Specify which users can access a screen reader to assist in interacting with
the system
 Set system-wide security controls and new user default groups
 Change passwords (if you are using an external directory, this functionality is
not available)
 Create database users (if you are using an external directory, this functionality
is not available)

The Users application and the Security Groups application work together. You
use the Security Groups application to define security groups, then assign users
to one or more groups to create security profiles which control authorizations.

In addition to granting rights to individual users, you can add, delete, and replace
group privileges for multiple users at one time. You can also manage user status
for multiple users.

The Users application contains these tabs:

 List: to search for user records.
 User: to add, view, modify, or delete user records, including specifying several
default settings.
 Groups: to specify and view the security groups to which a user belongs.
 Security Profile: to view a user's security privileges to Sites, applications,
and options.

Adding a new user

A user record contains the user ID and password. You create records for users in
the Users application. User records cannot be created without a corresponding
person record. You create person records either in the People application or in
the Personal section in the User application.

98 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine

Draft Document for Review June 17, 2009 9:59 am [Link]

Note: As a best practice, create person records before you create user
records. You create person records in the People application. When you
create a user record, the application checks for a corresponding person record
by trying to match a user ID with a person ID. For example, if you create a user
record for JSmith, the system checks for a corresponding person ID, JSmith, in
the person table. If a corresponding person record is not found, the application
notifies you

Perform the following to add a user:

1. On the toolbar, click the New User icon.
2. If the User field is empty, type a user identifier. This identifier must be unique
within the database. The application checks to see if there is a corresponding
person record that matches the user ID.

Note: If you use autonumbering, the User field is populated.

3. If no matching person ID is found, select one of the following options:

• To have the software create a person record from the information
recorded in the Personal section of the user record, click Yes.
• To select an existing person record, click No, specify the value in the
Person field
• To create a person record manually, click No, in the Person field click
on the Select Value then Go to People.

Note: You could have a User ID that you want to associate with a different
person ID. For example, an employee marries and changes their last name,
and last name is used as their person ID. You use the Change Person action
to change the association between the user ID and the person ID.
You cannot associate a person ID that is already a user with a second user ID

4. In the Type field, click Select Value and select the license type.

Note: The system has user types 1 through 10. In the USERTYPE domain,
update the descriptions to reflect the types of users in the license. The
appropriate type must be associated with each user ID to ensure license
compliance. These values can be modified in the DOMAINS option under
System Configuration → Platform Configuration (Figure on page 100).

Chapter 5. Security Configuration 99

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-16 Synonym Domain

5. The User Name field defaults to the ID name in the User field, but you can
type a different value. The user types a user name to access the system.
6. Click Set Password. The Set Password dialog box opens.
a. Select one of these options:
• To generate a random password, click Generate Password.
• To specify a particular password, type the password in the Password
field and re-type it in the Confirm Password field.
b. To send an e-mail message to the user containing their password, select
the E-Mail Password to User? check box. To be able to send an e-mail to
a user, e-mail must be enabled and the user must have an e-mail address
in their person record.

Note: The E-Mail Password to User? option is selected and read-only when
the Always E-mail Generated Passwords to Users (Never Display on Screen)
option in the Security Controls dialog box is selected.

The E-Mail Password to User? option is editable when the Allow Generated
Passwords to Be Displayed on Screen option in the Security Controls dialog
box is selected.

100 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

c. If you do not want to force the user to change their password when they
initially sign in, clear the Password Should Expire After First Login?
check box. This check box is selected by default.
d. Click OK to close the Set Password dialog box.
7. If appropriate, enter additional personal data about the user in the Personal
section. The system uses this information to create a user record.
8. If appropriate, specify default settings for the user in the User Settings
section.

Note: As a best practice, assign a default insert site. Without a default insert
site, many applications will not function. For example, you will not be able to
insert purchase orders or labor records in an application that is defined on site
level

9. If appropriate, you can type one or more General Ledger accounts as a

default purchasing account.
[Link] Save User. The application assigns the user to the default security
group.

Note: A new user has no security authorizations until you assign them to
security groups.

Assigning a user to a security group

Note: You can only add security groups that you have been authorized to
manage. You use the Authorize Group Reassignment action to grant
someone the ability to assign users to security groups. Depending on your
security structure, an administrator authorizes you or you can authorize
yourself.

To assign a user to a security group proceed as follows:

In the Users application, display the record that you want to assign to groups.
See Figure 5-17 on page 102.

Chapter 5. Security Configuration 101

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-17 Users list

[Link] the Groups tab.

[Link] the Groups table window, click New Row.
[Link] the Group field, type a group or click Select Groups to select an option
and retrieve a group. See Figure 5-18 on page 103.

102 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

Figure 5-18 Assignment to security groups

[Link] steps 3 and 4 as necessary to enter more groups.

[Link] Save User.

Security profile tab

You use the Security Profile tab to view a read-only view of the user’s combined
security profile. The authorization of the user is presented in an expandable tree
view. If the node has a plus sign (+), you can expand the node to view specific
authorizations. The security profile reflects the highest level of rights as a result
of the combination of all security groups to which the user belongs.

The first level of the tree contains two different types of nodes or branches, as
shown in Figure 5-19 on page 104.
 System level applications - The System level node contains System-level
applications. You can expand each application to view the actions that the
user has been authorized to use.
 Sites - These nodes contain authorizations that correspond to the tabs in the
Security Groups application: Applications, Approval Limits, GL Components,
Labor, Restrictions, Storerooms, and Tolerances. You can expand each
authorization to view the details of the user’s security authorization.

When you add or modify the groups to which a user belongs, you must save the
record before you can see the modifications on the Security Profile tab.

Chapter 5. Security Configuration 103

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-19 Security Profile tab

To set security profiles for a user proceed as follows:

1. In the Users application, display the user whose profile you want to set.
2. From the Select Action menu, select Set Security Profile. See Figure 5-20
on page 105.

104 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

Figure 5-20 Set Security Profile

3. In the Update Groups section in the Set Security Profile dialog box, select one
of these options in the Group field:
a. Add - Adds the groups to the profiles of the selected user. If the groups to
be added exist in the selected user's profile, the record is not updated.
a. Remove - Removes the groups from the profiles of the selected user. If a
selected user's profile does not include the groups to be removed, the
record is not updated.
a. Replace - Replaces all groups in the profiles of selected user with the
groups you specify here. All of the user’s groups are removed and
replaced with the specified groups.
4. In the Groups table window, click New Row.
5. In the Group field, type a group or specify a value. See Figure 5-21 on
page 106.

Chapter 5. Security Configuration 105

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-21 Set Security Profile options

The Independent of Other Groups? check box is read-only. You set this value in
the Security Groups application.
6. If necessary, click New Row again to specify additional groups.
7. In the Update User Defaults section, select the Edit? check box above a field
to make the field editable. Type new defaults as needed.
8. Click OK

To modify security profiles for multiple users:

1. In the List tab, query for the records whose profile you want to change.
2. At the bottom of the Users table window, select the Select Records check
box.
3. Select the check boxes for the user records whose profile you want to change,
as shown in Figure 5-22 on page 107.

106 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

Figure 5-22 Records selection

4. From the Select Action menu, select Set Security Profile. In the Set Security
Profile dialog box, the Records Being Updated field displays the number of
selected users.
5. In the Update Groups section, in the Group field, select one of the following
options:
a. Add - Adds the groups to the profiles of the selected users. If the groups to
be added exist in the selected user’s profile, the record is not updated.
b. Remove - Removes the groups from the profiles of the selected users. If a
selected user's profile does not include the groups to be removed, the
record is not updated.
c. Replace - Replaces all groups in the profiles of selected users with the
groups you specify here. All of the user’s groups are removed and
replaced with the specified groups.
6. In the Groups table window, click New Row.
7. In the Group field, type a group or click Detail Menu to specify a value.

Chapter 5. Security Configuration 107

[Link] Draft Document for Review June 17, 2009 9:59 am

8. The Independent of Other Groups? check box is read-only. You set this value
in the Security Groups application.
9. If necessary, click New Row again to specify additional groups.
[Link] the Update User Defaults section, select the Edit? check box above a field
to make the field editable. Type new defaults as needed.
[Link] OK to display the number of records that have been updated.

Security Controls action

You use the Security Controls action to specify the following defaults for new
user records:
 Default security group for new users - New users are automatically assigned
to a security group, which defines their security permissions until they are
assigned to additional groups. The default group is DEFLTREG. The
permissions for this group are limited to access to the Start Center and
permission for the user to change their own password.
 Default status for new user records - The default status is NEWREG. This
status allows you to search for new user records, or to route them into a
Workflow process.
 Group for all users - The default security group for global permissions is
EVERYONE. When you select Group for All Users in Security Controls, the
user is added to EVERYONE.
 Electronic signature dialog - When you select Display User ID in the
Electronic Signature Dialog? in Security Controls, the system displays the
user ID in the dialog box, and prompts the user to enter their password.

You can access the Security Controls action from either the Security Groups or
the Users applications.

To set new user defaults:

1. From the Select Action menu, select Security Controls. The Security
Controls dialog box opens.
2. In the User Defaults section, specify the following defaults:
– In the Default Group for New Users field, enter the name of the group or
click Detail Menu to select an option and retrieve a group.
– In the Initial Self-Registered User Status field, enter a user status or
click Select Value.
– In the Group for All Users field, enter the group for global permissions
(the default is EVERYONE) or click Detail Menu to select an option and
retrieve a group.

108 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

– Select the Display User ID in the Electronic Signature Dialog? check

box to display the user ID in the dialog box when the system prompts
users to enter their password.

Note: If you implement electronic signatures, you must enable Login Tracking.

3. Click OK.

Note: If implementation uses an application server to authenticate with an

external directory (via LDAP), you will not use the system to perform some
functions. These functions include:

– Self registration - This function is not supported in conjunction with an

external directory.
– Setting or changing passwords and password hints - All password-related
functions are managed by the directory.

5.3 Setting up authentication

Tivoli process automation engine can use two different types of authentication:
LDAP (Lightweight Directory Access Protocol) and native authentication.

5.3.1 LDAP authentication

You can authenticate users against LDAP using Microsoft Active Directory. If your
organization has Virtual Member Management (VMM) in place, consider using it
to perform your authentication.

When you configure the application server to authenticate against an Active

Directory, you create and manage users in the LDAP directory server. The VMM
cron task updates the Maximo database when users, groups, and
groupmembership are changed in the directory server. When users and groups
are deleted from the Active Directory, they are not deleted from the Maximo
database because these records might be needed for auditing purposes.

You can also configure the system to populate person, user, and group
information from the external directory. The system currently supports
synchronization of information from Microsoft Active Directory.

Synchronization with other directories is possible, but is not supported as a

standard feature and might require programming to configure.

Chapter 5. Security Configuration 109

[Link] Draft Document for Review June 17, 2009 9:59 am

5.3.2 Native authentication

You can use the native authentication provided with the system to authenticate
users and verify their identity and security authorizations.

A user types a login ID and password in the Welcome page. The security
functions validate whether the user ID and password exist in the database. The
user is granted access to applications, actions, and data based on the security
groups with which their user ID is associated.

In addition, when the security services load at system startup, they perform the
following actions:
 Verify if Login ID is blocked or inactive
 Authenticate Login ID and updates password history (if configured)
 Establish user’s default insert Site, Organization, and Person ID
 Establish the user’s language, locale, time zone, and Start Center ID
 Route any Workflow assignments to the user’s inbox (if Workflow processes
are enabled)
The following procedure is the most common way to authenticate application
access:
1. At the Web client login screen, users type a login ID (in the User Name field)
and password.
2. Security services validate users’ credentials against the Maximo database.
This validation uses Java encryption to check the user in the Maximo
schema/database.
3. The system checks users’ security profiles. Based on the authorizations that
they contain, the system grants users access to the applications.

5.3.3 Application server authentication

You can use application server security with an external authentication
mechanism, such as LDAP to authenticate users. LDAP is a set of protocols to
access information directories.

The system uses application server security with an external authentication

mechanism. System installation enables WebSphere Application Server security
by default.

Depending on the product offering, application server security might be enabled

by default.

110 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

The system is built using J2EE technology, which requires a commercial

application server. The system uses WebSphere Application Server or WebLogic
Server.

5.4 Conditional security overview

You can configure the system to meet different user requirements. The system,
provides a function that enhances the user interface and give access to data
based on user groups, by evaluating of one or more conditions.

In the system, you can use data restrictions to limit the data to hide entire records
or to make them read-only. You can also create data restrictions at the attribute
level and make them hidden, read-only, when required. Because these data
restrictions exist at the data level, they apply to any user interface element or
application that uses an object or attribute.
The following information can help you determine the best place to create the
restrictions:
 Data restrictions always win over application configurations in the Application
Designer application. For example, if an attribute has a data restriction that
makes it read-only, the Application Designer application can never make that
attribute editable. The hierarchy is:
– Database configuration
– Data restriction
– Application Designer application
 Configurations that you create with data restrictions apply everywhere an
attribute is used, while Application Designer configurations does not. For
example, you want to restrict access to a field that appears in the header
section of multiple tabs. If you put a data restriction on the attribute, all of the
fields inherit the restriction. If you configure the same restriction in the
Application Designer application, apply the same configuration to each field
on each tab.
 Configurations using Application Designer are always for one application.
Configurations that use data restrictions can apply either to all applications
that use the object/attribute or to one specific application.

Note: A data restriction created on an object does not apply to views of that
object. Create a separate restriction for the view.

Chapter 5. Security Configuration 111

[Link] Draft Document for Review June 17, 2009 9:59 am

5.4.1 Conditional Expression Manager

The system has a condition library. Within this library, a user can define
conditions, either as expressions or as custom class files that you can use to
drive application behavior. You can use conditions within the library for
conditional option access, data restrictions, and conditional user interface. The
expressions for these conditions use a syntax that is like SQL, but that uses bind
variables for reusability.

The Conditional Expression Manager application facilitates the management of

these conditions. You can use the Conditional Expression Manager application to
define conditions used in data restrictions and elsewhere in the system. Using
this application, you can create and maintain a library of conditions.

When the expression evaluates to true, conditions let you configure access to
fields, tabs, and other user interface controls within applications. For example,
you can set the following types of conditional access:
 Give read-only access to information displayed in a field
 Give read-write access to information displayed in a field
 Give a user group read-only access to a specific field in an application
 Give all members of a user group read-write access to a specific application
 Do not display a field or tab in an application to certain users

You can also set access to application options, controls, or data elements.
Examples include:
 Grant access to application options in the Select Action menu for a security
group
 Configure any property in a control for a group, such as making a control
hidden, masked, read-only, or required
 Configure other properties, such as color, label, and application link, to differ
according to group and different conditions
 Show or hide a data attribute globally or for a security group

Creating and using a Conditional Expression

You use the Conditional Expression Manager application to define conditions
used in data restrictions. The system uses a syntax like SQL. However, the
syntax of the system uses additional variables.

You can create a condition in the Conditional Expression Manager application. In

the example below we will illustrate the behavior of an application using the

112 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

Conditional Expression Manager function. We will only allow the assets of type
IT to be listed in the Asset application.

The current asset list looks as shown in Figure 5-23.

Figure 5-23 Assets list

To create a condition:
1. In the Conditional Expression Manager application, All Conditions table
window, click New Row. The Row Details opens. For our example we have
used the following:
• Condition = ITASSET
• Description = Asset type is IT
• Type = Expression
• Expression = :assettyp = ‘IT’
2. Type a value in the Condition field. By default, the condition is assigned a
number. You can, however, modify this field. See Figure 5-24 on page 114.
3. Type text in the Description field.
4. In the Type field, specify a value or click Select Value to choose a type.
5. In the Expression field, click SQL Expression Builder to build a condition.
The SQL Expression Builder dialog box opens.

Chapter 5. Security Configuration 113

[Link] Draft Document for Review June 17, 2009 9:59 am

Note: The value that you specified in the Type field determines whether you
can edit the field or if it is read-only. If you selected Class in the Type field, the
Expression field is read-only. If you specified Expression in the Type field,
then you can edit the Expression field

6. Enter a file name in the Class field. The file must be in a folder under the root
of the product installation.

Figure 5-24 Conditional Expression Manager

Note: The value that you specified in the Type field determines whether you
can edit the Class field or if it is read-only. If you selected Expression in the
Type field, the Class field is read-only. If you specified Class in the Type field,
then you can edit the Class field.

7. Click Save Condition Expression.

Note: The Reference Count field is not editable. The value in this field
automatically increments when the condition is specified in another
application.

8. Go to Security Groups
9. On the object Restrictions sub-tab, select New Row to create a new data
restriction
• Object = ASSET
• Application = Null
• Type = Qualified
• Reevaluate = checked (this is the default)

114 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

• Condition = ITASSET (This is the conditional expression created

above). See Figure 5-25.

Figure 5-25 Conditional UI for security groups

[Link] out then log in again as the user whom the security group this restriction
applies to. Only “IT Assets” will be displayed, as shown in Figure 5-26.

Figure 5-26 Conditional expression list

Creating a Signature Option

In the example below we will use the Signature Option to modify the outlook of
the Asset application by showing and hiding the Safety tab based on the security
groups.

To create a SIGOPTION proceed as follows:

1. Go to Application Designer and open the application

Chapter 5. Security Configuration 115

[Link] Draft Document for Review June 17, 2009 9:59 am

2. Create a SIGOPTION called ‘SAFTAB’ with the description ‘Safety Tab’

3. Navigate to the Safety Tab of Assets
4. Open the control properties dialog and add SAFTAB signature option to the
control. See Figure 5-27.

Figure 5-27 Signature option

5. Go to Security Groups.
6. Find the security group you are intending to use then go to the Applications
tab.
7. Select Asset application.
8. Find the Safety tab option and Grant it. See Figure 5-28 on page 117.

116 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 9:59 am [Link]

Figure 5-28 Security Groups for SIGOPTION

9. Logout and Login as the user belonging to the security group to whom the
condition applies. You will notice that the safety tab do not display, as shown
in Figure 5-29 on page 118.

Chapter 5. Security Configuration 117

[Link] Draft Document for Review June 17, 2009 9:59 am

Figure 5-29 Sigoption for Asset tab

118 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

Chapter 6. Migration Configuration

This chapter will provide some basic guidelines for the Integration Framework for
data exchange with external systems followed by the Migration Manager
application. The functionality described in this chapter is in the context of the
Certification Test, therefore for a more detailed documentation please refer to the
Migration Manager Guide at
[Link]
=/[Link].doc_7.1.1/ccmdb_welcome.htm.
This chapter has the following sections:
 “Integration Framework” on page 120
 “Basic integration configuration” on page 121
 “Migration Manager” on page 127

© Copyright IBM Corp. 2009. All rights reserved. 119

[Link] Draft Document for Review June 18, 2009 10:20 am

6.1 Integration Framework

The Integration Framework includes the Maximo adapter which are part of IBM
Tivoli process automation engine and are provided with IBM Tivoli Maximo Asset
Management, IBM Tivoli Change and Configuration Management Database
(CCMDB), IBM Tivoli Service Request Manager (SRM) and IBM Tivoli Asset
Management for IT (TAMIT).

Furthermore, IBM provides additional add-on adapters to Maximo Asset

Management for Oracle® and SAP® applications which can be implemented
within the Integration Framework. This add-on to Maximo provides an end-to-end
integration solution, thus enabling business to more quickly and easily connect
Maximo Asset Management to their Oracle or SAP suite and leverage approved
integration tools and processes on both ends.

The different components of an Integration Framework solution can be arranged

in a layered 'stack' in a way that each layer builds on the layers below. The object
structure is the basis for applications and adapters to communicate. It is used to
define message content encapsulating business objects. The processing layers
operate on top of the object structure to transform, and standardize messages
between Maximo data exchange format and an external system’s data exchange
format.

The Integration Framework, as shown in Figure 6-1 on page 121, comes with
advanced integration functionality, including:
 A real-time engine for real-time inbound Web services queries.
 Synchronous and asynchronous Java Message Service (JMS) based
message exchange.
 Ability to build, transform, and customize message content
 Means to configure, predefine, and create new integration definitions based
on Maximo’s out-of-the box pre-configured integration contents:
– Object structures
– Publish channels
– Enterprise services
– External system (EXTSYS1)
– Adapter (MAXIMO)
– Endpoints
 Defining and managing multiple integration triggers, message format (XML
Flat File, Integration Table) and systems.

120 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

 Real-time user notifications and alerts on integration issues.

 Rules-based message processing and routing through a rules engine. The
rule processor can act on message values, destination and sending system
processing rules.
 Running as a native Maximo application server component for tighter
alignment with enterprise service bus architecture and better
performance.(See Appendix 6-1, “Integration Framework overview” on
page 121)

Figure 6-1 Integration Framework overview

6.2 Basic integration configuration

Basic configuration tasks involve:
– Validating system properties
– Validating queue and cron setup.

Chapter 6. Migration Configuration 121

[Link] Draft Document for Review June 18, 2009 10:20 am

– Validating Web Services/Schema setup

– Validating Security setup

We will briefly go through the options of the Integration module. To view these
modules click on Go To → Integration (See Figure 6-2).

Figure 6-2 Integration module

6.2.1 Object structures

The object structure is the building block of the Integration Framework that lets
integration applications perform the following functions:
 Publish and query application data
 Add, update, and delete application data via the following operations:
– Sync
– Create
– Update
– Delete

122 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

– Query
 Import and export application data
Each Integration Object consists of:
 Persistent
 Non-Persistent
 User defined field

The product includes various pre-defined object structures out of the box to
facilitate the development of integration contents. In creating object structures,
instead of having to create new components, duplicate and use the existing.

Configuring object structures

Use the Object Structure tab in the Object Structures application (Go To →
Integration → Object Structures) to perform the following configuration
activities:
1. Create an object structure.
2. Add the system objects to the object structure.
3. Assign the processing classes (inbound or outbound) to the object structure.
4. Specify whether the object structure supports a flat file representation.
5. Restrict object structure supported operations to QUERY.
6. Use the Select Action menu in the Object Structures application to perform
the following configuration activities:
a. Configure the column aliases to resolve alias conflicts in the object
structure.
b. Include and exclude the system object columns from the object structure.

6.2.2 Publish channels

Publish channels are used to create and manage asynchronous outbound data
flow from the integration framework to an external system.(See Figure 6-3 on
page 124).

The publish channel provides the Integration Framework to:

 Transform object structures to service input
 Associate an End Point
 Transform service response to object structures
Events that initiate publish channel processing are:

Chapter 6. Migration Configuration 123

[Link] Draft Document for Review June 18, 2009 10:20 am

 Object events (insert, update, and delete)

 Application-initiated calls
 Data export.

Figure 6-3 Publish channels

The publish channel can use the following processing layers to map the XML to
the external system XML:
 Processing class
 User exit class
 XSL map file

The publish channel can apply any specified processing rules to objects before it
saves the objects. Processing rules are used to access and retrieve pertinent
data from objects which are not included in the object structure.

You can override the behavior of predefined data processing that the enterprise
service supports through the integration controls. This integration control
behavior are implemented through enterprise service processing rules and Java
processing classes.

6.2.3 Invocation channels

The Invocation Channels application is used to create and manage synchronous
(does not go through the outbound queue) outbound data flow from the

124 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

Integration Framework to an external system. The invocation channels is similar

to publish channels but it is initiated via a Custom Action Class (Java). (See
Figure 6-4)

Figure 6-4 Invocation channels

6.2.4 Enterprise services

You use the Enterprise Services application to create, view, modify, or delete
enterprise service records.

An enterprise service is the pipeline for importing data to the integration

framework from an external system. Enterprise services processing can be
triggered by the following system events (event driven) or user actions
(user-driven):
– Scheduled cron tasks
– User initiated queries
– Data Import

The content of an enterprise service data structure is based on the content of the
associated object structure. When you trigger enterprise service processing, the
system moves the integration framework message data into the inbound queue.

Chapter 6. Migration Configuration 125

[Link] Draft Document for Review June 18, 2009 10:20 am

If necessary, you can use the object structure processing rules to define
conditions under which the integration framework can skip or stop a message.
When you use processing rules, you also can change data in the enterprise
service, before the creation of the objects. You can achieve this task without
having to use Java class files.

You also can alter the logic of predefined inbound processing, inbound channel
mapping, and event filtering through the use of Java class files. These alterations
are specific to the enterprise service record and overwrite any predefined
processing logic you define at the object structure level.

The Enterprise Service application contains the following tabs:

 List: to search for enterprise service records.
 Enterprise Service: to add, view, modify, or delete enterprise service
records.

6.2.5 External systems

External systems let you synchronize inbound and outbound data through the
enterprise services and publish channels, respectively.

6.2.6 End Points

Outbound transactions (publish channels or invocation channels) for your
business processes need endpoint values. The endpoints specify how the
transactions are delivered and the handler that will route the transactions to the
endpoint.

6.2.7 Importing data

The following steps describe the inbound process that uses the data import
feature. Before importing data, be sure to cross check all fields and data for
validity.
1. The Integration Framework checks that the external system and the
enterprise service are valid and enabled. If you are importing flat files, the
integration framework also checks that the enterprise service object structure
supports flat structures. If the verification fails, the integration framework
issues an error and does not process the message.
2. If the verification is successful, the integration framework identifies the
inbound JMS queue that is assigned to the enterprise service and the
external system.

126 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

3. The integration framework writes the message to the inbound queue. If the
message contains multiple instances of a document, for example, if a single
message contains 10 person records, the application writes 10 messages to
the queue. If one of the referred records has a processing error, a single
message processing exception is identified and none of the other messages
that can be successfully processed are committed to the database.
4. The integration framework updates the message header with the external
system and enterprise service names. You have the option to preview the
data that you want to import to check the format and the data validity of a
source file. It is a synchronous validation mechanism that presents all the
source file processing errors without committing data to the database.
The preview data process verifies that the data structure of the selected file
complies with the integration XML or flat file definitions.

6.2.8 Integration Framework summary

With the Integration Framework platform, you can connect Maximo with other
external system using different integration mediums such as: file systems,
databases, message queues and Web services. This allows for bidirectional
synchronous and asynchronous data exchange more easily and effectively.
Another benefit of Integration Framework is the vast array of pre-defined
out-of-the box integration libraries that support various integration scenarios
between Maximo and external system, thus allowing for quicker implementation
with less complex integration procedures.

The Integration Framework is used to create and manage integration modules.

The Integration Modules application provides a mechanism for a process
management product, such as a Change or Release, to call an external
operational management product.

6.3 Migration Manager

In the context of Migration Manager, migration is the process of promoting
product configuration content from one product environment to another.
Configuration content is the data that the system requires to construct and run a
business application in the application server and make it available to end users
in the enterprise. Product environments can include development, test, and
production.

For example, you might want to extend the Purchase Order application by
making the following configuration changes:

Chapter 6. Migration Configuration 127

[Link] Draft Document for Review June 18, 2009 10:20 am

 Add a new table and several columns to the database (using the Database
Configuration application)
 Add a new domain that contains several lookup values (using the Domains
application)
 Add a new tab in the Purchase Order application screen presentation (using
the Application Designer application)
 Develop a workflow process to automate an approval of data managed
through the new table (using the Workflow Designer application)

All of the preceding configuration changes are product configurations that are
typically created in a development environment and promoted to production.

6.3.1 Overview
Migration Manager is a set of applications that enables a structured set of steps
to promote your configurations from one product environment to another.
You can use the Migration Manager to perform the following tasks:
 Organize and consolidate all the configurations and customizations for a new
product environment.
 Promote your configurations from a development environment to a test
environment for validation.
 Promote your validated configurations from a test environment to a production
environment.

6.3.2 Migration Manager concepts and components

In this section you will learn about the details of Migration Manager concepts and
components.

Package definitions and packages

You manage the configuration content that you want to migrate in the form of
package definitions and packages. This configuration data that you have grouped
together will constitute the configuration data in the form of a package. A
package is an instance of a package definition. A package definition serves as a
template from which you create unique packages. A package definition organizes
the content to be migrated.

A package contains data either from the product database or from files that are
deployed on the application server. Data from the product database is organized
in migration objects and migration groups. Files are organized as compiled

128 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

sources.

Note: The batch size of a package which is the number of records at a time
that are retrieved at one time from each object in a migration group. The
default value is 100.

Package contents
A package contains the following:
 Package manifest - contains important information about a package, such as
the source environment versions, the migration objects whose data is
included in the package, the types of content in the package, the record count
for each migration object, and README information entered in the source
environment by an administrator to help during deployment to a target
environment.
 Package metadata - defines metadata information that pertains to the
package definition of the package to be deployed in a target environment
 Structural configuration content - data that must be used to create or update
database tables, columns, views, keys, indexes and sequences
 Non-structural configuration content - configuration content that resides in the
form of records of various configuration tables
 Compiled sources - files that include source code customizations, libraries,
configuration files, and report executable files
 History data - life cycle information regarding the package

Types of package definitions and packages

There are two types of package definitions and packages:
 Package
 Change

A snapshot package contains “as is” configuration content collected for a

package on demand. You define the snapshot package at any time, even after
the configuration changes have been made.

A change package contains configuration content collected over a period of time.

The data collected is based on database inserts, updates and deletes that occur
between the time you activate the package definition and the time that you create
the package. A change package can contain configuration records inserted,
updated, or deleted by designated users. You define the change package before
the changes occur.

Chapter 6. Migration Configuration 129

[Link] Draft Document for Review June 18, 2009 10:20 am

6.3.3 Migration objects and migration groups

Configuration content is organized into migration objects and migration groups.

Migration objects
A migration object is a group of one or more related business objects that
represents one or more database tables (for example, workflow process, action,
role) You define migration objects in a development instance and then move
them into test and production environments. The product includes a
comprehensive set of migration objects. Migration objects are implemented using
the Object Structures application. You can also create your own migration objects
using this application.

Migration groups
A migration group is a collection of related migration objects. It allows one to
organize and group configuration content that will need to be migrated. A
migration group can be either internal or user-defined. Internal migration groups
are included with the product and are linked to other logically related migration
groups called dependencies. You cannot modify internal migration groups.
User-defined migration groups are migration groups that you create.

Note: You can select which Migration Groups are to be migrated

6.3.4 Compiled sources

You can include compiled sources in a package definition.

Compiled sources define content from outside the database that packages
contain when they are migrated. Compiled sources are files that must be part of
the Enterprise Archive (EAR) file of the product. They can include many types of
files, such as class files, archive files, image files, and properties files. They can
also be aggregations of files from the server file system that must be migrated
with configuration data from the database.

If you need to migrate multiple compiled source files, aggregate them into a
single compressed file to simplify the migration process.

Sources and target environments

The environment from which you are migrating content is the source
environment. The environment to which you are migrating content is the target
environment. Migration Manager identifies sources and targets uniquely across
all of your product environments. Migration Manager generates this identification

130 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

in the form of a string comprising three parts. The identification is the

combination of the database host name, the database identifier, and the
database schema name.

A package definition can be associated with any target. However, you can set
inbound restrictions in a target environment to prevent the distribution and
deployment of packages to that environment from restricted sources.

6.3.5 Migration Manager applications

Migration Manager consists of the following three applications. These
applications are in the Migration module, which is in the System Configuration
module of the product:
 Object Structures
 Migration Groups
 Migration Manager

Object Structures application

You use the Object Structures application to view, create, and modify an object
structure. One or more related business objects comprise an object structure. A
business object is an object-relational representation that corresponds to a
database table of the product. You can use the object structures that are included
with the product, or you can create custom object structures to meet your
business needs.

Figure 6-5 Object structure application

Chapter 6. Migration Configuration 131

[Link] Draft Document for Review June 18, 2009 10:20 am

Migration Groups application

You use the Migration Groups application (Figure 6-6) to view, create, modify or
delete a migration group. One or more migration objects (object structures)
comprise a migration group (Figure 6-7 on page 133). You can include one or
more migration groups in a package.

Each migration group can be linked to other related migration groups. This
relationship between migration groups is called a dependency.

Figure 6-6 Migration groups application

A dependency ensures that all dependent configuration content is collected from

source environments and distributed to target environments.

132 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

Figure 6-7 Content of a migration group

Migration Manager application

You use the Migration Manager application, as shown in Figure 6-9 on
page 134 to migrate your configuration content between product environments.
You use this application in both your source and target environments. In a source
environment, you define, create, and distribute packages. In a target
environment, you deploy packages.

You specify the type when you create a package definition. Every package that is
created from a package definition is of the same type as the package
[Link] types of packages can be defined in the Migration Manager
application. See Figure 6-8 on page 134.
 Snapshot™
 Change

Chapter 6. Migration Configuration 133

[Link] Draft Document for Review June 18, 2009 10:20 am

Figure 6-8 Types of packages

Figure 6-9 Migration Manager application

134 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

6.3.6 Migration planning

You need to determine the types of configuration changes, You will be organizing
tasks by affected configuration applications, for example you will be grouping all
screen presentations tasks under the Application Designer application.

Another aspect when planning the migration is the organization of your

configuration content. Configuration content can come from two types of
sources:
 Content in the database
 Content outside the database

Note: Migration Manager gives you the flexibility to have all or a subset of your
configurations defined, created, distributed and deployed at a time.

6.3.7 Migration flow

You migrate the configuration content in four stages as depicted in Figure 6-10.

Figure 6-10 Migration process flow

Note: You can migrate configuration content between any two product
environments.

The migration task flow is depicted in Figure 6-11 on page 136.

Chapter 6. Migration Configuration 135

[Link] Draft Document for Review June 18, 2009 10:20 am

Figure 6-11 Migration task flow

Note: To preserve the integrity of structural changes, you can only deploy one
package at a time to preserve the integrity of the structural change.

6.3.8 Migration Manager summary

Use the Migration Manager application to migrate configuration content from one
product environment to another. You manage the configuration content that you
want to migrate in the form of package definitions and packages. As part of your
implementation of a migration process, you use the Migration Manager
application to define and create the package definitions, and then distribute and
deploy the packages.

For example, you can migrate configuration from a development environment to a

test environment. After testing, you can migrate the configuration to a production
environment. The development environment is the source and the test and
production environments are targets. You can use this approach during the initial

136 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 10:20 am [Link]

configuration of the product or at any time when you want to change your
configuration of the product.

Chapter 6. Migration Configuration 137

[Link] Draft Document for Review June 18, 2009 10:20 am

138 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 10:04 am [Link]

Chapter 7. Start Center configuration

This chapter provides details regarding the configuration and administration of
the Start Center within Tivoli Process Automation Engine. Following the
installation an administrator and or privileged user may configure start centers to
provide shortcuts to applications, quick inserts, and display data and key
performance indicators within the portlets.

This section includes the following topics:

 Start Center templates“Start Center templates” on page 140
– Start Center permissions
– Creating a new Start Center template
– Modifying an existing Start Center template
– Modifying a portlet
– Associating a Start Center template to a security group
 Key Performance Indicators (KPIs)“Key Performance Indicators” on page 146
– Creating a KPI
– KPI Cron Task

© Copyright IBM Corp. 2009. All rights reserved. 139

[Link] Draft Document for Review June 17, 2009 10:04 am

7.1 Start Center templates

Start Center templates are configurable dashboards which provide access to the
applications, result sets, and KPIs a user or administrator would like quickly
utilize.

7.1.1 Start Center permissions

Once the installation has been completed and the system has been populated
with the necessary basic data, Start Center creation may begin.

Upon first login a user is not presented with a Start Center as one needs to either
be created or associated with their particular security group as shown in
Figure 7-1.

Figure 7-1 No Start Center to display

An Administrator such as maxadmin must now access the security groups

module to provide access to the appropriate groups who will be able to create
and modify start centers.

To access security groups, select Go To → Security → Security Groups

Within the security groups application select the group you would like to apply the
permissions to from the list tab and then select the applications tab to apply
permissions for layout and configuration as well as the necessary start center
portlets.

The following are the security group applications or as referred to within the Start
Center, portlets, associated with Start Center configuration:
 Layout and Configuration - Administrator users can modify and configure the
layout of the portlets display on the Start Center.
 Inbox / Assignments Setup - Administrators can define and edit which
columns are displayed in the Workflow assignments inbox on the Start
Center.
 KPI Graph Setup - Administrators can define and edit a KPI graph-style
portlet to display on the Start Center.

140 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 10:04 am [Link]

 KPI List Setup - Administrators can define and edit a KPI list-style portlet to
display on the Start Center.
 Result Set Setup - Administrators can define and edit the query used and
columns displayed on the Start Center.
 Favorite Applications Setup - Administrators can define and edit the list of
applications displayed in a Favorite Application Portlet.
 Quick Insert - Administrators can define and edit the list of applications
displayed in a Quick Insert Portlet.
 Quick Insert Setup - Administrators can define and edit the list of applications
in a Quick Insert portlet.
 Bulletin Board - View messages from the Maximo system.

7.1.2 Creating a new Start Center template

Once provided with access to layout and configuration, the user will have the
following options displayed on their Start Center upon login as shown in
Figure 7-2.

Figure 7-2 Layout and Configuration Options

 Change Content/Layout - You use Change Content/Layout to add, remove, or

to reconfigure the portlets displayed on your Start Center page.
 Display Settings - When you have more than one Start Center page available
to you, the system displays tabs for each page. You can set which ones
appear as tabs and which one is the default.
 Create New Template - When you create a template, it must be assigned to a
group before users in a group can access it.
 Modify Existing Template - If you have the Administrator permissions you can
modify existing templates, even if you are not currently viewing that template.
 Update Start Center - If a system administrator notifies you that they have
made changes to your Start Center template, you can update the Start Center
page. When you update the Start Center page, you will lose any
configurations that you made, for example, specific quick inserts or result
sets. If you update the Start Center page and there are no changes to your
original template, the latest changes you have made to the Start Center are

Chapter 7. Start Center configuration 141

[Link] Draft Document for Review June 17, 2009 10:04 am

discarded. Also, the template on which the Start Center was originally based
on is reapplied.
1. After selecting Create New Template you will be able to select the layout
whether it is Narrow-Wide or Wide-Narrow as well as which portlets you
would like to display and their order.
2. The user may select either the left or right column and modify the display
name as seen in Figure 7-3.

Figure 7-3 Start Center Portlet Selection

3. The portlet ordering is configured as shown in Figure 7-4.

Figure 7-4 Start Center Portlet Ordering

142 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 10:04 am [Link]

7.1.3 Modifying a portlet

Once you have selected which portlets you would like to use in the Start Center,
you will need to edit them by selecting the Edit Portlet icon as shown in
Figure 7-5.

Figure 7-5 Start Center Edit Portlet

Within each type of portlet there are several configurable options. For example
the result set portlet has the ability to select a user defined or public query and
then display it’s results with colored conditions on a bar or pie graph.

The following tabs are available within the Result Set setup:
 Available Queries - lists all of the queries from which you can select one to
display.
 Column Display - is where you select which columns to display and their
order.
 Display Options - is where you can set a color to indicate a status level.
 Chart Options - is where you set the parameters for a graph, if you choose to
display one.

For example, if the user would like to display all NEW work orders in the color red
they would configure the color parameters with an expression of equal to, an
expression value of NEW, and a color of red as seen in Figure 7-6.

Figure 7-6 Result Set Setup Color Parameters

Chapter 7. Start Center configuration 143

[Link] Draft Document for Review June 17, 2009 10:04 am

When the results are returned in the Start Center, those work orders with a
status of NEW will be shown in the color red.

7.1.4 Modifying an existing Start Center template

With the appropriate security group permissions (layout and configuration) a user
or Administrator may modify an existing Start Center template by selecting
Modify Existing Template as seen in Figure 7-7.

Figure 7-7 Start Center Modify Existing Template

1. You will be presented with the list of Start Centers you may modify as shown
in Figure 7-8.

Figure 7-8 Start Center Modify a Template

2. Select the Start Center you wish to modify and make your changes.
3. Following your modifcations, choose Save Changes to save your
modifications.

144 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 10:04 am [Link]

7.1.5 Associating a Start Center template to a security group

Start Center template assignments are driven by the users security group. Select
Goto → Security → Security Groups and then choose the appropriate group
from the list tab.

You may then populate the Start Center template field and this will now be the
default Start Center for that particular group as seen in Figure 7.2 on page 146.

Figure 7-9 Start Center Security Group

If a user is part of multiple security groups, they will see a tabbed view of these
Start Centers, as shown in Figure 7-10.

Figure 7-10 Multiple Start Center Templates

The user is able to navigate between their Start Centers and may also select to
hide of set a particular Start Center as their user default by selecting Display
Settings, as seen in Figure 7-11 and Figure 7-12 on page 146.

Figure 7-11 Start Center Display Settings Icon

Chapter 7. Start Center configuration 145

[Link] Draft Document for Review June 17, 2009 10:04 am

Figure 7-12 Display Settings

7.2 Key Performance Indicators

Key Performance Indicators (KPIs) provide the ability to track critical performance
variables over time.

7.2.1 Creating a Key Performance Indicator

In order to display a Key Performance Indicator or KPI within the Start Center one
must be first be created from within the KPI Manager application.

To access the KPI Manager select Go To → Administration → Reporting →

KPI Manager.

Within the KPI Manager select the New KPI icon on the toolbar as seen in
Figure 7-13.

Figure 7-13 New KPI Icon

To create a KPI the user must define a select statement for the query and set the
following parameters:

146 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 17, 2009 10:04 am [Link]

 Target - the target value.

 Caution At - the caution value which will be displayed in yellow.
 Alert At - the alert value which will be displayed in red.

See Figure 7-14 for an example of a KPI graph:

Figure 7-14 Sample KPI Graph

7.2.2 KPI Crontask

In order for a KPI to stay current with live data a crontask must be established to
facilitate and poll on a schedule.

To access the Cron Task Setup application select, Goto → System

Configuration → Platform Configuration → Cron Task Setup.

Out of the box a crontask named KPICronTask is available to use for keeping KPI
data current.

To enable this cron task, select the task from the list tab, then within the instance
define the schedule (default is 1 day), the administrative user to run the cron task
under, and set it to active as shown in Figure 7-15.

Figure 7-15 KPI Cron Task Instance

Chapter 7. Start Center configuration 147

[Link] Draft Document for Review June 17, 2009 10:04 am

The KPI data will now be updated on the schedule you have established.

148 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:01 pm

Chapter 8. Work management

configuration and
administration
This chapter provides the information necessary to properly configure the work
management functionalities. It goes through the applications that should be set
up before start using the system.

The following topics are described in this chapter:

 “Work order settings” on page 150
 “Setting up job plan templates” on page 156
 “Work Order module” on page 157
 “Work management capabilities” on page 160

© Copyright IBM Corp. 2009. All rights reserved. 149

[Link] Document for Review June

8.1 Work order settings

This section describes some required settings in order to start using the system
and also some useful settings for the business.

8.1.1 Organizations application

Most of the settings can be accessed from the Organizations application. From
the start center, select Go To → Administration → Organizations.

Note: All of the settings should be set up for each organization in the system.

Work order options

Select an organization that was already created in the system and open the
Work order options in the Select Action menu, as shown in Figure 8-1.

Figure 8-1 Work order options menu

Work type
The first step to configure the work orders are the work types. Without
configuring them, you will be not able to create a work order, since it is a required
field in the work order application.

150 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:01 pm

Figure 8-2 Work Type dialog

Note: Remember that the work order work types are NOT configured in the
Domains application, as usual for the value lists. Work types are set up in the
Organizations application.

Edit rules
Edit rules are tied to the work order status. Depending on the status, you are able
to edit or not some predefined fields as seen in the Figure 8-3

Figure 8-3 Edit rules dialog

Other organization options

There are other few options related to the organization that are explained in the
following sections. See Figure 8-4 on page 152.
 Default Downtime Start - Specifies which date appears by default in the start
date field when Maximo displays the downtime report message.
 Actual Start Date - Specifies the actual start date for a work order on status
changes

Chapter 8. Work management configuration and administration 151

[Link] Document for Review June

 Display Warranty Status - Specifies whether Maximo will display a message if

the asset is under warranty when entered on a work order.
 Display Downtime report prompt upon WO Completion for Asset in Down
Status - Specifies whether Maximo will display the Change Asset Status
dialog box when the work order status for a down asset changes to complete
or closed.
 Clear Material Reservation when WO status changes - Specifies when
Maximo will clear a work plan reservation used on a work order on status
changes.
 Display Duplicate Problem Warning - Specifies whether Maximo will display
the duplicate problem dialog box when a user enters a work order for an asset
or location that is already entered on another open work order with the same
problem code.

Figure 8-4 Other organization options dialog

152 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:01 pm

Note: In this section we presented a couple of options to be configured related

to reporting assets downtime. This is an important action used to keep track of
assets problems for further maintenance. It can be found in the following
applications:
 Work Order Tracking
 Quick Reporting
 Assets
 Activities and Tasks

Site options
Figure 8-5 shows settings tied to the sites included in the current organization.
The only options you can set here are the task numbering start and increment by.

Figure 8-5 Site Options dialog

Autonumber setup
Autokey feature is not only related to work management applications, although it
is an interesting and important point to be discussed since most of the clients use
it to customize the auto-numbering patterns for each type of work order.

An example of it would be a company that wants to set a different prefix on the

autonumber for each site in the organization or even to set a prefix for each type
of work order. This is a good practice for tracking and identify how the work
orders were generated.

To create or modify an autokey, open the Autonumber setup in the Select Action
menu of the Organizations application as shown in Figure 8-6 on page 154.

Chapter 8. Work management configuration and administration 153

[Link] Document for Review June

There are four types of autokeys. Each one refers to a specific object level:
System, Item, Set, Organization and Site.

Figure 8-7 on page 155 shows the dialog referring to the site level dialog as an
example, where it is possible to create and modify the autokey attributes for each
site of the current organization record.
 Seed is the starting number of the sequence.
 Prefix is the char or the word that you can set before the number, so that the
records can be identified easily.

Figure 8-6 Autonumber setup menu

154 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:01 pm

Figure 8-7 Site level autonumber dialog

8.1.2 Start Center setup for work management

This section describes useful functionality that can be set up in the Start Centers
to display the users a list of all the tickets, work orders and activities that they
own.

The Start Center is composed by portlets and each portlet has an application
that controls the content and configuration of the portlet. This section is focused
on the work management public queries.

In most of the applications you have a list tab that can be used to create queries
to be used in the Start Center. Here follows an example on how to create a query
to retrieve your tasks:
1. Select, Go To → Work Orders → Activities and Tasks
2. In the list tab, filter out the tasks you want to show in the Start Center.
3. Save the query, as shown in the Figure 8-8 on page 156.
4. Set up the query as explained in Chapter 5, “Security Configuration” on
page 77.

Chapter 8. Work management configuration and administration 155

[Link] Document for Review June

Figure 8-8 Save query menu

8.2 Setting up job plan templates

In this section we will delve into the details of creation job plan templates.

A job plan is a work template that contains detailed information about the work to
be done on an asset, item, or location. It has all the necessary info about the
work such as a task list, the labor/crafts involved and all the materials and the
tools used to perform the work.

It is useful when you need to enter the same information in the work orders many
times. Using job plans, it is not necessary to create a new work plan everytime
that a new work order is created. Applying the job plan to a work order, all the
tasks and its resource estimates are copied into the work plan for the work order.

There is some important information that you should know about the job plans:

Working with job plans allows for standardization of work orders, but it is
important to note that it doesn’t restrict the work orders to be equal to the
template.

After applying a job plan to the work order, it is still possible to modify the work
plan so that the procedures, labor, materials, services and tools are more
specific to the work order without affecting the original template.

Furthermore, job plans are at the system level, but you can optionally set an
organization and even a site for it. The same occurs for tasks, labor, materials,
services and tools.

For example, you can create a job plan at organization level, and add specific
tasks at the site level. This feature allows you to set up standardized job plans
across all sites and make that the work plan inherit specific tasks for each site.

Note: Not only tasks can be defined for a specific site. It is also possible to
define and set up the other related objects like labor, materials, services and
tools.

156 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:01 pm

To access the Job Plan application, select Go To → Planning → Job Plans.

The job plan statuses can be:

– DRAFT - Default status for new records.
– ACTIVE - Approved job plans that can be used in work orders.
– INACTIVE - Job plans that are not used in work orders anymore.

8.2.1 Job plan concepts

The following are important concepts about a job plans:
– Task is step that must be performed to complete the job. The information
that comes along with each task is the description of the work to be done
and the duration of the task. You can also attach a meter or set a nested
job plan for more complicated work.
– Craft is the necessary skill to do the job. There are some procedures that
require specialized skills like working with chemical products or electrical
current.
– Labor is the person that will perform the work. It is usually not set in the
job plans because as a template that can be reused, most planners
specify crafts rather than laborers when planning labor.
– Material is some item required to do the work like replacement parts. You
can set the quantity, the issuing storeroom and other fields like the task
that this material will be used.
– Tool should be used when you know that certain tool is needed to perform
the work, like pliers and cutters. You can set the task that requires it and
also check if a reservation for that tool is required before start the work.
– Service is necessary for example when your company cannot provide
something that you need to do the job, so that you specify the service,
quantity and the vendor that provides the service.

8.3 Work Order module

This topic describes the Work Orders module. It does not go deep into the details
of each application, but provides you an overview of the work management
capabilities and functionalities that you should know.

Work orders are the core of the maintenance management. A work order is a
request for work to be performed and this module has the applications that

Chapter 8. Work management configuration and administration 157

[Link] Document for Review June

describes the work to be done, who will do the work, and when the work will start
and finish.

8.3.1 Work Order applications

The module contains the following applications that is described in the following
sections:
 Work Order Tracking
 Labor Reporting
 Quick Reporting
 Activities and Tasks
 Assignment Manager
 Service Requests

Work Order Tracking

The Work Order Tracking application is used to create, review, approve and
manage work on assets and locations. To access it, select Go To → Work
Orders → Work Order Tracking.

The application has the following important tabs:

 List - to search for existing work order records.
 Work Order - to add, view or modify information related to the assets and/or
locations needed, scheduling, job plans and PMs.
 Plans - to add, view or modify information related to the work order children,
tasks needed to perform the work and all the material, labor, services and
tools associated to the work order.
 Related Records - to add, view or delete related ticket and work order
records.
 Actuals - very similar to the plans tab, but used to report the actual work that
was done in the work order.
 Safety Plan - to add, view and modify safety information associated with a
work order, like hazards and precautions.
 Log - to create, view and edit Work Log and Communication Log entries.
 Failure Reporting - to enter information that helps to analyze failure trends
for the company’s assets, locations and CIs.

158 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:01 pm

Note: Entering Failure Class data is a way you can analyze failure trends for
the company’s assets, locations or configuration items.

Labor Reporting
The Labor Reporting application is used to report and keep track of the labor
hours such as type and the total number of hours of work that were performed by
external or internal employees.

Quick Reporting
The Quick Reporting application is a simplified version of the Work Order
Tracking application that was designed to simplify reporting the actuals and other
data after the work has been completed.

Activities and Tasks

The Activities and Tasks application is a subset of Work Order Tracking
functionality to support single task specific work orders.

It is used to review and manage activities and tasks created by the other
applications. It is important to know that an activity or a task does not exist by
itself, so you are not able to create records from this application.

Activities are created from the Service Desk module in the Incidents and
Problems applications while Tasks are created in the Work Order tracking.

Assignment Manager
The Assignment Manager application is used to manage work schedules, labor
requirements and dispatching of the work.

You can view work order assignments, labor craft and skill levels. Dispatch labor
according to work priority and schedule work according to labor availability. It is
also possible to filter labor to match work and vice versa.

Another important functionality of the Assignment Manager application is to

record the time spent by the labor in the task. It can be done by the actions: Start
Assignment, Interrupt Assignment and Finish Assignment.

Service Requests
The Service Requests application is used to create, view and resolve service
requests form customers. Records created from this application are a type of
ticket.

Chapter 8. Work management configuration and administration 159

[Link] Document for Review June

Service requests in Maximo are created to resolve issues, obtain information and
obtain or change services. Either a service desk agent or a customer can create
a service request.

8.3.2 Creating work orders

This section shows several applications that can be used to create work orders
using Maximo:
 Changes -Use to create work orders related to service desk tickets.
 Condition Monitoring - Use to generate work orders to correct problem
conditions found during monitoring procedures.
 Incidents - Use to create work orders related to service desk tickets.
 Preventive Maintenance - Use to generate scheduled maintenance work
orders.
 Problems - Use to create work orders related to service desk tickets.
 Quick Reporting - Use to create work orders and report actual work done for
simple jobs, unplanned work, or work not performed by the maintenance
department.
 Releases - Use to create work orders related to service desk tickets.
 Service Requests - Use to create work orders related to service desk tickets.
 Work Order Tracking - Use to create and report on high-volume or complex
work orders.

8.4 Work management capabilities

This section describes some of the new and enhanced work management
configuration funtionalities included in Maximo V7.1 that you should know for the
exam.

8.4.1 Nested job plans

This functionality allows job plans to be nested within a hierarchical relationship.
Users can create a job plan that refers to other job plans. These plans are nested
and generate a work order hierarchy when applied to a work order (not just to
tasks). Job plans may be nested in as many levels as needed.

160 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:01 pm

8.4.2 Job plan template

Another enhancement to the Job Plan application includes the addition of the
Template Type field. This field has a domain associated with it, pre-populated
with three choices:
 Maintenance
 Activity
 Process

This is a required field for the Job Plan application.

8.4.3 Work management status flow control

Maximo V7.1 provides the capability to define precedence relationships between
work orders and tasks. This then initiates the resulting network of records
automatically applied with a finish-to-start action, thus automating the flow of
status changes between them. For example, if flow control sequencing is
enabled at the job plan level, each task generated when applying the Job Plan to
a work order evaluates the one before it to determine if it has completed. If the
predecessor has completed, its status is automatically changed to “In Progress”.
Any successive tasks may not have its status changed to “In Progress” until its
immediate predecessor has completed. As such, the status on the work order
cannot be changed to “Complete” until all tasks have been completed in the
order in which they are sequenced. When all tasks are completed, the work order
status is automatically changed to “Complete”.

Chapter 8. Work management configuration and administration 161

[Link] Document for Review June

162 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 11:16 am [Link]

Chapter 9. Reporting configuration

Reporting is an important component of the product as the information produced
will have an impact on business decisions. This chapter will discuss the reporting
capabilities of the Tivoli process automation engine.

The application is integrated with the Business Intelligence Reporting Tool

(BIRT). This open source reporting system integrates with Java/J2EE
applications and will produce custom reports.

The following are the main topics covered in this section:

 “Report administration” on page 164
 “Report configuration” on page 167
 “Running reports” on page 169

© Copyright IBM Corp. 2009. All rights reserved. 163

[Link] Draft Document for Review June 18, 2009 11:16 am

9.1 Report administration

The report administration assists the Administrator in:
 Viewing a list of reports
 Defining the reports for the end users
 Changing the names of the reports and fields
 Setting or viewing the security

As an Administrator you are allowed to specify the following for the end users:
 Making the reports available and how to open, run and print these reports
 Determining the outlook of the report titles and headings
 Setting the report security

The Report Administration contains the following tabs:

 List: To open a list of reports and perform a search on the list
 Report: To perform the following tasks
– Configure reporting options
– Delete a report
– Duplicate a report
– Import report files
– Import library files
– Preview and print reports
– Add a report to the database
– Set and view the security settings for the report
 Security: Set and view the report security

You can set the security for an application in the Report Administration.
Application security settings let you set group security for all reports in a selected
application. The Maxadmin group has access to all “out of the box” reports. You
must setup group or report access to each individual application or other new or
customized reports.

To set the application security:

1. In the Report Administration application, from the Select Action menu,
select Set Application Security. The report Application Security dialog box
opens.

164 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 11:16 am [Link]

2. Select an application name from the Application table window. Click New
Row.
3. In the Application Level Security table window you can add, change or
delete security settings for a group. Security settings are defined by report
type. For example, you can set report security so that Group A can see all
reports in the classification application.
4. Click Save.

Prior to the deployment of the application, the Administrator will carry out several
customizations, described in the following sections.

9.1.1 Generating the Requests pages

The Request pages are the parameter inputs required for each report. Before the
reports can be accessed from with the application the request pages have to be
generated. To ensure the reports will be available to users ensure the following is
carried out;
1. Login into Maximo as the System Administrator.
2. From the Start Center navigate to the Go To function and select
Administration → Reporting Administration. See Figure 3-2.

Figure 9-1 Report Administration option

3. At the bottom of the page you will see a button called Generate Request
Pages, click Generate Request Pages. A message box will be generated, as
shown in Figure 9-2 on page 166.

Chapter 9. Reporting configuration 165

[Link] Draft Document for Review June 18, 2009 11:16 am

Figure 9-2 Generate Request Page notification box

At this stage the request pages have been successfully generated.

Note: Generating the request pages is a step you will only need to execute
when you have a new installation or have uploaded a new report. It is
advisable that this step is done when other users have logged out of the
system.

9.1.2 Adding a report

This is to add a report to the database. You use the Report Administration
application to add a report.

To add a report follow the below instructions:

1. In the Report Administration application, click New Report. See Figure 9-3 on
page 167.
2. In the Report File Name, enter the name of the report, with the file
description as it has been created in the Report Designer.
3. In the Report Type field, select the type of report. To view the list of reports
click on Select Value.
4. In the Application field, enter the application that end users use to run this
report. To open a dialog box that you select contains available application
names, click Select Value. This information will determine the application from
which the end user can access the report a well as the attribute names of any
report parameters.
5. Select the Report Folder field. This field defaults to the value you enter in the
Application field.
6. Click Save Report.
7. Click Generate Request Page to apply the changes.

166 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 11:16 am [Link]

Figure 9-3 Adding a report

9.2 Report configuration

As shown in Figure 9-4, several options are available to configure a report. Note
that any field preceding an asterisk (*) indicates a required entry.

Figure 9-4 Report configuration

 Report Type: BIRT, Crystal, Custom. By determining the report type and
settings you register that report in the Maxim database.

Chapter 9. Reporting configuration 167

[Link] Draft Document for Review June 18, 2009 11:16 am

 Limit Records: The action limits the number of records against which an end
user can run a report. It prevents end users from executing large queries,
which can cause negative performance impacts. Use the Report
Administration application toolbar to open a report directly in the browser.
When Browser View is checked then enter a value other than None in the
browser View Location field. This field determines the application tabs that
have an active Browser View icon.
 Use Where Clause?: Enables Current / Selected plus User defined
parameters.
 No Request Page: Disables Request Page for Database Updates
 Browser View and Browser View Location: The Browser View feature lets
you create a shortcut. With the shortcut, the end user can click an icon once
in the application toolbar to open a report directly in the browser. When
Browser View is checked then enter a value other than None in the Browser
View Location field. This field determines the application tabs that can have
an active Browser View icon.

The following options are available:

– All: The Browser View icon is available on a tabs for the selected
application.
– List: The Browser View icon is only available on the List tab for he
selected application.
– Main: The Browser View icon is available on all tabs, except the list tab.
– None: The Browser View icon does not appear in the selected application.
None is the default.
 Direct Print and Direct Print Location: The Direct Print features lets you
create a shortcut so an end user can click an icon in the application toolbar to
print the report. The configuration is the same as for Browser View Location.
 Direct Print with Attachments and Direct Print with Attachment
Location: The Direct Print with Attached Document feature lets you create a
shortcut so an end user can click an application icon once (and select Yes in a
message dialog box) to print the report and any associated attached
documents. The configuration is the same as for Browser View Location.
 Generate Request Page: Click Generate Request Page if you have not
previously configured the report for Browser View. This option is available for
all reports or at individual report level.
 Preview: In the Report Administration application, you can preview a request
page and run a report. You can check for the following items:
– The correct parameters, if any, appear to the end user on the request
page.

168 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 11:16 am [Link]

– The generated report opens with the correct data and format.

To preview a report:
a. In the Report Administration, select the report that you want to run
b. Click Preview. The Request Page dialog box opens. The parameters that
appears depend on the report that you select.
c. Enter values in any required fields. Required fields have an orange
asterisk (*) next to them.
d. Click Submit to run the report. The report opens in a separate browser
session
 Parameters: From the parameters tab you can define ad hoc user
parameters. Note that these parameters must also be specified in the actual
report design itself.

9.3 Running reports

During the application installation process the BIRT default Report Writer is
automatically configured to run reports from within the application.

The set of instructions below enables you to open a report. After running the
report you will then be able to print and export data.

Use one of the following methods to open a report dialog box:

– From the Reports Menu in the application toolbar, select an application as
shown in Figure 9-5 on page 170.

Chapter 9. Reporting configuration 169

[Link] Draft Document for Review June 18, 2009 11:16 am

Figure 9-5 Report Menu

Or
– From the Select Action menu, select Run Reports. The Report tab opens.
The Report to Run table window lists he available reports for the
application. Click the report that you want to run (Figure 9-6 on page 171).

170 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 11:16 am [Link]

Figure 9-6 Select Action Run Reports option

8. Select the report you want to see, for example, “Asset List”. See Figure 9-7.

Figure 9-7 Selecting a Report to Run

9. Enter the required parameters in the Request Page dialog box, as shown in
Figure 9-8 on page 172.

Chapter 9. Reporting configuration 171

[Link] Draft Document for Review June 18, 2009 11:16 am

Figure 9-8 Asset Lists report

[Link] Submit to run the report. The report opens in your browser.
[Link] the reporting toolbar, perform any of the following actions:
a. Click the Print Report as PDF icon to print the report
b. Click the Export Data icon to export the data in .CSV format
c. Click the Toggle table of contents icon to see the table of contents for
your report. The report you select determines the table of contents

9.3.1 To schedule a report and send with e-mail

To schedule a report and send with e-mail perform the folowing:
1. Open the Reports dialog box through one of the following methods:
a. From the Reports Menu in the application toolbar, select an application.
a. From the Select Action menu, select Run Reports.
2. Click the Scheduling Status tab. Select one of the following scheduling
options:

172 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 11:16 am [Link]

– Once: The report runs on a specific date and time in the future. Enter a
date or click the select date icon. The date that you enter must be in (M or
MM) / (D or DD) / YY format. Specify a time in HH:MM format and specify
a.m. or p.m.

Note: Use this option to schedule complex or lengthy reports to run

during off-peak hours.

– Recurring: The report runs at regular intervals. Four fields let you
determine when the report runs.
• In the first field, enter a number from 1 through 365.
• In the second field, enter the interval (day, week, or month).
• In the third field, enter the day of the week or date of the month.
• In the fourth field, enter the time in HH:MM format, along with AM or
PM.
The following examples show the use of these fields:
• To run a report every day at 6:00 AM, select 1, and then Day. Leave the
third field blank and then 6:00 AM.
• To run a report every other Friday at 5:00 PM, select 2, then Weeks,
then Friday, and then 5:00 PM.
• To run a report every three months at 11:00 PM, on 15th of the month,
select 3, then Months, then Day 15, and then 11:00 PM.
3. Use the following fields to send the report with e-mail. The system sends the
report in .PDF format.
• To – Enter one or more e-mail addresses to receive the report. Click
Select Value to enter a system validated e-mail address.
• Subject – Enter a subject for the report. If you do not enter a subject,
the report name defaults to this field.
• Comments – Enter any comments you want to include in the e-mail
message.
4. Click Submit to run the report. The report is sent to the e-mail address at the
scheduled time.

9.3.2 To view and edit scheduled reports

You can use the Reports dialog box to view scheduled reports.
1. Open the Reports dialog box through one of the following methods:
a. From the Reports Menu in the application toolbar, select an application.

Chapter 9. Reporting configuration 173

[Link] Draft Document for Review June 18, 2009 11:16 am

b. From the Select Action menu, select Run Reports.

2. Click the Scheduling Status tab to open the Scheduling Status dialog box. In
the Schedules You Can Edit section, you can view the type of report (once or
recurring) and the next run time. You can delete a scheduled report and
change schedule information.

174 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 3:51 pm [Link]

Appendix A. Sample certification test

questions
In this appendix, we provide sample questions that are representative of the ones
you encounter on the actual certification test. We recommend you take this
sample test after studying the chapters in this book.

© Copyright IBM Corp. 2009. All rights reserved. 175

[Link] Draft Document for Review June 18, 2009 3:51 pm

Questions
We provide the following questions to assist you in studying for the certification
test:
1. Which configuration data is required while installing WebSphere Application
server
a. Web Server Name, Port and Node name.
b. Web Server Name and Port.
c. Web Server Name, Port, Node Name and Cluster Name.
d. Web Server Name, Port and Cluster Name.
e. Web Server Port, Node Name and Cluster Name.
2. Which type of queues types are not supported by message engine in a Web
Sphere application server?
a. Sequential Inbound and Outbound, Continuous Inbound Queues.
b. Sequential Outbound.
c. Continuous Inbound.
d. Continuous Inbound error.
e. Continuous Outbound.
3. What is the recommended maximum heap size for Maximo optimum
performance?
a. 1.5 – 2.0 GB
b. 1.0 –1.5 GB
c. 2.0 – 2.5 GB
d. 0.5- 1.0 GB
4. Where do you define the conditions on source and destination of a crossover
domain fields?
a. Crossover domain.
b. Domain application.
c. Condition Expression Manager.
d. System Properties.
e. Application Designer.
5. Which of the following describes the staging table?
a. Database view table where record set records are moved after execution
of a query.

176 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 3:51 pm [Link]

b. Data stored after execution of multiple joins query.

c. Table in the system used to store the attributes of an incoming e-mail
message.
d. Before report generation staging table is used to store result set.
e. None of the above.
6. Which of the following is not true?
a. Indexes can be created on a persistent tables.
b. Clustered index can be created for Oracle Database.
c. Indexed table data can be searched in ascending or descending order.
d. It is possible to have an index status.
e. It is possible to create an unique index.
7. Vendor’s labor costs are captured by using which default GL account?
a. Labor Control Account.
b. External Labor Control Account.
c. No default GL Account exists.
d. No default GL Account exists, one has to define labor resource code for
external.
e. None of the above.
8. Is it possible to define a Financial period as per user required tenures for
example. 18 months or 3 months?
a. Yes
b. No
c. You can only define up to 12 months
9. Which of the following are not an organization’s default accounts?
a. Global Rotating Suspense Account.
b. Global Ticket Account.
c. Tool Control Account.
d. External Labor Control Account.
e. Internal Labor Control Account.
[Link] of the following is not a part of Security Profile infrastructure?
a. A user’s security privileges controls a user’s access to modules,
applications, menu options, and data.

Appendix A. Sample certification test questions 177

[Link] Draft Document for Review June 18, 2009 3:51 pm

b. The security group to which a user belongs controls the user’s level of
access and privileges within the system.
c. The security architecture is designed to use organization as the first level
of security.
d. The profile tab in the users application displays the user's security profile.
e. The security profile information displays the access that has been granted
to the selected user through the combination of their roles.
[Link] of the following is not a relevant for security groups?
a. Security groups are two types Independent and non-independent.
b. It is possible to combine access rights and grants of one security group to
another security group in one type of security group.
c. Using security controls action, you can specify EVERYONE group for all
user fields.
d. It is necessary to create a security groups first before creation of a new
user.
e. In short, security groups define authorizations and users inherit
authorization of security groups.
[Link] approval limits and tolerances are applied at organization level, but
users inherits them to all the sites to which they have access. If a user has
invoice approval limits of $1200 for site A and $900 for site B. What is the
overall invoice approval limits?
a. $900 for both sites.
b. $1200 for both sites.
c. S1050 for both Sites.
d. $1200 at Site A and $900 at Site B.
e. $1200 at Site A and $1050 at Site B.
[Link] of the following is not a pre-migration task?
a. Create Migration Objects.
b. Create Migration Groups.
c. Organize and upload compiled source.
d. Package Definition.
e. Package Deployment.
[Link] of the following is not the best practices using migration manager to
deploy a package?
a. Same base language in source and target environments.

178 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 3:51 pm [Link]

b. No inbound restrictions in the target environment.

c. When one package at a time is deployed on the target environment
d. Administration mode turned on during Package Deployment.
e. Same product versions in source and target environments.
[Link] is the not the best way to troubleshoot errors during the migration?
a. Avoid package creation errors.
b. Avoid package distribution errors.
c. Avoid same environment in source and target.
d. Avoid package deployment errors.
e. Avoid deployment of multiple packages at the same time.
[Link] of the following is not a Start Center portlet?
a. Bulletin Board.
b. Favorite Applications.
c. Inbox / Assignments.
d. Quick Insert.
e. Workflow.
[Link] a user belongs to two security groups, after login how Start Center
appears?
a. Start Center will have two tabs each tab showing one Start Center
application.
b. Only one Start Center application appears after user logins.
c. There is no relation between security groups memberships and Start
Center.
d. User should login with two different credentials and configure each Start
Center separately.
e. None of the above.
[Link] which of the following we cannot set edit rules?
a. GL Account.
b. Asset.
c. Location.
d. WP Labor.
e. Actions.

Appendix A. Sample certification test questions 179

[Link] Draft Document for Review June 18, 2009 3:51 pm

[Link] the organization level, which of the following can a user configure for work
order application?
a. Revert material reservations when work order status is changed to closed
/ completed.
b. Display Contract Status.
c. Failure prompt.
d. Downtime prompt.
e. Display Annual Maintenance Contracts.
[Link] of the following is a Work Management configuration at the
organization level?
a. Increment task numbering with start number under plan tab of work order
tracking.
b. Under Flow Control.
c. Suspend Flow Control.
d. Flow Action Assist.
e. Inherit Status Changes.
[Link] Administration application allows to which of the following?
i. Open a list of reports.
ii. Define reports to end users.
iii. Change names of reports and field titles.
iv. Set or view security.
a. i and iii
b. i, ii and iv
c. i, ii and iii
d. i, ii, iii and iv
e. None of the above
[Link] do you define number of lines per page?
a. Define number of records per page in the report code.
b. Once page size is defined, number of records per page is taken care of by
reporting tool.
c. Using select action option define records per page.
d. Enter no of records per page value in Max Record Limit field.
e. None of the above.

180 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 18, 2009 3:51 pm [Link]

[Link] do you define Report Level authorization?

a. Define authorizations for a groups under security tab.
b. Define authorizations under Report Administration.
c. System Administrator allows report designer to Authorize.
d. Using select action option define report authorizations.
e. None of the above.

Appendix A. Sample certification test questions 181

[Link] Draft Document for Review June 18, 2009 3:51 pm

Answers
The following list shows the correct answers to the sample questions in this
appendix:
1. c
2. e
3. b
4. c
5. c
6. b
7. b
8. a
9. e
10.c
11.d
12.b
13.e
14.d
15.c
16.e
17.a
18.e
19.a
20.a
21.d
22.d
23.a

182 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 16, 2009 12:13 pm [Link]

Related publications

The publications listed in this section are considered particularly suitable for a
more detailed discussion of the topics covered in this book.

IBM Redbooks
For information about ordering these publications, see “How to get Redbooks” on
page 184. Note that some of the documents referenced here may be available in
softcopy only.
 Deployment Guide Series: Maximo Enterprise Asset Management,
SG247640
 IT Asset Management Processes using Tivoli Asset Manager for IT,
SG247601
 Maximo Asset Management Essentials V7.1 Implementer's Guide,
SG247645

Online resources
These Web sites are also relevant as further information sources:
 IBM Professional Certification Program Web site
[Link]
 Test 017 objectives
[Link]
 Tivoli process automation engine courses:
[Link]
 Tivoli Asset Management for IT Release 7.1, Installation Guide:
[Link]
ic=/[Link]/[Link]

© Copyright IBM Corp. 2009. All rights reserved. 183

[Link] Draft Document for Review June 16, 2009 12:13 pm

How to get Redbooks

You can search for, view, or download Redbooks, Redpapers, Technotes, draft
publications and Additional materials, as well as order hardcopy Redbooks
publications, at this Web site:
[Link]/redbooks

Help from IBM

IBM Support and downloads
[Link]/support

IBM Global Services

[Link]/services

184 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:02 pm [Link]

Index
checklist 5
Symbols IBM Professional Certification Program 2
/[Link] 16
process 7
Tivoli Professional Certification Program 4
A Chart of Account application 71
actions 49 classification structure 40
Actions application 48 Classifications application 39–40
Activities and Tasks application 159 Associates Classifications 41
add-on adapters 120 Attributes 41
Allow Generated Passwords to Be Displayed on Classification Structure / Hierachy 40
Screen 100 Other Systems 41
ALN domains 31 Sections 41
Always E-mail Generated Passwords to Users 100 Separate Classification Hierachies 41
Application Designer 115 Using Classifications 40
Application Designer applicatio 111 Clearing Account 36, 73
Application Designer application 135 Com Log Entry? 45
application server 80 Communication templates 43–44
Assignment Manager application 159 associate file attachments 45
autokey attributes 154 create e-mail notifications 44
Prefix 154 create generic communication template 44
Seed 154 working with 44
Autokey feature 153 communication templates 43
autokeys 154 Condition field 47
Autonumber setup 153 Conditional Expression Manager 58
Autonumbering application 36 Conditional Expression Manager application 58
auto-numbering patterns 153 how to access 58
Conditional Expression Manager. 89
Conditional security
B best place to create the restrictions 111
BIRT default Report Writer 169
Conditional Expression Manager 112
built-in workflow process 42
creating 112
Bulletin Board 141
Creating a Signature Option 115
Business Intelligence Reporting Tool (BIRT) 163
overview 111
business object 59
Conditional SQL Expression Builder 47
configure the database 33
C creating an object 33
calendars 38 modifying 33
create and modify calendars 38 Cost Management 74
holidays 39 Cost Management application
organization level 39 Budget 75
referencing a calendar 39 Parent Project 75
Calendars application 38 Project 75
Certification Value 75
benefits 3 courses 8

© Copyright IBM Corp. 2009. All rights reserved. 185

[Link] Draft Document for Review June 22, 2009 3:02 pm

create calendars 39 enterprise service 125

Create Communication action 44 Enterprise Service application 125
Create New Template 142 tabs
CRON Task Setup application 43 Enterprise Service 126
cron tasks 43 List 126
CROSSOVER Domains 32 Enterprise services processing 125
Currency Codes application 35, 68 enterprises 10
Active? 69 escalation
Currency 69 deletion of rules 50
Description 69 rules 50
Custom Action Class 125 schedule 51
validation 51
Escalation application 46
D actions and notifications 49
Data Restrictions 79
components 47
Database Configuration application 33, 62, 71
Actions 48
Database server 15
Escalation Point 48
deleting the TEMP and TMP directories 14
Notifications 48
Deployment manager 25
Object 47
host name 25
Organization and or site 48
operating system password 25
Schedule 48
operating system user id 25
SQL Statement 47
SOAP port 25
creating an escalation 46
deployment plan 16
escalation items
Direct Print 168
Actions 48
Directory server 17
Escalation points 48
disabling the firewall 14
Header attributes 48
domains 31
Notifications 48
types
maintaining 46
ALN 31
multiple escalation points 49
CROSSOVER 31
usage
NUMERIC 31
IT Asset Management 46
NUMERIC RANGE 31
Service Desk Management 46
SYNONYM 31
Workflow processes 46
TABLE 31
Workflow application action (APPACTION) 48
Domains application 128
Escalation Point Condition field 51
Escalations 46
E Exchange Rates application 69
E-Mail Listener 41 Active Date 70
E-mail Listeners application 41 Convert from Currency 70
features 42 Convert to Currency 70
free form / formatted e-mails 42 Exchange Rate 70
Security 42 Memo 70
Storing attachments 42 External systems 126
The E-mail listener cron task 42
Workflow Process 42
E-Mail Password to User? 100 F
Favorite Application Portlet 141
encapsulating business objects 120
files 16
End Points 126

186 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:02 pm [Link]

Financial Configuration applications 68 summary 127

Financial Periods 71, 73 Invocation Channels application 124
Financial Periods application ISM solution environment 12
Accounting Close Date 74 middleware 12
Actual Close Date 74 Administrative system 12
Closed by 74 Application server 12
From 74 Database 12
To 74 Directory server 12
HTTP server 12
G
General Ledger Account 71 J
Generate Request Page 166 J2EE Application Server 25
GL Account 71 J2EE server 15
GL Account Configuration 71 J2EE technology 111
Java Message Service (JMS) 120
Job plan
I concepts 157
IBM Certification Agreement 6
Craft 157
IBM Service Management (ISM) 10
Labor 157
IBM Tivoli Change and Configuration Management
Material 157
Database (CCMDB) 120
Service 157
IBM Tivoli Directory Server 44
Task 157
IBM Tivoli process automation engine 9
Tool 157
IBM Tivoli Service Request Manager 120
nested 160
IBM WebSphere application server 25
statuses
Import Middleware Configuration Information 21
DRAFT 157
Inbox / Assignments Setup 140
INACTIVE 157
Independent of Other Groups? 82
template 161
integration configuration 121
Job Plan application 157, 161
Integration Framework 120, 122, 125–126
Job plan statuses 157
advanced integration functionality 120
configuring object structures 123
Importing data 126 K
inbound Web services queries 120 Key Performance Indicators (KPIs) 146
Invocation channels 124 creating 146
JMS based message exchange 120 crontask 147
Object Structure tab 123 Graph Setup 140
Object structures 122 KPICronTask 147
pre-configured integration contents 120 List Setup 141
Adapter (MAXIMO) 120 KPICrontask 147
Endpoints 120
Enterprise services 120
External system (EXTSYS1 120
L
Labor Reporting application 159
Object structures 120
Launch in Context 63
Publish channels 120
Launchpad 17
real-time user notifications 121
Layout and Configuration 140
rules-based message processing and rout-
LDAP (Lightweight Directory Access Protocol) 79
ing 121
LDAP authentication 109
Publish channels 123

Index 187
[Link] Draft Document for Review June 22, 2009 3:02 pm

Limits and Tolerances 79 overview 128

List 79 summary 136
Locations 38 migration objects 130
working with 38 multiple integration triggers 120
Locations application 38 multiserver topology 14
Login Tracking 109
N
M notification 50
maxadmin 140 Broadcast? field 50
Maxadmin group 164 notification types 50
[Link] file 23 free-form 50
metadata 129 template-based 50
Microsoft® Active Directory 109 NUMERIC domains 32
middleware 12 NUMERIC RANGE domains 32
Middleware installation 15, 17 continuous 32
Middleware Installer 19 discrete 32
migration 127 lookups 32
planning 135
Migration Configuration 119
Migration Manager 130
O
object structure 122
applications 131
Object Structures application 64
Migration Groups 132
Oracle 120
Migration Groups application 132
Organizations 35
Migration Manager 133
create an organization 35
Change 133
create a company set 35
Snapshot 133
create an item set 35
Migration Manager application 133
delete an organization 36
Object Structures 131
edit an organization 36
Object Structures application 131
working with 35
compiled sources 130
Organizations application 71, 73
concepts and components 128
package contents 129
Compiled sources 129 P
History data 129 People application 98
Non-structural configuration content persist JMS messages 27
129 platform configuration options 29
Package manifest 129 Platform configuration summary 61
Package metadata 129 portlet 140, 155
Structural configuration content 129 Portlet Ordering 142
package definitions 128 Processes table window 58
types 129 publish channels 123
packages 128 Purchase Order application 128
configuration content 135
example scenarios 127
Q
Migration flow 135 Quick Insert Portlet 141
Migration group 130 Quick Reporting application 159
Migration objects 130
Migration planning 135

188 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:02 pm [Link]

R EVERYONE 79
Redbooks Web site 184 MAXADMIN 79
Contact us xvi MAXREG 79
Reporting 163 Independent of Other Groups? check box 82
Direct Print and Direct Print Location 168 Revoke Listed Applications 84
Direct Print with Attachments and Direct Print set restrictions 89
with Attachment Location 168 Start Centers 95
Generate Request Page 168 tabs
Parameters 169 Applications 79
Preview 168 Data Restrictions 79
schedule a report 172 GL Components 79
table of contents 172 Group 79
Request pages 165 Labor 79
resources recommended for study 8 Limits and Tolerances 79
return on investment (ROI) 5 Sites 79
rules engine 121 Storerooms 79
Run Reports 172 Users 79
security profile 78
Self registration 109
S self-registration 80
Safety tab option 116
Service Desk module 159
sample questions 175
service providers 10
SAP suite 120
service requests 41
Security Controls action 108
Service Requests application 159
security group 78
Set Application Security 164
security group types
Setting or changing passwords and password hints
independent 95
109
non-independent 95
Setting up authentication 109
Security Groups application 78
LDAP authentication 109
adding a new ecurity group 80
native authentication 110
adding applications to a security groups 83
Signature Option 115
adding Limits and Tolerances to security groups
Sites 37
88
active a site 38
adding storerooms to security groups 85
add a site 37
adding users to a security group 91
working with 37
applying Data Restrictions to security groups 89
site-specific calendars 39
approval limits 88
Start Center
assigning GL Components to security groups
associating a template 145
87
creating a template 141
Authorize Group for All Storerooms? check box
modifying an existing template 144
86
Portlets
Authorize Group Reassignment 93
Bulletin Board 141
Base Currency field 89
Favorite Applications Setup 141
Conditional Expression Manager 89
Inbox / Assignments Setup 140
Grant Listed Applications 84
KPI Graph Setup 140
Grant Listed Options for This Application 85
KPI List Setup 141
groups
Layout and Configuration 140
78
modifying 143
DEFLTREG 78
Quick Insert 141

Index 189
[Link] Draft Document for Review June 22, 2009 3:02 pm

Quick Insert Setup 141 DOMAINS option 99

Result Set setup 141, 143 E-Mail Password to User? check box 100
Chart Options 143 Generate Password 100
Column Display 143 My Profile action 97
Column Display Available Queries 143 no matching person ID found 99
Display Options 143 Password Should Expire After First Login?
templates 140 check box 101
Storerooms 79 Personal section 98
Synonym Domain 100 Security profile tab 103
SYNONYM domains 31 Set Security Profile action 96
Site field 96
Sites 103
T System level applications 103
TABLE domains 32
tabs
Test 435 7
Groups 94, 98
Thomson Prometric 6
List 94, 98
TICKET table 33
Security Profile 94, 98
Tivoli base services 10
User 94, 98
Tivoli Certification benefits 4
user record statuses
Tivoli environment 5
ACTIVE 94
Tivoli process automation engine 10, 14
BLOCKED 94
database data 22
DELETED 94
installation example 14
INACTIVE 94
before you begin 14
NEWREG 94
Deployment plan 16
SELFREG 95
Logs 16
middleware installation 15
solution description 16 V
Tivoli middleware installer 15 validation 51
Topology file 16 Validation Results table window 51
installation prerequisites 12
overview 10
portfolio 11
W
Web-based courses 8
typical deployment environments 12
WebLogic 111
custom 13
WebSphere connectivity data 25
simple 12
Windows 2003 Server 16
topology file 16
wonum attribute 59
[Link] file 19–20
Work management
administration 149
U applying a job plan to a work order 156
ulimit 14 Autonumber setup 153
User approval limits 178 capabilities 160
Users application 78, 91, 93, 96 Edit rules 151
adding a new user 98 job plan 156
assigning a user to a security group 101 Other organization options 151
Authorize Group Reassignment 101 Actual Start Date 151
creating person records 99 Clear Material Reservation when WO status
Default Insert field 96 changes 152
default insert site 96 Default Downtime Start 151

190 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
Draft Document for Review June 22, 2009 3:02 pm [Link]

Display Downtime report prompt upon WO Workflow Designer 51

Completion for Asset in Down Status 152 Workflow Designer application 51
Display Duplicate Problem Warning 152 Condition Node 54
Display Warranty Status 152 Connection Lines 56
settings 150 Negative Connections 56
Start Center setup 155 Positive Connections 56
status flow control 161 creating workflows 56
work order options 150 Interaction Nodes 55
Work type 150 Manual Input Nodes 54
work order 157 Process Node Types 52
Work Order module 157 Start Nodes 53
applications 158 Stop Nodes 56
Activities and Tasks 159 Subprocess Nodes 54
Assignment Manager 159 tabs 51
Labor Reporting 159 Canvas 52
Quick Reporting 159 List 51
Service Requests 159 Process 52
Work Order Tracking 158 Task Nodes 53
Actuals 158 Wait Nodes 55
Failure Reporting 158 Workflow Desinger Toolbar 52
List 158 Workflow Process 42
Log 158 workspace 15–17
Plans 158
Related Records 158
Safety Plan 158
Work Order 158
creating work orders 160
applications
Condition Monitoring 160
Incidents 160
Preventive Maintenance 160
Problems 160
Quick Reporting 160
Releases 160
Service Requests 160
Work Order Tracking 160
work order definition 157
work order number 45
Work Order Tracking application 158
work template 156
Workflow Administration application 57
tasks
Delete Workflow assignments 58
Reassign Workflow assignments 58
Stop active processes 58
View Workflow assignments 58
workflow and escalation processes 44
Workflow Assignement (WFASSIGNMENT object)
48

Index 191
[Link] Draft Document for Review June 22, 2009 3:02 pm

192 Certification Study Guide Series: Foundations of Tivoli Process Automation Engine
To determine the spine width of a book, you divide the paper PPI into the number of pages in the book. An example is a 250 page book using Plainfield opaque 50#
smooth which has a PPI of 526. Divided 250 by 526 which equals a spine width of .4752". In this case, you would use the .5” spine. Now select the Spine width for
the book and hide the others: Special>Conditional Text>Show/Hide>SpineSize(-->Hide:)>Set . Move the changed Conditional text settings to all files in your
book by opening the book file with the [Link] still open and File>Import>Formats the Conditional Text Settings (ONLY!) to the book files.
Draft Document for Review June 16, 2009 1:01 pm [Link] 193
Certification Study Guide
Series: Foundations of Tivoli
Process Automation Engine
(1.5” spine)
1.5”<-> 1.998”
789 <->1051 pages
Certification Study Guide
Series: Foundations of Tivoli
(1.0” spine)
0.875”<->1.498”
460 <-> 788 pages
Certification Study Guide Series: Foundations of Tivoli
(0.5” spine)
0.475”<->0.875”
250 <-> 459 pages
Certification Study Guide Series: Foundations of Tivoli Process
(0.2”spine)
0.17”<->0.473”
90<->249 pages
(0.1”spine)
0.1”<->0.169”
53<->89 pages
To determine the spine width of a book, you divide the paper PPI into the number of pages in the book. An example is a 250 page book using Plainfield opaque 50#
smooth which has a PPI of 526. Divided 250 by 526 which equals a spine width of .4752". In this case, you would use the .5” spine. Now select the Spine width for
the book and hide the others: Special>Conditional Text>Show/Hide>SpineSize(-->Hide:)>Set . Move the changed Conditional text settings to all files in your
book by opening the book file with the [Link] still open and File>Import>Formats the Conditional Text Settings (ONLY!) to the book files.
Draft Document for Review June 16, 2009 1:01 pm [Link] 194
Certification Study
Guide Series:
Foundations of Tivoli
(2.5” spine)
2.5”<->nnn.n”
1315<-> nnnn pages
Certification Study
Guide Series:
Foundations of Tivoli
(2.0” spine)
2.0” <-> 2.498”
1052 <-> 1314 pages
 Back cover ®
Draft Document for Review June 22, 2009 4:20 pm

Certification Study Guide

Series: Foundations of
Tivoli Process Automation ®

Helps you achieve This IBM® Redbooks® publication is a study guide for Test
Foundations of Tivoli 000-017: Foundations of Tivoli Process Automation Engine and is INTERNATIONAL
Process Automation aimed at individuals who want to get an IBM Professional TECHNICAL
Engine certification
Certification on Tivoli Process Automation Engine. SUPPORT
The Foundations of Tivoli Process Automation Engine Professional ORGANIZATION
Certification, offered through the Professional Certification Program
Explains the from IBM, is designed to validate the skills required of technical
certification path professionals who work in the implementation of the Tivoli Process
and prerequisites Automation Engine. Note that this test is a prerequisite for several BUILDING TECHNICAL
other certifications, such as IBM Tivoli Maximo Asset Management INFORMATION BASED ON
Introduces sample for IT V7.1 Implementation PRACTICAL EXPERIENCE
test questions This book provides a combination of theory and practical experience
needed for a general understanding of the subject matter. It also
IBM Redbooks are developed by
provides sample questions that will help in the evaluation of
the IBM International Technical
personal progress and provide familiarity with the types of Support Organization. Experts
questions that you will encounter in the exam. from IBM, Customers and
This publication does not replace practical experience, nor is it Partners from around the world
designed to be a stand-alone guide for any subject. Instead, it is an create timely technical
effective tool that, when combined with educational activities and information based on realistic
scenarios. Specific
experience, can be an extremely useful preparation guide for the
recommendations are provided
exam. to help you implement IT
For your convenience, we structure the chapters based on the solutions more effectively in
sections of the Test 000-017, such as Prerequisites and Installation,
your environment.
Platform Configuration and so on, so studying each chapter will help
you prepare for one section of the exam.
For more information:
[Link]/redbooks

SG24-7763-00 ISBN