MDB Install Overview for Federated and Shared MDBs

1
MDB Install OverviewforFederated and Shared MDBs

• Revised June 19, 2006

2
Glossary

• The following terms and abbreviations are used
  in this presentation
• HA Highly Available
• USD Unicenter Service Desk
• eIAM CA eTrust Embedded Identity and Access
  Management
• Federated MDB Multiple MDB spread around
  different servers or multiple sql instances
• Shared MDB MDB shared by multiple products

3
Objectives

• The main objective of this presentation is to
  demonstrate Federated SQL MDB installs of DSM,
  UAPM, NSM and USD products.
• DSM and UAPM will the share same MDB. There is no
  enterprise DSM MDB in this setup
• Separate NSM MDB will be shared by one or
  multiple NSM managers.
• USD MDB will be installed on a separate server.
  As this is ITIL-based , it will be used as
  Enterprise (top tier) MDB for all products.
• In addition, second NSM MDB will be shared with
  the USD MDB. WV manager will also be installed on
  the USD MDB server to enable critical objects
  from NSM MDB to be Bridged to this USD MDB.

4
Federated Shared SQL 2005 MDBs
5
Ingres vs. SQL which and when

• Ingres is geared for small to low-medium
  deployments. It is expected to be used for small
  sites who have issues with SQL licenses.
• If SQL licensing is not an issue, then select
  SQL. It is more scalable and typically requires
  no additional DB skills
• Most SQL sites will already have db housekeeping
  processes in place. This will simplify the
  implementation as no additional housekeeping
  process will need to be defined for the MDB

6
Ingres vs. SQL Platforms

• Unicenter Desktop and Server Management (DSM)
  11.1 supports SQL 2005, SQL 2000 and Ingres
• Unicenter NSM 11.1 will support SQL 2005 and SQL
  2000
• Unicenter NSM 11.0 supports Ingres
• Unicenter Service Desk (USD) 11.2 supports SQL
  2005, SQL 2000, Ingres and Oracle
• Unicenter Asset Portfolio Management (UAPM) 11.1
  supports SQL , Ingres and Oracle

7
Oracle ?

• NSM No plan date
• DSM No plan date

8
DB Users

• Ingres MDB includes DB users for all products
• For SQL, the db users are created by the product
  that is being installed.
• For SQL MDB, if the option to create MDB is
  available it should be run. This should create
  the db users and also apply required MDB patches

9
O/S Users

• Not many products are able to create O/S users
  remotely. Thus if the product requires an O/S
  user to be created (e.g, USD) on the MDB server,
  then the install process to create MDB should be
  run for that product on the MDB Server

10
SQL MDB Creation

• SQL MDB create process includes built-in
  intelligence that performs the following checks
  
• Does the MDB already exist ? If not create mdb
• If MDB exists, is it the correct version? 1.0.4
  If not - upgrade MDB
• Are the patches applied? If not - apply the
  patches
• The product being installed should then
• Create O/S user ID if required
• Create Database user ID if required
• Define roles\grant access for the newly created
  product and Database users

11
eIAM

• eIAM requires Ingres
• For SQL MDB, it will install Ingres Instance ET
  with the MDB.
• For Ingres MDB, it will use MDB Ingres instance
• Embedded Ingres Instance ET is cut-down Ingres
  version which does not install all Ingres tools .
  The Ingres database it creates is expected to
  store eIAM policy and the database size will be
  small
• Not extensive configuration as for MDB

12
MDB on Non-Windows Platform

• Ingres may still be required if the MDB is to be
  created on non-Windows Platform

13
Multi-product MDBs

• If the SQL MDB is shared with other products,
  execute Install SQL MDB process from all products
  that will share the MDB.
• First product installed will create the MDB
• Subsequent MDB installs will simply execute the
  post-install MDB tasks such as create db users,
  create O/S users (if required)

14
Walk-through DSM SQL MDB Install
15
DSM 11.1 MDB Install
16
DSM 11.a SQL 2005 MDB
17
MDB Configuration
18
FQDN Not recognized
19
Summary
20
MDB Creation
21
MDB Patches
22
SQL Roles
23
MDB Creation
24
MDB Size
25
O/S Users

• Creates two O/S users
• ca_itrm
• ca_itrm_ams

26
DB Users

27
Domain Management Component Overview
Database Communications
Inter-Component Communications
28
Walk-through UAPM SQL MDB Install

• DSM and UAPM on Shared MDB

29
Install UAPM MDB

• MDB created by DSM and shared by UAPM
• Select Install UAPM Optional Components option
  to create db users and grant UAPM roles

30
Product Explorer
31
Optional Components
32
Welcome Screen
33
Optional Components
34
Optional Components
35
SQL 2005 Details
36
Create DB Users
37
UAPM MDB
38
UAP Optional Components
39
DB Users
40
Registry Entry
41
Setup.log
42
UAPM Manager Install
Installing UAPM Manager on a different server
connecting to a remote MDB
43
Walk-through NSM 11.1 SQL MDB Install

• Middle tier install

44
NSM

• WV Manager can only be installed on a local MDB.
• WV Provider should also be selected with WV
  Manager as it cannot be selected on the remote
  NSM manager install
• Note that NSM 11.1 does not support Ingres MDB

45
CCS

• If MDB is created from NSM media, it will also
  install common services
• This includes DIA, CCI, Discovery Services, CAM,
  etc.

46
NSM 11.1 Install
47
Management Database
48
Middle-Tier Install

• It is best practice to install local MDB for the
  middle tier NSM manager
• Repository Bridge can be used to replicate key
  objects to top tier level

49
USD and NSM

• NSM is service-aware
• pdm_nsmimp uses WV APIs to extract details of
  discovered objects. Thus, for pdm_nsmimp, WV
  administration client must be installed on the
  Primary Server
• USD Change Impact Analyzer does not provide
  option to define NSM integration on different NSM
  mdb.

50
USD Change Impact Analyzer
51
Walk-through USD 11.1 SQL MDB Install

• Top Tier

52
Remote Components MDB and eIAM
53
Remote Components MDB and eIAM
54
Remote Components Install
55
Database Configuration
56
eIAM
Best Practice to install eIAM with MDB
57
Privileged User
58
Summary
59
Remote Components - Install