IBM SmartCloud Control Desk: Installation Guide (Oracle ... › support › knowledgecenter › en › ... · Configuring and managing Oracle WebLogic Server .....201 Starting Oracle

IBM SmartCloud Control DeskVersion 7 Release 5.1

Installation Guide(Oracle WebLogic Server)

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 225.

Contents

Chapter 1. Preparing for installation . . 1Before you begin . . . . . . . . . . . . . 1

Programmatically verifying prerequisites . . . . 2Checking port availability . . . . . . . . . 6Accessing system directories . . . . . . . . 7AIX and HP-UX tar command requirements . . . 7AIX font requirements . . . . . . . . . . 7Increasing AIX file size and number of descriptors 8Increasing AIX paging space . . . . . . . . 8Enabling asynchronous I/O on AIX. . . . . . 9Checking for required libraries on Linux . . . 10Configuring the JRE in Linux . . . . . . . 10Setting the ulimit . . . . . . . . . . . 10Setting the swap size . . . . . . . . . . 11Setting shared memory . . . . . . . . . 11Remote configuration enablement . . . . . . 12System password policy settings . . . . . . 13Backing up the Deployment Engine database . . 13Specifying host name values. . . . . . . . 14

Establishing a fully qualified host name onWindows systems . . . . . . . . . . 14Forcing the middleware installer to usealphanumeric hostnames . . . . . . . . 15

Enabling full text search for IBM DB2 . . . . 15Launchpad . . . . . . . . . . . . . . 15

Starting the launchpad . . . . . . . . . 16

Chapter 2. Deploy with automaticmiddleware configuration. . . . . . . 17Middleware installation program middlewaredeployment plan overview . . . . . . . . . 17Installing middleware using the middlewareinstallation program . . . . . . . . . . . 17

Middleware installation program logs . . . . 20Middleware installation program log reference 21

Configuring IBM Tivoli Directory Server user andgroup strings . . . . . . . . . . . . . 26

Uninstalling middleware . . . . . . . . . . 27Reinstalling middleware with IBM DB2 . . . . . 28Manually configuring WebLogic Server . . . . . 29

Creating the MAXIMOSERVER domain . . . . 29Configuring JMS options for integrationframework . . . . . . . . . . . . . 30Configuring JMS for the email listener inWebLogic Server. . . . . . . . . . . . 31

Installation program overview . . . . . . . . 33Installing the product and automaticallyconfiguring middleware . . . . . . . . . 35Installing optional content . . . . . . . . 39Installing optional integration modules . . . . 40

Post installation for Oracle WebLogic Serverdeployments . . . . . . . . . . . . . . 40Deploying ear files . . . . . . . . . . . . 42Setting the Oracle WebLogic Server host name. . . 43

Language deployment after database updatedeferral . . . . . . . . . . . . . . . . 44

Manually deploying languages after databaseupdate deferral . . . . . . . . . . . . 44

Chapter 3. Deploying automaticallyreusing existing middleware . . . . . 47Run the middleware installation program onexisting middleware servers . . . . . . . . . 47

Configuring an existing DB2 with themiddleware installation program . . . . . . 49

Manually configuring WebLogic Server . . . . . 50Creating the MAXIMOSERVER domain . . . . 51Configuring JMS options for integrationframework . . . . . . . . . . . . . 51Configuring JMS for the email listener inWebLogic Server. . . . . . . . . . . . 53

Installation program overview . . . . . . . . 55Installing the product and automaticallyconfiguring middleware . . . . . . . . . 56Installing optional content . . . . . . . . 61Installing optional integration modules . . . . 61

Post installation for Oracle WebLogic Serverdeployments . . . . . . . . . . . . . . 62Deploying ear files . . . . . . . . . . . . 64Setting the Oracle WebLogic Server host name. . . 65Language deployment after database updatedeferral . . . . . . . . . . . . . . . . 65


Chapter 4. Deploying manually reusingexisting middleware . . . . . . . . . 69SmartCloud Control Desk installation with manualmiddleware configuration . . . . . . . . . 69

Manually configuring the database . . . . . 69Manually configuring DB2 9.x . . . . . . 70Manually configuring Oracle 11g . . . . . 71Manually configuring Oracle 10g . . . . . 74Manually configuring Microsoft SQL Server 76

Manually configuring the directory server . . . 79Manually configuring IBM Tivoli DirectoryServer . . . . . . . . . . . . . . 79Manually configuring Microsoft ActiveDirectory . . . . . . . . . . . . . 83

Manually configuring the J2EE server . . . . 86Manually configuring WebLogic Server . . . 86

Installing the product and manually configuringmiddleware . . . . . . . . . . . . . . 91Installing optional content . . . . . . . . . 96Installing optional integration modules . . . . . 96Post installation for Oracle WebLogic Serverdeployments . . . . . . . . . . . . . . 97Deploying ear files . . . . . . . . . . . . 98Setting the Oracle WebLogic Server host name . . 100

© Copyright IBM Corp. 2012 iii

Language deployment after database updatedeferral . . . . . . . . . . . . . . . 100


Chapter 5. Silent installation . . . . . 103Installing SmartCloud Control Desk silently . . . 103Silent installation properties . . . . . . . . 105

Chapter 6. Programmatically verifyingthat the installation was successful . . 125

Chapter 7. Verifying the installationmanually . . . . . . . . . . . . . 129

Chapter 8. Installing IntegrationComposer . . . . . . . . . . . . . 131Integration Composer overview . . . . . . . 131Hardware and software requirements . . . . . 132Installation prerequisites. . . . . . . . . . 134Performing an Integration Composer installation 135

Installing Integration Composer using theLaunchpad . . . . . . . . . . . . . 135Installing Integration Composer on UNIXoperating systems in console mode . . . . . 137

Performing an Integration Composer upgrade . . 139Upgrading Integration Composer using theLaunchpad . . . . . . . . . . . . . 140Upgrading Integration Composer on UNIXoperating systems in console mode . . . . . 141

Confirming the installation . . . . . . . . . 142Post-installation tasks. . . . . . . . . . . 143

Verifying the settings in the IntegrationComposer fusion.properties file . . . . . 143Changing the memory allocation in thestartFusion file (optional) . . . . . . . . 145Changing the memory allocation in theexecuteMapping file (optional) . . . . . . . 145

Uninstalling Integration Composer . . . . . . 146Uninstalling Integration Composer on Windowsoperating systems . . . . . . . . . . . 146Uninstalling Integration Composer on UNIXoperating systems . . . . . . . . . . . 147

Chapter 9. Installing the Deployer'sWorkbench . . . . . . . . . . . . 149

Chapter 10. Installing IBM SmartCloudControl Desk Everyplace . . . . . . 151Installing as part of a new product installation . . 151Installing as part of a product upgrade . . . . . 152Installing after SmartCloud Control Desk has beeninstalled . . . . . . . . . . . . . . . 152

Chapter 11. Post installation tasks 153Accessing product documentation . . . . . . 153Initial data configuration . . . . . . . . . 153

Signing in using a default user ID . . . . . 153

Configuring SMTP . . . . . . . . . . 154Create currency codes . . . . . . . . . 154Create item and company sets . . . . . . . 155Create an organization . . . . . . . . . 155Create a general ledger account component . . 155Applying changes to the database . . . . . 156Create a general ledger account . . . . . . 156Update General Ledger Component TypeAuthorization . . . . . . . . . . . . 157Update Company-Related Accounts . . . . . 157Create default insert site. . . . . . . . . 157Create worktypes . . . . . . . . . . . 158Create a classification structure for IT assets . . 158Specify a top-level class for IT assets andsoftware . . . . . . . . . . . . . . 159Signing out and signing in . . . . . . . . 160

Generating xml request pages . . . . . . . . 160Synchronizing users and groups . . . . . . . 161Understanding and configuring security . . . . 161

Chapter 12. Middleware clean upscripts . . . . . . . . . . . . . . 163Using the middleware cleanup scripts . . . . . 163

Chapter 13. Uninstalling the product 167Uninstalling an automatically configureddeployment . . . . . . . . . . . . . . 167

Running the product uninstallation program forautomatically configured middleware . . . . 168

Uninstalling a manually configured deployment 169Running the product uninstall program formanually configured middleware. . . . . . 169Database configuration recovery . . . . . . 170

Restoring the DB2 database server . . . . 170Restoring the Oracle database . . . . . . 171Restoring the Microsoft SQL Server database 172

Uninstalling the product without the uninstallationprogram . . . . . . . . . . . . . . . 173

Uninstall program recovery tool . . . . . . 173Using the uninstallation program recoverytool. . . . . . . . . . . . . . . 173

Manual uninstallation . . . . . . . . . 175Removing files from the system . . . . . 175

Chapter 14. Starting and stoppingmiddleware . . . . . . . . . . . . 177Restarting middleware on Windows . . . . . . 177Restarting middleware on UNIX . . . . . . . 178

Chapter 15. Process solution packageinstallation methods . . . . . . . . 179Software life cycle operations . . . . . . . . 179Process solution packages . . . . . . . . . 180Package types . . . . . . . . . . . . . 180Aggregation packages . . . . . . . . . . 181Determining which process solution installationprogram to use . . . . . . . . . . . . . 181Supported operations for the process solutioninstallation programs . . . . . . . . . . . 182

iv IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server)

Before using the process solution installationprograms . . . . . . . . . . . . . . . 183Managing process solution deployment from theadministrative workstation . . . . . . . . . 183Typical deployment operation . . . . . . . . 184Selectable features . . . . . . . . . . . . 184Pre-deployment system check . . . . . . . . 189Installing process managers using the processsolution installation wizard. . . . . . . . . 190Process solution installation client command-lineinterface . . . . . . . . . . . . . . . 192

Starting the process solution installation clientCLI. . . . . . . . . . . . . . . . 192

General syntax . . . . . . . . . . . 192Perform action . . . . . . . . . . . 193Summary of supported parameters . . . . 193

Process solution command-line interfacereference . . . . . . . . . . . . . . 195

install action - install\ a package . . . . . 195modfeatures action - modify existing featuresof a deployed package . . . . . . . . 196

Process solution installation logs . . . . . . . 197

Chapter 16. Advanced installationtopics. . . . . . . . . . . . . . . 201Configuring and managing Oracle WebLogicServer . . . . . . . . . . . . . . . . 201

Starting Oracle WebLogic Server . . . . . . 201Stopping the Oracle WebLogic Server . . . . 201

Changing the middleware installation programconfiguration parameters . . . . . . . . . 202Maintaining EAR files . . . . . . . . . . 202

Building EAR files. . . . . . . . . . . 203Manually uninstalling applications from OracleWebLogic Server . . . . . . . . . . . 203

Manually uninstalling applications fromOracle WebLogic Server . . . . . . . . 203

Chapter 17. Middleware on Solarisand HP-UX . . . . . . . . . . . . 205Operating system preparation . . . . . . . . 205

Middleware installation on Solaris . . . . . 205HP-UX . . . . . . . . . . . . . . 205

Installing the components . . . . . . . . . 206Installing DB2 . . . . . . . . . . . . 206Installing IBM Tivoli Directory Server on Solaris 208

Chapter 18. Backup and restoration 211Backing up the administrative workstation . . . 211Restoring the administrative workstation . . . . 212Installation properties . . . . . . . . . . 212

Updating environment data . . . . . . . 222

Notices . . . . . . . . . . . . . . 225Trademarks . . . . . . . . . . . . . . 227

Index . . . . . . . . . . . . . . . 229

Contents v

vi IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server)

Chapter 1. Preparing for installation

These topics provide information about product media, preinstallationconsiderations, overview of the installation procedure, and instructions on usingthe SmartCloud Control Desk launchpad.

Use the planning information to familiarize yourself with the overall process of aSmartCloud Control Desk deployment before you use this information to conductthe installation.

Before you beginA set of tasks must be completed before installing SmartCloud Control Desk. Insome cases, to perform the steps, you must be logged in as a user withadministrator privileges on Windows or as root on UNIX. Some processes, such asanti-virus programs, can negatively affect SmartCloud Control Desk installation onthe system. You must temporarily shut down any noncritical processes beforerunning the SmartCloud Control Desk installation program.

Most tasks must be completed for middleware installed on UNIX systems,regardless of whether you intend to use the middleware installation program toinstall and configure SmartCloud Control Desk middleware. These tasks must becompleted for any UNIX systems hosting middleware you intend to use withSmartCloud Control Desk.

Note: Make a copy of the image of the system, database, and application server onwhich you are planning to install the product.

Note: IBM® publishes updates to the middleware installation program. Beforeusing it, visit the IBM Support Portal to see whether there is an updated copy ofthe installation program available for your use.

Ensure that you have adequate disk space for the future on the systems being usedfor the SmartCloud Control Desk deployment. Filling up the disk space on aSmartCloud Control Desk deployment system can cause problems withSmartCloud Control Desk operations.

Fully qualified host names provided to the installation programs must resolvebetween systems involved in the product deployment. Ensure all IP addressesconfigured for systems targeted for the product deployment are reachable usingthe ping command from the administrative workstation.

“Checking port availability” on page 6You need to ensure that certain ports are available before using the productinstallation programs.“AIX and HP-UX tar command requirements” on page 7Both the native UNIXtar command and the GNU version of the tar commandare required by the middleware installation program. Because the native utilitydoes not support long file names, ensure that GNU tar version 1.14 or higher isinstalled. GNU tar version 1.14 ensures that installation files can be extracted.“Increasing AIX file size and number of descriptors” on page 8For SmartCloud Control Desk to function correctly, you must increase the

© Copyright IBM Corp. 2012 1

default number of file descriptors that are allowed for the root user and set themaximum allowable file size to unlimited.“Increasing AIX paging space” on page 8To successfully install and run SmartCloud Control Desk, you must increase thedefault paging space for the AIX® system to a minimum of 4 GB, or, preferably,the total amount of physical memory in the system.“Enabling asynchronous I/O on AIX” on page 9IBM Tivoli® Directory Server requires asynchronous I/O be enabled on AIXsystems.“Checking for required libraries on Linux” on page 10The SmartCloud Control Desk deployment requires certain Linux systemlibraries.“Configuring the JRE in Linux” on page 10In some cases, the middleware installation program fails on Red Hat EnterpriseLinux 5 systems, or other systems with Security-Enhanced Linux (SELinux)enabled.“Setting the ulimit” on page 10This section details how to set the ulimit in Linux, which is used to define usersystem and process resource limits.“Setting the swap size” on page 11SmartCloud Control Desk can be a resource-intensive application. Configureand tune your system for maximum performance. This section details how toset the size of the swap space used in Linux systems.“Setting shared memory” on page 11This section details how to set a minimum shared memory value in Linux.“Remote configuration enablement” on page 12The SmartCloud Control Desk installation program can automatically configuremiddleware. You must enable a remote access protocol for each system onwhich you intend to install the middleware.“System password policy settings” on page 13Be familiar with the password policies of systems you are using as part of aSmartCloud Control Desk deployment.“Backing up the Deployment Engine database” on page 13These instructions are for backing up the Deployment Engine database.Backups are used to restore the database to the state it was before installing.“Programmatically verifying prerequisites”You can use the prerequisite verification utility to verify that installationprogram prerequisites are present on a system. Use this utility before startingthe middleware and product installation programs.

Programmatically verifying prerequisitesYou can use the prerequisite verification utility to verify that installation programprerequisites are present on a system. Use this utility before starting themiddleware and product installation programs.

About this task

The prerequisite verification utility checks the following items:v Operating system requirements, including fix packs.v Hardware requirements, including memory and hard disk space.v Port availability.

2 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server)

v Middleware requirements such as software packages, library files, directorypermissions, host names, and installation locations.

Note: This utility cannot be used to check Oracle WebLogic Server.

You can start the prerequisite verification utility from the product installationlaunchpad or from the command line. When started from the launchpad, the utilityruns in interactive mode. When started from the command line, the prerequisiteverification utility accepts various parameters. The prerequisite verification utilitymust be run on the system hosting the prerequisite being checked. You cannot usethis utility to check prerequisites on a remote system.

Table 1. System verification parameters

Parameters Details

-component Specifies the type of component being verified. At least one component must beused with the prerequisite verification utility.

dbserverUse the dbserver parameter to have the prerequisite verification utility checkfor DB2® prerequisites.

dirserverUse the dirserver parameter to have the prerequisite verification utility checkfor IBM Tivoli Directory Server prerequisites.

bsiUse the bsi parameter to have the prerequisite verification utility check forprerequisites required by the product installation program. Run theprerequisite verification utility with the bsi parameter on the administrativeworkstation.

Syntax example:

tpae_req_check.bat -component bsi

If you do not use the -component parameter, you are prompted to specifycomponents when using the utility.

Multiple components can be specified as comma-separated values.

-input The prerequisite verification utility can accept a property file as input. The utilityverifies property values found in the file.

For example, the default DB2 server port parameter is DB2_SERVER_PORT=50000.The prerequisite verification utility verifies that this port is available on the DB2server host.

The default input property file is tpae.properties, and is found on themiddleware installation media in the SystemRequirements directory. There are alsoseveral sample property files found in the SystemRequirements\sample_property_files. These sample property files contain custom valuesdefined for particular operating systems. You can copy these property files to thesystem and modify them, or create your own, before running the prerequisiteverification utility.

Syntax example:

tpae_req_check.bat -component dbserver -input path to the property file

If you do not use the input parameter when you run the prerequisite verificationutility, the utility is run in interactive mode. You are prompted for individualvalues to be verified.

Chapter 1. Preparing for installation 3

Table 1. System verification parameters (continued)

Parameters Details

-mode The prerequisite verification utility can be run in silent or interactive mode.

interactiveBy default, the prerequisite verification utility is run in interactive mode. Ifyou do not specify the -mode parameter, the utility defaults to running ininteractive mode. When started from the launchpad, the utility runs ininteractive mode.

silentIf you use the silent qualifier, you can also use the input parameter andsupply a property file. If an input file not provided, default property valuesare used. The output must also be directed to a file to view the results.

Syntax example:

tpae_req_check.bat-component dbserver-mode silent-input path to the property file > prereqresults.log

-lang Parameter used to specify the locale of the system being verified.

Syntax example:

tpae_req_check.bat-component dbserver-lang en

Results are produced in the language of the locale specified.

This is an optional parameter.

By default, the language set in the system locale is used. If the resource bundle isnot found for the system locale, or, the system locale language is not supported,messages are displayed in English.

-trace Parameter used to specify trace output statements while the utility is running.

NoneSelecting this qualifier results in no trace information being generated whilethe utility is running.

VerboseSelecting this qualifier results in detailed trace information being generatedwhile the utility is running.

NormalSelecting this qualifier results in default trace information being generatedwhile the utility is running.

Syntax example:

tpae_req_check.bat-component dbserver-trace None

Procedure1. Log on to the system you are checking for prerequisites with a user ID that has

permission to run scripts on the system. Ensure that the middlewareinstallation media is mounted or otherwise available to the system. Thisexample procedure uses values found in the default tpae.properties file toverify that a system is suitable to host DB2 for a SmartCloud Control Deskdeployment.


2. Open a command-line window and change directory to the SystemRequirementsdirectory of the middleware installation media.

3. Run the prerequisite verification utility. Specify the component being checkedand the property file to use.tpae_req_check.bat-component dbserver-input d:\SystemRequirements\tpae.properties

In this example, the tpae.properties file is located in the same directory as thetpae_req_check.bat script.

Results

After the prerequisite verification utility has completed successfully, results areprinted to the screen.

CTGIN8117I : The Tivoli Pre-requisite Scanner has been launched.CTGIN8118I : The Tivoli Pre-requisite Scanner exited with the return codeIBM Prerequisite Scanner

Version : 1.0.34Build : 20101109OS Name : Microsoft Windows Server 2003, Enterprise Edition Service Pack 2User Name: Administrator

Machine InfoMachine name : MYMACHINESerial Number: KKKKKK0OS Serial : 66666-666-6666666-66666

PAE [not defined] [version 07500000]:Property Result Found Exp...======== ====== ===== ===...os.totalPhysicalMemory PASS 2.00GB 1.90GBnetwork.hasFQDN FAIL False TrueDisk#1 (C:\ibm\tivoli\mwi\workspace) PASS 27.99GB 300MBDisk#2 (C:\Temp\1) PASS 27.99GB 1000MBDisk#3 (C:\Temp\1) PASS 27.99GB 250MBnetwork.availablePorts.db2 PASS 135,445,1025,2967,3389,5800,5900,139 50000network.availablePorts.ctginst PASS 135,445,1025,2967,3389,5800,5900,139 50005Disk#4 (C:\Program Files\IBM\SQLLIB) PASS 27.99GB 1.40GB

ALL COMPONENTS :Property Result Found Exp...======== ====== ===== ===...C: PASS 27.99GB 2.91GB

Prereq Scanner Overall Result: FAILprereq_checker.bat 1

These values can also be redirected to a file when starting the command from thecommand line.

If any of the verification steps report a failure, resolve the issue and rerun theverification utility before installing SmartCloud Control Desk components.

Table 2 contains a list of the properties checked. Use this information to analyzeprerequisite verification utility results.

Table 2. Prerequisite verification utility properties

Property Description

CpuArchitecture Verifies the machine architecture is supported.


Table 2. Prerequisite verification utility properties (continued)

Property Description

disk(rw permissions) Checks read/write permissions of required directories.

network.availablePorts.* Verifies required ports are available.

The following example checks to ensure a port required by DB2 is available.

network.availablePorts.db2inst=50000

network.dns Verifies there is a DNS entry for the system on the DNS server.

network.fqdn Verifies that the system host name is fully qualified.

os.architecture Verifies the operating system architecture is supported.

os.dir.tmp/home Verifies required permissions for the system directories

os.FreePagingSpace Verifies adequate free paging space is available on the system.

os.iodevicestatus Verifies the I/O device status of the system.

os.lib.ksh Checks the ksh library.

os.lib.libstdc++.so.5 Verifies a prerequisite library is available on the system.

os.lib.xlC.rte=xlC.rte.9.0.0.8+ Verifies a prerequisite library is available on the system.

os.mountcheck Checks for the existence of nosuid on the file system.

os.package.rpm Verifies prerequisite packages are available on the system.

os.RAMSize Reports system RAM available.

os.SELinux Determines if selinux is enabled.

os.servicePack Verifies required service packs are installed on the system.

os.shell.default Determines the default shell for users.

os.space.* Determines disk space availability for various file systems.

The following example shows the check made for the middleware installationprogram workspace.

os.space.root=[dir:root=/root/ibm/tivoli/mwi/workspace,unit:MB]300

os.totalPhysicalMemory Reports physical RAM available to the operating system.

os.ulimit Identifies user limits configured on the system.

os.Version Reports the operating system type and version.

Checking port availabilityYou need to ensure that certain ports are available before using the productinstallation programs.

About this task

You must check to see if ports are in use and accepting connections for the systemyou are using to host middleware.

For example, port 50000 must be made available for DB2.

Port 7001 must be made available for Oracle WebLogic Server.

If you intend to use these default port values, ensure that the port is not alreadyassigned before you run installation programs.


You can either use the prerequisite verification utility to check for port availability,or you can check manually.

Procedure1. Open the appropriate port checking utility on the host system. If present, check

firewall rules for the system.2. Check the availability of ports required by SmartCloud Control Desk. If you

find that port already assigned, ensure that you choose another value whenprompted by the middleware installation program.“Programmatically verifying prerequisites” on page 2You can use the prerequisite verification utility to verify that installationprogram prerequisites are present on a system. Use this utility before startingthe middleware and product installation programs.

Accessing system directoriesBefore using the product installation programs, you need to assign accesspermission to particular directories.

Before you begin

Before using the product installation programs, you need to assign accesspermission for the /tmp and /home directories on Linux systems.

About this task

The user that starts the product installation programs requires read, write, andexecute permissions for the /tmp and /home directories. If one of these directoriesuses a symbolic link, for example, /products/home, ensure that symbolic linkdirectory also has the proper access.

Procedure1. Log in to the system as a user with root authority on the system.2. Enter the following commands:

#chmod 777 /tmp#chmod 777 /home

AIX and HP-UX tar command requirementsBoth the native UNIXtar command and the GNU version of the tar command arerequired by the middleware installation program. Because the native utility doesnot support long file names, ensure that GNU tar version 1.14 or higher isinstalled. 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 tarpaths. The GNU tar path must be defined before the native UNIX tar path. Forexample, the native tar utility is installed in /usr/bin and the GNU tar utility isinstalled in /opt/freeware/bin/tar.

If you have set a symbolic link to overwrite the native UNIX tar command withthe GNU tar command an error occurs.

http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html

AIX font requirementsAIX requires specific fonts in order to produce reports.


http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html

About this task

When producing reports from AIX systems, TrueType fonts must be available onthe system.

Procedure1. Install TrueType fonts on the AIX system.2. Ensure the fonts-path environment variable refers to the location of the fonts.

Increasing AIX file size and number of descriptorsFor SmartCloud Control Desk to function correctly, you must increase the defaultnumber of file descriptors that are allowed for the root user and set the maximumallowable file size to unlimited.

About this task

To increase the allowable file size and number of allowable descriptors for the rootuser in AIX, complete the following steps:

Procedure1. Edit the /etc/security/limits file by opening it in a text editor.2. Locate the section for the root user, and change the parameters to the following

values:root:

fsize = -1nofiles = 8192

A value of -1 for the fsize parameter indicates no limit.3. Save and exit the file. You must log out as root and log back in for these

changes to take effect.4. Verify the settings from a command window using the following command:

ulimit -a

Output from the ulimit command is like the following example:time(seconds) unlimitedfile(blocks) unlimiteddata(kbytes) 2097152stack(kbytes) 32768memory(kbytes) unlimitedcoredump(blocks) 2097151nofiles(descriptors) 8192

Increasing AIX paging spaceTo successfully install and run SmartCloud Control Desk, you must increase thedefault paging space for the AIX system to a minimum of 4 GB, or, preferably, thetotal amount of physical memory in the system.

About this task

In order to add more paging space, you add more logical partitions to the system.

Procedure1. Determine the current amount of paging space available to the server by

issuing the following command.lsps -a


This command results output contains the following information, for example:

Page Space Physical Volume Volume Group Size Used

hd6 hdisk0 rootvg 5632MB 2

2. Determine the size of a logical partition by issuing the following command:lslv hd6

This command results in output that includes partition information, forexample:

Table 3.

LPs PP Size

44 127 megabytes

In the example output, there are a total of 44 Logical Partitions that are each128 Mb in size. These results show a total of 5632 Mb of paging space availableto the system.

3. Add more logical partitions, which are required in order to add more pagingspace, by issuing the following command:chps -s xx yyy

Where xx is the number of logical partitions to add and yyy identifies thelogical volume. For example,chps -s 10 hd6

adds 10 logical partitions to the logical volume hd6, which results in adding1280 Mb to the paging space.

Enabling asynchronous I/O on AIXIBM Tivoli Directory Server requires asynchronous I/O be enabled on AIX systems.

About this task

Enabling asynchronous I/O on AIX is an installation requirement, so this stepmust be run before running the middleware installation program. You need toperform this step only if the system hosts the IBM Tivoli Directory Server.

Without asynchronous I/O, DB2 database instances cannot be started successfully.

Without asynchronous I/O, Oracle database instances cannot be startedsuccessfully.

To turn on asynchronous I/O follow these steps:

Procedure1. Log in to the system as root.2. Open a terminal and run the following command:

smit chgaio

3. From the System Management Interface Tool (SMIT) dialog box, change STATEto be configured at system restart from defined to available.

4. Click OK.5. Exit SMIT.


6. Run the following command from the command line:smit aio

7. In the System Management Interface Tool (SMIT) dialog box, select ConfigureDefined Asynchronous I/O, and then click Enter.

8. Reboot the system to enable the changes.

Checking for required libraries on LinuxThe SmartCloud Control Desk deployment requires certain Linux system libraries.

Procedure1. Locate the libstdc++.so.5 library in the /usr/lib/ directory. If this library is

not installed, the middleware installation program throws an error whenrunning the middleware installation program in graphical mode. If you cannotlocate this library on your system, locate the RPM package for your system thatcontains this library and install the package.

2. Ensure that you have the libstdc++33-32bit-3.3.3-11.9.x86_64.rpm packageinstalled before running the product installation program. SUSE LinuxEnterprise Server 10 64-bit systems hosting manually configured middlewaremust host this package.

3. Ensure you have the compat-libstdc++ library installed on Red Hat EnterpriseLinux v6 systems running the product installation program or the processsolution installation program.

Configuring the JRE in LinuxIn some cases, the middleware installation program fails on Red Hat EnterpriseLinux 5 systems, or other systems with Security-Enhanced Linux (SELinux)enabled.

About this task

In one scenario, the middleware installation program fails with an error statingthat the Java™ Runtime Environment (JRE) cannot be found. In another scenario,the middleware installation program fails stating that it cannot find the VM.

Complete the following steps to avoid these problems:

Procedure1. Temporarily disable SELinux by using the setenforce 0 command.2. Run the middleware installation program.3. Re-enable SELinux by using the setenforce 1 command.4. Manually issue the chcon -R -t textrel_shlib_t install_home/jvm/jre> command.

Results

The middleware installation program is now able to locate the JRE. Alternatively,you can edit the /etc/selinux/config file and set SELINUX to either permissive ordisabled for a more permanent fix. This solution, however, affects the level ofsecurity for the entire system.

Setting the ulimitThis section details how to set the ulimit in Linux, which is used to define usersystem and process resource limits.


About this task

For Linux systems, you must set the ulimit for the system before using themiddleware installation program.

If you set the ulimit in .profile for root, the ulimit setting applies to all processes.

To set the ulimit, complete the following steps:

For AIX systems, see “Increasing AIX file size and number of descriptors” on page8.

Procedure1. From a command line, type ulimit -f unlimited

2. From a command line, type ulimit -n 8192

Setting the swap sizeSmartCloud Control Desk can be a resource-intensive application. Configure andtune your system for maximum performance. This section details how to set thesize of the swap space used in Linux systems.

About this task

Typically, the swap size for Linux is set to twice the amount of physical RAM inthe server. See the product documentation for your Linux distribution for moreinformation. For AIX systems, See “Increasing AIX paging space” on page 8.

Additional swap space can be made available to the system by:

Procedurev increasing the size of the existing swap partitionv creating a new, additional swap partitionv creating a swap file

Setting shared memoryThis section details how to set a minimum shared memory value in Linux.

About this task

For Linux systems, you must set a minimum shared memory value for the systembefore using the middleware installer.

To set the minimum shared memory value, complete the following steps:

Procedure1. From a command line, type sysctl kernel.shmmax and determine if the value is

less than 268435456 bytes (256 Mb).2. If you must increase the value, from a command line, type sysctl -w

kernel.shmmax=268435456.3. Update the value in /etc/sysctl.conf.


Remote configuration enablementThe SmartCloud Control Desk installation program can automatically configuremiddleware. You must enable a remote access protocol for each system on whichyou intend to install the middleware.

Use SSH for logging on to and configuring remote Linux and UNIX systems. UseWindows SMB for logging on to and configuring remote Windows systems.Windows SMB is a Windows protocol. The IBM JRE on the administrativeworkstation includes SSH.

You do not need an SSH client to remotely configure middleware on Linux orUNIX systems. But, you must install OpenSSH on remote non-Windowsworkstations so that you can log on to them, using SSH protocol.

Before you start the installation program, ensure that you can log on to any remoteservers with the protocols that you intend to use. Use the credentials that you planto supply to the installation program.

For remote Windows systems, ensure that the following requirements are metbefore installing the software:v The user name that you provide to the installation program must exist as a local

account on the remote system. This user must be a member of the WindowsAdministrators group.

v The following Windows services must be started on the remote system beforeyou begin a remote installation and configuration:– winmgmt (Windows Management Instrumentation)– RemoteRegistry (Remote Registry)– lanmanserver (Service)

v The SMB protocol must be enabled and configured to send NetBIOS overTCP/IP, by choosing to use port 139. Alternatively, you can configure SMB touse TCP/IP as the transport protocol, without NetBIOS, by configuring it to useport 445.

v Ensure that any ports that you use for remote protocols are not blocked byfirewalls or security policies, including ports 137 and 139. Port 139 is used ifSMB is configured to run on NetBIOS over TCP/IP. Port 445 is used if SMB isrun directly on TCP/IP, without NetBIOS.

v To disable simple file sharing, start Windows Explorer. Click Tools > FolderOptions, and clear the Use Simple File Sharing check box.

v The Windows administrative share (C$) and the interprocess communications(IPC$) folder must be shared.

v For Microsoft Windows Server 2008 systems that support password-protectedsharing, disable password-protection. Shares must be shared for the Guest orEveryone accounts.

v For Windows systems that have User Account Control (UAC) enabled, it mustbe disabled before software can be remotely installed and configured.

v If Cygwin is installed on the remote Windows system the SSH daemon (sshd)must be uninstalled or disabled.

For remote Linux or UNIX systems, ensure that the following requirements are metbefore installing the software:v For AIX systems, set the following SSH parameters located in the

/etc/ssh/sshd_config file:


– ClientAliveInterval 900– ClientAliveCountMax 10

Stop the SSH daemon using the stopsrc -s sshd command and then restart itusing the startsrc -s sshd command.

v For AIX systems, set the TMOUT and TIMEOUT variables in the user profilescript to 0. This setting prevents the user from idling out and being logged offthe remote system during the installation.

v The user name that you provide to the installation program must exist as aprivileged account (for example, root) on the remote systems.

v Ensure that a current version of OpenSSH is installed and running. Do not useOpenSSH 4.7.0.5302.

v For Oracle Solaris systems, the remote access protocols require the use ofinternal shell scripts that must be run within the korn (ksh) shell. The methodsneed ksh, even if the user ID that you use to log on to the remote system isconfigured to use a different shell. Consequently, Oracle Solaris systems musthave the ksh environment installed and properly configured.

v If you plan to remotely configure software on remote Linux or UNIX computers,ensure that SSH is installed.

Remote configuration does not support accessing network drives on the local orremote system.

System password policy settingsBe familiar with the password policies of systems you are using as part of aSmartCloud Control Desk deployment.

Your organization might have password policy regulations enforced on systems onyour network. Before deploying SmartCloud Control Desk, be sure that you arefamiliar with the password policies of systems used in the deployment, or youmight experience errors during installation.

For example, Microsoft Windows Server 2008 systems have a stricter set ofpassword requirements than previous versions configured by default. If you arenot familiar with these stronger password requirements, you might experience anerror during the installation of SmartCloud Control Desk. This error occurs whencreating users on a Microsoft Windows Server 2008 system.

Password values that you provide during the SmartCloud Control Desk installationmust be compliant with the password policies set for the target system. Passwordsare not validated against the password policies of target systems at the time youenter them on the installation program panels. If your passwords do not conformto the password policies of systems used to deploy the product, errors occur whenthe installation program attempts to create these passwords during theconfiguration step,

Backing up the Deployment Engine databaseThese instructions are for backing up the Deployment Engine database. Backupsare used to restore the database to the state it was before installing.


Before you begin

Back up the Deployment Engine database of the system before and after applyingany updates to an existing deployment. Use backups to recover from partialinstallation attempts.

About this task

To back up the Deployment Engine database, complete the following steps:

Procedure1. Set up the environment using the following command:

Windowsc:\install_home\ctg_DE\acsi\setenv.cmd

UNIXcd install_home/ctg_DE/acsi./setenv.sh

2. Run the command to back up the Deployment Engine registry:

Windowsc:\install_home\ctg_DE\acsi\bin\backupdb.cmd backup file name

UNIXcd install_home/ctg_DE/acsi/bin./backupdb.sh backup file name

Use a meaningful name for backup file name to reflect the fact that it contains thestate of the registry after your installation of SmartCloud Control Desk. Forexample, DEBackupAfterInstall.

Specifying host name valuesDo not use localhost for host name values in the installation program. Specify thefully 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 fullyqualified host name, consult the system documentation for assistance.

Establishing a fully qualified host name on Windows systemsUse this task to establish a fully qualified host name on Windows systems.

About this task

To establish a fully qualified host name on Windows systems, complete thefollowing steps.

Procedure1. On the desktop, right-click My Computer.2. Select Properties.3. On the Computer Name tab, click Change.4. Enter a fully qualified host name in the Computer name field, and then click

More.Alternatively, you can provide the IP address for the system.5. In the DNS Suffix and NetBIOS Computer Name window, verify that the

Primary DNS suffix field displays a domain name, and then click OK.6. In the Computer Name Changes window, click OK.7. Click Apply and close the System Properties window.


Forcing the middleware installer to use alphanumeric hostnamesYou can force the use of alphanumeric host name use within the middlewareinstallation program by starting it from the command line and using theforceHostname=true parameter.

Example

The following example shows a use of the forceHostname=true parameter:mwi-console -V forceHostname=true

What to do next

If you launched the middleware installation program from the command line usingthe forceHostname=true parameter, then you are required to provide analphanumeric value in the Hostname field. An IP address results in an errormessage.

Enabling full text search for IBM DB2Full text search is a search option that lets you search for words and phrases, aswell as perform more complex searches using wildcards and logical operators. ForSmartCloud Control Desk 7.5.1, it is essential to install and enable the Text Searchfeature that comes with DB2 9.7.5 or later.

About this task

The steps that you take depend on whether you are installing a new instance ofSmartCloud Control Desk 7.5.1 , or you are upgrading from an earlier release. Thisprocedure applies to a new installation. If you are upgrading from an earlierrelease, refer to the Upgrade Guide.

Important: Follow this procedure before you install SmartCloud Control Desk.

Procedure1. Ensure that DB2 9.7.5 or later is installed.2. From the DB2 server, enable full text search. For more information, see

Installing and configuring DB2 Text Search .3. Install SmartCloud Control Desk.

LaunchpadThe IBM SmartCloud Control Desk launchpad serves as a centralized interface forlaunching a collection of installation programs and product information.

The launchpad application assists you in choosing which product installationprograms you must install and indicates the order in which they must be installed.

Use the SmartCloud Control Desk launchpad to:v start the middleware installation program.v start the prerequisite checker utility.v start the SmartCloud Control Desk installation program.v start the Service Provider support installation program.v access the SmartCloud Control Desk information center, including information

used to plan the SmartCloud Control Desk installation and deployment.


http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.ts.doc/doc/c_installation.html

Just before starting the launchpad, ensure that you meet the middlewareprerequisites. Ensure that you have the correct service pack levels for yourenvironments and always use fully qualified domain names when entering valuesfor the installation program.

Starting the launchpadUse the following information to start the SmartCloud Control Desk launchpad

Before you begin

Launchpad generated messages are captured in a hidden log frame while thelaunchpad is running. To show the log frame on the bottom of the launchpadpanels, hold the CTRL key while simultaneously clicking the banner frame of thelaunchpad. Messages that are generated while the launchpad is running are notautomatically saved on the hard disk drive. You can manually save the messagesfrom a session by clicking Save at the bottom of the log frame and then specifyingwhere you want to save the file.

About this task

To start the IBM SmartCloud Control Desk launchpad, complete the followingsteps:

Procedure1. Log on to an account with system administration privileges on the computer

where you want SmartCloud Control Desk components to be installed.2. Start the launchpad from the root directory of the installation image:

v Windows: Start the launchpad by using the launchpad.exe program.v AIX: Start the launchpad from the root directory by using the launchpad.sh

program.The launchpad program uses the system default browser to run. If thedefault browser on AIX is Firefox, it is likely that the launchpad programdoes not run properly due to the ksh shell interface. If you must use thelaunchpad with the Firefox browser, follow these steps to modify it.a. Download and extract the launchpad images as described in the

download document.b. Modify /user_dir/launchpad/Firefox.sh and remove the following lines:

typeset +r LOGNAME 2>/dev/nullLOGNAME=lp_user_$$; export LOGNAME

c. Run the launchpad from /user_dir

v Linux: Start the launchpad by using the launchpad.sh program.For example,./launchpad.sh


Chapter 2. Deploy with automatic middleware configuration

Use this information to use product installation programs and tools to install andautomatically configure a SmartCloud Control Desk deployment within yourenterprise.

This information provides a high-level overview or road map of tasks you need tocomplete in order to deploy SmartCloud Control Desk with automatic middlewareconfiguration.

In this scenario, you use the middleware installation program to install andautomatically configure new instances of the following components:v DB2v IBM Tivoli Directory Server

You use the product installation program to perform further middlewareconfiguration tasks automatically before finally deploying the product itself.

Oracle WebLogic Server must always be configured manually.

You can use the middleware installation program to install DB2. You then use theSmartCloud Control Desk installation program to automatically configure it.

Middleware installation program middleware deployment plan overviewThe deployment plan resides in the workspace directory and is generated fromdeployment choices selected in the middleware installation program.

The plan is a series of deployment steps and configuration parameters. Each step isresponsible for installing and uninstalling one portion of the middleware. Whendeployment choices are changed, the existing deployment plan is deleted andreplaced with the new deployment plan.

Installing middleware using the middleware installation programYou use the middleware installation program to install middleware components foruse with IBM SmartCloud Control Desk. The middleware components that youchoose to install, and the associated configuration parameters, are recorded in adeployment plan for the target system.

Before you beginv Plan your installation.v Use the planning worksheets for middleware installation to record the values

that you need to specify during the installation procedure.

About this task

These instructions cover the use of the middleware installation program to installand configure middleware components on a single server. The single serverdeployment scenario is suitable for demonstration, test, or training purposes.

The following middleware components are installed:


v DB2v Tivoli Directory Server

If you want to use Oracle WebLogic Server with SmartCloud Control Desk, youmust install it separately or reuse an existing instance, and then configure itmanually.

You must run the middleware installation program locally on the target system.You can start the program by using the launchpad or a setup script. When you usethe launchpad, the program files are copied to a temporary directory on the targetsystem. When you use a setup script, no files are copied to the target system. Ifyou are installing on a 64-bit Windows system, you must use a setup script to startthe program.

Procedure1. 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 terminalwindow, you must be logged in as the root user.

2. Start the middleware installation program by using the launchpad or a setupscript.v Use the launchpad to start the middleware installation program.

a. Start the launchpad.

Windows (32-bit only)From the root directory of the installation image, run thefollowing command: launchpad.exe.

Linux and UNIXFrom the root directory of the installation image or productmedia, run the following command: launchpad.sh.

b. Run the middleware installation requirements checking utility.c. Click Middleware.

v Run the following command to launch a setup script which starts themiddleware installation program:

Windowslaunchpad\Install\MWI\setupwin.bat /l

Linux and UNIXlaunchpad/Install/MWI/setupUNIX.sh -l

3. Specify the workspace location for this installation of middleware.4. On the Deployment Choices panel, select the components that you want to

install on this system.5. Review the summary of the generated deployment plan and click Next to

proceed with configuration of the specified components. When you click Next,the middleware installation program verifies the prerequisites for installingthe specified components.

6. To specify a host name for the target system other than the default host name,select Override the local machine hostname and enter a host name in theHostname field. You cannot clear this option after it has been selected,however, you can change the value in the Hostname field.

7. Optional: To specify a default password that can be used throughout themiddleware installation program, select Use this password as the value forall subsequent passwords and enter the required password.

8. Specify the following details for DB2 Enterprise Edition Server:


a. Specify the installation directory.b. Specify administrative account details for the DB2 Administration Server.

The password that you specify is also used as the password for the DB2default database instance.

c. If you are installing on a Linux or AIX system, specify fenced user accountdetails for DB2.

9. Specify an instance name, port, and user name for the default databaseinstance.

10. Specify an instance name, port, and user account details for the SmartCloudControl Desk database instance.

11. Specify names for the DB2 administrators and users groups. A users groupname is required only if DB2 Enterprise Edition Server is installed on aWindows system.

12. Specify the following details for IBM Tivoli Directory Server:a. Specify the installation directory.b. Specify a distinguished name and password for the Tivoli Directory Server

administrator.13. Specify the configuration parameters that are required for Tivoli Directory

Server, including the organizational unit, organization suffix, and countrysuffix that are required when the directory server is used with SmartCloudControl Desk.

14. Specify the following details for the Tivoli Directory Server database instance:a. Specify the name of the DB2 database that you are using to hold Tivoli

Directory Server data.b. Specify the name and password of the Tivoli Directory Server database

instance.15. Specify the configuration parameters that are required when Tivoli Directory

Server is being used as the LDAP resource for WebSphere® Application ServerNetwork Deployment security.

16. Specify the bind distinguished name and password that are required forbinding to the LDAP instance. When you click Next, the middlewareinstallation program validates the host and directory information that youspecified for the directory server. The specified information must be verifiedbefore the installation can proceed.

17. Specify whether you need to copy the SmartCloud Control Desk middlewareinstallation images from the product media to your file system:v If you need to copy the middleware installation images from the product

media, specify the source and destination directories.v If the middleware installation images are already saved to the file system,

specify the directory where they are located.18. Optional: Before you deploy, verify the integrity of the middleware installation

images by selecting the option for checksum validation. If the checksumoperation fails, click Back and recopy the images. If you do not select thisoption and the middleware installation images are corrupted or otherwiseinaccessible from the directory specified, an error occurs. If you encounter thiserror, you must replace the corrupted middleware installation images andthen restart the middleware installation program.

19. Specify a directory to use for middleware installation program temporary filesand extracted middleware installation images.

20. Select Deploy the plan to confirm that you are ready to install and configurethe selected middleware components.

Chapter 2. Deploying with automatic middleware configuration 19

21. Click Deploy to initiate the installation process.22. When the deployment is complete, click Finish to close the installation

wizard.

Middleware installation program logsMiddleware installation program log files are in the workspace directory that wasdefined in the middleware installation program.

There are several types of log files.

User interface logsThe logs generated by the middleware installation program user interfaceare in the workspace directory.

The middleware installation program logs all information in<workspace_loc>/mwi.log: Default workspace locations for all platforms areas follows:

WindowsC:\ibm\tivoli\mwi\workspace

Linux /root/ibm/tivoli/mwi/workspace

AIX /ibm/tivoli/mwi/workspace

The mwi.log file is the high-level log file that was generated by the mostrecent invocation of the middleware installation program. If an erroroccurs, examine this log file first. An entry in this log file might direct youto a lower-level log file.

Log files named mwi.logX, where X is a number, are copies of the mwi.logfile from earlier invocations of the middleware installation program. So, forexample, mwi.log0 is produced after the first invocation of the middlewareinstallation program. mwi.log1 is produced after the second invocation ofthe middleware installation program.

Logs for steps run by the user interfaceIn addition to collecting input from the user, the user interface of themiddleware installation program also performs several system checks.Examples of system checks run by the user interface runs include:v dependency checking to ensure that the operating system meets the

deployment requirementsv inventorying the software on the system to locate existing instances of

middleware products deployed by the middleware installation programv checking the available disk space to ensure that there is enough for the

deployment

Each of these checks is produced in the form of a step so that it can also berun as part of the deployment plan. When the user interface runs a step, itcopies the step into a subdirectory of the workspace directory. The log filesgenerated by a step are in the same subdirectory. These files follow thesame pattern as a step that is run as part of the deployment plan.

Logs for the deployment planThe deployment plan is in the directory <Workspace Directory>/hostname/deploymentPlan, where host name is the host name of the currentsystem. Each time the deployment plan is used to install or uninstallmiddleware products, a process ID is assigned and log files are generated.


The log files for the deployment plan are in the subdirectorylogs/processID. The primary log file for the deployment plan isDeploymentPlan.log, a high-level log file that lists the steps started as partof the deployment plan.

Logs for the workstation planThe machine plan is located in the directory <Workspace Directory>/hostname/deploymentPlan/MachinePlan_host name. The log files for the machineplan are in the logs subdirectory. The primary log files for the machineplan are named MachinePlan_host name_processID. These log files containthe output generated by Apache ANT when running the machine planANT script.

Logs for steps in the deployment planEach step in the deployment plan is in a directory named <WorkspaceDirectory>/host name/deploymentPlan/MachinePlan_hostname/stepNum_stepID, where stepNum is the sequence number of this stepin installation processing order of the deployment plan and stepIDidentifies the step. The log files for the step are in the logs subdirectory.

Some steps might provide a message log file namedstepID_processID.message, which contains a few entries that summarizethe result of starting the step. All steps provide a trace log file namedstepID_processID.log, which contains many entries, typically includinginformation about the input parameters and the substeps started.

Logs for substepsEach step contains one or more substeps. The substeps perform the actualinstallation, uninstall, and checking work for the middleware installationprogram.

Each substep is in the directory <Workspace Directory>/hostname/deploymentPlan/MachinePlan_host name/stepNum_stepID/operation/substepNum_substepID, where operation is the ANT target in the step ANTscript that starts this substep. substepNum is the sequence number of thissubstep in the processing order of the step, and substepID identifies thesubstep. Typical values for operation are install, uninstall, and check.

The log files for the substep are typically in a subdirectory namedprocessID/logs.

Log files generated by the native middleware installation programs arealso kept here.

As an example, the log file generated by the middleware installation programduring DB2 installation on a UNIX system would be found in the followingdirectory: <workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_DB2_9.7/install/01_BASE/<Time_Stamp>/logs/db2setup.log

Middleware installation program log referenceThe following logs are produced during the use of the middleware installationprogram.

DB2 Installation Step

DB2 installation logs can be found in the following locations:

DB2 baseThe following DB2 base log files can be found in the <workspace>/


<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_DB2_9.7/install/01_BASE/<Time_Stamp>/logs directory:v DB2_ESE_InstallProduct_<TimeStamp>.err

v DB2_ESE_InstallProduct_<TimeStamp>.log

v DB2_ESE_MoveDB2InstallLogsToLogsLoc_<TimeStamp>.err

v DB2_ESE_MoveDB2InstallLogsToLogsLoc_<TimeStamp>.log

v DB2_ESE_Register_DB_<TimeStamp>.err

v DB2_ESE_Register_DB_<TimeStamp>.log

v DB2_ESE_Verify_DB2_Level_<TimeStamp>.err

v DB2_ESE_Verify_DB2_Level_<TimeStamp>.log

v db2setup.log

v de_processreq.log

v de_processreq.log_utf8

v de_trace.log

For Windows, the following additional files will be available:v DB2_ESE_Verify_DB2_Service_20080805_063132GMT.err

v serviceList.log

The de_processreq.log contains status information. This log file providesdetails on which action has failed. The failed action log can be examinedfor more information. The db2setup.log file is the native product log forDB2. This log contains DB2 installation information.

DB2 fix packThe following DB2 fix pack log files can be found in the<workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_DB2_XX/install/02_FP/<Time_Stamp>/logs directory:v DB2_ESE_FP2MoveDB2LogsToLogsLoc_<Time_Stamp>.err

v DB2_ESE_FP2MoveDB2LogsToLogsLoc_<Time_Stamp>.log

v DB2_ESE_InstallDB2Fixpack_<Time_Stamp>.err

v DB2_ESE_InstallDB2Fixpack_<Time_Stamp>.log

v DB2_ESE_ListDB2FPAdmin_<Time_Stamp>.err

v DB2_ESE_ListDB2FPAdmin_<Time_Stamp>.log

v DB2_ESE_ListDB2FPinstance_<Time_Stamp>.err

v DB2_ESE_ListDB2FPinstance_<Time_Stamp>.log

v DB2_ESE_StartDB2FPAdminInstance_<Time_Stamp>.err

v DB2_ESE_StartDB2FPAdminInstance_<Time_Stamp>.log

v DB2_ESE_StopDB2FPAdminInstance_<Time_Stamp>.err

v DB2_ESE_StopDB2FPAdminInstance_<Time_Stamp>.log

v DB2_ESE_UpdateDB2_<Time_Stamp>.err

v DB2_ESE_UpdateDB2_<Time_Stamp>.log

v DB2_ESE_Verify_DB2_FP_Level_<Time_Stamp>.err

v DB2_ESE_Verify_DB2_FP_Level_<Time_Stamp>.log

v de_processreq.log

v de_processreq.log_utf8

v de_trace.log

v installFixPack.log


The de_processreq.log contains status information. This log file providesdetails on which action has failed. The failed action log can be examinedfor more information. The installFixPack.log file is the native log for thefix pack. This log contains DB2 fix pack installation information.

No fix pack logs are available on Windows systems.

If you encounter a failure wrapper failure, more information can be found in the$(_TempLocation) directory in the <Time_Stamp> folder. This directory contains thelogs related to DB2 installation

DB2 Configuration Step

The following DB2 configuration logs can be found in <workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_DB2_Configuration/install/01_CONFIG/<Time_Stamp>/logs:v checkpasswdCreated.log

v createuser.log

v etcgroupfile.log

v etcpasswdfile.log

v setUserPassword.log

For Linux, including Linux on IBM System z®, the following additional files areproduced:v permissions.log

v catalogLocalNode.log (produced in the 02_CONFIG folder)v catalogLocalNode.log (produced in the 02_CONFIG folder)v startDB2.log

For Windows, the following additional files are produced:v createDB2instance.log

v localEnvVariables.log

v setTCPIPCommForDB2instance.log

v setTCPIPPortForDB2instance.log

v setWindowsServiceToAutoStart.log

For UNIX, including Linux, Linux on IBM System z, and AIX, the followingadditional files are produced:v createinstance.log

v SetTCPIPCOMM.log

v stopDB2.log

v updatePort.log

IBM Tivoli Directory Server DB2 for SmartCloud Control Desk Step

The following IBM Tivoli Directory Server DB2 for SmartCloud Control Desk logscan be found in <workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_ITDS_DB2_CCMDB/check/01_CHECKS/<Time_Stamp>/logs:v etcgroupfile.log

v etcpasswdfile.log


IBM Tivoli Directory Server Installation Step

IBM Tivoli Directory Server installation logs can be found in the followinglocations:

GSKITThe following IBM Tivoli Directory Server installation log files can befound in the <workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_ITDS_6.3/install/01_GSKIT/<Time_Stamp>/logs directory.v de_processreq.log

v de_trace.log

For Windows and Linux, including Linux on IBM System z, the followingadditional files are produced:v GSKit_Install_GSKit_<Time_Stamp>.log

v GSKit_Install_GSKit_<Time_Stamp>.err

For 32-bit Windows systems, the following additional file is produced:v gskInstall.log

For 32-bit Windows systems, the following additional files are produced:v ISScript_Install.log

v gskInstall.log

For AIX systems, the following additional files are produced:v GSKit_Install_JS_RTE_20080721_084044GMT-06.00.log

v GSKit_Install_SA_RTE_20080721_084044GMT-06.00.log

v vGSKit_Install_TA_RTE_20080721_084044GMT-06.00.log

v rteList.log

The de_processreq.log contains status information. This log file providesdetails on which action has failed. The failed action log can be examinedfor more information.

IBM Tivoli Directory Server baseThe following IBM Tivoli Directory Server base log files can be found inthe <workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_ITDS_6.3/install/02_BASE/<Time_Stamp>/logs directory:v de_processreq.log

v de_trace.log

For Windows, the following additional files are available:v ldapinst.log

v registryList.log

For Linux, including Linux on IBM System z, the following additional filesare produced:v ITDS6.3_CheckRPMEntry_<Time_Stamp>.err

v ITDS6.3_CheckRPMEntry_<Time_Stamp>.log

v rpmList.log

For AIX systems, the following additional files are produced:v ITDS6.3_CheckRTEEntry_<Time_Stamp>.log

v ITDS6.3_CheckRTEEntry_<Time_Stamp>.err


v rteList.log


IBM Tivoli Directory Server fix packThe following IBM Tivoli Directory Server fix pack log files can be foundin the <workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_ITDS_6.3/install/02A_FP/<Time_Stamp>/logs directory:v de_processreq.log

v de_trace.log

For Windows, the following additional file are available:v ldapinst.log

For Linux, the following additional files are produced:v ITDS6.3_CheckRPMEntry_<Time_Stamp>.err

v ITDS_InstallFixpack_<Time_Stamp>.log

v rpmList.log

For AIX systems, the following additional files are produced:v ITDS_InstallFixpack_<Time_Stamp>.err

v ITDS_InstallFixpack_<Time_Stamp>.log

v ITDS6.3_CheckRTEEntry_<Time_Stamp>.log

v ITDS6.3_CheckRTEEntry_<Time_Stamp>.err

v rteList.log


IBM Tivoli Directory Server language packThe following IBM Tivoli Directory Server language pack log files can befound in the <workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_ITDS_6.3/install/03_LP/<Time_Stamp>/logs directory:v de_processreq.log

v de_trace.log

For Windows, the following additional files are available:v ldapLP_inst.log

v registryList.log

For Linux, including Linux on IBM System z, the following additional fileis produced:v checkIfRPMEntryExists_<Time_Stamp>.log

For AIX systems, the following additional files are produced:v checkIfRTEEntryExists_<Time_Stamp>.log

v checkIfRTEEntryExists_<Time_Stamp>.err


IBM Tivoli Directory Server Configuration Step

The following IBM Tivoli Directory Server configuration logs can be found in<workspace>/<machine_name>/deploymentPlan/MachinePlan_<machine_name>/000XX_ITDS_Configuration/install/01_CONFIG/logs:v createUsers.log

v netUserCheck.log

For Windows, the following additional files are produced:v PasswdNeverExpires.log

v configureDB.log (produced in the 02_CONFIG folder)v configureDNPassword.log (produced in the 02_CONFIG folder)v configureSuffix.log (produced in the 02_CONFIG folder)v startInstanceTool.log (produced in the 02_CONFIG folder)v startServer.log (produced in the 02_CONFIG folder)v audit.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v bulkload.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v db2clicmds.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v lostandfound.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v traceibmslapd.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v adminaudit.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v ibmdiradm.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v db2cli.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v perftune_stat.log (produced in the C:\idsslapd-idsccmdb\logs folder)

v idstools.log (produced in the C:\idsslapd-idsccmdb\logs folder)

For UNIX, including Linux,Linux on IBM System z, and AIX, the followingadditional files are produced:v permissions.log

v ITDS_LDAP_Config.encrypted.ldif (produced in the 03_CONFIG folder)v addLDIFData.log (produced in the 03_CONFIG/logs folder)v idsadm.log (produced in the /var/idsldap/V6.3 folder)

v idsadmdb2.log (produced in the /var/idsldap/V6.3 folder)

v idsadmdb2cmds.log (produced in the /var/idsldap/V6.3 folder)

Configuring IBM Tivoli Directory Server user and groupstrings

You can configure user and group strings in IBM Tivoli Directory Server to adapt itto your deployment needs.

About this task

You can manually create user and group strings for Tivoli Directory Server duringinstallation.

If you configure directory server user and group strings for a system that hostsonly the IBM Tivoli Directory Server , you must manually create properties in theinput.properties file of the ITDS_CONFIGURATION step of the deployment plan.


Procedure1. Edit the input.properties file that is in the directory server folder at:

Workspace\machine name\deploymentPlan\MachinePlan_machineshortname\00006_ITDS_Configuration. For example, in Windows, the defaultlocation of the input.properties file is C:\ibm\tivoli\mwi\workspace\mymachine.ibm.com\deploymentPlan\MachinePlan_mymachine\00006_ITDS_Configuration.

2. Add the following properties:was_nd.secure.GroupSuffix=ou\=groups,ou\=SWG,o\=IBM,c\=USwas_nd.secure.UserSuffix=ou\=users,ou\=SWG,o\=IBM,c\=US

3. If Tivoli Directory Server configuration parameters are customized, change theapplicable values to your custom values on the configuration parameters panel.For example, if your custom values are ou=SWG1 and the Organizationcountry suffix is o=IBM1,c=US1, you must manually replace all occurrences ofthose values in the input.properties file:was_nd.secure.GroupSuffix=ou\=groups,ou\=SWG1,o\=IBM1,c\=US1was_nd.secure.UserSuffix=ou\=users,ou\=SWG1,o\=IBM1,c\=US1

Uninstalling middlewareTo uninstall IBM SmartCloud Control Desk middleware, you must run themiddleware installation program and select the options to remove the previousdeployment.

Before you begin

If you chose to deploy SmartCloud Control Desk middleware with a directoryserver, ensure that it is active.

About this task

The middleware installation program creates a registry when installing SmartCloudControl Desk middleware. Using the native middleware uninstall programs causesthis registry to be out of sync with what is deployed. As a result, errors occurwhen you attempt to reinstall middleware with the middleware installationprogram.

Procedure1. Stop and start servers as required:

a. Stop the IBM Tivoli Directory Server (IBM Tivoli Directory Server v6.3 -idsccmdb).

b. Stop the IBM Tivoli Directory Server daemon (IBM Tivoli Directory AdminServer v6.3 - idsccmdb).

c. Start DB2.d. Start the idsccmdb DB2 instance (DB2 - DB2COPY1 - IDSCCMDB).e. Start the IBM Tivoli Directory Server daemon (IBM Tivoli Directory Admin

Server v6.3 - idsccmdb)2. Log in as Administrator on Windows and root on Linux and AIX.3. Start the launchpad by running the following command from the root

directory of the downloaded installation image:

Option Description

Windows launchpad.exe


Option Description

Linux launchpad.sh

AIX launchpad.sh

4. In the launchpad navigation pane, click Install Product.5. In the Install the middleware section, click Middleware and step through the

launchpad panels.6. When you are prompted to browse to a workspace, specify the workspace

directory that contains the currently deployed plan, and click Next. Thedefault location for the workspace is the last workspace location specified. Ifyou did not specify a path previously, the default location for the workspaceisc:\ibm\tivoli\mwi\workspace

7. In the Select Operation panel, select Undeploy the plan, and click Next.8. From the undeployment preview panel, click Next to undeploy the plan.9. Exit the middleware installation program.

10. On UNIX systems, remove the following DB2 references from the/etc/services file:v db2c_db2insxy 50001/tcpv db2c_db2inst1 50000/tcp

Reinstalling middleware with IBM DB2You can run an installation of the middleware with the DB2 user and groupsettings from a previous installation.

Before you begin

Remove all middleware products and their components before you reinstall themiddleware.

About this task

When DB2 is uninstalled, users and groups are not removed. You can specify thesame DB2 user and group values or replace them with new users and groupswhen you run the installation program.

Procedure1. Verify that all middleware products were properly removed by examining the

deployment plan log files. The log files are in the subdirectory WorkspaceDirectory/host name/deploymentPlan/logs/processID. The primary log file forthe deployment plan is DeploymentPlan.log.

2. The middleware installation program creates a default instance for DB2 andadds the owner of the default instance to the DB2 administrator group that youspecify. Specify the DB2 users and groups that you want to use for thisinstallation:v Provide the same values that were previously used for the DB2

administrators group.v Remove the existing instance owner and specify a new administrators group.

You cannot specify an existing instance owner with a new DB2administrators group.

3. Start the middleware installation program from the launchpad.


Manually configuring WebLogic ServerWebLogic Server can be used with SmartCloud Control Desk if it is manuallyconfigured.

About this task

You can use a WebLogic Server as your J2EE server. The SmartCloud Control Deskinstallation process prepares EAR files on the SmartCloud Control Deskadministrative workstation. These files are then manually deployed to yourWebLogic Server. The SmartCloud Control Desk installation program does notautomatically configure a WebLogic Server environment It does not install orotherwise deploy SmartCloud Control Desk applications into a WebLogic Serverserver.

Manually configuring WebLogic Server consists of the following tasks:

Procedure1. “Creating the MAXIMOSERVER domain”2. “Configuring JMS options for integration framework” on page 303. “Configuring JMS for the email listener in WebLogic Server” on page 31

Creating the MAXIMOSERVER domainThis section details how to create the MAXIMOSERVER domain within WebLogicServer.

About this task

To create the MAXIMOSERVER domain within WebLogic Server, complete thefollowing steps:

Procedure1. Launch the Configuration wizard tool.

v For Windows systems, select Start > Programs > BEA Products > Tools >Configuration Wizard.

v For UNIX systems, launch the Configuration wizard using the config.shcommand located in <WebLogic_Home>/weblogic10/common/bin.

2. From the welcome panel, select Create a new WebLogic Server domain, andthen click Next.

3. From the Select a Domain Source panel, select Generate a domain configuredautomatically to support the following products, and then click Next.

4. From the Specify Domain Name and Location panel, name the domainMAXIMOSERVER, and then click Next

5. From the Configure Administrator Username and Password panel, enter anadministrator user ID and password, and then click Next.

6. From the Configure Server Start Mode and JDK panel, enter the followinginformation, and then click Next.

WebLogic Server Domain Startup ModeSelect Production.

Selecting this option requires that you provide a user ID and passwordin order to deploy applications.


JDK SelectionSelect a JDK with a version number 1.6.0 or greater from the suppliedJDKs.

7. Proceed through the next few panels until you reach the CustomizeEnvironment and Services Settings panel. From the Customize Environmentand Services Settings panel, select the default option No, and then click Next.

8. From the Create WebLogic Server Domain panel, change the Domain Namevalue to MaximoServer, and then click Create to create the domain.

9. Once the domain has been created, ensure that the Start Admin Server optionis cleared, and then click Done to close the Configuration wizard. On UNIXsystems, this option is not displayed.

Configuring JMS options for integration frameworkThis procedure provides details on steps to configure JMS queues.

Before you begin

You need to be familiar with the Oracle WebLogic Server Administration Consoleto complete the following procedure. See your Oracle WebLogic Serverdocumentation on how to navigate through the Oracle WebLogic ServerAdministration Console.

Procedure1. Launch Internet Explorer and open the MAXIMOSERVER Administration Console

by typing the following URL:http://host_name:7001/console

2. Sign in by entering your user ID and password.3. Create three persistent file stores with the following configuration parameters:

Option Description

File Store Name sqinstore, sqoutstore, cqinstore

File Store Target MAXIMOSERVER

File Store Directory C:\WebLogic, or another directory of your choice

File stores have better performance in general. However, you can choose tocreate database-based stores. To choose between file stores and database-basedstores, consult your Oracle WebLogic Server documentation.

4. Create three JMS servers with the following configuration parameters:

Option Description

Properties Name sqinserver, sqoutserver, cqinserver

Server Target MAXIMOSERVER

Bytes Maximum 20% or below of the allotted JVM heap size

It is recommended that you configure the Bytes Maximum for the JMS serversto a value of 20% or below of the allotted JVM heap size to prevent the OracleWebLogic Server from running out of memory.

5. Create a JMS system module named intjmsmodule with MAXIMOSERVER asthe target server.

6. Add a connection factory resource to the JMS module:

Option Description

Name intjmsconfact


Option Description

JNDI Name jms/maximo/int/cf/intcf

Target MAXIMOSERVER

7. Add three queue resources to the JMS Module:a. Create the queue resource type.b. Create a new subdeployment with the same name as the queue.c. Assign the subdeployment_nameserver server target to the subdeployment.

Option Description

Queue 1 Name: sqin JNDI Name: jms/maximo/int/queues/sqin

Queue 2 Name: sqout JNDI Name: jms/maximo/int/queues/sqout

Queue 3 Name: cqin JNDI Name: jms/maximo/int/queues/cqin

Template None

8. Enable the JMS connection factory for integration framework:a. Select the intjmsconfact link.b. From the Transactions tab, check the XA Connection Factory Enabled

check box.c. Set the Maximum Messages per Session to -1.

9. Save and activate the changes.

What to do next

You need to stop and restart the MAXIMOSERVER application server for the update totake effect.

Configuring JMS for the email listener in WebLogic ServerYou use the email listeners application to receive and process requests throughemail in the form of email messages.

About this task

To configure JMS queues for the WebLogic Server, complete the following steps:

Procedure1. Log in to the WebLogic Server administration console.2. Create a persistent store.

a. In the Domain Structure panel, expand Services and then click PersistentStores.

b. Click New and select the option to create a file store.c. Enter lsnrstore for the name of the file store and c:\wls10 as the directory,

and then click Finish.3. Create a JMS Server

a. In the Domain Structure panel, under Services > Messaging , click JMSServers, enter the following information, and then click Next.

Name Enter a name for a new JMS server, for example, lsnrserver.


Persistent StoreSelect lsnrstore.

b. For the Target, select AdminServer, and then click Finish.4. Create a JMS System Module

a. In the Domain Structure panel, under Services > Messaging , click JMSModules, and then click New.

b. Enter a value for the Name field, such as lsnrjmsmodule, and then clickNext.

c. Select the option for AdminServer, and then click Next.d. Select the option for Would you like to add resources to the JMS system

module?, and then click Finish.5. Add a connection factory to the JMS module.

a. From the Summary of Resources table of the lsnrjmsmodule module, clickNew to add a resource.

b. Select the Connection Factory option, and then click Next.c. From the Connection Factory Properties panel, enter the following

information, and then click Next.

Name Enter a name for the new connection factory. For example,lsnrconnfact.

JNDI NameEnter jms/mro/lsnr/lsnrcf.

d. Ensure AdminServer is selected, and then click Finish

6. Add a queue to the JMS module.a. From the Summary of Resources table of the lsnrjmsmodule module, click

New to add a resource.b. Select the Queue option, and then click Next.c. From the JMS Destination Properties panel, enter the following information,

and then click Next.

Name Enter a name for the new queue. For example, lsnrqueue.

JNDI NameEnter jms/mro/lsnr/qin.

TemplateNo template is necessary.

d. Click Create a new Subdeployment, select lsnrserver, and then clickFinish.

7. Set the XA option for the connection factory.a. Select lsnrconnfact, and then select the Transactions tab.b. Ensure that the XA Connection Factory Enabled option is selected, and then

click Save.8. Click Activate Changes to save and activate all changes.9. To enable an email listener to use JMS queues, a Message Driven Bean is

configured through a deployment descriptor file that is part of the installation.You configure the Message Driven Bean by removing comment lines fromsections within the deployment descriptor files. Edit the ejb-jar.xml andweblogic-ejb-jar.xml files.a. Open the install_dir\applications\maximo\mboejb\ejbmodule\META-INF\

ejb-jar.xml file in an editor, uncomment the following sections, and thensave the file:


Email Listener JMS is not deployed by default<message-driven id="MessageDriven_LSNRMessageBean"><ejb-name>LSNRMessageBean</ejb-name>ejb-class>psdi.common.emailstner.LSNRMessageBean</ejb-class>transaction-type>Container</transaction-type><message-destination-type>javax.jms.Queue</messagedestination-type></message-driven>

Email Listener JMS is not deployed by default<container-transaction><method><ejb-name>LSNRMessageBean</ejb-name><method-name>*</method-name></method><trans-attribute>Required</trans-attribute></container-transaction>

b. Open the c:\ibm\smp\maximo\applications\maximo\mboejb\ejbmodule\META-INF\weblogic-ejb-jar.xml file in an editor, uncomment the followingsection, and then save the file:Email Listener JMS is not deployed by default<weblogic-enterprise-bean><ejb-name>LSNRMessageBean</ejb-name><message-driven-descriptor><destination-jndi-name>jms/mro/lsnr/qin</destination-jndiname><connection-factory-jndi-name>jms/mro/lsnr/lsnrcf</connection-factory-jndi-name></message-driven-descriptor><transaction-descriptor><trans-timeout-seconds>600</trans-timeout-seconds></transaction-descriptor><jndi-name>LSNRMessageBean</jndi-name></weblogic-enterprise-bean>

Installation program overviewThe SmartCloud Control Desk installation program provides an interface forinstalling and deploying SmartCloud Control Desk, which includes the processautomation engine and process managers.

The SmartCloud Control Desk installation program records choices you makeabout your SmartCloud Control Desk deployment. It records configurationparameters associated with those choices, and then installs and deploysSmartCloud Control Desk based upon the information you entered.

There are two installation paths available to you when you are installingSmartCloud Control Desk.

SimpleA simple deployment consists of installing SmartCloud Control Deskmiddleware on one system. You do not have the option of using existingmiddleware within your organization with SmartCloud Control Desk. Allmiddleware used with SmartCloud Control Desk must be installed on thesystem with the middleware installation program with default values.SmartCloud Control Desk is installed with default values provided by themiddleware installation program and SmartCloud Control Desk installationprogram.

If you intend to override default values used by the simple deploymentpath, you must use the custom deployment path instead.


If you are deploying with Oracle WebLogic Server, you cannot choose thisoption.

CustomA custom deployment typically involves deploying SmartCloud ControlDesk across several systems. Some of these systems might already hostmiddleware products that you want to use with your SmartCloud ControlDesk deployment. You can modify default installation values when youdeploy with the custom installation path.

This deployment option does not require you to spread the SmartCloudControl Desk deployment across several systems. You can enter the nameof the local host as the destination for all SmartCloud Control Deskcomponents.

If you are deploying with Oracle WebLogic Server, you must choose thisoption.

The SmartCloud Control Desk installation program can automate the configurationof some middleware for use with SmartCloud Control Desk.

The SmartCloud Control Desk installation program cannot automate theconfiguration of Oracle WebLogic Server.

If you choose not to have the SmartCloud Control Desk installation programautomatically configure middleware, you must configure that piece of middlewaremanually before the installation of SmartCloud Control Desk.

Important: When you are entering LDAP values for SmartCloud Control Deskinstallation panel fields, be aware of the product-specific syntax rules for usingspecial characters in an LDAP string. In most cases, special characters must bepreceded by an escape character in order to make it readable by the directoryserver. Failing to escape special characters contained in an LDAP string used withSmartCloud Control Desk results in SmartCloud Control Desk errors.

Many directory server products consider a blank space as a special character that ispart of the LDAP string. If you enter an LDAP string with an unescaped blankcharacter at the end of a field value, you encounter SmartCloud Control Deskerrors.

For more information about special character usage in LDAP strings, see theproduct documentation for your directory server.

Information that you enter for the SmartCloud Control Desk installation programis stored in the maximo.properties and install.properties files and the Maximo®

database. These values are populated into the panel fields of the SmartCloudControl Desk installation program on subsequent uses of the program. If youcancel the installation program, it recalls most values that you entered the nexttime you start it. Values excluded from being saved in this manner are theSmartCloud Control Desk installation directory and the shortcut option chosenduring the installation. You can restore the default values in the SmartCloudControl Desk installation program by deleting <Maximo_Home>/applications/maximo/properties/maximo.properties and <Maximo_Home>/etc/install.properties. If you cannot locate the maximo.properties file in the<Maximo_Home> directory, look for it in the system temp file directory.


Installing the product and automatically configuringmiddleware

To install SmartCloud Control Desk, you run the installation program from thelaunchpad. The installation procedure automatically configures middleware onmultiple servers, using default values.

Before you begin

Ensure that you meet prerequisite conditions.v Oracle WebLogic Server must have been manually configured for your

deployment.v The database server, the directory server, and application server services must be

started and active.v The /tmp and /var/tmp directories must be present on the system. The

installation program depends on these directories for information duringdeployments on IBM WebSphere Application Server Network Deployment.

v On the administrative workstation, temporarily shut down any noncriticalprocesses that can have a negative effect on the installation, such as antivirussoftware.

v Ensure that the Windows DEP setting does not prevent the launchpad fromrunning: Select Start > Settings > Control Panel > System > Advanced >Performance > Settings > Data Execution Prevention. Select Turn on DEP foressential Windows programs and services only and click Apply. You might beasked to reboot the server.

v For Linux and UNIX systems with middleware installed, the command hostname-f must return a fully qualified host name. If necessary, consult thedocumentation for your operating system. Alternatively, you can provide the IPaddress for the system.

v Enable a remote execution and access service on every system that hasmiddleware installed. Each remote system must support a remote accessprotocol. It must also accept remote logins from a user name and password thatwere configured on the target server. Remote access protocols include SSH andWindows SMB. If the remote system is a Windows server, you must configureremote execution and access to use SMB.

v The DB2 database must be prepared.– If DB2 is installed on a Linux or UNIX system, you must create the instance

user and the home directory for the user on the DB2 server.– The database instance owner home directory must have 8 GB of space

available regardless of whether a database is installed in that location.– The user ID for the DB2 instance administrator must have SYSADM (system

administration) authority. You specify this user ID during the productinstallation program. See the DB2 product documentation for informationabout creating a user with SYSADM authority on the DB2 server. You mustadd root to a group with SYSADM authority for UNIX systems.

About this task

The instructions are for a multiple server installation that uses default values.

If you experience problems with the user interface of the installation programwhen installing on AIX 6.x systems remotely, reattempt the installation locally. Usethe console or an X terminal on the system locally.


Procedure1. Log in on the administrative system.2. Start the product installation program from the launchpad.

a. Start the launchpad. Browse to the root directory of the downloadedinstallation image, and run the following command:

Windowslaunchpad.exe

UNIX launchpad.shIf the launchpad does not start the installation, you can start the productinstallation program directly. On the downloaded installation image, browseto \Install\\, and run one of the following commands:

Windows

v install.bat

v install_win64.bat

UNIX

v install_aix64.sh

v install_linux32.sh


3. Select a language for the installation and click OK.4. On the Choose Installation Folder panel, specify the path to the location

where you want to install SmartCloud Control Desk.You can specify a description for the installation. A description is useful fordifferentiating between multiple installations that are hosted on the sameadministrative workstation.

5. Review the information that is on the Verify Installation Location panel. Thepanel shows any previous installation information that was found based onthe installation directory that you specified on the previous panel. After youadvance past this panel, you cannot go back and change the installationdirectory for this installation.If a more recent version of the installation program is found in the specifiedtarget directory, you are notified. The notification means that you are using anolder version of the installation program. The version found on theadministrative workstation is newer and can contain important features andenhancements. To use the newer version of the installation program, select theoption on the notification panel and click Next. This action exits the currentinstallation process and restarts the installation process with the newerinstallation program. If you do not select the option, you continue theinstallation with the older version of the installation program.

6. On the Package Summary panel, review the package deployment information.This panel lists version information for both new and existing packages on thesystem. Target package version information indicates the package versionbeing currently deployed.

7. On the Choose Deployment panel, specify Simple or Custom as thedeployment type.

8. On the Import Middleware Configuration Information panel, you selectImport middleware configuration information to have the productinstallation program reuse the middleware installation program values. Thesevalues are used as default values for the same fields in the productinstallation program.


The Workspace location field refers to the location of the topology file thatcontains the values that were specified for the middleware installationprogram. The file is located in the workspace that was defined during themiddleware installation task. For example, C:\ibm\tivoli\mwi\workspace forWindows or /root/ibm/tivoli/mwi/workspace for UNIX.If you selected the simple deployment, the middleware default information isnot used.

9. On the Database Type panel, specify the software to use for the Maximodatabase.

10. On the Database panel, specify configuration information for your databasesoftware.For things such as the database user ID, the database name, the databaseinstance for SmartCloud Control Desk, and the schema name, if the values donot exist when you specify them, they are created.For DB2, the user ID cannot be the same as the instance administrator user ID.Database users and database instance names cannot contain spaces.For DB2, the database instance is created if it does not exist, but the user andits associated home directory must exist on the DB2 server. For DB2, theschema name can be the same value as the owner of the table spaces that aredefined or it can be a different value, such as maximo.After you specify configuration information for your database software, theinstallation program validates the information with the database server.

11. On the Automate Database Configuration panel, you can specify that databasecreation and configuration is to be automated.If you do not select the option, you must configure the database manually.

12. On the Remote Access Authorization panel, specify authorization informationfor the automatic database configuration feature. Specifying the values enablesremote configuration.

13. On the Database Administration panel, specify configuration informationabout the database. The required information varies by database platform.For DB2, the instance administrator user ID cannot be the same as thedatabase user ID. And the Windows service user ID must have administrativeauthority on the system.

14. On the Database Tablespace panel, specify information about the table spaceof the database.When you click Next, the product installation program connects to thedatabase server and validates the information that you specified.

15. When the database validation is complete, on the Application Server Typepanel, specify the application server type for the product deployment.You must manually configure WebLogic Server and manually deployapplication files.

16. On the Specify Maximo Users panel, enter Maximo database user information.

Maximo administration userThe product administrator user ID that is used for initial configurationand adding users.

Maximo system registration userThe user ID that is used for the self-registration of users.

Maximo system integration userThe user ID that is used with enterprise adapters.


Custom user ID and password values are stored in the Maximo database. Thedefault user IDs of maxadmin, maxreg, and maxintadm are also created asusers in the Maximo database. Creation of the default user IDs is done forinternal processing purposes. If you use Maximo database security forauthentication and authorization, the default user IDs can be used to log in tothe application. If you regard this condition as a security risk, you can modifythe passwords for the default user IDs. You modify passwords for the userIDs in the Users application.

17. On the SMTP Configuration panel, specify the SMTP configurationinformation that is used by workflows to communicate with workflowparticipants.The administrator e-mail address is the e-mail address that is used to sendmessages. If you leave the fields blank, you must configure the SMTPparameters through the product interface as a post-installation task.

18. On the Data Integration and Context Menu Services Options panel, click theoption that indicates where the database tables for these functions are created:in the Maximo ("same") database, or in a separate database instance that youcreated for this purpose. If you are installing the Entry edition, choose theMaximo database. These tables are created but are not used by the Entryedition.

19. On the Base Language Selection panel, specify the base language for theinstallation.

20. On the Additional Language Selection panel, you can optionally specify oneor more additional languages that the installation is to support.

21. On the Run Configuration Step panel, specify how to perform theconfiguration step of the installation. If you do not select an option, theconfiguration step proceeds when you click Next.

Copy files now, but perform the installation configuration step laterSelect this option to copy files from the installation source to theadministrative workstation. You must perform the configuration stepat a later time to complete the deployment.

Important: Do not install another product before you complete theconfiguration step of the original installation. Installing anotherproduct before you run the configuration step for this installationoverwrites the taskstore, which prevents the original installation fromever being deployed.

The configuration values that you specify are stored in theinstall_home\maximo\applications\maximo\properties\maximo.properties and install_home\etc\install.properties files.You run the configuration steps outside of the product installationprogram by using the taskrunner utility, in the install_home\scriptsdirectory. Run the taskrunner utility from the command line.install_home\scripts\taskrunner [CONTINUE <STOPONERROR|NOSTOPONERROR>]

The taskrunner uses the configuration values that are stored in themaximo.properties and install.properties files to configureSmartCloud Control Desk.

If you run taskrunner with the NOSTOPONERROR parameter, thetaskrunner continues despite errors. If you run taskrunner with theSTOPONERROR parameter, the taskrunner stops when it encounters anerror. If you used STOPONERROR, you can rectify the conditions thatcaused the error. You can then resume the installation where the last


successfully completed task was recorded in the previous attempt bystarting taskrunner with the CONTINUE parameter.

Defer the update of the Maximo databaseSelect this option if you want to manually run the database updatetask for the product deployment. This option can be used when thereis a fix pack available that addresses known issues with the updatedbscript. In this scenario, you choose the Defer the update of theMaximo database option, apply the fix pack, and then run theupdatedb -v1 command manually.

22. On the Choose Shortcut Folder panel, specify where you want SmartCloudControl Desk icons created.If you select In the Start Menu and use Internet Explorer, add theSmartCloud Control Desk URL to the trusted sites web content zone. Disablethe option that requires server verification for all sites in the zone.Do not select In the Quick Launch Bar. The selection does not create ashortcut in the Quick Launch bar.Attention: Shortcuts are created for Windows systems only. BecauseWebLogic Server deployments are a manual process, you must manuallyupdate any shortcuts that you create. You update shortcuts after youmanually deployed the SmartCloud Control Desk EAR files.

23. On the Input Summary panel, review the information that you provided forthe product installation program.If necessary, use Previous to return to previous panels to change values.

24. On the Pre-Installation Summary panel, review the installation information,then click Install.The installation process begins. You can monitor the progress of theinstallation by viewing the messages that are shown.

25. On the Installation Completed panel, review any information presented, thenclick Done.Attention: In some cases, on AIX systems, the Installation Completed panelmight appear blank. Click Done to exit the installation program.

“Restarting middleware on Windows” on page 177This procedure describes how to restart middleware on Windows, if you mustrestart any middleware services.“Restarting middleware on UNIX” on page 178Middleware services on Linux and AIX platforms occasionally must berestarted, such as when a reboot occurs. Middleware servers and services mustbe active before running the SmartCloud Control Desk installation program.

Installing optional contentInstall the relevant optional content package for your edition of the product.

Optional content is often used in development environments as a way to begindeveloping your own content.

If you do not install optional content during the product installation process, youcan install it later. If you install it later, you must update the database and rebuildand deploy the maximo.ear file.


Installing optional integration modulesInstall integration module packages in order to set up integrations with otherproducts.

You can install these integration modules from the Integrations page of thelaunchpad:

IBM Tivoli Provisioning Manager Integration ModuleThis integration module enables you to integrate Tivoli ProvisioningManager with the release management process. For example, you can useTivoli Provisioning Manager as a Definitive Media Library. See the Releasemanagement section of the information center for more information aboutthis integration.

Deployed Assets CMS LIC Enablement PackageThis package is required if you plan to use the Context Menu Service tomanage launch-in-context actions for deployed assets. See the Planningsection of the information center for information about options forlaunch-in-context actions.

CI AppsCMS LIC Enablement PackageThis package is required if you plan to use the Context Menu Service tomanage launch-in-context actions for actual configuration items. See thePlanning section of the information center for information about optionsfor launch-in-context actions.

Rational ClearQuest OSLC IntegrationsThis integration enables you to use the Open Services for LifecycleCollaboration (OSLC) technology to link from the Problems application toRational ClearQuest to share information about problems and theirsolutions.

Rational Team Concert™ OSLC IntegrationsThis integration enables you to use the Open Services for LifecycleCollaboration (OSLC) technology to link from the Problems application toRational Team Concert to share information about problems and theirsolutions.

If you do not install integration modules during the product installation process,you can install them later. If you install them later, you must update the databaseand rebuild and deploy the maximo.ear file.

Post installation for Oracle WebLogic Server deploymentsThere is a post installation step required for Oracle WebLogic Server deployments.

About this task

When using Oracle WebLogic Server as the application server for your SmartCloudControl Desk deployment, the installation program produces an EAR file. Youmust then manually deploy that file to Oracle WebLogic Server.

When using Oracle WebLogic Server, you must modify the weblogic.xml file andrebuild the maximo.ear file before deploying it.

Procedure1. Install the updated JDK 1.6 program.


a. Obtain the latest JDK program with a version number 1.6.0 SR7 or greater,from http://www.oracle.com/technetwork/java/index.html

b. Start the installation program.c. Accept the license agreement.d. Change the installation destination path to your Oracle home folder, and

click OK , then Next.e. Accept any additional prompts to install the JDK program so that the

installation process can complete successfully.2. If you are using an Oracle database, copy the oraclethin.jar file.

a. Copy the oraclethin.jar file from the administrative workstation to theserver where you installed Oracle WebLogic Server. Use any file transferprotocol that is available.

b. The oraclethin.jar file is in the install_home\maximo\applications\maximo\lib directory. The default install_home directory isC:\IBM\SMP\Maximo\Applications\Maximo\lib. Copy the oraclethin.jar fileto the J2EE server and into the wls11g/server/lib directory. For example,C:/Oracle/wls11g/server/lib.

3. Edit the domain configuration file for appropriate Java settings.a. Navigate to Install_dir\user_projects\domains\mydomain\bin.b. Right-click and edit (do not double-click) setDomainEnv.cmd (Windows) or

setDomainEnv.sh (UNIX).c. Using your text editor, search for and replace jdk entries with entries that

configure Oracle WebLogic Server to use the updated JDK program. Twoinstances must be replaced.

d. (Oracle only) Search for PRE_CLASSPATH. Set the parameter as follows:set PRE_CLASSPATH=%WL_HOME%\server\lib\oraclethin.jar (Windows)PRE_CLASSPATH={WL_HOME}/server/lib/oraclethin.jar (UNIX)

Note: This step is required for connecting to Oracle databases from OracleWebLogic Server.

e. Increase the Java Heap parameters by searching for MEM_ARGS and settingthe parameter as follows:set MEM_ARGS=-Xms512m -Xmx1024m -XX:MaxPermSize=512m (Windows)MEM_ARGS=-Xms512m -Xmx1024m -XX:MaxPermSize=512m (UNIX)

These parameters are case-sensitive. Ensure to include the minus (-) signbefore each parameter and to include the m after each value.

f. Search for set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES%. Insert anoption directly after this string, as follows:-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0

The entry looks like this example when complete:set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES%-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0-Dwlw.iterativeDev=%iterativeDevFlag% -Dwlw.testConsole=%testConsoleFlag%-Dwlw.logErrorsToConsole=%logErrorsToConsoleFlag%

g. Save and close the setDomainEnv.cmd file.4. Edit the \IBM\SMP\maximo\applications\maximo\maximouiweb\webmodule\WEB-

INF\weblogic.xml file and add the following entries:<session-descriptor><cookie-http-only>false</cookie-http-only></session-descriptor>


http://www.oracle.com/technetwork/java/index.html

5. Start the server without being prompted for user name and password. If youare working in Production mode and do not want to be prompted for theOracle WebLogic Server user name and password, create a boot.propertiesfile. This procedure stores the user name and password in an encrypted format.Place the following two lines in a text file:username=<administrator username>password=<administrator password>

The user name and password values must match an existing user account inthe Authentication provider for the default security realm. If you save the fileas boot.properties and locate it in the mydomain folder (for example,C:\BEA\User_projects\domains\mydomain), the server automatically uses this fileduring its subsequent startup cycles. The first time you use this file to start aserver, the server reads the file and then overwrites it with an encryptedversion of the user name and password.

6. Verify settings by starting Oracle WebLogic Server. To ensure that the edits thatyou made to the previous Oracle WebLogic Server files were accurate, start theOracle WebLogic Server.

7. Rebuild the maximo.ear file.\IBM\SMP\maximo\deployment\buildmaximoear

8. Deploy the maximo.ear file to Oracle WebLogic Server.

Deploying ear filesYou are now ready to deploy the EAR files from the Oracle WebLogic ServerAdministration Console. Deploying the EAR files starts the Maximo ApplicationServer.

Before you begin

Windows WindowsIf MAXIMOSERVER is not running, start it from a command prompt.

UNIX UNIXEnsure that the Oracle WebLogic Server daemon is running.

About this task

In order to view the Oracle WebLogic Server Administration Console, you need toalso install a Java Virtual Machine (JVM). Newer versions of Windows might notship with JVM.

Procedure1. Change to the my_domain directory:

Windows WindowsFrom a command prompt, change directory path to:drive_name:\weblogic_install_dir\user_projects\domain\my_domain

UNIX UNIXOpen a Terminal window (or a command prompt, if you are telnetingfrom a Windows computer) and change directory as follows:cd /home/mxadmin/weblogic_install_dir/user_projects/domains/my_domain

2. Type


Windows WindowsstartWebLogic.cmd

UNIX UNIX./startWebLogic.sh

and press Enter. Once the phrase: Server started in RUNNING mode displays,the Oracle WebLogic Server is running.

3. Start the MAXIMOSERVER Oracle WebLogic Server Administration Console bytyping the following URL in the address bar of your browser:http://host_name:7001/console

4. Log in to the administrative console with the administrative user name andpassword.

5. Click the Lock&Edit button in the Change Center section to set the server toedit mode.

6. Click the Deployments link in the Domain Structure section.7. In the Summary of Deployments section, click the Install button. The Install

Application Assistant opens.8. Click the upload your file(s) link.9. Click the Browse button next to the Deployment Archive field. Browse to

where you have maximo.ear file installed (c:/ibm/smp/maximo/deployment/default/ of the administrative workstation), select the file and click Open.

10. Click Next to upload the file to the Oracle WebLogic Server server.11. Click the radio button next to the maximo.ear file, and Next to continue the

deployment.12. Accept the default value to install the deployment as an application and click

Next.13. Accept all other default values and click Finish to start the deployment

process.14. 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.

15. Repeat Steps 8 through 14 to deploy maximoiehs.ear.16. Click the checkbox next to the maximo application.17. Click the dropdown arrow of the Start button and select Servicing all

requests. The Start Application Assistant displays.18. Click Yes to start the system.

Setting the Oracle WebLogic Server host nameSetting the Oracle WebLogic Server host name manually to access application helpinformation.

About this task

By default, the property used to store the host name for the SmartCloud ControlDesk help system is set to localhost. The fully qualified host name of the OracleWebLogic Server must be configured in the help system property to viewSmartCloud Control Desk application help topics. Complete this step after youhave deployed SmartCloud Control Desk EAR files to the Oracle WebLogic Server.


Procedure1. Log in to the SmartCloud Control Desk console as maxadmin.2. Browse to Go To > System Configuration > Platform Configuration > System

Properties

3. Using the Filter feature, search for the mxe.help.host Property Name.4. Expand the mxe.help.host property and set the attribute to the fully qualified

host name of the Oracle WebLogic Server.5. Select the mxe.help.host record check box.6. Click the Live Refresh icon in the toolbar.7. From the Live Refresh dialog, click OK.

Results

You are now able to access application help topics in the SmartCloud Control Deskuser interface.

Language deployment after database update deferralSelecting the option to defer the update of the Maximo database when installingthe product, affects how you deploy languages.

During installation, you have the option to defer the database update task. Thisoption prevents writing data to the database during the installation. Theinstallation program is limited to copying files to the administrative system andregistering product process solution packages. You add languages by completingthe installation, manually updating the database, and then updating languagesmanually.

“Manually deploying languages after database update deferral”Languages must be deployed manually if you defer database updates by theinstallation program.

Manually deploying languages after database update deferralLanguages must be deployed manually if you defer database updates by theinstallation program.

Before you begin

You must have run updatedb command before manually configuring languages forPSI packages.

About this task

To manually configure languages for PSI packages, complete the following steps:

Procedure1. Update language support for the core components.

Files for the language selections you made during the installation are extractedto the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory on the system.a. To update a language as the base language to use for the product, run the

following command:


install_home\maximo\tools\maximo\TDToolkit.bat-IMPORT-SLEN-TLlocale-maxmessfix

b. To add one or more languages as additional languages for use with theproduct, run the following command for each language you want to add:install_home\maximo\tools\maximo\TDToolkit.bat-ADDLANGlocale-maxmessfix

2. Update languages for additional packages.In order to determine which packages you need to update, change directory toinstall_home\maximo\tools\maximo\en\xliff. Each folder located in the xliffdirectory, with the exception of MAXUPG folder, is used as input for the-pmpupdate operation of TDToolkit. Unlike the process for updating languagesfor SmartCloud Control Desk, you run the TDToolkit command once for eachpackage. TDToolkit determines which languages are currently deployed andupdates all languages.a. Change directory to install_home\maximo\tools\maximo\en\xliff. and

identify a package folder to update, for example calibration.b. Update languages for the chosen package.

C:\IBM\SMP\maximo\tools\maximo\TDToolkit.bat-pmpupdatepackagedirectory

In this example, pmpupdatepackagedirectory could be pmpupdatecalibrationor pmpupdateconfig_pmp for example.

c. Repeat for each additional package that require language updates.



Chapter 3. Deploying automatically reusing existingmiddleware

Use this information to use SmartCloud Control Desk installation programs andtools to automatically configure existing middleware within your enterprise duringthe SmartCloud Control Desk deployment process.

This information provides a high-level overview or road map of tasks you need tocomplete in order to deploy SmartCloud Control Desk automatically. You usemiddleware already established in your enterprise.

In this scenario, you use the middleware installation program and the SmartCloudControl Desk installation program to automatically configure existing middlewareresources. Middleware configuration is performed automatically before deployingthe product.

Oracle WebLogic Server must always be configured manually.

The installation programs are used to automatically configure an existing DB2server in your environment.

Run the middleware installation program on existing middlewareservers

If you intend to reuse existing middleware servers with SmartCloud Control Desk,they must be configured before you run the SmartCloud Control Desk installationprogram.

This section contains information about configuring existing DB2 servers for usewith SmartCloud Control Desk using the middleware installation program.

Information for using the middleware installation program with IBM TivoliDirectory Server is included.

Details are provided for using the middleware installation program with MicrosoftActive Directory.

You cannot use the middleware installation program to configure existing Oracleservers.

Oracle WebLogic Server cannot be configured using the middleware installationprogram.

Microsoft SQL Server cannot be configured using the middleware installationprogram.

Ensure that all of your middleware is at supported levels for SmartCloud ControlDesk.

Figure 1. Deploying SmartCloud Control Desk reusing existing middleware


When you install and configure middleware in the middleware installationprogram and the SmartCloud Control Desk installation program, consider thefollowing special characters restrictions:

Table 4. Middleware object naming conventions

Naming Convention Details

DB2 naming conventions for Group names,user names, and user IDs.

Group names and user IDs on Linux andUNIX operating systems can contain up to 8characters and must consist of lowercasecharacters only.

Group names and user names on Windowscan contain up to 30 characters.

Names and IDs cannot be any of thefollowing values: USERS, ADMINS,GUESTS, PUBLIC, LOCAL, or anySQL-reserved word.

Names and IDs cannot begin with IBM, SQLor SYS. They must also not begin with theunderscore (_) character.

DB2 naming conventions for DB2 instances. Instance names can have up to 8 characters.

On Windows, no instance can have the samename as a service name.

DB2 naming conventions for passwords. For UNIX systems, passwords can be amaximum of 8 characters.

For Windows systems, passwords can be amaximum of 14 characters.

IBM Tivoli Directory Server conventions fordatabases and database aliases.

Database names must be unique within thelocation in which they are cataloged. ForLinux and UNIX , this location is a directorypath. For Windows it is a logical disk.

Database alias names must be unique withinthe system database directory. When a newdatabase is created, the alias defaults to thedatabase name. As a result, you cannotcreate a database using a name that exists asa database alias, even if there is no databasewith that name.

Database and database alias names can haveup to 8 characters.

Be mindful that the special characters @, #,and $ are not common to all keyboards.Avoid these characters when you create adatabase name.


Table 4. Middleware object naming conventions (continued)

Naming Convention Details

IBM Tivoli Directory Server conventions forusers, groups, databases, and instances

Values must not be longer than 8 characters.

Values cannot be any of the following:USERS, ADMINS, GUESTS, PUBLIC,LOCAL, or idsldap

Values cannot begin with IBM, SQL, or SYS.

Values must not include accented characters.

Values can include characters A through Z, athrough z, and 0 through 9.

Values must begin with characters Athrough Z or a through z.

Double-byte characters cannot be used inadministrator passwords values.

Passwords cannot contain the followingspecial characters: ` ' \ " |

The middleware installation program The middleware installation program doesnot validate that your password is compliantwith the operating system of the target host.Ensure that the password values youprovide are valid for your environment.

The middleware installation program doesnot allow the use of the '%' character onWindows and the use of the !, $, #, %characters on UNIX.

The middleware installation program doesnot check for accented characters in username values. The use of accented characterscan cause errors.

Configuring an existing DB2 with the middleware installationprogram

An existing DB2 server can be configured with the middleware installationprogram.

Before you begin

If you plan to configure an existing DB2 server with the middleware installationprogram, a set of users and groups must exist. These users and groups are used bythe middleware installation program during configuration.

Default values for users and groups include:

Users

v db2adminv dasusr1 (UNIX)v db2fenc1 (UNIX)

Groups

Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 49

v db2admns (Windows)v dasadm1 (UNIX)v dbgrp1 (UNIX)v db2fgrp1 (UNIX)

These values are default user and group values. These values can be customized ifthe values provided to the middleware installation program match the valuesfound on the system. Again, if these users do not exist on the system, you mustcreate them before you run the installation program.

About this task

If you have an existing DB2 installation that you would like to reuse forSmartCloud Control Desk, you can run the middleware installation program on thesystem to configure it. The middleware installation program identifies instances ofmiddleware that exist on the system that are compatible with SmartCloud ControlDesk, and it configures the existing instance for use with SmartCloud ControlDesk.

To have the middleware installation program configure an existing DB instance forreuse with SmartCloud Control Desk, complete the following steps:

Procedure1. Log in as a user with administrative authority.2. Start the middleware installation program from the launchpad.3. Complete the middleware installation program panels until you reach the

Deployment Choices panel.4. From the Deployment Choices panel, select Database Server, and then click

Next. The middleware installation program displays any instances of DB2found on the system.

5. From the Installation menu, select the appropriate instance to reuse, and thenclick Next.

6. Complete the remainder of the middleware installation program panels.“Installing middleware using the middleware installation program” on page 17You use the middleware installation program to install middleware componentsfor use with IBM SmartCloud Control Desk. The middleware components thatyou choose to install, and the associated configuration parameters, are recordedin a deployment plan for the target system.


About this task




Procedure1. “Creating the MAXIMOSERVER domain” on page 292. “Configuring JMS options for integration framework” on page 303. “Configuring JMS for the email listener in WebLogic Server” on page 31

Creating the MAXIMOSERVER domainThis section details how to create the MAXIMOSERVER domain within WebLogicServer.

About this task


Procedure1. Launch the Configuration wizard tool.

v For Windows systems, select Start > Programs > BEA Products > Tools >Configuration Wizard.

v For UNIX systems, launch the Configuration wizard using the config.shcommand located in <WebLogic_Home>/weblogic10/common/bin.

2. From the welcome panel, select Create a new WebLogic Server domain, andthen click Next.

3. From the Select a Domain Source panel, select Generate a domain configuredautomatically to support the following products, and then click Next.

4. From the Specify Domain Name and Location panel, name the domainMAXIMOSERVER, and then click Next









Configuring JMS options for integration frameworkThis procedure provides details on steps to configure JMS queues.


Before you begin


Procedure1. Launch Internet Explorer and open the MAXIMOSERVER Administration Console

by typing the following URL:http://host_name:7001/console


Option Description






Option Description







Option Description

Name intjmsconfact


Target MAXIMOSERVER


Option Description




Template None





What to do next


Configuring JMS for the email listener in WebLogic ServerYou use the email listeners application to receive and process requests throughemail in the form of email messages.

About this task


Procedure1. Log in to the WebLogic Server administration console.2. Create a persistent store.













b. Select the Connection Factory option, and then click Next.


c. From the Connection Factory Properties panel, enter the followinginformation, and then click Next.














ejb-jar.xml file in an editor, uncomment the following sections, and thensave the file:Email Listener JMS is not deployed by default<message-driven id="MessageDriven_LSNRMessageBean"><ejb-name>LSNRMessageBean</ejb-name>ejb-class>psdi.common.emailstner.LSNRMessageBean</ejb-class>transaction-type>Container</transaction-type><message-destination-type>javax.jms.Queue</messagedestination-type></message-driven>


b. Open the c:\ibm\smp\maximo\applications\maximo\mboejb\ejbmodule\META-INF\weblogic-ejb-jar.xml file in an editor, uncomment the followingsection, and then save the file:


Email Listener JMS is not deployed by default<weblogic-enterprise-bean><ejb-name>LSNRMessageBean</ejb-name><message-driven-descriptor><destination-jndi-name>jms/mro/lsnr/qin</destination-jndiname><connection-factory-jndi-name>jms/mro/lsnr/lsnrcf</connection-factory-jndi-name></message-driven-descriptor><transaction-descriptor><trans-timeout-seconds>600</trans-timeout-seconds></transaction-descriptor><jndi-name>LSNRMessageBean</jndi-name></weblogic-enterprise-bean>

Installation program overviewThe SmartCloud Control Desk installation program provides an interface forinstalling and deploying SmartCloud Control Desk, which includes the processautomation engine and process managers.

The SmartCloud Control Desk installation program records choices you makeabout your SmartCloud Control Desk deployment. It records configurationparameters associated with those choices, and then installs and deploysSmartCloud Control Desk based upon the information you entered.

There are two installation paths available to you when you are installingSmartCloud Control Desk.

SimpleA simple deployment consists of installing SmartCloud Control Deskmiddleware on one system. You do not have the option of using existingmiddleware within your organization with SmartCloud Control Desk. Allmiddleware used with SmartCloud Control Desk must be installed on thesystem with the middleware installation program with default values.SmartCloud Control Desk is installed with default values provided by themiddleware installation program and SmartCloud Control Desk installationprogram.

If you intend to override default values used by the simple deploymentpath, you must use the custom deployment path instead.

If you are deploying with Oracle WebLogic Server, you cannot choose thisoption.

CustomA custom deployment typically involves deploying SmartCloud ControlDesk across several systems. Some of these systems might already hostmiddleware products that you want to use with your SmartCloud ControlDesk deployment. You can modify default installation values when youdeploy with the custom installation path.

This deployment option does not require you to spread the SmartCloudControl Desk deployment across several systems. You can enter the nameof the local host as the destination for all SmartCloud Control Deskcomponents.

If you are deploying with Oracle WebLogic Server, you must choose thisoption.

The SmartCloud Control Desk installation program can automate the configurationof some middleware for use with SmartCloud Control Desk.


The SmartCloud Control Desk installation program cannot automate theconfiguration of Oracle WebLogic Server.

If you choose not to have the SmartCloud Control Desk installation programautomatically configure middleware, you must configure that piece of middlewaremanually before the installation of SmartCloud Control Desk.

Important: When you are entering LDAP values for SmartCloud Control Deskinstallation panel fields, be aware of the product-specific syntax rules for usingspecial characters in an LDAP string. In most cases, special characters must bepreceded by an escape character in order to make it readable by the directoryserver. Failing to escape special characters contained in an LDAP string used withSmartCloud Control Desk results in SmartCloud Control Desk errors.

Many directory server products consider a blank space as a special character that ispart of the LDAP string. If you enter an LDAP string with an unescaped blankcharacter at the end of a field value, you encounter SmartCloud Control Deskerrors.

For more information about special character usage in LDAP strings, see theproduct documentation for your directory server.

Information that you enter for the SmartCloud Control Desk installation programis stored in the maximo.properties and install.properties files and the Maximodatabase. These values are populated into the panel fields of the SmartCloudControl Desk installation program on subsequent uses of the program. If youcancel the installation program, it recalls most values that you entered the nexttime you start it. Values excluded from being saved in this manner are theSmartCloud Control Desk installation directory and the shortcut option chosenduring the installation. You can restore the default values in the SmartCloudControl Desk installation program by deleting <Maximo_Home>/applications/maximo/properties/maximo.properties and <Maximo_Home>/etc/install.properties. If you cannot locate the maximo.properties file in the<Maximo_Home> directory, look for it in the system temp file directory.

Installing the product and automatically configuringmiddleware

To install SmartCloud Control Desk, you run the installation program from thelaunchpad. The installation procedure automatically configures middleware onmultiple servers, using default values.

Before you begin

Ensure that you meet prerequisite conditions.v Oracle WebLogic Server must have been manually configured for your

deployment.v The database server, the directory server, and application server services must be







v Enable a remote execution and access service on every system that hasmiddleware installed. Each remote system must support a remote accessprotocol. It must also accept remote logins from a user name and password thatwere configured on the target server. Remote access protocols include SSH andWindows SMB. If the remote system is a Windows server, you must configureremote execution and access to use SMB.





About this task


If you experience problems with the user interface of the installation programwhen installing on AIX 6.x systems remotely, reattempt the installation locally. Usethe console or an X terminal on the system locally.





Windows

v install.bat

v install_win64.bat

UNIX

v install_aix64.sh






5. Review the information that is on the Verify Installation Location panel. Thepanel shows any previous installation information that was found based onthe installation directory that you specified on the previous panel. After youadvance past this panel, you cannot go back and change the installationdirectory for this installation.If a more recent version of the installation program is found in the specifiedtarget directory, you are notified. The notification means that you are using anolder version of the installation program. The version found on theadministrative workstation is newer and can contain important features andenhancements. To use the newer version of the installation program, select theoption on the notification panel and click Next. This action exits the currentinstallation process and restarts the installation process with the newerinstallation program. If you do not select the option, you continue theinstallation with the older version of the installation program.



8. On the Import Middleware Configuration Information panel, you selectImport middleware configuration information to have the productinstallation program reuse the middleware installation program values. Thesevalues are used as default values for the same fields in the productinstallation program.The Workspace location field refers to the location of the topology file thatcontains the values that were specified for the middleware installationprogram. The file is located in the workspace that was defined during themiddleware installation task. For example, C:\ibm\tivoli\mwi\workspace forWindows or /root/ibm/tivoli/mwi/workspace for UNIX.If you selected the simple deployment, the middleware default information isnot used.


10. On the Database panel, specify configuration information for your databasesoftware.For things such as the database user ID, the database name, the databaseinstance for SmartCloud Control Desk, and the schema name, if the values donot exist when you specify them, they are created.For DB2, the user ID cannot be the same as the instance administrator user ID.Database users and database instance names cannot contain spaces.For DB2, the database instance is created if it does not exist, but the user andits associated home directory must exist on the DB2 server. For DB2, the


schema name can be the same value as the owner of the table spaces that aredefined or it can be a different value, such as maximo.After you specify configuration information for your database software, theinstallation program validates the information with the database server.

11. On the Automate Database Configuration panel, you can specify that databasecreation and configuration is to be automated.If you do not select the option, you must configure the database manually.

12. On the Remote Access Authorization panel, specify authorization informationfor the automatic database configuration feature. Specifying the values enablesremote configuration.

13. On the Database Administration panel, specify configuration informationabout the database. The required information varies by database platform.For DB2, the instance administrator user ID cannot be the same as thedatabase user ID. And the Windows service user ID must have administrativeauthority on the system.









18. On the Data Integration and Context Menu Services Options panel, click theoption that indicates where the database tables for these functions are created:in the Maximo ("same") database, or in a separate database instance that you


created for this purpose. If you are installing the Entry edition, choose theMaximo database. These tables are created but are not used by the Entryedition.





Important: Do not install another product before you complete theconfiguration step of the original installation. Installing anotherproduct before you run the configuration step for this installationoverwrites the taskstore, which prevents the original installation fromever being deployed.



If you run taskrunner with the NOSTOPONERROR parameter, thetaskrunner continues despite errors. If you run taskrunner with theSTOPONERROR parameter, the taskrunner stops when it encounters anerror. If you used STOPONERROR, you can rectify the conditions thatcaused the error. You can then resume the installation where the lastsuccessfully completed task was recorded in the previous attempt bystarting taskrunner with the CONTINUE parameter.


22. On the Choose Shortcut Folder panel, specify where you want SmartCloudControl Desk icons created.If you select In the Start Menu and use Internet Explorer, add theSmartCloud Control Desk URL to the trusted sites web content zone. Disablethe option that requires server verification for all sites in the zone.Do not select In the Quick Launch Bar. The selection does not create ashortcut in the Quick Launch bar.


Attention: Shortcuts are created for Windows systems only. BecauseWebLogic Server deployments are a manual process, you must manuallyupdate any shortcuts that you create. You update shortcuts after youmanually deployed the SmartCloud Control Desk EAR files.

23. On the Input Summary panel, review the information that you provided forthe product installation program.If necessary, use Previous to return to previous panels to change values.



“Restarting middleware on Windows” on page 177This procedure describes how to restart middleware on Windows, if you mustrestart any middleware services.“Restarting middleware on UNIX” on page 178Middleware services on Linux and AIX platforms occasionally must berestarted, such as when a reboot occurs. Middleware servers and services mustbe active before running the SmartCloud Control Desk installation program.











Rational Team Concert OSLC IntegrationsThis integration enables you to use the Open Services for LifecycleCollaboration (OSLC) technology to link from the Problems application toRational Team Concert to share information about problems and theirsolutions.



About this task


























7. Rebuild the maximo.ear file.


\IBM\SMP\maximo\deployment\buildmaximoear



Before you begin



About this task





2. Type








Application Assistant opens.8. Click the upload your file(s) link.


9. Click the Browse button next to the Deployment Archive field. Browse towhere you have maximo.ear file installed (c:/ibm/smp/maximo/deployment/default/ of the administrative workstation), select the file and click Open.



Next.13. Accept all other default values and click Finish to start the deployment

process.14. 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.

15. Repeat Steps 8 on page 43 through 14 on page 43 to deploy maximoiehs.ear.16. Click the checkbox next to the maximo application.17. Click the dropdown arrow of the Start button and select Servicing all



About this task



Properties



Results





“Manually deploying languages after database update deferral” on page 44Languages must be deployed manually if you defer database updates by theinstallation program.


Before you begin


About this task




following command:install_home\maximo\tools\maximo\TDToolkit.bat-IMPORT-SLEN-TLlocale-maxmessfix










Chapter 4. Deploying manually reusing existing middleware

Use this information if you intend to deploy SmartCloud Control Desk by reusingexisting middleware servers and manually configuring them to work withSmartCloud Control Desk.

This information provides a high-level overview or road map of tasks you need tocomplete in order to deploy SmartCloud Control Desk automatically, usingmiddleware already established in your enterprise.

In this scenario, you manually configure existing middleware resources beforerunning the SmartCloud Control Desk installation program.

SmartCloud Control Desk installation with manual middlewareconfiguration

Manually configured installations involve configuring middleware components, thedatabase server, the directory server, and the J2EE server, to work with SmartCloudControl Desk before using the SmartCloud Control Desk installation program.

You can elect to have one or more SmartCloud Control Desk middlewarecomponents configured automatically by the SmartCloud Control Desk installationprogram. Alternatively, you can choose to manually configure one or more of themiddleware servers to work with SmartCloud Control Desk.

The information contained in this section provides details on how to manuallyconfigure SmartCloud Control Desk middleware before running the SmartCloudControl Desk installation program.

Before you begin, ensure you have addressed the following prerequisite conditions:v You have designated a Windows or UNIX-based server to start the SmartCloud

Control Desk installation program.

You must complete the manual configuration of each server you plan to notconfigure using the autoconfigure feature of the SmartCloud Control Deskinstallation program before you actually use the SmartCloud Control Deskinstallation program to install SmartCloud Control Desk.

Ensure that all of your middleware is at supported version levels.

Manually configuring the databaseYou have the option of manually configuring the database server used inSmartCloud Control Desk deployment. Manual configuration of the databaseserver must be completed before you use the SmartCloud Control Desk installationprogram.

For DB2 on UNIX and Linux, a minimum of 8 gigabytes (binary) free of space isrequired for DB2 table spaces. This space must be available to the databaseinstance home directory (/home/ctginst1).

Figure 2. Deploying SmartCloud Control Desk with manual middleware configuration


For DB2 on Windows, ensure that you have a minimum of 8 gigabytes of freespace in the DB2 installation directory.

Manually configuring DB2 9.xThis section contains instructions for manually configuring DB2 9.x servers for useby SmartCloud Control Desk.

About this task

To configure an existing DB2 9.x server for use with SmartCloud Control Desk,complete the following steps before starting the SmartCloud Control Deskinstallation program:

Procedure1. Log in to the system as a user that has administrative permissions on the

system.2. Create system users if they do not exist on the system.

v Windows– db2admin– maximo

v Linux or UNIX– db2admin– maximo– ctgfenc1– ctginst1

The ctginst1 user ID must be assigned to the db2iadm1 group.3. Open a console window and set up the DB2 environment:

v Windowsdb2cmd

v Linux or UNIXEnsure that the /opt/ibm/db2/V9.7/bin, /opt/ibm/db2/v9.7/instance, and/opt/ibm/db2/V9.7/adm directories are added to your PATH.

4. Create the DB2 instance:v Windows

db2icrt -s ese -u db2admin,myPassword -r 50005,50005 ctginst1set db2instance=ctginst1db2startdb2 update dbm config using SVCENAME 50005 DEFERREDdb2stopdb2set DB2COMM=tcpipdb2start

v Linux orUNIXdb2icrt -s ese -u db2fenc1 -p 50005 ctginst1. /home/ctginst1/sqllib/db2profiledb2startdb2 update dbm config using SVCENAME 50005 DEFERREDdb2stopdb2set DB2COMM=tcpipdb2start

5. Create the database.db2 create db ’maxdb75’ ALIAS ’maxdb75’ using codeset UTF-8 territory US pagesize 32 Kdb2 connect to ’maxdb75’db2 GRANT DBADM ON DATABASE TO USER db2admin (windows only)db2 GRANT SECADM ON DATABASE TO USER db2admin (windows only)db2 connect reset

6. Configure the database.db2 update db cfg for maxdb75 using SELF_TUNING_MEM ONdb2 update db cfg for maxdb75 using APP_CTL_HEAP_SZ 16384 DEFERREDdb2 update db cfg for maxdb75 using APPLHEAPSZ 2048 AUTOMATIC DEFERREDdb2 update db cfg for maxdb75 using AUTO_MAINT ON DEFERREDdb2 update db cfg for maxdb75 using AUTO_TBL_MAINT ON DEFERREDdb2 update db cfg for maxdb75 using AUTO_RUNSTATS ON DEFERREDdb2 update db cfg for maxdb75 using AUTO_REORG ON DEFERRED


db2 update db cfg for maxdb75 using AUTO_DB_BACKUP ON DEFERREDdb2 update db cfg for maxdb75 using CATALOGCACHE_SZ 800 DEFERREDdb2 update db cfg for maxdb75 using CHNGPGS_THRESH 40 DEFERREDdb2 update db cfg for maxdb75 using DBHEAP AUTOMATICdb2 update db cfg for maxdb75 using LOCKLIST AUTOMATIC DEFERREDdb2 update db cfg for maxdb75 using LOGBUFSZ 1024 DEFERREDdb2 update db cfg for maxdb75 using LOCKTIMEOUT 300 DEFERREDdb2 update db cfg for maxdb75 using LOGPRIMARY 20 DEFERREDdb2 update db cfg for maxdb75 using LOGSECOND 100 DEFERREDdb2 update db cfg for maxdb75 using LOGFILSIZ 8192 DEFERREDdb2 update db cfg for maxdb75 using SOFTMAX 1000 DEFERREDdb2 update db cfg for maxdb75 using MAXFILOP 32768 DEFERRED #32-bit Windowsdb2 update db cfg for maxdb75 using MAXFILOP 65335 DEFERRED #64-bit Windowsdb2 update db cfg for maxdb75 using MAXFILOP 30720 DEFERRED #32-bit UNIXdb2 update db cfg for maxdb75 using MAXFILOP 61440 DEFERRED #64-bit UNIXdb2 update db cfg for maxdb75 using PCKCACHESZ AUTOMATIC DEFERREDdb2 update db cfg for maxdb75 using STAT_HEAP_SZ AUTOMATIC DEFERREDdb2 update db cfg for maxdb75 using STMTHEAP AUTOMATIC DEFERREDdb2 update db cfg for maxdb75 using UTIL_HEAP_SZ 10000 DEFERREDdb2 update db cfg for maxdb75 using DATABASE_MEMORY AUTOMATIC DEFERREDdb2 update db cfg for maxdb75 using AUTO_STMT_STATS OFF DEFERREDdb2 update db cfg for maxdb75 using STMT_CONC LITERALS DEFERREDdb2 update alert cfg for database on maxdb75 using db.db_backup_req SET THRESHOLDSCHECKED YESdb2 update alert cfg for database on maxdb75 using db.tb_reorg_req SET THRESHOLDSCHECKED YESdb2 update alert cfg for database on maxdb75 using db.tb_runstats_req SET THRESHOLDSCHECKED YESdb2 update dbm cfg using PRIV_MEM_THRESH 32767 DEFERREDdb2 update dbm cfg using KEEPFENCED NO DEFERREDdb2 update dbm cfg using NUMDB 2 DEFERREDdb2 update dbm cfg using RQRIOBLK 65535 DEFERREDdb2 update dbm cfg using HEALTH_MON OFF DEFERRED## Windows: AGENT_STACK_SZ 1000# Unix : AGENT_STACK_SZ 1000#db2 update dbm cfg using AGENT_STACK_SZ 1000 DEFERREDdb2 update dbm cfg using MON_HEAP_SZ AUTOMATIC DEFERREDdb2set DB2_SKIPINSERTED=ONdb2set DB2_INLIST_TO_NLJN=YESdb2set DB2_MINIMIZE_LISTPREFETCH=Ydb2set DB2_EVALUNCOMMITTED=YESdb2set DB2_FMP_COMM_HEAPSZ=65536db2set DB2_SKIPDELETED=ONdb2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON

7. For Linux orUNIX log in as the ctginst1 user and then restart the DB2command-line environmensu - ctginst1db2

8. Restart DB2.db2stop forcedb2start

9. Reconnect to the database.db2 connect to ’maxdb75’

10. Create a buffer pool.db2 CREATE BUFFERPOOL MAXBUFPOOL IMMEDIATE SIZE 4096 AUTOMATIC PAGESIZE 32 K

11. Create table spaces.db2 CREATE REGULAR TABLESPACE MAXDATA PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE INITIALSIZE 5000 M BUFFERPOOL MAXBUFPOOLdb2 CREATE TEMPORARY TABLESPACE MAXTEMP PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE BUFFERPOOL MAXBUFPOOLdb2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO

12. Grant authority to maximo.db2 GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT,SECADM ON DATABASE TO USER MAXIMO

db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO

db2 GRANT CREATEIN,DROPIN,ALTERIN ON SCHEMA MAXIMO TO USER MAXIMO

db2 create schema maximo authorization maximo

13. Break the database connection.db2 connect reset

14. Exit the DB2 command-line environment15. Install the appropriate fix pack indicated in the prerequisites topic in the

chapter that describes how to prepare for the installation. Ensure that youreview and complete all the installation and post-installation tasks containedwithin the fix pack readme file. Failure to do so can potentially cause theSmartCloud Control Desk installation to fail. See the appropriate productsupport page for more information.

Manually configuring Oracle 11gUse the following instructions to manually configure Oracle 11g for use withSmartCloud Control Desk.

Chapter 4. Deploying manually reusing existing middleware 71

Before you begin

Oracle instance names must be limited to eight characters in length. For Oracledatabases, the schema owner must use the same user ID as the database user.

About this task

To configure an existing Oracle 11g server for use with SmartCloud Control Desk,complete the following steps before you start the SmartCloud Control Deskinstallation program:

Procedure1. Log in as the Oracle software user. Typically this user is named oracle.2. Create the database listener. The listener manages requests to connect to the

database. This step is only required if you do not already have an existinglistener in place.a. Open the Oracle Network Configuration Assistant application.b. From the Welcome panel, select Listener configuration, and then click Next.c. From the action panel, select Add, and then click Next.d. Enter a name for the listener or accept the default value, and then click

Next.e. Accept the default Selected Protocols listed by clicking Next.f. From the port panel, select Use the standard port of 1521, and then click

Next.g. Select No to indicate that you are finished configuring listeners, and then

click Next.h. From the Listener Configuration Done panel, click Next.i. Click Finish.

3. Create a database for use by SmartCloud Control Desk.a. Open the Oracle Database Configuration Assistant.b. Click Next.c. Select Create a Database, and then click Next.d. Select General Purpose or Transaction Processing, and then click Next.e. Enter ctginst1 for both the Global Database Name value and the SID value,

and then click Next.f. Leave the defaults selected, and click Next.g. Ensure Use the Same Administrative Password for All Accounts is

selected, enter a password for Oracle users, and then click Next.h. Ensure File System is selected as the storage mechanism to use for the

database. Ensure Use Database File Locations from Template is selected asthe value to use for database file location, and then click Next.

i. Leave defaults selected for the database recovery options panel, and thenclick Next.

j. From the Sample Schemas panel, click Next.k. From the Initialization Parameters panel, on the Memory tab, select Custom

and provide the following values (measured in Mb):

Memory ManagementSet this value to Manual Shared Memory Management.


Shared PoolSet this value to 152.

Buffer CacheSet this value to 36.

Java PoolSet this value to 32.

Large PoolSet this value to 8.

PGA SizeSet this value to 36.

l. From the Character Sets tab, select Use Unicode (AL32UTF8).m. Click All Initialization Parameters....n. Click Show Advanced Parameters.o. Locate the following parameters, change them to the values indicated, and

then click Close.

nls_length_semanticsChange this value to CHAR.

open_cursorsChange this value to 1000.

cursor_sharingSet this value to FORCE.

p. From the Initialization Parameters panel, click Next.q. From the Database Storage panel, click Next.r. From the Creation Options panel, click Finish.s. Click Exit to exit the Database Configuration Assistant. The database is

successfully created.

Note: The Oracle Database Configuration Assistant starts theORACLE_HOME/ctx/admin/defaults/drdefus.sql script as part of theconfiguration of the CTXSYS user. You must start this script manually if theOracle Database Configuration Assistant is not used.

4. Create a table space using the following command in SQL*Plus:Create tablespace maxdata datafile’C:\oracle\product\11.1.0\db_1\dbs\maxdata.dbf’size 1000M autoextend on;

Change the directory specified in the example to the database location. If thedirectory does not exist, this command fails.

5. Create a temporary table space using the following command in SQL*Pluscreate temporary tablespace maxtemp tempfile’C:\oracle\product\11.1.0\db_1\dbs\maxtemp.dbf’size 1000M autoextend on maxsize unlimited;

Change the directory specified in the example to the database location. If thedirectory does not exist, this command fails.

6. Create the maximo user and grant permissions using the following commandin SQL*Plus:create user maximo identified by maximo default tablespace maxdata temporarytablespace maxtemp;grant connect to maximo;grant create job to maximo;grant create trigger to maximo;


grant create session to maximo;grant create sequence to maximo;grant create synonym to maximo;grant create table to maximo;grant create view to maximo;grant create procedure to maximo;grant alter session to maximo;grant execute on ctxsys.ctx_ddl to maximo;alter user maximo quota unlimited on maxdata;

If you created a separate table space for indexing, you must also grant access tothat index table space to the maximo user. For example, use the followingcommand if you created a separate table space for indexing calledTSI_MAM_OWN.":alter user maximo quota unlimited on TSI_MAM_OWN

These instructions assume that you did not modify default role sets assigned tothe Oracle DBA user or user IDs created to connect to the database. If yourestricted the default privileges granted to user IDs, you must explicitly grantthem to the maximo user. For example, if you do not grant a role such as theselect_catalog_role role, you must explicitly grant that role to the maximouser. This assignment can be done by running this SQL*Plus command:grant select_catalog_role to maximo

Manually configuring Oracle 10gOracle 10g can be manually configured for use with SmartCloud Control Desk.

Before you begin

Oracle instance names must be limited to eight characters in length. For Oracledatabases, the schema owner must use the same user ID as the database user.

About this task

To configure an existing Oracle 10g server for use with SmartCloud Control Desk,complete the following steps before you start the SmartCloud Control Deskinstallation program:

Procedure1. Log in as the Oracle software user. Typically this user is named oracle.2. Create the database listener. The listener manages requests to connect to the

database.a. Open the Oracle Network Configuration Assistant application.b. From the Welcome panel, select Listener configuration, and then click Next.c. From the action panel, select Add, and then click Next.d. Enter a name for the listener or accept the default value, and then click

Next.e. Accept the default Selected Protocols listed by clicking Next.f. From the port panel, select Use the standard port of 1521, and then click

Next.g. Select No to indicate that you are finished configuring listeners, and then

click Next.h. From the Listener Configuration Done panel, click Next.i. Click Finish.

3. Create a database for SmartCloud Control Desk.


a. Open the Oracle Database Configuration Assistant.b. Click Next.c. Select Create a Database, and then click Next.d. Select General Purpose, and then click Next.e. Enter ctginst1 for both the Global Database Name value and the SID value,

and then click Next.f. Leave the defaults selected, and click Next.g. Ensure Use the Same Password for All Accounts is selected, enter a

password for Oracle users, and then click Next

h. Ensure File System is selected as the storage mechanism to use for thedatabase, and then click Next.

i. Ensure Use Database File Locations from Template is selected as the valueto use for database file location, and then click Next.

j. Leave defaults selected for the database recovery options panel, and thenclick Next.

k. From the Sample Schemas panel, click Next.l. From the memory allocation panel, select Custom, provide the following

values (measured in bytes), and then click Next.

Shared Memory ManagementSet this value to Manual.

Shared PoolSet this value to 152.

Buffer CacheSet this value to 36.

Java PoolSet this value to 32

Large PoolSet this value to 8.

PGA SizeSet this value to 36.

m. From the Character Sets tab, select Use Unicode (AL32UTF8),

n. Click All Initialization Parameters....o. Click Show Advanced Parameters.p. Locate the following parameters, change them to the values indicated, and

then click Close.

nls_length_semanticsChange this value to CHAR

open_cursorsChange this value to 1000

cursor_sharingSet this value to FORCE.

q. From the Initialization Parameters panel, click Next.r. From the Database Storage panel, click Next.s. From the Creation Options panel, click Finish.t. After the database is created, click Password Management.


u. Unlock the CTXSYS account by clearing the check mark in the LockAccount? column for that entry, enter a password for the account, and thenclick OK.

v. Click Exit to exit the Database Configuration Assistant. The database issuccessfully created.

Note: The Oracle Database Configuration Assistant uses theORACLE_HOME/ctx/admin/defaults/drdefus.sql script as part of theconfiguration of the CTXSYS user. This script must be used manually if theOracle Database Configuration Assistant is not used.

4. Create a table space using the following command in SQL*Plus:Create tablespace maxdata datafile’C:\oracle\product\10.2.0\oradata\ctginst1\maxdata.dbf’size 1000M autoextend on;

The directory specified in the example must be changed to the installationlocation of the database. If the directory does not exist, this command fails.

5. Create a temporary table space.6. Create the maximo user and grant permissions using the following command

in SQL*Plus:create user maximo identified by maximo default tablespace maxdata temporarytablespace maxtemp;grant connect to maximo;grant create job to maximo;grant create trigger to maximo;grant create session to maximo;grant create sequence to maximo;grant create synonym to maximo;grant create table to maximo;grant create view to maximo;grant create procedure to maximo;grant alter session to maximo;grant execute on ctxsys.ctx_ddl to maximo;alter user maximo quota unlimited on maxdata;

If you have elected to create a separate table space for indexing, you must alsogrant the maximo user access to that index table space. For example, you mustperform the following additional SQL*plus command if you had created aseparate table space for indexing called TSI_CMDB_OWN:alter user maximo quota unlimited on TSI_CMDB_OWN

These instructions assume that you did not modify the default role sets that areassigned to the Oracle DBA user or other database connection user IDs. If yourestrict the default privileges granted to user IDs, you must explicitly grantthem to the maximo user. For example, the select_catalog_role role is requiredfor user IDs connecting to the database. To deploy SmartCloud Control Desksuccessfully, you must explicitly grant that role to the maximo user by usingthe SQL*Plus command:grant select_catalog_role to maximo

Manually configuring Microsoft SQL ServerYou can manually configure Microsoft SQL Server for use with SmartCloudControl Desk.

Before you begin

Because Microsoft SQL Server does not support UTF-8, SmartCloud Control Deskdoes not have multilingual support when deployed with Microsoft SQL Server.


Microsoft SQL Server Database Collation settings must be set to the followingoptions:v Dictionary orderv Case-insensitivev For use with 1252 Character set

About this task

To configure an existing Microsoft SQL Server for use with SmartCloud ControlDesk, perform the following steps before starting the SmartCloud Control Deskinstallation program:

Procedure1. Configure the listener port.

If The default instance of the Microsoft SQL Server Database Engine listens onTCP port 1433. Named instances of the Microsoft SQL Server Database Engineand Microsoft SQL Server Compact Edition are configured for dynamic ports,which means they select any available port when the service starts. Whenconnecting to a named instance across a firewall, configure the Database Engineto listen on a specific port, to open this port in the firewall.a. Open Programs > Microsoft SQL Server 2008 > Configuration Tools >

SQL Server Configuration Manager

b. From the Microsoft SQL Server Configuration Manager navigation pane,expand SQL Server Network Configuration > Protocols for <instancename>, and then double-click TCP/IP.

c. In the TCP/IP Properties dialog box, click the IP addresses tab.d. For each IP address listed, ensure that the TCP Dynamic Ports field is blank.

If the TCP Dynamic Ports field contains a value of 0, that IP address isusing dynamic ports. Since SmartCloud Control Desk requires MicrosoftSQL Server to listen on a static port, this field must be blank.

e. For each IP address listed, enter 1433 for the TCP Port field.f. Click OK.g. From the SQL Server Configuration Manager navigation pane, click SQL

Server Services.h. Right-click SQL Server (<instance name>) and then click Restart, to stop,

and restart Microsoft SQL Server.i. Verify the Microsoft SQL Server instance is running, and then close SQL

Server Configuration Manager.2. Verify that you enabled the Full-text Search setting during the installation of

Microsoft SQL Server 2008. To determine if Full-text Search is installed on yourexisting Microsoft SQL Server database, perform the following steps:a. Open SQL Server Management Studio, select SQL Server Authentication as

the authentication type, and enter the credentials for the sa user ID, andthen click Connect.

b. Click New Query.c. Type the following command:

select FULLTEXTSERVICEPROPERTY ( ’IsFulltextInstalled’ )

If you did not install Full-text Search (the resulting value is zero), you mustdo so at this time. To install Full-text Search, insert the Microsoft SQL Server2008 product media into the system and start the installation wizard.


Navigate through the wizard and enable the Full-Text Search option locatedon the Custom portion of the Setup Type dialog box. To finish theinstallation process, restart the server.

3. Create a Microsoft SQL Server Database.a. Open SQL Server Management Studio (Start > Programs > Microsoft SQL

Server 2008 > SQL Server Management Studio)b. Right-click the Databases folder from the navigation tree , and select New

Database.c. In the Database name entry field, specify a unique database name (for

example maxdb75)d. For the maxdb75 Logical Name, change the Initial Size (MB) attribute to 500

(MB), and also set the value of the Autogrowth field to By 1MB,unrestricted growth.

e. If you prefer, modify the log settings to accommodate your productionenvironment.

f. Click OK.4. Create the Maximo User for Microsoft SQL Server.

a. Open Microsoft SQL Server Management Studio (Start > Programs >Microsoft SQL Server 2008 > SQL Server Management Studio)

b. Click New Query.c. Select the SmartCloud Control Desk database (maxdb75) from the Available

Databases menu,d. Enter the following script to create the Maximo database user MAXIMO with a

password of MAXIMO.sp_addlogin MAXIMO,MAXIMOgo

This value is case-sensitive.e. Click Execute.f. Enter the following script to change the database owner to maximo.

sp_changedbowner MAXIMOgo

g. Click Execute.

What to do next

If you add additional logical names to the database and set their file group to avalue other than PRIMARY, you must complete the following steps after you setup the database and create the Maximo user:1. Run the SmartCloud Control Desk installation program and choose the Do not

run the configuration step now option.2. Add the following property to the install_home\etc\install.properties file:

Database.SQL.DataFilegroupName=<your logical name>

3. Run the configuration steps outside of the SmartCloud Control Deskinstallation program by using the taskrunner utility, located in theinstall_home\scripts directory.

Complete these additional steps only if you added additional logical names to thedatabase and set their file group to a value other than PRIMARY.


Manually configuring the directory serverThese topics provide details on manually configuring a directory server for use bySmartCloud Control Desk

There are several methods you can use to secure SmartCloud Control Desk.If wantto use a directory server to secure SmartCloud Control Desk, you must completethe manual configuration of the directory server before you use the SmartCloudControl Desk installation program. Manual configuration is necessary if youchoose to not have the SmartCloud Control Desk installation program performconfiguration.

Note: The base dn, bind user, and other various node values listed in thesesections are defaults. These values are replaced with values applicable to existingLDAP hierarchies within your organization.

Important: When entering LDAP values for SmartCloud Control Desk installationpanel fields, entries in LDIF files, or values you enter directly into a directoryinstance using directory server tools, be aware of the product-specific syntax rulesfor using special characters in an LDAP string. In most cases, special charactersmust be preceded by an escape character in order to make it readable by thedirectory server. Failing to escape special characters contained in an LDAP stringused with SmartCloud Control Desk results in SmartCloud Control Desk errors.

Many directory server products consider a blank space as a special character that ispart of the LDAP string. If you mistakenly enter an LDAP string that contains ablank, at the end of a field value, for example, and you do not precede the blankcharacter with an escape character, you encounter SmartCloud Control Desk errorsthat are difficult to troubleshoot.

See the product documentation for your directory server for more informationabout special characters in LDAP strings.

Manually configuring IBM Tivoli Directory ServerUse the following instructions to manually configure IBM Tivoli Directory Serverfor use with SmartCloud Control Desk.

About this task

To configure IBM Tivoli Directory Server before starting the SmartCloud ControlDesk installation program, you must create an instance of IBM Tivoli DirectoryServer.

Note: While you can technically share a DB2 instance between SmartCloudControl Desk and the one needed by IBM Tivoli Directory Server, it might lead toproblems. During the installation, the database instance is restarted, which mightdisrupt the availability of IBM Tivoli Directory Server to your enterprise. If you areusing the automated installation programs, separate instances are created for useby SmartCloud Control Desk and IBM Tivoli Directory Server.

Procedure1. Using your preferred method, create a user on the system and assign it to the

appropriate group.

WindowsCreate the user db2admin and make it a member of the followinggroups:


v Windows Administratorsv DB2ADMNSv DB2USERS

UNIX Create the user idsccmdb and make it a member of the followinggroups:v dasadmn1v idsldapv dbsysadm

The root user must also be a member of the dasadm1, idsldap, anddbsysadm groups.

2. If the Instance Administration tool is not already started, ensure that you arelogged in as an administrator on the system, and then start the tool

WindowsSelect Programs > IBM Tivoli Directory Server 6.3 > InstanceAdministration Tool.

UNIX Type ./opt/IBM/ldap/V6.3/sbin/idsxinst at the command line.3. In the Instance Administration tool, click Create an instance.4. In the Create a new instance window, click Create a new directory server

instance, and then click Next.5. From the Instance details window, enter values for the following fields, and

then click Next.

User nameSelect idsccmdb as the system user ID of the user who owns theinstance. This name is also the name of the instance.

Install locationEnter the location where the instance files are stored.

Encryption seed stringType a string of characters that are used as an encryption seed. Thisvalue must be a minimum of 12 characters.

Instance descriptionEnter a brief description of the instance.

6. In the DB2 instance details panel, enter idsccmdb as the value for the DB2instance name field, and then click Next.

7. In the TCP/IP settings for multihomed hosts panel, select Listen on allconfigured IP addresses, and then click Next.

8. In the TCP/IP port settings panel, complete the following fields, and thenclick Next.

Server port numberEnter 389 as the contact port for the server.

Server secure port numberEnter 636 as the secure port for the server.

Admin daemon port numberEnter 3538 as the administration daemon port.

Admin daemon secure port numberEnter 3539 as the administration daemon secure port.

9. In the Option steps panel, leave the following options selected, and then clickNext.


Configure admin DN and passwordYou want to configure the administrator DN and password for theinstance now.

Configure databaseYou want to configure the database for the directory server now.

10. In the Configure administrator DN and password window panel, complete thefollowing fields, and then click Next.

Administrator DNEnter cn=root for the administrator distinguished name.

Administrator PasswordEnter a password for the Administrator DN.

11. From the Configure database panel, complete the following fields, and thenclick Next.

Database user nameEnter idsccmdb as the database user.

PasswordEnter the password for the idsccmdb user.

Database nameEnter idsccmdb as the database to be used with this directory instance.

12. In the Database options panel, complete the following fields, and then clickNext.

Database install locationType the location for the database.

WindowsFor Windows platforms, this value must be a drive letter.

UNIX For non-Windows platforms, the location must be a directoryname, such as /home/ldapdb.

Ensure that you have at least 80 MB of free hard disk space in thelocation you specify. Additional disk space must be available toaccommodate growth as new entries are added to the directory.

Character-set optionLeave the Create a universal DB2 database (UTF-8/UCS-2) optionselected.

13. In the Verify settings panel, review the instance creation details provided, andthen click Finish to create the idsccmdb instance.

14. Click Close to close the window and return to the main window of theInstance Administration tool.

15. Click Close to exit the Instance Administration tool.16. Start the IBM Tivoli Directory Server Configuration tool:

WindowsSelectPrograms > IBM Tivoli Directory Server 6.3 > InstanceAdministration Tool.

UNIX Type ./opt/IBM/ldap/V6.3/sbin/idsxcfg at the command line.17. Select Manage suffixes.18. In the Manage suffixes panel, type the following suffix, and then click Add.

o=IBM,c=US

19. Click OK.


20. Create and save an LDIF file.Add the DN information, for example:v ou=SWG,o=IBM,c=USv ou=users

Note: ou=SWG,o=IBM,c=US in this example is an organization unit calledSWG. SWG houses the OU=Users organization units to place the userscreated for SmartCloud Control Desk. DC=IBM and DC=COM would indicatea domain forest of ibm.com®. You can replace the example with the directorystructure of your own organization.Define the following users and their positions within the ou=users DN's youcreated. These users are defined in order for Virtual Member Manager to beused to secure SmartCloud Control Desk.

Important: Before you begin this procedure, ensure that you have thefollowing users created in the root of your LDAP repository:

Table 5. Base SmartCloud Control Desk required users

User

maxadmin

mxintadm

maxreg

Here is an example of the default base LDIF data:dn: o=ibm,c=usobjectClass: topobjectClass: organizationo: IBM

dn: ou=SWG, o=ibm,c=usou: SWGobjectClass: topobjectClass: organizationalUnit

dn: ou=users,ou=SWG, o=ibm,c=usou: usersobjectClass: topobjectClass: organizationalUnit

dn: uid=maxadmin,ou=users,ou=SWG, o=ibm,c=ususerPassword: maxadminuid: maxadminobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: maxadmincn: maxadmin

dn: uid=mxintadm,ou=users,ou=SWG, o=ibm,c=ususerPassword: mxintadmuid: mxintadmobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: mxintadmcn: mxintadm


dn: uid=maxreg,ou=users,ou=SWG, o=ibm,c=ususerPassword: maxreguid: maxregobjectClass: inetorgpersonobjectClass: topobjectClass: personobjectClass: organizationalPersonsn: maxregcn: maxreg

Note: If you create the LDIF file on Windows, ensure that you remove the ^Mcharacters from the file before using.

Note: Before you can import an LDIF file on UNIX systems, you must runthe dos2unix command to format the file.

21. In the IBM Tivoli Directory Server Configuration Tool, click Import LDIF data.22. Click Browse to locate the LDIF file.23. Click Import.24. Close the IBM Tivoli Directory Server Configuration Tool and restart the

server.

Manually configuring Microsoft Active DirectoryYou can manually configure Microsoft Active Directory for use with SmartCloudControl Desk.

Before you begin

Use this procedure to manually create users and groups within Microsoft ActiveDirectory.

Important: The users and passwords you create in the following steps must matchthis exact configuration for the deployment to succeed. It is sometimes necessary totemporarily alter theMicrosoft Active Directory security policy to create theseaccounts in the required format. After installation, you can change these defaultpasswords to conform to a stricter security policy.

About this task

Before starting theSmartCloud Control Desk installation program, configureMicrosoft Active Directory. Complete the following steps

Procedure1. Select Start > Control Panel > Administrative Tools > Microsoft Active

Directory Users and Computers and then select the domain that you areworking with.

2. Edit the functional level of the domain by selecting Action > Raise DomainFunctional Level. The Raise Domain Functional Level dialog box is displayed.

3. Select Microsoft Windows Server 2008 from the Select an available domainfunctional level menu, and then click Raise. An alert dialog box is displayed.

4. Click OK.5. When the domain raise task has completed, click OK.6. In the Microsoft Active Directory Users and Computers interface, using the

right mouse button, click the domain to work with. Select New >Organizational Unit.


7. Enter a name for the new Organizational Unit (OU), for example, SWG, andthen click OK.

8. Create a groups object under the SWG organizational unit:a. Right-click the SWG OU, and select New > Organizational Unit.b. Enter Groups as the name for the new OU then click OK.

9. Create a users object under the SWG organizational unit:a. Right-click the SWG OU, and select New > Organizational Unit.b. Enter Users as the name for the new OU then click OK.

10. Create an administrator user, for example maxadmin:a. Right click the Users OU and select New > User.b. From the New Object - User dialog, enter the following values, and then

click Next:

First nameEnter maxadmin.

InitialsLeave this field blank.

Last nameLeave this field blank.

Full nameEnter maxadmin.

User login nameEnter maxadmin in the first field. Leave the default value of thesecond field.

User login name (pre-Microsoft Windows 2000)This field is populated with the same value (maxadmin) enteredfor the User login name.

c. From the next panel, enter the following information, and then click Next:

PasswordEnter maxadmin as the password for the maxadmin user.

User must change password at next logonEnsure this check box is cleared.

User cannot change passwordEnsure this check box is selected.

Password never expiresEnsure this check box is selected.

Account is disabledEnsure this check box is cleared.

The preceding values are examples. Enter values that comply with thepassword policy of your organization.

d. Review the password settings in the summary panel, and click Finish.11. Create the mxintadm user:

a. Right click the Users OU and select New > User.b. From the New Object - User dialog, enter the following values, and then

click Next:

First nameEnter mxintadm.




Full nameEnter mxintadm.

User login nameEnter mxintadm in the first field. Leave the default value of thesecond field.

User login name (pre-Microsoft Windows 2000)This field is displayed with the same value (mxintadm) entered forthe User login name.


PasswordEnter a value as the password for the mxintadm user.





The preceding values are examples. You must set these fields to valuesthat comply with the password policy of your organization.

d. Review the password settings in the summary panel, and click Finish.12. Create the maxreg user:

a. Right click the Users OU and select New > User.b. From the New Object - User dialog, enter the following values, and then

click Next:

First nameEnter maxreg.



Full nameEnter maxreg.

User login nameEnter maxreg in the first field. Leave the default value of thesecond field.

User login name (pre-Microsoft Windows 2000)This field is filled with the same value (maxreg) entered for theUser login name.



PasswordEnter a value as the password for the maxreg user.





The preceding values are examples. Enter values that comply with thepassword policy of your organization.

d. Review the password settings in the summary panel, and click Finish.13. You can now exit the Microsoft Active Directory Users and Computers tool.

What to do next

Microsoft Active Directory configuration is finished and you are now ready toinstall the remaining SmartCloud Control Desk middleware and configure the J2EEserver to use Microsoft Active Directory.

Manually configuring the J2EE serverThis section contains instructions for manually configuring an existing J2EE serverfor use by SmartCloud Control Desk.

Manual configuration of the J2EE server is required if you choose to deploySmartCloud Control Desk using Oracle WebLogic Server. You must complete themanual configuration before you use the SmartCloud Control Desk installationprogram.


About this task



Procedure1. “Creating the MAXIMOSERVER domain” on page 292. “Configuring JMS options for integration framework” on page 303. “Configuring JMS for the email listener in WebLogic Server” on page 31


Creating the MAXIMOSERVER domain:

This section details how to create the MAXIMOSERVER domain within WebLogicServer.

About this task


Procedure

1. Launch the Configuration wizard tool.v For Windows systems, select Start > Programs > BEA Products > Tools >

Configuration Wizard.v For UNIX systems, launch the Configuration wizard using the config.sh

command located in <WebLogic_Home>/weblogic10/common/bin.2. From the welcome panel, select Create a new WebLogic Server domain, and

then click Next.3. From the Select a Domain Source panel, select Generate a domain configured

automatically to support the following products, and then click Next.4. From the Specify Domain Name and Location panel, name the domain

MAXIMOSERVER, and then click Next









Configuring JMS options for integration framework:

This procedure provides details on steps to configure JMS queues.

Before you begin



Procedure

1. Launch Internet Explorer and open the MAXIMOSERVER Administration Consoleby typing the following URL:http://host_name:7001/console


Option Description






Option Description







Option Description

Name intjmsconfact


Target MAXIMOSERVER


Option Description




Template None





What to do next


Configuring JMS for the email listener in WebLogic Server:

You use the email listeners application to receive and process requests throughemail in the form of email messages.

About this task


Procedure

1. Log in to the WebLogic Server administration console.2. Create a persistent store.













b. Select the Connection Factory option, and then click Next.c. From the Connection Factory Properties panel, enter the following

information, and then click Next.















ejb-jar.xml file in an editor, uncomment the following sections, and thensave the file:Email Listener JMS is not deployed by default<message-driven id="MessageDriven_LSNRMessageBean"><ejb-name>LSNRMessageBean</ejb-name>ejb-class>psdi.common.emailstner.LSNRMessageBean</ejb-class>transaction-type>Container</transaction-type><message-destination-type>javax.jms.Queue</messagedestination-type></message-driven>


b. Open the c:\ibm\smp\maximo\applications\maximo\mboejb\ejbmodule\META-INF\weblogic-ejb-jar.xml file in an editor, uncomment the followingsection, and then save the file:Email Listener JMS is not deployed by default<weblogic-enterprise-bean><ejb-name>LSNRMessageBean</ejb-name><message-driven-descriptor><destination-jndi-name>jms/mro/lsnr/qin</destination-jndiname><connection-factory-jndi-name>jms/mro/lsnr/lsnrcf</connection-factory-jndi-name></message-driven-descriptor><transaction-descriptor>


<trans-timeout-seconds>600</trans-timeout-seconds></transaction-descriptor><jndi-name>LSNRMessageBean</jndi-name></weblogic-enterprise-bean>

Installing the product and manually configuring middlewareYou can deploy SmartCloud Control Desk with configured middleware before theinstallation begins. You use this procedure if your organization has specific policiesand procedures that govern how you create databases, database instances, andusers within your organization.

Before you begin

Ensure that you meet prerequisite conditions.v Oracle WebLogic Server must be configured.v The database server, the directory server, and application server services must be






v Enable a remote execution and access service on every system that hasmiddleware installed. Each remote system must support a remote accessprotocol. Each system must accept remote logins from a user name andpassword that were configured on the target server. Remote access protocolsinclude SSH and Windows SMB. If the remote system is a Windows server, youmust configure remote execution and access to use SMB.





– To avoid high system memory usage by DB2, you can set the following DB2property and then restart the DB2 server:db2 update dbm cfg using KEEPFENCED NO


v If you use DB2 on UNIX systems with SmartCloud Control Desk, you must addroot to a group with SYSADM authority for the database instance. Thismembership must be in place before you start the SmartCloud Control Deskinstallation program.

v Complete the following tasks for Oracle WebLogic Server:– Configure JMS options for integration framework– Create the domain.– Set up JMS for e-mail listener.

About this task


If you experience problems with the user interface of the installation programwhen you install on AIX 6.x systems remotely, reattempt the installation locally.Use the console or an X terminal on the system locally.





Windows

v install.bat

v install_win64.bat

UNIX

v install_aix64.sh





5. Review the information that is on the Verify Installation Location panel. Thepanel shows any previous installation information that was found based onthe installation directory that you specified on the previous panel. After youadvance past this panel, you cannot go back and change the installationdirectory for this installation.If a more recent version of the installation program is found in the specifiedtarget directory, you are notified. The notification means that you are using anolder version of the installation program. The version found on the


administrative workstation is newer and can contain important features andenhancements. To use the newer version of the installation program, select theoption on the notification panel and click Next. This action exits the currentinstallation process and restarts the installation process with the newerinstallation program. If you do not select the option, you continue theinstallation with the older version of the installation program.



8. On the Import Middleware Configuration Information panel, you selectImport middleware configuration information to have the productinstallation program reuse the middleware installation program values. Thesevalues are used as default values for the same fields in the productinstallation program.The Workspace location field refers to the location of the topology file thatcontains the values that were specified for the middleware installationprogram. The file is located in the workspace that was defined during themiddleware installation task. For example, C:\ibm\tivoli\mwi\workspace forWindows or /root/ibm/tivoli/mwi/workspace for UNIX.If you selected the simple deployment, the middleware default information isnot used.


10. On the Database panel, specify configuration information for your databasesoftware.For things such as the database user ID, the database name, the databaseinstance for SmartCloud Control Desk, and the schema name, if the values donot exist when you specify them, they are created. Database users anddatabase instance names cannot contain spaces.For DB2, the user ID cannot be the same as the instance administrator user ID.For DB2, the database instance is created if it does not exist, but the user andits associated home directory must exist on the DB2 server. For DB2, theschema name can be the same value as the owner of the table spaces that aredefined or it can be a different value, such as maximo.After you specify configuration information for your database software, theinstallation program validates the information with the database server.

11. On the Automate Database Configuration panel, select The database hasalready been created and configured and click Next.This step assumes that you created a database instance, a database, tablespaces, a user, and schema for use with SmartCloud Control Desk. See“Manually configuring the database” on page 69. If you have not manuallyconfigured the database before selecting The database has already beencreated and configured you are prompted to complete them before you restartthe installation program.










16. On the Data Integration and Context Menu Services Options panel, select theoption that indicates where the database tables for these functions should becreated: in the Maximo ("same") database, or in a separate database instancethat you have already created for this purpose. If you are installing the Entryedition, choose the Maximo database. These tables are created but are not bythe Entry edition.





Important: Do not install another product before completing theconfiguration step of the original installation. Installing anotherproduct before running the configuration step for this installationoverwrites the taskstore, which prevents the original installation fromever being deployed.




If you run taskrunner with the NOSTOPONERROR parameter, thetaskrunner continues despite errors. If you run taskrunner with theSTOPONERROR parameter, the taskrunner stops when it encounters anerror. If you used STOPONERROR, you can rectify the conditions thatcaused the error. You can then resume the installation at the pointwhere the last successfully completed task was recorded in theprevious attempt by starting taskrunner with the CONTINUE parameter.


20. On the Choose Shortcut Folder panel, specify where you want SmartCloudControl Desk icons created.If you select In the Start Menu and use Internet Explorer, add theSmartCloud Control Desk URL to the trusted sites web content zone. Disablethe option that requires server verification for all sites in the zone.Do not select In the Quick Launch Bar. The selection does not create ashortcut in the Quick Launch bar.Attention: Shortcuts are created for Windows systems only.

Because WebLogic Server deployments are a manual process, you mustmanually update any shortcuts that you create. You update shortcuts afteryou have manually deployed the SmartCloud Control Desk EAR files.

21. On the Input Summary panel, review the information that you have providedfor the product installation program.If necessary, use Previous to return to previous panels to change values.




What to do next

Complete the post installation tasks that are required for installing with manualmiddleware configuration.

You must now deploy the maximo.ear and maximoiehs.ear files.

You can install optional content and integration modules from the launchpad.“Maintaining EAR files” on page 202This section contains information about maintaining SmartCloud Control DeskEAR files.










Rational Team Concert OSLC IntegrationsThis integration enables you to use the Open Services for Lifecycle


Collaboration (OSLC) technology to link from the Problems application toRational Team Concert to share information about problems and theirsolutions.



About this task


























7. Rebuild the maximo.ear file.\IBM\SMP\maximo\deployment\buildmaximoear




Before you begin



About this task





2. Type








Application Assistant opens.8. Click the upload your file(s) link.9. Click the Browse button next to the Deployment Archive field. Browse to

where you have maximo.ear file installed (c:/ibm/smp/maximo/deployment/default/ of the administrative workstation), select the file and click Open.



Next.


13. Accept all other default values and click Finish to start the deploymentprocess.

14. When the deployment process is complete, click the Activate Changes buttonin the Change Center to apply the changes. The following message displays:All changes have been activated. No restarts are necessary.

15. Repeat Steps 8 on page 43 through 14 on page 43 to deploy maximoiehs.ear.16. Click the checkbox next to the maximo application.17. Click the dropdown arrow of the Start button and select Servicing all



About this task



Properties



Results





“Manually deploying languages after database update deferral” on page 44Languages must be deployed manually if you defer database updates by theinstallation program.


Before you begin


About this task




following command:install_home\maximo\tools\maximo\TDToolkit.bat-IMPORT-SLEN-TLlocale-maxmessfix









Chapter 5. Silent installation

SmartCloud Control Desk provides the option of installing silently.

The SmartCloud Control Desk silent installation option allows you to interfacewith the SmartCloud Control Desk installation program using a command prompt(not the SmartCloud Control Desk launchpad), and a response file.

Installing SmartCloud Control Desk silentlySmartCloud Control Desk can be installed silently by using an installation responsefile.

Before you begin

You must complete a successful SmartCloud Control Desk installation to produce aresponse file that can be used for a silent installation. Alternatively, you can useone of the sample response files that are provided on the product media andmodify it according to your needs.

You must verify that all response file paths are formatted correctly. For example, aUNIX style path statement in the response file might look like the followingstatement: USER_INSTALL_DIR=K:/IBM/max_dev. If a path such asUSER_INSTALL_DIR=K:/IBM/max_dev is contained in a response file that is used witha Windows administrative system, an error occurs. The Windows equivalent in thisexample must be formatted for a Windows system: USER_INSTALL_DIR=K:\\IBM\\max_dev

Note: You can use a silent installation response file to populate SmartCloudControl Desk installation program fields during an attended installation. Removethe INSTALLER_UI=silent property from the response file before you use it with theSmartCloud Control Desk installation program. The installation program usesdefault values by reading from the response file. The SmartCloud Control Deskinstallation program uses the response file automatically when it is namedinstaller.properties or install.properties and it is in the same directory. Youdo not have to specify the response file name when you start the SmartCloudControl Desk installation program.

Note: This response file can also be used with the SmartCloud Control Deskuninstallation program to uninstall SmartCloud Control Desk silently.

About this task

To install SmartCloud Control Desk silently, complete the following steps:

Procedure1. Make configuration choices by using the SmartCloud Control Desk installation

program, and record those choices in a response file:a. Start the SmartCloud Control Desk installation program from the product

image. Use the following command for 32–bit systems:install.exe -r <response file path and name>


For 64–bit systems, use the following command:install_win64.exe -r <response file path and name>

The SmartCloud Control Desk installation program executable files are inthe SmartCloud Control Desk directory of the SmartCloud Control Desk7.5.1 product image.Response files must have a file extension of .properties, for example,response.properties.You must include the full path when you specify the response file.

b. Proceed through the SmartCloud Control Desk installation program, makingconfiguration choices.

c. Exit the SmartCloud Control Desk installation program after SmartCloudControl Desk is successfully installed.

There are several sample response files provided on the IBM SmartCloudControl Desk 7.5.1 product image.

Table 6. SmartCloud Control Desk installation program sample silent response files

File Description

simple_response.properties This file contains a sample response file thatwould be used to install a simpledeployment of SmartCloud Control Desk.

custom_response_win.properties This file contains a sample response file thatwould be used to install a customdeployment of SmartCloud Control Desk onWindows.

custom_response_unix.properties This file contains a sample response file thatwould be used to install a customdeployment of SmartCloud Control Desk onUNIX.

The files are in the SmartCloud Control Desk\samples directory of the productimage.If the response file is created by recording an actual installation, you must addan entry for LICENSE_ACCEPTED=true. If you are using a sample responsefile, you must change the entry from false to true. If a silent installation isstarted and this entry is not included in the response file then the installationends immediately. No messages or log file are created.If you plan to deploy SmartCloud Control Desk using middleware hosted onboth Windows and UNIX operating systems, your response file contains bothWindows and UNIX values. These values include directory paths andexecutable file names. In some cases, the response file is not generated becausethe user who starts the installation program does not have write access to thetarget directory. In this scenario, the installation program does not report anerror. The response file is not written to the target directory and the log file isnot produced in the ibm\smp\logs directory. To resolve this issue, ensure thatthe user who starts the installation program has write access to the targetdirectory before they run the installation program.

2. Open the response file in a text editor and change the INSTALLER_UI propertyto INSTALLER_UI=silent. Passwords are stored in clear text format. You mustedit the CONFIRM_PASSWORD fields contained in the response file to matchits corresponding password value used for each task. For example, ensure thatCONFIRM_PASSWORD matches RXA_PASSWORD in the following example:


#Middleware Server Information#-----------------------------MIDDLEWARE_SERVER=myserver.mydomain.comRXA_USER_ID=rootRXA_PASSWORD=mypasswordCONFIRM_PASSWORD=mypassword

3. Copy the response file to the target system.4. Start the SmartCloud Control Desk installation program silently and identify

the response file to be used.install.exe -f <response file path and name>

You must include the full path when you specify the response file and it mustbe on the C:\ drive of your system.

Results

The installation proceeds silently with the values that you provided in the responsefile.

Response files that include fields for Oracle configuration must be edited toremove extraneous backslashes. A response file that includes Oracle as adeployment option is generated with fields like the following excerpt:DB_INSTALL_DIR=C\:/oracle/product/10.2.0/db_1INSTANCE_LOCATION=C\:/oracle/product/10.2.0/db_1/dbsUSER_INSTALL_DIR=C\:/IBM/USER_SHORTCUTS=C\:/Documents and Settings/All Users/Start Menu/Programs/process automation engineMAXIMO_INSTALL_DIR=C\:/IBM/maximo

You must remove the backslash that is directly after the drive letter, so that yourresponse file looks like following excerpt:DB_INSTALL_DIR=C:/oracle/product/10.2.0/db_1INSTANCE_LOCATION=C:/oracle/product/10.2.0/db_1/dbsUSER_INSTALL_DIR=C:/IBM/USER_SHORTCUTS=C:/Documents and Settings/All Users/Start Menu/Programs/process automation engineMAXIMO_INSTALL_DIR=C:/IBM/maximo

If you attempt to install SmartCloud Control Desk silently and the installation UIis shown, check inside the response file to ensure that it contains this line:INSTALLER_UI=silent

Silent installation propertiesSilent installation properties are recorded in an installation response file. Silentinstallation response files are generated when the installation program is startedwith the parameters described in the silent installation procedure. Alternatively, asilent installation response file can be created and populated manually.

Chapter 5. Silent installation 105

Common silent installation properties

The following properties are common to all deployments.

Table 7. Common silent installation response file properties

Category Property Definition

File header INSTALLER_UI=SILENT This property must be set so thefile can be used with the productinstallation program.

Packagedeployment set

INSTALL_SOME_PACKAGES=0 If only a subset of packages can beinstalled, set this value to 1. Thissetting allows the productinstallation program to continue.

LicenseAgreement

LICENSE_ACCEPTED=TRUE Set this value to true to accept thelicense agreement or false to rejectit.

Installation folder USER_INSTALL_DIR=installation path Set an installation path. Forexample, for UNIX, /opt/IBM/SMPor for Windows, C:\\IBM\\SMP.

Installationdescription

INSTALLATION_DESCRIPTION Description of the installationlocation.

Deployment type SIMPLE=0 Installation is set to a type ofSIMPLE. Set to 0 to disable. Set to1 to enable. If SIMPLE is enabled,ADVANCED must be disabled.

ADVANCED=1 Installation is set to a type ofADVANCED, which is a Custominstallation. Set to 0 to disable. Setto 1 to enable. If ADVANCED isenabled, SIMPLE must be disabled.

MiddlewareServerInformation (onlyused for Simpleinstallations)

MIDDLEWARE_SERVER=host name Set the host name of the systemthat is hosting all middleware.

RXA_USER_ID=user name Set the user ID for accessing thesystem that is hosting allmiddleware.

RXA_PASSWORD=password Set a password for the user ID foraccessing the system that is hostingall middleware.

ImportMiddlewareinstallationprograminformation

MWI_IMPORT_DATA=0 Set this parameter to importconfiguration data from themiddleware installation program.

Set to 0 to disable. Set to 1 toenable.

MWI_HOSTNAME=host name Set the host name of the systemthat is hosting the middlewareinstallation program workspace.

MWI_USER_ID=user name Set a user ID used to access thesystem that is hosting themiddleware installation programworkspace. For example, root.


Table 7. Common silent installation response file properties (continued)


MWI_PASSWORD=passsword Set a password for the user IDused to access the system that ishosting the middleware installationprogram workspace.

MWI_LOCATION=path Set a path for the location of themiddleware installation programworkspace. For example, for UNIX,/root/ibm/tivoli/mwi/workspaceor for Windows,C:\\ibm\\tivoli\\mwi\\workspace.

SMTPConfiguration

SMTP_SERVER=host name Set the name of the system that ishosting the SMTP serverresponsible for distributingadministration messages to theSmartCloud Control Deskadministrator.

ADMIN_EMAIL=email address Set the email address for theSmartCloud Control Deskadministrator.

RunConfigurationStep

RUN_CONFIG_NO=0 Set the behavior of the runconfiguration step.

Set to 0 to disable (run theconfiguration step at installationtime). Set to 1 to enable (defer theconfiguration step).

DEPLOY_EAR_NO=0 Set the behavior of the EARdeployment step.

Set to 0 to disable (deploy the EARat installation time). Set to 1 toenable (defer deployment of theEAR).

DEFER_DB_UPDATE=0 Set the behavior of the databaseupdate step.

Set to 0 to disable (run updateDBat installation time). Set to 1 toenable (defer updateDB).

Shortcut Folder USER_SHORTCUTS=path Set a path for shortcuts. Forexample, for Windows,C:\\Documents andSettings\\Administrator\\Desktop\\process automationengine.


Table 7. Common silent installation response file properties (continued)


Installer version LAUNCH_NEW_INSTALLER=TRUE If a more recent version of theinstallation program was found inthe target installation directoryspecified. This circumstanceindicates that you are using anolder version of the installationprogram. In order to use thenewer version of the installationprogram, set this value to TRUE. Ifyou set this value to FALSE, theolder version of the installationprogram is used to perform theinstallation.

Users silent installation properties

The following properties are for users created by or identified to the installationprogram.

Table 8. Users silent installation properties


User Information MAXADMIN_USER_NAME=user name Set a user name for the Maximoadministrator. For example,maxadmin.

MAXADMIN_PASSWORD=password Set a password for the Maximoadministrator. For example,maxadmin.

MAXREG_USER_NAME=user name Set a user name for the selfregistration user. This user isresponsible for the process bywhich users can create their ownaccounts. For example, maxreg.

MAXREG_PASSWORD=password Set a password for the selfregistration user. For example,maxreg.

MXINTADM_USER_NAME=user name Set a user name for the internaluser. For example, mxintadm.

MXINTADM_PASSWORD=password Set a password for the internaluser. For example, mxintadm.

Common database silent installation properties

The following properties contain common information about the database used forthe deployment.

Table 9. Common database silent installation response file properties


Database Type DB_TYPE_DB2=1 Set the database type to DB2. Setto 0 to disable. Set to 1 toenable. Only one Database Typecan be enabled.


Table 9. Common database silent installation response file properties (continued)


DB_TYPE_ORACLE=0 Set the database type to Oracle. Setto 0 to disable. Set to 1 to enable.Only one Database Type can beenabled.

DB_TYPE_SQLSERVER=0 Set the database type to MicrosoftSQL Server. Set to 0 to disable. Setto 1 to enable. Only one DatabaseType can be enabled.

Database DB_HOST_NAME=host name Set the host name of the databaseserver.

DB_PORT=port Set the database port. Forexample, 50005.

DB_NAME=name Set a name for the database. Forexample, maxdb75.

DB2

DB_NAME=name Set a name for the database. Forexample, maxdb75.

Microsoft SQL Server

DB_INSTANCE=instance Set a name for the databaseinstance to use with the product.For example, ctginst1.

DB2

DB_INSTANCE=instance Set a name for the databaseinstance to use with the product.For example, ctginst1.

Oracle

DB_USER=user name Set the name of the user ID toaccess the database. For example,maximo.

DB_PASSWORD=password Set a password for the databaseuser ID. For example, maximo.

DatabaseConfigurationAutomation

AUTOMATE_DB=1 Configure the automaticconfiguration of the database bythe installation program. Set to 0 todisable. Set to 1 to enable. EitherAUTOMATE_DB orDO_NOT_AUTOMATE_DB can beenabled at one time.

DO_NOT_AUTOMATE_DB=0 Configure the automaticconfiguration of the database bythe installation program. Set to 0 todisable. Set to 1 to enable. EitherAUTOMATE_DB orDO_NOT_AUTOMATE_DB can beenabled at one time.




Remote AccessAuthorization

DB_RXA_USER=user name Set the name of the user ID toaccess the remote database serversystem. For example, root.

Only required if AUTOMATE_DBwas enabled.

DB2

Remote AccessAuthorization

DB_RXA_USER=user name Set the name of the user ID toaccess the remote database serversystem. For example, root.


Oracle

DB_RXA_PASSWORD=password Set a password for the remoteaccess user ID.


DB2

DB_RXA_PASSWORD=password Set a password for the remoteaccess user ID.


Oracle

DatabaseAdministration

DB_INSTALL_DIR=path Enter the database serverinstallation path. For example,

UNIX /opt/IBM/db2/V9.7

/opt/oracle/product/11.2.0/db_1

WindowsC:\ProgramFiles\oracle\product\11.2.0\db_1


DB2




DatabaseAdministration

DB_INSTALL_DIR=path Enter the database serverinstallation path. For example,

UNIX /opt/IBM/db2/V9.7

/opt/oracle/product/11.2.0/db_1

WindowsC:\ProgramFiles\oracle\product\11.2.0\db_1


Oracle

DB_ADMIN_USER=user name Set the name of the databaseadministrator. For example:db2admin.

DB2

DB_ADMIN_USER=user name Set the name of the databaseadministrator. For example, Sys.

Oracle

DB_ADMIN_PASSWORD=password Set a password for the remoteaccess database administrator.

DB2

DB_ADMIN_PASSWORD=password Set a password for the remoteaccess database administrator.

Oracle

Database TableSpace

DB_TABLE_SPACE_NAME=table space name Set the name of the database tablespace. For example, MAXDATA.

DB2

Database TableSpace

DB_TABLE_SPACE_NAME=table space name Set the name of the database tablespace. For example, MAXDATA.

Oracle

DB_TABLE_SPACE_SIZE=table space size in Mb Set the size of the database tablespace, in Mb. For example, 5000. y.


DB_TEMP_TABLE_SPACE_NAME=temporary table spacename

Set the name of the databasetemporary table space. Forexample, MAXTEMP.

DB2

DB_TEMP_TABLE_SPACE_NAME=temporary table spacename

Set the name of the databasetemporary table space. Forexample, MAXTEMP.

Oracle




DB_TEMP_TABLE_SPACE_SIZE=temporary table space size inMb

Set the size of the temporarydatabase table space, in Mb. Forexample, 1000.


DB2

DB_TEMP_TABLE_SPACE_SIZE=temporary table space size inMb

Set the size of the temporarydatabase table space, in Mb. Forexample, 1000.


Oracle

DB_INDEX_TABLE_SPACE_NAME=index table space name Set the name of the database indextable space. For example, MAXDATA.

DB2

DB_INDEX_TABLE_SPACE_NAME=index table space name Set the name of the database indextable space. For example, MAXDATA.

Oracle

DB_INDEX_TABLE_SPACE_SIZE=index table space size in Mb Set the size of the index databasetable space, in Mb. For example,5000.


DB2

DB_INDEX_TABLE_SPACE_SIZE=index table space size in Mb Set the size of the index databasetable space, in Mb. For example,5000.


Oracle only.

DB2 silent installation properties

The following properties contain information about an DB2 database used for thedeployment. These properties are only necessary if you are using a DB2 databasefor deployment.

Table 10. DB2 silent installation response file properties


DB2 DB_SCHEMA=schema Designate the databaseschema. For example, maximo.


Table 10. DB2 silent installation response file properties (continued)


DB_WIN_SERVICE_USER=user name Set the name of the databaseservice owner in Windows. Forexample, ctginst1.


DB_WIN_SERVICE_PASSWORD=password Set a password for the databaseservice owner in Windows.


DB2_VARCHAR=0 Configure varchar or vargraphic inthe database by the installationprogram. Set to 0 to use vargraphicformatting. Set to 1 to use varchar.

varchar formatting supportsEnglish only.

Oracle silent installation properties

The following properties contain information about an Oracle database used forthe deployment. These properties are only necessary if you are using an Oracledatabase for deployment.

Table 11. Oracle silent installation response file properties


Oracle ORACLE_OWNER_ID=user name Set the Oracle software owner userID. For example, oracle.


ORACLE_OWNER_PASSWORD=password Set the Oracle software ownerpassword.


INSTANCE_LOCATION=instance location Set the Oracle database instancelocation. For example,/opt/oracle/product/11.2.0/db_1.


Microsoft SQL Server silent installation properties

The following properties contain information about a Microsoft SQL Serverdatabase used for the deployment. These properties are only necessary if you areusing a Microsoft SQL Server database for deployment.


Table 12. Microsoft SQL Server silent installation response file properties


Microsoft SQLServer

SQL_DATA_FILE_NAME=data file name Set the file name for the MicrosoftSQL Server data source. Forexample, maxdb75_dat.


DB_TABLE_SPACE_SIZE=data source size in Mb Set the size of the Microsoft SQLServer data source, in Mb. Forexample, 1000.


SQL_ADMIN=user name Set the name of the Microsoft SQLServer administrator. For example,sa.


SQL_ADMIN_PW=password Set a password for the MicrosoftSQL Server administrator.


SQL_LOG_FILE_NAME Microsoft SQL Server logname. For example, maxdb75_log


Common application server silent installation properties

The following properties contain common information about the application serverused for the deployment.

Table 13. Common application server silent installation response file properties


APPLICATION_SERVER_TYPE_BEA=0 Configure the application serverused for the SmartCloud ControlDesk deployment. Set to 0 todisable. Set to 1 to enable.

Only one Application Server Typecan be enabled.


Language silent installation properties

The following properties are used to configure languages.

Table 14. Language silent installation response file properties


BaseLanguage

BASE_ARABIC=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.

Set to 0 todisable. Set to 1to enable.

BASE_BRAZILIAN_PORTUGUESE=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_CROATIAN=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_CZECH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_DANISH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.



Table 14. Language silent installation response file properties (continued)


BASE_DUTCH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_ENGLISH=1 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_FINNISH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_FRENCH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_GERMAN=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.





BASE_HEBREW=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_HUNGARIAN=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_ITALIAN=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_JAPANESE=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_KOREAN=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.





BASE_NORWEGIAN=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_POLISH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_RUSSIAN=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_SIMPLIFIED_CHINESE=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_SLOVAK=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.





BASE_SLOVENIAN=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_SPANISH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_SWEDISH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_TRADITIONAL_CHINESE=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.


BASE_TURKISH=0 Set this languageas the baselanguage used bythe SmartCloudControl Deskapplication.





AdditionalLanguages

ADD_ARABIC=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_BRAZILIAN_PORTUGUESE=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_CROATIAN=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_CZECH=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_DANISH=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.





ADD_DUTCH=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_ENGLISH=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_FINNISH=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_FRENCH=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_GERMAN=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.





ADD_HEBREW=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_HUNGARIAN=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_ITALIAN=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_JAPANESE=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_KOREAN=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.





ADD_NORWEGIAN=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_POLISH=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_RUSSIAN=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_SIMPLIFIED_CHINESE=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_SLOVAK=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.





ADD_SLOVENIAN=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_SPANISH=1 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_SPANISH=1 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_TRADITIONAL_CHINESE=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.


ADD_TURKISH=0 Set this languageas an additionallanguage used bythe SmartCloudControl Deskapplication.



Chapter 6. Programmatically verifying that the installation wassuccessful

After you have exited the SmartCloud Control Desk installation program withoutencountering any errors, you can verify that the installation completed successfully.The installation is programmatically verified through the use of post installationvalidation utilities.

Before you begin

The JAVA_HOME environment variable must be set on the system before you canuse the verification utilities.

About this task

During installation, the SmartCloud Control Desk installation program performs asimple health check. This health check consists of logging in to the application toverify availability. This health check might not be sufficient to verify a successfulinstallation in all deployment scenarios. For example, if, during installation, youselect the option to deploy the application EAR file at a later date, this healthcheck cannot verify the installation. This simple health check is also insufficient forverifying an upgrade.

Post installation validation utilities are available after the product has beendeployed.

The middlewareValidate utility is used to verify the middleware.

The installValidation utility is used to validate the product installation. Thesecommand-line utilities are used to verify the installation and configuration of theproduct in a more complete manner. These utilities can also be used to verify anexisting deployment after changes in the environment, such as changes to hostnames, user IDs, and passwords.

Results of the installValidation utility are logged ininstallValidationTrace00.log. This log is found in the \ibm\smp\logs directoryon the administrative workstation.

Procedure1. 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 theadministrative workstation. If you intend to use the middlewareValidateutility, log in to the server hosting the middleware.

2. Ensure the JAVA_HOME environment variable is set properly to the location ofa JRE 1.6 installation.

3. To verify product installation, from the administrative workstation, changedirectory to \ibm\smp\scripts and run the installValidation.bat command.For either command, use the parameters described below: To verifymiddleware installation, from the middleware image, update themiddleware.properties file with the installation parameter values formiddleware components to be verified, change directory to \HealthCheck andrun the middlewareValidate.[sh|bat] command.


Table 15. Verification utilities parameters

Program Syntax parameters Input

installValidation.bat -action Use -action validate to start thevalidation of the product installation.

The -action parameter is the onlymandatory parameter when using theinstallValidation utility.

-trace Verification progress information iswritten to the screen during theverification process. You can modifythe output using the -tracingparameter.

v minimal

Progress information is limited toerror information.

v normal

Information includes individualtest progress, individual testresults, and overall progress of theentire verification process.

This is the default mode of tracing.

v verbose

In addition to providing normalprogress information, verbosetracing includes the test classname, test method name, andcorrective action information.

-confirm You are prompted before each test isstarted. You must confirm each testto be performed. There is no inputfor this parameter.

-component You can provide a comma-delimitedlist of directories containing the testobjects to limit testing to a specificset of tests.

These test objects must be located inthe \ibm\smp\HealthValidation\directory. For the product installationprogram, only the CTGIN folder isprovided.

-dbuser Provide the user ID used to accessthe database.

-dbpwd Provide the password of the user IDused to access the database.

-maxuser Provide the SmartCloud ControlDesk administrator user ID. Forexample, maxadmin.

-maxpwd Provide the password for theSmartCloud Control Deskadministrator user ID.


Table 15. Verification utilities parameters (continued)


middlewareValidate.[sh|bat] -middlewareproperties Use

-middlewareproperties file

where file is the location of themiddleware.properties file. Bydefault, this file is found on themiddleware installation media in the\HealthCheck directory.

The middleware.properties containsthe middleware installationproperties, such as installationlocations and ports. User names andpasswords are not stored in thisplain-text file. Some of the propertiescommon to all platforms have beendefined default values, butplatform-specific properties likeinstallation locations need to beupdated in this file before startingthe middlewareValidate utility.

The -middlewarepropertiesparameter is the only mandatoryparameter when using themiddlewareValidate utility.

-trace Verification progress information iswritten to the screen during theverification process. You can modifythe output using the -traceparameter.

v minimal

Progress information is limited toerror information.

v normal

Information includes individualtest progress, individual testresults, and overall progress of theentire verification process.

v verbose

In addition to providing normalprogress information, verbosetracing includes the test classname, test method name, andcorrective action information.

If this option is not provided, bydefault, no output displayed.

Chapter 6. Programmatically verifying that the installation was successful 127

Table 15. Verification utilities parameters (continued)


-component Specify the middleware components:

v DBSERVER - verify installation ofthe IBM DB2 server.

v DIRSERVER - verify installation ofthe optional IBM Tivoli DirectoryServer.

v LDAPSERVER - verifyconfiguration of the optional IBMTivoli Directory Server.

One or more of these keywords canbe specified as comma separated list.If this argument is skipped, the toolassumes all the components areselected to verify.

-bindUser Provide the bind user.

Required to verify LDAPSERVER.The bind user credentials, bindDistinguished Name and bindpassword are required to be specifiedwith the -bindUser and -bindPassoptions.

-bindPass Provide the password for the binduser.

Required to verify LDAPSERVER.The bind user credentials, bindDistinguished Name and bindpassword are required to be specifiedwith the -bindUser and -bindPassoptions.

For example,installValidation.bat -action validate

Results

The installValidation.bat validation utility results are logged inctginstallvalidationtrace00.log. This log is found in the \ibm\smp\logsdirectory on the administrative workstation.

The middlewareValidate.[sh|bat] validation utility results are logged inCTGInstallValidationTrace.log. This log is found in the HealthCheck directory.


Chapter 7. Verifying the installation manually

After you exit the SmartCloud Control Desk installation program without errors,you can further verify that the installation completed successfully. The installationis manually verified by locating key artifacts and performing a few simple tasks.

Before you begin

The product installation program performs installation verification, or a healthcheck, by logging on to the product before exiting the installation. The productinstallation program returns a success message if all installation steps, includingthe product log in task, are successful. If the health check task is unsuccessful, aHealthCheckFailed error is thrown for the getUrlContentString function. Thiserror is in the install_home\logs\CTGInstallTraceXX.log file, where XX is atwo-digit number such as 00.

About this task

To further verify that the SmartCloud Control Desk installation was completedsuccessfully, perform the following verification procedures:

Procedure1. Examine the CTGInstallTrace00.log file for success messages.

The following success messages are found in the CTGInstallTrace00.log fileand can be used to verify which phases of the installation were successful:v CTGIN2114I: The database was created successfullyv CTGIN2135I: Tablespace maxdata created successfullyv CTGIN2135I: Tablespace maxtemp created successfullyv CTGIN2079I: process automation engine database configuration completed

successfully (This message indicates that maxinst finished successfully.)v CTGIN2253I: buildmaximoear.cmd completed successfullyv CTGIN2253I: buildhelpear.cmd completed successfullyv CTGIN2208I: runConfigurationStep completed successfullyv CTGIN2370I: The installation finished successfullySearch the CTGInstallTrace00.log file for the following message, whichindicates that the maxinst task completed successfully:CTGIN2079I, maxinst.*completed

2. Compare the packages chosen for installation with the packages that wereinstalled. The Package Summary panel of the SmartCloud Control Deskinstallation program provides a summary of all the packages to be installed.You can compare the contents of that panel with a listing of what was installedon the system. Use the solutioninstaller command to list installed packages:install_home\bin\setupPSIenv.batinstall_home\bin\solutionInstaller.bat -action showInstalled -type all

The resulting list matches the packages listed in the Package Summary panel.3. Log in to the product and verify that applications are present. Being able to log

in to the product manually is a good indicator that the installation was


successful. Once you have logged in, verify that you can access expectedapplications. If you experience access problems with the product, clear thecache of your browser and try again.


Chapter 8. Installing Integration ComposerAfter you have successfully installed the IBMSmartCloud Control Desk components, you canoptionally install (or upgrade) Integration Composer, anintegration tool that imports information technology (IT)data into the Maximo database.

IBM SmartCloud Control Desk installations use theLaunchpad as an interface for installing IntegrationComposer. However, if necessary, you can installIntegration Composer on a UNIX operating system inconsole mode, from the command line.

When you install Integration Composer and IBMSmartCloud Control Desk from the Launchpad, theinstaller automatically updates the Integration Composerdatabase tables in the Integration Composer repositoryfor you.

Integration Composer overviewIntegration Composer is the IBM application for transforming and importinginventory data about deployed hardware and software. This inventory data isimported from a discovery or system management tool database into the Maximodatabase tables for deployed assets or configuration items.

With Integration Composer, an enterprise can aggregate data collected by externaldiscovery tools and integrate it into the Maximo database, creating a centralrepository for enterprise IT asset management, reporting, and decision support.The Maximo database is the repository used by:v IBM Tivoli Asset Management for ITv IBM Tivoli Service Request Manager®

v IBM Tivoli Change and Configuration Management Database

To collect the data about deployed assets or configuration items, a discovery toolscans computers, network devices, and network printers deployed in an enterpriseand records information about the hardware and software it finds there.Integration Composer uses an integration adapter to transform the data collectedby the discovery tool and move it from the discovery tool database into theMaximo database. (For more about creating your own integration adapter, see thebook Integration Composer Administrator Guide.)

You can view imported data from various applications on your system. The data isalso used to generate reports.

Note: Integration Composer is used to import hardware and software inventorydata from a discovery tool database into the Deployed Asset, Actual CI, or (for thepurposes of asset initialization) Asset tables in the Maximo database. The import orexport of data into or out of other tables within the Maximo database isaccomplished using a different tool, the integration framework. Refer to the relatedbook, Integration Guide, for more on this subject.


Hardware and software requirementsThis section describes the products and versions supported by IntegrationComposer, plus the hardware and software requirements for the corequisiteapplications.

The hardware and software requirements for Integration Composer and itscorequisites are as follows:

IntegrationComposer

Integration Composer 7.5.1 has the following minimum requirements:

v 3 GB memoryv 70 MB disk spacev IBM Java Software Development Kit 6.0 for the appropriate operating system

A compatible assetmanagementproduct

One of the following compatible products is required and must be installed beforeyou can use Integration Composer. For details about version compatibility, see thedocumentation for the specific product:

v IBM Tivoli Unified Service Centerv IBM Tivoli Asset Management for ITv IBM Tivoli Service Request Managerv IBM Tivoli Change and Configuration Management Database


IBM TivoliIntegrationComposer server

A dedicated server is required for running the Integration Composer applicationand Java components. Integration Composer can run on any of the followingoperating systems:

v HP-UX 11i 3 (on Intel Itanium hardware)v IBM AIX 5L™ 6.1 (32-bit)v IBM AIX 5L 6.1 (64-bit)v IBM AIX 5L 7.1 on Power Systems™ hardware (32-bit)v IBM AIX 5L 7.1 on Power Systems hardware (64-bit)v Microsoft Windows Server 2003 Enterprise Edition (on x86-32 hardware)v Microsoft Windows Server 2003 Enterprise Edition (on x86-64 hardware)v Microsoft Windows Server 2008 Enterprise Edition, Release 2 (on x86-64

hardware)v Microsoft Windows Server 2008 Standard Edition, Release 2 (on x86-64

hardware)v Red Hat Enterprise Linux 5 (on x86-32 hardware)v Red Hat Enterprise Linux 5 (on x86-64 hardware)v Red Hat Enterprise Linux 5 (on zSeries and System z hardware)v Red Hat Enterprise Linux 6 (on x86-32 hardware)v Red Hat Enterprise Linux 6(on x86-64 hardware)v Sun Solaris 9 (on SPARC processor-based systems)v Oracle Solaris 10 (on SPARC processor-based systems)v SUSE Linux Enterprise Server (SLES) 10 (on System z hardware)v SUSE Linux Enterprise Server (SLES) 10 (on x86-32 hardware)v SUSE Linux Enterprise Server (SLES) 10 (on x86-64 hardware)v SUSE Linux Enterprise Server (SLES) 11 (on System z hardware)v SUSE Linux Enterprise Server (SLES) 11 (on x86-32 hardware)v SUSE Linux Enterprise Server (SLES) 11 (on x86-64 hardware)v SUSE Linux Enterprise Server (SLES) 11 (for IBM POWER® processors)v VMWare ESX Server 3

Note: Bidirectional languages are not supported on the Sun Solaris platform.

Chapter 8. Installing Integration Composer 133

Database servers The customer is responsible for the database servers, which contain and manageone or more source databases and a target (Maximo) database.

The following databases are supported:

v IBM DB2 Enterprise Server Edition 9.5 (on all supported operatingsystems—does not support 32-bit Linux)

v IBM DB2 Enterprise Server Edition 9.7v Microsoft SQL Server 2008 Enterprise Edition (on Microsoft Windows operating

systems only)v Oracle Database 9i Enterprise Edition Release 2.9.2.0.8 (on all supported

operating systems)v Oracle Database 10g Enterprise Edition Release 1 (on all supported operating

systems)v Oracle Database 10g Enterprise Edition Release 2 (on all supported operating

systems)v Oracle Database 11g Enterprise Edition Release 1 (on all supported operating

systems)v [Upgrade only] Oracle Database 11g Enterprise Edition Release 2 (on all

supported operating systems)

See the appropriate database documentation for the database server hardwarerequirements.

Web browser To display its help information, Integration Composer requires a Web browser.

Installation prerequisitesBefore installing, you must have the IBM Java Software Development Kitprerequisite for Integration Composer on your system, and any software thatadversely affects the InstallAnywhere installation program must be removed.

IBM Java SDK 6.0 for the appropriate operating system is an installationprerequisite that must be present on the Integration Composer computer. The IBMJava SDK is provided on the product DVDs.

The installation or upgrade has to run on JRE 1.6, so it must be set as the system'sJava virtual machine (JVM). If more than one JRE is installed on the computer, thePATH and CLASSPATH system variables must indicate JRE 1.6.

UNIX On UNIX-based operating systems, be sure the PATH environmentvariable includes the location of the Java Virtual Machine (for example, Java60).

Because the following software can adversely affect InstallAnywhere—theinstallation program used by Integration Composer—disable the followingprograms before attempting to install Integration Composer:v Antivirus software, such as Norton Antivirus or Symantec Client Firewallv Dell OpenManagev Search software, such as pcAnywhere


Use of these software programs affects the ability of InstallAnywhere to installprograms; however, the problem is not specific to Integration Composer.

[Installation only] Before beginning your installation, make sure you have on handthe information on the target (Maximo) database described in Table 16 on page 136.

Performing an Integration Composer installationSmartCloud Control Desk installations that want to use Integration Composershould install it from the Launchpad, as described herein. If you need to installIntegration Composer on a UNIX operating system in console mode, instructionsto do that are also described.

Results

When the installation completes successfully, you can access Integration Composeras follows:

Windows From the Start menu, or by entering the command: itic_installation_dir\bin\startFusion.bat

The default Integration Composer installation directory for Windowsoperating systems is C:\Integration Composer.

UNIX By entering the command: itic_installation_dir/bin/startFusion.sh

The default Integration Composer installation directory for UNIX operatingsystems is /home/user/Integration_Composer.

Installing Integration Composer using the LaunchpadWindows UNIX For IBM SmartCloud Control Desk installations, the

recommended way to install Integration Composer is from the Launchpad. Use theLaunchpad to install Integration Composer on Windows or UNIX operatingsystems.

Before you begin

Make sure that you have up to 70 MB of free space for the installation directory.

Procedure1. Insert the Launchpad DVD into the server where you install Integration

Composer.If you are installing on a UNIX operating system, you might have to start theLaunchpad manually by running the launchpad.sh command, which is locatedin the root directory of the Launchpad DVD. (On Windows operatingsystems, the launchpad.exe command runs automatically.)

Note: Confirm that the java -version command returns 1.6 before startingthe installation. IBM Java SDK 6.0 with JRE 1.6 is provided on the productDVDs.

2. From the Launchpad, launch the Integration Composer installation programby clicking the link under Install IBM Tivoli Integration Composer.

3. In the IBM Tivoli Integration Composer window, select your language fromthe drop-down list at the bottom and click OK.


4. [UNIX only] In the Select Install Type window, select New Install and clickNext.

5. In the Introduction window, review the information and click Next.6. 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. Thenclick Next.

7. In the Choose Install Folder window, accept the default location or type a filepath to specify where you want to install the product. (Or you can clickChoose to browse and select the location you want.) Then click Next.

8. In the Database Type window, select your Maximo database type (the Maximodatabase is where the Integration Composer repository is installed) and clickNext. IBM DB2 is the default.The Database Login Information window is displayed.

9. On the Database Login Information window, type login specifications for thedatabase and click Next.The Database Login Information window is where you define the parametersfor connecting to the Maximo database. The fields displayed in this windowvary slightly, depending on the type of database you chose in the previousstep. The following table defines the fields that the installation programdisplays for the supported databases.

Table 16. Login specifications for the Maximo database

Field Description

Database Server Name Name of the server on which the Maximo databaseresides

Port Number Port number of the server on which the Maximodatabase resides

Database Name (SID)

or

Database Name

For Oracle databases, this is the session identifier(SID) for the database; that is, the databaseinstance

For SQL Server or IBM databases, this is simplythe name of the database

Database Username Valid user name for signing in to the Maximodatabase

Database/Schema Owner Database or schema owner

Tip: Make note of the values that you specified here. Later, when you launchIntegration Composer, use the values entered in these fields to defineconnection parameters for the Maximo database.

10. On the Update Software Instances window, select one of the following optionsand click Next:

Yes, disable software updatesIf you select this option, when Integration Composer imports data intothe Maximo database, Integration Composer inserts or deletessoftware records but does not update software records. This option ispreferred.

No, don't disable software updatesIf you select this option, when Integration Composer imports data intothe Maximo database, Integration Composer updates existing softwarerecords.


In the Software Class Name field, it is recommended to accept the defaultvalue Software. The Software Class name is used to identify the class that youdo not want to update based on the choice you made. In the Deployed Assetstarget schema, the name is Software.

11. [UNIX only] In the Choose Internet Browser File window, accept the defaultbrowser or choose another browser to be used for displaying the IntegrationComposer online help, then click Next.

12. On the Preinstallation Summary window, review the installation details. (Ifnecessary, use the Previous buttons to go back and make corrections, and usethe Next buttons to return to this window.) When satisfied with the summarydata, click Install.The Installing Integration Composer progress window displays duringinstallation. When installing is finished, the Installation Complete window isdisplayed.

13. In the Installation Complete window, click Done.

Installing Integration Composer on UNIX operating systems inconsole mode

UNIX Use the procedure described here if you have to install IntegrationComposer on a UNIX computer in console (command line) mode.

Before you begin

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\ITICdirectory on the version 7.5.1 product DVD. Use the setup.bin command from theDVD layout to start the upgrade process:setup.bin ←setup.exe

The steps for installing Integration Composer on a UNIX-based operating systemfollow.

Procedure1. 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_locationis the path for your IBM JRE; for example, /opt/ibm/java-i386-60/jre/bin:$PATH):JAVA_HOME=JRE_locationexport JAVA_HOMEPATH=$JAVA_HOME:$PATHexport 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 byentering 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 startingthe installation. IBM Java SDK 6.0 with JRE 1.6 is provided on the productDVDs.

7. In the Choose Locale step, type the number of your locale from the list oflocales and press Enter.

8. In the Introduction step, review the Introduction information and press Enter.9. In the Select Install Type step, press Enter to accept the default (New Install).

10. In the IBM SDK Location step, specify the file path where IBM Java SDK 6.0 isinstalled 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.

11. In the Choose Install Folder step, specify where you want to install IntegrationComposer 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; then type y to

confirm the new location, and press Enter again.12. In the Database Type step, indicate your Maximo database type (the Maximo

database is where the Integration Composer repository will be installed) bytyping the associated number; then press Enter. The Database LoginInformation step is displayed.This Database Login Information step is where you define the parameters forconnecting to the Maximo database. The fields displayed in this step varyslightly, depending on the type of database you chose in the previous step.The following table defines the fields that the installation program displaysfor the supported databases.

Field Description

Database Server Name Name of the server on which the target databaseresides

Port Number Port number of the server on which the targetdatabase resides

Database Name (SID)

or

Database Name

For Oracle databases, this is the session identifier(SID) for the database; that is, the database instance

For SQL Server or databases provided by IBM, thisis simply the name of the database

Database Username Valid user name for signing in to the targetdatabase

Database/Schema Owner Database or schema owner

13. In the Database Login Information step, type each login specification for thedatabase, one at a time, pressing Enter after each entry to advance to the nextspecification.


Tip: Make note of the values that you specified here. Later, when you launchIntegration Composer, use the values entered in these fields to defineconnection parameters for the target data source.

14. In the Update Software Instances step, type a number to select one of thefollowing options, and press Enter:v Yes, disable software updates

If you select this option, when Integration Composer imports data into thetarget database, Integration Composer inserts or deletes software recordsbut does not update software records. This option is preferred forperformance reasons.

v No, don't disable software updates

If you select this option, when Integration Composer imports data into thetarget database, Integration Composer updates existing software records.

15. In the Software Class Name step, accept the default and press Enter.16. In the Choose Internet Browser File step, accept the default browser, Netscape

(only the Netscape browser is supported on UNIX-based operating systems);then press Enter.

17. In the Preinstallation Summary step, review the installation details and pressEnter to begin installing Integration Composer. The Installing progress bardisplays during installation.When installation is complete, the Installation Complete step is displayed.

18. In the Installation Complete step, press Enter. The installation is done and youare returned to the UNIX command prompt.

Performing an Integration Composer upgradeIBM SmartCloud Control Desk installations that want to upgrade IntegrationComposer should do so from the Launchpad, as described herein. If you need toupgrade 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, includingIntegration Composer 7.2.1, 7.2.2, and 7.2.2.1. The installation program does notpermit upgrades from earlier releases. On Windows operating systems, theinstallation program automatically checks for a valid current release prior toupgrading.

Results

When the upgrade completes successfully, you can access Integration Composer asfollows:

Windows From the Start menu, or by entering the command: itic_installation_dir\bin\startFusion.bat

The default Integration Composer installation directory for Windowsoperating systems is C:\Integration Composer.

UNIX By entering the command: itic_installation_dir/bin/startFusion.sh

The default Integration Composer installation directory for UNIX operatingsystems is /home/user/Integration_Composer.


Upgrading Integration Composer using the LaunchpadWindows UNIX For SmartCloud Control Desk installations, the recommended

way to upgrade Integration Composer is from the Launchpad. Use the Launchpadto upgrade Integration Composer on Windows or UNIX operating systems.

Before you begin

To avoid losing any of your current data, back up your Integration Composerdata\dataschema and data\mappings directories before upgrading.

Attention: For this release, the Naming and Reconciliation Service (NRS) wasupgraded to Data Integration Services (DIS). As part of this Integration Composerinstallation, the nameReconciliation.logging.properties file is removed from theproperties subdirectory in the Integration Composer installation directory, and theremoved file is replaced with the dis.logging.properties file. As a result, anycustomizations that were made to the originalnameReconciliation.logging.properties file are lost.

Before upgrading to this release of Integration Composer, note your currentcustomization information if you plan to to reuse any of that information in thenew dis.logging.properties file. For additional details about these propertiesfiles, see the book IBM Tivoli Integration Composer Administrator Guide.

Make sure that you have up to 70 MB of free space for the installation directory.

Procedure1. 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 theLaunchpad manually by running the launchpad.sh command, which is locatedin 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 theupgrade. 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 byclicking the link under Install IBM Tivoli Integration Composer.

3. In the IBM Tivoli Integration Composer window, select your language from thedrop-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 clickChoose to browse and select the location you want.) Then click Next.

7. In the Choose IBM SDK Location window, type the directory where IBM JavaSDK 6.0 is located, or click Choose to browse and select the directory. Thenclick Next.

8. On the Preinstallation Summary window, review the upgrade details. (Ifnecessary, use the Previous buttons to go back and make corrections, and usethe Next buttons to return to this window.) When satisfied with the summarydata, click Install.


The Installing Integration Composer progress window displays duringupgrade. When upgrading is finished, the Installation Complete window isdisplayed.

9. In the Installation Complete window, click Done.

Upgrading Integration Composer on UNIX operating systemsin console mode

UNIX Use the procedure described here if you have to upgrade IntegrationComposer on a UNIX computer in console (command line) mode.

Before you begin

Installing Integration Composer 7.5.1, as described in this section, will upgrade theprevious version of Integration Composer. You do not need to remove the previousversion first. To avoid losing any of your current data, back up your IntegrationComposer data\dataschema and data\mappings directories before upgrading.

Attention: For this release, the Naming and Reconciliation Service (NRS) wasupgraded to Data Integration Services (DIS). As part of this Integration Composerinstallation, the nameReconciliation.logging.properties file is removed from theproperties subdirectory in the Integration Composer installation directory, and theremoved file is replaced with the dis.logging.properties file. As a result, anycustomizations that were made to the originalnameReconciliation.logging.properties file are lost.

Before installing this release of Integration Composer, note your currentcustomization information if you plan to to reuse any of that information in thenew dis.logging.properties file. For additional details about these propertiesfiles, 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\ITICdirectory on the version 7.5.1 product DVD. Use the setup.bin command from theDVD layout to start the upgrade process:setup.bin ←setup.exe

The steps for upgrading Integration Composer on a UNIX-based operating systemfollow.

Procedure1. 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_locationis the path for your IBM JRE; for example, /opt/ibm/java-i386-60/jre/bin:$PATH):


JAVA_HOME=JRE_locationexport JAVA_HOMEPATH=$JAVA_HOME:$PATHexport 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 byentering 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 startingthe upgrade. IBM Java SDK 6.0 with JRE 1.6 is provided on the productDVDs.

7. In the Choose Locale step, type the number of your locale from the list oflocales and press Enter.

8. In the Introduction step, review the Introduction information and press Enter.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 Composerfrom the previous release.

10. In the Choose Install Folder step, type the location (absolute path) whereIntegration Composer is currently installed and press Enter. Or just pressEnter to accept the displayed path.

11. In the IBM SDK Location step, specify the file path where IBM Java SDK 6.0 isinstalled 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 pressEnter to begin installing Integration Composer. The Installing progress bardisplays 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 youare returned to the UNIX command prompt.

Confirming the installationThis section explains how to verify that your new Integration Composerinstallation (or upgrade) is installed correctly.

Procedure1. Open the Integration Composer application by doing one of the following

things:

Windows From the Windows Start menu, select Start > Programs > IBM Tivoli >Integration Composer > IBM Tivoli Integration Composer

or

from the command line, enter the command: startFusion.bat


UNIX Enter the command: ./startFusion.sh.

2. Sign in to the Integration Composer application using the database (or schemaowner) username and password that you supplied during the installation.

3. From the Help menu in the Integration Composer main window, select About.4. On the About Integration Composer window, check that the number in the

Version field is 7.5.1. If this number is displayed, Integration Composer wassuccessfully installed.

Post-installation tasksThis section provides instructions for verifying that Integration Composer isconfigured correctly after you install or upgrade.

Verifying the settings in the Integration Composerfusion.properties file

The fusion.properties file is the properties file for Integration Composer. Amongother things, these properties specify Maximo and Integration Composerdatabase-related properties and application properties. This verification task is toensure that, after you have installed or upgraded Integration Composer, criticalproperty settings in the fusion.properties file are correct.

Before you begin

The Integration Composer fusion.properties file is located as follows:

itic_install_dir\data\properties\fusion.properties

Procedure1. Locate the Integration Composer fusion.properties file in your Integration

Composer installation directory, itic_install_dir.2. In the IBM Tivoli Integration Composer (ITIC) Mapping Execution Properties

section, verify that NRS is enabled (set to true) if you are using NRS:mxe.fusion.mapping.nrs.enable=true

or disabled (set to false) if you are not using NRS:mxe.fusion.mapping.nrs.enable=false

Naming and Reconciliation Service (NRS), which is part of Data IntegrationServices (DIS), is an optional component that Integration Composer works withto uniquely identify deployed assets or actual CIs (configuration items) andavoid duplication of asset or CI records in your database.By default, Integration Composer is configured to use this component, whichassigns a globally unique identifier, the DIS GUID, to a deployed asset or actualCI based on defined naming rules. However, Integration Composer will notoperate successfully if it is configured to use NRS (if the NRS property is set totrue) but NRS is not installed and running. So, if you do not use NRS, be sureto set the NRS property to false so that Integration Composer will runsuccessfully.DIS/NRS is required to perform automated linking of their authorized asset andCI counterparts. If you use this function, you should have DIS/NRS runningand have the NRS property in the fusion.properties file set to true.


Integration Composer recommends that DIS/NRS be installed and enabled. TheNRS property is enabled (set to true) by default.

3. In the IBM Tivoli Maximo Database Related Properties section, verify that thedatabase schema owner, JDBC driver specification, and JDBC URL specificationare correct. Use the following table as a guide:

Property Description Value

mxe.db.schemaowner Database schemaowner

Enter the appropriate schema for your database; for example, dbo.

mxe.db.driver JDBC driverspecification

This varies depending on the database, for example:

IBM DB2:com.ibm.db2.jcc.DB2Driver

Oracle JDBC Thin driver:oracle.jdbc.driver.OracleDriver

Microsoft JDBC driver (SqlServer):com.microsoft.sqlserver.jdbc.SQLServerDriver

i-net Opta driver (SqlServer):com.inet.tds.TdsDriverNote: Users upgrading from a previous release and whoalready have this (deprecated) driver can still use it forMicrosoft SQL Server support. However, in the future, usingthe Microsoft JDBC driver for your SQL Server isrecommended.

mxe.db.url JDBC database URL This varies depending on the database, for example:

IBM DB2:jdbc:db2://host_name:host_port/database_name

Oracle JDBC Thin driver:jdbc:oracle:thin:@host_name:host_port:host_SID

Microsoft JDBC driver (SqlServer):jdbc:sqlserver://host_name:host_port;databaseName=database_name;integratedSecurity=false;

i-net Opta driver (SqlServer 7.0 or higher):jdbc:inetdae7:host_name:host_port?database=database_nameNote: Users upgrading from a previous release and whoalready have this (deprecated) driver can still use it forMicrosoft SQL Server support. However, in the future, usingthe Microsoft JDBC driver for your SQL Server isrecommended.

mxe.db.user Database user loginname

4. UNIX In the Integration Composer (ITIC) Application Properties section,users of UNIX-based operating systems should check that themxe.fusion.browser property specifies netscape. For UNIX, Netscape is the onlysupported Web browser for Integration Composer:mxe.fusion.browser=netscape


Note: Windows For Windows operating systems, the browser always defaultsto Microsoft Windows Explorer.

Changing the memory allocation in the startFusion file(optional)

The startFusion file, named startFusion.bat in Windows operating systems orstartFusion.sh in UNIX-based operating systems, is the startup file for theIntegration Composer graphical user interface. This verification task is to ensurethat, after you have installed or upgraded Integration Composer, the memoryallocation in the startFusion file is correct.

Before you begin

This task is optional. You need to perform it only if the Integration Composergraphical user interface does not start as described in “Confirming the installation”on page 142.

About this task

The Integration Composer startFusion file is located in the Windows and UNIXinstallation directories, as follows:

Windows itic_install_dir\bin\startFusion.bat

UNIX itic_install_dir/bin/startfusion.sh

When you install Integration Composer, the installation program assigns 1536megabytes as the default amount of virtual RAM to allocate to the application. But,for example, if your server only has 1GB of physical memory, the 1536M setting willnot work for you.

Procedure

If the Integration Composer graphical user interface does not start, check thememory setting for the start javaw.exe command in the startFusion file, anddecrease memory as necessary.

Example

For example, change -Xmx1536M to -Xmx1024M.

Changing the memory allocation in the executeMapping file(optional)

The executeMapping file, named executeMapping.bat in Windows operating systemsor executeMapping.sh in UNIX-based operating systems, is the IntegrationComposer script for running a mapping. This verification task is to ensure that,after you have installed Integration Composer, the memory allocation in theexecuteMapping file is correct.

Before you begin

This task is optional. You need to perform it only if the Integration Composermapping does not run, or if you just upgraded and had increased the amount of


memory allocated to Integration Composer in your previously installed version.

About this task

The Integration Composer executeMapping file is located in the Windows andUNIX-based installation directories, as follows:

Windows itic_install_dir\bin\executeMapping.bat

UNIX itic_install_dir/bin/executeMapping.sh

When you install Integration Composer, the installation program assigns 1536 MBas the default amount of virtual RAM to allocate to the application. But, forexample, if your server only has 1 GB of physical memory, the 1536M setting willnot work for you.

Procedurev If the Integration Composer mapping does not run, check the memory setting

for the java command in the executeMapping file, and decrease memory. To doso, edit the executeMapping file and change the –Xmx parameter in the javacommand.For example, change -Xmx1536M to -Xmx1024M

v [Upgrade only] If you previously increased the amount of memory allocated toIntegration Composer imports, verify that your memory settings have notchanged. If you have to increase the amount of memory assigned, edit theexecuteMapping file and change the –Xmx parameter in the java command.For example: change -Xmx1536M to -Xmx2048M

Uninstalling Integration ComposerThis section provides instructions for removing Integration Composer fromMicrosoft Windows and UNIX-based operating systems.

Uninstalling Integration Composer on Windows operatingsystems

Windows Use the procedure described here to remove Integration Composer froma Windows-based operating system.

Procedure1. In Microsoft Windows Explorer, go to the uninstall folder, installation_dir\

Uninstall_Integration_Composer, where Integration Composer 7.5.1 wasinstalled.

2. In the uninstall folder, double-click the uninstall file,Uninstall_Integration_Composer.exe. The Integration Composer utility foruninstalling the application displays the Uninstall IBM Tivoli IntegrationComposer window.

3. Click Uninstall. The Uninstall IBM Tivoli Integration Composer progresswindow is displayed as the uninstall utility removes the application.

Note: If necessary, you can click Cancel to stop the uninstallation.


When the removal of Integration Composer is finished, the Uninstall Completewindow is displayed.

4. Click Done. The removal of Integration Composer is completed.5. Optional: When the utility removes Integration Composer, one or more files

sometimes remain in the installation directory. (For example, these files mightbe files that someone manually put into the directory, such as mapping files orschema files that the user imported, or they might be log files that IntegrationComposer created.) You can delete these files manually.

Uninstalling Integration Composer on UNIX operating systemsUNIX Use the procedure described here to remove Integration Composer from

a UNIX-based operating system.

Procedure1. Go to the uninstall folder, itic_install_dir\Uninstall_Integration_Composer,

where Integration Composer 7.5.1 was installed.2. In the uninstall folder, do one of the following options:

v If you installed the Integration Composer using the X Window Systemapplication, type:sh ./Uninstall_IBM_Tivoli_Integration_Composer

v If you installed the Integration Composer using console mode, type:sh ./Uninstall_IBM_Tivoli_Integration_Composer -i console

The instructions that follow describe the remaining uninstallation steps usingconsole mode.

3. Press Enter to initiate the command from the previous step. The Uninstallingprogress bar is displayed as the uninstall utility removes the application.When the removal of Integration Composer is finished, you are returned to thecommand prompt.

4. Optional: After the utility removes Integration Composer, one or more filessometimes remain in the installation directory. (For example, these files mightbe files that someone manually put into the directory, such as mapping files orschema files that the user imported, or they might be log files that IntegrationComposer created.) You can delete these files manually.



Chapter 9. Installing the Deployer's Workbench

The Deployer's Workbench is a separately installed, Eclipse-based workbench thatis the best-practice tool for creating authorized CI spaces. Install it on a Windowsworkstation that can connect to your SmartCloud Control Desk server.

About this task

If you are installing the Entry edition of SmartCloud Control Desk, you do notneed to install the Deployer's Workbench.

You can install the Deployer's Workbench using either the SmartCloud ControlDesk launchpad or the native installer. In either case, the DVD1 image or physicalDVD must be accessible from the workstation where you want to install theDeployer's Workbench.

Procedure1. Start the Deployer's Workbench installer. Either start the SmartCloud Control

Desk launchpad, click Install the Product, and click Install Deployer'sWorkbench, or to use the native installer, cd to the DW directory and runinstall.exe.

2. You might see a message saying that Install Anywhere is preparing to install.When the Deployer's Workbench screen appears, choose a language from thedrop-down list and click OK.

3. Review the information on the Introduction screen. Click Next to continue.4. Choose the installation folder and where to install icons.5. Review the pre-installation summary. Click Previous to make any changes.

Click Install to begin the installation.6. You will see a progress bar indicating the progress of the installation procedure.

After the installation has completed, click Done to exit the installer.



Chapter 10. Installing IBM SmartCloud Control DeskEveryplace

Use the information in this section to install the optional component IBMSmartCloud Control Desk Everyplace®.

IBM SmartCloud Control Desk Everyplace comes with its own launchpad, whichyou can use to install it on the same administrative workstation where youinstalled SmartCloud Control Desk. The installation process does not create a newEAR file; it updates the maximo.ear file, which you must then rebuild andredeploy. The installation process does not update the maximoiehs.ear file, so youdo not need to rebuild and redeploy this file. The installation procedure dependson your scenario. Choose the link that matches your situation.

Installing as part of a new product installationFollow these steps if you are installing IBM SmartCloud Control Desk Everyplaceas part of a fresh installation of SmartCloud Control Desk.

About this task

When you begin the installation of SmartCloud Control Desk, be sure to defer theupdate of the database and the deployment of the ear file. You must completethese steps after running the SmartCloud Control Desk installer and beforeupdating the database.

Procedure1. Insert the IBM SmartCloud Control Desk Everyplace installation DVD or link to

the installable image.2. Issue the command to start the launchpad that is appropriate for your

administrative workstation:

launchpad.exeUse this command for 32-bit Windows workstations.

launchpad64.exeUse this command for 64-bit Windows workstations.

launchpad.shUse this command for workstations running other operating systems.

3. To install IBM SmartCloud Control Desk Everyplace, open the Install Productpage and click the link to start the installer.

4. As you run the installer, be sure to choose Deploy application files manuallylater and Defer the update of the Maximo database. This causes the IBMSmartCloud Control Desk Everyplace code to be added to the SmartCloudControl Desk files whose installation will be completed in subsequent steps.

5. When the installation is complete, in the Package Successfully Deployedwindow, click Done.

What to do next

After you have installed IBM SmartCloud Control Desk Everyplace, you mustreturn to the product installer to complete the installation of all components, the


updating of the database, and the building and deployment of the EAR file.

Installing as part of a product upgradeIf you are installing IBM SmartCloud Control Desk Everyplace as part of anupgrade to SmartCloud Control Desk, follow the steps in the Upgrade Guide.

About this task

The Upgrade guide includes information on installing IBM SmartCloud ControlDesk Everyplace as part of an upgrade. You can find the Upgrade Guide on theInstalling, Migrating and Upgrading page of the SmartCloud Control Desk wiki.

Installing after SmartCloud Control Desk has been installedFollow these steps if you are installing IBM SmartCloud Control Desk Everyplaceafter you have completed the installation of SmartCloud Control Desk.

About this task

You can install IBM SmartCloud Control Desk Everyplace as an addition to anexisting installation of SmartCloud Control Desk.

The following procedure assumes that you want to minimize the time for whichyour J2EE server is down.

Procedure1. Insert the IBM SmartCloud Control Desk Everyplace installation DVD or link to

the installable image.2. Issue the command to start the launchpad that is appropriate for your

administrative workstation:

launchpad.exeUse this command for 32-bit Windows workstations.

launchpad64.exeUse this command for 64-bit Windows workstations.

launchpad.shUse this command for workstations running other operating systems.

3. To install IBM SmartCloud Control Desk Everyplace, open the Install Productpage and click the link to start the installer.

4. Select the installation path for SmartCloud Control Desk from the drop-downmenu.

5. Do not choose Deploy application files manually later or Defer the update ofthe Maximo database. Instead, allow the installer to complete all steps.

6. When the installation is complete, in the Package Successfully Deployedwindow, click Done.


https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20SmartCloud%20Control%20Desk/page/Installing%2C%20Migrating%20and%20Upgrading

Chapter 11. Post installation tasks

There are several post installation tasks required in order to complete theSmartCloud Control Desk deployment.

Accessing product documentationAccessing the SmartCloud Control Desk information center documentation andproduct online help.

If you manually configured the application server after you ran the productinstallation program, you must set the property for the product documentationserver. For more information, see https://www.ibm.com/support/docview.wss?uid=swg21508594.

Initial data configuration

After you have successfully installed and configured SmartCloud Control Deskcomponents, there are several data configuration tasks you must complete beforeusing SmartCloud Control Desk.

Signing in using a default user IDUser management can be managed through the Maximo application or though thedirectory server you have configured to use with SmartCloud Control Desk

Before you begin

When first installed, SmartCloud Control Desk contains the following default userIDs:

Table 17. SmartCloud Control Desk users

User

maxadmin

mxintadm

maxreg

Important: Before you begin this procedure, if you are using a directory server aspart of your deployment, ensure that these users are created in your LDAPrepository.

Note: User names and passwords are case-sensitive. The defaultuser names arelowercase.

About this task

To sign in, complete the following steps:

Procedure1. Open a browser window.


https://www.ibm.com/support/docview.wss?uid=swg21508594

https://www.ibm.com/support/docview.wss?uid=swg21508594

2. Navigate to the SmartCloud Control Desk login URL. For example: http://hostname:port/maximo.

3. Enter the user name maxadmin (lower case).4. Enter the password you entered during the installation, and click Enter. The

default start center for maxadmin is displayed.

Configuring SMTPInstallation panels provide an opportunity to configure an SMTP server to send anadministrator, or other users, e-mail notifications of system events. If you skipthese panels when you install SmartCloud Control Desk, you can use theSmartCloud Control Desk interface to configure SMTP parameters.

Before you begin

This task must be completed before you apply changes to the database.

About this task

To configure SMTP for SmartCloud Control Desk, complete the following steps.

Procedure1. Log in to the console as maxadmin.2. Open the System Configuration > Platform Configuration > System

Properties application.3. Using the Filter feature, search for the mail.smtp.host Property Name.4. Expand the mail.smtp.host property and set the Global Value attribute to

your SMTP host.5. Select the mail.smtp.host record check box.6. Click the Live Refresh icon in the toolbar.7. From the Live Refresh dialog, click OK.8. Using the Filter feature, search for the mxe.adminEmail Property Name.9. Expand the mxe.adminEmail property and set the Global Value attribute to

your e-mail address.10. Select the mxe.adminEmail record check box.11. Click the Live Refresh icon in the toolbar.12. From the Live Refresh dialog, click OK.

“Applying changes to the database” on page 156When you create a general ledger account component, it must be applied to theMaximo database.

Create currency codesYou must define a currency code for an organization.

About this task

To define a currency code for an organization, complete the following steps.

Procedure1. Open the Financial > Currency Code application.2. Click New Row.


3. Enter a currency name. For example, USD.4. Click the Save icon.

Create item and company setsYou must define item and company sets for an organization.

About this task

To define item and company sets for an organization, complete the following steps:

Procedure1. Open the Administration > Sets application.2. Click New Row.3. Enter an item name. For example, IT Items.4. Enter ITEM in the Type field.5. Click New Row.6. Enter a company set name. For example, IT Comps.7. Enter COMPANY in the Type field.8. Click the Save icon.

Create an organizationYou must define at least one organization for SmartCloud Control Desk.

About this task

To define an organization, complete the following steps.

Procedure1. Open the Administration > Organizations application.2. Click the New Organization icon in the toolbar.3. Enter an organization name in the Organization field. For example, ENGLENA.4. Enter the base currency you defined in the Base Currency 1 field. For

example, USD.5. Enter the item set you defined in the Item Set field. For example, IT Items.6. Enter the company set you defined in the Company Set field. For example,

IT Comps.7. Enter the default item status of PENDING in the Default Item Status field.8. Click theSites tab.9. Click New Row.

10. Enter a site name in the Site field. For example, B901.11. Click the Save icon.

Create a general ledger account componentYou must create a general ledger account component for SmartCloud Control Desk.

About this task

To create a general ledger account component, complete the following steps.

Chapter 11. Post installation tasks 155

Procedure1. Open the System Configuration > Platform Configuration > Database

Configuration application.2. Choose the GL Account Configuration action.3. Click New Row.4. Enter a component name in the Component field. For example, MYCOMPONENT.5. Enter a numeric length for the component. For example, 5.6. Enter a type for the component. For example, ALN.7. Click OK.

Applying changes to the databaseWhen you create a general ledger account component, it must be applied to theMaximo database.

About this task

To apply configuration changes to the Maximo database, complete the followingsteps.

Procedure1. Log in to the Maximo console as maxadmin2. Open the System Configuration > Platform Configuration > Database

Configuration application. Every object that must be updated in the Maximodatabase has a status of To Be Added.

3. Choose the Manage Admin Mode action.4. Click Turn Admin Mode ON, and then click OK when prompted. This task

takes several minutes to complete. You can use the Refresh Status button toview progress.

5. After Admin Mode has been enabled, select Apply Configuration Changes, toapply the changes to the Maximo database. To Be Changed must not appear inthe status column for objects listed.

6. Turn Admin Mode OFF.a. Open the System Configuration > Platform Configuration > Database

Configuration application.b. Choose the Manage Admin Mode action.c. Click Turn Admin Mode OFF, and then click OK when prompted. Failing

to turn off Admin Mode within the application causes cron tasks to fail.

Create a general ledger accountYou must create a general ledger account for SmartCloud Control Desk.

About this task

To create a general ledger account, complete the following steps:

Procedure1. Open the Financial > Chart of Accounts application.2. Click the name of your organization to select it. For example, click

ENGLENA.3. Choose the GL Component Maintenance action.


4. Click New Row.5. Add a GL Component value and a description and then click OK. For

example, 1234.6. Click New Row.7. Select your General Ledger Account.8. Click Save.9. Open the Goto > Administration > Organizations application.

10. Click the organization name you created. For example, ENGLENA.11. From the Clearing Account field, select the General Ledger Account you just

created.12. Select Active.13. Click the Save icon.

Update General Ledger Component Type AuthorizationYou must update the general ledger component type authorization for SmartCloudControl Desk.

About this task

To authorize a Security Group to change a general ledge component type, completethe following steps:

Procedure1. Open the Security > Security Groups application.2. Select the Group that provides authorization (for example, PMSCOA).3. Click the GL Components tab.4. Click the Authorized check box for each GL Component.5. Click Save

Update Company-Related AccountsYou must update the company-related accounts for SmartCloud Control Desk.

About this task

To update the company-related accounts, complete the following steps:

Procedure1. Open the Financials > Chart of Accounts application.2. From the action menu, select Company-Related Accounts.3. On the dialog click New Row.4. Select company type 'C'.5. Set the RBNI Account, AP Suspense Account, and AP Control Account to the

components you created.6. Click OK.7. From the action menu, select Update Database.8. Click OK.

Create default insert siteYou must create a default insert site for SmartCloud Control Desk.


About this task

To create a default insert site, complete the following steps.

If you encounter an error message that indicates that the record is being updatedby another user, log out as maxadmin and then log back in.

Procedure1. Open the Security > Users application.2. Search for maxadmin and then select it to open the record for maxadmin.3. Enter the site you created earlier in the Default Insert Site field. For example,

B901.4. Enter the site you created earlier in the Storeroom Site for Self-Service

Requisitions field. For example, B901.5. Click Save.

Create worktypesYou must create worktypes for SmartCloud Control Desk.

About this task

To create a worktype, complete the following steps.

Procedure1. Open the Administration > Organizations application.2. Search for the organization you created. For example, ENGLENA.3. Click the name of the organization to open the record for that organization.4. Select Work Order Options > Work Type from the Select Action menu.5. Click New Row.6. Select PMCFGWO as the Work Order class.7. Set the Work Type as AR.8. Set Start Status as INPRG.9. Set Complete Status as COMP.

10. Click New Row.11. Select PMCFGWO as the Work Order class.12. Set the Work Type as UR.13. Set Start Status as INPRG.14. Set Complete Status as COMP.15. Click OK.16. Click Save.17. Restart the MXServer application server.

Create a classification structure for IT assetsBefore you can implement IT asset management, you need to define a classificationstructure for IT assets.


About this task

You can use the Classifications application to set up a nested, hierarchical structurein which to classify information about your company's assets. This structure letsyou group assets with similar or common characteristics into categories or classes.You can use the classification to retrieve instances of assets that belong to the class.For example, you can specify that the class computers has the following subclasses:notebooks, servers, desktops. If you want to analyze or review data about allnotebooks in your enterprise, you can search for all assets classified as notebooksand retrieve instances of notebooks.

Best practices content for creating classifications is provided in the Open ProcessAutomation Library.

The steps for creating classifications follow.

Procedure1. On the navigation bar in SmartCloud Control Desk, open the Administration >

Classifications application.2. In the Classifications application, create classifications as needed. For

instructions about creating classifications and other information related toclassifications, see the integrated online help for the Classifications applicationin the SmartCloud Control Desk user interface.

What to do next

After you create an IT asset classification structure, specify the top-level IT assetclassification and the top-level software classification in the Organizationsapplication.

Specify a top-level class for IT assets and softwareTo distinguish IT assets from other types of assets, specify a top-level class for ITassets. Any asset that belongs to the hierarchy of the top-level IT asset class is anIT asset. Also, define a top-level class for software.

Before you begin

Before you can specify top-level classifications for IT assets and software, create aclassification structure for IT assets and software in the Classifications application.

About this task

The class structure ID that is displayed in the System Settings window is a valuestored in the database. If the classifications structure changes such that thetop-level IT asset class no longer exists at the same place in the hierarchy, the ITAsset Class Structure ID field will remain populated, but the IT Asset Top-LevelClass field will be blank or show the wrong class. Consequently, if changes aremade to the database, and the classification is moved within the classificationstructure, or deleted and re-added, repeat this procedure to update the classstructure ID.

Procedure1. Open the Administration > Organizations application.


2. From the Select Action menu in the Organizations application, select SystemSettings.

3. To specify the top-level IT asset, complete the following steps:a. In the IT Options section in the Systems Settings window, in the IT Asset

Top-Level Class field, click the Detail Menu and select Classify. Ifnecessary, you can select Clear Classification to clear the value displayedand then click Classify.

b. In the Classify window, select the top-level asset class for IT assets byclicking the blue square to the left of the classification name. Theapplication closes the Classify dialog box and populates the IT AssetTop-Level Class field.

4. To specify the top-level software classification, complete the following steps:a. In the IT Options section in the Systems Settings window, in the IT

Software Top-Level Class field, click the Detail Menu and select Classify.b. In the Classify window, select the top-level asset class for IT assets by

clicking the blue square to the left of the classification name. Theapplication closes the Classify dialog box and populates the IT SoftwareTop-Level Class field.

5. Click OK to save the settings and close the dialog box.

Signing out and signing inWhen you change a security group that includes your user ID, you must sign outand sign in to see the changes. For example, even though you have granted agroup permission to create start center templates, the actions are not visible untilyou sign in again.

Procedure1. Sign out.2. Sign in as the same user.

Generating xml request pagesPerform this task after you install SmartCloud Control Desk and before you runrequest pages. This procedure needs to be performed for every language that isenabled on your system.

Before you begin

When multiple languages are enabled in Maximo applications, request pages haveto be generated in each of the enabled languages.

Procedure1. Log in as a maxadmin user.2. From the Start menu, go to Administrator > Reporting > Report

Administration.3. Review all rows in the list view then in the bottom right corner click Generate

Request Page button. Wait a couple of minutes for the process to complete.


Synchronizing users and groupsWhen you select application server security, the scheduled synchronization of usersand groups that occurs between LDAP repositories and SmartCloud Control Deskis governed by the federated repositories.

About this task

LDAP repositories are synchronized with Oracle WebLogic Server using the LDAPcron task.

To configure the synchronization schedule between LDAP repositories andSmartCloud Control Desk, complete the following steps:

Procedure1. Open a web browser and point to http://host name:port/maximo.2. Log in to SmartCloud Control Desk using the maxadmin user ID.3. From the SmartCloud Control Desk interface, open the System Configuration >

Platform Configuration > Cron Task Setup application.4. Search for the appropriate cron task in the Cron Task field and configure it.5. Set the task to active.

What to do next

By default, the cron task performs its task every 5 minutes. Change the Schedulefield of the cron task if you want to change the interval.

Understanding and configuring securityYou must configure security to ensure that only authorized users can log on toSmartCloud Control Desk. You must also ensure that the appropriate users haveaccess to their applications and configuration items.

The Security information contained in the SmartCloud Control Desk informationcenter provides an overview of the following information:v How security is implemented.v The steps you perform to configure security.



Chapter 12. Middleware clean up scripts

Middleware clean up scripts are available to remove middleware components andobjects installed and created by the middleware installation program.

Middleware clean up scripts are provided to clean up components that wereinstalled on a system by the middleware installation program. These scripts can beused after experiencing a middleware installation program failure, as well assuccessful install. These scripts work with the middleware installation programuninstall feature and are capable of removing one or more middleware installationcomponents. These components include middleware installed, the workspace,installation directories, and users created by the middleware installation program.

Using the middleware cleanup scriptsMiddleware clean up scripts can be used to remove all artifacts and componentsinstalled on a system by the middleware installation program.

About this task

When using the middleware cleanup scripts, you are prompted to confirm that youwant to remove the component specified. A timestamped log file is created in theworking directory for each action. If the script detects that the installation of acomponent experienced an error, you might have to uninstall that productmanually by using the uninstallation program provided with that program.

Table 18. Middleware clean up script parameters

Parameter Description

-default This is the default option for cleaning upobjects created by the middlewareinstallation program. This option removesany middleware that was installed, theworkspace, and the deployment engine.

This option does not remove users andgroups created by the middlewareinstallation program.

-workspace This option reads the middlewareinstallation program workspace. Thedeployment plan contained in the workspaceserves as a roadmap for the clean up script.

-all This option removes all components andobjects from the system that were installedand created by the middleware installationprogram.

This option also removes middleware usersand groups. This is true for users andgroups created by the middlewareinstallation program and also users andgroups created manually that were used forconfiguration during use of the middlewareinstallation program.


Table 18. Middleware clean up script parameters (continued)

Parameter Description

-mw This option refers to the middlewareinstallation program workspace for objectsto remove.

You must provide extra confirmations toremove users, groups, and DB2 instances.

-db2 This option removes DB2. All DB2 instancesare dropped, the DB2 server is stopped, DB2is uninstalled, and the DB2 installationdirectories are removed.

-itds This option removes IBM Tivoli DirectoryServer. All IBM Tivoli Directory Serverinstances are dropped, the IBM TivoliDirectory Server server is stopped, IBMTivoli Directory Server is uninstalled, andthe IBM Tivoli Directory Server installationdirectories are removed.

-deMWI This option removes the deployment engine.If there are entries in the deployment engineregistry that were not deployed by themiddleware installation program, you arewarned and asked to confirm that you stillwant to remove the deployment engine.

Once the deployment engine has beenremoved, you are given the option toremove the workspace.

-users This option removes users and groupscreated by the middleware installationprogram. It removes the default userscreated by the program and also promptsyou to enter additional user and groupnames associated with the middlewareinstallation that you want removed.

-prop This option allows you to use themwi.properties file to supply input to theclean up scripts.

-f This option allows you to skip confirmationby confirming all prompts y or n.

Procedure1. From the product installation image, change directory to the

MWICleanupScripts\operating_system directory.2. Start the clean up script and provide input parameters:

v Windowsmwiclean.bat

v Linux and UNIXmwiClean.sh

For example:mwiclean.bat -deMWI

3. Type y or n when prompted for confirmation.


4. When prompted, reboot the system. Rebooting the system removes thetemporary entries which can remain after the cleanup procedure has completed.

Chapter 12. Middleware clean up scripts 165


Chapter 13. Uninstalling the product

Uninstalling SmartCloud Control Desk 7.5.1 is dependant upon how it wasdeployed.

The procedures and instructions provided here are based upon a scenario in whichthe SmartCloud Control Desk installation program has experienced an error orfailure.

SmartCloud Control Desk uninstallation is a comprehensive procedure and doesnot support partial removal of individual components or process managers,including process managers deployed by other products. Process managers ofpreviously deployed products are also removed when you uninstall SmartCloudControl Desk.

The SmartCloud Control Desk uninstallation program can only be run once. Ifthere are errors, messages are generated that indicate conditions that you mustresolve manually before attempting a reinstall. Resolution includes manuallyremoving files from the administrative workstation.

SmartCloud Control Desk can only be uninstalled using the SmartCloud ControlDesk uninstallation program as directed. Do not use other methods to attempt touninstall SmartCloud Control Desk, such as using the Add/Remove Programspanel.

The uninstall procedure you follow depends on the type of SmartCloud ControlDesk deployment you are uninstalling. For uninstallation purposes, SmartCloudControl Desk deployments falls into one of the following categories:

Fully-automated configurationIn this scenario, you selected the option to allow the SmartCloud ControlDesk installation program to automatically configure middleware duringdeployment.

Manual configurationIn this scenario, you selected the option to manually configure middleware.You did not allow the SmartCloud Control Desk installation program toautomatically configure middleware during deployment.

After the SmartCloud Control Desk uninstall process is complete, you can reinstallSmartCloud Control Desk by restarting the SmartCloud Control Desk installationprogram.

“Uninstalling an automatically configured deployment”Uninstalling a SmartCloud Control Desk deployment that was deployed usingthe automatic middleware configuration options is an automated process.“Uninstalling a manually configured deployment” on page 169Uninstalling a SmartCloud Control Desk deployment that was deployed withmiddleware that you configured manually includes additional manual tasks.

Uninstalling an automatically configured deploymentUninstalling a SmartCloud Control Desk deployment that was deployed using theautomatic middleware configuration options is an automated process.


Deployments consisting of automatic middleware configuration can be uninstalledusing automated methods.

Running the product uninstallation program for automaticallyconfigured middleware

Running the SmartCloud Control Desk uninstallation program reverts theadministrative system and middleware servers back to their previous state.

Before you begin

Ensure that all applicable services are running and all middleware servers areaccessible.

The SmartCloud Control Desk uninstallation program must be able to access thedatabase used with SmartCloud Control Desk to fetch installation properties andconfiguration data. If the uninstallation program cannot access an unavailable,corrupted, or otherwise inaccessible database, it removes files from theadministrative workstation. It then informs you that some manual recovery mightbe required before another SmartCloud Control Desk installation can be successful.

The uninstallation program uses values entered during the initial installationduring uninstallation. If credentials used to access the database and J2EE server arestill valid, you are not prompted to enter them again. If the uninstallation programis unable to validate these credentials you are prompted to supply the updatedinformation. The uninstallation program would not be able to validate credentialsif you updated passwords since the original installation.

Procedure1. To run the SmartCloud Control Desk uninstallation program, from the

administrative workstation, open a command prompt and issue the followingcommand:v Windows

install_home\_uninstall\uninstall.bat

v UNIXinstall_home\_uninstall\uninstall.sh

2. From the application server information panel, enter the following informationand then click Next.

Remote user IDEnter a user ID in order to access the system hosting the applicationserver. The remote user ID must be able to access the server using theremote access protocol enabled on that system.

Remote passwordEnter a password for the remote user ID.

User IDEnter the password for the application server administrator.

PasswordEnter the password for the application server administrator user ID.

3. From the database administration panel, enter the information requested, andthen click Next. For DB2, enter the following information:

Remote user IDEnter a user ID in order to access the system that is hosting the


database. The remote user ID must be able to access the server usingthe remote access protocol enabled on that system.

Remote passwordEnter a password for the remote user ID.

Instance administrator user IDEnter the database instance administrator user ID that you enteredduring the installation.

Instance administrator passwordEnter the password for the database instance administrator user ID.

For Oracle, supply credentials for the Administrator user ID and the Oraclesoftware owner ID. For Microsoft SQL Server, supply the Microsoft SQL Serveradministrator user ID and password.

4. Review the components that are listed in the uninstallation summary panel,and then click Uninstall.

5. After the uninstallation process completes, specify whether you want to restartthe computer now or later, and click Done to exit the program.

6. Remove the SmartCloud Control Desk installation directory, for example,c:\ibm\smp. You must manually remove this directory before you proceed tothe reinstallation process.

Uninstalling a manually configured deploymentUninstalling a SmartCloud Control Desk deployment that was deployed withmiddleware that you configured manually includes additional manual tasks.

Uninstalling a manually configured SmartCloud Control Desk deployment consistsof two tasks:v Running the SmartCloud Control Desk uninstallation programv Manually dropping and recreating the database you intend to use with the

reinstall process

Running the product uninstall program for manuallyconfigured middleware

Running the SmartCloud Control Desk uninstall program reverts theadministrative system and middleware servers back to a state where you can rerunthe SmartCloud Control Desk installation program.

Before you begin

Ensure that all applicable services are running and all middleware servers areaccessible.

The SmartCloud Control Desk uninstall program must be able to access thedatabase used with SmartCloud Control Desk to fetch installation properties andconfiguration data. If the uninstall program cannot access an unavailable,corrupted, or otherwise inaccessible database, it removes files from theadministrative workstation. It then informs you that some manual recovery mightbe required before another SmartCloud Control Desk installation can be successful.

The uninstall program uses values entered during the initial installation duringuninstall. If credentials used to access the database and J2EE server are still valid,

Chapter 13. Uninstalling the product 169

you are not prompted to enter them again. If the uninstall program is unable tovalidate these credentials you are prompted to supply the updated information.The uninstall program would not be able to validate credentials if you updatedpasswords since the original installation.

Procedure1. To run the SmartCloud Control Desk uninstall program, from the

administrative workstation, open a command prompt and issue the followingcommand:

Windowsinstall_home\_uninstall\uninstall.bat

UNIXinstall_home\_uninstall\uninstall.sh

2. From the Introduction panel, read the introductory information and then clickNext.

3. From the application server information panel, enter the following informationand then click Next.

User IDEnter the password for the application server administrator.

PasswordEnter the password for the application server administrator user ID.

4. Review the components that are listed in the uninstall summary panel, andthen click Uninstall.

5. After the uninstall process has completed, click Done to exit the program.6. Remove the SmartCloud Control Desk installation directory, for example,

c:\ibm\smp. You must manually remove this directory before you proceed tothe reinstallation process.

What to do next

You can now proceed with recovery of your manually configured database.

Database configuration recoveryDatabase objects created before running the SmartCloud Control Desk installationprogram must be deleted after a failed installation before the SmartCloud ControlDesk installation program is run again.

Before rerunning the SmartCloud Control Desk installation program, you mustdrop the SmartCloud Control Desk database and recreate it.

Note: Alternatively, if you want to preserve the instance, you can examine thedatabase for objects (tables, views, and procedures, for example) that were createdby the maxadmin user. You can then drop those objects individually.

Restoring the DB2 database serverIn order to rerun the SmartCloud Control Desk installation program, you must firstrestore the DB2 database server to the same state as before SmartCloud ControlDesk was installed.


About this task

To restore the DB2 database server to its previous state, drop the SmartCloudControl Desk database that you manually created. You then recreate it before yourerun the SmartCloud Control Desk installation program.

To restore the SmartCloud Control Desk database, complete the following steps:

Procedure1. Log on to the system that hosts the DB2 server.2. Start a DB2 command session or run db2cmd from the command prompt.3. First list and then force all applications connected to the database to close using

the following commands:a. To list applications, type this command:

db2 list applications

You might see output like the following sample output:

Table 19. DB2 list command sample output

Auth IdApplicationName

Appl.Handle Application ID DB Name # of Agents

CTGINST1 db2taskd 507 *LOCAL.DB2.071113150237 MAXDB75 1

CTGINST1 db2stmm 506 *LOCAL.DB2.071113150236 MAXDB75 1

CTGINST1 db2bp 504 *LOCAL.ctginst1.071113150234 MAXDB75 1

b. If any connections exist, close the connect application using a command likethe following sample command:db2 force application ’( 507,506,504 )’

4. Drop the SmartCloud Control Desk database (MAXDB75, by default):db2 drop database MAXDB75

5. Manually recreate the maxdb75 database.“Manually configuring DB2 9.x” on page 70This section contains instructions for manually configuring DB2 9.x servers foruse by SmartCloud Control Desk.

Restoring the Oracle databaseIn order to rerun the SmartCloud Control Desk installation program, you must firstrestore the Oracle database server to the same state as before SmartCloud ControlDesk was installed.

Before you begin

The MXServer application server must be stopped before deleting the database.

About this task

Drop the SmartCloud Control Desk database schema user to restore the Oracledatabase server to its previous state. This task must be completed before you rerunthe SmartCloud Control Desk installation program.



Procedure1. Log in to the Oracle database server as the Oracle software owner.2. Log in to the Oracle instance with SQLPlus as a DBA user: The Oracle SID for

a clean installation is ctginst1. If you are using an existing Oracle instance withSmartCloud Control Desk, use the Oracle SID associated with the existinginstance.

AIX, Linux, HP-UX, Solaris

a. Set the environment variable from the command line:ORACLE_SID=<your sid>export ORACLE_SID

b. Start SQLPlus from the command line:sqlplus /nolog

c. Login to SQLPlus as a DBA user:connect sys/<sys password> as sysdba

Windows

a. Set the environment variable from the command line:set ORACLE_SID=<your sid>

b. Start SQLPlus from the command line:sqlplus /nolog

c. Login to SQLPlus as a DBA user:connect sys/<sys password> as sysdba

3. Delete the SmartCloud Control Desk database user (maximo, by default) usingan SQL command like the following sample command:drop user maximo cascade;

Do not disconnect from the database. If you receive an error that you cannotdrop a currently connected user, issue the following commands and use theSQL drop command:shutdown immediate;startup;

4. Manually recreate the database.“Manually configuring Oracle 11g” on page 71Use the following instructions to manually configure Oracle 11g for use withSmartCloud Control Desk.“Manually configuring Oracle 10g” on page 74Oracle 10g can be manually configured for use with SmartCloud Control Desk.

Restoring the Microsoft SQL Server databaseIn order to rerun the SmartCloud Control Desk installation program, you must firstrestore the Microsoft SQL Server database server to the same state as beforeSmartCloud Control Desk was installed.

Before you begin

Stop the MXServer application server before you delete the database.

About this task

To restore the Microsoft SQL Server database server to its previous state, drop theSmartCloud Control Desk database that you manually created. You then recreate itbefore you rerun the SmartCloud Control Desk installation program.



Procedure1. Open the Microsoft SQL Server Management Studio.2. Log in to the instance of Microsoft SQL Server that is used by SmartCloud

Control Desk installation using the sa user ID, and then click Connect.3. Expand the instance tree down to the databases node. Using the right mouse

button, click the database name you created during installation (MAXDB75 forexample). Click Delete to delete the database.

4. In the Delete Object window, select Delete backup and restore historyinformation for databases and Close existing connections, and then click OK.

5. Manually recreate the maxdb75 database.“Manually configuring Microsoft SQL Server” on page 76You can manually configure Microsoft SQL Server for use with SmartCloudControl Desk.

Uninstalling the product without the uninstallation programUninstalling the product when a failed installation does not produce anuninstallation program.

If the installation program has experienced a failure that causes it to not producethe product uninstallation program, you must perform alternative uninstallationtasks.

If uninstallation program was not produced, you must complete one of thefollowing tasks in order to uninstall the product:v Run the uninstallation recovery tool described in “Uninstall program recovery

tool.”v Complete the uninstallation manually using the following steps:

1. Recover the database as described in “Database configuration recovery” onpage 170.

2. Manually remove files from the system as described in “Removing files fromthe system” on page 175.

Uninstall program recovery toolThe uninstall program recovery tool is used to automatically uninstall SmartCloudControl Desk when the installation program fails to produce the productuninstallation program.

The uninstall program recovery tool is run on the administrative workstationfollowing a failed installation. This tool performs the same functions of theSmartCloud Control Desk uninstallation program. This tool is intended to restorethe administrative workstation and middleware servers so the SmartCloud ControlDesk installation can be run again. The uninstall program recovery tool isavailable on the product media and also from the product support site.

Using the uninstallation program recovery toolUse the uninstallation program recovery tool to restore the administrativeworkstation and middleware servers so the SmartCloud Control Desk installationcan be run again.


About this task

The uninstallation program recovery tool is a command line tool that prompts youfor input. This information is used as input for a collection of scripts that are runserially. These scripts perform the steps necessary to restore the administrativeworkstation and middleware servers so the installation program can be rerun. Ifyou choose to skip any of the uninstallation program recovery tool tasks, you canrun the tool at a later time to perform that task.

The uninstallation program recovery tool must be run on each system that hosts acomponent of the SmartCloud Control Desk deployment. For example, to removethe database associated with the deployment, you must run the program on theserver hosting the database.

Procedure1. Open a command prompt on the administrative workstation and start the

uninstallation program recovery tool.v For Windows, use cleanupPAE.bat.v For UNIX, use cleanupPAE.sh.

2. Provide input for the scripts responsible for recovering the database serverused in the deployment.v DB2

a. Supply information for the database used in the deployment.1) At the Would you like to cleanup the database? [y/n]: prompt,

select y.2) At the Which database type would you like to cleanup? [DB2,

Oracle, SQLServer (BAT only)]: prompt, select DB2.3) At the Enter database name: prompt, enter the name of the database

used in the deployment.4) At the Enter database instance administrator user ID: prompt,

enter the database instance administrator user ID.5) At the Enter database instance administrator password: prompt,

enter the password for the database instance administrator user ID.6) At the Enter database instance name: prompt, enter the name of the

database instance.b. Confirm you want to drop the database.

1) At the Are you sure you would like to drop the <database name>database? [y/n]: prompt, select y.

2) Verify the database was dropped.v Oracle

a. Supply information for the database used in the deployment.1) At the Would you like to cleanup the database? [y/n]: prompt,

select y.2) At the Which database type would you like to cleanup? [DB2,

Oracle, SQLServer (BAT only)]: prompt, select Oracle.3) At the Enter the SID of the Oracle instance: prompt, enter the

Oracle System ID of the Oracle instance used in the deployment.4) At the Enter the Oracle install directory: prompt, enter the

Oracle installation path.b. Supply user information.


1) At the Enter the SYSDBA user: prompt, enter the SYSDBA user ID.2) At the Enter the SYSDBA password: prompt, enter the password for

the SYSDBA user ID.3) At the Enter database user: prompt, enter the Oracle database user

ID.4) At the Would you like to delete the <database user name>

database user? [y/n]: prompt, select y.c. Delete the Oracle table spaces and the Oracle instance.

1) At the Would you like to delete the 'maxdata', 'maxtemp', and'maxindex' tablespaces? [y/n]: prompt, select y.

2) At the Would you like to delete the oracle instance? [y/n]:prompt, select y.

v Microsoft SQL Servera. At the Enter database name: prompt, enter the name of the database

used in the deployment.b. At the Are you sure you would like to drop the <database name>

database? [y/n]: prompt, select y.3. Provide input for the scripts responsible for recovering the administrative

workstation used in the deployment.a. At the Would you like to cleanup the administrator workstation?

[y/n]: prompt, select y.b. At the Would you like to enter a custom install directory? [y/n]:

prompt, select n if you installed SmartCloud Control Desk in the defaultdirectory. If you installed SmartCloud Control Desk in a custom directory,you are prompted to enter that directory.

c. At the Are you sure you would like to cleanup the following directory:<install directory>? [y/n]: prompt, select y.

Manual uninstallationManual uninstallation steps are sometimes necessary to uninstall SmartCloudControl Desk when the installation program fails to produce the productuninstallation program.

Manual uninstallation steps are performed following a failed installation. Thesesteps are used to remove the same objects as the SmartCloud Control Deskuninstallation program. These steps are intended to restore the administrativeworkstation and middleware servers so the SmartCloud Control Desk installationcan be run again.

Removing files from the systemIf an uninstallation program is unavailable due to failed installation, product filesmust be manually removed from the system.

About this task

Remove files from the system by completing the following steps:

Procedure1. Ensure that you are logged in to the system with the same user ID used to start

the product installation program.


2. Manually delete the SmartCloud Control Desk home directory. For Windows,the default location of this directory is C:\IBM\SMP. For UNIX systems, thisdirectory is /opt/IBM/SMP.


Chapter 14. Starting and stopping middleware

Use this information to start and stop middleware when necessary.

There might be occasions when you have to stop or restart middleware.

Restarting middleware on WindowsThis procedure describes how to restart middleware on Windows, if you mustrestart any middleware services.

About this task

To properly start middleware products on Windows, use the following scripts inthe order in which they are listed:

Procedure1. Log in as a user with Administrative permissions.2. If you installed DB2, start ctginst1.

a. Click Start, and select Run.b. Type services.msc, and click OK.c. Select DB2 - DB2COPY1 - CTGINST1-0, and click Start the service.

Alternatively, you can use the db2start command from a command line to startCTGINST1.

3. If you installed IBM Tivoli Directory Server, start the IBM Tivoli DirectoryServer Admin Daemon.a. Click Start, and select Run.b. Type services.msc, and click OK.c. Select IBM Tivoli Directory Admin Daemon V6.3 - idsccmdb, and click Start

the service.

Alternatively, you can use the following command from the command line tostart the IBM Tivoli Directory Server admin daemon:idsdiradm -I idsccmdb

4. If you installed IBM Tivoli Directory Server, start the IBM Tivoli DirectoryServer instance.a. Click Start, and select Run.b. Type services.msc, and click OK.c. Select IBM Tivoli Directory Server Instance V6.3 - idsccmdb, and click

Start the service.

Alternatively, you can use the following command to start the IBM TivoliDirectory Server instance:idsslapd -I idsccmdb

Important: The IBM Tivoli Directory Server Instance must remain as a manualstartup type. It must be started manually to synchronize correctly with thedatabase in the context of SmartCloud Control Desk.


Restarting middleware on UNIXMiddleware services on Linux and AIX platforms occasionally must be restarted,such as when a reboot occurs. Middleware servers and services must be activebefore running the SmartCloud Control Desk installation program.

About this task

To properly start middleware products on UNIX, perform the following steps:

Procedure1. Log in as root.2. Start servers by using the following scripts in the order in which they are

listed:

If you installed DB2, start ctginst1 instancesu - ctginst1 -c db2start

If you installed IBM Tivoli Directory Server, start IBM Tivoli DirectoryServer Admin Daemon

<ITDS_HOME>/sbin/idsdiradm -I idsccmdb

If you installed IBM Tivoli Directory Server, start IBM Tivoli DirectoryServer daemon

<ITDS_HOME>/sbin/idsslapd -I <instancename>

So this command would look like the following example:<ITDS_HOME>/sbin/idsslapd -I idsccmdb

Important: The instance of IBM Tivoli Directory Server must remain asa manual startup type. It must be started manually to synchronizecorrectly with the database in the context of SmartCloud Control Desk.


Chapter 15. Process solution package installation methods

Included within SmartCloud Control Desk are common installation programs thatprovide you with the ability to manage the software life cycle of SmartCloudControl Desk process solutions, including functions to query, install, upgrade, anduninstall process solution packages. These common installation programs arecollectively known as the process solution installation programs.

SmartCloud Control Desk provides a flexible approach for incremental deploymentof service management functionality using separately packaged process solutions.Process solutions can be partitioned into Process Manager Products and IntegrationModules.

Process solution packages can be installed and deployed using two mechanisms:

Process Solution Installation WizardThe process solution installation wizard provides you with an interface forinstalling process solution packages.

Process Solution Command Line InterfaceThe process solution command-line interface allows you to install processsolution packages from a command line.

SmartCloud Control Desk must have been deployed, including post-installationsteps, before the installation and deployment of additional process managers.

Software life cycle operationsProcess solutions are software components with versions. The process solutioninstallation programs support various software life cycle operations that can beapplied against process solutions.

The following software life cycle operations are available:v The Base Install operation installs and deploys a new process solution into your

SmartCloud Control Desk environment.v The Add Feature and Modify Feature operations add or remove specific features of

a package after the package has been installed.v Once installed, a process solution can be updated in several ways. An

Incremental Update or Upgrade operation modifies the existing installed processsolution and changes its version. Often a process solution fix pack is appliedusing the Incremental Update operation.

v Another operation that can be used to update an installed process solution is theApply Fix operation. This operation is used to install individual interim fixes orpatches to a currently installed process solution.

v Some Incremental Updates or Fixes are designed to be able to be removed orbacked off. The Undo operation is used to remove the effects of an IncrementalUpdate operation and return the process solution to its previous version andstate. The Undo Fix operation removes a currently installed interim fix from aprocess solution.

v The Uninstall operation removes a currently installed process solution.


Process solution packagesA process solution package is a self-contained archive file of installation artifacts anddeployment logic that can be deployed using the process solution installationprograms.

Installation artifacts are the files and content that are installed into yourSmartCloud Control Desk environment. These artifacts enable the servicesmanagement functionality of the Process Manager Product or Integration Module.For example, a Process Manager Product provides J2EE application content anddatabase content.

The deployment logic consists of the actions that are carried out in order to deploythe process solution into the SmartCloud Control Desk environment. These actionsinclude building J2EE applications, running database scripts that load the processsolution content into the database, and adding users and groups for security.Additionally, optional sample data can be installed.

SmartCloud Control Desk packages are automatically installed when SmartCloudControl Desk is installed.

Package typesClosely related to the concept of the software life cycle operation is softwarepackage type.

The process solution installation programs are able to process the followingpackage types:v A Base Install Package is required to install a new process solution using the Base

Install operation.v An Incremental Update Package is required when performing an Upgrade

operation.v A Fix Package is required when applying an interim fix to a process solution.v A Full Update Package can be used in two separate operations. It can be used to

perform a Base Install operation if no instance of the process solution iscurrently installed or it can be used to perform an Upgrade operation on acurrently installed process solution.

v An Aggregation package consist of multiple PSI installable packages that can bedeployed as one package in a single process solution installation client CLI orinterface session.

The process solution installation programs ensure that the appropriate packagetype is processed for any given operation.

The Process Solution Command Line Interface issues appropriate messages whenan inappropriate package type is specified for a life cycle operation. For example, amessage would be issued if a Fix Package was specified for a Base Installoperation. You can use the showavail action of the Process Solution Command LineInterface to determine the package type associated with a process solutioninstallable package.

The Process Solution Installation Wizard determines the operation to employ basedon the type of the package and the current state of the installed components. Forexample, if you select to deploy a Full Update Package, the Process SolutionInstallation Wizard performs an Upgrade operation if a suitable base version of the


process solution is already installed and a Base Install operation if no suitable baseversion is detected. When using the Process Solution Installation Wizard, you canview the package type for the package you selected on the Package ValidationResults panel.

The following table highlights the supported operations with their requiredpackage types:

Table 20. Operations and package types

Operation Package Type

Base Install Base Install Package or Full Update Package

Incremental Update/Fix Pack Incremental Update Package or Full UpdatePackage

Apply Interim Fix Fix Package

Aggregation packagesThis section contains information about aggregation packages.

A process solution package can be composed from other process solution packages.This technique allows construction of single offering-level packages that may bedeployed using a single session with the process solution installation programs.Such a package is known as a process solution aggregate package. The subpackages that are bundled within a process solution aggregate package are knownas child packages.

Process solution aggregate packages are deployed using the same mechanismsused to deploy non-aggregate packages. All actions defined within the processsolution command-line interface can be applied to a process solution aggregatepackage. Similarly, the process solution installation wizard can be used to baseinstall, upgrade, and apply fixes to a process solution aggregate package.

Process solution aggregate packages support the same package types (Base Install,Full Update, Incremental Update, and Fix) and the same life cycle operations asnon-aggregate packages.

Process solution aggregate packages often expose their child packages as selectablefeatures of the aggregate. You can selectively deploy only the pieces of theaggregate that you prefer.

A process solution aggregate has a version, unique identifier, and display nameinformation just like a non-aggregate package. When you use the showinstalledaction of the process solution command-line interface, the output includesinformation about the installed parent aggregate package. Out also containsinformation about the child packages within that parent aggregate package thathave also been installed.

Determining which process solution installation program to useThe process solution installation programs provided each have unique benefits andboth must be used in the appropriate scenario.

Consider the following facts when deciding which process solution installationprogram to use.

Chapter 15. Process solution package installation methods 181

v The Process Solution Installation wizard provides a user experience typical ofmost software installation programs. You select the process solution package toinstall and provide additional installation options from wizard panels. TheProcess Solution Installation wizard is an attended installation.

v The Process Solution Command Line Interface provides a simple command-linesyntax for specifying the life cycle operation to perform and the package againstwhich the operation is performed. You enter the Process Solution CommandLine Interface command and messages and command output are displayed tothe command line as the command is processed.

v All functions and operations are available in the Process Solution CommandLine Interface program. Only a subset of those functions is supported in theProcess Solution Installation Wizard. Generally, use the Process SolutionInstallation wizard if it supports the operation you must perform.

v The Process Solution Installation Command Line Interface is useful where yourequire an unattended or silent installation. The Process Solution InstallationCommand Line Interface passes return codes detailing the success of thecommand back to the operating system. The Process Solution InstallationCommand Line Interface is suitable for use in a higher-level deploymentautomation package or script.

Supported operations for the process solution installation programsThere are multiple operations and functions that are supported by the ProcessSolution Installation wizard and Process Solution Command Line Interface.

The following table highlights the operations and functions that are supported bythe Process Solution Installation wizard and Process Solution Command LineInterface.

Table 21. Process solution operations

OperationSupported by CommandLine Interface

Supported by Installationwizard

List Installed Packages Yes No

List Available Packages Yes No

Base Installation Yes Yes

Incremental Update/Fix Pack Yes Yes

Full Update Yes Yes

Undo IncrementalUpdate/Fix Pack

Yes No

Uninstall Yes No

Apply interim fix Yes Yes

Undo interim fix Yes No

List Installed Fixes for aPackage

Yes No

Refresh language support Yes No

Load Language Support Files Yes Yes

Add Features Yes Yes

Remove Features Yes Yes

Show Available Features Yes Yes


Note: The process solution installation programs allow an uninstall action to beinitiated against a package. However, not all packages support the uninstallaction. If an uninstall action is initiated against a package that does not supportthis action, a message detailing this condition is shown. If you want to restore yourenvironment to the state before the installation of the SmartCloud Control Deskprocess managers, you must back up your affected middleware servers beforerunning the SmartCloud Control Desk installation program.

Before using the process solution installation programsReview the following prerequisite information before using process solutioninstallation programs.

When you perform a deployment operation using the process solution installationprograms, you are running actions that modify the configuration and content ofyour J2EE, database, and directory middleware servers. Review the following stepsbefore starting the process solution installation programs.

Have Middleware Login Information AvailableThe process solution installation programs require access to middlewareservers in order to automate the deployment of the process solutionpackage. You must know the administrative user IDs and passwords forthe affected middleware servers. The actual middleware servers whoselogin information is required depends on the process solution packagebeing installed. The process solution installation programs ensure that anyrequired login information is specified before continuing with thedeployment operation.

Backup Middleware Servers and Administrative WorkstationYou should create backups for affected J2EE, database, and directoryservers before you deploy a process solution package using the processsolution installation programs. Backup the installation folder of theadministrative workstation, C:\IBM\SMP, for example. Also, backup thedeployment engine registry.

Ensure Middleware Servers Are StartedStart any affected middleware servers before running the process solutioninstallation programs. Before the actions associated with a package arestarted, the process solution installation programs attempts to connect tothe middleware servers using the middleware login information that youspecify. If the targeted middleware servers are not started or if connectionsto the middleware servers cannot be established with the specifiedmiddleware login information, then the process solution installationprograms displays error messages and not continue on with thedeployment actions.

“Backing up the Deployment Engine database” on page 13These instructions are for backing up the Deployment Engine database.Backups are used to restore the database to the state it was before installing.

Managing process solution deployment from the administrativeworkstation

Process solution deployment is managed from the administrative workstation.


Process solution installation programs are installed on the administrativeworkstation when the SmartCloud Control Desk is installed. In addition to startingprocess solution installation programs from the administrative workstation, youmust also have access to any process solution packages from the administrativeworkstation.

The administrative workstation provides a deployment hub from which theprocess solution packages are deployed. In order to automate deployment, theprocess solution installation programs connects to either local or remotemiddleware servers from the administrative workstation

Typical deployment operationProcess solution deployment is integrated tightly with SmartCloud Control Deskdeployment

Process solutions use the SmartCloud Control Desk deployment model. In thismodel, as process solution packages are deployed, database content and metadatain the package is loaded into the Maximo database and the Maximo core J2EEapplications are redeployed with Java code provided in the process solutionpackage. This model effectively merges the features of the process solution packageinto the Maximo database and Maximo J2EE application.

High-level deployment steps are:1. Files in the process solution package are unpacked onto the Maximo

installation directory on the SmartCloud Control Desk administrativeworkstation. The Maximo installation directory contains the Maximo contentfor the process solution being deployed and any other currently installedSmartCloud Control Desk process solutions or Maximo applications andindustry solutions.

2. J2EE applications are rebuilt on the SmartCloud Control Desk administrativeworkstation to contain the features of the process solution package. This featureincludes Java classes, report definitions, and other artifacts.

3. Database content scripts associated with the package being installed areprocessed on the SmartCloud Control Desk administrative workstation. Thisresults in updates to the database.

Selectable featuresThis section contains information about managing selectable content using features.

A process solution package might define one or more features that representuser-selectable, optional content. Examples of typical features include globalizationand samples. Process solution installation methods support operations on features,including capabilities for querying, adding, and removing features.

Feature support in a process solution package is optional. Features are alsopackage-specific. The process solution installation methods examine the processsolution install package and ensure that only features defined within the packageare able to be manipulated.

Attributes of a Feature

Associated with every feature are the following attributes:


v Feature Identifier represents a non-localized name by which the feature isuniquely identified within its package. When using the process solutioncommand-line interface, the Feature Identifier is used to specify the feature toadd or remove.

v Feature Display Name is a localized label for the feature.v Parent Identifier identifies the parent feature associated with a feature. A feature

with no parent is termed a top-level feature.v Install State indicates whether the feature is installed.v Required Attribute indicates whether the feature is a required feature. A required

feature is a feature that must be installed if its parent feature is installed and cannot be installed if its parent feature is not installed. A top-level feature that isrequired is always installed.

Operations Associated with Features

Both the process solution command-line interface and process solution installationwizard provide features for managing features associated with a process installpackage. This section describes those capabilities.

Installing Features during a Base InstallIf a process solution package defines features, you can select the features toinstallation during the base installation of the package.

Installing Features Using the wizardFor the process solution installation wizard, a Feature SelectionPanel is displayed after license acceptance processing if thepackage being deployed supports features. The Feature SelectionPanel displays a tree where the nodes in the tree are features andthe tree nesting represents parent feature and child featurerelationships. Each node has a check box that indicates theselection state of the feature. You select a feature to be installed byselecting the check box for the feature.

Installing Features Using the Command Line InterfaceFor the process solution command-line interface, the -addfeatlistparameter on the install action allows you to specify the featuresto be installed during the base installation of the package. Thevalue specified for this parameter is a colon separated list ofFeature Identifiers representing the features to install.

Adding FeaturesAfter the base installation of a package, you can incrementally add featuresif there exists at least one feature not already installed for that package.

Adding Features Using the wizardWhen using the process solution installation wizard, if the packageis already installed but has at least one feature not alreadyinstalled, you can elect to install additional features after thePackage Validation Panel is displayed.

Note that the Deployment Engine does not support bothincremental feature add and removal in the same deploymentoperation. If the state of the installed features on a package is suchthat features can be both added or removed, then the Add orRemove Features Panel is displayed that allows you to selectwhether you want to add or remove features from the package.


If you select to install additional features from the Add or RemoveFeatures Panel, the Feature Selection Panel is again displayed withthe currently installed features checked and disabled. You cannotuninstall currently installed features in this mode, but you canselect additional features for installation.

Adding Features Using the Command Line InterfaceFor the process solution command-line interface, a newmodfeatures action allows you to install features to an alreadyinstalled process solution package. The parameters on this actionare like the install action. You specify the path of the processsolution package and required middleware user IDs andpasswords. The -addfeatlist parameter on the modfeatures actionallows you to specify the features to be added. The value specifiedfor this parameter is a colon separated list of Feature Identifiersrepresenting the features to be installed.

Removing FeaturesAfter the base installation of a package, you can incrementally remove oruninstall features if there exists at least one feature already installed forthat package.

Feature uninstallation is OptionalSupport for uninstallation of features is optional. A processsolution package that supports incremental feature installationmight not support uninstallation of its features. If the processsolution package does not support uninstallation of its features,then the process solution installation programs do not permit youto uninstall features on the package. The process solutioninstallation wizard does not allow you to initiate featureuninstallation operations against the package. The process solutioncommand-line interface will issue messages if uninstallationoperations are attempted against a package that does not supportfeature uninstallation.

Removing Features Using the wizardWhen using the process solution installation wizard, if the packageis already installed and has at least one feature already installed,you can elect to uninstall features after the Package ValidationPanel is displayed.

As described above, if the state of the installed features on apackage is such that features can be both added or removed, thenthe Add or Remove Features Panel is displayed that allows you toselect whether you want to add or remove features from thepackage.

If you select to uninstall currently installed features from the Addor Remove Features Panel, the Feature Selection Panel is againdisplayed with the currently installed features checked. You maynot install new features in this mode, but you can clear currentlyinstalled features to trigger the uninstallation operation againstthose features.

Removing Features Using the Command Line InterfaceFor the process solution command-line interface, the modfeaturesaction described above also allows you to uninstall features thatare already installed on a currently installed process solutionpackage. The -delfeatlist parameter on the modfeatures action


allows you to specify the features to be uninstalled. The valuespecified for this parameter is a colon separated list of FeatureIdentifiers representing the features to be uninstalled.

Showing Feature Information for a PackageThe process solution installation programs allow you to displayinformation about the supported and installed features for a processsolution package.

Showing Feature Information Using the WizardThe Feature Selection Panel of the process solution installationwizard displays the feature tree of a process solution package. Thispanel depicts the parent-child relationships between the featuresand also displays whether the features are currently installed.

Showing Feature Information Using the Command Line InterfaceFor the process solution command-line interface, the showfeaturesaction allows you to display information about the featuresassociated with a process solution package. Input to the action isthe path to the process solution package. The output lists thefeature attributes for the features defined for the package. Thoseattributes are detailed in “Attributes of a Feature” on page 184.

Feature Selection Processing Rules and Behavior

When using the process solution installation programs to manage the features, theactual collection of features to install or uninstall are derived using a combinationof the input selections/deselections you specify and a set of feature selectionsrules. For example, you can select a single feature for installation, but, due tofeature selection rule processing, additional features can also be installed.

When you install or uninstall features, the process solution installation programsenforce these feature selection rules to ensure that the derived set of featureselections are valid and meet all the feature selection rules.

This section highlights the feature selection rules that are enforced by the processsolution installation programs.

Summary of Feature Selection Rules

1. Features can be arranged in a parent-child tree structure. Child featurescannot be installed unless their parent feature is installed.

2. A feature can be marked as required which indicates that the featuremust be installed if its parent is installed. A top-level feature that ismarked required is always installed.

3. Features that are marked required can never be selected/deselectedexplicitly by you. The selection state of a required feature is alwaysderived from the selection state of their parent feature.

4. A feature can have real content (files/actions) or can be a nestingfeature which acts as a parent feature for other child features.

5. A Nesting Feature cannot be installed unless at least one of its childfeatures (with content) is also installed. This violation is detectedduring Feature Selection Validation. Message CTGIN0200E is issuedwhen this rule is violated.

6. Special select-if-selected rules can be coded into the package to assertprerequisite dependencies between features. These rules are specific to


a particular package. For example, select-if-selected rules can be definedin a package that ensures that Feature A is installed if Features B or Care installed.

Feature Selection Processing

1. When a child feature is selected, all its ancestor features (Parent,Grandparent, and so on) are selected as well.

2. When a parent feature is selected, any of its required child features areautomatically selected.

3. When a feature is selected, select-if-selected rules are evaluated and anydependent features are automatically selected.

4. The rules are applied against all features in the tree until there are nomore features to select.

Feature Deselection Processing

1. When a parent feature is cleared, all its descendant features (Childfeatures, Grandchild features, and so on) are cleared as well.

2. When a feature is cleared, all select-if-selected rules targeting thatfeature are evaluated and any dependent features are cleared.

3. These rules are applied against all features in the tree until there are nomore features to clear.

Feature Selection ValidationThe process solution installation programs enforce feature selection rulesby performing a feature selection validation process. This is the process ofderiving the complete set of features that are to be processed anddetermining if the user input violates any rules. If any feature ruleviolations are detected, then the operation to install or uninstall features isnot carried out by the process solution installation programs.

Feature Validation Using the WizardWhen you use the process solution installation wizard, most rulesare dynamically enforced as selections/deselections are madeagainst the feature tree on the Feature Selection Panel. Forexample, when you select a child feature, all of its ancestor featuresare automatically selected.

Additional rules are validated when you have finished makingyour selections and attempt to move to the next panel. If anyviolations of the rules are detected, messages describing theviolations are displayed on the Feature Selection Panel and youmust correct your input before proceeding.

Feature Validation Using the Command Line InterfaceFor the process solution command-line interface, the same featureselection rules are enforced and the complete set of features toinstall or uninstall is derived using those rules.

For example, if you specify only a child feature in your -addfeatlistparameter, the PSI CLI adds all ancestor features to the list that areactually installed. Similarly, if you specify a parent Feature on the-delfeatlist parameter, then any installed child features under thatparent feature is also uninstalled.

Additionally, the process solution command-line interface alsoperforms additional checks against the features you specify. Thesechecks include:


1. Ensuring that any feature identifier specified is a valididentifier for the package.

2. Ensuring that features specified using the -addfeatlistparameter are not already installed for the package.

3. Ensuring that features specified using the -delfeatlist parameterare already installed for the package.

Pre-deployment system checkBefore the actions associated with a software life cycle operation are initiated, theprocess solution installation programs perform a system check activity. Associatedwith each process solution package are a set of requirements that must be satisfiedbefore the deployment operation is carried out. The system check is a process thatanalyzes the requirements to determine that all requirements have been satisfiedbefore continuing on with the deployment operation.

The actual requirements are specific to each process solution package.Requirements include disk space and memory consumption checks for the packageand dependency checks between a process solution package and other processsolution packages. When unsatisfied requirements are detected during the systemcheck, the process solution installation programs display messages that describethe failed requirements. Before trying the deployment operation again, you mustupdate your environment such that all requirements associated with the processsolution package are satisfied.

Bypassing Unsatisfied RequirementsUnder certain circumstances, you may find it necessary to bypass thesystem check processing and carry out a deployment operation even if oneor more requirements associated with the process solution package are notsatisfied. For example, a process solution package might have embeddedan incorrectly specified disk space check which would prohibit the packagefrom being installed on a system that has adequate free disk space requiredby the package.

Both process solution installation programs provide mechanisms that allowyou to bypass failed requirements and continue with the deploymentoperation.

Using the Installation wizardWhen using the Process Solution Installation wizard, a SystemCheck Failed panel displays messages for any failed requirements.From this panel, you can bypass the system check failures byselecting the check box entitled Ignore System Check Failures.When you select this check box, the Process Solution Installationwizard continues with the deployment of the process solutionpackage.

Using the Command Line InterfaceWhen using the Process Solution Command Line Interface, you canbypass unsatisfied system check requirements by specifying the-force command-line flag.

Package requirements represent criteria put in place to ensure a successfuldeployment. While you must not bypass any requirements normally, theprocess solution installation programs permit the following types ofrequirements to be bypassed:v Capacity and consumption checks, for example, disk space and memory

requirements for a package.


v Prerequisite, corequisite, and exrequisite relationships defined for a rootpackage. For example, Package B might require that Package A isinstalled before Package B can be installed. You can force processing ofthe installation operation for Package B even if Package A is notcurrently installed.

v Property checks defined for the package, for example, a check of thetype of operating system on which the installation is being performed.

v Any custom checks defined for the package.

Note: Prerequisite, corequisite, and exrequisite dependencies definedbetween fix packages cannot be overridden.

System check progress messagesDuring the processing of the system check, the IBM Autonomic ComputingDeployment Engine publishes events detailing the progress of the systemcheck. The process solution installation programs receive the events andconvert them into localized messages with identifier CTGIN0146I whichare displayed to the user. The messages include the label for the checkbeing performed, the number of completed checks, and the total number ofchecks that are to be performed.

The IBM Autonomic Computing Deployment Engine is not able tocompute the total number of checks to be carried out before any checks areprocessed. The counter associated with the total number of checks to beperformed can increase during system check processing. For example, thefollowing set of messages might be issued during the system checkprocessing. The counter associated with the total number of checks is notfixed, but recalculated and increased during system check processing.CTGIN0146I: Completed system check for check "1" of "2". Check display name:"Check_Common_PMP_Installed".CTGIN0146I: Completed system check for check "2" of "3". Check display name:"Check_LTA_WAR_Package_Installed".CTGIN0146I: Completed system check for check "3" of "4". Check display name:"Check_Foundation_PM_Package_Installed".CTGIN0146I: Completed system check for check "4" of "4". Check display name:"MaximoDiskSpaceCheck".

Installing process managers using the process solution installationwizard

Process managers can be installed using the process solution installation wizard

About this task

Complete the following steps to install a process solution package into SmartCloudControl Desk using the process solution installation wizard:

Procedure1. Start the process solution installation program by navigating to the

<install_home>\bin directory of your SmartCloud Control Desk installation,and using solutionInstallerGUI.bat. As with the Process Solution InstallationCommand Line Interface Client, the Process Solution Installation InstallAnywhere installation program starts on the administrative workstation. Thelaunch script is deployed and configured by the SmartCloud Control Deskinstallation program. No post-installation configuration is required. StartsolutionInstallerGUI.bat and the wizard is started.


Alternatively, if you elected to create program shortcuts during theSmartCloud Control Desk installation, a link to the Process Solutioninstallation program UI can be available from the Start menu, a desktop icon,or a quick launch bar.

2. Select a language for your installation, and then click OK.3. From the Introduction panel, click Next.4. From the Choose PSI Package panel, click Choose and navigate to the package

file you want to deploy, select it, and then click Open. The PSI packageselected can be a base install, incremental update, full update, or fix packageOnce a package has been selected and you click Next, the process solutioninstallation program performs a series of validation checks to verify that thepackage you selected is valid. The system is checked to ensure that thepackage has not already been deployed, or, if the package is intended as anupgrade, the system is checked to ensure that the base package has alreadybeen installed.

5. From the Package Validation Results panel, review and verify the informationdisplayed, and then click Next.

6. If this is the first time you have installed this process manager, the processsolution installation program license agreement window is displayed. Readthe license information and select I accept the terms in the license agreementif you agree with the terms. Click Next. If you are incrementally adding orremoving features from a previously installed process manager, you encounteran Add or Remove Features? panel where you declare whether you areadding or removing features from the process manager, followed by anotherpanel where you select which specific features you are adding or removing.

7. If this is the first time you have installed this process manager and it hasselectable features, you are prompted by the Feature Selection panel to selector clear features you would like to install or uninstall from the previouslydeployed package.

8. From the Middleware Login Information panel, enter the credentials for whichyou are being prompted, and then click Next. The contents of this panel areconstructed dynamically, depending on the type of package you are installing.The package is queried to determine what middleware login credentials arenecessary to complete the installation of the package.Once you have entered the requested user IDs and passwords, the processsolution installation wizard validates the credentials by connecting to themiddleware servers using the supplied credentials.

9. After the credentials have been verified, a package options panel is displayedthat details the deployment options that the package supports. If the PSIinstallable package supports the Overwrite Customer Modified Data duringUpdate option, you can select it from this page. After you specify whichoptions are used, the process solution installation program will perform asystem check. to ensure that all system requirements necessary for thepackage to be installed are present. Click Next to advance.

10. From the Pre-Install Summary panel, review and verify the informationdisplayed, and then click Next. The process solution installation programbegins the package installation process. A progress panel informs you of thedeployment progress of the installation.

11. When the installation has completed successfully, from the PackageSuccessfully Deployed panel, click Next. If there is a package failure, amessage appears for the step that failed. If this was a Feature Add, orRemoval, a message displays indicating the feature was added or removedsuccessfully.


12. From the Install Another Package panel, select Install Another Package? andclick Done, to install another package. Otherwise, ensure that Install AnotherPackage? is cleared and click Done to exit the process solution installationwizard.

Results

You might see an installation progress bar displayed briefly after you click Done.The Process Solution Installation wizard is actually terminating and no installationactivities are being performed. The deployment of the Process Solution Packageyou were installing has already completed and the progress bar can be safelyignored.

Process solution installation client command-line interfaceUse the process solution installation client command-line interface (CLI) to query,install, upgrade, and uninstall process solution packages.

Process solution packages can consist of process modules and integration modules.

Starting the process solution installation client CLIA launch script is provided for starting the Process Solution Command LineInterface. The script is named solutionInstaller.bat and is deployed andconfigured in the <install_home>\bin directory. The Process Solution CommandLine Interface is used on the administrative workstation. The launch script isdeployed and configured by the SmartCloud Control Desk installation program.No post-installation configuration is required. Start solutionInstaller.bat withthe preferred command string and the action is performed.

During processing of the command, the Process Solution Command Line Interfacewrites messages to the standard output of the command window from which thecommand was launched.

General syntaxGeneral syntax of starting the solution installation program.

solutionInstaller syntax

The syntax for starting solutionInstaller is:solutionInstaller.bat parameter-clause-1 parameter-clause-2 ... parameter-clause-n

v Each parameter-clause consists of either -parameterName parameterValue or-parameterName.

v -parameterName parameterValue is used for parameters that require a parametervalue.

v -parameterName is used for parameters that represent switches or flags which donot require a parameter value.

v parameterName represents the name of one of the supported parameters.v parameterNames are always prefaced with a dash.v parameterValue represents the value associated with a particular parameter name.v parameterValues that contained embedded spaces must be enclosed in double

quotation marks


Perform actionThe solution installation program uses an action parameter when interfacing withpackages.

A special parameter, -action, must be specified on each invocation ofsolutionInstaller. This parameter specifies the action or software life cycleoperation to be performed. Based on the value specified for this parameter,additional parameters can be specified. For example, when -action showinstall isspecified, the type parameter must also be provided. The following table identifiesthe supported actions that can be specified for the Process Solution Command LineInterface.

Table 22. Process solution command-line interface actions

Operation Value of -action Parameter

List Installed Packages showinstalled

List Available Packages showavail

Base Install install

Incremental Update/Fix Pack upgrade

Undo Incremental Update/Fix Pack undo

Uninstall uninstall

Apply interim fix applyfix

Undo interim fix undofix

List Installed Fixes for a Package showfixes

Refresh Language Support Files for aPackage

refreshlangs

Add or Remove Features modfeatures

Show Available Features showfeatures

Summary of supported parametersThis section contains a summary of parameters supported by the command-lineinterface.

The collection of supported parameters for the Process Solution Command LineInterface is described in the following table.

Table 23. Process solution command-line interface supported parameters

Parameter Name Description

-action Specify the function or software life cycleoperation to perform.

-addfeatlist Specifies the list of features to be installed. Afeature is identified by its untranslatedEnglish Feature Identifier. Multiple featuresin the list are separated by a colon character.If any of the Feature Identifiers includes aspace, then the entire value for thisparameter must be enclosed in doublequotation marks.

-dbpwd Specifies the password of the database userID that is used to access the Maximodatabase.


Table 23. Process solution command-line interface supported parameters (continued)


-dbuser Specifies the database user ID that is used toaccess the Maximo database.

-delfeatlist Specifies the list of features to be deleted. Afeature is identified by its untranslatedEnglish Feature Identifier. Multiple featuresin the list are separated by a colon character.If any of the Feature Identifiers includes aspace, then the entire value for thisparameter must be enclosed in doublequotation marks.

-fixid Specifies the unique identifier of an interimfix/patch that you want processed.

-force Specifies whether to continue on with adeployment operation even if there are oneor more unsatisfied requirements associatedwith the package being processed.

-license Automatically accept the license agreementor be prompted for the acceptance orrejection of the license agreement by usingone of the following values: accept orprompt.

-loadlanguages Specifies whether options Language Supportfiles for the package must be loaded into theMaximo Database

-loadsampdata Specifies whether to load sample ordemonstration data associated with thepackage being processed.

-maxpwd Specifies the password of the SmartCloudControl Desk administrative user that isused to access the SmartCloud Control Deskapplication.

-maxuser Specifies the SmartCloud Control Deskadministrative user ID that is used to accessthe Maximo console.

-pkgpath Specifies the file path of a process solutionpackage. Paths that have embedded spacesmust be enclosed in double quotation marks.

-pkguuid Specifies the unique identifier of the processsolution package that you want processed.

-pkgver Specifies the version of the process solutionpackage that you want processed.

-skipdbcfg Specifies whether to defer the update of theMaximo database during packagedeployment.

-skipj2eecfg Specifies whether to defer the regenerationand redeployment of the Maximo J2EEApplications during package deployment.


Table 23. Process solution command-line interface supported parameters (continued)


-type Specify one of the following types ofsolution element package to be returnedwhen the showavail or showinstalled actionsare used. Valid values are processmodule,integrationmodule, or all.

Process solution command-line interface referenceSee the following sections for process solution command-line interface referenceinformation.

Several of the command-line interface actions reference a syntax element named[<middleware login information>].

The syntax for the middleware login element is:[-wasuser <userid> -waspwd <password>][-dbuser <userid> -dbpwd <password>][-maxuser <userid> -maxpwd <password>][-wasrxauser <userid> -wasrxapwd <password>].

The actual user IDs and passwords that are required depend on the package beingprocessed. For example, a package that only deploys content to the Maximodatabase would only require the -dbuser and -dbpwd parameters.

Table 23 on page 193

install action - install\ a packageDescription of the action used to install packages.

install

Actioninstall

PurposePerform an installation of a process solution package not already installed.

SyntaxsolutionInstaller

-action install-pkgpath <path-to-base-install-package-file>[<middleware login information>][-license <accept|prompt>][-skipj2eecfg] [-skipdbcfg] [-loadlanguages] [-loadsampdata] [-force]

DescriptionThe install action is used to install a process solution package. Wheninstalling a package, the file name of the process solution package archivefile to be installed is specified using the -pkgpath parameter.

PreconditionsBefore using this action, you must ensure that:v The process solution package archive file you specify is a valid Base

Install package.v The package is not already installed. You can check by using the

showinstalled action.


v All additional requirements associated with the package specified aresatisfied.

Sample Usage

modfeatures action - modify existing features of a deployedpackageDescription of the action used to modify existing features of a deployed package.

modfeatures

Actionmodfeatures

PurposeModify features of a currently installed process solution package.

SyntaxsolutionInstaller

-action modfeatures-pkgpath <path-to-base-install-package-file>[-addfeatlist FeatA:FeatB:¦:Featn][-delfeatlist FeatA:FeatB:¦:Featn][<middleware login information>][-skipj2eecfg] [-skipdbcfg] [-force]

DescriptionThe modfeatures action is used to modify the installed features for acurrently installed process solution package. When modifying features, thefile name of the process solution package archive file containing thefeatures to be modified is specified using the -pkgpath parameter. To addnew features not already installed, you use the –addfeatlist parameter. Toremove currently installed features, you use the –delfeatlist parameter.You cannot both add and remove features with one invocation. One andexactly one of either the –addfeatlist or the –delfeatlist parametersmust be provided when this command is started.


Process solution installation logsIf you experience any problems or encounter any error messages during the use ofthe process solution installation program, see these log files.

Log files are kept in the following locations:

Table 24. Process solution installation logs

Log type Description Location

Package log These are log files containingthe StdOut/StdErr output ofexternal commands launchedby the package as it isprocessed by theDeployment Engine. Theselog files are typically vital tothe proper debugging ofpackage issues.

In general, logs have twoparts, a ".out" and ".err" file,both with the samepre-extension file name. .outfiles contain the contents ofthe Standard Output streamas output by the externalcommand. .err files containthe contents of the StandardError stream. It is normal forone to be blank, providedthere was no error output (orthere was ONLY erroroutput).

Note that you might discovernumerous (10-20) packagelog files generated for anyparticular package installed.

<install_home>\solutions\logs\<PACKAGE_NAME>\


Table 24. Process solution installation logs (continued)


SmartCloud Control Desklog

These are logs kept by thePSI subsystem.

<install_home>\logs\CTGInstallMessageXX.log<install_home>\logs\CTGInstallTraceXX.log

XX is a two-digit numbersuch as 00. These logscontain the trace output ofthe PSI subsystem.

Note: You might encountermessages like the followingin theMAXIMO_DEPLOY_ERR.err filefound in the<install_home>\solutions\logs directory for a processmanager once it has beeninstalled:

v *sys-package-mgr*:processing new jar,'C:\IBM\SMP\lib\icl.jar'

v *sys-package-mgr*:processing new jar,'C:\IBM\SMP\lib\CTGInstallCommon.jar'

v *sys-package-mgr*:processing new jar,'C:\IBM\SMP\lib\CTGInstallResources.jar'

Although these messagesappear in an error log file,they are informational only,and do not representdeployment errors. Thesemessages can be safelyignored.

Solution Install/DeploymentEngine Logs

These are logs kept by theIBM Solution installationprogram/Deployment enginerun time. PSI utilizes theIBM technology as the meansto install and track installedpackages. This run time hasits own logging system.

Note: After an installationthese logs contain sensitivecredentials. Remove logsafter a successful installation.

C:\IBM\SMP\CTG_DE\acsi\logs\<USERNAME>\de_msg.log

C:\IBM\SMP\CTG_DE\acsi\logs\<USERNAME>\de_trace.log

So for instance, if youinstalled under the username "Administrator", thelogs would be found under:C:\IBM\SMP\CTG_DE\acsi\logs\Administrator\de_msg.log




WebSphere ApplicationServer Logs

These are logs kept ofconnections, exceptions, andother failures experienced bythe WebSphere ApplicationServer in its day-to-dayrunning. These logs are oftenhelpful in the diagnosis oferrors in particular EAR filesor other operations, such asdatabase connections.

<WAS_HOME>\profiles\<PROFILE>\logs\AboutThisProfile.txt

<WAS_HOME>\profiles\<PROFILE>\logs\<SERVER_NAME>\startServer.log

<WAS_HOME>\profiles\<PROFILE>\logs\<SERVER_NAME>\stopServer.log

<WAS_HOME>\profiles\<PROFILE>\logs\<SERVER_NAME>\SystemErr.log

<WAS_HOME>\profiles\<PROFILE>\logs\<SERVER_NAME>\SystemOut.log

So for instance, if yourWebSphere ApplicationServer was installed in"C:\IBM\WebSphere\AppServer\", your profilename was "AppSrv01", andyour server name was"server1", you would providethe followinglogs:C:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\AboutThisProfile.txt

Maximo Logs There are also a few logskept by Maximo itself. Theseare useful in tracking theprogress, success, and failureof a few commands providedby Maximo.

<install_home>\maximo\tools\maximo\log\updatedb<TIMESTAMP>.log

So if your Maximoinstallation location was"C:\IBM\SMP\Maximo", and thepackage executed the"UpdateDB" command onApril 19th at approximately5:06:07PM, the logginginformation would bewritten to the file:C:\IBM\SMP\Maximo\tools\maximo\log\updatedb20070419170607.log




WebSphere Thin Client Logs The WebSphere thin client isthe mechanism by which theprocess manager packagescommunicate with theWebSphere ApplicationServer. If this automateddeployment fails, the exactactions the Thin Client tookand the associated responsesfrom the WebSphereApplication Server are storedin logs.

<install_home>\wasclient\logs\CTGIN_wsadmin.traceout

<install_home>\wasclient\logs\wsadmin.traceout

<install_home>\wasclient\logs\wsadmin.valout

So if your SmartCloudControl Desk installationlocation were C:\IBM\SMP, thefollowing log files wouldcontain the Thin WebSphereClient tracing information:

C:\IBM\SMP\wasclient\logs\CTGIN_wsadmin.traceout

C:\IBM\SMP\wasclient\logs\wsadmin.traceout

C:\IBM\SMP\wasclient\logs\wsadmin.valout

It is a good practice to rename existing logs before attempting a package install. Itis useful to have a log composed of only the information related to the success orfailure of current package installation to facilitate problem determination.


Chapter 16. Advanced installation topics

This section contains information useful for advanced SmartCloud Control Deskdeployment scenarios.

Refer to this information for installation and configuration information in advanceddeployments.

Configuring and managing Oracle WebLogic ServerThis section describes common tasks on configuring and administering the OracleWebLogic Server.

For more comprehensive information on running and administering OracleWebLogic Server visit the Oracle Web site.

Starting Oracle WebLogic ServerStarting the Oracle WebLogic Server.

About this task

To start the MAXIMOSERVER application, complete the following steps:

Procedure1. Open a command prompt window and change the directory to:

Windows Windows:C:\bea\user_projects\domains\mydomain

UNIX UNIX:weblogic_install_dir/user_projects/domains/mydomain

2. Launch:

Windows Windows:startWebLogic.cmd

UNIX UNIX:./startWebLogic.sh

3. If prompted, type the administrator user name and password. Once you see thephrase: server started in RUNNING Mode or Started weblogic Admin ServerMAXIMOSERVER for domain mydomain running in production mode (dependingon your operating system), the Oracle WebLogic Server is running.

Stopping the Oracle WebLogic ServerYou can use the Administrative Console to stop the Oracle WebLogic Server.

About this task

To stop the MAXIMOSERVER from the Administrative Console, complete thefollowing steps:


http://www.oracle.com/technology/products/weblogic/index.html

Procedure1. Open a browser window and enter the URL: http://localhost:7001/console This

URL is the administration URL for Oracle WebLogic Server domain youcreated.

2. Log in to the Administration Console with the administrator user name andpassword.

3. In the Domain Structure section, click Environment > Servers.4. In the main section of the console, click the AdminServer link.5. Click the Control tab.6. Click Shutdown and then Force Shutdown Now. The MAXIMOSERVER is

stopped.

Changing the middleware installation program configurationparameters

You can change the configuration parameters you have entered for a deploymentplan before deploying the plan. You would use this option if you chose to cancelthe deployment of the deployment plan you developed by exiting the middlewareinstallation program. Configuration parameters for a plan can be changed onlybefore deploying the deployment plan.

About this task

These instructions assume that you have developed a deployment plan, enteredconfiguration parameters for the plan, and then exited the middleware installationprogram before actually deploying the deployment plan.

Procedure1. Relaunch the middleware installation program from the launchpad and

advance along the installation program panels until you reach the ChooseWorkspace panel.

2. From the Choose Workspace panel, specify the directory you previously usedas the middleware installation program workspace, and then click Next.

3. Select Edit the configuration parameters, and then click Next.4. Advance along the middleware installation program panels and make changes.5. When you reach the Deployment Plan Operation panel, select Deploy the plan,

and then click Next.6. From the Deployment Plan and Parameter Configuration summary panel,

review the contents of the summary, and then click Next to initiate theinstallation and configuration of the middleware you selected.

7. From the Select Middleware Image Directories panel, enter the location forcompressed images for the middleware contained in the deployment plan, anda directory to use to hold the uncompressed images. After you have entered thetwo locations, click Next. During deployment, the middleware images areuncompressed onto the system.

8. Click Finish to exit.

Maintaining EAR filesThis section contains information about maintaining SmartCloud Control DeskEAR files.


The following instructions are used to manually build or uninstall the SmartCloudControl Desk maximo.ear and maximoiehs.ear files on Oracle WebLogic Server.v If you modify any database connection parameters in the maximo.properties file

after the initial installation, you must rebuild of the maximo.ear file, and thenredeploy it in Oracle WebLogic Server. In this scenario, you would likely onlyrebuild and redeploy the maximo.ear file. You would not be required to rebuildand redeploy the maximoiehs.ear file.

v If you have installed SmartCloud Control Desk into a development environment,you might at some point like to migrate the deployment into a test orproduction environment. In this scenario, you must deploy both the maximo andmaximo help applications into the new environment.

Building EAR filesYou can manually build SmartCloud Control Desk EAR files if, for example, youmodify a database connection parameter in the maximo.properties file after theinitial installation.

About this task

To manually build SmartCloud Control Desk EAR files, complete the followingsteps:

Procedure1. Build the maximo EAR file:

Windowsinstall_home\maximo\deployment\buildmaximoear.cmd

Linux and UNIXinstall_home/maximo/deployment/buildmaximoear.sh

2. Build the maximo help system EAR file:

Windowsinstall_home\maximo\deployment\buildmxiehsear.cmd

Linux and UNIXinstall_home/maximo/deployment/buildmxiehsear.sh

Manually uninstalling applications from Oracle WebLogicServer

This section contains information about uninstalling SmartCloud Control Deskapplications from Oracle WebLogic Server.

Manually uninstalling applications from Oracle WebLogic ServerProcedure1. Log into the Administration Console. For example, http://<server>:<port>/

console2. Click Lock & Edit.3. Click Deployments.4. Select the application for the EAR to uninstall.5. Click Delete.

Chapter 16. Advanced installation topics 203


Chapter 17. Middleware on Solaris and HP-UX

Middleware versions that are not installable by the middleware installationprogram are installed by using graphical installation programs that are providedwith each middleware product.

The procedures in this document can be used to manually install the followingproducts on the following operating systems:

Solaris 11 SPARC and HP-UX 11i v2+3 64 bit

v IBM DB2 Enterprise Server Edition 9.7v IBM Tivoli Directory Server 6.3.

IBM Tivoli Directory Server 6.3 is only supported for Solaris 11.

Operating system preparationSome operating system default configuration settings must be change to providean environment that can host middleware operations.

The steps needed to prepare each newly supported operating system are operatingsystem dependent.

Perform the operating system preparation steps before installing any middleware.

Middleware installation on SolarisSome of the default kernel configuration parameters on Solaris might not besufficient to run IBM DB2 9.7.

Ensure that your Solaris system includes required kernel parameters by runningthe db2osconf utility after you install IBM DB2, but before you create any databaseobjects.Related information:

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp

HP-UXIn order for IBM DB2 9.7 to run correctly on HP-UX, certain group membershiprequirements must be addressed following the installation of IBM DB2.

After IBM DB2 9.7 is installed, you must ensure that the root user is assigned as amember of the db2iadm1 group.

Run the db2osconf utility to ensure that your HP-UX system has required kernelparameters in place. This utility must be run after you install IBM DB2, but beforeyou create any database objects.



Related information:


Installing the componentsAfter the operating system is configured as needed, install the middlewarecomponents.

Middleware components are installed in the following order:1. IBM DB22. IBM Tivoli Directory Server

Note: The media or web site you use to install middleware has directory-specificlocations for each supported operating system. The directory structure isos/product.

These commands display the contents of the os/product directory.cd osls

Within each os subdirectory are the installation directories for each middlewareproduct.ls solarisDB2-ESE_9.7_FP3aTIV-DirectoryServer_6.3

Installing DB2Run the db2setup program to install DB2.

Before you begin

Before you install DB2, review the requirements.

There are a number of things you must check to ensure a successful installation.Before you start the DB2 setup wizard, consider the following prerequisiteconditions:v If you choose to automate database configuration when you install SmartCloud

Control Desk, the user maximo is typically created for you on the system thathosts the database server. For Solaris and HP-UX systems, you must manuallycreate the user even if the SmartCloud Control Desk installation programconfigures the database automatically. Before you install SmartCloud ControlDesk, ensure that you create the maximo user on the database server.

v db2setup starts a wizard installer so X Window System must be installed andrunning before you start the DB2 installer program. Export your display:export DISPLAY= your_ip_address:0

v If NIS, NIS+, or similar security software is used in your environment, you mustmanually create the required DB2 users, before you start the DB2 setup program.See the centralized user-management considerations topic in the DB2information center, before you begin.

v In general, you can choose to defer some installation activities. For example, ifyou choose to not set up email notifications of database events at installationtime. If you want to defer specific installation activities, select that option, andconfigure them later.



v Some middleware products have specific requirements or conventions foraccount names and other settings. Override the installation defaults as shown ifthe defaults provided are not satisfactory. On panels that prompt for passwords,both the password and its confirmation entry must be specified before theinstaller can continue to the next panel.

About this task

This procedure describes how to perform a typical installation of DB2 on a singlecomputer. If you want to install DB2 components on multiple computers, see theDB2 information center for those instructions.

Databases must contain a single partition and Unicode data (UTF-8).

DB2 is installed, by default, in the /opt/IBM/db2/V9.7 directory.

The /opt/IBM/db2/V9.7/logs directory contains a db2install.history file. This filecontains the installation settings used, and errors that occurred during theinstallation process. The vmrfis.history file contains information aboutmaintenance that has been applied to DB2, such as fix packs that have beeninstalled.

The db2setup.log file captures all DB2 installation information including errors.The db2setup.err file captures any error output that is returned by Java (forexample, exceptions and trap information). By default, both logs are created in the/tmp directory unless you change that location during the installation process.

Procedure1. Log in as root.2. Copy the DB2 Enterprise Server Edition tar file to a writable disk.

For SolarisCopy solaris/DB2-ESE_9.7_FP3a/v9.7fp3a_sun64_server.tar.gz

For HP-UXCopy hpux-ia64/DB2-ESE_9.7_FP3a/v9.7fp3a_hpipf64_server.tar.gz

3. Change to the directory where you copied the compressed file anduncompress it.

4. Extract the file DB2_Enterp_Svr_OEM_Activation.zip into an appropriatedirectory. For example, for Solaris, solaris/DB2-ESE_9.7/

5. Start the installer. Type ./db2setup.6. From the launchpad, select Install a Product.7. Click Install New.8. Accept the license agreement.9. In general, accept all defaults, except where you must provide custom values.

For example, the email address of the recipient of email notifications ofdatabase events defaults to host name@local_server_name. This value must bechanged to a valid email address if you choose to enable SMTP notifications.This value can also be changed at a later time.

10. Leave the check boxes for the GUI and UID options selected; the systemassigns them for you.

11. On the Start copying files and create response file panel, click Finish to initiatethe installation.

12. Start the DB2 instance.

Chapter 17. Middleware on Solaris and HP-UX 207

13. Register the DB2 server license:a. Extract the license file.b. Use the DB2 license management tool command to apply the license:

DB2_HOME/adm/db2licm -a full path to the license file

The license file can be found in the appropriate folder for your operatingsystem. For Solaris, the license file is in solaris/DB2-ESE_9.7/DB2_Enterp_Svr_OEM_Activation/db2/license/db2ese_o.lic.

c. Stop and then restart the DB2 instance by using the db2stop and db2startcommands.

d. Verify that the license was installed successfully:DB2_HOME/adm/db2licm -l

This command results in output like the following information:Product name: "DB2 Enterprise Server Edition"License type: "Restricted"Expiry date: "Permanent"Product identifier: "db2ese"Version information: "9.7"


http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/r0007059.html

Installing IBM Tivoli Directory Server on SolarisYou typically install IBM Tivoli Directory Server on a computer that does not hostother middleware products.

Procedure1. Login as root.2. Copy the tar files for IBM Tivoli Directory Server to a writable disk. For

Solaris, copy the tds63-solaris-sparc-base.tar and tds63-solaris-sparc-gskit.tar files from solaris64/TIV-DirectoryServer_6.3.

3. Unpack the files:tar -xvf tds63-solaris-sparc-base.tartar -xvf tds63-solaris-sparc-gskit.tar

4. Change to the /tdsV6.3/tds directory and then type ./install_tds.bin

If you prefer, you can specify a temporary directory other than the systemtemporary directory. Change to the appropriate directory and type thefollowing command at a command prompt:./install_tds.bin -is:tempdir directory

. The variable directory is the directory you want to use for temporary space.Be sure that you have at least 400 MB of free space in this directory. Forexample:./install_tds.bin -is:tempdir /opt/tmp

5. When the installation wizard starts, select a language to use for theinstallation process, accept the license agreement, and choose a Custominstallation.

6. Select the Proxy Server, Server, C Client, Java Client, and WebAdministration Tool options, and then click Next.

7. Select Do not specify. I will manually deploy at a later time, then click Next.





8. Click Install.9. Close the Instance Administration tool.

10. Click Finish.11. Create the idsccmdb instance.12. Start the directory server, type the following commands:

a. /opt/ibm/ldap/V6.3/sbin/idsdiradm -I idsccmdb

b. /opt/ibm/ldap/V6.3/sbin/idsdirctl -D admin user ID -w admin userpassword

Chapter 17. Middleware on Solaris and HP-UX 209


Chapter 18. Backup and restoration

Like all important business data, it is a good idea to establish a process andschedule for backing up SmartCloud Control Desk data.

Back up and restore middleware application data using the methods described inthe documentation for that product is important. Also, establish a process forbacking up data contained on the SmartCloud Control Desk administrativeworkstation.

The default installation directory on the SmartCloud Control Desk administrativeworkstation is C:\ibm. This directory contains the critical files for your SmartCloudControl Desk deployment, which includes all class files and customizations thathave been performed in your environment, the current Enterprise Archive (EAR)file, and the properties files and installation tools used for your environment. Planto back up SmartCloud Control Desk administrative workstation data just afterinitial deployment and schedule periodic backups on an ongoing basis.

Backing up the administrative workstationIt is recommended that you back up all SmartCloud Control Desk middlewareapplications and SmartCloud Control Desk administrative workstation on a regularbasis.

About this task

The default installation directory on the administrative workstation is C:\ibm. Thisdirectory contains the critical files for your SmartCloud Control Desk deployment.

Specifically, the administrative workstation contains the following items:v Class files and customizations performed in your environment.v The current Enterprise Archive (EAR) file.v The properties files and installation tools used for your environment.

It is important to make a back up of the database at the same time that you backup the administrative workstation. During restoration, you restore the databaseback up at the same time you restore the administrative workstation back up itwas paired with.

To back up critical SmartCloud Control Desk information, complete the followingsteps:

Procedure1. Back up the SmartCloud Control Desk database, J2EE server, and

authentication server information using the instructions provided by yourmiddleware vendors.

2. Create a backup of the installation directory. By default, this directory isC:\IBM\SMP. Ensure that all file permissions are preserved.


Restoring the administrative workstationThis section details how to restore previously backed up SmartCloud Control Deskadministrative workstation information to a Windows workstation. Thisinformation can be used to return an existing SmartCloud Control Deskadministrative workstation to a previous state.

Before you begin

It is important to restore the back up of the database that was made when youbacked up the administrative workstation. A database back up should be restoredwith the administrative workstation back up it was paired with.

About this task

To restore SmartCloud Control Desk information to an administrative workstation,complete the following steps:

Procedure1. Restore the database back up that was paired with the administrative

workstation back up you are restoring.2. Log on to the target administrative system with the same user ID that was used

to install the product on the existing administrative workstation.3. Copy the SmartCloud Control Desk installation files and directories to the file

system of the target administrative system. You must maintain the directorystructure of the original installation. For example, if the SmartCloud ControlDesk installation directory on the existing administrative system is C:\IBM\SMP,you cannot copy those files to a C:\NewAdminWS\IBM\SMP directory on the targetadministrative workstation.

Installation propertiesInstallation properties are recorded in properties files during a deployment and areused as input by future install-related actions. Installation properties are found inthe install.properties and maximo.properties files as well as the database. Youshould only modify properties found in the install.properties file that arerelated to host names or user IDs. Changing values for other properties canseverely impact your ability to perform future installation actions, upgrades and fixpack installations.

Table 25. Installation properties


MAXIMO Properties Maximo.InstallLocation Install location of the maximo directory.

For example, C:\\IBM\\SMP\\maximo

mxe.db.user Database user that the server uses to attachto the database server.

For example, maximo

mxe.db.schemaowner Owner of the database schema.

For example, maximo

This value must be dbo for Microsoft SQLServer.


Table 25. Installation properties (continued)


mxe.db.password Password for the database user name.

mail.smtp.host SMTP host server.

mxe.workflow.admin E-mail account of the workflowadministrator.

mxe.adminEmail Valid e-mail address used by workflows tocommunicate with workflow participants.

mxe.name Name to bind the MXServer server object toin the RMI registry.

For example, mxserver.

mxe.hostname Name of the machine and port hostingMXServer.

mxe.rmi.port RMI communication port. If set at zero, RMIuses any available port. You can selectanother available port number.

mxe.registry.port The port number used to bind RMI/JRMPcommunications.

For example, 13400.

The RMI registry is started by the firstinstance of the maximo application to run.An environment could have multipleinstances of the product application running.This registry coordinates these instances.There is a single central RMI registry server.This value is the port available for the otherapplication instances to communicate withthe central server.

mxe.allowLocalObjects Set to true in production environments, toimprove system performance. Set to false fordevelopment work, or for customapplications.

The default is false.

mxe.useAppServerSecurity Indicates whether to use LDAP or nativeauthentication. Setting this value to 1indicates you are using LDAP for security.

mxe.MLCacheLazyLoad By default, the multi-language metadatacache loads one object at a time. Set this flagto 1 to load all objects simultaneously forone language.

mxe.UserLicenseKey The product enabler (license key) is usedduring installation. If the product enablerchanges this value must be updated.

mxe.adminuserid The administrative user. Used by the serverfor administrative tasks and to run crontasks. This user must have access to all Sitesin the system.

mxe.adminuserloginid Defines the default login user ID for theproduct application.

The default value is maxadmin.

Chapter 18. Backup and restoration 213



mxe.adminPasswd The password for the mxe.adminuserloginiduser.

mxe.system.reguser Self registration user. This user isresponsible for the process by which userscan create their own accounts.

The default value is maxreg.

mxe.system.regpassword User registration login password. This valueis the password for the user listed formxe.system.reguser.

mxe.email.charset The character set for e-mail notifications sentfrom the product.

When this property is defined, it is thecharset that is used to encode the subjectand message when an e-mail notification issent.

mxe.reorder.previewtimeout The reorder preview time out period (inminutes). This value must be set to the samevalue as the Web server session time out.

The default value is 30 minutes.

mxe.security.provider The security provider is obtained from thepolicy file, which is normallycom.sun.crypto.provider.SunJCE.

To use a different provider, you can specifya value for this parameter.

mxe.mbocount Displays the number of business objectscreated by the server.

The default is 1. Changing the value to 0disables this feature.

mxe.esig.defaultuserid Set this flag to true if you want theEsignature login dialog to default to thelogin ID.

The default value is true.

maximo.min.required.db.version Defines what the minimum level of databaseis required for an upgrade. An examplevalue would be 7100.

mxe.encrypted Property used by the application todetermine if property files are encrypted.

This value is set to true if the file isencrypted.

mxe.LDAPUserMgmt Indicates whether LDAP owns usermanagement whenmxe.userAppServerSecurity = 1.

The default value is 1.

SmartCloud ControlDesk specificProperties

CCMDB.InstallLocation Product install location.

For example, C:\\IBM\\SMP.




CCMDB.JREInstallLocation JRE install location.

For example, C:\\IBM\\SMP\\JRE.

CCMDB.SDKInstallLocation SDK install location.

For example, C:\\IBM\\SMP\\SDK.

CCMDB.PMP Unused property.

CCMDB.Locale The locale setting of the administrativeworkstation system.

For example, en.

CCMDB.BaseLanguage Base language that was set for the product.

For example, en.

CCMDB.AdditionalLanguages Additional languages installed for theproduct.

CCMDB.DeploySampleData Binary value that determines whethersample data is to be loaded during theinstallation.

For example, false.

CCMDB.UserShortcuts Location of the menu for process solutioninstaller and the product console shortcuts.

CCMDB.InstallType Type of installation, which includes fix pack,upgrade, or new installation.

For example, Install.

CCMDB.DeployEar Binary value that indicates if EAR files aredeployed during the installation.

For example, true.

process automationengine specificproperties

BASE.DeployOptionalContent Binary value that indicates if optionalcontent is deployed during the installation.

For example, true.

BASE.DeployOptionalContentSet Indicates whether you selected to deployoptional content during the initial upgrade.This value, once set, is a fixed value andcannot be changed. This value will be usedfor all future upgrades and fix packs.

BASE.VersionUpgradingFrom The previous version of process automationengine that was installed.

LDAP Server-specificProperties

LDAP.AutomateConfig Binary value that indicates whether theinstallation program automaticallyconfigures the directory server.

For example, true.

LDAP.Vendor The type of LDAP repository.

LDAP.ServerHostName Host name of the LDAP system host.

LDAP.AdminDN Administrator distinguished name.

For example, cn=root.




LDAP.AdminPassword Password for user ID named inLDAP.AdminDN.

LDAP.ServerPort Port listening for connection requests.

For example, 389.

LDAP.InstallLocation Install location of the directory server.

For example, C:\ProgramFiles\IBM\LDAP\V6.2.

Database-specificProperties

Database.AutomateConfig Binary value that indicates whether theinstallation program automaticallyconfigures the database.

For example, true.

Database.Vendor Database type.

For example, DB2.

Database.RemoteAccessUserName Database server system user ID that is usedfor configure the database remotely.

Database.RemoteAccessPassword Password for user ID named inDatabase.RemoteAccessUserName.

mxe.db.driver Java class name of the JDBC driver.

For example, com.ibm.db2.jcc.DB2Driver.

For example, oracle.jdbc.OracleDriver.

For example com.inet.tds.TdsDriver.

mxe.db.url JDBC URL of the database.

For example,

jdbc:db2://mymachine.mydomain.com:50005/maxdb75

jdbc:inetdae7a:mymachine.mydomain.com:1433?database=maxdb75&language=us_english&nowarnings=true&mars=false

jdbc:oracle:thin:@mymachine.mydomain.com:1521:ctginst1

mxe.db.initialConnections Number of database connections to createwhen the application server is started.

For example, 8.

mxe.db.maxFreeConnections Maximum number of free databaseconnections available in the connection pool.

For example, 8.




mxe.db.minFreeConnections Minimum number of free databaseconnections needed in the connection poolin order for more connections to beallocated.

For example, 5.

mxe.db.newConnectionCount Number of new connections to be createdwhen the minimum free connections areavailable in the connection pool.

For example, 3.

mxe.db.transaction_isolation The system install sets the value to:TRANSACTION_READ_COMMITTED.

This value cannot be modified.

mxe.db.format.upper This value defines the database uppercasefunction for the system.


mxe.db.autocommit This value sets the autocommit mode usedfor the Write connections. Can be either trueor false. The default is false.


mxe.db.systemdateformat System date format.

For DB2, the value is current timestamp.

For Oracle, the value is sysdate, and thedefault value cannot be edited.

For Microsoft SQL Server, the value isgetdate().

mxe.db.format.nullvalue The database-specific format of the nullvalue function.

For DB2 the value is COALESCE, and thedefault value cannot be edited.

The value for Oracle is NVL, and the defaultvalue cannot be edited.

The value for Microsoft SQL Server must beset to ISNULL.

mxe.db.sqlserverPrefetchRows Setting to reduce lock contention.

Optimal setting is 200 rows. Setting a valuelarger than 500 can degrade performance.

The default value is 0.

This value is only valid for SQL Server.




mxe.db.logSQLTimeLimit The system logs the SQL statements thattake longer than the specified time limit. Thetime is measured in milliseconds(thousandths of a second).

The default value is 1000 milliseconds.

To disable, edit the file to read:mxe.db.logSQLTimeLimit=0.

mxe.db.fetchResultLogLimit When this setting is enabled, a stack trace isprinted in the log for every business objectset that fetches beyond the set limit of rows.The stack trace log is also repeated for everymultiple of such fetches.

The default is 200 rows.

To disable, edit the file to read:mxe.db.fetchResultLogLimit=0.

Oracle Properties Database.Oracle.InstanceName Oracle instance name.

Database.Oracle.SoftwareOwner Owner of the software installation.

For example, oracle.

Database.Oracle.SoftwareOwnerPassword Password for the user ID listed inDatabase.Oracle.SoftwareOwner.

Database.Oracle.InstallLocation Oracle installation location. For example,/opt/app/oracle/product/10.2.0/db_1.

Database.Oracle.DataTablespaceName Oracle table space name for the productdatabase.

For example, maxdata.

Database.Oracle.InstanceLocation Oracle instance location.

For example, /opt/app/oracle/product/10.2.0/db_1.

Database.Oracle.DataTablespaceLocation Location of Oracle database table space.

Database.Oracle.DataTablespaceSize Tablespace size, measured in Mb.

For example, 1000.

Database.Oracle.DataTablespaceMaxSize Maximum size of the table space, measuredin Mb.

For example, 8000.

Database.Oracle.TempTablespaceName Temporary table space name.

For example, maxtemp.

Database.Oracle.TempTablespaceLocation Location of temporary table space.

Database.Oracle.TempTablespaceSize Temporary table space size, measured in Mb.

For example, 1000.




Database.Oracle.TempTablespaceMaxSize Maximum size of the temporary table space,measured in Mb.

For example, 8000.

Database.Oracle.IndexTablespaceName Index table space name.


Database.Oracle.IndexTablespaceLocation Location of index table space.

Database.Oracle.IndexTablespaceSize Index table space size, measured in Mb.

For example, 1000.

Database.Oracle.IndexTablespaceMaxSize Maximum size of the index table space,measured in Mb.

For example, 8000.


Database.Oracle.SchemaPassword Password for user listed inmxe.db.schemaowner.

Database.Oracle.ServerHostName Host name of the Oracle server.

Database.Oracle.ServerPort Port number used by Oracle.

For example, 1521.

Database.DBAUserName Oracle DBA user name.

For example, sys.

Database.DBAPassword Password for user ID listed forDatabase.DBAUserName.

DB2 Properties mxe.db.schemaowner Owner of the database schema.

Database.DB2.ServerHostName Host name of the DB2 server.

For example, mymachine.mydomain.com.

Database.DB2.ServerPort Database server port.

For example, 50005.

Database.DB2.InstanceName Name of the database instance.

For example, ctginst1.

Database.DB2.DatabaseName Name of the database.

For example, maxdb75.

Database.DB2.InstallLocation Install location of the database.

For example, /opt/IBM/db2/V9.7

Database.DB2.LogFileSize Set the size for transaction logs.

For example, 4096

Database.DB2.AppCtlHeapSize Application control heap size.

For example, 1024




Database.DB2.ApplHeapSize Application heap size.

For example, 1024

Database.DB2.LockListSize Size allocated to the lock list.

For example, 30000

Database.DB2.LogSecond Number of secondary log files allowed.

For example, 4

Database.DB2.ServiceUser User ID used to autostart.

Database.DB2.ServicePassword Password for Database.DB2.ServiceUser.

Database.DB2.PageSize Page size setting.

Measured in kb. For example, 32

Database.DB2.ExtentSize Number of pages per extent (group ofpages).

For example, 32

Database.DB2.FencedUser Fenced user ID for DB2 on Linux or UNIXsystems.

For example, db2fenc1.

Database.DB2.AuthType Method DB2 uses to authenticate users.

For example, server.

Database.DB2.DataTablespaceName DB2 table space name for the productdatabase.


Database.DB2.BufferPoolName DB2 buffer pool name.

For example, MAXBUFPOOL.

Database.DB2.BufferPoolLocation Location of the buffer pool.

Database.DB2.BufferPoolSize Size of the buffer pool.

For example, 32

Database.DB2.DataTablespaceLocation Location of DB2 database table space.

Database.DB2.DataTablespaceSize Tablespace size, measured in Mb.

For example, 1000.

Database.DB2.DataTablespaceMaxSize Maximum size of the table space, measuredin Mb.

For example, 8000.

Database.DB2.TempTablespaceName Temporary table space name.

For example, maxtemp.

Database.DB2.TempTablespaceLocation Location of temporary table space.

Database.DB2.TempTablespaceSize Temporary table space size, measured in Mb.

For example, 1000.




Database.DB2.TempTablespaceMaxSize Maximum size of the table space, measuredin Mb.

For example, 8000.

Database.DB2.IndexTablespaceName Index table space name.


Database.DB2.IndexTablespaceLocation Location of index table space.

Database.DB2.IndexTablespaceSize Temporary table space size, measured in Mb.

For example, 1000.

Database.DB2.IndexTablespaceMaxSize Maximum size of the index table space,measured in Mb.

For example, 8000.

Database.DB2.InstanceAdminUserName Administrative user or the database instance.

Database.DB2.InstanceAdminPassword Password for the user ID specified forDatabase.DB2.InstanceAdminUserName

Microsoft SQL ServerProperties


Database.SQL.DatabaseName Name of the database.

For example, maxdb75.

Database.SQL.InstallLocation Microsoft SQL Server installationlocation. For example,C:\\ProgramFiles\\Microsoft SQL Server\\90.

Database.SQL.DataFileLocation Location for database data file

Database.SQL.DataFileName A way to specify the name of the data fileused for the database. For example,maxdb75_dat.

Database.SQL.DataFileMaxSize Maximum size for data file for database.

Database.SQL.DataFileSize Initial size for data file for database.

Database.SQL.LogFileName A way to specify the name for the databasetransaction log file. For example,maxdb75_log.

Database.SQL.LogFileSize Microsoft SQL Server Database transactionlog file size.

Database.SQL.DataFilegroupName Database logical name file group. Forexample, PRIMARY.

Database.SQL.ServerHostName Host name of the database server. Forexample, myhost.mydomain.com.

Database.SQL.ServerPort Database server port. For example, 1433.

Database.SQL.InstanceAdminUserName Administrative user for the Microsoft SQLServer instance. used during install forcreating database, creating database user,and modifying the database.

Database.SQL.InstanceAdminPassword Administrative users password.

ADE (DE) Properties DE.InstalllLocation Location of the deployment engine.




Application ServerType Properties

ApplicationServer.Vendor Indicates which application server waschosen during installation. For example,WebLogic.

Updating environment dataWhen you install a second product on the same administrative workstation, orupgrade a single product, the installation program uses values recorded from theprevious deployment. These values are stored on the administrative system in theinstall.properties and maximo.properties files, and also in the database. If youmade any environmental changes to any of the systems used for the originaldeployment, they must be recorded in the install.properties andmaximo.properties files. They also must be updated in the database. Typically,these types of changes include changing a host name or updating a password.

Before you begin

During a follow-up installation task, the installation program uses values found inthe install.properties and maximo.properties files to complete the upgrade orinstallation of an additional product. Pending successful use of these credentials,you are not prompted to provide them again. If the installation program fails tolog on to the system with the credentials from the properties files, you areprompted to supply current credentials. These values are then written to theappropriate property file.

This method of updating credential information in property files has one exception.Database connection and credential information must always be current before youattempt an upgrade operation. Information for the database connection andcredentials are stored in the maximo.properties file. Any changes to thisinformation from the time of the original deployment must be recorded manuallyin the maximo.properties file before you upgrade.

Passwords are encrypted within properties files. Update the encrypted values inthe properties files with clear text values and then re-encrypt the property file.

About this task

Updates to properties files can be performed by manually editing the appropriatevalue in a property file. There is a reconfiguration tool available from theIntegrated Service Management Library that can be used to update properties. Seethe Integrated Service Management Library (https://www.ibm.com/software/brandcatalog/ismlibrary/) and search for IBM Maximo Reconfiguration Tool forAdministrative Workstations.

Procedure1. Update the property value in the database by using the System Properties

application in SmartCloud Control Desk.2. Update the database properties in the maximo.properties file:

a. As a precaution, create a backup of the c:\ibm\smp\maximo\applications\maximo\properties\maximo.properties file.

b. Delete the c:\ibm\smp\maximo\applications\maximo\properties\maximo.properties file.


https://www.ibm.com/software/brandcatalog/ismlibrary/

https://www.ibm.com/software/brandcatalog/ismlibrary/

c. Copy c:\ibm\smp\etc\maximo.properties_orig to c:\ibm\smp\maximo\applications\maximo\properties\maximo.properties

d. Rename c:\ibm\smp\maximo\applications\maximo\properties\maximo.properties_orig to c:\ibm\smp\maximo\applications\maximo\properties\maximo.properties.

e. Edit c:\ibm\smp\maximo\applications\maximo\properties\maximo.properties and update the credential or connection information forthe target database server.

f. Encrypt the file c:\ibm\smp\maximo\tools\maximo\encryptproperties.batfile.

3. Update the c:\ibm\smp\etc\install.properties file on the administrativeworkstation with any properties that changed. Do not change encryptedpassword properties. Encrypted password properties are prefixed by [enc] inthe installation.properties file. Passwords can be updated during the nextupgrade.

Results

After completing these updates, you can upgrade, install a fix pack, or installanother product with the corrected values.



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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct 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 itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationSoftware Interoperability Coordinator, Department 49XA3605 Highway 52 NRochester, MN 55901U.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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,


modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© IBM Corp. 2013. Portions of this code are derived from IBM Corp. SamplePrograms. © Copyright IBM Corp. 2012. All rights reserved.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksFor trademark attribution, visit the IBM Terms of Use Web site(http://www.ibm.com/legal/us/)

The following terms are trademarks of International Business MachinesCorporation in the United States, other countries, or both:

IBM, the IBM logo, AIX, Tivoli, the Tivoli logo, and WebSphere are trademarks orregistered trademarks of International Business Machines Corporation in theUnited States, other countries, or both.

Intel, the Intel logo, and Pentium are trademarks of Intel Corporation in the UnitedStates, other countries, or both.

Microsoft, Windows, the Windows logo, and Internet Explorer are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Other company, product, and service names may be trademarks or service marksof others.

Notices 227


Index

Aaction

install 192showavail 192showinstalled 192undo 192uninstall 192upgrade 192

administrative workstationbacking up 211restoring 212

aggregation packages 181

Bbackup 211

Ccompany related accounts

updating 157configure 154configure SMTP 154configuring

database server 69confirming the Integration Composer

installation 142currency codes

creating 154

Ddatabase

applying changes 156database server 69DB2

configuring existing server with themiddleware installationprogram 49

install on Solaris and HP-UX 206manual configuration, 9.x 70

default insert sitecreating 158

deploying ear files 42, 64, 99deployment engine

backing up 14deployment operations

typical 184deployment plan

overview 17directory server

manually configuring 79

Ee-mail listener

configuring in WebLogic Server 31,53, 89

EAR filesbuilding manually 203maintaining 203

environmental dataupdating 222

executeMapping command 145

Ffonts

AIX 8

Ggeneral ledger account

creating 156general ledger account component

creating 155general ledger component type

authorizationupdating 157

group 26

Hhardware and software requirements,

Integration Composer 132help 153

IIBM Tivoli Directory Server 26

install on Solaris 208manually configuring 79

installautomatic middleware

configuration 17install action 195install silently 103installation

advanced topics 201automatically configuring existing

middleware 47deploying using manual middleware

configuration 69deploying with manually configured

middleware 69Integration Composer

with Launchpad 131preparing 1product, automatically configured

middleware 35, 56product, manually configured

middleware 91properties 212Tivoli Integration Composer 135, 140

Installationpost installation tasks 153

installation prerequisites, IntegrationComposer 134

installingprerequisite software products 17,

103silent 103

Integration Composerinstalling

with process solution installationpackage 137, 141

UNIX systems 137, 141Integration Composer installation

prerequisites 134Integration Composer installation,

confirming 142Integration Composer overview 131Integration Composer requirements,

hardware and software 132Integration Composer, uninstalling 146integration framework

JMS optionsconfiguring 30, 52, 87

item and company setscreating 155

JJ2EE server

manually configuring 86JRE

configuring in Linux 10

Llanguage enablement 160languages

deploying after database updatedeferral 44, 66, 100, 101

launchpadoverview 15starting 16

librariesLinux 10

logsmiddleware installation program 20,

21process solution installation

program 197

MMaximo Application Server

starting 42, 64, 99MAXIMOSERVER domain

creating 29, 51, 87memory allocation

changing 145Microsoft Active Directory

configuring 83


Microsoft SQL Servermanual configuration 76restoring 172

middleware 17, 103changing configuration

parameters 202install on Solaris and HP-UX 205,

206install preparation on Solaris and

HP-UX 205installing on HP-UX 205installing on Solaris 205remote configuration 12starting and stopping 177starting on UNIX 178starting on Windows 177uninstalling 27

middleware clean up scripts 163middleware cleanup scripts 163middleware installation

before you begin 1middleware installation program

log reference 21logs 20

modfeatures action 196

Nnstallation

before you begin 1

Oonline help 153Oracle

manual configuration, 10g 74manual configuration, 11g 72restoring 171

Oracle WebLogic Serverconfiguring 201managing 201manually uninstalling 203post product installation 40, 62, 97setting the host name in the

application 43, 65, 100starting 201

organizationcreating 155

overview, Integration Composer 131

Ppackage types 180packages 180port availability

checking 6post installation 153post product installation

Oracle WebLogic Server 40, 62, 97post-installation tasks 143

top-level class for ITassets 159software 159

pre-deployment system checkprocess solution installation

program 189

prerequisite 17, 103process managers

installing using the process solutioninstallation wizard 190

process solution command line interfacereference 195

process solution deploymentmanaging from the administrative

workstation 184process solution installation

packages 180process solution installation client 192process solution installation

program 195, 196before you begin 183choosing 181logs 197supported operations 182

process solution packageinstallation methods 179

product installationbefore you begin 1

product installation programoverview 33, 55

propertiesinstallation 212silent product installation 106

Rrecovery tool

uninstall 173restoration 211

Ssecurity

configuring 161selectable features 184shared memory

setting 11signing in 153signing in and out 160silent install 103silent product installation

properties 106SMTP 154software life cycle operations 179solution installation program

command line interface supportedparameters 193

solution installer programaction 193

solution packagescommand line interface 192

solutionInstallersyntax 192

solutionInstaller scriptsolutionInstaller.bat 192solutionInstaller.sh 192

startFusion filememory allocation 145

swap sizesetting 11

system directoriesaccessing 7

system password policyconsiderations 13

Ttar command

AIX 7Tivoli Integration Composer

installation 135upgrade 140

Uulimit

setting 11uninstall

automatically configureddeployment 168

database configuration recover 170manual 175manually configured

deployment 169manually configured

middleware 169manually removing files 175product 167

without uninstallationprogram 173

recovery tool 173uninstall program recovery tool 174

uninstallationautomatically configured

middleware 168uninstalling Integration Composer 146uninstalling Integration Composer on

Unix-based operating systems 147uninstalling Integration Composer on

Windows operating systems 146user 26users

groupssynchronizing 161

synchronizing 161

Vverifying prerequisites

programmatically 2verifying the installation

manually 129programmatically 125

WWebLogic Server

manually configuring 29, 50, 86stopping 201

worktypescreating 158

Xxml request pages 160


��

Printed in USA