ism installation guidelines and best practices v1.2 - external

ISM Family Version: 1.0Installation Guidelines and Best Practices Date: 06/05/2009

SWG - TIVOLI

ISM Installation Guidelines and Best Practices

Document Version: 1.2

Document Date: 07/1/2009

IBM SWG, Tivoli, 2023


Document Control Information

Document Owner & Author: David Kulczar ISM Test Architect



Table of Contents

1. Introduction 5

1.1 Purpose 51.2 Content and Scope 5

1.2.1 Products Covered 5

2. Planning Exercises 8

2.1 Product Requirements 82.1.1 Platform Concerns 82.1.2 Compatibility Concerns 9

2.2 Sizing and Capacity Planning 92.3 Other Recommendations 9

3. Recommended Install Sequence 9

3.1 CCMDB 103.1.1 Integration Example Scenario (CCMDB-MAM-TAMIT-SRM-Fixpacks) 103.1.2 Sample Scenario from Multiple Customer Environments (CCMDB-SRM-TAMIT-Fixpacks) 11

3.2 SRM 123.2.1 Integration Example Scenario 1 (SRM-CCMDB-BCPM-ITRPM-Fixpacks) 133.2.2 Integration Example Scenario 2 (SRM-CCMDB-MAM-TAMIT-Fixpacks) 14

3.3 MAM 153.3.1 Integration Example Scenario 1 (MAM-TAMIT-CCMDB-SRM-Fixpacks) 15

3.4 TAMIT 173.4.1 Integration Example Scenario 1 (TAMIT-MAM-SRM-CCMDB-Fixpacks) 17

3.5 TPM 183.6 Other Process Manager Products (PMPs) 183.7 Fixpack and Interim Fix Considerations 193.8 Back-level and Mixed Product Version Support 19

4. Post-Install Activities 19

4.1 Installation Validation 194.1.1 Validating Package Deployment 194.1.2 Validating Installation Logs 20

4.2 Backup Recommendations 21

5. Known Deployment Issues 21

5.1 Common Middleware Configuration Issues 215.1.1 Database 215.1.2 Ldap 215.1.3 Application Server 22

5.2 Known Integration Issues 225.2.1 Integration Defect Analysis 225.2.2 Integrity Checker Issues 225.2.3 Migration Manager Issues 235.2.4 Fixpack and Interim Fix Considerations 23

6. Advanced Topics 23

6.1 Clustering 236.1.1 Vertical Clustering 236.1.2 Horizontal Clustering 24



6.2 WebLogic Support 256.3 Upgrade 26

6.3.1 Upgrade from 7.x releases 276.3.2 Upgrade from 6.x releases 27

7. Appendix 27

7.1 Source Documentation 27



1. Introduction

1.1 Purpose

The Installation Guidelines and Best Practices document is intended to provide detailed examples and recommendations on key deployment issues being faced during deployment of ISM-based applications. Specific focus will be given to installing multiple products on the same platform. It is meant to be an additional information source and reference document and should be used in tandem with the normal install documentation that is delivered with each product.

1.2 Content and Scope

The Installation Guidelines and Best Practices document will focus on installability and coexistence of the standard IBM Service Management (ISM) product offerings as defined in the next section. Content will include examples of successful deployment paths, known issues teams have seen during multi-product deployments, guidelines for validating successful installs and high-level coverage of advanced topics, such as clustering. In some cases, other documents will be referenced to provide more detailed information.

1.2.1 Products Covered

The product set that this document is intended to cover is the Change and Configuration Management Database (CCMDB), Service Request Manager (SRM), Maximo Asset Management (MAM), Tivoli Asset Management for IT (TAMIT), Tivoli Release Process Manager (ITRPM), Business Continuity Process Manager, (BCPM) and high-level information on Tivoli Provisioning Manager. More detailed information on the TPM product and other products that are capable of coexisting on the Tivoli Process Automation Engine (Tpae) base will be targeted for addition in future revisions of this document.

1.2.1.1 CCMDB

IBM Tivoli® Change and Configuration Management Database (CCMDB) software is a platform for storing deep, standardized enterprise data.

This CCMDB software from Tivoli automates data, workflows and policies, to align IT infrastructure management with business priorities.

Aligns development and operations with new Rational Asset Manager integrations.

Simplifies architectural complexity and reduces CCMDB incident and problem management costs.

Provides a non-intrusive configuration and change management database for fast, automated application discovery, deep configuration detail, enterprise-class security and easy integration with other data sources.

Includes a portal interface for creating, monitoring, and reporting about change requests and configuration items.

Includes a toolkit for the creation of custom discovery library adapters and integration modules.

Helps ensure compliance with internal and regulatory requirements by enforcing policies and tracking changes throughout your organization

Note: For the purposes of this document CCMDB focuses on the process layer of the application. CCMDB also ships the TADDM (Tivoli Application Dependency Discovery) application as part of the entire solution. That component is not covered in this document. See the TADDM infocenter for details on that product.



1.2.1.2 SRM

IBM Tivoli Service Request Manager provides an integrated service desk and catalog for a "one touch" IT experience.

This integrated service desk software unifies and automates key service support and asset management processes

Manages both call-based and catalog-based requests in one solution with integrated service desk software and service catalog

Takes problem and incident management software to another level with best practice incident and problem processing

Enables users to obtain IT services through published service offerings

Takes advantage of proven workflows and for fast time to market

Employs change and configuration management software features, such as easy drag and drop screen, workflow customization and simple configuration tools for on-the-fly changes

Combines upgradeability, easy configuration, customer-built customizations and data

1.2.1.3 MAM

IBM Maximo® Asset Management unifies comprehensive asset life cycle and maintenance management on a single platform.

This asset management software provides insight for all of your enterprise assets, their conditions and work processes, for better planning and control.

Manages asset deployment, specifications, monitoring, calibration, costing and tracking from a single system

Provides enterprise asset management software for long and short-term planning, preventive, reactive and condition-based maintenance, schedule management, resource optimization and key performance indicators

Plans inventory to meet maintenance demand, making the right parts available at the right location when needed

Manages vendor contracts with comprehensive support for purchase, lease, rental, warranty, rate, master, blanket and user-defined contracts

Aligns service levels with business objectives by defining service offerings and establishing service level agreements (SLAs)

Adapts to changing business requirements and connects with other enterprise systems through a flexible business process configuration

1.2.1.4 TAMIT

IBM Tivoli Asset Management for IT helps manage IT asset lifecycles in order to control cost and mitigate compliance risk.



Enables effective management of the IT asset lifecycle, to lower cost, mitigate license and regulatory compliance risk, and better align IT with business goals.

Help control the cost of IT assets with a single solution that tracks and manages your hardware, software and related information throughout their life cycle.

Optimize IT asset utilization and IT service levels: deploy not more, not less.

Closely align IT with business requirements through IT asset cost and usage information.

Reduce IT asset cost by redeploying underutilized assets and avoiding software overlicensing.

Relevant contract, lease, warranty and license data minimizes procurement &maintenance expenses and helps negotiate contract renewals.

Improve Service Desk quality & incident resolution time with accurate IT asset information.

1.2.1.5 ITRPM

IBM Tivoli® Release Process Manager provides a process-based solution to address the domain of Release Management as defined by Information Technology Infrastructure Library.

IBM Tivoli Release Process Manager automates complex deployments in the context of your overall release management process, allowing you to assess impact on your IT infrastructure and business critical functions before you release.

Conserve valuable IT resources by assigning critical and time-sensitive releases to the proper person in the release chain.

Speed completion dates and increase performance against service level agreements by making sure that releases related to business-critical functions and servers receive greater scheduling priority.

Keep the workflow moving, support communication

1.2.1.6 BCPM

Tivoli Business Continuity Process Manager provides configurable processes to plan, test and execute IT service continuity.

Enables a comprehensive business continuity solution that integrates the management of people and process with the underlying technology solutions.

Helps reduce the possibility of human error in recovery efforts for systems and applications.

Improves alignment of employee work efforts with prioritized recovery tasks.

Improves productivity through efficient, effective, and tested recovery plans for key business systems and applications.

Reduces the impact of an outage by automating the execution of recovery tasks according to the requirements of specific business systems and applications.

Provides automated process flow that is aligned to industry best practices and ITIL® standards.

Reduces the possibility of Service Level Agreement (SLA) violations and the corresponding IT costs.



Leverages the infrastructure provided by IBM Tivoli Change and Configuration Management Database V7.1.1.

Operating systems supported: Linux, Windows

1.2.1.7 TPM

IBM® Tivoli® Provisioning Manager software provides server, storage and network automation.

Built on a service-oriented architecture, this provisioning software from Tivoli enhances usability for executing changes while keeping server and desktop software compliant.

Provides automated provisioning, improved resource utilization and enhanced IT service delivery through integration with IBM Tivoli Intelligent Orchestrator

Includes a development toolkit for building flexible, customized automation packages tailored to IT or business processes

Works with your existing IT infrastructure and offers scalability for smoother transitions as your business needs change

Simplifies automated provisioning and deployment software with a number of features that are easy to use and improve time-to-value, including a Web replay feature and a graphical user interface with role-based views

Integrates with Rational Test Lab Manager to provide more value in test environments

Operating systems supported: AIX, Sun Solaris, Windows

2. Planning ExercisesThis section of the guide is meant to review some of the considerations that should be analyzed prior to attempting to integrate multiple products in a customer environment.

2.1 Product Requirements

2.1.1 Platform Concerns

Review the requirements in the product documentation for each product that will be included in the environment. Specific focus should be taken to make sure that the Hardware and Software that are targeted for deployment are supported on all products that are to be deployed and minimum requirements are met for all products. If any item is not supported on any one of the targeted products an issue may be encountered.

For instance, the CCMDB 7.x release does not explicitly support WebLogic, while many other products in the stack do provide this support. There is a workaround to enable CCMDB to work with WebLogic, (see Section 6) but prior planning is needed to define a strategy to deploy or problem are likely to be encountered.

Another common deployment consideration to be understood prior to beginning installation is ldap security support. Some products, like CCMDB 7.x, require that an ldap (generally IBM Tivoli Directory Server (ITDS) or Microsoft Active Directory (MSAD)) be used during deployment. If a product that does not require an ldap is the base product in the stack, some compatibility issues may be found during installation.


http://www-01.ibm.com/software/tivoli/products/ccmdb/

http://www-01.ibm.com/software/tivoli/products/ccmdb/


2.1.2 Compatibility Concerns

The next key consideration to evaluate prior to deploying multiple products is the levels and releases that are compatible with the specific version of the Tpae base that will be installed in the environment. Reference the following table to illustrate which products are compatible. This information is current through Tpae 7114. It also lists information for Tpae 7115, which will be delivered in June 2009.

Base levels of the applications mentioned in this spreadsheet can be downloaded externally from Passport Advantage or the Extreme Leverage (XL) Software download location for internal customers. All product patches and fixpacks can be download from the IBM support site at http://www.ibm.com/support.

2.2 Sizing and Capacity Planning

Sizing and Capacity planning should be well thought out when integrating multiple products in the customer environment. Lessons learned from current customer deployments have shown that capacity varies by ISM product despite the capabilities of the Tpae base infrastructure.

It is important to analyze the business processes that are being implemented as a function of the concurrent users expected in the environment. Once that information is obtained, cross-reference that data with the performance documentation from the key products that are responsible for those business processes. Integrating multiple products has not been seen to affect performance or capacity times of other deployed products, so this issue tends to be more of a single product concern.

This document is the comprehensive sizing document for the base version 7 Maximo product set and can be used as a general reference to get started with the sizing task.

2.3 Other Recommendations

It is highly recommended that some mechanism be used to take environment snapshots and backups during key sections of the deployment process. Prior to adding a new application or upgrading an existing application in the environment, a snapshot or complete backup should be performed.

3. Recommended Install SequenceThe purpose of this section is to document the common install paths that have been used in customer deployments and in internal IBM integration testing. These will be documented with each key product as the starting point in the deployment process. These recommendations are not meant to be the definitive list of what is supported but are only intended to document what integration strategies have been executed successfully by current teams.

These instructions should server as high level guidelines. For specific product installation details, the product documentation should be reviewed for each product during the install process.



3.1 CCMDB

Installation scenarios where CCMDB is the first product deployed. Example scenarios have been successfully executed in customer environments or in internal integration testing.

3.1.1 Integration Example Scenario (CCMDB-MAM-TAMIT-SRM-Fixpacks)

Scenario was copied directly from the November 2008 integration scenarios.

1) Install latest version of CCMDB 711 Open the CCMDB Launchpad Click the ‘Launch the CCMDB installer’ link Enter correct information in all panels (see product docs for details) Once installed validate that the installation was successful by opening up CCMDB: http:\\

hostname\maximo

Note: Execute the following steps to help prevent database corruption when adding other ISM products to the same environment

from <InstallDir>\smp\maximo\tools\maximo run "configdb" from <InstallDir>\smp\maximo\tools\maximo run "restorefrombackup" from <InstallDir>\smp\maximo\tools\maximo run "dropbackup"

2) Install MAM 7.1 Open the MAM Launchpad Click on the Activate Maximo Asset Manager License link Enter correct information in all panels (see product docs for details) Once installed validate that the installation was successful by opening up: http:\\

hostname\maximo



3) Install TAMIT 7.1 Open the TAMIT Launchpad Click on the Activate Maximo Asset Manager License link Enter correct information in all panels (see product docs for details) Once installed validate that the installation was successful by opening up: http:\\

hostname\maximo



4) Install SRM 7.1 Open the SRM Launchpad Click on the “Launch SRM Installer” link Enter correct information in all panels (see product docs for details)

o For the list of selectable components demo data installation is optional. Once installed validate that the installation was successful by opening up: http:\\

hostname\maximo





5) Install latest CCMDB fixpacks and hotfixes Launch <InstallDir>\smp\bin\solutioninstallergui Select the appropriate fixpack or hotfix package and enter correct information in all

panels (see product docs for details).o All currently available fixpacks and hotfixes can be downloaded from

http://www.ibm.com/support Complete the installation Repeat for each desired fixpack or hotfix. Note: If more than one package is part of the fixpack, the order should be

Base Services, Common PMP, Foundation, Change Management, then Configuration Management. See the Release Notes for details.

Repeat for SRM MAM and TAMIT fixes are generally installed through the application’s

automatic update utility. (See product doc for details.)

3.1.2 Sample Scenario from Multiple Customer Environments (CCMDB-SRM-TAMIT-Fixpacks)

This is the scenario used during successful deployments at various customer sites.


hostname\maximo



2) Install SRM 7.1 Open the SRM Launchpad Click on the “Launch SRM Installer” link Enter correct information in all panels (see product docs for details)


hostname\maximo






hostname\maximo



4) Install CCMDB Fixpack 4 Launch <InstallDir>\smp\bin\solutioninstallergui Select the CCMDB fixpack 4 packages and enter correct information in all panels (see

product docs for details). Complete the installation

5) Install CCMDB Interim Fix 12 Launch <InstallDir>\smp\bin\solutioninstallergui Select the CCMDB interim fix 12 package and enter correct information in all panels (see


6) Install SRM Fixpack 3 Launch <InstallDir>\smp\bin\solutioninstallergui Select the SRM Fixpack 3 packages and enter correct information in all panels (see


7) Install SRM Interim Fix 1 Launch <InstallDir>\smp\bin\solutioninstallergui Select the SRM interim fix 1 package and enter correct information in all panels (see


3.2 SRM

Installation scenarios where SRM is the first product deployed. Example scenarios have been successfully executed in customer environments or in internal integration testing.

Note: Products that have CCMDB in the installed product stack require that ldap security be enabled.

3.2.1 Integration Example Scenario 1 (SRM-CCMDB-BCPM-ITRPM-Fixpacks)


1) Install SRM 7.1



Open the SRM Launchpad Click on the “Launch SRM Installer” link Enter correct information in all panels (see product docs for details)


hostname\maximo




hostname\maximo



3) Install BCPM 7.1 Open the BCPM Launchpad Click on the Activate Business Continuity Process Manager License link Enter correct information in all panels (see product docs for details) Once installed validate that the installation was successful by opening up: http:\\

hostname\maximo



4) Install ITRPM 7.1.1 Open the ITRPM Launchpad Click on the “Install Release Process Manager” link Enter correct information in all panels (see product docs for details) Once installed validate that the installation was successful by opening up: http:\\

hostname\maximo



5) Install latest SRM fixpacks and hotfixes Launch <InstallDir>\smp\bin\solutioninstallergui



Select the appropriate fixpack or hotfix package and enter correct information in all panels (see product docs for details).

o All currently available fixpacks and hotfixes can be downloaded from http://www.ibm.com/support

Complete the installation Repeat for each desired fixpack or hotfix.

Repeat for CCMDB Repeat for BCPM Repeat for ITRPM

3.2.2 Integration Example Scenario 2 (SRM-CCMDB-MAM-TAMIT-Fixpacks)


1) Install latest version of SRM 7.11 Open the SRM Launchpad Click the ‘Launch SRM Installer’ link Enter correct information in all panels (see product docs for details) Once installed validate that the installation was successful by opening up CCMDB: http:\\

hostname\maximo



2) Install CCMDB 7.1.1 Open the CCMDB Launchpad Click the ‘Launch the CCMDB installer’ link Enter correct information in all panels (see product docs for details) Once installed validate that the installation was successful by opening up: http:\\

hostname\maximo




hostname\maximo






hostname\maximo



5) Install latest SRM fixpacks and hotfixes Launch <InstallDir>\smp\bin\solutioninstallergui Select the appropriate fixpack or hotfix package and enter correct information in all


http://www.ibm.com/support Complete the installation Repeat for each desired fixpack or hotfix.

Repeat for CCMDB MAM and TAMIT fixes are generally installed through the application’s


3.3 MAM

Installation scenarios where MAM is the first product deployed. Example scenarios have been successfully executed in customer environments or in internal integration testing.


3.3.1 Integration Example Scenario 1 (MAM-TAMIT-CCMDB-SRM-Fixpacks)



hostname\maximo



2) Install TAMIT 7.1 Open the TAMIT Launchpad



Click on the Activate Maximo Asset Manager License link Enter correct information in all panels (see product docs for details) Once installed validate that the installation was successful by opening up: http:\\

hostname\maximo




hostname\maximo




hostname\maximo



5) Install latest CCMDB fixpacks and hotfixes Launch <InstallDir>\smp\bin\solutioninstallergui Select the appropriate fixpack or hotfix package and enter correct information in all



Repeat for SRM MAM and TAMIT fixes are generally installed through the application’s


3.4 TAMIT

Installation scenarios where TAMIT is the first product deployed. Example scenarios have been successfully executed in customer environments or in internal integration testing.




3.4.1 Integration Example Scenario 1 (TAMIT-MAM-SRM-CCMDB-Fixpacks)



hostname\maximo




hostname\maximo




hostname\maximo




hostname\maximo





5) Install latest SRM fixpacks and hotfixes Launch <InstallDir>\smp\bin\solutioninstallergui Select the appropriate fixpack or hotfix package and enter correct information in all



Repeat for CCMDB MAM and TAMIT fixes are generally installed through the application’s


3.5 TPM

The Tivoli Provisioning Manager (TPM) 7.x release is relatively new to the Tpae infrastructure, and therefore has had the least amount of formal integration testing. The TPM 7.1 version of the product only officially supports CCMDB 7.1.1.3 and SRM 7.1.0.2 releases in an integrated environment. Full ISM product support and integration TESTING for TPM 7.1.1 is targeted for execution in June 2009 and formal information should be available after those tests are complete.

3.6 Other Process Manager Products (PMPs)

In several of the above scenarios, Business Continuity Process Manager and Release Process Manager are mentioned as part of the deployment path. BCPM and ITRPM are specialized process managers that cover key aspects of the ITIL process, however they require that the Tpae base already exist in the environment. The standard integration route for both BCPM and ITRPM is through CCMDB. Deployments of these two products should have a CCMDB base installation in place prior to deployment.

Also, several products deliver external adapters or integration tools. Examples of these are the Tivoli Provisioning Manager Integration Module (for TPM version 5.x) and Tivoli Configuration Manager (TCM) Integration Module for the Release Process Manager and the Service Desk Integration adapter for the Service Request Manager Product. These are installed through the Solution Installer engine by running “solutioninstaller” or “solutioninstallergui” from the <InstallDir>\smp\bin\ directory. See product Readme files for details on deployment.

Some of the newer products to the Tpae stack also present interesting complications to deployment scenarios. Tivoli System Automation Manager (TSAM) 7.1 is a system automation and virtualization solution that shipped in Q4 2008. It bundles CCMDB 7.1.0.4, TPM 7.1, and SRM 7.1.0.3 as part of the product. Due to this inherent product stack integration, TSAM has not been tested with and may not successfully support other levels of ISM products without support of service professionals. Desktop Management (DTM) 7.1 was also delivered in Q4 2008 and has a written limitation that it will currently not support integration with other Tpae products for the first release. To deploy DTM 7.1 in an environment with other ISM products, multiple infrastructures would need to be built and supported (one for DTM 7.1 and one for the remaining ISM products). The limitations around TSAM and DTM are targeted for resolution in their followon releases. Both products will be involved in future integration testing efforts and they will be integrated fully into the ISM platform support strategy.



3.7 Fixpack and Interim Fix Considerations

All current fixpacks and interim fixes for the current products can be located on the standard IBM support website at http://www.ibm.com/support. It is recommended that any available fixes are reviewed and deployed as soon as possible so that the latest most complete versions of all products are deployed in all environments.

However, this is not always in the best interests of the customer or the deployment plan, so careful consideration and review of the platform support and product compatibility matrices should be undertaken before upgrade.

3.8 Back-level and Mixed Product Version Support

When deploying a fixpack (or mod level) update, the expectation is that all products will move up in tandem. This is how integration testing is currently planned and executed around the ISM suite. An example of this is when the IBM integration team tests CCMDB, SRM, TAMIT, MAM, and RPM on Tpae 7114, all products are brought up to the latest product FP levels.

When deploying a new Tpae Version, the expectation is typically that all new products are installed on a new server, and the data is “migrated” from the old server to the new. An example of this is when products move from 6.2.x to 7.x, where the database is upgraded to the new level, but the Application Server products are deployed on a new server and then targeted to work with the upgraded database. More information on this process can be found in the Advanced Topics section of this document.

When deploying a new Version/Release, expectations are not crisply defined at this time and the latest product documentation should be referenced to understand the full level of support for each product. An example of this type of issue is that when a customer with CCMDB 7.1.1.5 and SRM 7.1.0.4 upgrades to 7.2, can the upgrade be done in stages? More accurately stated, the question is whether or not one or more of the products in the install stack can be left at a back level and still function correctly? This issue is being addressed in future releases.

4. Post-Install ActivitiesThis section is intended to provide some guidelines on activities to perform after deployment of the integrated environment is complete and all documented product post-install steps have been completed.

4.1 Installation Validation

Once the deployment is complete, there are a few steps to use to validate that the installation completed successfully.

4.1.1 Validating Package Deployment

Login to the application by going to http://<hostname>/maximo. Then click the System Information link under the Help menu in the top right of the screen. This will show the installed products and levels of all deployed applications. It will look similar to this, but will vary based on the products and fixpacks deployed. This is an example of System Information output from a CCMDB 7.1.1 Refresh 2 installation. All deployed products and levels should appear in this view.


http://www.ibm.com/support


Product install information can also be validated from the command line on the Admin Workstation, using the following steps.

1. Open a cmd prompt and browse to c:\IBM\SMP\bin2. Run solutioninstaller.bat -action showinstalled -type all

The output from this script will look like similar to the following based on the products that are deployed. In this example, CCMDB and SRM (with sample content) are deployed in the environment.base services Package 7.1.1 Process Manager Product Full Update 56CB9E49C593486BBE0B140FC9796034

Best Practices Content for Service Desk 7.1 7.1 Process Manager Product Base FD45CE7C1F314DDA91FF933CE6AC6C81

IBM Tivoli Maximo Common PMP 7.1.1 Process Manager Product Full Update 0E35A86B92424AE2B94CACB48CCFE623

Sample Data Classifications Based on UNSPSC for Service Desk 7.1 7.1 Process Manager Product Base FAB690894B57417991CBBC06246CD5F8

Service_Catalog_7.1 7.1.0 Process Manager Product Base A8ED00C7D7EA4F0DA01322E4D1D0C971

Service Catalog Content - Users 7.1 Process Manager Product Base C291A60C5C344322A998E32C5D6CF9D3

Service Desk 7.1 7.1 Process Manager Product Base 0E73FC2A870D4CB78F5359501C61FADE

Service Request Manager 7.1 7.1 Process Solution Aggregate Base 822D6A475A9A4B38AFD3FB9D227E4556

Survey Application for Service Request Manager 7.1 7.1 Process Manager Product Base 543EAF78A1A74B7F859146125AFF155A

4.1.2 Validating Installation Logs

The following logs should be reviewed for errors:

Admin Workstation Logs<InstallDir>\SMP\logs\CCMDB_Install.log<InstallDir>\SMP\solutions\logs\<PackageDirectory>\<err and out files>

- This directory has logging information for every solution installer package that was deployed.

WebSphere Logs<InstallDir>\WebSphere\AppServer\profiles\ctgAppSrv01\logs\MXServer (or equivalent directory)

There is significantly more logging information written by each product to assist with problem determination, but most issues will first be uncovered in the logs above.



4.2 Backup Recommendations

It is recommended that the environment be backed up after deployment. There are numerous tools and techniques to perform environment backups and corporations generally have a backup plans and tooling in place. Most general backup procedures and tools are sufficient to handle backing up ISM environments. Here are some general notes and comments about performing backups.

ISM products are generally dependent on the middleware stack pieces (I.e. DB2, Oracle, WebSphere, WebLogic, ITDS, MSAD, etc.) It is recommended that the backup policies for those products be followed.

Frequency should be determined based on customer requirements, but daily backups are recommended.

The Admin Workstation should be backed up entirely, using tools such as VMWare or Symantec Ghost type products. The Admin Workstation environment needs to be maintained as part of the ISM environment for deployment of all future product installs, upgrades, patches or fixes.

It is not sufficient to copy the Admin Workstation install directories as a backup. Registry information on the Windows Admin Workstation is key to the deployment and can be difficult to recreate if destroyed.

5. Known Deployment IssuesThe purpose of this section is to list some of the common deployment issues that have been seen in current multi-product deployments.

5.1 Common Middleware Configuration Issues

5.1.1 Database

Because deploying multiple products generates a large number of database tables, it is important to carefully plan out database sizing and configuration guidelines prior to install. Common configuration settings to be validated on the database prior to deployment include:

Extent Size:The initial-extent size is the number of kilobytes allocated to a table when it is first created. Because ISM solutions create a very large number of tables, we have seen issues with the database quickly running out of space due to a large extent size. This setting should be carefully planned based on the number of products being deployed and the capacity set for the ISM database.

Maxcursors Setting:In the current set of GA products, we have seen issues with maxcursors being exceeded and crashing deployments. This issue is being investigated and corrected in the next versions of ISM releases, but for products released prior to November 2009, a maxcursor setting of 3000 is recommended.

5.1.2 Ldap

A few issues have been uncovered in LDAP configurations during customer deployments.

First, some products in the ISM stack require that an ldap exist for successful deployment. CCMDB 7.x is the key product that requires an ldap for installation. However, the product docs should be validated for all ISM products to better understand how each product supports security. In this case, if the deployment will contain a product that only supports an ldap-based configuration, then the first product installed in the stack



should be installed with ldap security enabled. It is possible to workaround this requirement, but IBM support should be engaged to bypass the requirement.

Second, there is a requirement during the deployment that a user named MAXADMIN exist in a group named MAXADMIN. This is required only during installation and can be changed once installation of all products is complete to better conform to security regulations of the customer. Related to this problem, is a requirement that the maxadmin user have a password of “maxadmin” during the install process. Once installation is complete this should be changed to conform with company password policies. There is a workaround for the password requirement, but IBM support should be engaged if this is desired to properly define and set expectations on the workaround.

Another issue is with customers who use spaces in LDAP group names may see an issue with VMMSync in some instances. This issue should be corrected in future releases and a hotfix is being planned to address the problem. LDAPSync can be used in place of VMMSync as a workaround for the issue.

Sharing the same DB2 instance between ITDS and other products caused some problems in the field because these products needed to restart the DB2 instance and/or change the DB2 port # which caused ITDS to get DB2 errors and fail. It is recommended that, whenever possible, the DB2 instance is not shared by ITDS and other products, if DB2 needs to be restarted during install. Creating a new DB2 instance for ITDS is the recommended solution.

5.1.3 Application Server

Most of the key concerns around configuration of the Application Server are specific to clustering and load balancing to achieve targeted scale goals. This issue is being addressed in an ISM Scalability whitepaper targeted for completion at a later date. Some scalability information is available in section 6.

However, it should also be noted that there are some limitations on supported application servers. Certain releases of ISM products only support WebSphere Application Server 6.x. Please review the product documents prior to installation to validate what is supported. It is possible to workaround this requirement (see Section 6), but IBM support should be engaged to bypass the requirement.

5.2 Known Integration Issues

This section will describe some of the known issues that we have seen and are working to address in customer environments where multiple ISM products have been deployed.

5.2.1 Integration Defect Analysis

There are no open integration defects around multi-product installation that were released into the field. However, install sequencing and product coexistence issues were found during the integration verification phase. Sequences tested during integration testing were selected according to common deployment practices and recommended adoption patterns. Section 3 of this document shows the tested integration adoption routes and therefore those routes are the officially recommended patterns for adoption.

5.2.2 Integrity Checker Issues

Integrity checker is a utility used to verify the integrity of the database data by checking it for errors that can prevent a successful upgrade, such as after applying a fix pack. It creates a list of database errors and warnings. It has a Repair mode that fixes any errors that do not require manual intervention. Other errors are recorded in the list files and log files and must be fixed manually.

After multi-product deployments, significant increases in the number of integrity checker errors have been



seen. These errors were causing blocking issues for customers who have attempted to upgrade to newer product levels or who were attempting to use the Migration Manager utility to move data between environments. The repair mode feature was not resolving these issues and significant manual work was needed to correct problems in the database caused by multi-product deployments.

Several fixpacks and hotfixes have been created to resolve these issues on the latest GA ISM products. Please review the available hotfixes on the IBM support website to attain the latest fixes to resolve these errors. The severity of this issues has caused a realignment in the development and test practices to ensure that these issues are addressed and corrected prior to product shipment. Future releases should not see these types of errors.

5.2.3 Migration Manager Issues

Migration Manager is a tool that enables content to be extracted from one Maximo database, and deployed to another database of the same version with the same base content. On the source machine, Migration Manager is used to define, create, and distribute a package containing the desired content. Migration Manager is then utilized on the target machine to upload and deploy the new or changed content.

In order for Migration Manager to function properly, all integrity checker issues in the environment must first be resolved. See the paragraph on integrity checker for more information on that topic.

The second problem that customers see when attempting to execute migration manager is with environment alignment. Migration manager requires that the source and target environments be at identical database and install levels. If the products installed in each environment are out of line, migration manager will fail. It is important to maintain consistency in environments when patches and fixpacks are applied.

5.2.4 Fixpack and Interim Fix Considerations

As stated in section 3.7, it is recommended to maintain currency with the latest fixpacks and interim fixes in the environment. Issues such are integrity checker and migration manager deployment problems are being aggressively tracked and resolved by the development team. Many of the issues listed in this section will likely have already been resolved or near completion with fixes coming available on the support site on a consistent basis.

6. Advanced TopicsThis section will cover some of the advanced deployment topics that are often faced in complex customer environments. The scope of this document does not include a detailed step-by-step guide on how to deploy these environments. Targeted whitepapers to specifically address, each one of these topics are currently available or are in development now.

6.1 Clustering

In general, clustering is configured in customer environments to provide failover protection and scalability for Application Servers. This section will provide general steps for configuring clustering on WebSphere Application Server environments. More details can be found in the WebSphere 6.1 infocenter:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_wlm_cluster_v61.html



6.1.1 Vertical Clustering

Clustering with vertical cluster members refers to the practice of defining cluster members of an application server on the same physical machine. Experience has shown that a single application server, which is implemented by a single JVM process, cannot always fully utilize the processor power and RAM of a large multiprocessor machine. Clustering with vertical cluster members provides a straightforward mechanism to create multiple JVM processes that together can fully use all the processing power and memory available.

Important: Before clustering a WebSphere instance, it strongly recommended that you backup the WebSphere Application Server administrative configuration. Backing up the administrative configuration will allow you to restore the original configuration if clustering fails during the clustering process.

To create a cluster with vertical cluster members:

1. Complete the installation of a WebSphere node using the standard product install information.

2. Create a WebSphere Cluster using the WebSphere Guided Activity Wizard for clustering.

3. Add additional cluster members.

4. Configure failover

5. Set relative weighting for cluster members.

6. Start the new WebSphere cluster.

6.1.2 Horizontal Clustering

Clustering with horizontal cluster members refers to the traditional practice of defining cluster members of an application server on multiple physical machines, allowing a single application to span several machines while presenting a single system image. Clustering with horizontal cluster members can provide increased throughput and high availability.

Important: Before clustering a WebSphere Commerce instance, it strongly recommended that you backup the WebSphere Application Server administrative configuration. Backing up the administrative configuration will allow you to restore the original configuration if clustering fails during the clustering process.

To create a cluster with horizontal cluster members:

1. Complete the installation of a WebSphere Network Deployment node using the standard product install information.

2. Prepare additional WebSphere nodes for each node to be added to the cluster.

3. Define the JDBC provider path for each node that contains a server that is or will be a member of the WebSphere cluster.

4. Create a WebSphere Cluster (WebSphere provides a wizard under Guided Activities).

5. Add the additional cluster members.

6. Configure failover

7. Set relative weighting for cluster members.



8. Start the new WebSphere cluster.

6.2 WebLogic Support

Several of the ISM products (i.e. CCMDB 7.1.1.x and SRM 7.1.0.x) do not provide out of the box support for the WebLogic Application Server. Due to requests for support, work was undertaken to provide a workable method to enable installation on WebLogic for all products. Here are the steps to install on WebLogic.

Since WebLogic support is not explicitly supported, product management should be in agreement prior to deployment of this configuration in a customer environment.

The following modified installation instructions should be used in conjunction with the Planning and Installation Guides for the products. If the environment is already installed with an existing application that supports WebLogic, such as TAMIT, skip steps 1-3 and start at step 4. Note: Substitute your installation home directory (which might be c:\ibm\SMP ) for "<ISM_HOME>" in the instructions below.

1) Run: install.exe -DPLATFORMONLY=yes

2) On the "Maximo Application Server Type" panel Choose "BEA WebLogic Server"

3) Complete the installation and configuration and exit the installer. See the Product Install Guides for details.

4) Use a file zip tool to open the CCMDB or SRM combined zip file (i.e. payload.zip) to extract the correct component zip files for the process solution installer engine.

(put them in the <ISM_HOME>\pmp directory)

5) Ensure the Maximo database server is started, and the Maximo application (i.e. mxserver) is stopped.

From a command window change directory (cd) to <ISM_HOME>\bin and run solutionInstallerGUI.bat

6) Follow the prompts and install the packages (unzipped earlier to the <ISM_HOME>\pmp directory)

7) Use the WebLogic Server Administration Console to deploy the Maximo EAR files:

<ISM_HOME>\maximo\deployment\default\maximo.ear <ISM_HOME>\maximo\deployment\default\maximohelp.ear

Limitations in WebLogic Environments

Many ISM products take advantage of the WebSphere security framework to provide tight integration with other IBM Tivoli family products. This integration provides a seamless Single SignOn (SSO) user experience when invoking launch-in-context (LIC) from one product to another. Additionally, having a common integrated user repository makes creating and managing of user identities easier across the products. Wherever possible, the common user repository also enables setting up and managing of cross product authorization policy in a single location.

The following configurations or features require WebSphere Application Server and therefore are not currently supported ‘out of the box’ in WebLogic environments. Some of these features, specifically around Single SignOn (SSO), can be manually implemented by the customer or an IBM Services professional, if an



appropriate third party SSO product is available in the customer’s environment.

Configuration/Feature WebSphere V 6.1 support

WebLogic support

Common repository with TADDM Both ISM and TADDM can share a common LDAP based user repository (ITDS or MSAD) by exploiting virtual member manager (VMM) component provided in WebSphere V 6.1.

Y N

SSO with TADDMUsers can seamlessly LIC into TADDM from ISM to view TADDM details. Both products support LTPA based authentication mechanism and as such can be configured in a WAS SSO security domain.

Y N

Authorization Sync with TADDMA common user repository between the two products makes it possible to setup object level authorization policies for CIs from a common location. CIs are grouped into security collections and LDAP groups are given access to these collections from CCMDB. When enabled, a similar authorization policy is automatically setup in TADDM for the same CI objects. This helps administrators with setting up a common object policy from a single product and not having to synchronize these manually.

Y N

SSO with other WAS based applicationsAdditional IBM and non-IBM products that are hosted on the WAS platform can be setup to share a common repository and common SSO security domain. This helps in consolidation of user identities across multiple products and seamless SSO among independently implemented components.

Y N (can do similar with other WebLogic products)

VMMSYNC for synchronizing LDAP objects and multiple LDAP supportCCMDB’s current authorization model relies on a background sync crontask to bring LDAP objects into the database. This WAS VMM-based implementation currently supports both ITDS and MSAD. The VMM based approach provides directory independence to CCMDB and is the recommended direction for future releases. VMM further helps in federating multiple LDAPs under one logical security realm. VMM is also at the base of CCMDB’s multiple LDAP support feature.

Y N (only supports MSAD with LDAPSYNC)



6.3 Upgrade

This section will define some of the specific details and considerations when upgrading ISM environments.

6.3.1 Upgrade from 7.x releases

In general, the product documentation should be used for all basic upgrade scenarios from 7.x to newer releases. The key consideration when upgrading products is platform support and product compatibility as defined in section 2. The documents in those sections should be analyzed to ensure that all products are supported at the same base Tpae level.

In general, it is recommended that all products be upgraded in tandem, but this may not always be possible based on customer environment requirements. The goal for ISM compatibility is to have complete product support at a version level (meaning that all ISM 7.x products would support all other 7.x products). This is currently not the case and the platform support matrix should be used to validate that product upgrades will not negatively affect other products that are deployed in the environment.

6.3.2 Upgrade from 6.x releases

This section provides a brief overview of the upgrade process from Maximo® 6.x products to CCMDB 7.1.1.x or SRM 7.1.0.x. Upgrading from Maximo 6.2 consists of migrating existing data and application customizations from the existing release to the new release.

For details about this process, refer to the IBM Maximo Upgrade Guide, which provides in-depth information about upgrading IBM® Maximo 6 to Version 7 products. You can find the upgrade guide and other upgrade resources at http://www.ibm.com/support/docview.wss?rs=3214&uid=swg21266217. Additional CCMDB 7.1.1.3 specific upgrade information can be found in the technical document located at http://www-01.ibm.com/support/docview.wss?rs=0&q1=ccmdb711relnotes&uid=swg27012900.

Upgrading an existing Maximo 6.x deployment involves the following tasks:

1. Install and deploy CCMDB 7.1.1.x or SRM 7.1.0.x on middleware servers that have not been used for a previous deployment.

2. Prepare the database. Preparing the database include tasks for making a backup of the production database, preparing database instances, granting privileges to users, and synchronization efforts.

3. Perform pre-upgrade tasks. Pre-upgrade tasks include things such as setting language options, processing transactions, and tuning tasks.

4. Run upgrade utilities. Upgrade utilities are provided as part of the CCMDB or SRM Version 7 install and are located in the tools folder of the Maximo root directory of the administrative system. These tools perform tasks that include validation, integrity checking, and upgrading the 6.x database for use with CCMDB 7.1.1.3.

5. Perform post-upgrade tasks. After all upgrade utilities have been successfully run, there are several post-upgrade tasks that must be completed that include various database and system administration tasks and user interface configuration.

7. Appendix


http://www-01.ibm.com/support/docview.wss?rs=0&q1=ccmdb711relnotes&uid=swg27012900

http://www.ibm.com/support/docview.wss?rs=3214&uid=swg21266217


7.1 Source Documentation

The following types of documents and information resources were used in the creation of this whitepaper. The documents and sources referred to in this section should be used as the primary source of information for installation issues for the individual products. This paper is focused directly on integration of the products in a single environment. It is an additional information resource and should be used in tandem with normal product documentation.

Product Installation Guides for each product

Infocenter documentation for each product

o http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index

Product Release Notes and Readmes


ism installation guidelines and best practices v1.2 - external

Documents