You are on page 1of 200

IBM Control Desk

Version 7 Release 6

Installation Guide
(IBM WebSphere)

IBM

Note
Before using this information and the product it supports, read the information in “Notices” on page 187.

Contents
Chapter 1. Preparing for installation .. 1 Manually configuring DB2 v10.5 . . . .. 29
Before you begin . . . . . . . . . . . .. 1 Manually configuring Oracle 12c . . . .. 31
Installation resources for IBM Control Desk . .. 1 Manually configuring Microsoft SQL Server
Verifying prerequisites from the command line .. 2 2012 . . . . . . . . . . . . . .. 34
Checking port availability . . . . . . . .. 6 Manually configuring the directory server . .. 36
Accessing system directories . . . . . . .. 7 Manually configuring IBM Security Directory
AIX tar command requirements . . . . . .. 7 Server . . . . . . . . . . . . .. 36
AIX font requirements . . . . . . . . .. 7 Manually configuring Microsoft Active
Increasing AIX file size and number of descriptors 8 Directory . . . . . . . . . . . .. 40
Increasing AIX paging space . . . . . . .. 8 Manually configuring the J2EE server . . .. 42
Verifying large page size support for AIX . . .. 9 Manually configuring WebSphere Application
Enabling asynchronous I/O on AIX. . . . .. 9 Server Network Deployment . . . . .. 42
Checking for required libraries on Linux . .. 10 Installing Control Desk . . . . . . . .. 84
Configuring the JRE in Linux . . . . . .. 10 Configuring Control Desk with manually
Setting the ulimit . . . . . . . . . .. 11 configured middleware . . . . . . . .. 85
Setting the swap size . . . . . . . . .. 11
Setting shared memory . . . . . . . .. 12 Chapter 5. Deploying in a cluster
Enabling remote configuration . . . . . .. 12 environment . . . . . . . . . . .. 87
Enabling SSL client authentication . . . . .. 13 Configuring SSL between Microsoft Active Directory
Preparing Microsoft SQL Server . . . . .. 14 and WebSphere Application Server Network
System password policy settings . . . . .. 14 Deployment . . . . . . . . . . . . .. 87
Starting the launchpad . . . . . . . . .. 15 Installing DB2 v10.5 using the Control Desk
Installation program overview . . . . . . .. 16 installation . . . . . . . . . . . . .. 88
Configuration program overview . . . . . .. 16 Installing WebSphere Application Server Network
Deployment v8.5 using the Control Desk installation 89
Chapter 2. Automatically configuring Preparing WebSphere Application Server Network
middleware during deployment . . .. 19 Deployment and configuring application server
Configuring SSL between Microsoft Active Directory cluster profiles . . . . . . . . . . . .. 90
and WebSphere Application Server Network Configuring cluster members on additional
Deployment . . . . . . . . . . . . .. 19 WebSphere Application Server Network
Installing DB2 v10.5 using the Control Desk Deployment nodes . . . . . . . . . .. 91
installation . . . . . . . . . . . . .. 20 Installing Control Desk . . . . . . . . .. 92
Installing WebSphere Application Server Network Configuring Control Desk in a cluster environment 94
Deployment v8.5 using the Control Desk installation 21
Preparing WebSphere Application Server Network Chapter 6. Silent installation . . . .. 95
Deployment v8.5 using the configuration program . 22 Creating silent response files for installation . .. 95
Installing Control Desk . . . . . . . . .. 22 Sample silent installation response files . . .. 96
Configuring Control Desk . . . . . . . .. 23 Updating password values in silent response files 97
Silently installing the Installation Manager software 97
Chapter 3. Automatically configuring Silently installing Control Desk and related
existing middleware during deployment 25 middleware . . . . . . . . . . . . .. 98
Configuring SSL between Microsoft Active Directory Silently uninstalling Control Desk and related
and WebSphere Application Server Network middleware . . . . . . . . . . . . .. 98
Deployment . . . . . . . . . . . . .. 25
Preparing WebSphere Application Server Network Chapter 7. Silent configuration . . .. 101
Deployment v8.5 using the configuration program . 26 Creating silent response files for middleware
Installing Control Desk . . . . . . . . .. 26 configuration . . . . . . . . . . . .. 101
Configuring Control Desk . . . . . . . .. 27 Sample silent middleware configuration
response files . . . . . . . . . . .. 101
Chapter 4. Manually configuring Creating a response file for silent Control Desk
configuration . . . . . . . . . . . .. 102
existing middleware during deployment 29
Silently configuring middleware . . . . . .. 102
Installing Control Desk with manual middleware
Silently configuring Control Desk . . . . .. 103
configuration . . . . . . . . . . . . .. 29
Silently remove middleware configuration. . .. 104
Manually configuring the database . . . .. 29
Remove product configuration silently . . . .. 104

© Copyright IBM Corp. 2015 iii

Chapter 8. Verifying that the Manually uninstalling applications from
installation was successful . . . .. 107 WebSphere Application Server Network
Deployment . . . . . . . . . . . . .. 140
Manually installing applications in WebSphere
Chapter 9. Verifying the installation Application Server Network Deployment . . .. 140
manually . . . . . . . . . . . .. 111
Chapter 16. Command-line
Chapter 10. Configuring the HTTPOnly configuration . . . . . . . . . .. 143
attribute . . . . . . . . . . . . .. 113 Configuration parameter validation . . . . .. 143
Input properties files . . . . . . . . . .. 144
Chapter 11. Installation and Command line interface parameters . . . . .. 145
configuration programs log Command line configuration program actions .. 152
information . . . . . . . . . . .. 115 action updateDatabaseConfiguration . . .. 152
action validateDatabaseConfiguration . . .. 152
action
Chapter 12. Installing Integration validateAndUpdateDatabaseConfiguration .. 153
Composer . . . . . . . . . . . .. 117 action deployDatabaseConfiguration. . . .. 153
Integration Composer overview . . . . . .. 117 action removeDatabaseConfiguration . . .. 154
Hardware and software requirements . . . .. 117 action enableDB2TextSearch . . . . . .. 154
Installation prerequisites . . . . . . . . .. 117 action updateJ2eeConfiguration . . . . .. 154
Installing Integration Composer . . . . . .. 118 action validateJ2eeConfiguration . . . . .. 154
Installing Integration Composer using the action validateAndUpdateJ2eeConfiguration .. 154
launchpad . . . . . . . . . . . .. 118 action deployJ2eeConfiguration . . . . .. 155
Installing Integration Composer on UNIX action removeJ2EEConfiguration . . . . .. 155
operating systems in console mode . . . .. 120 action deployConfiguration. . . . . . .. 155
Upgrading Integration Composer. . . . . .. 122 action removeConfiguration . . . . . .. 155
Upgrading Integration Composer using the action reapplyAppServerTuning . . . . .. 156
launchpad . . . . . . . . . . . .. 122 action enableAppSecurity . . . . . . .. 156
Upgrading Integration Composer on UNIX action disableAppSecurity . . . . . . .. 156
operating systems in console mode . . . .. 123 action updateApplication . . . . . . .. 156
Confirming the installation . . . . . . . .. 125 action addLanguages . . . . . . . . .. 156
Post-installation tasks. . . . . . . . . .. 125 action configureProducts . . . . . . .. 157
Verifying the settings in the Integration action deployMiddlewareConfiguration . .. 157
Composer fusion.properties file . . . .. 125 Configuration program properties . . . . .. 158
Changing the memory allocation in the
startFusion file (optional) . . . . . . .. 127 Chapter 17. Configuring your product
Changing the memory allocation in the
with performance analysis data . .. 181
executeMapping file (optional) . . . . . .. 128
Uninstalling Integration Composer . . . . .. 129
Uninstalling Integration Composer on Windows Chapter 18. Backup and restoration 183
operating systems . . . . . . . . . .. 129 Backing up the administrative workstation . .. 183
Uninstalling Integration Composer on UNIX Restoring the administrative workstation . . .. 183
operating systems . . . . . . . . . .. 129
Chapter 19. Uninstalling the product 185
Chapter 13. Installing the Deployer's Removing Control Desk configuration values. .. 185
Workbench . . . . . . . . . . .. 131 Removing WebSphere Application Server Network
Deployment configuration data . . . . . .. 185
Uninstalling Control Desk and middleware . .. 186
Chapter 14. Post-installation tasks 133
Accessing product documentation . . . . .. 133
Installing help in a new language . . . . .. 133
Notices . . . . . . . . . . . . .. 187
Configuring initial data . . . . . . . . .. 134 Trademarks . . . . . . . . . . . . .. 189
Before working with BIRT reports . . . . .. 137 Terms and conditions for product documentation 189
Generating XML request pages . . . . . .. 137
Synchronizing users and groups . . . . . .. 138 Index . . . . . . . . . . . . . .. 191

Chapter 15. Maintaining EAR files .. 139
Building EAR files. . . . . . . . . . .. 139

iv IBM Control Desk: Installation Guide (IBM WebSphere)

Preparing for installation Familiarize yourself with the product media. make sure that you have the latest version of the installation documentation. database. Installation resources for IBM Control Desk When installing IBM Control Desk. can negatively affect the Control Desk installation on the system. Fully qualified host names provided to the installation programs must resolve between systems involved in the product deployment. and instructions on using the Control Desk launchpad. WebSphere Application Server V8.5. Ensure all IP addresses configured for systems targeted for the product deployment are reachable using the ping command from the administrative workstation. IBM Control Desk Support Resources Select the Architecture/Configuration Help tab to find the link to upgrade information for products that are based on Tivoli's process automation engine. preinstallation considerations. © Copyright IBM Corp. In some cases. Filling up the disk space on a Control Desk deployment system can cause problems with Control Desk operations. Product configuration matrix This workbook describes software support for IBM Control Desk and the various products and components that are based on Tivoli®'s process automation engine. Temporarily shut down any noncritical processes before running the Control Desk installation program. Use the planning information to understand the overall process of a Control Desk deployment before you use this information to conduct the installation. The following links offer additional resources. 2015 1 .5.5 Fix Pack 3 This site provides information about downloading WebSphere® Application Server version 8. such as anti-virus programs. Before you begin Prepare your environment before you install Control Desk. and application server on which you are planning to install the product. Make a copy of the image of the system. Ensure that you have adequate disk space for the future on the systems being used for the Control Desk deployment. overview of the installation procedure. you must be logged in as a user with administrator privileges on Windows or as root on UNIX.Chapter 1.5. Some processes. Installation Resources page on the IBM Control Desk wiki This site is frequently updated with useful tips and best practices for installation.

performance Use the performance parameter to have the prerequisite verification utility check for prerequisites performance settings for Control Desk. the prerequisite verification utility accepts various parameters.bat -component asset_mgt If you do not use the -component parameter. Syntax example: tpae_req_check. asset_mgt Use the asset_mgt parameter to have the prerequisite verification utility check for prerequisites that are required by Control Desk. 2 IBM Control Desk: Installation Guide (IBM WebSphere) . rxa Use the rxa parameter to have the prerequisite verification utility check for prerequisites that are required by Control Desk. Table 1. About this task When started from the command line. You can specify multiple components as comma-separated values. Use this utility before you start the product installation programs. db2 Use the db2 parameter to have the prerequisite verification utility check for DB2® prerequisites. you are prompted to specify components when you use the utility. At least one component must be used with the prerequisite verification utility. The prerequisite verification utility must be run on the system that hosts the prerequisite to check. was Use the was parameter to have the prerequisite verification utility check for WebSphere Application Server Network Deployment prerequisites. Verifying prerequisites from the command line You can use the prerequisite verification utility from the command line to verify that installation program prerequisites are present on a system. . asset_mgt_upg Use the asset_mgt_upg parameter to have the prerequisite verification utility check for prerequisites that are required to connect remotely during configuration. System verification parameters Parameters Details -component Specifies the type of component to verify. You cannot use this utility to check prerequisites on a remote system. Run the prerequisite verification utility with the pip parameter on the administrative workstation.

The prerequisite verification utility verifies that this port is available on the DB2 server host. default property values are used. Verbose Selecting this qualifier results in detailed trace information that is generated while the utility is running. and is found on the middleware installation media in the SystemRequirements directory. Syntax example: tpae_req_check. silent If you use the silent qualifier. The default input property file is tpae. the utility defaults to running in interactive mode. Preparing for installation 3 . the prerequisite verification utility is run in interactive mode. Syntax example: tpae_req_check. or create your own. you can also use the input parameter and supply a property file. These sample property files contain custom values that are defined for particular operating systems. the utility is run in interactive mode. Syntax example: tpae_req_check.bat -component db2 -input path to the property file If you do not use the input parameter when you run the prerequisite verification utility. -mode You can run the prerequisite verification utility in silent or interactive mode. System verification parameters (continued) Parameters Details -input The prerequisite verification utility can accept a property file as input. For example. The utility verifies property values that are found in the file. None Selecting this qualifier results in no trace information that is generated while the utility is running. You are prompted for individual values to be verified. If an input file is not provided. Several sample property files are found in the SystemRequirements\ sample_property_files directory.log -trace Parameter that is used to specify trace output statements while the utility is running. interactive By default.bat -component db2 -trace None Chapter 1. Normal Selecting this qualifier results in default trace information that is generated while the utility is running. before you run the prerequisite verification utility. the default DB2 server port parameter is DB2_SERVER_PORT=50000. The output must also be directed to a file to view the results. If you do not specify the -mode parameter. You can copy these property files to the system and modify them.Table 1.bat -component db2 -mode silent -input path to the property file > prereqresults.properties.

00GB 1.availablePorts.properties file to verify that a system is suitable to host DB2 for a Control Desk deployment. Run the prerequisite verification utility.5900. C: PASS 27.99GB 1000MB Disk#3 (C:\Temp\1) PASS 27. Ensure that the middleware installation media is mounted or otherwise available to the system.445.139 50000 network.bat -component db2 -input d:\SystemRequirements\tpae.99GB 300MB Disk#2 (C:\Temp\1) PASS 27..5800. Results After the prerequisite verification utility successfully completes the verification task.90GB network.totalPhysicalMemory PASS 2.2967. ======== ====== ===== ===. the tpae.2967.properties file is in the same directory as the tpae_req_check. Procedure 1.availablePorts. 3. CTGIN8118I : The Tivoli Pre-requisite Scanner exited with the return code IBM Prerequisite Scanner Version : 1.ctginst PASS 135. os.99GB 250MB network.db2 PASS 135. 2.. tpae_req_check. Log on to the system you are checking for prerequisites with a user ID that has permission to run scripts on the system.hasFQDN FAIL False True Disk#1 (C:\ibm\tivoli\mwi\workspace) PASS 27. 4 IBM Control Desk: Installation Guide (IBM WebSphere) .. Specify the component to check and the property file to use.5800.40GB ALL COMPONENTS : Property Result Found Exp.bat script. This example procedure uses values that are found in the default tpae. results are printed to the screen.445. ======== ====== ===== ===. resolve the issue and rerun the verification utility before you install Control Desk components...bat 1 These values can also be redirected to a file when you start the command from the command line. If any of the verification steps report a failure.1025.139 50005 Disk#4 (C:\Program Files\IBM\SQLLIB) PASS 27..99GB 1. 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.1025.0.3389.34 Build : 20101109 OS Name : Microsoft Windows Server 2012..91GB Prereq Scanner Overall Result: FAIL prereq_checker.5900. CTGIN8117I : The Tivoli Pre-requisite Scanner has been launched.99GB 2.3389.. Open a command-line window and change directory to the SystemRequirements directory of the middleware installation media.properties In this example.

package. os. network.availablePorts.package.dns Verifies that there is a DNS entry for the system on the DNS server. os. os.* Verifies that required ports are available. os.lib.package.package. os. os. Use this information to analyze prerequisite verification utility results.MozillaVersion Checks browser version.tmp/home Verifies required permissions for the system directories os.package.iodevicestatus Verifies the I/O device status of the system. network. os. os.availablePorts. CpuArchitecture Verifies that the machine architecture is supported. os.Version Checks browser version.* Verifies that a prerequisite library is available on the system. os. os.dir. Prerequisite verification utility properties Property Description browser.package. The following example checks to ensure a port that is required by DB2 is available. The Table 2 table contains a list of the properties checked.expat Verifies a prerequisite library that is required for GTK on AIX is available on the system.pixman Verifies a prerequisite library that is required for GTK on AIX is available on the system.libjpeg Verifies a prerequisite library that is required for GTK on AIX is available on the system.mountcheck Checks for the existence of nosuid on the file system.architecture Verifies that the operating system architecture is supported.fontconfig Verifies a prerequisite library that is required for GTK on AIX is available on the system.package.cairo Verifies a prerequisite library that is required for GTK on AIX is available on the system.glib2 Verifies a prerequisite library that is required for GTK on AIX is available on the system.kernelversion Checks kernel version. os.package.package. os.package.fqdn Verifies that the system host name is fully qualified.gtk2 Verifies a prerequisite library that is required for GTK on AIX is available on the system. network. os. os.libtiff Verifies a prerequisite library that is required for GTK on AIX is available on the system. os. os. os. os. Preparing for installation 5 . Chapter 1.pango Verifies a prerequisite library that is required for GTK on AIX is available on the system.package. Table 2.package.package.libpng Verifies a prerequisite library that is required for GTK on AIX is available on the system. os.db2inst=50000 network.gettext Verifies a prerequisite library that is required for GTK on AIX is available on the system.freetype2 Verifies a prerequisite library that is required for GTK on AIX is available on the system.atk Verifies a prerequisite library that is required for GTK on AIX® is available on the system.FreePagingSpace Verifies that adequate free paging space is available on the system.

unit:MB]512 os.Table 2.xrender Verifies a prerequisite library that is required for GTK on AIX is available on the system.ServicePack Verifies that required service packs are installed on the system.var=[dir:root=/var.xft Verifies a prerequisite library that is required for GTK on AIX is available on the system. About this task Default port values are assigned for the middleware that you deploy.SeaMonkeyVersion Checks browser version.zlib Verifies a prerequisite library that is required for GTK on AIX is available on the system.package. os.space. For example. os. os.Version Reports the operating system type and version. Port 9060 or an alternative port must be available for IBM® WebSphere Application Server Network Deployment.package.space. os. os. port 50000 or an alternative port must be available for DB2. The following example shows the check that is made for the middleware installation program workspace. ensure that certain ports in your environment are available for use with the middleware that you are installing. os.default Determines the default shell for users.* Determines disk space availability for various file systems. For a full list of port requirements.SELinux Determines whether selinux is enabled. You can either use the prerequisite verification utility to check for port availability or you can check manually. Checking port availability Before you use the product installation programs.totalPhysicalMemory Reports physical RAM available to the operating system. os.rpm Verifies that prerequisite packages are available on the system.package.xcursor Verifies a prerequisite library that is required for GTK on AIX is available on the system. 6 IBM Control Desk: Installation Guide (IBM WebSphere) . os.package.shell.RAMSize Reports system RAM available. os. OS. os. os. os. Prerequisite verification utility properties (continued) Property Description os.ulimit Identifies user limits that are configured on the system. see the information on the System Requirements page in the IBM Control Desk wiki.package.

If you have set a symbolic link to overwrite the native UNIX tar command with the GNU tar command an error occurs. 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 installation and configuration programs. If one of these directories uses a symbolic link. For example. The GNU tar path must be defined before the native UNIX tar path. Verify that the system path variable contains both native UNIX tar and GNU tar paths. The network.14 ensures that installation files can be extracted. /products/home.com/systems/p/os/aix/linux/toolbox/download.availablePorts. http://www. Before you begin Assign access permission for the /tmp and /home directories on Linux systems before you use the Control Desk installation and configuration programs.14 or higher is installed. the native tar utility is installed in /usr/bin and the GNU tar utility is installed in /opt/freeware/bin/tar. for example.html AIX font requirements AIX requires specific fonts to produce reports. Accessing system directories You must assign access permission to particular directories before you use the product installation and configuration programs. specify the value of an open port when you are prompted to by the installation program. ensure that GNU tar version 1. If you find that a port is already assigned. and run permissions for the /tmp and /home directories. Log in to the system as a user with root authority on the system. Chapter 1.* parameter indicates the availability of the required ports.ibm. Procedure 1. 2. write. About this task To install. Because the native utility does not support long file names. ensure that symbolic link directory also has the correct access. Check the available ports on the host system: Option Description Automatic Run the prerequisite verification utility. you must have read. Procedure 1. Manual Run the following command to see a list of active connections: netstat -ao 2. Preparing for installation 7 . GNU tar version 1.

2. About this task To add more paging space. 3. 4. for example: Page Space Physical Volume Volume Group Size Used hd6 hdisk0 rootvg 5632 MB 2 2. Verify the settings from a command window with 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 Increase the default paging space for the AIX system to a minimum of 4 GB. Procedure 1. Ensure the fonts-path environment variable refers to the location of the fonts. Save and exit the file. Install TrueType fonts on the AIX system. Locate the section for the root user. Determine the size of a logical partition by issuing the following command: lslv hd6 8 IBM Control Desk: Installation Guide (IBM WebSphere) . root: fsize = -1 nofiles = 8192 A value of -1 for the fsize parameter indicates no limit. About this task When you produce reports from AIX systems. Determine the current amount of paging space available to the server by issuing the following command. or. Increasing AIX file size and number of descriptors Increase the default number of file descriptors that are allowed for the root user and set the maximum allowable file size to unlimited. Open the /etc/security/limits file in a text editor. You must log out as root and log back in for these changes to take effect. preferably. lsps -a This command results output contains the following information. Procedure 1. 2. the total amount of physical memory in the system. Procedure 1. and change the parameters values. you must add logical partitions to the system. TrueType fonts must be available on the system.

This command results in output that includes partition information. that system must be configured to support large page sizes. Chapter 1. large page size support must be enabled on AIX servers that host WebSphere Application Server. chps -s 10 hd6 adds 10 logical partitions to the logical volume hd6. For example. Add more logical partitions. Typically this feature is enabled by default on AIX systems. which results in adding 1280 Mb to the paging space. Preparing for installation 9 . About this task If you are deploying Control Desk on WebSphere Application Server hosted on an AIX system. for example: Table 3. 2. These results show a total of 5632 Mb of paging space available to the system. Procedure 1. 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. Verify large page size support by running the following command: ps -Z Output from the command includes 4 K and 64 K page sizes that are listed for processes. 3. You must have root authority to work with the AIX operating system commands. which are required to add more paging space. Verifying large page size support for AIX For Control Desk to function correctly. a total of 44 Logical Partitions are shown that are each 128 Mb in size. Large page usage is primarily intended to provide performance improvements to high performance computing applications. LPs PP Size 44 127 megabytes In the example output. Log on to the AIX system that hosts WebSphere Application Server and open a console window. 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 Enabling asynchronous I/O on AIX IBM Security Directory Server requires asynchronous I/O be enabled on AIX systems.

Without asynchronous I/O. Open a terminal and run the following command: smit chgaio 3. or other systems with Security-Enhanced Linux (SELinux) enabled. SUSE Linux Enterprise Server 10 64-bit systems that host manually configured middleware must host this package. From the System Management Interface tool (SMIT) dialog box. 3. Exit SMIT.3. Oracle database instances cannot be started successfully. 6. the Control Desk installation program produces an error when run in graphical mode. Run the following command from the command line: smit aio 7.so. 10 IBM Control Desk: Installation Guide (IBM WebSphere) . To enable asynchronous I/O. Locate the following libraries in the /usr/lib64/ directory: v libstdc++. Checking for required libraries on Linux The Control Desk deployment requires certain Linux system libraries. Ensure that you have the compat-libstdc++ library installed on Red Hat Enterprise Linux v6 systems that run the product installation program or the process solution installation program.so. Log in to the system as root. 2. follow these steps: Procedure 1. In the System Management Interface tool (SMIT) dialog box.3-11. Without asynchronous I/O.6 v libaio. select Configure Defined Asynchronous I/O. Click OK. Ensure that you have the libstdc++33-32bit-3. change STATE to be configured at system restart from defined to available. DB2 database instances cannot be started successfully. 5.5 v libstdc++. About this task Asynchronous I/O must be enabled on AIX systems if the system hosts IBM Security Directory Server. 4.1 If these libraries are not installed. If you cannot locate this library on your system. and then click Enter.rpm package that is installed before you run the product installation program. Procedure 1.x86_64.so. 2.9. Configuring the JRE in Linux The Control Desk installation or configuration program might fail on Red Hat Enterprise Linux systems. Restart the system to enable the changes. 8. locate the Red Hat Package Manager package for your system that contains these libraries and install the packages.

type ulimit -n 8192 Setting the swap size Control Desk can be a resource-intensive application. This solution. About this task In one scenario. 3. About this task For Linux systems. The ulimit setting is used to define user system and process resource limits. affects the level of security for the entire system. Setting the ulimit Set the ulimit in Linux. Preparing for installation 11 . however. Set the size of the swap space that is used in Linux systems. For more information. Configure and tune your system for maximum performance.profile for root. From a command line. Procedure 1. About this task Typically. Run the Control Desk installation or configuration program. Manually issue the chcon command. Procedure 1. 2. From a command line. In another scenario. see “Increasing AIX file size and number of descriptors” on page 8. type ulimit -f unlimited 2. Chapter 1. Temporarily disable SELinux by using the setenforce 0 command. see the product documentation for your Linux distribution. More swap space can be made available to the system. see “Increasing AIX paging space” on page 8. If you set the ulimit in . the swap size for Linux is set to twice the amount of physical RAM in the server. Re-enable SELinux by using the setenforce 1 command. the Control Desk installation or configuration program fails stating that it cannot find the VM. For AIX systems. the ulimit setting applies to all processes. you can edit the /etc/selinux/config file and set SELINUX to either permissive or disabled for a more permanent fix. For AIX systems. you must set the ulimit for the system before you use the Control Desk installation program. the Control Desk installation or configuration program fails with an error that states that the Java™ Runtime Environment (JRE) cannot be found. Alternatively. chcon -R -t textrel_shlib_t install_home/jvm/jre Results The Control Desk installation or configuration program is now able to locate the JRE. 4.

by configuring it to use port 445. you must install OpenSSH on remote non-Windows workstations to log on to them using the SSH protocol. Procedure v Increase the size of the existing swap partition. Enabling remote configuration The Control Desk configuration program can automatically configure middleware. v The user name that you provide to the Control Desk configuration program must exist as a local account on the remote system. This user must be a member of the Windows Administrators group. The IBM JRE on the Control Desk administrative workstation includes SSH. Alternatively. type sysctl -w kernel. 2. Use the credentials that you plan to supply to the Control Desk configuration program. you can configure SMB to use TCP/IP as the transport protocol. v Create a swap file. For remote Windows systems. About this task For Linux systems. You must enable a remote access protocol for each system on which you intend to configure the middleware. Update the value in /etc/sysctl. 12 IBM Control Desk: Installation Guide (IBM WebSphere) . you must set a minimum shared memory value for the system before you use the Control Desk installation program. Setting shared memory Set a minimum shared memory value in Linux.conf. v The following Windows services must be started on the remote system before you begin a remote configuration: – winmgmt (Windows Management Instrumentation) – RemoteRegistry (Remote Registry) – lanmanserver (Service) v The SMB protocol must be enabled and configured to send NetBIOS over TCP/IP. from a command line. by choosing to use port 139. without NetBIOS. extra swap partition.shmmax and determine whether the value is less than 268435456 bytes (256 Mb). type sysctl kernel.shmmax=268435456. Windows SMB is a Windows protocol. v Create a new. Before you start the Control Desk configuration program. You do not need an SSH client to remotely configure middleware on Linux or UNIX systems. From a command line. But. Use SSH for accessing remote Linux and UNIX systems. If you must increase the value. ensure that the following requirements are met before you configure the software. Procedure 1. 3. ensure that you can log on to any remote servers with the protocols that you intend to use. Use Windows SMB accessing remote Windows systems.

0. v The Windows administrative share (C$) and the interprocess communications (IPC$) folder must be shared. Oracle Solaris systems must have the ksh environment installed and properly configured. v The user name that you provide to the Control Desk configuration program must exist as a privileged account (for example. v Ensure that any ports that you use for remote protocols are not blocked by firewall software or security policies. v For Windows systems that have User Account Control (UAC) enabled. and clear the Use Simple File Sharing check box. start Windows Explorer. Port 139 is used if SMB is configured to run on NetBIOS over TCP/IP. set the TMOUT and TIMEOUT variables in the user profile script to 0. v To disable simple file sharing. Before you begin The Control Desk configuration programs use HTTP client requests for various configuration actions. v For AIX systems. The Control Desk configuration program does not configure Chapter 1. v If Cygwin is installed on the remote Windows system the SSH daemon (sshd) must be uninstalled or disabled. This setting prevents the user from idling out and being logged off the remote system during the configuration. root) on the remote systems. set the following SSH parameters in the /etc/ssh/sshd_config file. the remote access protocols require the use of internal shell scripts that must be run within the Korn (ksh) shell. without NetBIOS. even if the user ID that you use to log on to the remote system is configured to use a different shell. v For Microsoft Windows Server 2008 systems that support password-protected sharing. The methods need ksh. including ports 137 and 139. v For Oracle Solaris systems. v For AIX systems. v Ensure that a current version of OpenSSH is installed and running. Shares must be shared for the Guest or Everyone accounts. Preparing for installation 13 . disable password-protection. For remote Linux or UNIX systems. Do not use OpenSSH 4. You can use a workaround to enable client authentication during configuration. Remote configuration does not support accessing network drives on the local or remote system.7. Click Tools > Folder Options. v If you plan to remotely configure software on remote Linux or UNIX computers. ensure that the following requirements are met before you configure the software. – ClientAliveInterval 900 – ClientAliveCountMax 10 Stop the SSH daemon with the stopsrc -s sshd command and then restart it using the startsrc -s sshd command. it must be disabled before software can be remotely installed and configured.5302. Port 445 is used if SMB is run directly on TCP/IP. ensure that SSH is installed. Enabling SSL client authentication The Control Desk configuration program produces an error if the client authentication feature of secure sockets layer (SSL) is enabled in the IBM HTTP Server.

they do function in environments where WebSphere Application Server Network Deployment and IBM HTTP Server are manually configured to use SSL. However. Stop and restart the IBM HTTP Server. 5. About this task If client authentication must be enabled for the IBM HTTP Server. Ensure that you have the following options set for the Microsoft SQL Server database you intend to use with Control Desk. Microsoft Windows Server 2008 systems have a stricter set of password requirements than previous versions configured by default. Remove the SSLClientAuth Required directive in the httpd. Control Desk configuration and standard deployment procedures do not work correctly when the client authentication feature of SSL is enabled in IBM HTTP Server. If you are not familiar with these stronger password requirements.conf configuration file. use the following workaround procedure to install the product. familiarize yourself with the password policies of systems that are used in the deployment. you might experience an 14 IBM Control Desk: Installation Guide (IBM WebSphere) . 3. Stop and restart the IBM HTTP Server. Preparing Microsoft SQL Server Microsoft SQL Server must be configured with specific options before you can use it with Control Desk. v Use the SQL Server Configuration Manager to disable TCP/IP dynamic ports usage on the server.conf configuration file of the IBM HTTP Server. Client authentication is enabled in the IBM HTTP Server. Add the SSLClientAuth Required directive back to the httpd. For example. v Verify that you enabled the Full-text Search setting during the installation of Microsoft SQL Server. by using the SSLClientAuth Required directive in the httpd. the validation of product administration credentials or the import of data with Maximo® Enterprise Adapter fails. WebSphere Application Server Network Deployment nor IBM HTTP Server to use SSL. Before deploying Control Desk. Run the Control Desk configuration program. v Set Microsoft SQL Server Database Collation settings to the following options: – Dictionary order – Case-insensitive – For use with 1252 Character set System password policy settings Familiarize yourself with the password policies of systems that you are using as part of a Control Desk deployment. Your organization might have password policy regulations that are enforced on systems on your network. 2. 4. Procedure 1.conf configuration file of the IBM HTTP Server. These settings must be configured before you use the Control Desk configuration program to configure Control Desk. As a result.

The launchpad also contains links to product information. Download and extract the launchpad images. To save the messages from a session. Modify the /user_dir/launchpad/Firefox. 2. The launchpad program uses the system default browser to run. error during the installation of Control Desk. Passwords are not validated against the password policies of target systems at the time you enter them on the installation and configuration program panels. Messages that are generated while the launchpad is running are not automatically saved on the hard disk drive. Start the launchpad from the root directory of the installation image. For information. Chapter 1. This error occurs when you create users on a Microsoft Windows Server 2008 system. Password values that you provide during the Control Desk installation and configuration must be compliant with the password policies set for the target system. Preparing for installation 15 . Starting the launchpad The IBM Control Desk launchpad serves as a centralized interface for starting the product installation and configuration programs. Before you begin Before you start the launchpad. ensure that you meet the middleware prerequisites. export LOGNAME 3. Ensure that you have the correct service pack levels for your environments. To show the log frame on the launchpad panels. About this task The launchpad generates messages that are captured in a hidden log frame while the launchpad is running. Run the launchpad from /user_dir. complete the following steps: 1.exe program. hold the Ctrl key and simultaneously click the banner frame of the launchpad. Always use fully qualified domain names when you enter values for the installation and configuration programs. click Save at the bottom of the log frame. If you must use the launchpad with the Firefox browser. Procedure 1. Log on to an account with system administration privileges on the system where you want to install Control Desk. Option Description Windows Start the launchpad by using the launchpad64. it is likely that the launchpad program does not run properly due to the ksh shell interface.sh file and remove the following lines: typeset +r LOGNAME 2>/dev/null LOGNAME=lp_user_$$. If the default browser on AIX is Firefox. see the download document. 2.

/launchpad. . Configuration program overview Use the configuration program to configure Control Desk and associated middleware. IBM WebSphere Application Server and IBM DB2. The installation program downloads the latest version of the packages listed from IBM Fix Central. start the installation program locally on the system that is designated as the IBM WebSphere Application Server server. 16 IBM Control Desk: Installation Guide (IBM WebSphere) . To search for fixes. Option Description AIX and Linux Start the launchpad from the root directory by using the launchpad. click Check for Other Versions.sh program. Note: In this documentation. Fixes. The configuration program is used to perform the following configuration tasks: v Prepare IBM WebSphere Application Server for configuration of your product v Configure a new Control Desk deployment v Update database access credentials v Change the Control Desk security model v Change the database server host v Update IBM WebSphere Application Server access credentials v Change IBM WebSphere Application Server host v Update database and build and deploy application EAR files v Install product help information in another language v Remove IBM WebSphere Application Server configuration v Remove Control Desk configuration The Control Desk configuration program records configuration choices that you make about your Control Desk deployment and then deploys Control Desk based on the information that you entered.sh Related information: Software Product Compatibility Reports Installation program overview Use the Control Desk installation program to install Control Desk. the configuration program referred to is Tivoli's Process Automation Suite Configuration program. and extensions for the packages listed. Select packages to install from the user interface. Run the installation program on the target system to install the component. and Extensions. updates. to install IBM WebSphere Application Server. for example. For example.

Figure 1. Control Desk configuration program

Information that you enter for the configuration program is stored in the
maximo.properties and install.properties files. Some of this information is also
written to the Maximo database. These values are displayed in the panel fields of
the configuration program during an upgrade or fix pack application.

The configuration program validates the values that you enter in configuration
item fields. Some configuration item fields are validated as a pair, for example,
user name and password fields.

In most cases, you can run the configuration program locally or remotely. You are
required to run the configuration program locally on the IBM WebSphere
Application Server server when you are preparing it for Control Desk
configuration.

If you choose not to have the configuration program automatically configure
middleware, you must configure that piece of middleware manually before the
configuration of Control Desk.

Note: If you are using a directory server to secure Control Desk, be aware of the
product-specific syntax rules for using special characters in LDAP strings that you
enter. In most cases, special characters must be preceded by an escape character to
make them readable by the directory server.

Many directory server products consider a blank space to be a special character in
an LDAP string. If you enter an LDAP string with an unescaped blank character at
the end of a field value, you encounter Control Desk errors.

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

Chapter 1. Preparing for installation 17

18 IBM Control Desk: Installation Guide (IBM WebSphere)

Chapter 2. Automatically configuring middleware during
deployment
Install and automatically configure a Control Desk deployment in your enterprise.

About this task

This is a high-level overview of tasks that you need to complete to deploy Control
Desk with automatic middleware configuration.

In this scenario, you use the Control Desk installation and configuration programs
to install and automatically configure new instances of the following components:
v DB2
v WebSphere Application Server Network Deployment
v Control Desk

You use the Control Desk installation program to install Control Desk and the
middleware you want to use in your deployment. You then use the configuration
program to configure both middleware and Control Desk.

You can use the installation program to install DB2. You then use the configuration
program to automatically configure it.

Configuring SSL between Microsoft Active Directory and WebSphere
Application Server Network Deployment
To enable the configuration program to automatically create users and groups
within Microsoft Active Directory, you must configure SSL communication between
Microsoft Active Directory and WebSphere Application Server Network
Deployment using the configuration program. If you plan to use a directory
server for Control Desk authentication and authorization, users and groups must
be created in the directory. If you plan to use Control Desk application security for
authentication and authorization, you do not need configure SSL for a directory
server.

About this task

This procedure is only required if you choose to allow the configuration program
to automatically configure WebSphere Application Server Network Deployment.
Then, you also want the configuration program to automatically create users in
Microsoft Active Directory.

You must enable SSL for Microsoft Active Directory, generate a certificate, and then
add that certificate to WebSphere Application Server Network Deployment.

Changing the name or domain of the certificate authority at any point invalidates
certificates previously issued from that authority.

Ensure that you have host name resolution setup properly in your
environment. Communication failures occur if the system hosting Microsoft Active
Directory cannot resolve host names for systems that have been issued certificates.

© Copyright IBM Corp. 2015 19

Installing DB2 v10.5 using the Control Desk installation
Use the Control Desk installation program to install DB2 v10.5.

Procedure
1. Log in to the target system as a user with administrative authority. If you are
running the Control Desk installation from a Linux or UNIX terminal window,
you must be logged in as the root user.
2. Start the Control Desk installation program from the launchpad.
a. Start the launchpad.
Windows
From the downloaded installation image, browse to the root
directory and run the following command: launchpad64.exe.
Linux and UNIX
From the downloaded installation image, browse to the root
directory and run the following command: launchpad.sh.
b. Select a language for the installation and click OK.
c. In the launchpad navigation pane, click Install Product.
d. From the Install Product panel, select IBM DB2 v10.5 and then click
Install IBM Control Desk components.
3. In the package selection panel, click Next.

Important: In the package selection panel, ensure that IBM Maximo for
Service Providers is selected. This package is required for the complete
installation of Control Desk including the advanced edition.
4. In the package prerequisite validation panel, review the results of the
prerequisite check and click Next. If any errors are reported on this panel,
resolve the issue and then click Recheck Status before continuing.
5. In the license agreement panel, review the license information for each
package being installed, accept the license agreement and click Next.
6. In the Installation Manager installation location panel, specify path
information for the shared resources directory and the Installation Manager
installation directory and click Next. Installation Manager is the installation
framework that is used to install Control Desk components. The shared
resources directory is a common workspace directory used by Installation
Manager when installing packages.
7. In the package installation location panel, select a package group, specify the
path information for its installation directory and click Next. Repeat this
process for each package group listed.
8. In the package translations panel, specify language support for DB2 and click
Next.
9. In the package features panel, leave all default options checked and click
Next.
10. In the package configuration panel, specify configuration information for DB2
v10.5 and click Next.
11. In the package summary panel, review the information for the planned
installation and click Install.

20 IBM Control Desk: Installation Guide (IBM WebSphere)

install Java v7. Chapter 2. In the package installation location panel. and click Next. specify language support for WebSphere Application Server Network Deployment and click Next. In the launchpad navigation pane. Windows From the downloaded installation image. specify path information for its installation directory. Automatically configuring middleware during deployment 21 . 3. a. specify the path information for the shared resources directory and the Installation Manager installation directory and click Next. In the package translations panel. Start the launchpad. Linux and UNIX From the downloaded installation image. b. browse to the root directory and run the following command: launchpad64. review the information and click Install. In the package configuration panel. specify configuration information for IBM HTTP Server and click Next. 5. Log in to the target system as a user with administrative authority. In the license agreement panel. Installation Manager is the installation framework that is used to install Control Desk components. review the results of the prerequisite check and click Next. Select a language for the installation and click OK.5 using the Control Desk installation Use the Control Desk installation program to install WebSphere Application Server Network Deployment v8. select a package group. This package is required for the complete installation of Control Desk including the advanced edition. accept the license agreement and click Next.sh. you must be logged in as the root user. If any errors are reported on this panel. Repeat this process for each package group that is listed. 9. 4. 7. browse to the root directory and run the following command: launchpad. In the package selection panel. leave all default options selected and click Next. From the Install Product panel. In the package summary panel.5. In the package prerequisite validation panel. c. 8. select IBM WebSphere Application Server Network Deployment v8. During the installation of WebSphere Application Server Network Deployment. review the license information for each package that is to be installed. In the package features panel.exe. 6. click Next. In the Installation Manager installation location panel. resolve the issue and click Recheck Status before continuing. the configuration program configures Control Desk to use Java v7. ensure that IBM Maximo for Service Providers is selected. The shared resources directory is a common workspace directory used by Installation Manager when installing packages. 2. click Install Product.5 and click Install IBM Control Desk components. Important: In the package selection panel.5.Installing WebSphere Application Server Network Deployment v8. 10. Procedure 1. Start the Control Desk installation program from the launchpad. When you install Java v7. d. 11. If you are running the IBM Control Desk installation from a Linux or UNIX terminal window.

run the installation program on the Control Desk administrative system. 22 IBM Control Desk: Installation Guide (IBM WebSphere) . After the installation is complete.5 using the configuration program Use the configuration program to prepare WebSphere Application Server Network Deployment v8. select the option to start the IBM Tivoli Process Automation engine configuration utility and click Finish. 12. if required. What to do next Use the configuration program to prepare WebSphere Application Server Network Deployment for Control Desk configuration.5 for Control Desk configuration. 3. Preparing WebSphere Application Server Network Deployment v8.5 is ready for Control Desk. Start the configuration program from the Control Desk launchpad. Select the option to automate the configuration of IBM HTTP Server. specify information to use to create the WebSphere Application Server Network Deployment deployment manager and application server profiles. 6. In the Configure Application Server Profiles panel. select all deployment operation options and click Finish. click Prepare WebSphere Application Server Network Deployment for configuration. specify the installation location and configuration information for WebSphere Application Server Network Deployment and associated components. In the Apply Deployment Operations panel. 5. click Configure Product and click Launch the Tivoli’s Process Automation Suite configuration program. About this task To install Control Desk. In the launchpad navigation pane. In the Control Desk configuration operations page. 2. specify information about the directory server host. Results WebSphere Application Server Network Deployment v8. Optional: In the Configure Application Server Advanced Options panel. 7. 4. Installing Control Desk Install Control Desk. specify additional configuration information. If you chose to use a directory server for WebSphere Application Server Network Deployment administrative security. credentials and directory structure from the Configure Administrative Security panel. In the Configure the Application for WebSphere panel. Procedure 1.

8. Configuring Control Desk Configure Control Desk. b. accept the license agreement and click Next. you must be logged in as the root user. In the launchpad navigation pane.exe. This package is required for the complete installation of Control Desk including the advanced edition. In the package summary panel. 4. In the license agreement panel. Linux and UNIX From the downloaded installation image. browse to the root directory and run the following command: launchpad64. a. review the information and click Install. From the Install Product panel. 7. 5. select IBM Control Desk v7. In the Installation Manager installation location panel. If any errors are reported on this panel. click Install Product. In the package features panel. The installation exits and the configuration program is started automatically. Automatically configuring middleware during deployment 23 . In the package selection panel. Select a language for the installation session and click OK. The shared resources directory is a common workspace directory used by Installation Manager when installing packages. If you run the installation program from a Linux or UNIX terminal window. Start the launchpad. Chapter 2. specify the path information for the Control Desk installation directory and click Next. Installation Manager is the installation framework that is used to install Control Desk components. 6. d. After the installation is complete. In the package installation location panel.sh. leave all default options checked and click Next. browse to the root directory and run the following command: launchpad. you might notice that the environment summary is listed as English. 10. Important: In the package selection panel. You configure supported languages later in the configuration program. c. select the process automation suite package group. resolve the issue and click Recheck Status. Log in to the Control Desk administrative workstation.6 and click Install IBM Control Desk components. Windows From the downloaded installation image. click Next. In the package prerequisite validation panel. 3. select the option to start the configuration program and click Finish. specify path information for the shared resources directory and the Installation Manager installation directory and click Next. If you install in a non-English environment. 9. Procedure 1. What to do next Use the configuration program to configure Control Desk. 2. Launch the Control Desk installation program from the launchpad. ensure that IBM Maximo for Service Providers is selected. review the results of the prerequisite check and click Next.

specify Control Desk installation location. specify information about the DB2 instance to create for Control Desk. Choose the base language and any additional languages you want to install. 10. 2. 4. In the Configure General Product Information panel. 3. Enter the user names and passwords for users that must be created for Control Desk. specify information about the DB2 database to create for Control Desk. Start the configuration program from the Control Desk launchpad. in this example. review summary details about the product components that you are installing. 7. click Configure a New Deployment. Click Finish. Select Create and configure the database to automatically configure WebSphere Application Server Network Deployment and DB2. In the Configure the DB2 Instance panel. 6. add an email address to receive workflow messages. 24 IBM Control Desk: Installation Guide (IBM WebSphere) . Specify the appearance and navigation features for your product. Do not use the user name as a password value. 5. DB2 and WebSphere Application Server Network Deployment servers that you installed and prepared. In the Configure the DB2 Database panel. In the Configure Application Security panel. and choose whether or not to deploy sample data. In the Control Desk configuration operations page. choose a security model for Control Desk. indicate whether you want to store JMS messages that originate from the integration adapter. Results Control Desk is installed and configured to use WebSphere Application Server Network Deployment and DB2. specify information for the WebSphere Application Server Network Deployment server that you installed. Procedure 1. In the Configure the Application Server panel. select all available deployment operations and click Finish. specify information about the your database and application server. If you choose a security model that includes a directory server. 9. If you chose to persist messages. and click Launch the Tivoli’s Process Automation Suite configuration program. specify information about the directory for the virtual member manager. 8. click Configure Product. In the Apply Deployment Operations panel. In the launchpad navigation pane. In the Define Deployment Environment panel.

© Copyright IBM Corp. In this scenario. Changing the name or domain of the certificate authority at any point invalidates certificates previously issued from that authority. Use the middleware that is already established in your enterprise. About this task This is a high-level overview of tasks that you must complete to deploy Control Desk automatically.Chapter 3. If you plan to use a directory server for Control Desk authentication and authorization. you do not need configure SSL for a directory server. Ensure that you have host name resolution setup properly in your environment. Communication failures occur if the system hosting Microsoft Active Directory cannot resolve host names for systems that have been issued certificates. The configuration program is used to automatically configure an existing DB2 and IBM WebSphere Application Server server in your environment. use the configuration program to automatically configure existing middleware resources. You must enable SSL for Microsoft Active Directory. Automatically configuring existing middleware during deployment Use the configuration program to automatically configure existing middleware within your enterprise for use with Control Desk. and then add that certificate to WebSphere Application Server Network Deployment. you also want the configuration program to automatically create users in Microsoft Active Directory. If you plan to use Control Desk application security for authentication and authorization. About this task This procedure is only required if you choose to allow the configuration program to automatically configure WebSphere Application Server Network Deployment. you must configure SSL communication between Microsoft Active Directory and WebSphere Application Server Network Deployment using the configuration program. generate a certificate. users and groups must be created in the directory. 2015 25 . Deploying Control Desk reusing existing middleware Configuring SSL between Microsoft Active Directory and WebSphere Application Server Network Deployment To enable the configuration program to automatically create users and groups within Microsoft Active Directory. Figure 2. Then.

If you run the installation program from a Linux or UNIX terminal window. Select the option to automate the configuration of IBM HTTP Server. Start the configuration program from the Control Desk launchpad. Launch the Control Desk installation program from the launchpad. browse to the root directory and run the following command: launchpad64. Procedure 1. credentials and directory structure from the Configure Administrative Security panel.5 using the configuration program Use the configuration program to prepare WebSphere Application Server Network Deployment v8. click Prepare WebSphere Application Server Network Deployment for configuration. a. 6. Log in to the Control Desk administrative workstation.Preparing WebSphere Application Server Network Deployment v8. specify the installation location and configuration information for WebSphere Application Server Network Deployment and associated components.5 for Control Desk configuration. 3. 7. 4. In the Configure Application Server Profiles panel. 26 IBM Control Desk: Installation Guide (IBM WebSphere) . In the launchpad navigation pane. If you chose to use a directory server for WebSphere Application Server Network Deployment administrative security. run the installation program on the Control Desk administrative system. Procedure 1. In the Apply Deployment Operations panel. Results WebSphere Application Server Network Deployment v8.exe. Windows From the downloaded installation image. specify information about the directory server host. 2. if required. About this task To install Control Desk. In the Configure the Application for WebSphere panel. Installing Control Desk Install Control Desk.5 is ready for Control Desk. you must be logged in as the root user. specify additional configuration information. In the Control Desk configuration operations page. 5. select all deployment operation options and click Finish. 2. specify information to use to create the WebSphere Application Server Network Deployment deployment manager and application server profiles. Optional: In the Configure Application Server Advanced Options panel. Start the launchpad. click Configure Product and click Launch the Tivoli’s Process Automation Suite configuration program.

Linux and UNIX
From the downloaded installation image, browse to the root
directory and run the following command: launchpad.sh.
b. Select a language for the installation session and click OK.
c. In the launchpad navigation pane, click Install Product.
d. From the Install Product panel, select IBM Control Desk v7.6 and click
Install IBM Control Desk components.
3. In the package selection panel, click Next.

Important: In the package selection panel, ensure that IBM Maximo for
Service Providers is selected. This package is required for the complete
installation of Control Desk including the advanced edition.
4. In the package prerequisite validation panel, review the results of the
prerequisite check and click Next. If any errors are reported on this panel,
resolve the issue and click Recheck Status.
5. In the license agreement panel, accept the license agreement and click Next.
6. In the Installation Manager installation location panel, specify path
information for the shared resources directory and the Installation Manager
installation directory and click Next. Installation Manager is the installation
framework that is used to install Control Desk components. The shared
resources directory is a common workspace directory used by Installation
Manager when installing packages.
7. In the package installation location panel, select the process automation suite
package group, specify the path information for the Control Desk installation
directory and click Next.
8. In the package features panel, leave all default options checked and click
Next.
9. In the package summary panel, review the information and click Install. If
you install in a non-English environment, you might notice that the
environment summary is listed as English. You configure supported languages
later in the configuration program.
10. After the installation is complete, select the option to start the configuration
program and click Finish. The installation exits and the configuration program
is started automatically.

What to do next

Use the configuration program to configure Control Desk.

Configuring Control Desk
Configure Control Desk.

Procedure
1. Start the configuration program from the Control Desk launchpad. In the
launchpad navigation pane, click Configure Product, specify Control Desk
installation location, and click Launch the Tivoli’s Process Automation Suite
configuration program.
2. In the Control Desk configuration operations page, click Configure a New
Deployment.
3. In the Define Deployment Environment panel, specify information about the
your database and application server, in this example, DB2 and WebSphere

Chapter 3. Automatically configuring existing middleware during deployment 27

Application Server Network Deployment servers that you installed and
prepared. Select Create and configure the database to automatically configure
WebSphere Application Server Network Deployment and DB2. Click Finish.
4. In the Configure General Product Information panel, review summary details
about the product components that you are installing. Specify the appearance
and navigation features for your product, add an email address to receive
workflow messages, and choose whether or not to deploy sample data.
5. In the Configure the DB2 Instance panel, specify information about the DB2
instance to create for Control Desk.
6. In the Configure the DB2 Database panel, specify information about the DB2
database to create for Control Desk.
7. In the Configure the Application Server panel, specify information for the
WebSphere Application Server Network Deployment server that you installed.
If you chose to persist messages, indicate whether you want to store JMS
messages that originate from the integration adapter.
8. In the Configure Application Security panel, choose a security model for
Control Desk. If you choose a security model that includes a directory server,
specify information about the directory for the virtual member manager. Enter
the user names and passwords for users that must be created for Control
Desk. Do not use the user name as a password value.
9. Choose the base language and any additional languages you want to install.
10. In the Apply Deployment Operations panel, select all available deployment
operations and click Finish.

Results

Control Desk is installed and configured to use WebSphere Application Server
Network Deployment and DB2.

28 IBM Control Desk: Installation Guide (IBM WebSphere)

Chapter 4. Manually configuring existing middleware during
deployment
You can deploy Control Desk by reusing existing middleware servers and
manually configuring them.

There are a number of tasks that you need to complete to deploy Control Desk
automatically, using middleware already established in your enterprise.

In this scenario, you manually configure existing middleware resources before
running the configuration program.

Installing Control Desk with manual middleware configuration
Manually configure middleware components, the database server, the directory
server, and the J2EE server before you use the Control Desk installation and
configuration programs.

You can automatically configure Control Desk middleware components with the
configuration program. Alternatively, you can manually configure middleware
servers to work with Control Desk before you run the Control Desk installation
and configuration programs.

Before you begin, ensure that the following prerequisite conditions are met:
v You designate a Windows or UNIX server to start the Control Desk
configuration program.
v For WebSphere Application Server Network Deployment, ensure that the Cell
and all related nodes are active.

You must complete the manual configuration of each middleware server before
you use the configuration program to configure Control Desk to work with the
servers.

Ensure that your middleware is supported.

Manually configuring the database
You can manually configure the database server that is used with Control Desk.
You must manually configure the database server before you use the Control Desk
installation and configuration programs.

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

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

Manually configuring DB2 v10.5
Manually configuring DB2 v10.5 servers for use by Control Desk.

© Copyright IBM Corp. 2015 29

About this task

To configure an existing DB2 v10.5 server for use with Control Desk, complete the
following steps before you start the Control Desk installation and configuration
programs:

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 db2iadm1 as its primary group.
3. Open a console window and set up the DB2 environment:
v Windows
db2cmd
v Linux or UNIX
Ensure that the /opt/ibm/db2/V10.5/bin, /opt/ibm/db2/v10.5/instance, and
/opt/ibm/db2/V10.5/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 ctgfenc1 -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 ’maxdb76’ ALIAS ’maxdb76’ using codeset UTF-8 territory US pagesize 32 K
db2 connect to ’maxdb76’
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 maxdb76 using SELF_TUNING_MEM ON
db2 update db cfg for maxdb76 using APPGROUP_MEM_SZ 16384 DEFERRED
db2 update db cfg for maxdb76 using APPLHEAPSZ 2048 AUTOMATIC DEFERRED
db2 update db cfg for maxdb76 using AUTO_MAINT ON DEFERRED
db2 update db cfg for maxdb76 using AUTO_TBL_MAINT ON DEFERRED
db2 update db cfg for maxdb76 using AUTO_RUNSTATS ON DEFERRED
db2 update db cfg for maxdb76 using AUTO_REORG ON DEFERRED
db2 update db cfg for maxdb76 using AUTO_DB_BACKUP ON DEFERRED
db2 update db cfg for maxdb76 using CATALOGCACHE_SZ 800 DEFERRED
db2 update db cfg for maxdb76 using CHNGPGS_THRESH 40 DEFERRED
db2 update db cfg for maxdb76 using DBHEAP AUTOMATIC
db2 update db cfg for maxdb76 using LOCKLIST AUTOMATIC DEFERRED
db2 update db cfg for maxdb76 using LOGBUFSZ 1024 DEFERRED
db2 update db cfg for maxdb76 using LOCKTIMEOUT 300 DEFERRED
db2 update db cfg for maxdb76 using LOGPRIMARY 20 DEFERRED
db2 update db cfg for maxdb76 using LOGSECOND 100 DEFERRED
db2 update db cfg for maxdb76 using LOGFILSIZ 8192 DEFERRED
db2 update db cfg for maxdb76 using SOFTMAX 1000 DEFERRED
db2 update db cfg for maxdb76 using MAXFILOP 32768 DEFERRED #32-bit Windows
db2 update db cfg for maxdb76 using MAXFILOP 65335 DEFERRED #64-bit Windows
db2 update db cfg for maxdb76 using MAXFILOP 30720 DEFERRED #32-bit UNIX

30 IBM Control Desk: Installation Guide (IBM WebSphere)

the schema owner must use the same user ID as the database user.CREATE_EXTERNAL_ROUTINE.IMPLICIT_SCHEMA. Chapter 4. db2 connect reset 15.DROPIN. Failure to do so can potentially cause the Control Desk installation to fail. Reconnect to the database.ctginst1 db2 8. Grant authority to maximo. 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 CREATE REGULAR TABLESPACE MAXINDEX PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE INITIALSIZE 5000 M BUFFERPOOL MAXBUFPOOL db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO 12. Manually configuring existing middleware during deployment 31 . Create a buffer pool. Manually configuring Oracle 12c You can manually configure Oracle 12c for use with Control Desk.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.tb_reorg_req SET THRESHOLDSCHECKED YES db2 update alert cfg for database on maxdb76 using db. Create Schema db2 create schema maximo authorization maximo 13.CREATETAB. su . Install the appropriate fix pack that is indicated in the prerequisites topic in the chapter that describes how to prepare for the installation. db2stop force db2start 9. For Linux orUNIX.ALTERIN ON SCHEMA MAXIMO TO USER MAXIMO 14. db2 connect to ’maxdb76’ 10. db2 update db cfg for maxdb76 using MAXFILOP 61440 DEFERRED #64-bit UNIX db2 update db cfg for maxdb76 using PCKCACHESZ AUTOMATIC DEFERRED db2 update db cfg for maxdb76 using STAT_HEAP_SZ AUTOMATIC DEFERRED db2 update db cfg for maxdb76 using STMTHEAP AUTOMATIC DEFERRED db2 update db cfg for maxdb76 using UTIL_HEAP_SZ 10000 DEFERRED db2 update db cfg for maxdb76 using DATABASE_MEMORY AUTOMATIC DEFERRED db2 update db cfg for maxdb76 using AUTO_STMT_STATS OFF DEFERRED db2 update db cfg for maxdb76 using STMT_CONC LITERALS DEFERRED db2 update alert cfg for database on maxdb76 using db. Restart DB2.CREATE_NOT_FENCED_ROUTINE. and then restart the DB2 command-line environment.CONNECT. Ensure that you review and complete all the installation and postinstallation tasks that are contained within the fix pack readme file.QUIESCE_CONNECT. Break the database connection.BINDADD. For Oracle databases. Before you begin Oracle instance names must be limited to 8 characters. db2 CREATE BUFFERPOOL MAXBUFPOOL IMMEDIATE SIZE 4096 AUTOMATIC PAGESIZE 32 K 11. db2 GRANT DBADM. Exit the DB2 command-line environment 16. Create table spaces.SECADM ON DATABASE TO USER MAXIMO db2 GRANT USE OF TABLESPACE MAXDATA TO USER MAXIMO db2 GRANT CREATEIN. LOAD.db_backup_req SET THRESHOLDSCHECKED YES db2 update alert cfg for database on maxdb76 using db. log into the system as the ctginst1 user.

g. Accept the default Selected Protocols that are listed by clicking Next. f. Select Advanced Mode and click Next. Open the Oracle Database Configuration Assistant. complete the following steps before you start the Control Desk installation program: Procedure 1. c. h. select Use the standard port of 1521 and click Next. Ensure Use Database File Locations from Template is selected as the value to use for database file location. e. b. Open the Oracle Network Configuration Assistant application. Enter ctginst1 for both the Global Database Name value and the SID value and click Next. e. 3. a. Shared Pool Set this value to 541. leave defaults selected for the database recovery options. About this task To configure an existing Oracle 12c server for use with Control Desk. Leave the defaults selected and click Next. 32 IBM Control Desk: Installation Guide (IBM WebSphere) . select Add and click Next. From the port panel. k. From the Listener Configuration Done panel. Select General Purpose or Transaction Processing and click Next. Select Create Database and click Next. select Custom Settings and provide the following values (measured in Mb): Memory Management Set this value to Manual Shared Memory Management. Large Pool Set this value to 8. Leave the defaults selected and click Next. Java Pool Set this value to 32. Typically this user is named oracle. 2. Ensure Use the Same Administrative Password for All Accounts is selected. i. f. Buffer Cache Set this value to 36. click Next. b. select Listener configurationand click Next. Click Finish. Create the database listener if it does not exist. Create a database for use by Control Desk. d. d. i. h. c. a. Log in as the Oracle software user. Select No to indicate that you are finished configuring listeners and click Next. j. and click Next. Enter a name for the listener or accept the default value and click Next. The listener manages requests to connect to the database. on the Memory tab. Ensure File System is selected as the storage type to use for the database. From the action panel. From the Initialization Parameters panel. From the Sample Schemas panel. enter a password for Oracle users and click Next. click Next. g. From the Welcome panel.

open_cursors Change this value to 3000. Click Exit to exit the Database Configuration Assistant.1\db_1\dbs\maxdata.0. p.1.1. grant alter session to maximo. Manually configuring existing middleware during deployment 33 . 5. click Next. Note: The Oracle Database Configuration Assistant starts the ORACLE_HOME/ctx/admin/defaults/drdefus. n. Click Show Advanced Parameters. o. From the Creation Options panel. Click All Initialization Parameters. Create a temporary table space with the following command in SQL*Plus create temporary tablespace maxtemp tempfile ’C:\oracle\product\12. grant create sequence to maximo. 4. grant connect to maximo. cursor_sharing Set this value to FORCE. nls_length_semantics Change this value to CHAR. grant create trigger to maximo. grant execute on ctxsys. Create a table space with the following command in SQL*Plus: Create tablespace maxdata datafile ’C:\oracle\product\12. grant create synonym to maximo. select Use Unicode (AL32UTF8). click Finish. r. alter user maximo quota unlimited on maxdata. PGA Size Set this value to 36. l. s. 6.. this command fails. From the Initialization Parameters panel.0.. Locate the following parameters. click Next. grant create table to maximo.ctx_ddl to maximo. this command fails. If the directory does not exist. change them to the values indicated. grant create session to maximo. Change the directory that is specified in the example to the database location. grant create procedure to maximo. You must start this script manually if you do not use the Oracle Database Configuration Assistant. and then click Close. Create the maximo user and grant permissions with the following command in SQL*Plus: create user maximo identified by maximo default tablespace maxdata temporary tablespace maxtemp. From the Summary panel. grant create job to maximo. Change the directory that is specified in the example to the database location. grant create view to maximo. The database is successfully created.dbf’ size 1000M autoextend on maxsize unlimited. From the Character Sets tab.. Chapter 4. q. If the directory does not exist.sql script as part of the configuration of the CTXSYS user. m.1\db_1\dbs\maxtemp.dbf’ size 1000M autoextend on.

e. Use the following command if you created a separate table space for indexing called TSI_MAM_OWN. c. you must also grant access to that index table space to the maximo user. A database instance does not support both Portuguese and Chinese because they have different character sets. configure the Database Engine to listen on a specific port. About this task To configure an existing Microsoft SQL Server for use with Control Desk. you must explicitly grant that role to the maximo user.": alter user maximo quota unlimited on TSI_MAM_OWN What to do next If you modified default role sets assigned to the user ID used to connect to the database. From the Microsoft SQL Server Configuration Manager navigation pane. French. multilingual support is limited. For example. you must explicitly grant them to the maximo user. If the TCP Dynamic Ports field contains a value of 0. For each IP address listed. Click OK. that IP address is using dynamic ports. Before you begin Because Microsoft SQL Server does not support UTF-8. if you do not grant a role such as the select_catalog_role role. When you connect to a named instance across a firewall. If you created a separate table space for indexing. or restricted the default privileges that are granted to user IDs. Configure the listener port. Since Control Desk requires Microsoft SQL Server to listen on a static port. this field must be blank. which means they select any available port when the service starts. Named instances of the Microsoft SQL Server Database Engine and Microsoft SQL Server Compact Edition are configured for dynamic ports. You can support multiple languages in one database instance only if they share the same character set. a database instance supports English. complete the following steps before you start the Control Desk installation and configuration programs: Procedure 1. For example. f. For each IP address listed. click the IP Addresses tab. If The default instance of the Microsoft SQL Server Database Engine listens on TCP port 1433. 34 IBM Control Desk: Installation Guide (IBM WebSphere) . to open this port in the firewall. Open Programs > Microsoft SQL Server 2012 > Configuration Tools > SQL Server Configuration Manager b. and Portuguese because they use the same character set. ensure that the TCP Dynamic Ports field is blank. d. In the TCP/IP Properties dialog box. a. This assignment can be done by running this SQL*Plus command: grant select_catalog_role to maximo Manually configuring Microsoft SQL Server 2012 You can manually configure Microsoft SQL Server for use with Control Desk. expand SQL Server Network Configuration > Protocols for <instance name>. enter 1433 for the TCP Port field. and double-click TCP/IP.

Right-click the databases folder from the navigation tree and select New Database. c. Verify that you enabled the Full-text Search setting during the installation of Microsoft SQL Server 2012. Type the following command and then click Execute. specify a unique database name. Click Execute. Right-click SQL Server (<instance name>) and click Restart. 4. Navigate through the wizard and enable the Full-Text Search option that is on the Custom portion of the Setup Type dialog box. Right-click the maxdb76 database and select New Query. c. restart the server. Chapter 4. Enter the following script to create the Maximo database user MAXIMO with a password that adheres to the password policy of the system. sp_addlogin MAXIMO. f. Open SQL Server Management Studio. enter maxdb76 d. 2. insert the Microsoft SQL Server 2012 product media into the system and start the installation wizard. Modify the log settings to accommodate your production environment. f. to stop. h. sp_changedbowner MAXIMO go g. Open SQL Server Management Studio (Start > Programs > Microsoft SQL Server 2012 > SQL Server Management Studio) b. select SQL Server Authentication as the authentication type. complete the following steps: a. Click Execute. and restart Microsoft SQL Server. In the database name entry field. and then close SQL Server Configuration Manager. 3. Create the Maximo User for Microsoft SQL Server. a. Open Microsoft SQL Server Management Studio (Start > Programs > Microsoft SQL Server 2012 > SQL Server Management Studio) b. i. Create a Microsoft SQL Server database. Manually configuring existing middleware during deployment 35 . b. For the maxdb76 Logical Name. c. change the Initial Size (MB) attribute to 500 (MB). Click New Query. d. and enter the credentials for the sa user ID. and then click Connect. From the SQL Server Configuration Manager navigation pane. g. a. and also set the value of the Autogrowth / Maxsize field to By 1 MB. Click OK. Unlimited. click Databases. Enter the following script to change the database owner to maximo. From the SQL Server Configuration Manager navigation pane. To determine if Full-text Search is installed on your existing Microsoft SQL Server database. Verify the Microsoft SQL Server instance is running. click SQL Server Services. e. e. For example. To finish the installation process. To install Full-text Search.: select FULLTEXTSERVICEPROPERTY ( ’IsFulltextInstalled’ ) If you did not install Full-text Search (the resulting value is zero).password go This value is case-sensitive. you must do so now.

Manually configuring IBM Security Directory Server Manually configure IBM Security Directory Server for use with Control Desk.DataFilegroupName=your_logical_name 3. Many directory server products consider a blank space as a special character that is part of the LDAP string. Manually configuring the directory server You can manually configure a directory server for Control Desk to manage authentication and authorization. for example. Add the following property to the install_home\etc\install. bind user. Run the configuration tool to complete the deployment. About this task If you choose the option to configure WebSphere Application Server Network Deployment automatically with the configuration program. If want to use a directory server to secure Control Desk.properties file: Database. Note: The base dn. complete these steps after you set up the database and create the Maximo user: 1. or values you enter directly into a directory instance with directory server tools. 36 IBM Control Desk: Installation Guide (IBM WebSphere) . There are several methods to secure Control Desk. special characters must be preceded by an escape character to make it readable by the directory server. Complete these additional steps only if you added logical names to the database and set their file group to a value other than PRIMARY. be aware of the product-specific syntax rules for using special characters in an LDAP string. For more information about special characters in LDAP strings. Run the Control Desk installation program and choose the Do not run the configuration step now option. at the end of a field value. and you do not precede the blank character with an escape character. If you do not want the configuration program to configure WebSphere Application Server Network Deployment. These values are replaced with values applicable to existing LDAP hierarchies within your organization. 2. and other various node values that are listed are default values.SQL. you must create users manually. What to do next If you add logical names to the database and set their file group to a value other than PRIMARY. see the product documentation for your directory server. If you mistakenly enter an LDAP string that contains a blank. entries in LDIF files. you can create these users and groups automatically. In most cases. you must complete the manual configuration of the directory server before you use the Control Desk installation and configuration programs. Important: When you enter LDAP values for Control Desk configuration panel fields. Failing to escape special characters that are contained in an LDAP string that is used with Control Desk results in Control Desk errors. you encounter Control Desk errors that are difficult to troubleshoot.

separate instances are created for use by Control Desk and IBM Security Directory Server. ensure that you are logged in as an administrator on the system and start the tool. Encryption seed string Type a string of characters that are used as an encryption seed. Note: While you can technically share a DB2 instance between Control Desk and the one needed by IBM Security Directory Server. you must create an instance of IBM Security Directory Server. This name is also the name of the instance. the database instance is restarted.3 > Instance Administration Tool. enter values for the following fields and click Next. This value must be a minimum of 12 characters. Windows Create the user db2admin and make it a member of the following groups: 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. and dbsysadm groups. Install location Enter the location where the instance files are stored. Chapter 4. click Create an instance. Using your preferred method. UNIX Type /opt/IBM/ldap/V6.To configure IBM Security Directory Server before you start the Control Desk installation and configuration programs. Instance description Enter a brief description of the instance. Manually configuring existing middleware during deployment 37 . Procedure 1.3/sbin/idsxinst at the command line. 2. User name Select idsccmdb as the system user ID of the user who owns the instance. From the Instance details window. idsldap. it might lead to problems. If you are using the automated installation programs. Windows Select Programs > IBM Tivoli Directory Server 6. 5. During the installation. which might disrupt the availability of IBM Security Directory Server to your enterprise. In the Create a new instance window. If the Instance Administration tool is not already started. 3. click Create a new directory server instance and click Next. create a user on the system and assign it to the appropriate group. 4. In the Instance Administration tool.

From the Configure database panel. Administrator DN Enter cn=root for the administrator distinguished name. Database install location Type the location for the database. Configure admin DN and password To configure the administrator DN and password for the instance. 11. Administrator Password Enter a password for the Administrator DN. Server port number Enter 389 as the contact port for the server. In the TCP/IP settings for multihomed hosts panel. Database user name Enter idsccmdb as the database user. In the TCP/IP port settings panel. 8. enter idsccmdb as the value for the DB2 instance name field and click Next. leave the following options selected and click Next. such as /home/ldapdb. Ensure that you have at least 80 MB of free hard disk space in the location you specify. Admin daemon secure port number Enter 3539 as the administration daemon secure port. Database name Enter idsccmdb as the database to be used with this directory instance. 12. 38 IBM Control Desk: Installation Guide (IBM WebSphere) . Admin daemon port number Enter 3538 as the administration daemon port. Character-set option Leave the Create a universal DB2 database (UTF-8/UCS-2) option selected. In the Option steps panel. 7. UNIX For non-Windows systems. In the DB2 instance details panel. complete the following fields and click Next. 6. In the Database options panel. Server secure port number Enter 636 as the secure port for the server. In the Configure administrator DN and password panel. the location must be a directory name. complete the following fields and click Next. select Listen on all configured IP addresses and click Next. 10. 9. complete the following fields and click Next. complete the following fields and click Next. Windows For Windows platforms. Configure database To configure the database for the directory server. Password Enter the password for the idsccmdb user. More disk space must be available to accommodate growth as new entries are added to the directory. this value must be a drive letter.

Add the DN information. In the Verify settings panel.ou=SWG.com®. Click Close to close the window and return to the main window of the Instance Administration tool. 17.c=US 19. is an organization unit called SWG. o=IBM. create the following users in the root of your LDAP repository: Table 4.c=us ou: users objectClass: top Chapter 4. Manually configuring existing middleware during deployment 39 .3 > Instance Administration Tool. 14. o=ibm. 18.o=IBM. You can replace the example with the directory structure of your own organization.c=us objectClass: top objectClass: organization o: IBM dn: ou=SWG.c=US. type the following suffix and click Add. These users are defined for Virtual Member Manager to be used to secure Control Desk. 15. 20. Base Control Desk users User wasadmin maxadmin mxintadm maxreg Here is an example of the default base LDIF data: dn: o=ibm. SWG houses the OU=Users organization units to place the users that are created for Control Desk.c=us ou: SWG objectClass: top objectClass: organizationalUnit dn: ou=users.3/sbin/idsxcfg at the command line. Select Manage suffixes. for example: v ou=SWG. DC=IBM and DC=COM indicate a domain forest of ibm. Start the IBM Security Directory Server Configuration tool: Windows SelectPrograms > IBM Tivoli Directory Server 6./opt/IBM/ldap/V6. Important: Before you begin this procedure.13. Click Close to exit the Instance Administration tool. Click OK. o=ibm.o=IBM. Define the following users and their positions within the ou=users DNs that you created. In the Manage suffixes panel. ou=SWG. 16.c=US v ou=users Note: The example. Create and save an LDIF file. UNIX Type . review the instance creation details that are provided and click Finish to create the idsccmdb instance.

Click Import. o=ibm. o=ibm. you must run the dos2unix command to format the file.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.ou=SWG. If you choose the option to configure WebSphere Application Server Network Deployment automatically with the configuration program. Note: Before you can import an LDIF file on UNIX systems. Click Browse to locate the LDIF file. o=ibm. ensure that you remove the ^M characters from the file before you use it. 21.ou=SWG.c=us uid: wasadmin userpassword: wasadmin objectclass: organizationalPerson objectclass: inetOrgPerson objectclass: person objectclass: top title: WebSphere Administrator sn: wasadmin cn: wasadmin dn: uid=maxadmin. click Import LDIF data. o=ibm. 22. then you can create these users and groups automatically. In the IBM Security Directory Server Configuration tool. Close the IBM Security Directory Server Configuration tool and restart the server.ou=users.ou=SWG. If you do not want the 40 IBM Control Desk: Installation Guide (IBM WebSphere) .c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg. 24.ou=users. 23.c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin dn: uid=mxintadm. Before you begin Manually configure Microsoft Active Directory for authorization and authentication within Control Desk.ou=users.ou=SWG. objectClass: organizationalUnit dn: cn=wasadmin. Manually configuring Microsoft Active Directory You can manually configure Microsoft Active Directory for use with Control Desk.ou=users.

In the Roles list. e.swg. clear the Domain Name System (DNS) server option. g. a. Restart the server Chapter 4. j. select Active Directory Domain Services. Accept the default paths for AD DS database. e. b. you must create users manually. and SYSVOL. Promote the server to a Domain Controller. From the All Servers Task Details and Notifications page. Click AD DS in the dashboard. click Next. Start the Server Manager. From the Select Features page. click the Promote this server to a domain controller action. From the Before You Begin page. you can change these default passwords to conform to a stricter security policy. Click Next. c. g. h. i. and provide a password for Directory Services Restore Mode (DSRM). log files.usma. Add the Active Directory Domain Services role. It is sometimes necessary to temporarily alter theMicrosoft Active Directory security policy to create these accounts in the required format. Click Close and restart the server. Specify the root domain name with a unique fully qualified domain name.configuration program to configure WebSphere Application Server Network Deployment.com and click Next f. From the Deployment Configuration page. for example. a.ibm. click Next and click Install. After installation. Accept the default NetBIOS name and click Next. Click Next f. Complete the following steps Procedure 1. 2. For Installation Type. Click Add roles and features. configure Microsoft Active Directory. qawin01ldap. click Install. About this task Before you start theControl Desk installation and configuration programs. d. Creating users automatically requires SSL communication between Microsoft Active Directory and WebSphere Application Server Network Deployment. accept the defaults and click Next. Start the Server Manager. Review the summary. b. select Role-based or feature-based installation and click Next. j. Click Next. Select the Select a server from the server pool option and choose your local server from the Server Pool list. Click Add Features and Next. c. From the Domain Controller Options page. On the confirmation page. select Add a new forest. d. Click the Configuration required for Active Directory Domain Services warning indicator. i. Important: The users and passwords you create in the following steps must match this exact configuration for the deployment to succeed. h. Manually configuring existing middleware during deployment 41 .

q. Select your server. h. Specify maxadmin as the First name and User logon name. a. right-click. click Add. Click Apply and OK. 3. Manually configuring WebSphere Application Server Network Deployment You can manually configure an existing WebSphere Application Server Network Deployment for use by Control Desk. Control Desk requires Java 7. e. users and click OK. What to do next Microsoft Active Directory configuration is finished and you are now ready to configure the J2EE server to use Microsoft Active Directory. Right-click the maximousers group and select Properties. i. o. f. k. You must complete the manual configuration before you use the configuration program. for example. Create two more users who are named mxintadm and maxreg. Click Next. c. Manually configuring the J2EE server Manually configuring an existing J2EE server for use by Control Desk. in this example. Java 7 must be installed and configured on the J2EE server that you want to use with Control Desk. right-click. j. and choose New > Organizational Unit. SWG. Select Control Panel > Administrative Tools > Active Directory Users and Computers. Right-click the groups organizational unit and select and choose New > Group l. Provide a password for maxadmin. m. and choose New > Organizational Unit. SWG. Click Next and then Finish. On the Members tab. b. Add the mxintadm and maxreg users to the maximousers group. you must include the domain that you specified with your login credentials. Specify a name for the organizational unit. and then click OK. In this example. The maxadmin user is now a member of the maximousers Members list. users. and groups for Control Desk. g. a QAWIN01LDAP domain was created. 42 IBM Control Desk: Installation Guide (IBM WebSphere) . for example. Create containers. Create a user who is called maxadmin. Select the new organizational unit that is located under your server. You must manually configure the J2EE server if you choose to deploy Control DeskWebSphere Application Server Network Deployment and you choose to not have the configuration program automatically configure it. p. Specify a name for the organizational unit. Type maxadmin in the Enter the object names to select field and click OK. Name the group maximousers and click OK. Right-click the users organizational unit and click New > User. Specify QAWIN01LDAP\Administrator as the user when you log in to the system. Create another organizational unit under SWG and name it groups. d. When the system restarts. n.

WebSphere Application Server Network Deployment includes the manageprofiles command-line tool which you use to create profiles. you might have to enter commands to avoid exceeding these limitations. The value is interpreted as WC_adminhost=9060&ltsp> (where <sp> represents a space character). you must create profiles before starting the Control Desk installation. Source the setupCmdLine.[sh|bat] -delete -profileName profile name Refresh the profile registry (for example. WAS_HOME is typically in /opt/IBM/WebSphere/AppServer or C:\Program Files\IBM\WebSphere\ AppServer\. WAS_HOME/bin/manageprofiles. In some cases. but an extra space is typed after 9060. 2. See WebSphere Application Server Network Deployment product documentation for more information about entering lengthy commands on more than one line. This can sometimes occur when you cut and paste an example. Before you begin Ensure that you are familiar with the character limitations for commands or the shell you are using.[sh|bat] -listProfiles WAS_HOME is equal to where WebSphere Application Server Network Deployment is installed. for example. Manually configuring existing middleware during deployment 43 . Note: It is important that there are no spaces after any value in this file. you specify the value WC_adminhost=9060. Chapter 4.[sh|bat] after deleting a profile) -validateAndUpdateRegistry List existing profiles WAS_HOME/bin/manageprofiles. Profile commands Task Command Delete a profile WAS_HOME/bin/manageprofiles. Creating WebSphere Application Server Network Deployment profiles: When you manually install WebSphere Application Server Network Deployment. About this task The following commands can be useful for managing profiles: Table 5. /opt/IBM/WebSphere/AppServer/ or C:\Program Files\IBM\WebSphere\AppServer\ To create WebSphere Application Server Network Deployment profiles. follow these steps: Procedure 1. Create a profile ports file for the ctgDmgr01 profile.You must manually configure WebSphere Application Server Network Deployment before you use the configuration program if you do not want the configuration program to configure it automatically. For example. This file is used with the manageprofiles command to set the ports used by this profile. WebSphere uses that space as the last character of that value. If there is an extra space trailing any of the values.[sh|bat] script in the bin directory of the WAS_HOME folder to set the WebSphere Application Server Network Deployment environment to the configuration instance.

3. List available Java JDKs to ensure Java 7 is installed on the system. This file is used by the manageprofiles command to set the ports that are used by this profile. Open a new text file named _portdef_AppSvr. List the version of Java associated with ctgDmgr01.[sh|bat] -create -templatePath WAS_HOME/profileTemplates/dmgr -hostName yourfullyqualifiedhost -profileName ctgDmgr01 -profilePath WAS_HOME/profiles/ctgDmgr01 -portsFile WAS_HOME/_portdef_DMgr.7_32 -enableServers 5.[sh|bat] -listEnabledProfile -profileName ctgDmgr01 -verbose c. 44 IBM Control Desk: Installation Guide (IBM WebSphere) . a.[sh|bat] -listAvailable -verbose b. Place the file in the WAS_HOME directory.props -cellName ctgCell01 -nodeName ctgCellManager01 -enableAdminSecurity "false" 4. Create a profile ports file for the ctgAppSrv01 profile. Create the ctgDmgr01 profile using the manageprofiles command.[sh|bat] 6. WAS_HOME/bin/managesdk. If required.props and enter the following text: CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9201 DCS_UNICAST_ADDRESS=9353 NODE_DISCOVERY_ADDRESS=7272 NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS=5001 BOOTSTRAP_ADDRESS=2809 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9901 SOAP_CONNECTOR_ADDRESS=8878 NODE_MULTICAST_DISCOVERY_ADDRESS=5000 ORB_LISTENER_ADDRESS=9101 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9202 b.[sh|bat] -enableProfile -profileName ctgDmgr01 -sdkName 1. Type the following command. all on one line. Open a new text file named _portdef_DMgr. Start the ctgDmgr01 server: WAS_HOME/profiles/ctgDmgr01/bin/startManager. WAS_HOME/bin>managesdk. with a space between each entry: WAS_HOME/bin/manageprofiles. enable the ctgDmgr01 profile to use Java 7.props and enter the following text: CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9403 WC_adminhost=9060 DCS_UNICAST_ADDRESS=9352 BOOTSTRAP_ADDRESS=9809 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9401 CELL_DISCOVERY_ADDRESS=7277 SOAP_CONNECTOR_ADDRESS=8879 ORB_LISTENER_ADDRESS=9100 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9402 WC_adminhost_secure=9043 b. Ensure the ctgDmgr01 profile is configured to use Java 7. a. Place the file in the WAS_HOMEdirectory. a. WAS_HOME/bin>managesdk.

WAS_HOME/profiles/ctgAppSrv01/bin/startNode. If required.[sh|bat] 11. enable the ctgAppSrv01 profile to use Java 7. Create the ctgAppSrv01 profile using the manageprofiles command: WAS_HOME/bin/manageprofiles. Manually creating a data source for the persistent store: If you chose to manually configure WebSphere Application Server Network Deployment. WAS_HOME/bin>managesdk. WAS_HOME/profiles/ctgDmgr01/firststeps/firststeps.[sh|bat] “Manually configuring Virtual Member Manager on WebSphere Application Server Network Deployment” on page 80 Some deployment environments require the manual configuration of Virtual Member Manager to secure Control Desk.html. For more information about WebSphere Application Server Network Deployment message storage. List available Java JDKs to ensure Java 7 is installed on the system.[sh|bat] 10. Chapter 4. Manually configuring existing middleware during deployment 45 . Start firststeps. List the version of Java associated with ctgAppSrv01.[sh|bat] -listAvailable -verbose b.[sh|bat] -create -templatePath WAS_HOME/profileTemplates/managed -hostName yourfullyqualifiedhost -profileName ctgAppSrv01 -profilePath WAS_HOME/profiles/ctgAppSrv01 -cellName ctgNodeCell01 -nodeName ctgNode01 -portsFile WAS_HOME/_portdef_AppSvr. WAS_HOME/profiles/ctgDmgr01/bin/stopManager.[sh|bat] WAS_HOME/profiles/ctgDmgr01/bin/startManager. you must create a data source to store JMS messages in a DB2 database.[sh|bat] -listEnabledProfile -profileName ctgAppSrv01 -verbose c. WAS_HOME/bin>managesdk.[sh|bat] WAS_HOME/profiles/ctgAppSrv01/bin/startNode.com/ support/knowledgecenter/SSLKT6/sslkt6_welcome. Start the ctgAppSrv01 node. Restart servers. Ensure the ctgAppSrv01 profile is configured to use Java 7. About this task You have the option of having WebSphere Application Server Network Deployment use a DB2 database to store JMS messages. WAS_HOME/bin/managesdk.[sh|bat] and select the Installation Verification option to confirm that your server has been properly installed and started. including the usage of products other than DB2.[sh|bat] WAS_HOME/profiles/ctgAppSrv01/bin/stopNode.[sh|bat] -enableProfile -profileName ctgAppSrv01 -sdkName 1. a.7_32 -enableServers 9. 7.props -dmgrHost yourfullyqualifiedhost -dmgrPort 8879 -isDefault 8. see http://www-01.ibm.

d. click Java Authentication and Authorization Service > J2C authentication data. Browse to Security > Global Security. j. j. 3. Create a database named maxsibdb using default settings. g. Under the Authentication header. c. Create and configure the database. c. b. Configure J2C authentication data and JDBC provider in WebSphere Application Server Network Deployment. Open and log in to the WebSphere Application Server Network Deployment administrative console. 2. and then. Description SIB database user alias. After the database has been created. i. expand the maxsibdb database and select User and Group objects. Click Apply and Save. Open DB2 Control Center. click Show scope selection drop-down list with the all scopes option. From the WebSphere Application Server administrative console. a. f. b. a user named mxsibusr with a password of mxsibusr. Click New. g. e. d. Under Scope. e. To create a data source for the persistent store. complete the following steps: Procedure 1. f. under Preferences. a. For example. click Apply. h. Grant all authorities to the mxsibusr except Security administrator authority. Specify the following values and click Apply: Database type DB2 Provider type DB2 Universal JDBC Driver Provider 46 IBM Control Desk: Installation Guide (IBM WebSphere) . Right-click the Databases folder and select Create Database > Standard. Verify that you can connect to the database using the mxsibusr user by right-clicking maxsibdb and selecting Connect. i. Click New. Create a system user and password on the server hosting the database server. Select mxsibusr from the User menu. Complete the following fields in the User identity form. browse to Resources > JDBC > JDBC Providers. select Cell=ctgCell01. Click Apply. Browse to the Databases folder listed in your system. Right-click DB Users and select Add. Alias maxJaasAlias User ID mxsibusr Password Password you created for mxsibusr. h.

Click Finish and Save. j. Click New. Click Next. Port number Specify the DB2 port number. Go back to Resources > JDBC > JDBC Providers > maxJdbcProvider. d. 4. and then click Next. To verify the data source. and correct the class path if required for both db2jcc. and then select maxJdbcProvider from the menu. l. Under Scope. Configure WebSphere Application Server: a. k. g. Click Next. select Cell=ctgCell01. h.jar and <DB2_HOME>/java/db2jcc_license_cu. 6. select maxJaasAlias f. Chapter 4. From the WebSphere Application Server Network Deployment administrative console. under Preferences.jar and db2jcc_license_cu.jar to the <WAS_HOME>\ctgMX\lib directory. Click Next. browse to Resources > JDBC > Data sources. m. select intjmsds and click Test Connection. click Apply. and then. Click Next. c. Complete the WebSphere Application Server variable ${DB2UNIVERSAL_JDBC_DRIVER_PATH} field with a value of <WAS_HOME>ctgMX\lib. Specify the following values: Database name maxsibdb Driver type 4 Server name Specify the DB2 server host name. click Show scope selection drop-down list with the all scopes option. 50005. From the Component-managed authentication alias and XA recovery authentication alias menu. i. Ensure the Use this data source in container managed persistence (CMP) option is selected. b. Open a command prompt and copy <DB2_HOME>/java/db2jcc. C:\Program Files\IBM\WebSphere\ AppServer\ctgMX\lib. Ensure that each jar file has the full path from ${DB2UNIVERSAL_JDBC_DRIVER_PATH} 5. Choose Select an existing JDBC provider. For example. For example. Implementation type XA data source Name maxJdbcProvider k. Manually configuring existing middleware during deployment 47 . n. Click Finish and Save.jar. Specify the following values: Data source name intjmsds JNDI name jdbc/intjmsds e.

f. you have to manually configure the WebSphere Application Server Network Deployment. g. c. Enter a user name to log in. Figure 3. a. The browser is redirected to a secure port (9043). Open a browser and access the administrative console: http:// server_name:9060/admin. Click Preferences. Accept default settings and click Next. b. This URL address depicts the default port number (9060) and context (admin) for the administrative console. Accept all default settings and click Next. h. Click OK. Edit JVM Memory Settings and JVM Arguments for the application server.p12 2. Click Save. Expand Servers > Server Types > WebSphere application servers. Select Synchronize changes with Nodes and click Apply. Create the MXServer application server. 48 IBM Control Desk: Installation Guide (IBM WebSphere) . Manually create the application server 4. Manually copy the keystore file from the WebSphere Application Server Network Deployment deployment manager host to a temporary directory on the Control Desk administrative system where you are installing Control Desk: WAS_HOME/profiles/ctgDmgr01/etc/trust. i. d. Click New. Click Finish. j. Performing WebSphere Application Server Network Deployment configuration tasks: Use this procedure to perform WebSphere Application Server Network Deployment configuration tasks. About this task If you elect to manually configure Control Desk middleware for use with Control Desk. Type MXServer and click Next. Procedure 1. e. 3.

Set Maximum Size to 50. From the Additional Properties group. Click Default. b. using a space between each argument: -Dsun. Click OK. c. Chapter 4. From the Server Infrastructure group. Set Minimum Size to 50. Set Maximum Size to 20. a. Click MXServer in the main window. expand the Java and Process Management link.rmi. Edit thread pool settings for the application server. f. Click Process Definition. Click WebContainer. set these values to 4096. Set Minimum Size to 5. a. Click Save in the messages box. Click Java Virtual Machine. b. 5. Set Minimum Size to 20. Click MXServer from the WebSphere application servers panel. Set Maximum Size to 50. Click OK. Set Thread inactivity timeout to 30000. d.dgc. Click OK. e.net. Set Thread inactivity timeout to 30000. Click OK.DCS.preferIPv4Stack=true # for Windows -Xdisableexplicitgc -Xgcpolicy:gencon -Xmn1024m # Xmn1024m for 64-bit JVM -Xlp64k # AIX Figure 4. click Thread pools. Manually configuring existing middleware during deployment 49 . Manually create the application server g. Enter the following values in the Generic JVM arguments field. e. h. d. c. For Initial Heap Size and Maximum Heap Size.ackTimeout=10000 -Djava. Set Thread inactivity timeout to 5000. Click TCPChannel.

d. click Deployment manager. e. Click Process Definition. c. expand the Java and Process Management link. From the Server Infrastructure group. 50 IBM Control Desk: Installation Guide (IBM WebSphere) . Scroll down and type 1024 for Initial Heap Size and 1024 for Maximum Heap Size and click OK. Edit JVM Memory Settings for the deployment manager. From System administration. Edit thread pool settings for the application server 6. b. Click Java Virtual Machine.Figure 5. a.

Open the Web Container Settings and click Web container transport chains. b. a. Click Start. Click Save in the messages box. Chapter 4. From Servers > Server Types > WebSphere application servers. Start the application server. c. b. Identify the HTTP Transfer Port Numbers. 7. Edit JVM Memory Settings for the deployment manager f. c.Figure 6. 8. Manually configuring existing middleware during deployment 51 . click Application servers. Select the check box for MXServer. Expand Servers > Server Types > WebSphere application servers. Note the default port number as it appears with WCInboundDefault (9080). a. and click MXServer from the main window.

k. m. w. Click New. Create the virtual host. Type * (asterisk) for host name and type 9080 for the port number. Click New. Click OK. Click Apply. Click OK and then click Save. i. Click New. Type * (asterisk) for host name and type 9044 for the port number. Click OK. u. j. r. v. c. e. Identify the HTTP Transfer Port Numbers 9. d. s. b. p. Click the Host Aliases link. In the General Properties section. t. g. l. Click OK. type maximo_host in the Name box.Figure 7. o. Click Save. Expand Environment. Click New. x. q. f. click maximo_host. Click New. n. 52 IBM Control Desk: Installation Guide (IBM WebSphere) . Click New. Click OK. h. a. Type * (asterisk) for host name and type the HTTP port number (by default 80). From the Virtual Hosts window. Click OK. Click Virtual Hosts. Type * (asterisk) for host name and type 9061 for the port number. Type * (asterisk) for host name and type 9443 for the port number.

Set Node restart state to RUNNING and click OK. expand Java and Process Management. c. Enable automatic startup of the application server when the node agent is started. Click Monitoring Policy. Expand Servers > Server Types > WebSphere application servers. d.Figure 8. f. Click MXServer in the main window. b. Manually configuring existing middleware during deployment 53 . Create the virtual host 10. Click Save in the messages box. e. From the Server Infrastructure group. Figure 9. Enable automatic startup of the application server when the node agent is started Chapter 4. a.

Configuring the authentication service: The authentication service is used for authentication purposes when launching in context to another product that shares credentials with Control Desk. About this task Although not required. 3. you are only required to authenticate once to the server hosting the client. then the authentication service has already been configured automatically. Type the following command with no line breaks (case-sensitive). TADDM.log" -restart true 4. Procedure 1. Manually configuring authentication service: You can manually configure an authentication service on Control Desk that provides the authentication for launch in context. Before you begin If you used the middleware installation program to install and configure your middleware. Open a command prompt. 2. Change directory to <WAS_HOME>\bin. follow these steps: 54 IBM Control Desk: Installation Guide (IBM WebSphere) . Close the command prompt. Creating a Windows service for the node agent: You can create a Windows service for starting the WebSphere Application Server Network Deployment node agent. WASService -add NodeAgent -serverName nodeagent -profilePath "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01" -wasHome "C:\IBM\WebSphere\AppServer" -logRoot "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent" -logFile "C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent\ startServer. If you used the middleware installation program to install WebSphere Application Server Network Deployment v7. you must configure it manually to use this feature. provided it has the authentication client installed and shares the same directory server for authentication. you can start the node agent as a Windows service. this step has already been completed by the middleware installation program. About this task The authentication service provides launch in context from Control Desk to the user interface of another server. Under this scenario. To configure the authentication service manually. for example. If you did not use the middleware installation program to install and configure middleware.

Procedure 1.sh WAS_HOME/profiles/ctgAppSrv01/bin/startServer./stopManager. and MXServer using the correct profile names: Windows WAS_HOME/profiles/ctgAppsrv01/bin/stopServer.bat MXServer UNIX .sh -profileName ctgDmgr01 -username WebSphere Admin -password WebSphere Admin password .bat WAS_HOME/profiles/ctgDmgr01/bin/startServer.sh -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgDmgr01/bin/stopManager.sh -profileName ctgAppSrv01 -username WebSphere Admin -password WebSphere Admin password . Manually configuring existing middleware during deployment 55 .sh MXServer -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgAppSrv01/bin/stopNode. and change directory to WAS_HOME/bin.sh MXServer -profileName ctgAppSrv01 Or: WAS_HOME/profiles/ctgAppSrv01/bin/stopServer.sh MXServer 3.bat -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgAppsrv01/bin/startManager. Log on to the wsadmin shell by opening a command prompt and issuing the following command: Windows wsadmin.sh MXServer -profileName ctgAppSrv01 -username WebSphere Admin -password WebSphere Admin password ./stopNode.bat -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgDmgr01/bin/stopManager./startServer.bat MXServer -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgAppsrv01/bin/stopNode. Application Server.sh -profileName ctgDmgr01 .bat WAS_HOME/profiles/ctgAppsrv01/bin/startNode.bat -username WebSphere Admin -password WebSphere Admin Password Chapter 4./stopServer.sh -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgDmgr01/bin/startManager./startNode.sh -profileName ctgAppSrv01 . Open a command prompt on the system that hosts WebSphere Application Server Network Deployment./startManager.sh WAS_HOME/profiles/ctgAppSrv01/bin/startNode. Restart Deployment Manager. 2.

Regenerate the WebSphere Application Server Network Deployment plug-in using the following command: WAS_HOME/bin/GenPluginCfg. Identify the application manager MBean for the server that hosts the application and assign it to the appManager variable: set appManager [$AdminControl queryNames cell=myNodeCell. and application server: $AdminConfig list Cell $AdminConfig list Node $AdminConfig list Server 9. type=ApplicationManager. for example. the value would be ctgNode01. serverName.ScriptingException: WASX7280E: An application with name "authnsvc_ctges" does not exist.name myNode –webserver. and then click Save. would be MXServer. click OK. Deploy the IBMESSAuthnSvc. and then click Manage Modules.scripting. 5. Exit the wsadmin shell by typing exit. 14. exception information: com. Copy the IBMESSAuthnSvc. 11.ear {-usedefaultbindings -deployws -appname authnsvc_ctges –node (nodeName) –server serverName |[-cluster (clustername)]} If nodeName was set to the default value by the middleware installation program. Copy the regenerated WebSphere Application Server Network Deployment.name myServer When the command has completed successfully.bat –cell. 13. 6. UNIX . click authnsvc_ctges. This file is located in the Operating System\WS-ESS_6. 12.ibm. Verify that you do not already have authentication services deployed: wsadmin>$AdminApp view authnsvc_ctges This command returns an exception like the following sample exception: WASX7015E: Exception running command: "$AdminApp view authnsvc_ctges".ear file to your local system.xml from WAS_HOME\AppServer\profiles\ ctgAppSrv01\config\cells to HTTPServer_HOME\Plugins\config\webserver1.myServer 15.myNode.ear file.*] You can use the following commands to determine the current values for the cell. plugin-cfg. node.node=myNode. Restart the HTTP Server and the HTTP admin console.ws. select listtokenservice and WSFedPassiveProfile.2_GA directory. Browse to Applications > Enterprise applications.process=myServer./wsadmin. Log in to the WebSphere Application Server Network Deployment console. 56 IBM Control Desk: Installation Guide (IBM WebSphere) . wsadmin>$AdminApp install file_path/IBMESSAuthnSvc. if set to the default value supplied by the Control Desk installation program. Save the configuration: wsadmin>$AdminConfig save 8. Start the application: $AdminControl invoke $appManager startApplication authnsvc_ctges 10.sh -username WebSphere Admin -password WebSphere Admin Password 4. 16. click Apply. Highlight all entries listed in the Clusters and Server list. 7.name myNodeCell –node. you see the following message: Plugin-in configuration file generation is complete for the Web server myNodeCell.

bat -username WebSphere Admin -password WebSphere Admin password WAS_HOME\profiles\ctgDmgr01\bin\stopManager.sh -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgDmgr01/bin/startManager. 21.(sh|bat) 20.sh 26.0.ess. you must generate a new key. Stop WebSphere Application Server Network Deployment and the managed nodes: WAS_HOME/profiles/ctgAppSrv01/bin/stopNode. Manually configuring existing middleware during deployment 57 . Create an LTPA Key: wsadmin>$AdminTask createESSLTPAKeys {-password password} If the key password is ever lost. Configure the service: wsadmin>$AdminTask configureESS 22. click authnsvc_ctges.bat WAS_HOME\profiles\ctgAppSrv01\bin\startNode.server_config.sh -username WebSphere Admin -password WebSphere Admin password 18. Browse to Applications > Enterprise applications. a.ibm. 23.(sh|bat) WAS_HOME/profiles/ctgAppSrv01/bin/startNode.bat UNIX WAS_HOME/profiles/ctgAppSrv01/bin/stopNode. Copy the com. 19.security.6.*] wsadmin>$AdminControl invoke $dmgr syncActiveNodes true 25. and then click Security role to user/group mapping Chapter 4. Verify that the service is configured: wsadmin>$AdminTask isESSConfigured This command returns a value of true.bat -username WebSphere Admin -password WebSphere Admin password WAS_HOME\profiles\ctgDmgr01\bin\startManager.17. This user was specified during the TADDM installation.2.sh -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgDmgr01/bin/stopManager. Ensure all clients connecting to the service use the new export key file you generate. Log back in to the wsadmin shell.2_GA directory. Add the role called TrustClientRole to the WebSphere Application Server Network Deployment administrator user. Restart WebSphere Application Server Network Deployment and the managed nodes: WAS_HOME/profiles/ctgDmgr01/bin/startManager. Stop and restart WebSphere Application Server Network Deployment and the managed nodes: Windows WAS_HOME\profiles\ctgAppSrv01\bin\stopNode. 24.sh -username WebSphere Admin -password WebSphere Admin password WAS_HOME/profiles/ctgDmgr01/bin/stopManager. Synchronize the configuration: wsadmin>$AdminConfig save wsadmin>set dmgr [$AdminControl completeObjectName type=DeploymentManager.sh WAS_HOME/profiles/ctgAppSrv01/bin/startNode.jar file to the WAS_HOME/plugins directory on your local system. This file is located in the Operating System\WS-ESS_6.

and use importESSLTPAKeys to import the keys into the ESS configuration. Update the Authentication Service application: a. click OK again. Before you begin If you have deployed the 7. Migrating the authentication service: This section provides information you can use to migrate the authentication service.6.sh If you did not change the wsadmin user name or password when you first installed the application server.3 version of CCMDB and installed WebSphere Application Server Network Deployment using the middleware installation program./wsadmin. click OK. and then click Save. When upgrading to Control Desk 7. b. Select TrustClientRole and click Look up Users c. Make a backup of the system before you begin. This step provides added security by restricting the users that can authenticate to the authentication service to those users with the TrustClientRole role. 27. Run the following commands: $AdminApp update authnsvc_ctges app {-operation update -contents (install_path)/IBMESSAuthnSvc. 58 IBM Control Desk: Installation Guide (IBM WebSphere) .ear -usedefaultbindings -deployws} $AdminConfig save 3. Note: these steps do not provide a restore capability. Stop WebSphere Application Server Network Deployment along with all wsadmin instances. Use the >> button. Ensure WebSphere Application Server Network Deployment services and servers are running. you need to migrate to a newer version of the authentication service. 2. if you intend to continue to use the launch in context function with IBM Tivoli Application Dependency Discovery Manager. you already have a version of the authentication service deployed on the application server. follow these steps: Procedure 1. Move the WebSphere Application Server Network Deployment administrator user from the Available column to the Selected column. Windows wsadmin. b. Log on to the wsadmin shell using the following command. About this task To configure the authentication service manually. Export the LTPA Keys directly from WebSphere.5.bat UNIX . the default is wsadmin for the user and wsadmin for the password.

Returns True if authentication service is configured. Exception if a system error is encountered.0. Restart WebSphere Application Server Network Deployment. Delete the existing WAS_HOME/plugins/ com.6.2. Throws Exception if authentication service is not configured. Syntax $AdminTask isESSConfiguredLTPAKeys Action configureESS Chapter 4. a. Replace back-level authentication service configuration JAR file located in the WebSphere Application Server Network Deployment plug-ins directory with the updated JAR file. Throws Exception if a system error is encountered.ess. False if authentication service is not configured. Manually configuring existing middleware during deployment 59 . Syntax $AdminTask isESSConfigured Action isESSConfiguredLTPAKeys Purpose Checks for authentication service LTPA Key configuration. Input None. Administrative commands Action isESSConfigured Purpose Checks for authentication service configuration.jar to the WAS_HOME/plugins directory c. False if authentication service LTPA keys are not configured.server_config.4.1. These commands can help you determine the state of the currently installed authentication service. Run the following command: WAS_HOME/profiles/PROFILE/bin/osgicfginit 5.6.ess.ibm. Input None.server_config.0. Authentication service administrative commands: There are several administrative commands for the authentication service that can be used with the wsadmin tool.security. Returns True if authentication service LTPA keys are configured.jar b. Copy the new com.security.ibm.

xml Input None. Throws Exception if authentication service is not configured. Returns None. Input password Password that was used to protect the LTPA keys in the file. Input None. Throws Exception if a system error is encountered. If there are existing LTPA keys configured for the authentication service. Syntax $AdminTask unconfigureESS Action createESSLTPAKeys Purpose Creates new LTPA Keys for use by authentication service. Throws Exception if a system error is encountered. Purpose This command configures the authentication service by creating an authentication service configuration file in the WebSphere Application Server Network Deployment configuration repository found in WAS_PROFILE/config/ibmess/authn/Configuration. Returns None. those keys are overwritten LTPA tokens that have been previously issued using the replaced keys are invalidated.xml file. Returns None. Exception if a system error is encountered. Syntax $AdminTask createESSLTPAKeys {-password password} Action importESSLTPAKeys 60 IBM Control Desk: Installation Guide (IBM WebSphere) . Syntax $AdminTask configureESS Action unconfigureESS Purpose Unconfigures the authentication service by removing authentication service configuration from the WebSphere Application Server Network Deployment configuration repository WAS_PROFILE/config/ibmess/authn/ Configuration. Exception if authentication service LTPA keys cannot be configured.

Exception if a system error is encountered. Exception if keys cannot be created. Chapter 4. Purpose Import LTPA keys into authentication service from an existing LTPA Key Export file. This key can be taken from the com. or by the authentication service through the exportESSLTPAKeys command.password String The password that was used to protect the keys created by the partner. If there are existing LTPA keys configured for the authentication service.partner.ltpa.websphere. Throws Exception if the authentication service is not configured.partner.ibm. 3DESKey name-value pair of an exported LTPA key file. ltpa. those keys are overwritten. This key can be taken from the com. Returns None. password Password that was used to protect the LTPA keys in the file.ltpa. LTPA tokens that have been previously issued using the replaced keys are invalidated.partner. This file might have been exported by WebSphere Application Server Network Deployment. Syntax $AdminTask importESSLTPAKeys {-pathname path name . Manually configuring existing middleware during deployment 61 . This key was encrypted when it was exported from the WebSphere Application Server Network Deployment server that created it. Input pathname Path and file name of file containing LTPA keys to import into the authentication service.PublicKey name-value pair of an exported LTPA key file. ltpa. LTPA exported key file mapping Name Type Description of Value ltpa.publickey String The public key for the partner that signed the token.ibm. Table 6.sharedkey String The shared key used for decryption of the token.websphere.password password} Reference This table shows the mapping of LTPA exported key file information to the authentication service configuration fields.

This key was encrypted when it was exported from the WebSphere Application Server Network Deployment server that created it. LTPA exported key file mapping (continued) Name Type Description of Value ltpa.password String The password that was used to protect the keys that the consuming application created.ibm. 3DESKey name-value pair of an exported LTPA key file. Action exportESSLTPAKeys Purpose Export LTPA keys from the authentication service and write to the LTPA key export file. This key can be taken from the com. Input pathname Path and file name to write LTPA keys to be exported from the authentication service.Table 6.sharedkey String The shared key used for the encryption of the token.self. Returns None. Exception if a system error is encountered.self. Throws Exception if the authentication service is not configured.self. This key was encrypted when it was exported from the WebSphere Application Server Network Deployment server that created it. ltpa.ltpa.ibm. PublicKey name-value pair of an exported LTPA key file. 62 IBM Control Desk: Installation Guide (IBM WebSphere) . ltpa.self. Exception if the authentication service LTPA keys have not been configured.websphere.self. This key can be taken from the com.privatekey property. This key can be taken from the com.publickey String The public key associated with the ltpa.websphere.ltpa. PrivateKey name-value pair of an exported LTPA key file.websphere.ltpa. this file might be used to import LTPA keys into another the authentication service server or into WebSphere Application Server Network Deployment. ltpa.privatekey String The private key that is used for signing the token. After successful export from the authentication service.ibm.

websphere.sharedkey) com.websphere. #IBM WebSphere Application Server key file #Mon Jun 11 08:05:50 EDT 2007 com.PrivateKey=(set from ltpa.CreationHost=(set to local host name) com.websphere.publickey) Action showESSLTPAConfiguration Purpose Returns a property object containing the current authentication service LTPA configuration. Returns Properties object.websphere.version=1.ibm. expiration.3DESKey= zDtRTqOEsw0F5NNhGpvzdp/xqoFFTyX0WFNxYMEpC10\= com.ltpa.websphere.PublicKey=(set from ltpa.ibm.ibm. Note there are no line breaks in the LTPA key export file.ibm.ltpa.CreationDate=Mon Jun 11 08\:05\:50 EDT 2007 com.ibm.ltpa.websphere.Realm= VmmLdapRealm com.websphere.ltpa.ibm.ibm.Realm=(set to the currently configured VMM realm) com.websphere.privatekey) com.websphere.websphere. The returned properties list contains version. Syntax $AdminTask showESSLTPAConfiguration Chapter 4.3DESKey=(set from ltpa.CreationDate=(set to the date/time when the export file is created) com.ltpa.ltpa.websphere.ibm.self.CreationHost= PestRHAS3 com. Exception if a system error is encountered.ltpa.ibm.ibm.ltpa.ibm.websphere.self.ibm.Syntax $AdminTask exportESSLTPAKeys {-pathname path name} Reference Here is an example of the LTPA key export file. After an initial configuration.ltpa. Manually configuring existing middleware during deployment 63 .version=1. Input None.0 com. the defaults will be returned.self. and usefips configuration properties.ltpa.websphere.websphere.ibm.PublicKey= AKj4wjeYEQoxL76Ph0g1i3gt5Siwgygu3+22xfh6Kh1JR3 LZGsT+nONpAfxY9NfmPTDFxjbrIESIS/ XAdp/0QgWBF9DZJ5vO1Ds0/M356seVtsnvwy3p/VVFQg4Uz T6j/f1G6SJaqPQjrv2EAZyEn+TL8Okl3CWdKiFtPjtpWdh5AQAB How ESSLTPAKeys are exported to a file: com.PrivateKey= hPyfNkqrClrwpQgRAnvNSRugf/6Su59g5Jh5FR28SrT/ XapX/OOghU3/41dX1HXL496sDKm9kXE/WYhsFvh3L8JVzacEqF3T+57akZZ /wDJdga6DcDlYMmzLll 91SgjV68dB6lsVgt/ jFtMczYxK+RgBDpKthEurI9rQr2eq73Gm75KehgRSMCaBwew+kQi6aWFdyhWc OlQLCod8BQtesJt2aTEaQ3NDD0PFQVkDMWVpzoLvBOJBdhwhQFWX9L7gE9gMeS PoeXr19MlEA780/E X9w7kEIKYu7UzrUbvTEREoYCUFklJcE2A3Q0rMKlIzlkIJ1QGXwR6EM2sVe9w6M CPHir32A45rEYyy1 lP0SuA\= com.ibm.0 com. Throws Exception if the authentication service is not configured.

self. version See ltpa. ltpa.self.self.version list (if a list 2 self This determines Yes exists.usefips boolean False partner This determines No whether the FIPS enabled flag was enabled when the partner created the token. Exception if a system error is encountered. ltpa.expiration in the table. Action createESSSigner Purpose Configures the authentication service to use response signing keys from the default keystore.self. LPTA Configuration Properties Parameter Type Default Config Type Description Required ltpa.self. expiration See ltpa. ltpa. 64 IBM Control Desk: Installation Guide (IBM WebSphere) . Syntax $AdminTask modifyESSLTPAConfiguration {[-version version] [-expiration expiration] [-usefips useFips]} Reference Table 7.expiration long 120 self The expiration time Yes that is set on the token in minutes.self.partner.usefips in the table. String what version of otherwise) LTPA token to issue: version 1 or 2. Action modifyESSLTPAConfiguration Purpose Modifies the authentication service LTPA properties.usefips boolean False self This determines No whether the FIPS enabled flag was enabled when the partner created the token. Returns None. Throws Exception if the authentication service is not configured. Input usefips See ltpa. This time is converted to milliseconds and then added to the current system time to give an absolute expiration time.version in the table.

Optional . If the keystore exists it is updated. keypassword .Password to open the imported keystore file. Throws Exception if the authentication service is not configured. keyalias . Chapter 4.Input None. password Required . Input pathname .Alias to specify to store the exported response. keyalias Required . Returns None. Exception if a system error is encountered. Syntax $AdminTask importESSSigner {-pathname path name -password password-keyalias alias -keypassword password } Action exportESSSigner Purpose Export the configured response signer keys to the specified keystore.The password to access the signer key in the keystore file. keypassword Required . Throws Exception if the authentication service is not configured. Exception if required parameter is missing.The alias of the signer key in the imported keystore file. Input pathname Required . Returns None. Manually configuring existing middleware during deployment 65 .The password to specify to encrypt the signer key in the keystore file.Path and filename of a keystore into which configured response signer keys are exported. password .Password for accessing the specified export keystore file. Exception if a system error is encountered. Exception if the keystore file cannot be located.Required . Returns None. to be used for synchronization with other authentication service instances. Syntax $AdminTask createESSSigner Action importESSSigner Purpose Configures the authentication service to use response signing keys from the specified keystore.Required .Required – File path name of an existing keystore file to import into Authentication Service configuration.

Throws Exception if the authentication service is not configured. to be used by an Authentication Client for response signature validation. Exception if a system error is encountered. 66 IBM Control Desk: Installation Guide (IBM WebSphere) . Input None. Exception if the keystore file cannot be located.Password for accessing the specified export keystore file. password Required . Input domain See domain in the table. Input pathname Required .Alias of the certificate to export. associated with the response signer key. Throws Exception if the authentication service is not configured Exception if a system error is encountered Exception if the keystore file cannot be located Syntax $AdminTask exportESSSignerCert {-pathname path name -password password -certalias alias} Action showESSWSFedConfiguration Purpose Display the current WS-Federation SSO servlet configuration settings.Path and filename of a keystore into which configured response signer keys are exported. If the keystore exists it is updated. certalias Required . Syntax $AdminTask exportESSSigner {-pathname path name -password password -keyalias alias -keypassword password } Action exportESSSignerCert Purpose Export the configured response signer certificate to the specified keystore. Returns Properties object with current SSO redirect WS-Federation servlet properties Throws Exception if the authentication service is not configured. Syntax $AdminTask showESSWSFedConfiguration Action modifyESSWSFedConfiguration Purpose Modifies SSO redirect WS-Federation servlet cookie properties. secure See secure in the table. Returns None. Exception if a system error is encountered.

com # domain = none # domain = default secure boolean True Specifies that the No. session cookies are sent to hosts in that domain. session cookies include the secure field. A browser does not accept the cookie if the cookie domain conflicts with the domain specified in the request URL. For example. Manually configuring existing middleware during deployment 67 . Throws Exception if the authentication service is not configured. the default domain is the domain of this server. Syntax $AdminTask modifyESSWSFedConfiguration {[-domain domain] [-secure true|false] [-maxage milliseconds|-1]} Reference Table 8. This value controls whether a browser sends a cookie to particular servers. Returns None. Chapter 4. modifyESSWSFedConfiguration parameters Parameter Type Default Description Required domain string Default Specifies the domain No. Enabling the feature restricts the exchange of cookies to HTTPS sessions only. #Examples: # domain = .ibm. field of a session tracking cookie. maxage See maxage in the table. If not specified. Exception if a system error is encountered. if you specify a particular domain.

That identity needs to be registered with WebSphere Application Server Network Deployment. Wsadmin interfaces must be used to map application roles under embedded WebSphere. Click OK. the authnsvc_ctges authentication service application installs into the WebSphere Application Server Network Deployment server. About this task To add users and groups to the TrustClientRole of the authentication service in the WebSphere Application Server Network Deployment console. The authentication service contains a role called TrustClientRole. select Everyone? or All authenticated? boxes. Setting maxage to “session” specifies a lifetime of current browser session. Save the configuration. 4. 68 IBM Control Desk: Installation Guide (IBM WebSphere) . and it is either mapped to the TrustClientRole role of the authentication service. 2. Use Look up users or groups to select the users or groups to add to the TrustClientRole role. the clients are configured with an identity that authenticates the client to WebSphere Application Server Network Deployment when it calls the authentication service. The embedded WebSphere ISC console does not provide application role mapping capability. Before you begin When single sign-on clients are configured and application security is enabled. of time that the cookie lives on the client browser. Configuring the TrustClientRole for the authentication service: If single sign-on is enabled. 3. Open Applications > Enterprise Applications > authnsvc_ctges > Security role to user/group mapping. or added to a group that is mapped to the TrustClientRole role of the authentication service. alternatively. Note: This section does not apply to embedded WebSphere. follow these steps: Procedure 1. modifyESSWSFedConfiguration parameters (continued) Parameter Type Default Description Required maxage integer / string Session Specifies the amount No. You can. Specify the maximum age in seconds. the WebSphere Application Server Network Deployment administrator assigns users or groups to TrustClientRole. If WebSphere Application Server Network Deployment security is enabled.Table 8.

Results

To query the users and groups currently mapped to the TrustClientRole of the
authentication service, use the wsadmin AdminApp view command:
wsadmin>$AdminApp view authnsvc_ctges

Alternatively, users and groups can be added to the TrustClientRole of the
authentication service using the wsadmin AdminApp edit command. For example, to
set the TrustClientRole to allow access to all authenticated users you would use the
following command:
wsadmin>$AdminApp edit authnsvc_ctges
{-MapRolesToUsers { {"TrustClientRole" no yes "" ""}} }

See the WebSphere Application Server Network Deployment documentation for
more information about the AdminApp edit command and the use of the
–MapRolesToUsers option.

The following sample Jython script called setAuthnSvcRoleAll.py sets the
TrustClientRole role to allow access to all authenticated users:
import sys

global AdminConfig
global AdminControl
# Usage:
# was_profile_dir/bin/wsadmin -lang jython -f setAuthnSvcRoleAll.py
# where was_profile_dir is the WebSphere profile directory

AdminApp.edit("authnsvc_ctges", ["-MapRolesToUsers",
[["TrustClientRole", "No", "Yes", "", ""]]] )
AdminConfig.save()

Clock synchronization:

Verify that the time, date, and time zone are synchronized among all servers
participating in the protected domain.

Because single sign-on authentication uses time-sensitive tokens, you must verify
that the time, date, and time zone are synchronized. This verification must be
done for all servers that are participating in the protected domain, such as the the
WebSphere Application Server Network Deployment server and the Tivoli
Application Dependency Discovery Manager server.

If the time difference is too high between servers, the single sign-on token might
prematurely expire on some servers and cause authentication or validation failures.

WebSphere Application Server Network Deployment and authentication
service-based single sign-on tokens are assigned a lifetime of two hours by default.
For best results, servers must be synchronized to within 5 minutes to ensure that
single sign-on tokens are evaluated consistently.

Authentication service logging:

The authentication service LTPA token provider and the authentication service
token service infrastructure logs can be useful when troubleshooting connection
errors related to the authentication service.

Chapter 4. Manually configuring existing middleware during deployment 69

Configuration of the authnsvc_ctges authentication service LTPA token provider
logging
Authentication service LTPA token provider logging is performed using the
java.util.logging.Logger message and trace logging facility. Logging
characteristics can be configured using the WebSphere Application Server
Network Deployment administrator console.
1. From the WebSphere Application Server Network Deployment
administrator console, select Troubleshooting > Logs and trace >
server 1 > Change Log Detail Levels.
2. Set the com.ibm.security.ess.authn.provider log level to All Messages
and Traces under both the Configuration and Runtime tabs.
3. Click OK and then save.
4. Restart the server.
Configuration of authnsvc_ctges authentication service token service
infrastructure logging
Authentication service user name provider and token service infrastructure
logging is performed using the Log4J utility. Logging characteristics can be
configured by modifying the WAS_PROFILE/installedApps/cell
name/authnsvc_ctges.ear/com.ibm.security.ess.war/WEB-INF/classes/
log4j.properties file, then restarting the server.
Format of the log4j.properties file:
### direct log messages to stdout ###

log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{HH:mm:ss,SSS} %5p %C{1}.%M
(%L): %m%n

### set log levels - for more verbose logging change ’info’ to ’debug’ ###

log4j.rootLogger=TRACE, stdout
log4j.logger.org.eclipse=info
log4j.logger.org.apache=info
log4j.logger.org.apache.xml.security=info
log4j.logger.org.xmlsoap.schemas.ws=info
log4j.logger.org.eclipse.higgins=trace
log4j.logger.org.eclipse.alf=info
log4j.logger.org.apache.axis.transport.http.HTTPSender=info
log4j.logger.org.openid=info
log4j.logger.com.ibm.openid=info
log4j.logger.com.ibm.security.ess=trace
In most cases, only the log4j.logger.org.eclipse.higgins and
log4j.logger.com.ibm.security.ess properties must be set to trace.
Logging levels, listed in order of least to most inclusive, are:
1. fatal
2. error
3. warn
4. info
5. debug
6. trace
Authentication service configuration AdminTask command logging
Authentication service configuration AdminTask command logging is
performed using the java.util.logging.Logger message and trace logging

70 IBM Control Desk: Installation Guide (IBM WebSphere)

facility. Logging characteristics can be configured using the WebSphere
Application Server Network Deployment administrator console.
1. From the WebSphere Application Server Network Deployment
administrator console, select Troubleshooting > Logs and trace >
server 1 > Change Log Detail Levels.
2. Set the com.ibm.security.ess.authn.provider log level to All Messages
and Traces under both the Configuration and Runtime tabs.
3. Click OK and then save.
4. Restart the server.

Manually configuring JMS queues:

This procedure provides details on steps to configure JMS queues, which must be
completed before using the product installation program.

About this task

During the installation process, the Control Desk installation program provides
you with the option of automatically configuring Control Desk middleware. If you
choose to have the Control Desk installation program automatically configure
Control Desk middleware, it creates and configures JMS message queues for you. If
you choose to manually configure Control Desk middleware for use with Control
Desk, you must manually configure these message queues.

To configure the JMS queues, complete the following steps:

Procedure
1. Start the WebSphere Application Server Network Deployment application
server.
2. Start Internet Explorer and open the WebSphere Application Server Network
Deployment administrative console by typing the following URL:
http://<server_name>:<port_number>/ibm/console
For example, enter a URL like the following sample URL:
http://localhost:9060/ibm/console
3. At the login screen, enter your user ID and click Log in. This action opens the
Welcome screen for the WebSphere Application Server Network Deployment
administrative console.
4. Click Service Integration > Buses to open the Buses dialog. A bus is a group
of interconnected servers and clusters that have been added as members of
the bus.
5. Click New to open the Create a new Service Integration Bus panel where
you can add a new service integration bus.
6. Enter intjmsbus as the name of the new bus in the Name field.
7. Clear the Bus security check box. If you leave this box checked, intjmsbus
inherits the Global Security setting of the cell.
8. Click Next.
9. Click Finish.
10. Click Save. This step propagates the JMS bus setup to the cluster
configuration.

Chapter 4. Manually configuring existing middleware during deployment 71

Adding a server to the service integration bus:

A server must be defined for the service integration bus.

About this task

Complete the following steps to add a server to the service integration bus:

Procedure
1. From the WebSphere Application Server Network Deployment administrative
console, click Service Integration > Buses to open the Buses dialog box.
2. Click intjmsbus to open the Buses > intjmsbus dialog box.
3. Under Topology, click Bus members.
4. In the Buses > intjmsbus > Bus members dialog box, click Add to open the
Add a new bus member dialog box.
5. Select the Server option, and select the server name ctgNode01:MXServer to
add to the bus, and then click Next.
6. Check that the File store radio button is selected, and then click Next.
7. From the Configure file store panel, click Next.
8. From the Tune application server for messaging performance panel, click
Next.
9. Click Finish.
10. Click Save.
11. Select intjmsbus.
12. Change the value of the Default messaging engine high message threshold
field to a minimum value of 500,000 messages, and then click Apply.
If the number of messages awaiting processing exceeds the High Message
Threshold you set, the application server limits the addition of new messages
in the processing queues.
Depending on your message requirements, you can to enter a higher message
threshold value. You can determine an optimal message threshold setting by
monitoring the messaging in/out queues and the impact of the message
threshold setting on system performance. You might, for example, lower the
threshold value if a higher value is degrading system performance.
If you decide to change the High message threshold setting after the initial
configuration, you must open the Additional Properties menu in the
administrative console and change the threshold value for each child
configuration.
13. Click Save.

Creating the service integration bus destination for the continuous inbound (CQINBD)
queue:

You must create a service integration bus destination for the continuous inbound
(CQINBD) queue.

About this task

To add a logical address for the continuous inbound bus destination queue
(CQINBD) within the JMS bus, complete the following steps:

72 IBM Control Desk: Installation Guide (IBM WebSphere)

Click New to open the Create new destination dialog box. and click Next to open the Create new queue dialog box. Click Apply. Click Save. Click None as the Exception destination value. Review your selections. and click Next to open the Create new queue dialog box. Verify Keep count of failed deliveries per message is enabled. Type CQINBD in the Identifier field and Continuous Queue Inbound in the Description field. 11. 13. Chapter 4. complete the following steps: Procedure 1. Navigate the path Buses > intjmsbus > Destinations. A bus destination. 5. is a virtual place within a service integration bus where applications can attach and exchange messages. 12. 2. 2. Leave Queue checked as the destination type. Click intjmsbus to open the Buses > intjmsbus dialog box. 14. 4. Click New to open the Create new destination dialog box. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer as the bus member that will store and process messages for the CQINBD bus destination queue. then click Next to open the Create a new queue for point-to-point messaging dialog box. for example CQINBD. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. click Service Integration > Buses to open the Buses dialog box. A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. then click Finish to complete the creation of the CQINBD bus destination queue. 3. 8. click Service Integration > Buses to open the Buses dialog box. 5. 4. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. About this task To add a logical address for the sequential inbound bus destination queue (SQINBD) within the service integration bus. 6. Leave Queue checked as the destination type. Click Next to open the Confirm queue creation dialog box. 9. Creating the service integration bus destination for the sequential inbound (SQINBD) queue: You must create the service integration bus destination for the sequential inbound (SQINBD) queue. 10. Manually configuring existing middleware during deployment 73 . From the WebSphere Application Server Network Deployment Administrative Console. 7. From the WebSphere Application Server Network Deployment Administrative Console.Procedure 1. Click intjmsbus to open the Buses > intjmsbus dialog box. then click CQINBD to open the configuration dialog box. 3.

2. and click Next to open the Create new queue dialog box. 10. Click None as the Exception destination value. then click Next to open the Create a new queue for point-to-point messaging dialog box. Navigate the path Buses > intjmsbus > Destinations. 12. Review your selections. for example SQOUTBD. 10. complete the following steps: Procedure 1. Review your selections. Navigate the path Buses > intjmsbus > Destinations. 7. About this task To add a logical address for the sequential outbound bus destination queue (SQOUTBD) within the service integration bus. 7. 9. Click Next to open the Confirm queue creation dialog box. then click SQOUTBD to open the configuration dialog box where you must make the following changes: 74 IBM Control Desk: Installation Guide (IBM WebSphere) . click Service Integration > Buses to open the Buses dialog box. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer 8. 3. Click Next to open the Confirm queue creation dialog box. A bus destination. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the Description field. Leave Queue checked as the destination type. then click Next to open the Create a new queue for point-to-point messaging dialog box. then click Finish to complete the creation of the SQINBD bus destination queue. then click Finish to complete the creation of the queue. Click Apply. Note that you must use this value and it must contain only uppercase letters. is a virtual place within a service integration bus where applications can attach and exchange messages. Click intjmsbus to open the Buses > intjmsbus dialog box. 14. Enter SQINBD in the Identifier field and Sequential Queue Inbound in the Description field. You must use this value and it must contain only uppercase letters. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. then click SQINBD to open the configuration dialog box. 6. 6. Click Save. Verify Keep count of failed deliveries per message is enabled. From the WebSphere Application Server Network Deployment administrative console. 8. Click New to open the Create new destination dialog box. 11. 9. 5. 4. Select the Bus Member menu and choose Node=ctgNode01:Server=MXServer as the bus member that stores and processes messages for the SQOUTBD bus destination queue. Creating the service integration bus destination for the sequential outbound (SQOUTBD) queue: You must create the service integration bus destination for the sequential outbound (SQOUTBD) queue. 13.

From the Scope drop-down list. 12. select Cell=ctgCell01. 4. Bus name Select intjmsbus. Enter the following information: Name Enter intjmsconfact. JNDI name Enter jms/maximo/int/cf/intcf. click Resources > JMS > Connection factories. select Cell=ctgCell01. Click Apply. Verify that the Default Messaging Provider is selected and click OK. 2. Click None as the Exception destination value. Click New. Click Save. Click New. Click Save. complete the following steps: Procedure 1.11. From the Scope drop-down list. 7. JNDI name Enter jms/maximo/int/queues/cqin Chapter 4. Creating the JMS connection factory: Add a connection factory for creating connections to the associated JMS provider of point-to-point messaging queues. Verify that the Default Messaging Provider is selected and click OK. Verify Keep count of failed deliveries per message is enabled. This value must contain only uppercase letters. 5. 14. Manually configuring existing middleware during deployment 75 . From the WebSphere Application Server Network Deployment administrative console. 6. complete the following steps: Procedure 1. About this task To create the JMS connection factory. Click Apply. Name Enter CQIN. 4. 5. 2. About this task To create the CQIN JMS queue. Enter the following information. and click OK. 3. From the WebSphere Application Server Network Deployment administrative console. 13. Creating the continuous inbound (CQIN) JMS queue: You must create a JMS queue (CQIN) as the destination for continuous inbound point-to-point messages. 3. click Resources > JMS > Queues.

Click New. Enter the following information. 7. complete the following steps: Procedure 1. select Cell=ctgCell01. JNDI name Enter jms/maximo/int/queues/sqin Bus name Select intjmsbus. Enter the following information. From the WebSphere Application Server Network Deployment administrative console. About this task To create the SQOUT JMS queue. click Resources > JMS > Queues. complete the following steps: Procedure 1. Bus name Select intjmsbus. and click OK. 4. and click OK. Click OK. 7. Queue name Select CQINBD. Name Enter SQIN. 5. 6. From the WebSphere Application Server Network Deployment administrative console. 76 IBM Control Desk: Installation Guide (IBM WebSphere) . select Cell=ctgCell01. 6. From the Scope drop-down list. 2. 3. About this task To create the SQIN JMS queue. 4. This value must contain only uppercase letters. Verify that the Default Messaging Provider is selected and click OK. Click New. From the Scope drop-down list. 3. Creating the sequential outbound (SQOUT) JMS queue: You must create a JMS queue (SQOUT) as the destination for sequential outbound point-to-point messages. 2. Click Save. Click Save. 5. Creating the sequential inbound (SQIN) JMS queue: You must create a JMS queue (SQIN) as the destination for sequential inbound point-to-point messages. Queue name Select SQINBD. click Resources > JMS > Queues. Verify that the Default Messaging Provider is selected and click OK. Click OK.

2. Select Default messaging provider and then click OK. 6. Error queues: You must create an error queue that receives redirected messages from the continuous queue (CQIN). Click OK. the error queue receives redirected messages from the continuous queue (CQIN). click Resources > JMS > Activation Specifications. This value must be lowercase. From the Scope drop-down list. Queue name Select SQOUTBD. 4. Name intjmsact This value is case-sensitive. Name Enter SQOUT. Click New. Creating JMS activation specification for the continuous inbound queue (CQIN): You must activate the continuous inbound queue (CQIN) before it can receive messages. About this task Complete the following steps to activate the CQIN queue: Procedure 1. 7. 3. When the messages go in error. and then click Save. select Cell=ctgCell01. and then click OK. From the WebSphere Application Server Network Deployment administrative console. Manually configuring existing middleware during deployment 77 . Enter the following information. Chapter 4. Click Save. This value must contain only uppercase letters. JNDI name Enter jms/maximo/int/queues/sqout Bus name Select intjmsbus. JNDI name intjmsact Destination type Queue Destination JNDI name jms/maximo/int/queues/cqin Bus name intjmsbus Maximum concurrent MDB invocations per endpoint 10 6. 5. Click OK.

Enter CQINERRBD in the Identifier field and Error Queue Inbound in the Description field. 10. Leave Queue checked as the destination type. click Service Integration > Buses to open the Buses dialog box. 78 IBM Control Desk: Installation Guide (IBM WebSphere) . Select Buses > intjmsbus > Destinations. Set the Maximum failed deliveries value to 5. Click Save. From the Bus Member menu. 17. Click intjmsbus to open the Buses > intjmsbus dialog box. select Node=ctgNode01:Server=MXServer 8. 18. Click Save. Verify Keep count of failed deliveries per message is enabled. b. You must use this value and it must contain only uppercase letters. click Service Integration > Buses to open the Buses dialog box. 19. A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. Click Next to open the Confirm queue creation dialog box. 15. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. then click Finish to create the CQINERRBD bus destination queue. Select CQINBD. Specify CQINERRBD as the exception destination. then click CQINERRBD to open the configuration dialog box where you must make the following changes: a. 9. 11. c. then click Next to open the Create a new queue for point-to-point messaging dialog box. 16. Select the Specify option and enter CQINERRBD as the exception destination value. Click Apply. Click New to open the Create new destination dialog box. From the WebSphere Application Server Network Deployment administrative console. About this task Perform the following steps: Procedure 1. Review your selections. Creating the service integration bus destination for the inbound error queue (CQINERRBD) queue: You must add a logical address for the inbound error queue (CQINERRBD) queue within the JMS bus. 13. 3. and click Next to open the Create new queue dialog box. 7. 4. Click intjmsbus to open the Buses > intjmsbus dialog box. Click OK. 6. 5. 14. This option is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. 2. 12. Change the Maximum failed deliveries value to 5. From the WebSphere Application Server Network Deployment administrative console.

Creating the error (CQINERR) JMS queue: After creating the Error Queue Bus Destination. From the Scope drop-down list. This value must be the same as the one used for the Name field. 2. 5. Click New. From the WebSphere Application Server Network Deployment administrative console. 3. Click Save. click Resources > JMS > Queues. you create the Error queue. 4. select Cell=ctgCell01. Click New to complete the General Properties section for the new JMS activation specification. From the Scope menu. This value must contain only uppercase letters. Creating JMS activation specification for the inbound error queue (CQINERR): You must activate the continuous inbound queue (CQINERR) before it can receive messages. Procedure 1. and click OK. Verify that the Default Messaging Provider is selected and click OK. 5. From the WebSphere Application Server Network Deployment administrative console. complete the following steps. 6. 2. About this task To create the Error queue. Manually configuring existing middleware during deployment 79 . 7. and click OK. Queue name Select CQINERRBD. and then click Apply. JNDI name Enter jms/maximo/int/queues/cqinerr Bus name Select intjmsbus. JNDI name Enter intjmsacterr. This value must only contain lowercase letters. Name Enter CQINERR. Enter the following information. click Resources > JMS > Activation Specifications. select Cell=ctgCell01. Click OK. Chapter 4. 3. Name Enter intjmsacterr. 4. Click OK. Enter the following information. About this task Complete the following steps to activate the CQINERR queue: Procedure 1.

you must manually configure Virtual Member Manager. You must now restart these processes for the update to take effect. then it will. it must be done only after a successful Control Desk installation and configuration. restart MXServer under Servers > Application servers. If you elected to have the configuration program automatically configure Control Desk middleware. The root of each 80 IBM Control Desk: Installation Guide (IBM WebSphere) . Do not configure a Virtual Member Manager LDAP federated repository to use SSL with an LDAP directory before configuration Control Desk. Configure SSL after the configuration program has completed successfully. Click Save. If you intend to configure Virtual Member Manager to use SSL with a federated LDAP repository. Each repository can be an entire external repository or. a subtree within that repository. Manually configuring Virtual Member Manager on WebSphere Application Server Network Deployment: Some deployment environments require the manual configuration of Virtual Member Manager to secure Control Desk. and federate that data into a single virtual repository. Destination JNDI name jms/maximo/int/queues/cqinerr Bus name intjmsbus Maximum concurrent MDB invocations per endpoint 10 6. in the case of LDAP. see the security planning information. The federated repository consists of a single named realm. perform Virtual Member Manager configuration for you. Start the bus member for the ctgNode MXServer intjmsbus if it is not started. Important: Before you begin this procedure. 10. If you cannot start ctgNode MXServer intjmsbus. If you elected to manually configure Control Desk middleware for use with Control Desk. ensure that you have a wasadmin user ID created in your LDAP repository. which is a set of independent user repositories. 9. If Virtual Member Manager is configured to use SSL with a federated LDAP repository before completing the Control Desk configuration. Ensure that you stop all IBM-related processes and daemons. the configuration program provided you with the option of automatically configuring Control Desk middleware. Click OK. Virtual Member Manager provides you with the ability to access and maintain user data in multiple repositories. Destination type Enter Queue. 7. the configuration fails. 8. About this task During the configuration process. Before you begin For a review of Control Desk security options. among other tasks.

For Microsoft Active Directory. substitute values where appropriate in this procedure. For Microsoft Active Directory. select IBM Tivoli Directory Server. Directory type For IBM Security Directory Server. The values provided here are example purposes only. 8. Start Internet Explorer and open the WebSphere Application Server Network Deployment administrative console by typing the following URL: http://<server_name>:<port_number>/admin For example. Multiple base entries can be added with different search bases for a single LDAP directory. you must first add the LDAP directory to the list of repositories available for configuration for the federated repository. Support referrals to other LDAP servers Set this value to ignore. Select Security > Global security. To add an LDAP directory to the Virtual Member Manager virtual repository. If you are configuring Virtual Member Manager to use Microsoft Active Directory. Locate the User account repository area and pick Federated repositories from the Available realm definitions field.repository is mapped to a base entry within the federated repository. Start the WebSphere Application Server Network Deployment application server. Port Enter 389. and then click Save. then click Log in. Repository identifier For IBM Security Directory Server. 2. This action opens the Welcome screen for the WebSphere Application Server Network Deployment administrative console. Chapter 4. Click Add repositories located under Repositories in the realm. enter the values used during the installation and configuration of IBM Security Directory Server. and then click Configure. Manually configuring existing middleware during deployment 81 . Click New repositoryLDAP repository to create new repository definition under the current default realm. To add the IBM Security Directory Server or Microsoft Active Directory to VMM. At the login screen. click Apply. complete the following steps: Procedure 1. enter your user ID. select Microsoft Windows Server 2012 Active Directory. 6. You must then add the root of baseEntries to a search base within the LDAP directory. Enter the following values. enter ISMMSAD . 7. 4. 5. Primary host name Enter the fully qualified host name or IP address of the directory server. You must modify the VMMCRONTASK accordingly. enter ISMITDS. If you are using IBM Security Directory Server. The root is a starting point within the hierarchical namespace of the virtual realm. enter a URL like the following sample URL: http://localhost:9060/admin 3.

enter the following values.o=IBM. enter ou=SWG. enter cn=root. Distinguished name in the repository is different This value is optional.DC=com. 82 IBM Control Desk: Installation Guide (IBM WebSphere) . Repository For IBM Security Directory Server. Certificate mapping Select EXACT_DN Figure 10. enter ou=SWG. enter CN=Administrator. click Apply. and then click Save: Realm name Enter ISMRealm. Bind password Enter the password for the bind distinguished name.DC=com. For IBM Security Directory Server.DC=com. You need to provide this value if it differs from the base entry in the repository you are adding. select ISMITDS. New Repository 9. enter DC=ism76. Bind distinguished name For IBM Security Directory Server. select ISMMSAD . enter DC=ism76. For Microsoft Active Directory. For Microsoft Active Directory.DC=ism76. click Apply.CN=Users.c=US. For Microsoft Active Directory.c=US. 10. Enter the following values.o=IBM. and then click Save. Unique distinguished name of the base entry (or parent) entry in federated repositories For IBM Security Directory Server. For Microsoft Active Directory. From the Federated repositories configuration area.

enter the following values: Entity type Verify that the value is PersonAccount. From the OrgContainer configuration area. Click Supported entity types. enter CN=Users. enter ou=users. Server user identity Select Automatically generated server identity.o=IBM.dc. enter ou=groups. 12.cn.o=IBM. 14. Relative Distinguished Name properties Enter cn. 20. Click OK and then click Save. Click OK and then click Save. enter ou=SWG.DC=com. complete the following: a. Relative Distinguished Name properties Enter uid. enter or verify the following values: Entity type Verify that the value is OrgContainer.CN=Groups.ou. Manually configuring existing middleware during deployment 83 . enter the following values: Entity type Verify that the value is Group.DC=com. Enable Enable administrative security. Base entry for the default parent For IBM Security Directory Server. 19. 16. This value must be a valid user from the configured LDAP repository. b.c=US. Primary administrative user name Enter wasadmin. Ignore case for authorization Select this check box. 17. and then click PersonAccount.o=IBM. Click Supported entity types. For Microsoft Active Directory. Click OK and then click Save. 18. 15. From the PersonAccount configuration area. and then click Group. Base entry for the default parent For IBM Security Directory Server. For Microsoft Active Directory. 11. For Microsoft Active Directory. Browse to Security > Global security. enter DC=ism76.DC=com.c=US. enter ou=groups. Relative Distinguished Name properties Enter o. Chapter 4.ou=SWG.c=US.DC=ism76. and then click OrgContainer. Base entry for the default parent For IBM Security Directory Server. From the Group configuration area.DC=ism76.ou=SWG. Click Supported entity types. From the Global security configuration page. 21. Enable Enable application security. 13.

run the installation program on the Control Desk administrative system. 23. Installing Control Desk Install Control Desk. d.bat b.bat d. <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.exe.bat Note: Substitute UNIX path and file extension values where appropriate. In the package selection panel. If you run the installation program from a Linux or UNIX terminal window. “Performing WebSphere Application Server Network Deployment configuration tasks” on page 48 Use this procedure to perform WebSphere Application Server Network Deployment configuration tasks. In the launchpad navigation pane. 3. <WAS_HOME>\profiles\ctgDmgr01\bin\stopManager. Click Apply. d. Log in to the Control Desk administrative workstation. This package is required for the complete installation of Control Desk including the advanced edition.bat c. “Manually configuring Microsoft Active Directory” on page 40 You can manually configure Microsoft Active Directory for use with Control Desk. b. click Install Product. select IBM Control Desk v7. 22. Linux and UNIX From the downloaded installation image.6 and click Install IBM Control Desk components. 2. 84 IBM Control Desk: Installation Guide (IBM WebSphere) . and then click Save.sh. Click Set as current. c. you must be logged in as the root user. <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. ensure that IBM Maximo for Service Providers is selected. Select a language for the installation session and click OK. Procedure 1. Restart WebSphere Application Server Network Deployment and the managed nodes by running the following commands: a. Windows From the downloaded installation image. click Next. select Federated repositories. c. From Available realm definition. Clear the option for Use Java 2 security to restrict application access to local resources. <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode. a. browse to the root directory and run the following command: launchpad64. e. About this task To install Control Desk. Start the launchpad. From the Install Product panel. browse to the root directory and run the following command: launchpad. Important: In the package selection panel. Launch the Control Desk installation program from the launchpad.

In the license agreement panel. 3. click Finish. What to do next Use the configuration program to configure Control Desk. Manually configuring existing middleware during deployment 85 . In the package installation location panel. If any errors are reported on this panel. In the package prerequisite validation panel. In the IBM Control Desk configuration operations page. review summary details about the product components you are installing. In the Configure the DB2 Database panel. click Configure a New Deployment. 7. 6. In the Configure the DB2 Instance panel. Specify the appearance and navigation features for your product. Configuring Control Desk with manually configured middleware Use the configuration program to configure Control Desk. 2. After you define your deployment environment. Select the WebSphere is already configured option. The installation exits and the configuration program is started automatically. You configure supported languages later in the configuration program. 8. add an e-mail address to receive workflow messages. and choose whether or not to deploy sample data. Procedure 1. specify Control Desk installation location and click Launch the Tivoli’s Process Automation Suite configuration program. In the package summary panel. Installation Manager is the installation framework that is used to install Control Desk components. specify the path information for the Control Desk installation directory and click Next. specify path information for the shared resources directory and the Installation Manager installation directory and click Next. 10. In the launchpad navigation pane. click Configure Product. select the option to start the configuration program and click Finish. 4. specify information about the DB2 database for Control Desk. you might notice that the environment summary is listed as English. In the Define Deployment Environment panel. accept the license agreement and click Next. 6. The shared resources directory is a common workspace directory used by Installation Manager when installing packages. 5. specify information about the DB2 instance for Control Desk. Start the configuration program from the Control Desk launchpad. review the results of the prerequisite check and click Next. After the installation is complete. In the Installation Manager installation location panel. leave all default options checked and click Next. 5. Chapter 4. If you install in a non-English environment. 9. select the process automation suite package group. specify information about DB2 and WebSphere Application Server Network Deployment servers you installed and prepared. resolve the issue and click Recheck Status. 4. In the package features panel. review the information and click Install. In the Configure General Product Information panel.

and then click Finish. 86 IBM Control Desk: Installation Guide (IBM WebSphere) . 8. In the Configure the Application Server panel. Indicate whether you want to store JMS messages originating from the integration adapter. 10. 7. Enter the user names and passwords for users that must be created for Control Desk. Results Control Desk is installed and configured to use WebSphere Application Server Network Deployment and DB2. select all available deployment operations. specify user interface preferences. choose a security model for Control Desk. Choose the base language and any additional languages you want to install. 9. If you choose a security model that includes a directory server. In the Configure Application Security panel. specify information about the directory for the virtual member manager. specify information for the WebSphere Application Server Network Deployment server you installed. In the Apply Deployment Operations panel.

Ensure that you have host name resolution setup properly in your environment. Configuring SSL between Microsoft Active Directory and WebSphere Application Server Network Deployment To enable the configuration program to automatically create users and groups within Microsoft Active Directory. © Copyright IBM Corp. you also want the configuration program to automatically create users in Microsoft Active Directory. Communication failures occur if the system hosting Microsoft Active Directory cannot resolve host names for systems that have been issued certificates. Then. If you plan to use a directory server for Control Desk authentication and authorization. you do not need configure SSL for a directory server. Deploying in a cluster environment Use the Control Desk installation and configuration programs to install and automatically configure Control Desk in a WebSphere Application Server Network Deployment cluster configuration. You must enable SSL for Microsoft Active Directory. You can use the installation program to install DB2. and then add that certificate to WebSphere Application Server Network Deployment. You then use the configuration program to configure both middleware and Control Desk. 2015 87 .Chapter 5. About this task This procedure is only required if you choose to allow the configuration program to automatically configure WebSphere Application Server Network Deployment. Changing the name or domain of the certificate authority at any point invalidates certificates previously issued from that authority. If you plan to use Control Desk application security for authentication and authorization. users and groups must be created in the directory. generate a certificate. you use the Control Desk installation and configuration programs to install and automatically configure new instances of the following components in a cluster configuration: v DB2 v WebSphere Application Server Network Deployment v Control Desk You use the Control Desk installation program to install Control Desk and the middleware you want to use in your deployment. About this task In this scenario. you must configure SSL communication between Microsoft Active Directory and WebSphere Application Server Network Deployment using the configuration program. You then use the configuration program to automatically configure it.

leave all default options checked and click Next. 4. Installation Manager is the installation framework that is used to install Control Desk components. In the launchpad navigation pane. Start the Control Desk installation program from the launchpad. specify language support for DB2 and click Next.sh.5 using the Control Desk installation Use the Control Desk installation program to install DB2 v10. If you are running the Control Desk installation from a Linux or UNIX terminal window. browse to the root directory and run the following command: launchpad. In the package translations panel. you must be logged in as the root user. click Next. review the results of the prerequisite check and click Next.5. 8. select a package group. The shared resources directory is a common workspace directory used by Installation Manager when installing packages. In the Installation Manager installation location panel. 9. Important: In the package selection panel. 5. If any errors are reported on this panel. 7. 2. a. 10. In the package summary panel. In the package prerequisite validation panel. In the package configuration panel. Select a language for the installation and click OK.Installing DB2 v10. review the information for the planned installation and click Install. b. In the package selection panel. This package is required for the complete installation of Control Desk including the advanced edition.5 and then click Install IBM Control Desk components. 3. 11. From the Install Product panel. Linux and UNIX From the downloaded installation image. 88 IBM Control Desk: Installation Guide (IBM WebSphere) . In the package features panel. Start the launchpad. specify path information for the shared resources directory and the Installation Manager installation directory and click Next. Repeat this process for each package group listed. specify the path information for its installation directory and click Next. Log in to the target system as a user with administrative authority.exe. Windows From the downloaded installation image. specify configuration information for DB2 v10. In the package installation location panel. browse to the root directory and run the following command: launchpad64. select IBM DB2 v10. resolve the issue and then click Recheck Status before continuing. accept the license agreement and click Next. review the license information for each package being installed. ensure that IBM Maximo for Service Providers is selected. d. Procedure 1. In the license agreement panel. click Install Product.5 and click Next. c. 6.

5.5. resolve the issue and click Recheck Status before continuing.5 using the Control Desk installation Use the Control Desk installation program to install WebSphere Application Server Network Deployment v8. 9. browse to the root directory and run the following command: launchpad. b. specify configuration information for IBM HTTP Server and click Next. In the package configuration panel. 6. review the license information for each package that is to be installed. 8. click Install Product. the configuration program configures Control Desk to use Java v7. 3. leave all default options selected and click Next. ensure that IBM Maximo for Service Providers is selected. Select a language for the installation and click OK. Start the Control Desk installation program from the launchpad. 10. 7. a. Installation Manager is the installation framework that is used to install Control Desk components. and click Next.5 and click Install IBM Control Desk components. If you are running the IBM Control Desk installation from a Linux or UNIX terminal window. If any errors are reported on this panel. specify language support for WebSphere Application Server Network Deployment and click Next. During the installation of WebSphere Application Server Network Deployment. d. Procedure 1. Deploying in a cluster environment 89 . browse to the root directory and run the following command: launchpad64. c. In the package installation location panel. The shared resources directory is a common workspace directory used by Installation Manager when installing packages. In the package prerequisite validation panel. This package is required for the complete installation of Control Desk including the advanced edition. Linux and UNIX From the downloaded installation image. Chapter 5.exe. review the information and click Install. accept the license agreement and click Next. In the package translations panel. 11. review the results of the prerequisite check and click Next. In the package selection panel. In the package summary panel. specify the path information for the shared resources directory and the Installation Manager installation directory and click Next. Log in to the target system as a user with administrative authority. specify path information for its installation directory. From the Install Product panel. In the launchpad navigation pane. 2. Windows From the downloaded installation image. When you install Java v7. Repeat this process for each package group that is listed. install Java v7. Start the launchpad. you must be logged in as the root user. 4. select a package group. In the license agreement panel. click Next. In the package features panel.sh. Important: In the package selection panel.5.Installing WebSphere Application Server Network Deployment v8. In the Installation Manager installation location panel. select IBM WebSphere Application Server Network Deployment v8.

You then configure Control Desk to work with the defined clusters. you must log onto the server and run the configuration program to configure a WebSphere Application Server Network Deployment profile and node to host those cluster members.5 for Control Desk configuration and configure application server cluster profiles. 5. node name. and SOAP port for the deployment manager profile. Log on to the system hosting the WebSphere Application Server Network Deployment deployment manager server. In the Configure WebSphere Application Server panel. 12. 4. each of which hosts a single product function. specify the installation location and configuration information for WebSphere Application Server Network Deployment and associated components. 3. specify information to use to create WebSphere Application Server Network Deployment deployment manager and application server profiles. In the IBM Control Desk configuration operations page. After the installation is complete. click Prepare WebSphere Application Server for configuration. Specify the profile name. You can create additional clusters based on your needs. Select the options to configure the system for clusters and to automate the configuration of IBM HTTP Server. see the Best Practices for System Performance guide. About this task When you configure Control Desk for a cluster environment. Select Configure a new Deployment Manager at this server. 2. You must define and configure clusters on the WebSphere Application Server Network Deployment deployment manager. In the launchpad navigation pane. For performance reasons. Procedure 1. you must first prepare the WebSphere Application Server Network Deployment server and configure application server cluster profiles. cell name. b. Start the configuration program from the Control Desk launchpad. In the Configure Application Server Cluster Profiles panel. select the option to start the IBM Tivoli Process Automation engine configuration utility and click Finish. For detailed performance information. What to do next Use the configuration program to prepare WebSphere Application Server Network Deployment for Control Desk configuration. click Configure Product and then click Launch the Tivoli’s Process Automation Suite configuration program. 90 IBM Control Desk: Installation Guide (IBM WebSphere) . If you want the cluster configuration to include members on other WebSphere Application Server Network Deployment nodes. Preparing WebSphere Application Server Network Deployment and configuring application server cluster profiles You can use the configuration program to prepare WebSphere Application Server Network Deployment v8. you are encouraged to define a minimum of four clusters. a.

e. but you must create at least one. Click New Managed Node to create a managed node. specify information about the directory server host. Specify a name and assign a single product function to the cluster. c.pdf Configuring cluster members on additional WebSphere Application Server Network Deployment nodes You can use the configuration program to configure cluster members on additional WebSphere nodes. you can configure cluster members on additional WebSphere Application Server Network Deployment nodes. Specify a node name and a name for the profile that contains information about the new managed node. In the Apply Deployment Operations panel select all deployment operation options and click Finish. Optional: Click Advanced to access the Deployment Manager Profile Advanced Options page where you can assign custom port values used by the deployment manager profile. f.x. From the WebSphere Managed Node Server Definition page. 7. h. About this task After you have defined clusters on the WebSphere Application Server Network Deployment deployment manager. and assign each a unique product function. but you must have at least one managed node defined. select Web server. From the WebSphere Managed Node Server Definition page. if required. Select the managed node and click New Server. Only one web server can be defined for a managed node. You can create more than one managed node. Repeat the process to create four clusters in total. Specify additional configuration information in the Configure Application Server Advanced Options panel. 8. d. If you chose to use a directory server for WebSphere Application Server Network Deployment administrative security. g.5 is ready for Control Desk. and specify a name for the web server the managed node will use.com/developerworks/community/files/form/anonymous/ api/library/75dbdf46-1a08-429c-9742-bd340d7d1fd3/document/c51d5f5b-dea3- 4043-a81f-d5213fc10063/media/Best%20Practices%20for%20System%20Performance %207. i. You can create as many cluster members as you need.5. select Application server cluster member. Specify the WebSphere Application Server Network Deployment administrator user credentials. Specify a name for the cluster member and select the cluster to associate with the cluster member. Results WebSphere Application Server Network Deployment v8.ibm. Chapter 5. 6. Click New Server. credentials and directory structure from the Configure Administrative Security panel. Deploying in a cluster environment 91 . Click New cluster to create a new cluster. Related information: https://www. j.

6. In the Configure Application Server Cluster Profiles panel. Click Load clusters to load cluster information from the remote WebSphere Application Server Network Deployment deployment manager. but you must have at least one managed node defined. but you must create at least one. 5. You can create more than one managed node. c. g. Log on to the system serving as the WebSphere Application Server Network Deployment nodes. d. click Configure WebSphere Application Server Network Deployment for a new deployment. 3. Specify a node name and a name for the profile that contains information about the new managed node. 4. b. Select the managed node and click New Server. if required. f. In the Configure WebSphere Application Server panel. From the WebSphere Managed Node Server Definition page. Select the options to configure the system for clusters and to automate the configuration of IBM HTTP Server. Specify the WebSphere Application Server Network Deployment administrator user credentials. Specify a name for the cluster member and select the cluster to associate with the cluster member. click Configure Product and then click Launch the Tivoli’s Process Automation Suite configuration program. In the Apply Deployment Operations panel select all deployment operation options and click Finish. About this task To install Control Desk. Specify connection information for the remote WebSphere Application Server Network Deployment deployment manager system. You can create as many cluster members as you need. specify information to use to create additional cluster members on this nodes. a. In the IBM Control Desk configuration operations page. specify the installation location and configuration information for WebSphere Application Server Network Deployment and associated components. select Application server cluster member. Start the configuration program from the Control Desk launchpad. e. Click New Managed Node to create a managed node. Specify additional configuration information in the Configure Application Server Advanced Options panel. Procedure 1. You cannot create a new web server for the cluster because it was defined when the cluster was created on the remote WebSphere Application Server Network Deployment deployment manager h. In the launchpad navigation pane. Repeat the process to create new cluster members and assign them to clusters defined on the remote WebSphere Application Server Network Deployment deployment manager. run the installation program on the Control Desk administrative system. 7. Installing Control Desk Install Control Desk. Select Use an existing Deployment Manager. 92 IBM Control Desk: Installation Guide (IBM WebSphere) . 2.

3. browse to the root directory and run the following command: launchpad64. In the package features panel.Procedure 1. If any errors are reported on this panel. leave all default options checked and click Next. click Next. d. You configure supported languages later in the configuration program. 7. In the Installation Manager installation location panel. accept the license agreement and click Next. Deploying in a cluster environment 93 . 2. review the results of the prerequisite check and click Next. From the Install Product panel. If you install in a non-English environment. Start the launchpad. click Install Product. Chapter 5. you must be logged in as the root user. This package is required for the complete installation of Control Desk including the advanced edition. Log in to the Control Desk administrative workstation. Installation Manager is the installation framework that is used to install Control Desk components. 6. Select a language for the installation session and click OK. b. If you run the installation program from a Linux or UNIX terminal window. c. In the package summary panel. What to do next Use the configuration program to configure Control Desk. you might notice that the environment summary is listed as English. ensure that IBM Maximo for Service Providers is selected. Important: In the package selection panel. 10. 9. 4. In the package installation location panel. browse to the root directory and run the following command: launchpad. After the installation is complete. The installation exits and the configuration program is started automatically. review the information and click Install. a. specify path information for the shared resources directory and the Installation Manager installation directory and click Next. In the package prerequisite validation panel. 5. select IBM Control Desk v7. In the package selection panel.exe. Linux and UNIX From the downloaded installation image.6 and click Install IBM Control Desk components. 8. The shared resources directory is a common workspace directory used by Installation Manager when installing packages. Launch the Control Desk installation program from the launchpad. In the launchpad navigation pane. resolve the issue and click Recheck Status. select the process automation suite package group. specify the path information for the Control Desk installation directory and click Next. Windows From the downloaded installation image. select the option to start the configuration program and click Finish. In the license agreement panel.sh.

and choose whether or not to deploy sample data. In the launchpad navigation pane. You must create at least one application for each function in a cluster. selecting a cluster to assign it to. 8. Create an application for a function managed by a cluster. 94 IBM Control Desk: Installation Guide (IBM WebSphere) . specify information about the DB2 instance to create for Control Desk. In the Apply Deployment Operations panel. specify user interface preferences. specify information about DB2 and the WebSphere Application Server Network Deployment servers that you installed and prepared. 3. add an email address to receive workflow messages. c. select all available deployment operations and click Finish. specify Control Desk installation location. The integration framework function requires JMS. 4. In the Configure Application Security panel. specify information about the DB2 database to create for Control Desk. d. In the Configure the DB2 Database panel. If you choose a security model that includes a directory server.Configuring Control Desk in a cluster environment You can use the Control Desk configuration program to configure Control Desk in a cluster environment after WebSphere Application Server Network Deployment has been configured for clustering. Optional: Change the function associated with the selected cluster. Click Finish. b. the Complete configuration of WebSphere for your product. specify information for the WebSphere Application Server Network Deployment domain manager where the clusters were defined and click Load cluster information. 2. configure JMS for the application. choose a security model for Control Desk. Select languages. click Configure Product. review summary details. Start the configuration program from the Control Desk launchpad. Specify the appearance and navigation features for your product. The reporting function does not support JMS. and selecting the web server to use for the application. a derby database is created to store the information. In the Define Deployment Environment panel. 10. a. Configure the Control Desk help application by supplying a name for the help application. 5. If you choose not to use DB2 to store JMS data. 12. and configure the Control Desk help application. Specify a name for the application and select the cluster name and web server associated with the function. Enter the user names and passwords for users that must be created for Control Desk. click Configure a New Deployment. Click Add application. Do not use the user name as a password value. 6. In the Configure the Application Server panel. In the Configure the DB2 Instance panel. Select the Create and configure the database. and the Deploy the product into a clustered environment options to automatically configure WebSphere Application Server Network Deployment and DB2. 11. 9. specify information about the directory for the virtual member manager. Enable and configure JMS message handling for the application. and click Launch the Tivoli’s Process Automation Suite configuration program. Procedure 1. 7. In the Configure General Product Information panel. In the IBM Control Desk configuration operations page.

xml Procedure 1. and then click Install to start the Control Desk installation program. Click Finish to exit the Control Desk installation program. Option Description Windows launchpad64. Select the components that you want to install.exe Linux or UNIX . Click Install Product. 2015 95 . for example.sh 3. 4. tpaeInstallerRsp20130716105258. You can determine the home directory of the current user by using the following commands. The Control Desk installation program can then be run silently using the response file for input. The response file is generated in the home directory of the user that started the program. Windows set HOMEPATH UNIX echo $HOME The name of the file is tpaeInstallerRspdate_and_time_stamp.xml. When you are satisfied with your installation choices. Select the packages you want to install silently. 6. Open a command prompt and set the record environment variable. Start the Control Desk launchpad. © Copyright IBM Corp. 5. and then starting the installation program through the Control Desk launchpad. Before you begin You can create a silent installation response file by setting the record environment variable./launchpad. click Install to install the packages. Option Description Windows set record=true Linux or UNIX export record=true 2.Chapter 6. You must install the Installation Manager software before you can silently install the Control Desk or related middleware packages Creating silent response files for installation A response file records selections that you make and values that you provide when using the Control Desk installation program. Silent installation The Control Desk silent installation option interacts with the Control Desk installation program by using a command prompt and a response file. and specifying the shared resources and installation directories.

you can use a sample response file and modify it according to your needs. host names. ResponseFile_ICD_Uninstall_Unix. Samples of silent response files File Description launchpad_directory\SilentResponseFiles\ Install Control Desk on Linux and Installer\Unix\ UNIX.xml launchpad_directory\SilentResponseFiles\ Install IBM DB2 on Linux and UNIX. Installer\Unix\ ResponseFile_DB2_Install_Unix.xml launchpad_directory\SilentResponseFiles\ Uninstall Control Desk on Linux and Installer\Unix\ UNIX. ResponseFile_TPAE_WAS_Install_Unix.xml launchpad_directory\SilentResponseFiles\ Uninstall IBM DB2 on Windows.xml launchpad_directory\SilentResponseFiles\ Uninstall base components of Installer\Unix\ WebSphere Application Server on Linux ResponseFile_TPAE_WAS_Uninstall_Unix.xml launchpad_directory\SilentResponseFiles\ Uninstall Control Desk on Windows. Installer\Windows\ ResponseFile_DB2_Install_Windows.xml launchpad_directory\SilentResponseFiles\ Install base components of WebSphere Installer\Windows\ Application Server on Windows. create your own silent response file with the Installation Manager software.xml Windows.xml launchpad_directory\SilentResponseFiles\ Install IBM DB2 on Windows. limit your updates to parameters such as installation locations. If you need to update non-environmental values. Table 9. Sample silent installation response files Instead of using the tpaeInstallerRspdate_and_time_stamp. If you update the values that are used in the sample response files.xml launchpad_directory\SilentResponseFiles\ Uninstall IBM DB2 on Linux and UNIX. Installer\Windows\ ResponseFile_ICD_Install_Windows. Installer\Windows\ ResponseFile_ICD_Uninstall_Windows. such as the main product name or the Installation Manager repository. launchpad_directory\SilentResponseFiles\ Uninstall base components of Installer\Windows\ WebSphere Application Server on ResponseFile_TPAE_WAS_Uninstall_Windows.xml launchpad_directory\SilentResponseFiles\ Install base components of WebSphere Installer\Unix\ Application Server on Linux and UNIX.xml file. ResponseFile_TPAE_WAS_Install_Windows. ResponseFile_ICD_Install_Unix. and user names. Sample files Sample response files are provided in the directory where you extracted the IBM Control Desk launchpad.xml launchpad_directory\SilentResponseFiles\ Install Control Desk on Windows. port numbers. 96 IBM Control Desk: Installation Guide (IBM WebSphere) . Installer\Windows\ ResponseFile_DB2_Uninstall_Windows.xml and UNIX. Installer\Unix\ ResponseFile_DB2_Uninstall_Unix.

Option Description Windows c:\Program Files\IBM\ InstallationManager\eclipse\tools\ imutilsc newpasswordvalue AIX or Linux /opt/IBM/InstallationManager/eclipse/ tools/imutilsc encryptString newpasswordvalue Replace newpasswordvalue with your new plain text password value. you must first install the Installation Manager software. 3. Copy the string in the Encrypted version of the string field. 4. \Install\IM\installer. for example. and then save the file.win64./installc –acceptLicense Results The Installation Manager software is successfully installed on the system. Silently installing the Installation Manager software To install Control Desk and related middleware silently. Chapter 6. 3. Start the Installation Manager silent installation process. You can now silently install Control Desk. use the Installation Manager string encryption utility.ini file in a text editor and update default values. Procedure 1. replace the password value with the copied encrypted password. Optional: Open the silent-install. Change directory to the folder that contains the installation manager program for your operating system. Silent installation 97 . 2. Start the Installation Manager string encryption utility from the command line. About this task The Installation Manager string encryption utility accepts a plain text password value and produces an encrypted version of that password. If you need to update encrypted password values in a response file. You must then copy and paste the encrypted value into the password field of the response file. 2. Procedure 1. Open the response file in a text editor. Option Description Windows installc –acceptLicense Other operating systems . Updating password values in silent response files The Control Desk installation program requires the encryption of password values that are in the response files. Open a command prompt on the system and change to the directory where you unzipped the launchpad files.

If the response file was created on a different system. for example. you can silently install middleware on separate systems. Results The installation proceeds silently with the values that you provided in the response file. /tmp/linuxDB2WASMAM_Log. Ensure that the path values that were defined when the response file was created are still valid for the target system. You can then use another response file to silently install Control Desk on the system that is designated as the administrative workstation. which contains the sample uninstallation response file. for example. you can use one of the sample response files that are provided on the product media and modify the sample file. /SI/tpaeInstallerRsp20130716105258. update the installLocation parameter value. you must also provide a new value for the profile id parameter. Copy the response file that you generated earlier and the Control Desk files to the target system. cd /opt/IBM/InstallationManager/eclipse/tools/. 3. Silently start the Installation Manager program. The -log parameter determines where log files are written. 2. You must include the full path when you specify the response and log files. Procedure 1. for example. For example. Open a command prompt and change to the launchpad_home\ SilentResponseFiles\Installer directory. Before you begin You must complete a successful installation to produce a response file that can be used to silently install Control Desk and related middleware. Silently uninstalling Control Desk and related middleware You can silently uninstall Control Desk and associated middleware based on settings that were used during the installation.Silently installing Control Desk and related middleware You can deploy Control Desk and associated middleware silently to perform an unattended installation based on predefined settings. If you update the value for the installLocation parameter. ensure that all values that are recorded in the response file are valid for the target system. Using different response files as input.xml. you might need to update the repository location parameter values to indicate the correct path for product and middleware installation images.xml. If you are installing the product in a directory different from the path used during creation of the response file. 98 IBM Control Desk: Installation Guide (IBM WebSphere) . imcl -input responsefilename -log logfilename-acceptLicense The -input parameter determines the response file to use. Open a command prompt and change directory to the location of the Installation Manager program that is appropriate for your operating system. Alternatively. Procedure 1.

Silent installation 99 .log. C:\tmp\silent. You can remove the Installation Manager software from the system using the uninstall program.xml. The -input parameter determines the response file to use. uninstallc Table 10. C:\tmp\install_response. The -log parameter determines where log files are written. Update the sample uninstallation response file with values that are used in your environment. You must include the full path when you specify the response and log files. 3. for example. Location of uninstallc command Windows Other operating systems Admin Admin 64-bit C:\ProgramData\IBM\Installation var/ibm/InstallationManager/uninstall Manager\uninstall User User 64-bit C:\Users\User ID\AppData\ User Home/var/ibm/InstallationManager/ Roaming\IBM\Installation uninstall Manager\uninstall Chapter 6. for example. The -acceptLicense parameter is used to accept the license automatically. 4. Silently start the Control Desk uninstallation program.2. imcl -input responsefilename -log logfilename-acceptLicense The default home directory for the imcl command is c:\Program Files\IBM\Installation Manager\eclipse\tools\ on Windows systems and /opt/IBM/InstallationManager/eclipse/ on Linux and UNIX systems.

100 IBM Control Desk: Installation Guide (IBM WebSphere) .

properties. update values as required. Sample files Silent response files are in the launchpad_home\SilentResponseFiles\ConfigTool directory of the product image. you might need to update the WAS.InstallLocation parameter value to indicate the correct path for WebSphere Application Server Network Deployment relative to the target system. 2015 101 . The configuration program can then be run silently using the response file for input. Create a copy of the sample file. and save the file. Procedure 1. you can proceed with silently configuring Control Desk.AutomateConfig value to false. “Silently configuring Control Desk” on page 103 Creating silent response files for middleware configuration You create a response file by modifying one of the sample response files that is provided. set the appropriate property value to false. “Creating a response file for silent Control Desk configuration” on page 102 3. particularly path values. Open the response file in a text editor. Sample silent middleware configuration response files Several sample response files are provided with IBM Control Desk. © Copyright IBM Corp. Ensure that all values listed in the response file are valid for the target system.Chapter 7. for example. Sample response files are in launchpad_home\SilentResponseFiles\ConfigTool. 2. For example. if you do not want to configure WebSphere Application Server Network Deployment on the system. The following tasks are required for silent configuration: 1. Related tasks: “Silently configuring middleware” on page 102 Middleware used with Control Desk can be configured silently by using a configuration response file. “Silently configuring middleware” on page 102 4. “Creating silent response files for middleware configuration” 2. You can use a sample response file and modify it according to your needs. If there are any Control Desk components you do not want to automatically configure. my-cfg-silent-win. you can use the configuration program by using a command prompt and a response file. For example.ND. What to do next After you have completed silent middleware configuration. set the WAS. Silent configuration Using the silent configuration.

particularly path values. Open the response file in a text editor. and save the file. 2. Create a copy of the sample file and name it something appropriate. You can then run the configuration program silently using the response file for input. Open a command prompt and start the configuration program silently.properties Configure Control Desk middleware on Linux.properties Configure Control Desk middleware on Windows. For example. cfg-silent-linux. Ensure that all values listed in the response file are valid for the target system. Before you begin There are several sample response files provided with IBM Control Desk.properties Configure Control Desk middleware on AIX. Copy the response file you created earlier to the target system. cfg-silent-win. 102 IBM Control Desk: Installation Guide (IBM WebSphere) .InstallLocation parameter value to indicate the correct path for WebSphere Application Server Network Deployment relative to the target system. Silently configuring middleware Middleware used with Control Desk can be configured silently by using a configuration response file.properties. you might need to update the WAS. Procedure 1. Table 11. set the WAS. For example. for example. If there are any Control Desk components you do not want to automatically configure. Related tasks: “Silently configuring Control Desk” on page 103 Control Desk can be configured silently by using an configuration response file. The files are in the directory where you uncompressed the product image under the \SilentResponseFile\ConfigTool directory.VmmFullyAutomatedConfig value to false. it uses the data in the response file to configure the product. update values as required. Creating a response file for silent Control Desk configuration You create a response file by modifying one of the sample response files provided according to your needs. About this task When you run the configuration program in silent mode. Procedure 1. my-maximocfg-silent-win. 2. set the appropriate property value to false. Samples of silent response files for middleware File Description cfg-silent-aix. if you do not want to configure WebSphere Application Server Network Deployment virtual member manager on the system.

. [-deploymaximoear] ..... For example: c:\IBM\SMP\ConfigTool\scripts>reconfigurePae. What to do next You can modify the silent configuration response file. -dbvendor DB2 or -j2eevendor WebSphere. In most cases.... [-automatej2eeconfig] ....... C:\tmp\my-cfg-silent.. Open a command prompt and start the configuration program silently..... [-buildears] ..... You must include the full path when you specify the response and log files.. and perform further configuration... The middlewarecomponents parameter indicates which middleware component to configure. for example.. Silently configuring Control Desk Control Desk can be configured silently by using an configuration response file.......properties... for example to see which parameters are available. Note: For information about the reconfigurePae command. [-j2eevendor <WebSphere|WebLogic>] . 2. for example. and then modify the response file to configure IBM Security Directory Server on another server.properties........ You must include the full path when you specify the response files. [-dbvendor <Oracle|DB2|SQLServer>] . copy it to another server........ (16) Deployment of a new configuration .. [-deployhelpear] Chapter 7. reconfigurePae -action deployConfiguration -inputFile responsefilename middlewarecomponents The responsefilename parameter determines the response file to use.......... [-usermanagement <j2ee|mixed> ] .... Copy the response file you created earlier to the target system.. for example............ Silent configuration 103 .... you configure middleware components together. reconfigurePae -action deployMiddlewareConfiguration -inputFile responsefilename The responsefilename parameter determines the response file to use.. execute the command without parameters... Procedure 1. you can use the configuration program to silently configure WebSphere Application Server Network Deployment on one server.. -inputfile <path to input properties file> ...... -action deployConfiguration ... Results The configuration proceeds silently with the values that you provided in the response file.. For example........Run configuration for J 2EE Application Server and Database . Part of the output: . [-automatedbconfig] .. C:\tmp\my-cfg-silent...

..properties. you can use the configuration program to silently configure WebSphere Application Server Network Deployment on one server. Open a command prompt and start the Control Desk unconfiguration program silently.. You must include the full path when you specify the response file.. ...... For example. rename the file to my-uncfg-silent.. [-enableappsecurity] .. and perform further configuration..... Silently remove middleware configuration You can use the same file you used to silently configure middleware to remove the configuration information. About this task Control Desk middleware configuration can be removed silently using the same configuration response file that was used to configure the product previously.... [-enableEnhancedNavigation] ... Procedure 1...... [-db2_english_only] .... copy it to another server... Change to the directory containing the response file used to silently configure previously..... Open the file in a text editor and change the MW. [-enableRestrictivePasswordPolicy] .... 104 IBM Control Desk: Installation Guide (IBM WebSphere) ... C:\tmp\my-uncfg-silent.properties...... [-enableSkin tivoli09|tivoli13|classic] .. 2.. and then modify the response file to configure IBM Security Directory Server on another server. [-deployDemoData] .... You must edit the configuration response file that was used to configure the product previously before it can be used to remove configuration information from the product.. Remove product configuration silently You can use the removeConfiguration action of the reconfigurePae command to remove Control Desk configuration information.. Make a copy of the response file and rename it....Operation property value to unconfigure.. for example. reconfigurePae -action deployMiddlewareConfiguration -inputFile responsefilename The responsefilename parameter determines the response file to use..... 3.. and then save the file.. For example. [-bypassJ2eeValidation] Results The configuration proceeds silently with the values that you provided in the response file. 4... What to do next You can modify the silent configuration response file.

Chapter 7. Silent configuration 105 . Procedure 1. Open a command prompt and change directory to Install_Home\ConfigTool\ scripts. reconfigurePae -action removeConfiguration -dbuser userid -dbpwd password -wasuser userid -waspwd password The -dbuser and -dbpwd parameters are the user ID and password used to configure the database. 3.About this task The removeConfiguration action is used to remove Control Desk configuration from the database and application server that was performed by the configuration tool. Log on to the Control Desk administrative workstation. Start the configuration program silently. The -wasuser and -waspwd parameters are the user ID and password used to configure IBM WebSphere Application Server Network Deployment. This action is equivalent to running the removeJ2EEConfiguration and removeDatabaseConfiguration actions together. 2.

106 IBM Control Desk: Installation Guide (IBM WebSphere)

Chapter 8. Verifying that the installation was successful
After you have exited the 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 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.

Post installation validation utilities are available after the product has been
deployed.

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 \smp\configtools\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.
2. Ensure the JAVA_HOME environment variable is set properly to the location of
a JRE 1.7 installation.
3. To verify product installation, from the administrative workstation, change
directory to ibm\smp\configtool\scripts and run the
installValidation.[sh|bat] command. For either command, use the
parameters in Table 1.

© Copyright IBM Corp. 2015 107

Table 12. 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 -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.
This is the default mode of tracing.
v verbose
In addition to providing normal
progress information, verbose
tracing includes the test class
name, test method name, and
corrective action information.
-confirm You are prompted before each test is
started. You must confirm each test
to be performed. There is no input
for this parameter.
-component You can provide a comma-delimited
list of directories containing the test
objects to limit testing to a specific
set of tests.

These test objects must be located in
the \ibm\smp\HealthValidation\
directory. For the product installation
program, only the CTGIN folder is
provided.
-dbuser Provide the user ID used to access
the database.
-dbpwd Provide the password of the user ID
used to access the database.
-wasuser Provide the WebSphere Application
Server Network Deployment user.
-waspwd Provide the password for the
WebSphere Application Server
Network Deployment user.
-maxuser Provide the Control Desk
administrator user ID. For example,
maxadmin.

108 IBM Control Desk: Installation Guide (IBM WebSphere)

Table 12. Verification utilities parameters (continued)
Program Syntax parameters Input
-maxpwd Provide the password for the Control
Desk administrator user ID.

For example,
installValidation.bat -action validate

Results

The installValidation.bat validation utility results are logged in
ctginstallvalidationtrace00.log. This log is found in the \smp\configtools\logs
directory on the administrative workstation.

Chapter 8. Verifying that the installation was successful 109

110 IBM Control Desk: Installation Guide (IBM WebSphere) .

The product installation program returns a success message if all installation steps. About this task To further verify that the Control Desk installation was completed successfully. or a health check.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMO was successful v CTGIN2253I: buildhelpear.log files for success messages. perform the following verification procedures: Procedure 1. 2015 111 . indicate that the configuration was successful: © Copyright IBM Corp.cmd completed successfully v CTGIN2224I: Deployment of application MAXIMOIEHS was successful v CTGIN2208I: runConfigurationStep completed successfully v CTGIN2370I: The installation finished successfully If you automatically configured WebSphere Application Server Network Deployment certain messages indicate success.log. are successful. including the product log in task. Examine the CTGConfigurationXX. by logging on to the product before exiting the installation. Verifying the installation manually After you exit the Control Desk installation program without errors.log file. you can further verify that the installation completed successfully.) v CTGIN2222I: WebSphere Application Server creation successful v CTGIN2188I: Creation and configuration of service integration bus successfully completed v CTGIN2184I: Creation and configuration of JMS resources successfully completed v CTGIN2310I: Application server security was successfully enabled for process automation engine v CTGIN2253I: buildmaximoear. The following success messages are found in the CTGConfigurationTraceXX. If the health check task is unsuccessful. The installation is manually verified by locating key artifacts and performing a few simple tasks.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. This error is in the install_home\configtools\logs\CTGConfigurationXX. Before you begin The product installation program performs installation verification. The following messages. found in CTGConfigurationTraceXX. a HealthCheckFailed error is thrown for the getUrlContentString function.Chapter 9.

navigate through the GoTo menu to verify that it has been populated with the applications you expect. maxinst. Being able to log in to the product manually is a good indicator that the installation was successful. clear the cache of your browser and try again.log file for the following message. 112 IBM Control Desk: Installation Guide (IBM WebSphere) . Log in to the product and verify that applications are present.*node</symptom> <symptom>CTGIN2232I.*server</symptom> <symptom>CTGIN2238I.*NodeAgent</symptom> <symptom>CTGIN2240I. Once you have logged in.*client</symptom> <symptom>CTGIN2230I.*completed 2.*security</symptom> Search the CTGConfigurationTraceXX. If you experience access problems with the product. You can compare the contents of that panel with a listing of what was installed on the system by using the configuration tool and selecting the update database task. Compare the packages chosen for installation with the packages that were installed. The resulting list matches the packages listed in the Package Summary panel. The Package Summary panel of the Control Desk installation program provides a summary of all the packages to be installed. <symptom>CTGIN2228I. which indicates that the maxinst task completed successfully: CTGIN2079I. 3.

if the HTTPOnly attribute is set for session cookies. MXServer. 3. the problem can often be attributed to a security setting within IBM WebSphere Application Server Network Deployment. Configuring the HTTPOnly attribute If applications do not start from the user interface in IBM WebSphere Application Server Network Deployment 8 environments. From the Configuration panel. Click Save and then click OK. 2. Under General properties. 10. 4. In particular. under Container Settings. Click the application server created for the product you want to update. © Copyright IBM Corp. From the navigation pane. browse to Servers > Server Types > WebSphere spplication servers. Click the label only. 6. 2015 113 . 9.Chapter 10. and then click OK. for example. click Enable cookies. Procedure 1. the applications are not accessible. and select the application server required. 5. Navigate back to the Application servers table. Click Restart to restart the application server in order to apply the changes made. save the changes. Log on to the administrative console for IBM WebSphere Application Server Network Deployment. Clear the Set session cookies to HTTPOnly check box to help prevent cross-site scripting attacks. Click OK. Do not clear this option. 8. click Session management. 7.

114 IBM Control Desk: Installation Guide (IBM WebSphere) .

if you receive an error credited to the J2EE server. 2015 115 . node agent. Installation and configuration programs log information Log files generated by the Control Desk and configuration programs can provide details on completed and configuration tasks and any errors that might occur. If you use the LogZipper utility. Log files for the Control Desk installation program are found on the system where it is run. © Copyright IBM Corp. Log file directories Log file directory C:\ProgramData\IBM\Installation Manager\logs /var/ibm/InstallationManager/logs C:\IBM\SMP\ConfigTool\logs opt/IBM/SMP/ConfigTool/logs In addition. When engaging IBM product support services.zip. and WebSphere Application Server application server. examine the logs in the log directories for the deployment manager.Chapter 11. The LogZipper utility provided in the install_home\ configtool\scripts directory can be used for this task. regardless of which components you choose to install. Table 13. Control Desk installation and configuration programs log locations Control Desk and associated middleware is installed through Installation Manager. The log files of Installation Manager are common to any installation. all relevant log files are archived in install_home/configtool/debug/ YYYYMMDD_hhmmss. be prepared to provide these log files in an archive file.

116 IBM Control Desk: Installation Guide (IBM WebSphere) .

Installation prerequisites Before installing. The data is also used to generate reports. and decision support. creating a central repository for enterprise IT asset management. reporting. Note: Integration Composer is used to import hardware and software inventory data from a discovery tool database into the Deployed Asset. you can optionally install or upgrade Integration Composer. network devices. Installing Integration Composer After you have successfully installed the IBM Control Desk components. Remove any software that adversely affects the InstallAnywhere installation program. This inventory data is imported from a discovery or system management tool database into the Control Desk database tables for deployed assets or configuration items. the integration framework Hardware and software requirements Ensure that your system meets the hardware and software requirements for Integration Composer. For information about the hardware and software requirements. an integration tool that imports IT data into the IBM Control Desk database. you must have the IBM Java Software Development Kit prerequisite for Integration Composer on your system. and network printers deployed in an enterprise and records information about the hardware and software it finds there. an enterprise can aggregate data collected by external discovery tools and integrate it into the Control Desk database. 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 Control Desk database. see the Integration Composer hardware and software requirements page in the Control Desk wiki. With Integration Composer. You can install Integration Composer from IBM Control Desk using the launchpad. or (for the purposes of asset initialization) Asset tables in the Control Desk database. 2015 117 . The import or export of data into or out of other tables within the Control Desk database is accomplished using a different tool. © Copyright IBM Corp.Chapter 12. Integration Composer overview Integration Composer transforms and imports inventory data about deployed hardware and software. Actual CI. The Control Desk database is the repository used by Control Desk. You can also install using the setup on Windows operating systems or in console mode from the command line on UNIX operating systems. a discovery tool scans computers. To collect the data about deployed assets or configuration items. You can view imported data from various applications on your system.

make sure you have on hand the information on the target (Maximo) database. Before you begin Make sure that you have up to 70 MB of free space for the installation directory.bat The default Integration Composer installation directory for Windows operating systems is C:\Integration Composer. the problem is not specific to Integration Composer. Results When the installation completes successfully. be sure the PATH environment variable includes the location of the Java Virtual Machine (for example. such as pcAnywhere Use of these software programs affects the ability of InstallAnywhere to install programs. install on a UNIX operating system in console mode. you can access Integration Composer as follows: Windows From the Start menu. Java70). Use the launchpad to install Integration Composer on Windows or UNIX operating systems. The installation or upgrade runs on JRE 1. or by entering the command: itic_installation_dir\ bin\startFusion. UNIX By entering the command: itic_installation_dir/bin/startFusion. UNIX On UNIX-based operating systems. Installing Integration Composer using the launchpad Windows UNIX For IBM Control Desk installations. [Installation only] Before beginning your installation. Or.sh The default Integration Composer installation directory for UNIX operating systems is /home/user/Integration_Composer. The IBM Java SDK is provided with the product images. Installing Integration Composer You can install Integration Composer for use with Control Desk from the launchpad or directly from the Windows setup file. 118 IBM Control Desk: Installation Guide (IBM WebSphere) . If more than one JRE is installed on the computer. however. so it must be set as the system's Java virtual machine (JVM).7. IBM Java SDK 7. the PATH and CLASSPATH system variables must indicate JRE 1. such as Norton Antivirus or Symantec Client Firewall v Dell OpenManage v Search software.0 for the appropriate operating system is an installation prerequisite that must be present on the Integration Composer computer.7. 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. the recommended way to install Integration Composer is from the launchpad.

6. 7. the launchpad. select youControl Desk database type. The Database Login Information window is where you define the parameters for connecting to theControl Desk database. The fields displayed in this window vary slightly. 3. you might have to start the launchpad manually by running the launchpad. IBM Java SDK 7. which is located in the root directory of the launchpad product image.) Note: Confirm that the java -version command returns 1.0 with JRE 1. type login specifications for the database and click Next. In the Choose IBM SDK Location window. In the Database Type window.exe command runs automatically. enter the directory where IBM Java SDK 7.7 before starting the installation. review the information and click Next. 4. depending on the type of database you chose in the previous step. 2. The Control Desk database is where the Integration Composer repository is installed.0 is located and click Next. Installing Integration Composer 119 . accept the default location or enter a file path to specify where you want to install the product and click Next. From the launchpad. If you are installing on a UNIX operating system. In the Introduction window. 8. Click Next. select New Install and click Next. select your language and click OK. Table 14. Chapter 12.7 is provided on the product images. this is the session identifier (SID) for the database. On the Database Login Information window. use the values entered in these fields to define connection parameters for the Control Desk database. Start the launchpad on the server where you install Integration Composer. launch the Integration Composer installation program by clicking the link under Install IBM Tivoli Integration Composer. Login specifications for the Control Desk database Field Description Database Server Name Name of the server on which the Control Desk database resides Port Number Port number of the server on which the Control Desk database resides Database Name (SID) For Oracle databases. The following table defines the fields that the installation program displays for the supported databases. In the IBM Tivoli Integration Composer window. the database or instance Database Name For SQL Server or IBM databases. The Database Login Information window is displayed. In the Choose Install Folder window. 5. 9. [UNIX only] In the Select Install Type window. this is simply the name of the database Database Username Valid user name for signing in to the Control Desk database Database/Schema Owner Database or schema owner Tip: Make note of the values that you specified here. when you launch Integration Composer. Later. IBM DB2 is the default. that is. (On Windows operating systems.sh command.Procedure 1.

setup. In the Software Class Name field. Use the setup. disable software updates If you select this option.bin command to start the upgrade process: setup. /opt/ibm/java-i386-60/jre/ bin:$PATH): 120 IBM Control Desk: Installation Guide (IBM WebSphere) . This option is preferred. In the Installation Complete window. About this task The Integration Composer files are located in either the \ITIC or \Install\ITIC directory on the product image. 11. The Software Class name is used to identify the class that you do not want to update based on the choice you made. the Installation Complete window is displayed.bin. In the Preinstallation Summary window. Installing Integration Composer 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.bin ← setup. 10. Sign on to the server as an administrator (for example. In the Deployed Assets target schema.exe The steps for installing Integration Composer on a UNIX-based operating system follow. On the Update Software Instances window. as root). 12. enter the following commands (where JRE_location is the path for your IBM JRE.7 to the path. Integration Composer inserts or deletes software records but does not update software records. Save the binary Integration Composer installation file. To add JRE 1. click Done. Before you begin Make sure you have up to 70 MB of free space for the installation directory. select one of the following options and click Next: Yes. 3. The Installing Integration Composer progress window displays during installation.7 is in your system path. When installing is finished. it is recommended to accept the default value Software. Integration Composer updates existing software records. Procedure 1. when Integration Composer imports data into theControl Desk database. when Integration Composer imports data into the Control Desk database. don't disable software updates If you select this option. Make sure JRE 1. for example. the name is Software. No. 2. on the server where you intend to install Integration Composer. click Install.

type each login specification for the database. Installing Integration Composer 121 .7 before starting the installation. indicate your Maximo database type. Run the Integration Composer installation program in console mode by entering the following command at the shell prompt: sh . this Database Name is simply the name of the database Database Username Valid user name for signing in to the target database Database/Schema Owner Database or schema owner 13. 5. pressing Enter after each entry to advance to the next specification. JAVA_HOME=JRE_location export JAVA_HOME PATH=$JAVA_HOME:$PATH export PATH 4. 7.0 with JRE 1. In the Database Login Information step. 12. specify where you want to install Integration Composer. depending on the type of database you chose in the previous step.7 is provided on the product images. The following table defines the fields that the installation program displays for the supported databases. In the Choose Locale step. This Database Login Information step is where you define the parameters for connecting to the Maximo database./setup. press Enter to accept the default (New Install). 10.bin file. v Type a different file path for the location and press Enter. Enter the following command to make the binary installation file executable: chmod +x setup. Press Enter. specify the file path where IBM Java SDK 7. Navigate to the location where you saved the setup.bin -i console In console mode. 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. The fields displayed in this step vary slightly. In the IBM SDK Location step.0 is installed by doing one of the following: v Accept the default location and press Enter. this is the session identifier (SID) for the database. In the Introduction step. The Maximo database is where the Integration Composer repository is installed. In the Select Install Type step.bin 6. 11. 8. In the Choose Install Folder step. In the Database Type step. The Database Login Information step is displayed. you are prompted to enter information line by line. 9. Chapter 12. IBM Java SDK 7. that is. review the Introduction information and press Enter. the database instance or For SQL Server or databases provided by IBM. type the number of your locale from the list of locales and press Enter. Note: Confirm that the java -version command returns 1.

Upgrading Integration Composer using the launchpad Windows UNIX For Control Desk installations. In the Choose Internet Browser File step.2. type a number to select one of the following options and press Enter: v Yes. Use the launchpad to upgrade Integration Composer on Windows or UNIX operating systems.2. disable software updates If you select this option. accept the default and press Enter.2. On Windows operating systems. Results When the upgrade completes successfully. This option is preferred for performance reasons. and 7.2. v No. the installation program automatically checks for a valid current release prior to upgrading.1. when Integration Composer imports data into the target database. About this task This upgrade is for any Integration Composer 7. when Integration Composer imports data into the target database. don't disable software updates If you select this option. when you launch Integration Composer. press Enter. Tip: Make note of the values that you specified here.1 or later release.2. 18. In the Preinstallation Summary step. In the Software Class Name step. including Integration Composer 7. you can access Integration Composer as follows: Windows From the Start menu.2. 17. When you see Installation Complete. You can also upgrade on Windows from the setup file or on a UNIX operating system in console mode. review the installation details and press Enter to install Integration Composer. Later. 122 IBM Control Desk: Installation Guide (IBM WebSphere) . Integration Composer inserts or deletes software records but does not update software records. use the values entered in these fields to define connection parameters for the target data source. The installation program does not permit upgrades from earlier releases. 15. or by entering the command: itic_installation_dir\ bin\startFusion. 16. the recommended way to upgrade Integration Composer is from the launchpad.sh The default Integration Composer installation directory for UNIX operating systems is /home/user/Integration_Composer. 14.bat The default Integration Composer installation directory for Windows operating systems is C:\Integration Composer. The installation is complete. 7. In the Update Software Instances step.1. Upgrading Integration Composer You can upgrade Integration Composer for use with IBM Control Desk from the launchpad. specify a browser and press Enter. Integration Composer updates existing software records. UNIX By entering the command: itic_installation_dir/bin/startFusion.

the nameReconciliation. Click Next. Start the launchpad on the server where you upgrade Integration Composer. 9. If you are upgrading on a UNIX operating system. In the Installation Complete window. the Installation Complete window is displayed. Before you begin Back up your Integration Composer data\dataschema and data\mappings directories before upgrading. launch the Integration Composer upgrade program by clicking the link under Install IBM Tivoli Integration Composer. see the IBM Tivoli Integration Composer Administrator Guide. [UNIX only] In the Select Install Type window. select Upgrade and click Next. you might have to start the launchpad manually by running the launchpad. and the removed file is replaced with the dis. In the Choose Install Folder window.0 with JRE 1.logging. The Installing Integration Composer progress window displays during upgrade. 7.properties file. Note: Confirm that the java -version command returns 1.logging. 8.properties file is removed from the properties subdirectory in the Integration Composer installation directory. For additional details about these properties files. Read the information in the Introduction window and click OK. Click Next.properties file. On Windows operating systems. As a result.sh command in the root directory of the launchpad image.exe command runs automatically. review the upgrade details and click Install. 6. select your language and click OK.logging. In the IBM Tivoli Integration Composer window. On the Preinstallation Summary window. 2.0 is located. In the Choose IBM SDK Location window. enter the directory where IBM Java SDK 7.logging. When the upgrade is complete. accept the default location or enter a file path to specify where you want to upgrade the product. Make sure that you have up to 70 MB of free space for the installation directory.7 before starting the upgrade. Attention: The Naming and Reconciliation Service (NRS) was upgraded to Data Integration Services (DIS). Chapter 12. Installing Integration Composer 123 . any customizations that were made to the original nameReconciliation. As part of this Integration Composer installation. Before upgrading to this release of Integration Composer. IBM Java SDK 7. click Done. 3. 4. Procedure 1. Upgrading Integration Composer on UNIX operating systems in console mode UNIX Complete the procedure to upgrade Integration Composer on a UNIX computer in console (command line) mode.7 is provided in the product image. the launchpad.properties file are lost. 5. note your current customization information if you plan to to reuse any of that information in the new dis. From the launchpad.

properties file.properties file is removed from the properties subdirectory in the Integration Composer installation directory.bin.7 is in your system path. enter the following commands (where JRE_location is the path for your IBM JRE. as root). setup. Save the binary Integration Composer installation file. As part of this installation. the nameReconciliation. Run the Integration Composer installation program in console mode by entering the following command at the shell prompt: sh . 3.7 to the path. /opt/ibm/java-i386-60/jre/ bin:$PATH): JAVA_HOME=JRE_location export JAVA_HOME PATH=$JAVA_HOME:$PATH export PATH 4.exe To upgrade Integration Composer on a UNIX-based operating system. 2. About this task The Integration Composer files are located in either the \ITIC or \Install\ITIC directory of the product image. Before installing this release of Integration Composer./setup. Procedure 1. note your current customization information if you plan to to reuse any of that information in the new dis. Back up your Integration Composer data\dataschema and data\mappings directories before upgrading. As a result. and the removed file is replaced with the dis. for example. Attention: For this release.logging. Navigate to the location where you saved the setup.bin command to start the upgrade process: setup. any customizations that were made to the original nameReconciliation. Use the setup. on the server where you intend to install Integration Composer. the Naming and Reconciliation Service (NRS) was upgraded to Data Integration Services (DIS). Before you begin Upgrading Integration Composer upgrades the program to the latest version.7 before starting the upgrade. Enter the following command to make the binary installation file executable: chmod +x setup. Note: Confirm that the java -version command returns 1.bin ← setup. see the IBM Tivoli Integration Composer Administrator Guide. you are prompted to enter information line by line.bin file. Make sure you have up to 70 MB of free space for the installation directory.properties file. You do not need to remove the previous version first. To add JRE 1.logging.bin 6. For additional details about these properties files.properties file are lost.bin -i console In console mode. 5. Sign on to the server as an administrator (for example. complete the following steps. Make sure JRE 1.logging. IBM Java SDK 7. 124 IBM Control Desk: Installation Guide (IBM WebSphere) .logging.0 with JRE 1.7 is provided.

In the Preinstallation Summary step. 3. 13.sh. 12. specify the file path where IBM Java SDK 7. This verification task is to ensure that.bat UNIX Enter the command: . In the Introduction step. enter the command: startFusion. review the installation details and press Enter to install Integration Composer./startFusion. Integration Composer was successfully installed. 4. These properties specify database-related properties and application properties. after you have installed or upgraded Integration Composer. select Start > Programs > IBM Tivoli > Integration Composer > IBM Tivoli Integration Composer or from the command line. In the Installation Complete step. Confirming the installation You can verify that your Integration Composer installation or upgrade is successful. In the Select Install Type step. Post-installation tasks You can verify that Integration Composer is configured correctly after you install or upgrade. 9.properties file are correct. review the Introduction information and press Enter. In the IBM SDK Location step. Open the Integration Composer application by doing one of the following things: Windows From the Windows Start menu. Sign in to the Integration Composer application using the database (or schema owner) user name and password that you supplied during the installation. 7. 11. 8.0 is installed. check that the number in the Version field is 7. press Enter. On the About Integration Composer window.0. 2. type the number for the Upgrade selection and press Enter. This indicates that you want to upgrade Integration Composer from the previous release. enter the number of your locale from the list and press Enter. Installing Integration Composer 125 . Procedure 1. In the Choose Locale step. From the Help menu in the Integration Composer main window.6. select About. type the location (absolute path) where Integration Composer is currently installed and press Enter. Or just press Enter to accept the displayed path. In the Choose Install Folder step. Verifying the settings in the Integration Composer fusion.properties file The fusion.properties file is the properties file for Integration Composer. 10. critical property settings in the fusion. The installation is complete. Chapter 12. If this version number is displayed.

db. itic_install_dir. By default. Procedure 1. 2. Integration Composer recommends that DIS/NRS is installed and enabled.properties file is located in itic_install_dir\data\properties\fusion. the DIS GUID. So. Integration Composer is configured to use this component. The NRS property is enabled (set to true) by default. be sure to set the NRS property to false so that Integration Composer runs successfully. Integration Composer does 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. for example.enable=false Naming and Reconciliation Service (NRS). which is part of Data Integration Services (DIS).nrs.fusion. 3. In the IBM Tivoli Integration Composer Mapping Execution Properties section.properties. to a deployed asset or actual CI based on defined naming rules. a product that uses Integration Composer to import deployed assets and actual CIs. Use the following table as a guide: Property Description Value mxe.properties file in your Integration Composer installation directory. requires DIS/NRS to perform automated linking of their authorized asset and CI counterparts. dbo. run DIS/NRS and set the NRS property in the fusion.properties file to true.schemaowner Database schema Enter the appropriate schema for your database. which assigns a globally unique identifier.fusion.nrs. Locate the Integration Composer fusion. owner 126 IBM Control Desk: Installation Guide (IBM WebSphere) . Before you begin The Integration Composer fusion.mapping. verify that NRS is enabled (set to true) if you are using NRS: mxe. if you do not use NRS. verify that the database schema owner. JDBC driver specification. In the Database Related Properties section. If you use IBM Control Desk. However. 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.mapping.enable=true or disabled (set to false) if you are not using NRS: mxe. and JDBC URL specification are correct. IBM Control Desk.

the memory allocation in the startFusion file is correct.integratedSecurity=false. using the Microsoft JDBC driver for your SQL Server is recommended.user Database user login name Note: Windows For Windows operating systems. for example: specification IBM DB2: com.sqlserver.url JDBC database URL This varies depending on the database. after you have installed or upgraded Integration Composer. Changing the memory allocation in the startFusion file (optional) The startFusion file.0 or higher): jdbc:inetdae7:host_name:host_port?database=database_name Note: If you are upgrading from a previous release and already have this deprecated driver. Installing Integration Composer 127 .db. Before you begin Perform this optional task only if the Integration Composer graphical user interface does not start as expected. in the future.jdbc. Chapter 12.OracleDriver Microsoft JDBC driver (SqlServer): com. 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. This verification task is to ensure that.Property Description Value mxe.inet.driver.db. named startFusion.sh in UNIX-based operating systems.driver JDBC driver This varies depending on the database.TdsDriver Note: If you are upgrading from a previous release and already have this deprecated driver. i-net Opta driver (SqlServer 7. using the Microsoft JDBC driver for your SQL Server is recommended.databaseName= database_name.jdbc. mxe. the browser always defaults to Microsoft Windows Explorer. However. in the future. you can still use it for Microsoft SQL Server support.jcc.bat in Windows operating systems or startFusion. is the startup file for the Integration Composer graphical user interface.db.tds.DB2Driver Oracle JDBC Thin driver: oracle. mxe. you can still use it for Microsoft SQL Server support.SQLServerDriver i-net Opta driver (SqlServer): com. However.ibm.microsoft.db2.

This verification task is to ensure that. you can also increase the size of virtual memory to about 80 percent of the size of physical memory that you have. as follows: Windows itic_install_dir\bin\startFusion.exe command in the startFusion file.sh Integration Composer requires at least 3 GB of physical RAM. Procedure If the Integration Composer graphical user interface does not start.sh in UNIX-based operating systems. named executeMapping. is the Integration Composer script for running a mapping. as follows: Windows itic_install_dir\bin\executeMapping.bat in Windows operating systems or executeMapping. About this task The Integration Composer executeMapping file is located in the Windows and UNIX-based installation directories. but.bat UNIX itic_install_dir/bin/executeMapping. or if you just upgraded and had increased the amount of memory allocated to Integration Composer in your previously installed version. If you have this allocated. the memory allocation in the executeMapping file is correct. you can also increase the size of virtual memory to about 80 percent of the size of physical memory that you have. after you have installed Integration Composer. If you have this allocated. check the memory setting for the start javaw. Before you begin Perform this optional task only if the Integration Composer mapping does not run. Example For example. you can leave it as it is. if you have more than 3 GB. but. if you have more than 3 GB. About this task The Integration Composer startFusion file is located in the Windows and UNIX installation directories.bat UNIX itic_install_dir/bin/startfusion. change -Xmx1536M to -Xmx3000M. 128 IBM Control Desk: Installation Guide (IBM WebSphere) . Changing the memory allocation in the executeMapping file (optional) The executeMapping file.sh Integration Composer requires at least 3 GB of physical RAM. you can leave it as it is.

Click Uninstall. you can delete these files manually. 3. do one of the following options: v If you installed the Integration Composer using the X Window System application. The removal of Integration Composer is complete. If you do not need these files for other purposes. Procedure v If the Integration Composer mapping does not run. change -Xmx1536M to -Xmx3000M v [Upgrade only] If you previously increased the amount of memory allocated to Integration Composer imports. for example. where Integration Composer was installed. For example.exe. type: sh . such as mapping files or schema files that the user imported. 2. itic_install_dir\Uninstall_Integration_Composer. Procedure 1. If you have to increase the amount of memory assigned. 4. edit the executeMapping file and change the –Xmx parameter in the java command. Procedure 1. edit the executeMapping file and change the –Xmx parameter in the java command. To do so. For example: change -Xmx1536M to -Xmx3000M Uninstalling Integration Composer You can remove Integration Composer from Microsoft Windows and UNIX-based operating systems. some files might remain in the installation directory./Uninstall_IBM_Tivoli_Integration_Composer v If you installed the Integration Composer using console mode. as backups or to reconfigure schemas or mappings. Installing Integration Composer 129 . What to do next When the utility removes Integration Composer. When the uninstallation is complete. Go to the uninstall folder. Uninstalling Integration Composer on Windows operating systems Windows You can remove Integration Composer from a Windows operating system. These files might be files that someone manually put into the directory. click Done. In the uninstall folder./Uninstall_IBM_Tivoli_Integration_Composer -i console Chapter 12. Navigate to the uninstall folder: installation_dir\ Uninstall_Integration_Composer 2. type: sh . check the memory setting for the java command in the executeMapping file. Uninstalling Integration Composer on UNIX operating systems UNIX Use the procedure described here to remove Integration Composer from a UNIX-based operating system. Double-click the uninstall file Uninstall_Integration_Composer. or they might be log files that Integration Composer created. verify that your memory settings have not changed.

What to do next When the utility removes Integration Composer. 130 IBM Control Desk: Installation Guide (IBM WebSphere) . These files might be files that someone manually put into the directory. you can delete these files manually. some files might remain in the installation directory. If you do not need these files for other purposes. 3. Use the console mode for the following steps. such as mapping files or schema files that the user imported. you are returned to the command prompt. or they might be log files that Integration Composer created. The Uninstalling progress bar is displayed as the uninstall utility removes the application. Press Enter to initiate the command from the previous step. When the removal of Integration Composer is finished. as backups or to reconfigure schemas or mappings. for example.

About this task If you are installing the Entry edition of Control Desk.Chapter 13. Choose the installation folder and where to install icons. Install it on a Windows workstation that can connect to your Control Desk server. the image must be accessible from the workstation where you want to install the Deployer's Workbench. In either case. click Install the Product. 6. you do not need to install the Deployer's Workbench. When the Deployer's Workbench screen appears. 5. Installing the Deployer's Workbench The Deployer's Workbench is a separately installed. v Use the native installer: navigate to the DW directory and run install. 3. Eclipse-based workbench that is the best-practice tool for creating authorized CI spaces. Procedure 1. Review the information and click Next. and click Install Deployer's Workbench.exe. 2015 131 . 2. Start the Deployer's Workbench installer in one of the following ways: v Start the Control Desk launchpad. 4. Click Install. click Done to exit the installer. choose a language and click OK. © Copyright IBM Corp. You can install the Deployer's Workbench using either the Control Desk launchpad or the native installer. You might see a message saying that Install Anywhere is preparing to install. After the installation is complete.

132 IBM Control Desk: Installation Guide (IBM WebSphere) .

For more information. 2. Accessing product documentation Accessing the Control Desk documentation in the IBM Knowledge Center and the online help.ibm.Chapter 14. see https://www. all management and deployment operations. Important: The deployment manager (a component of WebSphere Application Server Network Deployment) allows for remote management and deployment operations. If you need to support multiple languages for Control Desk.wss?uid=swg21508594. 2015 133 . Restarting enables the full function of the IBM Knowledge Center and online help. Stop the deployment manager by running the following command: c:\Program Files\IBM\WebSphere\AppServer\profiles\<dmgr profile>\bin\stopManager -username wasadmin -password <password> 2. © Copyright IBM Corp.com/support/ docview. To be able to access the product documentation system with the product. While the deployment manager is stopped. Start the Control Desk launchpad. you must first install it using the configuration program. Procedure 1. you optionally install the help information for other languages. About this task Multi-language help information for Control Desk is available on Fix Central as a fix pack that includes multiple language plug-ins. complete the following steps after you install Control Desk: 1. Installing help in a new language Help information is available in multiple languages. Download the fix pack that contains the multi-language Control Desk documentation from the Fix Central support site to a temporary location on the administrative workstation. Before you can use multi-language help information in Control Desk. including outside of Control Desk. The fix pack must be downloaded from Fix Central and then applied with the configuration program. Click Configure Product. Post-installation tasks You must perform several post-installation tasks to complete the Control Desk deployment. Start the deployment manager by running the following command: c:\Program Files\IBM\WebSphere\AppServer\profiles\<dmgr profile>\bin\startManager If you manually configured the application server after you ran the product installation program. are stopped. 3. you must set the property for the product documentation server. Important: The WebSphere Application Server deployment manager must be restarted after the installation of Control Desk.

In the Live Refresh window. If you selected the Deploy the product help EAR to the application server option. the help information EAR file is deployed to the application server. From the Common Actions menu. but not deployed to the application server. d. you must complete several data configuration tasks before you use Control Desk. a.smtp. Procedure 1. configure the SMTP server to send users email notifications of system events. i. Log in to Control Desk by entering the user name maxadmin and the password that you specified during the installation. c. k. h. Configuring initial data After you successfully install and configure Control Desk components. select Financial > Currency Codes 134 IBM Control Desk: Installation Guide (IBM WebSphere) . and then click Launch the Tivoli's Process Automation Suite configuration program. specify the SMTP host name. use the filter feature to search for the mxe. From the Go To menu.host check box. If you didn't set the SMTP server by using the Configuration tool. From the Common Actions menu. use the filter feature to search for and expand the mail. click Add Additional Help Plug-ins. select System Configuration > Platform Configuration > System Properties. If you do not select this option. Select the location of the Control Desk installation you want to configure. Before you begin v Create security groups and add users to the security groups.adminEmail record check box. 6. 3. f. see the System properties information.smtp. e. v If you are using a directory server as part of your deployment. 5. ensure that the user names are created in your LDAP repository. In the Global Properties table window. From the Go To menu. click OK. j. In the Live Refresh window. v To ensure that you have the accounting information that you need. the Control Desk help information EAR file is rebuilt.adminEmail property and in the Global Value field. 2. specify your email address. Optional: Select Deploy the product help EAR to the application server to install the updated help information to Control Desk now. 7. Select the mxe. 4. Expand the mxe. consult the financial department of your organization. 8. click Live Refresh.host property. a. To learn about the range of system properties in Control Desk. click Live Refresh.adminEmail property. Click Browse to locate the fix pack file that you downloaded. click OK. In the Global Properties table window. g. From the Configuration Actions page. Define a currency code. Select the mail. Click Finish to rebuild the Control Desk help information EAR file. In the Global Value field. b.

From the More Actions menu. Specify a site name. Create a general ledger account. Select Turn Admin Mode ON and click OK. Define item sets and company sets. enter IT Comps. select Manage Admin Mode. In the Default Item Status field. select Administration > Sets. c. c. b. Specify a component name. For example. enter MYCOMPONENT. For example. enter IT Items. Specify the base currency that you defined in step 3. Chapter 14. b. For example. From the More Actions menu. For example. specify COMPANY. For example. Select Turn Admin Mode OFF and click OK. Click New Row. a. For example. c. Specify a length for the component. select Administration > Organizations. In the Type field. Click Save Sets. d. select Apply Configuration Changes. From the More Actions menu. enter 5. Specify an item set name. g. d. Specify a type for the component. c. i. This task takes several minutes to complete. Click Save Organization. From the More Actions menu. g. e. In the Organizations table window. 6. e. set the status to PENDING. g. d. b. select Financial > Chart of Accounts. select Alphanumeric. Post-installation tasks 135 . Click the Sites tab and select New Row under the Sites table window. b. 4. Ensure that the status To Be Changed does not appear in the status column of the listed objects. a. Click New Row. Specify the item set and the company set that you defined in step 4. e. Click New Row and specify a currency code and a description. d. Click New Row. You can click Refresh Status to view the progress. h. e. Create an organization. select GL Account Configuration. specify ITEM. click New Organization. enter EAGLENA. cron tasks fail. and enter a long description. b. From the Go To menu. For example. select your organization. c. 7. h. In the Type field. Apply changes to the database. For example. 5. From the toolbar. a. f. select System Configuration > Platform Configuration > Database Configuration. Specify a company set name. 8. Click OK. f. a. Specify an organization name. a. From the Go To menu. Click Save Currency. If you do not turn off Admin Mode. enter Factory01 and enter a long description. enter USD for United States of America Dollar. select Manage Admin Mode. b. From the Go To menu. f. Create a general ledger account component. From the Go To menu.

Specify a GL Component value and a description. g. select WORKORDER. c. Click New Row. AP Suspense Account. you can select Authorize Group to Change All GL Component Types. h. a. Select the group that provides authorization. Find your organization and select the record. In the Work Order Class field. You can specify the same account number in each field. and AP Control Account fields. From the Go To menu. Work types denote the importance of the work task. Click Save Group. enter MAJOR. c. l. c. d. select Administration > Organizations. and then click OK. a. For each GL Component that is listed. select Financials > Chart of Accounts. Specify a Work Type. f. f. b. select Administration > Organizations. In the Components table window. c. click New Row. 136 IBM Control Desk: Installation Guide (IBM WebSphere) . c. Authorize a security group to modify a general ledger component type. g. d. d. In the Storeroom Site for Self-Service Requisitions field. e. As a shortcut. Create a default insert site. Define work types. Click Save Organization. select Security > Users. d. From the More Actions menu. Select your organization and from the More Actions menu. b. 11. select Company-Related Accounts. From the Go To menu. From the More Actions menu. k. select FINANCE. 10. a. Update the company-related accounts. j. Click the GL Components tab. For example. e. a. select GL Component Maintenance. i. select Update Database and click OK. Click OK. Specify a General Ledger Account and click Save GL Account. In the GL Accounts table window. From the More Actions menu. Click Save User. From the Go To menu. specify the same site name. e. In the Default Insert Site field. select Security > Security Groups. e. e. Select Active. select the Authorized check box. d. 9. In the Clearing Account field. specify the general ledger account that you created. 12. b. Set the Start Status to In Progress. From the Go To menu. f. For example. From the Go To menu. Find maxadmin and select the record. Click New Row and specify the company type Courier. select the component that you entered in step 6 and click New Row. b. specify the site name that you created in step 5. Find your organization and select the record. select Work Order Options > Work Type. Enter an account number in the RBNI Account.

4.birt. Before you begin When multiple languages are enabled in Control Desk applications. 2.tempfolder=c:\tempReport\BIRT-TEMP to Generic JVM Argument. Click OK and click Save Organization.report.tempfolder. Post-installation tasks 137 . you must generate request pages in each of the enabled languages. Before you begin The mxe. Related information: Integrating data with external applications System properties Before working with BIRT reports Before running any reports. Restart the server. set up JVM System Properties mxe. 3. 5. Log in as a maxadmin user. Chapter 14.report. Generating XML request pages Perform this task after you install Control Desk and before you run request pages. Add -Dmxe.birt. Click Java Virtual Machine under Additional Properties. 6. You must complete this procedure for every language that is enabled on your system. and then click Save.tempfolder in JVM system Properties in the BIRT report engine. 7. enter SIG to represent a significant change.birt.tempfolder property specifies the location of a temporary folder on the reporting server for BIRT. click the server name where you have deployed Control Desk.birt. h. Click New Row and repeat steps f-i to create a CHANGE work order class with a different work type.report. For example. j. Go to Servers > Application servers. Go to Process Definition under Server Infrastructure. Set the Complete Status to Completed. For example. Procedure 1. Log in to WebSphere Application Server.report. enter MINOR. you need to set up manually the mxe. From the right panel. go to Administrator > Reporting > Report Administration. From the Start menu. Procedure 1. 2. k. Click New Row and repeat steps f-i to create another work order class with a different work type. About this task To configure BIRT. i.

Search for the appropriate cron task in the Cron Task field and configure it. Wait a couple of minutes for the process to complete. navigate to Go To > System Configuration > Platform Configuration > Cron Task Setup. 2. Synchronizing users and groups When you select application server security. Review all rows in the list view and click Generate Request Page. From the Control Desk interface. the scheduled synchronization of users and groups that occurs between LDAP repositories and Control Desk is governed by the federated repositories. Set the task to active. About this task LDAP repositories managed by IBM WebSphere Application Server Network Deployment through Virtual Member Manager are synchronized through the VMMSYNC cron task. 3. To configure the synchronization schedule between LDAP repositories and Control Desk. Open a web browser and point to http://host name:port/maximo. Change the Schedule field of the cron task if you want to change the interval. 3. What to do next By default. 5. the cron task performs its task every 5 minutes. 138 IBM Control Desk: Installation Guide (IBM WebSphere) . Log in to Control Desk using the maxadmin user ID. 4. complete the following steps: Procedure 1.

Build the maximo EAR file: Windows install_home\maximo\deployment\buildmaximoear. Building EAR files You can manually build Control Desk EAR files if.Chapter 15. complete the following steps: Procedure 1. Although the Control Desk installation program deploys these EAR files when you install. For more information that applies to both applications. you must rebuild of the maximo. or provide a new name for the application when installing the MAXIMO application into a cluster (“Manually installing applications in WebSphere Application Server Network Deployment” on page 140).sh © Copyright IBM Corp.properties file after the initial installation.properties file after the initial installation. then you must either uninstall the MAXIMO application (“Manually uninstalling applications from WebSphere Application Server Network Deployment” on page 140).ear files on WebSphere Application Server Network Deployment. If you have already installed Control Desk into an application server but want to redeploy into a cluster. You are not required to rebuild and redeploy the maximoiehs. You can manually build or uninstall the Control Desk maximo. you can either redeploy the Control Desk EAR files into a cluster.ear file. and then redeploy it in WebSphere Application Server Network Deployment. v If you have installed Control Desk into a development environment. you must deploy both the maximo and maximo help applications into the new environment.ear file.ear and maximoiehs. or. 2015 139 . you modify a database connection parameter in the maximo. create a cluster from the application server used during the installation. there might be a situation where you might want to rebuild these EAR files manually: v If you modify any database connection parameters in the maximo. v Control Desk must be installed into a WebSphere Application Server Network Deployment application server.ear file. However. you might at some point want to migrate the deployment into a test or production environment. Control Desk can be run within the framework of a WebSphere Application Server Network Deployment cluster. you rebuild and redeploy the maximo. see “Manually installing applications in WebSphere Application Server Network Deployment” on page 140. for example. If you want to deploy Control Desk in a cluster.cmd Linux and UNIX install_home/maximo/deployment/buildmaximoear. Maintaining EAR files Learn about maintaining Control Desk EAR files. In this scenario. In this scenario. About this task To manually build Control Desk EAR files.

2. Select the application that you want to uninstall.cmd Linux and UNIX install_home/maximo/deployment/buildmxiehsear. From the Specify the EAR. 5. and click Apply. Manually installing applications in WebSphere Application Server Network Deployment You can add Control Desk applications to WebSphere Application Server Network Deployment. Select all web modules listed in the table. 3. 2. Log on to the WebSphere Application Server Network Deployment administrative console. Expand Apply Multiple Mappings.sh Manually uninstalling applications from WebSphere Application Server Network Deployment You can uninstall Control Desk applications from WebSphere Application Server Network Deployment.ear file and click Next. Click Step 2: Map modules to servers. Click the Applications link. Select Detailed and click Next. Build the maximo help system EAR file: Windows install_home\maximo\deployment\buildmxiehsear. Procedure 1. By default. select Servers > Server Types > WebSphere application servers. WAR. 3. Select a virtual host. click Continue. or SAR module to upload and install page. from the Virtual Host menu. the Control Desk applications are named maximo and maximoiehs. Click Step 11: Map virtual hosts for Web modules. 7. 4. From the Application Security Warnings panel. 12. for example. select Local file system. and click Apply. JAR. Browse to Applications > New Application > New Enterprise Application. 10. select MXServer and click Stop. Click Uninstall. 4. check all check boxes for Modules listed in the table. Log in to the WebSphere Application Server Network Deployment administrative console. Browse to the location on your system of the maximo. maximo_host. 2. 140 IBM Control Desk: Installation Guide (IBM WebSphere) . Highlight all entries listed in the Clusters and servers field. Procedure 1. 8. 11. 9. 6.

Click Step 15: Map security roles to users or groups. 14. Maintaining EAR files 141 . Click Step 17: Summary and click Finish. Select the maximouser in the Role table and select Everyone from the Map Special Subjects menu. Chapter 15. 15. Map virtual hosts for Web modules 13.Figure 11.

142 IBM Control Desk: Installation Guide (IBM WebSphere) .

table spaces. Validate credentials. Configuration parameter validation Use the command-line configuration program to validate input in the same way the configuration program validates input in the user interface.properties files. Command-line configuration is used to quickly update configuration values when you choose to not use the configuration tool user interface. v Host names or IP addresses are correctly formatted and are reachable.properties files that are located under the install_home\etc and install_home\maximo\applications\maximo\properties directories. the configuration program uses values that are recorded from the previous deployment. Properties are encrypted when they are saved. v Update database or application server configuration settings without the server available. and application server objects. These values cannot be validated in this scenario. these types of changes would include changing a host name or updating a password. Command-line configuration Control Desk includes a configuration program that is accessed from the command line.properties and maximo. This command-line configuration program performs the same duties as the configuration program user interface. host names. either as parameters. Typically. If you make any environmental changes to any of the systems that are used for the original deployment. © Copyright IBM Corp. These values are stored on the administrative system in the install. You can complete the following tasks with the configuration command line interface tool: v Change the security model for the original deployment.properties files. v Confirm that updated property values conform to required input domains. replace existing properties in the maximo. You can update these values manually. for example. v Clone an existing environment and use the configuration command line interface tool to reconfigure the administrative workstation to use the new servers. v Remove configuration from a previously configured database. for example. The cloned environment must use the same directory structure as the original. This option is not available for Oracle WebLogic Server. Properties that are specified for the configuration command line interface tool. you can migrate from Control Desk-based security to WebSphere Application Server security.properties and install.Chapter 16. they must be recorded in the install. You can validate the following items with the command-line configuration program.properties and maximo. v Create an environment (non-cloned) and use the configuration command line interface tool to create all required artifacts database. When you install a fix pack or upgrade Control Desk. For example. or in an input properties file. 2015 143 . or you can use the configuration command line interface tool to update configuration values for your existing deployment when they change. and available ports.

properties v WebSphere_App_Server_Sample_input.properties These sample files are in the ibm\smp\configtools\samples directory. The following sample input property files are provided with the Control Desk command-line configuration program.properties files are updated with the values you provided. v Specified port values are listening on the corresponding host. databases. 144 IBM Control Desk: Installation Guide (IBM WebSphere) . are validated before they are used. the maximo.properties v Oracle_Sample_input. v Required WebSphere Application Server virtual member manager users exist. Port values contain numbers only and are within a valid range. After validation is successful. v User IDs and passwords meet length and character set criteria. v Sufficient authority is available to create WebSphere Application Server virtual member manager users.properties and install. v Specified credentials are used to authenticate to WebSphere Application Server. v There is enough space in the supplied directories to create database objects. introduced from either the command line or in the input properties file. Input properties files You can use property files as input for the Control Desk command-line configuration program. v DB2_Sample_input. and table spaces exist. v Preconfigured middleware can authenticate to the product database.properties v SQLServer_Sample_input. You can then use the updated file as input for the configuration command line interface tool with the –input parameter. v Middleware installation directories that are supplied exist. All input properties. Each of these sample files contains properties that are associated with a specific database or application server type. v Remote login credentials are valid. They contain comments and properties you can update with values from your environment. v Required objects such as JMS queues. SIB destinations.

Configures more products after an initial installation and configuration. v deployDatabaseConfiguration . v reapplyAppServerTuning – Reapplies tuning configuration to an application server. Control Desk command line configuration program parameters Parameter name Description -action Configuration action.Disables application security for the application. v deployMiddlewareConfiguration – Configures initial middleware installation.Validates command input and defines configuration property values for a new database for the current product. v removeDatabaseConfiguration – Removes product configuration information from a previously configured database. v configureProducts .Command line interface parameters The following parameters can be used with the configuration command line program to configure your environment. v addLanguages – Adds additional languages to a current deployment. and updates the mxe. Security is handled entirely through Control Desk. v deployConfiguration .Configures initial installation. v deployJ2eeConfiguration . Command-line configuration 145 . This action can configure multiple products after they are installed. v removeJ2EEConfiguration – Removes application server configuration that was added by the configuration tool. Chapter 16.Validates command input and defines configuration property values for a new application server for the current product. v enableAppSecurity – Enables application security for the application. This action can configure multiple products after they are installed and can also be used in an upgrade scenario. v disableDB2TextSearch .Enable the full text search feature on a DB2 database. This action is used for new installations only. v enableDB2TextSearch – Enables the full text search feature on a DB2 database.ldapUserManagement flag. This value is written to the database when the database is updated. v disableAppSecurity . v updateApplication – Updates the Control Desk application by updating the database and redeploying application EAR files. This value is written to the database when updated. Table 15.useAppServerSecurity property to a value of 0. This action sets the mxe. This action sets the mxe.useAppServerSecurity property to a value of 1.

The actions that modify the security setting for Control Desk also updates Control Deskweb. -automatej2eeconfig Automates the configuration of WebSphere Application Server. v validateJ2eeConfiguration . Control Desk command line configuration program parameters (continued) Parameter name Description v updateDatabaseConfiguration – Updates existing database configuration values. v updateJ2eeConfiguration . table spaces. v validateDatabaseConfiguration . -additionalLangs Adds one or more additional languages to the deployment. ES for Spanish.Validates reconfiguration command line interface tool input and then updates application server configuration values. -automatedbconfig Automates the configuration of the database. -buildAndDeployEAR Rebuilds and deploys application EAR files.Validates application server configuration values that are specified as input for the reconfiguration command line interface tool. For example. and creates database schema.Table 15.Removes database and application configuration performed by the configuration tool. v validateAndUpdateJ2eeConfiguration .xml files.Updates existing application server configuration values. This parameter requires one or more locale abbreviations for input. Application EAR files must be rebuilt and redeployed for configuration changes to take effect in the application. JMS queues and profiles. -allowUpdateDB The database update task is run to add the languages that are specified to the database. -applicationServerName Name of the application server. database users. v validateAndUpdateDatabaseConfiguration – Validates reconfiguration command line interface tool input and then updates existing database configuration property values. the database.Validates database configuration values specified as input for the reconfiguration command line interface tool. -applicationServerNode Name of the application server node. 146 IBM Control Desk: Installation Guide (IBM WebSphere) . v removeConfiguration . for example. Use this parameter to create the database instance. -buildears Rebuilds application EAR files. Using this parameter creates.

If you do not want to provide those credentials to the configuration program. If you use this parameter. Chapter 16. -dbrxapwd Password for the user ID used to access a remote middleware server. -db2textsearchport Port that is used by the DB2 server for full text search. Control Desk command line configuration program parameters (continued) Parameter name Description -bypassJ2eeValidation Skips the validation and configuration of the application server. -createResourcesIfMissing Creates any resources that are not found during configuration. you cannot also use the following parameters: v applicationServerName v applicationServerNode v automatej2eeconfig v buildAndDeployEAR v createResourcesIfMissing v deployhelpear v deploymaximoear v enableappsecurity v enableEnhancedNavigation v enableSkin v inputfile v j2eeserverport v usermanagement v wasuser v waspwd -bypassUpdateDB Specifies that the database update task is not run and the installation program does not update the database. Languages files for the locales that are specified are built into the application EAR file. alphanumeric data is stored as a vargraphic data type. -db2_english_only Specifies that alphanumeric data is stored as a varchar data type. If you do not use this parameter. -dbpwd Password for the user ID that accesses the database. If you use the bypassJ2eeValidation parameter. -dbrxauser User ID used to access a remote middleware server. Use this parameter if you have run the database update task and included the language files in the database through another method. -dbname Name of the database. then you must manually configure the application server before you can deploy Control Desk. Using this parameter limits you to using English in the user interface. Validation of a manually configured application server requires logging in to the application server with application server administrative credentials.Table 15. you can skip the validation task. Command-line configuration 147 .

This parameter works the same as the enableAppSecurity action. you must re-enable enhanced navigation. -deployhelpear Deploys help application EAR file. If you enable enhanced navigation. -enableMultiTenancy Enables the multitenancy feature. The deleteInstanceUsersAndGroups parameter requires the dbrxauser and dbrxapwd and the dbuser and dbpwd parameters. v DB2 v Oracle v SQLServer -deleteInstanceUsersAndGroups Removes the instance owner and database user IDs and associated groups from the DB2 server. Each group of tenants is served by an instance of the software that uses data that only they can access. -deploymaximoear Deploys Maximo application EAR file.Table 15. -dbserverport Port name of the database server.useAppServerSecurity property to a value of 1. -deployDemoData Includes sample data. including enhancements for switching between applications and viewing record lists. and then you enable a different user interface skin with the –enableSkin parameter. This value is written to the database when updated. Multitenancy refers to software or services that can be configured to serve multiple groups of clients referred to as tenants. -dbuser User ID that accesses the database. 148 IBM Control Desk: Installation Guide (IBM WebSphere) . -enableappsecurity Enables application security for the application. and updates the mxe. This parameter has cannot be used with and Microsoft SQL Server.ldapUserManagement flag. This action sets the mxe. -deleteWASprofiles Deletes the WebSphere Application Server profiles that are created for the application. -enableEnhancedNavigation Enables enhanced navigational elements in the user interface. The enableEnhancedNavigation parameter must be used with the enableSkin parameter. Control Desk command line configuration program parameters (continued) Parameter name Description -dbserverhost Host name of the database server. -dbvendor Database software name.

v Limit of allowed consecutive characters Standard policy has no restrictions to the amount of times a character can be repeated consecutively in a password.Table 15. Restrictive policy allows a character to be repeated two times consecutively in a password value. Command-line configuration 149 . v Login attempts Standard policy allows 10 login attempts before the account is locked. v Password minimum character length Standard policy passwords must be at least six characters. Restrictive policy passwords expire after 90 days. Restrictive policy allows 3 login attempts before the account is locked. v Number of alphabetic characters required in the password Standard policy does not require alphabetic characters in a password value. Control Desk command line configuration program parameters (continued) Parameter name Description -enableRestrictivePasswordPolicy Enables a more restrictive password policy for Control Desk users. Chapter 16. Restrictive policy allows 3 uses of the forgotten password link before locking the account. Restrictive policy requires one or more numeric characters in a password value. Restrictive policy requires one or more alphabetic characters in a password value. Restrictive policy passwords must be at least eight characters. Restrictive policy does not allow you to use the same value for the user name and password. v Password can be same value as user name Standard policy allows you to use the same value for the user name and password. v Number of numeric characters required in the password Standard policy does not require numeric characters in a password value. v Password duration (days) Standard policy passwords never expire. Restrictive policy warns the user that the account password is about to expire seven days before it expires. v Password threshold Standard policy does not enforce a password threshold. v Password expiration warning (days) Standard policy does not warn the user that the account password is about to expire. Restrictive policy enforces a password threshold of 270 characters. v Number of times that the forgotten password link can be used Standard policy allows 5 uses of the forgotten password link before locking the account.

150 IBM Control Desk: Installation Guide (IBM WebSphere) .systemNavBar – mxe.webclient.Table 15. -j2eeserverhost Host name of the domain manager of the application server.tabBreadCrumbs – mxe.webclient.skin v tivoli09 Removes settings for the following properties: – mxe.skin=tivoli09 v tivoli13 Sets the following properties to a value of 1: – mxe.skin=tivoli13 -force Indicates that an input property file updates the properties file and skips the validation of parameters input to the command line tool through an input properties file.verticalLabels Sets the following property: – mxe.tabBreadCrumbs – mxe. -inputfile Fully qualified path to the properties file that is used to set properties in an environment. -j2eeserverport Port name of the application server domain manager server.homeButtonHeaders – mxe. If deployment manager host name or server port is specified the thinwsadmin scripts are updated accordingly.webclient. Values that are specified as command line parameters for the configuration command line interface tool supersede values from the input file. you are not prompted for confirmation of the property update task.webclient.webclient.webclient.webclient. Control Desk command line configuration program parameters (continued) Parameter name Description -enableSkin Change the appearance of the user interface.homeButtonHeaders – mxe.webclient. When you use this parameter.verticalLabels – mxe.webclient.systemNavBar – mxe.homeButtonHeaders – mxe.systemNavBar – mxe.verticalLabels Sets the following property: – mxe. If deployment manager host name or server port is specified the thinwsadmin scripts are updated accordingly.webclient.webclient. -j2eevendor Application server software.tabBreadCrumbs – mxe. v WebSphere v WebLogic -mtadminpwd Password for the user ID of the multitenancy configuration manager.webclient. v Classic Removes settings for the following properties: – mxe.webclient.webclient.webclient.

If this parameter is not specified. If the users do not exist.Table 15. -validateUsers Used with the enableAppSecurity action to validate users exist in the LDAP repository. -mtdbuser User ID of the multitenancy configuration manager that is used to connect to the database. JMS objects. including disk space availability and remote access credentials. v mixed Manage users through application server security mechanisms. validation is performed as if the tool was configuring the middleware. v j2ee Change the security setting in Control Desk so that both Control Desk users and Control Desk groups are managed through application server security mechanisms. Additional configuration details are checked. -stopAppServer The application server must be stopped when you add languages. -waspwd WebSphere Application Server administrator user ID password. -removeInstance Removes the database instance for DB2 and Oracle. -mtdbpwd Password for the user ID of the multitenancy configuration manager that is used to connect to the database. and the application server. This parameter is used for WebSphere Application Server only. Chapter 16. This parameter cannot be used with Microsoft SQL Server. -setjdbcurl Sets the JDBC connection URL string. validation is performed in the context of a component that is already established in the environment. -updatedb Runs the updatedb configuration task. -removeCreatedArtifacts Removes any artifacts that are created by the configuration tool. When this parameter is specified. -validateForNewDeploy Validate middleware configuration. you must stop the application server manually before you use the addLanguages action. and manage groups using Control Desk. -unsetjdbcurl Removes the currently used JDBC connection URL string. -wasrxapwd Password for user ID to access remote WebSphere Application Server server host. Examples include directories that are created by the configuration program. Control Desk command line configuration program parameters (continued) Parameter name Description -mtadminuser User ID of the multitenancy configuration manager. Command-line configuration 151 . the existing security model is not modified. The removeInstance parameter requires the dbrxauser and dbrxapwd. -usermanagement Changes the security configuration of the existing Control Desk deployment. If you do not use the stopAppServer parameter with the addLanguages action. and the dbuser and dbpwd parameters.

DB2. action updateDatabaseConfiguration The updateDatabaseConfiguration action is used to update existing database configuration values. This action can be used to verify database properties before they are updated. or following an update action. Typically. -wasuser WebSphere Application Server administrator user ID.FencedUser v Database. this user ID is defined as wasadmin.FencedUserPassword v Database.DB2.InstanceUserPassword These properties must be added manually to the install. 152 IBM Control Desk: Installation Guide (IBM WebSphere) .DB2. Control Desk command line configuration program parameters (continued) Parameter name Description -wasrxauser Operating system user ID used to access remote WebSphere Application Server host. Command line configuration program actions Use the command line configuration program to configure new or existing deployments of Control Desk. -action validateDatabaseConfiguration [-validateForNewDeploy] [-dbserverhost hostname] [-dbserverport port number] [-dbname database name] [-dbuser userid] [-dbpwd password] [-dbrxauser userid] [-dbrxapwd password] [-setjdbcurl jdbcurl] [-unsetjdbcurl] [-enableMultiTenancy] [-mtadminuser userid] [-mtadminpwd password] [-mtdbuser userid] [-mtdbpwd password] [-inputfile path to input properties file] The following properties are required if the -validateForNewDeploy parameter is used.InstanceAdminUserName (Windows only) v Database. This is the user ID that is used to log in to the WebSphere Application Server administrative client application. -action updateDatabaseConfiguration [-force] [-buildAndDeployEAR] [-dbserverhost hostname] [-dbserverport port number] [-dbname database name] [-dbuser userid] [-dbpwd password] [-dbrxauser userid] [-dbrxapwd password] [-setjdbcurl jdbcurl] [-unsetjdbcurl] [-inputfile path to input properties file] action validateDatabaseConfiguration Use the validateDatabaseConfiguration action to validate current database configuration properties.InstanceAdminPassword (Windows only) v Database.DB2.properties file.InstanceAdminGroup v Database.DB2.DB2.Table 15. v Database.FencedGroupName v Database. Typically this user ID is defined either as Administrator or root.DB2.

properties file.FencedUserPassword v Database. v Database.DB2. -action deployDatabaseConfiguration [-buildAndDeployEAR] [-createResourcesIfMissing] [-dbserverhost hostname] [-dbserverport port number] \[-dbname database name] [-dbuser userid] [-dbpwd password] [-dbrxauser userid] [-dbrxapwd password] [-setjdbcurl jdbcurl] [-unsetjdbcurl] [-enableMultiTenancy] [-mtadminuser userid] [-mtadminpwd password] [-mtdbuser userid] [-mtdbpwd password] [-deployDemoData] [-inputfile path to input properties file] [-enableRestrictivePasswordPolicy] The following properties are required if the -createResourcesIfMissing parameter is used.FencedUser v Database. -action validateAndUpdateDatabaseConfiguration [-validateForNewDeploy] [-force] [-buildAndDeployEAR] [-dbserverhost hostname] [-dbserverport port number] [-dbname database name] [-dbuser userid] [-dbpwd password] [-dbrxauser userid] [-dbrxapwd password] [-setjdbcurl jdbcurl] [-unsetjdbcurl] [-enableMultiTenancy] [-mtadminuser userid] [-mtadminpwd password] [-mtdbuser userid] [-mtdbpwd password] [-inputfile path to input properties file] The following properties are required if the -validateForNewDeploy parameter is used. action deployDatabaseConfiguration The deployDatabaseConfiguration action is used to validate command-line configuration program input and define configuration property values for a new database for the currently deployed product.DB2.DB2.InstanceAdminPassword (Windows only) v Database.InstanceAdminUserName (Windows only) v Database.InstanceUserPassword These properties that must be added manually to the install.InstanceUserPassword These properties that must be added manually to the install.FencedUserPassword v Database.DB2.FencedGroupName v Database. This action can be run after a successful deployConfiguration action.DB2.FencedUser v Database.DB2.InstanceAdminPassword (Windows only) v Database. Chapter 16.DB2.InstanceAdminGroup v Database.DB2.DB2.FencedGroupName v Database.action validateAndUpdateDatabaseConfiguration The validateAndUpdateDatabaseConfiguration action is used to both validate reconfiguration command-line interface tool input and then update existing database configuration property values.InstanceAdminGroup v Database.DB2.properties file.DB2.DB2.DB2. Command-line configuration 153 . The -enableMultiTenancy parameter must be used with the -validateForNewDeploy parameter. v Database.InstanceAdminUserName (Windows only) v Database.DB2.

FencedUserPassword 154 IBM Control Desk: Installation Guide (IBM WebSphere) . -action validateAndUpdateJ2eeConfiguration [-force] [-validateForNewDeploy] [-buildAndDeployEAR] [-j2eeserverhost hostname] [-j2eeserverport port number] [-wasuser userid] [-waspwd password] [-applicationServerNode nodeName] [-applicationServerName appServerName] [-inputfile path to input properties file] The following properties are required if the –validateForNewDeploy parameter is used and the WAS. -action updateJ2eeConfiguration [-force] [-buildAndDeployEAR] [-j2eeserverhost hostname] [-j2eeserverport port number] [-wasuser userid] [-waspwd password] [-applicationServerNode nodeName] [-applicationServerName appServerName] [-inputfile path to input properties file] action validateJ2eeConfiguration The validateJ2eeConfiguration action is used to validate application server configuration values specified as input for the reconfiguration command-line interface tool.FencedUserPassword v Database.FencedUser v Database.DB2.DB2. v Database.SibPersistMessages property is set to true.FencedUser v Database. -action validateJ2eeConfiguration [-validateForNewDeploy] [-j2eeserverhost hostname] [-j2eeserverport port number] [-wasuser userid] [-waspwd password] [-applicationServerNode nodeName] [-applicationServerName appServerName] [-inputfile path to input properties file] The following properties are required if the –validateForNewDeploy parameter is used and the WAS. action removeDatabaseConfiguration The removeDatabaseConfiguration action is used to remove configuration settings from a previously configured database. -action enableDB2TextSearch [-db2textsearchport port number] action updateJ2eeConfiguration The updateJ2eeConfiguration action is used to update existing application server configuration values.SibPersistMessages property is set to true. v Database.InstanceUserPassword These properties that must be added manually to the install.DB2. -action removeDatabaseConfiguration [-removeInstance] [-dbrxauser userid] [-dbrxapwd password] [-dbuser userid] [-dbpwd password] [-deleteInstanceUsersAndGroups] action enableDB2TextSearch The enableDB2TextSearch action is used to enable the full text search feature for a DB2 database. action validateAndUpdateJ2eeConfiguration The validateAndUpdateJ2eeConfiguration action is used to both validate reconfiguration command-line interface tool input and then update existing application server configuration property values.properties file.DB2.DB2.

This action can configure multiple middleware products after they are installed. This action is equivalent to running the removeJ2EEConfiguration and removeDatabaseConfiguration actions together -action removeConfiguration -dbuser userid -dbpwd password -wasuser userid -waspwd password [-wasrxauser userid] Chapter 16.FencedUserPassword v Database. This action is used for new Control Desk installation scenarios only.SibPersistMessages property is set to true.DB2. -action deployJ2eeConfiguration [-bypassJ2eeValidation] [-buildAndDeployEAR] [-createResourcesIfMissing] [-j2eeserverhost hostname] [-j2eeserverport port number] [-wasuser userid] [-waspwd password] [-applicationServerNode nodeName] [-applicationServerName appServerName] [-inputfile path to input properties file] [–enableSkin Classic|tivoli09|tivoli13] [-enableEnhancedNavigation] The following properties are required if the -validateForNewDeploy parameter is used and the WAS.properties file. and JMS objects.InstanceUserPassword These properties must be added manually to the install.DB2. Command-line configuration 155 .InstanceUserPassword These properties that must be added manually to the install. v Database.DB2. -action removeJ2EEConfiguration [-wasuser userid] [waspwd password] [-wasrxauser userid] [-wasrxapwd password] [-removeCreatedArtifacts] [-deleteWasProfiles] action deployConfiguration Use the deployConfiguration action to configure the initial installation. action removeJ2EEConfiguration The removeJ2EEConfiguration action is used to remove configuration settings from a previously configured application server. action deployJ2eeConfiguration The deployJ2eeConfiguration action is used to validate command line configuration program input and define configuration property values for a new application server for the currently deployed product. This action can be run after a successful deployConfiguration action.DB2.properties file. -action deployConfiguration [-inputfile path to input properties file] [-dbvendor Oracle|DB2|SQLServer] [-j2eevendor WebSphere|WebLogic] [-bypassJ2eeValidation][-automatedbconfig] [-automatej2eeconfig] [-usermanagement j2ee|mixed] [-buildears] [-deploymaximoear] [-deployhelpear] [-enableappsecurity] [-deployDemoData] [-enableMultiTenancy] [-db2_english_only] [–enableSkin Classic|tivoli09|tivoli13] [-enableEnhancedNavigation] [-enableRestrictivePasswordPolicy] action removeConfiguration The removeConfiguration action is used to removes database and application configuration that is performed by the configuration tool.FencedUser v Database. The deployConfiguration action requires the inputfile parameter and an input properties file populated with the configuration values you want to use. Items removed include domain manager and application server profiles. v Database.

and mboweb web.ldapUserManagement property according to the setting of the –usermanagement parameter.locale3] [-buildAndDeployEAR] [-allowUpdateDB | -bypassUpdateDB] [-stopAppServer] [-inputfile path to input properties file] The application server must be stopped when you add languages.xml files are updated during this action. -action reapplyAppServerTuning [-wasuser userid] [-waspwd password] [-applicationServerNode nodeName] [-applicationServerName appServerName] action enableAppSecurity The enableAppSecurity action is used to enable application security for the application. This value is written to the database when updated. [-wasrxapwd password] [-dbrxauser userid] [-dbrxapwd password] [-removeInstance] [-deleteInstanceUsersAndGroups] [-removeCreatedArtifacts] [-deleteWasProfiles] [-inputfile path to input properties file] action reapplyAppServerTuning The action is used to reapply application server tuning. The maximouiweb. This action sets the mxe. -action updateApplication [-updatedb] [-deploymaximoear] [-deployhelpear] [-wasuser userid] [-waspwd password] [–enableSkin Classic|tivoli09|tivoli13] [-enableEnhancedNavigation] [-enableRestrictivePasswordPolicy] action addLanguages Use the addLanguages action to configure additional languages for a deployment.useAppServerSecurity property to a value of 1. maxrestweb.locale2. meaweb. This value is written to the database when updated. -action enableAppSecurity -usermanagement {j2ee. meaweb. you must stop the application server manually before you use the addLanguages action. If you do not use the stopAppServer parameter with the addLanguages action. -action addLanguages [-additionalLangs locale1. Using this action reverts the security implementation to Control Desk security for users and groups. Locales supported by the configuration program Language Locale Arabic ar Brazilian Portuguese pt_BR 156 IBM Control Desk: Installation Guide (IBM WebSphere) . Table 16. and updates the mxe. The maximouiweb.xml files are updated during this action. -action disableAppSecurity [-buildAndDeployEar] [-force] action updateApplication The updateApplication action is used to update the application by updating the database and redeploying application EAR files. This action sets the mxe.useAppServerSecurity property to a value of 0. and mboweb web. The following locale values are supported.mixed} [-buildAndDeployEAR] [-validateUsers] [-force] action disableAppSecurity The disableAppSecurity action is used to disable application security for the application. maxrestweb.

This action verifies a full installation and configuration of an existing product was completed successfully before it continues. -action deployMiddlewareConfiguration [-inputfile path to input properties file] The following properties can be included in the input properties file used with the deployMiddlewareConfiguration action. Command-line configuration 157 . Properties that can be used in the deployMiddlewareConfiguration action input file Category Property HTTP Server properties IHS. This action can configure multiple products after they are installed. This action can also be used in an upgrade scenario. -action configureProducts [-updatedb] [-buildears] [-deploymaximoear] [-deployhelpear] [-wasuser userid] [-waspwd password] action deployMiddlewareConfiguration The deployMiddlewareConfiguration action is used to configures middleware after it is installed. Locales supported by the configuration program (continued) Language Locale Croatian hr Czech cs Danish da Dutch nl Finnish fi French fr German de Hebrew he Hungarian hu Italian it Japanese ja Korean ko Norwegian no Polish pl Russian ru Simplified Chinese zh_CN Slovak sk Slovenian sl Spanish es Swedish sv Traditional Chinese zh_TW Turkish tr action configureProducts The configureProducts action is used to configure more products that are installed after an initial installation and configuration. Table 17.HTTPPort Chapter 16. Table 16.

ServerHostName LDAP. Control Desk properties Category Property Definition Shared database mxe. When you set property values to a Linux or UNIX path.ND. Properties that can be used in the deployMiddlewareConfiguration action input file (continued) Category Property IHS.WebserverName LDAP server properties LDAP.AdminUserName WAS.AdminDN LDAP.ApplicationServerName WAS.LDAPAutomatedConfig WAS.ServerProfileName WAS. maximo. When you set a property value to a Windows path.Operation WebSphere properties PLG.AutomateConfig WAS.AdminPassword WAS.InstallLocation Configuration program properties Control Desk properties can be modified with the command line configuration program by using an input.CellName WAS.ServerPort LDAP.schemaowner Owner of the database schema. properties For example. C:\\IBM\\WebSphere\\AppServer.SOAPConnectorPort WCT.InstallLocation IHS. you must use two consecutive backslashes.AdminPassword LDAP. use single forward slashes.UserSuffix LDAP. For example.DeploymentManagerProfileName WAS.InstallLocation WAS.db.OrgContainerSuffix LDAP. Table 18.GroupSuffix LDAP. /opt/IBM/db2/V10.Vendor General middleware configuration properties MW.DeploymentManagerNodeName \ WAS.5.BaseEntry LDAP. Table 17. for example.properties file.NodeName WAS. This value is written to the database when updated.InstallLocation WAS. 158 IBM Control Desk: Installation Guide (IBM WebSphere) .

This property is only required if the createResourcesIfMissing. mxe.DB2. For example.DB2.Table 18. This value is written to the database when updated. For example. validatefornewdeploy.com.password Password for the user ID that accesses the database. validatefornewdeploy. mymachine.user User ID that accesses the database.ServerHostName Fully qualified host name of the DB2 server. or automatedbconfig parameters are specified. This value is written to the database when updated. Chapter 16.InstanceUserPassword Password for the database instance owner This property is only required if the createResourcesIfMissing. 50005. Command-line configuration 159 .db.DB2.DB2. Control Desk properties (continued) Category Property Definition mxe. Database.RemoteAccessUserName. validatefornewdeploy. This property is only required if the createResourcesIfMissing.mydomain. For example. validatefornewdeploy. Database. This value is written to the database when updated. Database. Database. Database.RemoteAccessUserName Database server system user ID that is used for configure the database remotely.ServerPort Database server port. ctginst1. DB2 Properties Database.InstanceName Name of the database instance. or automatedbconfig parameters are specified. or automatedbconfig parameters are specified.RemoteAccessPassword Password for user ID named in Database.db. or automatedbconfig parameters are specified. This property is only required if the createResourcesIfMissing.

validatefornewdeploy.InstanceAdminGroup Group for the instance administrator. For example. This property is only required if the createResourcesIfMissing. Database. This value is written to the database when updated. This property is only required if the createResourcesIfMissing.DB2. For example. This property is only required if the createResourcesIfMissing.InstallLocation Install location of the database.DatabaseName Name of the database. or automatedbconfig parameters are specified.DB2.5. For example.Table 18. Database. or automatedbconfig parameters are specified. This property is only required if the createResourcesIfMissing. Control Desk properties (continued) Category Property Definition Database. validatefornewdeploy. validatefornewdeploy. ctgiadm1.DB2.ApplHeapSize Application heap size. For example. Database. or automatedbconfig parameters are specified. validatefornewdeploy. or automatedbconfig parameters are specified. 8192. maxdb76. or automatedbconfig parameters are specified. 1024.DB2.AppCtlHeapSize Application control heap size. For example. This property is only required if the createResourcesIfMissing. /opt/IBM/db2/V10. For example.DB2.LogFileSize Set the size for transaction logs. Database. validatefornewdeploy. 1024.DB2. 160 IBM Control Desk: Installation Guide (IBM WebSphere) . Database.

This property is only required if DB2 is installed on a Windows system. For example.LogSecond Number of secondary log files allowed. Control Desk properties (continued) Category Property Definition Database. validatefornewdeploy.DB2. Command-line configuration 161 . or automatedbconfig parameters are specified.DB2. validatefornewdeploy.ServiceUser. Database. Database.ServicePassword Password for Database. This property is only required if the createResourcesIfMissing. or automatedbconfig parameters are specified. 32. Database. validatefornewdeploy.DB2.DB2. This property is only required if the createResourcesIfMissing. or automatedbconfig parameters are specified.LockListSize Size that is allocated to the lock list. AUTOMATIC. 100. validatefornewdeploy. or automatedbconfig parameters are specified.ExtentSize Number of pages per extent (group of pages). This property is only required if the createResourcesIfMissing. validatefornewdeploy.DB2.DB2. For example. or automatedbconfig parameters are specified.ServiceUser User ID used to autostart. Database. This property is only required if DB2 is installed on a Windows system.Table 18. Chapter 16. For example. This property is only required if the createResourcesIfMissing. This property is only required if the createResourcesIfMissing.

FencedUserPassword Password for the fenced user ID for DB2 on Linux or UNIX systems.DB2.FencedUser Fenced user ID for DB2 on Linux or UNIX systems. validatefornewdeploy. Database. For example. validatefornewdeploy. This property is only required if the createResourcesIfMissing. server. or automatedbconfig parameters are specified. db2fenc1. Control Desk properties (continued) Category Property Definition Database.FencedGroupName Default group for database fenced user. validatefornewdeploy. ctgfgrp1. This property is only required if the createResourcesIfMissing. Database.DB2. For example.DB2. or automatedbconfig parameters are specified. This property is only required if the createResourcesIfMissing.Table 18. MAXBUFPOOL. For example.DB2. Database. 162 IBM Control Desk: Installation Guide (IBM WebSphere) .DataTablespaceName DB2 table space name for the product database. This property is only required if the createResourcesIfMissing.AuthType Method DB2 uses to authenticate users. or automatedbconfig parameters are specified. or automatedbconfig parameters are specified. This property is only required if the createResourcesIfMissing. or automatedbconfig parameters are specified.DB2. Database. validatefornewdeploy. This property is only required if DB2 is installed on a Linux or UNIX system. Database. validatefornewdeploy. maxdata.DB2. For example.BufferPoolName DB2 buffer pool name. For example.

5000. This property is only required if the createResourcesIfMissing. This property is only required if the createResourcesIfMissing.DB2. 4096.BufferPoolSize Size of the buffer pool. CTGDAT.TempTablespaceName Temporary table space name. This property is only required if the createResourcesIfMissing. Chapter 16. Database.TempTablespaceLocation Location of temporary table space. 1000. Database. This property is only required if the createResourcesIfMissing. which is measured in Mb. validatefornewdeploy.DB2. Database.DB2. Database. CTGTMP. Command-line configuration 163 . or automatedbconfig parameters are specified. Control Desk properties (continued) Category Property Definition Database. validatefornewdeploy.DB2.TempTablespaceSize Temporary table space size.DataTablespaceLocation Location of DB2 database table space data files. For example. For example.DataTablespaceSize Table space size. Database. For example. or automatedbconfig parameters are specified. maxtemp. For example.DB2. or automatedbconfig parameters are specified. validatefornewdeploy. validatefornewdeploy.Table 18. This property is only required if the createResourcesIfMissing.DB2. validatefornewdeploy. For example. This property is only required if the createResourcesIfMissing. or automatedbconfig parameters are specified. For example. which is measured in Mb. validatefornewdeploy. or automatedbconfig parameters are specified. or automatedbconfig parameters are specified.

IndexTablespaceSize Index table space size.DB2. which is measured in Mb.InstanceName Oracle instance name.Oracle. CTGDAT.DB2. validatefornewdeploy. or automatedbconfig parameters are specified. validatefornewdeploy. This value is written to the database when updated. or automatedbconfig parameters are specified. validatefornewdeploy. This property is only required if the createResourcesIfMissing. maxdata.DB2.createResourcesIfMissing Oracle Database. This property is only required if the createResourcesIfMissing. validatefornewdeploy. This property is only required if the createResourcesIfMissing.Oracle. Database.Table 18.InstanceAdminPassword Password for the user ID specified for Database.SchemaPassword Password for the schema owner.DB2. Control Desk properties (continued) Category Property Definition Database.IndexTablespaceName Index table space name.IndexTablespaceLocation Location of index table space. For example. Database. Database. 164 IBM Control Desk: Installation Guide (IBM WebSphere) .DB2.InstanceAdminUserName.InstanceAdminUserName Administrative user or the database instance. or automatedbconfig parameters are specified. 5000. db2admin. This property is only required if the createResourcesIfMissing. or automatedbconfig parameters are specified. For example. For example. For example. this value must be the same as the instance owner. Database. For Unix and Linux platforms.DB2. Database.

Command-line configuration 165 . Control Desk properties (continued) Category Property Definition Database. which is measured in Mb. 5000. oracle. Chapter 16. This property is only required if the createResourcesIfMissing. /opt/app/oracle/product/ 10.SoftwareOwnerPassword Password for the user ID listed in Database.2. validatefornewdeploy. or automatedbconfig parameters are specified. This property is only required if the createResourcesIfMissing. For example.DataTablespaceName Oracle table space name for the product database.InstallLocation Oracle installation location. maxdata.DataTablespaceSize Table space size. or automatedbconfig parameters are specified. or automatedbconfig parameters are specified.0/db_1.SoftwareOwner. Database.Oracle. or automatedbconfig parameters are specified. Database. /opt/app/oracle/ product/10. For example.2. Database.SoftwareOwner Owner of the software installation.0/db_1.Oracle. Database.InstanceLocation Oracle instance location.Oracle. validatefornewdeploy. validatefornewdeploy. This property is only required if the createResourcesIfMissing.Oracle. For example.Oracle. Database.Oracle. validatefornewdeploy. For example.Table 18. This property is only required if the createResourcesIfMissing. or automatedbconfig parameters are specified.Oracle. This property is only required if the createResourcesIfMissing. For example. validatefornewdeploy.

TempTablespaceName Temporary table space name.Oracle. maxdata. which is measured in Mb. or automatedbconfig parameters are specified. Database. This property is only required if the createResourcesIfMissing. For example. Database.Oracle. validatefornewdeploy. This property is only required if the createResourcesIfMissing.IndexTablespaceName Index table space name. For example. For example. or automatedbconfig parameters are specified. This property is only required if the createResourcesIfMissing. or automatedbconfig parameters are specified. validatefornewdeploy. This property is only required if the createResourcesIfMissing.Oracle. 1000. Database. Control Desk properties (continued) Category Property Definition Database.DBAUserName Oracle DBA user name. Database.ServerPort Port number that is used by Oracle. validatefornewdeploy. maxtemp. For example. which is measured in Mb. sys. or automatedbconfig parameters are specified. 166 IBM Control Desk: Installation Guide (IBM WebSphere) .ServerHostName Fully qualified host name of the Oracle server. Database.IndexTablespaceSize Index table space size.Oracle. This value is written to the database when updated. This property is only required if the createResourcesIfMissing. 1521. Database. or automatedbconfig parameters are specified. Database. validatefornewdeploy.Oracle. 1000.TempTablespaceSize Temporary table space size.Table 18. For example.DBAPassword Password for user ID listed for Database. For example. validatefornewdeploy.DBAUserName.Oracle.

Database. For example. 5000. This property is only required if the createResourcesIfMissing. For example. Database.SQL.DataFileName A way to specify the name of the data file used for the database. This property is only required if the createResourcesIfMissing. Command-line configuration 167 .DataFilegroupName Database logical name file group. validatefornewdeploy. maxdb76_dat. or automatedbconfig parameters are specified. Database. or automatedbconfig parameters are specified.LogFileName A way to specify the name for the database transaction log file. For example.SQL.DatabaseName Name of the database. This value is written to the database when updated. Control Desk properties (continued) Category Property Definition Microsoft SQL Server Database.DataFileSize Initial size for data file for the database in kb.SQL. validatefornewdeploy. Database.LogFileSize Microsoft SQL Server transaction log file size. Database. Chapter 16. This property is only required if the createResourcesIfMissing. maxdb76_log. validatefornewdeploy. For example. This property is only required if the createResourcesIfMissing.SQL.SQL. validatefornewdeploy. or automatedbconfig parameters are specified. validatefornewdeploy. or automatedbconfig parameters are specified.Table 18. Database.SQL. or automatedbconfig parameters are specified. This property is only required if the createResourcesIfMissing. PRIMARY. maxdb76.DataFileMaxSize Maximum size for data file for the database. For example.SQL.

myhost. This property is only required if the createResourcesIfMissing. 168 IBM Control Desk: Installation Guide (IBM WebSphere) . This value is written to the database when updated.mydomain. v WAS.ServerPort Database server port. Database. sa. For example.InstallLocation Installation location for WebSphere Server Network Application Server Network Deployment Deployment.UISIBPropertiesFile WAS. This property is required in the properties file that is specified in one of the following properties. Control Desk properties (continued) Category Property Definition Database. Used during installation for creating and modifying the database and database user.DeploymentManagerHostName Host name of the WebSphere Application Server Network Deployment deployment manager.com.SQL.Table 18. For example. validatefornewdeploy. C:\\IBM\\WebSphere\\ AppServer.SQL. For example. or automatedbconfig parameters are specified. 1433.InstanceAdminUserName Administrative user for the Microsoft SQL Server instance.SQL. For example.SQL. Database. This property is only required if the createResourcesIfMissing. or automatedbconfig parameters are specified. WebSphere Application WAS.MIFSIBPropertiesFile v WAS.CronSIBPropertiesFile v WAS. This value is written to the database when updated. Database.SibPersistMessages property is set to true. This property is required if the WAS.ServerHostName Host name of the database server.InstanceAdminPassword Administrative user password. validatefornewdeploy.

MIFSIBPropertiesFile v WAS.UISIBPropertiesFile WAS.Table 18.SibPersistMessages property is set to true.MIFSIBPropertiesFile v WAS.CronSIBPropertiesFile v WAS.CronSIBPropertiesFile v WAS. For example. ctgCell01.CellName WebSphere Application Server Network Deployment cell name. For example. This property is required if the WAS.DeploymentManagerProfileName WebSphere Application Server Network Deployment profile name. v WAS.ApplicationServerName WebSphere Application Server Network Deployment application server name. Command-line configuration 169 . This value is written to the database when updated. Chapter 16. ctgNode01 WAS. v WAS. For example. WAS. This property is required in the properties file that is specified in one of the following properties. For example.SibPersistMessages property is set to true. MXServer. C:\\ IBM\\WebSphere\\AppServer\\ profiles\\ctgDmgr01 This property is only required if the WAS. For example. For example.NodeName WebSphere Application Server Network Deployment node name. wasadmin.UISIBPropertiesFile WAS. Control Desk properties (continued) Category Property Definition WAS. WAS. ctgDmgr01.DeploymentManagerProfileRoot Location of the WebSphere Application Server Network Deployment profile.AdminUserName WebSphere Application Server Network Deployment administrator name. This property is required in the properties file that is specified in one of the following properties.

intjmsbus.MIFSIBPropertiesFile v WAS. For example.UISIBPropertiesFile WAS. v WAS. v WAS. WAS. This property is required in the properties file that is specified in one of the following properties.VirtualHost Name of the WebSphere Application Server Network Deployment virtual host. WAS.SibPersistMessages property is set to true. WAS. WAS.SOAPConnectorPort SOAP port for WebSphere Application Server Network Deployment deployment manager.CronSIBPropertiesFile v WAS. 8879. For example.RemoteAccessPassword WebSphere Application Server Network Deployment deployment manager system user password. Control Desk properties (continued) Category Property Definition WAS.MIFSIBPropertiesFile v WAS. maximo_host.WebServerHostName Host name where the HTTP server is located.Table 18.CronSIBPropertiesFile v WAS.SibPersistMessages property is set to true. This property is required if the WAS.SibName Name of the service integration bus.AdminPassword WebSphere Application Server Network Deployment administrator password. This property is required if the WAS.RemoteAccessUserName WebSphere Application Server Network Deployment deployment manager system user ID used for tasks such as copying Integrated Solutions Console web archive files and fetching the keystore. For example. This property is required in the properties file that is specified in one of the following properties. 170 IBM Control Desk: Installation Guide (IBM WebSphere) .UISIBPropertiesFile WAS.

MIFSIBPropertiesFile v WAS. For example.UISIBPropertiesFile WAS. This property is only required if the createResourcesIfMissing. This property is required in the properties file that is specified in one of the following properties. 500000. webserver1. This property is required in the properties file that is specified in one of the following properties. or automatej2eeconfig parameters are specified.UISIBPropertiesFile Chapter 16. Control Desk properties (continued) Category Property Definition WAS.SibPersistMessages Binary value that indicates if service integration bus messages are persisted in either the product database or a local derby database.WebServerName Name of the WebSphere Application Server Network Deployment web server. For example. This property is only required if the createResourcesIfMissing.Table 18.CronSIBPropertiesFile v WAS. validatefornewdeploy. v WAS. validatefornewdeploy. A value of true indicates that the messages are persisted.SibHiMsg Service integration bus high message count.CronSIBPropertiesFile v WAS. v WAS. Used to manage HTTP server from within WebSphere Application Server Network Deployment. Command-line configuration 171 .MIFSIBPropertiesFile v WAS. WAS. or automatej2eeconfig parameters are specified.

UISIBPropertiesFile WAS. intjmsds.SibPersistMessages property is set to true.CronSIBPropertiesFile v WAS.MIFSIBPropertiesFile v WAS.SibDBInstancePassword IBM DB2 instance users password for the SIB IBM DB2 data store. v WAS. This property is required if the WAS.SibDSName Service integration bus data source name that is created to access the service integration bus persistence store. This property is only required if the WAS. For example. v WAS.MIFSIBPropertiesFile v WAS. This property is required in the properties file that is specified in one of the following properties.SibPersistMessages property is set to true.CronSIBPropertiesFile v WAS. This property is required if the WAS.UISIBPropertiesFile 172 IBM Control Desk: Installation Guide (IBM WebSphere) .UISIBPropertiesFile WAS. This property is required in the properties file that is specified in one of the following properties.SibDBName Name of the service integration bus messages database. This property is required in the properties file that is specified in one of the following properties.SibPersistMessages property is set to true.Table 18. This property is required in the properties file that is specified in one of the following properties. Control Desk properties (continued) Category Property Definition WAS. v WAS.MIFSIBPropertiesFile v WAS.MIFSIBPropertiesFile v WAS.CronSIBPropertiesFile v WAS.SibDBInstance Instance name of the service integration bus database. v WAS.UISIBPropertiesFile WAS.CronSIBPropertiesFile v WAS.

SibDBUserName User ID used to access the persistence data store database for service integration bus messages. This property is required if the WAS. v WAS. Control Desk properties (continued) Category Property Definition WAS.SibDBServerPort Database server port for the database that contains the service integration bus messages.UISIBPropertiesFile WAS. For example.Table 18.SibPersistMessages property is set to true.CronSIBPropertiesFile v WAS.MIFSIBPropertiesFile v WAS. This property is required if the WAS.SibPersistMessages property is set to true.CronSIBPropertiesFile v WAS. This property is required in the properties file that is specified in one of the following properties.CronSIBPropertiesFile v WAS.SibPersistMessages property is set to true.UISIBPropertiesFile Chapter 16.UISIBPropertiesFile WAS. This property is required if the WAS. v WAS. 50005. v WAS.SibDBServerName Server name of the system that is hosting the service integration bus message database. This property is required in the properties file that is specified in one of the following properties. Command-line configuration 173 . This property is required in the properties file that is specified in one of the following properties.MIFSIBPropertiesFile v WAS.MIFSIBPropertiesFile v WAS.

SibDbFencedUser Fenced user ID for the service integration bus database.UISIBPropertiesFile WAS. This property is only required if the WAS. This property is required in the properties file that is specified in one of the following properties.CronSIBPropertiesFile v WAS.UISIBPropertiesFile WAS.SibPersistMessages property is set to true. This property is required if the WAS.CronSIBPropertiesFile v WAS. This property is required if the WAS.SibDBUserName. For example. v WAS.SibPersistMessages property is set to true.SibDBUserPass Password for user ID named in WAS. db2fenc1. This property is required in the properties file that is specified in one of the following properties.Table 18.SibPersistMessages property is set to true.MIFSIBPropertiesFile v WAS. Control Desk properties (continued) Category Property Definition WAS. v WAS.SibDBInstallDir Where the service integration bus database is installed.MIFSIBPropertiesFile v WAS.CronSIBPropertiesFile v WAS.MIFSIBPropertiesFile v WAS. This property is only used for databases that are hosted on Linux and UNIX systems. v WAS. This property is required in the properties file that is specified in one of the following properties. This property is required if the database is hosted on a Linux or UNIX system.UISIBPropertiesFile 174 IBM Control Desk: Installation Guide (IBM WebSphere) . For example. c:\\program files\\ibm\\sqllib.

MIFSIBPropertiesFile v WAS.CronSIBPropertiesFile v WAS.CronSIBPropertiesFile v WAS. Command-line configuration 175 . Control Desk properties (continued) Category Property Definition WAS.UISIBPropertiesFile WAS.SibDbFencedPassword Password for the fenced user ID for the service integration bus database.Table 18.SibDbInstanceAdminUser Instance owner for the service integration bus database.UISIBPropertiesFile WAS. This property is required if the WAS. This property is required if the database is hosted on a Windows system.MIFSIBPropertiesFile v WAS.SibPersistMessages property is set to true. This property is required if the database is hosted on a Windows system.SibDbInstanceAdminPassword Password for the instance owner of the service integration bus database.SibPersistMessages property is set to true. v WAS. v WAS.CronSIBPropertiesFile v WAS. This property is required if the WAS. This property is required if the WAS. This property is required in the properties file that is specified in one of the following properties. This property is required in the properties file that is specified in one of the following properties.UISIBPropertiesFile Chapter 16. This property is required in the properties file that is specified in one of the following properties. v WAS.SibPersistMessages property is set to true. This property is required if the database is hosted on a Linux or UNIX system.MIFSIBPropertiesFile v WAS.

c=US.SibDbRemoteAccessPassword Password for user ID named in WAS. WAS.SibPersistMessages property is set to true.UIClusterName Name of the cluster that manages UI tasks. For example. ou=groups.Table 18.CronSIBPropertiesFile v WAS.ou=SWG. v WAS.SibDbRemoteAccessUser Database server system user that is used to configure the service integration bus remotely.SibPersistMessages property is set to true.UISIBPropertiesFile WAS.VmmUserRDN Relative Distinguished Name of the location of virtual member manager users. WAS. v WAS. 176 IBM Control Desk: Installation Guide (IBM WebSphere) . Set a value for this parameter if WAS. true.o=IBM.CronSIBPropertiesFile v WAS. This property is required in the properties file that is specified in one of the following properties.MIFSIBPropertiesFile v WAS. For example. This property is required if the WAS.o=IBM. ou=users. This property is required if the WAS. WAS.UseClustersForDeploy is set to true.SibDbRemoteAccessUser.MIFSIBPropertiesFile v WAS.ou=SWG.UISIBPropertiesFile WAS.VmmGroupRDN Relative Distinguished Name of the location of virtual member manager groups. This property is required in the properties file that is specified in one of the following properties. For example.UseClustersForDeploy Deploy the application EAR to a cluster. Control Desk properties (continued) Category Property Definition WAS.c=US.

CronClusterName Name of the cluster that manages cron tasks. c:\\sibdb_cr.Table 18.WAS.UseClustersForDeploy is set to true.ReportingClusterName Name of the cluster that manages reporting tasks. WAS.UseClustersForDeploy is set to true. Control Desk properties (continued) Category Property Definition WAS.CronEnableJMS Enable JMS for Maximo Enterprise Adapter for the cron task cluster. maximorpt.UseClustersForDeploy is set to true. Set a value for this parameter if WAS. For example. For example. WAS.UISIBPropertiesFile File that contains SIB persistence properties if you are persisting messages in the UI clusters bus. WAS.UseClustersForDeploy is set to true. Set a value for this parameter if WAS. Set a value for this parameter if WAS. For example.properties. true. WAS. c:\\sibdb_ui. For example.UseClustersForDeploy is set to true.properties. For example. Set a value for this parameter if WAS. Set a value for this parameter if WAS. For example. Chapter 16. maximocron.UIEnableJMS Enable or disable JMS for Maximo Enterprise Adapter for the UI cluster. Set a value for this parameter if WAS. WAS.UseClustersForDeploy is set to true. Command-line configuration 177 .CronSIBPropertiesFile File that contains SIB persistence properties if you are persisting messages in the cron clusters bus. true.

This value can be the same value used for the mtadminuser user.adminuserid User ID of the multi-tenancy configuration manager. mt. WAS.UseClustersForDeploy is set to true. For example. This property is required to enable multi-tenancy. mt. Set a value for this parameter if WAS.Table 18.sysprovider. MTM.desc Description of the multi-tenancy manager. Multi-tenancy mt. For example. mt.tenantcode Tenant code identifier for the multi-tenancy system provider. WAS. maximomea. maxadmin.UseClustersForDeploy is set to true. c:\\ sibdb_mif.properties. For example. Set a value for this parameter if WAS.UseClustersForDeploy is set to true. Set a value for this parameter if WAS.MIFClusterName Name of the cluster that manages Maximo Integration Framework tasks.configmanager.configmanager. 178 IBM Control Desk: Installation Guide (IBM WebSphere) .sysprovider.MIFEnableJMS Enable JMS for Maximo Enterprise Adapter for the Maximo Integration Framework task cluster. true.adminpassword Password for the User ID of the multi-tenancy configuration manager.MIFSIBPropertiesFile File that contains SIB persistence properties if you are persisting messages in the Maximo Integration Framework clusters bus. For example. This property is required to enable multi-tenancy. This value can be the same value used for the mtadminpwd value. For example. Control Desk properties (continued) Category Property Definition WAS. This property is required to enable multi-tenancy.

This value can be the same value used for the mtdbpwd value. This property is required to enable multi-tenancy.mt.mt. For example. mxe.mt.configmanager.dbuser User ID of the multi-tenancy configuration manager used to connect to the database.dbpassword Password for the user ID of the multi-tenancy configuration manager that is used to connect to the database.properties file during the maxinst operation. This is property is required to enable multi-tenancy. This property is set in the maximo. This value can be the same value used for the mtdbuser user. GA.enabled Value that indicates whether multi-tenancy is enabled. mt.properties file during the maxinst operation.db. Chapter 16. mt. For example.configmanager.desc Description of the multi-tenancy global administrator. mt.adminuser This value is the same as the value set for the mtdbuser parameter. Control Desk properties (continued) Category Property Definition mt. This property is required to enable multi-tenancy. 10. A value of 0 indicates that multi-tenancy is not enabled for the product.configmanager. ADMIN. This property is set in the maximo.extratenants Number of sample tenants to create when you enable multi-tenancy. For example. mxe. a value of 1 indicates that multi-tenancy is enabled.tenantcode Tenant code identifier for the multi-tenancy configuration manager.demo.Table 18.configmanager. For example. mxe. Command-line configuration 179 .

180 IBM Control Desk: Installation Guide (IBM WebSphere) .

Configuring your product with performance analysis data Configure Control Desk with optimized settings. tuneSystem -d install_dir -e env_name -w workspace_zip_file -r [generate|update] -c [warning|critical] -o output_dir -p plugin_name --debug Use this parameter to turn on debug logging. -w workspace_zip_file Use this parameter to enter the name of the zipped file containing the data that was collected when you used the IBM Performance Analysis Suite. 3. open a command prompt.sql is generated to update the Control Desk database. The system tuner utility takes IBM Performance Analysis Suite data and automatically configures your environment and middleware. 4. The IBM Performance Analysis Suite collects configuration data about the database. host operating system settings. -d install_dir Use this parameter to specify where the IBM Performance Analysis Suite is installed on the system. and change to the install_home\scripts directory. All parameters listed are required.Chapter 17.py is generated to update the Control © Copyright IBM Corp. You must manually run these scripts to re-configure Control Desk. 2015 181 . WebSphere Application Server Network Deployment and IBM HTTP Server. Click the link on the Control Desk launchpad to download the IBM Performance Analysis Suite from the IBM developerWorks community and install it on the Control Desk administrative workstation. Procedure 1. -e env_name Use this parameter to enter the name of the environment you defined when you used the IBM Performance Analysis Suite to collect data about your environment. 2. About this task The IBM Performance Analysis Suite checks Control Desk for compliance with best practices and optimized performance settings. -r [generate|update] Use this parameter to generate scripts to update Control Desk configuration. applies a set of performance metrics to the data. the scripts are generated in the output directory you specify. If you use generate. A file with an extension of . A file with an extension of . Analyze your Control Desk deployment with the IBM Performance Analysis Suite and export the IBM Performance Analysis Suite workspace. Refer to the IBM Performance Analysis Suite developerWorks community for information about using IBM Performance Analysis Suite. and then generates a report. Run the tuneSystem command. Log on to the Control Desk administrative workstation.

-h Use this parameter to display help for the tuneSystem command.com/developerworks/community/blogs/28cb6d68-ab67- 4203-96f9-5538e654a5ff/entry/june_16_2013_11_07_pm https://www.bat is generated to update the Control Desk administrative workstation. If you use warning.com/developerworks/community/wikis/home?lang=en- us#!/wiki/W16f314e69702_46b3_9252_04023c060b9a 182 IBM Control Desk: Installation Guide (IBM WebSphere) . Desk application server. If you use critical. tuneSystem -d install_dir -e env_name -w workspace_zip_file -r [generate|update] -c [warning|critical] -o output_dir -p plugin_name What to do next Use the IBM Performance Analysis Suite and the tuneSystem command to perform Control Desk configuration updates as part of your regularly scheduled maintenance program. Related information: https://www. If you use update. the scripts are generated and then run on the system to update Control Desk configuration. A file with an extension of .sh or . configuration values that were categorized as critical by the IBM Performance Analysis Suite are updated by the Control Desk system tuner utility.ibm. -c [warning|critical] Use this parameter to specify which conditions identified by the IBM Performance Analysis Suite to update in Control Desk. -o output_dir Use this parameter to specify where to output the scripts generated by the Control Desk system tuner utility. -p plugin_name Use this parameter to enter the name of the plugin you specified when you used the IBM Performance Analysis Suite. configuration values that were categorized as either critical or warnings by the IBM Performance Analysis Suite are updated by the Control Desk system tuner utility.ibm.

About this task The default installation directory on the administrative workstation is \ibm. it is a good idea to establish a process and schedule for backing up Control Desk data. you restore the database back up at the same time you restore the administrative workstation back up it was paired with. 2015 183 . To back up critical Control Desk information. Also. which includes all class files and customizations that have been performed in your environment. Restoring the administrative workstation Restore previously backed up Control Desk administrative workstation information. This directory contains the critical files for your Control Desk deployment. Specifically. © Copyright IBM Corp. Back up the Control Desk database. the administrative workstation contains the following items: v Class files and customizations performed in your environment. This information can be used to return an existing Control Desk administrative workstation to a previous state. this directory is \IBM\SMP. 2. Plan to back up Control Desk administrative workstation data just after initial deployment and schedule periodic backups on an ongoing basis. Backup and restoration Like all important business data. This directory contains the critical files for your Control Desk deployment. Ensure that all file permissions are preserved.Chapter 18. It is important to make a back up of the database at the same time that you back up the administrative workstation. The default installation directory on the Control Desk administrative workstation is C:\ibm. Back up and restore middleware application data using the methods described in the documentation for that product is important. the current Enterprise Archive (EAR) file. J2EE server. By default. and the properties files and installation tools used for your environment. Backing up the administrative workstation It is recommended that you back up all Control Desk middleware applications and Control Desk administrative workstation on a regular basis. and authentication server information using the instructions provided by your middleware vendors. v The current Enterprise Archive (EAR) file that was deployed to the application server. establish a process for backing up data contained on the Control Desk administrative workstation. Create a backup of the installation directory. During restoration. complete the following steps: Procedure 1. v The properties files and installation tools used for your environment.

2. For example. 184 IBM Control Desk: Installation Guide (IBM WebSphere) . Copy the Control Desk installation files and directories to the file system of the target administrative system. 3. Before you begin Restore the back up of the database that was made when you backed up the administrative workstation. complete the following steps: Procedure 1. Log on to the target administrative system with the same user ID that was used to install the product on the existing administrative workstation. you cannot copy those files to a \NewAdminWS\IBM\SMP directory on the target administrative workstation. Restore the database backup that was paired with the administrative workstation backup you are restoring. You must maintain the directory structure of the original installation. About this task To restore Control Desk information to an administrative workstation. A database back up must be restored with the administrative workstation backup it was paired with. if the Control Desk installation directory on the existing administrative system is \IBM\SMP.

Process managers of previously deployed products are also removed when you uninstall Control Desk. click Configure Product. the application server and JMS queue information are removed. and click Launch the Tivoli’s Process Automation Suite configuration program. 4. 5. © Copyright IBM Corp. The instance user. specify credentials to access the database and servers you previously configured for Control Desk. 2. table spaces. Control Desk uninstallation is a comprehensive procedure and does not support partial removal of individual components or process managers. Control Desk can only be uninstalled using the Control Desk installation and configuration programs. Removing WebSphere Application Server Network Deployment configuration data Removing the WebSphere Application Server Network Deployment configuration with the configuration program deletes all configuration data. Click Finish and OK. Removing Control Desk configuration values The first step to uninstall Control Desk is to remove configuration values using the configuration program. Log on to the application server with the admin console and stop all of the Control Desk applications. In the Remove Product Configuration Information panel. After you uninstall Control Desk. including process managers that are deployed by other products. click Remove Product Configuration Information. In the IBM Control Desk configuration operations page. and then uninstalling Control Desk. In the launchpad navigation pane. and system users that were created with the configuration program can also be removed. specify Control Desk installation location. Procedure 1. 2015 185 . About this task If you choose the option to delete the database instance. 3. the database and the database instance are removed. If you choose the option to delete application server artifacts. Do not use other methods to attempt to uninstall Control Desk. Start the configuration program from the Control Desk launchpad. database users. Uninstalling the product Uninstalling Control Desk involves removing configuration values from Control Desk and associated middleware. Specify credentials for the administrative user to uninstall the Control Desk application. you can reinstall it using the Control Desk installation and configuration programs. such as the Add/Remove Programs panel.Chapter 19.

2. click Configure Product. Select the packages that you want to remove and click Next. select the Unconfigure WebSphere Application Server Network Deployment option. Open the configuration program rom the Control Desk launchpad. Stop all DB2 and WebSphere Application Server Network Deployment processes on the system. 3. 186 IBM Control Desk: Installation Guide (IBM WebSphere) . In the Unconfigure Middleware panel. click Unconfigure WebSphere Application Server. 2. Windows UNIX C:\Program Files\IBM\Installation IBMIM. From the IBM Installation Manager interface. Procedure 1. click Finish and OK. specify credentials for the WebSphere administrative user to remove WebSphere Application Server Network Deployment profile information and click Next. 4. Uninstalling Control Desk and middleware Use the Installation Manager software to uninstall Control Desk and any middleware that was installed with Control Desk. Review the package summary information and click Uninstall to remove the selected packages. You must run Installation Manager locally on the system that hosts the component that you want to uninstall. click Uninstall. use the Installation Manager software to uninstall previously installed components.exe 3.sh Manager\eclipse\IBMIM. In the Unconfigure WebSphere panel. specify the Control Desk installation location and click Launch the Tivoli’s Process Automation Suite configuration program. In the launchpad navigation pane. Procedure 1. Open a command prompt and start Installation Manager. 5. 4. In the IBM Control Desk configuration operations page. About this task After you use the configuration program to unconfigure Control Desk and associated middleware.

program. INCLUDING. program. Any functionally equivalent product. You can send license inquiries. 2015 187 . Changes are periodically made to the information herein. MD-NC119 Armonk. or service may be used. Any reference to an IBM product. in writing. or service is not intended to state or imply that only that IBM product. IBM may have patents or pending patent applications covering subject matter described in this document. or service. therefore. program. IBM may not offer the products. This information could include technical inaccuracies or typographical errors. services. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. program. it is the user's responsibility to evaluate and verify the operation of any non-IBM product. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. However. Some states do not allow disclaimer of express or implied warranties in certain transactions. contact the IBM Intellectual Property Department in your country or send inquiries. this statement may not apply to you. or service that does not infringe any IBM intellectual property right may be used instead. 19-21. BUT NOT LIMITED TO. Chuo-ku Tokyo 103-8510. 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. Nihonbashi-Hakozakicho. EITHER EXPRESS OR IMPLIED. 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. to: IBM Director of Licensing IBM Corporation North Castle Drive. in writing. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those © Copyright IBM Corp. or features discussed in this document in other countries. NY 10504-1785 United States of America For license inquiries regarding double-byte character set (DBCS) information. Consult your local IBM representative for information on the products and services currently available in your area. The furnishing of this document does not grant you any license to these patents.Notices This information was developed for products and services that are offered in the USA. these changes will be incorporated in new editions of the publication.

All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. compatibility or any other claims related to non-IBM products. the examples include the names of individuals. payment of a fee. 2015. Users of this document should verify the applicable data for their specific environment. © Copyright IBM Corp. the results obtained in other operating environments may vary significantly. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement. Any performance data contained herein was determined in a controlled environment. brands. Information concerning non-IBM products was obtained from the suppliers of those products. 188 IBM Control Desk: Installation Guide (IBM WebSphere) . NY 10504-1785 U. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM International Program License Agreement or any equivalent agreement between us. This information is for planning purposes only. some measurements may have been estimated through extrapolation. Furthermore. are current and are subject to change without notice. Dealer prices may vary. All rights reserved. Such information may be available. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice. their published announcements or other publicly available sources. subject to appropriate terms and conditions. The information herein is subject to change before the products described become available. To illustrate them as completely as possible. All IBM prices shown are IBM's suggested retail prices. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. and products. This information contains examples of data and reports used in daily business operations. Therefore. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM has not tested those products and cannot confirm the accuracy of performance.A. should contact: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. including in some cases. 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. Actual results may vary. companies. 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.S. websites. and represent goals and objectives only.

and ibm. distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. to the publications or any information. the use of the publications is detrimental to its interest or. the IBM logo. other countries. IBM reserves the right to withdraw the permissions granted herein whenever. Microsoft. You may not distribute. noncommercial use provided that all proprietary notices are preserved. Other product and service names might be trademarks of IBM or other companies. UNIX is a registered trademark of The Open Group in the United States and other countries. without the express consent of IBM. no other permissions.ibm. Windows. or any portion thereof. Personal use You may reproduce these publications for your personal. Terms and conditions for product documentation Permissions for the use of these publications are granted subject to the following terms and conditions. registered in many jurisdictions worldwide. Commercial use You may reproduce. distribute or display these publications or any portion thereof outside your enterprise. A current list of IBM trademarks is available on the web at www. software or other intellectual property contained therein. other countries. the above instructions are not being properly followed. or both. Rights Except as expressly granted in this permission.shtml.com/legal/ copytrade. licenses or rights are granted. in its discretion. data. or reproduce. or both..com are trademarks or registered trademarks of International Business Machines Corp. Linux is a registered trademark of Linus Torvalds in the United States. display or make derivative work of these publications. without the express consent of IBM. Notices 189 . either express or implied. as determined by IBM. and the Windows logo are trademarks of Microsoft Corporation in the United States. You may not make derivative works of these publications. Applicability These terms and conditions are in addition to any terms of use for the IBM website.Trademarks IBM.

INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY. including all United States export laws and regulations. EITHER EXPRESSED OR IMPLIED. export or re-export this information except in full compliance with all applicable laws and regulations. You may not download. NON-INFRINGEMENT. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND. 190 IBM Control Desk: Installation Guide (IBM WebSphere) . IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. AND FITNESS FOR A PARTICULAR PURPOSE.

124 deployJ2eeConfiguration 155 executeMapping command 128 UNIX systems 120. 88 installation prerequisites. 92 Configuration 154 command line configuration uninstalling 186 action program 143 IBM Security Directory Server validateDatabaseConfiguration 152 validate configuration parameters manually configuring 36 action validateJ2eeConfiguration 154 from the command line 143 IBM WebSphere Application Server administrative workstation confirming the Integration Composer Network Deployment backing up 183 installation 125 HTTPOnly 113 restoring 184 continuous inbound (CQIN) JMS queue install AIX creating 75 automatic middleware asynchronous I/O. Integration parameters 145 directory server Composer 118 Command line configuration program manually configuring 36 installation program actions 152 logs 115 configuration 134 installing 54. 58. 26. 123 database server 29 Installation DB2 post-installation tasks 134 C manual configuration. enabling 10 Control Desk configuration 19 descriptor numbers 8 configuring in a cluster clustered environment 87 file size 8 environment 94 install silently 98 fonts 8 configuring with the Control Desk installation large page size support 9 configuration program 85 automatically configuring existing paging space 8 remove configuration 185 middleware 25 tar command 7 CQINERR JMS queue deploying using manual middleware asynchronous I/O creating 79 configuration 29 enabling on AIX 10 deploying with manually configured authentication service 54. 2015 191 .6 22. deployMiddlewareConfiguration 157 updateApplication 156 Integration Composer 117 action disableAppSecurity 156 updateDatabaseConfiguration 152 help 133 action enableAppSecurity 156 updateJ2eeConfiguration 154 help information action enableDB2TextSearch 154 validate And Update Database installing in multiple languages 133 action reapplyAppServerTuning 156 Configuration 153 HTTP server 13 action removeConfiguration 155 validate And Update J2ee HTTPOnly action Configuration 154 configuring 113 removeDatabaseConfiguration 154 validateDatabaseConfiguration 152 action removeJ2EEConfiguration 155 validateJ2eeConfiguration 154 action updateApplication 156 action updateDatabaseConfiguration 152 configure Control Desk silently 103 configure middleware silently 102 I action updateJ2eeConfiguration 154 configuring 68 IBM Control Desk action validate And Update Database database server 29 configuring with the IBM Control Configuration 153 silent 101 Desk configuration program 24. 84.Index A configuration actions (continued) disableAppSecurity 156 F action addLanguages 156 enableAppSecurity 156 fonts action configureProducts 157 enableDB2TextSearch 154 AIX 8 action deployConfiguration 155 reapplyAppServerTuning 156 action deployDatabaseConfiguration 153 removeConfiguration 155 action deployJ2eeConfiguration 155 action removeDatabaseConfiguration 154 H removeJ2EEConfiguration 155 hardware and software requirements. 27 action validate And Update J2ee configuring Control Desk installing version 7. 68 middleware 29 Integration Composer D with launchpad 117 B data source manually creating for the persistent preparing 1 program logs 115 backup 183 store 45 Tivoli Integration Composer 118. v10.5 30 Installation Manager command line configuration program DB2 v10. 124 deployMiddlewareConfiguration 157 © Copyright IBM Corp.5 installing silently 97 input properties files 144 installing 20. 58 configuration actions E silent 95 addLanguages 156 EAR files Integration Composer configureProducts 157 building manually 139 installing deployConfiguration 155 maintaining 139 with process solution installation deployDatabaseConfiguration 153 error queue 77 package 120.

configuring 11 uninstall shared memory. setting 11 R middleware 186 product 185 remove configuration uninstalling Integration Composer 129 Control Desk 185 uninstalling Integration Composer on WebSphere Application Server M Network Deployment 186 Unix-based operating systems 129 uninstalling Integration Composer on memory allocation restoration 183 Windows operating systems 129 changing 128 users Microsoft Active Directory groups configuring 40 Microsoft SQL Server S synchronizing 138 sequential inbound (SQIN) JMS queue synchronizing 138 manual configuration 34 middleware 95. 87 startFusion file J2EE server paging space AIX 8 memory allocation 127 manually configuring 42 password swap size JMS activation specification updating in response files 97 setting in Linux 11 creating for the continuous inbound password policies 14 system directories queue (CQIN) 77 performance analysis data accessing 7 creating for the inbound error queue importing 181 system file settings (CQINERR) 79 port availability AIX JMS connection factory check 6 descriptor numbers 8 creating 75 post installation 133 file size 8 JMS queues manually configure 71 post-installation tasks 125 JRE prerequisite 95. 103 WebSphere Application Server Network sample response files 96 Deployment configuration tasks 48 192 IBM Control Desk: Installation Guide (IBM WebSphere) . Integration Composer 117 middleware configuration 101 hardware and software 117 SQL Server Integration Composer. setting 12 IBM Control Desk 186 swap size. 101 configuring in Linux 11 product T remove configuration silently 105 tar command product configuration program AIX 7 overview 16 L product installation Tivoli Integration Composer installation 118 language enablement 137 before you begin 1 upgrade 123 launchpad product installation program starting 15 overview 16 libraries profiles Linux 10 creating in WebSphere 43 U required libraries 10 properties ulimit Linux Control Desk 158 setting in Linux 11 JRE. 102. 12c 31 installation 95 Integration Composer requirements. 25. setting 11 ulimit. uninstalling 129 preparing 14 P SSL page size support client authentication workaround 13 J AIX 9 configuring 19.Integration Composer installation prerequisites 118 O silent installation uninstallation 98 Integration Composer installation. online help 133 silent response file confirming 125 Oracle Control Desk configuration 102 Integration Composer overview 117 manual configuration. 101 creating 76 remote configuration 12 sequential outbound (SQOUT) JMS queue remove configuration silently 104 creating 76 V middleware installation service integration bus verifying prerequisites before you begin 1 adding a server 72 command line 2 middlware configuration service integration bus destination verifying the installation silent sample response files 101 creating for the continuous inbound manually 111 multi-language help information 133 (CQINBD) queue 72 programmatically 107 creating for the inbound error queue VMM (CQINERRBD) queue 78 manual configuration 80 creating for the sequential inbound N (SQINBD) queue 73 node agent creating for the sequential outbound creating as a Windows service 54 (SQOUTBD) queue 74 W nstallation shared memory WebSphere before you begin 1 setting in Linux 12 manually creating profiles 43 silent install 98. overview.

89 X xml request pages 137 Index 193 . 90 WebSphere Application Server Network Deployment v8. 26.WebSphere Application Server Network Deployment (continued) install Control Desk applications 140 manually configuring 43 manually uninstalling 140 remove configuration 186 WebSphere Application Server Network Deployment servers configuring application server cluster profiles 90 configuring cluster members on additional WebSphere nodes 91 preparing for Control Desk configuration 91 preparing for IBM Control Desk configuration 22.5 installing 21.

194 IBM Control Desk: Installation Guide (IBM WebSphere) .

.

IBM® Printed in USA .