Planning worksheets for middleware installation

Before you start the installation, use the planning worksheets to record values to specify when installing the components you choose for your deployment. For distributed deployments, record multiple values where appropriate.

The worksheets are also helpful if you intend to manually configure or reuse existing middleware.

Directory structure for middleware products

Do not install multiple middleware products into the same custom directory.

For example, when installing DB2®, WebSphere® Application Server Network Deployment, and IBM® Security Directory Server on the same computer, you cannot install them all in a C:\ISM_middleware directory. You can, however, install them in C:\ISM_middleware\DB2, C:\ISM_middleware\WAS, and C:\ISM_middleware\ITDS. You also cannot install one middleware product in a custom directory and then install another middleware product in a subdirectory of that custom directory. For example, if you install DB2 into C:\ISM_middleware, you cannot then install IBM Security Directory Server into C:\ISM_middleware\ITDS.

Users and groups

When you run the middleware installation program, you are prompted for user IDs to initiate the installation of middleware. You can either supply an existing system user ID, or allow the middleware installation program to create a user ID.

Note: The installation can fail on Linux and UNIX operating systems if you specify an existing user account to install and that user account is not located under the /home directory.

In this table, list the users and groups that you want to create if you do not want to use the default values.

Table 1. Users and groups created during Control Desk deployment
User Group Description Your value
db2admin (Windows only)
Windows
  • Administrators
  • DB2USERS
  • DB2ADMNS
 DB2 administrator. Windows Service user ID.

This user only required for deployments using DB2.

  
idsccmdb
Note: The root user must also be a member of the primary group of the IBM Security Directory Server instance user (by default, idsccmdb).
Linux and UNIX
  • dasadm1

    This value cannot be changed when using the middleware installer.

  • idsldap

    This value cannot be changed when using the middleware installer.

  • dbsysadm

    This value cannot be changed when using the middleware installer.

 IBM Security Directory Server instance owner. Also the owner of the database used with the IBM Security Directory Server instance.

This user only required for deployments using IBM Security Directory Server.

  
maximo   Used for Maximo database configuration.  
ctginst1
Linux and UNIX
  • dasadm1

    This value cannot be changed when using the middleware installer.

  • db2iadm1
 The system user that is used as the database instance owner on UNIX systems.

This user only required for deployments using DB2.

  
db2fenc1
Linux and UNIX
  • db2fgrp1
 System user that is used as the fenced user ID for the DB2 default instance of db2inst1.

This user only required for deployments using DB2.

  
ctgfenc1
Linux and UNIX
  • ctgfgrp1

    This value cannot be changed when using the middleware installation program.

 System user that is used as the fenced user ID for the DB2 server instance of ctginst1.

This user only required for deployments using DB2.

  
dasusr1
Linux and UNIX
  • dasadm1

    This value cannot be changed when using the middleware installation program.

 System user used as the administration server user.

This user only required for deployments using DB2.

  
db2inst1
Linux and UNIX
  • dasadm1

    This value cannot be changed when using the middleware installation program.

  • db2iadm1
 System user used as the default database instance owner.

This user only required for deployments using DB2.

  
idsldap

This value cannot be changed when using the middleware installer.
Linux and UNIX
  • idsldap

    This value cannot be changed when using the middleware installation program.

  • db2iadm1
  • root
 IBM Security Directory Server user.

This user only required for deployments using DB2.

  
wasadmin Not a system user. User ID created for use with IBM WebSphere Application Server Network Deployment.

This user only required for deployments using IBM WebSphere Application Server Network Deployment.

  

For Linux and UNIX systems, the root user must be a member of the dasadm1, idsldap, and dbsysadm groups. The root user must also be a member of the primary group of the IBM Security Directory Server instance user (by default, idsccmdb).

The following example illustrates users and groups created if you use the middleware installation program to install middleware on Linux and UNIX systems using default values. Use this information to determine the primary group of a user ID.
# id db2inst1
uid=510(db2inst1) gid=102(db2iadm1) groups=102(db2iadm1),101(dasadm1)

#id ctginst1
uid=512(ctginst1) gid=102(db2iadm1) groups=102(db2iadm1),101(dasadm1)

# id idsccmdb
uid=514(idsccmdb) gid=502(dbsysadm) groups=502(dbsysadm),101(dasadm1),501(idsldap)

# id db2fenc1
uid=511(db2fenc1) gid=103(db2fgrp1) groups=103(db2fgrp1)

# id ctgfenc1
uid=513(ctgfenc1) gid=104(ctgfgrp1) groups=104(ctgfgrp1)

# id dasusr1
uid=508(dasusr1) gid=101(dasadm1) groups=101(dasadm1)

# id idsldap
uid=513(idsldap) gid=501(idsldap) groups=501(idsldap),0(root),102(db2iadm1)

#id root
uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),
6(disk),10(wheel),501(idsldap),502(dbsysadm)
The following entries are found in the /etc/group file:
dasadm1:x:101:db2inst1,ctginst1,idsccmdb

db2iadm1:x:102:idsldap

idsldap:x:501:idsldap,root,idsccmdb

dbsysadm:x:502:root

Directory locations

In this table, list the middleware directory locations to use.

Table 2. Directory locations
Setting Default Your value
Workspace directory user_home\ibm\tivoli\mwi\workspace  
Middleware images source directory    
Compressed images directory    
Uncompressed images directory    

DB2 configuration

In this table, list the configuration values to use when you install DB2.

Table 3. DB2 configuration
Setting Default Your value
Installation directory
Windows
SystemDrive\Program Files\IBM\SQLLIB
Linux, AIX®, HP-UX, Solaris
/opt/IBM/db2/V9.7
  
DAS user
Windows
db2admin
Linux, AIX, HP-UX, Solaris
dasusr1
  
Fenced user for the DB2 default instance
Linux, AIX, HP-UX, Solaris
db2fenc1

The option to create the DB2 default instance is not enabled in the middleware installation program, by default.

  
Fenced user group name for the DB2 default instance
Linux, AIX, HP-UX, Solaris
db2fgrp1

The option to create the DB2 default instance is not enabled in the middleware installation program, by default.

  
Fenced user for the DB2 default instance home directory
Linux, AIX, HP-UX
/home/db2fenc1
Solaris
/export/home/db2fenc1

The option to create the DB2 default instance is not enabled in the middleware installation program, by default.

  
Fenced user for the DB2 server instance
Linux, AIX, HP-UX, Solaris
ctgfenc1
  
Fenced user group name for the DB2 server instance
Linux, AIX, HP-UX, Solaris
ctgfgrp1
  
Fenced user for the DB2 server instance home directory
Linux, AIX, HP-UX
/home/ctgfenc1
Solaris
/export/home/db2fenc1
  
Instance name ctginst1  
Port 50005  
Instance user name home directory
Linux, AIX, HP-UX
/home/ctginst1
Solaris
/export/home/ctginst1
  
Database instance user ID
Windows
db2admin
Linux, AIX, HP-UX, Solaris
ctginst1
  
DB2 administrators group
Windows
DB2ADMNS
Linux, AIX, HP-UX, Solaris
db2iadm1
  
DB2 users group
Windows
DB2USERS
  
Use same user name and password for remaining DB2 Services YES  
Configure Tools Catalog NO

This value is relevant for reuse scenarios only.

  
Enable operating system security for DB2 objects YES

This value is relevant for reuse scenarios only.

  
DB2 instance port    
Data table space name MAXDATA  
Data table space size medium (1000 MB)
DB2
Medium (5000 MB)
  
Temporary table space name MAXTEMP  
Temporary table space size 1000 MB  

Oracle configuration

In this table, list the configuration values to use when you install Oracle.

Table 4. Oracle configuration
Setting Default Your value
Installation directory
Windows
SystemDrive\oracle\product\11.2.0\db_1
Linux, AIX, HP-UX, Solaris
/opt/app/oracle/product/11.2.0/db_1
  
Administrator User ID sys  
Oracle Software Owner ID
Windows
Administrator
Linux, AIX, HP-UX, Solaris
oracle
  
Instance Location
Windows
C:\oracle\product\11.2.0\db_1
Linux, AIX, HP-UX, Solaris
/opt/app/oracle/product/11.2.0/db_1
  
Data table space name MAXDATA  
Data table space size
Oracle
Medium (1000 MB)
  
Temporary table space name MAXTEMP  
Temporary table space size 1000 MB  

Microsoft SQL Server configuration

In this table, list the configuration values to use when you install Microsoft SQL Server.

Table 5. Microsoft SQL Server configuration
Setting Default Your value
Installation directory ProgramFiles\Microsoft SQL Server\90  
Named instance maximo  
Microsoft SQL Server administrator sa  
Microsoft SQL Server administrator password    
Port 1433  
Database name maxdb75  
User ID maximo  
User ID password    
Data file name maxdb75_dat  
Log file name maxdb75_log  

WebSphere Application Server Network Deployment configuration

List the configuration values to use when you install WebSphere Application Server Network Deployment.

Table 6. WebSphere Application Server Network Deployment configuration
Setting Default Your value
Installation location
Windows
C:\Program Files\IBM\WebSphere\AppServer
Linux, HP-UX, Solaris
/opt/IBM/WebSphere/AppServer
AIX
/usr/IBM/WebSphere/AppServer
  
WebSphere Administration user name wasadmin  
Deployment Manager profile name ctgDmgr01  
Application server profile name ctgAppSrv01  
Profile directory
Linux, HP-UX, Solaris
/opt/IBM/WebSphere/AppServer/profiles
AIX
/usr/IBM/WebSphere/AppServer/profiles
  
Cell name ctgCell01  
Deployment Manager node name ctgCellManager01  
Application server node name ctgNode01  
HTTP server installation location
Windows
C:\Program Files\IBM\HTTPServer
Linux, HP-UX, Solaris
/opt/IBM/HTTPServer
AIX
/usr/IBM/HTTPServer
  
HTTP port 80

On Windows, this port might already be in use. Ensure that you either free this port, or use another port that is unassigned.

  
HTTP admin server port 8008  
HTTP plug-in profile name ctgAppSvr01  

Oracle WebLogic Server configuration

List the configuration values to use when configuring Oracle WebLogic Server.

Table 7. Oracle WebLogic Server configuration
Setting Default Your value
Domain source
Windows:
\wlserver_10.3\common\templates\domains
Linux, Solaris:
/wlserver_10.3/common/templates/domains
  
Customize environment and services settings No.
Note: If you plan to implement integration framework - YES.
  
Domain name my_domain
Note: Enter any name except for MAXIMOSERVER
  
Administration server name MAXIMOSERVER  
Listen address All Local Addresses  
Listen port 7001  
Start Menu shortcut link name Start Server  
Start Server program name startWebLogic.cmd  

IBM Security Directory Server configuration

In this table, list the configuration values to use when you install IBM Security Directory Server.

Table 8. IBM Security Directory Server configuration
Setting Default Your value
Install location
Windows
C:\Program Files\IBM\LDAP\V6.3
Linux, AIX, HP-UX, Solaris
/opt/IBM/ldap/V6.3
  
Administrator distinguished name cn=root  
Organizational unit ou=SWG  
Organization and country suffix o=IBM,c=US  
Directory server port 389  
Directory server secure port 636  
Administration port 3538  
Administration secure port 3539  
Database name security  
Instance name idsccmdb  
Instance user name idsccmdb  

Microsoft Active Directory configuration

List the configuration values to use when you install Microsoft Active Directory.

Table 9. Microsoft Active Directory configuration
Setting Default Your value
Directory server port 389  
LDAP base entry    
User suffix    
Group suffix    
Organization container suffix    
Bind distinguished name    
Parent topic: Reference

Feedback