ibm smartcloud control desk version 7 release 5€¦ · websphere application server network...

IBM SmartCloud Control DeskVersion 7 Release 5

Planning for Deployment Guide

��

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

Contents

Chapter 1. Prerequisite hardware andsoftware . . . . . . . . . . . . . . 1

Chapter 2. Planning to deploy . . . . . 3Deployment topologies . . . . . . . . . . . 3

Administrative workstation . . . . . . . . 4Single server deployment . . . . . . . . . 4Multiple server deployment . . . . . . . . 4

Planning for security . . . . . . . . . . . 6Planning for serviceability . . . . . . . . . . 7Planning language support . . . . . . . . . 8Installation program log information . . . . . . 9

Chapter 3. Deployment scenario roadmaps . . . . . . . . . . . . . . . 11

Chapter 4. Installation options . . . . 13Simple or custom option . . . . . . . . . . 13Deferring database update and ear file deployment 13

Chapter 5. Middleware . . . . . . . . 15Middleware installation program workspace . . . 17Middleware configuration options . . . . . . . 18Middleware object naming conventions . . . . . 18

Chapter 6. Performing multiple productinstallations on one administrativeworkstation. . . . . . . . . . . . . 23

Chapter 7. DVD layout . . . . . . . . 25

Appendix A. Installation program tasks 27

Appendix B. Planning worksheets formiddleware installation. . . . . . . . 31

Appendix C. Planning worksheets formanual middleware configuration . . . 41

Appendix D. Planning worksheet forproduct installation . . . . . . . . . 53

Notices . . . . . . . . . . . . . . 55Trademarks . . . . . . . . . . . . . . 57

Index . . . . . . . . . . . . . . . 59

© Copyright IBM Corp. 2007, 2011 iii

iv IBM SmartCloud Control Desk: Planning for Deployment Guide

Chapter 1. Prerequisite hardware and software

As you plan your deployment, review the list of prerequisite hardware andsoftware

The prerequisite hardware and software are listed on the product wiki athttps://www.ibm.com/developerworks/wikis/display/tivoli/SmartCloud+Control+Desk+-+System+Requirements.

These requirements are the minimum for a working system. Best practices formaximizing the performance of your system are available at developerWorks.

Use these two resources together to design the environment into which you willdeploy the product.

For a list of the product DVDs or images, refer to the download document athttp://www.ibm.com/support/search.wss?q=sccd75download.

© Copyright IBM Corp. 2007, 2011 1

https://www.ibm.com/developerworks/wikis/display/tivoli/SmartCloud+Control+Desk+-+System+Requirements

https://www.ibm.com/developerworks/wikis/display/tivoli/SmartCloud+Control+Desk+-+System+Requirements

https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=a9ba1efe-b731-4317-9724-a181d6155e3a#fullpageWidgetId=W5f281fe58c09_49c7_9fa4_e094f86b7e98&file=c51d5f5b-dea3-4043-a81f-d5213fc10063

http://www.ibm.com/support/search.wss?q=sccd75download

2 IBM SmartCloud Control Desk: Planning for Deployment Guide

Chapter 2. Planning to deploy

Planning your SmartCloud Control Desk installation is critical to ensure that yourdeployment is successful.

Review the deployment information and prepare your environment to suit yourbusiness needs. Use the planning worksheets that are provided to record thevalues you use during the installation process. Recording this information is usefulfor future installations of SmartCloud Control Desk.

When you have reviewed the deployment information, and when yourdeployment plan is complete, refer to the SmartCloud Control Desk installationinformation to begin your installation.

Deployment topologiesDetermine the most suitable deployment option for your environment andbusiness needs.

SmartCloud Control Desk works with various databases and J2EE server software,as listed in the system requirements information. You use the middlewareinstallation program to install IBM® middleware products such as IBM DB2® andIBM WebSphere® Application Server Network Deployment. You can also reuseexisting resources in your environment, which can include supported versions ofboth IBM and non-IBM middleware, such as Microsoft SQL Server, OracleWebLogic Server, and Oracle.

Although IBM middleware is included with SmartCloud Control Desk, you candeploy SmartCloud Control Desk with non-IBM middleware exclusively.

There are two primary strategies to deploying SmartCloud Control Desk in yourenterprise.

Single-serverThe single-server topology consists loading all SmartCloud Control Deskcomponents, including all SmartCloud Control Desk middleware, theSmartCloud Control Desk administrative workstation, process managers,TADDM, and so on, onto one server. This deployment is typical forproof-of-concept purposes, as a demonstration, or to create a learningenvironment. For managing enterprise assets and processes, you wouldtypically implement a multi-server topology.

Multi-serverThe multi-server topology consists of splitting SmartCloud Control Deskcomponents across several different servers. This method is beneficial, as itoptimizes resource use and decreases the workload for each system. Thistype of deployment would be typical for production use within anenterprise.

In a disparate environment, the collection of computers in this deploymentcan be a mixture of Windows and UNIX computers.

In IBM WebSphere Application Server Network Deployment, you cancreate deployment managers that provide centralized administration ofmanaged application server nodes and custom nodes as a single cell. IBM


WebSphere Application Server Network Deployment provides basicclustering and caching support, including work balancing, automatedperformance optimization, and centralized management and monitoring.

The Oracle WebLogic Server configuration requires, at a minimum, a singleadministration server on a single computer.

A typical deployment life cycle can begin with a single-server topology andprogress to a multi-server topology. This progression can occur if you start with ademonstration phase and then move onward to a functional proof-of-concept.Next, you test the integration in the existing environment and move toward a pilotmulti-server environment. Finally, you move to a multi-server productiondeployment in the enterprise.

SmartCloud Control Desk is built upon the process automation engine. The processautomation engine is a core set of functions used by Integrated ServiceManagement (ISM) products. It serves as a common base for shared services andapplications inherited by all SmartCloud Control Desk based products. Processmanagers are workflow-based applications that you can use to create executableprocess flows.

Process managers provide a user interface that can be used to:v Perform process proceduresv Gather information from various sourcesv Interact with external toolsv Use and update information in a databasev Provide information to monitoring, analysis, and reporting tools

In addition, you can track execution metrics and use dashboards and reports toidentify bottlenecks and improve organizational productivity.

Administrative workstationYou install SmartCloud Control Desk on an administrative workstation that isrunning a UNIX or Windows operating system. The administrative workstation iswhere the product EAR files are built and later deployed to the application server.

The administrative workstation is used in all phases of the product life cycle. It isrequired for the initial installation and configuration of SmartCloud Control Desk.You also use the administrative workstation to install program fixes, productupgrades, new applications, new process managers, and additional language packs.

Single server deploymentYou can use a single server deployment as a proof-of-concept, as an educationaltool, or as a demonstration configuration.

During installation on a single server, you must select either the simple installationpath or the custom installation path. If you choose the simple installation path,SmartCloud Control Desk middleware is installed on the system with defaultvalues that you cannot change. If you choose the custom installation path, you canspecify your own values.

Multiple server deploymentYou can implement a multiple server deployment by reusing existing componentsor by installing all new components.


You can simplify the deployment by installing all new components with theSmartCloud Control Desk middleware and product installation programs. If youplan to reuse or migrate resources that exist in your network, adjust your rolloutplan to allow time for additional tasks. For example, you must bring the existingresources to version levels that are compatible with SmartCloud Control Desk.

In the following figure, SmartCloud Control Desk has been deployed with TADDMand LDAP security on a collection of systems.

The required components for SmartCloud Control Desk are all installed ondifferent servers.

Important: In certain cases, you must avoid the sharing of resources. For example,do not share one DB2 database instance between SmartCloud Control Desk andIBM Tivoli® Directory Server. During installation, the database instance is restarted,which can disrupt the availability of IBM Tivoli Directory Server for yourenterprise.

If you are using the automated installation programs, separate database instancesare created for use by SmartCloud Control Desk and IBM Tivoli Directory Server.

In a disparate environment, the collection of servers can be a combination ofWindows and UNIX servers.

With Oracle WebLogic Server or WebSphere Application Server NetworkDeployment you can create deployment managers that provide centralizedadministration of managed application servers nodes and custom nodes as a singlecell. Oracle WebLogic Server and WebSphere Application Server NetworkDeployment provide basic clustering and caching support, which includes workbalancing, automated performance optimization, and centralized management andmonitoring.

MultipleServer Deployment

DirectoryServer

DatabaseServer

J2EE server IntegrationComposer

Administrativeworkstation

Middleware servers

Figure 1. Multiple server deployment

Chapter 2. Planning to deploy 5

Planning for securityYou must choose a security option and decide which system users work withapplications in SmartCloud Control Desk.

SmartCloud Control Desk can be configured to manage system users and theirmemberships in security groups. The following user information is required:

Maximo administration userThe product administrator user that is used for initial configuration and foradding users. By default, the value is maxadmin.

Maximo system registration userThe user that is used for the self-registration of users. By default, the valueis maxreg.

Maximo system integration userThe user that is used with enterprise adapters. By default, the value ismaxintadm.

Default users are created and stored in the Maximo® database. You can log in toSmartCloud Control Desk by using the default users or you can modify the usersto suit your security requirements.

When you install SmartCloud Control Desk, you must choose a method formanaging users and groups. This method applies to all products that you installtogether. If you are installing SmartCloud Control Desk with another product thatis already installed, the choice you made when installing the first product is usedfor SmartCloud Control Desk as well.

Databaseserver

Directoryserver

WebSphere Cell (ctgCell01)

WebsphereDeployment Manager

Cluster

ctgNode3ApplSrv3

ctgNode3ApplSrv2

ctgNode3ApplSrv1

S

Figure 2. Multiple server deployment


If you are using Oracle WebLogic Server, SmartCloud Control Desk internalauthentication is used as the default security option and a directory server is notrequired. You create and manage users and groups in the Users and SecurityGroups applications, separately from any corporate user data.

Choosing a security option

The security option you choose determines how your system performsauthentication and authorization. Authentication is the validation of a user signing into SmartCloud Control Desk. Authorization uses security groups to control whichusers can work with each application.

Choose one of the following security options:

Use application server and LDAP for authentication and user/groupmanagement

With this option, you create all your users and security groups in yourdirectory (LDAP) server. The information from the directory server isupdated in your Maximo database by using a cron task. With this option,you can create additional security groups and assign group membershipsin Maximo. All users must be added in the directory - adding users is notallowed in Maximo. Information entered in Maximo is never propagated toyour directory.

Use application server and LDAP for authentication onlyWith this option, you can create your users and groups in the directory(LDAP) server or in Maximo. The information from the directory server isupdated in your Maximo database by using a cron task. With this option,you can create additional users, security groups and assign groupmemberships in Maximo. Information entered in Maximo is neverpropagated to your directory.

Use Maximo internal authenticationWith this option, a directory server is not required. Use the default usersthat are provided or manage users and groups in the Users and SecurityGroups applications. Configure the users and groups to protect anycorporate user data you might have.

With this option, you cannot configure single sign-on to launch in contextto the TADDM interface without providing credentials. You have to defineusers in TADDM as well as in SmartCloud Control Desk and make surethat you coordinate their maintenance. When you launch in context to theTADDM interface, you always have to provide credentials that TADDMrecognizes. You cannot synchronize access collection definitions betweenSmartCloud Control Desk and TADDM using this option.

Planning for serviceabilityServiceability refers to problem analysis from a central point, using data collectedfrom a wide range of sources.

Serviceability has changed from the method used in the previous version of theproduct. Serviceability is supported in SmartCloud Control Desk 7.5 through theuse of the IBM Support Assistant Workbench. The workbench is a free utility thatyou can configure to work with many different products.


Log files for the middleware installation program can be found in the workspacedirectory you defined when you ran the installation program. These files can beanalyzed by the Log Analyzer tool.

Log files for the SmartCloud Control Desk installation program are on theadministrative system in the following directories, where install_home equalsC:\IBM\SMP.

Table 1. Log file directories

Log file directory Details

install_home\logs

install_home\solutions\logs

install_home\maximo\tools\logs

install_home\CTG_DE

The ACULogger.properties anddeexlogger.properties files contain *fileDirkeys whose values provide the location forthe log files. The properties files can befound in

install_home\CTG_DE..

Log files are generated here if a problemoccurs during the validation sequence of theinstallation program.

After installation, during normal usage of SmartCloud Control Desk, it can beuseful to examine the logs generated for the MXServer application server,WebSphere deployment manager, and the WebSphere node agent.

For more information about log information and the IBM Support AssistantWorkbench, refer to the troubleshooting section of the SmartCloud Control Deskinformation center.

Planning language supportSmartCloud Control Desk includes language support for languages that aresupported by UTF-8 and UCS-2.

When SmartCloud Control Desk is deployed with Microsoft SQL Server, UTF-8 isnot supported. Language support is limited to those languages supported by thecurrent Windows system code page. Supported language set choices are:v All Latin languages and Englishv One double-byte character set (DBCS) language and English

If you plan to add language support to SmartCloud Control Desk, you must usethe SmartCloud Control Desk product installation program to define the baselanguage before you perform any post-installation steps. You can add additionallanguages at a later date.

If you specify DB2 as the database type, you can disable non-English languagesupport to prevent the process automation engine from deploying languages otherthan English. Disabling non-English language support enhances databaseperformance, but prevents you from deploying additional languages at a laterstage.


Installation program log informationLog files generated by the SmartCloud Control Desk installation program canprovide details on completed installation tasks and any installation errors thatmight occur.

SmartCloud Control Desk installation program log locations

Logs can be found in the following locations:v install_home\logs

v install_home\solutions\logs

v install_home\maximo\tools\logs

v install_home\CTG_DE\logs

If you encounter an error during a validation task, logs can also be located withinthe home directory of the user that started the installation program. For example,C:\Documents and Settings\Administrator.

In addition, if you receive an error credited to the J2EE server, examine the logs inthe log directories for the deployment manager, node agent, and WebSphereApplication Server application server.

When engaging IBM product support services, be prepared to provide these logfiles in an archive file. The LogZipper utility provided in the install_home\scripts directory can be used for this task. If you use the LogZipper utility, allrelevant log files are archived in install_home/debug/YYYYMMDD_hhmmss.zip.


Chapter 3. Deployment scenario road maps

Deployment scenario road maps are summaries consisting of product deploymenttasks.

The product installation information provides the following deployment scenarios:v Scenario 1: Deploying with automatic middleware configurationv Scenario 2: Deploying automatically reusing existing middlewarev Scenario 3: Deploying manually reusing existing middleware

In scenarios 2 and 3, you reuse existing middleware installations as SmartCloudControl Desk components. For example, you might have an instance of DB2 orOracle in an existing database server farm which already has established accesspolicies, redundancy measures, and backup plans in place.

If you plan to reuse existing middleware, ensure that they are at the levelsupported by SmartCloud Control Desk. The middleware and product installationprograms do not provide a mechanism for updating servers using unsupportedversions of middleware, nor do these programs provide remote prerequisite checksto ensure that they are at the correct level. Use the prerequisite checking toolprovided with the product.

Scenario 1: Deploying with automatic middleware configuration

In this scenario, you deploy this product in a new environment. You use theSmartCloud Control Desk installation programs and tools to install andautomatically configure new installations of middleware and the product. OracleWebLogic Server must still be configured manually, but you can use themiddleware installation program to install DB2, for example, and use theSmartCloud Control Desk installation program to automatically configure it. Thisscenario is particularly useful for setting up a demonstration environment.

Note: The middleware installation program does not support the HP-UX andOracle Solaris platforms. However, installable images for WebSphere ApplicationServer Network Deployment, DB2 and IBM Tivoli Directory Server are providedwith this product. You can install this software individually using information inthis guide if you want to deploy SmartCloud Control Desk using this middlewareon those platforms.

Scenario 2: Deploying automatically reusing existing middleware

In this scenario, you deploy this product using middleware that exists in yourenterprise. You use the product installation programs and tools to automaticallyconfigure your middleware. Oracle WebLogic Server must be configured manually,but you can use the SmartCloud Control Desk installation program toautomatically configure an existing database, for example. This scenario isapplicable in situations where you already have existing middleware resourcesestablished in your enterprise.


Scenario 3: Deploying manually reusing existing middleware

In this scenario, you deploy this product using middleware that exists in yourenterprise, and you manually configure that middleware. This scenario isapplicable to those situations in which you have existing middleware resources,but you have particular company-sanctioned processes and regulations that restrictyour use of automated configuration tools when deploying a new application inyour enterprise. In this scenario, you do not use the middleware installationprogram at any time during the deployment. All manual middleware configurationinformation is contained in this scenario.


Chapter 4. Installation options

The installation programs provide options that give you flexibility in the way youdeploy the middleware and product.

Simple or custom optionEarly in the installation, you can choose which type of installation you want,simple, or custom.

SmartCloud Control Desk can be installed in one of two ways:

SimpleSelect simple if you want to deploy all SmartCloud Control Deskcomponents on a single system using all IBM middleware. Thisdeployment option is typically only used for demonstration,proof-of-concept, or training purposes.

CustomSelect custom if you want to deploy SmartCloud Control Desk componentsacross several systems. This deployment option is typically used in aproduction environment. If you are deploying SmartCloud Control Deskon Oracle WebLogic Server, you must choose this option.

In some instances, you want to avoid the sharing of resources. For example, mostdeployments do not use the same DB2 database instance between SmartCloudControl Desk and IBM Tivoli Directory Server. During the installation, the databaseinstance is restarted, which can disrupt the availability of IBM Tivoli DirectoryServer to your enterprise. If you are using the automated installation programs,separate instances are created for use by SmartCloud Control Desk and IBM TivoliDirectory Server.

Deferring database update and ear file deployment

Whether you are performing a simple or complex installation, you can let theinstaller update the database and deploy the ear files to your J2EE server(deployment of ear files must be done manually if you use a WebLogic server).However, there are two scenarios in which you should not let the installer performthese tasks automatically:v If you plan to install the optional content that is provided with the product

imagesv If you plan to install any of the integration packages that are available from the

product launchpad

You might also choose to defer these tasks when you install the product into yourproduction environment, in order to minimize your maintenance window, theperiod during which your production J2EE and database servers are unavailable tousers. You can do this even if you are not installing optional content or integrationpackages.

Each of these scenarios requires that the database be updated and the product earfile be deployed. The installer offers you the option to defer these steps. If you


plan to choose either of these scenarios, defer these two steps so that they will notbe performed multiple times. This means that the steps to follow are:1. Run the product installer, deferring the update of the database and the

deployment of the ear files.2. Install the optional content if desired, deferring the update of the database and

the deployment of the ear files.3. Install integration packages if desired, deferring the update of the database and

the deployment of the ear files (but see the section below about CMSpackages).

4. Re-run the product installer. The installer will update the database, runTDToolkit to process any additional languages, and build and deploy the earfiles. This is the only step for which your servers must be taken out of service.

Note: If you prefer to deploy the ear files manually, you can defer the deploymentof the ear files on the final run of the product installer.

Note: If your installation does not include any additional languages, it is notnecessary to run TDToolkit. If you prefer, instead of running the product installerto update the database and build and deploy the ear files, you can perform thosesteps manually. If you are installing any non-English language, TDToolkit must berun. It is much easier to allow the installer to run TDToolkit against eachinstallation package than to determine the correct list of packages for yourinstallation and run it manually against each package.

There is one exception to this approach. There are two integration packages usedwith the Context Menu System. These packages enable launching in context toother products to view details about configuration items or assets. You can installthese packages from the Integrations page of the product launchpad:v Deployed Assets CMS LIC Enablement Packagev CI Apps CMS LIC Enablement Package

If you plan to install either of these integration packages, you must allow theinstaller to update the database before you install the packages. These packagesupdate database tables that are created when you install the product. Theirinstallation will fail if the tables are not found in the database. If you are installingthese packages, change to these steps:1. Run the product installer, deferring the deployment of the ear files. You can

defer the update of the database if you want to minimize your maintenancewindow.

2. Install the optional content if desired, deferring the update of the database andthe deployment of the ear files.

3. If you deferred the update of the database in step 1, run updatedb to create orupdate the database.

4. Install integration packages if desired.5. Re-run the product installer. The installer will update the database if needed,

run TDToolkit to process any additional languages, and build and deploy theear files. (See the notes above.)


Chapter 5. Middleware

Before you can install the SmartCloud Control Desk, there are several SmartCloudControl Desk middleware products that can be deployed, or, if you intend to reuseexisting resources, configured either manually or using the SmartCloud ControlDesk installation programs

The middleware installation program provides an interface for installing anddeploying SmartCloud Control Desk middleware in a reliable and repeatablefashion. The middleware installation program records choices you make aboutyour SmartCloud Control Desk deployment and configuration parametersassociated with those choices, and then installs and deploys SmartCloud ControlDesk middleware based upon the information you entered.

The middleware includes the following software:v Database server

SmartCloud Control Desk uses the Maximo database to store details about theattributes and history of each configuration item and the details about therelationships between configuration items. A database is a required componentfor deploying SmartCloud Control Desk.You have the choice of installing a new instance of DB2 9.7 using themiddleware installation program, or using a preexisting instance of DB2 9.5, orDB2 9.7. You can also choose to use Microsoft SQL Server or Oracle for yourSmartCloud Control Desk deployment, but you must install and configure themmanually.

v Directory serverThe directory server is an optional component that can be used to secureSmartCloud Control Desk if you choose to use an LDAP server for security.You have the choice of installing a new instance of IBM Tivoli Directory Server6.3 for Windows and UNIX, or using a preexisting IBM Tivoli Directory Serveror Microsoft Active Directory server. If you choose to install a new version ofIBM Tivoli Directory Server, you must choose to install a new DB2 instance orreuse a an existing DB2 server. Alternatively, you can use the SmartCloudControl Desk database server for the DB2 data store if the SmartCloud ControlDesk database server uses DB2. If you choose to install the directory server butnot the database server, the middleware installation program attempts to locatean existing database instance to use. If it fails to locate an existing instance, itinstalls a database for use with the directory server. If you choose to useMicrosoft Active Directory Server for your directory server, you must install andconfigure it separately.

v J2EE serverThe J2EE server is the application server used to serve and manage theSmartCloud Control Desk application.The J2EE server can optionally be secured with a IBM Tivoli Directory Server orMicrosoft Active Directory directory server.The J2EE component includes the following subcomponents:– IBM HTTP Server

IBM HTTP Server is used as the primary HTTP server.You install a new instance of IBM HTTP Server.

– IBM HTTP Server plug-in


The IBM HTTP Server plug-in is used as the interface between IBM HTTPServer and the J2EE serverYou install a new instance of IBM HTTP Server plug-in.

The middleware installation program does not install Oracle WebLogic Server andthe SmartCloud Control Desk installation program does not have the option toautomatically configure it. Oracle WebLogic Server is a manual configuration effort.

The middleware installation program deploys software on a single server. Todeploy SmartCloud Control Desk middleware on multiple servers, the middlewareinstallation program must be started on each server in the topology configurationyou have chosen. Ensure that you have a strategy for deploying SmartCloudControl Desk middleware for each system you plan to use in your SmartCloudControl Desk deployment. If you deploy a SmartCloud Control Desk componentusing the middleware installation program on a system, for example, DB2, andthen later decide you would also like to add IBM Tivoli Directory Server to thatsame system, you must undeploy DB2 before redeploying it in the samemiddleware installation program deployment plan that included IBM TivoliDirectory Server. When installing SmartCloud Control Desk middleware on asystem, you must install all of the middleware intended for that system at onetime.

A process ID is generated each time the middleware installation program is usedto install or uninstall a set of middleware products. The process ID appears on thefile system in various places related to logs and generated files, such as file names,directory names, and log messages. The process ID is used to group logs and othergenerated files that are related to the same invocation of the middlewareinstallation program. It also separates logs and other generated files that arerelated to different invocations of the middleware installation program. The processID is a string of the format [operation_MMdd_HH.mm], where operation is astring indicating the operation being performed, such as "INSTALL" or"UNINSTALL", MM is a two-digit number (1-12) indicating the current month, ddis a two-digit number (1-31) indicating the current day in the month, HH is atwo-digit number (0-23) indicating the current hour, and mm is a two-digit number(0-59) indicating the current minute. Here are some examples of process ID values:v [INSTALL_0924_15.45]

An installation started on September 24 at 3:45pmv [UNINSTALL_1216_09.59]

An uninstallation started on December 16 at 9:59am

In addition to installing and configuring SmartCloud Control Desk middleware,the middleware installation program performs additional tasks. If you choose tonot run the middleware installation program because you intend to perform thenecessary configuration on existing middleware resources manually, you mustperform the following tasks.v If installing on WebSphere Application Server Network Deployment, you must

configure Virtual Member Manager after the J2EE server and the Directoryserver have been installed and configured. The directory server containsinformation about SmartCloud Control Desk users and groups and itcommunicates that information to the Maximo database with Virtual MemberManager to provide security and access to SmartCloud Control Deskapplications. See "Manually configuring Virtual Member Manager" in theinstallation guide for more information.


v Configure authentication services. See "Migrating the authentication service" inthe installation guide for more information. This step is not needed if you areinstalling the Entry edition.

Note: The middleware installation program does not support the HP-UX andOracle Solaris platforms, however, installable images for DB2, WebSphereApplication Server Network Deployment, and IBM Tivoli Directory Server areprovided with SmartCloud Control Desk. You can install this software individuallyusing information in this guide if you want to deploy SmartCloud Control Deskusing this middleware on those platforms.

Middleware installation program workspaceThe middleware installation program is designed to record the options you selectduring installation in a directory known as the workspace, and then configure thecomponents selected as a single deployed application.

After a plan has been deployed, the middleware installation program cannotdeploy additional features and products onto the system at a later time. Theexisting plan must first be undeployed with the middleware installation programbefore a different set of features and products can be deployed.

The composition and details of the deployment and any logs generated by themiddleware installation program process are located in the workspace.

By default, the middleware installation program workspace is defined as:

WindowsC:\ibm\tivoli\mwi\workspace

AIX® /ibm/tivoli/mwi/workspace

Linux /root/ibm/tivoli/mwi/workspace

The workspace can be defined on a shared resource that is made available to allthe systems that run the middleware installation program. Locating the workspaceon a shared resource avoids the need to copy files such as the topology filemanually from one system to another.

The workspace contains the following items:

Deployment PlanThe deployment plan is a collection of installation steps, configurationparameters for those steps, and target system information. It is generatedby the middleware installation program and is located in the workspacedirectory.

When deployment steps are changed, the existing deployment plan isdeleted and replaced with the new deployment plan.

The deployment plan configuration files contain information about thedeployment plan itself. Whenever a deployment plan is modified, whichincludes reconfiguring existing deployment choices, the deployment planconfiguration files are deleted. These files are regenerated when thedeployment plan is redeployed.

Topology FileThe topology file is a properties file that describes the configurationparameters of the SmartCloud Control Desk middleware deployment. This

Chapter 5. Middleware 17

file is created and then updated after every deployment or undeployment.If you have not defined a workspace that is centrally located and accessibleto all the systems receiving SmartCloud Control Desk middleware, this filemust be copied to the workspace of each system where SmartCloudControl Desk middleware is being deployed. The contents of this file canbe used by the SmartCloud Control Desk installation program to populateits panels with meaningful default values.

This file is saved in workspace/topology.xml.

Logs Log files that contain information about the deployment can be found inthe workspace directory. In addition, log files native to the SmartCloudControl Desk middleware itself are also contained in this directory.

Middleware configuration optionsIf the middleware has been either been installed by the middleware installationprogram or you have identified an existing middleware resource you intend to use,you have two options of configuring the servers for use with SmartCloud ControlDesk.

Auto-configureThe SmartCloud Control Desk installation program automaticallyconfigures middleware to work together with SmartCloud Control Desk.

ManualYou can manually configure middleware that either exists in yourenvironment or has been installed by the middleware installation program.This configuration must be completed before running the SmartCloudControl Desk installation program.

When deploying SmartCloud Control Desk on Oracle WebLogic Server,you must manually configure it.

Middleware object naming conventionsWhen installing and configuring middleware in the middleware installationprogram and the SmartCloud Control Desk installation program, observe theconventions for object names that are described in this topic.

The following table lists the restrictions for names of middleware objects.


Table 2. Middleware object naming conventions

Header Header

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

Group names and user IDs on Linux andUNIX operating systems can contain up toeight characters and must consist oflowercase characters only.

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

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

Names and IDs cannot begin with IBM,SQL, or SYS. They must also not begin withthe underscore (_) character.

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

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

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

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

IBM Tivoli Directory Server conventions fordatabases and database aliases.

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

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

Database and database alias names can haveup to 8 characters.

Be mindful that the special characters @, #,and $ are not common to all keyboards.Avoid using these characters when creatinga database name.


Table 2. Middleware object naming conventions (continued)

Header Header

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

Values cannot be longer than 8 characters.

Do not use any of the following values:USERS, ADMINS, GUESTS, PUBLIC,LOCAL, or idsldap.

Values cannot begin with IBM, SQL, or SYS.

Values cannot include accented characters.

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

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

Double-byte characters cannot be used inadministrator passwords values.

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

WebSphere Application Server NetworkDeployment

The administrator name cannot contain thefollowing characters: / \ * ,: ;=+?|< > & %'"] [> # $ ~ ( ) !

The administrator name cannot begin with aperiod.

The administrator name cannot containleading and trailing spaces.

The administrator password must consist of8 characters.

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

You cannot use the '%' character onWindows or !, $, #, % characters on UNIX.

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

Do not include the underscore character (_)when entering host names. Using thischaracter causes an error during middlewareinstallation.

Important: When entering LDAP values for product installation panel fields, inLDIF files, or directly into a directory instance, be aware of the product-specificsyntax rules for using special characters in an LDAP string. In most cases, specialcharacters must be preceded by an escape character to make them readable by thedirectory server. Failing to escape special characters contained in an LDAP stringused with SmartCloud Control Desk result in SmartCloud Control Desk errors.


Many directory server products consider a blank space as a special character that ispart of the LDAP string. If you enter an LDAP string that contains a blank in afield, you encounter SmartCloud Control Desk errors that are difficult totroubleshoot. You must precede any blank characters with an escape character. Seethe product documentation for your directory server for more information aboutspecial characters in LDAP strings.


Chapter 6. Performing multiple product installations on oneadministrative workstation

You can use a single computer to deploy multiple installations, such as a testenvironment, a development environment, and a training environment.

A single administrative workstation can support multiple product deployments.During the SmartCloud Control Desk installation, you specify the installationdirectory for that particular deployment on the Choose installation folder panel.When the installation is complete, you can install another instance of the producton the same administrative workstation by specifying a new installation path.Enter a meaningful directory name that represents the purpose of the deployment.

Each instance of the product requires a dedicated database instance and adedicated Java 2 Platform, Enterprise Edition (J2EE) server. You cannot share theseresources between deployments.

Tip: For workstations with multiple product deployments, complete anypost-installation actions for one single deployment at a time. The same practiceapplies to all future installation actions that are started from the process solutioninstaller, from the product installation program, or from applying fix packs.


Chapter 7. DVD layout

IBM SmartCloud Control Desk ships on a set of DVDs that contain the prerequisitemiddleware, middleware fix packs, and the product code. Alternatively, you candownload files containing these same images from Passport Advantage®.

The DVDs and images available for the product are listed in the downloaddocument. Click this link or enter it into your browser: http://www.ibm.com/support/search.wss?q=sccd75download.




Appendix A. Installation program tasks

The SmartCloud Control Desk installation program performs a series ofconfiguration and deployment tasks when you instruct it to automaticallyconfigure middleware.

The following list details the steps taken by the SmartCloud Control Deskinstallation program during a typical installation. This information is provided soit can be reviewed in order to ensure that the SmartCloud Control Desk installationprogram is compliant with your corporate application deployment policy.

For applicable tasks, links are provided to manual configuration instructions if youplan to opt out of the automatic middleware configuration provided by theSmartCloud Control Desk installation program. In this case, these tasks must becompleted before running the SmartCloud Control Desk installation program

Table 3. SmartCloud Control Desk installation program tasks

Task CategoryAutomatedInstallation Action Description Manual Instructions

Access Database usercreated for DB2

A system user named maximo bydefault is created on the DB2server that are used to access theMaximo database. This defaultvalue can be modified.

You can manually create thissystem user on the DB2 serverbefore running the SmartCloudControl Desk installation programusing the methods prescribed byyour organization.

WebSphereApplication Serverthin client

WebSphereApplication Serverthin clientconfiguration

The keystore file is copied from theWebSphere Domain Manager to theSmartCloud Control Deskadministrative system in order toestablish communications betweenthe two systems.

Instructions for manually copyingthe keystore file from theWebSphere Domain Manager canbe found in the productinstallation information.

Ensure that the SOAP port for theWebSphere Domain Manager isaccessible by the SmartCloudControl Desk administrativesystem. By default, this port is8879.

Database Create a databaseinstance

A new database instance is createdfor SmartCloud Control Desk onDB2 and Oracle if one does notexist.

You can either reuse an existingdatabase instance or create adatabase instance. Instructions formanually creating a databaseinstance for DB2 and Oracle can befound in the product installationinformation.

Create a database A new database is created forSmartCloud Control Desk for DB2and Microsoft SQL Server.

Instructions for manually creatinga database for DB2 and MicrosoftSQL Server can be found in theproduct installation information.


Table 3. SmartCloud Control Desk installation program tasks (continued)


Database usercreated for Oracle orMicrosoft SQLServer.

A database user named maximo bydefault is created for Oracle orMicrosoft SQL Server that is usedto access the Maximo database.This default value can be modified.

You can manually create thissystem user on Oracle or MicrosoftSQL Server before running theSmartCloud Control Deskinstallation program using themethods prescribed by yourorganization.

For Microsoft SQL Server, this usermust be the owner of thedatabase.

Information on grantingpermissions to the user for Oraclecan found in the productinstallation information.

Create table spaces Table spaces are created for thenew DB2 or Oracle database.

Instructions for manually creatingtable spaces for DB2 and Oraclecan be found in the productinstallation information.

Deploy the Maximodatabase schema

The Maximo database schema isdeployed into the newly createddatabase.

The name of the database schemais required to be the same value asthe owner of the table spacesdefined.

The maxinstcommand is run

maxinst deploys database tablesand required data.

WebSphereApplication ServerNetworkDeployment

Create a databaseinstance and user ID

If you opt to persist JMS messagesin a database, a new DB2 databaseinstance is created. A databaseinstance user ID is also created.

A new database instance forpersisting JMS messages can bemanually created using thestandard procedures of yourorganization.

If you are using Oracle orMicrosoft SQL Server, andassuming that you do not intendto reuse existing resources, youmust manually create a databaseinstance and user ID for messagepersistence.

Create a database If you opt to persist JMS messagesin a database, a new database iscreated on DB2.

A new database for persisting JMSmessages can be manually createdusing the standard procedures ofyour organization.

If you are using Oracle orMicrosoft SQL Server, andassuming that you do not intendto reuse existing resources, youmust manually create a databasefor message persistence.

Create a data source If you opt to persist JMS messagesin a database, a data source iscreated.

Instructions for manually creatingthe data source for persistingmessages can be found in theproduct installation information..




Create an applicationserver.

A new application server namedMXServer is created if it does notalready exist. This value is thedefault value.

Right after the application server iscreated, the JVM heap size is setfor it. If the application server hasbeen previously created, then thisstep consists only of setting theJVM heap size for it.

Instructions for manually creatingan application server can be foundin the product installationinformation.

Set JVM heap size onthe WebSphereDeploymentManager.

The JVM heap size is set to 1536for Initial Heap Size and MaximumHeap Size on the WebSphereDeployment Manager for 32-bitplatforms. For 64-bit platforms,this value is 4096.

You can manually set the heap sizeon the WebSphere DeploymentManager using the standardprocedures of your organization.

Create systemintegration buses andsystem integrationbus destinations

System integration buses andsystem integration bus destinationsare created for messagingpurposes.

Instructions for manually creatingsystem integration buses andsystem integration bus destinationscan be found in the productinstallation information.

Create JMS queues JMS queues are created formessaging purposes.

Instructions for manually creatingJMS queues can be found in theproduct installation information.

Modify web.xml files The web.xml files located on thedeployment manager are modifiedto include SmartCloud ControlDesk deployment information,including letting the deploymentmanager know how theSmartCloud Control Deskapplication handles itsauthentication needs.

IntegrationFramework Adapteris enabled.

Users created withinthe LDAP repository.

The following default users andgroups created in the LDAPrepository.

Users

v wasadmin

v maxadmin

v mxintadm

v maxreg

More information found in theproduct installation information.

Process managersdeployed.

The SmartCloud Control Deskcomponents are deployed using theProcess Solution installationprogram.

Appendix A. Installation program tasks 29



Applicationsdeployed

The maximo and maximohelpapplications are deployed to theMXServer application server.

updatedb commandrun

The updatedb command is run toupdate the Maximo database.

The VMMSYNCcrontask. is modified.

The VMMSYNC crontask is used toschedule the synchronizationbetween Virtual Member Managerand the LDAP repository youconfigure for authentication.

More information can be found inthe product installationinformation.

You have the option of manually completing these tasks. You would then selectthe option to not automatically configure middleware servers SmartCloud ControlDesk installation program.


Appendix B. Planning worksheets for middleware installation

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

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

Directory structure for middleware products

Do not install multiple middleware products into the same custom directory. Forexample, when installing DB2, WebSphere Application Server NetworkDeployment, and IBM Tivoli Directory Server on the same computer, you cannotinstall them all in a C:\ISM_middleware directory. You can, however, install them inC:\ISM_middleware\DB2, C:\ISM_middleware\WAS, and C:\ISM_middleware\ITDS. Youalso cannot install one middleware product in a custom directory and then installanother middleware product in a subdirectory of that custom directory. Forexample, if you install DB2 into C:\ISM_middleware, you cannot then install IBMTivoli Directory Server into C:\ISM_middleware\ITDS.

Users and groups

When you run the middleware installation program, you are prompted for userIDs to initiate the installation of DB2, WebSphere Application Server NetworkDeployment, and IBM Tivoli Directory Server. You can either supply an existingsystem 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 youspecify an existing user account to install DB2 or IBM Tivoli Directory Server andthat 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 wantto use the default values.

Table 4. Users and groups created during SmartCloud Control Desk deployment

User Group Description Your value

db2admin (Windowsonly) Windows

v Administrators

v DB2USERS

v DB2ADMNS

DB2 administrator. Windows Serviceuser ID.

This user only required fordeployments using DB2.


Table 4. Users and groups created during SmartCloud Control Desk deployment (continued)


idsccmdb

Note: The root usermust also be amember of theprimary group of theIBM Tivoli DirectoryServer instance user(by default,idsccmdb).

Linux and UNIX

v dasadm1

This value cannot bechanged when usingthe middlewareinstaller.

v idsldap


v dbsysadm


IBM Tivoli Directory Server instanceowner. Also the owner of the databaseused with the IBM Tivoli DirectoryServer instance.

This user only required fordeployments using IBM Tivoli DirectoryServer.

maximo Used for Maximo databaseconfiguration.

ctginst1Linux and UNIX

v dasadm1


v db2iadm1

The system user that is used as thedatabase instance owner on UNIXsystems.


db2fenc1Linux and UNIX

v db2fgrp1

System user that is used as the fenceduser ID for the DB2 default instance ofdb2inst1.


ctgfenc1Linux and UNIX

v ctgfgrp1


System user that is used as the fenceduser ID for the DB2 server instance ofctginst1.


dasusr1Linux and UNIX

v dasadm1


System user used as the administrationserver user.



Table 4. Users and groups created during SmartCloud Control Desk deployment (continued)


db2inst1Linux and UNIX

v dasadm1


v db2iadm1

System user used as the defaultdatabase instance owner.


idsldap


Linux and UNIX

v idsldap


v db2iadm1

v root

IBM Tivoli Directory Server user.


wasadmin Not a system user. User ID created for use with IBMWebSphere Application Server NetworkDeployment.

This user only required fordeployments using IBM WebSphereApplication Server NetworkDeployment.

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 theprimary group of the IBM Tivoli Directory Server instance user (by default,idsccmdb).

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

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

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

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

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

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

Appendix B. Planning worksheets for middleware installation 33

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

#id rootuid=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 5. 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 6. DB2 configuration


Installation directoryWindows

SystemDrive\ProgramFiles\IBM\SQLLIB

Linux, AIX, HP-UX, Solaris/opt/IBM/db2/V9.7

DAS userWindows

db2admin

Linux, AIX, HP-UX, Solarisdasusr1

Fenced user for the DB2 defaultinstance Linux, AIX, HP-UX, Solaris

db2fenc1

The option to create the DB2 defaultinstance is not enabled in themiddleware installation program, bydefault.


Table 6. DB2 configuration (continued)


Fenced user group name for the DB2default instance Linux, AIX, HP-UX, Solaris

db2fgrp1


Fenced user for the DB2 defaultinstance home directory Linux, AIX, HP-UX

/home/db2fenc1

Solaris /export/home/db2fenc1


Fenced user for the DB2 serverinstance Linux, AIX, HP-UX, Solaris

ctgfenc1

Fenced user group name for the DB2server instance Linux, AIX, HP-UX, Solaris

ctgfgrp1

Fenced user for the DB2 serverinstance home directory Linux, AIX, HP-UX

/home/ctgfenc1

Solaris /export/home/db2fenc1

Instance name ctginst1

Port 50005

Instance user name home directoryLinux, AIX, HP-UX

/home/ctginst1

Solaris /export/home/ctginst1

Database instance user IDWindows

db2admin

Linux, AIX, HP-UX, Solarisctginst1

DB2 administrators groupWindows

DB2ADMNS

Linux, AIX, HP-UX, Solarisdb2iadm1

DB2 users groupWindows

DB2USERS

Use same user name and passwordfor remaining DB2 Services

YES

Configure Tools Catalog NO

This value is relevant for reusescenarios only.


Table 6. DB2 configuration (continued)


Enable operating system security forDB2 objects

YES

This value is relevant for reusescenarios 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 7. Oracle configuration



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 IDWindows

Administrator

Linux, AIX, HP-UX, Solarisoracle

Instance LocationWindows

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 sizeOracle Medium (1000 MB)


Temporary table space size 1000 MB

Microsoft SQL Server configuration

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


Table 8. Microsoft SQL Server configuration


Installation directory ProgramFiles\Microsoft SQLServer\90

Named instance maximo

Microsoft SQL Server administrator sa

Microsoft SQL Server administratorpassword

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 Deploymentconfiguration

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

Table 9. WebSphere Application Server Network Deployment configuration


Installation locationWindows

C:\ProgramFiles\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 directoryLinux, 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


Table 9. WebSphere Application Server Network Deployment configuration (continued)


HTTP server installation locationWindows

C:\ProgramFiles\IBM\HTTPServer

Linux, HP-UX, Solaris/opt/IBM/HTTPServer

AIX /usr/IBM/HTTPServer

HTTP port 80

On Windows, this port might alreadybe in use. Ensure that you either freethis port, or use another port that isunassigned.

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 10. Oracle WebLogic Server configuration


Domain sourceWindows:

\wlserver_10.3\common\templates\domains

Linux, Solaris:/wlserver_10.3/common/templates/domains

Customize environment and servicessettings

No.

Domain name my_domainNote: Enter any name except forMAXIMOSERVER

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 Tivoli Directory Server configuration

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


Table 11. IBM Tivoli Directory Server configuration


Install locationWindows

C:\ProgramFiles\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 12. Microsoft Active Directory configuration


Directory server port 389

LDAP base entry

User suffix

Group suffix

Organization container suffix

Bind distinguished name


Appendix C. Planning worksheets for manual middlewareconfiguration

If you want to manually configure your middleware, you can use the followingtables as worksheets to plan the necessary tasks. It is recommended that onlyexpert users configure middleware manually.

In the deployment scenario that includes reusing existing middleware in yourenterprise, there are several configuration tasks that you must complete on thatmiddleware before you use the product installation program. Comprehensive stepsfor manually configuring existing middleware are provided in the installationguide.

You might have policies and procedures mandated by your organization that affecthow you perform common application deployment tasks. These policies andprocedures may be incompatible with the instructions in the installation guide. Ifso, you can use the information in this topic to manually configure existingmiddleware.


Table 13. System user creation task

MiddlewareComponent Server type Task Value Platform

Database v DB2

v Oracle

v Microsoft SQLServer

Create the maximouser and assign togroups.

This value is theuser used to accessthe maximodatabase.

User maximo

This value iscustomizable.

Groups

v Users

v Administrators

v Windows

v AIX

v Linux

v DB2 Create the systemuser used as thedatabase instanceowner on UNIXplatforms.

User ctginst1


Groups

v Users group

v Administratorsgroup

ctginst1 must bea member of theinstanceadministratorsgroup, forexample,db2grp1.

v AIX

v Linux

v Solaris

v HP-UX

DB2 Create system userused as the fenceduser ID for DB2default instance onUNIX platforms.

User db2fenc1


Groupsdb2fgrp1


v AIX

v Linux

v Solaris

v HP-UX

DB2 Create system userused as the fenceduser ID for DB2server on UNIXplatforms.

User ctgfenc1


Groupsctgfgrp1



Table 13. System user creation task (continued)

MiddlewareComponent Server type Task Value Platform

Directory Server IBM TivoliDirectory Server

Create the IBMTivoli DirectoryServer user andassign to groups.

User idsccmdb


Groups

v Windows

– Users

–Administrators

v UNIX

– root (primary)

– idsldap

– db2iadm1

v Windows

v AIX

v Linux

Appendix C. Planning worksheets for manual middleware configuration 43

Table 14. Database tasks

Server type Task Subtask

DB2 Create a database instancenamed ctginst1. This value iscustomizable.

Set the listening port to 50005. This value iscustomizable.

Set the instance service to start automatically.

Start the database instance.

Create a database namedmaxdb75. This value iscustomizable.

Enable database for XML (UTF-8)

Set the page size value to 32k

Configure the maxdb75 database. Set LOGFILSIZ to 4096.

Set APP_CTL_HEAP_SZ to 1024.

Set APPLHEAPSZ to 1024.

Set LOCKLIST to 30000.

Set LOGSECOND to 4.

Stop and restart the instance.

Add the maximo user to thedatabase.

Configure the user maximo with Grant Allpermissions.

Create a table space namedMAXDATA. This value iscustomizable.

Specify MAXBUFPOOL as a new buffer pool.

Change the Page size value to 32

Change the Size in 32 KB pages value to 4096.

For the Container, set the Type to File

Set the Size to 5000 Mb.

Set the File name to CTGDAT.

For UNIX, enter /home/ctginst1 as the locationof the file.

Enable the dropped table recovery option.

Create a temporary table spacenamed MAXTEMP. This value iscustomizable.

Specify MAXBUFPOOL as the buffer pool.

For the Container, set the Type to File

Set the Size to 3000 Mb.

Set the File name to CTGTMP.

For UNIX, enter /home/ctginst1 as the locationof the file.

Grant permissions for theMAXDATA table space.

Permit the user maximo to access the MAXDATAtable space.

Create a schema.

This name must be the same aswas used for the Database userID.

This schema is named maximowhen created by the productinstallation program.

Grant permissions for themaximo schema.

Permit the user maximo to access the maximoschema.


Table 14. Database tasks (continued)


Oracle

These instructions assume thatyou have not modified thedefault role sets that areassigned to the Oracle DBA useror user ID's created to connectto the database. If you haverestricted the default privilegesgranted to user ID's, you mustexplicitly grant them to themaximo user. So, for example, ifyou do not by default grant arole such as theselect_catalog_role role to userIDs connecting to the database,in order to deploy SmartCloudControl Desk successfully, youmust explicitly grant that role tothe maximo user by using theSQL*Plus command:

grant select_catalog_roleto maximo

Create a database. Enter ctginst1 for both the Global DatabaseName value and the SID value. The databasename value is customizable.

Set Shared Memory Management to Manual

Set Shared Pool to 157286400

For Oracle 9i Rel2 use 150

Set Buffer Cache to 36000000


Set Large Pool to 8388608


Set PGA Size to 37748736


Use the Unicode (AL32UTF8) character set.

Set nls_length_semantics to CHAR

Set cursor_sharing to SIMILAR.

Set open_cursors to 1000

Unlock the CTXSYS account.

Create a table space namedMAXDATA. This value iscustomizable.

Set the size to 1000 Mb.

Set autoextend to on.

Create a temporary table spacenamed MAXTEMP. This value iscustomizable.

Set the size to 1000 Mb.

Set autoextend to on.

Set maxsize to unlimited.

Grant permissions to the maximouser.

If you have elected to create aseparate table space forindexing, you must also grantthe maximo user access to thatindex table space. For example,you perform the followingadditional SQL*plus commandif you had created a separatetable space for indexing calledTSI_CMDB_OWN:

alter user maximo quotaunlimited on TSI_CMDB_OWN

Run the following command:

create user maximo identified bymaximo default tablespace maxdatatemporary tablespace maxtemp;

Grant the following permissions:

v connect

v create job (Oracle 10 only)

v create trigger

v create session

v create sequence

v create synonym

v create table

v create view

v create procedure

v alter session

v execute on ctxsys.ctx_ddl

Run the following command:

alter user maximo quotaunlimited on maxdata;


Table 14. Database tasks (continued)


Microsoft SQL ServerNote: If you add additionallogical names to the databaseand set their file group to avalue other than PRIMARY,refer to the information formanually configuring MicrosoftSQL Server.Note: Microsoft SQL Servercollation settings must be set tothe following options:

v Dictionary order

v Case-insensitive

v For use with 1252 Characterset

Configure the listener port.

SmartCloud Control Deskrequires Microsoft SQL Serverto listen on a static port.

Ensure the TCP Dynamic Ports field is blankfor each IP address listed in the TCP/IPProperties for the Protocols for the instancename you are using for SmartCloud ControlDesk.

For each IP address listed, enter 1433 for theTCP Port field.

Restart the database service.

Verify that you have enabledFull-text Search.

Create a database namedmaxdb75. This value iscustomizable.

Set the Initial size attribute to 500.

Set the Autogrowth field to By 1MB,unrestricted growth.

Create the Microsoft SQL Serverlogin user maximo.

Change the maxdb75 databaseowner to maximo

Table 15. Directory Server tasks


IBM Tivoli Directory Server Create an instance namedidsccmdb.

Enter idsccmdb as the value for the DB2 instancename field.

Configure multihome hosts to listen on allconfigured IP addresses.

Set Server port number to 389

Set Server secure port number to 636.

Set Admin daemon port number to 3538

Set Admin daemon secure port number to 3539

Set Database user name to idsccmdb

Set Database name to idsccmdb

Set the Character-set option to Create auniversal DB2 database (UTF-8/UCS-2)

Stop the server

Add required SmartCloudControl Desk users and groups.Existing users and groups canbe viewed by logging into theadministrative console andsearching for users and groupsunder the configured DN.

Add the following users to the repository.

v wasadmin

v maxadmin

v mxintadm

v maxreg

Restart the server

Microsoft Active Directory Add required SmartCloudControl Desk users.

Add the following users to the repository.

v wasadmin

v maxadmin

v mxintadm

v maxreg


Table 16. WebSphere Application Server Network Deployment Server tasks


WebSphere Application ServerNetwork Deployment

Create profiles, if required.

The middleware installationprogram creates a deploymentmanager profile (ctgDmgr01)and an application serverprofile (ctgAppSrv01). If you arereusing existing profiles for theSmartCloud Control Deskdeployment, you can ignore thisstep.

Configure Virtual MemberManager to use your directoryserver for SmartCloud ControlDesk authentication.

Perform infrastructureconfiguration:

1. Enable Enableadministrative security.

2. Enable Enable applicationsecurity.

3. Deselect Use Java 2 securityto restrict application accessto local resources.

Restart WebSphere ApplicationServer Network Deploymentand the managed nodes.


Table 16. WebSphere Application Server Network Deployment Server tasks (continued)


Manually copy the keystore filefrom the WebSphereApplication Server NetworkDeployment deploymentmanager host to a temporarydirectory on the SmartCloudControl Desk administrativesystem where you are installingSmartCloud ControlDesk:<WAS_HOME>/profiles/ctgDmgr01/etc/trust.p12

Create an application server, orexample, MXServer. Ensure thatyou set the application server tosynchronize changes withnodes.

Edit JVM Memory Settings forthe MXServer applicationserver.

Set Initial Heap Size to 512.

Set Maximum Heap Size to 1024.

Edit JVM Memory Settings forthe deployment manager.

Set Initial Heap Size to 512.

Set Maximum Heap Size to 1024.

Create a virtual host. Forexample, maximo_host.

Set HTTP port to 80.

Set administrative console port to 9061.

Set HTTPS transport port to 9443.

Set HTTP transport port to 9080.

Set administrative console secure port to 9044.

If you intend to persistmessages in a database, create adata source.

Configure JMS message queues. Create a JMS bus calledintjmsbus and deselect the Bussecurity check box so it doesnot inherit the Global Securitysetting of the cell.

Add MXServer to the serviceintegration bus. Specify thevalue of the High messagethreshold field to a minimumvalue of 500,000 messages.

Create the service integrationbus destination for thecontinuous inbound (CQINBD)queue. Choose MXServer as thebus member that stores andprocesses messages for theCQINBD bus destination queue.

Create the service integrationbus destination for thesequential inbound (SQINBD)queue. Choose MXServer as thebus member.




Create the JMS connection factory.

Scope Cell containing MXServer.

Name Enter intjmsconfact.

JNDI nameEnter jms/maximo/int/cf/intcf.

Bus nameSelect intjmsbus.

Create the continuous inbound (CQIN) JMSqueue.


Name Enter CQIN.

This value must contain only uppercaseletters.

JNDI nameEnter jms/maximo/int/queues/cqin


Queue nameSelect CQINBD.

Create the sequential inbound (SQIN) JMSqueue.


Name Enter SQIN.


JNDI nameEnter jms/maximo/int/queues/sqin


Queue nameSelect SQINBD.

Create the sequential outbound (SQOUT) JMSqueue.


Name Enter SQOUT.


JNDI nameEnter jms/maximo/int/queues/sqout


Queue nameSelect SQOUTBD.




Create the JMS activation specification for thecontinuous inbound queue (CQIN).


Name intjmsact

This value is case-sensitive. This valuemust be lowercase.

JNDI nameintjmsact

Destination typeQueue

Destination JNDI namejms/maximo/int/queues/cqin

Bus nameintjmsbus

Maximum concurrent endpoints10

Create the service integration bus destination forthe inbound error queue (CQINERRBD) queue.Set the Maximum failed deliveries value to 5.Set the exception destination of CQINBD toCQINERRBD.

Create the error (CQINERR) JMS queue.


Name Enter CQINERR.


JNDI nameEnter jms/maximo/int/queues/cqinerr


Queue nameSelect CQINERR.

Create the JMS activation specification for theinbound error queue (CQINERR).


Name Enter intjmsacterr.

This value must only contain lowercaseletters.

JNDI nameEnter intjmsacterr

Destination typeEnter Queue.

Destination JNDI namejms/maximo/int/queues/cqinerr


Table 17. Oracle WebLogic Server Server tasks


Oracle WebLogic Server Create an application server, forexample, MAXIMOSERVER.

Create three JMS servers withthe following configurationparameters:

Properties Namesqinserver,sqoutserver,cqinserver

Server TargetMAXIMOSERVER

Bytes Maximum20% or below of theallotted JVM heap size


Table 17. Oracle WebLogic Server Server tasks (continued)


Create a JMS system module intjmsmodule withMAXIMOSERVER as the target server.

Add a connection factory resource to the JMSmodule:

Name intjmsconfact

JNDI Namejms/maximo/int/cf/intcf

Target MAXIMOSERVER

Add three queue resources to the JMS Module:

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

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

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

TemplateNone

Enable the JMS connection factory forintegration framework.

Save and restart Oracle WebLogic Server.

Create the MAXIMOSERVERdomain.

Select a JDK with a version number 1.6.0 orgreater.

Configuring JMS for the emaillistener in WebLogic Server.

Create a persistent store called lsnrstore.

Create a JMS Server called lsnrserver with atarget of AdminServer.

Create a JMS System Module calledlsnrjmsmodule.

Add a connection factory to the JMS modulecalled lsnrconnfact with a JNDI Name ofjms/mro/lsnr/lsnrcf.

Add a queue to the JMS module calledlsnrqueue with a JNDI Name ofjms/mro/lsnr/qin.

Set the XA option for the connection factory forlsnrconnfact.

Enable an email listener to use JMS queues byediting the ejb-jar.xml andweblogic-ejb-jar.xml files.


Appendix D. Planning worksheet for product installation

These tables list the values for settings you supply when using the SmartCloudControl Desk installation program. Values you enter depend on the componentsyou select for the deployment.

Table 18. Settings for a custom installation



C:\IBM\SMP

Linux /opt/IBM/SMP

AIX /opt/IBM/SMP

DB2 host name

DB2 port 50005

Maximo database name maxdb75

Maximo database instance ctginst1

Schema name maximo

Maximo database user ID maximo

DB2 installation directoryWindows

C:\ProgramFiles\IBM\SQLLIB

Linux /opt/ibm/db2/V9.7

AIX /opt/IBM/db2/V9.7

DB2 instance administrator user IDWindows

db2admin

Linux ctginst1

AIX ctginst1

Windows DB2 service user ID db2admin

Oracle installation directoryWindows

C:\oracle\product\11.2.0\db_1

Linux /opt/app/oracle/product/11.2.0/db_1

AIX /opt/app/oracle/product/11.2.0/db_1

Oracle administrator user ID sys

Oracle software owner user ID oracle

SQL installation directory C:\Program Files\Microsoft SQLServer\90



Table 18. Settings for a custom installation (continued)


Data table space size medium (1000 Mb)

DB2 Medium (5000 Mb)

Oracle Medium (1000 Mb)

Microsoft SQL Server (Initial datafile size)

Medium (1000 Mb)


Temporary table space size 1000 Mb

Index table space name MAXDATA

Index table space sizeDB2 Medium (5000 Mb)

Oracle Medium (1000 Mb)

Schema name maximo (required to be the samevalue as the owner of the tablespaces)

WebSphere host name

WebSphere SOAP port 8879

WebSphere server home directoryWindows

C:\ProgramFiles\IBM\WebSphere\AppServer

Linux /opt/IBM/WebSphere/AppServer

AIX /usr/IBM/WebSphere/AppServer

WebSphere admin user ID wasadmin

WebSphere profile name ctgDmgr01

Web server port 80

Web server name webserver1

Node name ctgNode01

Application server MXServer

JMS data source name

JMS database name maxsibdb

JMS server name

Database server port 50000

Instance admin user ID db2inst1

Group base entry ou=groups,ou=SWG,o=IBM, c=US

User base entry ou=users,ou=SWG,o=IBM, c=US

SMTP server

Administrator e-mail


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationSoftware Interoperability Coordinator, Department 49XA3605 Highway 52 NRochester, MN 55901U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operating


platform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© IBM Corp. 2012. Portions of this code are derived from IBM Corp. SamplePrograms. © Copyright IBM Corp. 2012. All rights reserved.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksFor trademark attribution, visit the IBM Terms of Use Web site(http://www.ibm.com/legal/us/)

The following terms are trademarks of International Business MachinesCorporation in the United States, other countries, or both:

IBM, the IBM logo, AIX, Tivoli, the Tivoli logo, and WebSphere are trademarks orregistered trademarks of International Business Machines Corporation in theUnited States, other countries, or both.

Intel, the Intel logo, and Pentium are trademarks of Intel Corporation in the UnitedStates, other countries, or both.

Microsoft, Windows, the Windows logo, and Internet Explorer are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States and other countries.

Other company, product, and service names may be trademarks or service marksof others.

Notices 57

Index

Aadministrative workstation 4

installing multiple products 23authentication 6

Ccomponents

administrative workstation 4configuration

middleware 18

Ddatabase 23, 27

DB2 15security 6

DB2 3deployment

multiple server 3, 5planning 3scenarios 11single server 3, 4topology 3

directory server 15

EEAR files

administrative workstation 4

Hhttp server 15

Iinstallation

custom 13middleware 15program logs 7, 9program tasks 27simple 13

installation directory 23installation program

logs 7, 9tasks 27

JJ2EE server 6, 15, 23

Llanguages

planning support 8LDAP 15

LDAP (continued)security options 6

MMicrosoft SQL server 15middleware

configuration options 11, 18configuration values for expert

users 41deployment 11installation program 15multiple server 15planning worksheet 31

middleware installation workspace 17multi-server 5multiple server deployment 5

OOracle 15Oracle WebLogic Server

multiple server deployment 3

Pplanning

deployment 3languages 8security 6serviceability 7

planning to deploy 3planning worksheet

middleware 31product 53

productplanning worksheet 53

Rreuse

DB2 11Oracle WebLogic Server 11Tivoli Directory Server 11WebSphere Application Server 11

roadmaps 11

Ssecurity

planning 6security group 6serviceability 7single server deployment 4Support Assistant Workbench 7

TTivoli Directory Server 15

Uusers

administration 6

WWebSphere Application Server

multiple server deployment 3workspace 17


��

Printed in US A