IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

IBM SmartCloud Control DeskVersion 7 Release 5.1

Installation Guide(IBM WebSphere)

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

Contents

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

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

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

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

Starting the launchpad . . . . . . . . . 17

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

Middleware installation program logs . . . . 22Middleware installation program log reference 24

Configuring IBM Tivoli Directory Server user andgroup strings . . . . . . . . . . . . . 34Configuring SSL between Microsoft ActiveDirectory and WebSphere Application ServerNetwork Deployment . . . . . . . . . . 35

Uninstalling middleware . . . . . . . . . . 39Reinstalling middleware with IBM DB2 . . . . . 40Installation program overview . . . . . . . . 41

Simple installation path values . . . . . . . 42Installing the product and automaticallyconfiguring middleware . . . . . . . . . 44Installing optional content . . . . . . . . 50Installing optional integration modules . . . . 50

Language deployment after database updatedeferral . . . . . . . . . . . . . . . . 51

Manually deploying languages after databaseupdate deferral . . . . . . . . . . . . 51

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

Configuring an existing DB2 with themiddleware installation program . . . . . . 55Verifying an existing IBM Tivoli Directory Serverusing the middleware installer . . . . . . . 57Preparing Microsoft Active Directory for reuse . 58

Installation program overview . . . . . . . . 60Simple installation path values . . . . . . . 61Installing the product and automaticallyconfiguring middleware . . . . . . . . . 63Installing optional content . . . . . . . . 69Installing optional integration modules . . . . 69

Language deployment after database updatedeferral . . . . . . . . . . . . . . . . 70


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

Manually configuring the database . . . . . 73Manually configuring DB2 9.x . . . . . . 74Manually configuring Oracle 11g . . . . . 76Manually configuring Oracle 10g . . . . . 78Manually configuring Microsoft SQL Server 80

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

Manually configuring the J2EE server . . . . 91Manually configuring WebSphere ApplicationServer Network Deployment . . . . . . 91

Installing the product and manually configuringmiddleware . . . . . . . . . . . . . . 133Installing optional content . . . . . . . . . 139Installing optional integration modules . . . . . 139Language deployment after database updatedeferral . . . . . . . . . . . . . . . 140


Chapter 5. Silent installation . . . . . 143Installing SmartCloud Control Desk silently . . . 143Silent installation properties . . . . . . . . 145

Copyright IBM Corp. 2012 iii

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

Chapter 7. Verifying the installationmanually . . . . . . . . . . . . . 177

Chapter 8. Configuring the HTTPOnlyattribute. . . . . . . . . . . . . . 179

Chapter 9. Installing IntegrationComposer . . . . . . . . . . . . . 181Integration Composer overview . . . . . . . 181Hardware and software requirements . . . . . 182Installation prerequisites. . . . . . . . . . 184Performing an Integration Composer installation 185

Installing Integration Composer using theLaunchpad . . . . . . . . . . . . . 185Installing Integration Composer on UNIXoperating systems in console mode . . . . . 187

Performing an Integration Composer upgrade . . 189Upgrading Integration Composer using theLaunchpad . . . . . . . . . . . . . 190Upgrading Integration Composer on UNIXoperating systems in console mode . . . . . 191

Confirming the installation . . . . . . . . . 192Post-installation tasks. . . . . . . . . . . 193

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

Uninstalling Integration Composer . . . . . . 196Uninstalling Integration Composer on Windowsoperating systems . . . . . . . . . . . 196Uninstalling Integration Composer on UNIXoperating systems . . . . . . . . . . . 197

Chapter 10. Installing the Deployer'sWorkbench . . . . . . . . . . . . 199

Chapter 11. Installing IBM SmartCloudControl Desk Everyplace . . . . . . 201Installing as part of a new product installation . . 201Installing as part of a product upgrade . . . . . 202Installing after SmartCloud Control Desk has beeninstalled . . . . . . . . . . . . . . . 202

Chapter 12. Post installation tasks 203Accessing product documentation . . . . . . 203Initial data configuration . . . . . . . . . 203

Signing in using a default user ID . . . . . 203Configuring SMTP . . . . . . . . . . 204Create currency codes . . . . . . . . . 205Create item and company sets . . . . . . . 205Create an organization . . . . . . . . . 205Create a general ledger account component . . 206Applying changes to the database . . . . . 206

Create a general ledger account . . . . . . 207Update General Ledger Component TypeAuthorization . . . . . . . . . . . . 207Update Company-Related Accounts . . . . . 207Create default insert site. . . . . . . . . 208Create worktypes . . . . . . . . . . . 208Create a classification structure for IT assets . . 209Specify a top-level class for IT assets andsoftware . . . . . . . . . . . . . . 209Signing out and signing in . . . . . . . . 210

Before working with BIRT reports . . . . . . 210Generating xml request pages . . . . . . . . 211Synchronizing users and groups . . . . . . . 211Understanding and configuring security . . . . 212

Chapter 13. Middleware clean upscripts . . . . . . . . . . . . . . 213Using the middleware cleanup scripts . . . . . 213

Chapter 14. Uninstalling the product 217Uninstalling an automatically configureddeployment . . . . . . . . . . . . . . 217

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

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

Restoring the DB2 database server . . . . 220Restoring the Oracle database . . . . . . 221Restoring the Microsoft SQL Server database 222

Uninstalling the product without the uninstallationprogram . . . . . . . . . . . . . . . 223

Uninstall program recovery tool . . . . . . 223Using the uninstallation program recoverytool. . . . . . . . . . . . . . . 224

Manual uninstallation . . . . . . . . . 227Recovering WebSphere Application Serverconfiguration . . . . . . . . . . . 227Removing files from the system . . . . . 230

Chapter 15. Starting and stoppingmiddleware . . . . . . . . . . . . 231Restarting middleware on Windows . . . . . . 231Restarting middleware on UNIX . . . . . . . 232Stopping middleware on Windows . . . . . . 233Stopping middleware on Linux and AIX . . . . 234

Chapter 16. Process solution packageinstallation methods . . . . . . . . 237Software life cycle operations . . . . . . . . 237Process solution packages . . . . . . . . . 238Package types . . . . . . . . . . . . . 238Aggregation packages . . . . . . . . . . 239Determining which process solution installationprogram to use . . . . . . . . . . . . . 239Supported operations for the process solutioninstallation programs . . . . . . . . . . . 240

iv IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

Before using the process solution installationprograms . . . . . . . . . . . . . . . 241Managing process solution deployment from theadministrative workstation . . . . . . . . . 241Typical deployment operation . . . . . . . . 242Selectable features . . . . . . . . . . . . 242Deferring J2EE and database configuration . . . 247

Manually completing deployment . . . . . 248Pre-deployment system check . . . . . . . . 249Installing process managers using the processsolution installation wizard. . . . . . . . . 250Process solution installation client command-lineinterface . . . . . . . . . . . . . . . 252

Starting the process solution installation clientCLI. . . . . . . . . . . . . . . . 252

General syntax . . . . . . . . . . . 252Perform action . . . . . . . . . . . 253Summary of supported parameters . . . . 253

Process solution command-line interfacereference . . . . . . . . . . . . . . 255

install action - install\ a package . . . . . 255modfeatures action - modify existing featuresof a deployed package . . . . . . . . 256

Process solution installation logs . . . . . . . 257

Chapter 17. Advanced installationtopics. . . . . . . . . . . . . . . 261WebSphere Application Server NetworkDeployment management . . . . . . . . . 261

Starting the application server from thecommand line . . . . . . . . . . . . 261Starting the application server from theadministrative console . . . . . . . . . 262Securing the WebSphere Application ServerNetwork Deployment administrative console . . 263Configuring Windows services . . . . . . 264

Configuring the WebSphere ApplicationServer Network Deployment applicationserver to run as a Windows service . . . . 264

Changing the middleware installation programconfiguration parameters . . . . . . . . . 265

Maintaining EAR files . . . . . . . . . . 266Building EAR files. . . . . . . . . . . 267Manually uninstalling applications fromWebSphere Application Server NetworkDeployment . . . . . . . . . . . . . 267Manually installing applications in WebSphereApplication Server Network Deployment . . . 267

Chapter 18. Middleware on Solarisand HP-UX . . . . . . . . . . . . 269Operating system preparation . . . . . . . . 269

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

Installing the components . . . . . . . . . 270Installing DB2 . . . . . . . . . . . . 270Installing IBM Tivoli Directory Server on Solaris 272Installing WebSphere Application ServerNetwork Deployment . . . . . . . . . 273

Creating WebSphere Application ServerNetwork Deployment profiles . . . . . . 274Manually configuring Virtual MemberManager on WebSphere Application ServerNetwork Deployment . . . . . . . . 276Installing the WebSphere update installer . . 280Installing and configuring IBM HTTP Server 280Installing the WebSphere plug-in . . . . . 283

Configuring Virtual Member Manager on IBMWebSphere Application Server NetworkDeployment . . . . . . . . . . . . . . 285

Chapter 19. Backup and restoration 287Backing up the administrative workstation . . . 287Restoring the administrative workstation . . . . 288Installation properties . . . . . . . . . . 288

Updating environment data . . . . . . . 301

Notices . . . . . . . . . . . . . . 305Trademarks . . . . . . . . . . . . . . 307

Index . . . . . . . . . . . . . . . 309

Contents v

vi IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

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 7You need to ensure that certain ports are available before using the productinstallation programs.AIX and HP-UX tar command requirements on page 8Both 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 9To 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 10IBM Tivoli Directory Server requires asynchronous I/O be enabled on AIXsystems.Checking for required libraries on Linux on page 11The SmartCloud Control Desk deployment requires certain Linux systemlibraries.Configuring the JRE in Linux on page 11In 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 12This 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 12SmartCloud 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 12This section details how to set a minimum shared memory value in Linux.Remote configuration enablement on page 13The 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.Enabling SSL client authentication on page 14The SmartCloud Control Desk installation program and the process solutioninstaller fail if the client authentication feature of secure sockets layer (SSL) isenabled in the IBM HTTP Server. You can use a workaround to enable clientauthentication during installation.System password policy settings on page 15Be 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 15These 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 prerequisitesYou 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.

2 IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)

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.v Middleware requirements such as software packages, library files, directory

permissions, host names, and installation locations.

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.

j2eeserverUse the j2eeserver parameter to have the prerequisite verification utilitycheck for WebSphere Application Server Network Deployment 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.

Chapter 1. Preparing for installation 3

Table 1. System verification parameters (continued)

Parameters Details

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

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


Table 1. System verification parameters (continued)

Parameters Details

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

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.


Table 2. Prerequisite verification utility properties (continued)

Property Description

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 9060 must be made available for IBM WebSphere Application Server NetworkDeployment.

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.

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.


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

2. Locate the section for the root user, and change the parameters to the followingvalues: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.

Verifying large page size support for AIXFor SmartCloud Control Desk to function correctly, large page size support mustbe enabled on AIX servers that host WebSphere Application Server.

About this task

If you are deploying SmartCloud Control Desk on WebSphere Application Serverhosted on an AIX system, that system must be configured to support large pagesizes.

Large page usage is primarily intended to provide performance improvements tohigh performance computing applications. Typically this feature is enabled bydefault on AIX systems.

Procedure1. Log on to the AIX system that hosts WebSphere Application Server and open a

console window. You must have root authority to work with the AIX operatingsystem commands.

2. Verify large page size support by running the following command:ps -Z

Output from the command includes 4K and 64K page sizes listed for processes,for example:# ps -Z

PID TTY TIME DPGSZ SPGSZ TPGSZ CMD311342 pts/4 0:00 4K 4K 4K ksh397526 pts/4 0:00 4K 4K 4K ps487558 pts/4 0:00 64K 64K 4K sleep

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 unlimited2. 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 9.

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.

Enabling SSL client authenticationThe SmartCloud Control Desk installation program and the process solutioninstaller fail if the client authentication feature of secure sockets layer (SSL) isenabled in the IBM HTTP Server. You can use a workaround to enable clientauthentication during installation.

Before you begin

The SmartCloud Control Desk installation and process solution installer programsuse HTTP client requests for various configuration actions. The SmartCloudControl Desk installation program does not configure WebSphere ApplicationServer Network Deployment nor IBM HTTP Server to use SSL. However, they dofunction in environments where WebSphere Application Server NetworkDeployment and IBM HTTP Server are manually configured to use SSL.SmartCloud Control Desk installation programs and standard deploymentprocedures do not work correctly when the client authentication feature of SSL isenabled in the IBM HTTP Server. As a result, the validation of productadministration credentials or the import of data with Maximo Enterprise Adapterfails. Client authentication is enabled in the IBM HTTP Server, by using theSSLClientAuth Required directive in the httpd.conf configuration file.


About this task

If client authentication must be enabled for the IBM HTTP Server, use thefollowing workaround procedure to install the product.

Procedure1. Remove the SSLClientAuth Required directive in the httpd.conf configuration

file of the IBM HTTP Server.2. Stop and restart the IBM HTTP Server.3. Run the SmartCloud Control Desk installation program or process solution

installation programs.4. Add the SSLClientAuth Required directive back to the httpd.conf

configuration file of the IBM HTTP Server.5. Stop and restart the IBM HTTP Server.

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.

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


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

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_dirv 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 WebSphere Application Server Network Deploymentv IBM Tivoli Directory Server

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

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:

Copyright IBM Corp. 2012 19

v DB2v WebSphere Application Server Network Deploymentv Tivoli Directory Server

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 the install location and administrative account details for WebSphereApplication Server Network Deployment.

18. Specify the profile names for the WebSphere Application Server NetworkDeployment deployment manager and application servers.

19. Specify the following details for WebSphere Application Server NetworkDeployment:a. Specify the WebSphere Application Server Network Deployment cell name.b. Specify the names of the WebSphere Application Server Network

Deployment deployment manager and application server nodes.c. Specify the install location WebSphere Application Server Network

Deployment update installer.20. Specify the install location, the port used by IBM HTTP Server, and the port

that must be used to administer IBM HTTP Server. If you install IBM HTTPServer into a directory path that includes spaces, for example, the defaultinstall location for Windows systems, you cannot start and stop it from theadministrative console. If the directory path includes spaces, you must startand stop the IBM HTTP Server from the command line.

Chapter 2. Deploying with automatic middleware configuration 21

21. Accept the default profile name for the WebSphere Application ServerNetwork Deployment plug-in for IBM HTTP Server by clicking Next. Thisvalue cannot be changed.

22. 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.23. 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.

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

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

26. Click Deploy to initiate the installation process.27. 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/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 /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 /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 /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 /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 this


substep 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: //deploymentPlan/MachinePlan_/000XX_DB2_9.7/install/01_BASE//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 //deploymentPlan/MachinePlan_/000XX_DB2_9.7/install/01_BASE//logs directory:v DB2_ESE_InstallProduct_.errv DB2_ESE_InstallProduct_.logv DB2_ESE_MoveDB2InstallLogsToLogsLoc_.errv DB2_ESE_MoveDB2InstallLogsToLogsLoc_.logv DB2_ESE_Register_DB_.errv DB2_ESE_Register_DB_.logv DB2_ESE_Verify_DB2_Level_.errv DB2_ESE_Verify_DB2_Level_.logv db2setup.logv de_processreq.logv de_processreq.log_utf8v de_trace.logFor Windows, the following additional files will be available:v DB2_ESE_Verify_DB2_Service_20080805_063132GMT.errv serviceList.logThe 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//deploymentPlan/MachinePlan_/000XX_DB2_XX/install/02_FP//logs directory:v DB2_ESE_FP2MoveDB2LogsToLogsLoc_.err


v DB2_ESE_FP2MoveDB2LogsToLogsLoc_.logv DB2_ESE_InstallDB2Fixpack_.errv DB2_ESE_InstallDB2Fixpack_.logv DB2_ESE_ListDB2FPAdmin_.errv DB2_ESE_ListDB2FPAdmin_.logv DB2_ESE_ListDB2FPinstance_.errv DB2_ESE_ListDB2FPinstance_.logv DB2_ESE_StartDB2FPAdminInstance_.errv DB2_ESE_StartDB2FPAdminInstance_.logv DB2_ESE_StopDB2FPAdminInstance_.errv DB2_ESE_StopDB2FPAdminInstance_.logv DB2_ESE_UpdateDB2_.errv DB2_ESE_UpdateDB2_.logv DB2_ESE_Verify_DB2_FP_Level_.errv DB2_ESE_Verify_DB2_FP_Level_.logv de_processreq.logv de_processreq.log_utf8v de_trace.logv installFixPack.logThe 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 folder. This directory contains thelogs related to DB2 installation

DB2 Configuration Step

The following DB2 configuration logs can be found in //deploymentPlan/MachinePlan_/000XX_DB2_Configuration/install/01_CONFIG//logs:v checkpasswdCreated.logv createuser.logv etcgroupfile.logv etcpasswdfile.logv setUserPassword.log

For Linux, including Linux on IBM System z, the following additional files areproduced:v permissions.logv 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.logv localEnvVariables.logv setTCPIPCommForDB2instance.logv setTCPIPPortForDB2instance.logv setWindowsServiceToAutoStart.log

For UNIX, including Linux, Linux on IBM System z, and AIX, the followingadditional files are produced:v createinstance.logv SetTCPIPCOMM.logv stopDB2.logv 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 //deploymentPlan/MachinePlan_/000XX_ITDS_DB2_CCMDB/check/01_CHECKS//logs:v etcgroupfile.logv 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 //deploymentPlan/MachinePlan_/000XX_ITDS_6.3/install/01_GSKIT//logs directory.v de_processreq.logv de_trace.logFor Windows and Linux, including Linux on IBM System z, the followingadditional files are produced:v GSKit_Install_GSKit_.logv GSKit_Install_GSKit_.errFor 32-bit Windows systems, the following additional file is produced:v gskInstall.logFor 32-bit Windows systems, the following additional files are produced:v ISScript_Install.logv gskInstall.logFor AIX systems, the following additional files are produced:v GSKit_Install_JS_RTE_20080721_084044GMT-06.00.logv GSKit_Install_SA_RTE_20080721_084044GMT-06.00.logv vGSKit_Install_TA_RTE_20080721_084044GMT-06.00.logv 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 //deploymentPlan/MachinePlan_/000XX_ITDS_6.3/install/02_BASE//logs directory:v de_processreq.logv de_trace.logFor Windows, the following additional files are available:v ldapinst.logv registryList.logFor Linux, including Linux on IBM System z, the following additional filesare produced:v ITDS6.3_CheckRPMEntry_.errv ITDS6.3_CheckRPMEntry_.logv rpmList.logFor AIX systems, the following additional files are produced:v ITDS6.3_CheckRTEEntry_.logv ITDS6.3_CheckRTEEntry_.errv rteList.logThe 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 fix packThe following IBM Tivoli Directory Server fix pack log files can be foundin the //deploymentPlan/MachinePlan_/000XX_ITDS_6.3/install/02A_FP//logs directory:v de_processreq.logv de_trace.logFor Windows, the following additional file are available:v ldapinst.logFor Linux, the following additional files are produced:v ITDS6.3_CheckRPMEntry_.errv ITDS_InstallFixpack_.logv rpmList.logFor AIX systems, the following additional files are produced:v ITDS_InstallFixpack_.errv ITDS_InstallFixpack_.logv ITDS6.3_CheckRTEEntry_.logv ITDS6.3_CheckRTEEntry_.errv 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 language packThe following IBM Tivoli Directory Server language pack log files can befound in the //deploymentPlan/MachinePlan_/000XX_ITDS_6.3/install/03_LP//logs directory:v de_processreq.logv de_trace.logFor Windows, the following additional files are available:v ldapLP_inst.logv registryList.logFor Linux, including Linux on IBM System z, the following additional fileis produced:v checkIfRPMEntryExists_.logFor AIX systems, the following additional files are produced:v checkIfRTEEntryExists_.logv checkIfRTEEntryExists_.err

IBM Tivoli Directory Server Configuration Step

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

For Windows, the following additional files are produced:v PasswdNeverExpires.logv 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.logv 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)

WebSphere Application Server Network Deployment Installation Step

WebSphere Application Server Network Deployment installation logs can be foundin the following locations:

WebSphere Application Server Network DeploymentThe following WebSphere Application Server Network Deploymentinstallation log files can be found in the //deploymentPlan/MachinePlan_/000XX_WAS_ND_7.0/install/01_BASE//logs directory.v de_processreq.logv de_processreq.log_utf8v de_trace.logv ProductInstall.logv WAS_ND_InstallProduct_.errv WAS_ND_InstallProduct_.log

UpdateInstallerThe following UpdateInstaller installation log files can be found in the//deploymentPlan/MachinePlan_/000XX_WAS_ND_7.0/install/01_UPDT_INST//logs directory.v de_processreq.logv de_processreq.log_utf8v de_trace.logv ProductInstall.logv Update_Installer_InstallProduct_.errv Update_Installer_InstallProduct_.logv UpdateInstaller_MoveUpdateInstallerInstallLogsToLogsLoc.errv UpdateInstaller_MoveUpdateInstallerInstallLogsToLogsLoc.log

The de_processreq.log contains status information. This log file provides detailson which action has failed. The failed action log can be examined for moreinformation. The ProductInstall.log file is the native log for the fix pack. This logcontains WebSphere Network Deployment and UpdateInstaller installationinformation.

WebSphere Application Server Network Deployment ConfigurationStep

WebSphere Application Server Network Deployment configuration logs can befound in the //deploymentPlan/MachinePlan_/000XX_WAS_ND_Configuration/install/01_CONFIG//logs directory:v createAppServer.log


v MXServer_serverStatus.logv nodeagent_serverStatus.logv setupcmd.logv startManager.logv startServer.logv UnixAugmentProfileDMgrForISC.logv UnixCreateProfileAppSvr.logv UnixCreateProfileDMgr.logv verifyProfile.logv startManager.log (produced in the 02_CONFIG folder)v stopManager.log (produced in the 02_CONFIG folder)v stopNode.log (produced in the 02_CONFIG folder)v syncNode.log (produced in the 02_CONFIG folder)v VMMConfigData.log (produced in the 02_CONFIG folder)v SystemErr.log (produced in the /profiles/ctgDmgr01/logs/dmgr

folder)

v SystemOut.log (produced in the /profiles/ctgDmgr01/logs/dmgrfolder)

v addNode.log (produced in the /profiles/ctgAppSrv01/logs folder)v runAddNode.log (produced in the /profiles/ctgAppSrv01/logs

folder)

v syncNode.log (produced in the /profiles/ctgAppSrv01/logsfolder)

v wsadmin.traceout (produced in the /profiles/ctgAppSrv01/logsfolder)

v SystemErr.log (produced in the /profiles/ctgAppSrv01/logs/nodeagent folder)

v SystemOut.log (produced in the /profiles/ctgAppSrv01/logs/nodeagent folder)

v startServer.log (produced in the /profiles/ctgAppSrv01/logs/MXServer folder)

v stopServer.log (produced in the /profiles/ctgAppSrv01/logs/MXServer folder)

v SystemErr.log (produced in the /profiles/ctgAppSrv01/logs/MXServer folder)

v SystemOut.log (produced in the /profiles/ctgAppSrv01/logs/MXServer folder)

IBM HTTP Server Installation Step

IBM HTTP Server installation logs can be found in the following locations:

IBM HTTP Server BaseThe following IBM HTTP Server base installation log files can be found inthe //deploymentPlan/MachinePlan_/000XX_IHS_7.0/install/01_BASE//logs directory.v de_processreq.logv de_processreq.log_utf8


v de_trace.logv IHS_InstallProduct_.errv IHS_InstallProduct_.logv ProductInstall.logThe de_processreq.log contains status information. This log file providesdetails on which action has failed. The failed action log can be examinedfor more information. ProductInstall.log is the native product log. Thislog contains IBM HTTP Server installation information.

IBM HTTP Server fix packThe following IBM HTTP Server fix pack log files can be found in the//deploymentPlan/MachinePlan_/000XX_IHS_7.0/install/01A_FP//logs directory:v de_processreq.logv de_processreq.log_utf8v de_trace.logv IHS_Fixpack_GetIHSUpdateVersion_.errv IHS_Fixpack_GetIHSUpdateVersion_.logv IHS_Fixpack_InstallIHSFixpack_.errv IHS_Fixpack_InstallIHSFixpack_.logv IHS_Fixpack_MoveIHSFixInstallLogsToLogsLoc_.errv IHS_Fixpack_MoveIHSFixInstallLogsToLogsLoc_.logFor Windows, the following additional files are available:v IHS_Fixpack_StartIHSAdminService_.errv IHS_Fixpack_StartIHSAdminService_.logv IHS_Fixpack_StartService_.errv IHS_Fixpack_StartService_.logv IHS_Fixpack_StopIHSAdminService_.errv IHS_Fixpack_StopIHSAdminService_.logv v IHS_Fixpack_StopService_.errv v IHS_Fixpack_StopService_.logFor UNIX, including Linux,Linux on IBM System z, and AIX, the followingadditional files are produced:v IHS_Fixpack_StartServiceLinux_.errv IHS_Fixpack_StartServiceLinux_.logv IHS_Fixpack_StopServiceLinux_.errv IHS_Fixpack_StopServiceLinux_.logv ProductInstall.logThe de_processreq.log contains status information. This log file providesdetails on which action has failed. The failed action log can be examinedfor more information. ProductInstall.log is the native product log. Thislog contains IBM HTTP Server fix pack installation information.

WebSphere plug-insThe following WebSphere plug-in logs can be found in the//deploymentPlan/MachinePlan_/000XX_IHS_7.0/install/02_WAS_PLUGIN//logs directory:


v de_processreq.logv de_processreq.log_utf8v de_trace.logv ProductInstall.logv WAS_plugins_for_WAS_InstallProduct_.errv WAS_plugins_for_WAS_InstallProduct_.logThe de_processreq.log contains status information. This log file providesdetails on which action has failed. The failed action log can be examinedfor more information. ProductInstall.log is the native product log. Thislog contains IBM HTTP Server fix pack installation information.

WebSphere plug-in fix packThe following WebSphere plug-in logs can be found in the//deploymentPlan/MachinePlan_/000XX_IHS_7.0/install/02A_FP//logs directory:v de_processreq.logv de_processreq.log_utf8v de_trace.logv ProductInstall.logv WAS_Plugins_for_WAS_Fixpack_GetWASPluginUpdateVersion_

.err

v WAS_Plugins_for_WAS_Fixpack_GetWASPluginUpdateVersion_.log

v WAS_Plugins_for_WAS_Fixpack_InstallWASPluginsFixpack_.err

v WAS_Plugins_for_WAS_Fixpack_InstallWASPluginsFixpack_.log

v WAS_Plugins_for_WAS_Fixpack_MoveIHSFixInstallLogsToLogsLoc_.err

v WAS_Plugins_for_WAS_Fixpack_MoveIHSFixInstallLogsToLogsLoc_.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. ProductInstall.log is the native product log. Thislog contains IBM HTTP Server fix pack installation information.

For Windows, the following additional files are available:v WASPlugin _Fixpack_StartIHSAdminService_.errv WASPlugin _Fixpack_StartIHSAdminService_.logv WASPlugin _Fixpack_StartService_.errv WASPlugin _Fixpack_StartService_.logv WASPlugin _Fixpack_StopIHSAdminService_.errv WASPlugin _Fixpack_StopIHSAdminService_.logv WASPlugin _Fixpack_StopService_.errv WASPlugin _Fixpack_StopService_.logFor UNIX, including Linux,Linux on IBM System z, and AIX, the followingadditional files are produced:v WASPlugin_Fixpack_StartServiceLinux_.err


v WASPlugin_Fixpack_StartServiceLinux_.logv WASPlugin_Fixpack_StopServiceLinux_.errv WASPlugin_Fixpack_StopServiceLinux_.logThe de_processreq.log contains status information. This log file providesdetails on which action has failed. The failed action log can be examinedfor more information. ProductInstall.log is the native product log. Thislog contains IBM HTTP Server fix pack installation information.

IBM HTTP Server WebSphere plug-in configurationThe following IBM HTTP Server WebSphere plug-in configuration logs canbe found in the //deploymentPlan/MachinePlan_/000XX_IHS_7.0/install/03_CONFIG//logs directory:v configure.webserver.command.outv ConfigureIHSPlugin.outv start.http.server.outv SystemErr.log (produced in the /profiles/ctgDmgr01/logs/

dmgr folder)

v SystemOut.log (produced in the /profiles/ctgDmgr01/logs/dmgr folder)

Authentication service

Authentication service logs can be found in the //deploymentPlan/MachinePlan_/000XX_ESS_XX/install/01_CONFIG//logs directory:v configureESS.logv exportWASLTPAKeys.logv importLTPAKeys.logv installESS.logv installWIM.logv key.filev modifyLTPASettings.logv save.logv startManager.01.logv startManager.02.logv startNode.01.logv startNode.02.logv startServer.01.logv startServer.02.logv stopManager.01.logv stopManager.02.logv stopNode.01.logv stopNode.02.logv stopServer.01.logv stopServer.02.logv sync.logv SystemErr.log (produced in the /profiles/ctgDmgr01/logs/dmgr/

folder)


v SystemOut.log (produced in the /profiles/ctgDmgr01/logs/dmgr/folder)

v addNode.log (produced in the /profiles/ctgAppSrv01/logs/folder)

v runAddNode.log (produced in the /profiles/ctgAppSrv01/logs/folder)

v syncNode.log (produced in the /profiles/ctgAppSrv01/logs/folder)

v wsadmin.traceout (produced in the /profiles/ctgAppSrv01/logs/folder)

v SystemErr.log (produced in the /profiles/ctgAppSrv01/logs/nodeagent/ folder)

v SystemOut.log (produced in the /profiles/ctgAppSrv01/logs/nodeagent/ folder)

v SystemErr.log (produced in the /profiles/ctgAppSrv01/logs/MXServer/ folder)

v SystemOut.log (produced in the /profiles/ctgAppSrv01/logs/MXServer/ 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

34 IBM SmartCloud Control Desk: Installation Guide (IBM WebSph

Documents

IBM SmartCloud Control Desk: Installation Guide (IBM WebSphere)