MAM71 Implementation - Student Exercises

IBM Tivoli Maximo Asset Management 7.
1 Implementation
Student Exercises
S150-3036-00
September 2008
Copyright Notice
Copyright © 2008 IBM Corporation, including this documentation and all software. All rights
reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Soft-
ware License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any computer language, in any form or by any means, electronic, mechanical,
magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corpora-
tion. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any
machine-readable documentation for your own use, provided that each such reproduction shall carry
the IBM Corporation copyright notice. No other rights under copyright are granted without prior writ-
ten permission of IBM Corporation. The document is not intended for production and is furnished “as
is” without warranty of any kind. All warranties on this document are hereby disclaimed, including the
warranties of merchantability and fitness for a particular purpose.
Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or
disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.
Trademarks
The following are trademarks of IBM Corporation or Tivoli Systems Inc.: IBM, Tivoli, AIX, Cross-Site,
NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, TME. In Den-
mark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.
Microsoft, Windows, Windows NT, 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.
C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States,
other countries, or both.
Lotus is a registered trademark of Lotus Development Corporation.
PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or
both and is used by IBM Corporation under license.
ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the
United States, other countries, or both.
SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For fur-
ther information, see http://www.setco.org/aboutmark.html.
Other company, product, and service names may be trademarks or service marks of others.
Notices
References in this publication to Tivoli Systems or IBM products, programs, or services do not imply
that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to
these products, programs, or services is not intended to imply that only Tivoli Systems or IBM prod-
ucts, programs, or services can be used. Subject to valid intellectual property or other legally pro-
tectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can
be used instead of the referenced product, program, or service. The evaluation and verification of
operation in conjunction with other products, except those expressly designated by Tivoli Systems or
IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent
applications covering subject matter 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 the IBM Director of
Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.
Printed in Ireland.
Table of Contents
Student Exercises for Unit 1

No student exercises are provided for this unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Exercise 1: Copy the Maximo Root Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Exercise 2: Creating a Second Database Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Binding the DB2 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Exercise 3: Run Maxinst Against DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Exercise 4: Create a Second Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Exercise 5: Building the EAR Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Exercise 6: Deploying the MAXIMO and MAXIMOHELP EAR Files . . . . . . . . . . . . . . . . . . . . 2-15
Exercise 7: Accessing the Second Start Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Exercise 1: Creating Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Exercise 2: Creating Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Exercise 3: Creating Communication Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Exercise 4: Creating a Workflow Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Exercise 1: Creating a Table Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Exercise 2: Creating an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Exercise 3: Creating a New Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Exercise 4: Create New Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Exercise 5: Configure the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Exercise 1: Create a New Application Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Exercise 2: Signature Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Exercise 3: Select Action Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Exercise 4: Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Exercise 5: Search Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Exercise 6: Modify the List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Exercise 7: Granting Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Exercise 8: Verify Your Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Exercise 1: Organizing the Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Exercise 2: Defining the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Exercise 3: Creating the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Exercise 4: Distributing the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Exercise 5: Deploying the Migration Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
•
•
• I
•
•
Table of Contents

Exercise 1: Create a WebSphere Messaging Resource (Bus) . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Exercise 2: Add a Server to the Service Integration Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Exercise 3: Create the Service Integration Bus Destination for the Continuous Inbound (CQINBD)
Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Exercise 4: Create the Service Integration Bus Destination for the Sequential Inbound (SQINBD)
Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Exercise 5: Create the Service Integration Bus Destination for the Sequential Outbound (SQOUT-
BD) Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Exercise 6: Create the JMS Connection Factory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Exercise 7: Create the Continuous Inbound (CQIN) JMS Queue . . . . . . . . . . . . . . . . . . . . . . . 7-9
Exercise 8: Create the Sequential Inbound (SQIN) JMS Queue . . . . . . . . . . . . . . . . . . . . . . . 7-11
Exercise 9: Create the Sequential Outbound (SQOUT) JMS Queue . . . . . . . . . . . . . . . . . . . . 7-12
Exercise 10: Create JMS Activation Specification for the Continuous Inbound Queue (CQIN) 7-14
Exercise 11: Stop and Start all WebSphere Application Server Services. . . . . . . . . . . . . . . . . 7-15
Exercise 12: Setting System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Exercise 13: Configuring Cron Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Exercise 14: Enable Integration Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Exercise 15: Publish Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Exercise 16: End Point Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Exercise 17: External Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Exercise 18: Test an Outbound Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Exercise 19: Test an Inbound Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Exercise 20: Importing Inbound Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

Exercise 1: Create a Result Set Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Exercise 2: Modify the Start Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Exercise 3: Create a KPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Exercise 4: Create a New Start Center Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Exercise 5: Run a BIRT Report from Work Order Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Exercise 6: Generate All System Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Exercise 7: Set Application Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Exercise 8: Install Eclipse and BIRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Exercise 9: Configure the Environment for BIRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Exercise 10: Configure BIRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24

Exercise 1: Create a New Appender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Exercise 2: Modify a Logger to Use an Appender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Exercise 3: Specify a new Folder for the Reporting Appender . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Exercise 4: Generate Request Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Exercise 5: Run Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Exercise 6: Verify the New Appender Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
•
•
II • IBM Tivoli Maximo Asset Management 7.1 Implementation ©Copyright IBM Corp. 2008
•
•
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
No student exercises are provided for this unit.
•
•
• 1-1
•
•
•
•
1-2 • IBM Tivoli Maximo Asset Management 7.1 Implementation ©Copyright IBM Corp. 2008
•
•
Exercise 1: Copy the Maximo Root Installation

Folder
You begin the task of creating a second Maximo instance, by copying the root Maximo
(SMP) folder onto your local (c:\) drive and renaming it. Complete the following steps:
___ 1. Using Windows Explorer, navigate to c:\IBM folder.
___ 2. Copy the SMP folder in the same directory (c:\IBM) and rename it SMP2.
This may take close to 30 minutes.
You will now update the maximo.properties file in the newly created Maximo
installation folder (SMP2) to reflect a second database (or Maximo instance) that
you will create in the next exercise.
___ 3. Using window Explorer, navigate to:
c:\IBM\SMP2\applications\maximo\properties
___ 4. With your text editor, open the maximo.properties file.

•
•
• 2-1
•
•
Exercise 1: Copy the Maximo Root Installation Folder
___ 5. Edit the maximo.properties file as follows:
___ a. Search for UDB01
mxe.db.url=jdbc:db2://localhost:50000/UDB02
___ b. Replace UDB01 with UDB02.
mxe.db.url=jdbc:db2://localhost:50000/UDB02
___ 6. Save and close the maximo.properties file.
•
•
•
•
Exercise 2: Creating a Second Database Instance
Exercise 2: Creating a Second Database

Instance
To create a local directory to hold the DB2 tablespace files and index files, complete the
following steps:
___ 1. For the purposes of this exercise, create the directory c:\db2data2.
___ 2. Launch the DB2 Control Center by right-clicking the DB2 system tray icon and
selecting DB2 Control Center.
___ 3. From the All Systems folder, expand the plus (+) signs to go down the chain until
you see the Databases folder, which contains UDB01.
___ 4. Select the Databases folder. From the Tools menu of the Control Center, select
Command Editor.
•
•
©Copyright IBM Corp. 2008 IBM Tivoli Maximo Asset Management 7.1 Implementation • 2-3
•
•
___ 5. Type or paste the following SQL code into the top pane of the Command Editor
tool to create a database named UDB02.
CREATE DATABASE UDB02 ON C: ALIAS UDB02 WITH "UDB02 Database";

CONNECT TO UDB02;
UPDATE DB CFG FOR UDB02 USING AUTO_MAINT ON;
UPDATE DB CFG FOR UDB02 USING AUTO_TBL_MAINT ON;
UPDATE DB CFG FOR UDB02 USING AUTO_RUNSTATS ON;
UPDATE DB CFG FOR UDB02 USING AUTO_REORG ON;
UPDATE DB CFG FOR UDB02 USING AUTO_DB_BACKUP ON;
UPDATE ALERT CFG FOR DATABASE ON UDB02 USING db.db_backup_req SET
THRESHOLDSCHECKED YES;
UPDATE ALERT CFG FOR DATABASE ON UDB02 USING db.tb_reorg_req SET
UPDATE ALERT CFG FOR DATABASE ON UDB02 USING db.tb_runstats_req SET
CONNECT TO UDB02;
GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,
IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT ON
DATABASE TO USER DB2ADMIN;
CREATE BUFFERPOOL UDB02BUFFERPOOL IMMEDIATE SIZE 4096 PAGESIZE 32 K
;
CREATE REGULAR TABLESPACE UDB02 PAGESIZE 32 K MANAGED BY SYSTEM
USING ('c:\db2data\UDB02\tablespace' ) EXTENTSIZE 16 OVERHEAD 10.67
PREFETCHSIZE 16 TRANSFERRATE 0.04 BUFFERPOOL UDB02BUFFERPOOL
DROPPED TABLE RECOVERY OFF;
GRANT USE OF TABLESPACE UDB02 TO USER DB2ADMIN WITH GRANT OPTION;
CREATE SCHEMA MAXIMO AUTHORIZATION maximodb2;
CREATE SYSTEM TEMPORARY TABLESPACE UDB02SYSTEMP PAGESIZE 32 K
MANAGED BY SYSTEM USING ('c:\db2data2\UDB02\systemp' ) EXTENTSIZE
8 OVERHEAD 10.67 PREFETCHSIZE 8 TRANSFERRATE 0.04 BUFFERPOOL
UDB02BUFFERPOOL ;
UPDATE DATABASE CONFIGURATION USING APPLHEAPSZ 1024 DEFERRED ;
UPDATE DATABASE CONFIGURATION USING LOGSECOND 3 IMMEDIATE ;
UPDATE DATABASE CONFIGURATION USING LOGFILSIZ 4096 DEFERRED ;
UPDATE DATABASE CONFIGURATION USING APP_CTL_HEAP_SZ 1024 DEFERRED ;
UPDATE DATABASE CONFIGURATION USING LOCKLIST 30000 IMMEDIATE ;
UPDATE DATABASE CONFIGURATION USING MAXLOCKS 75 IMMEDIATE;
CONNECT RESET;
•
•
•
•
___ 6. Click the green triangle on the Commands tool bar to execute the query. This
process will take from 2 to 5 minutes to complete, depending on the performance
capabilities of your hardware.
___ 7. When the database creation process is completed, Exit the Command Editor.
___ 8. Refresh the Control Center view (View >> Refresh) and expand the All Systems
folder. Drill down to the Databases folder.
___ 9. Right-click the UDB02 database and select Stop to stop the database
(acknowledge the warning dialog box).
___ 10. Click Start to restart the UDB02 database.
___ 11. Right-click the UDB02 database and select Authorities.
___ 12. From the Database Authorities dialog box, click Add User.
___ 13. Select MAXIMO and click OK.
___ 14. Highlight the MAXIMO user and click Grant All.
___ 15. Click OK to close the dialog box.
___ 16. Close the DB2COPY1 Control Center.
•
•
•
•
Binding the DB2 Schema

To optimize DB2 for interaction with Maximo®, you tune it using configuration
parameters. Before tuning it, you must bind the database, which formats DB2 metadata and
structures the database with a security access template. Complete the following DB2 bind
procedures against the DB2 database that you plan to connect to Maximo.
___ 1. Launch a Windows Command Prompt and enter the following commands:
cd \IBM\SQLLIB\BND
set DB2DBDFT=UDB02
db2cmd db2 connect to UDB02
___ 2. The DB2 command-line processor tool is launched. Enter the following
commands:
db2 bind db2schema.bnd

db2 bind @db2cli.lst clipkg 4
•
•
•
•
Exercise 3: Run Maxinst Against DB2
___ 3. Close all open command windows.
Exercise 3: Run Maxinst Against DB2

You create the Maximo database by running maxinst, which populates DB2 with the
specific database objects Maximo requires. To do so, complete the following steps:
1. Open a command prompt.
2. Change directory path to C:\IBM\SMP2\tools\maximo.
3. Launch maxinst using the –t parameter (to specify tablespace) and the –s
parameter (to specify index storage area).
Maxinst –tUDB02 –sUDB02
This process will take approximately 30 minutes.
By default, Maximo reads the maximo.properties file (in this example,

c:\IBM\SMP2\applications\maximo\properties) for connectivity information to the
database. It connects using a JDBC connection and then creates a Maxdemo database. To
create an empty database, use the -imaximo -sUDB02 -tUDB02 flag.
For example, at the command prompt, instead of typing maxinst, type maxinst -imaximo.
•
•
•
•
Exercise 4: Create a Second Application Server
Exercise 4: Create a Second Application

Server
Use the WebSphere console to complete the following steps:
___ 1. Invoke a browser window.
___ 2. Open the WebSphere Administrative console by typing

http://vm100:9060/admin in the browser address bar.
This URL address uses the default port number (9060) and context (admin) for the
Administrative console.
___ 3. Enter any user name to log in, or just click Log in.
___ 4. Expand the Servers link and click Application servers.
Notice the MAM71 Application server is running.
___ 5. From Windows command prompt, change directory to:
c:\IBM\WebSphere\AppServer\profiles\Custom01\bin
___ 6. At the prompt, type stopnode. Allow for the Node Agent to stop.
___ 7. Refresh the Servers page, by clicking the Application servers link and the icon
turns from an X to unavailable.
___ 8. Click New.
___ 9. Type MAM71Target in the Server name field and click Next.
___ 10. Accept the defaults in Step 2 and click Next.
___ 11. Accept the defaults in Step 3 and click Next.
___ 12. Click Finish to confirm the new server.
___ 13. Before you save the new application, click Preferences from the Messages
window. The goal is to synchronize changes with nodes.
You synchronize changes with nodes when you have one Deployment Manager
and multiple application server custom profiles. For example, if you have
WebSphere spread over four machines, you would have one Deployment Manager
and four custom profiles. If you make a change and select Synchronize changes
with Nodes, the change will be replicated out to all of the profiles.
___ 14. Select Synchronize changes with Nodes, click Apply, and then click Save.
•
•
•
•
___ 15. Click OK when the save is complete.
___ 16. Click the Servers >> Application Servers link on the left pane.
___ 17. Click MAM71Target in the middle pane.
___ 18. Under Container settings, expand Web Container Settings, then click Web
container transport chains.
•
•
•
•
___ 19. Click New.
___ 20. In Step 1 of the Select transport chain template, type

MAM71TargetTRANSPORT and click Next.
___ 21. In Step 2, specify Port name as MAM71Target, Host as * (asterisk), and Port as
8888. Click Next.
___ 22. In Step 3, click Finish.
___ 23. Click Save.
___ 24. Allow for the synchronization to complete and click OK.
•
•
•
•
___ 25. Click the Application servers link in the left pane.
___ 26. Click MAM71Target.
___ 27. Under the Server Infrastructure section, expand Java and Process
Management.
___ 28. Click Process Definition.
___ 29. Under the Additional Properties section, click Java Virtual Machine.
___ 30. Specify the following settings. Ensure to type these values, especially the Generic
Java argument. Do not copy/paste it into WebSphere.
Parameter name Enter this value...
Initial heap size 512
Maximum heap size 1024
Generic Java (or JVM) -Dsun.rmi.dgc.ackTimeout=10000

arguments –Djava.net.preferIPv4Stack=true
There are no line breaks in the Generic Java argument settings. There is a space
after the 10000, followed by the dash (-) and so forth. Please type the entire
argument, do not copy/paste the string value.
•
•
•
•
The value of this property represents the length of time (in milliseconds) that the
server-side RMI runtime will strongly refer to a remote object (or a reference to a
remote object). This elapsed time is returned from the current virtual machine as
part of the result of a remote method call. The time stops when it receives positive
acknowledgment from the client that the remote reference has been fully received
and processed. This time-out only applies to failure situations in which the client
fails to send the acknowledgment. Setting the value too low can increase the risk
of a remote object being prematurely garbage collected when the only known
reference to the remote object is the one in transit as part of the remote method
call result. The maximum value is Long.MAX_VALUE. The default value is 300
000 (5 minutes).
The second argument tells WebSphere to use the IPv4 stack as the default, rather
than both the IPv4 and the IPv6 stacks.
___ 31. Click OK and then click Save.
___ 32. Click OK.
___ 33. In the left pane, expand Environment and then click Virtual Hosts.
___ 34. Click New.
___ 35. Type MAM71TargetSERVER as the virtual host name, and click OK.
___ 36. Click Save.
___ 37. Click MAM71TargetSERVER from the main Virtual Hosts pane.
___ 38. From Additional Properties, click Host Aliases.
•
•
•
•
___ 39. Click New to create the first host alias.
___ 40. Accept the default values (Host Name: * and Port: 80) and click OK.
___ 41. Click New again to create a second host alias.
___ 42. Change the port number to 8888 and then click OK.
___ 43. Click Save.
Later in this paper, you will use port number 8888 in your browser to connect to
the Target environment.
___ 44. Click Save to save these changes and click OK.
The first alias is usually the port that the IBM HTTP Server is running on. The
second one is for the Web container port.
You have completed your middleware installation and configuration manually, without
using the scripts that are available to the middleware installer.
•
•
•
•
Exercise 5: Building the EAR Files
Exercise 5: Building the EAR Files

The middleware installer is responsible for running the batch files that create or build the
resulting EAR files. There are four batch files; each is responsible for building the
corresponding EAR files. The c:\Maximo\deployment folder lists these batch files, which
are described in the following table.
Batch File Description
Contains WAR, JAR, and EJB files. It is responsible

buildmaximoear.cmd for building the entire enterprise application
(Maximo).
Contains mostly HTML and style sheet files and is
buildhelpear.cmd
responsible for building the help files.
Builds the EAR file responsible for creating an
buildbocrystalwar integration between Maximo and a custom Crystal
Report Environment.
The new acweb.ear that was in Maximo Version 6.
buildportalear.cmd This is the Actuate Integration file that allows Actuate
reports to work in Version 7.
This file is used if you have multiple JVM instances; it
buildmiregwar.cmd allows a common RMI bind, which is useful if running
a cluster.
For the purposes of this exercise, you will build only the Maximo and the Maximo Help
EAR files.
___ 1. From a Windows Command Prompt, change directory to

IBM\SMP2\deployment.
___ 2. At the prompt, type buildmaximoear. After the maximo.ear file is built, type
buildhelpear.
Ignore the message that the tools.jar file was not found. It is of no consequence.
Note the newly built EAR files in the c:\IBM\SMP2\deployment\default

directory.
In the next section you will deploy these EAR files using the IBM WebSphere
Administrative Console.
•
•
•
•
Exercise 6: Deploying the MAXIMO and MAXIMOHELP EAR Files
Exercise 6: Deploying the MAXIMO and

MAXIMOHELP EAR Files
You perform the following tasks from the WebSphere Console.
___ 1. From the WAS console, click Applications > Install New Application.
___ 2. Browse to C:\IBM\SMP2\deployment\default. Both EAR files are displayed.
___ 3. Select maximo.ear (order does not matter). Click Next.
•
•
•
•
___ 4. From the Select Installation Options panel, change the Application name from
MAXIMO to MAXIMOTarget and click Next.
___ 5. From the Map modules to servers panel, complete the following sub-steps in the
exact order that they appear:
___ a. Select and high light the The MAM71Target server.
___ b. Select all four modules.
___ c. Click the Apply button next to the MAM71Target server.
3
1
___ d. Scroll to the right and ensure that the Server column depicts:
•
•
•
•
WebSphere:cell=vm100Cell01,node=vm100Node01,
server=MAM71Target
___ e. Click Next.
___ 6. From the Map virtual hosts for Web modules panel, select all three entries (just
one for the help EAR file).
___ 7. Select MAM71TargetSERVER from the Virtual host drop-down list for all
three Web modules and click Next.
___ 8. Click Finish in the Summary window to install the maximo.ear file.
•
•
•
•
___ 9. Wait for the successful deployment message and then click Save.
You are now ready to install the maximohelp EAR file.
___ 10. Browse to C:\IBM\SMP2\deployment\default.
___ 11. Select maximohelp.ear. Click Next.
___ 12. From the Select Installation Options panel, change the Application name from
MAXIMO to MAXIMOHELPTarget and click Next.
___ 13. From the Map modules to servers panel, select:
___ a. The MAM71Target server
___ a. enmaximohelp.war module and click Next.
___ 14. From the Map virtual hosts for Web modules panel, select enmaximohelp.war.
___ 15. Select MAM71TargetSERVER from the Virtual host drop-down list for all
three Web modules and click Next.
___ 16. Click Finish.
___ 17. Click Save when the MAXIMOHELPTarget is installed successfully.
You must now start the Node Agent in WebSphere.
•
•
•
•
___ 18. From a command prompt change directory to:

c:\IBM\WebSphere\AppServer\profiles\Custom01\bin
___ 19. At the prompt, type startnode.
Allow for the Node Agent to start.
___ 20. From the Servers section, open the Application servers link.
___ 21. Select the MAM71Target and MAM71Target application servers (check box)
and click Start. After 1 minute or so, the Status icon will change from an X to an
arrow.
___ 22. From the Applications section, open the Enterprise applications link. Note that
all four applications are displaying green arrows for their status icon.
•
•
•
•
Exercise 7: Accessing the Second Start Center
Exercise 7: Accessing the Second Start

Center
___ 1. Open a new browser window or tab.
___ 2. In the URL address bar, type http://vm100:8888/maximo and press Enter.
___ 3. Log in as user maxadmin with password maxadmin.
___ 1. Open a another browser window or tab.
___ 2. In the URL address bar, type http://vm100:9999/maximo and press Enter.
___ 3. Log in as user maxadmin with password maxadmin.
The Maximo Workflow Designer requires a Java runtime environment™ (JRE™) 1.5.
You can obtain JRE 1.5 from the following Web site:
http://java.sun.com/javase/downloads/index_jdk5.jsp
This image includes that JRE.

•
•
•
•
In this exercise, you create a Service Request (SR) workflow process that automatically sets
the internal priority of a new SR. The process then places the SR into the Inbox of a Service
Desk manager. The manager reviews the SR and places it into the queue of a Service Desk
agent. The agent receives an automatic e-mail notification to take action based on the
queued SR.
You can launch the workflow process manually or automatically using Maximo workflow
infrastructure. When launched, the process examines the chosen SR record. If the record
has NEW status and its reported priority is 1 or 2, Maximo places the SR into the Service
Desk manager’s Inbox for review. After the manager has acted on the SR, the internal
priority of the SR is changed to 1. A notification is sent to the designated Service Desk
agent to work on the SR.
You use the following applications to create your workflow.
• Roles
• Actions
• Communication Templates
• Workflow
Later, in Unit 6, you will migrate this workflow from your Source environment to your
target environment that you created in Unit 2.
Exercise 1: Creating Roles

___ 1. Using the source environment (http://vm100:9999/maximo), sign in to Maximo
Asset Manager 7.1 as user wilson with password wilson.
___ 2. From the Go To menu, select System Configuration > Platform

Configuration > Roles.
___ 3. Click the New Role button to create a new role.
___ 4. On the Role tab, make the following specifications:
– Role name: SDAGNT

– Type: A set of data related to the record
– Object: SR
•
•
• 3-1
•
•
Exercise 2: Creating Actions
– Value: :owner (You can use the lookup available for the Value field to select
the OWNER attribute of SR.)
Accept other default values and click the Save icon.
Exercise 2: Creating Actions

Configuration > Actions.
___ 2. Click the New Action button to create a new action.
___ 3. On the Action tab, make the following specifications:
– Action name: MMACT

– Object: SR
– Type: Set Value
– Value: 1
– Parameter/Attribute: internalpriority (You can use the lookup available for
the Parameter/Attribute field to select the INTERNALPRIORITY attribute
of SR.)
•
•
•
•
Exercise 3: Creating Communication Templates
Accept other default values and click the Save icon.
Exercise 3: Creating Communication

Templates
___ 1. From the Go To menu, select System Configuration > Platform Configuration
> Communication Templates.
___ 2. Click the New Communication Template button to create a new communication
template.
___ 3. On the Communication Template tab, specify the following items:
– Template: MMNOTIF
– Applies To: SR
– Send From: maxadmin@us.ibm.com
– Subject: Service Request :ticketid is prioritized
– Message: Service Request :ticketid is set to internal priority
:internalpriority - please take action.
•
•
•
•
Exercise 3: Creating Communication Templates
Accept other default values, and click the Save icon.
You must now activate the Recipients tab of the Communication Templates application
for the same template.
___ 4. Click the Recipients tab.
___ 5. Open the Roles section on the Recipients tab (the Expand icon is to the right).
___ 6. Click the Select Roles button.
___ 7. In the Select Roles lookup, locate the SDAGNT role.
___ 8. Select the check box to the left of the role record, and click OK to carry the value
to the Recipients tab.
___ 9. Select the To? field for the role record brought back to the Recipients tab.
___ 10. Click the Change Status button on the application tool bar.
___ 11. In the Change Status dialog box, change the status to ACTIVE.
•
•
•
•
Exercise 4: Creating a Workflow Process

Configuration > Workflow Designer.
___ 2. Click the New Process button to create a new workflow process definition.
___ 3. Click the Canvas tab.
___ 4. In the Process box, type MMWF. For Object, type SR.
___ 5. Click the canvas applet to activate it. The canvas already displays Start and Stop
nodes.
___ 6. Using the canvas, drag and drop a Condition node.
___ 7. Right-click the node to display its properties.
___ 8. In the Condition Node properties, specify the following items:
– Title: ISNEW
– Description: Is New Service Request?
– Expression: :status='NEW' (Type the colon before status and the single
quotation marks around NEW.)
Click OK to save the changes.
___ 9. Drag and drop another Condition node.
___ 10. Right-click the node to bring up its properties.
___ 11. In the Condition Node properties, specify the following items:
– Title: ISHIPRT
– Description: Is High Priority Service Request?
– Expression: :reportedpriority <3 (Start with the colon.)
Click OK to save the changes.
___ 12. Drag and drop a Task node.
___ 13. Right-click the node to bring up its properties.
___ 14. In the Task Node properties dialog box, specify the following items:
– Title: 'QUESR'
– Description: Queue the Service Request
– Application: SR
•
•
•
•
Click New Row in the Assignments section.
– Role ID: SDMGR

– Application: SR
Accept all other default values and then click OK to save the changes.
___ 15. Drag and drop positive connect lines (blue lines) between all the nodes on the
canvas. Similar to the image in the bottom of the next page.
___ 16. Drag and drop negative connect lines (red dashed lines) between the ISNEW
condition node, the ISHIPRT condition node, and the STOP node.
___ 17. Right-click the positive connect line between the QUESR task node and the
STOP node.
___ 18. In the Action properties, specify the following items:
– Action: MMACT
Click New Row in the Notifications section.
– Communication Template: MMNOTIF
Accept all other default values and click OK to save the changes.
•
•
•
•
You have now created a basic SR workflow process. The process checks SR records and
routes these records to a Service Desk manager for review and queueing to an agent’s SR
queue.
The workflow process can be launched manually or automatically using Maximo workflow
infrastructure. When launched, it examines the chosen SR record. If the record has the
NEW status and its reported priority is 1 or 2, the SR is placed into the Service Desk
manager’s Inbox for review. After the manager has acted on the SR, the internal priority of
the SR is changed to 1. A notification is sent to the designated Service Desk agent to work
on the SR.
•
•
•
•
•
•
•
•
In this exercise, you will create a database object which will be used to create an
application. You will perform the following steps:
• Create a new table domain in the Domains application.
• Create a new object and new relationships in the Database Configuration

application.
Exercise 1: Creating a Table Domain

Complete the following steps to create a table domain for the ASSET object.
___ 1. Open the Domains application (Go To > System Configuration > Platform
Configuration > Domains).
___ 2. Click the Add New Domain button to display the following menu.
___ 3. Click to select Add New TABLE Domain. The TABLE Domain dialog box
opens.
___ 4. Enter the following values.
Domain: CUASSET
Description: Use to Look Up Values in Asset Application
•
•
• 4-1
•
•
Exercise 1: Creating a Table Domain
___ 5. Click New Row. A new row opens for editing.
Field Value
Object ASSET
Validation Where Clause assetnum=:assetnum
Organization EAGLENA
Site BEDFORD
___ 7. Click OK. The TABLE Domain dialog box closes, saving your values.
•
•
•
•
Exercise 2: Creating an Object

In the following exercise, use the Database Configuration application to create a new
KNOWAPP object, which will be used later in this course to build a new application.
___ 1. Open the Database Configuration application (Go To > System Configuration
> Platform Configuration > Database Configuration).
___ 2. Click the New Object button. A new object opens on the Object tab, ready for
editing.
Field Value
Object KNOWAPP
Description Knowledge Base for Work Orders
Note: You will not be able to change the Level to ORG or SITE until after the attributes are
created.
___ 4. Save the record.
___ 5. Click the Attribute tab. The following attributes are automatically created.
Attribute Name Data Type Length
KNOWAPPID INTEGER 12
DESCRIPTION ALN 50
DESCRIPTION_
LONGALN (CLOB) 32000
LONGDESCRIPTION
HASLD YORN 1
•
•
•
•
___ 6. Use the New Row button to enter each of the following attributes.
Attribute Name Data Type Length
ADDITEMS ALN 50
ASSETNUM UPPER 12
CREATEDATE DATETIME 10
KNOWNUM UPPER 12
OBSERVATIONS ALN 1024
ORGID UPPER 8
SITEID UPPER 8
USERCREATE ALN 50
___ 7. For the CREATEDATE attribute, add the following values.
Field Value
Description Date Created

Default Value &SYSDATE&
•
•
•
•
Your screen should look like the following example.
___ 8. For the KNOWNUM attribute, add the following values.
Field Value
Description Knowledge Number

Required? [Selected]
Can Autonumber? [Selected]
KNOWNUM (click Yes in the system Message
Autonumber
box)
Search Type WILDCARD
Default Value &AUTOKEY&
Note: If the system displays the following message, click Yes.
•
•
•
•
Your screen should look similar to the following example.
___ 9. For the ASSETNUM attribute, add the following values.
Field
Same as Object ASSET

Same as Attribute ASSETNUM
psdi.app.workorder.FldWOAssetnum (case-
Class
sensitive)
Domain CUASSET
Search Type WILDCARD
Your screen should look similar to the following example.
•
•
•
•
___ 10. For the ORGID attribute, add the following values.
Field Value
Same as Object ORGANIZATION

Same as Attribute ORGID
___ 11. For the SITEID attribute, add the following values.
Field Value
Same as Object SITE

Same as Attribute SITEID
___ 12. For the USERCREATE attribute, add the following values.
Field Value
Description User Who Created

Default Value &USERNAME&
___ 13. Save your record. Your display should look similar to the following example.
___ 14. Save your record.
•
•
•
•
Exercise 3: Creating a New Index
Exercise 3: Creating a New Index

Follow these steps below to create a new index for your database object (KNOWAPP).
___ 1. Click the Indexes tab.
___ 2. Click New Row in the Indexes section. A new row opens for editing.
___ 3. Enter the following values and then save your record.
Field Value
Index KNOWAPP_NDX1
Enforce Uniqueness? {Selected}
Field Value
Column KNOWAPPID
Sequence 1
Ascending? [Selected]
___ 5. Save your record. Your new index, KNOWAPP_NDX1 is ready to be configured.
•
•
•
•
Exercise 4: Create New Relationships
For the index to take effect, you must reconfigure the database. You will do this
later.
Note: Indexes must contain at least one required field for best function.
You can drop an index by removing the data row the same way you remove any data row
throughout Maximo: by clicking the Trash button. The pending index to be dropped
receives a status of Delete, as shown in the following example.
The change will be identified and take effect pending configuration of the database.
Exercise 4: Create New Relationships

In this exercise you will create two relationships for your database object (KNOWAPP).
• The KNOWASSET relationship will be used to look up additional columns from

the ASSET object.
• The DRILLDOWN relationship enables you to use the drilling down feature for
both assets and locations.
___ 1. Click the Relationships tab.
___ 2. Click New Row.
Field Value
Relationship KNOWASSET
Where Clause assetnum=:assetnum
Child Object ASSET
•
•
•
•
Exercise 5: Configure the Database
___ 4. Click New Row and enter the following values.
Field Value
Relationship DRILLDOWN
Child Object DRILLDOWN
___ 5. Save your record. Your display should look similar to the following example.

To make changes to the database, complete the following steps:
___ 1. In the Database Configuration application, select Manage Admin Mode from
the Select Action menu (you need to be on the List tab). The Turn Admin Mode
ON dialog box is displayed. The default value is 5 for the Number of
Administrative Sessions Allowed and Number of Minutes for User Logout.
•
•
•
•
___ 2. In the Number of Minutes for User Logout field, change the value from 5 to 1
minute.
___ 3. Click Update Properties.A System Message dialog box is displayed
___ 4. Click OK.
___ 5. Click Turn Admin Mode ON. A System dialog box is displayed.
___ 6. In the Password field, enter maxadmin and in the Reason for Change field,
enter db change.
___ 7. Click OK. A System message is displayed.
___ 8. Click OK.
•
•
•
•
___ 9. To view the refresh status, after one minute, click Refresh Status. Your display
should look similar to the following example. A System dialog box is displayed.
___ 10. Click OK and close the dialog box. After you turn admin mode on, a message is
posted on the Bulletin Board of the product. The message informs users that they
should log out of the system.
___ 11. Click on the List tab. Select Apply Configuration Changes from the Select
Action menu. The Structural Database Configuration dialog box is displayed.
•
•
•
•
___ 12. Select the Do you have a current backup? check box.
___ 13. Click Start Configuring the Database.
___ 14. In the Password field, enter: maxadmin and in the Reason for Change field,
enter: db change.
___ 15. Click OK. A System message is displayed.
___ 16. Click OK.
___ 17. Refresh your screen by clicking the List tab and pressing Enter in the Object
field. The Status column should not have a status indicated.
•
•
•
•
___ 18. Select Manage Admin Mode from the Select Action menu.
___ 19. Click on Turn Admin Mode Off. A System message is displayed.
___ 20. In the Password field, enter: maxadmin and in the Reason for Change field,
enter: db change.
___ 21. Click OK.
___ 22. Click OK in the System Message box.
___ 23. Click Close. You are returned to the List tab.
•
•
•
•
In this exercise, you create a simple knowledge base application to capture asset
information. The new application uses the object created in the previous unit. You perform
the following tasks:
• Use the Application Designer to create a new application definition.
• Use the Security Groups application to allow users to access the new application.
Exercise 1: Create a New Application

Definition
In this section you use the Application Designer to create a new power application for your
KNOWAPP object.
___ 1. Open the Application Designer application (Go To > System Configuration >
Platform Configuration > Application Designer.)
___ 2. Click New Application Definition to insert a new application. The Create a New
Application dialog box opens.
Field Value
Application KNOWAPP
Description WO Asset KB
Key Attribute KNOWNUM
Main Object KNOWAPP
•
•
• 5-1
•
•
Exercise 2: Signature Security Options
___ 4. Save the record. Your display should look similar to the following example:
.
A power application has at least two tabs: List and Main. The first tab is the
standard Maximo List tab. The Main tab automatically populates with text boxes
linked to the various attributes of the KNOWAPP object.
Note: The power application provides a generic application with a field for each attribute
in the associated database object. If you did not reconfigure the database after adding the
attributes, the attributes will not appear here.You can customize the layout of the
application by adding sections and controls. This exercise will not customize the layout.
Exercise 2: Signature Security Options

WO Asset Knowledge Base power application is generated with a default set of signature
security options. You will verify these options.
To verify security options, complete the following steps:
___ 1. From the Select Action menu, select Add/Modify Signature Options.
•
•
•
•
Exercise 3: Select Action Menu Items
The Add/Modify Signature Options dialog box opens.
___ 2. Click the View Details button for the various options, and verify the values.
Exercise 3: Select Action Menu Items

A default set of Select Action menu items is assigned to new power applications. You can
use the Application Designer Add/Modify Select Action menu to add or modify Select
Action menu items.
Before adding a menu item to the Select Action menu, you create a signature security
option to associate it with the application as you did in the previous exercise. Select Action
menu items have a Position field property. The position property is a relative position and
not an absolute position.
•
•
•
•
Exercise 4: Toolbar Buttons
___ 1. From the Select Action menu, select Add/Modify Select Action Menu. The
Add/Modify Select Action Menu dialog box opens.
___ 2. View and verify the options.

A default set of toolbar buttons is assigned to new power applications. You select the Add/
Modify Tool bar Menu option to add or to modify the toolbar buttons. You will not be able
to modify the position of many of the default toolbar buttons.
Before adding a toolbar button, you need to create a signature security option to associate
it with the application.
The Select Tool bar Button items have a Position field property. The position property is
a relative position and not an absolute position.
Complete the following steps to verify that toolbar menu items are part of your new
application.
___ 1. From the Select Action menu, select Add/Modify Tool bar Menu. The Add/
Modify Tool bar Menu dialog box opens.
___ 2. Verify the following information for the INSERT toolbar menu item.
Field Value
Key Value INSERT

Header Description [Leave blank]
•
•
•
•
Field Value
Element Type OPTION

Subposition 1
Image nav_icon_insert.gif
Visible? [Selected]
Access Key CTRL+ALT+I
Tabs ALL
___ 3. Verify the following information for the SAVE toolbar menu item.
Field Value
Key Value SAVE

Element Type OPTION
Position 1
Subposition 2
Image nav_icon_save.gif
Visible? [Selected]
Access Key CTRL+ALT+S
Tabs MAIN
___ 4. Verify the following information for the CLEAR toolbar menu item.
Field Value
Key Value CLEAR

Element Type OPTION
Position 1
Subposition 3
Image nav_icon_clear.gif
Visible? [Selected]
Access Key CTRL+ALT+C
•
•
•
•
Field Value
Tabs MAIN
___ 5. Verify the following information for the AT2 toolbar separator.
Field Value
Key Value AT2

Element Type SEP
Position 2
Subposition 0
Visible? [Selected]
Tabs [Leave blank]
___ 6. Verify the following information for the PREVIOUS toolbar menu item.
Field Value
Key Value PREVIOUS

Element Type OPTION
Position 2
Subposition 1
Image nav_icon_previous.gif
Visible? [Selected]
Access Key CTRL+ALT+P
Tabs MAIN
___ 7. Verify the following information for the NEXT toolbar menu item.
Field Value
Key Value NEXT

•
•
•
•
Exercise 5: Search Menu Items
Field Value
Element Type OPTION

Position 2
Subposition 2
Image nav_icon_next.gif
Visible? [Selected]
Tabs MAIN
___ 8. Before you click OK, verify that your display looks similar to this screen capture.
___ 9. Click OK. The Add/Modify Toolbar Menu dialog box closes.
Exercise 5: Search Menu Items

A default set of Search menu items is assigned to new applications. You use the Add/
Modify Search Menu option of the Application Designer to add or to modify the Search
menu items.
Before adding a menu item to the Search menu, you must create a Signature Security
option to associate it with the application. These have been created beforehand.
The Search menu has been created for you; so you will verify the settings.
Complete the following steps to verify the default Search menu items in your new WO
Asset Knowledge Base application.
•
•
•
•
Exercise 6: Modify the List Tab
___ 1. From the Select Action menu, select Add/Modify Search Menu.
The Add/Modify Search Menu dialog box opens.
___ 2. Verify the information in the dialog box.

Before you complete your WO Asset Knowledge Base power application, you need to
modify the List tab so that it will work properly with your application.
The List tab holds Table Column controls. Table Column controls are always added to
the left of the current Table Column control.
To make the necessary modifications, complete the following steps:
___ 1. In the Application Designer workspace, click the List tab.The List tab opens in
the Workspace.
___ 2. Right-click the Table title, open the Properties dialog box, and enter the
following information.
Field Value
Label Knowledge Base
___ 3. Close the Table Properties dialog box and save the record.
•
•
•
•
___ 4. Click the Control Palette icon.
Control Palette icon
Table Column icon
___ 5. To add a Table Column control, drag and drop a Table Column control onto the
Description control. The new table column will appear to the left.
This is the first table column
___ 6. Open the Control Properties dialog box for the first Table Column control and
enter the following information.
Field Value
Show Filter [Selected]

Type EVENT
Attribute KNOWNUM
Event toggleselectrow (if not available by default)
Event Description Select Row {0} (if not available by default)
•
•
•
•
Your Table Column control should look similar to the following example.
___ 7. Close the Table Column Properties dialog box.
___ 8. Open the Control Properties dialog box for the second Table Column control
and enter the following information.
Field Value
Show Filter? [Selected]

Label Knowledge ID
Attribute KNOWNUM
Event selectrecord
Event Description Go To %1
•
•
•
•
Exercise 7: Granting Access
Your Table Column control should look similar to the following example.
___ 9. Close the Table Column Properties dialog box. Your List tab should look similar
to the following example.
___ 10. Save you record.

You cannot see all of the features of your new application until you grant access to a
specific user or users through a security group. Because the MAXADMIN security group
has full access to all applications, this security group should have full access, at the very
least.
•
•
•
•
To grant access to other users, complete the following steps:
___ 1. Open the Security Groups application (Go To > Security > Security Groups).
___ 2. Search and retrieve the MAXADMIN security group.
___ 3. Click the Applications tab.
___ 4. Using the Filter, find and select your Knowledge Base application. Your WO
Asset Knowledge Base application opens.
___ 5. Click the Grant Listed Options for This Application button. A dialog box
opens.
___ 6. Click OK.

•
•
•
•
Exercise 8: Verify Your Work
___ 7. Click the Grant Listed Applications button and select All Above.
Your display should look similar to the following example. (Notice that all the
check boxes are selected.)
___ 8. Click OK.

Now that you have granted access to the MAXADMIN security group, you can sign in to
Maximo as a user assigned to this security group. Because Mike Wilson is assigned to this
group, and you are already signed in, you can go directly to your new Knowledge Base
power application.
Complete the following steps to verify your work.
___ 1. Sign out and sign back in for the security changes to take effect.
•
•
•
•
___ 2. From the Go To menu, select WO Asset KB from the Work Order module. Your
Knowledge Base application opens.
___ 3. Test the functions of your application by performing the following tasks, at a
minimum:
– Create at least four new records.

– Use the Asset field’s Select Value menu.
– Delete one of the records.
– Find all records using the List tab.
– Navigate your records.
– Make changes to your records.
– Verify any other functions that you want to investigate.
___ 4. When you are finished, return to the Start Center.
•
•
•
•
Before going into the steps on how to define, create, and distribute a sample snapshot
package (all performed in the source environment), consider the following scenario.
You have created a Service Request (SR) workflow process that automatically sets the
internal priority of a new SR. The process then places the SR into the Inbox of a Service
Desk manager. The manager reviews the SR and places it into the queue of a Service Desk
agent. The agent receives an automatic e-mail notification to take action based on the
queued SR.
This workflow process definition with its constituent roles, actions, and communication
templates comprises the configuration changes that you want to migrate from source
environment to target environment.
This workflow scenario is not intended as a best practices approach. It serves as a simple
workflow example facilitating the exercises depicted for the Migration Manager
application in this lab.
Exercise 1: Organizing the Content

In this section you use the Migration Groups application to organize the content (see
Appendix A) that comprises the types of records used to create:
• Workflow process
• Communication template
• Action
• Role
___ 1. Using the source environment (http://vm100:9999/maximo), sign in to Maximo

Asset Manager 7.1 as user wilson with password wilson.
___ 2. From the Go To menu, select System Configuration > Migration > Migration
Groups.
___ 3. After the Migration Manager application opens, place the cursor in the List box
and press Enter. All of the available migration groups are displayed.
•
•
• 6-1
•
•
___ 4. Select and click the BPM (Business Process Management) entry. The Migration
Group tab opens, displaying the BPM object group.
The two sections are Migration Objects and Dependency. The first section, Migration
Objects for BPM, lists the migration objects (object structures) that are part of the BPM
group. These objects include:
• DMACTION
• DMACTIONGROUP
• DMROLE
• DMCOMMTEMPLATE
• DMESCALATION
• DMWFPROCESS
• DMINBOUNDCOMM
You chose the BPM group because the object structures of interest to you are already
members of the BPM group. In the current scenario, you have not built any escalation
(DMESCALATION), nor do you need to migrate any Email Listener configurations
(DMINBOUNDCOMM).
The second section, Dependency, lists other groups on which the BPM migration group is
dependent. This can be the case if you have put together a new custom application including
new BOs, domains, tabs, dialog boxes, and so on. However, this is not the case for this
scenario. All you need to migrate is a single workflow process and its constituent data.
Because no dependencies are required, you discard all the entries in the Dependency
section. You cannot change the migration groups shipped with the product (notice that they
are marked Internal), so you duplicate the BPM group.
•
•
•
•
___ 5. With the BPM group selected, click Select Action > Duplicate Migration Group
to duplicate the BPM group.
___ 6. In the name field, type MYBPM.
___ 7. In the Description field, type Workflow only. Accept the default order of 12
assigned to this new group.
___ 8. You can now remove the existing dependencies that were copied over from BPM.
Delete each dependency using the Delete icon to the right in the Dependency
section.
You are now left with just the object structures that are members of the MYBPM group.
You only need the DMACTION, DMROLE, DMCOMMTEMPLATE, and
DMWFPROCESS object structures. You do not need the DMACTIONGROUP,
DMESCALATION, or DMINBOUNDCOMMCFG object structures because you have no
changes in these areas.
Use these arrows to view more items
___ 9. Delete DMACTIONGROUP, DMESCALATION, and

DMINBOUNDCOMMCFG from the Migration Objects table window.
___ 10. Save the group.
You have created a migration group that you can use to migrate only workflow definitions
and related data without other data such as data dictionary or application.
•
•
•
•
Exercise 2: Defining the Migration Package

In the source environment, you need to define a package, approve it, and activate it. Later
in this exercise, you will create a physical package based on the definition and distribute it.
Manager.
___ 2. Click New Package Definition in the application toolbar to activate the Package
Definition tab.
___ 3. In the Package Definition Name field, type mmwf. Notice that the Source field
is automatically populated.
___ 4. Accept the default value of SNAPSHOT for the Type field and the default value
of 100 for the Batch Size field.
___ 5. Click New Row in the Migration Groups section.
___ 6. Click the Detail Menu, and then click Select Value.
___ 7. From the Select Value dialog box, select MYBPM. After the value is returned to
the Migration Groups section, click the Save icon.
You now have included the newly created MYBPM group in a package definition. By
doing so, you are declaring that the content of the package contains workflow definitions
and related data.
The scenario calls for the migration of a workflow process and its related data. With the
current package definition, all workflow processes, roles, actions, and active
communication templates in the source environment will be brought into the physical
package during package creation. This is not the migration requirement. You need to filter
the package contents to just the specific MMWF workflow-related roles, actions, and so on
(see Appendix A). You can set up such a filter as part of the definition by completing the
following steps.
•
•
•
•
___ 8. Click the Set Where Clause icon to the right of the MYBPM entry in the
Migration Groups section. The resulting dialog box lists the migration objects
included in the MYBPM group.
In the next step, you attach a SQL Where condition to each migration object. This action
ensures that the physical package, when created, will contain only the MMWF workflow
process and related records.
___ 9. Select the DMACTION migration object. (The prefix DM means data
migration.) Click the SQL Expression Builder icon to the right of the row.
___ 10. From the SQL Expression Builder dialog box, select the Action attribute (click
the blue square).
___ 11. Type the ='MMACT' condition immediately following the Action attribute.
Include the equal sign and the single quotation marks surrounding MMACT. See
Appendix A regarding the user-defined MMACT condition.
By adding this WHERE condition, you have filtered action records to just the
MMACT action that is being used by workflow MMWF.
___ 12. Click OK.
___ 13. Repeat steps 10 through 12 to set the remaining three attributes with specific
conditions that apply only to your MMWF process.
___ a. Click each main object from the Set Where Clause dialog box to display the
attributes that are specific to the main object.
•
•
•
•
___ b. Select the attribute (for example, maxrole) from the SQL Expression
Builder dialog box.
___ c. Type the condition, with the quotation marks, exactly as shown in the
following table. The MMNOTIF, SDAGNT, SDMGR, and MMWF are
user-defined and are explained in Appendix A.
Main Object Select Attribute Type Condition
DMCOMMTEMPLATE templateid ='MMNOTIF'

DMROLE maxrole in ('SDAGNT','SDMGR')
DMWFPROCESS processname ='MMWF'
___ d. Click OK after assigning attributes and conditions to each migration object.
You are now ready to approve the package.
___ 14. Click the Change Status icon in the Migration Manager application toolbar.
___ 15. From the drop-down list of the Change Status dialog box, select Approved
Package Definition.
___ 16. Click OK.
You are now ready to activate the package.
___ 17. From the Select Action menu in the toolbar, click Activate/Deactivate Package
Definition. You will notice that the Active check box to the right of the Package
Definition tab header area is now selected.
You have completed the tasks required to prepare for a physical package.
•
•
•
•
Exercise 3: Creating the Migration Package
You can now visually verify the contents of the package definition using the Package
Definition Structure tab.
___ 18. In the Migration Manager application, click the Package Definition Structure
tab. A hierarchical view of your package definition is displayed.
___ 19. To verify the contents, drill down into the Migration Groups node of the
hierarchy. You will see that MYBPM is immediately under Migration Groups.
___ 20. Expand MYBPM and verify the individual migration objects within the group.
You can also open each migration object and verify each BO within the object.
This visual verification step helps you determine the total contents of any physical
package based on this definition.

Before creating a migration package, you must identify the target environments to which
you plan to distribute this package. To familiarize yourself with the system landscape,
always identify various target environments. You will identify your target environment in
this step. A set of targets can be defined in the Migration Manager application without
having a single package defined. You can then identify target environments ahead of time
and declare them in your source environments.
For the purpose of this scenario, your target will be a folder on a file system. The file system
must be accessible to the application server where Maximo is executing. Later, you will
download this package to your client machine.
___ 1. In the Migration Manager application toolbar, click the Manage Targets icon.
___ 3. Enter a target name. For this example, enter Production.
___ 4. Enter or select Type as FILE, because you want to distribute the physical package
in the form of a file.
•
•
•
•
___ 5. In the Database URL or File Path field enter c:\ (or other appropriate folder if
you have your own local Maximo build). The physical package file will be copied
to this folder upon distribution. This folder is accessible to the application server.
___ 6. Click OK to save this new target and close the Manage Targets dialog box.
___ 7. In the Migration Manager application, click the Distribution tab.
You are now linking your approved package definition to the newly defined target. A
distribution is what links a package to a particular target.
___ 8. Click New Row in the Distributions section.
___ 9. From the new row that is created, use the lookup on the Target Name field or type
Production.
___ 10. Click Save in the application toolbar to save this distribution record.
•
•
•
•
___ 11. In the Migration Manager application, click the Package tab.
___ 12. Click Create to begin the package creation.
Creating a package might take several minutes, depending on the volume of data
to be collected. Data collection (or export) is based entirely upon the package
definition. When you click the Create button, the Upload Compiled Sources
dialog box opens.
This dialog box serves two purposes:
– To collect compiled sources that might be part of the package: You upload
compiled sources using this dialog box. Compiled sources are outside of the
database, and they might be class files or properties files that are included in
the EAR files.
– To enter read-me information regarding the particular physical package
that can be reviewed in a target environment before deployment: Because
you did not specify any compiled sources for your package, you can ignore
the Compiled Sources section.
___ 13. In the Read-Me Information field, enter text that describes the content of the
package. For example, enter Workflow artifacts for MMWF workflow
targeting Service Requests.
___ 14. Click Continue to continue the package creation.
___ 15. Click OK when package creation is complete and the progress dialog box displays
the Done message.
When created, the Package tab refreshes to show the new package record. The Manifest
subtab below the Packages section shows the manifest for the package. Review the
manifest and look at the listing of various migration objects that now contain actual data for
the MMWF workflow process.
•
•
•
•
Exercise 4: Distributing the Migration Package
Exercise 4: Distributing the Migration Package

You are now ready to distribute the newly generated package to the target you associated
with the package definition.
___ 1. In the Packages section of the Migration Manager application, click the
Distribute button to the right of the Create button.
___ 2. Indicate the target by selecting the box to the left of the Distribution row and
clicking OK.
Distribution is initiated. The progress dialog box opens, and messages are posted
to the dialog box as distribution progresses. When distribution is complete, the
dialog box displays a Done message.
___ 3. Click the OK button to close the dialog box.
You have now distributed the contents of the physical package to a file that currently is
located on the file system of the application server. You can, if necessary, download this
file to the client machine where you are working.
You also can download the package file to the client machine from where you are accessing
Maximo. Click the Download Package File icon to the right of the package record in the
Packages section of the Package tab.
Up to this point, you have completed all of the migration activities necessary in the source
environment. You started with the identification of changes to be migrated. You
determined the need to organize content and then defined a package that would serve as a
template for physical packages. You approved and activated the definition. After
associating a target with the definition, you created and distributed the package to the
chosen target.
Exercise 5: Deploying the Migration Package

You perform the deployment task on the target machine. For the purposes of this lab, you
connect your browser to another instance of the MAM71 database. This technique allows
you to use the same VMware image, but by accessing two different MAM71 instances, in
effect you are accessing two different environments.
Complete the following steps:
___ 1. Open a new tab in your Mozilla or Internet Explorer 7 browser (or a new browser
window).
___ 2. Connect to the target environment by using the URL http://vm100:8888/maximo

(the port number is different from the source environment, which is 9999).
•
•
•
•
___ 3. Sign in with user name wilson and password wilson.
Manager.
___ 5. Click Select Action > Upload Package.
___ 6. From the Upload Package box, click Browse and locate the package file that you
downloaded from the source environment.
___ 7. Select the package file. Click Open to bring back the folder and file information
into the Upload Package dialog box.
___ 8. Click OK in this dialog box to physically upload the package file into the test
environment.
___ 9. From the application toolbar, click the Deploy Package button. A pop-up dialog
box opens, displaying the newly uploaded package.
To begin deployment from the Deploy Package dialog box, you must first confirm that you
have a database backup in place. Remember that the Migration Manager cannot roll back
the package. If deployment fails, your only option to recover might be to restore your
database from a backup.
___ 10. Select the Do you have a current database backup? check box. Then click the
Deploy button.
The electronic signature authentication dialog box is displayed.
___ 11. Enter the password for the currently logged-in user (wilson) and a memo into the
Reason for Change field. Click OK to proceed with deployment.
___ 12. Click OK after the deployment progress dialog box posts a Done message. When
you review the contents of the Package tab, you will see a row for the package
that you just deployed. It shows a status of DEPLOYED.
For this package, the deployment does not require you to log out or restart the application
server to see the changes take effect. Therefore, you can access the Workflow Designer
application and bring up the MMWF workflow process. You will see that the workflow is
laid out exactly as in the source environment. It is disabled and inactive. Now you can
validate this process, enable it, and activate it.
•
•
•
•
•
•
•
•
The following list provides an overview an a brief explanation of the exercises in this unit:
• Create and Configure JMS Queues in WebSphere
This includes exercises 1 through 11. The main idea here is to create three
destination or queues for your transactions (messages in Java language). You
perform all this activities in the WebSphere application.
– Continuos Inbound (CQINBD)

– Sequential Inbound (SQINBD)
– Sequential Outbound (SQOUTBD)
• Configure Maximo settings
Configuring settings in Maximo take place in the Maximo Asset Manager

application and it includes exercises
• Test an Inbound transaction
From the Assets Application, you make changes to an asset in the list.
• Test an Outbound transaction
You manually modify the outbound XML file, pretending that an external system
has made changes to the file (transactional changes, such as approved a PO) and
import that xml file into Maximo.
You have just been told your system will be configured with the Maximo Enterprise
Adapter interfacing with other products. You need to configure the Java Messaging System
(JMS) queues and rebuild the EAR file(s)
Note: Bus names and queue names are case sensitive.
•
•
• 7-1
•
•
Exercise 1: Create a WebSphere Messaging Resource (Bus)
Exercise 1: Create a WebSphere Messaging

Resource (Bus)
___ 1. Launch Internet Explorer and open the WebSphere Administrative Console by
typing the following URL:
http://vm100:9060/ibm/console
___ 2. Security is not enabled so you can enter any username or just click enter.
___ 3. Click System administration > Console preferences.
___ 4. Ensure that the Synchronize changes with Nodes option is selected, and then
click Apply.
___ 5. Click Service Integration > Buses to open the Buses dialog.
___ 6. A bus is a group of interconnected servers and clusters that have been added as
members of the bus. Click New to open the Buses >New dialog box where you
can add a new service integration bus.
___ 7. Enter intjmsbus as the name of the new bus in the Name field.
___ 8. Click Next.
___ 10. Click Save. This step propagates the JMS bus setup to the cluster configuration.
Confirm that build completed screen displays the following:
– Bus name, for example, intjmsbus.

– Auto-generated, unique ID (UUID), for example, 4BCAC78E15820FED.
– The Secure field is unchecked.
Exercise 2: Add a Server to the Service

Integration Bus
Complete the following steps to add a server to the service integration bus:
___ 1. From the WebSphere® Administrative Console, click Service Integration >
Buses to open the Buses dialog box.
___ 2. Click intjmsbus to open the Buses > intjmsbus dialog box.
___ 3. Under Topology, click Bus members.

•
•
•
•
Exercise 2: Add a Server to the Service Integration Bus
___ 4. In the Buses > intjmsbus > Bus members dialog box, click Add to open the Add
a new bus member dialog box.
___ 5. Click the Server drop-down arrow, and select the server name
vm100Node01:MAM71 to add to the bus, and then click Next.
___ 6. Ensure that the File store radio button is selected, and then click Next.
___ 7. From the Provide the message store properties panel, click Next.
___ 9. Click Save.
___ 10. Click OK.
___ 11. Click Service Integration > Buses to open the Buses dialog box
___ 12. Click intjmsbus.
___ 13. Change the value of the High message threshold field to a minimum value of
500,000 messages, and then click Apply.
___ 14. If the number of messages awaiting processing exceeds the High Message
Threshold you set, the application server will take action to limit the addition of
new messages in the processing queues.
Depending on your message requirements, you may want to enter a higher

message threshold value. You can determine an optimal message threshold setting
by monitoring the messaging in/out queues and the impact of the message
threshold setting on system performance. You might, for example, lower the
threshold value if a higher value is degrading system performance.
If you decide to change the High message threshold setting after the initial
configuration, open the Additional Properties menu in the Administrative Console
and change the threshold value for each child configuration.
___ 15. Click Save.
___ 16. Click OK.
•
•
•
•
Exercise 3: Create the Service Integration Bus Destination for the Continuous Inbound (CQINBD) Queue
Exercise 3: Create the Service Integration Bus

Destination for the Continuous Inbound
(CQINBD) Queue
___ 1. From the WebSphere Administrative Console, click Service Integration > Buses
to open the Buses dialog box (if not already open).
___ 3. Click Destinations under Destination resources to open the Buses > intjmsbus >
Destinations dialog box.
___ 4. Click New to open the Create new destination dialog box.
___ 5. Leave Queue checked as the destination type, and click Next to open the Create
new queue dialog box.
___ 6. Type CQINBD in the Identifier field and Continuous Queue Inbound in the
Description field, then click Next to open the Create a new queue for point-to-
point messaging dialog box.
Note: Queue names are case sensitive. Use all upper-case to specify queue names.
___ 7. Select the Bus Member pull-down and choose a server, such as
Node=vm100Node01:Server=MAM71 as the bus member that will store and
process messages for the CQINBD bus destination queue.
___ 8. Click Next.
___ 9. Review your selections, then click Finish to complete the creation of the
CQINBD bus destination queue.
___ 10. Navigate to Buses > intjmsbus > Destinations, then click CQINBD to open the
configuration dialog box where you must make the following changes:
– Change the Maximum failed deliveries value to 1.

– Click None as the Exception destination value.
•
•
•
•
Exercise 4: Create the Service Integration Bus Destination for the Sequential Inbound (SQINBD) Queue
This is the maximum number of times you want the system to process a failed
messaging attempt before forwarding the message to the exception destination.
___ 11. Click Apply.
___ 12. Click Save.

Destination for the Sequential Inbound
(SQINBD) Queue
to open the Buses dialog box.
•
•
•
•
Exercise 4: Create the Service Integration Bus Destination for the Sequential Inbound (SQINBD) Queue
___ 6. Type SQINBD in the Identifier field and Sequential Queue Inbound in the
process messages for the SQINBD bus destination queue.
___ 8. Click Next.
SQINBD bus destination queue.
___ 10. Navigate to Buses > intjmsbus > Destinations, then click SQINBD to open the
configuration dialog box where you must make the following changes:

___ 12. Click Save.
•
•
•
•
Exercise 5: Create the Service Integration Bus Destination for the Sequential Outbound (SQOUTBD) Queue

Destination for the Sequential Outbound
(SQOUTBD) Queue
to open the Buses dialog box.
___ 6. Type SQOUTBD in the Identifier field and Sequential Queue Outbound in the
process messages for the SQOUTBD bus destination queue.
___ 8. Click Next.
SQINBD bus destination queue.
___ 10. Navigate to Buses > intjmsbus > Destinations, then click SQOUTBD to open
the configuration dialog box where you must make the following changes:

___ 12. Click Save.
•
•
•
•
Exercise 6: Create the JMS Connection Factory
Exercise 6: Create the JMS Connection

Factory
You add a connection factory for creating connections to the associated JMS provider of
point-to-point messaging queues.
___ 1. From the WebSphere® Administrative Console, click Resources > JMS >
Connection factories.
___ 2. From the Scope drop-down list select Cell=vm100Cell01.
___ 3. Click New.
___ 4. Verify that the Default Messaging Provider is selected and click OK.
___ 5. Enter the following information, and then click OK:
___ a. Name: intjmsconfact.
___ b. JNDI name: jms/maximo/int/cf/intcf.
•
•
•
•
Exercise 7: Create the Continuous Inbound (CQIN) JMS Queue
___ c. Bus name: Select intjmsbus.
___ 6. Click Apply.
___ 7. Click Save.
Exercise 7: Create the Continuous Inbound

(CQIN) JMS Queue
You must create a JMS queue (CQIN) as the destination for continuous inbound point-to-
point messages.
Queues.
___ 2. From the Scope drop-down list, select Cell=vm100Cell01.
___ 3. Click New.
___ 5. Enter the following information:
– Name: CQIN
•
•
•
•
Exercise 7: Create the Continuous Inbound (CQIN) JMS Queue
– JNDI name: jms/maximo/int/queues/cqin

– Bus name: intjmsbus
– Queue name: CQINBD
___ 6. Click Apply.
___ 7. Click Save.
•
•
•
•
Exercise 8: Create the Sequential Inbound (SQIN) JMS Queue
Exercise 8: Create the Sequential Inbound

(SQIN) JMS Queue
You must create a JMS queue (SQIN) as the destination for sequential inbound point-to-
point messages.
Queues.
___ 3. Click New.
___ 5. Enter the following information, and click OK.
– Name: SQIN
– JNDI name: jms/maximo/int/queues/sqin

– Bus name: Select intjmsbus
– Queue name: Select SQINBD
___ 6. Click Apply.
•
•
•
•
Exercise 9: Create the Sequential Outbound (SQOUT) JMS Queue
___ 7. Click Save.
Exercise 9: Create the Sequential Outbound

(SQOUT) JMS Queue
You must create a JMS queue (SQOUT) as the destination for sequential outbound point-
to-point messages.
Queues.
___ 3. Click New.
___ 5. Enter the following information, and click OK.
– Name: SQOUT
– JNDI name: jms/maximo/int/queues/sqout

– Bus name: Select intjmsbus
•
•
•
•
Exercise 9: Create the Sequential Outbound (SQOUT) JMS Queue
– Queue name: Select SQOUTBD
___ 6. Click Apply.
___ 7. Click Save.
•
•
•
•
Exercise 10: Create JMS Activation Specification for the Continuous Inbound Queue (CQIN)
Exercise 10: Create JMS Activation

Specification for the Continuous Inbound
Queue (CQIN)
You must activate the continuous inbound queue (CQIN) before it can receive messages.
Complete the following steps to activate the CQIN queue:
Activation Specifications.
___ 3. Click New to complete the General Properties section for the new JMS activation
specification.
___ 4. Click OK.
___ 5. Enter the following information, and then click OK:
– Name: intjmsact
Note: Queue names are case sensitive. Use lower-case to specify queue names.
– JNDI name: intjmsact

– Destination type: Queue (default)
– Destination JNDI name: jms/maximo/int/queues/cqin
– Bus name: intjmsbus
– Maximum concurrent endpoints: 10
___ 6. Click Apply.
___ 7. Click Save.
•
•
•
•
Exercise 11: Stop and Start all WebSphere Application Server Services.
Exercise 11: Stop and Start all WebSphere

Application Server Services.
You must stop all of the following three application servers and then restart them in the
order listed below:
___ 1. Stop the MAM71 Application server from the WAS Console
___ 2. Stop the Node Agent from the following directory:
C:\IBM\WebSphere\AppServer\profiles\Custom01\bin\stopNode
___ 3. Stop the IBM WebSphere Application Server V6.1 vm100CellMananager01

from the Services panel by right-clicking the service name and selection Stop.
___ 4. Restart all three services in the reverse order: begin with the
vm100CellManager01, then the Node Agent, and finally the MAM71
application server.
Exercise 12: Setting System Properties

___ 1. From the Go to menu select System Configuration >>Platform Configuration
>> System Properties.
___ 2. Click the Filter link in the Global Properties bar.
___ 3. Type mxe.int in the Property Name field and press Enter.
___ 4. Open the mxe.int.globaldir property.
•
•
•
•
___ 5. In the Global Value field specify c:\temp.
___ 6. Save you changes
___ 7. From the Global Properties section, open the mxe.int.flatfiledelimiter property.
___ 8. For Global Value, enter the pipe sign on your key board (|). It is beneath your
Backspace button.
___ 9. Save you changes.
•
•
•
•
___ 10. Check the check boxes of both properties: mxe.int.globaldir and
mxe.int.flatfiledelimiter.
___ 11. From the Select Action menu, click Live Refresh.
___ 12. From the Global Properties section, open the mxe.int.webappurl property (you
may need to advance to the next page of Global Properties).
___ 13. Specify the correct URL on the Global Value field. In this case, change the port
number to 9999 (ensure the colon is included).
___ 14. Save your changes.
___ 15. Check the check box of the mxe.int.webappurl Global Property.
___ 16. From the Select Action menu, click Live Refresh.
___ 17. Click OK.
•
•
•
•
Exercise 13: Configuring Cron Task
Exercise 13: Configuring Cron Task

___ 1. From the Go to menu select System Configuration >>Platform Configuration
>> Cron Task Setup.
___ 1. Place your cursor in the Cron Task list box and press Enter.
___ 2. Click and open the JMSQSEQCON Cron Task.
___ 3. Open the SEQQIN instance name and change the schedule to 10 seconds.
___ 4. Open the SEQQOUT instance name and change that schedule to 10 seconds.
___ 5. Check the Active check boxes for both Cron Task Instance Names.
Exercise 14: Enable Integration Components

You enable Integration Components, so when you update an asset it will be written to an
XML file.
___ 1. From the Go to menu select Integration >>Integration Structure.
___ 2. In the Consumed by field to the right, type integration and press Enter.
___ 3. Open the MXASSET object.
•
•
•
•
Exercise 14: Enable Integration Components
The source objects for MXASSET, define the content of MXASSET object
structure.
___ 4. From the Select Action menu, click Generate Schema/View XML.
___ 5. Click OK in the System Message box.
Click OK to close the window.
•
•
•
•
Exercise 15: Publish Channels
Exercise 15: Publish Channels

Publish Channels is a task specific for outbound settings.
___ 1. From the Go to menu select Integration >>Publish Channels.
___ 2. Place your cursor in the Publish Channel field and press Enter.
___ 3. Click and open the MXASSETInt Publish Channel.
___ 4. From the Select Action menu, click Enable Event Listener.
___ 5. Click OK.
Exercise 16: End Point Configuration

End Point configuration is about specifying the output location of the XML file.
___ 1. From the Go to menu select Integration >>End Points.
___ 2. Press Enter in the list box.
___ 3. Click and open the MXXMLFILE End Point.
___ a. Open the FILEDIR Property.
___ b. Type c:\temp in the Value field in the Details section.
___ c. Open the PRETTYPRINT Property.
___ d. Specify 1 (true) in the Value field in the Details section.
•
•
•
•
Exercise 17: External Systems
Exercise 17: External Systems

___ 1. From the Go to menu select Integration >>External Systems.
___ 3. Click and open the EXTSYS1 System.
___ 4. Check the Enabled? box.
___ 6. Click the Publish Channels tab.
___ 7. Note that the End Point value in the top left (under System) is MXXMLFILE.
There is no need for further action in this application, merely a visual verification.
Exercise 18: Test an Outbound Transaction

You are now ready to test an outbound transaction. In this exercise, you will open the
Assets application, make a change, for example to the description and save the record.
___ 1. From the Go to menu select Assets >>Assets.
___ 3. Select Asset number 7500 (first in the list)
___ 4. Change Description to Outbound test.
•
•
•
•
Exercise 19: Test an Inbound Transaction
___ 6. Using Windows Explorer, From the C:\temp folder, open the
EXTSYS1_MXASSETInterface_<12.....>.xml file with Note pad.
Exercise 19: Test an Inbound Transaction

In this exercise, you will manually edit the XML file, pretending that you are an external
system that has acted upon the original XML file or transaction.
___ 1. Using your text editor make the following changes to the XML file:
___ a. Change the beginning tab from PublishMXASSET to SyncMXASSET
___ b. Repeat the same change for the closing tag in the bottom of the file.
•
•
•
•
Exercise 20: Importing Inbound Data
___ c. Change the content of the Description tag from Outbound to Inbound test.
Change from Publish to Sync
Also the closing tag
Change description to Inbound test
___ 2. Save and close the XML file.

Having made the manual changes to the XML file, you are now ready to import the changes
made from an external application into Maximo.
___ 1. From the Go to menu select Integration >>Enterprise Services.
___ 3. Select MXASSETInt (first one in the list) Enterprise Service.
___ 4. Note that the Operation value is Sync.
___ 5. From the Go to menu select Integration >> External Systems.
___ 7. Open the EXTSYS1 system.
___ 8. Click the Enterprise Services tab.
___ 9. Open the MXASSETInterface Enterprise Service.
•
•
•
•
___ 10. Uncheck the Use Continuous Queue check box in the bottom right corner.
___ 12. Click Data Import (button of the window).
___ 13. In the Data Import dialog box, use the Browser button to navigate to c:\temp and
import the XML file.
___ 14. Click OK.
In 10 seconds the data is dropped in SQIN queue.
___ 15. Go to the Assets application
___ 16. Open Assets and note the new description: Inbound test.
•
•
•
•
In this unit, you perform the following exercises:
• Create a result set query
• Modify the Start Center
• Create a new Start Center
• Run a BIRT report from Work Order Tracking
• Generate all systems report
• Set application security
• Install Eclipse and BIRT
• Configure the Environment for BIRT
• Configure BIRT
Exercise 1: Create a Result Set Query
In this exercise, you will create a public query for use with a Start Center portlet.
___ 1. Sign in to the system as user name wilson, password wilson.
___ 2. Open the Work View application in the Administration module.
___ 3. Open the More Search Fields dialog box (Advanced Search > More Search
Fields).
___ 4. Enter the following information.
Field Value
Status =WSCH, =WAPPR, =NEW

Site =BEDFORD
•
•
• 8-1
•
•
The dialog box should look like the following example.
___ 5. Click Find.
___ 6. To modify the result set so that it is in order by priority, open the Where Clause
dialog box (Advanced Search > Where Clause).
•
•
•
•
___ 7. At the end of the Where clause statement, type order by priority.
___ 8. Click Find.
___ 9. To save the current query, open the Save Current Query dialog box (Save Query
> Save Current Query) and enter the following information.
Field Value
Query Name RSDEMO

Description Result set demo
•
•
•
•
Exercise 2: Modify the Start Center
___ 10. Select the Public? check box.
___ 11. Click OK.

In this exercise you will modify a Start Center to display a list of all tickets, work orders,
and activities. These items will be displayed in color, based on their priority.
___ 1. On the Start Center, click Change Content/Layout.
___ 2. In the Right Column content, click Select Content.
___ 3. In the Available Portlet list, select Result Set.
___ 4. Click OK.
___ 5. For all KPI Graph rows, click the Delete Row icon.
The screen should look like the following example.
___ 6. Click Finished.
•
•
•
•
The Start Center should look like the following example.
___ 7. To edit the Result Set portlet, click the Edit icon. In the Display Name field, type
RSDemo.
___ 8. On the Available Queries tab, select the RSDEMO query.
The Column Display tab shows the Query Column and Description columns.
.
___ 9. On the Column Display tab, select these columns:
– Status
– Priority
– Reported Date
– Description
___ 10. Click the Display Option tab. For the Condition Attribute field, use the Select
Value icon and select PRIORITY.
•
•
•
•
Exercise 3: Create a KPI
___ 11. Click Add Color Alert and enter the following alerts (click Add Color Alert,
each time that you want to add a new Expression).
Expression Expression Value Color
Equal to 1 Red
Greater than or equal to 2 Purple
Greater than or equal to 5 Teal
___ 12. Click Finished.
The Start Center displays the RSDEMO result set by priority order and color.
In this exercise you will create a KPI using the KPI Manager application.
___ 1. Open the KPI Manager application (Go To > Administration > Reporting >
KPI Manager).
___ 2. Click the NewKPI icon and enter the following data.
Field Value
KPI Name MYKPI

Description Current # of logged-in users
Select select currentcount from logintracking
Target 500
•
•
•
•
Field Value
Caution At 550
Alert At 750
Is Public? [Selected]
___ 3. Save the record.
The KPI should look like the following example.
___ 4. In the Graphic Details table window, click Update.
A graphical representation of the KPI shows the number of currently logged-in

users.
•
•
•
•
Exercise 4: Create a New Start Center Template
Exercise 4: Create a New Start Center

Template
In this exercise, you will create a Start Center template and associate it to a security group.
___ 1. Return to the Start Center.
___ 1. Click the New Template tab.
___ 2. Click Change Content/Layout.
___ 3. In the Description field, type My SC Template.
___ 4. For the Left Column Content, click Select Content.
___ 5. Select Quick Insert from the Available Portlets dialog box and click OK.
___ 6. For the Right Column Content, select this content:
– KPI List
– KPI Graph
– Bulletin Board
___ 7. Click OK.
___ 8. Click Finished. The Start Center should look like the following example.
___ 9. Click the Edit Portlet icon to edit the Quick Insert portlet and select these
actions. You may need to type New Message in the description field and click OK
and do the same for New Person.
– New Message
– New Person
___ 10. Click OK.
•
•
•
•
___ 11. Click Finished. The Start Center should look like the following example.
___ 12. Edit the KPI List portlet. In the Display Name field, type My KPI.
___ 13. Click Select KPIs.
___ 14. From the KPI list, select MYKPI (current # of logged-in users).
___ 15. Click OK and then click Finished. The Start Center should look like the
following example.
___ 16. Edit the KPI Graph portlet. In the Display Name field, type Work Order KPIs.
___ 17. Click Select KPIs.
___ 18. Select the following KPIs:
– KPI-4 (Open work orders waiting for approval)

– KPI-10 (Work orders overdue)
___ 19. Click OK and then click Finished.
•
•
•
•
The Start Center should look like the following example.
___ 20. In the tool bar of the New Template tab, click Save Template.
___ 21. Open the Security Groups application and retrieve the EVERYONE group.
___ 22. Using the Select Value icon, select My SC Template for your Start Center
Template.
___ 23. Save the record. The screen should look like the following example.
___ 24. Sign in to the system as user name stanley, password stanley.
•
•
•
•
Exercise 5: Run a BIRT Report from Work Order Tracking
___ 25. Click the My SC Template tab. The Start Center should look like the following
example.
Exercise 5: Run a BIRT Report from Work

Order Tracking
In this exercise you will access a record and run a report from the Work Order Tracking
application.
___ 1. Go to the Report Administration application (Administration > Reporting >

Report Administration).
___ 2. Select the Work Order Details report. To do so, enter woprint.rptdesign in the
Report File Name text box and enter Work Order Details in the Description
field. Then click Enter.
•
•
•
•
The List tab will look like the following example.
___ 3. Click the link for woprint.rptdesign and change the following information.
Field Value
Max Record Limit 20

Browser View Location ALL
Direct Print Location NONE
Direct Print Attachments
NONE
Location
The Report tab detail screen will look similar to the following example.
•
•
•
•
___ 4. Click Generate Request Page.
When the page is completed, you will see the following system message.
___ 5. Click Close to close the window.
___ 7. Go to the Work Order Tracking application in the Work Orders module.
___ 8. Click into the Work Order text box and then press the Enter key (or click the
Filter Table icon [binoculars].
The system shows a list of work orders that are in the user’s default insert site.
•
•
•
•
Note: The default insert site is set by the administrator when a user record is
created. With permissions, the user can change this site using the Default
Information profile. The Site filter field can be cleared to see the sites that the user
has permission to access.
___ 9. Click the link for work order 1008 in the Work Order column. The selected
record opens on the Work Order tab.
Note: Most of the navigational links found on the Start Center (top of the screen)
are also available in applications.
___ 10. Click Select Action > Run Reports.
•
•
•
•
The dialog box opens a list of reports on the On Demand Reports tab.
___ 11. Click the Work Order Details link. The following screen is displayed.
•
•
•
•
Exercise 6: Generate All System Reports
___ 12. Click Submit. The Work Order Details report opens in a separate browser
window.
___ 13. Close the Reporting browser window.
Exercise 6: Generate All System Reports

In this exercise you will make all installed reports available for use in the system.
___ 1. Open the Report Administration application (Administration > Reporting >
Report Administration).
___ 2. Click Generate Request Pages.
The system indicates that the request is being processed. The processing will take
a few minutes.
___ 3. Click Close in the ensuing System Message box.
•
•
•
•
Exercise 7: Set Application Security
___ 4. All reports available in the system are now ready for use. Click into the Report
File Name text box to view all available reports.
The available reports are displayed on the List tab.
Exercise 7: Set Application Security

Use the following steps to set report application security for the Job Plan application to the
Planning security group.
___ 1. Open and sign into the product as maxadmin/maxadmin.
___ 2. Go to: Administration > Reporting > Report Administration.
___ 3. Find and select the Job Plan List report (jobplan.rptdesign).
___ 4. On the Report tab, click Set Application Security from the Select Action menu.
___ 5. In the Report Application Security window, filter for the JOBPLAN application.
___ 7. Click Select Value for the Group field.
___ 8. In the Select Value window, click Planning, and then click OK.
•
•
•
•
Exercise 8: Install Eclipse and BIRT
___ 9. In the Details section of the Report Application Security window, Click BIRT
Reports, and then click OK.
___ 10. Click Save Report.
___ 11. Click the Security tab, and verify that the Planning security group has been
granted access to reports for the Job Plan application.
___ 12. Click Sign Out, and close the browser.

Follow these steps to install Eclipse and the Business Intelligence Reporting Tools (BIRT).
___ 1. Using Windows Explorer, navigate to c:\Eclipse_dwnlds folder and ensure that
you have the following files:
– birt-report-framework-sdk-2.1.2.zip
– eclipse-SDK-3.2.2-win32.zip
– emf-sdo-SDK-2.2.2.zip
– GEF-SDK-3.2.2.zip
•
•
•
•
___ 2. Create a new folder named c:\eclipse.
New folder
Note: Extract the compressed files into c:\eclipse in the order that it is stated below.
___ a. Extract the eclipse-SDK-3.2.2-win32.zip file into c:\eclipse.
Note: Use the right-click context menu and extract the compressed file to c:\eclipse. Files
will extract to c:\eclipse\eclipse. Your active directory will also be c:\eclipse\eclipse,
which is used throughout this course.
___ b. Extract the GEF-SDK-3.2.2.zip file into c:\eclipse.
___ c. If you receive the following warning, click Yes to All.
•
•
•
•
___ d. Extract the emf-sdo-SDK-2.2.2.zip file into c:\eclipse. (Click Yes to All if
the message appears.)
___ e. Extract the birt-report-framework-sdk-2.1.2.zip file into c:\eclipse.
Tip: Except for the Eclipse SDK 3.2.2 compressed file, which must be extracted first, the
order in which the three remaining files are extracted does not matter.
If you do not have JDK 1.5 (5.0) installed, install an IBM-authorized version
(ibm-java2-sdk-50-win-i386.exe). This version is available to IBM employees
from JIM at http://w3.hursley.ibm.com/java/jim/jim/index.html.
Note: If you are using the IBM Tivoli Education developed image, the JDK is already
installed.
___ 3. Copy the com.lowagie.itext_1.5.2.jar file:
from:c:\ibm\smp\applications\maximo\maximouiweb\webmodule\
WEB-INF\birt\platform\plugins
to: c:\eclipse\eclipse\plugins
•
•
•
•
Exercise 9: Configure the Environment for BIRT
Exercise 9: Configure the Environment for

BIRT
Follow these steps to configure BIRT for integration with the IBM Tivoli TPAP product.
___ 1. Create a new classes folder in the following location:
c:\eclipse\\eclipse\plugins\org.eclipse.birt.report.viewer_2.1.2.v20070205-
1728\birt\WEB-INF\
___ 2. Copy the entire \com folder:
from: c:\IBM\SMP\reports\birt\scriptlibrary\classes\com
to: The new classes folder you created in the previous step
___ 3. Copy the mxdatasources.properties file:
from: c:\IBM\SMP\reports\birt\scriptlibrary\classes\
•
•
•
•
to: c:\eclipse\eclipse\plugins\org.eclipse.birt.report.viewer_2.1.2.v20070205-
1728\birt\WEB-INF\classes\
___ 4. Open the newly copied mxdatasources.properties file and edit it for your local
configuration.
Add these four lines to the bottom of the file
Notes: If you are using the IBM Tivoli Education developed image, use the values from
one of the following lists. Otherwise, you can find these values in the maximo.properties
file in c:\IBM\SMP\applications\maximo\properties.
• If you are using the IBM Tivoli Education image for MAM 7.1:
...//localhost:50000/UDB01
...username = maximo
...password = object00
• If you are using the IBM Tivoli Education image for CCMDB 7.1, connect to the
MAXDB71 database.
...//localhost:50005/MAXDB71
• If you are using the IBM Tivoli Education image for SRM 7.1, connect to the
MAXDB71 database.
..//localhost:50005/MAXDB71
• If you are using the IBM Tivoli Education image for TAMIT 7.1, connect to the
MAXDB71 database.
..//localhost:50005/MAXDB71
•
•
•
•
___ 5. Copy the JDBC drivers:
from: c:\IBM\SMP\applications\maximo\lib\
to: c:\eclipse\eclipse\plugins\org.eclipse.birt.report.viewer.2.1.1.v20070205-
1728\birt\WEB-INF\lib\
Note: If you are using the IBM Tivoli Education developed image, you will need the DB2
drivers: db2jcc.jar and db2jcc_license_cu.jar.
___ 6. Create a shortcut to c:\eclipse\eclipse\eclipse.exe on the desktop. You must

include the path and the parameters for the JDK 1.5 installation.
\\{path}\eclipse.exe -vm “{JDK path}” -vmargs -Xmx512m
For example:
C:\eclipse\eclipse\eclipse.exe -vm "C:\program files\IBM\Java50\bin\

javaw.exe" -vmargs -Xmx512m
Type: -vm "C:\program files\IBM\Java50\bin\javaw.exe" -vmargs -Xmx512m
after c:\eclipse\eclipse\eclipse.exe
Do not copy and paste from this document; type the parameters.
•
•
•
•
Exercise 10: Configure BIRT

___ 1. Create a new folder: c:\eclipse\workspace.
___ 2. Open Eclipse using your newly created desktop shortcut.
___ 3. In the Workspace Launcher window, browse for c:\eclipse\workspace.
___ 4. Click the Use this as the default and do not ask again check box.
___ 5. Click OK.
___ 6. After Eclipse opens, click File > New > Project.
___ 7. Expand the Business Intelligence and Reporting Tools section and click Report
Project. Click Next.
___ 8. Type a project name and click Finish.
___ 9. If prompted, click Yes and open the Report Design perspective.
___ 10. Click Window > Preferences.
___ 11. In the Preferences window, expand Report Design and click Resource.
___ 12. Click Select.

•
•
•
•
___ 13. Browse to the local report library location at c:\maximo\reports\birt\libraries

and click Apply.
___ 14. With Report Design expanded, click Template.
___ 15. Browse to the local report template location at

c:\IBM\SMP\reports\birt\templates and click Apply.
___ 16. With Report Design expanded, click Comment Template.
___ 17. Clear the Generate Comment check box and click Apply.
___ 18. Click OK.
___ 19. Click File > New > Project.
___ 20. Under Business Intelligence and Reporting Tools, click Report Project, and then
click Next.
___ 21. Enter a new project name and clear the Use Default Location field.
•
•
•
•
___ 22. Browse to the location of your V7 Report Source,

for example c:\IBM\SMP\reports\birt\reports, and click OK.
___ 23. then click Finish.
•
•
•
•
Exercise 1: Create a New Appender

In this scenario, you are having problems with Reporting log files. Support has asked you
to give them a log file for analysis. By default, the Reporting logger directs output to the
console. You can modify Reporting to use one of the two existing appenders: Daily or Daily
Rolling. However, both of these files contain output from all of the loggers that direct
output using either of these two appenders. Reporting data will be mixed in and will need
to be separated, a tedious task.
Follow these steps to create a separate appender that directs output to a log file specifically
for Reporting.
___ 1. From the Go to menu, select System Configuration >> Platform Configuration
>> Logging and open the Logging application.
___ 2. From the Select Action drop-down list, select Manage Appenders.
___ 3. In the Manage Appenders dialog box, click New Row.
___ 4. Enter the following data:
• Appender: Reporting
• Description: Log file appender for Reporting
• Appender Implementation Class:

psdi.util.logging.MXDailyFileAppender
Note: Use the Select Value button.
• File Name: reporting.log
___ 5. Click OK.
•
•
• 9-1
•
•
Exercise 2: Modify a Logger to Use an Appender
Exercise 2: Modify a Logger to Use an

Appender
By default, most loggers use the Console appender, directing the specified level of output
to the console. You must now link the newly created appender from the previous exercise
to the Reporting logger.
Follow these steps to modify the appropriate logger to use this appender.
___ 1. From the Logging application, In the Root Loggers table window, find and select
the report root logger.
___ 2. In the Loggers table window, find and view details for the birt logger.
___ 3. Clear the Active? field.
___ 4. Select Apply Settings from the Select Action menu.
___ 5. Click the Manage Appenders button for the Appenders field.
___ 6. In the Manage Appenders dialog box, click to select the Reporting appender.
___ 7. Change the Log Level field to DEBUG (you select DEBUG instead of ERROR,
so that informational log statements are written into the log file).
___ 8. Click to select the Active? field. (Ensure that the reporting root logger is
reactivated.)
___ 9. Select Apply Settings from the Select Action menu.
Exercise 3: Specify a new Folder for the

Reporting Appender
It is helpful to specify a folder location for your log files, rather than navigating to the
default and tedious log file location such as:
\\[root]\ibm\WebSphere\AppServer\profiles\[AppServer]\maximo\logs\.
Follow these steps to specify a log file location:
___ 1. In the logging application, from the Select Action menu, select Set Logging Root
Folder.
___ 2. Specify c:\Reporting_Logs as your new location to store log files.
___ 3. Click OK.
•
•
•
•
Exercise 4: Generate Request Page
Exercise 4: Generate Request Page

Before you run reports, you must generate a request page.
Follow these steps to generate a request page:
___ 1. From the Go to menu, select Administration >> Reporting >> Report
Administration and open the Report Administration application.
___ 2. In the List tab, place your cursor in the Report File Name field and press Enter.
___ 3. Select asset.rptdesign (Asset List).
___ 4. Click the Generate Request Page button.
___ 5. Once the request page has been generated, click Close in the System Message
box.
•
•
•
•
Exercise 5: Run Reports
Exercise 5: Run Reports

___ 1. From the Go to menu, select Assets >> Assets and open the Assets application.
___ 2. In the List tab, place your cursor in the Assets field and press Enter.
___ 3. Select the first asset in the list, 7500 (Standard Laptop Computer).
___ 4. From the Select Action Menu, click Run Reports (you may have to scroll down).
___ 5. Select Asset List from the Reports menu.
___ 6. Accept the default setting of Immediate, and click Submit.
A second page appears displaying the Asset List report.
Exercise 6: Verify the New Appender Log File

Follow these steps to verify that the following file exists:
___ 1. Open Windows Explorer.
___ 2. Navigate to:
c:\Reporting_logs\maximo\logs\
___ 3. Verify that the vm100_MXServer_reporting.log file exists.
___ 4. Open the log file and view its contents.
•
•
•
•

MAM71 Implementation - Student Exercises

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MAM71 Implementation - Student Exercises

Uploaded by

Copyright:

Available Formats

IBM Tivoli Maximo Asset Management 7.

Student Exercises for Unit 1

Student Exercises for Unit 2

Student Exercises for Unit 3

Student Exercises for Unit 4

Student Exercises for Unit 5

Student Exercises for Unit 6

Student Exercises for Unit 7

Student Exercises for Unit 8

Student Exercises for Unit 9

No student exercises are provided for this unit.

Exercise 1: Copy the Maximo Root Installation

___ 1. Using Windows Explorer, navigate to c:\IBM folder.

This may take close to 30 minutes.

___ 3. Using window Explorer, navigate to:

___ 4. With your text editor, open the maximo.properties file.

___ 5. Edit the maximo.properties file as follows:

___ a. Search for UDB01

___ b. Replace UDB01 with UDB02.

___ 6. Save and close the maximo.properties file.

Exercise 2: Creating a Second Database

CREATE DATABASE UDB02 ON C: ALIAS UDB02 WITH "UDB02 Database";

___ 10. Click Start to restart the UDB02 database.

___ 11. Right-click the UDB02 database and select Authorities.

___ 13. Select MAXIMO and click OK.

___ 15. Click OK to close the dialog box.

___ 16. Close the DB2COPY1 Control Center.

Binding the DB2 Schema

db2 bind db2schema.bnd

___ 3. Close all open command windows.

Exercise 3: Run Maxinst Against DB2

1. Open a command prompt.

2. Change directory path to C:\IBM\SMP2\tools\maximo.

Maxinst –tUDB02 –sUDB02

This process will take approximately 30 minutes.

By default, Maximo reads the maximo.properties file (in this example,

Exercise 4: Create a Second Application

___ 1. Invoke a browser window.

___ 2. Open the WebSphere Administrative console by typing

___ 4. Expand the Servers link and click Application servers.

Notice the MAM71 Application server is running.

___ 5. From Windows command prompt, change directory to:

___ 8. Click New.

___ 10. Accept the defaults in Step 2 and click Next.

___ 11. Accept the defaults in Step 3 and click Next.

___ 12. Click Finish to confirm the new server.

___ 15. Click OK when the save is complete.

___ 17. Click MAM71Target in the middle pane.

___ 19. Click New.

___ 20. In Step 1 of the Select transport chain template, type

___ 22. In Step 3, click Finish.

___ 23. Click Save.

___ 26. Click MAM71Target.

___ 28. Click Process Definition.

Parameter name Enter this value...

Initial heap size 512

Maximum heap size 1024

Generic Java (or JVM) -Dsun.rmi.dgc.ackTimeout=10000

___ 31. Click OK and then click Save.

___ 32. Click OK.

___ 34. Click New.

___ 36. Click Save.

___ 38. From Additional Properties, click Host Aliases.

___ 39. Click New to create the first host alias.