UCMDB Zeus History - Hewlett Packard · Get history changes – See log and database impact Modify specific attribute Total Time to Complete: 30 minutes Task 1 - Create new CI - Types

Field Excellence HP RESTRICTED 1

UCMDB Zeus History

© Copyright 2012 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. The only warranties for HP products and

services are set forth in the express warranty statements accompanying such products and services. Nothing

herein should be construed as constituting an additional warranty. HP shall not be liable for technical or

editorial errors or omissions contained herein.

This is an HP copyrighted work that may not be reproduced without the written permission of HP. You may not

use these materials to deliver training to any person outside of your organization without the written

permission of HP.

[List the third-party trademarks that are used in the course and that are listed at

http://legal.hp.com/legal/files/tradeack.asp. However, it is not necessary to list any trademarks if the

audience consists of HP employees only. Delete this explanatory text.]

HP Restricted — Contact HPSoftware Education for customer training materials.

http://legal.hp.com/legal/files/tradeack.asp


Contents

HISTORY.

HISTORY OVERVIEW

Use History ............................................................................................................. 3

Task 1 - Create new CI - Types................................................................................ 3

Task 2 - Create new CI instances .......................................................................... 12

Task 3 - Get history changes ................................................................................ 18

Task 4 - Modify specific attribute .......................................................................... 19

Align history .......................................................................................................... 20

Task 1 - Run operations for specific class type ......................................................... 20

Task 2 - Look at log files and databse .................................................................... 20

Task 3 - Run JMX to align the history ..................................................................... 21

Task 4 - Rerun operations for specific class type ...................................................... 21


HISTORY.

HISTORY OVERVIEW

Use History In this exercise we get practice with common history uses.

Create new CI - Types – See log and database impact

Create new CI instances and update some properties – See log and database

impact

Get history changes – See log and database impact

Modify specific attribute

Total Time to Complete: 30 minutes

Task 1 - Create new CI - Types In this stage we create some CI-types and see the effect in history log files and in history

database tables

1. Login to UCMDB with admin user


2. Go to CI Type Manager pane in Modeling tab


3. Create new object CIT – Venus

a) Search for already defined class type ‘Solar System’

b) Create new CIT under ‘Solar System’


c) Type name and description: venus (name in lowercase)

d) Click Finish button

4. Create new object CIT – Mars

a) Repeat step number 3 with name mars (name in lowercase)

5. Create new Relation type – Space

a) Select Relationships in CI Type pane selection box


b) Create new relationship under Membership


c) Type name and description: space (name in lowercase)

d) Click Finish button

6. Define valid link ‘Space’ between Venus and Mars

a) Back to CI Type


b) Select Venus and Mars CITs (use Ctrl key)

c) Select Add/Remove Relationship right-click menu

d) In the opened windows select Space relationship type and check the two

check-boxes. – Press OK

7. Look at history.classmodel.changes.log file

a) You can see ‘alignment for class’ messages for each class you created:


8. Login to JMX console with sysadmin user


9. In order to look at new database tables, run SQL queries through DAL services JMX

10. Select executeQuery JMX operation

11. Run the following SQL queries to see the history table content: (schemaType should stay

empty)

select * from HDM_120610venus_1;

select * from HDM_120610mars_1;

select * from HDM_120610space_1;

Note that tables’ names can be different. Is depending on date.

Run the following SQL to retrieve the current tables’ names:

select ACTIVE_TABLENAME from HDMP_ACTIVE_PARTITION_MAP where

CLASS_NAME in (‘venus‘, ‘mars’, ‘space’);

12. The tables should be empty


Task 2 - Create new CI instances 1. Create new instance of Venus

a) Go to IT Universe Manager (ITU) and click New CI button in the top toolbar


b) Search for Venus CIT

c) Fill properties: Location type property = undefined ; Name = V1

d) Click Save button

2. Create related CI Mars – linked by Space

a) In the Search pane select Location


b) Click OK button

c) Click search button

d) Select V1 from the results list and click on New Related CI button in the top

toolbar


e) Search for Mars CIT

f) Fill properties: Location type property = undefined ; Name = M1

g) Click on Relationship button


h) Select Space relationship type

i) Click Save button

3. Modify Description and Note properties for Venus CI

a) Select V1 venus CI and click on Show CI Properties button on the top toolbar


b) Change the Description and Note properties value and press OK

4. Look at history.update.audit.log

a) Content should be:

5. Look at history tables

a) Run again the SQL queries as described in Task 1 section 11

b) The results should contain Add events for Venus, Mars and Space CIT and also one

Update event for Venus CIT


Task 3 - Get history changes 1. Get history changes for Venus CI

a) Select V1 venus CI and click on CI History on the right click menu

b) History changes


2. Look at history.queries.log

Task 4 - Modify specific attribute 1. Modify ‘Number of moons’ property for V1 Venus CI instance

2. Get history changes – ‘Number of moons’ changes not presents

a) The reason is that ‘Number of moons’ attribute is defined with Not Tracked for

History qualifier


Align history This is a troubleshooting exercise. Get history changes and Data-in not working for specific CIT

Run operations for specific class type – Got an error

Look at log files and database

Run JMX to align the history

Run operations for specific class type – Completed with no error

Total Time to Complete: 20 minutes

Task 1 - Run operations for specific class type 1. Search instances of class ‘HP Desktop’

2. Try to get history – Got an error

3. Try to create new ‘HP Desktop’ instance – Got an error

Task 2 - Look at log files and database 1. Look at log files – see errors

a) In cmdb.dal.log and cmdb.dal.log files see the line: java.sql.SQLSyntaxErrorException: [mercury][SQLServer JDBC

Driver][SQLServer]Invalid column name 'A_COLOR'.

2. Look at HDM table – column A_COLOR is missing

a) Run SQL query through DAL services JMX: select * from HDM_120610hpd_1;

Note that table name can be different. Is depending on date.

Run the following SQL to retrieve the current table name:

select ACTIVE_TABLENAME from HDMP_ACTIVE_PARTITION_MAP

where CLASS_NAME in (‘hpd‘);


Task 3 - Run JMX to align the history 1. Login to JMX console with sysadmin user

2. Select History DB Services

3. Select alignHistoryForType operation

4. Enter hpd in CI Type field and press Invoke

Task 4 - Rerun operations for specific class type After we run the history alignment, let’s try again

1. Try to get history for ‘HP Desktop’ instance – Completed with no error


2. Try to create new ‘HP Desktop’ instance – Completed with no error

UCMDB Zeus History - Hewlett Packard · Get history changes – See log and database impact Modify specific attribute Total Time to Complete: 30 minutes Task 1 - Create new CI - Types

Documents