Beruflich Dokumente
Kultur Dokumente
00
Installation and
Configuration Guide
December 2009
www.bmc.com
Telephone
Fax
Fax
If you have comments or suggestions about this documentation, contact Information Development by email at
doc_feedback@bmc.com.
Copyright 2005-2009 BMC Software, Inc.
BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with
the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC
trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other
trademarks or registered trademarks are the property of their respective owners.
IBM is a registered trademark of International Business Machines Corporation.
UNIX is a registered trademark of The Open Group.
Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle
Corporation.
SAP is a trademark or registered trademark of SAP AG in Germany and in several other countries.
Sun Solaris, Java, Java runtime environment, and JRE are trademarks or registered trademarks of Sun Microsystems, Inc.
in the U.S. or other countries.
BMC Software considers information included in this documentation to be proprietary and confidential. Your use of this
information is subject to the terms and conditions of the applicable End User License Agreement for the product and the
proprietary and restricted rights notices included in this documentation.
Customer Support
You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer
Support by telephone or email. To expedite your inquiry, please see Before Contacting BMC Software.
Support Website
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at
http://www.bmc.com/support_home. From this website, you can:
Read overviews about support services and programs that BMC Software offers.
Find the most current information about BMC Software products.
Search a database for problems similar to yours and possible solutions.
Order or download product documentation.
Report a problem or ask a question.
Subscribe to receive email notices when new product versions are released.
Find worldwide BMC Software support center locations and contact information, including email addresses, fax
numbers, and telephone numbers.
Product information
Product name
Product version (release number)
License number and password (trial or permanent)
Machine type
Operating system type, version, and service pack
System hardware configuration
Serial numbers
Related software (database, application, and communication) including type, version, and service pack or
maintenance level
Messages received (and the time and date that you received them)
Contents
Preface
17
18
20
20
21
22
26
Chapter 2
31
32
32
33
34
37
38
38
39
39
41
41
41
43
43
43
44
44
44
45
45
45
5
57
81
Preface
The purpose of BSM Interoperability 8.0.00 is to provide a validated workflow
based on use cases that span multiple BMC products. The products considered in
this document are listed in Products and applications in BSM Interoperability
8.0.00 on page 8. These products are current releases and have been validated at
the solution level.
NOTE
The purpose of this guide is to help customers, BMC Partners, and BMC
Professional Services successfully install the solution offerings by providing a
certified path that has been tested and validated. Only the environment tested and
certified by BMC Software is documented. For information about known issues,
see the BSM Interoperability 8.0.00 Release Notes.
This guide does not encompass specific installation, administration, configuration,
or user information at the product level. See the appropriate product
documentation for that type of information.
For the version of BSM Interoperability documentation that applies to your
environment, see the BMC Customer Support website.
Depending on your product versions, the most recent BSM Interoperability
documentation might include newer versions of products which might not exist in
your environment. Check the products and applications version list in the BSM
Interoperability Installation and Configuration Guide or the BSM Interoperability Release
Notes before using BSM Interoperability documentation.
Preface ! 7
Short name
Version
Patch
Function
Analyzes data and creates ad hoc
reports for AR System and BMC
Remedy IT Service Management
applications.
7.5.01
7.5.00
BMC
7.6.00
Dashboards for
BSM
AR System
7.5.00
001
003
Short name
Version
Patch
Function
7.6.00
7.6.00
!
!
BMC Atrium
Integration Engine
BMC Atrium CMDB
Product Catalog
Preface ! 9
10
Version Patch
Function
7.3.02
BMC Impact
Administration Server
BMC Impact Explorer
(BMC IX)
BMC Impact
Integration for z/OS
BMC Impact
Integration Web
Services
BMC Impact Manager
(BMC IM)
BMC Impact Service
Model Editor
BMC Impact
Publishing Server
Integration for BMC
Remedy Service Desk
7.3.00 patch 001
(IBRSD)
BMC Atrium CMDB
extensions (version
7.3.01)
Short name
Short name
Version Patch
Function
BMC ProactiveNet
8.0.00
BMC Transaction
BMC TM
Management
ART
Application Response
Time, either
Infrastructure Edition or
Service Level Edition
3.7.00
Short name
Version
7.5.05
7.5.05
BMC Atrium
Orchestrator Content
Installer
8.1.00
Patch
Function
Delivers workflow-based process
templates, with which customers
can rapidly adapt and deploy
functional design to ensure
consistent and appropriate, policybased response across the
enterprise.
Enables administrators to manage
software changes, manage content
changes, configure endpoints, and
collect inventory information.
Preface ! 11
Short name
Version
Patch
Function
BMC BladeLogic
Decision Support for
Network Automation
5.3.01
BMC BladeLogic
Decision Support for
Server Automation
2.0.00
8.0.00
BMC BladeLogic
Network Automation
5.3.01
8.0.00
BMC BladeLogic
Integration with
Atrium
12
Short name
Version
Patch
Function
BMC
Remedy
ITSM
7.6.00
see KB
20020198
7.5.00.001
7.6.00
BRIM
7.5.01
Patch
Function
A suite of integrated solutions
for handling the problems
related to identity management
in the enterprise.
Preface ! 13
Related documentation
BMC product documentation is available from the BMC Customer Support
website at http://www.bmc.com/support.
NOTE
This document does not cover the specific procedures and detailed information
that are provided in the product documentation. See the documents listed here and
the product release notes for information related to procedures in this guide, and
see the BMC Customer Support website for complete product documentation.
The following table lists the BSM Interoperability 8.0.00 documentation set.
Table 2-6: BSM Interoperability 8.0.00 documentation.
Manual name
Description
14
Document organization
Document organization
This document is organized as follows:
!
Audience
This document is intended for system integrators in several organizations:
customers, BMC Professional Services, and BMC Partners.
Preface ! 15
16
Chapter
This chapter describes the data flow, prerequisites, installation overview, and the
high-level steps for installing BSM Interoperability 8.0.00 on Windows and UNIX.
The following topics are provided:
!
!
!
!
Chapter 1
17
18
Integration
Consumer from
BMC Atrium
Provider to
BMC Atrium
Legend
Service Support
Service Automation
Service Assurance
BMC Atrium
BMC Atrium
Integration
Engine
Product
Catalog
to Exception
Detector
BMC Capacity
Management
Essentials
BMC
Performance
Assurance
BMC
Performance
Analysis
BDSSA
Master Transmitter
Repeaters/Mirrors
Proxies
Tuners
BMC BladeLogic
Client Automation
Client Automation
database
integrations with
-BMC Remedy AR System
-BMC Atrium
-BMC SIEM
-BMC Remedy Change
Management
-BMC ProactiveNet
Analytics
BMC Atrium
Orchestrator
BMC BladeLogic
Server Automation
Service
Automation
BMC Configuration
Automation
dataset
Approval Server
Assignment Engine
BMC Asset
dataset
Reconciliation
Engine
BMC Atrium
Discovery
dataset
BMC Atrium
To multiple
consumers
Collection
Nodes
Collection
Points
(such as
BMC Service Impact Manager,
BMC Performance Manager)
data sources
Data
Collector
Service Level
Management
Change
Management
Identity
Management
BMC Remedy
Knowledge
Management
BMC Performance
Manager dataset
Impact Production
dataset
Asset Management
Sandbox
dataset
Impact
Sandbox datasets
(1 per user)
work orders
BMC
Analytics
SLM
Discovery
database
BMC Discovery
for z/OS
BMC Atrium
Discovery
BMC Atrium
Discovery
Asset
Management
(or Asset
Inventory
Module)
BMC Remedy
IT Service
Management
Service Support
Service Request
Management
BMC Atrium
CMDB
Drift
Management
from Discovery
database
BMC
BladeLogic
Network
Automation
Problem
Management
Incident
Management
Service Desk
BMC
Dashboards
for BSM
iiws
data sources
RSM
BMC
Performance
Manager
Portal
BMC
Impact Portal
BMC Atrium
Orchestrator
BMC
ProactiveNet
BMC Transaction
iiws
BMC Portal
database
Application
Service Management
Response Time
Assurance
Publishing Server
Impact Explorer
Impact Administration
Server
data sources
Data Service
Exception
Detector
BMC Portal
Prerequisites
BMC Software recommends these system prerequisites and suggested
considerations based on end-to-end testing of the BSM Interoperability 8.0.00
offering.
Windows
During testing, BSM Interoperability 8.0.00 was tested on Windows 2003 Server
Enterprise Edition with Service Pack 2 and SQL Server 2005 Enterprise Edition
with Service Pack 2. The examples in the documentation reference this
configuration, although any supported combination listed in the compatibility
matrix can be used.
NOTE
Many BMC Software products that use SQL Server require that the SQL Server
Agent is running so that the server can connect to remote databases.
BMC Portal requires an Oracle database. You can use an existing Oracle 10g
database or the BMC Datastore (included on the BMC Portal DVD).
UNIX
During testing, BSM Interoperability 8.0.00 was tested on Sun Solaris 10 and
Oracle 11g with the latest patches installed. The examples in the documentation
reference this configuration, although any supported combination listed in the
compatibility matrix can be used.
For UNIX installations, all servers must be server-class computers, preferably with
multiple processors. Because some BSM Interoperability 8.0.00 products do not
have UNIX versions, some servers in the environment must be Windows
computers.
20
Prerequisites
Other requirements
Individual products in the BSM Interoperability 8.0.00 offering have their own
installation prerequisites. Some of these prerequisites are satisfied by steps you
take when installing other products using the procedures in this section. Any other
prerequisites are shown in Figure 1-2 on page 27.
Consult your documentation for details on licensing for specific products.
BMC
Analytics
for BSM
Patch
Function
7.6.00
7.5.01
7.5.05
8.0.00
7.6.00
8.1.00
5.2.01
7.5.00
22
002
Delivers workflow-based
process templates, with which
customers can rapidly adapt and
deploy functional design to
ensure consistent and
appropriate, policy-based
response across the enterprise.
Acts as a platform for the
management, control and
enforcement of configuration
changes in the data center.
Enables administrators to
manage software changes,
manage content changes,
configure endpoints, and collect
inventory information.
000
Function
hotfix
Integrates discovered
configuration data with the
BMC Remedy IT Service
Management suite of products.
This integration enables you to
use BMC Remedy Asset
Management, BMC Remedy
Change Management, BMC
Remedy Incident Management,
and BMC Remedy Problem
Management to access accurate,
real-time information about IT
infrastructure components
across your enterprise.
SW00335267
BMC
7.6.00
Dashboards
for BSM
000
2.8.00
2.7.00.030
(supported
by version
2.7.00 and
2.7.50)
8.0.00
000
BMC ProactiveNet
Patch
BMC
Remedy
ITSM
7.6.00
Patch
Function
!
24
BSARA
7.5.00.001
2.0.00
A web-based reporting
application that provides
extensive report capabilities
related to your data center
servers that are managed by
BMC BladeLogic. BMC Service
Automation Reporting and
Analytics uses rich data
warehouse schema and
dimensional modeling
principles to access and report
on historical data captured by
BMC BladeLogic.
Patch
Function
7.6.00
000
7.6.00
3.7.00
Installation overview
This section contains information about the method and sequence used by BMC
Software to perform a new installation of the solution and test it.
The procedure is not the only possible way to set up a successful environment. For
more information about implementing different use cases based on the amount of
data present in your environment, see the documentation set for your products, as
well as other documentation available on the BMC Customer Support website.
NOTE
For interoperability testing, computers running VMware images were used to
minimize the need for pre-existing web or application servers.
Figure 1-2 on page 27 illustrates the BSM Interoperability 8.0.00 installation order
on Windows and UNIX.
26
Installation overview
SERVER F
Prerequisites
BMC
Remedy ITSM
1 BMC Remedy
SERVER G
Management
14 BMC ProactiveNet
BMC ProactiveNet
including
- Minimum of 6 GB of memory
-64-bit OS
Prerequisites
Management
BMC Atrium
Discovery
BMC Configuration
Drift Management
Prerequisites
- Dual 2.1 GHz processors, or four in
- Administrator privileges
large production environments
- MS SQL Server 2005 database
- Minimum of 4 GB of memory
- Minimum of 6 GB of permanent storage (10 GB
recommended) plus 2 GB of temporary
storage for the installation
13 Integration for
SERVER H
Prerequisites
- SQL Server 2005 database
- Minimum of 1 GB of memory
16 BMC Transaction Management Application Response Time
SERVER B Prerequisites
BMC TM ART
SERVER I
Prerequisites
- Minimum of 1 GB of memory
Web Server
17 BMC Transaction Management Application Response Time
SERVER C
Prerequisites
BMC TM ART
SERVER J
BMC Remedy
Knowledge
Management
SERVER D
Prerequisites
Reporting
SERVER K
BMC Remedy Identity Management Suite;
BMC Identity Management
Prerequisites
- Minimum of 2 GB of memory
- 1 MB of disk space for each cell
or console you intend to use
10 BMC Impact Solutions
11 BMC Portal, including
BMC Performance Manager Portal
BMC Impact Portal
- Administrator privileges
- Java SDK 1.6.0_11
-BMC Datastore on separate
server
Prerequisites
- Minimum of 8 GB of memory
- Java SDK 1.6, 64-bit version
-Processor: 2 @ 2.8GHz ( physical machine ), 1 @ 2.8 GHz ( VM )
-20 GB free disk space
-64 bit OS preferred
BMC Identity
Management
BMC Impact
Solutions
Prerequisites
- Minimum of 2 GB of memory
- BusinessObjects
- 2 GB temp space
SERVER E
Alerting Server
- Administrator privileges
-own SQL server
BMC Atrium
Orchestrator CDP
SERVER L
BMC Atrium
Orchestrator
Development Studio
Prerequisites
- Minimum of 4 GB of memory
- Java SDK 1.6, 64-bit version
-Processor: 2 @ 2.8GHz ( physical machine ), 1 @ 2.8 GHz ( VM )
-20 GB free disk space
-64 bit OS preferred
21 BMC Atrium Orchestrator Development Studio
Prerequisites
- Minimum of 512 MB of memory
- Same database vendor as AR System
22
BladeLogic
SERVER N
23
Prerequisites
- Minimum of 4 GB of memory
- Same database vendor as AR System
24 BMC BladeLogic Decision Support
BladeLogic
SERVER O
Prerequisites
- Minimum of 1 GB of memory
BNA
SERVER P
Prerequisites
- Administrator privileges
- Database client connectivity tools
- Access to the same LDAP directory
server that Server A uses
BladeLogic
Client Automation
SERVER Q
Prerequisites
- Minimum of 2 GB of memory
- Administrator privileges
- Java SDK 1.6
Capacity
Management
SERVER
SERVER RI
28
Prerequisites
- z/OS 1.4 through
1.7 or later
29 BMC Impact Integration for z/OS
Mainframe
impact &
Discovery
28
Installation overview
30
Chapter
Installing BSM
Interoperability components
This chapter presents procedures for installing BSM Interoperability 8.0.00
components on Windows and UNIX environments. Any specific configuration
required for either of these installations is explained in separate sections within the
procedure.
The following topics are provided:
!
!
!
!
!
!
!
!
!
!
!
!
!
Installing BMC Atrium and BMC IT Service Management applications (page 32)
Installing BMC Identity Management (page 38)
Installing BMC Impact Solutions and BMC Portal, integrating with BMC
Remedy Service Desk (page 38)
Installing BMC ProactiveNet (page 41)
Installing BMC Atrium Discovery and Dependency Mapping (page 41)
Installing transaction management applications (page 43)
Installing reporting and monitoring applications (page 44)
Installing BMC Atrium Orchestrator (page 45)
Installing BMC BladeLogic Server Automation and integrating with BMC
Atrium (page 47)
Installing BMC BladeLogic Decision Support for Server Automation (page 47)
Installing BMC BladeLogic configuration automation applications (page 48)
Installing BMC Capacity Management Essentials (page 54)
Installing mainframe applications (page 55)
Chapter 2
31
BMC Atrium Core applications, including BMC Atrium CMDB and BMC
Atrium Integration Engine
UNIX/opt/bmc/ARSystem
Each feature has its own subdirectory within these directories, such as:
! approval
! Arserver
! AREmail
! arsystem (for utilities)
! assignmentengine
! dataimporttool
! DevStudio
! flashboards
! midtier
! usertool
32
Related documentation
See the following documentation, as well as applicable patch technical bulletins
and release notes, for detailed instructions on installing and configuring the
products in this section.
AR System
!
installation directories
installation instructions
license keys
installation instructions
installation directories
installation instructions
installation instructions
integration instructions
installation instructions
installation instructions
NOTE
Depending on the amount of data you store in your BMC Atrium CMDB, your
database size might need to be increased. The minimum size used in
interoperability testing was 8000 MB.
!
34
In the MS SQL Information panel of the installer, increase the Database Initial
Size from 300 MB to at least 8000 MB if you are installing the entire BMC
Remedy IT Service Management suite of applications.
Verify that the user installing the AR System server has access to the
tnsnames.ora file.
Increase the default data tablespace from 300 to at least 8000 megabytes at the
AR System server Database Settings prompt if you are installing the entire
BMC Remedy IT Service Management suite of applications.
IMPORTANT
To avoid BMC Atrium Discovery and Dependency Mapping and BMC Atrium
CMDB export failures, you must select the Unicode option when installing the
AR System server on both UNIX and Windows.
2 In AR System Administration Console, apply the appropriate licenses.
NOTE
For Windows 2008 servers, you cannot use the BMC Remedy User Tool for
licensing as it will return an invalid Host ID. You must use ipconfig /all on the
local machine to determine the physical address of the computer. This physical
address acts as your Host ID for licensing purposes.
3 In AR System Administration Console, increase the maximum number of threads
for the Fast and List queues to improve performance. Fast queues should have five
times as many threads as the number of processors in your server, while List
queues should have three times as many threads as the number of processors.
4 Install BMC Atrium Core 7.6.00, including these features:
!
Product Catalog
NOTE
Install BMC Atrium Web Services on its own computer to avoid resource
contention and port conflicts.
5 If applicable, choose to import your data during the installation.
6 Install BMC Remedy Mid Tier on its own computer.
order:
!
BMC Remedy Service Desk (includes BMC Remedy Incident Management and
BMC Remedy Problem Management)
IMPORTANT
You must start BMC Remedy Assignment Engine before you install any BMC
Remedy IT Service Management application.
Before installing BMC Remedy Asset Management and BMC Remedy Change
Management, you must start BMC Remedy Approval Server and BMC Remedy
Assignment Engine.
8 Optionally, install BSM Enablement data. BSM Interoperability testing used BSM
Enablement data in their testing. Register with the BMC Developer Network to
obtain the data files and instructions for installing the data.
9 Install BMC Service Level Management and the Collector.
NOTE
On UNIX, the installer must be launched in graphical mode from
bmcslm-solaris.bin.
10 Install BMC Service Level Management Collection Point.
11 Install BMC Service Request Management.
IMPORTANT
The server name on the CAI Registry form must be the same name as the server
that is registered on the mid tier, which is the value of $SERVER$ that you get on the
web.
12 Install BMC Service Request Management integrations.
13 Install BMC Configuration Drift Management.
36
NOTE
The installer asks to install Hummingbird and Tomcat along with BMC Remedy
Knowledge Management. Install both if not already present on the computer.
2 Complete the special instructions that begin When integrating with BMC Remedy
NOTE
If your system includes BMC Remedy ITSM 7.5 or later, integration with BMC
Remedy Knowledge Management 7.5 automatically becomes available. This
integration enables users to create, search, and associate knowledge articles from
within the BMC Remedy Incident Management forms, the BMC Remedy Problem
Management forms, and Requester Console.
BMC Performance Exception Detector are installed in this step, during the
installation of BMC Portal.
Step 2 Install the Integration with Remedy Service Desk (page 41).
38
Installing BMC Impact Solutions and BMC Portal, integrating with BMC Remedy Service Desk
Related documentation
See the following documentation, as well as applicable patch technical bulletins
and release notes, for detailed instructions on installing and configuring the
products in this section.
installation instructions
installation instructions for the integration with BMC Remedy Service Desk
BMC Datastore
!
installation instructions
BMC Portal
!
installation instructions for the BMC Performance Manager Portal and BMC
Impact Portal modules
IMPORTANT
This step can fail if performed over a network. Copy the extensions to a local drive
on the BMC Atrium CMDB system and run the extensions installer there.
On UNIX, this step must be performed as the root user.
2 Optionally, install a database for BMC Portal. If you install a database for BMC
BMC Portal requires an Oracle database. You can use an existing Oracle 10g
database or the BMC Datastore (on BMC Portal Infrastructure and Datastore DVD
or BMC Datastore CD Windows Disk 1).
3 Execute the BMC Impact Solutions installer and perform a full installation.
4 Install BMC Portal. During the installation, install the following BMC Portal
modules:
!
If you have installed BMC Performance Manager Express for SAP, you must resynchronize the cell KB with the new classes in the BMC Atrium CMDB. See
Updating the SIM KB component classes in BMC Service Impact Solutions
Installation Guide.
If you are installing BMC TM ART in your environment, return to this step and
update SIM KB component classes after all extensions are loaded.
7 Install Remote Service Monitor on a separate computer or as part of a Remote
40
Desk.
2 Restart the BMC Remedy AR System server and plug-in server.
3 Set Incident Management rules for Require Service CI Related on Submit on
NOTE
Disable Data Execution Prevention (DEP) on the target computer before installing.
NOTE
This procedure includes instructions for only Windows because there are no UNIX
versions of BMC Atrium Discovery and Dependency Mapping.
1 Make sure that:
!
For instructions about creating the SQL Server database instance, see the Creating
the discovery datastore section of BMC Atrium Discovery and Dependency
Mapping: Planning and Installation.
Installing BSM Interoperability components ! 41
3 Install and start the BMC Atrium Discovery and Dependency Mapping server by
42
Related documentation
See the following documentation, as well as applicable patch technical bulletins
and release notes, for detailed instructions on installing and configuring the
products in this section.
Integrations.
a Configure the integration with BMC Impact Manager.
b Configure the integration with BMC Atrium CMDB.
Related documentation
See the following documentation, as well as applicable patch technical bulletins
and release notes, for detailed instructions on installing and configuring the
products in this section.
The default directory path for this file is <BMC Impact Solutions directory>\iiws.
3 Add the name of the default cell you specified during BMC Impact Manager
44
Related documentation
See the following documentation, as well as applicable patch technical bulletins
and release notes, for detailed instructions on installing and configuring the
products in this section.
Orchestrator CDP. For more information, see the BMC Atrium Orchestrator Platform
Installation Guide.
NOTE
Each workflow must be installed by a unique user and all templates, filters, and
other configuration settings associated with each user must be unique to that user
(and re-set to each new user before every workflow installation, if installing
multiple workflows from the same computer). In summary, you must have:
--a unique user to own the actor and monitor adapters
--the same unique user acts as the Assignee on the template
--the same unique user is assigned to the filters
46
Installing BMC BladeLogic Server Automation and integrating with BMC Atrium
NOTE
The authentication server and reports server can be installed on two different
computers, but interoperability tested the configuration given in this section.
Related documentation
See the following documentation, as well as applicable patch technical bulletins
and release notes, for detailed instructions on installing and configuring the
products in this section.
installation instructions
instructions for integrating with BMC Remedy AR System and BMC Atrium
CMDB
48
Integrations
!
implementation
data mappings
data exchanges
configuring the ARDBC LDAP plug-in
user roles
TIP
You must create a local user account for the BMC BladeLogic Network
Automation services and FTP/SCP configuration file transfers.
2 Perform integrations with BMC Remedy AR System and BMC Atrium CMDB.
CMS
Transmitter
Infrastructure Service
Report Center
Scanner Service
Schema Manager
On WindowsMS SQL Server 2005 SP2 is used as the BMC BladeLogic Client
Automation database.
NOTE
In Tuner, make sure that Schema Manager and Report Center are running. If the
Schema Manager and Report Center are running, you can select them.
3 To normalize your BMC BladeLogic Client Automation data with the Product
Catalog, continue with this step to configure access. See the BMC Atrium Core
Product Catalog and DML Guide for details. Otherwise, skip to step 4 on page 51.
a For Product Catalog integration, set up the database links from both the BMC
NOTE
Use the MSSql_installSecurityScript_Unicode.sql script if the SQL Server
AR System database was installed with the Unicode option ON and the columns
are of Unicode data type nvarchar and the ODBC driver does not automatically
translate data. The MSSql_installSecurityScript_Unicode.sql script rewrites the
views by casting the Unicode nvarchar types to the varchar datatype, allowing
successful population of the CM database columns.
c Configure parameters for the BMC CM database.
IMPORTANT
Any time you change AR System settings in CMS, restart CMS or the tuner.
d Establish a connection between the CM and AR System databases.
50
T IP
To verify connectivity to the Product Catalog using Report Center Query Library,
run one of the predefined queries. For details, see the Service Management
integration section of Appendix I, Query Library list, in BMC BladeLogic Client
Automation Report Center Guide.
4 Install BMC BladeLogic Client Automation views using the following steps:
a From the Schema Manager, connect to the BMC CM database.
b Install the CMDB Integration with Configuration Discovery schema.
5 In the Report Center, enable and configure the Inventory plug-in.
For instructions about enabling and configuring the Inventory plug-in, see the
Updating Report Center and the Inventory and Logging plug-ins section of the
BMC BladeLogic Client Automation Report Center Guide.
NOTE
The BMC BladeLogic Client Automation Configuration Discovery Integration
package includes BMC Atrium Integration Engine and Remedy Link applications.
You already installed these applications in step 13 on page 36.
1 Stop the BMC Atrium Integration Engine service.
2 Install BMC BladeLogic Client Automation Configuration Discovery Integration.
3 After installation, restart the BMC Remedy Action Request System service and the
Reconciliation Process job to reconcile your Configuration Discovery data with the
BMC_Asset dataset.
Installing BSM Interoperability components ! 51
NOTE
You should also create a schedule for the Configuration Discovery Reconciliation
Process job so that it can reconcile your Configuration Discovery data after each
transfer. By default, the job has no scheduled runs.
NOTE
Make sure that your environment has a directory service enabled.
2 Configure BMC BladeLogic Client Automation to use the directory service for user
Settings.
b Choose the User Authentication tab.
c On the User Authentication Settings page, choose the User Authentication Type
link.
d Set the User Authenticate Type to Directory Service.
3 From Schema Manager, connect to the directory service and install the Policy
Manager schema.
This action generates a script that you need on the directory service server.
4 Configure Deployment Manager to use the BMC BladeLogic Client Automation
database.
The Deployment Manager is located, for example, at
http://<deployment_manager_host>:<deployment_manager_port> with
a default port
number of 8000.
5 Configure Deployment Manager to use the directory service for user
authentication.
6 Configure console settings to enable Report Center integration.
7 Create a user in the directory service in cn=Users that is accessible by BMC
52
8 Configure the master transmitter to use the Product Catalog by editing the settings
3 Use BMC Remedy Administrator to import the changed .xml definitions to the
AR System server.
4 In the AR System server, configure the ARDBC LDAP plug-in to use the directory
For the purposes of integration, you must create the following types of users in the
CTM:People form to use the Change Management application.
!
CMS AR System UserThis is a single special user created for the integration.
Change Management UsersThese are regular users created for the Change
Management application.
For both users, you must use the same login and password combination in the
Configuration Management and Change Management applications. Therefore,
you must create users in CTM:People that match the user name and password
combinations that have access to CMS in LDAP.
7 Provide the CMS Host and DM Host names and set the status to Active.
This step creates links between the BMC BladeLogic Client Automation system,
Change Management, and Task Management System.
8 For the integration to be complete, you must:
!
Edit the Directory Service or Remedy Integration to include the CMS AR System
User with exactly the same login and password.
For instructions about editing directory services, see the Adding or editing a
directory service section of the BMC Configuration Automation for Clients CMS
and Tuner Guide.
Make sure that the user has appropriate roles to perform configuration
management tasks. Verify that correct roles are available in BMC BladeLogic
Client Automation.
For information about user roles, see the What are user roles? section of the
BMC Configuration Automation for Clients CMS and Tuner Guide.
Configure mid tier, AR System database, and Java runtime settings. For
instructions about these procedures, see the following guides:
!
Mid tierSee the Configuring the mid tier chapter of BMC Remedy AR
System BMC Remedy Mid Tier Guide.
54
BMC Discovery for z/OS Agent Installation and User GuideReview for
procedures about installing the BMC Discovery for z/OS Agent that enables
mainframe inventory discovery.
BMC Impact Integration for z/OS User GuideSee the Preparing to install and
customize BMC II for z/OS chapter for installation prerequisites and the
Installing BMC II for z/OS cell and console components chapter for
installation procedures.
56
Chapter
BSM Interoperability
workflows
This chapter presents technical workflows and troubleshooting for use cases in
BSM Interoperability.
The following topic is provided:
!
Chapter 3
57
NOTE
These use cases do not represent all potential use cases or functions of these
products.
The following use cases are described:
58
Holistic compliance
Intelligent incident
Problem management
Virtualization
Web self-service
Continuous complianceservers
Continuous compliancenetworks
Decision Support
Products involved
This section lists the primary products involved in this use case.
!
BMC Atrium
!
Service Assurance
!
Service Automation
!
Prerequisites
!
Data sources have been integrated with BMC Atrium CMDB and data model
extensions, if appropriate, have been installed.
Technical flow
" Technical use case
1 Data sources, such as those listed below, collect data and populate that data into
uses the BMC Atrium CMDB API to populate the import dataset in the CMDB
sends the information to BMC Atrium CMDB via BMC Atrium Integration
Engine
collects information about your environment through the use of tuners and
distribution servers
sends the information to BMC Atrium CMDB via BMC Atrium Integration
Engine
uses the BMC Atrium CMDB API to populate the import dataset in the CMDB
uses the BMC Atrium CMDB API to populate the import dataset in the CMDB
uses the BMC Atrium CMDB API to populate the import dataset in the CMDB
2 Synchronization tasks import the new data (such as CIs and relationships), as well
data can be normalized against the Product Catalog using the BMC Atrium CMDB
Normalization Engine.
4 Reconciliation jobs are run using the BMC Atrium CMDB Reconciliation Engine to
merge CIs and relationships with other data in the (development or production)
dataset.
5 Data collection and discovery tasks, synchronization tasks, purge jobs, and
Related documentation
For more information about normalization and reconciliation, see the
documentation for your products and the BMC Atrium CMDB 7.5.00 Patch 001
Normalization and Reconciliation Guide.
60
Troubleshooting
For issues with importing data to the CMDB, see the appropriate source:
Table 3-1: Troubleshooting reconciliation of multiple data sources
Process
Product
populating data
into the CMDB
data normalization
BMC BladeLogic
Server
Automation
BMC BladeLogic
Client
Automation
Documentation
BMC Atrium Core 7.6.00 Troubleshooting Guide for steps to
enable BMC Atrium Integration Engine logs
BMC Performance
Manager Portal
BMC Atrium
Discovery and
Dependency
Mapping
BMC Atrium
CMDB
reconciliation
BMC Atrium
CMDB
Data flow
Figure 3-1 illustrates the flow of data depicted in this use case.
Figure 3-1: Reconciliation of multiple data sources data flow
1
BMC Atrium
Discovery
BMC
BladeLogic
BCAC
BMC Identity
Management
BMC Performance
Manager Portal
import datasets
Product
Catalog
Normalization
Engine
Reconciliation
Engine
production dataset
62
BMC TMART
Products involved
This section lists the primary products involved in this use case.
!
BMC Atrium
!
Service Assurance
!
Prerequisites
1 A discovery tool has scanned existing assets and migrated the data into BMC
service model.
3 Service targets have been configured in BMC Service Level Management to assign
Technical flow
" Technical use case
1 An event causes a business impact.
2 A business service is impacted as reported by BMC Performance Manager Portal.
3 BMC Service Level Management polls BMC Service Impact Manager through IIWS
on the status of business service CIs and discovers that the CI is impacted.
4 Based on the SLA previously set up in BMC Service Level Management, the
as breached.
7 BMC Dashboards for Business Service Management reports the breached SLAs.
8 When the CI is no longer impacted, BMC Service Level Management, which polls
the CI status periodically, re-computes the SLA status and finds that the SLA is
now compliant.
9 BMC Performance Manager Portal reports the improved status of the SLA.
10 BMC Dashboards for BSM also reports the improved status of the SLA.
64
Data flow
Figure 3-2 illustrates the flow of data depicted in this use case.
Figure 3-2: End-to-end service level management data flow
1
2
BMC Service
Impact Management
BMC Performance
Manager Portal
an event causes a
business impact
IT department
view
SLA
breach
BMC Performance
Manager Portal
6
SLA
breach
BMC Dashboards
for BSM
7
executive
view
SLA
breach
BMC Performance
Manager Portal
9
SLA
OK
BMC Dashboards
for BSM
10
SLA
OK
Products involved
This section lists the primary products involved in this use case.
!
Atrium
!
Service Automation
!
Service Support
!
Prerequisites
!
The baseline system is used to generate templates for audit jobs and to send
SNMP events if the audit fails.
!
!
66
BMC Remedy ITSM user with permissions to create, update, and close change
and incident tickets and read assets in BMC Asset Management.
Technical flow
" Technical use case
1 After an audit is run on the system, an out-of-compliance condition is created (for
created by the workflow is related to the change request. A change task is also
created with work notes that list relevant information regarding the audit, such as
target server information, and a description of what is out of compliance.
4 A CI from BMC Asset Management is related to the change request.
5 The change request is approved either manually or automatically, based on impact
and priority.
6 BMC BladeLogic Server Automation creates a remediation package job and
remediation job.
7 BMC BladeLogic Server Automation reconfigures the system to reach compliance.
8 After the change ticket and its tasks have been closed, the audit workflow in BMC
Atrium Orchestrator closes the incident. The change is completed and task and
incident are closed.
Data flow
Figure 3-3 illustrates the flow of data depicted in this use case.
Figure 3-3: Holistic compliance data flow
1
SNMP trap
incident is created
4
BMC Remedy
Asset Management
CI is related to the
change request
5
change request approved
7
BMC BladeLogic
or
BMC Configuration
Automation for
Clients
system reconfigured
to reach compliance
68
8
change is completed and
incident and task are closed
Products involved
This section lists the primary products involved in this use case.
!
Atrium
!
Service Assurance
!
BMC ProactiveNet
Service Support
!
Prerequisites
!
Asset inventory scan has been run and the data synchronized with the CMDB.
Transaction and service model CIs, and impact relationships between the
business service and activities, are set up in the service model.
A service policy has been set up in Integration for BMC Remedy Service Desk.
Data prerequisites
!
Technical flow
" Technical use case
1 An out-of-compliance event is detected and an exception is generated.
2 Depending on your configuration, one of the following occurs:
!
BMC Performance Manager Portal sends the event to BMC Event Manager.
3 BMC ProactiveNet generates intelligent events from the data and forwards to BMC
Event Manager.
4 The event is propagated from BMC Event Manager to BMC Service Impact
Manager.
5 The impact of the event on CIs and business services is computed by BMC Service
the CI.
7 The incidents are assigned and worked by users in BMC Remedy Service Desk.
70
Data flow
Figure 3-4 illustrates the flow of data depicted in this use case.
Figure 3-4: Intelligent incident data flow
Event
2
BMC TM-ART or
BMC Performance
Manager Portal
detects exception,
forwards data
3
BMC ProactiveNet
Analytics
BMC Event
Manager
BMC Service
Impact Manager
IBRSD
creates incidents
BMC Remedy
Service Desk
Products involved
This section lists the primary products involved in this use case.
!
Atrium
!
Service Assurance
!
Prerequisites
!
Asset inventory scan has been performed and data has been synchronized with
the CMDB.
In the Service Model Editor, a service model has been created where a business
service is impacted by servers.
Technical flow
" Technical use case
1 Incidents are assigned and worked by users in Service Desk.
2 The incident assignee searches for known problems in Problem Management and
72
6 When the affected system returns to normal, BMC Service Impact Manager reports
the change.
7 BMC Impact Explorer indicates that the system has returned to normal.
Data flow
Figure 3-5 illustrates the flow of data depicted in this use case.
Figure 3-5: Problem management data flow
BMC Remedy
Service Desk
BMC Problem
Management
BMC Remedy
Knowledge
Management
BMC Atrium
Explorer
BMC Service
Impact Manager
BMC Impact
Explorer
Products involved
This section lists the primary products involved in this use case.
!
Atrium
!
Service Support
!
74
Prerequisites
!
Technical flow
" Technical use case
1 A virtual system undergoes an unplanned change. Here, it migrates to another
Discovery to immediately run the Virtual Center discovery task. BMC Atrium
Discovery synchronizes changes to the relationship to indicate that the VM image
runs on new ESX server, so data in BMC Atrium CMDB is up to date. Continuous
reconciliation in the BMC Atrium CMDB Reconciliation Engine merges the change
to the production dataset.
Data flow
Figure 3-6 illustrates the flow of data depicted in the use case with a manual
change.
Figure 3-6: Virtualization data flow
BMC Atrium Orchestrator
1
change approved
4
BMC Atrium
Discovery
reconciles with production dataset
BMC Atrium
CMDB
76
Products involved
This section lists the primary products involved in this use case.
!
Atrium
!
Service Support
!
Prerequisites
!
Data prerequisites
!
Discovery product to discover CIs and pupate them in CMDB, and reconcile
into BMC.ASSET.
Technical flow
" Technical use case
1 A user reviews available services in the Service Catalog in the Self Service Interface
5 For change requests: IT goes through the change approval process and implements
the change.
For automated tasks (such as resetting a password): the task is initiated and
performed automatically.
6 The service request is updated as Resolved.
7 BMC Service Request Management updates the service request view with the
78
Data flow
The following diagram illustrates the flow of data depicted in this use case.
Figure 3-7: Web self-service data flow
2
Service
Request
Process
Definition
3
manual or automatic task created
5
IT approval process and change initiation,
or automatic change
6
service request status is updated
80
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Index
A
access to BMC BladeLogic Client Automation from
ITSM user accounts, providing 53
access to ITSM from BMC BladeLogic Client
Automation user accounts, providing 52
applying licenses 35
AR System and AR System applications, installing 32
AR System installation paths 32
audience for this guide 15
audience, intended 15
B
BMC 46
BMC Analytics for Business Service Management
function 8, 22
installing 45
BMC Analytics for CMDB and Asset Management 45
BMC Atrium CMDB SIM extensions 39
BMC Atrium CMDB, function 9
BMC Atrium CMDB, installing 35
BMC Atrium Core
function 9
installing 35
BMC Atrium Discovery and Dependency Mapping
function 8, 22
installing 41
BMC Atrium Impact Simulator, installing 35
BMC Atrium Integration Engine, function 9
BMC Atrium Integration Engine, installing 35
BMC Atrium Orchestrator
function 11, 22
BMC Atrium Orchestrator Configuration
Distribution Peer, installing 45
BMC Atrium Orchestrator Development Studio,
installing 46
BMC Atrium Orchestrator Lightweight Activity Peer,
installing 46
Index
81
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
BMC Portal
function 10, 23
installing 40
BMC ProactiveNet Analytics
function 11, 23
installing 41
BMC ProactiveNet Analytics, installing 41
BMC Remedy Action Request System
function 8
BMC Remedy Approval Server
installing 34
BMC Remedy AR System
installing 34
BMC Remedy Asset Management
function 13, 24
BMC Remedy Assignment Engine
installing 34
BMC Remedy Change Management
function 13, 24
BMC Remedy Flashboards
installing 34
BMC Remedy Incident Management
function 13, 24
BMC Remedy IT Service Management
function 13, 24
BMC Remedy Knowledge Management
function 13, 24
installation 37
integration with BMC Remedy ITSM 37
BMC Remedy Knowledge Management,
installing 37
BMC Remedy Mid Tier, installing 35
BMC Remedy Problem Management
function 13, 24
BMC Remedy Service Desk
function 13, 24
BMC Run Book Automation, installing 45
BMC Service Automation Reporting
installing 47
BMC Service Automation Reporting and Analytics
function 12, 24
BMC Service Level Management
function 9, 25
installing 36
BMC Service Level Management Collection Point 36
BMC Service Request Management
CAI Registry options 36
function 13, 25
installation tip 36
BMC Service Request Management integrations 36
BMC Service Request Management, installing 36
BMC Software, contacting 2
82
C
CMDB synchronization 42
Configuration Management user accounts, providing
access to ITSM from 52
customer support 3
D
data flow diagram 19
Database Initial Size setting 34
database requirements 20
Database Settings 35
diagram, integrations 19
documentation, related 14
E
export failures, cause 35
I
iiws 44
installation
overview 26
paths for WIndows and UNIX 32
installation order 27, 34
installation paths for AR System 32
installing
BMC Transaction Management Application
Response Time Integrations 43
Integration for BMC Remedy Service Desk,
installing 41
ITSM user accounts, providing access to CM from 53
L
licenses, applying 35
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
M
mainframe applications, installing 55
mid tier, installing 35
monitoring applications, installing 44
MSSql_installSecurityScript_Unicode.sql 50
P
patches, for AR System 34
prerequisites 20
Product Catalog
function 9
installing 35
product support 3
purpose of interoperability 7
R
recommended database size, for AR System 34
related documentation 14
reporting applications, installing 44
S
SIM KB component classes 40
support, customer 3
system requirements 20
T
technical support 3
threads setting, in AR System 35
tnsnames.ora 34
transaction management applications, installing 43
U
UNIX
installation path 32
system requirements 20
user accounts
providing access to CM from ITSM 53
providing access to ITSM from 52
W
Windows
installation path 32
system requirements 20
Index
83
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
84
*118532*
*118532*
*118532*
*118532*
*118532*