Unicenter NSM Repository Bridge 3.1 -> r11. © 2005 Computer Associates International, Inc. (CA)....

Post on 29-Jan-2016

220 views 0 download

Tags:

transcript

Unicenter NSM Repository Bridge

3.1 -> r11

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Agenda

- Product Overview / Positioning

- Terminology

- Installation

- Configuration

- Summary

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Some Background

- Originally ‘Field Developed Code’- First released in 1997 (for TNG 2.1)- Direct response to Customer requirements - Already in production at hundreds of sites- Supported via TNGFDP queue in TCC

- First ‘official’ GA release in 3.0- Anything pre-3.0 is still FDP, NOT GA- Only minor differences between versions

- Update in 3.1 with Linux / Unix support- Minor changes for R11

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

When is Bridge required- Federated MDB

MDB MDB MDB MDB MDB

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Unicenter Repository Bridge- What is it..?!

- World View Application

- NT / W2K and Unix

- Replicates and maintains a policy-defined subset of the objects from one Repository to another

- Uses Rules to decide which objects and events should be replicated

- Facilitates an n-Tier repository Architecture“A tool for replicating and maintaining a policy-

defined subset of the objects in a Source Repository to a Destination Repository...”

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

What is Bridging..?

Brid

ge

Insta

nce

DestinationMDB

Replicate Objects which conform to Bridging PolicyReplicate updates to Properties on Bridged Objects

Delete Objects which no longer conform to Bridging Policy

SourceMDB

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Terminology

- Source Repository- Originating Repository

- Destination Repository- Target Repository

- Bridge Instance- Manages the relationship between a Source and Destination

- Bridge Configuration- Source\Destination configuration details- Determines the data that will be bridged between the Source and

Destination repository by an Instance

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

What does it consist of?

- Bridge Instances

- Implements a Bridge Configuration

- One Instance per Source/Destination pair

- Windows Service / Unix

- Controls Bridge Instance start-up and shutdown (during reboot)

- Can control multiple Bridge Instances

- Administrative GUIs

- Configure and control the Bridge Instances

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Unicenter r11 NSM Install

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Accessing the Installation

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Bridge Configuration

- Includes:

- Source and Destination repository Details

- Bridging Policy (Rules)

- Logging and Event Configuration

- Start-up and initialisation Options

- Saved as flat ASCII Text File

- Passwords are Encrypted

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

NSM 3.1 CORE Definition

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

NSM 3.1 CORE Definition

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

NSM 3.1 CORE Definition

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

NSM 3.1 CORE Definition

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Bridge Rule

Bridge 3.1 CORE to r11 Ingres MDB

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Bridge Rule

Bridge 3.1 Windows 2003 Servers from which are critical (propagated severity)

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Displaying 3.1 CORE from r11

This shows 2dmap display NSM 3.1 CORE from r11 setup.

Caution: This may not be supported

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

R11 MDB display

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Summary

- TNG Bridge is a powerful tool but is open to misuse- Think carefully about the information required in the

Destination repository- Configure instances with efficiency in mind- Read the documentation but if in doubt, ask….

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

Questions