Upgrade Guide IBM SmartCloud Control Desk Version 7 Release 5

IBM SmartCloud Control Desk
Version 7 Release 5
Upgrade Guide
Note
Before using this information and the product it supports, read the information in “Notices” on page 141.
Contents
Chapter 1. Overview of the upgrade
process . . . . . . . . . . . . . . . 1
What the upgrade program supports . . .
What the upgrade program does not support
Supported products and releases . . . .
AIX and HP-UX tar command requirements .
Situations requiring special steps . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
2
2
3
4
Chapter 2. Planning your upgrade . . . 7
Minimizing the maintenance window . . . .
Deferring upgrade actions . . . . . . . .
Separating the J2EE server upgrade. . . . .
Upgrading multiple products . . . . . . .
Upgrade scenarios . . . . . . . . . .
Upgrading customizations . . . . . . .
Identifying file differences on Windows . .
Identifying file differences on other platforms
.
.
.
.
.
.
.
.
. 7
. 8
. 9
. 9
. 10
. 10
. 11
. 11
Chapter 3. Before you upgrade . . . . 13
Run Integrity Checker .
Tuning your database .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 14
. 15
.
. 18
Chapter 4. Rehearsing your upgrade
Restarting updatedb
.
.
.
.
.
.
.
.
.
17
Chapter 5. Upgrade scenario road
maps . . . . . . . . . . . . . . . 19
Chapter 6. Upgrading by installing
WebSphere Application Server Network
Deployment v7.0 on a new server
(Scenario 1) . . . . . . . . . . . . 23
Establish supported middleware . . . . . . .
Installing and configuring WebSphere
Application Server Network Deployment v7.0
using the middleware installation program . . .
Migrate database or directory server data (optional)
Running the SmartCloud Control Desk 7.5
installation program with automated configuration .
Installing optional content and integration modules
Migrate customizations . . . . . . . . . .
Running the installation program to update the
database . . . . . . . . . . . . . . .
Running Integrity Checker 7.5 . . . . . . . .
25
25
32
33
39
40
41
42
Chapter 7. Upgrading by migrating
WebSphere v6.1 configuration
information (Scenario 2) . . . . . . . 45
Establish supported middleware . . . .
Installing WebSphere Application Server
Network Deployment . . . . . . .
© Copyright IBM Corp. 2012
.
.
. 47
.
.
. 47
Migrating IBM WebSphere Application Server
Network Deployment configuration
information . . . . . . . . . . . .
Installing the WebSphere update installer . .
Installing and configuring IBM HTTP Server
Installing the WebSphere plug-in . . . . .
Migrate database or directory server data (optional)
Running the SmartCloud Control Desk 7.5
installation program with manual configuration . .
Installing optional content and integration modules
Migrate customizations . . . . . . . . . .
Running the installation program to update the
database . . . . . . . . . . . . . . .
Run integrity checker 7.5 . . . . . . . . . .
48
50
51
54
55
56
60
61
62
63
Chapter 8. Upgrading by migrating
WebSphere v6.1 configuration
information to WebSphere v7.0 using
the middleware installation program
(Scenario 3) . . . . . . . . . . . . 65
Establish supported middleware . . . . . . .
Installing WebSphere Application Server
Network Deployment v7.0 and migrating
configuration information using the middleware
installation program . . . . . . . . . .
Migrate database or directory server data (optional)
Running the SmartCloud Control Desk 7.5
installation program with manual configuration. . .
Installing optional content and integration modules
Migrate customizations . . . . . . . . . .
Running the installation program to update the
database . . . . . . . . . . . . . . .
Run integrity checker 7.5 . . . . . . . . . .
67
67
73
73
77
78
79
80
Chapter 9. Upgrading on Oracle
WebLogic Server (Scenario 4) . . . . . 83
Establish supported middleware . . . . . . .
Configure WebLogic . . . . . . . . . . .
Migrate database or directory server data (optional)
Running the SmartCloud Control Desk 7.5
installation program with manual configuration . .
Installing optional content and integration modules
Migrate customizations . . . . . . . . . .
Running the installation program to update the
database . . . . . . . . . . . . . . .
Run integrity checker 7.5 . . . . . . . . . .
Deploy application files to Oracle WebLogic Server
Chapter 10. Upgrading your VM image
84
85
85
86
88
88
89
90
91
93
Chapter 11. Post-upgrade tasks . . . . 97
Clear the browser cache . . . . . . . . . . 97
Programmatically verifying that the installation was
successful . . . . . . . . . . . . . . . 97
iii
Reviewing your upgraded screens . . . . .
Enabling the improved UI . . . . . . . .
Reviewing table domains and crossover domains
Updating BIRT reports . . . . . . . . .
Updating statistics. . . . . . . . . . .
Uninstalling WebSphere Application Server
Network Deployment v6.1 . . . . . . . .
. 103
. 103
104
. 104
. 105
. 105
Chapter 12. Upgrading Integration
Composer . . . . . . . . . . . . . 107
Upgrading Integration Composer using the
Launchpad . . . . . . . . . . . .
Upgrading Integration Composer on UNIX
operating systems in console mode . . . .
Upgrading integration adapters . . . . .
Improving Integration Composer performance
.
. 107
.
.
.
. 108
. 110
. 112
Chapter 13. Upgrading the Deployer's
Workbench . . . . . . . . . . . . 115
iv
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 14. Miscellaneous topics . . . 117
Presentation XML files . . . . . . . . .
Restoring presentation XML files . . . . .
Adding the PLUSPLISTPRICE field to offerings .
If you have installed fix pack 7.2.1.1 . . . . .
Avoiding database issues from Service Catalog 7.1
.
.
.
.
117
117
118
119
120
Chapter 15. Troubleshooting . . . . . 121
Message CTGIN0024E when upgrading
.
.
.
. 121
Appendix. Integrity checker error
messages . . . . . . . . . . . . . 123
Notices . . . . . . . . . . . . . . 141
Trademarks .
.
.
.
.
.
.
.
.
.
.
.
.
. 143
Index . . . . . . . . . . . . . . . 145
Chapter 1. Overview of the upgrade process
These are the high-level steps that you will complete in order to upgrade to
SmartCloud Control Desk version 7.5.
v Obtain the product images. If you do not have physical DVDs, use the
download document to learn how to download images: http://www.ibm.com/
support/search.wss?q=sccd75download.
v Review the system requirements at https://www.ibm.com/developerworks/
wikis/display/tivoli/SmartCloud+Control+Desk+-+System+Requirements and
the best practices for maximizing the performance of your system at
https://www.ibm.com/developerworks/mydeveloperworks/groups/service/
html/communityview?communityUuid=a9ba1efe-b731-4317-9724a181d6155e3a#fullpageWidgetId=W5f281fe58c09_49c7_9fa4_e094f86b7e98
&file=c51d5f5b-dea3-4043-a81f-d5213fc10063. Note that you must upgrade to a
new version of your J2EE server, whether it is IBM® WebSphere® Application
Server or Oracle WebLogic Server.
v Be sure that you have the latest version of this upgrade guide. You can find the
latest version of this guide, as well as additional information about upgrading,
on the SmartCloud Control Desk wiki's Upgrade page at https://
www.ibm.com/developerworks/wikis/display/tivoli/
SmartCloud+Control+Desk+-+Installing%2C+Migrating+and+Upgrading.
v Review the latest news and updates regarding the upgrade process on the wiki's
Upgrade page.
v Review the list of products from which you can upgrade and note special
requirements that apply in some situations.
v Review the available upgrade scenarios and choose which scenario you will
follow.
v Run the upgrade in a test environment to identify and fix problems.
v Upgrade your production environment.
v Complete an acceptance test and go live with your upgraded system.
When you upgrade your production environment, you want to minimize the time
during which your production system is unavailable to users. This time is called
the maintenance window. This guide helps you minimize your maintenance window
by identifying tasks that can be performed before the window starts.
What the upgrade program supports
The upgrade program supports upgrading the following elements of your Maximo
system:
v All data
v Any configurations that you performed with the Maximo configuration tools,
including user-interface changes that you made with the Application Designer
(but see “Reviewing your upgraded screens” on page 103 for information about
applications that you have modified)
v Data model, including new columns or tables that you added to the database.
v User interface and presentation layer
v Workflow processes
v Data validations and defaults
© Copyright IBM Corp. 2012
1
v Integration definitions
v Escalations
What the upgrade program does not support
The SmartCloud Control Desk SmartCloud Control Desk 7.5 installation program
does not automatically upgrade certain aspects of your prior deployment.
The following items are not automatically upgraded by the installation program:
v Any changes to the Maximo database schema or database objects (tables,
columns, indexes, and so on) that were not made with the Database
Configuration application.
Any changes to the database schema or database objects must be made using
Maximo applications. If you did not use the Database Configuration application
when modifying the Maximo database schema, you must remove those
customizations before beginning the upgrade process. You can use Maximo
applications to reapply these customizations after the upgrade to SmartCloud
Control Desk 7.5.
v Any database objects that you created (including stored procedures, triggers,
views, and synonyms) that are dependent on Maximo database objects.
The upgrade does not re-create such objects. You must reapply any custom
triggers after the SmartCloud Control Desk 7.5 upgrade has completed.
v Custom extensions of product code such as additions to Java code, Java applets,
JavaScript, and HTML.
These customizations must be manually migrated to the SmartCloud Control
Desk 7.5, as described in the upgrade scenarios.
v Service Catalog 7.1 configurations and data. If you want to preserve the
offerings that you defined using Service Catalog version 7.1, you must upgrade
to Service Request Manager® version 7.2.1, and then upgrade to SmartCloud
Control Desk 7.5. You might find it easier to upgrade directly to SmartCloud
Control Desk and then re-create your offerings using the superior Service
Catalog tooling available in the new release.
v Upgrading from one database platform to another. For example you cannot
upgrade from version 7.2.1 on Oracle to version 7.5 on DB2®.
If you want to move from one database platform to another, you must install a
new instance of SmartCloud Control Desk 7.5.
The upgrade does not grant security authorizations to new applications or to new
options within existing applications. You must assign authorization through the
product security applications after the upgrade is complete for new SmartCloud
Control Desk 7.5 applications. Refer to the Security section of the information
center for details.
Supported products and releases
You can upgrade to SmartCloud Control Desk version 7.5 from several different
starting points. Some of these starting points require extra steps.
SmartCloud Control Desk combines features and functions from these prior
products:
v IBM Tivoli® Change and Configuration Management Database (CCMDB)
v IBM Tivoli Service Request Manager
v IBM Tivoli Asset Management for IT
2
IBM SmartCloud Control Desk: Upgrade Guide
You can upgrade from any of the following product releases. Be sure to review the
notes at the end of this section to learn about special requirements for some
upgrade scenarios, including upgrading Service Catalog data from Service Request
Manager 7.1.
Product
Releases
Change and Configuration Management
Database
v 7.1.1.6 and subsequent fix-pack levels
v 7.2.0.1 and subsequent fix-pack levels
v 7.2.1 and subsequent fix-pack levels
Service Request Manager
v 7.1.0.5 and subsequent fix-pack levels
v 7.2.0.1 and subsequent fix-pack levels
v 7.2.1.1 and subsequent fix-pack levels
Asset Management for IT
v 7.1.1.6 and subsequent fix-pack levels
v 7.2.1 and subsequent fix-pack levels
v 7.2.2 and subsequent fix-pack levels
Tivoli Service Manager Quick Install
v 7.2.1
Any valid combination of these product releases can be upgraded. You do not
need to have all these products installed before you upgrade. The Service Provider
editions of these product releases can be upgraded to IBM SmartCloud Control
Desk - Service Provider Edition.
These products run on the 7.1.1.6 or later release of Tivoli's process automation
engine. To check the versions that you have installed, click Help > System
Information. If you are using an earlier release of one or more of these products,
you must upgrade to a release listed here before you can upgrade to SmartCloud
Control Desk.
If you have installed Tivoli Service Manager Quick Install, you can upgrade to IBM
SmartCloud Control Desk VMImage.
You cannot change deployment options during the upgrade process. For example,
you cannot upgrade from Tivoli Service Manager Quick Install to a locally installed
product.
AIX and HP-UX tar command requirements
Both the native UNIX tar command and the GNU version of the tar command are
required by the middleware installation program. Because the native utility does
not support long file names, ensure that GNU tar version 1.14 or higher is
installed. GNU tar version 1.14 ensures that installation files can be extracted.
Verify that the system path variable contains both native UNIX tar and GNU tar
paths. The GNU tar path must be defined before the native UNIX tar path. For
example, the native tar utility is installed in /usr/bin and the GNU tar utility is
installed in /opt/freeware/bin/tar.
If you have set a symbolic link to overwrite the native UNIX tar command with
the GNU tar command an error occurs.
http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html
Chapter 1. Overview of the upgrade process
3
Situations requiring special steps
Some upgrade scenarios require special steps beyond the normal upgrade process.
Review this list to see whether you need to take any of these steps.
To upgrade from earlier versions of the supported products
Apply the necessary fix packs to upgrade your products to a release from
which upgrade is supported. For example, if you have CCMDB 7.1.1.4, you
can apply a fix pack to get to version 7.1.1.7. You can find available fix
packs at Fix Central: http://www.ibm.com/support/fixcentral
To upgrade from base services version 7.1.1.6
By default, the installer requires version 7.1.1.7 to upgrade. When you use
the launchpad, this value is automatically set to 7.1.1.6. To upgrade from
version 7.1.1.6 without using the launchpad, you must set the environment
variable UPGRADEMINLEVEL to 7.1.1.6. This applies if you are upgrading
from Change and Configuration Management Database version 7.1.1.6 or
7.2.0.1 or Service Request Manager 7.2.0.1.
To upgrade from Service Request Manager 7.1
If you are using the Service Catalog component of Service Request
Manager 7.1, your offering definitions cannot be upgraded directly to
SmartCloud Control Desk. If you want to preserve your offerings, you
must upgrade first to version 7.2.1, complete or resolve all of your active
Service Catalog processes, and then upgrade to SmartCloud Control Desk.
If you want to define new offerings in version 7.5, and do not need to
preserve your offerings from version 7.1, you can upgrade directly to
version 7.5.
To upgrade from Service Request Manager 7.2.x, if you customized the
PLUSPLISTPRICE field in offerings
In order to better support Pricing and Billing in Service Provider
environments, significant architectural changes have been made. The field
PLUSPLISTPRICE, currently defined for Offerings, has been removed. If
you customized this field, and you want to include this customization in
your upgraded environment, you must take steps after upgrading to add
the field back in. See “Adding the PLUSPLISTPRICE field to offerings” on
page 118 for details.
If you did not use the default install directory
During the upgrade, the Choose Installation Directory panel shows the
installation directory that you used when you installed prior releases. If
your administrative workstation runs Windows, the installer can detect the
original installation directory, and this panel should show the correct path.
If your administrative workstation runs another platform, the installer
cannot detect the original installation directory; it will always show the
default directory. In this case you must enter the original installation
directory on this panel.
If you had optional content installed
If you installed the optional content packages available with any of the
prior products, you cannot update your database without replacing the
content. You must install the optional content package using the option
provided on the SmartCloud Control Desk launchpad.
If you had Tivoli Provisioning Manager installed
If you had Tivoli Provisioning Manager installed on Tivoli's process
4
IBM SmartCloud Control Desk: Upgrade Guide
automation engine along with other products that you are upgrading, you
must remove database artifacts related to Tivoli Provisioning Manager
before you perform the upgrade.
Chapter 1. Overview of the upgrade process
5
6
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 2. Planning your upgrade
Because all implementations are unique, the upgrade process is different for every
deployment. However, there are some considerations in the process that should be
common to every upgrade.
Planning your upgrade schedule
When you plan your upgrade schedule, you need to plan adequate time to
complete each of the different phases of the upgrade process:
v Determining when you can upgrade
v Planning the upgrade
v Performing pre-upgrade tasks
v Upgrading in a test environment
v Troubleshooting your test upgrade
v Performing acceptance tests
v Training staff on new features
v Upgrading your production environment
You should plan time into your schedule to perform the upgrade in a test
environment. Performing a test upgrade allows you to test and troubleshoot your
upgrade, without additional downtime in your production environment. It is
essential to make your test or rehearsal environment as similar as possible to your
production environment.
You should also schedule sufficient time to train administrators and users to use
the new software. Team members need to understand the capabilities of
SmartCloud Control Desk in order to participate in the upgrade planing process.
Note: IBM offers additional services to assist in evaluating or performing your
upgrade.
Review current database settings
To ensure a successful upgrade, compare the configuration settings of your existing
database with the default configuration settings used by the current installation
program. This information can be found in the SmartCloud Control Desk 7.5
installation information within the manual configuration instructions for your
database type. If your current values are insufficient, it could cause problems
during the upgrade process. Set configuration parameters equal to or greater than
those defined in the SmartCloud Control Desk 7.5 installation information.
Minimizing the maintenance window
The maintenance window is the time during which your system is unavailable to
users. One goal of the upgrade process is to make this window as short as
possible.
There are certain upgrade activities that must be completed during the
maintenance window. These include updating your database and deploying code
to your J2EE server. Other activities can be performed either during the
© Copyright IBM Corp. 2012
7
maintenance window or before it begins. Careful planning can help you minimize
the window by performing only those tasks that must take place during it.
Preparing for these tasks can enable you to shorten the duration of some of the
tasks.
These activities must take place during the maintenance window
v
v
v
v
v
v
v
v
v
v
Shut down your operational system
Back up your Maximo® database
Make any database fixes that were identified during testing
Update the database with the updatedb tool, and TDToolkit if you have installed
additional languages.
Run Integrity Checker 7.5 and fix any errors
Apply any post-upgrade customizations or configuration
Build and deploy the Maximo Enterprise Archive (EAR) file and the
maximoeclipse.ear file to the J2EE server
Perform acceptance testing
Revert to the previous configuration if the upgrade fails
Make the upgraded system available to your users
The time required for these activities depends on your environment. For example,
the time required to back up your database depends on the size of the database as
well as the backup media used and its speed. The time required to run updatedb
depends on the size of your database and the releases from which you are
upgrading. The time required to deploy ear files depends on the number of servers
in your clustered system and the speed of data transfer.
Careful preparation can help you shorten the time required for some tasks. By
rehearsing your upgrade in a test environment, you can be prepared to spend a
shorter time on customizations and on fixing Integrity Checker errors. You might
be able to prepare scripts to remove custom triggers from the database before
upgrading and re-apply them afterwards. Having specific use cases identified for
acceptance testing enables you to proceed through the steps with less wasted time.
Deferring upgrade actions
When you upgrade, using any scenario, defer the update of the database and the
deployment of the ear file.
When you run the product installer, you will see options to defer the updating of
the database and the deployment of the ear files to the J2EE server. You should
choose to defer these processes when you upgrade. There are two reasons to make
this choice:
Additional actions
After the installation program finishes, you might want to take any of
these actions. If you wait until later, you must re-deploy the ear file
afterwards.
v Install optional content: optional content includes sample artifacts
designed to help you get started using product functions. If you had
optional content packages from any of the prior products, you must
install the SmartCloud Control Desk optional during your upgrade,
before you update the database.
8
IBM SmartCloud Control Desk: Upgrade Guide
v Install integration enablement packages: if you want to integrate
SmartCloud Control Desk with one or more other products, you can
install enablement packages from the launchpad.
Shortening the maintenance window
The maintenance window is the period during which your production is
unavailable for use during the upgrade process. If you do not defer the
database update and the ear file deployment, your maintenance window
begins when you start the installer. By deferring these actions, you can
complete the running of the installer before beginning your maintenance
window.
Separating the J2EE server upgrade
You might want to separate the upgrade of your J2EE server from the product
upgrade.
If you are using WebSphere Application Server for your J2EE server, you can
separate the upgrade to WebSphere Application Server v7 from the upgrade to
SmartCloud Control Desk. All releases of Change and Configuration Management
Database, Service Request Manager, and Asset Management for IT, beginning with
7.2, have been certified to run on WebSphere Application Server v7. If, for
example, you have version 7.2.1 of Service Request Manager and CCMDB
installed, you can upgrade your WebSphere Application Server to version 7 and
keep Service Request Manager and CCMDB at their current version. Then you can
upgrade to SmartCloud Control Desk as a separate project at a later date.
If you want to use this option, you can either deploy a new server with WebSphere
Application Server v7, or add WebSphere Application Server v7 to your current
v6.1 server. You can continue to use your current database server and optional
directory server.
In either case you must configure your WebSphere Application Server v7 server
and deploy the ear file to it.
Upgrading multiple products
You must upgrade all products before you update your database.
You might have other products deployed to your instance of Tivoli's process
automation engine besides the products that will be upgraded to SmartCloud
Control Desk. For example, you might have Service Request Manager installed
along with Maximo Asset Management and one or more industry solutions. In this
case, you must run the installers for all the products to upgrade them to the new
version before you update your database. As you run each installer, defer the
updating of the database and the deployment of the ear files. After you have run
all the installers, you can start your maintenance window. When you update the
database, the updates required to upgrade all the products will be made at the
same time.
If you are upgrading to both SmartCloud Control Desk 7.5 and Maximo Asset
Management 7.5, upgrade to SmartCloud Control Desk first. This ensures that the
level of the Deployment Engine that is installed works successfully for both
upgrades.
Chapter 2. Planning your upgrade
9
Upgrade scenarios
There are several different ways in which you can approach the upgrade process.
The scenarios differ primarily in how you prepare your new application server
before running the upgrade.
Install WebSphere Application Server version 7 on a new server
In this scenario, you install WebSphere Application Server on a different
server from your existing production server. In this case you cannot use
the WebSphere migration wizard or the middleware installer to migrate
your profiles, port definitions, other data, and existing applications to the
version 7 instance. You must migrate this information yourself. In this
scenario you can prepare your new environment while still using your
existing products, so that the time when your system is unavailable to
users is minimized.
In these scenarios, you install IBM WebSphere Application Server on your current
production server.
Use the WebSphere Application Server migration wizard
You can install WebSphere Application Server version 7 on the same server
where you are currently running WebSphere Application Server version
6.1. By using the same server, you can use the migration wizard provided
with WebSphere Application Server to migrate your profiles, port
definitions, other data, and existing applications to the version 7 instance.
When you start the migration wizard, it disables your version 6.1 instance,
so that your production environment is unavailable until the new version
is brought online.
Use the middleware installer to migrate configuration information
If you installed WebSphere Application Server version 6.1 using the
middleware installer, and you use the middleware installer to install
WebSphere Application Server version 7 on the same server, you can use
the middleware installer to migrate configuration information to the new
version.
Upgrade on WebLogic Server
If your existing products are installed on Oracle WebLogic Server, you
must upgrade your WebLogic Server to the required version. Refer to the
WebLogic Server documentation for upgrade information.
Upgrading customizations
If you have customized the products from which you are upgrading, you must
evaluate each customization and decide how to move it to your upgraded
environment.
About this task
You might have modified the behavior of one or more products by implementing
Java-based extensions, scripts, style sheets, or other customizations. You must
review each of these customizations to determine the best approach to
implementing it in your new environment.
When you run the installer, it renames the existing maximo directory to
pre_75_maximo and creates a new maximo directory for the new release. You must
move the customizations that you want to use in your upgraded environment into
this new directory.
10
IBM SmartCloud Control Desk: Upgrade Guide
Make a list of your customizations and follow these steps to determine what to do
with each one.
Procedure
1. Perform a product upgrade in a test environment. You can use the techniques
described below to identify files that are present in your old environment but
not in the upgraded environment.
2. Review the information provided with the new release. Has the new release
provided functions that make your customization unnecessary? If so, mark it
appropriately and proceed to the next customization on your list.
3. If the customization is required in the new environment, recompile it against
Java version 6.
4. Test the recompiled customization thoroughly in your upgraded test
environment to ensure that it produces the desired results.
5. After verifying the customization, move it to the new maximo subdirectory on
the administrative workstation, which contains code compatible with the 7.5
release. This will ensure that it will be built into the maximo.ear file for
deployment to your J2EE server.
Identifying file differences on Windows
About this task
After upgrading, you can use these commands to identify differences in the lists of
files in the new and old maximo directories on your administrative workstation.
These commands do not look at the contents of the files; they simply compare lists
of file names. Comparing the lists can help you to identify files that you added to
your prior products. The lists of differences will include changes in product files as
well as new files that you have added for customizations. You must determine
which files you added.
On Windows, these commands capture the directory name as well as the file
names, so you must rename the directories in order to make the results
meaningful. If you run the commands in directories with different names, all the
file names will be flagged as different. These commands use the default installation
location; if you have installed to a different directory, substitute its name for
"IBM\SMP."
Procedure
1. cd C:\IBM\SMP\maximo
2. dir * /b /s > maximo_new.txt
3. Rename the maximo directory to a temporary name.
4. Rename the pre_75_maximo directory to maximo.
5. dir * /b /s > maximo_old.txt
6. View the differences between the lists: fc maximo_new.txt maximo_old.txt
7. Rename the directories to their original names.
Identifying file differences on other platforms
About this task
After upgrading, you can use these commands to identify differences in the lists of
files in the new and old maximo directories on your administrative workstation.
These commands do not look at the contents of the files; they simply compare lists
Chapter 2. Planning your upgrade
11
of file names. Comparing the lists can help you to identify files that you added to
your prior products. The lists of differences will include changes in product files as
well as new files that you have added for customizations. You must determine
which files you added. These commands use the default installation location; if
you have installed to a different directory, substitute its name for
"/opt/IBM/SMP."
Procedure
1.
2.
3.
4.
cd /opt/IBM/SMP/maximo
ls -R -1 >./maximo_new.txt
cd ../pre_75_maximo
ls -R -1 >./maximo_old.txt
5. diff maximo_new.txt maximo_old.txt
12
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 3. Before you upgrade
Complete these tasks before you upgrade.
Procedure
1. Back up your installation directory on the administrative workstation. By
default, this directory is C:\IBM\SMP or /opt/IBM/SMP.
2. Back up your Deployment Engine database. Issue this command:
C:\Program Files\IBM\Common\acsi\bin\de_backupdb.cmd C:\IBM\SMP\DE_BACKUPS\BEFORE_7.5
3. Create a backup of the Deployment Engine binaries, which are in this location:
C:\Program Files\IBM\Common\acsi. If you restore the DE database, you
must restore the same level DE database into the same level of DE binaries.
4. Make sure that you have no Deployment Engine lock files, which can prevent
the installer from running. Delete any files with .lck extensions from the
C:\Program Files\IBM\Common\acsi\logs directory.
5. Disconnect any tools, such as monitoring tools, that are connected to your
database.
6. Disable any custom triggers that you have created in your database. You must
re-implement these triggers after completing the upgrade.
7. Disable any integrations with other products that you have installed.
8. Commit all database changes.
In order to confirm that all changes have been committed, run the following
SQL queries against the Maximo database.
SELECT count(*) from maxobjectcfg where changed != ’N’
SELECT count(*) from maxsysindexes where changed != ’N’
'N' indicates that a change has been committed. For this query, if entries are
returned with any value other than N, you must apply or discard the
configuration changes using the appropriate menu option in the Database
Configuration application.
Alternatively, you can use configdb.bat to commit configuration
changes. Open a command prompt on the administrative workstation and
issue the following commands:
cd c:\IBM\maximo\tools\maximo
configdb.bat
restorefrombackup.bat
dropbackup.bat
Running configdb.bat and restorefrombackup.bat performs the same
function as choosing the Apply Configuration Changes menu option from the
Database Configuration application. The configdb.bat and
restorefrombackup.bat require all application servers serving the maximo
application to be stopped. The dropbackup.bat command does not require
application servers to be stopped.
9. Find and drop any temporary tables. Tables whose names begin with "XX" are
temporary tables that must be dropped before running the upgrade process. If
these tables exist, they cause the upgrade process to fail. Complete the
following steps to remove these tables:
a. Verify that the temporary tables exist in the database:
© Copyright IBM Corp. 2012
13
DB2®
select count(*) from sysibm.systables where name like ’XX%’ and
creator = ’MAXIMO’
Microsoft SQL Server
SELECT count(*) FROM sysobjects WHERE xtype = ’U’ AND name like ’XX%’
Oracle
SELECT count(*) from all_tables where table_name like ’XX%’
b. Stop all Application Servers running the maximo application, for example,
MXServer.
c. Open a command prompt on the administrative workstation and issue the
following commands:
cd c:\IBM\maximo\tools\maximo
configdb.bat
restorefrombackup.bat
dropbackup.bat
Running configdb.bat and restorefrombackup.bat performs the same
function as choosing the Apply Configuration Changes menu option from
the Database Configuration application in Maximo. The configdb.bat and
restorefrombackup.bat require all application servers serving the maximo
application to be stopped. The dropbackup.bat command does not require
application servers to be stopped.
d. Restart all Application Servers running the maximo application, for
example, MXServer.
10. Remove any integration objects that you added to the database. These objects
prevent updatedb from running successfully.
a. Run this command to see whether you have any user-defined integration
objects:
select * from maxintobject where intobjectname=’MXORGANIZATION’ and userdefined=1
b. If the command returns any results, run this command to delete the
objects:
delete * from maxintobject where intobjectname=’MXORGANIZATION’ and userdefined=1
11. Back up your Maximo database, using the tools provided by your database
vendor.
12. Check for issues with older reports at http://www-01.ibm.com/support/
docview.wss?uid=swg21418457
13. If you are upgrading from Service Request Manager, run this SQL statement:
select * from sigoption where optionname in (’tsdmandwnt’,’TSDMANDWNT’)
If it returns only the upper-case value, you do not need to do anything. If it
returns both an upper and lower-case value, delete the lower-case value:
delete * from sigoption where optionname=’tsdmandwnt’
If returns only a lower-case value, run this command to change the
lower-case value to upper-case:
sigoption set optionname = upper(optionname) where optionname = ’tsdmandwnt’
Run Integrity Checker
Run the Integrity Checker utility from your prior release.
14
IBM SmartCloud Control Desk: Upgrade Guide
About this task
Before proceeding further with the upgrade process, run the Integrity Checker
utility. This utility checks the database to ensure it is ready for the upgrade. When
run in Report mode, the Integrity Checker utility checks the current database and
reports on common errors. If the Integrity Checker reports an error, you should
resolve it before proceeding with the upgrade.
The upgrade process can fix some types of errors in your database. You can use
your test environment to determine which database errors the upgrade process can
fix and which errors you must fix before upgrading.
Procedure
1. From the administrative workstation of the existing deployment, open a
command prompt and change directory to the maximo tools directory. For
example, c:\ibm\SMP\maximo\tools\maximo
2. Start the Integrity Checker tool.
integrityui.bat
3. Select the Check Integrity tab.
4. Run the Integrity Checker in Report mode.
a. Ensure that the Repair Mode? check box is cleared, and then click Run
Integrity Checker.
b. When the report dialog box appears, click OK.
Results are found in the install dir\maximo\tools\maximo\log directory in the
file defined in the Log File Name field of the Check Integrity panel.
5. Review the log files for errors. Some error messages will state that the error can
be resolved by running the Integrity Checker in Repair mode. Other errors
might require you to fix them using other means before running Integrity
Checker in Repair mode.
6. Optional: If any errors are reported, run the Integrity Checker in Repair mode.
a. Select the Repair Mode? check box, and then click Run Integrity Checker.
b. When the report dialog box appears, click OK.
7. If you had to fix any errors, you have pending database updates. Run the
configdb command to commit these pending updates. Run configdb.bat or
configdb.sh from the same prompt where you ran the integrityui command.
8. Optional: If Integrity Checker was run in Repair mode, check the log file to
ensure all reported items have been repaired. If further manual intervention is
required, resolve the errors, run configdb, and then re-run the Integrity Checker
in Report mode. Repeat the process until no more errors are reported.
Results
Review error messages reported by the Integrity Checker in “Integrity checker
error messages,” on page 123. While the Integrity Checker can repair many issues,
you might have to resolve some errors manually by consulting the log files.
Tuning your database
Tuning your database properly can make a big difference in how well and how
quickly your upgrade goes.
Chapter 3. Before you upgrade
15
About this task
The updatedb process updates your database, processing updates specified by all
the products that you are upgrading. Several factors affect the efficiency with
which this process runs. One of the most important factors is a well tuned
database.
To prepare your database for upgrading, take all of the following steps. In some
cases, the command to perform the step for an IBM DB2 database is provided. If
you use an Oracle database, be sure to run the equivalent commands. If necessary,
experiment with some settings in your test environment so that you can tune your
production environment to optimize the upgrade.
Procedure
1. Be sure you have adequate tablespace. Allocate a tablespace larger than your
database, to allow for expansion and movement of data. For example, if your
database is 41GB, issue this command:
db2 "alter tablespace MAXDATA resize (ALL 45000 M)"
2. Be sure you allocate enough space to your primary and secondary transaction
log files. Increase the size of the primary log file to lessen the spillover to the
secondary log file. For example:
db2 update database configuration for db-name using LOGFILSIZ 40000
db2 update database configuration for db-name using LOGPRIMARY 30
db2 update database configuration for db-name using LOGSECOND 100
3. Run the RUNSTATS tool for all tables, including the system catalog. The
RUNSTATS tool collect current statistics on tables and indexes. This provides
the optimizer with accurate information with which to determine the best
access plan.
4. Be sure that the DB2 statement concentrator is on. The statement concentrator
modifies dynamic SQL statements at the database server so that similar, but not
identical, SQL statements can share the same access plan.
5. Turn on sequence caching. For example:
db2 "alter SEQUENCE MAXIMO.MAXSEQ cache 500"
6. Ensure that logging is directed to a system that is not I/O constrained. For
example:
db2 update db cfg for db-name using NEWLOGPATH "/db2data/db2logs/NODE0000”
7. Review other best practices for maximizing the performance of your system,
including your database, at https://www.ibm.com/developerworks/
mydeveloperworks/groups/service/html/
communityview?communityUuid=a9ba1efe-b731-4317-9724a181d6155e3a#fullpageWidgetId=W5f281fe58c09_49c7_9fa4_e094f86b7e98
&file=c51d5f5b-dea3-4043-a81f-d5213fc10063.
16
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 4. Rehearsing your upgrade
Rehearsing the upgrade in a test environment helps your production upgrade to
go as smoothly as possible.
About this task
Before you perform your production upgrade, be sure to rehearse your upgrade in
a test environment. This rehearsal helps your production upgrade go smoothly by
identifying any issues that must be corrected and enabling you to make those
corrections before you begin your production maintenance window, or to make
them quickly during the window if necessary. Rehearsing your upgrade also helps
you to gauge how much time to allocate for your production upgrade.
To make the test rehearsals as useful as possible, mimic your production
environment as closely as you can. The most crucial element is your database.
Database-related issues are the most prevalent issues that arise during the upgrade
process. For this reason, it is important to use as current a copy of your production
database as possible in your testing. Ensure that the configurations and
customizations that you have made in your production database are included in
your test environment.
Follow these steps to prepare for testing. As you complete each step, make notes to
record your procedures so that you can duplicate them.
Procedure
1. Review the hardware and software prerequisites and make sure that your test
environment meets them.
2. Identify the product releases from which you are upgrading. Review the list of
special situations to see whether any of them apply to your upgrade.
3. Locate the images required to upgrade your middleware and products.
4. Decide which upgrade scenario best fits your needs.
5. Perform backups and other tasks identified in Before you upgrade.
6. Bring your middleware products to the required levels.
7. Follow the steps listed in your chosen upgrade scenario.
8. Correct any problems that are found in your database or your test
environment. Record these changes so that you can make them in your
production environment if needed. Make note of how long the changes take,
so that you can plan to include them in your maintenance window.
9. If you have implemented automation scripts for use with Service Catalog
offerings, test the scripts in the upgraded environment.
10. If you have implemented Java-based or other customizations in your
environment, review and test them in the upgraded environment.
11. Repeat the procedures as needed until the upgrade runs cleanly.
© Copyright IBM Corp. 2012
17
Restarting updatedb
The updatedb tool performs database update tasks during an upgrade. This tool
keeps track of the last database update statement that was successfully
performed. If you experience a failure during the use of updatedb, you might be
able to correct the error, restart updatedb, and resume from the last successfully
completed task.
You can resume processing only if the error was caused by the statement being
processed, for example, a name collision on an insert. If the problem is systemic or
environmental, such as running out of table space, you cannot resume updatedb
processing.
The tool records the number of commands or free-form lines it has processed
successfully in the current file. It does not record the commands themselves.
To resume processing after encountering and fixing an updatedb error, issue the
updatedb command again from the same command prompt. This will continue
processing from the last successful statement that was run.
If you modify a database change file in order to fix a problem, you might need the
updatedb tool to rerun all database update tasks instead of resuming. For example,
if you add a new statement before the last successful statement, updatedb might
not be able to resume successfully. In this scenario, use the following SQL
commands to clear variables used to identify the last successful statement before
restarting the updatedb tool.
delete from maxvars where varname in (’BMXLASTATEMENT’,’BMXLGFFLINE’)
delete from maxvartype where varname in (’BMXLASTATEMENT’,’BMXLGFFLINE’)
Ideally, you should use this capability only in your test environment. When you
upgrade your production system, you should have eliminated all the errors from
your database before running updatedb. If you cannot eliminate all the conditions
causing errors, you can develop a workaround for those conditions, implement the
workaround when you encounter the error, and then resume updatedb processing.
18
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 5. Upgrade scenario road maps
Deployment scenario road maps are summaries consisting of product deployment
tasks.
The upgrade information provided with SmartCloud Control Desk 7.5 describes
several upgrade scenarios.
Scenario 1 focuses on using the middleware installation program to install a new
instance of WebSphere Application Server Network Deployment v7.0 on a different
system than the instance of WebSphere Application Server Network Deployment
v6.1 used in your prior deployment. You then use the SmartCloud Control Desk
7.5 installation program to automatically configure WebSphere Application Server
Network Deployment v7.0.
Scenario 2 describes manually installing a new instance of WebSphere Application
Server Network Deployment v7.0 on the same system as the instance of
WebSphere Application Server Network Deployment v6.1 used in your prior
deployment. You then migrate configuration information from WebSphere
Application Server Network Deployment v6.1 to WebSphere Application Server
Network Deployment v7.0.
Scenario 3 describes upgrading to SmartCloud Control Desk 7.5 by migrating
configuration information from WebSphere Application Server Network
Deployment v6.1 to WebSphere Application Server Network Deployment v7.0
using the middleware installation program.
Scenario 4 describes upgrading to SmartCloud Control Desk 7.5 on Oracle
WebLogic Server.
The following series of road maps provide procedural summaries of SmartCloud
Control Desk deployment scenarios. The steps contained in each deployment
scenario road map briefly describe the overall task and then provide links to more
detailed information about that task.
The deployment scenarios provided include the following situations:
Upgrading by installing and configuring WebSphere Application Server
Network Deployment v7.0 on a new server (Scenario 1)
You want to install WebSphere Application Server Network Deployment
v7.0 on a new system in order to preserve your existing WebSphere
Application Server Network Deployment v6.1 environment. You intend to
use SmartCloud Control Desk 7.5 installation programs and tools to install
and automatically configure a new installation of WebSphere Application
Server Network Deployment v7.0.
This scenario is useful if you want to preserve your prior deployment
while upgrading to SmartCloud Control Desk 7.5. In this scenario, you are
installing and configuring a new instance of WebSphere Application Server
Network Deployment v7.0. None of the WebSphere Application Server
Network Deployment v6.1 configuration information from your existing
deployment is reused. You are establishing WebSphere Application Server
Network Deployment v7.0 in your environment in the same manner you
would for a new SmartCloud Control Desk 7.5 installation.
© Copyright IBM Corp. 2012
19
Note: The middleware installation program used to install WebSphere
Application Server Network Deployment v7.0 does not support the HP-UX
and Oracle Solaris platforms. However, installable images for WebSphere
Application Server Network Deployment, DB2 and IBM Tivoli Directory
Server are provided with SmartCloud Control Desk. You can install this
software individually using information in the installation guide if you
want to deploy SmartCloud Control Desk using this middleware on those
platforms.
Upgrading by migrating WebSphere Application Server Network Deployment
v6.1 configuration information to WebSphere Application Server Network
Deployment v7.0 (Scenario 2)
You want to install WebSphere Application Server Network Deployment
v7.0 on the same server as WebSphere Application Server Network
Deployment v6.1 and migrate configuration information from WebSphere
Application Server Network Deployment v6.1 to WebSphere Application
Server Network Deployment v7.0.
This scenario applies when you want to move existing WebSphere
Application Server Network Deployment v6.1 configuration data from
your prior deployment to SmartCloud Control Desk 7.5. In this scenario,
WebSphere Application Server Network Deployment v6.1 was configured
manually for the SmartCloud Control Desk 7.5 deployment. The
middleware installation program was not used to install or configure
WebSphere Application Server Network Deployment v6.1. For this
scenario, you install WebSphere Application Server Network Deployment
v7.0 on the same system that is hosting WebSphere Application Server
Network Deployment v6.1. You then use the WebSphere Application Server
Network Deployment v7.0 migration tool to move configuration data from
WebSphere Application Server Network Deployment v6.1 to WebSphere
Application Server Network Deployment v7.0.
Note: When you migrate configuration information from WebSphere
Application Server Network Deployment v6.1 to WebSphere Application
Server Network Deployment v7.0, the configuration information is no
longer hosted on WebSphere Application Server Network Deployment
v6.1.
Upgrading by migrating WebSphere Application Server Network Deployment
v6.1 configuration information to WebSphere Application Server Network
Deployment v7.0 using the middleware installation program (Scenario 3)
You want to install WebSphere Application Server Network Deployment
v7.0 on the same server as WebSphere Application Server Network
Deployment v6.1 and migrate configuration information from WebSphere
Application Server Network Deployment v6.1 to WebSphere Application
Server Network Deployment v7.0.
This scenario applies when you want to move existing WebSphere
Application Server Network Deployment v6.1 configuration data from
your prior deployment to SmartCloud Control Desk 7.5. In this scenario,
WebSphere Application Server Network Deployment v6.1 was installed
and configured using the middleware installation program for the
SmartCloud Control Desk 7.5 deployment. Because the middleware
installation program was used to install and configure WebSphere
Application Server Network Deployment v6.1 for your prior deployment,
you can use the SmartCloud Control Desk 7.5 middleware installation
program to migrate existing data. For this scenario, you install WebSphere
Application Server Network Deployment v7.0 using the middleware
20
IBM SmartCloud Control Desk: Upgrade Guide
installation program on the same system that is hosting WebSphere
Application Server Network Deployment v6.1. You then use the
middleware installation program migration option to move configuration
data from WebSphere Application Server Network Deployment v6.1 to
WebSphere Application Server Network Deployment v7.0.
Note: When you migrate configuration information from WebSphere
Application Server Network Deployment v6.1 to WebSphere Application
Server Network Deployment v7.0, the configuration information is no
longer hosted on WebSphere Application Server Network Deployment
v6.1. ra
Upgrading on Oracle WebLogic Server (Scenario 4)
You want to upgrade SmartCloud Control Desk on Oracle WebLogic
Server.
This scenario focuses on upgrading in Oracle WebLogic Server
environments. You must consult Oracle WebLogic Server documentation
for application server migration information.
Chapter 5. Upgrade scenario road maps
21
22
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 6. Upgrading by installing WebSphere Application
Server Network Deployment v7.0 on a new server (Scenario 1)
Use this information to use product installation programs and tools to install and
automatically configure WebSphere Application Server Network Deployment v7.0
for SmartCloud Control Desk 7.5.
Before you begin
Any custom configuration that you performed on the WebSphere Application
Server Network Deployment v6.1 server for your prior deployment must be
performed again for WebSphere Application Server Network Deployment v7.0.
About this task
This information provides a high-level overview or road map of tasks you need to
complete in order to upgrade to SmartCloud Control Desk 7.5 with automatic
installation and configuration of WebSphere Application Server Network
Deployment v7.0.
In this scenario, you use the middleware installation program to install WebSphere
Application Server Network Deployment v7.0 and then use the SmartCloud
Control Desk 7.5 installation program to perform further automated configuration
tasks on that server. None of the WebSphere Application Server Network
Deployment v6.1 configuration information from your prior deployment is
reused. You are establishing WebSphere Application Server Network Deployment
v7.0 in your environment in the same manner you would for a new product
installation. WebSphere Application Server Network Deployment v7.0 must be
installed on a system that is different from the one hosting WebSphere Application
Server Network Deployment v6.1.
The benefit of using this upgrade scenario is that it provides automated installation
and configuration of WebSphere Application Server Network Deployment v7.0
while maintaining the existing WebSphere Application Server Network
Deployment v6.1 configuration for your prior deployment. During the upgrade
process, the database is upgraded to work with version 7.5. You cannot use the
upgraded database with your prior products. If you want to retain your previous
environment, you must upgrade a separate instance of your database.
Procedure
1. Perform pre-upgrade tasks.
2. Run the Integrity Checker from your existing environment in Report mode.
Tasks “Run Integrity Checker” on page 14
3. Establish supported middleware
The middleware installation program is used to install WebSphere Application
Server Network Deployment v7.0 and is configured automatically by the
SmartCloud Control Desk 7.5 installation program.
If necessary, upgrade your database software to a supported version using the
installation program for that software.
© Copyright IBM Corp. 2012
23
If necessary, upgrade your directory server software to a supported version
using the installation program for that software. Refer to the documentation
provided with your product for upgrade information.
Concepts
“Establish supported middleware” on page 25
“Installing and configuring WebSphere Application Server Network
Deployment v7.0 using the middleware installation program” on page
25
4. Optional: Migrate the database or directory server data, if necessary.
Tasks
Concepts
“Migrate database or directory server data (optional)” on page 32
5. Run the SmartCloud Control Desk 7.5 installation program.
In this step the SmartCloud Control Desk 7.5 installation program copies files
onto the administrative workstation and runs the configuration step, but
updatedb is deferred.
“Running the SmartCloud Control Desk 7.5 installation program with
automated configuration” on page 33
6. Migrate customizations from your prior deployment.
When you upgraded to SmartCloud Control Desk 7.5, data from your prior
deployment was preserved in a directory called pre_75_maximo, located in the
installation directory, which, by default, is C:\IBM\SMP. You must migrate your
customizations archived in the pre_75_maximo directory to the installation
directories of the current SmartCloud Control Desk 7.5 deployment.
Tasks
Tasks
“Migrate customizations” on page 40
7. Run the SmartCloud Control Desk 7.5 installation program to automate the
steps to upgrade the database.
The SmartCloud Control Desk 7.5 installation program is run a second time to
have it perform actions skipped the first time. For example, running updatedb
and running tdtoolkit.
Tasks
“Running the installation program to update the database” on page 41
8. Run SmartCloud Control Desk 7.5 Integrity Checker
Run the Integrity Checker tool in Report mode. If the Integrity Checker reports
an error, you must resolve it.
Tasks “Running Integrity Checker 7.5” on page 42
9. Perform post-upgrade tasks
Concepts
Chapter 11, “Post-upgrade tasks,” on page 97
Tasks
v
v
v
v
v
24
“Reviewing your upgraded screens” on page 103
“Reviewing table domains and crossover domains” on page 104
“Updating BIRT reports” on page 104
“Updating statistics” on page 105
“Uninstalling WebSphere Application Server Network Deployment
v6.1” on page 105
IBM SmartCloud Control Desk: Upgrade Guide
Establish supported middleware
Establish middleware in your environment that is compatible with SmartCloud
Control Desk 7.5.
The first step in a SmartCloud Control Desk 7.5 upgrade is to establish supported
middleware in your environment. In some cases, middleware you used in your
prior deployment, for example, database or directory server software , can be
reused for the SmartCloud Control Desk 7.5 upgrade. In other cases, you might
have to use new middleware servers that were not part of your prior deployment.
The middleware installation program is used to install WebSphere Application
Server Network Deployment v7.0, which is then configured automatically by the
SmartCloud Control Desk 7.5 installation program.
If necessary, upgrade database software to a version supported by SmartCloud
Control Desk 7.5. Upgrading the existing database software used with your prior
deployment is the preferred method of establishing a supported database. This
method allows you to reuse existing elements of your prior deployment, such as
user IDs and database instances. In some cases, you might be forced to install a
new instance of the database software. For example, your prior deployment might
include a database server that is established on a platform that is no longer
supported in SmartCloud Control Desk 7.5, as could be the case with 32-bit
platforms. In this scenario, you would install a fresh instance of the database
software compatible with SmartCloud Control Desk 7.5. For DB2, you could install
this software using the SmartCloud Control Desk 7.5 middleware installation
program. If you install new instances of database software outside the middleware
installation program, you would have to perform additional manual configuration
tasks that are described in the SmartCloud Control Desk 7.5 installation
information. In addition, you would have to migrate the database from the old
server to the new server.
If necessary, upgrade directory server software to a version supported by
SmartCloud Control Desk 7.5. Refer to the documentation provided with your
directory server product for upgrade information.
Installing and configuring WebSphere Application Server
Network Deployment v7.0 using the middleware installation
program
This procedure explains how to use the middleware installation program to create
a deployment plan that is responsible for installing and configuring WebSphere
Application Server Network Deployment v7.0.
Before you begin
These instructions are for the installation of WebSphere Application Server
Network Deployment v7.0 on a single system using the middleware installation
program.
In some cases, information about the middleware installation program screens is
not correctly displayed when installing through a remote session. If you do
encounter the problem, first minimize and then maximize the installation wizard to
redisplay the screen. To avoid such a problem, run the middleware installation
program locally on the system that is to host the middleware.
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
25
Do not use localhost for host name values in the installation program. Specify the
fully qualified host name or IP address of the system on which you are installing.
For Linux or UNIX systems, if the hostname -f command does not return a fully
qualified host name, consult the system documentation for assistance. For
Windows systems, to establish a fully qualified host name, complete the following
steps:
1. On the desktop, right-click My Computer.
2. Select Properties.
The System Properties panel is displayed.
3. From the Computer Name tab, click Change.
The Computer Name Changes panel is displayed.
4. Enter your fully qualified host name in the Computer name field, and then
click Enter.
Alternatively, you can provide the IP address for the system.
The DNS Suffix and NetBIOS Computer Name panel is displayed.
5. Verify that the Primary DNS suffix field displays a domain name, and then
click OK.
6. From the Computer Name Changes panel, click OK.
7. Click Apply and close the System Properties panel.
You can force the use of alphanumeric host name within the middleware
installation program by starting it from the command line and using the
forceHostname=true parameter. For example:
mwi -V forceHostname=true
When installing and configuring WebSphere Application Server Network
Deployment v7.0 in the middleware installation program and the SmartCloud
Control Desk installation program, consider the following special characters
restrictions:
Table 1. Middleware object naming conventions
Header
Header
WebSphere Application Server Network
Deployment
The administrator name cannot contain the
following characters: / \ * ,: ;=+?|< > & %
'"] [> # $ ~ ( ) !
The administrator name cannot begin with a
period.
The administrator name cannot contain
leading and trailing spaces.
The administrator password must consist of
eight characters.
26
IBM SmartCloud Control Desk: Upgrade Guide
Table 1. Middleware object naming conventions (continued)
Header
Header
Middleware installation program
The middleware installation program does
not validate that the password provided is
compliant with the operating system of the
target host. Ensure that the password values
you provide are valid for your environment.
You cannot use the '%' character on
Windows or !, $, #, % characters on UNIX.
The middleware installation program does
not check for accented characters in user
name values. The use of accented characters
can cause errors.
Do not include the underscore character (_)
when entering host names. Using this
character causes an error during middleware
installation.
If the middleware installation program reports that you have insufficient disk
space to install WebSphere Application Server Network Deployment v7.0, you
must increase the available disk space on the system. When disk space has been
increased, restart the middleware installation program.
Important: The middleware installation program does not account for the
temporary space needed on the application server host for the migration of
WebSphere Application Server Network Deployment data. An additional 700 Mb of
disk space is required on the workspace directory partition to ensure data
migration is successful.
When you run the middleware installation program, you are prompted for user
IDs to initiate the installation of WebSphere Application Server Network
Deployment v7.0. You can either supply an existing system user ID, or allow the
middleware installation program to create a user ID.
If you encounter the following error, it indicates that you are attempting to use the
64-bit middleware installation program (mwi-AMD64.exe) on a 32-bit Windows
system.
CreateProcess failed ==> The image file %1 is valid, but for a machine type
other than the current machine
The appropriate middleware installation program for 32-bit Windows systems is
mwi.exe. Alternatively, run the following command to automatically select the
appropriate program for the system:
setupwin.bat /l
About this task
To install WebSphere Application Server Network Deployment v7.0 for IBM
SmartCloud Control Desk 7.5 using the middleware installation program, follow
these steps.
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
27
Procedure
1. Log in to the target system as a user with administrative authority. If you are
running the middleware installation program from a Linux or UNIX terminal
window, you must be logged in as the root user.
2. Launch the middleware installation program from the launchpad.
a. Start the launchpad.
Windows
From the downloaded installation image, browse to the root
directory and run the following command: launchpad.exe.
Linux and UNIX
From the downloaded installation image, browse to the root
directory and run the following command: launchpad.sh.
When starting the middleware installation program from the launchpad,
installation program files are copied to a temporary directory on the
system. You can use the following setup scripts to start the middleware
installation program directly and prevent the installer from copying the
files to the system.
Windows
launchpad\Install\MWI\setupwin.bat /l
Linux and UNIX
launchpad\Install\MWI\setupUNIX.sh -l
The following errors can occur when using the setup scripts.
Table 2. Middleware installation program setup script error codes
Error
Code
Error
Description
11
Unsupported operating system
The middleware installation program
or one of the middleware products
cannot run on this operating system.
12
Unsupported Linux distribution
The middleware installation program
or one of the middleware products is
not supported on this Linux kernel.
Currently only Red Hat and SuSE are
supported.
13
Unsupported kernel bit mode
The middleware installation program is
supported on Linux 32/64 bit mode
and on AIX 64 bit mode.
14
Unsupported Processor architecture
The middleware installation program
or one of the middleware products is
not supported on this processor
architecture. Currently only x86 and
AMD64 architecture are supported.
21
Env variable
mwi_launchpadroot(UNIX) /
LaunchPadBatchPath(Win) is not set
The environment variable must be set
to the middleware installation program
install files location:
Windows
LaunchPadBatchPath
Linux and UNIX
mwi_launchpadroot
28
IBM SmartCloud Control Desk: Upgrade Guide
Table 2. Middleware installation program setup script error codes (continued)
Error
Code
Error
Description
22
The middleware installation program
file not found
The middleware installation program
install file is missing or not accessible.
Check to ensure that the specified file
exists in the current directory.
31
Host name is not a fully qualified
domain name.
The middleware installation program
or one of the middleware products
requires a fully qualified host name
defined.
Alternatively, you can provide the IP
address for the system.
32
SELinux is enabled or set in Enforcing
mode
Middleware product installation fails
with the following error:
JRE could not be found on the system
Disable SELinux using one of the
following methods:
v setenforce 0
v Add the following entry to the
/etc/system file:
set fmac_enforcing = 0
33
The library libstdc++.so.5 (64-bit) is
not installed.
The installer requires libstdc++.so.5
(64-bit), which is located in
/usr/lib64/libstdc++.so.5. If the
system does not have this library
installed, search for an RPM package
(64-bit) compatible with system that
contains this library and install it.
34
The library libstdc++.so.5 is not
installed.
The installer requires libstdc++.so.5,
which is located in
/usr/lib/libstdc++.so.5. If the system
does not have this library installed,
search for an RPM package compatible
with system that contains this library
and install it.
b. In the launchpad navigation pane, click Install the product.
c. From the IBM SmartCloud Control Desk 7.5 Installation panel, click
Middleware.
3. Select a language for the installation and click OK.
4. In the Welcome panel, click Next.
5. In the middleware installation program license agreement window, read the
license information, select I accept both the IBM and the non-IBM terms if
you agree with the terms, and then click Next.
6. In the Choose Workspace panel, specify the directory used as the middleware
installation program workspace, and then click Next. The default location for
the workspace is the last workspace location used by this user, as specified in
the middleware user preferences node. If no previous workspace location
exists in the middleware user preferences node, then the default location for
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
29
the workspace is C:\ibm\tivoli\mwi\workspace for Windows,
/root/ibm/tivoli/mwi/workspace for Linux, and /ibm/tivoli/mwi/workspace
for AIX®.
If the selected directory does not exist, it is created.
After deployment, the middleware installation program also generates a
topology file in this directory. This topology file can be manually copied by
the user to the workspace of the next system in the topology. Information
about the deployment of middleware is available to the middleware
installation program when it is used on the next system.
7. In the Install IBM Autonomic Deployment Engine panel, click Next to install
the IBM Autonomic Deployment Engine.
8. In the Deployment Choices panel, select J2EE Server, and then click Next.
9. In the Deployment Plan Summary window, click Next to configure the
parameters displayed. The deployment plan is generated and you are
provided details about the plan.
10. In the Configurable Host Name panel, if you want to manually specify the
host name of the system you are running the installation from, select the
Override the local machine hostname option and enter a host name value in
the Hostname field, and then click Next. Select this option only if you want to
manually specify the host name of the system instead of having the
installation program programmatically detect it. This option is useful when
there is more than a single host name assigned to the system. This situation is
present when a system has more than one network interface, or it is
configured to support virtual IP addresses. When this option is selected, you
are required to provide a resolvable host name. You cannot clear this option
after it has been selected, however, you are able to change the value of the
Hostname field. If you launched the middleware installation program from
the command line using the forceHostname=true parameter, then you are
required to provide an alphanumeric value in the Hostname field. An IP
address results in an error message.
11. In the password reuse panel, you can optionally select Use this password as
the value for all subsequent passwords. You then enter a password value and
then click Next. This option allows you to use the same password as the
default user password value in all panels of the middleware installation
program. If you do not want to use this option, ignore the Use this password
as the value for all subsequent passwords option, and click Next.
12. Enter the following configuration parameters for WebSphere Application
Server Network Deployment, and then click Next.
Install location
Enter the location to install WebSphere Application Server Network
Deployment.
Windows:
Default is C:\Program Files\IBM\WebSphere\AppServer
Linux: Default is /opt/IBM/WebSphere/AppServer
AIX:
Default is /usr/IBM/WebSphere/AppServer
WebSphere Administration username
Enter the WebSphere Application Server Network Deployment
administrative account name.
Default for all platforms is wasadmin.
30
IBM SmartCloud Control Desk: Upgrade Guide
WebSphere Administration password
Enter the password for the WebSphere Application Server Network
Deployment administrative account.
13. Enter the following configuration parameters for WebSphere Application
Server Network Deployment, and then click Next.
Deployment Manager profile name
Enter the WebSphere Application Server Network Deployment profile
name of the deployment manager server.
Default for all platforms is ctgDmgr01.
Application server profile name
Enter the WebSphere Application Server Network Deployment profile
name of the application server.
Default for all platforms is ctgAppSrv01.
14. Enter the following configuration parameters for WebSphere Application
Server Network Deployment, and then click Next.
Cell name
Enter the WebSphere Application Server Network Deployment Cell
name.
Default for all platforms is ctgCell01.
Deployment Manager node name
Enter the name of the WebSphere Application Server Network
Deployment deployment manager node.
Default for all platforms is ctgCellManager01.
Application server node name
Enter the name of the WebSphere Application Server Network
Deployment node.
Default for all platforms is ctgNode01.
Update Installer install location
Enter the location where the WebSphere Application Server Network
Deployment update installer is installed.
Windows:
Default is C:\Program Files\IBM\WebSphere\UpdateInstaller
Linux: Default is /opt/IBM/WebSphere/UpdateInstaller
AIX:
Default is /usr/IBM/WebSphere/UpdateInstaller
15. Enter the following configuration parameters for IBM HTTP Server, and then
click Next.
Install location
Enter the location to install IBM HTTP Server.
Windows:
Default is C:\Program Files\IBM\HTTPServer.
You cannot start and stop IBM HTTP Server from the
administrative console if you install it into a directory path
that includes spaces. For example, Program Files. You must
start and stop the IBM HTTP Server from the command line.
Linux: Default is /opt/IBM/HTTPServer
AIX:
Default is /usr/IBM/HTTPServer
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
31
HTTP port
Enter the port used by the IBM HTTP Server.
Default for all platforms is 80.
Admin Server port
Enter the port to use to administer IBM HTTP Server.
Default for all platforms is 8008.
16. In the Configuration Parameters for WebSphere Application Server Network
Deployment plug-in for the IBM HTTP Server, the default profile name is
ctgAppSvr01. You cannot change this value. To accept the value, click Next.
17. Specify the location of the SmartCloud Control Desk middleware images, and
then click Next.
Copy the middleware install images from the source media to a specified
directory
Select this option to copy the middleware images from the product
media to a specified directory.
18.
19.
20.
21.
Specify a directory containing all the required middleware install images
Select this option if you intend to specify a file system directory that
already contains the middleware installation images.
If you selected the option to copy installation images from the source media,
specify the source and destination directories, and then click Next. If you
selected the option to specify a directory that already contained the
middleware images, specify that directory, and then click Next. There is an
option for checksum validation for the middleware images. Select this option
if you want to confirm the integrity of the images before deploying the
middleware. If the checksum operation fails, click Back and recopy the
images before proceeding. If you do not select this option and the middleware
images are corrupted or otherwise inaccessible from the directory specified, an
error occurs. If you encounter this error, you must replace the corrupted
middleware image and then restart the middleware installation program.
Specify a directory to use for middleware installation program temporary files
and extracted middleware installation images, and then click Next.
In the Deployment Plan Operation panel, select Deploy the plan, and then
click Next. You can also elect to change the deployment plan or parameters
you have previously configured from this panel.
In the Deployment Plan and Parameter Configuration summary panel, review
the contents of the summary. Click Deploy to initiate the installation and
configuration of the middleware you selected.
22. After the deployment completes successfully, click Finish to exit.
Migrate database or directory server data (optional)
Depending upon your environment, you might have to migrate database or
directory server data from the middleware servers used in your prior deployment
to new middleware servers.
If the middleware you used in your prior deployment is incompatible with
SmartCloud Control Desk 7.5, you can migrate data to a new server supported by
SmartCloud Control Desk 7.5.
If your existing database software is compatible with SmartCloud Control Desk 7.5,
you can use the existing database. If the existing database is not compatible, refer
to the documentation provided with your software for instructions on migrating
32
IBM SmartCloud Control Desk: Upgrade Guide
database objects. For DB2, this information can be found at http://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/
com.ibm.db2.luw.qb.upgrade.doc/doc/c0011933.html. Recall that if you performed
an upgrade of your database software, you are only required to migrate the
existing database instance (ctginst1) and database (maxdb71). If you installed a
new instance of the database software, you must complete additional configuration
tasks as described in the SmartCloud Control Desk 7.5 installation
information. Additional tasks include creating system users, creating a new
database instance, and modifying the maximo.properties file to update information
for the new server.
If you chose to use a directory server for security in your prior deployment and
you are required to migrate directory server information to comply with
SmartCloud Control Desk 7.5 prerequisites, consult the documentation provided
with your software for instructions on migrating. If you used IBM Tivoli Directory
Server in your prior deployment, no migration is required because the same
version of IBM Tivoli Directory Server is supported.
Running the SmartCloud Control Desk 7.5 installation program with
automated configuration
Upgrade to SmartCloud Control Desk 7.5 and automatically configure WebSphere
Application Server Network Deployment v7.0
About this task
In order to upgrade your prior deployment to SmartCloud Control Desk 7.5, run
the SmartCloud Control Desk 7.5 installation program on the original
administrative workstation. The installation program detects the existing
deployment and guides you through the upgrade process.
If you encounter any errors related to the installation program during the upgrade,
refer to the installation information for troubleshooting details.
Before the upgrade, ensure that all existing process managers are at the expected
level. Open a command prompt and issue the following command:
Install_Home\bin\solutioninstaller -action showinstalled -type all
The choices you made in the previous deployment affect which panels you
encounter during the upgrade. If WebSphere Application Server Network
Deployment credentials used for the previous deployment have changed since the
initial deployment, you are prompted to provide them during upgrade. If the
credentials remain the same, the upgrade process uses the values recorded during
the original deployment. You are not prompted to provide these values.
Procedure
1. Stop the MXServer application server or servers of your prior deployment.
2. Log in to the administrative workstation using the administrative user ID
used in the previous deployment.
3. Start the SmartCloud Control Desk installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
33
b. In the launchpad navigation pane, click Install The Product.
c. Click Install IBM SmartCloud Control Desk 7.5.
Alternatively, you can start the SmartCloud Control Desk installation program
directly. Browse to the \Install\product_abbreviation\ directory of the
downloaded installation image and run the following command
Windows
v install.bat
v install_win64.bat
4. Select a language for the installation and click OK.
5. In the Introduction panel, click Next.
6. In the Choose Installation folder panel, enter the install location of your prior
deployment to target it for an upgrade.
7. Review the information presented in the Verify installation location panel, and
then click Next. The Verify installation location panel reports previous
installation information that was found based upon the installation directory
you chose in the previous panel. Once you advance past this panel, you
cannot go back and change the installation directory for this installation.When
you click Next, the installation program performs some pre-installation
processing to ensure that the Deployment Engine is ready to run the upgrade.
A progress bar for this activity is displayed.
8. In the Package Summary panel, review the package deployment actions, and
then click Next. This panel lists version information for both new and existing
packages on the system. Target package version information indicates the
package version being currently deployed.
Note: If you had optional content installed with any of the prior products, the
package analysis shows that the current level of the content packages does not
support the level of process automation engine being installed. In this case
you must install the optional content package from the launchpad before you
update the database. A check box is displayed below the table, with a
statement saying that you understand that you must apply additional
updates. Check this box and click Next.
9. The SmartCloud Control Desk program license agreement window is
displayed. Read the license information and select I accept the terms in the
license agreement. if you agree with the terms. Click Next.
10. In the Database Upgrade panel, review the prerequisite database task
information. Select the option indicating that you have performed the
prerequisite database tasks, and then click Next.
11. In the Import Middleware Configuration Information panel, indicate that you
want to use the field values that you used with the middleware installation
program for WebSphere Application Server Network Deployment. These
values are used as default values for those same fields in the SmartCloud
Control Desk installation program. Click Next.
Import middleware configuration information
Select this check box to allow the SmartCloud Control Desk
installation program to reuse values specified in the middleware
installation program.
If you select the Simple deployment path, the middleware default
information is not used.
34
IBM SmartCloud Control Desk: Upgrade Guide
Host name
Enter the host name of the system where the middleware installation
program was run.
User ID
Enter the user ID that was used to run the middleware installation
program.
Password
Enter the password of the user ID that was used to run the
middleware installation program.
Workspace location
Enter the location of the topology file that contains the values entered
for the middleware installation program. This file is found in the
workspace that was defined during the middleware installation task.
For example, C:\ibm\tivoli\mwi\workspace for Windows and
/root/ibm/tivoli/mwi/workspace for UNIX.
12. In the Automate WebSphere Configuration panel, choose the option to
automate WebSphere Application Server Network Deployment configuration,
and then click Next.
13. In the WebSphere Connectivity panel, enter host information about the
WebSphere Application Server Network Deployment, and then click Next.
Host name
Enter the fully qualified host name of the system hosting WebSphere
Application Server Network Deployment.
Alternatively, you can provide the IP address for the system.
SOAP port
Enter the SOAP port of the WebSphere Application Server Network
Deployment system.
The default value for this field is 8879.
User ID
Enter the administrative user ID used to access the WebSphere
Application Server Network Deployment Server.
Default for all platforms is wasadmin.
Password
Enter the password for the administrative user ID used to access the
WebSphere Application Server Network Deployment Server.
In IP v6 environments, you are also prompted to provide the RMI bootstrap
port.
14. In the WebSphere Remote Access Authorization panel, enter authorization
information for WebSphere Application Server Network Deployment
configuration, and then click Next.
Operating system user ID
Enter a valid user ID that allows the SmartCloud Control Desk
installation program to access the system that is hosting WebSphere
Application Server Network Deployment.
This user ID must have administrative rights on the server you are
accessing.
Operating system password
Enter the password for the system user ID.
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
35
WebSphere installation directory
Enter the directory where WebSphere Application Server Network
Deployment is installed on the host system.
Windows
On Windows, this value might be C:\Program
Files\IBM\WebSphere\AppServer
Linux On Linux or UNIX, this value might be /opt/IBM/WebSphere/
AppServer
AIX
On AIX, this value might be /usr/IBM/WebSphere/AppServer
Profile name
Enter the name of the WebSphere Application Server Network
Deployment profile.
Default for all platforms is ctgDmgr01.
15. In the WebSphere Application Server Network Deployment Configuration
panel, enter the following information, and then click Next.
Web server port
Enter the web server port used by WebSphere Application Server
Network Deployment.
Default for all platforms is 80.
This value should match an existing HTTP server port value you
configured when you set up WebSphere Application Server Network
Deployment. If you enter a different value for this port, you must
restart WebSphere Application Server Network Deployment at the
conclusion of the installation. Restarting the server activates the new
port, making it available for incoming requests.
Web server name
Enter the name of the web server.
Default for all platforms is webserver1.
Node name
Enter the name of the WebSphere Application Server Network
Deployment node containing the application server.
Default for all platforms is ctgNode01.
Application server
Enter the name of the WebSphere Application Server Network
Deployment application server to associate with SmartCloud Control
Desk.
Default for all platforms is MXServer. This value can be customized.
The application server is created if it does not exist.
16. In the Integration Adapter JMS Configuration panel, enter the following
information, and then click Next. A JMS server requires a DB2 data repository
to be configured to maintain messages. If you are using another database
type, you cannot have the installation program configure message persistence.
JMS Data Source name
Enter the name of the database to be used by JMS.
If you are using Microsoft SQL Server, this field is pre-populated. If it
is not, enter intjmsds.
36
IBM SmartCloud Control Desk: Upgrade Guide
Select whether the JMS data store should be persisted.
Persist JMS messages
Select this option to enable the SmartCloud Control Desk
installation program to set the JMS implementation to persist
messages within DB2.
Do not persist JMS messages
If you select this option, the SmartCloud Control Desk
installation program does not set the JMS implementation to
persist messages automatically in DB2. You can configure the
JMS implementation manually at a later date. If you select this
option, when you click Next, the installation wizard skips to
to the panel to configure SMTP.
Select this option if you are deploying SmartCloud Control
Desk with Oracle or Microsoft SQL Server.
17. If you chose to persist JMS messages, in the DB2 Database Server
Configuration panel, enter the following information, and then click Next. If
you chose not to persist JMS messages you do not see this panel.
Note: The JMS data store can only be created as a DB2 database.
Host name
Enter the fully qualified host name of the server hosting the JMS data
store.
Alternatively, you can provide the IP address for the system.
Port
Enter the port used to access the database server.
Default for all platforms is 50005.
Database name
Enter the name of the database serving as the JMS data store.
Default for all platforms is maxsibdb.
User ID
Enter the user ID used to access the database server.
Default for all platforms is maximo.
Password
Enter the password for the user ID used to access the database server.
18. If you chose to persist JMS messages, in the DB2 Database Server Remote
Access Authorization panel, enter authorization information for the automatic
configuration feature, and then click Next. If you chose not to persist JMS
messages you do not see this panel.
User ID
Enter a valid user ID that allows the SmartCloud Control Desk
installation program to access the system that is hosting the JMS
database.
This user ID must have administrative rights on the server you are
accessing.
For Windows, this user must be a member of the DB2ADMNS group.
For Linux or UNIX, this user must be root and a member of a group
with SYSADM authority for the database instance.
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
37
Password
Enter the password for the user ID.
19. If you chose to persist JMS messages, in the DB2 Database Instance
Configuration panel, enter the following information, and then click Next. If
you chose not to persist JMS messages you do not see this panel.
Installation directory
Enter the installation directory for the DB2 server that is hosting the
JMS database that contains the instance to be used with WebSphere
Application Server Network Deployment.
Windows
This value might be C:\Program Files\IBM\SQLLIB
Linux or UNIX
This value might be /opt/IBM/db2/V9.7
Instance
Enter the JMS database instance to be used with WebSphere
Application Server Network Deployment.
For all platforms, the default is ctginst1
Instance administrator user ID
Enter the user ID of the administrator for the JMS database instance.
Windows
This value might be db2admin.
Linux or UNIX
This value might be ctginst1.
Instance administrator password
Enter the password for the user ID of the administrator for the JMS
database instance.
20. On the Data Integration Services and Context Menu Service Deployment
Options panel, specify a deployment option. If you deployed a separate
database for Data Integration Services and Context Menu Service in your prior
deployment, select Configure data integration and context menu services for
this product using a previously deployed data integration and context menu
service instance to use that previously deployed database. Otherwise, select
Deploy data integration and context menu services into the same database
that you created for the product to use the SmartCloud Control Desk
database for the Data Integration Services and Context Menu Service. The
Data Integration Services and Context Menu Service allow products to register
themselves to offer launch in context to all other registered products and to
gain launch access to all other registered products. This ability is provided
without unique product-to-product integration efforts. Refer to the product
information center for more information about configuring cross-product
launch points.
21. If you have not previously configured the following parameters for your prior
deployment, you are prompted to supply SMTP configuration information. In
the SMTP Configuration panel, specify SMTP configuration information used
by workflows to communicate with workflow participants.
SMTP server
Enter the fully qualified host name of the SMTP server that sends
messages to participants.
Alternatively, you can provide the IP address for the system.
38
IBM SmartCloud Control Desk: Upgrade Guide
Administrator e-mail
Enter a valid e-mail address. This address is used to send messages.
You can defer SMTP configuration at this time by not providing any
information and clicking through to the next panel. However, you must
configure these parameters through the product interface as a post installation
task.
22. On the Run Configuration Step panel, if check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes. If you leave these check boxes cleared, the
installer will perform these steps before your system is ready. If you are
performing a test upgrade in an environment that did not have optional
content installed with your prior products, and you do not care about
minimizing the maintenance window, you can leave these boxes cleared.
However, doing so will prevent you from measuring the time needed for
updating the database and other maintenance-window activities.
23. From the input summary panel, verify that the values displayed are the ones
used in your existing SmartCloud Control Desk deployment, and then click
Next.
24. From the Pre-Installation Summary panel, review the install summary values,
and then click Install.
The upgrade process begins copying files to your local system.
25. Click Finish to exit the installation program.
Installing optional content and integration modules
You might want to add optional content to your environment, or integrate with
other products.
About this task
Optional content is often used in development environments as a way to begin
developing your own content. The Reference section of the product information
center contains a detailed description of the optional content that you can install
from the product launchpad. If you do not install optional content during the
product upgrade process, you can install it later. If you install it later, you must
update the database and rebuild and deploy the maximo.ear file.
If you had optional content installed in your prior deployment, you must install
the new optional content to replace it. The database cannot be updated if it
contains content from prior releases.
You can install integration modules to help you integrate SmartCloud Control Desk
applications with other products. If you do not install integration modules during
the product upgrade process, you can install them later. If you install them later,
you must update the database and rebuild and deploy the maximo.ear file.
Procedure
1. Restart the launchpad.
2. To install optional content, use the link in the navigation area to open the
Optional Content page of the launchpad.
3. Click the link to install optional content. The product installer is launched.
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
39
4. Follow the screens through the installer. If check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes.
5. Click Finish to exit the installation program.
6. To install optional integrations, restart the launchpad. Use the link in the
navigation area to open the Integrations page of the launchpad.
7. Click the link for each integration that you want to install. The product installer
is launched.
8. Follow the screens through the installer. If check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes.
9. Click Finish to exit the installation program.
Migrate customizations
Customizations you made in your prior deployment are not migrated
automatically to your new environment.
About this task
When you installed SmartCloud Control Desk 7.5, your prior deployment was
preserved in a directory called pre_75_maximo, located in the C:\IBM\SMP
directory. You must migrate your customizations archived in the pre_75_maximo
directory to the installation directories of the current SmartCloud Control Desk 7.5
deployment.
Procedure
1. Compile custom Java code using the JDK 1.6 compiler. Custom Java classes that
were created for your prior deployment were likely compiled using JDK 1.5,
which was provided with previous product versions. Custom Java code must
be recompiled using the JDK 1.6 compiler supplied with SmartCloud Control
Desk 7.5 in the C:\IBM\SMP\sdk\bin folder, or any supported 1.6 JDK.
a. Locate custom Java source files in subdirectories of the pre_75_maximo
archive directory.
b. Compile source into Java class files using JDK 1.6.
c. Move recompiled class files into the appropriate SmartCloud Control Desk
7.5 directory. Typically this is the same directory under SmartCloud Control
Desk 7.5 as it was in your prior deployment.
2. Identify customizations that were made to default JSP, XML, HTML, CSS or
XSLT files in your prior deployment. These customizations of default files must
be recreated in the SmartCloud Control Desk 7.5 versions of these files. You can
find the customized files in the pre_75_maximo archive directory. You cannot
overwrite SmartCloud Control Desk 7.5 files with modified versions of default
files from your prior deployment found in the pre_75_maximo directory.
Customizations must be reapplied to the SmartCloud Control Desk 7.5 versions
of these default files.
3. Copy or move any custom JSP, XML, HTML, CSS or XSLT files you created to
work with your prior deployment.
4. For any changes made to Applet extensions, move the compiled code into the
appropriate folders on the SmartCloud Control Desk 7.5 installation directory.
Ensure that you build the Applet Jars from the SmartCloud Control Desk 7.5
folders.
40
IBM SmartCloud Control Desk: Upgrade Guide
5. Copy or move any customized report files from the pre_75_maximo directory
structure to the appropriate SmartCloud Control Desk 7.5 folder. These report
files need to be imported into the database after the upgrade process is
complete, as describe in the post-upgrade information.
6. Move any custom configuration files (.properties and .xml) that contain
extensions defined for SmartCloud Control Desk 7.5. Product XML files can be
found in the \maximo\applications\maximo\properties\product folder. If
customizations were made to default configuration files in your prior
deployment, you must replicate those changes in the SmartCloud Control Desk
7.5 versions of those files.
7. Copy or move the webclient.properties file from the pre_75_maximo directory
structure to the \maximo\applications\maximo\properties\product folder of the
SmartCloud Control Desk 7.5 installation.
8. Copy or move any third-party libraries used with the previous release from the
pre_75_maximo directory structure to the appropriate SmartCloud Control Desk
7.5 folder. Consult the information provided with your third-party libraries to
verify that no further configuration tasks are required.
Running the installation program to update the database
Run the installation program a final time to update the database and perform final
deployment steps.
About this task
The SmartCloud Control Desk 7.5 installation program is run a final time to have it
perform actions skipped on previous invocations. These actions can include
running updatedb, running TDToolkit, and building and deploying EAR files. The
installer will not repeat steps that you have already run.
Procedure
1. Start the SmartCloud Control Desk installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
b. In the launchpad navigation pane, click Install The Product.
c. Click Install IBM SmartCloud Control Desk 7.5.
Alternatively, you can start the SmartCloud Control Desk installation program
directly. Browse to the \Install\product_abbreviation\ directory of the
downloaded installation image and run the following command
Windows
v install.exe
v install_win64.exe
2. Select a language for the installation and click OK.
3. In the Introduction panel, click Next.
4. In the Choose Installation folder panel, use the drop-down menu to choose
the folder where you have begun the upgrade.
5. Review the information presented in the Verify installation location panel, and
then click Next.
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
41
6. In the Package Summary panel, review the package deployment actions, and
then click Next.
7. From the Run Configuration Step panel, clear the check boxes for all options,
and then click Next. If you allow the installation program to perform these
steps, you do not have to complete them manually. If you prefer to deploy
the EAR files to your J2EE server manually after the installer has created
them, check the box for "Deploy application files manually later."
8. From the input summary panel, verify that the values displayed are the ones
used in your existing SmartCloud Control Desk deployment, and then click
Next.
9. From the Pre-Installation Summary panel, review the install summary values,
and then click Install. The installation program performs the following tasks
that remain for the upgrade:
v Run updatedb. This commits data for SmartCloud Control Desk 7.5, and
any other products or add-ons that you have upgraded, to the Maximo
database.
v Run TDToolkit to load languages for SmartCloud Control Desk 7.5.
v Build application EAR files.
v Deploy application EAR files.
10. Click Finish to exit the installation program.
Running Integrity Checker 7.5
After upgrading your database, run the Integrity Checker utility to drive out
additional errors.
About this task
Before proceeding further with the upgrade process, run the 7.5 version of the
Integrity Checker utility to confirm the integrity of the SmartCloud Control Desk
7.5 database after the upgrade steps have been completed. When run in Report
mode, the Integrity Checker utility checks the current database and reports on
common errors. If the Integrity Checker reports an error, you must resolve it by
running the Integrity Checker in Repair mode.
The 7.5 version of the Integrity Checker utility is more thorough than the version
that was provided with earlier product releases. It will identify potential database
issues that were not detected by earlier versions of the tool. Therefore you should
expect that it might identify issues with your upgraded database that were not
detected before you upgraded. Fixing these issues will help your upgraded system
run more smoothly than it would have without fixing the issues. Be sure to include
this step when you rehearse your upgrade, so that you will know what to expect
when you run it during your production upgrade. You can have the fixes ready to
implement quickly, and anticipate the time required to implement them during
your production maintenance window.
Procedure
1. Stop the application server. For example, MXServer.
2. From the administrative workstation of the existing deployment, open a
command prompt and change directory to the maximo tools directory. For
example, c:\ibm\SMP\maximo\tools\maximo
3. Start the Integrity Checker tool.
integrityui.bat
42
IBM SmartCloud Control Desk: Upgrade Guide
4. Select the Check Integrity tab.
5. Run the Integrity Checker in Report mode.
a. Ensure that the Repair Mode? check box is cleared, and then click Run
Integrity Checker.
b. When the report dialog box appears, click OK.
Results are found in the install dir\maximo\tools\maximo\log directory in the
file defined in the Log File Name field of the Check Integrity panel.
6. Optional: If any errors are reported, run the Integrity Checker in Repair mode.
a. Select the Repair Mode? check box, and then click Run Integrity Checker.
b. When the report dialog box appears, click OK.
7. Optional: If you ran the Integrity Checker in Repair mode, check the log file to
ensure all reported items have been repaired. If further manual intervention is
required, you must resolve the errors and then re-run the Integrity Checker in
Report mode. Repeat the process until no more errors are reported.
Results
Review error messages reported by the Integrity Checker in “Integrity checker
error messages,” on page 123. While the Integrity Checker can repair many issues,
you might have to resolve some errors manually by consulting the log files.
Chapter 6. Upgrading by installing WebSphere Application Server Network Deployment v7.0 on a new server (Scenario 1)
43
44
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 7. Upgrading by migrating WebSphere v6.1
configuration information (Scenario 2)
Use this information to migrate configuration information from your existing
WebSphere Application Server Network Deployment v6.1 installation to a new
installation of WebSphere Application Server Network Deployment v7.0.
About this task
This information provides a high-level overview or road map of tasks you need to
complete in order to upgrade to SmartCloud Control Desk 7.5 by migrating the
configuration of WebSphere Application Server Network Deployment v6.1 used in
your prior deployment to WebSphere Application Server Network Deployment
v7.0.
In this scenario, you use the WebSphere Application Server Network Deployment
v7.0 migration wizard to transfer existing product configuration information from
WebSphere Application Server Network Deployment v6.1 to WebSphere
Application Server Network Deployment v7.0. WebSphere Application Server
Network Deployment v7.0 must be installed on the same system as the one
hosting WebSphere Application Server Network Deployment v6.1
This scenario assumes you also have customizations that you want to migrate to
SmartCloud Control Desk 7.5.
The benefit of using this upgrade scenario is that you do not have to configure
WebSphere Application Server Network Deployment v7.0. You reuse the
configuration you performed for WebSphere Application Server Network
Deployment v6.1.
Procedure
1. Perform pre-upgrade tasks
2. Run the Integrity Checker from your existing environment in Report mode.
Tasks “Run Integrity Checker” on page 14
3. Establish supported middleware
If necessary, upgrade your database software to a supported version using the
installation program for that software.
If necessary, upgrade your directory server software to a supported version
using the installation program for that software. Refer to the documentation
provided with your product for upgrade information.
Concepts
“Establish supported middleware” on page 47
4. Install WebSphere Application Server Network Deployment v7.0 and migrate
configuration information. You install WebSphere Application Server Network
Deployment v7.0 using its native installation program. You do not use the
middleware installation program to install WebSphere Application Server
Network Deployment v7.0 because it creates profile information as it installs
WebSphere Application Server Network Deployment v7.0. You intend to
migrate existing WebSphere Application Server Network Deployment v6.1
© Copyright IBM Corp. 2012
45
profile information created for your prior deployment to WebSphere
Application Server Network Deployment v7.0.
Tasks
v “Installing WebSphere Application Server Network Deployment” on
page 47
v “Migrating IBM WebSphere Application Server Network
Deployment configuration information” on page 48
v “Installing the WebSphere update installer” on page 50
v “Installing and configuring IBM HTTP Server” on page 51
v “Installing IBM HTTP Server fix packs” on page 53
v “Installing the WebSphere plug-in” on page 54
v “Installing WebSphere Application Server Network Deployment
plug-in fix packs” on page 55
5. Optional: Migrate the database or directory server data, if necessary.
Concepts
“Migrate database or directory server data (optional)” on page 32
6. Run the SmartCloud Control Desk 7.5 installation program.
In this step the SmartCloud Control Desk 7.5 installation program copies files
onto the administrative workstation and runs the configuration step, but
updatedb is deferred.
Tasks
“Running the SmartCloud Control Desk 7.5 installation program with
manual configuration” on page 56
7. Migrate customizations from your prior deployment.
When you upgraded to SmartCloud Control Desk 7.5, data from your prior
deployment was preserved in a directory called pre_75_maximo, located in the
installation directory, which, by default, is C:\IBM\SMP. You must migrate your
customizations archived in the pre_75_maximo directory to the installation
directories of the current SmartCloud Control Desk 7.5 deployment.
Tasks “Migrate customizations” on page 40
8. Run the SmartCloud Control Desk 7.5 installation program to automate the
steps to upgrade the database.
The SmartCloud Control Desk 7.5 installation program is run a second time to
have it perform actions skipped the first time. For example, running updatedb
and running tdtoolkit.
Tasks “Running the installation program to update the database” on page 41
9. Run SmartCloud Control Desk 7.5 Integrity Checker
Run the Integrity Checker tool in Report mode. If the Integrity Checker
reports an error, you must resolve it.
Tasks “Run integrity checker 7.5” on page 63
10. Perform post-installation tasks
Concepts
Chapter 11, “Post-upgrade tasks,” on page 97
Tasks
v
v
v
v
46
“Reviewing your upgraded screens” on page 103
“Reviewing table domains and crossover domains” on page 104
“Updating BIRT reports” on page 104
“Updating statistics” on page 105
IBM SmartCloud Control Desk: Upgrade Guide
v “Uninstalling WebSphere Application Server Network Deployment
v6.1” on page 105
Establish supported middleware
Establish middleware in your environment that is compatible with SmartCloud
Control Desk 7.5.
The first step in the upgrade process is to establish middleware in your
environment that is supported by SmartCloud Control Desk 7.5. In some cases,
middleware you used in your prior deployment can be reused for the SmartCloud
Control Desk 7.5 upgrade. In other cases, you might have to use new middleware
servers that were not part of your prior deployment.
You install WebSphere Application Server Network Deployment v7.0 using its
native installation program on the same system as WebSphere Application Server
Network Deployment v6.1 and then migrate configuration information from your
prior deployment.
If necessary, upgrade database software to a version supported by SmartCloud
Control Desk 7.5. Upgrading the existing database software used with your prior
deployment is the preferred method of establishing a supported database. This
method allows you to reuse existing elements of your prior deployment, such as
user IDs and database instances. In some cases, you might be forced to install a
new instance of the database software. For example, your prior deployment might
include a database server that is established on a platform that is no longer
supported in SmartCloud Control Desk 7.5, as could be the case with 32-bit
platforms. In this scenario, you would install a fresh instance of the database
software compatible with SmartCloud Control Desk 7.5. For DB2, you could install
this software using the SmartCloud Control Desk 7.5 middleware installation
program. If you install new instances of database software outside of the
middleware installation program, you would have to perform additional manual
configuration tasks that are described in the SmartCloud Control Desk 7.5
installation information. In addition, you would have to migrate the database from
the old server to the new server.
If necessary, upgrade directory server software to a version supported by
SmartCloud Control Desk 7.5. Refer to the documentation provided with your
product for upgrade information.
Installing WebSphere Application Server Network Deployment
WebSphere Application Server Network Deployment v7.0 must be installed
manually in order to migrate profile information from WebSphere Application
Server Network Deployment v6.1.
Procedure
1. Log in to the system hosting WebSphere Application Server Network
Deployment v6.1 using a user ID with administrative permissions.
2. Stop WebSphere Application Server v6.1 services, if they are running.
a. Stop IBM HTTP Server and webserver1.
b. Stop WebSphere Application Server deployment manager.
c. Stop node.
d. Stop all Maximo application servers. For example, MXServer.
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
47
3. Copy the WebSphere Application Server Network Deployment v7.0
compressed installable image file from the downloaded product media to the
system. The file is in the WS-WAS_ND_7.0_Custom_FP15 directory.
Unpack the compressed file:
Remove the compressed files.
Change to the directory where you unpacked the file.
Start the installation program (install.[exe|sh]).
Proceed through the initial panels, accepting the license agreement. Accept
defaults provided unless you have a specific reason to change them.
9. On the Installation directory panel, specify an installation directory that does
not conflict with the installation directory of WebSphere Application Server
Network Deployment v6.1.
If you change the installation directory, do not use symbolic links as the
destination directory and do not add space characters to the path.
10. From the WebSphere Application Server Network Deployment environments
panel, select None as your environment, and then click Next. Profiles are
migrated from WebSphere Application Server Network Deployment v6.1
during a later step of the SmartCloud Control Desk7.5 process.
11. Click Yes to indicate that you want to proceed.
4.
5.
6.
7.
8.
12. Advance to the end of the installation and click Finish.
Migrating IBM WebSphere Application Server Network
Deployment configuration information
Use the IBM WebSphere Application Server Network Deployment v7.0 migration
wizard to migrate profiles from IBM WebSphere Application Server Network
Deployment v6.1 to IBM WebSphere Application Server Network Deployment v7.0.
About this task
You can transfer existing profile information used with SmartCloud Control Desk
7.2.1 instead of creating new profiles for SmartCloud Control Desk 7.5. You must
have installed IBM WebSphere Application Server Network Deployment v7.0 on
the same system as the IBM WebSphere Application Server Network Deployment
v6.1 server that was used for SmartCloud Control Desk 7.2.1.
Note: Migrating profiles used with SmartCloud Control Desk 7.2.1 disables your
SmartCloud Control Desk 7.2.1 deployment. After the migration , you are no
longer able to access or use SmartCloud Control Desk 7.2.1. Do not migrate profile
information as described here unless you no longer have a need to access
SmartCloud Control Desk 7.2.1.
Procedure
1. Log on to the system hosting WebSphere Application Server v6.1 and v7.0.
2. Stop WebSphere Application Server v6.1 services, if they are running.
a. Stop IBM HTTP Server and IBM HTTP Administration.
b. Stop WebSphere Application Server deployment manager.
c. Stop node.
d. Stop all Maximo application servers. For example, MXServer.
3. Migrate the deployment manager profile. For example, ctgDmgr01.
a. Start the WebSphere Application Server Migration Wizard.
48
IBM SmartCloud Control Desk: Upgrade Guide
Windows
Start > IBM WebSphere > Application Server Network
Deployment V7.0 > Migration Wizard
Unix or Linux
app_server_root/bin/migration.sh
b. From the Welcome panel, click Next.
c. Select or specify the WebSphere Application Server v6.1 installation used in
the SmartCloud Control Desk 7.2.1 deployment from which to migrate.
Click Next.
d. Choose the existing deployment manager profile, for example, ctgDmgr01,
as the source profile you want to migrate, and then click Next.
Select <Create a new profile> for the target profile, and then click Next.
Set the same name for the profile, for example, ctgDmgr01, and click Next.
Set a backup directory for the migration, and click Next.
Select Do not migrate the applications for the Application migration
settings panel, and click Next.
i. From the Deployment manager disablement panel, click Next.
j. From the Port value assignment panel, select Use the port values assigned
to previous (source) installation, and then click Next.
e.
f.
g.
h.
k. From the Migrate administrative console customized "My Tasks" settings
panel, select Use the default workspace user root location, and click Next.
l. If global security is enabled in WebSphere Application Server v6.1 and the
security.xml file does not contain the corresponding User name and
Password values, you encounter the Administrative security panel. Supply
the administrative credentials requested, and click Next.
m. Indicate if you want the migration to support script compatibility on the
Additional migration options panel, and then click Next. This option is
only needed if you have scripts or programs that are used to create or
modify configuration definitions.
n. From the migration summary panel, click Next.
o. From the Profile creation output panel, click Next. You only see this panel
if you selected <Create a new profile> for the target profile earlier. The new
profile is first created, then the backup of existing configurations is taken
and applied to the newly created deployment manager profile.
p. From the Migration status panel, look for the Migration complete success
message, click Next, and then click Finish.
4. Start the WebSphere Application Server v7.0 deployment manager.
Windows
Start > IBM WebSphere > Process Server > Profiles > profile_name >
Start the deployment manager.
Unix or Linux
/usr/IBM/WebSphere/AppServer/profiles/profile_name/bin/startManager.sh
/opt/IBM/WebSphere/AppServer/profiles/profile_name/bin/startManager.sh
5. Migrate the application server profile. For example, ctgAppSrv01.
a. Start the WebSphere Application Server Migration Wizard.
Windows
Start > IBM WebSphere > Application Server Network
Deployment V7.0 > Migration Wizard
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
49
Unix or Linux
app_server_root/bin/migration.sh
b. From the Welcome panel, click Next.
c. Select or specify the WebSphere Application Server v6.1 installation used in
the SmartCloud Control Desk7.2.1 deployment from which to migrate.
Click Next.
d. Choose the existing application server profile, for example, ctgAppSrv01, as
the source profile you want to migrate, and then click Next.
e. Select <Create a new profile> for the target profile, and then click Next.
f. Set the same name for the profile, for example, ctgAppSrv01, and click Next.
g. Set a backup directory for the application server profile migration which is
different from the location provided earlier for the deployment manager
profile migration, and click Next.
h. Select Do not migrate the applications for the Application migration
settings panel, and click Next.
i. From the Deployment manager disablement panel, click Next.
j. From the Port value assignment panel, select Use the port values assigned
to previous (source) installation, and then click Next.
k. From the Migrate administrative console customized "My Tasks" settings
panel, select Use the default workspace user root location, and click Next.
l. If global security is enabled in WebSphere Application Server v6.1 and the
security.xml file does not contain the corresponding User name and
Password values, you encounter the Administrative security panel. Supply
the administrative credentials requested, and click Next.
m. Indicate if you want the migration to support script compatibility on the
Additional migration options panel, and then click Next. This option is
only needed if you have scripts or programs that are used to create or
modify configuration definitions.
n. From the migration summary panel, click Next.
o. From the Profile creation output panel, click Next. You only see this panel
if you selected <Create a new profile> for the target profile earlier. The new
profile is first created, then the backup of existing configurations is taken
and applied to the newly created deployment manager profile.
p. From the Migration status panel, look for the Migration complete success
message, click Next, and then click Finish.
6. Start the WebSphere Application Server v7.0 node agent.
7. Set the application server profile as the default profile.
WAS7_HOME/bin/manageprofiles.[sh|bat] -setDefaultName -profileName ctgAppSrv01
Installing the WebSphere update installer
This procedure uses the update installer to apply maintenance.
Before you begin
Complete documentation for the update installer is at http://
publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/
com.ibm.websphere.installation.nd.doc/info/ae/ae/tins_updi_install.html. Review
the prerequisites before installing the update installer.
50
IBM SmartCloud Control Desk: Upgrade Guide
About this task
The update installer simplifies maintenance of WebSphere Application Server
Network Deployment v7.0 and related components. These components include
things such as the HTTP server plug-in and fix packs.
Procedure
1. Log in to the system hosting WebSphere Application Server Network
Deployment v7.0 using a user ID with administrative permissions.
2. Stop WebSphere Application Server v6.1 services, if they are running.
a. Stop IBM HTTP Server and webserver1.
b. Stop WebSphere Application Server deployment manager.
c. Stop node.
d. Stop application server. For example, MXServer.
3. Copy the update installer installable image file from the downloaded product
media to the system. The file is in the WS-WAS_UpdateInstaller_7.0.0.15
directory.
4. Unpack the compressed file:
5. Remove the compressed files.
6. Change to the directory where you unpacked the file.
7. Start the installation program (install.[exe|sh]).
8. Accept the license agreement.
9. Proceed through the initial panels, accepting the license agreement. Accept
defaults provided unless you have a specific reason to change them.
10. Before you finish the installation, clear the option to Launch IBM Update
Installer for WebSphere software on exit.
11. Start the WebSphere Application Server v7.0 deployment manager.
Windows
Start > IBM WebSphere > Process Server > Profiles > profile_name >
Start the deployment manager.
Unix or Linux
/usr/IBM/WebSphere/AppServer/profiles/profile_name/bin/startManager.sh
/opt/IBM/WebSphere/AppServer/profiles/profile_name/bin/startManager.sh
Installing and configuring IBM HTTP Server
About this task
If you have a prior version of IBM HTTP Server installed, you can update it to
version 7. Follow the instructions at http://pic.dhe.ibm.com/infocenter/wasinfo/
v7r0/topic/com.ibm.websphere.ihs.doc/info/ihs/ihs/cihs_upgrading.html .
Procedure
1. Log in to the system hosting WebSphere Application Server Network
Deployment v7.0 using a user ID with administrative permissions.
2. Ensure all services associated with the WebSphere Application Server Network
Deployment v6.1 server are stopped, including IBM HTTP Server v6.1.
3. Log in to the WebSphere Application Server Network Deployment v7.0
administrative console. Ensure the ctgDmgr01 deployment manager is running
and that the SOAP port is set to listen at the correct port (8879 is the default).
4. Copy the update installer installable image file from the downloaded product
media to the system. The file is in the WS-WAS_ND_7.0_Supplemental directory.
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
51
5.
6.
7.
8.
9.
10.
11.
12.
13.
Unpack the compressed file:
Remove the compressed files.
Change to the directory where you unpacked the file.
Change to the IHS directory and start the installation program
(install.[exe|sh]).
From the Welcome panel, click Next.
Accept the license agreement and click Next to display the installation root
directory panel.
From the System prerequisites check panel, click Next.
Specify the installation location, and click Next.
From the Port Values Assignment panel, specify the following values, and
click Next.
HTTP Port
80
HTTP Administration Port
8008
14. From the HTTP Administration Server Authentication panel, specify the
following values, and click Next.
Create a user ID for IBM HTTP administration server authentication
Enable this option by selecting this check box.
User ID
Specify wasadmin
Password
Specify the password for the wasadmin user.
15. From the Setup HTTP Administration Server panel, specify the following
values, and click Next.
Set up IBM HTTP administration server to administer IBM HTTP Server
Enable this option by selecting this check box.
Create a unique user ID and group for IBM HTTP Server administration
Enable this option by selecting this check box.
User ID
Specify wasadmin.
Group Specify ihsadmin
16. From the IBM HTTP Server plug-in for WebSphere Application Server panel,
specify the following values, and click Next.
Install the IBM HTTP Server plug-in for IBM WebSphere Application
Server Enable or clear this check box to disable this option as is appropriate
for your configuration. In an environment where you have multiple
deployment manager profiles, it is more practical to run the web
server plug-ins installation task separately. This task is done by
running the plug-in installation program after exiting the IBM HTTP
Server installation program. However, if your WebSphere environment
only contains a single deployment manager profile, you can leave the
WebSphere plug-in option selected. When it is selected, the web server
plug-ins installation task starts when you click Next.
For more information about deployment scenarios for IBM HTTP
Server, see http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/
index.jsp?topic=/com.ibm.websphere.ihs.doc/info/welcome_ihs.html.
52
IBM SmartCloud Control Desk: Upgrade Guide
If you decide to install the IBM HTTP Server plug-in now, you must
configure it. Perform the following steps to configure the plug-in.
a. Stop and restart the deployment manager:
WebSphere_Install/profiles/ctgDmgr01/bin/stopManager
WebSphere_Install/profiles/ctgDmgr01/bin/startManager
b. Copy the HTTPSrv_Install/Plugins/bin/configurewebserver1 program file
to WebSphere_Install/bin/
c. Change directory to WAS_HOME/bin and then use the following command:
configurewebserver1
d. Start the IBM HTTP Server servers.
e. Log in to the WebSphere administrator console and ensure that webserver1
has started.
Installing IBM HTTP Server fix packs:
IBM HTTP Server fix pack must be installed. This fix pack updates the base
installation of the IBM HTTP Server to the latest maintenance level.
Procedure
1. Log in to the system hosting WebSphere Application Server Network
Deployment v7.0 using a user ID with administrative permissions.
2. Stop WebSphere Application Server v7 services, if they are running.
a. Stop IBM HTTP Server.
b. Stop the admin server.
c. Stop node.
d. Stop application server. For example, MXServer.
3. Copy the fix pack file from the downloaded product media to the
HTTPSrv_Install/maintenance directory. Create this directory if it does not
exist. The file is in the WS-WAS_IHS_7.0_FP15 directory.
4. Unpack the compressed file:
5. Remove the compressed files.
6. Change to the update installer directory where you unpacked the file.
7. Install the fix pack.
a. Start the update installer wizard:
WebSphere_Install/UpdateInstaller/update.[bat|.sh]
b. Click Next.
c. From the Product Selection panel, select the IBM HTTP Server directory by
browsing to the HTTPSrv_Install directory, and then clicking Next.
d. From the Maintenance Operation Selection panel, select Install
maintenance package, and then click Next.
e. From the Maintenance Package Directory Selection panel, browse to the
HTTPSrv_Install/maintenance directory, and then click Next.
f. From the Available Maintenance Package to Install panel, click Select
Recommended Updates, select the target update, and click Next.
g. On the Installation Summary screen, click Next to begin the installation of
the critical fixes.
8. Start IBM HTTP Server.
9. Start the admin server.
10. Restart WebSphere Application Server and the managed nodes:
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
53
Installing the WebSphere plug-in
This procedure provides task information for manually installing and configuring
WebSphere plug-in for IBM HTTP Server. This procedure is optional if you chose
to install and configure the WebSphere plug-in when you installed the IBM HTTP
Server.
Procedure
1. Log on as an administrative user on the system where you have installed
WebSphere Application Server Network Deployment v7.0.
2. Change to the directory where you previously extracted the IBM HTTP Server
installable images. For example, WS-WAS_ND_7.0_Supplemental.
3. Change to the plugin directory.
4. Start the WebSphere plug-in installation program.
5. On the Welcome panel, clear the option to learn more about the Installation
roadmap: Overview and installation scenarios. Click Next.
6. Accept the license agreement and click Next.
7. From the plug-in selection panel, select the IBM HTTP Server V7 plug-in, and
then click Next.
8. From the installation scenario panel, select WebSphere Application Server
machine (local), and then click Next.
9. Accept or change the installation directory. Click Next.
10. Specify the location where you installed the application server; the default is
WebSphere_Install/AppServer. Click Next.
11. From the select profile panel, select ctgDmgr01 from the list, and then click
Next.
12. From the web server configuration file panel, specify the following
information:
Select the existing IBM HTTP Server httpd.conf file
Browse to the location of the httpd.conf file; the default is
HTTPSrv_Install/conf/httpd.conf.
Specify the Web server port
The default is port 80.
Clicking Next might produce warning message that indicates that the selected
IBM HTTP Server configuration file already contains plug-in entries. If you
proceed, this configuration file is updated with a new plugin-cfg xml file
location. You can click OK to proceed.
13. From the web server definition panel, specify a unique web server definition
name; the default name (webserver1) is satisfactory.
14. Accept the default web server plug-in configuration file name
(plugin-cfg.xml) and location.
15. Click Next to acknowledge the manual configuration steps.
16. From the installation summary panel, click Next.
17. When the installation is complete, click Finish.
18. Stop and start the deployment manager.
19. Copy the HTTPSrv_Install/Plugins/bin/configurewebserver1 file to
WebSphere_Install/bin/
20. Change directory to WebSphere_Install/bin and then run the
configurewebserver1 command:
54
IBM SmartCloud Control Desk: Upgrade Guide
21. Log in to the WebSphere administrator console and ensure that webserver1
has started.
Installing WebSphere Application Server Network Deployment plug-in fix
packs:
The WebSphere Application Server Network Deployment plug-in fix pack 15 is
required. This task updates the base installation of the plug-in to the latest
maintenance level.
Procedure
1. Copy the fix pack file to the WebSphere_Install/UpdateInstaller/maintenance
directory. Create this directory if it does not exist. The file is in the
WS-WAS_Plugins_7.0_FP15 directory.
2. Stop the IBM HTTP Server. Type /opt/IBM/HTTPServer/bin/apachectl stop.
3. Stop WebSphere Application Server Network Deployment and the managed
nodes.
4. Install the fix pack.
a. Launch the update installer wizard.
WebSphere_Install/UpdateInstaller/update
b. Click Next.
c. From the Product Selection panel, select the IBM HTTP Server Plugin
directory by browsing to the HTTPSrv_Install/Plugin directory, and then
clicking Next.
d. From the Maintenance Operation Selection panel, select Install maintenance
package, and then click Next.
e. From the Maintenance Package Directory Selection panel, browse to the
WebSphere_Install/UpdateInstaller/maintenance directory, and then click
Next.
f. From the Available Maintenance Package to Install panel, click Select
Recommended Updates, select the target update, and click Next.
g. On the Installation Summary screen, click Next to begin the installation of
the critical fixes.
5. Start the IBM HTTP Server.
6. Restart WebSphere Application Server Network Deployment and the managed
nodes.
Migrate database or directory server data (optional)
Depending upon your environment, you might have to migrate database or
directory server data from the middleware servers used in your prior deployment
to new middleware servers.
If the middleware you used in your prior deployment is incompatible with
SmartCloud Control Desk 7.5, you can migrate data to a new server supported by
SmartCloud Control Desk 7.5.
If your existing database software is compatible with SmartCloud Control Desk 7.5,
you can use the existing database. If the existing database is not compatible, refer
to the documentation provided with your software for instructions on migrating
database objects. For DB2, this information can be found at http://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/
com.ibm.db2.luw.qb.upgrade.doc/doc/c0011933.html. Recall that if you performed
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
55
an upgrade of your database software, you are only required to migrate the
existing database instance (ctginst1) and database (maxdb71). If you installed a
new instance of the database software, you must complete additional configuration
tasks as described in the SmartCloud Control Desk 7.5 installation
information. Additional tasks include creating system users, creating a new
database instance, and modifying the maximo.properties file to update information
for the new server.
If you chose to use a directory server for security in your prior deployment and
you are required to migrate directory server information to comply with
SmartCloud Control Desk 7.5 prerequisites, consult the documentation provided
with your software for instructions on migrating. If you used IBM Tivoli Directory
Server in your prior deployment, no migration is required because the same
version of IBM Tivoli Directory Server is supported.
Running the SmartCloud Control Desk 7.5 installation program with
manual configuration
Manually configure WebSphere Application Server Network Deployment v7.0 and
upgrade to SmartCloud Control Desk 7.5 .
About this task
In order to upgrade an existing SmartCloud Control Desk 7.2.1 deployment to
SmartCloud Control Desk 7.5 you first must migrate WebSphere Application Server
Network Deployment v6.1 configuration information to WebSphere Application
Server Network Deployment v7.0. You then run the SmartCloud Control Desk 7.5
installation program on the original SmartCloud Control Desk administrative
system. The SmartCloud Control Desk 7.5 installation program detects the existing
SmartCloud Control Desk deployment and guides you through the upgrade
process. You select the option to inform the installation program that you have
already manually configured WebSphere Application Server Network Deployment
v7.0. No automated configuration of WebSphere Application Server Network
Deployment v7.0 is performed by the SmartCloud Control Desk 7.5 installation
program.
If you encounter any errors related to the installation program during the upgrade,
refer to the installation information for troubleshooting details.
Before the upgrade, ensure that all SmartCloud Control Desk process managers are
at the expected level. Open a command prompt and issue the following command:
Install_Home\bin\solutioninstaller -action showinstalled -type all
To upgrade an existing SmartCloud Control Desk deployment to SmartCloud
Control Desk 7.5, complete the following steps:
Procedure
1. Stop the MXServer application server or servers of the SmartCloud Control
Desk 7.2.1 deployment.
2. Log in to the administrative workstation using the administrative user ID
used in the previous deployment.
3. Copy the trust.p12 keystore file from the WebSphere_Install/profiles/
ctgDmgr01/etc directory of the WebSphere Application Server Network
56
IBM SmartCloud Control Desk: Upgrade Guide
Deployment v7.0 server to the administrative workstation. This step is not
necessary if WebSphere Application Server Network Deployment is hosted on
the administrative workstation system.
4. Start the SmartCloud Control Desk installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
b. In the launchpad navigation pane, click Install The Product.
c. Click Install IBM SmartCloud Control Desk 7.5.
Alternatively, you can start the SmartCloud Control Desk installation program
directly. Browse to the \Install\mam\ directory of the downloaded installation
image and run the following command
Windows
v install.bat
v install_win64.bat
5. Select a language for the installation and click OK.
6. In the Introduction panel, click Next.
7. In the Choose Installation folder panel, manually enter the install location of
the existing SmartCloud Control Desk 7.2.1 deployment to target it for an
upgrade.
8. Review the information presented in the Verify installation location panel, and
then click Next. The Verify installation location panel reports previous
installation information that was found based upon the installation directory
you chose in the previous panel. Once you advance past this panel, you
cannot go back and change the installation directory for this installation.
9. In the Package Summary panel, review the package deployment actions, and
then click Next. This panel lists version information for both new and existing
packages on the system. Target package version information indicates the
package version being currently deployed.
10. The SmartCloud Control Desk program license agreement window is
displayed. Read the license information and select I accept the terms in the
license agreement. if you agree with the terms. Click Next.
11. In the Database Upgrade panel, review the prerequisite database task
information. Select the option indicating that you have performed the
prerequisite database tasks, and then click Next.
12. In the Import Middleware Configuration Information panel, clear the selection
for the Import middleware configuration information option. Click Next.
13. In the Automate WebSphere Configuration panel, clear the option for
automating WebSphere Application Server Network Deployment
configuration, and then click Next. Manual configuration of WebSphere
Application Server Network Deployment v7.0 was performed when you
migrated profiles from WebSphere Application Server Network Deployment
v6.1. Ensure the domain and node managers are started before proceeding.
14. In the WebSphere Connectivity panel, enter host information about the
WebSphere Application Server Network Deployment, and then click Next.
Host name
Enter the fully qualified host name of the system hosting WebSphere
Application Server Network Deployment.
Alternatively, you can provide the IP address for the system.
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
57
SOAP port
Enter the SOAP port of the WebSphere Application Server Network
Deployment system.
The default value for this field is 8879.
User ID
Enter the administrative user ID used to access the WebSphere
Application Server Network Deployment Server.
Default for all platforms is wasadmin.
Password
Enter the password for the administrative user ID used to access the
WebSphere Application Server Network Deployment Server.
In IP v6 environments, you are also prompted to provide the RMI bootstrap
port.
15. In the WebSphere Application Server Network Deployment Configuration
panel, enter the following information, and then click Next.
Web server port
Enter the web server port used by WebSphere Application Server
Network Deployment.
Default for all platforms is 80.
This value should match an existing HTTP server port value you
configured when you set up WebSphere Application Server Network
Deployment. If you enter a different value for this port, you must
restart WebSphere Application Server Network Deployment at the
conclusion of the installation. Restarting the server activates the new
port, making it available for incoming requests.
Web server name
Enter the name of the web server.
Default for all platforms is webserver1.
Node name
Enter the name of the WebSphere Application Server Network
Deployment node containing the application server.
Default for all platforms is ctgNode01.
Application server
Enter the name of the WebSphere Application Server Network
Deployment application server to associate with SmartCloud Control
Desk.
Default for all platforms is MXServer. This value can be customized.
The application server is created if it does not exist.
16. In the Integration Adapter JMS Configuration panel, enter the following
information, and then click Next. A JMS server requires a DB2 data repository
to be configured to maintain messages. If you are using another database
type, you cannot have the installation program configure message persistence.
JMS Data Source name
Enter the name of the database to be used by JMS.
If you are using Microsoft SQL Server, this field is pre-populated. If it
is not, enter intjmsds.
58
IBM SmartCloud Control Desk: Upgrade Guide
Select whether the JMS data store should be persisted.
Persist JMS messages
Select this option to enable the SmartCloud Control Desk
installation program to set the JMS implementation to persist
messages within DB2.
Do not persist JMS messages
If you select this option, the SmartCloud Control Desk
installation program does not set the JMS implementation to
persist messages automatically in DB2. You can configure the
JMS implementation manually at a later date. If you select this
option, when you click Next, the installation wizard skips to
the panel to configure SMTP.
Select this option if you are deploying SmartCloud Control
Desk with Oracle or Microsoft SQL Server.
17. If you chose to persist JMS messages, in the DB2 Database Server
Configuration panel, enter the following information, and then click Next. If
you chose not to persist JMS messages you do not see this panel.
Note: The JMS data store can only be created as a DB2 database.
Host name
Enter the fully qualified host name of the server hosting the JMS data
store.
Alternatively, you can provide the IP address for the system.
Port
Enter the port used to access the database server.
Default for all platforms is 50005.
Database name
Enter the name of the database serving as the JMS data store.
Default for all platforms is maxsibdb.
User ID
Enter the user ID used to access the database server.
Default for all platforms is maximo.
Password
Enter the password for the user ID used to access the database server.
18. In the WebSphere Application Server Network Deployment keystore file panel,
browse to where you copied the trust.p12 keystore file, and then click Next.
19. On the Data Integration Services and Context Menu Service Deployment
Options panel, specify a deployment option. If you deployed a separate
database for Data Integration Services and Context Menu Service in your prior
deployment, select Configure data integration and context menu services for
this product using a previously deployed data integration and context menu
service instance to use that previously deployed database. Otherwise, select
Deploy data integration and context menu services into the same database
that you created for the product to use the SmartCloud Control Desk
database for the Data Integration Services and Context Menu Service. The
Data Integration Services and Context Menu Service allow products to register
themselves to offer launch in context to all other registered products and to
gain launch access to all other registered products. This ability is provided
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
59
without unique product-to-product integration efforts. Refer to the product
information center for more information about configuring cross-product
launch points.
20. If you have not previously configured the following parameters for your
SmartCloud Control Desk 7.2.1 deployment, you are prompted to supply
SMTP configuration information. In the SMTP Configuration panel, specify
SMTP configuration information used by workflows to communicate with
workflow participants.
SMTP server
Enter the fully qualified host name of the SMTP server that sends
messages to participants.
Alternatively, you can provide the IP address for the system.
Administrator e-mail
Enter a valid e-mail address. This address is used to send messages.
You can defer SMTP configuration at this time by not providing any
information and clicking through to the next panel. However, you must
configure these parameters through the product interface as a post installation
task.
21. From the Run Configuration Step panel, click Next.
22. From the input summary panel, verify that the values displayed are the ones
used in your existing SmartCloud Control Desk deployment, and then click
Next.
23. From the Pre-Installation Summary panel, review the install summary values,
and then click Install.
The upgrade process begins copying files to your local system.
24. Click Finish to exit the installation program.
Installing optional content and integration modules
You might want to add optional content to your environment, or integrate with
other products.
About this task
Optional content is often used in development environments as a way to begin
developing your own content. The Reference section of the product information
center contains a detailed description of the optional content that you can install
from the product launchpad. If you do not install optional content during the
product upgrade process, you can install it later. If you install it later, you must
update the database and rebuild and deploy the maximo.ear file.
If you had optional content installed in your prior deployment, you must install
the new optional content to replace it. The database cannot be updated if it
contains content from prior releases.
You can install integration modules to help you integrate SmartCloud Control Desk
applications with other products. If you do not install integration modules during
the product upgrade process, you can install them later. If you install them later,
you must update the database and rebuild and deploy the maximo.ear file.
Procedure
1. Restart the launchpad.
60
IBM SmartCloud Control Desk: Upgrade Guide
2. To install optional content, use the link in the navigation area to open the
Optional Content page of the launchpad.
3. Click the link to install optional content. The product installer is launched.
4. Follow the screens through the installer. If check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes.
5. Click Finish to exit the installation program.
6. To install optional integrations, restart the launchpad. Use the link in the
navigation area to open the Integrations page of the launchpad.
7. Click the link for each integration that you want to install. The product installer
is launched.
8. Follow the screens through the installer. If check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes.
9. Click Finish to exit the installation program.
Migrate customizations
Customizations you made in your prior deployment are not migrated
automatically to your new environment.
About this task
When you installed SmartCloud Control Desk 7.5, your prior deployment was
preserved in a directory called pre_75_maximo, located in the C:\IBM\SMP
directory. You must migrate your customizations archived in the pre_75_maximo
directory to the installation directories of the current SmartCloud Control Desk 7.5
deployment.
Procedure
1. Compile custom Java code using the JDK 1.6 compiler. Custom Java classes that
were created for your prior deployment were likely compiled using JDK 1.5,
which was provided with previous product versions. Custom Java code must
be recompiled using the JDK 1.6 compiler supplied with SmartCloud Control
Desk 7.5 in the C:\IBM\SMP\sdk\bin folder, or any supported 1.6 JDK.
a. Locate custom Java source files in subdirectories of the pre_75_maximo
archive directory.
b. Compile source into Java class files using JDK 1.6.
c. Move recompiled class files into the appropriate SmartCloud Control Desk
7.5 directory. Typically this is the same directory under SmartCloud Control
Desk 7.5 as it was in your prior deployment.
2. Identify customizations that were made to default JSP, XML, HTML, CSS or
XSLT files in your prior deployment. These customizations of default files must
be recreated in the SmartCloud Control Desk 7.5 versions of these files. You can
find the customized files in the pre_75_maximo archive directory. You cannot
overwrite SmartCloud Control Desk 7.5 files with modified versions of default
files from your prior deployment found in the pre_75_maximo directory.
Customizations must be reapplied to the SmartCloud Control Desk 7.5 versions
of these default files.
3. Copy or move any custom JSP, XML, HTML, CSS or XSLT files you created to
work with your prior deployment.
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
61
4. For any changes made to Applet extensions, move the compiled code into the
appropriate folders on the SmartCloud Control Desk 7.5 installation directory.
Ensure that you build the Applet Jars from the SmartCloud Control Desk 7.5
folders.
5. Copy or move any customized report files from the pre_75_maximo directory
structure to the appropriate SmartCloud Control Desk 7.5 folder. These report
files need to be imported into the database after the upgrade process is
complete, as describe in the post-upgrade information.
6. Move any custom configuration files (.properties and .xml) that contain
extensions defined for SmartCloud Control Desk 7.5. Product XML files can be
found in the \maximo\applications\maximo\properties\product folder. If
customizations were made to default configuration files in your prior
deployment, you must replicate those changes in the SmartCloud Control Desk
7.5 versions of those files.
7. Copy or move the webclient.properties file from the pre_75_maximo directory
structure to the \maximo\applications\maximo\properties\product folder of the
SmartCloud Control Desk 7.5 installation.
8. Copy or move any third-party libraries used with the previous release from the
pre_75_maximo directory structure to the appropriate SmartCloud Control Desk
7.5 folder. Consult the information provided with your third-party libraries to
verify that no further configuration tasks are required.
Running the installation program to update the database
Run the installation program a final time to update the database and perform final
deployment steps.
About this task
The SmartCloud Control Desk 7.5 installation program is run a final time to have it
perform actions skipped on previous invocations. These actions can include
running updatedb, running TDToolkit, and building and deploying EAR files. The
installer will not repeat steps that you have already run.
Procedure
1. Start the SmartCloud Control Desk installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
b. In the launchpad navigation pane, click Install The Product.
c. Click Install IBM SmartCloud Control Desk 7.5.
Alternatively, you can start the SmartCloud Control Desk installation program
directly. Browse to the \Install\product_abbreviation\ directory of the
downloaded installation image and run the following command
Windows
v install.exe
v install_win64.exe
2. Select a language for the installation and click OK.
3. In the Introduction panel, click Next.
62
IBM SmartCloud Control Desk: Upgrade Guide
4. In the Choose Installation folder panel, use the drop-down menu to choose
the folder where you have begun the upgrade.
5. Review the information presented in the Verify installation location panel, and
then click Next.
6. In the Package Summary panel, review the package deployment actions, and
then click Next.
7. From the Run Configuration Step panel, clear the check boxes for all options,
and then click Next. If you allow the installation program to perform these
steps, you do not have to complete them manually. If you prefer to deploy
the EAR files to your J2EE server manually after the installer has created
them, check the box for "Deploy application files manually later."
8. From the input summary panel, verify that the values displayed are the ones
used in your existing SmartCloud Control Desk deployment, and then click
Next.
9. From the Pre-Installation Summary panel, review the install summary values,
and then click Install. The installation program performs the following tasks
that remain for the upgrade:
v Run updatedb. This commits data for SmartCloud Control Desk 7.5, and
any other products or add-ons that you have upgraded, to the Maximo
database.
v Run TDToolkit to load languages for SmartCloud Control Desk 7.5.
v Build application EAR files.
v Deploy application EAR files.
10. Click Finish to exit the installation program.
Run integrity checker 7.5
Run the SmartCloud Control Desk 7.5 integrity checker utility.
About this task
Before proceeding further with the SmartCloud Control Desk 7.5 upgrade process,
you need to run the SmartCloud Control Desk 7.5 Integrity Checker utility to
confirm the integrity of the SmartCloud Control Desk 7.5 database after the
upgrade steps have been completed. When run in Report mode, the integrity
checker utility checks the current database and reports on common errors. If the
Integrity Checker reports an error, you must resolve it by running the Integrity
Checker in Repair mode.
Procedure
1. Stop the application server. For example, MXServer.
2. From the administrative workstation of the existing deployment, open a
command prompt and change directory to the maximo tools directory. For
example, c:\ibm\SMP\maximo\tools\maximo
3. Start the Integrity Checker tool.
integrityui.bat
4. Select the Check Integrity tab.
5. Run the Integrity Checker in Report mode.
a. Ensure that the Repair Mode? check box is cleared, and then click Run
Integrity Checker.
b. When the report dialog box appears, click OK.
Chapter 7. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 (Scenario 2)
63
Results are found in the install dir\maximo\tools\maximo\log directory in the
file defined in the Log File Name field of the Check Integrity panel.
6. Optional: If any errors are reported, run the Integrity Checker in Repair mode.
a. Select the Repair Mode? check box, and then click Run Integrity Checker.
b. When the report dialog box appears, click OK.
7. Optional: If Integrity Checker was run in Repair mode, check the log file to
ensure all reported items have been repaired. If further manual intervention is
required, you must resolve the errors and then rerun the Integrity Checker in
Report mode. Repeat the process until no more errors are reported.
Results
While the Integrity Checker can repair many issues, you might have to resolve
some errors manually by consulting the log files.
64
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 8. Upgrading by migrating WebSphere v6.1
configuration information to WebSphere v7.0 using the
middleware installation program (Scenario 3)
Use this information to migrate configuration information from your existing
WebSphere Application Server Network Deployment v6.1 installation to a new
installation of WebSphere Application Server Network Deployment v7.0.
About this task
This information provides a high-level overview or road map of tasks you need to
complete in order to upgrade to SmartCloud Control Desk 7.5 by migrating the
configuration of WebSphere Application Server Network Deployment v6.1 used
with your prior deployment to WebSphere Application Server Network
Deployment v7.0.
In this scenario, you use the middleware installation program to install and
configure WebSphere Application Server Network Deployment v7.0. You also use
the middleware installation program migration option to transfer existing product
configuration information from WebSphere Application Server Network
Deployment v6.1 to WebSphere Application Server Network Deployment v7.0. The
WebSphere Application Server Network Deployment v6.1 server used in your prior
deployment must have been previously installed and configured using the
middleware installation program. If you did not previously install WebSphere
Application Server Network Deployment v6.1 using the middleware installation
program, you cannot use the middleware installation program to migrate data
from WebSphere Application Server Network Deployment v6.1 to WebSphere
Application Server Network Deployment v7.0. WebSphere Application Server
Network Deployment v7.0 must be installed using the middleware installation
program on the same system as the one hosting WebSphere Application Server
Network Deployment v6.1
This scenario assumes you have customizations from your prior deployment that
you want to migrate to SmartCloud Control Desk 7.5.
The benefit of using this upgrade scenario is that you do not have to configure
WebSphere Application Server Network Deployment v7.0. You reuse the
configuration you performed for WebSphere Application Server Network
Deployment v6.1.
Procedure
1. Perform pre-upgrade tasks
2. Run the Integrity Checker from your existing environment in Report mode.
Tasks “Run Integrity Checker” on page 14
3. Establish supported middleware
If necessary, upgrade your database software to a supported version using the
installation program for that software.
If necessary, upgrade your directory server software to a supported version
using the installation program for that software. Refer to the documentation
provided with your product for upgrade information.
© Copyright IBM Corp. 2012
65
Concepts
“Establish supported middleware” on page 67
4. Install WebSphere Application Server Network Deployment v7.0 and migrate
configuration information. You install WebSphere Application Server Network
Deployment v7.0 using the middleware installation program. You migrate
existing WebSphere Application Server Network Deployment v6.1 information
created for your prior deployment to WebSphere Application Server Network
Deployment v7.0. Migration is performed by the SmartCloud Control Desk 7.5
middleware installation program.
Tasks
v “Installing WebSphere Application Server Network Deployment
v7.0 and migrating configuration information using the middleware
installation program” on page 67
5. Optional: Migrate the database or directory server data, if necessary.
Concepts
“Migrate database or directory server data (optional)” on page 32
6. Run the SmartCloud Control Desk 7.5 installation program.
In this step the installation program copies files onto the administrative
workstation and runs the configuration step, but updatedb is deferred.
“Running the SmartCloud Control Desk 7.5 installation program with
manual configuration.” on page 73
7. Migrate customizations from your prior deployment.
When you upgraded to SmartCloud Control Desk 7.5, the data from your
prior deployment was preserved in a directory called pre_75_maximo, located
in the installation directory, which, by default, is C:\IBM\SMP. You must
migrate your customizations archived in the pre_75_maximo directory to the
installation directories of the current SmartCloud Control Desk 7.5
deployment.
Tasks
Tasks “Migrate customizations” on page 40
8. Run the SmartCloud Control Desk 7.5 installation program to automate the
steps to upgrade the database.
The SmartCloud Control Desk 7.5 installation program is run a second time to
have it perform actions skipped the first time. For example, running updatedb
and running tdtoolkit.
Tasks
“Running the installation program to update the database” on page 41
9. Run Integrity Checker
Run the Integrity Checker tool in Report mode. If the Integrity Checker
reports an error, you must resolve it.
Tasks “Run integrity checker 7.5” on page 80
10. Perform post-installation tasks
Concepts
Chapter 11, “Post-upgrade tasks,” on page 97
Tasks
v
v
v
v
66
“Reviewing your upgraded screens” on page 103
“Reviewing table domains and crossover domains” on page 104
“Updating BIRT reports” on page 104
“Updating statistics” on page 105
IBM SmartCloud Control Desk: Upgrade Guide
v “Uninstalling WebSphere Application Server Network Deployment
v6.1” on page 105
Establish supported middleware
Establish middleware in your environment that is compatible with SmartCloud
Control Desk 7.5.
The first step in a SmartCloud Control Desk 7.5 upgrade is to establish middleware
in your environment that is supported by SmartCloud Control Desk 7.5. In some
cases, middleware you used in your prior deployment, for example, database or
directory server software , can be reused for the SmartCloud Control Desk 7.5
upgrade. In other cases, you might have to use new middleware servers that were
not part of your prior deployment.
The middleware installation program is used to install WebSphere Application
Server Network Deployment v7.0. Existing WebSphere Application Server Network
Deployment configuration information is migrated using the middleware
installation program.
If necessary, upgrade database software to a version supported by SmartCloud
Control Desk 7.5. Upgrading the existing database software used in your prior
deployment is the preferred method of establishing a SmartCloud Control Desk 7.5
supported database. This method allows you to reuse existing data such as user
ID's and database instances. In some cases, you might be forced to install a new
instance of the database software. For example, your prior deployment might
include a database server that is established on a platform that is no longer
supported in SmartCloud Control Desk 7.5, as could be the case with 32-bit
platforms. In this scenario, you would install a fresh instance of the database
software compatible with SmartCloud Control Desk 7.5. For DB2, you could install
this software using the SmartCloud Control Desk 7.5 middleware installation
program. If you install new instances of database software outside of the
middleware installation program, you would have to perform additional manual
configuration tasks that are described in the SmartCloud Control Desk 7.5
installation information. In addition, you would have to migrate the database from
the old server to the new server.
If necessary, upgrade directory server software to a version supported by
SmartCloud Control Desk 7.5. Refer to the documentation provided with your
directory server product for upgrade information.
Installing WebSphere Application Server Network Deployment
v7.0 and migrating configuration information using the
middleware installation program
Use the middleware installation program to create a deployment plan that is
responsible for installing WebSphere Application Server Network Deployment v7.0
and migrate existing configuration information.
Before you begin
These instructions are for the installation of WebSphere Application Server
Network Deployment v7.0 on a single system using the middleware installation
program. In this scenario, you install WebSphere Application Server Network
Deployment v7.0 on the same system as WebSphere Application Server Network
Deployment v6.1 and use the middleware installation program to automatically
Chapter 8. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 using the middleware installation
program (Scenario 3)
67
migrate WebSphere Application Server Network Deployment v6.1 configuration to
WebSphere Application Server Network Deployment v7.0.
In some cases, information about the middleware installation program screens is
not correctly displayed when installing through a remote session. If you do
encounter the problem, first minimize and then maximize the installation wizard to
redisplay the screen. To avoid such a problem, run the middleware installation
program locally on the system that is to host the middleware.
Do not use localhost for host name values in the installation program. Specify the
fully qualified host name or IP address of the system on which you are installing.
For Linux or UNIX systems, if the hostname -f command does not return a fully
qualified host name, consult the system documentation for assistance. For
Windows systems, to establish a fully qualified host name, complete the following
steps:
1. On the desktop, right-click My Computer.
2. Select Properties.
The System Properties panel is displayed.
3. From the Computer Name tab, click Change.
The Computer Name Changes panel is displayed.
4. Enter your fully qualified host name in the Computer name field, and then
click Enter.
Alternatively, you can provide the IP address for the system.
The DNS Suffix and NetBIOS Computer Name panel is displayed.
5. Verify that the Primary DNS suffix field displays a domain name, and then
click OK.
6. From the Computer Name Changes panel, click OK.
7. Click Apply and close the System Properties panel.
You can force the use of alphanumeric host name within the middleware
installation program by starting it from the command line and using the
forceHostname=true parameter. For example:
mwi -V forceHostname=true
When installing and configuring WebSphere Application Server Network
Deployment v7.0 in the middleware installation program and the SmartCloud
Control Desk installation program, consider the following special characters
restrictions:
Table 3. Middleware object naming conventions
Header
Header
WebSphere Application Server Network
Deployment
The administrator name cannot contain the
following characters: / \ * ,: ;=+?|< > & %
'"] [> # $ ~ ( ) !
The administrator name cannot begin with a
period.
The administrator name cannot contain
leading and trailing spaces.
The administrator password must consist of
eight characters.
68
IBM SmartCloud Control Desk: Upgrade Guide
Table 3. Middleware object naming conventions (continued)
Header
Header
Middleware installation program
The middleware installation program does
not validate that the password provided is
compliant with the operating system of the
target host. Ensure that the password values
you provide are valid for your environment.
You cannot use the '%' character on
Windows or !, $, #, % characters on UNIX.
The middleware installation program does
not check for accented characters in user
name values. The use of accented characters
can cause errors.
Do not include the underscore character (_)
when entering host names. Using this
character causes an error during middleware
installation.
If the middleware installation program reports that you have insufficient disk
space to install WebSphere Application Server Network Deployment v7.0, you
must increase the available disk space on the system. When disk space has been
increased, restart the middleware installation program.
Important: The middleware installation program does not account for the
temporary space needed on the application server host for the migration of
WebSphere Application Server Network Deployment data. An additional 700MB of
disk space is required on the workspace directory partition to ensure data
migration is successful.
When you run the middleware installation program, you are prompted for user
IDs to initiate the installation of WebSphere Application Server Network
Deployment v7.0. You can either supply an existing system user ID, or allow the
middleware installation program to create a user ID.
If you encounter the following error, it indicates that you are attempting to use the
64-bit middleware installation program (mwi-AMD64.exe) on a 32-bit Windows
system.
CreateProcess failed ==> The image file %1 is valid, but for a machine type
other than the current machine
The appropriate middleware installation program for 32-bit Windows systems is
mwi.exe. Alternatively, run the following command to automatically select the
appropriate program for the system:
setupwin.bat /l
About this task
To install WebSphere Application Server Network Deployment v7.0 for IBM
SmartCloud Control Desk 7.5 using the middleware installation program, follow
these steps.
Chapter 8. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 using the middleware installation
program (Scenario 3)
69
Procedure
1. Log in to the target system as a user with administrative authority. If you are
running the middleware installation program from a Linux or UNIX terminal
window, you must be logged in as the root user.
2. Launch the middleware installation program from the launchpad.
a. Start the launchpad.
Windows
From the downloaded installation image, browse to the root
directory and run the following command: launchpad.exe.
Linux and UNIX
From the downloaded installation image, browse to the root
directory and run the following command: launchpad.sh.
When starting the middleware installation program from the launchpad,
installation program files are copied to a temporary directory on the
system. You can use the following setup scripts to start the middleware
installation program directly and prevent the installer from copying the
files to the system.
Windows
launchpad\Install\MWI\setupwin.bat /l
Linux and UNIX
launchpad\Install\MWI\setupUNIX.sh -l
The following errors can occur when using the setup scripts.
Table 4. Middleware installation program setup script error codes
Error
Code
Error
Description
11
Unsupported operating system
The middleware installation program
or one of the middleware products
cannot run on this operating system.
12
Unsupported Linux distribution
The middleware installation program
or one of the middleware products is
not supported on this Linux kernel.
Currently only Red Hat and SuSE are
supported.
13
Unsupported kernel bit mode
The middleware installation program is
supported on Linux 32/64 bit mode
and on AIX 64 bit mode.
14
Unsupported Processor architecture
The middleware installation program
or one of the middleware products is
not supported on this processor
architecture. Currently only x86 and
AMD64 architecture are supported.
21
Env variable
mwi_launchpadroot(UNIX) /
LaunchPadBatchPath(Win) is not set
The environment variable must be set
to the middleware installation program
install files location:
Windows
LaunchPadBatchPath
Linux and UNIX
mwi_launchpadroot
70
IBM SmartCloud Control Desk: Upgrade Guide
Table 4. Middleware installation program setup script error codes (continued)
Error
Code
Error
Description
22
The middleware installation program
file not found
The middleware installation program
install file is missing or not accessible.
Check to ensure that the specified file
exists in the current directory.
31
Host name is not a fully qualified
domain name.
The middleware installation program
or one of the middleware products
requires a fully qualified host name
defined.
Alternatively, you can provide the IP
address for the system.
32
SELinux is enabled or set in Enforcing
mode
Middleware product installation fails
with the following error:
JRE could not be found on the system
Disable SELinux using one of the
following methods:
v setenforce 0
v Add the following entry to the
/etc/system file:
set fmac_enforcing = 0
33
The library libstdc++.so.5 (64-bit) is
not installed.
The installer requires libstdc++.so.5
(64-bit), which is located in
/usr/lib64/libstdc++.so.5. If the
system does not have this library
installed, search for an RPM package
(64-bit) compatible with system that
contains this library and install it.
34
The library libstdc++.so.5 is not
installed.
The installer requires libstdc++.so.5,
which is located in
/usr/lib/libstdc++.so.5. If the system
does not have this library installed,
search for an RPM package compatible
with system that contains this library
and install it.
b. In the launchpad navigation pane, click Install the product.
c. From the IBM SmartCloud Control Desk 7.5 Installation panel, click
Middleware.
3. Select a language for the installation and click OK.
4. In the Welcome panel, click Next.
5. In the middleware installation program license agreement window, read the
license information, select I accept both the IBM and the non-IBM terms if
you agree with the terms, and then click Next.
6. In the Choose Workspace panel, specify the directory used as the middleware
installation program workspace, and then click Next. The default location for
the workspace is the last workspace location used by this user, as specified in
the middleware user preferences node. If no previous workspace location
exists in the middleware user preferences node, then the default location for
Chapter 8. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 using the middleware installation
program (Scenario 3)
71
the workspace is C:\ibm\tivoli\mwi\workspace for Windows,
/root/ibm/tivoli/mwi/workspace for Linux, and /ibm/tivoli/mwi/workspace
for AIX.
If the selected directory does not exist, it is created.
After deployment, the middleware installation program also generates a
topology file in this directory. This topology file can be manually copied by
the user to the workspace of the next system in the topology. Information
about the deployment of middleware is available to the middleware
installation program when it is used on the next system.
7. In the Install IBM Autonomic Deployment Engine panel, click Next to install
the IBM Autonomic Deployment Engine.
8. In the WebSphere Upgrade Options panel, select WebSphere Application
Server ND migration, and then click Next. The existing WebSphere
Application Server Network Deployment v6.1 processes are stopped and the
deployment manager is disabled before starting the migration process. The
WebSphere Application Server Network Deployment v7.0 installation uses a
unique installation path, but reuses the ports set up for WebSphere
Application Server Network Deployment v6.1.
9. Enter the following configuration parameters for WebSphere Application
Server Network Deployment, and then click Next.
WebSphere Application Server Install location
Enter the location to install WebSphere Application Server Network
Deployment v7.0.
Update Installer Install location
Enter the location to install the WebSphere Application Server
Network Deployment update program.
IBM HTTP Server Install location
Enter the location to install IBM HTTP Server.
10. Specify the location of the SmartCloud Control Desk middleware images, and
then click Next.
Copy the middleware install images from the source media to a specified
directory
Select this option to copy the middleware images from the product
media to a specified directory.
Specify a directory containing all the required middleware install images
Select this option if you intend to specify a file system directory that
already contains the middleware installation images.
11. If you selected the option to copy installation images from the source media,
specify the source and destination directories, and then click Next. If you
selected the option to specify a directory that already contained the
middleware images, specify that directory, and then click Next. There is an
option for checksum validation for the middleware images. Select this option
if you want to confirm the integrity of the images before deploying the
middleware. If the checksum operation fails, click Back and recopy the images
before proceeding. If you do not select this option and the middleware images
are corrupted or otherwise inaccessible from the directory specified, an error
occurs. If you encounter this error, you must replace the corrupted
middleware image and then restart the middleware installation program.
12. Specify a directory to use for middleware installation program temporary files
and extracted middleware installation images, and then click Next.
72
IBM SmartCloud Control Desk: Upgrade Guide
13. In the Deployment Plan Operation panel, select Deploy the plan, and then
click Next. You can also elect to change the deployment plan or parameters
you have previously configured from this panel.
14. In the Deployment Plan and Parameter Configuration summary panel, review
the contents of the summary. Click Deploy to initiate the installation and
configuration of the middleware you selected.
15. After the deployment completes successfully, click Finish to exit.
Migrate database or directory server data (optional)
Depending upon your environment, you might have to migrate database or
directory server data from the middleware servers used in your prior deployment
to new middleware servers.
If the middleware you used in your prior deployment is incompatible with
SmartCloud Control Desk 7.5, you can migrate data to a new server supported by
SmartCloud Control Desk 7.5.
If your existing database software is compatible with SmartCloud Control Desk 7.5,
you can use the existing database. If the existing database is not compatible, refer
to the documentation provided with your software for instructions on migrating
database objects. For DB2, this information can be found at http://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/
com.ibm.db2.luw.qb.upgrade.doc/doc/c0011933.html. Recall that if you performed
an upgrade of your database software, you are only required to migrate the
existing database instance (ctginst1) and database (maxdb71). If you installed a
new instance of the database software, you must complete additional configuration
tasks as described in the SmartCloud Control Desk 7.5 installation
information. Additional tasks include creating system users, creating a new
database instance, and modifying the maximo.properties file to update information
for the new server.
If you chose to use a directory server for security in your prior deployment and
you are required to migrate directory server information to comply with
SmartCloud Control Desk 7.5 prerequisites, consult the documentation provided
with your software for instructions on migrating. If you used IBM Tivoli Directory
Server in your prior deployment, no migration is required because the same
version of IBM Tivoli Directory Server is supported.
Running the SmartCloud Control Desk 7.5 installation program with
manual configuration.
Manually configure WebSphere Application Server Network Deployment v7.0 and
upgrade to SmartCloud Control Desk 7.5 .
About this task
In order to upgrade an existing SmartCloud Control Desk 7.2.1 deployment to
SmartCloud Control Desk 7.5 you first must migrate WebSphere Application Server
Network Deployment v6.1 configuration information to WebSphere Application
Server Network Deployment v7.0. You then run the SmartCloud Control Desk 7.5
installation program on the original SmartCloud Control Desk administrative
system. The SmartCloud Control Desk 7.5 installation program detects the existing
SmartCloud Control Desk deployment and guides you through the upgrade
process. You select the option to inform the installation program that you have
Chapter 8. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 using the middleware installation
program (Scenario 3)
73
already configured WebSphere Application Server Network Deployment v7.0 using
the middleware installation program. No automated configuration of WebSphere
Application Server Network Deployment v7.0 is performed by the SmartCloud
Control Desk 7.5 installation program.
If you encounter any errors related to the installation program during the upgrade,
refer to the installation information for troubleshooting details.
Before the upgrade, ensure that all SmartCloud Control Desk process managers are
at the expected level. Open a command prompt and issue the following command:
Install_Home\bin\solutioninstaller -action showinstalled -type all
To upgrade an existing SmartCloud Control Desk deployment to SmartCloud
Control Desk 7.5, complete the following steps:
Procedure
1. Log in to the administrative workstation using the administrative user ID
used in the previous deployment.
2. Copy the trust.p12 keystore file from the WebSphere_Install/profiles/
ctgDmgr01/etc directory of the WebSphere Application Server Network
Deployment v7.0 server to the administrative workstation. This step is not
necessary if WebSphere Application Server Network Deployment is hosted on
the administrative workstation system.
3. Start the SmartCloud Control Desk installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
b. In the launchpad navigation pane, click Install The Product.
c. Click Install IBM SmartCloud Control Desk 7.5.
Alternatively, you can start the SmartCloud Control Desk installation program
directly. Browse to the \Install\mam\ directory of the downloaded installation
image and run the following command
Windows
v install.bat
v install_win64.bat
4. Select a language for the installation and click OK.
5. In the Introduction panel, click Next.
6. In the Choose Installation folder panel, manually enter the install location of
the existing SmartCloud Control Desk 7.2.1 deployment to target it for an
upgrade.
7. Review the information presented in the Verify installation location panel, and
then click Next. The Verify installation location panel reports previous
installation information that was found based upon the installation directory
you chose in the previous panel. Once you advance past this panel, you
cannot go back and change the installation directory for this installation.
8. In the Package Summary panel, review the package deployment actions, and
then click Next. This panel lists version information for both new and existing
packages on the system. Target package version information indicates the
package version being currently deployed.
74
IBM SmartCloud Control Desk: Upgrade Guide
9. The SmartCloud Control Desk program license agreement window is
displayed. Read the license information and select I accept both the IBM and
the non-IBM terms if you agree with the terms. Click Next.
10. In the Database Upgrade panel, review the prerequisite database task
information. Select the option indicating that you have performed the
prerequisite database tasks, and then click Next.
11. In the Import Middleware Configuration Information panel, clear the selection
for the Import middleware configuration information option. Click Next.
12. In the Automate WebSphere Configuration panel, clear the option for
automating WebSphere Application Server Network Deployment
configuration, and then click Next. Configuration of WebSphere Application
Server Network Deployment v7.0 was performed when you migrated
configuration information from WebSphere Application Server Network
Deployment v6.1 using the middleware installation program. Ensure the
domain and node managers are started before proceeding.
13. In the WebSphere Connectivity panel, enter host information about the
WebSphere Application Server Network Deployment, and then click Next.
Host name
Enter the fully qualified host name of the system hosting WebSphere
Application Server Network Deployment.
Alternatively, you can provide the IP address for the system.
SOAP port
Enter the SOAP port of the WebSphere Application Server Network
Deployment system.
The default value for this field is 8879.
User ID
Enter the administrative user ID used to access the WebSphere
Application Server Network Deployment Server.
Default for all platforms is wasadmin.
Password
Enter the password for the administrative user ID used to access the
WebSphere Application Server Network Deployment Server.
In IP v6 environments, you are also prompted to provide the RMI bootstrap
port.
14. In the WebSphere Application Server Network Deployment Configuration
panel, enter the following information, and then click Next.
Web server port
Enter the web server port used by WebSphere Application Server
Network Deployment.
Default for all platforms is 80.
This value should match an existing HTTP server port value you
configured when you set up WebSphere Application Server Network
Deployment. If you enter a different value for this port, you must
restart WebSphere Application Server Network Deployment at the
conclusion of the installation. Restarting the server activates the new
port, making it available for incoming requests.
Web server name
Enter the name of the web server.
Chapter 8. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 using the middleware installation
program (Scenario 3)
75
Default for all platforms is webserver1.
Node name
Enter the name of the WebSphere Application Server Network
Deployment node containing the application server.
Default for all platforms is ctgNode01.
Application server
Enter the name of the WebSphere Application Server Network
Deployment application server to associate with SmartCloud Control
Desk.
Default for all platforms is MXServer. This value can be customized.
The application server is created if it does not exist.
15. In the Integration Adapter JMS Configuration panel, enter the following
information, and then click Next. A JMS server requires a DB2 data repository
to be configured to maintain messages. If you are using another database
type, you cannot have the installation program configure message persistence.
JMS Data Source name
Enter the name of the database to be used by JMS.
If you are using Microsoft SQL Server, this field is pre-populated. If it
is not, enter intjmsds.
Select whether the JMS data store should be persisted.
Persist JMS messages
Select this option to enable the SmartCloud Control Desk
installation program to set the JMS implementation to persist
messages within DB2.
Do not persist JMS messages
If you select this option, the SmartCloud Control Desk
installation program does not set the JMS implementation to
persist messages automatically in DB2. You can configure the
JMS implementation manually at a later date. If you select this
option, when you click Next, the installation wizard skips to
the panel to configure SMTP.
Select this option if you are deploying SmartCloud Control
Desk with Oracle or Microsoft SQL Server.
16. If you chose to persist JMS messages, in the DB2 Database Server
Configuration panel, enter the following information, and then click Next. If
you chose not to persist JMS messages you do not see this panel.
Note: The JMS data store can only be created as a DB2 database.
Host name
Enter the fully qualified host name of the server hosting the JMS data
store.
Alternatively, you can provide the IP address for the system.
Port
Enter the port used to access the database server.
Default for all platforms is 50005.
Database name
Enter the name of the database serving as the JMS data store.
Default for all platforms is maxsibdb.
76
IBM SmartCloud Control Desk: Upgrade Guide
User ID
Enter the user ID used to access the database server.
Default for all platforms is maximo.
Password
Enter the password for the user ID used to access the database server.
17. In the WebSphere Application Server Network Deployment keystore file panel,
browse to where you copied the trust.p12 keystore file, and then click Next.
18. On the Data Integration Services and Context Menu Service Deployment
Options panel, specify a deployment option. If you deployed a separate
database for Data Integration Services and Context Menu Service in your prior
deployment, select Configure data integration and context menu services for
this product using a previously deployed data integration and context menu
service instance to use that previously deployed database. Otherwise, select
Deploy data integration and context menu services into the same database
that you created for the product to use the SmartCloud Control Desk
database for the Data Integration Services and Context Menu Service. The
Data Integration Services and Context Menu Service allow products to register
themselves to offer launch in context to all other registered products and to
gain launch access to all other registered products. This ability is provided
without unique product-to-product integration efforts. Refer to the product
information center for more information about configuring cross-product
launch points.
19. If you have not previously configured the following parameters for your
SmartCloud Control Desk 7.2.1 deployment, you are prompted to supply
SMTP configuration information. In the SMTP Configuration panel, specify
SMTP configuration information used by workflows to communicate with
workflow participants.
SMTP server
Enter the fully qualified host name of the SMTP server that sends
messages to participants.
Alternatively, you can provide the IP address for the system.
Administrator e-mail
Enter a valid e-mail address. This address is used to send messages.
You can defer SMTP configuration at this time by not providing any
information and clicking through to the next panel. However, you must
configure these parameters through the product interface as a post installation
task.
20. From the Run Configuration Step panel, click Next.
21. From the input summary panel, verify that the values displayed are the ones
used in your existing SmartCloud Control Desk deployment, and then click
Next.
22. From the Pre-Installation Summary panel, review the install summary values,
and then click Install.
The upgrade process begins copying files to your local system.
23. Click Finish to exit the installation program.
Installing optional content and integration modules
You might want to add optional content to your environment, or integrate with
other products.
Chapter 8. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 using the middleware installation
program (Scenario 3)
77
About this task
Optional content is often used in development environments as a way to begin
developing your own content. The Reference section of the product information
center contains a detailed description of the optional content that you can install
from the product launchpad. If you do not install optional content during the
product upgrade process, you can install it later. If you install it later, you must
update the database and rebuild and deploy the maximo.ear file.
If you had optional content installed in your prior deployment, you must install
the new optional content to replace it. The database cannot be updated if it
contains content from prior releases.
You can install integration modules to help you integrate SmartCloud Control Desk
applications with other products. If you do not install integration modules during
the product upgrade process, you can install them later. If you install them later,
you must update the database and rebuild and deploy the maximo.ear file.
Procedure
1. Restart the launchpad.
2. To install optional content, use the link in the navigation area to open the
Optional Content page of the launchpad.
3. Click the link to install optional content. The product installer is launched.
4. Follow the screens through the installer. If check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes.
5. Click Finish to exit the installation program.
6. To install optional integrations, restart the launchpad. Use the link in the
navigation area to open the Integrations page of the launchpad.
7. Click the link for each integration that you want to install. The product installer
is launched.
8. Follow the screens through the installer. If check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes.
9. Click Finish to exit the installation program.
Migrate customizations
Customizations you made in your prior deployment are not migrated
automatically to your new environment.
About this task
When you installed SmartCloud Control Desk 7.5, your prior deployment was
preserved in a directory called pre_75_maximo, located in the C:\IBM\SMP
directory. You must migrate your customizations archived in the pre_75_maximo
directory to the installation directories of the current SmartCloud Control Desk 7.5
deployment.
Procedure
1. Compile custom Java code using the JDK 1.6 compiler. Custom Java classes that
were created for your prior deployment were likely compiled using JDK 1.5,
which was provided with previous product versions. Custom Java code must
78
IBM SmartCloud Control Desk: Upgrade Guide
2.
3.
4.
5.
be recompiled using the JDK 1.6 compiler supplied with SmartCloud Control
Desk 7.5 in the C:\IBM\SMP\sdk\bin folder, or any supported 1.6 JDK.
a. Locate custom Java source files in subdirectories of the pre_75_maximo
archive directory.
b. Compile source into Java class files using JDK 1.6.
c. Move recompiled class files into the appropriate SmartCloud Control Desk
7.5 directory. Typically this is the same directory under SmartCloud Control
Desk 7.5 as it was in your prior deployment.
Identify customizations that were made to default JSP, XML, HTML, CSS or
XSLT files in your prior deployment. These customizations of default files must
be recreated in the SmartCloud Control Desk 7.5 versions of these files. You can
find the customized files in the pre_75_maximo archive directory. You cannot
overwrite SmartCloud Control Desk 7.5 files with modified versions of default
files from your prior deployment found in the pre_75_maximo directory.
Customizations must be reapplied to the SmartCloud Control Desk 7.5 versions
of these default files.
Copy or move any custom JSP, XML, HTML, CSS or XSLT files you created to
work with your prior deployment.
For any changes made to Applet extensions, move the compiled code into the
appropriate folders on the SmartCloud Control Desk 7.5 installation directory.
Ensure that you build the Applet Jars from the SmartCloud Control Desk 7.5
folders.
Copy or move any customized report files from the pre_75_maximo directory
structure to the appropriate SmartCloud Control Desk 7.5 folder. These report
files need to be imported into the database after the upgrade process is
complete, as describe in the post-upgrade information.
6. Move any custom configuration files (.properties and .xml) that contain
extensions defined for SmartCloud Control Desk 7.5. Product XML files can be
found in the \maximo\applications\maximo\properties\product folder. If
customizations were made to default configuration files in your prior
deployment, you must replicate those changes in the SmartCloud Control Desk
7.5 versions of those files.
7. Copy or move the webclient.properties file from the pre_75_maximo directory
structure to the \maximo\applications\maximo\properties\product folder of the
SmartCloud Control Desk 7.5 installation.
8. Copy or move any third-party libraries used with the previous release from the
pre_75_maximo directory structure to the appropriate SmartCloud Control Desk
7.5 folder. Consult the information provided with your third-party libraries to
verify that no further configuration tasks are required.
Running the installation program to update the database
Run the installation program a final time to update the database and perform final
deployment steps.
About this task
The SmartCloud Control Desk 7.5 installation program is run a final time to have it
perform actions skipped on previous invocations. These actions can include
running updatedb, running TDToolkit, and building and deploying EAR files. The
installer will not repeat steps that you have already run.
Chapter 8. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 using the middleware installation
program (Scenario 3)
79
Procedure
1. Start the SmartCloud Control Desk installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
b. In the launchpad navigation pane, click Install The Product.
c. Click Install IBM SmartCloud Control Desk 7.5.
Alternatively, you can start the SmartCloud Control Desk installation program
directly. Browse to the \Install\product_abbreviation\ directory of the
downloaded installation image and run the following command
Windows
v install.exe
2.
3.
4.
5.
6.
v install_win64.exe
Select a language for the installation and click OK.
In the Introduction panel, click Next.
In the Choose Installation folder panel, use the drop-down menu to choose
the folder where you have begun the upgrade.
Review the information presented in the Verify installation location panel, and
then click Next.
In the Package Summary panel, review the package deployment actions, and
then click Next.
7. From the Run Configuration Step panel, clear the check boxes for all options,
and then click Next. If you allow the installation program to perform these
steps, you do not have to complete them manually. If you prefer to deploy
the EAR files to your J2EE server manually after the installer has created
them, check the box for "Deploy application files manually later."
8. From the input summary panel, verify that the values displayed are the ones
used in your existing SmartCloud Control Desk deployment, and then click
Next.
9. From the Pre-Installation Summary panel, review the install summary values,
and then click Install. The installation program performs the following tasks
that remain for the upgrade:
v Run updatedb. This commits data for SmartCloud Control Desk 7.5, and
any other products or add-ons that you have upgraded, to the Maximo
database.
v Run TDToolkit to load languages for SmartCloud Control Desk 7.5.
v Build application EAR files.
v Deploy application EAR files.
10. Click Finish to exit the installation program.
Run integrity checker 7.5
Run the SmartCloud Control Desk 7.5 integrity checker utility.
About this task
Before proceeding further with the SmartCloud Control Desk 7.5 upgrade process,
you need to run the SmartCloud Control Desk 7.5 Integrity Checker utility to
confirm the integrity of the SmartCloud Control Desk 7.5 database after the
80
IBM SmartCloud Control Desk: Upgrade Guide
upgrade steps have been completed. When run in Report mode, the integrity
checker utility checks the current database and reports on common errors. If the
Integrity Checker reports an error, you must resolve it by running the Integrity
Checker in Repair mode.
Procedure
1. Stop the application server. For example, MXServer.
2. From the administrative workstation of the existing deployment, open a
command prompt and change directory to the maximo tools directory. For
example, c:\ibm\SMP\maximo\tools\maximo
3. Start the Integrity Checker tool.
integrityui.bat
4. Select the Check Integrity tab.
5. Run the Integrity Checker in Report mode.
a. Ensure that the Repair Mode? check box is cleared, and then click Run
Integrity Checker.
b. When the report dialog box appears, click OK.
Results are found in the install dir\maximo\tools\maximo\log directory in the
file defined in the Log File Name field of the Check Integrity panel.
6. Optional: If any errors are reported, run the Integrity Checker in Repair mode.
a. Select the Repair Mode? check box, and then click Run Integrity Checker.
b. When the report dialog box appears, click OK.
7. Optional: If Integrity Checker was run in Repair mode, check the log file to
ensure all reported items have been repaired. If further manual intervention is
required, you must resolve the errors and then rerun the Integrity Checker in
Report mode. Repeat the process until no more errors are reported.
Results
While the Integrity Checker can repair many issues, you might have to resolve
some errors manually by consulting the log files.
Chapter 8. Upgrading by migrating WebSphere v6.1 configuration information to WebSphere v7.0 using the middleware installation
program (Scenario 3)
81
82
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 9. Upgrading on Oracle WebLogic Server (Scenario 4)
Use this information to upgrade products that have been deployed on Oracle
WebLogic Server.
About this task
This information provides a high-level overview or road map of tasks you need to
complete in order to upgrade to SmartCloud Control Desk 7.5 in a Oracle
WebLogic Server environment.
In this scenario, you upgrade your existing products in a Oracle WebLogic Server
environment.
This scenario assumes you have customizations from your prior deployment that
you want to migrate to SmartCloud Control Desk 7.5.
Procedure
1. Perform pre-upgrade tasks
2. Run the Integrity Checker from your existing environment in Report mode.
Tasks
“Run Integrity Checker” on page 14
3. Establish supported middleware
You must establish in your environment a version of Oracle WebLogic Server
that is supported by SmartCloud Control Desk 7.5. The versions of Oracle
WebLogic Server that were supported by your prior deployment are not
compatible with SmartCloud Control Desk 7.5.
If necessary, upgrade your database software to a supported version using the
installation program for that software.
If necessary, upgrade your directory server software to a supported version
using the installation program for that software. Refer to the documentation
provided with your product for upgrade information.
Concepts
“Establish supported middleware” on page 84
4. Manually configure Oracle WebLogic Server. Oracle WebLogic Server
configuration tasks are described in the SmartCloud Control Desk7.5
installation information.
Concepts
“Configure WebLogic” on page 85
5. Optional: Migrate the database or directory server data, if necessary.
Concepts
“Migrate database or directory server data (optional)” on page 32
6. Run the SmartCloud Control Desk 7.5 installation program.
In this step the installation program copies files onto the administrative
workstation and runs the configuration step, but updatedb is deferred.
Tasks
“Running the installation program to update the database” on page 89
7. Migrate customizations from your prior deployment.
© Copyright IBM Corp. 2012
83
When you upgraded to SmartCloud Control Desk 7.5, data from your prior
deployment was preserved in a directory called pre_75_maximo, located in the
installation directory, which, by default, is C:\IBM\SMP. You must migrate your
customizations archived in the pre_75_maximo directory to the installation
directories of the current SmartCloud Control Desk 7.5 deployment.
Tasks “Migrate customizations” on page 40
8. Run the SmartCloud Control Desk 7.5 installation program to automate the
steps to upgrade the database.
The SmartCloud Control Desk 7.5 installation program is run a second time to
have it perform actions skipped the first time. For example, running updatedb
and running TDToolkit.
Tasks “Running the installation program to update the database” on page 89
9. Run SmartCloud Control Desk 7.5 Integrity Checker
Run the Integrity Checker tool in Report mode. If the Integrity Checker
reports an error, you must resolve it.
Tasks “Run integrity checker 7.5” on page 90
10. Deploy applications.
The Maximo and Maximo help applications must be deployed manually.
Tasks
“Deploy application files to Oracle WebLogic Server” on page 91
11. Perform post-upgrade tasks
Concepts
Chapter 11, “Post-upgrade tasks,” on page 97
Tasks
v “Reviewing your upgraded screens” on page 103
v “Reviewing table domains and crossover domains” on page 104
v “Updating BIRT reports” on page 104
v “Updating statistics” on page 105
Establish supported middleware
Establish middleware in your environment that is compatible with SmartCloud
Control Desk 7.5.
The first step in a SmartCloud Control Desk 7.5 upgrade is to establish middleware
in your environment that is supported by SmartCloud Control Desk 7.5. In some
cases, middleware you used in the SmartCloud Control Desk 7.2.1 deployment can
be reused for the SmartCloud Control Desk 7.5 upgrade. In other cases, you might
have to use new middleware servers that were not part of the original SmartCloud
Control Desk 7.2.1 deployment.
You need to install or otherwise establish a supported version of Oracle WebLogic
Server. Versions of Oracle WebLogic Server that were supported in SmartCloud
Control Desk 7.2.1 are not supported in SmartCloud Control Desk 7.5. Refer to the
documentation provided with Oracle WebLogic Server for installation and upgrade
information.
If necessary, upgrade database software to a version supported by SmartCloud
Control Desk 7.5. Upgrading the existing database software is the preferred
method of establishing a SmartCloud Control Desk 7.5 supported database. This
method allows you to reuse data such as user IDs and database instances. In some
84
IBM SmartCloud Control Desk: Upgrade Guide
cases, you might be forced to install a new instance of the database software. For
example, your prior deployment might include a database server that is
established on a platform that is no longer supported in SmartCloud Control Desk
7.5, as could be the case with 32-bit platforms. In this scenario, you would install a
fresh instance of the database software compatible with SmartCloud Control Desk
7.5. For DB2, you could install this software using the SmartCloud Control Desk
7.5 middleware installation program. If you install new instances of database
software outside of the middleware installation program, you would have to
perform additional manual configuration tasks that are described in the
SmartCloud Control Desk 7.5 installation information. In addition, you would have
to migrate the database from the old server to the new server.
If necessary, upgrade directory server software to a version supported by
SmartCloud Control Desk 7.5. Refer to the documentation provided with your
product for upgrade information.
Configure WebLogic
You must configure a supported version of Oracle WebLogic Server for
SmartCloud Control Desk 7.5.
Oracle WebLogic Server configuration tasks are described in the SmartCloud
Control Desk7.5 installation information. Complete the Oracle WebLogic Server
configuration tasks described for SmartCloud Control Desk 7.5.
Migrate database or directory server data (optional)
Depending upon your environment, you might have to migrate database or
directory server data from the middleware servers used in your prior deployment
to new middleware servers.
If the middleware you used in your prior deployment is incompatible with
SmartCloud Control Desk 7.5, you can migrate data to a new server supported by
SmartCloud Control Desk 7.5.
If your existing database software is compatible with SmartCloud Control Desk 7.5,
you can use the existing database. If the existing database is not compatible, refer
to the documentation provided with your software for instructions on migrating
database objects. For DB2, this information can be found at http://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/
com.ibm.db2.luw.qb.upgrade.doc/doc/c0011933.html. Recall that if you performed
an upgrade of your database software, you are only required to migrate the
existing database instance (ctginst1) and database (maxdb71). If you installed a
new instance of the database software, you must complete additional configuration
tasks as described in the SmartCloud Control Desk 7.5 installation
information. Additional tasks include creating system users, creating a new
database instance, and modifying the maximo.properties file to update information
for the new server.
If you chose to use a directory server for security in your prior deployment and
you are required to migrate directory server information to comply with
SmartCloud Control Desk 7.5 prerequisites, consult the documentation provided
with your software for instructions on migrating. If you used IBM Tivoli Directory
Server in your prior deployment, no migration is required because the same
version of IBM Tivoli Directory Server is supported.
Chapter 9. Upgrading on Oracle WebLogic Server (Scenario 4)
85
Running the SmartCloud Control Desk 7.5 installation program with
manual configuration
Upgrade to SmartCloud Control Desk 7.5 on Oracle WebLogic Server.
About this task
In order to upgrade an existing deployment to SmartCloud Control Desk 7.5 on
Oracle WebLogic Server, you must manually configure Oracle WebLogic Server
before running the SmartCloud Control Desk 7.5 installation program.
If you encounter any errors related to the installation program during the upgrade,
refer to the installation information for troubleshooting details.
To upgrade an existing SmartCloud Control Desk deployment to SmartCloud
Control Desk 7.5, complete the following steps:
Procedure
1. Log in to the administrative workstation using the administrative user ID
used in the previous deployment.
2. Start the SmartCloud Control Desk installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
b. In the launchpad navigation pane, click Install The Product.
c. Click Install IBM SmartCloud Control Desk 7.5.
Alternatively, you can start the SmartCloud Control Desk installation program
directly. Browse to the \Install\mam\ directory of the downloaded installation
image and run the following command
Windows
v install.bat
v install_win64.bat
3. Select a language for the installation and click OK.
4. In the Introduction panel, click Next.
5. In the Choose Installation folder panel, enter the install location of your prior
deployment to target it for an upgrade.
6. Review the information presented in the Verify installation location panel, and
then click Next. The Verify installation location panel reports previous
installation information that was found based upon the installation directory
you chose in the previous panel. Once you advance past this panel, you
cannot go back and change the installation directory for this installation.When
you click Next, the installation program performs some pre-installation
processing to ensure that the Deployment Engine is ready to run the upgrade.
A progress bar for this activity is displayed.
7. In the Package Summary panel, review the package deployment actions, and
then click Next. This panel lists version information for both new and existing
packages on the system. Target package version information indicates the
package version being currently deployed.
86
IBM SmartCloud Control Desk: Upgrade Guide
8.
9.
10.
11.
Note: If you had optional content installed with any of the prior products, the
package analysis shows that the current level of the content packages does not
support the level of process automation engine being installed. In this case
you must install the optional content package from the launchpad before you
update the database. A check box is displayed below the table, with a
statement saying that you understand that you must apply additional
updates. Check this box and click Next.
The SmartCloud Control Desk program license agreement window is
displayed. Read the license information and select I accept the terms in the
license agreement. if you agree with the terms. Click Next.
In the Database Upgrade panel, review the prerequisite database task
information. Select the option indicating that you have performed the
prerequisite database tasks, and then click Next.
On the Data Integration Services and Context Menu Service Deployment
Options panel, specify a deployment option. If you deployed a separate
database for Data Integration Services and Context Menu Service in your prior
deployment, select Configure data integration and context menu services for
this product using a previously deployed data integration and context menu
service instance to use that previously deployed database. Otherwise, select
Deploy data integration and context menu services into the same database
that you created for the product to use the SmartCloud Control Desk
database for the Data Integration Services and Context Menu Service. The
Data Integration Services and Context Menu Service allow products to register
themselves to offer launch in context to all other registered products and to
gain launch access to all other registered products. This ability is provided
without unique product-to-product integration efforts. Refer to the product
information center for more information about configuring cross-product
launch points.
If you have not previously configured the following parameters for your prior
deployment, you are prompted to supply SMTP configuration information. In
the SMTP Configuration panel, specify SMTP configuration information used
by workflows to communicate with workflow participants.
SMTP server
Enter the fully qualified host name of the SMTP server that sends
messages to participants.
Alternatively, you can provide the IP address for the system.
Administrator e-mail
Enter a valid e-mail address. This address is used to send messages.
You can defer SMTP configuration at this time by not providing any
information and clicking through to the next panel. However, you must
configure these parameters through the product interface as a post installation
task.
12. From the Run Configuration Step panel, click Next.
13. From the input summary panel, verify that the values displayed are the ones
used in your existing SmartCloud Control Desk deployment, and then click
Next.
14. From the Pre-Installation Summary panel, review the install summary values,
and then click Install.
The upgrade process begins copying files to your local system.
15. Click Finish to exit the installation program.
Chapter 9. Upgrading on Oracle WebLogic Server (Scenario 4)
87
Installing optional content and integration modules
You might want to add optional content to your environment, or integrate with
other products.
About this task
Optional content is often used in development environments as a way to begin
developing your own content. The Reference section of the product information
center contains a detailed description of the optional content that you can install
from the product launchpad. If you do not install optional content during the
product upgrade process, you can install it later. If you install it later, you must
update the database and rebuild and deploy the maximo.ear file.
If you had optional content installed in your prior deployment, you must install
the new optional content to replace it. The database cannot be updated if it
contains content from prior releases.
You can install integration modules to help you integrate SmartCloud Control Desk
applications with other products. If you do not install integration modules during
the product upgrade process, you can install them later. If you install them later,
you must update the database and rebuild and deploy the maximo.ear file.
Procedure
1. Restart the launchpad.
2. To install optional content, use the link in the navigation area to open the
Optional Content page of the launchpad.
3. Click the link to install optional content. The product installer is launched.
4. Follow the screens through the installer. If check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes.
5. Click Finish to exit the installation program.
6. To install optional integrations, restart the launchpad. Use the link in the
navigation area to open the Integrations page of the launchpad.
7. Click the link for each integration that you want to install. The product installer
is launched.
8. Follow the screens through the installer. If check boxes are presented that say
"Deploy application files manually later" and Defer the Update of the Maximo
Database," check these boxes.
9. Click Finish to exit the installation program.
Migrate customizations
Customizations you made in your prior deployment are not migrated
automatically to your new environment.
About this task
When you installed SmartCloud Control Desk 7.5, your prior deployment was
preserved in a directory called pre_75_maximo, located in the C:\IBM\SMP
directory. You must migrate your customizations archived in the pre_75_maximo
directory to the installation directories of the current SmartCloud Control Desk 7.5
deployment.
88
IBM SmartCloud Control Desk: Upgrade Guide
Procedure
1. Compile custom Java code using the JDK 1.6 compiler. Custom Java classes that
were created for your prior deployment were likely compiled using JDK 1.5,
which was provided with previous product versions. Custom Java code must
be recompiled using the JDK 1.6 compiler supplied with SmartCloud Control
Desk 7.5 in the C:\IBM\SMP\sdk\bin folder, or any supported 1.6 JDK.
a. Locate custom Java source files in subdirectories of the pre_75_maximo
archive directory.
b. Compile source into Java class files using JDK 1.6.
c. Move recompiled class files into the appropriate SmartCloud Control Desk
7.5 directory. Typically this is the same directory under SmartCloud Control
Desk 7.5 as it was in your prior deployment.
2. Identify customizations that were made to default JSP, XML, HTML, CSS or
XSLT files in your prior deployment. These customizations of default files must
be recreated in the SmartCloud Control Desk 7.5 versions of these files. You can
find the customized files in the pre_75_maximo archive directory. You cannot
overwrite SmartCloud Control Desk 7.5 files with modified versions of default
files from your prior deployment found in the pre_75_maximo directory.
Customizations must be reapplied to the SmartCloud Control Desk 7.5 versions
of these default files.
3. Copy or move any custom JSP, XML, HTML, CSS or XSLT files you created to
work with your prior deployment.
4. For any changes made to Applet extensions, move the compiled code into the
appropriate folders on the SmartCloud Control Desk 7.5 installation directory.
Ensure that you build the Applet Jars from the SmartCloud Control Desk 7.5
folders.
5. Copy or move any customized report files from the pre_75_maximo directory
structure to the appropriate SmartCloud Control Desk 7.5 folder. These report
files need to be imported into the database after the upgrade process is
complete, as describe in the post-upgrade information.
6. Move any custom configuration files (.properties and .xml) that contain
extensions defined for SmartCloud Control Desk 7.5. Product XML files can be
found in the \maximo\applications\maximo\properties\product folder. If
customizations were made to default configuration files in your prior
deployment, you must replicate those changes in the SmartCloud Control Desk
7.5 versions of those files.
7. Copy or move the webclient.properties file from the pre_75_maximo directory
structure to the \maximo\applications\maximo\properties\product folder of the
SmartCloud Control Desk 7.5 installation.
8. Copy or move any third-party libraries used with the previous release from the
pre_75_maximo directory structure to the appropriate SmartCloud Control Desk
7.5 folder. Consult the information provided with your third-party libraries to
verify that no further configuration tasks are required.
Running the installation program to update the database
Run the installation program a final time to update the database and perform final
deployment steps.
About this task
The SmartCloud Control Desk 7.5 installation program is run a final time to have it
perform actions skipped on previous invocations. These actions can include
Chapter 9. Upgrading on Oracle WebLogic Server (Scenario 4)
89
running updatedb, running TDToolkit, and building EAR files. The installer will
not repeat steps that you have already run.
Procedure
1. Start the SmartCloud Control Desk installation program from the launchpad.
a. Start the launchpad. Browse to the root directory of the downloaded
installation image, and run the following command:
Windows
launchpad.exe
b. In the launchpad navigation pane, click Install The Product.
c. Click Install IBM SmartCloud Control Desk 7.5.
Alternatively, you can start the SmartCloud Control Desk installation program
directly. Browse to the \Install\product_abbreviation\ directory of the
downloaded installation image and run the following command
Windows
v install.exe
v install_win64.exe
2. Select a language for the installation and click OK.
3. In the Introduction panel, click Next.
4. In the Choose Installation folder panel, use the drop-down menu to choose
the folder where you have begun the upgrade.
5. Review the information presented in the Verify installation location panel, and
then click Next.
6. In the Package Summary panel, review the package deployment actions, and
then click Next.
7. From the Run Configuration Step panel, clear the check boxes for all options,
and then click Next. If you allow the installation program to perform these
steps, you do not have to complete them manually.
8. From the input summary panel, verify that the values displayed are the ones
used in your existing SmartCloud Control Desk deployment, and then click
Next.
9. From the Pre-Installation Summary panel, review the install summary values,
and then click Install. The installation program performs the following tasks
that remain for the upgrade:
v Run updatedb. This commits data for SmartCloud Control Desk 7.5, and
any other products or add-ons that you have upgraded, to the Maximo
database.
v Run TDToolkit to load languages for SmartCloud Control Desk 7.5.
v Build application EAR files.
10. Click Finish to exit the installation program.
Run integrity checker 7.5
Run the SmartCloud Control Desk 7.5 integrity checker utility.
About this task
Before proceeding further with the SmartCloud Control Desk 7.5 upgrade process,
you need to run the SmartCloud Control Desk 7.5 Integrity Checker utility to
confirm the integrity of the SmartCloud Control Desk 7.5 database after the
90
IBM SmartCloud Control Desk: Upgrade Guide
upgrade steps have been completed. When run in Report mode, the integrity
checker utility checks the current database and reports on common errors. If the
Integrity Checker reports an error, you must resolve it by running the Integrity
Checker in Repair mode.
Procedure
1. Stop the application server. For example, MXServer.
2. From the administrative workstation of the existing deployment, open a
command prompt and change directory to the maximo tools directory. For
example, c:\ibm\SMP\maximo\tools\maximo
3. Start the Integrity Checker tool.
integrityui.bat
4. Select the Check Integrity tab.
5. Run the Integrity Checker in Report mode.
a. Ensure that the Repair Mode? check box is cleared, and then click Run
Integrity Checker.
b. When the report dialog box appears, click OK.
Results are found in the install dir\maximo\tools\maximo\log directory in the
file defined in the Log File Name field of the Check Integrity panel.
6. Optional: If any errors are reported, run the Integrity Checker in Repair mode.
a. Select the Repair Mode? check box, and then click Run Integrity Checker.
b. When the report dialog box appears, click OK.
7. Optional: If Integrity Checker was run in Repair mode, check the log file to
ensure all reported items have been repaired. If further manual intervention is
required, you must resolve the errors and then rerun the Integrity Checker in
Report mode. Repeat the process until no more errors are reported.
Results
While the Integrity Checker can repair many issues, you might have to resolve
some errors manually by consulting the log files.
Deploy application files to Oracle WebLogic Server
When you deploy SmartCloud Control Desk 7.5 on Oracle WebLogic Server, you
must deploy application EAR files manually.
About this task
Deploy the Maximo and Maximo help applications on Oracle WebLogic Server.
Procedure
1. Start the Oracle WebLogic Server Administration Console.
2. Log in to the administrative console with the administrative user name and
password.
3. In the left pane, click the Lock&Edit button in the Change Center section to
set the server to edit mode.
4. In the left pane, click the Deployments link in the Domain Structure section.
5. In the Summary of Deployments section, click the Install button. The Install
Application Assistant opens.
6. Click the upload your file(s) link.
Chapter 9. Upgrading on Oracle WebLogic Server (Scenario 4)
91
7. Click the Browse button next to the Deployment Archive field. Browse to
where you have maximo.ear file installed, select the file and click Open.
8. Click Next to upload the file to the Oracle WebLogic Server server.
9. Click the radio button next to the maximo.ear file, and Next to continue the
deployment.
10. Accept the default value “Install this deployment as an application” and click
Next to continue the deployment.
11. Accept all other default values and click Finish to start the deployment
process.
12. When the deployment process is complete, click the Activate Changes button
in the Change Center to apply the changes. The following message displays:
All changes have been activated. No restarts are necessary.
13. Click the upload your file(s) link.
14. Click the Browse button next to the Deployment Archive field. Browse to
where you have maximoiehs.ear file installed, select the file and click Open.
15. Click Next to upload the file to the Oracle WebLogic Server server.
16. Click the radio button next to the maximoiehs.ear file, and Next to continue
the deployment.
17. Accept the default value “Install this deployment as an application” and click
Next to continue the deployment.
18. Accept all other default values and click Finish to start the deployment
process.
19. When the deployment process is complete, click the Activate Changes button
in the Change Center to apply the changes. The following message displays:
All changes have been activated. No restarts are necessary.
20. Click the checkboxes next to the maximo and maximo help applications.
21. Click the dropdown arrow of the Start button and select Servicing all
requests. The Start Application Assistant displays.
22. Click Yes to start the system.
92
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 10. Upgrading your VM image
Use this procedure to upgrade your Tivoli Service Manager Quick Install
installation to the IBM SmartCloud Control Desk VMImage deployment model.
About this task
If you have installed Tivoli Service Manager Quick Install, you can upgrade your
VM image to the IBM SmartCloud Control Desk VMImage. You cannot upgrade
Tivoli Service Manager Quick Install to a SmartCloud Control Desk enterprise
installment.
Procedure
1. Obtain the appropriate product images or DVDs.
2. Install WebSphere Application Server, version 7 on your VM image, and
migrate the configuration from version 6.1 to version 7.
3. Replace the installer's derby jar files. The current jar files are corrupt and will
cause the installer to fail. These jar files are part of the Deployment Engine
component of the installer.
a. Stop the IBM ACSI Service:
cd /usr/ibm/common/acsi/bin
./acsisrv.sh -stop
b. Copy the four derby jar files from the Derby directory on the product
image into the /usr/ibm/common/acsi/lib directory. derby.jar,
derbyclient.jar, derbynet.jar, derbytools.jar.
c. Restart the IBM ACSI Service:
cd /usr/ibm/common/acsi/bin
./acsisrv.sh -start
d. Verify that the installer is working properly:
cd /opt/IBM/SMP/bin/
./solutionInstaller.sh -action showinstalled -type all
This command displays a list of the installed packages, with a message
similar to this:
CTGIN0059I: There are currently "69" installed process solution
element packages that matched the specified criteria.
4. There is an existing installer package on the system that will prevent the
upgrade from occurring. You must remove this package before you proceed.
Substitute your userids and passwords into the following command:
cd /opt/IBM/SMP/bin
./solutionInstaller.sh -action uninstall
-pkguuid 2F1AF50386C04D749A4A9DAE8D3AE1B0
-dbuser <dbuser> -dbpwd <dbpassword>
-wasuser <was admin user> -waspwd <was admin password>
-wasrxauser <OS user> -wasrxapwd <OS user password>
You will see output similar to:
CTGIN0055I: The process solution installation client received
the following command:
"-action uninstall -pkguuid 2F1AF50386C04D749A4A9DAE8D3AE1B0
-dbuser maximo -dbpwd
****** -wasuser wasadmin -waspwd ****** -wasrxauser administrator
© Copyright IBM Corp. 2012
93
-wasrxapwd ******** ".
CTGIN0054I: The command is correctly formed and will be sent
to the process solution installation service.
CTGIN0145I: Initializing Deployment Engine Runtime environment.
CTGIN0148I: Deployment Engine is performing a system check
to ensure all requirements are satisfied.
CTGIN0147I: Deployment Engine is resolving the topology.
CTGIN0147I: Deployment Engine is resolving the topology.
CTGIN0149I: Deployment Engine is running the actions associated
with this Change Request.
CTGIN0123I: The process solution package that was being processed
does not support the "-dbpwd" parameter.
CTGIN0123I: The process solution package that was being processed
does not support the "-dbuser" parameter.
CTGIN0123I: The process solution package that was being processed
does not support the "-loadlanguages" parameter.
CTGIN0087I: The request passed the system check.
CTGIN0184I: Processing change operation "1" of "1". Change Operation:
"Delete" Software Component: "MBS7115_HotFix_IU" Version: "7115.20091028.1150" .
CTGIN0150I: Deployment Engine is updating the registry of
installed software components.
CTGIN0169W: Actions associated with the uninstall of the package
with the unique identifier 2F1AF50386C04D749A4A9DAE8D3AE1B0 completed
successfully. Additional manual actions must be performed before the package
may be reinstalled.
5. Reset the heap size on the DB2 image and enter the specified commands. You
should see the messages listed under each command.
su ctginst1
db2 update db cfg for maxdb71 using stat_heap_sz automatic
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
db2 force applications all
DB20000I The FORCE APPLICATION command completed successfully.
DB21024I This command is asynchronous and may not be effective immediately.
db2stop
SQL1064N
DB2STOP processing was successful.
db2start
SQL1063N
DB2START processing was successful.
6. Extend the DB2 tablespace size.
7. Ensure that there is enough free space on the WebSphere instance to perform
the upgrade. One place to free up space is the WAS 61 backup directory that
is left over from the WebSphere 6.1 to version 7 migration. This backup
directory may be located in the /root directory.
8. Rebase the Tivoli Service Manager Quick Install user interface to a level that
can be properly upgraded to version 7.5. Copy the rebase files from the
Upgrade page on the product wiki at https://www.ibm.com/
developerworks/wikis/display/tivoli/SmartCloud+Control+Desk+-+Installing
%2C+Migrating+and+Upgrading. Then follow these steps:
unzip 7211rebase_build.zip, which contains 2 updatedb files.
Copy file 7211rebase.mxs to the $MAXIMO/tools/maximo/en/srmapp directory.
Copy file 7211rebase_1.db2 to the $MAXIMO/tools/maximo/en/srmapp directory.
cd /opt/IBM/SMP/maximo/tools/maximo/internal/
./runscriptfile.sh -csrmapp -f7211rebase
./runscriptfile.sh -csrmapp -f7211rebase_1
9. Stop the MXServer. Supply your values for the user and password.
cd /opt/IBM/WebSphere/AppServer7.0/profiles/ctgAppSrv01/bin
./stopServer.sh MXServer -user <was admin user> -password <was admin password>
94
IBM SmartCloud Control Desk: Upgrade Guide
10. Set the TEMP variable to opt/IBM/temp before running the installer so that
the installer has ample temporary working space. Set this variable in the
command prompt in which you will run the installer.
mkdir /opt/IBM/temp
export TEMP=/opt/IBM/temp
11. Use the product launchpad to start the installer. This is the first of two times
that you must run the installer. It recognizes that Tivoli Service Manager
Quick Install is already installed and begins the upgrade process. The installer
determines that the content packages that were installed with Tivoli Service
Manager Quick Install are not compatible with the new release, and presents a
panel titled Process automation engine notice, asking whether you want to
continue. Check the box that says that you want to continue the installation,
and click Next. Allow the installer to run to completion.
12. Start the launchpad again, and install the optional content that is delivered
with SmartCloud Control Desk. Defer the configuration of the database and
the deployment of the ear file.
13. Use the solution installer to install the Saas PMP. Run /ibm/SMP/bin/
solutionInstallerGUI.sh to install saas_7.5.0.0.zip, which is in the
/Install/extras folder on product media. Allow the installer to perform
database configuration and ear file deployment.
14. You must add a symbolic link between two directories. Log in to a command
prompt on the server on which the UI runs and issue these commands:
cd /opt/IBM/SMP/maximo/tools/maximo/pmsc
ln -s updateTool.properties updateTool72.properties
Results
This completes your upgrade to IBM SmartCloud Control Desk VMImage. Review
and complete the steps listed in Chapter 11, “Post-upgrade tasks,” on page 97.
Chapter 10. Upgrading your VM image
95
96
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 11. Post-upgrade tasks
There are several tasks to complete after you have successfully upgraded
SmartCloud Control Desk.
Once you have upgraded SmartCloud Control Desk, complete post-upgrade tasks
to conclude the upgrade.
Clear the browser cache
Before you log in to your upgraded system, clear your browser's cache.
If you have used your prior applications and have not cleared your browser cache,
the cache might include older javascript files that will not work on your upgraded
system. In that case you might see a blank white screen when you log in, and the
following message in your log file:
BMXAA8354E - User is not allowed to perform current action. Please contact system
administrator for additional details.
Be sure to clear your browser's cache, and close and restart your browser, before
you use the upgraded system.
Programmatically verifying that the installation was successful
After you have exited the SmartCloud Control Desk installation program without
encountering any errors, you can verify that the installation completed successfully.
The installation is programmatically verified through the use of post installation
validation utilities.
Before you begin
The JAVA_HOME environment variable must be set on the system before you can
use the verification utilities.
About this task
During installation, the SmartCloud Control Desk installation program performs a
simple health check. This health check consists of logging in to the application to
verify availability. This health check might not be sufficient to verify a successful
installation in all deployment scenarios. For example, if, during installation, you
select the option to deploy the application EAR file at a later date, this health
check cannot verify the installation. This simple health check is also insufficient for
verifying an upgrade.
Two post installation validation utilities are available after the product has been
deployed. The middlewareValidate utility is used to verify the middleware. The
installValidation utility is used to validate the product installation. These
command-line utilities are used to verify the installation and configuration of the
product in a more complete manner. These utilities can also be used to verify an
existing deployment after changes in the environment, such as changes to host
names, user IDs, and passwords.
© Copyright IBM Corp. 2012
97
Results of the installValidation utility are logged in
installValidationTrace00.log. This log is found in the \ibm\smp\logs directory
on the administrative workstation.
Procedure
1. Log in to the server using the user ID that was used to run the installation
program. If you intend to use the installValidation utility, log in to the
administrative workstation. If you intend to use the middlewareValidate utility,
log in to the server hosting the middleware.
2. Ensure the JAVA_HOME environment variable is set properly to the location of
a JRE 1.6 installation.
3. To verify middleware installation, from the middleware image, update the
middleware.properties file with the installation parameter values for
middleware components to be verified, change directory to \HealthCheck and
run the middlewareValidate.[sh|bat] command. To verify product installation,
from the administrative workstation, change directory to \ibm\smp\scripts and
run the installValidation.bat command. For either command, use the
parameters described below:
Table 5. Verification utilities parameters
Program
Syntax parameters
Input
installValidation.bat
-action
Use -action validate to
start the validation of the
product installation.
The -action parameter is
the only mandatory
parameter when using the
installValidation utility.
98
IBM SmartCloud Control Desk: Upgrade Guide
Table 5. Verification utilities parameters (continued)
Program
Syntax parameters
Input
-trace
Verification progress
information is written to the
screen during the
verification process. You can
modify the output using the
-tracing parameter.
v minimal
Progress information is
limited to error
information.
v normal
Information includes
individual test progress,
individual test results,
and overall progress of
the entire verification
process.
This is the default mode
of tracing.
v verbose
In addition to providing
normal progress
information, verbose
tracing includes the test
class name, test method
name, and corrective
action information.
-confirm
You are prompted before
each test is started. You
must confirm each test to be
performed. There is no
input for this parameter.
-component
You can provide a
comma-delimited list of
directories containing the
test objects to limit testing to
a specific set of tests.
These test objects must be
located in the
\ibm\smp\HealthValidation\
directory. For the product
installation program, only
the CTGIN folder is provided.
-dbuser
Provide the user ID used to
access the database.
-dbpwd
Provide the password of the
user ID used to access the
database.
-wasuser
Provide the WebSphere
Application Server Network
Deployment user.
Chapter 11. Post-upgrade tasks
99
Table 5. Verification utilities parameters (continued)
Program
middlewareValidate.[sh|bat]
Syntax parameters
Input
-waspwd
Provide the password for
the WebSphere Application
Server Network Deployment
user.
-maxuser
Provide the SmartCloud
Control Desk administrator
user ID. For example,
maxadmin.
-maxpwd
Provide the password for
the SmartCloud Control
Desk administrator user ID.
-middlewareproperties
Use
-middlewareproperties file
where file is the location of
the middleware.properties
file. By default, this file is
found on the middleware
installation media in the
\HealthCheck directory.
The middleware.properties
contains the middleware
installation properties, such
as installation locations and
ports. User names and
passwords are not stored in
this plain-text file. Some of
the properties common to
all platforms have been
defined default values, but
platform-specific properties
like installation locations
need to be updated in this
file before starting the
middlewareValidate utility.
The -middlewareproperties
parameter is the only
mandatory parameter when
using the
middlewareValidate utility.
100
IBM SmartCloud Control Desk: Upgrade Guide
Table 5. Verification utilities parameters (continued)
Program
Syntax parameters
Input
-trace
Verification progress
information is written to the
screen during the
verification process. You can
modify the output using the
-trace parameter.
v minimal
Progress information is
limited to error
information.
v normal
Information includes
individual test progress,
individual test results,
and overall progress of
the entire verification
process.
v verbose
In addition to providing
normal progress
information, verbose
tracing includes the test
class name, test method
name, and corrective
action information.
If this option is not
provided, by default, no
output displayed.
-component
Specify the middleware
components:
v DBSERVER - verify
installation of the IBM
DB2 server.
v DIRSERVER - verify
installation of the optional
IBM Tivoli Directory
Server.
v LDAPSERVER - verify
configuration of the
optional IBM Tivoli
Directory Server.
v J2EESERVER - verify
installation of the
WebSphere Application
Server server
One or more of these
keywords can be specified
as comma separated list. If
this argument is skipped,
the tool assumes all the
components are selected to
verify.
Chapter 11. Post-upgrade tasks
101
Table 5. Verification utilities parameters (continued)
Program
Syntax parameters
Input
-bindUser
Provide the bind user.
Required to verify
LDAPSERVER, the bind
user credentials, in addition
to WebSphere Application
Server administrative user
credentials, bind
Distinguished Name and
bind password are required
to be specified with the
-bindUser and -bindPass
options.
-bindPass
Provide the password for
the bind user.
Required to verify
LDAPSERVER, the bind
user credentials, in addition
to WebSphere Application
Server administrative user
credentials, bind
Distinguished Name and
bind password are required
to be specified with the
-bindUser and -bindPass
options.
-wasuser
Provide the WebSphere
Application Server user.
WebSphere Application
Server administrative user
credentials are required for
the LDAPSERVER and
J2EESERVER component
checks.
-waspwd
Provide the password for
the WebSphere Application
Server user.
WebSphere Application
Server administrative user
credentials are required for
the LDAPSERVER and
J2EESERVER component
checks.
For example,
installValidation.bat -action validate
Results
The installValidation.bat validation utility results are logged in
ctginstallvalidationtrace00.log. This log is found in the \ibm\smp\logs
directory on the administrative workstation.
102
IBM SmartCloud Control Desk: Upgrade Guide
The middlewareValidate.[sh|bat] validation utility results are logged in
CTGInstallValidationTrace.log. This log is found in the HealthCheck directory.
What to do next
After the upgrade is complete and you have verified that your installation is
operating correctly, you can delete the deployment engine backup files to reclaim
disk space. Deployment engine backup files are located in the \ibm\smp\DE_BACKUPS
directory on the administrative workstation.
Reviewing your upgraded screens
If you customized any screens in version 7, review your upgraded screens after the
upgrade. Use the Application Designer application in version 7.5 to make additions
or adjustments to the upgraded screens.
Version 7.5 introduces updates to numerous applications to make them easier to
use. These updates might conflict with updates that you have made to applications
in prior releases. During an upgrade, the product installation program creates a
backup of the presentation XML files, which govern the appearance of
applications. This backup file is stored on the administrative workstation in the
ibm/smp/logs directory. The name of the file includes a timestamp indicating when
it was created, for example, PresentationXML_201108120908.xml. The sections of
the file that apply to different applications can be identified easily.
You can use this backup file to reinstate updates that you have made to
applications. Be sure to review the changes that have been made during the
upgrade so that you can optimize the screens for your needs. You might decide to
keep the upgraded screen configurations only for some applications and use the
default version 7.5 screens for other applications.
Enabling the improved UI
When you upgrade to this product, the layout of the user interface is the same as
in the previous products by default. However, IBM SmartCloud Control Desk
provides a number of UI features that make navigating and using the applications
easier and more intuitive. It is highly recommended that you configure your
installation to use these new UI features.
About this task
After you enable the new UI, existing users will have the same methods for
selecting application actions as before; similarly, going to an application is equally
intuitive. The added UI features only increase the usability of applications, with a
minimal learning curve for your users.
To find out more about the improved UI, see the "Navigating the application UI"
topics in the Getting Started section of the product information center.
You enable key UI features that you want individually, by configuring system
properties that are provided in the System Properties application. Perform the
following steps to complete the configuration:
Procedure
1. Go to the System Properties application Go To > System Configuration >
Platform Configuration > System Properties).
Chapter 11. Post-upgrade tasks
103
2. Type navigator in the Description field, and click Enter to display a list of the
four system properties that you can configure to obtain the UI features. The
properties are as follows:
System property
Description
mxe.webclient.homeButtonHeaders
Creates Go To and Start Center icons in the left-hand portion of the top
navigation bar. These icons enable users to go to applications and
return to their start centers.
mxe.webclient.systemNavBar
Creates a navigation bar down the left side of the start center and
application displays. Users use sections in the left navigation bar to go
to applications, select available queries, and select available application
actions. The application actions are also accessible from the Select
Action menu and menu bar icons, just as before.
mxe.webclient.tabBreadCrumbs
Removes tabs from the list view. In the new UI layout, application tabs
are displayed only after a user selects a record. Users can open a full or
limited list of records using easy, intuitive controls provided in the UI,
and can then select a record from the list.
mxe.webclient.verticalLabels
Sets field labels above, rather than beside, application work area fields.
This minimizes horizontal scrolling, which might otherwise be
necessary with the left navigation bar.
3. For each property that you want to configure, expand the property, and replace
the 0 in the Global Value field with 1. This turns on the property, which was
disabled in the shipped upgrade.
4. Click Save.
5. Check the box beside each of the properties that you have modified, and click
Live refresh to refresh the system properties to include your modifications.
Reviewing table domains and crossover domains
Review all custom crossover domains and table domains. If you added or modified
any crossover domains or table domains, review their WHERE clauses. Ensure that
the WHERE clauses use the version 7.5 table and column names.
If necessary, use the Database Configuration application to re-specify the table and
column information. You must edit any custom domains that name any of the
tables that were referenced in your prior deployment, but do not exist in version
7.5. Ensure that you examine all custom crossover and table domains.
Updating BIRT reports
The following procedures must be followed in order to update your BIRT reports
for version 7.5.
Regenerating the request pages for your reports
After you upgrade, you must go to the Report Administration application and
regenerate the request pages for all of your reports.
104
IBM SmartCloud Control Desk: Upgrade Guide
Updating statistics
In Oracle, system administration tasks include analyzing table commands. Analyze
all tables to ensure that the Oracle Cost-Based Optimizer has up-to-date statistics.
1. Sign into the Maximo application.
2. Open the Database Configuration application.
3. From the Select Action menu, select Update Statistics, and then click OK to
continue.
Uninstalling WebSphere Application Server Network Deployment v6.1
When you have completed the upgrade to SmartCloud Control Desk 7.5, you can
uninstall WebSphere Application Server Network Deployment v6.1.
If you used the middleware installation program to install WebSphere Application
Server Network Deployment v6.1, and you also installed WebSphere Application
Server Network Deployment v7.0, as described in Chapter 6, “Upgrading by
installing WebSphere Application Server Network Deployment v7.0 on a new
server (Scenario 1),” on page 23, you can use the middleware installation program
from your prior deployment to uninstall WebSphere Application Server Network
Deployment v6.1. Refer to the installation information for your prior product for
details on uninstalling middleware with the middleware installation program.
If you installed WebSphere Application Server Network Deployment v7.0 using the
native WebSphere Application Server Network Deployment v7.0 installation
program and migrated WebSphere Application Server Network Deployment v6.1
configuration information to WebSphere Application Server Network Deployment
v6.1 as described in Chapter 7, “Upgrading by migrating WebSphere v6.1
configuration information (Scenario 2),” on page 45, you must use the native
WebSphere Application Server Network Deployment v6.1 uninstall program.
Because profiles have been migrated from WebSphere Application Server Network
Deployment v6.1, you cannot use the middleware installation program from your
prior deployment to uninstall WebSphere Application Server Network Deployment
v6.1, even if it was originally installed using that program. Refer to
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/
com.ibm.websphere.nd.doc/info/ae/ae/tins_uninstall.html for more information
on uninstalling WebSphere Application Server Network Deployment v6.1.
Chapter 11. Post-upgrade tasks
105
106
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 12. Upgrading Integration Composer
IBM SmartCloud Control Desk installations that want to upgrade Integration
Composer should do so from the Launchpad, as described herein. If you need to
upgrade Integration Composer on a UNIX operating system in console mode,
instructions to do that are also described.
About this task
This upgrade is for any Integration Composer 7.2.1 or later release, including
Integration Composer 7.2.1, 7.2.2, and 7.2.2.1. The installation program does not
permit upgrades from earlier releases. On Windows operating systems, the
installation program automatically checks for a valid current release prior to
upgrading.
Results
When the upgrade completes successfully, you can access Integration Composer as
follows:
Windows
From the Start menu, or by entering the command: itic_installation_dir\
bin\startFusion.bat
The default Integration Composer installation directory for Windows
operating systems is C:\Integration Composer.
UNIX
By entering the command: itic_installation_dir/bin/startFusion.sh
The default Integration Composer installation directory for UNIX operating
systems is /home/user/Integration_Composer.
Upgrading Integration Composer using the Launchpad
UNIX
Windows
For SmartCloud Control Desk installations, the recommended
way to upgrade Integration Composer is from the Launchpad. Use the Launchpad
to upgrade Integration Composer on Windows or UNIX operating systems.
Before you begin
To avoid losing any of your current data, back up your Integration Composer
data\dataschema and data\mappings directories before upgrading.
Attention: For this release, the Naming and Reconciliation Service (NRS) was
upgraded to Data Integration Services (DIS). As part of this Integration Composer
installation, the nameReconciliation.logging.properties file is removed from the
properties subdirectory in the Integration Composer installation directory, and the
removed file is replaced with the dis.logging.properties file. As a result, any
customizations that were made to the original
nameReconciliation.logging.properties file are lost.
© Copyright IBM Corp. 2012
107
Before upgrading to this release of Integration Composer, note your current
customization information if you plan to to reuse any of that information in the
new dis.logging.properties file.
Make sure that you have up to 70 MB of free space for the installation directory.
Procedure
1. Insert the Launchpad DVD into the server where you upgrade Integration
Composer.
If you are upgrading on a UNIX operating system, you might have to start the
Launchpad manually by running the launchpad.sh command, which is located
in the root directory of the Launchpad DVD. (On Windows operating systems,
the launchpad.exe command runs automatically.)
Note: Confirm that the java -version command returns 1.6 before starting the
upgrade. IBM Java™ SDK 6.0 with JRE 1.6 is provided on the product DVDs.
2. From the Launchpad, launch the Integration Composer upgrade program by
clicking the link under Install IBM Tivoli Integration Composer.
3. In the IBM Tivoli Integration Composer window, select your language from the
drop-down list at the bottom and click OK.
4. Read the information in the Introduction window and click OK.
5. [UNIX only] In the Select Install Type window, select Upgrade and click Next.
6. In the Choose Install Folder window, accept the default location or type a file
path to specify where you want to upgrade the product. (Or you can click
Choose to browse and select the location you want.) Then click Next.
7. In the Choose IBM SDK Location window, type the directory where IBM Java
SDK 6.0 is located, or click Choose to browse and select the directory. Then
click Next.
8. On the Preinstallation Summary window, review the upgrade details. (If
necessary, use the Previous buttons to go back and make corrections, and use
the Next buttons to return to this window.) When satisfied with the summary
data, click Install.
The Installing Integration Composer progress window displays during
upgrade. When upgrading is finished, the Installation Complete window is
displayed.
9. In the Installation Complete window, click Done.
Upgrading Integration Composer on UNIX operating systems in
console mode
UNIX
Use the procedure described here if you have to upgrade Integration
Composer on a UNIX computer in console (command line) mode.
Before you begin
Installing Integration Composer 7.5, as described in this section, will upgrade the
previous version of Integration Composer. You do not need to remove the previous
version first. To avoid losing any of your current data, back up your Integration
Composer data\dataschema and data\mappings directories before upgrading.
108
IBM SmartCloud Control Desk: Upgrade Guide
Attention: For this release, the Naming and Reconciliation Service (NRS) was
upgraded to Data Integration Services (DIS). As part of this Integration Composer
installation, the nameReconciliation.logging.properties file is removed from the
properties subdirectory in the Integration Composer installation directory, and the
removed file is replaced with the dis.logging.properties file. As a result, any
customizations that were made to the original
nameReconciliation.logging.properties file are lost.
Before installing this release of Integration Composer, note your current
customization information if you plan to to reuse any of that information in the
new dis.logging.properties file. For additional details about these properties
files, see the book IBM Tivoli Integration Composer Administrator Guide.
Make sure you have up to 70 MB of free space for the installation directory.
About this task
The Integration Composer files are located in either the \ITIC or \Install\ITIC
directory on the version 7.5 product DVD. Use the setup.bin command from the
DVD layout to start the upgrade process:
setup.bin ←
setup.exe
The steps for upgrading Integration Composer on a UNIX-based operating system
follow.
Procedure
1. Sign on to the server as an administrator (for example, as root).
2. Save the binary Integration Composer installation file, setup.bin, on the
server where you intend to install Integration Composer.
3. Make sure JRE 1.6 is in your system path.
To add JRE 1.6 to the path, enter the following commands (where JRE_location
is the path for your IBM JRE; for example, /opt/ibm/java-i386-60/jre/
bin:$PATH):
JAVA_HOME=JRE_location
export JAVA_HOME
PATH=$JAVA_HOME:$PATH
export PATH
4. Navigate to the location where you saved the setup.bin file.
5. Enter the following command to make the binary installation file executable:
chmod +x setup.bin
6. Run the Integration Composer installation program in console mode by
entering the following command at the shell prompt:
sh ./setup.bin -i console
In console mode, you are prompted to enter information line by line.
Note: Confirm that the java -version command returns 1.6 before starting
the upgrade. IBM Java SDK 6.0 with JRE 1.6 is provided on the product
DVDs.
7. In the Choose Locale step, type the number of your locale from the list of
locales and press Enter.
8. In the Introduction step, review the Introduction information and press Enter.
Chapter 12. Performing an upgrade
109
9. In the Select Install Type step, type the number for the Upgrade selection and
press Enter. This indicates that you want to upgrade Integration Composer
from the previous release.
10. In the Choose Install Folder step, type the location (absolute path) where
Integration Composer is currently installed and press Enter. Or just press
Enter to accept the displayed path.
11. In the IBM SDK Location step, specify the file path where IBM Java SDK 6.0 is
installed by doing one of the following:
v Accept the default location and press Enter.
v Type a different file path for the location and press Enter.
12. In the Preinstallation Summary step, review the installation details and press
Enter to begin installing Integration Composer. The Installing progress bar
displays during installation.
When installation is complete, the Installation Complete step is displayed.
13. In the Installation Complete step, press Enter. The installation is done and you
are returned to the UNIX command prompt.
Upgrading integration adapters
For this initial release of SmartCloud Control Desk, it is recommended that you
follow the adapter configuration instructions for a new installation.
Upgrade process
The configuration instructions take you through the process of performing the
following tasks:
1. Creating a source data source
2. Creating a target data source
3. Defining the mapping
Any customization that you made for legacy adapters can be applied to your new
data sources once they are re-created.
Configuration instructions can be found at the following locations:
v For assets: http://publib.boulder.ibm.com/infocenter/tivihelp/v50r1/topic/
com.ibm.tusc.doc/import_asset/c_import_data.html
v For CIs: http://publib.boulder.ibm.com/infocenter/tivihelp/v50r1/topic/
com.ibm.tusc.doc/int_comp/c_itic_config_intro.html
Supported adapters
The following table contains a list of adapters that are supported under the initial
release of SmartCloud Control Desk.
Table 6. Supported adapters for SmartCloud Control Desk
110
Adapter
Source schema
Tivoli Application
Dependency Discovery
Manager CI Type
TADDM75CIType CCMDB75CIType TADDM72CITypeToCCMDB75
Classification.fsn
Tivoli Application
Dependency Discovery
Manager Actual CI
TADDM75ActualCICCMDB75ActualCITADDM72ToCCMDB75
ActualCI.fsn
IBM SmartCloud Control Desk: Upgrade Guide
Target schema
Mapping file
Table 6. Supported adapters for SmartCloud Control Desk (continued)
Adapter
Source schema
Target schema
Mapping file
Centennial Discovery
2006 and 2007
Centennial
Discovery
2006/2007
Deployed Assets CentennialDiscovery
2006_2007ToDPA75.fsn
7.5
Tivoli Application
Dependency Discovery
Manager 7.2
Tivoli
Application
Dependency
Discovery
Manager 7.2
Deployed Assets TADDM72ToDPA75.fsn
7.5
Tivoli Application
Dependency Discovery
Manager 7.2.1
Tivoli
Application
Dependency
Discovery
Manager 7.2.1
Deployed Assets TADDM721ToDPA75.fsn
7.5
Tivoli Asset Discovery
for Distributed 7.2 and
7.5
Tivoli Asset
Discovery for
Distributed
7.2/7.5
Deployed Assets TAD4D72_75toDPA75.fsn
7.5
Tivoli Asset
Tivoli Asset Discovery
Discovery for
for z/OS® 7.2 and 7.5.
See the Additional
z/OS 7.2/7.5
information section that
follows this table.
Deployed Assets TAD4Z72_75toDPA75.fsn
7.5
Tivoli Endpoint
Manager for Software
Use Analysis 1.3
Tivoli Endpoint
Deployed Assets TEMSUA13ToDPA75.fsn
Manager SUA 1.3 7.5
Tivoli Network
Manager IP Edition 3.8
and 3.9
Tivoli Network
Manager IP
Edition 3.8/3.9
Deployed Assets ITNM38_39toDPA75.fsn
7.5
Tivoli Provisioning
Manager 7.1.1
Tivoli
Provisioning
Manager
7.1.1/7.2
Deployed Assets TPM711ToDPA75.fsn
7.5
Tivoli Provisioning
Manager 7.2
Tivoli
Provisioning
Manager
7.1.1/7.2
Deployed Assets TPM72ToDPA75.fsn
7.5
Microsoft System Center MS System
Configuration Manager Center
2007
Configuration
Manager 2007
Source Deployed Assets
7.5
Deployed Assets SCCM2007ToDPA75.fsn
7.5
MaximoAssets
7.5
AssetInitDPA75to
Assets75.fsn
Additional information for users of the Tivoli Asset Discovery for
Distributed adapters
There is a known issue when running the Tivoli Asset Discovery for Distributed
7.2, 7.2.1, or 7.2.2 adapters in Integration Composer 7.5. Before running these
adapters, you must run the /data/dataschema/tad4d72/
updateTAD4D72_721views.sql file in the Integration Composer directory structure.
Chapter 12. Performing an upgrade
111
Improving Integration Composer performance
You can take advantage of new options to improve the performance of the Actual
CI adapter.
The integration adapter for Actual CI data is used to transform data received from
TADDM into the format required for use by SmartCloud Control Desk
applications. Version 7.5 introduces new options to improve the performance of
this adapter. By default, these options are not enabled on upgraded systems.
Review the options and decide whether to enable them in your environment.
The first option concerns the caching of alternate and primary keys while
retrieving data. You can achieve a significant performance improvement by not
caching these keys.
The fusion.properties file, located in theIntegration Composer\data\properties
directory, contains properties that control the mapping process. In version 7.5, this
file contains these new lines:
mxe.fusion.referencecache.Actual_Target_CI=1000,Guid,ALTERNATE_KEY
mxe.fusion.referencecachesameas.Actual_CI=Actual_Target_CI
mxe.fusion.referencecache.Actual_CI=1000,Guid,ALTERNATE_KEY
To disable caching of alternate and primary keys, add the NO_CACHE_LOAD parameter
to the two referencecache properties, so that the lines look like this:
mxe.fusion.referencecache.Actual_Target_CI=1000,Guid,ALTERNATE_KEY,NO_CACHE_LOAD
mxe.fusion.referencecachesameas.Actual_CI=Actual_Target_CI
mxe.fusion.referencecache.Actual_CI=1000,Guid,ALTERNATE_KEY,NO_CACHE_LOAD
Do not add the parameter to the referencecachesameas property.
When you add the NO_CACHE_LOAD parameter, the Actual CI adapter also uses
threading while importing data from TADDM. Using threads offers performance
improvements of up to 50% on the running of the adapter. Using threads causes
the adapter to use more memory, so using it without the NO_CACHE_LOAD parameter
is not recommended.
You can control thread-related behavior using properties in the ccmdb.properties
file, located in theIntegration Composer\data\properties\provider directory. The
ccmdb.itic.num.of.threads property takes two numeric values. The first value is the
number of threads to be used, and the second value is the maximum number of
queued configuration items (CIs). The default values are 5:25 for 32-bit operating
systems and 10:50 for 64-bit operating systems.
Another new option is to import only those actual CIs that will be promoted to
authorized CIs. This option uses the promotion scopes that are defined as part of
your authorized CI space. Using this option prevents importing data about CIs that
will never become authorized CIs. To implement this option, change the value of
the ccmdb.actualci.filtering.level property in the ccmdb.properties file to 2.
If a thread does not receive a response from TADDM in a specified period of time,
you will see a message like this in the fusion.log file and standard out:
Did not receive any TADDM data for GUID
7C386211D2403B02A769DD00B8797C32 after waiting for 100000 milliseconds.
Error occurred during: Retrieving TADDM CI data for
7C386211D2403B02A769DD00B8797C32
Error occurred in: TADDMThreadManager.getTaddmData
112
IBM SmartCloud Control Desk: Upgrade Guide
Integration Composer stops working when this error occurs. If you see this
message, you can modify the ccmdb.properties file to override the period of time
that the thread waits before failing. By default this property is not defined in the
file, but you can add it. Add this line to the file:
ccmdb.itic.thread.max.wait.time=200000
This doubles the wait time from ten minutes to 20 minutes.
If you modify properties files to implement any of these options, restart the
Integration Composer server to activate the property changes.
Chapter 12. Performing an upgrade
113
114
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 13. Upgrading the Deployer's Workbench
The Deployer's Workbench is a separately installed, Eclipse-based workbench that
is the best-practice tool for creating authorized CI spaces. If you have already
installed a prior version of Deployer's Workbench, upgrade it to work with
SmartCloud Control Desk 7.5.
About this task
You can upgrade the Deployer's Workbench using either the product launchpad or
the native installer. In either case, the DVD1 image or physical DVD must be
accessible from the workstation where you have installed the Deployer's
Workbench.
The upgrade process preserves your Deployer's Workbench projects. The
Deployer's Workbench subsequently upgrades them to work with the new product
version.
Procedure
1. Start the Deployer's Workbench installer. Either start the product launchpad
and click Install Deployer's Workbench, or to use the native installer, cd to the
DW directory and run install.exe.
2. The Deployer's Workbench installer detects that Deployer's Workbench is
already installed and asks whether you want to upgrade to the new version.
Click OK.
3. You might see a message saying that Install Anywhere is preparing to install.
When the Deployer's Workbench screen appears, choose a language from the
drop-down list and click OK.
4. The Deployer's Workbench installer asks whether you want to upgrade your
Deployer's Workbench projects to be compatible with the new version.
Upgrades include modifications to authorized classifications to match those
supported with SmartCloud Control Desk 7.5. You must upgrade your projects
to use them with the new product version.
5. Review the pre-installation summary. Click Previous to make any changes.
Click Upgrade to begin the upgrade.
6. You will see a progress bar indicating the progress of the upgrade procedure.
After the upgrade has completed, click Done to exit the installer. At this point
the installer has upgraded the Deployer's Workbench software, but not any of
the existing projects. The projects in the Deployer's Workbench workspace will
be automatically upgraded the next time that Deployer's Workbench is started.
Results
Upon startup Deployer's Workbench will scan each project to see if it qualifies for
upgrading. If so, a message and progress indicator will appear to show the overall
progress of the upgrade. In some cases the upgrade may require you to answer a
question pertaining to the current upgrade step. Before elements in the project are
upgraded, Deployer's Workbench will make a backup of the project and place the
backup file within the project itself.
© Copyright IBM Corp. 2012
115
Additionally, if you import a Deployer's Workbench project that was exported from
an earlier release, this same upgrade procedure will occur.
116
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 14. Miscellaneous topics
These topics cover specific situations that you might encounter as you plan and
perform your upgrade.
Presentation XML files
During the upgrade process, the product installation program creates a backup of
presentation XML files used for your existing deployment.
XML files are used to control the look and feel of SmartCloud Control Desk
applications. These presentation files are stored in the database and are updated as
new products and solutions are added to the existing deployment.
During an upgrade, the product installation program creates a backup of the
presentation XML files. This backup is stored on the administrative workstation in
the ibm/smp/logs directory. The name of the file includes a timestamp indicating
when it was created. For example, presentationset_201106281117.zip.
If you are installing a new product to an existing deployment you might
experience a failure. New XML presentation files can be written to the database
before a product is fully deployed. This circumstance leads to a disconnect
between what the application interface displays and functioning features. In this
instance, you might want to restore the presentation XML files to their previous
state. The presentation XML backup file is created so you can restore presentation
XML files to their original state in the database.
Restoring presentation XML files
SmartCloud Control Desk provides a way to restore presentation XML files to the
database.
About this task
Use the backup file created when you performed the upgrade to restore
presentation XML files to the database.
Procedure
1. Log on to the administrative workstation using the same credentials that were
used to perform the upgrade.
2. Change directory to ibm\smp\logs.
3. Copy the presentation XML backup file, for example,
presentationset_201106281117.zip, to the ibm\smp\maximo\tools\maximo\
screenupgrade\ directory.
4. Change directory to ibm\smp\maximo\tools\maximo\screenupgrade\.
5. Extract the backup file. When prompted, choose to overwrite the existing
presentationset.xml file.
6. Run the mximportset command. The contents of the presentationset.xml file
are written to the database.
© Copyright IBM Corp. 2012
117
Results
The presentation XML is restored to the point before the upgrade action committed
changes to the database.
Adding the PLUSPLISTPRICE field to offerings
If you customized this field, and you want to include this customization in your
upgraded environment, you must take steps to add the field back in.
About this task
In order to better support Pricing and Billing in Service Provider environments,
significant architectural changes have been made. The field PLUSPLISTPRICE
currently defined for Offerings has been removed. If you if added customizations
to this field, and you want to use this customization in your upgraded
environmant, you must complete three steps:
1. Add the field PLUSPLISTPRICE to the database.
2. Copy the data from the new location in PLUSPPBLINE to the newly created
field.
3. Update the Offering application to use the new field.
Procedure
1. Add the field PLUSPLISTPRICE to the database.
a. Open the Data Configuration application: click Go To > System
Configuration > Platform Configuration > Database Configuration.
b. Find the Object PMSCOFFERINGEXT.
c. On the attributes tab, add a new field with the following properties:
Attribute: PLUSPLISTPRICE
Alias: PLUSPLISTPRICE
Description: The item’s list sales price. This must be a positive value
and can have decimals.
Type: Amount
Title: List Sales Price
Default Value: 0
Positive: Checked
Must Be: Checked
Persistent: Checked
Leave the default values for all other properties.
d. Click Save.
e. Open the List tab.
f. From the Select Action menu, choose Manage Admin Mode. The Turn
Admin Mode ON dialog box is displayed.
g. Click Turn Admin Mode ON. The Turn Admin Mode ON dialog box closes.
h. From the Select Action menu, choose Apply Configuration Changes.
i. From the Select Action menu, choose Manage Admin Mode. The Turn
Admin Mode OFF dialog box is displayed.
j. Click Turn Admin Mode OFF. The Turn Admin Mode OFF dialog box
closes.
2. Using an SQL Editor, connect to the database and run the following commands:
118
IBM SmartCloud Control Desk: Upgrade Guide
update pmscofferingext set plusplistprice = (select listprice from plusppbline
where itemnum = pmscofferingext.itemnum and
itemsetid = pmscofferingext.itemsetid)
update pmscofferingext set plusplistprice = 0 where plusplistprice is null
3. Use the Application Designer to update the PMSCOFFERING application. On
the list tab, create a new text box field and configure the properties so that it
exposes the PLUSPLISTPRICE field.
If you have installed fix pack 7.2.1.1
When the Service Request Manager 7.2.1.1 or subsequent fix pack is installed, one
application is in a state from which it cannot be updated directly.
About this task
If you applied the 7.2.1.1 fix pack to Service Request Manager on the server from
which you are upgrading, the Service Request Manager Search application cannot
be updated directly. If you upgrade using the launchpad, this problem is corrected
automatically, and you do not need to follow the procedure described here. If you
upgrade from the command line, you must follow this procedure to correct the
problem before upgrading.
Procedure
1. Locate these files in the /Install/extras directory on the product media or
downloaded product image: updatecmstate.cmd/sh and
ForceMoveCmstateToUsable.class.
2. Copy these two files to a directory of your choice on your administrative
workstation. For example, you could create a new directory called
/ibm/SMP/SRMpatch and copy the files there.
3. Run the updatecmstate script. You should see out put similar to this:
==================================
FORCE MOVE *CMSTATE TO USABLE*
Version 1.0
==================================
Connecting to DE database...
Successfully connected to IU Registry
Moved *CMSTATE TO USABLE* for 2 IUs
Results
The application's state in the Deployment Engine database is updated so that the
application can be upgraded successfully.
Note: You can run the utility more than once if you are uncertain about its results.
On a subsequent invocation, you should see output similar to this, indicating that
no problem is found:
==================================
FORCE MOVE *CMSTATE TO USABLE*
Version 1.0
==================================
Connecting to DE database...
Successfully connected to IU Registry
No IUs found in *CMSTATE UPDATED*. Nothing to do.
Chapter 14. Miscellaneous topics
119
Avoiding database issues from Service Catalog 7.1
If you are upgrading a system that includes IBM Tivoli Service Request Manager,
read this to determine whether you need to remove old data.
About this task
If you are upgrading to the current version on a system with the Service Request
Manager 7.2.x.x release and your 7.2.x.x instance was upgraded from Service
Request Manager 7.1 with Service Catalog installed, you might encounter an
installation error because of data that may be present on the system. To prevent the
error, you can delete the date without affecting the new installation.
Procedure
1. Run the following SQL statements on your system to determine whether the
data can be found. Normal results of the queries are presented below each
query. Column headings have been hyphenated to enable the output to fit on
the page.
select * from ctrlcondition where conditionnum = ’PMSCSOCOMP3’
CTRLCTRLCONDITIONID GROUPID
---------- -------81
101
82
102
CONDITIONCONDITIONNUM SEQ
REEVALUATE ROWSTAMP
------------ ---------- ---------- -------PMSCSOCOMP3
10
1
462086
PMSCSOCOMP3
10
1
462087
select * from ctrlcondprop where ctrlconditionid in
(select ctrlconditionid from ctrlcondition where conditionnum = ’PMSCSOCOMP3’)
CTRLCONDCONDITION- CTRLPROPID
PROPERTY PROPERTYVALUE
RESULT
CONDITIONID ROWSTAMP
-------- -------- --------------- ----------- ----------- -------79
Label
Vendor
1
82
796753
80
Label
Delivery Team
0
82
796752
81
Label
Vendor
1
81
796751
82
Label
Delivery Team
0
81
796750
2. If the queries return results similar to those listed above (two records from the
first query matching the conditionnum and four records from the second query
matching the property / property value combinations), you can run these
commands to delete those records:
delete from ctrlcondprop where ctrlconditionid in
(select ctrlconditionid from ctrlcondition where conditionnum = ’PMSCSOCOMP3’)
delete from ctrlcondition where conditionnum = ’PMSCSOCOMP3’
Results
After removing these records if they are present, you can proceed with your
upgrade.
120
IBM SmartCloud Control Desk: Upgrade Guide
Chapter 15. Troubleshooting
Refer to the topics in this chapter if you experience a problem while running the
upgrade program.
Message CTGIN0024E when upgrading
When upgrading, you might see this error: SEVERE: CTGIN0024E: An unexpected
exception was encountered during processing of a process solution
installation service request. The exception is com.ibm.ac.si.iuproc.
About this task
This is the full set of messages:
SEVERE: CTGIN0024E: An unexpected exception was encountered during processing of
a process solution installation service request. The exception is
com.ibm.ac.si.iuproc.BuildCMOperationException:
at com.ibm.ac.si.iuproc.BuildChangeManagementOperations.buildChangeManagementOperations
(BuildChangeManagementOperations.java:515)
at com.ibm.ac.si.iuproc.IUProcessor.buildChangeManagementOperations(IUProcessor.java:999)
at com.ibm.ac.si.iuproc.IUProcessor.processIUDeploymentDescriptor(IUProcessor.java:554)
at com.ibm.ac.si.iuproc.IUProcessor.processIUDeploymentDescriptor(IUProcessor.java:378)
at com.ibm.ac.si.checker.AbstractChecker.setupTree(AbstractChecker.java:75)
at com.ibm.ac.si.checker.SystemCheckerImpl.checkSystem(SystemCheckerImpl.java:131)
at com.ibm.ac.si.runtime.impl.DCAPIController.checkSystem(DCAPIController.java:445)
at com.ibm.tivoli.ccmdb.install.ps.si.checker.SISystemChecker.checkSystem
(SISystemChecker.java:198)
at com.ibm.tivoli.ccmdb.install.ps.si.change.PsiChangeRequestManager.runAsync
(PsiChangeRequestManager.java:331)
at com.ibm.tivoli.ccmdb.install.ps.processor.SIInvoker.processInstallPackage
(SIInvoker.java:1192)
at com.ibm.tivoli.ccmdb.install.ps.processor.SIInvoker.processInstallPackage
(SIInvoker.java:1461)
at com.ibm.tivoli.ccmdb.install.ps.processor.UpgradeSolutionElementProcessor.
processRequest(UpgradeSolutionElementProcessor.java:82)
at com.ibm.tivoli.ccmdb.install.ps.request.SolutionElementRequestDispatcher.
requestInvokerHelper(SolutionElementRequestDispatcher.java:690)
at com.ibm.tivoli.ccmdb.install.ps.request.SolutionElementRequestDispatcher.
dispatchUpgradeRequest(SolutionElementRequestDispatcher.java:254)
at com.ibm.tivoli.ccmdb.install.ps.client.PsiInstallationService.
upgradeSolutionElement(PsiInstallationService.java:466)
at com.ibm.tivoli.ccmdb.install.ps.processor.PsiDpeProcessor.run
(PsiDpeProcessor.java:234)
at java.lang.Thread.run(Thread.java:736)
Caused by: com.ibm.ac.si.iuproc.IUProcessorException:
independent full update of refIUs not allowed
at com.ibm.ac.si.iuproc.BuildChangeManagementOperations.
buildChangeManagementOperations(BuildChangeManagementOperations.java:399)
... 16 more
This error indicates that one or more packages are not in the correct status to be
updated. It has been seen when upgrading from Tivoli Service Request Manager
7.2.1, when not using the Launchpad to perform the upgrade, or when upgrading
on a non-Windows administrative workstation.
© Copyright IBM Corp. 2012
121
Procedure
1. Change to the install_home/sccd75/launchpad/Install/extras directory on the
administrative workstation.
2. Run this command: ./updateCmstate.sh
The output should include this line:
Moved *CMSTATE TO USABLE* for 2 IUs
If you run the command a second time, you should see this message:
No IUs found in *CMSTATE UPDATED*. Nothing to do.
3. Restart the installer to resume the upgrade process.
122
IBM SmartCloud Control Desk: Upgrade Guide
Appendix. Integrity checker error messages
Errors prevent the integrity checker utility from successfully passing. All errors
must be corrected. The following is a subset of the possible error messages that
may arise when using the integrity checker.
ERROR BMXAA0333E
Native index names longer than 18 characters exist. Before running
ConfigDB, you must manually identify and rename these native indexes.
Cause The Maximo database requires that index names have a maximum length
of 18 characters. The restriction was bypassed through the database back
end, and an index name was created containing more than 18 characters.
Action
Any index with a name longer than 18 characters must be dropped from
the database back end. Use an SQL editor to drop the index. If the index is
needed, you can use the Database Configuration application to re-create it.
See the Technical Reference Guide for more details. If you need additional
help, contact your Maximo database administrator or IBM Maximo
Support.
ERROR BMXAA0451E
Tables exist that have not had their backup data restored. You must run
RestoreFromBackup before you can run Upgrade.
Cause When the database tables are configured using the Database Configuration
application, Maximo makes backup copies of the tables, then applies your
changes to the original tables. After this process is done, run the Database
Configuration application again and restore the data from the backup
tables. If this data restoration is not performed, the integrity checker stops
the process with this error message because there might be serious
implications to the overall upgrade of the Maximo database.
Action
To pass the integrity checker, you must run the Database Configuration
application and select the option to restore from the backup tables. You are
then given the choice of retaining the backup tables after restoration or
dropping them. It is usually advisable to drop the backup tables because it
saves disk space. Dropping the backup tables, however, is not mandatory.
If you need additional help, contact IBM Maximo Support.
ERROR BMXAA0453E
The following groups should be removed from Maximo because they have no
MAXIMO privileges:
Cause User groups are centrally stored in a Maximo database table called
MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user
entry is not present in these tables, it might cause problems while using
Maximo. The database has been modified through the back end and data
consistency between these tables and all other Maximo security tables has
been compromised.
© Copyright IBM Corp. 2012
123
Action
Run integrity checker in repair mode.
ERROR BMXAA0455E
The following users should be removed from Maximo because they have no
MAXIMO privileges:
Cause User groups are centrally stored in a Maximo database table called
MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user
entry is not present in these tables, it might cause problems while using
Maximo. The database has been modified through the back end and data
consistency between these tables and all other Maximo security tables has
been compromised.
Action
Run integrity checker in repair mode.
ERROR BMXAA0456E
The following users should be removed from the security tables: <table>
because they are not Maximo users.
Cause User groups are centrally stored in a Maximo database table called
MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user
entry is not present in these tables, it might cause problems while using
Maximo. The database has been modified through the back end and data
consistency between these tables and all other Maximo security tables has
been compromised.
Action
Run integrity checker in repair mode.
ERROR BMXAA0458E
The following Users Groups were not found in MAXGROUPS:
Cause User groups are centrally stored in a Maximo database table called
MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user
entry is not present in these tables, it might cause problems while using
Maximo. The database has been modified through the back end and data
consistency between these tables and all other Maximo security tables has
been compromised.
Action
Run integrity checker in repair mode.
ERROR BMXAA0459E
This group is defined as a user in the Maximo security tables: <table>
Cause User groups are centrally stored in a Maximo database table called
MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user
entry is not present in these tables, it might cause problems while using
Maximo. The database has been modified through the back end and data
consistency between these tables and all other Maximo security tables has
been compromised.
Action
Run integrity checker in repair mode.
124
IBM SmartCloud Control Desk: Upgrade Guide
ERROR BMXAA0462E
The database has a different UNIQUE property for the following original
index definition(s):
Cause Many indexes were originally defined in the Maximo database for better
performance. The original indexes have been modified (probably through
the back end).
Action
You can potentially improve Maximo performance by re-creating any
unique indexes.
ERROR BMXAA0470E
Non-sequential primary key sequence on table(s): <table>
Cause Every Maximo table must have a primary key sequence of columns,
defined by MAXATTRIBUTE.PrimaryKeyColSeq. The values of
PrimaryKeyColSeq must be consecutive and sequential. For these tables,
the primary key sequence is not consecutive or not sequential.
Action
For the definitions of these tables, check and, if necessary, adjust the values
of PrimaryKeyColSeq in MAXATTRIBUTE and MAXATTRIBUTECFG. The
primary key sequence should have a corresponding unique index.
ERROR BMXAA0474E
These tables should be removed from Maximo becuase they do not exist in the
database: <table>
Cause One or more table names are defined as persistent tables in MAXTABLE
but do not exist in the Maximo database. All Maximo database tables must
be defined in the MAXTABLE table. They also might appear in other
Maximo tables, including the following tables:
v AUTOKEY
v MAXATTRIBUTE
v MAXATTRIBUTECFG
v MAXSYSINDEXES
Action
If you selected the report mode run-time option and you determine that
the table is required, re-create the table. Use backup, if available, to restore
the data in the table.
If the table is not required, remove the table name entry from all of the
Maximo tables listed in the Cause section. For example, delete from
MAXTABLE where tbname = ‘.....'.
In addition, if the table name is the main table in a custom application,
remove any application entries from the following Maximo tables:
v APPDOCTYPE
v APPFIELDDEFAULTS
v APPLICATIONAUTH
v BOOKMARK
v DEFAULTQUERY
Appendix. Integrity checker error messages
125
v
v
v
v
v
EXCLUDEDACTIONS
LOGINTRACKING
MAXAPPS
MAXLABELS
MAXMENU
v
v
v
v
v
v
v
MAXPRESENTATION
QUERY
SIGOPTION
WFAPPTOOLBAR
WFASSIGNMENT
WFTASK
WORKVIEW
For example, delete from MAXAPPS where app = ‘.....'. If necessary, contact
IBM Maximo Support.
If you select the repair option, the table name entry and application entry
(if the table name entry was for a custom application) are removed from
the tables that are listed. In repair mode, you do not have an opportunity
to maintain these relevant entries and restore the table from backup.
ERROR BMXAA0476E
The following tables own Maximo columns but are not defined as Maximo
tables: <table>
Cause A table name entry was found in MAXATTRIBUTE, but the table is not
defined in MAXTABLE table. The names of all Maximo database tables
must be entered in the MAXTABLE table. Each table name also appears in
the MAXATTRIBUTE table, together with the names of all columns in that
table. The table name might also be found in one or more of the following
tables:
v AUTOKEY
v MAXATTRIBUTECFG
v MAXSYSINDEXES
Action
If you selected the report mode option, and the table exists in the database,
contact IBM Maximo Support.
If you selected the report mode option and the table does not exist in the
database, remove the table name entries from all of the Maximo tables
listed in the Cause section, including MAXATTRIBUTE. For example,
delete * from MAXATTRIBUTE where tbname = ‘.....'.
In addition, if the table name is the main table in a custom application,
remove any application entries from the following Maximo tables:
v APPDOCTYPE
v APPFIELDDEFAULTS
v APPLICATIONAUTH
v BOOKMARK
v DEFAULTQUERY
v EXCLUDEDACTIONS
126
IBM SmartCloud Control Desk: Upgrade Guide
v
v
v
v
v
LOGINTRACKING
MAXAPPS
MAXLABELS
MAXMENU
MAXPRESENTATION
v
v
v
v
v
v
QUERY
SIGOPTION
WFAPPTOOLBAR
WFASSIGNMENT
WFTASK
WORKVIEW
For example, delete from MAXAPPS where app = ‘.....'. If necessary, contact
IBM Maximo Support.
If you selected the repair option and the table exists in the database, the
problem cannot be repaired automatically. Contact IBM Maximo Support.
If you select the repair option and the table does not exist in the database,
the table name entry is removed from all of the Maximo tables listed in the
Cause section, including MAXATTRIBUTE. If the table name entry was for
a custom application, any application entries are also removed from the
following Maximo tables:
v APPDOCTYPE
v APPFIELDDEFAULTS
v APPLICATIONAUTH
v
v
v
v
v
v
v
v
v
BOOKMARK
DEFAULTQUERY
EXCLUDEDACTIONS
LOGINTRACKING
MAXAPPS
MAXLABELS
MAXMENU
MAXPRESENTATION
QUERY
v SIGOPTION
v WFAPPTOOLBAR
v WFASSIGNMENT
v WFTASK
v WORKVIEW
ERROR BMXAA0477E
The following are defined as Maximo tables but do not contain any maximo
columns: <table>
Cause
A table name is missing from MAXATTRIBUTE even though the name is
present in the MAXTABLE table.
Appendix. Integrity checker error messages
127
The names of all Maximo database tables must be entered in the
MAXTABLE table. Each table name also appears in the MAXATTRIBUTE
table, together with the names of all columns in that table. The table name
might also be found in one or more of the following tables:
v AUTOKEY
v MAXATTRIBUTECFG
v MAXSYSINDEXES
Action
If you selected the report mode option and the table exists in the database,
contact IBM Maximo Support.
If you selected the report mode option and the table does not exist in the
database, you must remove the table name from all of the Maximo tables
listed in the Cause section, including the MAXTABLE table. For example:
delete * from MAXTABLE where tbname = ‘.....'.
In addition, if the table name is the main table in a custom application,
remove any application entries from the following Maximo tables:
v APPDOCTYPE
v APPFIELDDEFAULTS
v APPLICATIONAUTH
v BOOKMARK
v DEFAULTQUERY
v EXCLUDEDACTIONS
v LOGINTRACKING
v MAXAPPS
v MAXLABELS
v MAXMENU
v MAXPRESENTATION
v QUERY
v
v
v
v
v
SIGOPTION
WFAPPTOOLBAR
WFASSIGNMENT
WFTASK
WORKVIEW
For example, delete from MAXAPPS where app = ‘.....'. If necessary, contact
IBM Maximo Support.
If you selected the repair option and the table exists in the database, the
problem cannot be repaired automatically. Contact IBM Maximo Support.
If you select the repair option and the table does not exist in the database,
the table name entry is removed from all of the Maximo tables listed in the
Cause section, including MAXATTRIBUTE. If the table name entry was for
a custom application, any application entries are also removed from the
following Maximo tables:
v APPDOCTYPE
v APPFIELDDEFAULTS
v APPLICATIONAUTH
v BOOKMARK
128
IBM SmartCloud Control Desk: Upgrade Guide
v
v
v
v
v
DEFAULTQUERY
EXCLUDEDACTIONS
LOGINTRACKING
MAXAPPS
MAXLABELS
v
v
v
v
v
v
v
MAXMENU
MAXPRESENTATION
QUERY
SIGOPTION
WFAPPTOOLBAR
WFASSIGNMENT
WFTASK
v WORKVIEW
ERROR BMXAA0478E
The ROWSTAMP trigger was not found for the following tables: <table>
Cause The table is missing a rowstamp trigger. This might have been caused by
installation of the integration gateway.
Action
Re-create the trigger, or run the integrity checker in repair mode to
automatically provide the missing trigger.
ERROR BMXAA0479E
The ROWSTAMP trigger was found DISABLED on the following tables: <table>
Cause The rowstamp trigger was inadvertently or intentionally disabled.
Action
Re-enable the trigger.
ERROR BMXAA0480E
Null rowstamp(s) found in the following tables: <table>
Cause A rowstamp is a unique identifier for a row of data. It should never be
null. The tables listed for this error contain null rowstamps. This might
have been caused by a database being brought forward through multiple
upgrades.
Action
Update any rowstamps that are null by assigning a unique rowstamp
value.
ERROR BMXAA0490E
This column should be removed from Maximo because it does not exist in the
database: <table.column>
Cause
An incompatibility exists between the column definition in the database
system catalog and the Maximo catalog (the MAXATTRIBUTE table).
Appendix. Integrity checker error messages
129
All Maximo columns must be defined as columns in the database's system
catalog. This column is not defined in the system catalog.
Action
If you selected the report mode option, you must either re-create the
column in the system catalog, or delete all occurrences of the column in
the MAXATTRIBUTE, and MAXATTRIBUTECFG tables. If necessary,
contact IBM Maximo Support to correct this situation.
If you select the repair option, all entries for this column name are
removed from the MAXATTRIBUTE and MAXATTRIBUTECFG tables. If
the column is must-be, same-as (same as some root column), or root (other
columns are the same as this column), this problem cannot be repaired
automatically. Contact IBM Maximo Support.
ERROR BMXAA0493E
These Maximo-owned columns should be removed from the database becauase
they do not exist in Maximo: <table.column>
Cause
A Maximo table column does not have a corresponding entry in
MAXATTRIBUTE.
This message might indicate a database table problem that could not be
fixed automatically. This error must be resolved before you can continue.
Ignoring this error during an upgrade might result in a faulty upgrade,
which might prevent the application from running smoothly.
Action
The listed table columns must be manually inserted or deleted from the
MAXATTRIBUTE table. See the Technical Reference Guide and your SQL
Language guide, or call IBM Maximo Support.
ERROR BMXAA0494E
The Maximo definition of this column does not match the actual column:
<table.column>
Cause An incompatibility exists between the column definition in the database
system catalog and the Maximo catalog.
Action
Determine which column definition is correct, and redefine the incorrect
column definition to match the correct one. If you are unsure which
definition is correct, contact IBM Maximo Support. The integrity checker
repair mode option modifies the Maximo column definition to match the
database definition.
If the column is must-be, same-as (same as a root column), or root (other
columns are the same as this column), the incompatibility is not repaired.
In this case you must call IBM Maximo Support, or use the Database
Configuration application to correct the incompatible column definitions.
ERROR BMXAA0495E
The ’’nulable’’ property of this column does not match the actual column
definition. Run the Integrity Checker in repair mode.
130
IBM SmartCloud Control Desk: Upgrade Guide
Cause
The NULLS value of the Maximo column is different from the NULLS
value of the system column.
It is permissible for some columns in a Maximo database to be null,
meaning that the column contains no value at all. Whether a column can
be null is defined by the NULLS value for that column.
Action
If you selected the report mode option, manually modify the NULLS value.
If a null value is appropriate for this column, change REQUIRED to N in
the database and in MAXATTRIBUTE. If this column should never be null,
change REQUIRED to Y in the database and in MAXATTRIBUTE. You can
make this change through the database back end. If you need additional
help, contact IBM Maximo Support.
If you selected the repair option, the REQUIRED column in the Maximo
table MAXATTRIBUTE is modified to match the column in the system
table.
ERROR BMXAA0496E
This column is defined to be the "same as" a column that does not exist in
Maximo: <table.column>
Cause Certain columns in Maximo database tables must be the same as—be the
same type and size—another column, called a root column, in the same or
a different table. The root column and the same-as column are supposed to
have the same data type, length, and scale. The indicated column is
defined to be the same as a root column, but that root column does not
exist.
Action
Redefine the same-as relationship so that it specifies a root column that
exists in the Maximo database. The missing column might have to be
added to the base Maximo database table. If necessary, contact IBM
Maximo Support.
ERROR BMXAA0497E
The following columns are defined to be ’’same-as’’, but have different
definitions <table.column> <table.column>
Cause Certain columns in Maximo database tables must be the same as—be the
same type and size—another column, called a root column, in the same or
a different table. The root column and the same-as column are supposed to
have the same data type, length, and scale. This same-as relationship was
broken by modifying the definition of one of the columns.
Action
If you selected the report mode option, contact IBM Maximo Support to
repair the error.
If you selected repair mode and the data type does not match, repair mode
changes the data type of the same-as column to match the data type of the
root column. Run the Maximo Database Configuration application in order
for changes to take effect. Then rerun the integrity checker utility. Note the
following limitations:
Appendix. Integrity checker error messages
131
v If the same-as column is set up as must-be, it cannot be repaired by
repair mode. Contact IBM Maximo Support.
v If the same-as column has a value list associated with it, and the value
list data type does not match the root column data type, and the value
list type is 3 or 4 (Maximo defined value list), and the Maximo release
version is 4.0 or above, this error cannot be repaired by repair mode.
Contact IBM Maximo Support.
v If the same-as column has a domain associated with it, and the domain
data type does not match the root column data type, this error cannot be
repaired by repair mode. Contact IBM Maximo Support.
If length does not match, repair mode compares all the columns that are the same
as the root column. repair mode changes the column lengths to match that of the
longest column. This result prevents user data loss and maintains the same-as
relationship. Run the Maximo Database Configuration application for changes to
take effect, then rerun the integrity checker.
ERROR BMXAA0513E
This column is both a root column and is same-as linked to another column:
<table.column>
Cause A column that is being referenced as a root column in a same-as
relationship is itself referencing another column as the root column in a
same-as relationship. There can only be one same-as reference between
columns.
Action
Run the integrity checker in repair mode to resolve multiple same-as
relationships between columns.
ERROR BMXAA0527E
The following groups have no privileges in the Maximo security tables. The
group and its users should be removed from Maximo:
Cause User groups are centrally stored in a Maximo database table called
MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user
entry is not present in these tables, it might cause problems while using
Maximo. The database has been modified through the back end and data
consistency between these tables and all other Maximo security tables has
been compromised.
Action
Run integrity checker in repair mode.
ERROR BMXAA0328E
The class name in the language code solumn is not correct: Atribute {0}
Class {1}
Cause The wrong class name was specified for the language code column.
Action
Use the Database Configuration application to specify the correct class
name, for example, psdi.app.system.FldLangCode.
132
IBM SmartCloud Control Desk: Upgrade Guide
ERROR BMXAA0329E
The maxviewcolumncfg table contains a row that does not have a
corresponding column in the maxviewcolumn table. View {0} Column {1}. If
database configuration changes are pending, run the ConfigDB utility. If no
configuration changes are pending, delete this row from the maxviewcolumn
table by using an SQL utility.
Cause A row exists in the maxviewcolumncfg table but there is no corresponding
row in maxviewcolumn. Parameter {0} is the name of the View and
parameter {1} is the name of the column.
Action
If database configuration changes are pending, run the ConfigDB utility. If
no configuration changes are pending, delete this row from the
maxviewcolumn table by using an SQL utility.
ERROR BMXAA0430E
The user name {0} could not be deleted from the MAXUSERGROUPS or GROUPUSER
table. Try the operation again, or delete the user name manually.
ERROR BMXAA0431E
The group name {0} could not be deleted from the MAXGROUP or MAXGROUPS
table. Try the operation again, or delete the group name manually.
ERROR BMXAA0432E
The security-related data for the user name {0} could not be deleted. Try
the operation again, or delete the security-related data manually.
ERROR BMXAA0433E
The security-group-related data for the group name {0} could not be
deleted. Try the operation again, or delete the security-group-related data
manually.
ERROR BMXAA0440E
You must specify Integrity Checking (-i) or Validation (-v)
ERROR BMXAA0441E
The folllowing SQL error occurred: {0} {1}.
ERROR BMXAA0443E
Error - {0}
ERROR BMXAA0444E
The INTEGRITYCHECK maxvar could not be inserted into the database.
Cause The Integrity checker found errors, but could not insert maxvar
INTEGRITYCHECK with a value FAIL.
Appendix. Integrity checker error messages
133
ERROR BMXAA0445E
The database version {0} was not recognized. The version stamp in maxvars
for varname MAXUPG should be of the form Vnnn[-mmm], where nnn is the
version of the database (for example, 7116), and -mmm is an optional build
or patch.
ERROR BMXAA0447E
The index file {0} either does not exist or could not be read. Check your
build and ensure that the file exists.
ERROR BMXAA0464E
Table and column entity names do not match for {0}. The value of
MaxAttribute.EntityName is {1}. The value of MaxObject.EntityName is {2}.
Fix the entity name of the column by using the Database Configuration
application.
Cause A discrepancy exists between the entity names in the MaxAttribute table
and the MaxObject table. The entity names must be the same in both
tables.
ERROR BMXAA0465E
The following indexes are missing from the database. Use the Database
Configuration application to remove the index definition.
Cause Some indexes are defined in the metadata but the actual index does not
exist in the database.
Action
Use the Database Configuration application to remove the index definition.
ERROR BMXAA0467E
The database has a different UNIQUE property for the following indexes. Use
the Database Configuration application to redefine the index.
Cause The UNIQUE property that is defined in the metadata does not match the
UNIQUE property in the database. These property values must match.
Action
Use the Database Configuration application to redefine the index.
ERROR BMXAA0468E
The database has a different CLUSTERED property for the following indexes.
Use the Database Configuration application to redefine the index.
Cause The CLUSTERED property defined in the metadata does not correspond
the actual CLUSTERED property defined in the database. These property
values must match.
Action
Use the Database Configuration application to redefine the index.
134
IBM SmartCloud Control Desk: Upgrade Guide
ERROR BMXAA0472E
A unique column ID must be defined for table(s):
ERROR BMXAA0491E
The following persistent columns are owned by non-persistent tables.
Non-persistent tables can contain only non-persistent attributes. To fix
this error, run the Integrity Checker in repair mode.
ERROR BMXAA0500E
The defined length for this column is incorrect. Change the data type of
the column to DECIMAL or change its length to match the AMOUNT length.
Cause This column's maxtype data type is AMOUNT but its length differs from
the standard Amount length defined by the maxvar AMTLENGTH.
ERROR BMXAA0501E
The scale for this column is invalid. If the maxtype for the column is
AMOUNT, the scale must the same as the maxvar AMTSCALE; otherwise the scale
should be 0.
Cause Either the column maxtype data type requires a scale of zero, or the
column has the AMOUNT maxtype and its scale does not equal the value
tha tis defined in the AMTSCALE maxvar.
Action
Correct the scale definition. The Integrity Checker repair mode does not fix
this error.
ERROR BMXAA0506E
The integrity check failed. See the log for a detailed list of errors.
ERROR BMXAA0530E
Column {0} is mapped to domain {1}, but the domain does not exist. Set the
attribute’s domain to a different value using the Database Configuration
application, or define the domain using the Domains application.
Cause The column specified in parameter 0 has a domain (specified in parameter
1) defined against it but the domain itself does not exist.
Action
Set the attribute's domain to a different value using the Database
Configuration application, or define the domain using the Domains
application.
ERROR BMXAA0532E
Column {0} is mapped to domain {2}, but is not defined the same. {0} is
{1}. {2} is {3}. Either change the attribute using the Database
Configuration application, or change the domain using the Domains
application.
Cause The datatype, length and scale of the attribute are inconsistent with the
datatype, length and scale of the domain.
Appendix. Integrity checker error messages
135
Action
Either change the attribute using the Database Configuration application,
or change the domain using the Domains application.
ERROR BMXAA0534E
A domain of type {0} should have a valid datatype and length., Domain {1}
has a maxtype of {2} and a length of {3}.
ERROR BMXAA0537E
0} definition differs from {1} for {2}.,{0}.{3}={4}{1}.{3}={5}. Use the
Database Configuration application to correct the configuration metadata.
Cause The pending configuration (MaxObjectCfg, MaxTableCfg, MaxAttributeCfg)
metadata does not match the live metadata (MaxObject, MaxTable,
MaxAttribute).
Action
Use the Database Configuration application to correct the configuration
metadata.
ERROR BMXAA0538E
This column is mapped to an AutoKey but the AutoKey does not exist. Column
{0} AutoKey {1}. Run the Integrity Checker in repair mode.
Cause The column specified in parameter 0 is mapped to an Autokey (specified
in parameter 1), but the Autokey itself does not exist.
Action
Run the Integrity Checker in repair mode.
ERROR BMXAA0494E
The Maximo definition of this column does not match the actual column:
<table.column>
Cause A column is defined one way in Maximo, and another way in the database.
Action
Determine which column definition is correct, and redefine the incorrect
column definition to match the correct one. If you are unsure which
definition is correct, contact IBM Maximo Support. The integrity checker
repair mode option modifies the Maximo column definition to match the
database definition.
ERROR BMXAA0388E
Database {0} Version {1}.
ERROR BMXAA0429E
Ignoring SQL Exception.
ERROR BMXAA0503E
You MUST run Database Configuration after Integrity Check is complete.
136
IBM SmartCloud Control Desk: Upgrade Guide
ERROR BMXAA0446E
Reading index file: {0}
ERROR BMXAA6233E
The following required Maximo indexes are missing from Maximo:
ERROR BMXAA6238E
These views should be removed from Maximo because they do not exist in the
database:
ERROR BMXAA6284E
These views should be manually fixed because they exist in the native
database but are not defined correctly in Maximo:
ERROR BMXAA6248E
Run the Integrity Checker in repair mode to fix this problem.
ERROR BMXAA4191E
{0} {1} is not valid.
ERROR BMXAA4195E
Required field {0} is blank.
ERROR BMXAA6290E
The Search Type should be WILDCARD for the attributes where SEARCHTYPE is
TEXT, but TEXTSEARCHENABLED is FALSE. Run repair mode to fix.
ERROR BMXAA6286E
The Search Type must be NONE for attributes that are non-persistent, CRYPTO
or BLOB. Run repair mode to fix.
ERROR BMXAA6287E
The Search Type must be TEXT for long description attributes that are
non-persistent, CRYPTO or BLOB. Run repair mode to fix.
ERROR BMXAA6288E
The Search Type must be EXACT or NONE for numeric, datetime and YORN
attributes. Run repair mode to fix.
ERROR BMXAA6289E
The Search Type must be TEXT for long description attributes that are not
on audit tables. Run repair mode to fix.
Appendix. Integrity checker error messages
137
ERROR BMXAA6315E
Text Search indexes missing for the following tables/attributes.
ERROR BMXAA6234E
Column {0} is not large enough for the values defined in domain {1}.
ERROR BMXAA6293E
The following organization level autokeys are missing in the AUTOKEY table.
Run repair mode to fix.
ERROR BMXAA0434E
{0} removed from table AUTOKEY.
ERROR BMXAA4116E
Maxvar type is not valid.
ERROR BMXAA4168E
Organization and site must both be blank.
ERROR BMXAA4166E
Site must be blank.
ERROR BMXAA4167E
Organization must be blank.
ERROR BMXAA0504E
Integrity check passed with warnings found.
ERROR BMXAA0505E
Integrity check passed.
ERROR BMXAA6283E
Maxrelationship cannot be added because it already exists in the database:
ERROR BMXAA6328E
Upgrade cannot add new apps because they already exist in MaxApps:
ERROR BMXAA0437E
Validate -- Integrity checking and repair requested.
138
IBM SmartCloud Control Desk: Upgrade Guide
ERROR BMXAA6292E
Records exist in the Wogen table which need be deleted. Run repair mode to
delete records from the table.
ERROR BMXAA4169E
No record found in maxvars table for maxvar {0}.
ERROR BMXAA0687E
Entity Name must be specified when the object is persistent.
ERROR BMXAA0689E
This object is a view, but Extends Object was not specified.
ERROR BMXAA5617E
When text search is enabled, a language column name must be specified.
ERROR BMXAA0686E
This object is audit enabled, but audit table name was not specified.
ERROR BMXAA0692E
When Auto Select is not selected, a value for View From must be entered.
ERROR BMXAA0693E
When Auto Select is not selected, a value for View Select must be entered.
ERROR BMXAA0582E
When an object is flagged for text search, at least one attribute must be
flagged for text search.
ERROR BMXAA0688E
Both Entity Name and Column Name must be specified when the attribute is
persistent.
ERROR BMXAA0700E
Same As Table and Same As Column must either both be null, or both not
null.
ERROR BMXAA0680E
The language column must have a data type of UPPER and length of 4.
ERROR BMXAA0600E
The default value for attribute {0} indicates autonumbering but autonumber
name is blank.
Appendix. Integrity checker error messages
139
ERROR BMXAA5613E
The default value for attribute {0} indicates sequencing but sequence name
is blank.
ERROR BMXAA0708E
Sequence Name cannot be null for the unique ID column.
ERROR BMXAA8088E
The Extends Object should be null if the object is not a view.
ERROR BMXAA7946E
Column {1} of table {0} is defined as a {2} but is not defined correctly in
the database table.
ERROR BMXAA8269E
Missing revision record for Process {0} called by main process {1}.
140
IBM SmartCloud Control Desk: Upgrade Guide
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
© Copyright IBM Corp. 2012
141
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
Software Interoperability Coordinator, Department 49XA
3605 Highway 52 N
Rochester, MN 55901
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement, or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
142
IBM SmartCloud Control Desk: Upgrade Guide
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© IBM Corp. 2012. Portions of this code are derived from IBM Corp. Sample
Programs. © Copyright IBM Corp. 2012. All rights reserved.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
For trademark attribution, visit the IBM Terms of Use Web site
(http://www.ibm.com/legal/us/)
The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
IBM, the IBM logo, AIX, Tivoli, the Tivoli logo, and WebSphere are trademarks or
registered trademarks of International Business Machines Corporation in the
United States, other countries, or both.
Intel, the Intel logo, and Pentium are trademarks of Intel Corporation in the United
States, other countries, or both.
Microsoft, Windows, the Windows logo, and Internet Explorer are trademarks of
Microsoft Corporation in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or
both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Other company, product, and service names may be trademarks or service marks
of others.
Notices
143
144
IBM SmartCloud Control Desk: Upgrade Guide
Index
C
P
ccmdb.properties file 112
customization
upgrading 10, 120
customizations
migrate 40, 61, 78, 88
performance
Integration Composer
PLUSPLISTPRICE 4
presentation XML 117
restoring 117
D
R
database
tuning 16
deferring upgrade actions 8
deployment roadmaps 19
rehearsing your upgrade 17
restoring
XML presentation files 117
XML presentation
117
112
T
F
file differences
on other platforms 11
on Windows 11
fusion.properties file 112
I
IBM HTTP Server
installing and configuring 51
installing fix packs 53
IBM WebSphere Application Server
Network Deployment
migrating configuration
information 48
industry solutions
upgrading 121
installation
Tivoli Integration Composer 107
Integration Composer
installing
with process solution installation
package 108
UNIX systems 108
integration modules 39, 60, 78, 88
integrity checker 15, 42, 63, 80, 90
tar command
AIX 3
TDToolkit 41, 62, 79, 89
threading 112
Tivoli Integration Composer
upgrade 107
U
updatedb
deferring 8
restarting 18
upgrade
automatic configuration of
WebSphere 33
automatic WebSphere
configuration 23
manual configuration of
WebLogic 86
manual configuration of
WebSphere 56, 73
migrate WebSphere configuration 45,
65
post-upgrade tasks 97
updatedb 41, 62, 79, 89
using Oracle WebLogic Server 83
M
V
maintenance window 7
middleware data
migrating 32, 55, 73, 85
middleware installation program
WebSphere Application Server
Network Deployment v7.0 25, 67
verifying the installation
programmatically 97
O
optional content
X
4, 39, 60, 78, 88
© Copyright IBM Corp. 2012
W
WebSphere Application Server Network
Deployment 47
installing the update installer 50
WebSphere Application Server Network
Deployment v7.0 25, 67
WebSphere plug-in
See installing
WebSphere plug-in fix packs
installing 55
145
146
IBM SmartCloud Control Desk: Upgrade Guide
Printed in USA