Transcript IBM Tivoli Composite Application Manager for Response Time 6.2

IBM Software Group
Tivoli Provisioning Manager
Beta Program
Web Replay Intro and Lab
September, 2008
Robert Uthe
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Agenda
 GOAL: Help you get started creating scenarios with Web Replay
 Quick Introduction of Web Replay if needed
 Help you create a scenario
 Best practices, hints and tips
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Do You Face These Problems?
 Are you new to TPM, and want to quickly get started with features
like discovery, patch management, and OS management?
 Do you have specific procedures in mind on how you want your
team to use TPM?
 Do you frequently have new users join your team and need to
train them on TPM, and how you want them to use TPM?
 Do you have users whose time you want to maximize by enabling
them to automate how they use TPM?
 Do you have users whose time you want to maximize by enabling
them to offload some of their more common tasks to others?
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
What is Web Replay?
Web Replay is a major usability feature of TPM that aims
to:
Guide and accelerate use of key TPM features within the product
Allow administrators to define how the larger team should use the TPM
user interface
Ensuring consistency and improving quality and speed
Ideal for training new users
Allows administrators to delegate more work to less-skilled users
Allow administrators to define automated scenarios to speed up their
work
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
How Does Web Replay Work?
 Web Replay allows anyone to “record” their use of the TPM web
UI, and to enable running it later
Individual steps may run in a “guided” mode or an automatic mode
Individual steps may include help that is displayed interactively to
explain to the user what is going on, or guidance on how they
should perform the step
 Anyone familiar with TPM can record a scenario, and do it in no
more time that it takes to just use TPM to do it the first time
 These scenarios can be shared amongst users, and exported and
imported across systems
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Hands On




Start TPM web UI
Start Web Replay
Run the “Running a Scenario” scenario
Piece by piece we will create a couple of scenarios
– I’ll show you how to do each piece first so you can see how its done
– Then, record and run the same thing on your system
 Import and export a scenario
 Wrap-up with some best practices and hints and tips
 You should be able to just access Web Replay from your local
server installation (or we’ll provide a link during the lab):
http://localhost/maximo
And login as maxadmin/maxadmin
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Best Practices - Granularity

How much "ground" should each scenario attempt to cover? Here are the factors
to consider:
A scenario should be something that a single user will run. Parts of the flow that will be
accomplished by a different person should be split into smaller scenarios.
A scenario should be something that a user will run "right now". Parts of the flow that are things
that a user may want to accomplish at some later time should be split into smaller scenarios. For
example, use one scenario to initiate a task to install software this weekend. Then, create a different
scenario they can run on the weekend to check its status and do some post-processing. Any time
gap like this should define a point at which a scenario should be split.
Parts of a scenario that are first time set up that only needs to be done once, or very
infrequently, should be put in its own scenario. For example, most major features like patch or
OS deployment have initial configuration to do around satellite servers, global variables and/or boot
servers. This type of thing should be in a separate scenario.
Similar to the previous item, parts of a flow that are what you expect a user to run frequently are
captured in its own scenario so they can run it was often as they like. For example, keep
compliance checking and remediation distinct from setup. Or, deploying an OS Image should be
separate from capturing an image.
The set of scenarios provided for any given feature or domain area should guide them from a
fresh installed version of TPM, through any needed configuration steps, on through to the routine
usage of the feature. The focus should also be on the path we recommend customers
follow. Esoteric options should be avoided, at least beyond help pop ups that can drop hints about
why they would pick one configuration option over another one.

Several good examples of the right granularity can be found in the scenario list for
5.1.1. In this PDF document you will see the individual scenarios and the order it
makes sense to run them in.
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Best Practices - Starting
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Best Practices – Check for Pre-reqs
Alternative for authorization check…
– Alternatively, you can specify the “Roles” associated with the scenario. In the
TPAE deployment of Web Replay, the Roles map to Security Groups which would
have the access needed (you should develop and test your scenario in that role.)
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Best Practices - Other
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Best Practices - Help
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Best Practices - Help
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Hint and Tips
1. When you save data, blank out fields you do not want to be saved and
played back. Only fields with a value are recorded.
For ‘record id’ fields, mark them to be ignored
2. Data fields that you name are remembered for a user across scenario
invocations with a browser cookie. Use this to help automatically fill in data
for the user based upon what they did last time.
3. When you want to operate on an item displayed in a table:
First do a data item to fill in a search value
Playback clicking on the “binocular” icon. At this point you can record operations on
the item.
If you want to work with its detail record clicking on the “item” tab to show its detail
instead of clicking on the resource in the table
4. Don’t bother trying to size and place the help windows while the step’s
properties is displayed. Just do it when you are running the scenario.
5. When playing a scenario and you want to edit it…
Pause the playback, edit, then resume
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation
IBM Software Group | Tivoli software
Hint and Tips (Continued)
4. The help windows can include any HTML. Here are some helpful
stanzas to include:
The font by default is a little small. Add this to make it a little bigger.
<big>
Insert a hot link in your help, that when clicked displays it in another window.
When displaying other web pages you should always do it this way.
<A href="http://www.ibm.com" target="_blank"><font color="blue"> You
can click here for more detail. </font></a>
Text then image:
Upper text <IMG src=“http://someurl/somepic.JPG”>
Image on left, text at right:
Upper text <table border=’0"><tbody><tr><td><br><IMG
src="http://someurl/somepic.JPG"></td><td> <big><br> right text
</td></tr></tbody></table>
Tivoli Provisioning Manager 7.1
© 2008 IBM Corporation