IBM SmartCloud Control Desk Version 7 Release 5
Installation Guide (Oracle WebLogic Server)
Note Before using this information and the product it supports, read the information in “Notices” on page 217. Contents
Chapter 1. Preparing for installation . . 1 Language deployment after database update Before you begin ...... 1 deferral...... 43 Programmatically verifying prerequisites ....2 Manually deploying languages after database Checking port availability ...... 6 update deferral ...... 44 Accessing system directories ...... 7 AIX tar command requirements ...... 7 Chapter 3. Deploying automatically AIX font requirements ...... 7 reusing existing middleware (Scenario Increasing AIX file size and number of descriptors 8 2)...... 45 Increasing AIX paging space ...... 8 Run the middleware installation program on Verifying large page size support for AIX....9 existing middleware servers ...... 45 Enabling asynchronous I/O on AIX .....10 Configuring an existing DB2 with the Checking for required libraries on Linux . . . 10 middleware installation program ...... 47 Configuring the JRE in Linux ...... 10 Verifying an existing IBM Tivoli Directory Server Setting the ulimit ...... 11 using the middleware installer ...... 48 Setting the swap size ...... 11 Preparing Microsoft Active Directory for reuse . 49 Setting shared memory ...... 12 Manually configuring WebLogic Server .....51 Remote configuration enablement ...... 12 Creating the MAXIMOSERVER domain ....52 System password policy settings ...... 13 Configuring JMS options for integration Backing up the Deployment Engine database . . 14 framework ...... 52 Specifying host name values...... 14 Configuring JMS for the email listener in Establishing a fully qualified host name on WebLogic Server...... 54 Windows systems ...... 15 Installation program overview ...... 56 Forcing the middleware installer to use Installing the product and automatically alphanumeric hostnames ...... 15 configuring middleware ...... 57 Launchpad ...... 15 Installing optional content ...... 62 Starting the launchpad ...... 16 Installing optional integration modules ....62 Post installation for Oracle WebLogic Server Chapter 2. Deploy with automatic deployments ...... 62 middleware configuration (Scenario 1) . 17 Deploying ear files ...... 64 Middleware installation program middleware Setting the Oracle WebLogic Server host name. . . 65 deployment plan overview ...... 17 Language deployment after database update Installing middleware using the middleware deferral...... 66 installation program ...... 17 Manually deploying languages after database Middleware installation program logs ....19 update deferral ...... 66 Middleware installation program log reference 21 Configuring IBM Tivoli Directory Server user and Chapter 4. Deploying manually reusing group strings ...... 26 existing middleware (Scenario 3) . . . 69 Uninstalling middleware ...... 27 SmartCloud Control Desk installation with manual Reinstalling middleware with IBM DB2 .....28 middleware configuration ...... 69 Manually configuring WebLogic Server .....28 Manually configuring the database .....69 Creating the MAXIMOSERVER domain ....29 Manually configuring DB2 9.x ...... 70 Configuring JMS options for integration Manually configuring Oracle 11g .....71 framework ...... 30 Manually configuring Oracle 10g .....74 Configuring JMS for the email listener in Manually configuring Microsoft SQL Server 76 WebLogic Server...... 31 Manually configuring the directory server . . . 79 Installation program overview ...... 33 Manually configuring IBM Tivoli Directory Installing the product and automatically Server ...... 79 configuring middleware ...... 35 Manually configuring Microsoft Active Installing optional content ...... 39 Directory ...... 83 Installing optional integration modules ....40 Manually configuring the J2EE server ....86 Post installation for Oracle WebLogic Server Manually configuring WebLogic Server . . . 86 deployments ...... 40 Installing the product and manually configuring Deploying ear files ...... 41 middleware ...... 91 Setting the Oracle WebLogic Server host name. . . 43 Installing optional content ...... 96 Installing optional integration modules .....96
© Copyright IBM Corp. 2007, 2011 iii Post installation for Oracle WebLogic Server Create an organization ...... 147 deployments ...... 96 Create a general ledger account component . . 147 Deploying ear files ...... 98 Applying changes to the database .....148 Setting the Oracle WebLogic Server host name. . . 99 Create a general ledger account ...... 148 Language deployment after database update Update General Ledger Component Type deferral ...... 100 Authorization ...... 149 Manually deploying languages after database Update Company-Related Accounts .....149 update deferral ...... 100 Create default insert site...... 150 Create worktypes ...... 150 Chapter 5. Silent installation .....101 Create a classification structure for IT assets . . 151 Installing SmartCloud Control Desk silently . . . 101 Specify a top-level class for IT assets and Silent installation properties ...... 103 software ...... 151 Signing out and signing in ...... 152 Chapter 6. Programmatically verifying Generating xml request pages ...... 152 Synchronizing users and groups ...... 153 that the installation was successful . . 123 Understanding and configuring security ....153
Chapter 7. Verifying the installation Chapter 12. Middleware clean up manually ...... 127 scripts ...... 155 Using the middleware cleanup scripts .....155 Chapter 8. Installing Integration Composer ...... 129 Chapter 13. Uninstalling the product 159 Integration Composer overview ...... 129 Uninstalling an automatically configured Installation prerequisites...... 129 deployment ...... 159 Performing the installation ...... 130 Running the product uninstall program for Installing using the Launchpad ...... 130 automatically configured middleware ....160 Installing on UNIX operating systems in console Uninstalling a manually configured deployment 161 mode ...... 132 Running the product uninstall program for Confirming the installation ...... 134 manually configured middleware...... 161 Post-installation tasks...... 135 Database configuration recovery ...... 162 Verifying the settings in the Integration Restoring the DB2 database server ....162 Composer fusion.properties file .....135 Restoring the Oracle database ...... 163 Changing the memory allocation in the Restoring the Microsoft SQL Server database 164 startFusion file (optional) ...... 137 Uninstalling the product without the uninstallation Changing the memory allocation in the program ...... 165 executeMapping file (optional) ...... 137 Uninstall program recovery tool ...... 165 Uninstalling Integration Composer ...... 138 Using the uninstallation program recovery Uninstalling Integration Composer on Windows tool...... 165 operating systems ...... 138 Manual uninstallation ...... 167 Uninstalling Integration Composer on UNIX Removing files from the system .....167 operating systems ...... 139 Chapter 14. Starting and stopping Chapter 9. Installing the Deployer's middleware ...... 169 Workbench ...... 141 Restarting middleware on Windows ...... 169 Restarting middleware on UNIX ...... 170 Chapter 10. Installing IBM SmartCloud Control Desk Everyplace ...... 143 Chapter 15. Process solution package Installing as part of a new product installation . . 143 installation methods ...... 171 Installing as part of a product upgrade .....144 Software life cycle operations ...... 171 Installing after SmartCloud Control Desk has been Process solution packages ...... 172 installed ...... 144 Package types ...... 172 Aggregation packages ...... 173 Chapter 11. Post installation tasks 145 Determining which process solution installation Accessing product documentation ...... 145 program to use ...... 173 Initial data configuration ...... 145 Supported operations for the process solution Signing in using a default user ID .....145 installation programs ...... 174 Configuring SMTP ...... 146 Before using the process solution installation Create currency codes ...... 146 programs ...... 175 Create item and company sets...... 147 iv IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Managing process solution deployment from the Deploying EAR files ...... 194 administrative workstation ...... 175 Building EAR files...... 195 Typical deployment operation ...... 176 Manually uninstalling applications from Oracle Selectable features ...... 176 WebLogic Server ...... 195 Pre-deployment system check ...... 181 Manually uninstalling applications from Installing process managers using the process Oracle WebLogic Server ...... 195 solution installation wizard...... 182 Process solution installation client command-line Chapter 17. Middleware on Solaris interface ...... 184 and HP-UX ...... 197 Starting the process solution installation client Operating system preparation ...... 197 CLI...... 184 Solaris...... 197 General syntax ...... 184 HP-UX ...... 197 Perform action ...... 185 Installing the components ...... 198 Summary of supported parameters ....185 Installing DB2 ...... 198 Process solution command-line interface Installing IBM Tivoli Directory Server on Solaris 200 reference ...... 187 install action - install\ a package .....187 modfeatures action - modify existing features Chapter 18. Backup and restoration 203 of a deployed package ...... 188 Backing up the administrative workstation . . . 203 Process solution installation logs ...... 189 Restoring the administrative workstation ....204 Installation properties ...... 204 Chapter 16. Advanced installation Updating environment data ...... 214 topics...... 193 Notices ...... 217 Configuring and managing Oracle WebLogic Trademarks ...... 219 Server ...... 193 Starting Oracle WebLogic Server ...... 193 Stopping the Oracle WebLogic Server ....193 Index ...... 221 Changing the middleware installation program configuration parameters ...... 194
Contents v vi IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 1. Preparing for installation
These topics provide information about product media, preinstallation considerations, overview of the installation procedure, and instructions on using the SmartCloud Control Desk launchpad.
Use the planning information to familiarize yourself with the overall process of a SmartCloud Control Desk deployment before you use this information to conduct the installation.
Before you begin A set of tasks must be completed before installing SmartCloud Control Desk. In some cases, to perform the steps, you must be logged in as a user with administrator privileges on Windows or as root on UNIX. Some processes, such as anti-virus programs, can negatively affect SmartCloud Control Desk installation on the system. You must temporarily shut down any noncritical processes before running 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 to install and configure SmartCloud Control Desk middleware. These tasks must be completed for any UNIX systems hosting middleware you intend to use with SmartCloud Control Desk.
Note: Make a copy of the image of the system, database, and application server on which you are planning to install the product.
Note: IBM® publishes updates to the middleware installation program. Before using it, visit the IBM Support Portal to see whether there is an updated copy of the installation program available for your use.
Ensure that you have adequate disk space for the future on the systems being used for the SmartCloud Control Desk deployment. Filling up the disk space on a SmartCloud Control Desk deployment system can cause problems with SmartCloud Control Desk operations.
Fully qualified host names provided to the installation programs must resolve between systems involved in the product deployment. Ensure all IP addresses configured for systems targeted for the product deployment are reachable using the ping command from the administrative workstation. “Checking port availability” on page 6 You need to ensure that certain ports are available before using the product installation programs. “AIX tar command requirements” on page 7 “Increasing AIX file size and number of descriptors” on page 8 For SmartCloud Control Desk to function correctly, you need to increase the default number of file descriptors allowed for the root user, and also set the maximum allowable file size to unlimited. “Increasing AIX paging space” on page 8 To successfully install and run SmartCloud Control Desk, you must increase the
© Copyright IBM Corp. 2007, 2011 1 default 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 10 IBM Tivoli® Directory Server requires asynchronous I/O be enabled on AIX systems. Without asynchronous I/O, DB2® and Oracle database instances cannot be started successfully. “Checking for required libraries on Linux” on page 10 The SmartCloud Control Desk deployment requires certain Linux system libraries. “Configuring the JRE in Linux” on page 10 In some cases, the middleware installation program fails on Red Hat Enterprise Linux 5 systems, or other systems with Security-Enhanced Linux (SELinux) enabled. “Setting the ulimit” on page 11 This section details how to set the ulimit in Linux, which is used to define user system and process resource limits. “Setting the swap size” on page 11 SmartCloud Control Desk can be a resource-intensive application. Configure and tune your system for maximum performance. This section details how to set the size of the swap space used in Linux systems. “Setting shared memory” on page 12 This section details how to set a minimum shared memory value in Linux. “Remote configuration enablement” on page 12 The SmartCloud Control Desk installation program can automatically configure middleware. You must enable a remote access protocol for each system on which you intend to install the middleware. “System password policy settings” on page 13 Be familiar with the password policies of systems you are using as part of a SmartCloud Control Desk deployment. “Backing up the Deployment Engine database” on page 14 These 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 installation program prerequisites are present on a system. Use this utility before starting the middleware and product installation programs. Programmatically verifying prerequisites You can use the prerequisite verification utility to verify that installation program prerequisites are present on a system. Use this utility before starting the middleware 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. v Middleware requirements such as software packages, library files, directory permissions, host names, and installation locations.
Note: This utility cannot be used to check Oracle WebLogic Server.
2 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) You can start the prerequisite verification utility from the product installation launchpad or from the command line. When started from the launchpad, the utility runs in interactive mode. When started from the command line, the prerequisite verification utility accepts various parameters. The prerequisite verification utility must be run on the system hosting the prerequisite being checked. You cannot use this 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 be used with the prerequisite verification utility. dbserver Use the dbserver parameter to have the prerequisite verification utility check for DB2 prerequisites. dirserver Use the dirserver parameter to have the prerequisite verification utility check for IBM Tivoli Directory Server prerequisites. bsi Use the bsi parameter to have the prerequisite verification utility check for prerequisites required by the product installation program. Run the prerequisite verification utility with the bsi parameter on the administrative workstation.
Syntax example: tpae_req_check.bat -component dbserver
If you do not use the -component parameter, you are prompted to specify components 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 utility verifies 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 DB2 server host.
The default input property file is tpae.properties, and is found on the middleware installation media in the SystemRequirements directory. There are also several sample property files found in the SystemRequirements\ sample_property_files. These sample property files contain custom values defined for particular operating systems. You can copy these property files to the system and modify them, or create your own, before running the prerequisite verification 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 verification utility, the utility is run in interactive mode. You are prompted for individual values 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. interactive By default, the prerequisite verification utility is run in interactive mode. If you do not specify the -mode parameter, the utility defaults to running in interactive mode. When started from the launchpad, the utility runs in interactive mode. silent If you use the silent qualifier, you can also use the input parameter and supply a property file. If an input file not provided, default property values are 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 is not 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. None Selecting this qualifier results in no trace information being generated while the utility is running. Verbose Selecting this qualifier results in detailed trace information being generated while the utility is running. Normal Selecting this qualifier results in default trace information being generated while the utility is running.
Syntax example: tpae_req_check.bat -component dbserver -trace None
Procedure 1. 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 middleware installation media is mounted or otherwise available to the system. This example procedure uses values found in the default tpae.properties file to verify that a system is suitable to host DB2 for a SmartCloud Control Desk deployment.
4 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 2. Open a command-line window and change directory to the SystemRequirements directory of the middleware installation media. 3. Run the prerequisite verification utility. Specify the component being checked and 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 the tpae_req_check.bat script. Results
After the prerequisite verification utility has completed successfully, results are printed to the screen. CTGIN8117I : The Tivoli Pre-requisite Scanner has been launched. CTGIN8118I : The Tivoli Pre-requisite Scanner exited with the return code IBM Prerequisite Scanner Version : 1.0.34 Build : 20101109 OS Name : Microsoft Windows Server 2003, Enterprise Edition Service Pack 2 User Name: Administrator
Machine Info Machine name : MYMACHINE Serial Number: KKKKKK0 OS Serial : 66666-666-6666666-66666
PAE [not defined] [version 07500000]: Property Result Found Exp... ======... os.totalPhysicalMemory PASS 2.00GB 1.90GB network.hasFQDN FAIL False True Disk#1 (C:\ibm\tivoli\mwi\workspace) PASS 27.99GB 300MB Disk#2 (C:\Temp\1) PASS 27.99GB 1000MB Disk#3 (C:\Temp\1) PASS 27.99GB 250MB network.availablePorts.db2 PASS 135,445,1025,2967,3389,5800,5900,139 50000 network.availablePorts.ctginst PASS 135,445,1025,2967,3389,5800,5900,139 50005 Disk#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: FAIL prereq_checker.bat 1
These values can also be redirected to a file when starting the command from the command line.
If any of the verification steps report a failure, resolve the issue and rerun the verification utility before installing SmartCloud Control Desk components.
Table 2 contains a list of the properties checked. Use this information to analyze prerequisite verification utility results. Table 2. Prerequisite verification utility properties Property Description CpuArchitecture Verifies the machine architecture is supported.
Chapter 1. Preparing for installation 5 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 installation program 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 availability You need to ensure that certain ports are available before using the product installation programs. About this task
You must check to see if ports are in use and accepting connections for the system you 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 already assigned before you run installation programs.
You can either use the prerequisite verification utility to check for port availability, or you can check manually.
6 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Procedure 1. 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 when prompted by the middleware installation program. “Programmatically verifying prerequisites” on page 2 You can use the prerequisite verification utility to verify that installation program prerequisites are present on a system. Use this utility before starting the middleware and product installation programs. Accessing system directories Before using the product installation programs, you need to assign access permission to particular directories. Before you begin
Before using the product installation programs, you need to assign access permission for the /tmp and /home directories on Linux systems. About this task
The user that starts the product installation programs requires read, write, and execute permissions for the /tmp and /home directories. If one of these directories uses a symbolic link, for example, /products/home, ensure that symbolic link directory also has the proper access. Procedure 1. 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 tar command requirements
Both the native UNIX tar command and the GNU version of the tar command are required by the middleware installation program. Because the native utility does not support long file names, ensure that GNU tar version 1.14 or higher is installed. GNU tar version 1.14 ensures that installation files can be extracted.
Verify that the system path variable contains both native UNIX tar and GNU tar paths. The GNU tar path must be defined before the native UNIX tar path. For example, the native tar utility is installed in /usr/bin and the GNU tar utility is installed in /opt/freeware/bin/tar.
If you have set a symbolic link to overwrite the native UNIX tar command with the GNU tar command an error occurs. http://www.ibm.com/systems/p/os/aix/linux/toolbox/download.html AIX font requirements AIX requires specific fonts in order to produce reports.
Chapter 1. Preparing for installation 7 About this task
When producing reports from AIX systems, TrueType fonts must be available on the system. Procedure 1. 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 descriptors For SmartCloud Control Desk to function correctly, you need to increase the default number of file descriptors allowed for the root user, and also set the maximum allowable file size to unlimited. About this task
To increase the allowable file size and number of allowable descriptors for the root user in AIX, complete the following steps: Procedure 1. 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 using the values listed. root: fsize = -1 nofiles = 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) unlimited file(blocks) unlimited data(kbytes) 2097152 stack(kbytes) 32768 memory(kbytes) unlimited coredump(blocks) 2097151 nofiles(descriptors) 8192 Increasing AIX paging space To successfully install and run SmartCloud Control Desk, you must increase the default paging space for the AIX system to a minimum of 4 GB, or, preferably, the total 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. Procedure 1. Determine the current amount of paging space available to the server by issuing the following command. lsps -a
8 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) This command results in output like the following sample output: 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 like the following sample information: LPs: 44 PP SIZE: 128 megabyte(s)
In the example output, there are a total of 44 Logical Partitions that are each 128 Mb in size. These results show a total of 5632 Mb of paging space available to the system. 3. Add more logical partitions, which are required in order to add more paging space, by issuing the following command: chps -s xx yyy
Where xx is the number of logical partitions to add and yyy identifies the logical volume. For example, chps -s 10 hd6
adds 10 logical partitions to the logical volume hd6, which results in adding 1280 Mb to the paging space. Verifying large page size support for AIX For SmartCloud Control Desk to function correctly, large page size support must be enabled on AIX servers hosting WebSphere® Application Server. About this task
If you are deploying SmartCloud Control Desk on WebSphere Application Server hosted on an AIX system, that system must be configured to support large page sizes.
Large page usage is primarily intended to provide performance improvements to high performance computing applications. Typically this feature is enabled by default on AIX systems. Procedure 1. Log on to the AIX system hosting WebSphere Application Server and open a console window. You must have root authority to work with the AIX operating system commands. 2. Verify large page size support by running the following command: ps -Z
Output from the command should include 4K and 64K page sizes listed for processes, for example: #ps-Z PID TTY TIME DPGSZ SPGSZ TPGSZ CMD 311342 pts/4 0:00 4K 4K 4K ksh 397526 pts/4 0:00 4K 4K 4K ps 487558 pts/4 0:00 64K 64K 4K sleep
Chapter 1. Preparing for installation 9 Enabling asynchronous I/O on AIX IBM Tivoli Directory Server requires asynchronous I/O be enabled on AIX systems. Without asynchronous I/O, DB2 and Oracle database instances cannot be started successfully. About this task
Enabling asynchronous I/O on AIX is an installation requirement, so this step must be run before running the middleware installation program. You only need to perform this step if the system hosts the IBM Tivoli Directory Server.
To turn on asynchronous I/O follow these steps: Procedure 1. 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 STATE to 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 Configure Defined Asynchronous I/O, and then click Enter. 8. Reboot the system to enable the changes. Checking for required libraries on Linux The SmartCloud Control Desk deployment requires certain Linux system libraries. Procedure 1. Locate the libstdc+.so.5 library in the /usr/lib/ directory. If this library is not installed, the middleware installation program throws an error when running the middleware installation program in graphical mode. If you cannot locate this library on your system, locate the RPM package for your system that contains this library and install the package. 2. Ensure that you have the libstdc++33-32bit-3.3.3-11.9.x86_64.rpm package installed before running the product installation program. SUSE Linux Enterprise Server 10 64-bit systems hosting manually configured middleware must host this package. 3. Ensure you have the compat-libstdc++ library installed on Red Hat Enterprise Linux v6 systems running the product installation program or the process solution installation program. Configuring the JRE in Linux In some cases, the middleware installation program fails on Red Hat Enterprise Linux 5 systems, or other systems with Security-Enhanced Linux (SELinux) enabled.
10 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) About this task
In one scenario, the middleware installation program fails with an error stating that 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: Procedure 1. 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 or disabled for a more permanent fix. This solution, however, affects the level of security for the entire system. Setting the ulimit This section details how to set the ulimit in Linux, which is used to define user system and process resource limits. About this task
For Linux systems, you must set the ulimit for the system before using the middleware 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 page 8. Procedure 1. From a command line, type ulimit -f unlimited 2. From a command line, type ulimit -n 8192 Setting the swap size SmartCloud Control Desk can be a resource-intensive application. Configure and tune your system for maximum performance. This section details how to set the size 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 in the server. See the product documentation for your Linux distribution for more information. For AIX systems, See “Increasing AIX paging space” on page 8.
Additional swap space can be made available to the system by:
Chapter 1. Preparing for installation 11 Procedure v increasing the size of the existing swap partition v creating a new, additional swap partition v creating a swap file Setting shared memory This 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 system before using the middleware installer.
To set the minimum shared memory value, complete the following steps: Procedure 1. 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 enablement The SmartCloud Control Desk installation program can automatically configure middleware. You must enable a remote access protocol for each system on which you intend to install the middleware.
Use SSH for logging on to and configuring remote Linux and UNIX systems. Use Windows SMB for logging on to and configuring remote Windows systems. Windows SMB is a Windows protocol. The IBM JRE on the administrative workstation includes SSH.
You do not need an SSH client to remotely configure middleware on Linux or UNIX systems. But, you must install OpenSSH on remote non-Windows workstations 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 remote servers with the protocols that you intend to use. Use the credentials that you plan to supply to the installation program.
For remote Windows systems, ensure that the following requirements are met before 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 Windows Administrators group. v The following Windows services must be started on the remote system before you begin a remote installation and configuration: – winmgmt (Windows Management Instrumentation) – RemoteRegistry (Remote Registry) – lanmanserver (Service)
12 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) v The SMB protocol must be enabled and configured to send NetBIOS over TCP/IP, by choosing to use port 139. Alternatively, you can configure SMB to use TCP/IP as the transport protocol, without NetBIOS, by configuring it to use port 445. v Ensure that any ports that you use for remote protocols are not blocked by firewalls or security policies, including ports 137 and 139. Port 139 is used if SMB is configured to run on NetBIOS over TCP/IP. Port 445 is used if SMB is run directly on TCP/IP, without NetBIOS. v To disable simple file sharing, start Windows Explorer. Click Tools > Folder Options, 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-protected sharing, disable password-protection. Shares must be shared for the Guest or Everyone accounts. v For Windows systems that have User Account Control (UAC) enabled, it must be 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 met before 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 it using the startsrc -s sshd command. v For AIX systems, set the TMOUT and TIMEOUT variables in the user profile script to 0. This setting prevents the user from idling out and being logged off the remote system during the installation. v The user name that you provide to the installation program must exist as a privileged account (for example, root) on the remote systems. v Ensure that a current version of OpenSSH is installed and running. Do not use OpenSSH 4.7.0.5302. v For Oracle Solaris systems, the remote access protocols require the use of internal shell scripts that must be run within the korn (ksh) shell. The methods need ksh, even if the user ID that you use to log on to the remote system is configured to use a different shell. Consequently, Oracle Solaris systems must have 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 or remote system. System password policy settings Be familiar with the password policies of systems you are using as part of a SmartCloud Control Desk deployment.
Chapter 1. Preparing for installation 13 Your organization might have password policy regulations enforced on systems on your network. Before deploying SmartCloud Control Desk, be sure that you are familiar with the password policies of systems used in the deployment, or you might experience errors during installation.
For example, Microsoft Windows Server 2008 systems have a stricter set of password requirements than previous versions configured by default. If you are not familiar with these stronger password requirements, you might experience an error during the installation of SmartCloud Control Desk. This error occurs when creating users on a Microsoft Windows Server 2008 system.
Password values that you provide during the SmartCloud Control Desk installation must be compliant with the password policies set for the target system. Passwords are not validated against the password policies of target systems at the time you enter them on the installation program panels. If your passwords do not conform to the password policies of systems used to deploy the product, errors occur when the installation program attempts to create these passwords during the configuration step, Backing up the Deployment Engine database These instructions are for backing up the Deployment Engine database. Backups are 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 applying any updates to an existing deployment. Use backups to recover from partial installation attempts. About this task
To back up the Deployment Engine database, complete the following steps: Procedure 1. Set up the environment using the following command: Windows c:\install_home\ctg_DE\acsi\setenv.cmd UNIX cd install_home/ctg_DE/acsi ./setenv.sh 2. Run the command to back up the Deployment Engine registry: Windows c:\install_home\ctg_DE\acsi\bin\backupdb.cmd backup file name UNIX cd 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 the state of the registry after your installation of SmartCloud Control Desk. For example, DEBackupAfterInstall. Specifying host name values Do not use localhost for host name values in the installation program. Specify the fully qualified host name or IP address of the system on which you are installing.
14 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) For Linux or UNIX systems, if the hostname -f command does not return a fully qualified host name, consult the system documentation for assistance. Establishing a fully qualified host name on Windows systems Use 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 the following steps.
Procedure 1. 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 hostnames You can force the use of alphanumeric host name use within the middleware installation program by starting it from the command line and using the forceHostname=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 using the forceHostname=true parameter, then you are required to provide an alphanumeric value in the Hostname field. An IP address results in an error message.
Launchpad The IBM SmartCloud Control Desk launchpad serves as a centralized interface for launching a collection of installation programs and product information.
The launchpad application assists you in choosing which product installation programs 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.
Chapter 1. Preparing for installation 15 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 middleware prerequisites. Ensure that you have the correct service pack levels for your environments and always use fully qualified domain names when entering values for the installation program. Starting the launchpad Use the following information to start the SmartCloud Control Desk launchpad Before you begin
Launchpad generated messages are captured in a hidden log frame while the launchpad is running. To show the log frame on the bottom of the launchpad panels, hold the CTRL key while simultaneously clicking the banner frame of the launchpad. Messages that are generated while the launchpad is running are not automatically saved on the hard disk drive. You can manually save the messages from a session by clicking Save at the bottom of the log frame and then specifying where you want to save the file. About this task
To start the IBM SmartCloud Control Desk launchpad, complete the following steps: Procedure 1. 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 the default browser on AIX is Firefox, it is likely that the launchpad program does not run properly due to the ksh shell interface. If you must use the launchpad 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/null LOGNAME=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
16 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 2. Deploy with automatic middleware configuration (Scenario 1)
Use this information to use product installation programs and tools to install and automatically configure a SmartCloud Control Desk deployment within your enterprise.
This information provides a high-level overview or road map of tasks you need to complete in order to deploy SmartCloud Control Desk with automatic middleware configuration.
In this scenario, you use the middleware installation program to install and automatically configure new instances of DB2 and IBM Tivoli Directory Server. You use the product installation program to perform further middleware configuration 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 the SmartCloud Control Desk installation program to automatically configure it.
Middleware installation program middleware deployment plan overview The deployment plan resides in the workspace directory and is generated from deployment choices selected in the middleware installation program.
The plan is a series of deployment steps and configuration parameters. Each step is responsible for installing and uninstalling one portion of the middleware. When deployment choices are changed, the existing deployment plan is deleted and replaced with the new deployment plan.
Installing middleware using the middleware installation program You use the middleware installation program to install middleware components for use with IBM SmartCloud Control Desk. The middleware components that you choose to install, and the associated configuration parameters, are recorded in a deployment plan for the target system. Before you begin v 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 install and configure middleware components on a single server. The single server deployment scenario is suitable for demonstration, test, or training purposes.
The following middleware components are installed: v DB2 v v Tivoli Directory Server
© Copyright IBM Corp. 2007, 2011 17 If you want to use Oracle WebLogic Server with SmartCloud Control Desk, you must install it separately or reuse an existing instance, and then configure it manually.
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 use the launchpad, the program files are copied to a temporary directory on the target system. When you use a setup script, no files are copied to the target system. If you are installing on a 64-bit Windows system, you must use a setup script to start the program. Procedure 1. Log in to the target system as a user with administrative authority. If you are running the middleware installation program from a Linux or UNIX terminal window, you must be logged in as the root user. 2. Start the middleware installation program by using the launchpad or a setup script. 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 the following command: launchpad.exe. Linux and UNIX From the root directory of the installation image or product media, 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 the middleware installation program: Windows launchpad\Install\MWIsetupwin.bat /l Linux and UNIX launchpad\Install\MWIsetupUNIX.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 installing the 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 the Hostname 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 the middleware installation program, select Use this password as the value for all subsequent passwords and enter the required password. 8. Specify the following details for DB2 Enterprise Edition Server: a. Specify the installation directory.
18 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) b. Specify administrative account details for the DB2 Administration Server. The password that you specify is also used as the password for the DB2 default database instance. c. If you are installing on a Linux or AIX system, specify fenced user account details for DB2. 9. Specify an instance name, port, and user name for the default database instance. 10. Specify an instance name, port, and user account details for the SmartCloud Control Desk database instance. 11. Specify names for the DB2 administrators and users groups. A users group name is required only if DB2 Enterprise Edition Server is installed on a Windows 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 country suffix that are required when the directory server is used with SmartCloud Control 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 whether you need to copy the SmartCloud Control Desk middleware installation 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. 16. Optional: Before you deploy, verify the integrity of the middleware installation images by selecting the option for checksum validation. If the checksum operation fails, click Back and recopy the images. If you do not select this option and the middleware installation images are corrupted or otherwise inaccessible from the directory specified, an error occurs. If you encounter this error, you must replace the corrupted middleware installation images and then restart the middleware installation program. 17. Specify a directory to use for middleware installation program temporary files and extracted middleware installation images. 18. Select Deploy the plan to confirm that you are ready to install and configure the selected middleware components. 19. Click Deploy to initiate the installation process. 20. When the deployment is complete, click Finish to close the installation wizard. Middleware installation program logs Middleware installation program log files are located in the workspace directory that was defined in the middleware installation program.
There are several types of log files.
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 19 User interface logs The logs generated by the middleware installation program user interface are located in the workspace directory. The middleware installation program logs all information in
20 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) machine plan are named MachinePlan_host name_processID. These log files contain the output generated by Apache ANT when running the machine plan ANT script. Logs for steps in the deployment plan Each step in the deployment plan is located in a directory named
As an example, the log file generated by the middleware installation program during DB2 installation on a UNIX system would be found in the following directory:
DB2 Installation Step
DB2 installation logs can be found in the following locations: DB2 base The following DB2 base log files can be found in the
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 21 v DB2_ESE_Register_DB_
22 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) If you encounter a failure wrapper failure, more information can be found in the $(_TempLocation) directory in the
DB2 Configuration Step
The following DB2 configuration logs can be found in
For Linux, including Linux on IBM System z®, the following additional files are produced: 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 following additional 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 logs can be found in
IBM Tivoli Directory Server Installation Step
IBM Tivoli Directory Server installation logs can be found in the following locations:
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 23 GSKIT The following IBM Tivoli Directory Server installation log files can be found in the
24 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) IBM Tivoli Directory Server fix pack The following IBM Tivoli Directory Server fix pack log files can be found in the
IBM Tivoli Directory Server Configuration Step
The following IBM Tivoli Directory Server configuration logs can be found in
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 25 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 following additional 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 group strings You can configure user and group strings in IBM Tivoli Directory Server to adapt it to your deployment needs. Before you begin About this task
You can manually create user and group strings for Tivoli Directory Server during installation.
If you configure directory server user and group strings for a system that hosts only the IBM Tivoli Directory Server , you must manually create properties in the input.properties file of the ITDS_CONFIGURATION step of the deployment plan. Procedure 1. Edit the input.properties file that is located in the directory server folder at: Workspace\machine name\deploymentPlan\MachinePlan_machine shortname\00006_ITDS_Configuration. For example, in Windows, the default
26 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) location 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\=US was_nd.secure.UserSuffix=ou\=users,ou\=SWG,o\=IBM,c\=US 3. If Tivoli Directory Server configuration parameters are customized, change the applicable values to your custom values on the configuration parameters panel. For example, if your custom values are ou=SWG1 and the Organization country suffix is o=IBM1,c=US1, you must manually replace all occurrences of those values in the input.properties file: was_nd.secure.GroupSuffix=ou\=groups,ou\=SWG1,o\=IBM1,c\=US1 was_nd.secure.UserSuffix=ou\=users,ou\=SWG1,o\=IBM1,c\=US1
Uninstalling middleware To uninstall IBM SmartCloud Control Desk middleware, you must run the middleware installation program and select the options to remove the previous deployment. Before you begin
If you chose to deploy SmartCloud Control Desk middleware with a directory server, ensure that it is active. About this task
The middleware installation program creates a registry when installing SmartCloud Control Desk middleware. Using the native middleware uninstall programs causes this registry to be out of sync with what is deployed. As a result, errors occur when you attempt to reinstall middleware with the middleware installation program. Procedure 1. Stop and start the following 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 Admin Server 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 Linux launchpad.sh AIX launchpad.sh
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 27 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. The default location for the workspace is the last workspace location specified. If you did not specify a path previously, the default location for the workspace isc:\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/tcp v db2c_db2inst1 50000/tcp
Reinstalling middleware with IBM DB2 You can run an installation of the middleware with the DB2 user and group settings from a previous installation. Before you begin
Remove all middleware products and their components before you reinstall the middleware. About this task
When DB2 is uninstalled, users and groups are not removed. You can specify the same DB2 user and group values or replace them with new users and groups when you run the installation program. Procedure 1. Verify that all middleware products were properly removed by examining the deployment plan log files. The log files are in the subdirectory Workspace Directory/host name/deploymentPlan/logs/processID. The primary log file for the deployment plan is DeploymentPlan.log. 2. The middleware installation program creates a default instance for DB2 and adds the owner of the default instance to the DB2 administrator group that you specify. Specify the DB2 users and groups that you want to use for this installation: 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 DB2 administrators group. 3. Start the middleware installation program from the launchpad.
Manually configuring WebLogic Server WebLogic Server can be used with SmartCloud Control Desk if it is manually configured.
28 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) About this task
You can use a WebLogic Server as your J2EE server. The SmartCloud Control Desk installation process prepares EAR files on the SmartCloud Control Desk administrative workstation. These files are then manually deployed to your WebLogic Server. The SmartCloud Control Desk installation program does not automatically configure a WebLogic Server environment It does not install or otherwise deploy SmartCloud Control Desk applications into a WebLogic Server server.
Manually configuring WebLogic Server consists of the following tasks: Procedure 1. “Creating the MAXIMOSERVER domain” 2. “Configuring JMS options for integration framework” on page 30 3. “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 WebLogic Server. About this task
To create the MAXIMOSERVER domain within WebLogic Server, complete the following steps: 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
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 29 7. Proceed through the next few panels until you reach the Customize Environment and Services Settings panel. From the Customize Environment and Services Settings panel, select the default option No, and then click Next. 8. From the Create WebLogic Server Domain panel, change the Domain Name value to MaximoServer, and then click Create to create the domain. 9. Once the domain has been created, ensure that the Start Admin Server option is cleared, and then click Done to close the Configuration wizard. On UNIX systems, this option is not displayed. Configuring JMS options for integration framework This procedure provides details on steps to configure JMS queues. Before you begin
You need to be familiar with the Oracle WebLogic Server Administration Console to complete the following procedure. See your Oracle WebLogic Server documentation on how to navigate through the Oracle WebLogic Server Administration Console. Procedure 1. 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 to create database-based stores. To choose between file stores and database-based stores, 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 servers to a value of 20% or below of the allotted JVM heap size to prevent the Oracle WebLogic Server from running out of memory. 5. Create a JMS system module named intjmsmodule with MAXIMOSERVER as the target server. 6. Add a connection factory resource to the JMS module:
Option Description Name intjmsconfact JNDI Name jms/maximo/int/cf/intcf Target MAXIMOSERVER
7. Add three queue resources to the JMS Module:
30 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 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 to take effect. Configuring JMS for the email listener in WebLogic Server
About this task
You use the email listeners application to receive and process requests through email in the form of email messages.
To configure JMS queues for the WebLogic Server, complete the following steps: Procedure 1. Log in to the WebLogic Server administration console. 2. Create a persistent store. a. In the Domain Structure panel, expand Services and then click Persistent Stores. 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 JMS Servers, enter the following information, and then click Next. Name Enter a name for a new JMS server, for example, lsnrserver. Persistent Store Select lsnrstore. b. For the Target, select AdminServer, and then click Finish. 4. Create a JMS System Module
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 31 a. In the Domain Structure panel, under Services > Messaging , click JMS Modules, and then click New. b. Enter a value for the Name field, such as lsnrjmsmodule, and then click Next. 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, click New 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 Name Enter 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 Name Enter jms/mro/lsnr/qin. Template No template is necessary. d. Click Create a new Subdeployment, select lsnrserver, and then click Finish. 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 from sections within the deployment descriptor files. Edit the ejb-jar.xml and weblogic-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 then save the file: Email Listener JMS is not deployed by default
32 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) transaction-type>Container
Installation program overview The SmartCloud Control Desk installation program provides an interface for installing and deploying SmartCloud Control Desk, which includes the process automation engine and process managers.
The SmartCloud Control Desk installation program records choices you make about your SmartCloud Control Desk deployment and configuration parameters associated with those choices, and then installs and deploys SmartCloud Control Desk based upon the information you entered.
There are two installation paths available to you when installing SmartCloud Control Desk. Simple A simple deployment consists of installing SmartCloud Control Desk middleware on one system. You do not have the option of using existing middleware within your organization with SmartCloud Control Desk. All middleware used with SmartCloud Control Desk must have been installed on the system using the middleware installation program using default values. SmartCloud Control Desk is installed using default values provided by the middleware installation program and SmartCloud Control Desk installation program. If you intend to override default values used by the simple deployment path, you must use the custom deployment path instead. If you are deploying using Oracle WebLogic Server, you cannot choose this option. Custom A custom deployment typically involves deploying SmartCloud Control
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 33 Desk across several systems, some of which might already host middleware products that you want to use with your SmartCloud Control Desk deployment. Deploying using the custom installation path also allows you to modify default installation values. This deployment option does not require you to spread the SmartCloud Control Desk deployment across several systems. You can enter the name of the local host as the destination for all SmartCloud Control Desk components that are installed using the middleware installation program and the SmartCloud Control Desk installation program. If you are deploying using Oracle WebLogic Server, you must choose this option.
The SmartCloud Control Desk installation program can automate the configuration of some middleware for use with SmartCloud Control Desk. It cannot automate the configuration of Oracle WebLogic Server. If you choose not to have the SmartCloud Control Desk installation program automatically configure middleware, you must configure that piece of middleware manually before the installation of SmartCloud Control Desk.
Important: When entering LDAP values for SmartCloud Control Desk installation panel fields, entries in LDIF files, or values you enter directly into a directory instance using the directory server tools, be aware of the product-specific syntax rules for using special characters in an LDAP string. In most cases, special characters must be preceded by an escape character in order to make it readable by the directory server. Failing to escape special characters contained in an LDAP string used with SmartCloud Control Desk results in SmartCloud Control Desk errors.
Many directory server products consider a blank space as a special character that is part of the LDAP string. If you mistakenly enter an LDAP string that contains a blank, at the end of a field value, for example, and you do not precede the blank character with an escape character, you encounter SmartCloud Control Desk errors that are difficult to troubleshoot.
See the product documentation for your directory server for more information about special characters in LDAP strings.
Information that you enter into the SmartCloud Control Desk installation program is stored in the maximo.properties and install.properties files and the Maximo® database. These values are populated into the panel fields of the SmartCloud Control Desk installation program on subsequent uses of the program. If you cancel the installation program after entering values across several installation panels, the installation program recalls most values the next time you start the SmartCloud Control Desk installation program. Values excluded from being saved in this manner are the SmartCloud Control Desk installation directory and the shortcut option chosen during the installation. You can restore the default values in the SmartCloud Control Desk installation program by deleting
34 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Installing the product and automatically configuring middleware To install SmartCloud Control Desk, you run the installation program from the launchpad. The installation procedure automatically configures middleware on multiple 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 during deployments on IBM WebSphere Application Server Network Deployment. v On the administrative workstation, temporarily shut down any noncritical processes that can have a negative effect on the installation, such as antivirus software. v Ensure that the Windows DEP setting does not prevent the launchpad from running: Select Start > Settings > Control Panel > System > Advanced > Performance > Settings > Data Execution Prevention. Select Turn on DEP for essential Windows programs and services only and click Apply. You might be asked 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 the documentation for your operating system. Alternatively, you can provide the IP address for the system. v Enable a remote execution and access service on every system that has middleware installed. Each remote system must support a remote access protocol. It must also accept remote logins from a user name and password that were configured on the target server. Remote access protocols include SSH and Windows SMB. If the remote system is a Windows server, you must configure remote 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 product installation program. See the DB2 product documentation for information about creating a user with SYSADM authority on the DB2 server. You must add 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 program when installing on AIX 6.x systems remotely, reattempt the installation locally. Use the console or an X terminal on the system locally.
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 35 Procedure 1. 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 downloaded installation image, and run the following command: Windows launchpad.exe UNIX launchpad.sh If the launchpad does not start the installation, you can start the product installation program directly. On the downloaded installation image, browse to \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 v install_linux64.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 for differentiating between multiple installations that are hosted on the same administrative workstation. 5. Review the information that is on the Verify Installation Location panel. The panel shows any previous installation information that was found based on the installation directory that you specified on the previous panel. After you advance past this panel, you cannot go back and change the installation directory for this installation. If a more recent version of the installation program is found in the specified target directory, you are notified. The notification means that you are using an older version of the installation program. The version found on the administrative workstation is newer and can contain important features and enhancements. To use the newer version of the installation program, select the option on the notification panel and click Next. This action exits the current installation process and restarts the installation process with the newer installation program. If you do not select the option, you continue the installation 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 the system. Target package version information indicates the package version being currently deployed. 7. On the Choose Deployment panel, specify Simple or Custom as the deployment type. 8. On the Import Middleware Configuration Information panel, you select Import middleware configuration information to have the product installation program reuse the middleware installation program values. These values are used as default values for the same fields in the product installation program.
36 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) The Workspace location field refers to the location of the topology file that contains the values that were specified for the middleware installation program. The file is located in the workspace that was defined during the middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for Windows or /root/ibm/tivoli/mwi/workspace for UNIX. If you selected the simple deployment, the middleware default information is not used. 9. On the Database Type panel, specify DB2, Oracle, or Microsoft SQL Server as the software to use for the Maximo database. 10. On the Database panel, specify configuration information for your database software. For things such as the database user ID, the database name, the database instance for SmartCloud Control Desk, and the schema name, if the values do not 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 for DB2 and Oracle cannot contain spaces. For DB2, the database instance is created if it does not exist, but the user and its 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 are defined or it can be a different value, such as maximo. After you specify configuration information for your database software, the installation program validates the information with the database server. 11. On the Automate Database Configuration panel, you can specify that database creation 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 information for the automatic database configuration feature. Specifying the values enables remote configuration. 13. On the Database Administration panel, specify configuration information about the database. The required information varies by database platform. For DB2, the instance administrator user ID cannot be the same as the database user ID. And the Windows service user ID must have administrative authority on the system. 14. On the Database Tablespace panel, specify information about the table space of the database. When you click Next, the product installation program connects to the database server and validates the information that you specified. 15. When the database validation is complete, on the Application Server Type panel, specify Oracle WebLogic Server for the product deployment. You must manually configure WebLogic Server and manually deploy application files. 16. On the Specify Maximo Users panel, enter Maximo database user information. Maximo administration user The product administrator user ID that is used for initial configuration and adding users. Maximo system registration user The user ID that is used for the self-registration of users. Maximo system integration user The user ID that is used with enterprise adapters.
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 37 Custom user ID and password values are stored in the Maximo database. The default user IDs of maxadmin, maxreg, and maxintadm are also created as users in the Maximo database. Creation of the default user IDs is done for internal processing purposes. If you use Maximo database security for authentication and authorization, the default user IDs can be used to log in to the application. If you regard this condition as a security risk, you can modify the passwords for the default user IDs. You modify passwords for the user IDs in the Users application. 17. On the SMTP Configuration panel, specify the SMTP configuration information that is used by workflows to communicate with workflow participants. The administrator e-mail address is the e-mail address that is used to send messages. If you leave the fields blank, you must configure the SMTP parameters through the product interface as a post-installation task. 18. On the Data Integration and Context Menu Services Options panel, click the button that indicates where the database tables for these functions should be created: in the Maximo ("same") database, or in a separate database instance that you have already created for this purpose. If you are installing the Entry edition, choose the Maximo database. These tables will be created but will not be used by the Entry edition. 19. On the Base Language Selection panel, specify the base language for the installation. 20. On the Additional Language Selection panel, you can optionally specify one or more additional languages that the installation is to support. 21. On the Run Configuration Step panel, specify how to perform the configuration step of the installation. If you do not select an option, the configuration step proceeds when you click Next. Copy files now, but perform the installation configuration step later Select this option to copy files from the installation source to the administrative workstation. You must perform the configuration step at a later time to complete the deployment.
Important: Do not install another product before completing the configuration step of the original installation. Installing another product before running the configuration step for this installation overwrites the taskstore, which prevents the original installation from ever being deployed. The configuration values that you specify are stored in the install_home\maximo\applications\maximo\properties\ maximo.properties and install_home\etc\install.properties files. You run the configuration steps outside of the product installation program by using the taskrunner utility, in the install_home\scripts directory. Run the taskrunner utility from the command line. install_home\scripts\taskrunner [CONTINUE
The taskrunner uses the configuration values that are stored in the maximo.properties and install.properties files to configure SmartCloud Control Desk. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner continues despite errors. If you run taskrunner with the STOPONERROR parameter, the taskrunner stops when it encounters an error. If you used STOPONERROR, you can rectify the conditions that caused the error. You can then resume the installation at the point
38 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) where the last successfully completed task was recorded in the previous attempt by starting taskrunner with the CONTINUE parameter. Defer the update of the Maximo database Select this option if you want to manually run the database update task for the product deployment. This option can be used when there is a fix pack available that addresses known issues with the updatedb script. In this scenario, you choose the Defer the update of the Maximo database option, apply the fix pack, and then run the updatedb -v1 command manually. 22. On the Choose Shortcut Folder panel, specify where you want SmartCloud Control Desk icons created. If you select In the Start Menu and use Internet Explorer, add the SmartCloud Control Desk URL to the trusted sites web content zone. Disable the option that requires server verification for all sites in the zone. Do not select In the Quick Launch Bar. The selection does not create a shortcut in the Quick Launch bar. Attention: Shortcuts are created for Windows systems only. Because WebLogic Server deployments are a manual process, you must manually update any shortcuts that you create. You update shortcuts after you have manually deployed the SmartCloud Control Desk EAR files. 23. On the Input Summary panel, review the information that you have provided for the 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 by viewing the messages that are displayed above the progress bar. 25. On the Installation Completed panel, review any information presented, then click Done. Attention: In some cases, on AIX systems, the Installation Completed panel might appear blank. Click Done to exit the installation program. “Restarting middleware on Windows” on page 169 This procedure describes how to restart middleware on Windows, if you must restart any middleware services. “Restarting middleware on UNIX” on page 170 Middleware services on Linux and AIX platforms occasionally must be restarted, such as when a reboot occurs. Middleware servers and services must be active before running the SmartCloud Control Desk installation program. Installing optional content Install the relevant optional content package for your edition of the product.
Optional content is often used in development environments as a way to begin developing your own content.
If you do not install optional content during the product installation process, you can install it later. If you install it later, you must update the database and rebuild and deploy the maximo.ear file.
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 39 Installing optional integration modules Install integration module packages in order to set up integrations with other products.
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 database and rebuild and deploy the maximo.ear file.
Post installation for Oracle WebLogic Server deployments There 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 SmartCloud Control Desk deployment, the installation program produces an EAR file. You must then manually deploy that file to Oracle WebLogic Server.
When using Oracle WebLogic Server, you must modify the weblogic.xml file and rebuild the maximo.ear file before deploying it. Procedure 1. 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 the server where you installed Oracle WebLogic Server. Use any file transfer protocol that is available. b. The oraclethin.jar file is in the install_home\maximo\applications\ maximo\lib directory. The default install_home directory is C:\IBM\SMP\Maximo\Applications\Maximo\lib. Copy the oraclethin.jar file to the J2EE server and into the wls11g/server/lib directory. For example, C:/Oracle/wls11g/server/lib. 3. Edit the domain configuration file for proper 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. Two instances 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)
40 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Note: This step is required for connecting to Oracle databases from Oracle WebLogic Server. e. Increase the Java Heap parameters by searching for MEM_ARGS and setting the 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 (-) sign before each parameter and to include the m after each value. f. Search for set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES%. Insert an option right after this string as follows: -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
The entry looks like this 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:
The user name and password values must match an existing user account in the Authentication provider for the default security realm. If you save the file as boot.properties and locate it in the mydomain folder (for example, C:\BEA\User_projects\domains\mydomain), the server automatically uses this file during its subsequent startup cycles. The first time you use this file to start a server, the server reads the file and then overwrites it with an encrypted version of the user name and password. 6. Verify settings by starting Oracle WebLogic Server. To ensure that the edits that you made to the previous Oracle WebLogic Server files were accurate, start the Oracle 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 files You are now ready to deploy the EAR files from the Oracle WebLogic Server Administration Console. Deploying the EAR files starts the Maximo Application Server.
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 41 Before you begin
Windows Windows If MAXIMOSERVER is not running, start it from a command prompt.
UNIX UNIX Ensure that the Oracle WebLogic Server daemon is running. About this task
In order to view the Oracle WebLogic Server Administration Console, you need to also install a Java Virtual Machine (JVM). Newer versions of Windows might not ship with JVM. Procedure 1. Change to the my_domain directory:
Windows Windows From a command prompt, change directory path to: drive_name:\weblogic_install_dir\user_projects\domain\my_domain
UNIX UNIX Open a Terminal window (or a command prompt, if you are telneting from a Windows computer) and change directory as follows: cd /home/mxadmin/weblogic_install_dir/user_projects/domains/my_domain 2. Type
Windows Windows startWebLogic.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 by typing 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 and password. 5. In the left pane, click the Lock&Edit button in the Change Center section to set the server to edit mode. 6. In the left pane, 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 “Install this deployment as an application” and click Next to continue the deployment.
42 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 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 42 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 name Setting the Oracle WebLogic Server host name manually to access application help information. About this task
By default, the property used to store the host name for the SmartCloud Control Desk help system is set to localhost. The fully qualified host name of the Oracle WebLogic Server must be configured in the help system property to view SmartCloud Control Desk application help topics. Complete this step after you have deployed SmartCloud Control Desk EAR files to the Oracle WebLogic Server. Procedure 1. 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 Desk user interface.
Language deployment after database update deferral Selecting the option to defer the update of the Maximo database when installing the product, affects how you deploy languages.
During installation, you have the option to defer the database update task. This option prevents writing data to the database during the installation. The installation program is limited to copying files to the administrative system and registering product process solution packages. You add languages by completing the installation, manually updating the database, and then updating languages manually.
Chapter 2. Deploying with automatic middleware configuration (Scenario 1) 43 “Manually deploying languages after database update deferral” Languages must be deployed manually if you defer database updates by the installation program. Manually deploying languages after database update deferral Languages must be deployed manually if you defer database updates by the installation program. Before you begin
You must have run updatedb command before manually configuring languages for PSI packages. About this task
To manually configure languages for PSI packages, complete the following steps: Procedure
Update language support for the Maximo core components. Files for the language selections you made during the installation are extracted to the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory on the system. 1. 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 2. To add one or more languages as additional languages for use with the product, run the following command for each language you want to add: install_home\maximo\tools\maximo\TDToolkit.bat -ADDLANGlocale -maxmessfix
44 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 3. Deploying automatically reusing existing middleware (Scenario 2)
Use this information to use SmartCloud Control Desk installation programs and tools to automatically configure existing middleware within your enterprise during the SmartCloud Control Desk deployment process.
This information provides a high-level overview or road map of tasks you need to complete in order to deploy SmartCloud Control Desk automatically. You use middleware already established in your enterprise.
In this scenario, you use the middleware installation program and the SmartCloud Control Desk installation program to automatically configure existing middleware resources. Middleware configuration is performed automatically before deploying the product. Oracle WebLogic Server must always be configured manually. The installation programs are used to automatically configure an existing DB2 server in your environment.
Figure 1. Deploying SmartCloud Control Desk reusing existing middleware
Run the middleware installation program on existing middleware servers If you intend to reuse existing middleware servers with SmartCloud Control Desk, they must be configured before running the SmartCloud Control Desk installation program.
This section contains information about configuring existing DB2, IBM Tivoli Directory Server and Microsoft Active Directory servers for use with SmartCloud Control Desk using the middleware installation program. You cannot use the middleware installation program to configure existing Oracle, Oracle WebLogic Server, or Microsoft SQL Server.
Ensure that all of your middleware is at supported levels for SmartCloud Control Desk.
When installing and configuring middleware in the middleware installation program and the SmartCloud Control Desk installation program, consider the following special characters restrictions:
© Copyright IBM Corp. 2007, 2011 45 Table 3. Middleware object naming conventions Naming Convention Details DB2 naming conventions for Group names, Group names and user IDs on Linux and user names, and user IDs. UNIX operating systems can contain up to 8 characters and must consist of lowercase characters only.
Group names and user names on Windows can contain up to 30 characters.
Names and IDs cannot be any of the following values: USERS, ADMINS, GUESTS, PUBLIC, LOCAL, or any SQL-reserved word.
Names and IDs cannot begin with IBM, SQL or SYS. They must also not begin with the underscore (_) character. DB2 naming conventions for DB2 instances. Instance names can have up to 8 characters.
On Windows, no instance can have the same name as a service name. DB2 naming conventions for passwords. For UNIX systems, passwords can be a maximum of 8 characters.
For Windows systems, passwords can be a maximum of 14 characters. IBM Tivoli Directory Server conventions for Database names must be unique within the databases and database aliases. location in which they are cataloged. For Linux and UNIX , this location is a directory path. For Windows it is a logical disk.
Database alias names must be unique within the system database directory. When a new database is created, the alias defaults to the database name. As a result, you cannot create a database using a name that exists as a database alias, even if there is no database with that name.
Database and database alias names can have up to 8 characters.
Be mindful that the special characters @, #, and $ are not common to all keyboards. Avoid these characters when creating a database name.
46 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 3. Middleware object naming conventions (continued) Naming Convention Details IBM Tivoli Directory Server conventions for Values must not be longer than 8 characters. users, groups, databases, and instances 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, a through z, and 0 through 9.
Values must begin with characters A through Z or a through z.
Double-byte characters cannot be used in administrator passwords values.
Passwords cannot contain the following special characters:`'\"| The middleware installation program The middleware installation program does not validate that your password is compliant with the operating system of the target host. Ensure that the password values you provide are valid for your environment.
The middleware installation program does not allow the use of the '%' character on Windows and the use of the !, $, #, % characters on UNIX.
The middleware installation program does not check for accented characters in user name values. The use of accented characters can cause errors.
Configuring an existing DB2 with the middleware installation program An existing DB2 server can be configured using the middleware installation program. Before you begin
If you plan to configure an existing DB2 server with the middleware installation program, a set of users and groups must exist. These users and groups are used by the middleware installation program during configuration.
Default values for users and groups include: Users v db2admin v dasusr1 (UNIX) v db2fenc1 (UNIX) Groups
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 47 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 if the values provided to the middleware installation program match the values found on the system. Again, if these users do not exist on the system, you must create them before running the installation program. About this task
If you have an existing DB2 installation that you would like to reuse for SmartCloud Control Desk, you can run the middleware installation program on the system to configure it. The middleware installation program identifies instances of middleware that exist on the system that are compatible with SmartCloud Control Desk, and it configures the existing instance for use with SmartCloud Control Desk.
To have the middleware installation program configure an existing DB instance for reuse with SmartCloud Control Desk, complete the following steps: Procedure 1. 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 DB2 found on the system. 5. From the Installation menu, select the appropriate instance to reuse, and then click Next. 6. Complete the remainder of the middleware installation program panels. “Installing middleware using the middleware installation program” on page 17 You use the middleware installation program to install middleware components for use with IBM SmartCloud Control Desk. The middleware components that you choose to install, and the associated configuration parameters, are recorded in a deployment plan for the target system. Verifying an existing IBM Tivoli Directory Server using the middleware installer If you have an existing IBM Tivoli Directory Server installation that you would like to reuse for SmartCloud Control Desk, you can verify that it works with SmartCloud Control Desk using the middleware installer. About this task
The middleware installer validates the following items: v The version of IBM Tivoli Directory Server is compatible with SmartCloud Control Desk. v The IBM Tivoli Directory Server is running.
48 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) v The Base DN information that you supply in the middleware installer panels are present in the IBM Tivoli Directory Server you are using. The middleware installer does not create an instance of IBM Tivoli Directory Server for use with SmartCloud Control Desk. If you want to reuse an existing instance of IBM Tivoli Directory Server, supply the correct Administrator Distinguished Name and password, LDAP BASE DN, directory server port, and the administration port information for that instance on the middleware installer panels when prompted. If you intend to host a new instance on your existing IBM Tivoli Directory Server, you must create it before running the middleware installer.
Note: While you can technically share a DB2 instance between SmartCloud Control Desk and the one required by IBM Tivoli Directory Server, it is not a recommended practice. During the installation, the database instance is restarted, which could disrupt the availability of IBM Tivoli Directory Server in your enterprise. If you are using the automated installers, separate instances are created for use by SmartCloud Control Desk and IBM Tivoli Directory Server.
To have the middleware installer verify an existing instance of IBM Tivoli Directory Server for reuse with SmartCloud Control Desk, complete the following steps. Procedure 1. Log in to the system as a user with administrative authority. 2. Start the middleware installer from the product launchpad. 3. Navigate the middleware installer panels up to the point where you reach the deployment choices panel. 4. In the deployment choices panel, select Directory Server, and then click Next. The middleware installer displays any instances of IBM Tivoli Directory Server discovered on the system. 5. In the Installation menu, select the appropriate instance to reuse, and then click Next. 6. Complete the installation by navigating the rest of the middleware installer panels. “Manually configuring the directory server” on page 79 These topics provide details on manually configuring a directory server for use by SmartCloud Control Desk “Installing middleware using the middleware installation program” on page 17 You use the middleware installation program to install middleware components for use with IBM SmartCloud Control Desk. The middleware components that you choose to install, and the associated configuration parameters, are recorded in a deployment plan for the target system. Preparing Microsoft Active Directory for reuse The middleware installation program can be used to validate Microsoft Active Directory configuration information. Before you begin
Before running the installation program, manually create the users. You can perform this task after you run the middleware installation program, but you must complete it before you run the SmartCloud Control Desk installation program.
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 49 About this task
The middleware installation program prompts you for LDAP configuration parameters.
To validate Microsoft Active Directory configuration information using the middleware installation program use, complete the following steps: Procedure 1. Log in as a user with administrative authority. 2. Start the middleware installation program from the launchpad. 3. Proceed through the middleware installation program panels until you reach the Deployment Choices panel. 4. From the Deployment Choices panel, clear the Directory Server deployment option, and then click Next. In the next panel, you are given the choice of selecting an existing instance of IBM Tivoli Directory Server or Microsoft Active Directory. 5. In the Deployment Plan Summary window, click Next to configure parameters. The deployment plan is generated and you are provided details about the plan. 6. In the Configurable Host Name panel, you can manually specify the host name of the system you are running the installation from. Select the Override the local machine hostname option and enter a host name value in the Hostname field. Select this option only if you want to manually specify the host name of the system instead of having the installation program programmatically detect it. This option is useful when there is more than one host name assigned to the system. This configuration occurs when a system has more than one network interface, or it is configured to support virtual IP addresses. When this option is selected, you are required to provide a resolvable host name. You cannot clear this option after it has been selected. However, you can still change the value of the Hostname field. If you started the middleware installation program from the command line using the forceHostname=true parameter, then you are required to provide an alphanumeric value in the Hostname field. Use of an IP address causes error message. When this option has been selected, you are not able to clear it. However, you can change the value you enter in the Hostname field. 7. In the password reuse panel, you can optionally select Use this password as the value for all subsequent passwords. This option allows you to use the same password as the default user password value in all panels of the middleware installation program. If you do not want to use this option, ignore the Use this password as the value for all subsequent passwords option, and click Next. 8. Select Secure with Microsoft Active Directory, and click Next. 9. Configure the following values for security, and then click Next. LDAP Host name Enter the fully qualified name of the server hosting Microsoft Active Directory. LDAP base entry Enter the LDAP base entry of the instance. For example, DC=ism75,DC=com
50 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) User suffix Enter the user suffix for the instance. For example, OU=Users,OU=SWG,DC=ism75,DC=com Group suffix Enter the group suffix for the instance. For example, OU=Groups,OU=SWG,DC=ism75,DC=com Organization container suffix Enter the organization container suffix for the instance. For example, DC=ism75,DC=com In this example. ism75 is the domain name. You must replace ism75 with the name of your own domain. 10. Supply the following configuration values for security, and then click Next. Bind distinguished name Enter the bind distinguished name for the instance. For example, CN=Administrator,CN=Users,DC=ism75,DC=com This value assumes that the Administrator user is already a member of the ism75 domain. You must replace ism75 with the name of your own domain. Bind password Enter the password for the Administrator user on the system hosting Microsoft Active Directory. 11. Finish the installation by completing the remainder of the middleware installation program panels. “Installing middleware using the middleware installation program” on page 17 You use the middleware installation program to install middleware components for use with IBM SmartCloud Control Desk. The middleware components that you choose to install, and the associated configuration parameters, are recorded in a deployment plan for the target system. “Manually configuring Microsoft Active Directory” on page 83 You can manually configure Microsoft Active Directory for use with SmartCloud Control Desk.
Manually configuring WebLogic Server WebLogic Server can be used with SmartCloud Control Desk if it is manually configured. About this task
You can use a WebLogic Server as your J2EE server. The SmartCloud Control Desk installation process prepares EAR files on the SmartCloud Control Desk administrative workstation. These files are then manually deployed to your WebLogic Server. The SmartCloud Control Desk installation program does not automatically configure a WebLogic Server environment It does not install or otherwise deploy SmartCloud Control Desk applications into a WebLogic Server server.
Manually configuring WebLogic Server consists of the following tasks:
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 51 Procedure 1. “Creating the MAXIMOSERVER domain” on page 29 2. “Configuring JMS options for integration framework” on page 30 3. “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 WebLogic Server. About this task
To create the MAXIMOSERVER domain within WebLogic Server, complete the following steps: 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
52 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Before you begin
You need to be familiar with the Oracle WebLogic Server Administration Console to complete the following procedure. See your Oracle WebLogic Server documentation on how to navigate through the Oracle WebLogic Server Administration Console. Procedure 1. 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 to create database-based stores. To choose between file stores and database-based stores, 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 servers to a value of 20% or below of the allotted JVM heap size to prevent the Oracle WebLogic Server from running out of memory. 5. Create a JMS system module named intjmsmodule with MAXIMOSERVER as the target server. 6. Add a connection factory resource to the JMS module:
Option Description Name intjmsconfact 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
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 53 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 to take effect. Configuring JMS for the email listener in WebLogic Server
About this task
You use the email listeners application to receive and process requests through email in the form of email messages.
To configure JMS queues for the WebLogic Server, complete the following steps: Procedure 1. Log in to the WebLogic Server administration console. 2. Create a persistent store. a. In the Domain Structure panel, expand Services and then click Persistent Stores. 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 JMS Servers, enter the following information, and then click Next. Name Enter a name for a new JMS server, for example, lsnrserver. Persistent Store Select 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 JMS Modules, and then click New. b. Enter a value for the Name field, such as lsnrjmsmodule, and then click Next. 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, click New to add a resource. b. Select the Connection Factory option, and then click Next.
54 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 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 Name Enter 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 Name Enter jms/mro/lsnr/qin. Template No template is necessary. d. Click Create a new Subdeployment, select lsnrserver, and then click Finish. 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 from sections within the deployment descriptor files. Edit the ejb-jar.xml and weblogic-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 then save the file: Email Listener JMS is not deployed by default
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 55 Email Listener JMS is not deployed by default
Installation program overview The SmartCloud Control Desk installation program provides an interface for installing and deploying SmartCloud Control Desk, which includes the process automation engine and process managers.
The SmartCloud Control Desk installation program records choices you make about your SmartCloud Control Desk deployment and configuration parameters associated with those choices, and then installs and deploys SmartCloud Control Desk based upon the information you entered.
There are two installation paths available to you when installing SmartCloud Control Desk. Simple A simple deployment consists of installing SmartCloud Control Desk middleware on one system. You do not have the option of using existing middleware within your organization with SmartCloud Control Desk. All middleware used with SmartCloud Control Desk must have been installed on the system using the middleware installation program using default values. SmartCloud Control Desk is installed using default values provided by the middleware installation program and SmartCloud Control Desk installation program. If you intend to override default values used by the simple deployment path, you must use the custom deployment path instead. If you are deploying using Oracle WebLogic Server, you cannot choose this option. Custom A custom deployment typically involves deploying SmartCloud Control Desk across several systems, some of which might already host middleware products that you want to use with your SmartCloud Control Desk deployment. Deploying using the custom installation path also allows you to modify default installation values. This deployment option does not require you to spread the SmartCloud Control Desk deployment across several systems. You can enter the name of the local host as the destination for all SmartCloud Control Desk components that are installed using the middleware installation program and the SmartCloud Control Desk installation program. If you are deploying using Oracle WebLogic Server, you must choose this option.
56 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) The SmartCloud Control Desk installation program can automate the configuration of some middleware for use with SmartCloud Control Desk. It cannot automate the configuration of Oracle WebLogic Server. If you choose not to have the SmartCloud Control Desk installation program automatically configure middleware, you must configure that piece of middleware manually before the installation of SmartCloud Control Desk.
Important: When entering LDAP values for SmartCloud Control Desk installation panel fields, entries in LDIF files, or values you enter directly into a directory instance using the directory server tools, be aware of the product-specific syntax rules for using special characters in an LDAP string. In most cases, special characters must be preceded by an escape character in order to make it readable by the directory server. Failing to escape special characters contained in an LDAP string used with SmartCloud Control Desk results in SmartCloud Control Desk errors.
Many directory server products consider a blank space as a special character that is part of the LDAP string. If you mistakenly enter an LDAP string that contains a blank, at the end of a field value, for example, and you do not precede the blank character with an escape character, you encounter SmartCloud Control Desk errors that are difficult to troubleshoot.
See the product documentation for your directory server for more information about special characters in LDAP strings.
Information that you enter into the SmartCloud Control Desk installation program is stored in the maximo.properties and install.properties files and the Maximo database. These values are populated into the panel fields of the SmartCloud Control Desk installation program on subsequent uses of the program. If you cancel the installation program after entering values across several installation panels, the installation program recalls most values the next time you start the SmartCloud Control Desk installation program. Values excluded from being saved in this manner are the SmartCloud Control Desk installation directory and the shortcut option chosen during the installation. You can restore the default values in the SmartCloud Control Desk installation program by deleting
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.
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 57 v The /tmp and /var/tmp directories must be present on the system. The installation program depends on these directories for information during deployments on IBM WebSphere Application Server Network Deployment. v On the administrative workstation, temporarily shut down any noncritical processes that can have a negative effect on the installation, such as antivirus software. v Ensure that the Windows DEP setting does not prevent the launchpad from running: Select Start > Settings > Control Panel > System > Advanced > Performance > Settings > Data Execution Prevention. Select Turn on DEP for essential Windows programs and services only and click Apply. You might be asked 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 the documentation for your operating system. Alternatively, you can provide the IP address for the system. v Enable a remote execution and access service on every system that has middleware installed. Each remote system must support a remote access protocol. It must also accept remote logins from a user name and password that were configured on the target server. Remote access protocols include SSH and Windows SMB. If the remote system is a Windows server, you must configure remote 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 product installation program. See the DB2 product documentation for information about creating a user with SYSADM authority on the DB2 server. You must add 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 program when installing on AIX 6.x systems remotely, reattempt the installation locally. Use the console or an X terminal on the system locally. Procedure 1. 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 downloaded installation image, and run the following command: Windows launchpad.exe UNIX launchpad.sh If the launchpad does not start the installation, you can start the product installation program directly. On the downloaded installation image, browse to \Install\\, and run one of the following commands:
58 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Windows v install.bat v install_win64.bat UNIX v install_aix64.sh v install_linux32.sh v install_linux64.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 for differentiating between multiple installations that are hosted on the same administrative workstation. 5. Review the information that is on the Verify Installation Location panel. The panel shows any previous installation information that was found based on the installation directory that you specified on the previous panel. After you advance past this panel, you cannot go back and change the installation directory for this installation. If a more recent version of the installation program is found in the specified target directory, you are notified. The notification means that you are using an older version of the installation program. The version found on the administrative workstation is newer and can contain important features and enhancements. To use the newer version of the installation program, select the option on the notification panel and click Next. This action exits the current installation process and restarts the installation process with the newer installation program. If you do not select the option, you continue the installation 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 the system. Target package version information indicates the package version being currently deployed. 7. On the Choose Deployment panel, specify Simple or Custom as the deployment type. 8. On the Import Middleware Configuration Information panel, you select Import middleware configuration information to have the product installation program reuse the middleware installation program values. These values are used as default values for the same fields in the product installation program. The Workspace location field refers to the location of the topology file that contains the values that were specified for the middleware installation program. The file is located in the workspace that was defined during the middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for Windows or /root/ibm/tivoli/mwi/workspace for UNIX. If you selected the simple deployment, the middleware default information is not used. 9. On the Database Type panel, specify DB2, Oracle, or Microsoft SQL Server as the software to use for the Maximo database. 10. On the Database panel, specify configuration information for your database software. For things such as the database user ID, the database name, the database instance for SmartCloud Control Desk, and the schema name, if the values do
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 59 not 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 for DB2 and Oracle cannot contain spaces. For DB2, the database instance is created if it does not exist, but the user and its 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 are defined or it can be a different value, such as maximo. After you specify configuration information for your database software, the installation program validates the information with the database server. 11. On the Automate Database Configuration panel, you can specify that database creation 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 information for the automatic database configuration feature. Specifying the values enables remote configuration. 13. On the Database Administration panel, specify configuration information about the database. The required information varies by database platform. For DB2, the instance administrator user ID cannot be the same as the database user ID. And the Windows service user ID must have administrative authority on the system. 14. On the Database Tablespace panel, specify information about the table space of the database. When you click Next, the product installation program connects to the database server and validates the information that you specified. 15. When the database validation is complete, on the Application Server Type panel, specify Oracle WebLogic Server for the product deployment. You must manually configure WebLogic Server and manually deploy application files. 16. On the Specify Maximo Users panel, enter Maximo database user information. Maximo administration user The product administrator user ID that is used for initial configuration and adding users. Maximo system registration user The user ID that is used for the self-registration of users. Maximo system integration user The user ID that is used with enterprise adapters.
Custom user ID and password values are stored in the Maximo database. The default user IDs of maxadmin, maxreg, and maxintadm are also created as users in the Maximo database. Creation of the default user IDs is done for internal processing purposes. If you use Maximo database security for authentication and authorization, the default user IDs can be used to log in to the application. If you regard this condition as a security risk, you can modify the passwords for the default user IDs. You modify passwords for the user IDs in the Users application. 17. On the SMTP Configuration panel, specify the SMTP configuration information that is used by workflows to communicate with workflow participants. The administrator e-mail address is the e-mail address that is used to send messages. If you leave the fields blank, you must configure the SMTP parameters through the product interface as a post-installation task.
60 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 18. On the Data Integration and Context Menu Services Options panel, click the button that indicates where the database tables for these functions should be created: in the Maximo ("same") database, or in a separate database instance that you have already created for this purpose. If you are installing the Entry edition, choose the Maximo database. These tables will be created but will not be used by the Entry edition. 19. On the Base Language Selection panel, specify the base language for the installation. 20. On the Additional Language Selection panel, you can optionally specify one or more additional languages that the installation is to support. 21. On the Run Configuration Step panel, specify how to perform the configuration step of the installation. If you do not select an option, the configuration step proceeds when you click Next. Copy files now, but perform the installation configuration step later Select this option to copy files from the installation source to the administrative workstation. You must perform the configuration step at a later time to complete the deployment.
Important: Do not install another product before completing the configuration step of the original installation. Installing another product before running the configuration step for this installation overwrites the taskstore, which prevents the original installation from ever being deployed. The configuration values that you specify are stored in the install_home\maximo\applications\maximo\properties\ maximo.properties and install_home\etc\install.properties files. You run the configuration steps outside of the product installation program by using the taskrunner utility, in the install_home\scripts directory. Run the taskrunner utility from the command line. install_home\scripts\taskrunner [CONTINUE
The taskrunner uses the configuration values that are stored in the maximo.properties and install.properties files to configure SmartCloud Control Desk. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner continues despite errors. If you run taskrunner with the STOPONERROR parameter, the taskrunner stops when it encounters an error. If you used STOPONERROR, you can rectify the conditions that caused the error. You can then resume the installation at the point where the last successfully completed task was recorded in the previous attempt by starting taskrunner with the CONTINUE parameter. Defer the update of the Maximo database Select this option if you want to manually run the database update task for the product deployment. This option can be used when there is a fix pack available that addresses known issues with the updatedb script. In this scenario, you choose the Defer the update of the Maximo database option, apply the fix pack, and then run the updatedb -v1 command manually. 22. On the Choose Shortcut Folder panel, specify where you want SmartCloud Control Desk icons created. If you select In the Start Menu and use Internet Explorer, add the SmartCloud Control Desk URL to the trusted sites web content zone. Disable the option that requires server verification for all sites in the zone.
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 61 Do not select In the Quick Launch Bar. The selection does not create a shortcut in the Quick Launch bar. Attention: Shortcuts are created for Windows systems only. Because WebLogic Server deployments are a manual process, you must manually update any shortcuts that you create. You update shortcuts after you have manually deployed the SmartCloud Control Desk EAR files. 23. On the Input Summary panel, review the information that you have provided for the 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 by viewing the messages that are displayed above the progress bar. 25. On the Installation Completed panel, review any information presented, then click Done. Attention: In some cases, on AIX systems, the Installation Completed panel might appear blank. Click Done to exit the installation program. “Restarting middleware on Windows” on page 169 This procedure describes how to restart middleware on Windows, if you must restart any middleware services. “Restarting middleware on UNIX” on page 170 Middleware services on Linux and AIX platforms occasionally must be restarted, such as when a reboot occurs. Middleware servers and services must be active before running the SmartCloud Control Desk installation program. Installing optional content Install the relevant optional content package for your edition of the product.
Optional content is often used in development environments as a way to begin developing your own content.
If you do not install optional content during the product installation process, you can install it later. If you install it later, you must update the database and rebuild and deploy the maximo.ear file. Installing optional integration modules Install integration module packages in order to set up integrations with other products.
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 database and rebuild and deploy the maximo.ear file.
Post installation for Oracle WebLogic Server deployments There 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 SmartCloud Control Desk deployment, the installation program produces an EAR file. You must then manually deploy that file to Oracle WebLogic Server.
62 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) When using Oracle WebLogic Server, you must modify the weblogic.xml file and rebuild the maximo.ear file before deploying it. Procedure 1. 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 the server where you installed Oracle WebLogic Server. Use any file transfer protocol that is available. b. The oraclethin.jar file is in the install_home\maximo\applications\ maximo\lib directory. The default install_home directory is C:\IBM\SMP\Maximo\Applications\Maximo\lib. Copy the oraclethin.jar file to the J2EE server and into the wls11g/server/lib directory. For example, C:/Oracle/wls11g/server/lib. 3. Edit the domain configuration file for proper 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. Two instances 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 Oracle WebLogic Server. e. Increase the Java Heap parameters by searching for MEM_ARGS and setting the 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 (-) sign before each parameter and to include the m after each value. f. Search for set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES%. Insert an option right after this string as follows: -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
The entry looks like this 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.
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 63 4. Edit the \IBM\SMP\maximo\applications\maximo\maximouiweb\webmodule\WEB- INF\weblogic.xml file and add the following entries:
The user name and password values must match an existing user account in the Authentication provider for the default security realm. If you save the file as boot.properties and locate it in the mydomain folder (for example, C:\BEA\User_projects\domains\mydomain), the server automatically uses this file during its subsequent startup cycles. The first time you use this file to start a server, the server reads the file and then overwrites it with an encrypted version of the user name and password. 6. Verify settings by starting Oracle WebLogic Server. To ensure that the edits that you made to the previous Oracle WebLogic Server files were accurate, start the Oracle 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 files You are now ready to deploy the EAR files from the Oracle WebLogic Server Administration Console. Deploying the EAR files starts the Maximo Application Server. Before you begin
Windows Windows If MAXIMOSERVER is not running, start it from a command prompt.
UNIX UNIX Ensure that the Oracle WebLogic Server daemon is running. About this task
In order to view the Oracle WebLogic Server Administration Console, you need to also install a Java Virtual Machine (JVM). Newer versions of Windows might not ship with JVM. Procedure 1. Change to the my_domain directory:
Windows Windows From a command prompt, change directory path to: drive_name:\weblogic_install_dir\user_projects\domain\my_domain
64 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) UNIX UNIX Open a Terminal window (or a command prompt, if you are telneting from a Windows computer) and change directory as follows: cd /home/mxadmin/weblogic_install_dir/user_projects/domains/my_domain 2. Type
Windows Windows startWebLogic.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 by typing 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 and password. 5. In the left pane, click the Lock&Edit button in the Change Center section to set the server to edit mode. 6. In the left pane, 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 “Install this deployment as an application” and click Next to continue the deployment. 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 42 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 requests. The Start Application Assistant displays. 18. Click Yes to start the system.
Setting the Oracle WebLogic Server host name Setting the Oracle WebLogic Server host name manually to access application help information.
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 65 About this task
By default, the property used to store the host name for the SmartCloud Control Desk help system is set to localhost. The fully qualified host name of the Oracle WebLogic Server must be configured in the help system property to view SmartCloud Control Desk application help topics. Complete this step after you have deployed SmartCloud Control Desk EAR files to the Oracle WebLogic Server. Procedure 1. 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 Desk user interface.
Language deployment after database update deferral Selecting the option to defer the update of the Maximo database when installing the product, affects how you deploy languages.
During installation, you have the option to defer the database update task. This option prevents writing data to the database during the installation. The installation program is limited to copying files to the administrative system and registering product process solution packages. You add languages by completing the installation, manually updating the database, and then updating languages manually. “Manually deploying languages after database update deferral” on page 44 Languages must be deployed manually if you defer database updates by the installation program. Manually deploying languages after database update deferral Languages must be deployed manually if you defer database updates by the installation program. Before you begin
You must have run updatedb command before manually configuring languages for PSI packages. About this task
To manually configure languages for PSI packages, complete the following steps:
66 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Procedure
Update language support for the Maximo core components. Files for the language selections you made during the installation are extracted to the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory on the system. 1. 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 2. To add one or more languages as additional languages for use with the product, run the following command for each language you want to add: install_home\maximo\tools\maximo\TDToolkit.bat -ADDLANGlocale -maxmessfix
Chapter 3. Deploying automatically reusing existing middleware (Scenario 2) 67 68 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 4. Deploying manually reusing existing middleware (Scenario 3)
Use this information if you intend to deploy SmartCloud Control Desk by reusing existing middleware servers and manually configuring them to work with SmartCloud Control Desk.
This information provides a high-level overview or road map of tasks you need to complete in order to deploy SmartCloud Control Desk automatically, using middleware already established in your enterprise.
In this scenario, you manually configure existing middleware resources before running the SmartCloud Control Desk installation program.
Figure 2. Deploying SmartCloud Control Desk with manual middleware configuration
SmartCloud Control Desk installation with manual middleware configuration Manually configured installations involve configuring middleware components, the database server, the directory server, and the J2EE server, to work with SmartCloud Control Desk before using the SmartCloud Control Desk installation program.
You can elect to have one or more SmartCloud Control Desk middleware components configured automatically by the SmartCloud Control Desk installation program. Alternatively, you can choose to manually configure one or more of the middleware servers to work with SmartCloud Control Desk.
The information contained in this section provides details on how to manually configure SmartCloud Control Desk middleware before running the SmartCloud Control 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 not configure using the autoconfigure feature of the SmartCloud Control Desk installation program before you actually use the SmartCloud Control Desk installation program to install SmartCloud Control Desk.
Ensure that all of your middleware is at supported version levels. Manually configuring the database You have the option of manually configuring the database server used in SmartCloud Control Desk deployment. the Manual configuration of the database server must be completed before you use the SmartCloud Control Desk installation program.
For DB2 on UNIX and Linux systems, ensure you have a minimum of 8 gigabytes (binary) free of space in the DB2 database instance home directory
© Copyright IBM Corp. 2007, 2011 69 (/home/ctginst1) in order to meet the default table space disk space requirements of the DB2 install. For DB2 on Windows, ensure you have a minimum of 8 gigabytes of free space in the DB2 installation directory. Manually configuring DB2 9.x This section contains instructions for manually configuring DB2 9.x servers for use by 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 Desk installation program:
Procedure 1. 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 setup the DB2 environment: v Windows db2cmd v Linux or UNIX Ensure 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 ctginst1 set db2instance=ctginst1 db2start db2 update dbm config using SVCENAME 50005 DEFERRED db2stop db2set DB2COMM=tcpip db2start v Linux orUNIX db2icrt -s ese -u db2fenc1 -p 50005 ctginst1 . /home/ctginst1/sqllib/db2profile db2start db2 update dbm config using SVCENAME 50005 DEFERRED db2stop db2set DB2COMM=tcpip db2start 5. Create the database. db2 create db ’maxdb75’ ALIAS ’maxdb75’ using codeset UTF-8 territory US pagesize 32 K db2 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 ON db2 update db cfg for maxdb75 using APP_CTL_HEAP_SZ 16384 DEFERRED db2 update db cfg for maxdb75 using APPLHEAPSZ 2048 AUTOMATIC DEFERRED db2 update db cfg for maxdb75 using AUTO_MAINT ON DEFERRED db2 update db cfg for maxdb75 using AUTO_TBL_MAINT ON DEFERRED
70 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) db2 update db cfg for maxdb75 using AUTO_RUNSTATS ON DEFERRED db2 update db cfg for maxdb75 using AUTO_REORG ON DEFERRED db2 update db cfg for maxdb75 using AUTO_DB_BACKUP ON DEFERRED db2 update db cfg for maxdb75 using CATALOGCACHE_SZ 800 DEFERRED db2 update db cfg for maxdb75 using CHNGPGS_THRESH 40 DEFERRED db2 update db cfg for maxdb75 using DBHEAP AUTOMATIC db2 update db cfg for maxdb75 using LOCKLIST AUTOMATIC DEFERRED db2 update db cfg for maxdb75 using LOGBUFSZ 1024 DEFERRED db2 update db cfg for maxdb75 using LOCKTIMEOUT 300 DEFERRED db2 update db cfg for maxdb75 using LOGPRIMARY 20 DEFERRED db2 update db cfg for maxdb75 using LOGSECOND 100 DEFERRED db2 update db cfg for maxdb75 using LOGFILSIZ 8192 DEFERRED db2 update db cfg for maxdb75 using SOFTMAX 1000 DEFERRED db2 update db cfg for maxdb75 using MAXFILOP 32768 DEFERRED #32-bit Windows db2 update db cfg for maxdb75 using MAXFILOP 65535 DEFERRED #64-bit Windows db2 update db cfg for maxdb75 using MAXFILOP 30720 DEFERRED #32-bit UNIX db2 update db cfg for maxdb75 using MAXFILOP 61440 DEFERRED #64-bit UNIX db2 update db cfg for maxdb75 using PCKCACHESZ AUTOMATIC DEFERRED db2 update db cfg for maxdb75 using STAT_HEAP_SZ AUTOMATIC DEFERRED db2 update db cfg for maxdb75 using STMTHEAP AUTOMATIC DEFERRED db2 update db cfg for maxdb75 using UTIL_HEAP_SZ 10000 DEFERRED db2 update db cfg for maxdb75 using DATABASE_MEMORY AUTOMATIC DEFERRED db2 update db cfg for maxdb75 using AUTO_STMT_STATS OFF DEFERRED db2 update db cfg for maxdb75 using STMT_CONC LITERALS DEFERRED db2 update alert cfg for database on maxdb75 using db.db_backup_req SET THRESHOLDSCHECKED YES db2 update alert cfg for database on maxdb75 using db.tb_reorg_req SET THRESHOLDSCHECKED YES db2 update alert cfg for database on maxdb75 using db.tb_runstats_req SET THRESHOLDSCHECKED YES db2 update dbm cfg using PRIV_MEM_THRESH 32767 DEFERRED db2 update dbm cfg using KEEPFENCED NO DEFERRED db2 update dbm cfg using NUMDB 2 DEFERRED db2 update dbm cfg using RQRIOBLK 65535 DEFERRED db2 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 DEFERRED db2 update dbm cfg using MON_HEAP_SZ AUTOMATIC DEFERRED db2set DB2_SKIPINSERTED=ON db2set DB2_INLIST_TO_NLJN=YES db2set DB2_MINIMIZE_LISTPREFETCH=Y db2set DB2_EVALUNCOMMITTED=YES db2set DB2_FMP_COMM_HEAPSZ=65536 db2set DB2_SKIPDELETED=ON db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON 7. For Linux orUNIX log in as the ctginst1 user and then restart the DB2 command-line environmen su - ctginst1 db2 8. Restart DB2. db2stop force db2start 9. Reconnect to the database. db2 connect to ’maxdb75’ 10. 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 MAXTDATA TO USER MAXIMO
db2 GRANT CREATEIN,DROPIN,ALTERIN ON SCHEMA MAXIMO TO USER MAXIMO
db2 create schema maximo authorization maximo 11. Create a buffer pool. db2 CREATE BUFFERPOOL MAXBUFPOOL IMMEDIATE SIZE 4096 AUTOMATIC PAGESIZE 32 K 12. Create table spaces. db2 CREATE REGULAR TABLESPACE MAXDATA PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE INITIALSIZE 5000 M BUFFERPOOL MAXBUFPOOL db2 CREATE TEMPORARY TABLESPACE MAXTEMP PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE BUFFERPOOL MAXBUFPOOL db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO 13. Break the database connection. db2 connect reset 14. Exit the DB2 command-line environment 15. Install the appropriate fix pack indicated in the prerequisites topic in the chapter that describes how to prepare for the installation. Ensure that you review and complete all the installation and post-installation tasks contained within the fix pack readme file. Failure to do so can potentially cause the SmartCloud Control Desk installation to fail. See the appropriate product support page for more information. Manually configuring Oracle 11g Use the following instructions to manually configure Oracle 11g for use with SmartCloud Control Desk.
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 71 Before you begin
Oracle instance names must be limited to eight characters in length. For Oracle databases, 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 starting the SmartCloud Control Desk installation program:
Procedure 1. 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 existing listener 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, and Use Database File Locations from Template is selected as the value to use for database file location, and then click Next. i. Leave defaults selected for the database recovery options panel, and then click 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 Management Set this value to Manual Shared Memory Management.
72 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Shared Pool Set this value to 152. Buffer Cache Set this value to 36. Java Pool Set this value to 32. Large Pool Set this value to 8. PGA Size Set 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_semantics Change this value to CHAR. open_cursors Change this value to 1000. cursor_sharing Set 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 has been successfully created.
Note: The Oracle Database Configuration Assistant executes the ORACLE_HOME/ctx/admin/defaults/drdefus.sql script as part of the configuration of the CTXSYS user. You must execute this script manually if the Oracle 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 the directory does not exist, this command fails. 5. Create a temporary table space using the following command in SQL*Plus create 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 the directory does not exist, this command fails. 6. Create the maximo user and grant permissions using the following command in SQL*Plus: create user maximo identified by maximo default tablespace maxdata temporary tablespace maxtemp; grant connect to maximo; grant create job to maximo; grant create trigger to maximo;
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 73 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 to that index table space to the maximo user. For example, use the following command if you created a separate table space for indexing called TSI_MAM_OWN.": alter user maximo quota unlimited on TSI_MAM_OWN These instructions assume that you did not modify default role sets assigned to the Oracle DBA user or user IDs created to connect to the database. If you restricted the default privileges granted to user IDs, you must explicitly grant them to the maximo user. For example, if you do not grant a role such as the select_catalog_role role, you must explicitly grant that role to the maximo user. This assignment can be done by running this SQL*Plus command: grant select_catalog_role to maximo Manually configuring Oracle 10g Oracle 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 Oracle databases, 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 starting the SmartCloud Control Desk installation program:
Procedure 1. 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.
74 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 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 the database, and then click Next. i. Ensure Use Database File Locations from Template is selected as the value to use for database file location, and then click Next. j. Leave defaults selected for the database recovery options panel, and then click 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 Management Set this value to Manual. Shared Pool Set this value to 152. Buffer Cache Set this value to 36. Java Pool Set this value to 32 Large Pool Set this value to 8. PGA Size Set 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_semantics Change this value to CHAR open_cursors Change this value to 1000 cursor_sharing Set 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 has been successfully created, click Password Management.
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 75 u. Unlock the CTXSYS account by clearing the check mark in the Lock Account? column for that entry, enter a password for the account, and then click OK. v. Click Exit to exit the Database Configuration Assistant. The database has been successfully created.
Note: The Oracle Database Configuration Assistant uses the ORACLE_HOME/ctx/admin/defaults/drdefus.sql script as part of the configuration of the CTXSYS user. This script must be used manually if the Oracle 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 installation location 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 temporary tablespace 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 also grant the maximo user access to that index table space. For example, you must perform the following additional SQL*plus command if you had created a separate table space for indexing called TSI_CMDB_OWN: alter user maximo quota unlimited on TSI_CMDB_OWN These instructions assume that you have not modified the default role sets that are assigned to the Oracle DBA user or other database connection user IDs. If you have restricted the default privileges granted to user IDs, you must explicitly grant them to the maximo user. For example, the select_catalog_role role is required for user IDs connecting to the database. To deploy SmartCloud Control Desk successfully, you must explicitly grant that role to the maximo user by using the SQL*Plus command: grant select_catalog_role to maximo Manually configuring Microsoft SQL Server You can manually configure Microsoft SQL Server for use with SmartCloud Control Desk.
Before you begin
Because Microsoft SQL Server does not support UTF-8, SmartCloud Control Desk does not have multilingual support when deployed with Microsoft SQL Server.
76 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Microsoft SQL Server Database Collation settings must be set to the following options: v Dictionary order v Case-insensitive v For use with 1252 Character set
About this task
To configure an existing Microsoft SQL Server for use with SmartCloud Control Desk, perform the following steps before starting the SmartCloud Control Desk installation program:
Procedure 1. Configure the listener port. If The default instance of the Microsoft SQL Server Database Engine listens on TCP port 1433. Named instances of the Microsoft SQL Server Database Engine and Microsoft SQL Server Compact Edition are configured for dynamic ports, which means they select any available port when the service starts. When connecting to a named instance across a firewall, configure the Database Engine to 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
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 77 Navigate through the wizard and enable the Full-Text Search option located on the Custom portion of the Setup Type dialog box. To finish the installation 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 production environment. 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,MAXIMO go
This value is case-sensitive. e. Click Execute. f. Enter the following script to change the database owner to maximo. sp_changedbowner MAXIMO go g. Click Execute.
What to do next
If you add additional logical names to the database and set their file group to a value other than PRIMARY, you must complete the following steps after you set up 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=
Complete these additional steps only if you added additional logical names to the database and set their file group to a value other than PRIMARY.
78 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Manually configuring the directory server These topics provide details on manually configuring a directory server for use by SmartCloud Control Desk
There are several methods you can use to secure SmartCloud Control Desk.If want to use a directory server to secure SmartCloud Control Desk, you must complete the manual configuration of the directory server before you use the SmartCloud Control Desk installation program. Manual configuration is necessary if you choose to not have the SmartCloud Control Desk installation program perform configuration.
Note: The base dn, bind user, and other various node values listed in these sections are defaults. These values are replaced with values applicable to existing LDAP hierarchies within your organization.
Important: When entering LDAP values for SmartCloud Control Desk installation panel fields, entries in LDIF files, or values you enter directly into a directory instance using directory server tools, be aware of the product-specific syntax rules for using special characters in an LDAP string. In most cases, special characters must be preceded by an escape character in order to make it readable by the directory server. Failing to escape special characters contained in an LDAP string used with SmartCloud Control Desk results in SmartCloud Control Desk errors.
Many directory server products consider a blank space as a special character that is part of the LDAP string. If you mistakenly enter an LDAP string that contains a blank, at the end of a field value, for example, and you do not precede the blank character with an escape character, you encounter SmartCloud Control Desk errors that are difficult to troubleshoot.
See the product documentation for your directory server for more information about special characters in LDAP strings. Manually configuring IBM Tivoli Directory Server Use the following instructions to manually configure IBM Tivoli Directory Server for use with SmartCloud Control Desk.
About this task
To configure IBM Tivoli Directory Server before starting the SmartCloud Control Desk installation program, you must create an instance of IBM Tivoli Directory Server.
Note: While you can technically share a DB2 instance between SmartCloud Control Desk and the one needed by IBM Tivoli Directory Server, it might lead to problems. During the installation, the database instance is restarted, which might disrupt the availability of IBM Tivoli Directory Server to your enterprise. If you are using the automated installation programs, separate instances are created for use by SmartCloud Control Desk and IBM Tivoli Directory Server.
Procedure 1. Using your preferred method, create a user on the system and assign it to the appropriate group. Windows Create the user db2admin and make it a member of the following groups:
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 79 v Windows Administrators v DB2ADMNS v DB2USERS UNIX Create the user idsccmdb and make it a member of the following groups: v dasadmn1 v idsldap v dbsysadm The root user must also be a member of the dasadm1, idsldap, and dbsysadm groups. 2. If the Instance Administration tool is not already started, ensure that you are logged in as an administrator on the system, and then start the tool Windows Select Programs > IBM Tivoli Directory Server 6.3 > Instance Administration 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 name Select idsccmdb as the system user ID of the user who owns the instance. This name is also the name of the instance. Install location Enter the location where the instance files are stored. Encryption seed string Type a string of characters that are used as an encryption seed. This value must be a minimum of 12 characters. Instance description Enter a brief description of the instance. 6. In the DB2 instance details panel, enter idsccmdb as the value for the DB2 instance name field, and then click Next. 7. In the TCP/IP settings for multihomed hosts panel, select Listen on all configured IP addresses, and then click Next. 8. In the TCP/IP port settings panel, complete the following fields, and then click Next. Server port number Enter 389 as the contact port for the server. Server secure port number Enter 636 as the secure port for the server. Admin daemon port number Enter 3538 as the administration daemon port. Admin daemon secure port number Enter 3539 as the administration daemon secure port. 9. In the Option steps panel, leave the following options selected, and then click Next.
80 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Configure admin DN and password You want to configure the administrator DN and password for the instance now. Configure database You want to configure the database for the directory server now. 10. In the Configure administrator DN and password window panel, complete the following fields, and then click Next. Administrator DN Enter cn=root for the administrator distinguished name. Administrator Password Enter a password for the Administrator DN. 11. From the Configure database panel, complete the following fields, and then click Next. Database user name Enter idsccmdb as the database user. Password Enter the password for the idsccmdb user. Database name Enter idsccmdb as the database to be used with this directory instance. 12. In the Database options panel, complete the following fields, and then click Next. Database install location Type the location for the database. Windows For Windows platforms, this value must be a drive letter. UNIX For non-Windows platforms, the location must be a directory name, such as /home/ldapdb. Ensure that you have at least 80 MB of free hard disk space in the location you specify. Additional disk space must be available to accommodate growth as new entries are added to the directory. Character-set option Leave the Create a universal DB2 database (UTF-8/UCS-2) option selected. 13. In the Verify settings panel, review the instance creation details provided, and then click Finish to create the idsccmdb instance. 14. Click Close to close the window and return to the main window of the Instance Administration tool. 15. Click Close to exit the Instance Administration tool. 16. Start the IBM Tivoli Directory Server Configuration tool: Windows SelectPrograms > IBM Tivoli Directory Server 6.3 > Instance Administration 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.
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 81 20. Create and save an LDIF file. Add the DN information, for example: v ou=SWG,o=IBM,c=US v ou=users
Note: ou=SWG,o=IBM,c=US in this example is an organization unit called SWG. SWG houses the OU=Users organization units to place the users created for SmartCloud Control Desk. DC=IBM and DC=COM would indicate a domain forest of ibm.com®. You can replace the example with the directory structure of your own organization. Define the following users and their positions within the ou=users DN's you created. These users are defined in order for Virtual Member Manager to be used to secure SmartCloud Control Desk.
Important: Before you begin this procedure, ensure that you have the following users created in the root of your LDAP repository: Table 4. Base SmartCloud Control Desk required users User maxadmin mxintadm maxreg
Here is an example of the default base LDIF data: dn: o=ibm,c=us objectClass: top objectClass: organization o: IBM
dn: ou=SWG, o=ibm,c=us ou: SWG objectClass: top objectClass: organizationalUnit
dn: ou=users,ou=SWG, o=ibm,c=us ou: users objectClass: top objectClass: organizationalUnit
dn: uid=maxadmin,ou=users,ou=SWG, o=ibm,c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin
dn: uid=mxintadm,ou=users,ou=SWG, o=ibm,c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm
82 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) dn: uid=maxreg,ou=users,ou=SWG, o=ibm,c=us userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg
Note: If you create the LDIF file on Windows, ensure that you remove the ^M characters from the file before using.
Note: Before you can import an LDIF file on UNIX systems, you must run the 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 Directory You can manually configure Microsoft Active Directory for use with SmartCloud Control Desk.
Before you begin
Use this procedure to manually create users and groups within Microsoft Active Directory.
Important: The users and passwords you create in the following steps must match this exact configuration for the deployment to succeed. It is sometimes necessary to temporarily alter theMicrosoft Active Directory security policy to create these accounts in the required format. After installation, you can change these default passwords to conform to a stricter security policy.
About this task
Before starting theSmartCloud Control Desk installation program, configure Microsoft Active Directory. Complete the following steps
Procedure 1. Select Start > Control Panel > Administrative Tools > Microsoft Active Directory Users and Computers and then select the domain that you are working with. 2. Edit the functional level of the domain by selecting Action > Raise Domain Functional Level. The Raise Domain Functional Level dialog box is displayed. 3. Select Microsoft Windows Server 2008 from the Select an available domain functional 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, right-click the domain to work with. Select New > Organizational Unit. 7. Enter a name for the new Organizational Unit (OU), for example, SWG, and then click OK.
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 83 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 name Enter maxadmin. Initials Leave this field blank. Last name Leave this field blank. Full name Enter maxadmin. User login name Enter maxadmin in the first field. Leave the default value of the second field. User login name (pre-Microsoft Windows 2000) This field is populated with the same value (maxadmin) entered for the User login name. c. From the next panel, enter the following information, and then click Next: Password Enter maxadmin as the password for the maxadmin user. User must change password at next logon Ensure this check box is cleared. User cannot change password Ensure this check box is selected. Password never expires Ensure this check box is selected. Account is disabled Ensure this check box is cleared. The preceding values are examples. Enter values that comply with the password 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 name Enter mxintadm. Initials Leave this field blank.
84 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Last name Leave this field blank. Full name Enter mxintadm. User login name Enter mxintadm in the first field. Leave the default value of the second field. User login name (pre-Microsoft Windows 2000) This field is displayed with the same value (mxintadm) entered for the User login name. c. From the next panel, enter the following information, and then click Next: Password Enter a value as the password for the mxintadm user. User must change password at next logon Ensure this check box is cleared. User cannot change password Ensure this check box is selected. Password never expires Ensure this check box is selected. Account is disabled Ensure this check box is cleared. The preceding values are examples. You must set these fields to values that 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 name Enter maxreg. Initials Leave this field blank. Last name Leave this field blank. Full name Enter maxreg. User login name Enter maxreg in the first field. Leave the default value of the second field. User login name (pre-Microsoft Windows 2000) This field is filled with the same value (maxreg) entered for the User login name. c. From the next panel, enter the following information, and then click Next: Password Enter a value as the password for the maxreg user.
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 85 User must change password at next logon Ensure this check box is cleared. User cannot change password Ensure this check box is selected. Password never expires Ensure this check box is selected. Account is disabled Ensure this check box is cleared. The preceding values are examples. Enter values that comply with the password 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 to install the remaining SmartCloud Control Desk middleware and configure the J2EE server to use Microsoft Active Directory. Manually configuring the J2EE server This section contains instructions for manually configuring an existing J2EE server for use by SmartCloud Control Desk.
You must complete the manual configuration of the J2EE server before you use the SmartCloud Control Desk installation program if you choose to deploy SmartCloud Control Desk using Oracle WebLogic Server. Manually configuring WebLogic Server WebLogic Server can be used with SmartCloud Control Desk if it is manually configured.
About this task
You can use a WebLogic Server as your J2EE server. The SmartCloud Control Desk installation process prepares EAR files on the SmartCloud Control Desk administrative workstation. These files are then manually deployed to your WebLogic Server. The SmartCloud Control Desk installation program does not automatically configure a WebLogic Server environment It does not install or otherwise deploy SmartCloud Control Desk applications into a WebLogic Server server.
Manually configuring WebLogic Server consists of the following tasks:
Procedure 1. “Creating the MAXIMOSERVER domain” on page 29 2. “Configuring JMS options for integration framework” on page 30 3. “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 WebLogic Server.
86 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) About this task
To create the MAXIMOSERVER domain within WebLogic Server, complete the following steps:
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
Configuring JMS options for integration framework:
This procedure provides details on steps to configure JMS queues.
Before you begin
You need to be familiar with the Oracle WebLogic Server Administration Console to complete the following procedure. See your Oracle WebLogic Server documentation on how to navigate through the Oracle WebLogic Server Administration Console.
Procedure 1. Launch Internet Explorer and open the MAXIMOSERVER Administration Console by typing the following URL:
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 87 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 to create database-based stores. To choose between file stores and database-based stores, 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 servers to a value of 20% or below of the allotted JVM heap size to prevent the Oracle WebLogic Server from running out of memory. 5. Create a JMS system module named intjmsmodule with MAXIMOSERVER as the target server. 6. Add a connection factory resource to the JMS module:
Option Description Name intjmsconfact 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.
88 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) What to do next
You need to stop and restart the MAXIMOSERVER application server for the update to take effect.
Configuring JMS for the email listener in WebLogic Server:
About this task
You use the email listeners application to receive and process requests through email in the form of email messages.
To configure JMS queues for the WebLogic Server, complete the following steps:
Procedure 1. Log in to the WebLogic Server administration console. 2. Create a persistent store. a. In the Domain Structure panel, expand Services and then click Persistent Stores. 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 JMS Servers, enter the following information, and then click Next. Name Enter a name for a new JMS server, for example, lsnrserver. Persistent Store Select 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 JMS Modules, and then click New. b. Enter a value for the Name field, such as lsnrjmsmodule, and then click Next. 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, click New 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 Name Enter jms/mro/lsnr/lsnrcf. d. Ensure AdminServer is selected, and then click Finish 6. Add a queue to the JMS module.
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 89 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 Name Enter jms/mro/lsnr/qin. Template No template is necessary. d. Click Create a new Subdeployment, select lsnrserver, and then click Finish. 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 from sections within the deployment descriptor files. Edit the ejb-jar.xml and weblogic-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 then save the file: Email Listener JMS is not deployed by default
90 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server)
Installing the product and manually configuring middleware You can deploy SmartCloud Control Desk with middleware that has been configured before the installation begins. You use this procedure if your organization has specific policies and procedures that govern how you create databases, database instances, and users within your organization. Before you begin
Ensure that you meet prerequisite conditions. v Oracle WebLogic Server must have been manually configured. 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 during deployments on IBM WebSphere Application Server Network Deployment. v On the administrative workstation, temporarily shut down any noncritical processes that can have a negative effect on the installation, such as antivirus software. v Ensure that the Windows DEP setting does not prevent the launchpad from running: Select Start > Settings > Control Panel > System > Advanced > Performance > Settings > Data Execution Prevention. Select Turn on DEP for essential Windows programs and services only and click Apply. You might be asked 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 the documentation for your operating system. Alternatively, you can provide the IP address for the system. v Enable a remote execution and access service on every system that has middleware installed. Each remote system must support a remote access protocol and must accept remote logins from a user name and password that were configured on the target server. Remote access protocols include SSH and Windows SMB. If the remote system is a Windows server, you must configure remote 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 product installation program. See the DB2 product documentation for information about creating a user with SYSADM authority on the DB2 server. You must add root to a group with SYSADM authority for UNIX systems. – To avoid high system memory usage by DB2, you can set the following DB2 property and then restart the DB2 server: db2 update dbm cfg using KEEPFENCED NO
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 91 v If you use DB2 on UNIX systems with SmartCloud Control Desk, you must add root to a group with SYSADM authority for the database instance. This membership must be in place before starting the SmartCloud Control Desk installation program. v Complete the following tasks for Oracle WebLogic Server: – Configure JMS options for integration framework – Create the domain. – Setup JMS for e-mail listener. 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 program when installing on AIX 6.x systems remotely, reattempt the installation locally. Use the console or an X terminal on the system locally. Procedure 1. 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 downloaded installation image, and run the following command: Windows launchpad.exe UNIX launchpad.sh If the launchpad does not start the installation, you can start the product installation program directly. On the downloaded installation image, browse to \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 v install_linux64.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 for differentiating between multiple installations that are hosted on the same administrative workstation. 5. Review the information that is on the Verify Installation Location panel. The panel shows any previous installation information that was found based on the installation directory that you specified on the previous panel. After you advance past this panel, you cannot go back and change the installation directory for this installation. If a more recent version of the installation program is found in the specified target directory, you are notified. The notification means that you are using an older version of the installation program. The version found on the
92 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) administrative workstation is newer and can contain important features and enhancements. To use the newer version of the installation program, select the option on the notification panel and click Next. This action exits the current installation process and restarts the installation process with the newer installation program. If you do not select the option, you continue the installation 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 the system. Target package version information indicates the package version being currently deployed. 7. On the Choose Deployment panel, specify Simple or Custom as the deployment type. 8. On the Import Middleware Configuration Information panel, you select Import middleware configuration information to have the product installation program reuse the middleware installation program values. These values are used as default values for the same fields in the product installation program. The Workspace location field refers to the location of the topology file that contains the values that were specified for the middleware installation program. The file is located in the workspace that was defined during the middleware installation task. For example, C:\ibm\tivoli\mwi\workspace for Windows or /root/ibm/tivoli/mwi/workspace for UNIX. If you selected the simple deployment, the middleware default information is not used. 9. On the Database Type panel, specify DB2, Oracle, or Microsoft SQL Server as the software to use for the Maximo database. 10. On the Database panel, specify configuration information for your database software. For things such as the database user ID, the database name, the database instance for SmartCloud Control Desk, and the schema name, if the values do not exist when you specify them, they are created. Database users and database instance names for DB2 and Oracle 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 and its 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 are defined or it can be a different value, such as maximo. After you specify configuration information for your database software, the installation program validates the information with the database server. 11. On the Automate Database Configuration panel, select The database has already been created and configured and click Next. This step assumes that you have already created a database instance, a database, table spaces, a user, and schema for use with SmartCloud Control Desk. See “Manually configuring the database” on page 69. If you have not manually configured the database before selecting The database has already been created and configured you are prompted to complete them before restarting the installation program. 12. On the Database Tablespace panel, specify information about the table space of the database. When you click Next, the product installation program connects to the database server and validates the information that you specified.
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 93 13. When the database validation is complete, on the Application Server Type panel, specify Oracle WebLogic Server for the product deployment. You must manually configure WebLogic Server and manually deploy application files. 14. On the Specify Maximo Users panel, enter Maximo database user information. Maximo administration user The product administrator user ID that is used for initial configuration and adding users. Maximo system registration user The user ID that is used for the self-registration of users. Maximo system integration user The user ID that is used with enterprise adapters.
Custom user ID and password values are stored in the Maximo database. The default user IDs of maxadmin, maxreg, and maxintadm are also created as users in the Maximo database. Creation of the default user IDs is done for internal processing purposes. If you use Maximo database security for authentication and authorization, the default user IDs can be used to log in to the application. If you regard this condition as a security risk, you can modify the passwords for the default user IDs. You modify passwords for the user IDs in the Users application. 15. On the SMTP Configuration panel, specify the SMTP configuration information that is used by workflows to communicate with workflow participants. The administrator e-mail address is the e-mail address that is used to send messages. If you leave the fields blank, you must configure the SMTP parameters through the product interface as a post-installation task. 16. On the Data Integration and Context Menu Services Options panel, click the button that indicates where the database tables for these functions should be created: in the Maximo ("same") database, or in a separate database instance that you have already created for this purpose. If you are installing the Entry edition, choose the Maximo database. These tables will be created but will not be used by the Entry edition. 17. On the Base Language Selection panel, specify the base language for the installation. 18. On the Additional Language Selection panel, you can optionally specify one or more additional languages that the installation is to support. 19. On the Run Configuration Step panel, specify how to perform the configuration step of the installation. If you do not select an option, the configuration step proceeds when you click Next. Copy files now, but perform the installation configuration step later Select this option to copy files from the installation source to the administrative workstation. You must perform the configuration step at a later time to complete the deployment.
Important: Do not install another product before completing the configuration step of the original installation. Installing another product before running the configuration step for this installation overwrites the taskstore, which prevents the original installation from ever being deployed.
94 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) The configuration values that you specify are stored in the install_home\maximo\applications\maximo\properties\ maximo.properties and install_home\etc\install.properties files. You run the configuration steps outside of the product installation program by using the taskrunner utility, in the install_home\scripts directory. Run the taskrunner utility from the command line. install_home\scripts\taskrunner [CONTINUE
The taskrunner uses the configuration values that are stored in the maximo.properties and install.properties files to configure SmartCloud Control Desk. If you run taskrunner with the NOSTOPONERROR parameter, the taskrunner continues despite errors. If you run taskrunner with the STOPONERROR parameter, the taskrunner stops when it encounters an error. If you used STOPONERROR, you can rectify the conditions that caused the error. You can then resume the installation at the point where the last successfully completed task was recorded in the previous attempt by starting taskrunner with the CONTINUE parameter. Defer the update of the Maximo database Select this option if you want to manually run the database update task for the product deployment. This option can be used when there is a fix pack available that addresses known issues with the updatedb script. In this scenario, you choose the Defer the update of the Maximo database option, apply the fix pack, and then run the updatedb -v1 command manually. 20. On the Choose Shortcut Folder panel, specify where you want SmartCloud Control Desk icons created. If you select In the Start Menu and use Internet Explorer, add the SmartCloud Control Desk URL to the trusted sites web content zone. Disable the option that requires server verification for all sites in the zone. Do not select In the Quick Launch Bar. The selection does not create a shortcut in the Quick Launch bar. Attention: Shortcuts are created for Windows systems only. Because WebLogic Server deployments are a manual process, you must manually update any shortcuts that you create. You update shortcuts after you have manually deployed the SmartCloud Control Desk EAR files. 21. On the Input Summary panel, review the information that you have provided for the product installation program. If necessary, use Previous to return to previous panels to change values. 22. On the Pre-Installation Summary panel, review the installation information, then click Install. The installation process begins. You can monitor the progress by viewing the messages that are displayed above the progress bar. 23. On the Installation Completed panel, review any information presented, then click Done. Attention: In some cases, on AIX systems, the Installation Completed panel might appear blank. Click Done to exit the installation program. What to do next
Complete the post installation tasks that are required for installing with manual middleware configuration. You can install optional content and integration
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 95 modules from the launchpad. You must now deploy the maximo.ear and maximoiehs.ear files. “Deploying EAR files” on page 194 This section contains information about deploying SmartCloud Control Desk EAR files manually into Oracle WebLogic Server.
Installing optional content Install the relevant optional content package for your edition of the product.
Optional content is often used in development environments as a way to begin developing your own content.
If you do not install optional content during the product installation process, you can install it later. If you install it later, you must update the database and rebuild and deploy the maximo.ear file.
Installing optional integration modules Install integration module packages in order to set up integrations with other products.
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 database and rebuild and deploy the maximo.ear file.
Post installation for Oracle WebLogic Server deployments There 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 SmartCloud Control Desk deployment, the installation program produces an EAR file. You must then manually deploy that file to Oracle WebLogic Server.
When using Oracle WebLogic Server, you must modify the weblogic.xml file and rebuild the maximo.ear file before deploying it. Procedure 1. 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 the server where you installed Oracle WebLogic Server. Use any file transfer protocol that is available.
96 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) b. The oraclethin.jar file is in the install_home\maximo\applications\ maximo\lib directory. The default install_home directory is C:\IBM\SMP\Maximo\Applications\Maximo\lib. Copy the oraclethin.jar file to the J2EE server and into the wls11g/server/lib directory. For example, C:/Oracle/wls11g/server/lib. 3. Edit the domain configuration file for proper 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. Two instances 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 Oracle WebLogic Server. e. Increase the Java Heap parameters by searching for MEM_ARGS and setting the 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 (-) sign before each parameter and to include the m after each value. f. Search for set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES%. Insert an option right after this string as follows: -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
The entry looks like this 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:
The user name and password values must match an existing user account in the Authentication provider for the default security realm. If you save the file as boot.properties and locate it in the mydomain folder (for example, C:\BEA\User_projects\domains\mydomain), the server automatically uses this file during its subsequent startup cycles. The first time you use this file to start a
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 97 server, the server reads the file and then overwrites it with an encrypted version of the user name and password. 6. Verify settings by starting Oracle WebLogic Server. To ensure that the edits that you made to the previous Oracle WebLogic Server files were accurate, start the Oracle 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 files You are now ready to deploy the EAR files from the Oracle WebLogic Server Administration Console. Deploying the EAR files starts the Maximo Application Server. Before you begin
Windows Windows If MAXIMOSERVER is not running, start it from a command prompt.
UNIX UNIX Ensure that the Oracle WebLogic Server daemon is running. About this task
In order to view the Oracle WebLogic Server Administration Console, you need to also install a Java Virtual Machine (JVM). Newer versions of Windows might not ship with JVM. Procedure 1. Change to the my_domain directory:
Windows Windows From a command prompt, change directory path to: drive_name:\weblogic_install_dir\user_projects\domain\my_domain
UNIX UNIX Open a Terminal window (or a command prompt, if you are telneting from a Windows computer) and change directory as follows: cd /home/mxadmin/weblogic_install_dir/user_projects/domains/my_domain 2. Type
Windows Windows startWebLogic.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 by typing 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 and password.
98 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 5. In the left pane, click the Lock&Edit button in the Change Center section to set the server to edit mode. 6. In the left pane, 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 “Install this deployment as an application” and click Next to continue the deployment. 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 42 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 requests. The Start Application Assistant displays. 18. Click Yes to start the system.
Setting the Oracle WebLogic Server host name Setting the Oracle WebLogic Server host name manually to access application help information. About this task
By default, the property used to store the host name for the SmartCloud Control Desk help system is set to localhost. The fully qualified host name of the Oracle WebLogic Server must be configured in the help system property to view SmartCloud Control Desk application help topics. Complete this step after you have deployed SmartCloud Control Desk EAR files to the Oracle WebLogic Server. Procedure 1. 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.
Chapter 4. Deploying manually reusing existing middleware (Scenario 3) 99 Results
You are now able to access application help topics in the SmartCloud Control Desk user interface.
Language deployment after database update deferral Selecting the option to defer the update of the Maximo database when installing the product, affects how you deploy languages.
During installation, you have the option to defer the database update task. This option prevents writing data to the database during the installation. The installation program is limited to copying files to the administrative system and registering product process solution packages. You add languages by completing the installation, manually updating the database, and then updating languages manually. “Manually deploying languages after database update deferral” on page 44 Languages must be deployed manually if you defer database updates by the installation program. Manually deploying languages after database update deferral Languages must be deployed manually if you defer database updates by the installation program. Before you begin
You must have run updatedb command before manually configuring languages for PSI packages. About this task
To manually configure languages for PSI packages, complete the following steps: Procedure
Update language support for the Maximo core components. Files for the language selections you made during the installation are extracted to the C:\IBM\SMP\Maximo\Tools\Maximo\locale\xliff\ directory on the system. 1. 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 2. To add one or more languages as additional languages for use with the product, run the following command for each language you want to add: install_home\maximo\tools\maximo\TDToolkit.bat -ADDLANGlocale -maxmessfix
100 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 5. Silent installation
SmartCloud Control Desk provides the option of installing silently.
The SmartCloud Control Desk silent installation option allows you to interface with the SmartCloud Control Desk installation program using a command prompt (not the SmartCloud Control Desk launchpad), and a response file.
Installing SmartCloud Control Desk silently SmartCloud Control Desk can be installed silently through the use of an installation response file. Before you begin
You must complete a successful SmartCloud Control Desk installation in order to produce a response file to use with a silent installation operation. Alternatively, you can use one of the sample response files provided on the product media and modify it according to your needs.
You must verify that all response file paths are formatted correctly. For example, a UNIX style path statement in the response file might look like this: USER_INSTALL_DIR=K:/IBM/max_dev
If this path is contained in a response file that is used with a Windows administrative system, an error occurs. The Windows equivalent in this example 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 SmartCloud Control Desk installation program fields during an attended installation. Remove the INSTALLER_UI=silent property from the response file before using it with the SmartCloud Control Desk installation program. The installation program uses default values by reading from the response file. The SmartCloud Control Desk installation program uses the response file automatically if it is named installer.properties or install.properties and is located in the same directory. You do not have to specify the response file name when starting the SmartCloud Control Desk installation program.
Note: This response file can also be used with the SmartCloud Control Desk uninstallation program in order to uninstall SmartCloud Control Desk silently. About this task
To install SmartCloud Control Desk silently, complete the following steps: Procedure 1. Make configuration choices 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
© Copyright IBM Corp. 2007, 2011 101 For 64–bit systems, use the following command: install_win64.exe -r
These files are located in the SmartCloud Control Desk\samples directory of the product image. If the response file is created by recording an actual installation, you must add an entry for LICENSE_ACCEPTED=true. If you are using a sample response file, you must change the entry from false to true. If a silent installation is started and this entry is not included in the response file then the install ends immediately. No messages or log file are created. If you plan to deploy SmartCloud Control Desk using middleware hosted on both Windows and UNIX operating systems, your response file contains both Windows and UNIX values. These values include directory paths and executable file names. In some cases, the response file is not generated because the user starting the installation program does not have write access to the target directory. In this scenario, the installation program does not report an error. The response file is not written to the target directory and the log file is not produced in the ibm\smp\logs directory, To resolve this issue, ensure the user invoking the installation program has write access to the target directory before running the installation program to produce a response file. 2. Open the response file in a text editor and change the INSTALLER_UI property to INSTALLER_UI=silent. Passwords are stored in clear text format. You must edit the CONFIRM_PASSWORD fields contained in the response file to match its corresponding password value used for each task. For example, ensure that CONFIRM_PASSWORD matches RXA_PASSWORD in the following example:
102 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) #Middleware Server Information #------MIDDLEWARE_SERVER=myserver.mydomain.com RXA_USER_ID=root RXA_PASSWORD=mypassword CONFIRM_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
You must include the full path when specifying the response file and it must be located on the C:\ drive of your system. Results
The installation proceeds silently, using the values provided in the response file.
Response files that include fields for Oracle configuration must be edited to remove extraneous backslashes. A response file that includes Oracle as a deployment option is generated with fields like the following excerpt: DB_INSTALL_DIR=C\:/oracle/product/10.2.0/db_1 INSTANCE_LOCATION=C\:/oracle/product/10.2.0/db_1/dbs USER_INSTALL_DIR=C\:/IBM/ USER_SHORTCUTS=C\:/Documents and Settings/All Users/Start Menu/Programs /process automation engine MAXIMO_INSTALL_DIR=C\:/IBM/maximo
Remove the backslash that appears directly after the drive letter. After editing the previous example, your response file looks like the following excerpt: DB_INSTALL_DIR=C:/oracle/product/10.2.0/db_1 INSTANCE_LOCATION=C:/oracle/product/10.2.0/db_1/dbs USER_INSTALL_DIR=C:/IBM/ USER_SHORTCUTS=C:/Documents and Settings/All Users/Start Menu/Programs /process automation engine MAXIMO_INSTALL_DIR=C:/IBM/maximo
If you attempt to install SmartCloud Control Desk silently, and the installation UI appears, check inside the response file and be sure that it contains this line: INSTALLER_UI=silent
Silent installation properties Silent installation properties are recorded in an installation response file. Silent installation response files are generated when the installation program is started with the parameters described in the silent installation procedure. Alternatively, a silent installation response file can be created and populated manually. Common silent installation properties
The following properties are common to all deployments. Table 6. Common silent installation response file properties Category Property Definition File header INSTALLER_UI=SILENT This property must be set so the file can be used with the product installation program.
Chapter 5. Silent installation 103 Table 6. Common silent installation response file properties (continued) Category Property Definition Package INSTALL_SOME_PACKAGES=0 If only a subset of packages can be deployment set installed, set this value to 1. This allows the product installation program to continue. License LICENSE_ACCEPTED=TRUE Set this value to true to accept the Agreement license agreement or false to reject it. Installation folder USER_INSTALL_DIR=installation path Set an installation path. For example, for UNIX, /opt/IBM/SMP or for Windows, C:\\IBM\\SMP. Installation INSTALLATION_DESCRIPTION Description of the installation description location. Deployment type SIMPLE=0 Installation is set to a type of SIMPLE. Set to 0 to disable. Set to 1 to enable. If SIMPLE is enabled, ADVANCED must be disabled. ADVANCED=1 Installation is set to a type of ADVANCED, which is a Custom installation. Set to 0 to disable. Set to 1 to enable. If ADVANCED is enabled, SIMPLE must be disabled. Middleware MIDDLEWARE_SERVER=host name Set the host name of the system Server hosting all middleware. Information (only used for Simple installations) RXA_USER_ID=user name Set the user ID for accessing the system hosting all middleware. RXA_PASSWORD=password Set a password for the user ID for accessing the system hosting all middleware. Import MWI_IMPORT_DATA=0 Set this parameter to import Middleware configuration data from the Installation middleware installation program. Program Information Set to 0 to disable. Set to 1 to enable. MWI_HOSTNAME=host name Set the host name of the system hosting the middleware installation program workspace. MWI_USER_ID=user name Set a user ID used to access the system hosting the middleware installation program workspace. For example, root. MWI_PASSWORD=passsword Set a password for the user ID used to access the system hosting the middleware installation program workspace.
104 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 6. Common silent installation response file properties (continued) Category Property Definition MWI_LOCATION=path Set a path for the location of the middleware installation program workspace. For example, for UNIX, /root/ibm/tivoli/mwi/workspace or for Windows, C:\\ibm\\tivoli\\mwi\\workspace. SMTP SMTP_SERVER=host name Set the name of the system hosting Configuration the SMTP server responsible for distributing administration messages to the SmartCloud Control Desk administrator. ADMIN_EMAIL=email address Set the email address for the SmartCloud Control Desk administrator. Run RUN_CONFIG_NO=0 Set the behavior of the run Configuration configuration step. Step Set to 0 to disable (run the configuration step at install time). Set to 1 to enable (defer the configuration step). DEPLOY_EAR_NO=0 Set the behavior of the EAR deployment step.
Set to 0 to disable (deploy the EAR at install time). Set to 1 to enable (defer deployment of the EAR). DEFER_DB_UPDATE=0 Set the behavior of the database update step.
Set to 0 to disable (run updateDB at install time). Set to 1 to enable (defer updateDB). Shortcut Folder USER_SHORTCUTS=path Set a path for shortcuts. For example, for Windows, C:\\Documents and Settings\\Administrator\\ Desktop\\process automation engine. Installer version LAUNCH_NEW_INSTALLER=TRUE If a more recent version of the installation program was found in the target install directory specified. This circumstance indicates that you are using an older version of the installation program. In order to use the newer version of the installation program, set this value to TRUE.If you set this value to FALSE, the older version of the installation program is used to perform the installation.
Chapter 5. Silent installation 105 Users silent installation properties
The following properties are for users created by or identified to the installation program. Table 7. Users silent installation properties Category Property Definition User Information MAXADMIN_USER_NAME=user name Set a user name for the Maximo administrator. For example, maxadmin. MAXADMIN_PASSWORD=password Set a password for the Maximo administrator. For example, maxadmin. MAXREG_USER_NAME=user name Set a user name for the self registration user. This user is responsible for the process by which users can create their own accounts. For example, maxreg. MAXREG_PASSWORD=password Set a password for the self registration user. For example, maxreg. MXINTADM_USER_NAME=user name Set a user name for the internal user. For example, mxintadm. MXINTADM_PASSWORD=password Set a password for the internal user. For example, mxintadm.
Common database silent installation properties
The following properties contain common information about the database used for the deployment. Table 8. Common database silent installation response file properties Category Property Definition Database Type DB_TYPE_DB2=1 Set the database type to DB2. Set to 0 to disable. Set to 1 to enable. Only one Database Type can be enabled. DB_TYPE_ORACLE=0 Set the database type to Oracle. Set to 0 to disable. Set to 1 to enable. Only one Database Type can be enabled. DB_TYPE_SQLSERVER=0 Set the database type to Microsoft SQL Server. Set to 0 to disable. Set to 1 to enable. Only one Database Type can be enabled. Database DB_HOST_NAME=host name Set the host name of the database server. DB_PORT=port Set the database port. For example, 50005. DB_NAME=name Set a name for the database. For example, maxdb75.
DB2 and SQL SERVER
106 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 8. Common database silent installation response file properties (continued) Category Property Definition DB_INSTANCE=instance Set a name for the database instance to use with the product. For example, ctginst1.
DB2 and Oracle only.
DB_USER=user name Set the name of the user ID to access the database. For example, maximo. DB_PASSWORD=password Set a password for the database user ID. For example, maximo. Database AUTOMATE_DB=1 Configure the automatic Configuration configuration of the database by Automation the installation program. Set to 0 to disable. Set to 1 to enable. Either AUTOMATE_DB or DO_NOT_AUTOMATE_DB can be enabled at one time. DO_NOT_AUTOMATE_DB=0 Configure the automatic configuration of the database by the installation program. Set to 0 to disable. Set to 1 to enable. Either AUTOMATE_DB or DO_NOT_AUTOMATE_DB can be enabled at one time. Remote Access DB_RXA_USER=user name Set the name of the user ID to Authorization access the remote database server system. For example, root.
Only required if AUTOMATE_DB was enabled.
Oracle or DB2 only. DB_RXA_PASSWORD=password Set a password for the remote access user ID.
Only required if AUTOMATE_DB was enabled.
Oracle or DB2 only. Database DB_INSTALL_DIR=path Enter the database server Administration installation path. For example, UNIX /opt/IBM/db2/V9.7 /opt/oracle/product/ 11.2.0/db_1 Windows C:\Program Files\oracle\product\ 11.2.0\db_1
Only required if AUTOMATE_DB was enabled.
Oracle or DB2 only.
Chapter 5. Silent installation 107 Table 8. Common database silent installation response file properties (continued) Category Property Definition DB_ADMIN_USER=user name Set the name of the database administrator. For example, db2admin or Sys.
Oracle or DB2 only. DB_ADMIN_PASSWORD=password Set a password for the remote access database administrator.
Oracle or DB2 only. Database Table DB_TABLE_SPACE_NAME=table space name Set the name of the database table Space space. For example, MAXDATA.
DB2 and Oracle only. DB_TABLE_SPACE_SIZE=table space size in Mb Set the size of the database table space, in Mb. For example, 5000.y.
Only required if AUTOMATE_DB was enabled. DB_TEMP_TABLE_SPACE_NAME=temporary table space Set the name of the database name temporary table space. For example, MAXTEMP.
DB2 and Oracle only. DB_TEMP_TABLE_SPACE_SIZE=temporary table space size in Set the size of the temporary Mb database table space, in Mb. For example, 1000.
Only required if AUTOMATE_DB was enabled.
DB2 and Oracle only. DB_INDEX_TABLE_SPACE_NAME=index table space name Set the name of the database index table space. For example, MAXDATA.
DB2 and Oracle only. DB_INDEX_TABLE_SPACE_SIZE=index table space size in Mb Set the size of the index database table space, in Mb. For example, 5000.
Only required if AUTOMATE_DB was enabled.
DB2 and Oracle only.
DB2 silent installation properties
The following properties contain information about an DB2 database used for the deployment. These properties are only necessary if you are using a DB2 database for deployment. Table 9. DB2 silent installation response file properties Category Property Definition DB2 DB_SCHEMA=schema Designate the database schema. For example, maximo.
108 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 9. DB2 silent installation response file properties (continued) Category Property Definition DB_WIN_SERVICE_USER=user name Set the name of the database service owner in Windows. For example, ctginst1.
Only required if AUTOMATE_DB was enabled. DB_WIN_SERVICE_PASSWORD=password Set a password for the database service owner in Windows.
Only required if AUTOMATE_DB was enabled. DB2_VARCHAR=0 Configure varchar or vargraphic in the database by the installation program. Set to 0 to use vargraphic formatting. Set to 1 to use varchar.
varchar formatting supports English only.
Oracle silent installation properties
The following properties contain information about an Oracle database used for the deployment. These properties are only necessary if you are using an Oracle database for deployment. Table 10. Oracle silent installation response file properties Category Property Definition Oracle ORACLE_OWNER_ID=user name Set the Oracle software owner user ID. For example, oracle.
Only required if AUTOMATE_DB was enabled. ORACLE_OWNER_PASSWORD=password Set the Oracle software owner password.
Only required if AUTOMATE_DB was enabled. INSTANCE_LOCATION=instance location Set the Oracle database instance location. For example, /opt/oracle/product/11.2.0/db_1.
Only required if AUTOMATE_DB was enabled.
Microsoft SQL Server silent installation properties
The following properties contain information about a Microsoft SQL Server database used for the deployment. These properties are only necessary if you are using a Microsoft SQL Server database for deployment.
Chapter 5. Silent installation 109 Table 11. Microsoft SQL Server silent installation response file properties Category Property Definition Microsoft SQL SQL_DATA_FILE_NAME=data file name Set the file name for the Microsoft Server SQL Server data source. For example, maxdb75_dat.
Only required if AUTOMATE_DB was enabled. DB_TABLE_SPACE_SIZE=data source size in Mb Set the size of the Microsoft SQL Server data source, in Mb. For example, 1000.
Only required if AUTOMATE_DB was enabled. SQL_ADMIN=user name Set the name of the Microsoft SQL Server administrator. For example, sa.
Only required if AUTOMATE_DB was enabled. SQL_ADMIN_PW=password Set a password for the Microsoft SQL Server administrator.
Only required if AUTOMATE_DB was enabled. SQL_LOG_FILE_NAME Microsoft SQL Server log name. For example, maxdb75_log
Only required if AUTOMATE_DB was enabled.
Common application server silent installation properties
The following properties contain common information about the application server used for the deployment. Table 12. Common application server silent installation response file properties Category Property Definition Application APPLICATION_SERVER_TYPE_WAS=1 Configure the application server Server Type used for the deployment. Set to 0 to disable. Set to 1 to enable.
Only one Application Server Type can be enabled. APPLICATION_SERVER_TYPE_BEA=0 Configure the application server used for the SmartCloud Control Desk deployment. Set to 0 to disable. Set to 1 to enable.
Only one Application Server Type can be enabled.
110 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Security silent installation properties
The following properties are used to configure security. Table 13. Security silent installation response file properties Category Property Definition Security LDAP_OPTION1=1 Configure security so that an LDAP resource is used for user authorization and authentication.
Set to 0 to disable. Set to 1 to enable.
Only one LDAP_OPTION parameter can be enabled at one time.
If LDAP_OPTION1 is enabled, then the VMM_USER_RDN, VMM_GROUP_RDN and CREATE_DEFAULT_USERS properties are also required to have valid values. LDAP_OPTION2=0 Configure security so that an LDAP resource is used for user authentication only. Group management is managed from the SmartCloud Control Desk application. Authorization data is stored in the database.
Set to 0 to disable. Set to 1 to enable.
Only one LDAP_OPTION parameter can be enabled at one time. LDAP_OPTION3=0 Configure security so that user authentication and authorization are both managed from the SmartCloud Control Desk application. Authentication and authorization data is stored in the database.
Set to 0 to disable. Set to 1 to enable.
Only one LDAP_OPTION parameter can be enabled at one time. VMM_USER_RDN=user RDN Set a relative distinguished name for users for VMM. For example, ou=users,ou=SWG,o=IBM,c=US. VMM_GROUP_RDN=group RDN Set a relative distinguished name for groups for VMM. For example, ou=groups,ou=SWG,o=IBM,c=US.
Chapter 5. Silent installation 111 Table 13. Security silent installation response file properties (continued) Category Property Definition CREATE_DEFAULT_USERS=1 Have the SmartCloud Control Desk installation program create default users automatically.
Set to 0 to disable. Set to 1 to enable.
Language silent installation properties
The following properties are used to configure languages. Table 14. Language silent installation response file properties Category Property Definition Base BASE_ARABIC=0 Set this language Language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_BRAZILIAN_PORTUGUESE=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_CROATIAN=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_CZECH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
112 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 14. Language silent installation response file properties (continued) Category Property Definition BASE_DANISH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_DUTCH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_ENGLISH=1 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_FINNISH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_FRENCH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
Chapter 5. Silent installation 113 Table 14. Language silent installation response file properties (continued) Category Property Definition BASE_GERMAN=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_HEBREW=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_HUNGARIAN=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_ITALIAN=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_JAPANESE=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
114 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 14. Language silent installation response file properties (continued) Category Property Definition BASE_KOREAN=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_NORWEGIAN=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_POLISH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_RUSSIAN=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_SIMPLIFIED_CHINESE=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
Chapter 5. Silent installation 115 Table 14. Language silent installation response file properties (continued) Category Property Definition BASE_SLOVAK=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_SLOVENIAN=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_SPANISH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_SWEDISH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. BASE_TRADITIONAL_CHINESE=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
116 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 14. Language silent installation response file properties (continued) Category Property Definition BASE_TURKISH=0 Set this language as the base language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. Additional ADD_ARABIC=0 Set this language Languages as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_BRAZILIAN_PORTUGUESE=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_CROATIAN=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_CZECH=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
Chapter 5. Silent installation 117 Table 14. Language silent installation response file properties (continued) Category Property Definition ADD_DANISH=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_DUTCH=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_ENGLISH=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_FINNISH=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_FRENCH=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
118 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 14. Language silent installation response file properties (continued) Category Property Definition ADD_GERMAN=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_HEBREW=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_HUNGARIAN=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_ITALIAN=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_JAPANESE=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
Chapter 5. Silent installation 119 Table 14. Language silent installation response file properties (continued) Category Property Definition ADD_KOREAN=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_NORWEGIAN=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_POLISH=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_RUSSIAN=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_SIMPLIFIED_CHINESE=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
120 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 14. Language silent installation response file properties (continued) Category Property Definition ADD_SLOVAK=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_SLOVENIAN=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_SPANISH=1 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_SPANISH=1 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable. ADD_TRADITIONAL_CHINESE=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
Chapter 5. Silent installation 121 Table 14. Language silent installation response file properties (continued) Category Property Definition ADD_TURKISH=0 Set this language as an additional language used by the SmartCloud Control Desk application.
Set to 0 to disable. Set to 1 to enable.
122 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 6. Programmatically verifying that the installation was successful
After you have exited the SmartCloud Control Desk installation program without encountering any errors, you can verify that the installation completed successfully. The installation is programmatically verified through the use of post installation validation utilities. Before you begin
The JAVA_HOME environment variable must be set on the system before you can use the verification utilities. About this task
During installation, the SmartCloud Control Desk installation program performs a simple health check. This health check consists of logging in to the application to verify availability. This health check might not be sufficient to verify a successful installation in all deployment scenarios. For example, if, during installation, you select the option to deploy the application EAR file at a later date, this health check cannot verify the installation. This simple health check is also insufficient for verifying an upgrade.
Two post installation validation utilities are available after the product has been deployed. The middlewareValidate utility is used to verify the middleware. The installValidation utility is used to validate the product installation. These command-line utilities are used to verify the installation and configuration of the product in a more complete manner. These utilities can also be used to verify an existing deployment after changes in the environment, such as changes to host names, user IDs, and passwords.
Results of the installValidation utility are logged in installValidationTrace00.log. This log is found in the \ibm\smp\logs directory on the administrative workstation. Procedure 1. Log in to the server using the user ID that was used to run the installation program. If you intend to use the installValidation utility, log in to the administrative workstation. If you intend to use the middlewareValidate utility, log in to the server hosting the middleware. 2. Ensure the JAVA_HOME environment variable is set properly to the location of a JRE 1.6 installation. 3. To verify middleware installation, from the middleware image, update the middleware.properties file with the installation parameter values for middleware components to be verified, change directory to \HealthCheck and run the middlewareValidate.[sh|bat] command. To verify product installation, from the administrative workstation, change directory to \ibm\smp\scripts and run the installValidation.bat command. For either command, use the parameters described below:
© Copyright IBM Corp. 2007, 2011 123 Table 15. Verification utilities parameters Program Syntax parameters Input installValidation.bat -action Use -action validate to start the validation of the product installation.
The -action parameter is the only mandatory parameter when using the installValidation utility. -trace Verification progress information is written to the screen during the verification process. You can modify the output using the -tracing parameter. v minimal Progress information is limited to error information. v normal Information includes individual test progress, individual test results, and overall progress of the entire verification process. This is the default mode of tracing. v verbose In addition to providing normal progress information, verbose tracing includes the test class name, test method name, and corrective action information. -confirm You are prompted before each test is started. You must confirm each test to be performed. There is no input for this parameter. -component You can provide a comma-delimited list of directories containing the test objects to limit testing to a specific set of tests.
These test objects must be located in the \ibm\smp\HealthValidation\ directory. For the product installation program, only the CTGIN folder is provided. -dbuser Provide the user ID used to access the database. -dbpwd Provide the password of the user ID used to access the database. -maxuser Provide the SmartCloud Control Desk administrator user ID. For example, maxadmin. -maxpwd Provide the password for the SmartCloud Control Desk administrator user ID.
124 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 15. Verification utilities parameters (continued) Program Syntax parameters Input middlewareValidate.[sh|bat] -middlewareproperties Use -middlewareproperties file
where file is the location of the middleware.properties file. By default, this file is found on the middleware installation media in the \HealthCheck directory.
The middleware.properties contains the middleware installation properties, such as installation locations and ports. User names and passwords are not stored in this plain-text file. Some of the properties common to all platforms have been defined default values, but platform-specific properties like installation locations need to be updated in this file before starting the middlewareValidate utility.
The -middlewareproperties parameter is the only mandatory parameter when using the middlewareValidate utility. -trace Verification progress information is written to the screen during the verification process. You can modify the output using the -trace parameter. v minimal Progress information is limited to error information. v normal Information includes individual test progress, individual test results, and overall progress of the entire verification process. v verbose In addition to providing normal progress information, verbose tracing includes the test class name, test method name, and corrective action information.
If this option is not provided, by default, no output displayed.
Chapter 6. Programmatically verifying that the installation was successful 125 Table 15. Verification utilities parameters (continued) Program Syntax parameters Input -component Specify the middleware components: v DBSERVER - verify installation of the IBM DB2 server. v DIRSERVER - verify installation of the optional IBM Tivoli Directory Server. v LDAPSERVER - verify configuration of the optional IBM Tivoli Directory Server.
One or more of these keywords can be specified as comma separated list. If this argument is skipped, the tool assumes all the components are selected to verify. -bindUser Provide the bind user.
Required to verify LDAPSERVER, the bind user credentials, bind Distinguished Name and bind password are required to be specified with the -bindUser and -bindPass options. -bindPass Provide the password for the bind user.
Required to verify LDAPSERVER, the bind user credentials, bind Distinguished Name and bind password are required to be specified with the -bindUser and -bindPass options.
For example, installValidation.bat -action validate
Results
The installValidation.bat validation utility results are logged in ctginstallvalidationtrace00.log. This log is found in the \ibm\smp\logs directory on the administrative workstation.
The middlewareValidate.[sh|bat] validation utility results are logged in CTGInstallValidationTrace.log. This log is found in the HealthCheck directory.
126 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 7. Verifying the installation manually
After you have exited the SmartCloud Control Desk installation program without encountering any errors, you can further verify that the installation completed successfully. The installation is manually verified by locating key artifacts and performing a few simple tasks. Before you begin
The product installation program performs installation verification, or a health check, by logging in to the product before exiting the installation. The product installation program returns a success message if all installation steps, including the product log in task, are successful. If the health check task is unsuccessful, a HealthCheckFailed error is thrown for the getUrlContentString function. This error is located in the install_home\logs\CTGInstallTraceXX.log file, where XX is a two-digit number such as 00. About this task
To further verify that the SmartCloud Control Desk installation was completed successfully, perform the following verification procedures: Procedure 1. Examine the CTGInstallTrace00.log file for success messages. The following success messages are found in the CTGInstallTrace00.log file and can be used to verify which phases of the installation were successful: v CTGIN2114I: The database was created successfully v CTGIN2135I: Tablespace maxdata created successfully v CTGIN2135I: Tablespace maxtemp created successfully v CTGIN2079I: process automation engine database configuration completed successfully (This message indicates that maxinst finished successfully.) v CTGIN2253I: buildmaximoear.cmd completed successfully v CTGIN2253I: buildhelpear.cmd completed successfully v CTGIN2208I: runConfigurationStep completed successfully v CTGIN2370I: The installation finished successfully Search the CTGInstallTrace00.log file for the following message, which indicates that the maxinst task completed successfully: CTGIN2079I, maxinst.*completed 2. Compare the packages chosen for installation with the packages that were installed. The Package Summary panel of the SmartCloud Control Desk installation 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 installed on the system. Use the solutioninstaller command to list installed packages: install_home\bin\setupPSIenv.bat install_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
© Copyright IBM Corp. 2007, 2011 127 successful. Once you have logged in, navigate through the GoTo menu to verify that it has been populated with the applications you expect. If you experience problems accessing the product, clear the cache of your browser and try again.
128 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 8. Installing Integration Composer
After you have successfully installed the IBM SmartCloud Control Desk components, you can optionally install (or upgrade) Integration Composer, an integration tool that imports information technology (IT) data into the Maximo database.
You can use the Launchpad to install Integration Composer. However, if necessary, you can install Integration Composer on a UNIX operating system in console mode, from the command line.
When you install Integration Composer and IBM SmartCloud Control Desk from the Launchpad, the installer automatically updates the Integration Composer database tables in the Maximo database.
Integration Composer overview Integration Composer is the IBM application for transforming and importing inventory data about deployed hardware and software. This inventory data is imported from a discovery or system management tool database into the Maximo database tables for deployed assets or configuration items.
With Integration Composer, an enterprise can aggregate data collected by external discovery tools and integrate it into the Maximo database, creating a central repository for enterprise IT asset management, reporting, and decision support.
To collect the data about deployed assets or configuration items, a discovery tool scans computers, network devices, and network printers deployed in an enterprise and records information about the hardware and software it finds there. Integration Composer uses an integration adapter to transform the data collected by the discovery tool and move it from the discovery tool database into the Maximo database.
You can view imported data from various applications on your system. The data is also used to generate reports.
Note: Integration Composer is used to import hardware and software inventory data from a discovery tool database into the Deployed Asset, Actual CI, or (for the purposes of asset initialization) Asset tables in the Maximo database. The import or export of data into or out of other tables within the Maximo database is accomplished using a different tool, the integration framework.
Installation prerequisites Before installing, you must have the IBM Java Software Development Kit prerequisite for Integration Composer on your system, and any software that adversely affects the InstallAnywhere installation program must be removed.
IBM Java SDK 6.0 for the appropriate operating system is an installation prerequisite that must be present on the Integration Composer computer. The IBM Java SDK is provided on the product DVDs.
© Copyright IBM Corp. 2007, 2011 129 The installation or upgrade has to run on JRE 1.6, so it must be set as the system's Java virtual machine (JVM). If more than one JRE is installed on the computer, the PATH and CLASSPATH system variables must indicate JRE 1.6.
UNIX On UNIX-based operating systems, be sure the PATH environment variable includes the location of the Java Virtual Machine (for example, Java60).
Because the following software can adversely affect InstallAnywhere—the installation program used by Integration Composer—disable the following programs before attempting to install Integration Composer: v Antivirus software, such as Norton Antivirus or Symantec Client Firewall v Dell OpenManage v Search software, such as pcAnywhere
Use of these software programs affects the ability of InstallAnywhere to install programs; however, the problem is not specific to Integration Composer.
[Installation only] Before beginning your installation, make sure you have on hand the information on the target (Maximo) database described in Table 16 on page 131.
Performing the installation SmartCloud Control Desk installations that want to use Integration Composer should install it from the Launchpad, as described herein. If you need to install Integration Composer on a UNIX operating system in console mode, instructions to do that are also described. Results
When the installation completes successfully, you can access Integration Composer as follows:
Windows From the Start menu, or by entering the command: itic_installation_dir\ bin\startFusion.bat
The default Integration Composer installation directory for Windows operating systems is C:\Integration Composer. UNIX By entering the command: itic_installation_dir/bin/startFusion.sh
The default Integration Composer installation directory for UNIX operating systems is /home/user/Integration_Composer.
Installing using the Launchpad Windows UNIX The recommended way to install Integration Composer on Windows or UNIX operating systems is from the Launchpad. Before you begin
Make sure that you have up to 70 MB of free space for the installation directory. Procedure 1. Insert the Launchpad DVD into the server where you install Integration Composer.
130 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) If you are installing on a UNIX operating system, you might have to start the Launchpad manually by running the launchpad.sh command, which is located in the root directory of the Launchpad DVD. (On Windows operating systems, the launchpad.exe command runs automatically.)
Note: Confirm that the java -version command returns 1.6 before starting the installation. IBM Java SDK 6.0 with JRE 1.6 is provided on the product DVDs. 2. From the Launchpad, launch the Integration Composer installation program by clicking the link under Install Integration Composer. 3. In the IBM Tivoli Integration Composer window, select your language from the drop-down list at the bottom and click OK. 4. [UNIX only] In the Select Install Type window, select New Install and click Next. 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. Then click Next. 7. In the Choose Install Folder window, accept the default location or type a file path to specify where you want to install the product. (Or you can click Choose to browse and select the location you want.) Then click Next. 8. In the Database Type window, select your Maximo database type (the Maximo database is where the Integration Composer repository is installed) and click Next. IBM DB2 is the default. The Database Login Information window is displayed. 9. On the Database Login Information window, type login specifications for the database and click Next. The Database Login Information window is where you define the parameters for connecting to the Maximo database. The fields displayed in this window vary slightly, depending on the type of database you chose in the previous step. The following table defines the fields that the installation program displays 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 database resides Port Number Port number of the server on which the Maximo database resides Database Name (SID) For Oracle databases, this is the session identifier (SID) for the database; that is, the database or instance
Database Name For SQL Server or IBM databases, this is simply the name of the database Database Username Valid user name for signing in to the Maximo database Database/Schema Owner Database or schema owner
Tip: Make note of the values that you specified here. Later, when you launch Integration Composer, use the values entered in these fields to define connection parameters for the Maximo database.
Chapter 8. Installing Integration Composer 131 10. On the Update Software Instances window, select one of the following options and click Next: Yes, disable software updates If you select this option, when data is imported into the Maximo database, Integration Composer inserts or deletes software records but does not update software records. This option is preferred. No, don't disable software updates If you select this option, when data is imported into the Maximo database, Integration Composer updates existing software records. In the Software Class Name field, it is recommended to accept the default value Software. The Software Class name is used to identify the class that you do not want to update based on the choice you made. In the Deployed Assets target schema, the name is Software. 11. [UNIX only] In the Choose Internet Browser File window, accept the default browser or choose another browser to be used for displaying the Integration Composer online help, then click Next. 12. On the Preinstallation Summary window, review the installation details. (If necessary, use the Previous buttons to go back and make corrections, and use the Next buttons to return to this window.) When satisfied with the summary data, click Install. The Installing Integration Composer progress window displays during installation. When installing is finished, the Installation Complete window is displayed. 13. In the Installation Complete window, click Done. Installing on UNIX operating systems in console mode UNIX Use the procedure described here if you have to install Integration Composer 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\ITIC directory on the version 7.5 product DVD. Use the setup.bin command from the DVD layout to start the upgrade process: setup.bin ← setup.exe
The steps for installing Integration Composer on a UNIX-based operating system follow. Procedure 1. Sign on to the server as an administrator (for example, as root). 2. Save the binary Integration Composer installation file, setup.bin,onthe server where you intend to install Integration Composer. 3. Make sure JRE 1.6 is in your system path. To add JRE 1.6 to the path, enter the following commands (where JRE_location is the path for your IBM JRE; for example, /opt/ibm/java-i386-60/jre/ bin:$PATH):
132 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) JAVA_HOME=JRE_location export JAVA_HOME PATH=$JAVA_HOME:$PATH export PATH 4. Navigate to the location where you saved the setup.bin file. 5. Enter the following command to make the binary installation file executable: chmod +x setup.bin 6. Run the Integration Composer installation program in console mode by entering the following command at the shell prompt: sh ./setup.bin -i console In console mode, you are prompted to enter information line by line.
Note: Confirm that the java -version command returns 1.6 before starting the installation. IBM Java SDK 6.0 with JRE 1.6 is provided on the product DVDs. 7. In the Choose Locale step, type the number of your locale from the list of locales and press Enter. 8. In the Introduction step, review the Introduction information and press Enter. 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 is installed by doing one of the following: v Accept the default location and press Enter. v Type a different file path for the location and press Enter. 11. In the Choose Install Folder step, specify where you want to install Integration Composer 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) by typing the associated number; then press Enter. The Database Login Information step is displayed. This Database Login Information step is where you define the parameters for connecting to the Maximo database. The fields displayed in this step vary slightly, depending on the type of database you chose in the previous step. The following table defines the fields that the installation program displays for the supported databases.
Field Description Database Server Name Name of the server on which the target database resides Port Number Port number of the server on which the target database resides Database Name (SID) For Oracle databases, this is the session identifier (SID) for the database; that is, the database instance or For SQL Server or databases provided by IBM, this Database Name is simply the name of the database Database Username Valid user name for signing in to the target database
Chapter 8. Installing Integration Composer 133 Field Description Database/Schema Owner Database or schema owner
13. In the Database Login Information step, type each login specification for the database, one at a time, pressing Enter after each entry to advance to the next specification.
Tip: Make note of the values that you specified here. Later, when you launch Integration Composer, use the values entered in these fields to define connection parameters for the target data source. 14. In the Update Software Instances step, type a number to select one of the following options, and press Enter: v Yes, disable software updates If you select this option, when Integration Composer imports data into the target database, Integration Composer inserts or deletes software records but does not update software records. This option is preferred for performance reasons. v No, don't disable software updates If you select this option, when Integration Composer imports data into the target 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 press Enter to begin installing Integration Composer. The Installing progress bar displays 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 you are returned to the UNIX command prompt.
Confirming the installation This section explains how to verify that your new Integration Composer installation (or upgrade) is installed correctly. Procedure 1. 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 schema owner) username and password that you supplied during the installation.
134 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 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. If this number is displayed, Integration Composer was successfully installed.
Post-installation tasks This section provides instructions for verifying that Integration Composer is configured correctly after you install or upgrade. Verifying the settings in the Integration Composer fusion.properties file The fusion.properties file is the properties file for Integration Composer. Among other things, these properties specify Maximo and Integration Composer database-related properties and application properties. This verification task is to ensure that, after you have installed or upgraded Integration Composer, critical property 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
Procedure 1. Locate the Integration Composer fusion.properties file in your Integration Composer installation directory, itic_install_dir. 2. In the IBM Tivoli Integration Composer 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 Integration Services (DIS), is an optional component that Integration Composer works with to uniquely identify deployed assets or actual CIs (configuration items) and avoid duplication of asset or CI records in your database. By default, Integration Composer is configured to use this component, which assigns a globally unique identifier, the DIS GUID, to a deployed asset or actual CI based on defined naming rules. However, Integration Composer will not operate successfully if it is configured to use NRS (if the NRS property is set to true) but NRS is not installed and running. So, if you do not use NRS, be sure to set the NRS property to false so that Integration Composer will run successfully. IBM SmartCloud Control Desk, a product that uses Integration Composer to import deployed assets and actual CIs, requires DIS/NRS to perform automated linking of their authorized asset and CI counterparts. If you use IBM SmartCloud Control Desk, you should have DIS/NRS running and have the NRS property in the fusion.properties file set to true. Integration Composer recommends that DIS/NRS be installed and enabled. The NRS property is enabled (set to true) by default.
Chapter 8. Installing Integration Composer 135 3. In the IBM Tivoli Maximo Database Related Properties section, verify that the database schema owner, JDBC driver specification, and JDBC URL specification are correct. Use the following table as a guide:
Property Description Value mxe.db.schemaowner Database schema Enter the appropriate schema for your database; for example, dbo. owner mxe.db.driver JDBC driver This varies depending on the database, for example: specification 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.TdsDriver Note: Users upgrading from a previous release and who already have this (deprecated) driver can still use it for Microsoft SQL Server support. However, in the future, using the Microsoft JDBC driver for your SQL Server is recommended. 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_name Note: Users upgrading from a previous release and who already have this (deprecated) driver can still use it for Microsoft SQL Server support. However, in the future, using the Microsoft JDBC driver for your SQL Server is recommended. mxe.db.user Database user login name
4. UNIX In the Integration Composer Application Properties section, users of UNIX-based operating systems should check that the mxe.fusion.browser property specifies netscape. For UNIX, Netscape is the only supported Web browser for Integration Composer: mxe.fusion.browser=netscape
Note: Windows For Windows operating systems, the browser always defaults to Microsoft Windows Explorer.
136 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Changing the memory allocation in the startFusion file (optional) The startFusion file, named startFusion.bat in Windows operating systems or startFusion.sh in UNIX-based operating systems, is the startup file for the Integration Composer graphical user interface. This verification task is to ensure that, after you have installed or upgraded Integration Composer, the memory allocation in the startFusion file is correct. Before you begin
This task is optional. You need to perform it only if the Integration Composer graphical user interface does not start as described in “Confirming the installation” on page 134. About this task
The Integration Composer startFusion file is located in the Windows and UNIX installation 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 1536 megabytes 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 will not work for you. Procedure
If the Integration Composer graphical user interface does not start, check the memory setting for the start javaw.exe command in the startFusion file, and decrease 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 systems or executeMapping.sh in UNIX-based operating systems, is the Integration Composer script for running a mapping. This verification task is to ensure that, after you have installed Integration Composer, the memory allocation in the executeMapping file is correct. Before you begin
This task is optional. You need to perform it only if the Integration Composer mapping does not run, or if you just upgraded and had increased the amount of memory allocated to Integration Composer in your previously installed version.
Chapter 8. Installing Integration Composer 137 About this task
The Integration Composer executeMapping file is located in the Windows and UNIX-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 MB as the default amount of virtual RAM to allocate to the application. But, for example, if your server only has 1 GB of physical memory, the 1536M setting will not work for you. Procedure v If the Integration Composer mapping does not run, check the memory setting for the java command in the executeMapping file, and decrease memory. To do so, edit the executeMapping file and change the –Xmx parameter in the java command. For example, change -Xmx1536M to -Xmx1024M v [Upgrade only] If you previously increased the amount of memory allocated to Integration Composer imports, verify that your memory settings have not changed. If you have to increase the amount of memory assigned, edit the executeMapping file and change the –Xmx parameter in the java command. For example: change -Xmx1536M to -Xmx2048M
Uninstalling Integration Composer This section provides instructions for removing Integration Composer from Microsoft Windows and UNIX-based operating systems. Uninstalling Integration Composer on Windows operating systems Windows Use the procedure described here to remove Integration Composer from a Windows-based operating system. Procedure 1. In Microsoft Windows Explorer, go to the uninstall folder, installation_dir\ Uninstall_Integration_Composer, where Integration Composer 7.5 was installed. 2. In the uninstall folder, double-click the uninstall file, Uninstall_Integration_Composer.exe. The Integration Composer utility for uninstalling the application displays the Uninstall IBM Tivoli Integration Composer window. 3. Click Uninstall. The Uninstall IBM Tivoli Integration Composer progress window 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 Complete window is displayed. 4. Click Done. The removal of Integration Composer is completed.
138 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 5. Optional: When the utility removes Integration Composer, one or more files sometimes remain in the installation directory. (For example, these files might be files that someone manually put into the directory, such as mapping files or schema files that the user imported, or they might be log files that Integration Composer created.) You can delete these files manually. Uninstalling Integration Composer on UNIX operating systems UNIX Use the procedure described here to remove Integration Composer from a UNIX-based operating system. Procedure 1. Go to the uninstall folder, itic_install_dir\Uninstall_Integration_Composer, where Integration Composer 7.5 was installed. 2. In the uninstall folder, do one of the following options: v If you installed the Integration Composer using the X Window System application, 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 using console mode. 3. Press Enter to initiate the command from the previous step. The Uninstalling progress bar is displayed as the uninstall utility removes the application. When the removal of Integration Composer is finished, you are returned to the command prompt. 4. Optional: After the utility removes Integration Composer, one or more files sometimes remain in the installation directory. (For example, these files might be files that someone manually put into the directory, such as mapping files or schema files that the user imported, or they might be log files that Integration Composer created.) You can delete these files manually.
Chapter 8. Installing Integration Composer 139 140 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 9. Installing the Deployer's Workbench
The Deployer's Workbench is a separately installed, Eclipse-based workbench that is the best-practice tool for creating authorized CI spaces. Install it on a Windows workstation 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 not need to install the Deployer's Workbench.
You can install the Deployer's Workbench using either the SmartCloud Control Desk launchpad or the native installer. In either case, the DVD1 image or physical DVD must be accessible from the workstation where you want to install the Deployer's Workbench. Procedure 1. Start the Deployer's Workbench installer. Either start the SmartCloud Control Desk launchpad, click Install the Product, and click Install Deployer's Workbench, or to use the native installer, cd to the DW directory and run install.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 the drop-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.
© Copyright IBM Corp. 2007, 2011 141 142 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 10. Installing IBM SmartCloud Control Desk Everyplace
Use the information in this section to install the optional component IBM SmartCloud Control Desk Everyplace.
IBM SmartCloud Control Desk Everyplace comes with its own launchpad, which you can use to install it on the same administrative workstation where you installed SmartCloud Control Desk. The installation process does not create a new EAR file; it updates the maximo.ear file, which you must then rebuild and redeploy. The installation process does not update the maximoiehs.ear file, so you do not need to rebuild and redeploy this file. The installation procedure depends on your scenario. Choose the link that matches your situation.
Installing as part of a new product installation Follow these steps if you are installing IBM SmartCloud Control Desk Everyplace as 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 the update of the database and the deployment of the ear file. You must complete these steps after running the SmartCloud Control Desk installer and before updating the database. Procedure 1. 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.exe Use this command for 32-bit Windows workstations. launchpad64.exe Use this command for 64-bit Windows workstations. launchpad.sh Use this command for workstations running other operating systems. 3. To install IBM SmartCloud Control Desk Everyplace, open the Install Product page and click the link to start the installer. 4. As you run the installer, be sure to choose Deploy application files manually later and Defer the update of the Maximo database. This causes the IBM SmartCloud Control Desk Everyplace code to be added to the SmartCloud Control Desk files whose installation will be completed in subsequent steps. 5. When the installation is complete, in the Package Successfully Deployed window, click Done. What to do next
After you have installed IBM SmartCloud Control Desk Everyplace, you must return to the product installer to complete the installation of all components, the
© Copyright IBM Corp. 2007, 2011 143 updating of the database, and the building and deployment of the EAR file.
Installing as part of a product upgrade If you are installing IBM SmartCloud Control Desk Everyplace as part of an upgrade to SmartCloud Control Desk, follow the steps in the Upgrade Guide. About this task
The Upgrade guide includes information on installing IBM SmartCloud Control Desk Everyplace as part of an upgrade. You can find the Upgrade Guide on the product wiki Upgrade page at https://www.ibm.com/developerworks/wikis/ display/tivoli/SmartCloud+Control+Desk+-+Installing %2C+Migrating+and+Upgrading.
Installing after SmartCloud Control Desk has been installed Follow these steps if you are installing IBM SmartCloud Control Desk Everyplace after you have completed the installation of SmartCloud Control Desk. About this task
You can install IBM SmartCloud Control Desk Everyplace as an addition to an existing installation of SmartCloud Control Desk.
The following procedure assumes that you want to minimize the time for which your J2EE server is down. Procedure 1. 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.exe Use this command for 32-bit Windows workstations. launchpad64.exe Use this command for 64-bit Windows workstations. launchpad.sh Use this command for workstations running other operating systems. 3. To install IBM SmartCloud Control Desk Everyplace, open the Install Product page and click the link to start the installer. 4. Select the installation path for SmartCloud Control Desk from the drop-down menu. 5. Do not choose Deploy application files manually later or Defer the update of the Maximo database. Instead, allow the installer to complete all steps. 6. When the installation is complete, in the Package Successfully Deployed window, click Done.
144 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 11. Post installation tasks
There are several post installation tasks required in order to complete the SmartCloud Control Desk deployment.
Accessing product documentation Accessing the SmartCloud Control Desk information center documentation and product online help.
If you chose to manually configure the application server before running the product installation program, you must manually set the value for the application server hosting the online product documentation. Refer to https://www.ibm.com/ support/docview.wss?uid=swg21508594 for more information.
Initial data configuration
After you have successfully installed and configured SmartCloud Control Desk components, there are several data configuration tasks you must complete before using SmartCloud Control Desk. Signing in using a default user ID User management can be managed through the Maximo application or though the directory server you have configured to use with SmartCloud Control Desk Before you begin
When first installed, SmartCloud Control Desk contains the following default user IDs:
Important: Before you begin this procedure, if you are using a directory server as part of your deployment, ensure that you have the following users created in your LDAP repository: Table 17. SmartCloud Control Desk users User maxadmin mxintadm maxreg
Note: User names and passwords are case-sensitive. The defaultuser names are lowercase. About this task
To sign in, complete the following steps: Procedure 1. Open a browser window.
© Copyright IBM Corp. 2007, 2011 145 2. Navigate to the SmartCloud Control Desk login URL. For example: http://host name: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 SMTP Installation panels provide an opportunity to configure an SMTP server to send an administrator, or other users, e-mail notifications of system events. If you skip these panels when you install SmartCloud Control Desk, you can use the SmartCloud 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. Procedure 1. Log in to the console as maxadmin. 2. Navigate to Go To > System Configuration > Platform Configuration > System Properties 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 148 When you create a general ledger account component, it must be applied to the Maximo database. Create currency codes You must define a currency code for an organization. About this task
To define a currency code for an organization, complete the following steps. Procedure 1. Open the Currency Code application for Users by selecting Goto > Financial > Currency Code 2. Click New Row.
146 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 3. Enter a currency name. For example, USD. 4. Click the Save icon. Create item and company sets You 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: Procedure 1. Open the Sets application for Users by selecting Goto > Administration > Sets. 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 organization You must define at least one organization for SmartCloud Control Desk. About this task
To define an organization, complete the following steps. Procedure 1. Open the Organizations application by selecting Goto > Administration > Organizations. 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 component You 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 147 Procedure 1. Open the Database Configuration application by selecting Goto > System Configuration > Platform Configuration > Database Configuration. 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 database When you create a general ledger account component, it must be applied to the Maximo database. About this task
To apply configuration changes to the Maximo database, complete the following steps. Procedure 1. Log in to the Maximo console as maxadmin 2. Select Go To > System Configuration > Platform Configuration > Database Configuration. Every object that must be updated in the Maximo database 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 to view progress. 5. After Admin Mode has been enabled, select Apply Configuration Changes,to apply the changes to the Maximo database. To Be Changed must not appear in the status column for objects listed. 6. Turn Admin Mode OFF. a. Select Go To > System Configuration > Platform Configuration > Database Configuration. 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 account You must create a general ledger account for SmartCloud Control Desk. About this task
To create a general ledger account, complete the following steps: Procedure 1. Open the Chart of Accounts application by selecting Goto > Financial > Chart of Accounts. 2. Click the name of your organization to select it. For example, click ENGLENA.
148 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 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 Organizations application by selecting Goto > Administration > Organizations\. 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 Authorization You must update the general ledger component type authorization for SmartCloud Control Desk. About this task
To authorize a Security Group to change a general ledge component type, complete the following steps: Procedure 1. Open the Security Groups application by selecting Go To > Security > Security Groups. 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 Accounts You must update the company-related accounts for SmartCloud Control Desk. About this task
To update the company-related accounts, complete the following steps: Procedure 1. Open the Chart of Accounts application by selecting Go To > Financials > Chart of Accounts. 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.
Chapter 11. Post installation tasks 149 8. Click OK. Create default insert site You 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 updated by another user, log out as maxadmin and then log back in. Procedure 1. Open the Users application by selecting Goto > Security > Users. 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 worktypes You must create worktypes for SmartCloud Control Desk. About this task
To create a worktype, complete the following steps. Procedure 1. Open the Organizations application by selecting Goto > Administration > Organizations. 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 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 Work Order class. 12. Set the Work Type as UR. 13. Set Start Status as INPRG. 14. Set Complete Status as COMP. 15. Click New Row. 16. Select CHANGE as the Work Order class. 17. Set the Work Type to a value that describes a type of change that is created. For example, you might set a Work Type as MAJOR to designate a major change. You can define as many Work Types for the CHANGE Work Order
150 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) class as you would like. For example, you might define the MINOR Work Type for a minor change, and a SIG Work Type for a significant change. 18. Set Start Status as INPRG. 19. Set Complete Status as COMP. 20. Click OK. 21. Click Save. 22. Restart the MXServer application server. Create a classification structure for IT assets Before you can implement IT asset management, you need to define a classification structure for IT assets. About this task
You can use the Classifications application to set up a nested, hierarchical structure in which to classify information about your company's assets. This structure lets you 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 all notebooks in your enterprise, you can search for all assets classified as notebooks and retrieve instances of notebooks.
Best practices content for creating classifications is provided in the Open Process Automation Library.
The steps for creating classifications follow. Procedure 1. On the navigation bar in SmartCloud Control Desk, click Go to > Administration > Classifications. 2. In the Classifications application, create classifications as needed. For instructions about creating classifications and other information related to classifications, see the integrated online help for the Classifications application in the SmartCloud Control Desk user interface. What to do next
After you create an IT asset classification structure, specify the top-level IT asset classification and the top-level software classification in the Organizations application. Specify a top-level class for IT assets and software To distinguish IT assets from other types of assets, specify a top-level class for IT assets. Any asset that belongs to the hierarchy of the top-level IT asset class is an IT 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 a classification structure for IT assets and software in the Classifications application.
Chapter 11. Post installation tasks 151 About this task
The class structure ID that is displayed in the System Settings window is a value stored in the database. If the classifications structure changes such that the top-level IT asset class no longer exists at the same place in the hierarchy, the IT Asset Class Structure ID field will remain populated, but the IT Asset Top-Level Class field will be blank or show the wrong class. Consequently, if changes are made to the database, and the classification is moved within the classification structure, or deleted and re-added, repeat this procedure to update the class structure ID. Procedure 1. Click Go to > Administration > Organizations. 2. From the Select Action menu in the Organizations application, select System Settings. 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.If necessary, you can select Clear Classification to clear the value displayed and then click 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. The application closes the Classify dialog box and populates the IT Asset Top-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. The application closes the Classify dialog box and populates the IT Software Top-Level Class field. 5. Click OK to save the settings and close the dialog box. Signing out and signing in When you change a security group that includes your user ID, you must sign out and sign in to see the changes. For example, even though you have granted a group permission to create start center templates, the actions are not visible until you sign in again. Procedure 1. Sign out as maxadmin. 2. Sign in as maxadmin.
Generating xml request pages Perform this task after you install SmartCloud Control Desk and before you run request pages. This procedure needs to be performed for every language that is enabled on your system. Before you begin
When multiple languages are enabled in Maximo applications, request pages have to be generated in each of the enabled languages.
152 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Procedure 1. 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 groups When you select application server security, the scheduled synchronization of users and groups that occurs between LDAP repositories and SmartCloud Control Desk is governed by the federated repositories. Before you begin
View the cron task configuration information in the Administering Maximo Asset Management section of the Maximo Asset Management information center. About this task
LDAP repositories are synchronized with Oracle WebLogic Server using the LDAP cron task.
To configure the synchronization schedule between LDAP repositories and SmartCloud Control Desk, complete the following steps: Procedure 1. 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, navigate to Go To > System Configuration > Platform Configuration > Cron Task Setup. 4. Search for the appropriate cron task in the Cron Task field and configure it as instructed in the Managing cron tasks section of the Maximo Asset Management information center. 5. Set the task to active. What to do next
By default, the cron task performs its task every 5 minutes. Change the Schedule field of the cron task if you want to change the interval.
Understanding and configuring security You must configure security to ensure that only authorized users can log on to SmartCloud Control Desk. You must also ensure that the appropriate users have access to their applications and configuration items.
The Security information contained in the SmartCloud Control Desk information center provides an overview of the following information: v How security is implemented. v The steps you perform to configure security.
Chapter 11. Post installation tasks 153 154 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 12. Middleware clean up scripts
Middleware clean up scripts are available to remove middleware components and objects installed and created by the middleware installation program.
Middleware clean up scripts are provided to clean up components that were installed on a system by the middleware installation program. These scripts can be used after experiencing a middleware installation program failure, as well as successful install. These scripts work with the middleware installation program uninstall feature and are capable of removing one or more middleware installation components. These components include middleware installed, the workspace, installation directories, and users created by the middleware installation program.
Using the middleware cleanup scripts Middleware clean up scripts can be used to remove all artifacts and components installed on a system by the middleware installation program. About this task
When using the middleware cleanup scripts, you are prompted to confirm that you want to remove the component specified. A timestamped log file is created in the working directory for each action. If the script detects that the installation of a component experienced an error, you might have to uninstall that product manually 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 up objects created by the middleware installation program. This option removes any middleware that was installed, the workspace, and the deployment engine.
This option does not remove users and groups created by the middleware installation program. -workspace This option reads the middleware installation program workspace. The deployment plan contained in the workspace serves as a roadmap for the clean up script. -all This option removes all components and objects from the system that were installed and created by the middleware installation program.
This option also removes middleware users and groups. This is true for users and groups created by the middleware installation program and also users and groups created manually that were used for configuration during use of the middleware installation program.
© Copyright IBM Corp. 2007, 2011 155 Table 18. Middleware clean up script parameters (continued) Parameter Description -mw This option refers to the middleware installation program workspace for objects to remove. You must provide extra confirmations to remove users, groups, and DB2 instances. -db2 This option removes DB2. All DB2 instances are dropped, the DB2 server is stopped, DB2 is uninstalled, and the DB2 installation directories are removed. -itds This option removes IBM Tivoli Directory Server. All IBM Tivoli Directory Server instances are dropped, the IBM Tivoli Directory Server server is stopped, IBM Tivoli Directory Server is uninstalled, and the IBM Tivoli Directory Server installation directories are removed. -was This option removes WebSphere Application Server. All WebSphere Application Server instances are dropped, the WebSphere Application Server server is stopped, WebSphere Application Server is uninstalled, and the WebSphere Application Server installation directories are removed.
This option also removes IBM HTTP Server and the WebSphere Application Server update installer. -deMWI This option removes the deployment engine. If there are entries in the deployment engine registry that were not deployed by the middleware installation program, you are warned and asked to confirm that you still want to remove the deployment engine.
Once the deployment engine has been removed, you are given the option to remove the workspace. -users This option removes users and groups created by the middleware installation program. It removes the default users created by the program and also prompts you to enter additional user and group names associated with the middleware installation that you want removed. -prop This option allows you to use the mwi.properties file to supply input to the clean up scripts. -f This option allows you to skip confirmation by confirming all prompts y or n.
Procedure 1. From the product installation image, change directory to the MWICleanupScripts\operating_system directory.
156 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 2. Start the clean up script and provide input parameters: Windows mwiclean.bat Linux and UNIX mwiClean.sh
For example: mwiclean.bat -db2 3. Type y or n when prompted for confirmation. 4. When prompted, reboot the system. Rebooting the system removes the temporary entries which can remain after the cleanup procedure has completed.
Chapter 12. 157 158 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 13. Uninstalling the product
Uninstalling SmartCloud Control Desk 7.5 is dependant upon how it was deployed.
The procedures and instructions provided here are based upon a scenario in which the SmartCloud Control Desk installation program has experienced an error or failure.
SmartCloud Control Desk uninstallation is a comprehensive procedure and does not support partial removal of individual components or process managers, including process managers deployed by other products. Process managers of previously deployed products are also removed when you uninstall SmartCloud Control Desk.
The SmartCloud Control Desk uninstallation program can only be run once. If there are errors, messages are generated that indicate conditions that you must resolve manually before attempting a reinstall. Resolution includes manually removing files from the administrative workstation.
SmartCloud Control Desk can only be uninstalled using the SmartCloud Control Desk uninstallation program as directed. Do not use other methods to attempt to uninstall SmartCloud Control Desk, such as using the Add/Remove Programs panel.
The uninstall procedure you follow depends on the type of SmartCloud Control Desk deployment you are uninstalling. For uninstallation purposes, SmartCloud Control Desk deployments falls into one of the following categories: Fully-automated configuration In this scenario, you selected the option to allow the SmartCloud Control Desk installation program to automatically configure middleware during deployment. Manual configuration In this scenario, you selected the option to manually configure middleware. You did not allow the SmartCloud Control Desk installation program to automatically configure middleware during deployment.
After the SmartCloud Control Desk uninstall process is complete, you can reinstall SmartCloud Control Desk by restarting the SmartCloud Control Desk installation program. “Uninstalling an automatically configured deployment” Uninstalling a SmartCloud Control Desk deployment that was deployed using the automatic middleware configuration options is an automated process. “Uninstalling a manually configured deployment” on page 161 Uninstalling a SmartCloud Control Desk deployment that was deployed with middleware that you configured manually includes additional manual tasks.
Uninstalling an automatically configured deployment Uninstalling a SmartCloud Control Desk deployment that was deployed using the automatic middleware configuration options is an automated process.
© Copyright IBM Corp. 2007, 2011 159 Deployments consisting of automatic middleware configuration can be uninstalled using automated methods. Running the product uninstall program for automatically configured middleware Running the SmartCloud Control Desk uninstall program reverts the administrative system and middleware servers back to their previous state. Before you begin
Ensure that all applicable services are running and all middleware servers are accessible.
The SmartCloud Control Desk uninstall program must be able to access the database used with SmartCloud Control Desk to fetch installation properties and configuration data. If the uninstall program cannot access an unavailable, corrupted, or otherwise inaccessible database, it removes files from the administrative workstation. It then informs you that some manual recovery might be required before another SmartCloud Control Desk installation can be successful.
The uninstall program uses values entered during the initial installation during uninstall. If credentials used to access the database and J2EE server are still valid, you are not prompted to enter them again. If the uninstall program is unable to validate these credentials you are prompted to supply the updated information. The uninstall program would not be able to validate credentials if you updated passwords since the original installation. Procedure 1. To run the SmartCloud Control Desk uninstall program, from the administrative workstation, open a command prompt and issue the following command: Windows install_home\_uninstall\uninstall.bat UNIX install_home\_uninstall\uninstall.sh 2. From the application server information panel, enter the following information and then click Next. Remote user ID Enter a user ID in order to access the system hosting the application server. The remote user ID must be able to access the server using the remote access protocol enabled on that system. Remote password Enter a password for the remote user ID. User ID Enter the password for the application server administrator. Password Enter the password for the application server administrator user ID. 3. From the database administration panel, for DB2, enter the following information and then click Next. Remote user ID Enter a user ID in order to access the system hosting the database. The
160 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) remote user ID must be able to access the server using the remote access protocol enabled on that system. Remote password Enter a password for the remote user ID. Instance administrator user ID Enter the database instance administrator user ID that you entered during the installation. Instance administrator password Enter the password for the database instance administrator user ID.
For Oracle databases, you can supply the credentials for the Administrator user ID and the Oracle software owner ID. For Microsoft SQL Server databases, you can supply the SQL Server administrator user ID and password. 4. Review the components that are listed in the uninstall summary panel, and then click Uninstall. 5. After the uninstall process has completed, specify whether you want to restart the 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 to the reinstallation process.
Uninstalling a manually configured deployment Uninstalling a SmartCloud Control Desk deployment that was deployed with middleware that you configured manually includes additional manual tasks.
Uninstalling a manually configured SmartCloud Control Desk deployment consists of two tasks: v Running the SmartCloud Control Desk uninstallation program v Manually dropping and recreating the database you intend to use with the reinstall process Running the product uninstall program for manually configured middleware Running the SmartCloud Control Desk uninstall program reverts the administrative system and middleware servers back to a state where you can rerun the SmartCloud Control Desk installation program. Before you begin
Ensure that all applicable services are running and all middleware servers are accessible.
The SmartCloud Control Desk uninstall program must be able to access the database used with SmartCloud Control Desk to fetch installation properties and configuration data. If the uninstall program cannot access an unavailable, corrupted, or otherwise inaccessible database, it removes files from the administrative workstation. It then informs you that some manual recovery might be required before another SmartCloud Control Desk installation can be successful.
The uninstall program uses values entered during the initial installation during uninstall. If credentials used to access the database and J2EE server are still valid,
Chapter 13. Uninstalling the product 161 you are not prompted to enter them again. If the uninstall program is unable to validate these credentials you are prompted to supply the updated information. The uninstall program would not be able to validate credentials if you updated passwords since the original installation. Procedure 1. To run the SmartCloud Control Desk uninstall program, from the administrative workstation, open a command prompt and issue the following command: Windows install_home\_uninstall\uninstall.bat UNIX install_home\_uninstall\uninstall.sh 2. From the Introduction panel, read the introductory information and then click Next. 3. From the application server information panel, enter the following information and then click Next. User ID Enter the password for the application server administrator. Password Enter the password for the application server administrator user ID. 4. Review the components that are listed in the uninstall summary panel, and then 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 to the reinstallation process. What to do next
You can now proceed with recovery of your manually configured database. Database configuration recovery Database objects created before running the SmartCloud Control Desk installation program must be deleted after a failed installation before the SmartCloud Control Desk installation program is run again.
Before rerunning the SmartCloud Control Desk installation program, you must drop the SmartCloud Control Desk database and recreate it.
Note: Alternatively, if you want to preserve the instance, you can examine the database for objects (tables, views, and procedures, for example) that were created by the maxadmin user. You can then drop those objects individually. Restoring the DB2 database server In order to rerun the SmartCloud Control Desk installation program, you must first restore the DB2 database server to the same state as before SmartCloud Control Desk was installed.
162 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) About this task
To restore the DB2 database server to its previous state, drop the SmartCloud Control Desk database that you manually created. You then recreate it before rerunning the SmartCloud Control Desk installation program.
To restore the SmartCloud Control Desk database, complete the following steps:
Procedure 1. Log on to the system hosting 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: Auth Id Application Appl. Application Id DB # of Name Handle Name 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 like the 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 70 This section contains instructions for manually configuring DB2 9.x servers for use by SmartCloud Control Desk. Restoring the Oracle database In order to rerun the SmartCloud Control Desk installation program, you must first restore the Oracle database server to the same state as before SmartCloud Control Desk 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 Oracle database server to its previous state. This task must be completed before rerunning the SmartCloud Control Desk installation program.
To restore the SmartCloud Control Desk database, complete the following steps:
Procedure 1. Log in to the Oracle database server as the Oracle software owner.
Chapter 13. Uninstalling the product 163 2. Log in to the Oracle instance using SQLPlus as a DBA user: The Oracle SID for a clean installation is ctginst1. If you are using an existing Oracle instance with SmartCloud Control Desk, use the Oracle SID associated with the existing instance. AIX, Linux, HP-UX, Solaris a. Set the environment variable from the command line: ORACLE_SID=
Do not disconnect from the database. If you receive an error that you cannot drop a currently connected user, issue the following commands and use the SQL drop command: shutdown immediate; startup; 4. Manually recreate the database. “Manually configuring Oracle 11g” on page 71 Use the following instructions to manually configure Oracle 11g for use with SmartCloud Control Desk. “Manually configuring Oracle 10g” on page 74 Oracle 10g can be manually configured for use with SmartCloud Control Desk. Restoring the Microsoft SQL Server database In order to rerun the SmartCloud Control Desk installation program, you must first restore the Microsoft SQL Server database server to the same state as before SmartCloud Control Desk was installed.
Before you begin
Stop the MXServer application server before deleting the database.
About this task
To restore the Microsoft SQL Server database server to its previous state, drop the SmartCloud Control Desk database that you manually created. You then recreate it before rerunning the SmartCloud Control Desk installation program.
To restore the SmartCloud Control Desk database, complete the following steps:
164 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Procedure 1. 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. Right-click the database name you created during installation (MAXDB75 for example). Click Delete to delete the database. 4. In the Delete Object window, select Delete backup and restore history information for databases and Close existing connections, and then click OK. 5. Manually recreate the maxdb75 database. “Manually configuring Microsoft SQL Server” on page 76 You can manually configure Microsoft SQL Server for use with SmartCloud Control Desk.
Uninstalling the product without the uninstallation program Uninstalling the product when a failed installation does not produce an uninstallation program.
If the installation program has experienced a failure that causes it to not produce the product uninstallation program, you must perform alternative uninstallation tasks.
If uninstallation program was not produced, you must complete one of the following 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” on page 162. 2. Manually remove files from the system as described in “Removing files from the system” on page 167. Uninstall program recovery tool The uninstall program recovery tool is used to automatically uninstall SmartCloud Control Desk when the installation program fails to produce the product uninstallation program.
The uninstall program recovery tool is run on the administrative workstation following a failed installation. This tool performs the same functions of the SmartCloud Control Desk uninstallation program. This tool is intended to restore the administrative workstation and middleware servers so the SmartCloud Control Desk installation can be run again. The uninstall program recovery tool is available on the product media and also from the product support site. Using the uninstallation program recovery tool Use the uninstallation program recovery tool to restore the administrative workstation and middleware servers so the SmartCloud Control Desk installation can be run again.
Chapter 13. Uninstalling the product 165 About this task
The uninstallation program recovery tool is a command line tool that prompts you for input. This information is used as input for a collection of scripts that are run serially. These scripts perform the steps necessary to restore the administrative workstation and middleware servers so the installation program can be rerun. If you choose to skip any of the uninstallation program recovery tool tasks, you can run the tool at a later time to perform that task.
The uninstallation program recovery tool must be run on each system that hosts a component of the SmartCloud Control Desk deployment. For example, to remove the database associated with the deployment, you must run the program on the server hosting the database.
Procedure 1. 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 server used 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
166 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 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
Manual uninstallation steps are performed following a failed installation. These steps are used to remove the same objects as the SmartCloud Control Desk uninstallation program. These steps are intended to restore the administrative workstation and middleware servers so the SmartCloud Control Desk installation can be run again. Removing files from the system If an uninstallation program is unavailable due to failed installation, product files must be manually removed from the system.
About this task
Remove files from the system by completing the following steps:
Procedure 1. Ensure that you are logged in to the system with the same user ID used to start the product installation program.
Chapter 13. Uninstalling the product 167 2. Manually delete the SmartCloud Control Desk home directory. For Windows, the default location of this directory is C:\IBM\SMP. For UNIX systems, this directory is /opt/IBM/SMP.
168 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 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 Windows This procedure describes how to restart middleware on Windows, if you must restart any middleware services. About this task
To properly start middleware products on Windows, use the following scripts in the order in which they are listed: Procedure 1. 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 start CTGINST1. 3. If you installed IBM Tivoli Directory Server, start the IBM Tivoli Directory Server 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 to start the IBM Tivoli Directory Server admin daemon: idsdiradm -I idsccmdb 4. If you installed IBM Tivoli Directory Server, start the IBM Tivoli Directory Server 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 Tivoli Directory Server instance: idsslapd -I idsccmdb
Important: The IBM Tivoli Directory Server Instance must remain as a manual startup type. It must be started manually to synchronize correctly with the database in the context of SmartCloud Control Desk.
© Copyright IBM Corp. 2007, 2011 169 Restarting middleware on UNIX Middleware services on Linux and AIX platforms occasionally must be restarted, such as when a reboot occurs. Middleware servers and services must be active before running the SmartCloud Control Desk installation program. About this task
To properly start middleware products on UNIX, perform the following steps: Procedure 1. 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 instance su - ctginst1 -c db2start If you installed IBM Tivoli Directory Server, start IBM Tivoli Directory Server Admin Daemon
Important: The instance of IBM Tivoli Directory Server must remain as a manual startup type. It must be started manually to synchronize correctly with the database in the context of SmartCloud Control Desk.
170 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 15. Process solution package installation methods
Included within SmartCloud Control Desk are common installation programs that provide you with the ability to manage the software life cycle of SmartCloud Control Desk process solutions, including functions to query, install, upgrade, and uninstall process solution packages. These common installation programs are collectively known as the process solution installation programs.
SmartCloud Control Desk provides a flexible approach for incremental deployment of service management functionality using separately packaged process solutions. Process solutions can be partitioned into Process Manager Products and Integration Modules.
Process solution packages can be installed and deployed using two mechanisms: Process Solution Installation Wizard The process solution installation wizard provides you with an interface for installing process solution packages. Process Solution Command Line Interface The process solution command-line interface allows you to install process solution packages from a command line.
SmartCloud Control Desk must have been deployed, including post-installation steps, before the installation and deployment of additional process managers.
Software life cycle operations Process solutions are software components with versions. The process solution installation programs support various software life cycle operations that can be applied 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 process solution and changes its version. Often a process solution fix pack is applied using the Incremental Update operation. v Another operation that can be used to update an installed process solution is the Apply Fix operation. This operation is used to install individual interim fixes or patches to a currently installed process solution. v Some Incremental Updates or Fixes are designed to be able to be removed or backed off. The Undo operation is used to remove the effects of an Incremental Update operation and return the process solution to its previous version and state. The Undo Fix operation removes a currently installed interim fix from a process solution. v The Uninstall operation removes a currently installed process solution.
© Copyright IBM Corp. 2007, 2011 171 Process solution packages A process solution package is a self-contained archive file of installation artifacts and deployment logic that can be deployed using the process solution installation programs.
Installation artifacts are the files and content that are installed into your SmartCloud Control Desk environment. These artifacts enable the services management functionality of the Process Manager Product or Integration Module. For example, a Process Manager Product provides J2EE application content and database content.
The deployment logic consists of the actions that are carried out in order to deploy the process solution into the SmartCloud Control Desk environment. These actions include building J2EE applications, running database scripts that load the process solution 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 SmartCloud Control Desk is installed.
Package types Closely related to the concept of the software life cycle operation is software package type.
The process solution installation programs are able to process the following package 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 is currently installed or it can be used to perform an Upgrade operation on a currently installed process solution. v An Aggregation package consist of multiple PSI installable packages that can be deployed as one package in a single process solution installation client CLI or interface session.
The process solution installation programs ensure that the appropriate package type is processed for any given operation.
The Process Solution Command Line Interface issues appropriate messages when an inappropriate package type is specified for a life cycle operation. For example, a message would be issued if a Fix Package was specified for a Base Install operation. You can use the showavail action of the Process Solution Command Line Interface to determine the package type associated with a process solution installable package.
The Process Solution Installation Wizard determines the operation to employ based on the type of the package and the current state of the installed components. For example, if you select to deploy a Full Update Package, the Process Solution Installation Wizard performs an Upgrade operation if a suitable base version of the
172 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) process solution is already installed and a Base Install operation if no suitable base version is detected. When using the Process Solution Installation Wizard, you can view the package type for the package you selected on the Package Validation Results panel.
The following table highlights the supported operations with their required package types: Table 19. 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 Update Package Apply Interim Fix Fix Package
Aggregation packages This 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 be deployed using a single session with the process solution installation programs. Such a package is known as a process solution aggregate package. The sub packages that are bundled within a process solution aggregate package are known as child packages.
Process solution aggregate packages are deployed using the same mechanisms used to deploy non-aggregate packages. All actions defined within the process solution command-line interface can be applied to a process solution aggregate package. Similarly, the process solution installation wizard can be used to base install, 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 as non-aggregate packages.
Process solution aggregate packages often expose their child packages as selectable features of the aggregate. You can selectively deploy only the pieces of the aggregate that you prefer.
A process solution aggregate has a version, unique identifier, and display name information just like a non-aggregate package. When you use the showinstalled action of the process solution command-line interface, the output includes information about the installed parent aggregate package. Out also contains information about the child packages within that parent aggregate package that have also been installed.
Determining which process solution installation program to use The process solution installation programs provided each have unique benefits and both must be used in the appropriate scenario.
Consider the following facts when deciding which process solution installation program to use.
Chapter 15. Process solution package installation methods 173 v The Process Solution Installation wizard provides a user experience typical of most software installation programs. You select the process solution package to install and provide additional installation options from wizard panels. The Process Solution Installation wizard is an attended installation. v The Process Solution Command Line Interface provides a simple command-line syntax for specifying the life cycle operation to perform and the package against which the operation is performed. You enter the Process Solution Command Line Interface command and messages and command output are displayed to the command line as the command is processed. v All functions and operations are available in the Process Solution Command Line Interface program. Only a subset of those functions is supported in the Process Solution Installation Wizard. Generally, use the Process Solution Installation wizard if it supports the operation you must perform. v The Process Solution Installation Command Line Interface is useful where you require an unattended or silent installation. The Process Solution Installation Command Line Interface passes return codes detailing the success of the command back to the operating system. The Process Solution Installation Command Line Interface is suitable for use in a higher-level deployment automation package or script.
Supported operations for the process solution installation programs There are multiple operations and functions that are supported by the Process Solution Installation wizard and Process Solution Command Line Interface.
The following table highlights the operations and functions that are supported by the Process Solution Installation wizard and Process Solution Command Line Interface. Table 20. Process solution operations Supported by Command Supported by Installation Operation Line Interface wizard 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 Incremental Yes No Update/Fix Pack Uninstall Yes No Apply interim fix Yes Yes Undo interim fix Yes No List Installed Fixes for a Yes No Package Refresh language support Yes No Load Language Support Files Yes Yes Add Features Yes Yes Remove Features Yes Yes Show Available Features Yes Yes
174 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Note: The process solution installation programs allow an uninstall action to be initiated against a package. However, not all packages support the uninstall action. If an uninstall action is initiated against a package that does not support this action, a message detailing this condition is shown. If you want to restore your environment to the state before the installation of the SmartCloud Control Desk process managers, you must back up your affected middleware servers before running the SmartCloud Control Desk installation program.
Before using the process solution installation programs Review the following prerequisite information before using process solution installation programs.
When you perform a deployment operation using the process solution installation programs, you are running actions that modify the configuration and content of your J2EE, database, and directory middleware servers. Review the following steps before starting the process solution installation programs. Have Middleware Login Information Available The process solution installation programs require access to middleware servers in order to automate the deployment of the process solution package. You must know the administrative user IDs and passwords for the affected middleware servers. The actual middleware servers whose login information is required depends on the process solution package being installed. The process solution installation programs ensure that any required login information is specified before continuing with the deployment operation. Backup Middleware Servers and Administrative Workstation You should create backups for affected J2EE, database, and directory servers before you deploy a process solution package using the process solution installation programs. Backup the installation folder of the administrative workstation, C:\IBM\SMP, for example. Also, backup the deployment engine registry. Ensure Middleware Servers Are Started Start any affected middleware servers before running the process solution installation programs. Before the actions associated with a package are started, the process solution installation programs attempts to connect to the middleware servers using the middleware login information that you specify. If the targeted middleware servers are not started or if connections to the middleware servers cannot be established with the specified middleware login information, then the process solution installation programs displays error messages and not continue on with the deployment actions. “Backing up the Deployment Engine database” on page 14 These 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 administrative workstation Process solution deployment is managed from the administrative workstation.
Chapter 15. Process solution package installation methods 175 Process solution installation programs are installed on the administrative workstation when the SmartCloud Control Desk is installed. In addition to starting process solution installation programs from the administrative workstation, you must also have access to any process solution packages from the administrative workstation.
The administrative workstation provides a deployment hub from which the process solution packages are deployed. In order to automate deployment, the process solution installation programs connects to either local or remote middleware servers from the administrative workstation
Typical deployment operation Process solution deployment is integrated tightly with SmartCloud Control Desk deployment
Process solutions use the SmartCloud Control Desk deployment model. In this model, as process solution packages are deployed, database content and metadata in the package is loaded into the Maximo database and the Maximo core J2EE applications are redeployed with Java code provided in the process solution package. This model effectively merges the features of the process solution package into 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 administrative workstation. The Maximo installation directory contains the Maximo content for the process solution being deployed and any other currently installed SmartCloud Control Desk process solutions or Maximo applications and industry solutions. 2. J2EE applications are rebuilt on the SmartCloud Control Desk administrative workstation to contain the features of the process solution package. This feature includes Java classes, report definitions, and other artifacts. 3. Database content scripts associated with the package being installed are processed on the SmartCloud Control Desk administrative workstation. This results in updates to the database.
Selectable features This section contains information about managing selectable content using features.
A process solution package might define one or more features that represent user-selectable, optional content. Examples of typical features include globalization and 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 also package-specific. The process solution installation methods examine the process solution install package and ensure that only features defined within the package are able to be manipulated. Attributes of a Feature
Associated with every feature are the following attributes:
176 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) v Feature Identifier represents a non-localized name by which the feature is uniquely identified within its package. When using the process solution command-line interface, the Feature Identifier is used to specify the feature to add 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 can not be installed if its parent feature is not installed. A top-level feature that is required is always installed. Operations Associated with Features
Both the process solution command-line interface and process solution installation wizard provide features for managing features associated with a process install package. This section describes those capabilities. Installing Features during a Base Install If a process solution package defines features, you can select the features to installation during the base installation of the package. Installing Features Using the wizard For the process solution installation wizard, a Feature Selection Panel is displayed after license acceptance processing if the package being deployed supports features. The Feature Selection Panel displays a tree where the nodes in the tree are features and the tree nesting represents parent feature and child feature relationships. Each node has a check box that indicates the selection state of the feature. You select a feature to be installed by selecting the check box for the feature. Installing Features Using the Command Line Interface For the process solution command-line interface, the -addfeatlist parameter on the install action allows you to specify the features to be installed during the base installation of the package. The value specified for this parameter is a colon separated list of Feature Identifiers representing the features to install. Adding Features After the base installation of a package, you can incrementally add features if there exists at least one feature not already installed for that package. Adding Features Using the wizard When using the process solution installation wizard, if the package is already installed but has at least one feature not already installed, you can elect to install additional features after the Package Validation Panel is displayed. Note that the Deployment Engine does not support both incremental feature add and removal in the same deployment operation. If the state of the installed features on a package is such that features can be both added or removed, then the Add or Remove Features Panel is displayed that allows you to select whether you want to add or remove features from the package.
Chapter 15. Process solution package installation methods 177 If you select to install additional features from the Add or Remove Features Panel, the Feature Selection Panel is again displayed with the currently installed features checked and disabled. You cannot uninstall currently installed features in this mode, but you can select additional features for installation. Adding Features Using the Command Line Interface For the process solution command-line interface, a new modfeatures action allows you to install features to an already installed process solution package. The parameters on this action are like the install action. You specify the path of the process solution package and required middleware user IDs and passwords. The -addfeatlist parameter on the modfeatures action allows you to specify the features to be added. The value specified for this parameter is a colon separated list of Feature Identifiers representing the features to be installed. Removing Features After the base installation of a package, you can incrementally remove or uninstall features if there exists at least one feature already installed for that package. Feature Uninstall is Optional Support for uninstall of features is optional. A process solution package that supports incremental feature installation might not support uninstall of its features. If the process solution package does not support uninstall of its features, then the process solution installation programs do not permit you to uninstall features on the package. The process solution installation wizard does not allow you to initiate feature uninstall operations against the package. The process solution command-line interface will issue messages if uninstall operations are attempted against a package that does not support feature uninstall. Removing Features Using the wizard When using the process solution installation wizard, if the package is already installed and has at least one feature already installed, you can elect to uninstall features after the Package Validation Panel is displayed. As described above, if the state of the installed features on a package is such that features can be both added or removed, then the Add or Remove Features Panel is displayed that allows you to select whether you want to add or remove features from the package. If you select to uninstall currently installed features from the Add or Remove Features Panel, the Feature Selection Panel is again displayed with the currently installed features checked. You may not install new features in this mode, but you can clear currently installed features to trigger the uninstall operation against those features. Removing Features Using the Command Line Interface For the process solution command-line interface, the modfeatures action described above also allows you to uninstall features that are already installed on a currently installed process solution package. The -delfeatlist parameter on the modfeatures action allows you to specify the features to be uninstalled. The value
178 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) specified for this parameter is a colon separated list of Feature Identifiers representing the features to be uninstalled. Showing Feature Information for a Package The process solution installation programs allow you to display information about the supported and installed features for a process solution package. Showing Feature Information Using the Wizard The Feature Selection Panel of the process solution installation wizard displays the feature tree of a process solution package. This panel depicts the parent-child relationships between the features and also displays whether the features are currently installed. Showing Feature Information Using the Command Line Interface For the process solution command-line interface, the showfeatures action allows you to display information about the features associated with a process solution package. Input to the action is the path to the process solution package. The output lists the feature attributes for the features defined for the package. Those attributes are detailed in “Attributes of a Feature” on page 176. Feature Selection Processing Rules and Behavior
When using the process solution installation programs to manage the features, the actual collection of features to install or uninstall are derived using a combination of the input selections/deselections you specify and a set of feature selections rules. For example, you can select a single feature for installation, but, due to feature selection rule processing, additional features can also be installed.
When you install or uninstall features, the process solution installation programs enforce these feature selection rules to ensure that the derived set of feature selections are valid and meet all the feature selection rules.
This section highlights the feature selection rules that are enforced by the process solution installation programs. Summary of Feature Selection Rules 1. Features can be arranged in a parent-child tree structure. Child features cannot be installed unless their parent feature is installed. 2. A feature can be marked as required which indicates that the feature must be installed if its parent is installed. A top-level feature that is marked required is always installed. 3. Features that are marked required can never be selected/deselected explicitly by you. The selection state of a required feature is always derived from the selection state of their parent feature. 4. A feature can have real content (files/actions) or can be a nesting feature which acts as a parent feature for other child features. 5. A Nesting Feature cannot be installed unless at least one of its child features (with content) is also installed. This violation is detected during Feature Selection Validation. Message CTGIN0200E is issued when this rule is violated. 6. Special select-if-selected rules can be coded into the package to assert prerequisite dependencies between features. These rules are specific to
Chapter 15. Process solution package installation methods 179 a particular package. For example, select-if-selected rules can be defined in a package that ensures that Feature A is installed if Features B or C are 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 are automatically selected. 3. When a feature is selected, select-if-selected rules are evaluated and any dependent features are automatically selected. 4. The rules are applied against all features in the tree until there are no more features to select. Feature Deselection Processing 1. When a parent feature is cleared, all its descendant features (Child features, Grandchild features, and so on) are cleared as well. 2. When a feature is cleared, all select-if-selected rules targeting that feature are evaluated and any dependent features are cleared. 3. These rules are applied against all features in the tree until there are no more features to clear. Feature Selection Validation The process solution installation programs enforce feature selection rules by performing a feature selection validation process. This is the process of deriving the complete set of features that are to be processed and determining if the user input violates any rules. If any feature rule violations are detected, then the operation to install or uninstall features is not carried out by the process solution installation programs. Feature Validation Using the Wizard When you use the process solution installation wizard, most rules are dynamically enforced as selections/deselections are made against the feature tree on the Feature Selection Panel. For example, when you select a child feature, all of its ancestor features are automatically selected. Additional rules are validated when you have finished making your selections and attempt to move to the next panel. If any violations of the rules are detected, messages describing the violations are displayed on the Feature Selection Panel and you must correct your input before proceeding. Feature Validation Using the Command Line Interface For the process solution command-line interface, the same feature selection rules are enforced and the complete set of features to install or uninstall is derived using those rules. For example, if you specify only a child feature in your -addfeatlist parameter, the PSI CLI adds all ancestor features to the list that are actually installed. Similarly, if you specify a parent Feature on the -delfeatlist parameter, then any installed child features under that parent feature is also uninstalled. Additionally, the process solution command-line interface also performs additional checks against the features you specify. These checks include:
180 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 1. Ensuring that any feature identifier specified is a valid identifier for the package. 2. Ensuring that features specified using the -addfeatlist parameter are not already installed for the package. 3. Ensuring that features specified using the -delfeatlist parameter are already installed for the package.
Pre-deployment system check Before the actions associated with a software life cycle operation are initiated, the process solution installation programs perform a system check activity. Associated with each process solution package are a set of requirements that must be satisfied before the deployment operation is carried out. The system check is a process that analyzes the requirements to determine that all requirements have been satisfied before 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 package and dependency checks between a process solution package and other process solution packages. When unsatisfied requirements are detected during the system check, the process solution installation programs display messages that describe the failed requirements. Before trying the deployment operation again, you must update your environment such that all requirements associated with the process solution package are satisfied. Bypassing Unsatisfied Requirements Under certain circumstances, you may find it necessary to bypass the system check processing and carry out a deployment operation even if one or more requirements associated with the process solution package are not satisfied. For example, a process solution package might have embedded an incorrectly specified disk space check which would prohibit the package from being installed on a system that has adequate free disk space required by the package. Both process solution installation programs provide mechanisms that allow you to bypass failed requirements and continue with the deployment operation. Using the Installation wizard When using the Process Solution Installation wizard, a System Check Failed panel displays messages for any failed requirements. From this panel, you can bypass the system check failures by selecting the check box entitled Ignore System Check Failures. When you select this check box, the Process Solution Installation wizard continues with the deployment of the process solution package. Using the Command Line Interface When using the Process Solution Command Line Interface, you can bypass unsatisfied system check requirements by specifying the -force command-line flag. Package requirements represent criteria put in place to ensure a successful deployment. While you must not bypass any requirements normally, the process solution installation programs permit the following types of requirements to be bypassed: v Capacity and consumption checks, for example, disk space and memory requirements for a package.
Chapter 15. Process solution package installation methods 181 v Prerequisite, corequisite, and exrequisite relationships defined for a root package. For example, Package B might require that Package A is installed before Package B can be installed. You can force processing of the installation operation for Package B even if Package A is not currently installed. v Property checks defined for the package, for example, a check of the type of operating system on which the installation is being performed. v Any custom checks defined for the package.
Note: Prerequisite, corequisite, and exrequisite dependencies defined between fix packages cannot be overridden. System check progress messages During the processing of the system check, the IBM Autonomic Computing Deployment Engine publishes events detailing the progress of the system check. The process solution installation programs receive the events and convert them into localized messages with identifier CTGIN0146I which are displayed to the user. The messages include the label for the check being performed, the number of completed checks, and the total number of checks that are to be performed. The IBM Autonomic Computing Deployment Engine is not able to compute the total number of checks to be carried out before any checks are processed. The counter associated with the total number of checks to be performed can increase during system check processing. For example, the following set of messages might be issued during the system check processing. The counter associated with the total number of checks is not fixed, 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 installation wizard 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 SmartCloud Control Desk using the process solution installation wizard: Procedure 1. Start the process solution installation program by navigating to the
182 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Alternatively, if you elected to create program shortcuts during the SmartCloud Control Desk installation, a link to the Process Solution installation 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 package selected can be a base install, incremental update, full update, or fix package Once a package has been selected and you click Next, the process solution installation program performs a series of validation checks to verify that the package you selected is valid. The system is checked to ensure that the package has not already been deployed, or, if the package is intended as an upgrade, the system is checked to ensure that the base package has already been installed. 5. From the Package Validation Results panel, review and verify the information displayed, and then click Next. 6. If this is the first time you have installed this process manager, the process solution installation program license agreement window is displayed. Read the license information and select I accept the terms in the license agreement if you agree with the terms. Click Next. If you are incrementally adding or removing features from a previously installed process manager, you encounter an Add or Remove Features? panel where you declare whether you are adding or removing features from the process manager, followed by another panel 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 has selectable features, you are prompted by the Feature Selection panel to select or clear features you would like to install or uninstall from the previously deployed package. 8. From the Middleware Login Information panel, enter the credentials for which you are being prompted, and then click Next. The contents of this panel are constructed dynamically, depending on the type of package you are installing. The package is queried to determine what middleware login credentials are necessary to complete the installation of the package. Once you have entered the requested user IDs and passwords, the process solution installation wizard validates the credentials by connecting to the middleware servers using the supplied credentials. 9. After the credentials have been verified, a package options panel is displayed that details the deployment options that the package supports. If the PSI installable package supports the Overwrite Customer Modified Data during Update option, you can select it from this page. After you specify which options are used, the process solution installation program will perform a system check. to ensure that all system requirements necessary for the package to be installed are present. Click Next to advance. 10. From the Pre-Install Summary panel, review and verify the information displayed, and then click Next. The process solution installation program begins the package installation process. A progress panel informs you of the deployment progress of the installation. 11. When the installation has completed successfully, from the Package Successfully Deployed panel, click Next. If there is a package failure, a message appears for the step that failed. If this was a Feature Add, or Removal, a message displays indicating the feature was added or removed successfully.
Chapter 15. Process solution package installation methods 183 12. From the Install Another Package panel, select Install Another Package? and click Done, to install another package. Otherwise, ensure that Install Another Package? is cleared and click Done to exit the process solution installation wizard. Results
You might see an installation progress bar displayed briefly after you click Done. The Process Solution Installation wizard is actually terminating and no installation activities are being performed. The deployment of the Process Solution Package you were installing has already completed and the progress bar can be safely ignored.
Process solution installation client command-line interface Use 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 CLI A launch script is provided for starting the Process Solution Command Line Interface. The script is named solutionInstaller.bat and is deployed and configured in the
During processing of the command, the Process Solution Command Line Interface writes messages to the standard output of the command window from which the command was launched. General syntax General 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 parameter value. v -parameterName is used for parameters that represent switches or flags which do not 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
184 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Perform action The solution installation program uses an action parameter when interfacing with packages.
A special parameter, -action, must be specified on each invocation of solutionInstaller. This parameter specifies the action or software life cycle operation to be performed. Based on the value specified for this parameter, additional parameters can be specified. For example, when -action showinstall is specified, the type parameter must also be provided. The following table identifies the supported actions that can be specified for the Process Solution Command Line Interface. Table 21. 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 a refreshlangs Package Add or Remove Features modfeatures Show Available Features showfeatures
Summary of supported parameters This section contains a summary of parameters supported by the command-line interface.
The collection of supported parameters for the Process Solution Command Line Interface is described in the following table. Table 22. Process solution command-line interface supported parameters Parameter Name Description -action Specify the function or software life cycle operation to perform. -addfeatlist Specifies the list of features to be installed. A feature is identified by its untranslated English Feature Identifier. Multiple features in the list are separated by a colon character. If any of the Feature Identifiers includes a space, then the entire value for this parameter must be enclosed in double quotation marks. -dbpwd Specifies the password of the database user ID that is used to access the Maximo database.
Chapter 15. Process solution package installation methods 185 Table 22. Process solution command-line interface supported parameters (continued) Parameter Name Description -dbuser Specifies the database user ID that is used to access the Maximo database. -delfeatlist Specifies the list of features to be deleted. A feature is identified by its untranslated English Feature Identifier. Multiple features in the list are separated by a colon character. If any of the Feature Identifiers includes a space, then the entire value for this parameter must be enclosed in double quotation marks. -fixid Specifies the unique identifier of an interim fix/patch that you want processed. -force Specifies whether to continue on with a deployment operation even if there are one or more unsatisfied requirements associated with the package being processed. -license Automatically accept the license agreement or be prompted for the acceptance or rejection of the license agreement by using one of the following values: accept or prompt. -loadlanguages Specifies whether options Language Support files for the package must be loaded into the Maximo Database -loadsampdata Specifies whether to load sample or demonstration data associated with the package being processed. -maxpwd Specifies the password of the SmartCloud Control Desk administrative user that is used to access the SmartCloud Control Desk application. -maxuser Specifies the SmartCloud Control Desk administrative user ID that is used to access the Maximo console. -pkgpath Specifies the file path of a process solution package. Paths that have embedded spaces must be enclosed in double quotation marks. -pkguuid Specifies the unique identifier of the process solution package that you want processed. -pkgver Specifies the version of the process solution package that you want processed. -skipdbcfg Specifies whether to defer the update of the Maximo database during package deployment. -skipj2eecfg Specifies whether to defer the regeneration and redeployment of the Maximo J2EE Applications during package deployment.
186 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 22. Process solution command-line interface supported parameters (continued) Parameter Name Description -type Specify one of the following types of solution element package to be returned when the showavail or showinstalled actions are used. Valid values are processmodule, integrationmodule, or all.
Process solution command-line interface reference See the following sections for process solution command-line interface reference information.
Several of the command-line interface actions reference a syntax element named [
The syntax for the middleware login element is: [-wasuser
The actual user IDs and passwords that are required depend on the package being processed. For example, a package that only deploys content to the Maximo database would only require the -dbuser and -dbpwd parameters. Table 22 on page 185 install action - install\ a package Description of the action used to install packages.
install Action install Purpose Perform an installation of a process solution package not already installed. Syntax solutionInstaller -action install -pkgpath
Chapter 15. Process solution package installation methods 187 v All additional requirements associated with the package specified are satisfied. Sample Usage modfeatures action - modify existing features of a deployed package Description of the action used to modify existing features of a deployed package.
modfeatures Action modfeatures Purpose Modify features of a currently installed process solution package. Syntax solutionInstaller -action modfeatures -pkgpath
188 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Process solution installation logs If you experience any problems or encounter any error messages during the use of the process solution installation program, see these log files.
Log files are kept in the following locations: Table 23. Process solution installation logs Log type Description Location Package log These are log files containing
In general, logs have two parts, a ".out" and ".err" file, both with the same pre-extension file name. .out files contain the contents of the Standard Output stream as output by the external command. .err files contain the contents of the Standard Error stream. It is normal for one to be blank, provided there was no error output (or there was ONLY error output).
Note that you might discover numerous (10-20) package log files generated for any particular package installed.
Chapter 15. Process solution package installation methods 189 Table 23. Process solution installation logs (continued) Log type Description Location SmartCloud Control Desk These are logs kept by the
XX is a two-digit number such as 00. These logs contain the trace output of the PSI subsystem.
Note: You might encounter messages like the following in the MAXIMO_DEPLOY_ERR.err file found in the
190 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 23. Process solution installation logs (continued) Log type Description Location WebSphere Application These are logs kept of
So for instance, if your WebSphere Application Server was installed in "C:\IBM\WebSphere\ AppServer\", your profile name was "AppSrv01", and your server name was "server1", you would provide the following logs:C:\IBM\WebSphere\ AppServer\profiles\ AppSrv01\logs\ AboutThisProfile.txt Maximo Logs There are also a few logs
Chapter 15. Process solution package installation methods 191 Table 23. Process solution installation logs (continued) Log type Description Location WebSphere Thin Client Logs The WebSphere thin client is
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. It is useful to have a log composed of only the information related to the success or failure of current package installation to facilitate problem determination.
192 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 16. Advanced installation topics
This section contains information useful for advanced SmartCloud Control Desk deployment scenarios.
Refer to this information for installation and configuration information in advanced deployments.
Configuring and managing Oracle WebLogic Server This section describes common tasks on configuring and administering the Oracle WebLogic Server.
For more comprehensive information on running and administering Oracle WebLogic Server visit the Oracle Web site. Starting Oracle WebLogic Server Starting the Oracle WebLogic Server. About this task
To start the MAXIMOSERVER application, complete the following steps: Procedure 1. 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 the phrase: server started in RUNNING Mode or Started weblogic Admin Server MAXIMOSERVER for domain mydomain running in production mode (depending on your operating system), the Oracle WebLogic Server is running. Stopping the Oracle WebLogic Server You can use the Administrative Console to stop the Oracle WebLogic Server. About this task
To stop the MAXIMOSERVER from the Administrative Console, complete the following steps:
© Copyright IBM Corp. 2007, 2011 193 Procedure 1. Open a browser window and enter the URL: http://localhost:7001/console This URL is the administration URL for Oracle WebLogic Server domain you created. 2. Log in to the Administration Console with the administrator user name and password. 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 configuration parameters You can change the configuration parameters you have entered for a deployment plan before deploying the plan. You would use this option if you chose to cancel the deployment of the deployment plan you developed by exiting the middleware installation program. Configuration parameters for a plan can be changed only before deploying the deployment plan. About this task
These instructions assume that you have developed a deployment plan, entered configuration parameters for the plan, and then exited the middleware installation program before actually deploying the deployment plan. Procedure 1. Relaunch the middleware installation program from the launchpad and advance along the installation program panels until you reach the Choose Workspace panel. 2. From the Choose Workspace panel, specify the directory you previously used as 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 the installation and configuration of the middleware you selected. 7. From the Select Middleware Image Directories panel, enter the location for compressed images for the middleware contained in the deployment plan, and a directory to use to hold the uncompressed images. After you have entered the two locations, click Next. During deployment, the middleware images are uncompressed onto the system. 8. Click Finish to exit.
Deploying EAR files This section contains information about deploying SmartCloud Control Desk EAR files manually into Oracle WebLogic Server.
194 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) The following instructions are used to manually deploy the SmartCloud Control Desk maximo.ear and maximoiehs.ear files into 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 then redeploy it in Oracle WebLogic Server. In this scenario, you would likely only rebuild and redeploy the maximo.ear file. You would not be required to rebuild and 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 or production environment. In this scenario, you must deploy both the maximo and maximo help applications into the new environment. Building EAR files You can manually build SmartCloud Control Desk EAR files if, for example, you modify a database connection parameter in the maximo.properties file after the initial installation. About this task
To manually build SmartCloud Control Desk EAR files, complete the following steps: Procedure 1. Build the maximo EAR file: Windows install_home\maximo\deployment\buildmaximoear.cmd Linux and UNIX install_home/maximo/deployment/buildmaximoear.sh 2. Build the maximo help system EAR file: Windows install_home\maximo\deployment\buildmxiehsear.cmd Linux and UNIX install_home/maximo/deployment/buildmxiehsear.sh Manually uninstalling applications from Oracle WebLogic Server This section contains information about uninstalling SmartCloud Control Desk applications from Oracle WebLogic Server. Manually uninstalling applications from Oracle WebLogic Server Procedure 1. Log into the Administration Console. For example, http://
Chapter 16. Advanced installation topics 195 196 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 17. Middleware on Solaris and HP-UX
Middleware versions that are not installable by the middleware installer program are installed by using graphical installation programs that are provided with each middleware product.
The procedures in this document can be used to manually install the following products on the following operating systems:
Solaris 11 SPARC and HP-UX 11i v2+3 64 bit v IBM DB2 Enterprise Server Edition 9.7 v IBM Tivoli Directory Server 6.3. IBM Tivoli Directory Server 6.3 is only supported for Solaris 11.
Operating system preparation Some operating system default configuration settings must be change to provide an environment that can host middleware operations.
The steps needed to prepare each newly supported operating system are operating system dependent.
Perform the operating system preparation steps before installing any middleware. Solaris Some of the default kernel configuration parameters on Solaris might not be sufficient to run IBM DB2 9.7.
Ensure that your Solaris system has required kernel parameters in place by running the db2osconf utility after you install IBM DB2, but before you create any database objects. Related information: http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp HP-UX In order for IBM DB2 9.7 to run correctly on HP-UX, certain group membership requirements must be addressed following the installation of IBM DB2.
After IBM DB2 9.7 has been installed, you must ensure that the root user has been assigned as a member of the db2iadm1 group.
In order to ensure that your HP-UX system has required kernel parameters in place, you will need to run the db2osconf utility after you install IBM DB2, but before you create any database objects.
© Copyright IBM Corp. 2007, 2011 197 Related information: http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp
Installing the components After the operating system is configured as needed, install the middleware components.
Middleware components are installed in the following order: 1. IBM DB2 2. IBM Tivoli Directory Server 3. IBM HTTP Server
Note: The media or web site you use to install middleware has directory-specific locations for each supported operating system. The directory structure is os/product.
These commands display the contents of the os/product directory. cd os ls
Within each os subdirectory are the installation directories for each middleware product. ls solaris DB2-ESE_9.7_FP3a TIV-DirectoryServer_6.3 Installing DB2 Run 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 prerequisite conditions: 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 hosting the database server. For Solaris and HP-UX systems, you must manually create the user even if the SmartCloud Control Desk installation program configures the database automatically. Ensure that you have created the maximo user on the database server before installing SmartCloud Control Desk. v db2setup starts a wizard installer so X Window System must be installed and running 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 must manually create the required DB2 users, before you start the DB2 setup program. See the centralized user-management considerations topic in the DB2 information center, before you begin.
198 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) v In general, you can choose to defer some installation activities. For example, if you choose to not set up email notifications of database events at installation time. If you want to defer specific installation activities, select that option, and configure them later. v Some middleware products have specific requirements or conventions for account names and other settings. Override the installation defaults as shown if the defaults provided are not satisfactory. On panels that prompt for passwords, both the password and its confirmation entry must be specified before the installer can continue to the next panel. About this task
This procedure describes how to perform a typical installation of DB2 on a single computer. If you want to install DB2 components on multiple computers, see the DB2 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 file contains the installation settings used, and errors that occurred during the installation process. The vmrfis.history file contains information about maintenance that has been applied to DB2, such as fix packs that have been installed.
The db2setup.log file captures all DB2 installation information including errors. The db2setup.err file captures any error output that is returned by Java (for example, exceptions and trap information). By default, both logs are created in the /tmp directory unless you change that location during the installation process. Procedure 1. Log in as root. 2. Copy the DB2 Enterprise Server Edition tar file to a writable disk. For Solaris Copy solaris/DB2-ESE_9.7_FP3a/v9.7fp3a_sun64_server.tar.gz For HP-UX Copy hpux-ia64/DB2-ESE_9.7_FP3a/v9.7fp3a_hpipf64_server.tar.gz 3. Change to the directory where you copied the compressed file and uncompress it. 4. Extract the file DB2_Enterp_Svr_OEM_Activation.zip into an appropriate directory. 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 of database events defaults to host name@local_server_name. This value must be changed to a valid email address if you choose to enable SMTP notifications. This value can also be changed at a later time.
Chapter 17. Middleware on Solaris and HP-UX 199 10. Leave the check boxes for the GUI and UID options selected; the system assigns them for you. 11. On the Start copying files and create response file panel, click Finish to initiate the installation. 12. Start the DB2 instance. 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 operating system. For Solaris, the license file is located in solaris/DB2-ESE_9.7/ DB2_Enterp_Svr_OEM_Activation/db2/license/db2ese_o.lic. c. Stop and then restart the DB2 instance using the db2stop and db2start commands. d. Verify that the license was installed successfully: DB2_HOME/adm/db2licm -l
This command results in output like the following: 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/index.jsp 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 Solaris IBM Tivoli Directory Server is typically installed on a computer that is not hosting other middleware products. Procedure 1. Log in 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.tar tar -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 system temporary directory. Change to the appropriate directory and type the following 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. For example: ./install_tds.bin -is:tempdir /opt/tmp
200 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) 5. When the installation wizard starts, select a language to use for the installation process, accept the license agreement, and choose a Custom installation. 6. Select the Proxy Server, Server, C Client, Java Client, and Web Administration 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. Refer to “Manually configuring IBM Tivoli Directory Server” on page 79 for details. 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 user password
Chapter 17. Middleware on Solaris and HP-UX 201 202 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Chapter 18. Backup and restoration
Like all important business data, it is a good idea to establish a process and schedule for backing up SmartCloud Control Desk data.
Back up and restore middleware application data using the methods described in the documentation for that product is important. Also establish a process for backing up data contained on the SmartCloud Control Desk administrative workstation.
The default installation directory on the SmartCloud Control Desk administrative workstation is C:\ibm. This directory contains the critical files for your SmartCloud Control Desk deployment, which includes all class files and customizations that have been performed in your environment, the current Enterprise Archive (EAR) file that was deployed in Oracle WebLogic Server, and the properties files and installation tools used for your environment. Plan to back up SmartCloud Control Desk administrative workstation data just after initial deployment and schedule periodic backups on an ongoing basis.
Backing up the administrative workstation It is recommended that you back up all SmartCloud Control Desk middleware applications and SmartCloud Control Desk administrative workstation on a regular basis. About this task
The default installation directory on the administrative workstation is C:\ibm. This directory 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 back up the administrative workstation. During restoration, you restore the database back up at the same time you restore the administrative workstation back up it was paired with.
To back up critical SmartCloud Control Desk information, complete the following steps: Procedure 1. Back up the SmartCloud Control Desk database, J2EE server, and authentication server information using the instructions provided by your middleware vendors. 2. Create a backup of the installation directory. By default, this directory is C:\IBM\SMP. Ensure that all file permissions are preserved.
© Copyright IBM Corp. 2007, 2011 203 Restoring the administrative workstation This section details how to restore previously backed up SmartCloud Control Desk administrative workstation information to a Windows workstation. This information can be used to return an existing SmartCloud Control Desk administrative workstation to a previous state. Before you begin
It is important to restore the back up of the database that was made when you backed up the administrative workstation. A database back up should be restored with 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: Procedure 1. 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 directory structure of the original installation. For example, if the SmartCloud Control Desk 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 target administrative workstation.
Installation properties Installation properties are recorded in properties files during a deployment and are used as input by future install-related actions. Installation properties are found in the install.properties and maximo.properties files as well as the database. You should only modify properties found in the install.properties file that are related to host names or user IDs. Changing values for other properties can severely impact your ability to perform future installation actions, upgrades and fix pack installations. Table 24. Installation properties Category Property Definition 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 attach to the database server.
For example, maximo mxe.db.schemaowner Owner of the database schema.
For example, maximo
This value must be dbo for Microsoft SQL Server.
204 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 24. Installation properties (continued) Category Property Definition mxe.db.password Password for the database user name. mail.smtp.host SMTP host server. mxe.workflow.admin E-mail account of the workflow administrator. mxe.adminEmail Valid e-mail address used by workflows to communicate with workflow participants. mxe.name Name to bind the MXServer server object to in the RMI registry.
For example, mxserver. mxe.hostname Name of the machine and port hosting MXServer. mxe.rmi.port RMI communication port. If set at zero, RMI uses any available port. You can select another available port number. mxe.registry.port The port number used to bind RMI/JRMP communications.
For example, 13400.
The RMI registry is started by the first instance of the maximo application to run. An environment could have multiple instances 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 other application instances to communicate with the central server. mxe.allowLocalObjects Set to true in production environments, to improve system performance. Set to false for development work, or for custom applications.
The default is false. mxe.useAppServerSecurity Indicates whether to use LDAP or native authentication. Setting this value to 1 indicates you are using LDAP for security. mxe.MLCacheLazyLoad By default, the multi-language metadata cache loads one object at a time. Set this flag to 1 to load all objects simultaneously for one language. mxe.UserLicenseKey The product enabler (license key) is used during installation. If the product enabler changes this value must be updated. mxe.adminuserid The administrative user. Used by the server for administrative tasks and to run cron tasks. This user must have access to all Sites in the system. mxe.adminuserloginid Defines the default login user ID for the product application.
The default value is maxadmin.
Chapter 18. Backup and restoration 205 Table 24. Installation properties (continued) Category Property Definition mxe.adminPasswd The password for the mxe.adminuserloginid user. mxe.system.reguser Self registration user. This user is responsible for the process by which users can create their own accounts.
The default value is maxreg. mxe.system.regpassword User registration login password. This value is the password for the user listed for mxe.system.reguser. mxe.email.charset The character set for e-mail notifications sent from the product.
When this property is defined, it is the charset that is used to encode the subject and message when an e-mail notification is sent. mxe.reorder.previewtimeout The reorder preview time out period (in minutes). This value must be set to the same value as the Web server session time out.
The default value is 30 minutes. mxe.security.provider The security provider is obtained from the policy file, which is normally com.sun.crypto.provider.SunJCE.
To use a different provider, you can specify a value for this parameter. mxe.mbocount Displays the number of business objects created by the server.
The default is 1. Changing the value to 0 disables this feature. mxe.esig.defaultuserid Set this flag to true if you want the Esignature login dialog to default to the login ID.
The default value is true. maximo.min.required.db.version Defines what the minimum level of database is required for an upgrade. An example value would be 7100. mxe.encrypted Property used by the application to determine if property files are encrypted.
This value is set to true if the file is encrypted. mxe.LDAPUserMgmt Indicates whether LDAP owns user management when mxe.userAppServerSecurity = 1.
The default value is 1. SmartCloud Control CCMDB.InstallLocation Product install location. Desk specific Properties For example, C:\\IBM\\SMP.
206 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 24. Installation properties (continued) Category Property Definition 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 administrative workstation system.
For example, en. CCMDB.BaseLanguage Base language that was set for the product.
For example, en. CCMDB.AdditionalLanguages Additional languages installed for the product. CCMDB.DeploySampleData Binary value that determines whether sample data is to be loaded during the installation.
For example, false. CCMDB.UserShortcuts Location of the menu for process solution installer 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 are deployed during the installation.
For example, true. process automation BASE.DeployOptionalContent Binary value that indicates if optional engine specific content is deployed during the installation. properties For example, true. BASE.DeployOptionalContentSet Indicates whether you selected to deploy optional content during the initial upgrade. This value, once set, is a fixed value and cannot be changed. This value will be used for all future upgrades and fix packs. BASE.VersionUpgradingFrom The previous version of process automation engine that was installed. LDAP Server-specific LDAP.AutomateConfig Binary value that indicates whether the Properties installation program automatically configures 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.
Chapter 18. Backup and restoration 207 Table 24. Installation properties (continued) Category Property Definition LDAP.AdminPassword Password for user ID named in LDAP.AdminDN. LDAP.ServerPort Port listening for connection requests.
For example, 389. LDAP.InstallLocation Install location of the directory server.
For example, C:\Program Files\IBM\LDAP\V6.2. Database-specific Database.AutomateConfig Binary value that indicates whether the Properties installation program automatically configures the database.
For example, true. Database.Vendor Database type.
For example, DB2. Database.RemoteAccessUserName Database server system user ID that is used for configure the database remotely. Database.RemoteAccessPassword Password for user ID named in Database.RemoteAccessUserName. mxe.db.driver Java class name of the JDBC driver.
For example, com.ibm.db2.jcc.DB2Driver, oracle.jdbc.OracleDriver,or 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 create when the application server is started.
For example, 8. mxe.db.maxFreeConnections Maximum number of free database connections available in the connection pool.
For example, 8.
208 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 24. Installation properties (continued) Category Property Definition mxe.db.minFreeConnections Minimum number of free database connections needed in the connection pool in order for more connections to be allocated.
For example, 5. mxe.db.newConnectionCount Number of new connections to be created when the minimum free connections are available 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 uppercase function for the system.
This value cannot be modified. mxe.db.autocommit This value sets the autocommit mode used for the Write connections. Can be either true or false. The default is false.
This value cannot be modified. mxe.db.systemdateformat System date format.
For DB2, the value is current timestamp.
For Oracle, the value is sysdate, and the default value cannot be edited.
For Microsoft SQL Server, the value is getdate(). mxe.db.format.nullvalue The database-specific format of the null value function.
For DB2 the value is COALESCE, and the default value cannot be edited.
The value for Oracle is NVL, and the default value cannot be edited.
The value for Microsoft SQL Server must be set to ISNULL. mxe.db.sqlserverPrefetchRows Setting to reduce lock contention.
Optimal setting is 200 rows. Setting a value larger than 500 can degrade performance.
The default value is 0.
This value is only valid for SQL Server.
Chapter 18. Backup and restoration 209 Table 24. Installation properties (continued) Category Property Definition mxe.db.logSQLTimeLimit The system logs the SQL statements that take longer than the specified time limit. The time 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 is printed in the log for every business object set that fetches beyond the set limit of rows. The stack trace log is also repeated for every multiple 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 in Database.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 product database.
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, measured in 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.
210 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 24. Installation properties (continued) Category Property Definition Database.Oracle.TempTablespaceMaxSize Maximum size of the temporary table space, measured in Mb.
For example, 8000. Database.Oracle.IndexTablespaceName Index table space name.
For example, maxdata. 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. mxe.db.schemaowner Owner of the database schema. Database.Oracle.SchemaPassword Password for user listed in mxe.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 for Database.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
Chapter 18. Backup and restoration 211 Table 24. Installation properties (continued) Category Property Definition 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 of pages).
For example, 32 Database.DB2.FencedUser Fenced user ID for DB2 on Linux or UNIX systems.
For example, db2fenc1. Database.DB2.AuthType Method DB2 uses to authenticate users.
For example, server. Database.DB2.DataTablespaceName DB2 table space name for the product database.
For example, maxdata. 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, measured in 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.
212 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Table 24. Installation properties (continued) Category Property Definition Database.DB2.TempTablespaceMaxSize Maximum size of the table space, measured in Mb.
For example, 8000. Database.DB2.IndexTablespaceName Index table space name.
For example, maxdata. 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 for Database.DB2.InstanceAdminUserName Microsoft SQL Server mxe.db.schemaowner Owner of the database schema. Properties Database.SQL.DatabaseName Name of the database.
For example, maxdb75. Database.SQL.InstallLocation Microsoft SQL Server installation location. For example,C:\\Program Files\\Microsoft SQL Server\\90. Database.SQL.DataFileLocation Location for database data file Database.SQL.DataFileName A way to specify the name of the data file used 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 database transaction log file. For example, maxdb75_log. Database.SQL.LogFileSize Microsoft SQL Server Database transaction log file size. Database.SQL.DataFilegroupName Database logical name file group. For example, PRIMARY. Database.SQL.ServerHostName Host name of the database server. For example, myhost.mydomain.com. Database.SQL.ServerPort Database server port. For example, 1433. Database.SQL.InstanceAdminUserName Administrative user for the Microsoft SQL Server instance. used during install for creating database, creating database user, and modifying the database. Database.SQL.InstanceAdminPassword Administrative users password. ADE (DE) Properties DE.InstalllLocation Location of the deployment engine.
Chapter 18. Backup and restoration 213 Table 24. Installation properties (continued) Category Property Definition Application Server ApplicationServer.Vendor Indicates which application server was Type Properties chosen during installation. For example, WebLogic.
Updating environment data When you install a second product on the same administrative workstation, or otherwise upgrade a single existing product, the installation program uses values recorded from the previous deployment. These values are stored on the administrative system in the install.properties and maximo.properties files, and also in the database. If you have made any environmental changes to any of the systems used for the original deployment, they must be recorded in the install.properties and maximo.properties files, and updated in the database. Typically these types of changes would include such as changing a host name or updating a password, for example. Before you begin
During a follow up installation task, the installation program uses values found in the install.properties and maximo.properties files to complete the upgrade or installation of an additional product. Pending successful use of these credentials, you are not prompted to provide them again. If the installation program fails to log in to the system using the credentials from the properties files, you are prompted to supply current credentials. These values are then written to the appropriate property file.
This method of updating credential information in property files has one exception. Database connection and credential information must always be current before you attempt an upgrade operation. Information for the database connection and credentials are stored in the maximo.properties file. Any changes to this information from the time of the original deployment must be manually recorded in the maximo.properties file before you upgrade.
Passwords will be encrypted within properties files. Update encrypted values in properties files with clear text values and then re-encrypt the property file. Procedure 1. Update the property value in the database by using the System Properties application in Maximo. For detailed information about managing system properties, see Administering Maximo Asset Management. 2. Complete the following steps to update database properties within the maximo.properties file: a. Change directory to Product_Home\maximo\applications\maximo\ properties\ b. Make a backup of the maximo.properties file. c. Delete the maximo.properties file. d. Change directory to Product_Home\etc e. Make a backup of the maximo.properties_orig found in the directory. This backup is a permanent backup that can be copied from when you need to update properties in the future.
214 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) f. Rename the unencrypted file named maximo.properties_orig to maximo.properties g. Copy the maximo.properties file to Product_Home\maximo\applications\ maximo\properties\ h. Edit the maximo.properties file and update the credential or connection information for the database server. i. Save the file. j. Run the encryptproperties.bat or encryptproperties.sh file located in Product_Home\maximo\tools\maximo\ directory against the file to encrypt it. 3. Complete the following steps to update properties within the install.properties file: The install.properties file contains most properties used by the installation program, including non-connection related properties for the database. These values must be up to date before you apply a fix pack or other upgrade operation. If these values have changed from the previous deployment, you must first manually update them. a. Change directory to Product_Home\etc\ b. Edit the install.properties file and make updates. Do not change encrypted properties (prefixed by [enc]). You are prompted for updated values during the update operation. These values are written to the install.properties file. c. Save the file. Results
After you have completed these updates, you will be able to upgrade, install a fix pack, or install another product using the corrected values.
Chapter 18. Backup and restoration 215 216 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
© Copyright IBM Corp. 2007, 2011 217 Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation Software Interoperability Coordinator, Department 49XA 3605 Highway 52 N Rochester, MN 55901 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating
218 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:
© IBM Corp. 2012. Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. 2012. All rights reserved.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks For trademark attribution, visit the IBM Terms of Use Web site (http://www.ibm.com/legal/us/)
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
IBM, the IBM logo, AIX, Tivoli, the Tivoli logo, and WebSphere are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.
Intel, the Intel logo, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.
Microsoft, Windows, the Windows logo, and Internet Explorer are trademarks of Microsoft Corporation in the United States, other countries, or both.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
Other company, product, and service names may be trademarks or service marks of others.
Notices 219 220 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) Index
installation (continued) A E properties 204 action e-mail listener Tivoli Integration Composer 130 install 184 configuring in WebLogic Server 31, Installation showavail 184 54, 89 post installation tasks 145 showinstalled 184 EAR files installation prerequisites, Integration undo 184 building manually 195 Composer 129 uninstall 184 manually deploying 195 installing upgrade 184 environmental data prerequisite software products 17, administrative workstation updating 214 101 backing up 203 executeMapping command 137 silent 101 restoring 204 Integration Composer aggregation packages 173 installing AIX F with process solution installation large page size support 9 fonts package 132 AIX 8 UNIX systems 132 Integration Composer installation B prerequisites 129 backup 203 Integration Composer installation, G confirming 134 general ledger account Integration Composer overview 129 creating 148 Integration Composer, uninstalling 138 C general ledger account component integration framework company related accounts creating 147 JMS options updating 149 general ledger component type configuring 30, 53, 87 configure 146 authorization item and company sets configure SMTP 146 updating 149 creating 147 configuring group 26 database server 69 confirming the Integration Composer J installation 134 H currency codes J2EE server help 145 creating 146 manually configuring 86 JRE configuring in Linux 11 D I IBM Tivoli Directory Server 26 database install on Solaris 200 applying changes 148 L manually configuring 79 database server 69 language enablement 152 verifying existing server using the DB2 languages middleware installation configuring existing server with the deploying after database update program 48 middleware installation deferral 43, 44, 66, 100 install program 47 launchpad automatic middleware install on Solaris and HP-UX 198 overview 15 configuration 17 manual configuration, 9.x 70 starting 16 install action 187 default insert site libraries install silently 101 creating 150 Linux 10 installation deploying ear files 42, 64, 98 logs advanced topics 193 deployment engine middleware installation program 19, automatically configuring existing backing up 14 21 middleware 45 deployment operations process solution installation deploying using manual middleware typical 176 program 189 configuration 69 deployment plan deploying with manually configured overview 17 middleware 69 directory server Integration Composer M manually configuring 79 with Launchpad 129 Maximo Application Server preparing 1 starting 42, 64, 98 product, automatically configured MAXIMOSERVER domain middleware 35, 57 creating 29, 52, 87 product, manually configured memory allocation middleware 91 changing 137
© Copyright IBM Corp. 2007, 2011 221 Microsoft Active Directory post-installation tasks (continued) solutionInstaller script (continued) configuring 83 top-level class for IT solutionInstaller.sh 184 configuring with middleware assets 151 startFusion file installation program 49 software 151 memory allocation 137 Microsoft SQL Server pre-deployment system check swap size manual configuration 76 process solution installation setting 11 restoring 164 program 181 system directories middleware 17, 101 prerequisite 17, 101 accessing 7 changing configuration process managers system password policy parameters 194 installing using the process solution considerations 14 install on Solaris and HP-UX 197, installation wizard 182 198 process solution command line interface install preparation on Solaris and reference 187 T HP-UX 197 process solution deployment tar command installing on HP-UX 197 managing from the administrative AIX 7 installing on Solaris 197 workstation 176 Tivoli Integration Composer remote configuration 12 process solution installation installation 130 starting and stopping 169 packages 172 starting on UNIX 170 process solution installation client 184 starting on Windows 169 process solution installation uninstalling 27 program 187, 188 U middleware clean up scripts 155 before you begin 175 ulimit middleware cleanup scripts 155 choosing 173 setting 11 middleware installation logs 189 uninstall before you begin 1 supported operations 174 automatically configured middleware installation program process solution package deployment 160 log reference 21 installation methods 171 automatically configured logs 19 product installation middleware 160 modfeatures action 188 before you begin 1 database configuration recover 162 product installation program manual 167 overview 33, 56 manually configured N properties deployment 161 installation 204 manually configured nstallation silent product installation 103 middleware 161 before you begin 1 manually removing files 167 product 159 R without uninstallation O program 165 recovery tool online help 145 recovery tool 165 uninstall 165 Oracle uninstall program recovery tool 166 restoration 203 manual configuration, 10g 74 uninstalling Integration Composer 138 manual configuration, 11g 72 uninstalling Integration Composer on restoring 163 Unix-based operating systems 139 Oracle WebLogic Server S uninstalling Integration Composer on configuring 193 security Windows operating systems 138 managing 193 configuring 153 user 26 manually uninstalling 195 selectable features 176 users post product installation 40, 62, 96 shared memory groups setting the host name in the setting 12 synchronizing 153 application 43, 66, 99 signing in 145 synchronizing 153 starting 193 signing in and out 152 organization silent install 101 creating 147 silent product installation V overview, Integration Composer 129 properties 103 verifying prerequisites SMTP 146 programmatically 2 software life cycle operations 171 verifying the installation solution installation program P manually 127 command line interface supported package types 172 programmatically 123 parameters 185 packages 172 solution installer program page size support 9 action 185 port availability solution packages W checking 6 command line interface 184 WebLogic Server post installation 145 solutionInstaller manually configuring 29, 51, 86 post product installation syntax 184 stopping 193 Oracle WebLogic Server 40, 62, 96 solutionInstaller script worktypes post-installation tasks 135 solutionInstaller.bat 184 creating 150
222 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server) X xml request pages 152
Index 223 224 IBM SmartCloud Control Desk: Installation Guide (Oracle WebLogic Server)
Printed in USA