Tamit installation | 64 Bit Computing | Oracle Database

Tivoli Asset Management for IT Release 7.

1

Installation Guide | IBM WebSphere Application Server
V ersion 7 Release 1.0

Tivoli Asset Management for IT Release 7.1

Installation Guide | IBM WebSphere Application Server
V ersion 7 Release 1.0

.This edition applies to version 7. modification 0 of IBM Tivoli Asset Management for IT and to all subsequent releases and modifications until otherwise indicated in new editions. All rights reserved. release 1. 2008. duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. © Copyright International Business Machines Corporation 2007. US Government Users Restricted Rights – Use.

. . 9 Planning for Tivoli Asset Management for IT middleware worksheet . . . . . . . . . . . . . . .Contents Chapter 1. . Increasing AIX file size and number of descriptors . . . . . 69 Tivoli Asset Management for IT simple install path values . . . . . . . 28 . . . . . . . . 28 29 30 30 30 Chapter 5. . . . . . . . . . . . . . . . . . . . . . Installing Tivoli Asset Management for IT middleware on zLinux (Linux/390) . . . . . . . . . . . . Tivoli Asset Management for IT installation program overview. . 3 . . Tivoli Asset Management for IT middleware deployment plan overview . . . . . Setting shared memory . . . . Starting the WebSphere Application Server . . Reusing IBM Tivoli Directory Server . . . Disabling the firewall . . . . . . . . . 20 . . . . . . . . . WebSphere management . . . . . . . . . . . . . Options for invoking the deployment plan Preparing UNIX systems for Tivoli Asset Management for IT middleware . 7 Tivoli Asset Management for IT administrative workstation . . . . . 7 Single machine deployment . . . 31 39 40 41 42 42 43 43 44 45 46 47 52 Chapter 2. Reusing DB2 . . . . . Enabling remote configuration . . . . . . . . 1 Tivoli Asset Management for IT components. 8 Reusing existing middleware components . . . . . . . . . . Tivoli Asset Management for IT middleware installation . . . . . . . . . . . . . . . . . . . . . . . . Installing and configuring Virtual Member Manager on WebSphere on zLinux . 22 . . . . . . . . . . 99 Manually configuring the J2EE server . Tivoli Asset Management for IT launchpad . . . . . . . . . . . . . Checking for required libraries on Linux Configuring the JRE in Linux . . . 19 . . . Starting the Tivoli Asset Management for IT launchpad . . . . 19 DVD layout . . . . . . . . 1 . . Installing and configuring IBM Tivoli Directory Server on zLinux . . . . WebSphere Portal Server overview . . 2007. . . Securing the WebSphere Administrative Console Configuring the WebSphere Application Server to run as a Windows service . . . . . © Copyright IBM Corp. . . . Tivoli Asset Management for IT deployed on WebSphere Portal Server . . Preparing to install Tivoli Asset Management for IT . . . . . 19 . . . . . . . 22 Chapter 4. . . 19 . 22 . . . . . . . . . . . . . . . . . . . 20 20 21 21 21 53 54 57 58 59 60 60 60 62 63 64 65 65 . . . . . . . 107 iii . . . . . . . . . Uninstalling Tivoli Asset Management for IT middleware . . . Reusing Microsoft Active Directory . . . . . . . . . . 72 Tivoli Asset Management for IT installation with manual middleware configuration . . . . . . . . . . . . . 7 Tivoli Asset Management for IT deployment topologies . . . . . Configuring the WebSphere node agent to run as a Windows service . . 27 . . . . . . . . . . . . . . . . . . . . . . . . . . Planning to deploy Tivoli Asset Management for IT . . . . . 86 Manually configuring the directory server . . . 2008 . . . . . . . . . . 7 Multiple machine deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tivoli Asset Management for IT component requirements . Enabling asynchronous I/O on AIX . . . . . . . . . . Before you begin . . . . . . . . . . Reusing middleware . . . . . Starting Tivoli Asset Management for IT middleware on UNIX . . Installing and configuring IBM HTTP Server on zLinux . More information . . . . . Deleting the TEMP and TMP user environment variables . . . . . . . . . . . . 70 Installing Tivoli Asset Management for IT . . . . . 10 Planning for Tivoli Asset Management for IT worksheet . . . . . . . . . . . . . . . . . . . . . . Setting the ulimit . . Reusing Oracle . . . . . . . . Introduction . . . . . . . . . . . . . . . . . Tivoli middleware installer logs . Installing and configuring DB2 on zLinux . . Increasing AIX paging space . . . . . . . . . 28 . . . . 86 Manually configuring the database server . . . . . . . . . . . . 25 Tivoli middleware installer workspace . Tivoli Asset Management for IT installation overview . . . . . 16 Chapter 3. . . . . . . . Installing and configuring the WebSphere Plug-in on zLinux . . . . . Installing and configuring IBM Agent Controller on zLinux . . . 5 Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer. . . . . Installing and configuring WebSphere Application Server Deployment Manager on zLinux . . . . . . . . Setting the swap size . . . . . . Verifying the required rpm-build package is installed . . . . . . . . . . . . . Creating profiles using 64-bit WebSphere Application Server Deployment Manager for zLinux . . Starting Tivoli Asset Management for IT middleware on Windows . . . 26 . . . . . . . . . . 9 Middleware configuration options . . . . . . . . . . . . . . . .

. . . . . . . . . . Installing Tivoli Asset Management for IT without middleware autoconfiguration . . . 153 153 154 154 154 155 155 155 156 156 156 158 158 158 Chapter 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 . . . . . . . . . . . . First steps to using Log and Trace Analyzer . Create a general ledger account component Create a general ledger account . . . . . . . . . 147 Index .Manually configuring Virtual Member Manager on WebSphere . . . . . . . . . . . . . . . . . . 143 Notices . . . . . . . . . . . . Signing in using a default user ID . . Integration Composer installation . . . 165 iv Installation Guide for IBM WebSphere Application Server: . . . . . . . . . Performing post installation tasks for the J2EE server . . . Tivoli Asset Management for IT language pack installation program overview . 135 136 137 138 Chapter 7. . . . . . . . . . . . . . . Manually configuring the VMMSYNC cron task for Microsoft Active Directory . Create a Work Type . . . . . . . . . . . . . Signing out and signing in . 151 Chapter 10. . . Create default insert site . . . . . . . . IBM Agent Controller overview . . Create an organization . . . Process solution package installation . . . . . . Manually creating a datasource for the persistence store . . . . . Synchronizing data . . . . . 161 Trademarks . . . 147 Installing Integration Composer with the Integration Composer DVD . . . . . . . . . . . . . . . . Manually configuring JMS queues . . . . . . . Create item and company sets . . . . . . . . . . . . . . . . . . . . Tivoli Asset Management for IT post installation tasks . . . . Installing process managers using the process solution installation wizard . . . . . . . 151 Installing the language pack . . . Locations of the resource set definition files Modifying the config. . . . . . . . . . . . . . . . . . . . 153 Initial data configuration . Installing IBM Agent Controller . 141 . . . . Error queues. . . . . . . . . Before using the process solution installation program . . . . . . . . . . . . . . . Starting IBM Agent Controller . . . . . 108 111 113 119 121 123 132 Installing Integration Composer with the Launchpad . . . . . . . . . 163 Chapter 8. . . . . . . . . . . 135 IBM Agent Controller supported platforms Planning for serviceability . . . . . Process solution installation logs . . . 142 . . . . . . .properties file . . . . . . . . . . . . . . . . Create currency codes . 141 Process solution packages . . . . . . . . . . . . 147 Chapter 9. . . . . .

2008 1 . For the system requirements for this configuration. see “Tivoli Asset Management for IT component requirements” on page 3.Chapter 1. service management. transportation. all based on the IT Infrastructure Library® (ITIL®) guidelines. Tivoli Asset Management for IT combines enhanced enterprise asset management functionality with new service management capabilities that together improve the effectiveness of asset management strategies. Tivoli Asset Management for IT includes advanced IT asset management. common platform. and a full-featured service desk. The following diagram depicts a typical Maximo® configuration. facility. and IT assets. The solution enhances asset management and ensures service performance of production. © Copyright IBM Corp. 2007. or the same physical server. dedicated server machines (for best performance). Tivoli Asset Management for IT components Tivoli Asset Management for IT requires multiple software servers that you can either install on separate. Introduction IBM® Tivoli® Asset Management for IT is a comprehensive suite of products built on a single. Each product can be implemented separately as a stand-alone solution or deployed with other products.

v Application server Tivoli Asset Management for IT is built using Java™ 2 Enterprise Edition (J2EE™) technology. v Directory server A directory server works in conjunction with Virtual Member Manager in WebSphere to provide security within Tivoli Asset Management for IT . The Application Server consists of Tivoli Asset Management for IT applications using JavaServer Pages (JSP). XML. which requires a commercial application server. dedicated HTTP server can be configured to work with the J2EE application server. – IBM Integrated Solutions Console The Integrated Solutions Console brings the interfaces for many different software products into a single user interface. allowing you to centralize data analysis efforts and evaluate information in context.JDBC SQ LC Integration Composer Server Database Server lie nt JDBC Directory Server TP HT Administration Workstation HTTP/HTTPS IBM Tivoli Asset Management for IT On IBM WebSphere Application Server End user with Microsoft Windows Internet Explorer 6 or 7 browser Figure 1. v HTTP server A separate. such as IBM WebSphere® Application Server. Tivoli Asset Management for IT Components v Database The Maximo database is the repository for all Configuration Items information. v Administrative system 2 Installation Guide for IBM WebSphere Application Server: . and Tivoli Asset Management for IT-application-specific business components.

1.8. which can only be done from the administrative system. Introduction 3 .2.3 or Oracle 10. Chapter 1. J2EE application server This is where you install WebSphere Application Server and where Tivoli Asset Management for IT runs. Changes to the Tivoli Asset Management for IT deployment typically require that Tivoli Asset Management for IT Enterprise Archive (EAR) files be rebuilt. After the initial deployment.3 (installed by the Tivoli middleware installer) or v8. If available. Each product version listed reflects the minimum requirement for use with Tivoli Asset Management for IT. Database Software v DB2® UDB 9. Operating System Refer to the database product specifications.2.5. the Tivoli Asset Management for IT administrative workstation and systems hosting Tivoli Asset Management for IT middleware can support IPv6 network configuration. Standard or Enterprise version. The administrative system can only be implemented as a Windows® system. Tivoli Asset Management for IT component requirements While Tivoli Asset Management for IT includes a language pack installer. Tivoli Asset Management for IT hardware and software requirements are listed in this section. Standard or Enterprise version v Microsoft SQL Server 2005 SP2.0.The administrative system is used to deploy Tivoli Asset Management for IT. Browser Tivoli Asset Management for IT supports Microsoft® Internet Explorer 6 and later.1.0.8 v Oracle 9. Tivoli Asset Management for IT does not support bi-directional languages or Turkish.2. Oracle 10. the administrative system is used to make updates or changes to the deployment.0.

1 FP13 Operating System v Windows Server 2003 SP2 (Standard SP2. if you are using an IBM DB2 Universal Database™ with Tivoli Asset Management for IT 7.1 IBM Integrated Solutions Console 7. 64-bit) v IBM AIX® 5. 64-bit) v Windows Vista (Business.0 Operating System Tivoli Asset Management for IT integration components can be run on any operating system supported by the integration software.Hardware v 2–4 dedicated processors Software v Windows Server 2003 (Standard SP2. Enterprise. you cannot use the following operating system on your Application Server: v Sun Solaris version 9 or 10 (SPARC processor-based systems v IBM WebSphere Network Deployment 6. or DataCenter) (32-bit.0. Enterprise.1 is installed as part of IBM WebSphere Network Deployment 6.3 v Red Hat Enterprise Linux® v4 (Enterprise or Advanced) (update 4+5 or later) (Intel®) (32 bit) v SuSE Linux (SLES) 9.1.1.11 v IBM WebSphere Portal Server 6.1. 64-bit) v Red Hat Enterprise Linux v4 (Enterprise or Advanced) (update 4+5 or later) (Intel) (32-bit) v IBM AIX 5L™ V5.5 GB or greater of disk space for Maximo and Java/Web Server components Integration options Software The following product can serve as integration options for a Tivoli Asset Management for IT 7.1.1 deployment. HTTP server Software The following product can serve as the HTTP server component of a Tivoli Asset Management for IT 7.0. Enterprise. However.11 (provided by IBM Corporation) v 2 GB RAM per processor v 1. v IBM Integrated Solutions Console 7.3 TL level 5300-06 (64-bit kernel) v SuSE Linux (SLES) 9.1 deployment. or DataCenter) (32-bit. v IBM HTTP Server v6. 64-bit) v Windows XP Professional SP2 (32-bit.0 Enterprise Server System z™ SP4 or later (manual install only) Note: Tivoli Asset Management for IT supports the following operating system.0 Enterprise Server System z SP4 or later (manual install only) 4 Installation Guide for IBM WebSphere Application Server: . Ultimate) (32-bit.

if used for Application Designer 1280 x 1024 resolution Software v Windows Vista (Business. 64-bit) v Windows XP Professional SP2 (32-bit. 64-bit) v Windows XP Professional SP2 (32-bit. you can find information on the Quick Start DVD (or the corresponding downloadable image) and the Web infocenter at http://publib.boulder.htm. Enterprise. JRE 1.ibm. Review these resources before you install Tivoli Asset Management for IT: Quick Start Guide A two-page document that gives you the information you need to get started. or DataCenter) (32-bit. 64-bit) v Windows Vista (Business. 64-bit) v Adobe® Acrobat® Reader® 6.0 Note: The Tivoli Asset Management for IT Workflow Designer requires a Java™ Runtime Environment.1 FP1 v Microsoft Windows Server 2003 SP2 Active Directory Microsoft Active Directory Application Mode is not supported. Ultimate) (32-bit. Client system Hardware v Intel-based Pentium processor v 1 GB RAM v SVGA 1024 x 768 resolution.itmaxam. Enterprise. or DataCenter) (32-bit.jsp?topic=/com. if used for Application Designer 1280 x 1024 resolution Software v Windows Server 2003 (Standard SP2. The Quick Start DVD and Web infocenter contain copies of the Quick Start Guide in several languages.ibm.0 Enterprise Server System z SP4 or later (manual install only) Administrative system Hardware v Intel-based Pentium® processor v 1 GB RAM v SVGA 1024 x 768 resolution.2 – JRE1. 64-bit) v Red Hat Enterprise Linux v4 (Enterprise or Advanced) (update 4+5 or later) (Intel) (32-bit) v IBM AIX 5L V5.doc/welcome. Introduction 5 .3 TL level 5300-06 (64-bit kernel) v SuSE Linux (SLES) 9.0 More information Use these resources to find more information about Tivoli Asset Management for IT.Directory server Software v IBM Tivoli Directory Server v6. Operating System v Windows Server 2003 (Standard SP2. Ultimate) (32-bit. Enterprise.4.com/infocenter/tivihelp/v3r1/ index.5 are supported. Chapter 1. Enterprise. Before you install Tivoli Asset Management for IT. 64-bit) v Adobe® Acrobat® Reader® 6.

ibm.Download document Describes how to download the product images from PassPort Advantage.1 Installation Guide (IBM WebSphere) This guide. the Quick Start Guide and Web infocenter have pointers to it. After you install Tivoli Asset Management for IT. 6 Installation Guide for IBM WebSphere Application Server: . Available in PDF on the Quick Start DVD or the Web infocenter. IBM Tivoli Asset Management for IT 7.com/software/tivoli/products/assetmanagement-it/ gives you access to the latest fixes and technical notes about Tivoli Asset Management for IT. Published on the Web. you can use the Product support site as a source of information. The IBM Software Support Web site for Tivoli Asset Management for IT at http://www-306.

Single machine deployment A topology consisting of deploying Tivoli Asset Management for IT on a single machine is frequently used as a proof-of-concept. product upgrades. Single-server The single-server topology consists of loading all Tivoli Asset Management for IT components onto one machine. This type of deployment would be typical for production use within an enterprise. or as a learning environment. the administrative workstation is used in all phases of the product lifecycle and is an important Tivoli Asset Management for IT support component. For managing enterprise assets and processes. This strategy is beneficial as it optimizes resource use and decreases the load on each system. and testing integration within the existing environment. Tivoli Asset Management for IT deployment topologies Use this information to determine the best deployment option for your environment and business needs. There are two primary strategies to deploy Tivoli Asset Management for IT within your enterprise. 2008 7 . Planning to deploy Tivoli Asset Management for IT Use this information to plan your Tivoli Asset Management for IT deployment. educational. Tivoli Asset Management for IT administrative workstation You install Tivoli Asset Management for IT from a Windows workstation designated as the administrative workstation. or demonstration configuration. and then gradually move towards a pilot multi-server environment before finally implementing a production deployment within the enterprise. functional proof-of-concept. and additional language packs. This workstation is where the Tivoli Asset Management for IT EAR files are built and later deployed to the application server. You use the administrative workstation to install program patches. For daily operations. the administrative workstation will not be required after the initial installation and configuration of Tivoli Asset Management for IT. While not typically used on a daily basis. A typical deployment lifecycle might begin with a single-server topology that moves through phases of demonstration. 2007. as a demonstration.Chapter 2. This topology is used typically for proof-of-concept purposes. © Copyright IBM Corp. you would typically implement a multi-server topology. There is not a Tivoli Asset Management for IT runtime requirement for the Administrative Workstation. Multi-server The multi-server topology consists of splitting Tivoli Asset Management for IT components across several different machines. new applications.

WebSphere Network Deployment provides basic clustering and caching support. automated performance optimization. This topology is the recommended deployment topology for a production environment. Only the Administrative system must be hosted on a Windows system. Figure 2. If you plan to reuse or migrate resources that exist in your network. and redundancy. Within WebSphere Application Server Network Deployment you can create deployment managers that provide centralized administration of managed Application Server nodes and custom nodes as a single cell. In a disparate environment. 8 Installation Guide for IBM WebSphere Application Server: . When contemplating your deployment strategy. the collection of machines in this deployment could be a mixture of Windows and UNIX® machines. Single server deployment Multiple machine deployment This section details deploying Tivoli Asset Management for IT across multiple machines. availability.The following figure details the Application Server MXServer running Tivoli Asset Management for IT on a single physical machine. including work balancing. reuse. Tivoli Asset Management for IT must be deployed on multiple machines. In order to provide load balancing. Implementing Tivoli Asset Management for IT by installing all new components using the Tivoli Asset Management for IT middleware and Tivoli Asset Management for IT installation programs simplifies the deployment. determine whether it includes systems already established in your network. and centralized management and monitoring. make adjustments to your rollout plan to allow time for things such as bringing the existing resources to version levels that are compatible with Tivoli Asset Management for IT.

Auto-configure The Tivoli Asset Management for IT installation program automatically configure middleware to work together with Tivoli Asset Management for IT. refer to http://publib.ibm. ensure that they are at the level supported by Tivoli Asset Management for IT. and backup plans in place. Planning to deploy Tivoli Asset Management for IT 9 .websphere. you have two options of configuring the servers for use with Tivoli Asset Management for IT.com/infocenter/wasinfo/ v6r1/index. WebSphere Cell (ctgCell01) Database Server MAXIMOCLUSTER ctgNode3 WebSphere Deployment Manager ctgNode2 ctgNode1 ApplSrv1 Srv2 Srv3 Directory Server (ctgCellManager01) Figure 3.doc/info/ae/ae/ trun_wlm_member.html. you might have an instance of DB2 or Oracle in an existing database server which already has established access policies.boulder. Tivoli Asset Management for IT Deployed in a Cluster While Tivoli Asset Management for IT requires a new WebSphere Application Server Network Deployment application server for deployment.jsp?topic=/com. or configuring each middleware component manually. If you plan to reuse existing middleware. once Tivoli Asset Management for IT has been deployed.Tivoli Asset Management for IT Deployed in a Cluster. The middleware and Tivoli Asset Management for IT installation programs do not provide a mechanism for patching backlevel servers. nor do these programs provide remote prerequisite checks to ensure they are at the right level. You are presented with the option of either allowing the Tivoli Asset Management for IT installation program to configure middleware automatically. This option is recommended if you are installing new instances of Chapter 2. Reusing existing middleware components You can reuse some existing middleware installations as Tivoli Asset Management for IT components. redundancy measures. For example. Middleware configuration options After middleware has been installed through the Tivoli middleware installer. you can add the application server used by Tivoli Asset Management for IT as a new member of an existing WebSphere Application Server Network Deployment cluster. For more information about adding a new member to an existing WebSphere Application Server Network Deployment cluster.nd.ibm.

member of This user is created by db2grp1 with secondary groups the Tivoli middleware installer if it does not of staff and exist. Planning for Tivoli Asset Management for IT middleware worksheet These tables list the settings for values that you must supply when installing the Tivoli Asset Management for IT middleware. This user is created by the Tivoli middleware installer if it does not exist. you want to review this worksheet if you plan to configure manually or reuse existing middleware. or has been installed by the Tivoli middleware installer. ctginst1 The system user used as v AIX the database instance v Administrators v Linux owner on UNIX ctginst1 must be a platforms. v Windows v Linux This user is created by v AIX the Tivoli Asset v Sun Solaris Management for IT installation program if it does not exist.middleware components. you can choose this deployment path . In a multi-machine deployment scenario. or if you have existing middleware instances that are not governed by policies that restrict programmatic configuration. dasadm1 v Users 10 Installation Guide for IBM WebSphere Application Server: . idsccmdb v Windows – Users ITDS user v Windows v AIX v Linux Platform Windows Your value This user is created by – Administrators the Tivoli middleware installer if it does not v AIX exist. Although many of the defaults can be accepted when navigating the panels of the Tivoli middleware installer. you might have multiple values to consider. Manual You can manually configure middleware that exists in your environment. – idslad v Linux – idslad – db2grp1 maximo v Users v Administrators Used for Maximo database configuration. If you have policies in place that dictate certain procedures and guidelines when configuring systems in your environment. Table 1. List of users and groups created during Tivoli Asset Management for IT installation User db2admin Group v DB2USERS v DB2ADMNS Description DB2 administrator. This configuration must be completed prior to running the Tivoli Asset Management for IT installation program. Windows Service User ID.

1 Your value Default <user home>\ibm\tivoli\ mwi\workspace Your value Windows db2admin Linux AIX dasusr1 dasusr1 db2fenc1 db2fenc1 Fenced user Linux AIX Chapter 2. DB2 configuration Setting Installation directory Default Windows <SystemDrive>\ Program Files\IBM\SQLLIB Linux AIX DAS user /opt/IBM/db2/ V9. v Linux This user is created by v Sun Solaris the Tivoli middleware installer if it does not exist. Tivoli middleware installer Setting Workspace directory Middleware images source directory Compressed images directory Uncompressed images directory Table 3. wasadmin Not a system user.1 /opt/IBM/db2/ V9. Planning to deploy Tivoli Asset Management for IT 11 . Table 2. This is a user ID created v Windows for use with WebSphere v AIX Application Server.Table 1. List of users and groups created during Tivoli Asset Management for IT installation (continued) User db2fenc1 Group db2fgrp1 Description Platform Your value UNIX system user used v AIX as the fenced user ID for v Linux DB2. This user is created by the Tivoli middleware installer if it does not exist.

Table 3. Enable O/S Security for DB2 YES objects This value is relevant for reuse scenarios only. DB2 instance port Data tablespace name Data tablespace size MAXDATA medium (1000Mb) DB2 Temporary tablespace name Temporary tablespace size Medium (5000Mb) MAXTEMP 1000Mb 12 Installation Guide for IBM WebSphere Application Server: . DB2 configuration (continued) Setting Fenced user group name Default Linux AIX Fenced user home directory Linux AIX: Instance name Port Instance user name home directory Database instance user ID ctginst1 50005 Linux: AIX: /home/ctginst1 /home/ctginst1 db2fgrp1 db2fgrp1 /home/db2fenc1 /home/db2fenc1 Your value Windows: db2admin Linux: AIX: ctginst1 ctginst1 DB2 administrators group Windows: DB2ADMNS Linux: AIX: db2grp1 db2grp1 DB2 users group Windows: DB2USERS YES Use same user name and p/w for remaining DB2 Services Configure Tools Catalog NO This value is relevant for reuse scenarios only.

0/ oradata /opt/app/oracle/ product/10.0/ oradata /opt/app/oracle/ product/10.2.Table 4.0/ oradata Data tablespace name Data tablespace size MAXDATA medium (1000Mb) Oracle Temporary tablespace name Temporary tablespace size Medium (1000Mb) MAXTEMP 1000Mb Chapter 2.2. Oracle configuration Setting Installation directory Default Windows <SystemDrive>\ oracle\product\ 10.2.2.0/ oradata AIX Sun Solaris /opt/app/oracle/ product/10.2.2.0\oradata Linux /opt/app/oracle/ product/10.0/ oradata Your value AIX Sun Solaris /opt/app/oracle/ product/10. this value might be C:\oracle\product\ 10.0/ oradata Administrator User ID Oracle Software Owner ID sys Windows Administrator Linux AIX oracle oracle Sun Solaris oracle Instance Location Windows On Windows. this value might be /opt/app/oracle/ product/10. Planning to deploy Tivoli Asset Management for IT 13 .2.0\oradata Linux On Linux.2.

Table 5. SQL Server configuration Setting Installation directory Named instance SQL Server administrator SQL Server administrator password Port Database name User ID User ID password Data file name Log file name maxdb71_dat maxdb71_log 1433 maxdb71 maximo Default <ProgramFiles>\Microsoft SQL Server\90 maximo sa Your value Table 6. WebSphere Application Server configuration Setting Install location Default Windows: C:\Program Files\IBM\ WebSphere\ AppServer Linux: /opt/IBM/ WebSphere/ AppServer /usr/IBM/ WebSphere/ AppServer Your value AIX: Sun Solaris /opt/IBM/ WebSphere/ AppServer WebSphere Administration User Name wasadmin Deployment Manager profile ctgDmgr01 name Application server profile name Profile directory ctgAppSrv01 Linux: /opt/IBM/ WebSphere/ AppServer/profiles /usr/IBM/ WebSphere/ AppServer/profiles AIX: Sun Solaris /opt/IBM/ WebSphere/ AppServer/profiles 14 Installation Guide for IBM WebSphere Application Server: .

1 15 . IBM Tivoli Directory Server configuration Setting Install location Default Windows: C:\Program Files\IBM\LDAP\ V6. Ensure that you either free up this port. WebSphere Application Server configuration (continued) Setting Cell name Deployment Manager node name Application server node name HTTP server install location Default ctgCell01 ctgCellManager01 ctgNode01 Your value Windows: C:\Program Files\IBM\ HTTPServer Linux: AIX: /opt/IBM/ HTTPServer /usr/IBM/ HTTPServer Sun Solaris /opt/IBM/ HTTPServer HTTP port 80 Note: On Windows.c=US 389 636 3538 3539 security Chapter 2.1 Linux: AIX: Administrator distinguished name Organizational unit Organization and country suffix Directory server port Directory server secure port Administration port Administration secure port Database name cn=root ou=SWG o=IBM.Table 6. this port might already be in use. 8008 ctgAppSvr01 HTTP admin server port HTTP plugin profile name Table 7.1 /opt/IBM/ldap/ V6. Planning to deploy Tivoli Asset Management for IT Your value /opt/IBM/ldap/ V6. or use another port that is unassigned.

DC=com CN=Users.DC=com DC=ism71.CN=Users. Settings for a custom installation Setting Installation directory API port DB2 host name DB2 port Maximo database name Maximo database instance Maximo database user ID 50005 maxdb71 ctginst1 maximo Default C:\IBM\SMP 9530 Your value 16 Installation Guide for IBM WebSphere Application Server: .DC=com CN=Administrator.Table 7. Microsoft Active Directory configuration Setting Directory server port LDAP base entry User suffix Group suffix Organization container suffix Bind distinguished name Default 389 DC=ism71.DC=com Your value Table 9. Table 10. IBM Tivoli Directory Server configuration (continued) Setting Instance name Instance port Instance user name Default idsccmdb 50006 idsccmdb Your value Table 8. DC=ism71.DC=ism71.DC=com DC=ism71. IBM Agent Controller configuration Setting IBM Agent Controller installation location Default Windows: C:\Program Files\IBM\ AgentController Linux: AIX: /opt/IBM/ AgentController /opt/IBM/ AgentController Your value Planning for Tivoli Asset Management for IT worksheet These tables list the settings whose values that you must supply when using the Tivoli Asset Management for IT installation program.

0\oradata Linux /opt/app/oracle/ product/10. Planning to deploy Tivoli Asset Management for IT 17 .0/ oradata AIX Sun Solaris /opt/app/oracle/ product/10.1 /opt/IBM/db2/ V9.2.2. Settings for a custom installation (continued) Setting DB2 installation directory Default Windows C:\Program Files\IBM\SQLLIB Linux AIX DB2 instance administrator user ID /opt/IBM/db2/ V9.1 Your value Windows db2admin Linux AIX ctginst1 ctginst1 Windows DB2 service user ID Oracle installation directory db2admin Windows C:\oracle\product\ 10.0/ oradata /opt/app/oracle/ product/10.0/ oradata Oracle administrator user ID Oracle software owner user ID SQL installation directory Data tablespace name Data tablespace size sys oracle <CProgramFiles>\Microsoft SQL Server\90 MAXDATA medium DB2 Oracle Medium (5000Mb) Medium (1000Mb) SQL Server (Initial data file size) Medium (1000Mb) Temporary tablespace name Temporary tablespace size WebSphere host name WebSphere SOAP port 8879 MAXTEMP 1000Mb Chapter 2.Table 10.2.2.

which must be a Windows system. 389 cn=root 50000 maxadmin maxsibdb SMTP server Workflow Admin E-mail Admin E-mail 18 Installation Guide for IBM WebSphere Application Server: .Table 10. Settings for a custom installation (continued) Setting WebSphere server home directory Default Windows C:\Program Files\IBM\ WebSphere\ AppServer Linux /opt/IBM/ WebSphere/ AppServer /usr/IBM/ WebSphere/ AppServer Your value AIX Sun Solaris /opt/IBM/ WebSphere/ AppServer WebSphere admin user ID WebSphere profile name Web server port Web server name Node name Cluster name Application server wasadmin ctgDmgr01 80 webserver1 ctgNode01 MAXIMOCLUSTER MXServer Note: This value cannot be changed. JMS Data Source name JMS database name JMS server name Database server port Database user ID Directory server host name Directory server port Directory server administrator DN Bind password Maximo installation folder C:\IBM\SMP Note: Maximo can only be installed on the Tivoli Asset Management for IT administrative system.

Tivoli Asset Management for IT installer. you can download Tivoli Asset Management for IT files containing these same images from Passport Advantage®.3 Contains prerequisite middleware software for AIX version 5. Preparing to install Tivoli Asset Management for IT These topics provide information about product media. The following DVDs contain files for the Tivoli Asset Management for IT product: Tivoli Asset Management for IT V7. middleware fix packs. See the documentation that comes with your Operation System for information on disabling the firewall. Middleware for Red Hat Enterprise Linux V4 Contains prerequisite middleware software for Red Hat Enterprise Linux version 4. preinstallation considerations. you must be logged in as a user with administrator privileges on Windows or as root on UNIX. and instructions on using the Tivoli Asset Management for IT launchpad.1 Quick Start Contains copies of the Quick Start guide in all languages and a copy of the information center. 2007. Alternatively. DVD layout IBM Tivoli Asset Management for IT ships on a set of DVDs that contain the prerequisite middleware. Tivoli Asset Management for IT V7. Middleware for AIX V5.1 Contains the launchpad. disable the firewall for the system to which you are installing Tivoli Asset Management for IT middleware.1. © Copyright IBM Corp. the Log and Trace Analyzer and Resource Generator tool. and the Tivoli Asset Management for IT language pack installation program for Windows. 2008 19 . IBM Agent Controller installer. An automated uninstall feature is not supplied with IBM Tivoli Asset Management for IT. If the installation fails. Note: Make a copy of the image of the system on which you are planning to install the product. Tivoli Asset Management for IT middleware installer. Before you begin This section describes the steps that you must take before you install middleware or Tivoli Asset Management for IT.3. version 7. Disabling the firewall Prior to the installation. To perform any of the steps. overview of the installation procedure. and the product code. Middleware for Windows 2003 Contains prerequisite middleware software for Windows 2003. restore the system to its previous working state using the copy of the disk image prior to attempting the installation again.Chapter 3.

If nothing is returned. the rpm-build package is installed. Repeat the process for the TMP variable. Prior to installing DB2. 20 Installation Guide for IBM WebSphere Application Server: . and then click Delete. 2. To remove the TEMP and TMP user variables on a Windows system.profile for root. Run rpm -qa | grep build. perform the following steps: 1. 5. complete the following steps: 1. From the System Properties dialog. From a command line. In the User variables section. first select the Advanced tab. To set the ulimit. refer to “Increasing AIX file size and number of descriptors” on page 28. Verifying the required rpm-build package is installed This procedure describes how to verify that the rpm-build package is installed on Linux. To verify that the rpm-build package is installed.3. and then click Environment Variables. select TEMP. For AIX systems. 3. Click OK. you must install the rpm-build package which is located on disk 3 (of 5) of the Red Hat Enterprise Advanced Server version 4 installation CDs using the rpm tool with the -i option.-18_nonptl”. not system variables. complete the following steps: 1. This package must be installed before you install the Tivoli Asset Management for IT middleware. which is used to define user system and process resource limits.Deleting the TEMP and TMP user environment variables The existence of the TEMP and TMP user variables can cause errors with the installation of DB2 on a Windows system.3. These variables are user environment variables that must be deleted. Exit the System Properties dialog by clicking OK. For Linux systems. type ulimit -f unlimited 2. the ulimit setting will apply to all processes. From a command line. 4. This procedure applies only if you are installing on Linux. you must set the ulimit for the system prior to installing Tivoli Asset Management for IT middleware. Setting the ulimit This section details how to set the ulimit in Linux. type ulimit -n 8192 If you set the ulimit in the . If the command returns a value like “rpm-build-4. Access the System Properties dialog by right-clicking the My Computer icon on your desktop and selecting Properties. remove these variables for the user ID that performs the installation. 2.

From a command line. ensure that one of these protocols is running and will accept remote logins using a user name and password configured on the target machine.456 bytes (256Mb). the swap size set for Linux systems should be equivalent to twice the amount of physical RAM in the machine. Preparing to install Tivoli Asset Management for IT 21 . Typically. RXA does not support accessing network drives on the local or remote system. refer to “Increasing AIX paging space” on page 29. Enabling remote configuration If you plan to take advantage of the Tivoli Asset Management for IT installation program feature that automates the configuration of Tivoli Asset Management for IT middleware. Additional swap space can be made available to the system by: v increasing the size of the existing swap partition v creating a new. To set the minimum shared memory value. additional swap partition v creating a swap file Refer to the product documentation for your Linux distribution for more information. set a minimum shared memory value for the system prior to installing the Tivoli Asset Management for IT middleware.Setting the swap size Tivoli Asset Management for IT can be a resource-intensive application. This section details how to set the size of the swap space used in Linux systems. complete the following steps: 1. If the remote system is a Windows machine. 2. rexec. For Linux systems. Before you start the Tivoli Asset Management for IT installation program. RXA requires that the target system enable at least one of the protocols supported by RXA.conf. Setting shared memory This section details how to set a minimum shared memory value in Linux. which include rsh.shmmax=268435456. you cannot use Cygwin ssh. If Cygwin is present on the Windows machine. Chapter 3. It is recommended that you configure and tune your system for maximum performance. SSH and Windows SMB.shmmax and determine if the value is less than 268. Default installations of AIX systems might not include a suitable protocol and will need to have RXA compatible protocols enabled. Update the value in /etc/sysctl. type sysctl -w kernel. you must enable a Remote Execution and Access (RXA) service for each system on which you intend to install Tivoli Asset Management for IT middleware. For AIX systems. If you want to increase the value. For Windows machines. type sysctl -w kernel. you must configure RXA to work over SMB.435. from a command line. the installation will fail. 3.

6. Installation and configuration of the IBM Agent Controller (installed by the Tivoli middleware installer). complete the following steps: 1. The installation programs for these Tivoli Asset Management for IT components can be initiated through the launchpad. “Tivoli Asset Management for IT language pack installation program overview. 5. Refer to “WebSphere Portal Server overview” on page 65. The launchpad application will assist you in choosing which product installation programs you should install and indicates the order in which they should be installed. “IBM Agent Controller overview.exe program if the Windows autorun feature is disabled. “Process solution package installation. Enabling Tivoli Asset Management for IT License for usage.Tivoli Asset Management for IT installation overview Installation and deployment of IBM Tivoli Asset Management for IT consists of the following tasks: 1. Installation of the language pack. Use the Tivoli Asset Management for IT launchpad to: v Access the Tivoli Asset Management for IT Information Center v Access information used to plan the Tivoli Asset Management for IT installation and deployment v Start the Tivoli middleware installer v Start the Tivoli Asset Management for IT installation program v Start the Tivoli Asset Management for IT language pack installation program v Enable the Tivoli Asset Management for IT license for usage Starting the Tivoli Asset Management for IT launchpad To start the IBM Tivoli Asset Management for IT launchpad.” on page 25.” on page 135. Refer to Chapter 7. Refer to Chapter 6. Installation and configuration of required Tivoli Asset Management for IT middleware software products. Installation and configuration of Tivoli Asset Management for IT. where you can also access product information. 2. Refer to Chapter 4.” on page 151. 4. Refer to Chapter 9. 2. 3. Log on to an account with system administration privileges on the computer where Tivoli Asset Management for IT components are to be installed. 22 Installation Guide for IBM WebSphere Application Server: . such as WebSphere Portal Server.” on page 141. Start the launchpad from the root directory of the product DVD: v Windows: Start the launchpad by using the launchpad. “Tivoli Asset Management for IT middleware installation. Tivoli Asset Management for IT launchpad The IBM Tivoli Asset Management for IT launchpad serves as a centralized interface for launching a collection of installation programs and product information. Configuration of optional Tivoli Asset Management for IT middleware software products.

The launchpad program uses the system default browser to run. it is likely that the launchpad program will not run properly due to the ksh shell interface. Modify /user_dir/launchpad/Firefox. a.v AIX: Start the launchpad from the root directory by using the launchpad. v Sun Solaris: Start the launchpad from the root directory by using the launchpad./media/cdrecorder/launchpad.sh program. b. export LOGNAME c. For more information on installation and configuration parameters you may encounter while installing Tivoli Asset Management for IT. /user_dir). download and extract the launchpad images as described in the download document.sh Running the launchpad from the root directory avoids complications that would arise if you ran it inside the mounted directory and you wanted to swap disks. at a certain point in the deployment process you would need to swap to another DVD. If the default browser on AIX is Firefox.sh program. but you would not be able to because launchpad was still running from the directory on DVD you have mounted. Copy all of the files from disk1 to a local directory (for example. If you changed directory to the mounted DVD and launched the launchpad from that directory. Run the launchpad from /user_dir v Linux: Start the launchpad from the root directory by using the launchpad.sh program. Preparing to install Tivoli Asset Management for IT 23 . For example. refer to “Planning for Tivoli Asset Management for IT middleware worksheet” on page 10 and “Planning for Tivoli Asset Management for IT worksheet” on page 16. If you have downloaded the product images rather than using physical media. follow these steps to modify it. If you want to use the launchpad with the Firefox browser.sh and remove the following lines: typeset +r LOGNAME 2>/dev/null LOGNAME=lp_user_$$. You would not be able to unmount the disk without terminating the launchpad. . Chapter 3.

24 Installation Guide for IBM WebSphere Application Server: .

there are several Tivoli Asset Management for IT middleware products that must be deployed. A directory server can be configured to secure the J2EE server deployment. The Tivoli middleware installer installs and deploys the following software: v Database server Tivoli Asset Management for IT uses the Maximo database to store details about the attributes and history of each configuration item and the details about the relationships between configuration items. v J2EE server The J2EE server is the application server used to serve and manage the Tivoli Asset Management for IT application. You must install a new instance of IBM WebSphere Network Deployment 6. You will have the choice of installing a new instance of DB2 UDB 9. You will have the choice of installing a new instance of IBM Tivoli Directory Server 6. and then installs and deploys Tivoli Asset Management for IT middleware based upon the information you entered.Chapter 4. or using a preexisting instance of DB2 UDB 8. If you choose to use MS SQL Server or Oracle for your Tivoli Asset Management for IT deployment. 2007.2 or DB2 UDB 9. 2008 25 . or using a preexisting IBM Tivoli Directory Server or MS Active Directory server. you will have to install and configure it separately. The WebLogic Server and MS Active Directory Server. will have to be installed and configured separately. if you choose to use it. © Copyright IBM Corp. Tivoli Asset Management for IT middleware installation Before you can install the IBM Tivoli Asset Management for IT.1.1. The Tivoli middleware installer records choices you make about your Tivoli Asset Management for IT deployment and configuration parameters associated with those choices. If you choose to use MS Active Directory Server for your directory server. v Directory server The directory server is used to secure the Tivoli Asset Management for IT J2EE application.1. you must choose to install a new DB2 UDB instance or reuse an existing DB2 UDB server. The Tivoli middleware installer provides an interface for installing and deploying Tivoli Asset Management for IT middleware in a reliable and repeatable fashion. you will have to install and configure them separately. The J2EE component includes the following subcomponents: – IBM HTTP Server IBM HTTP Server is used as the primary HTTP server. If you choose to install a new version of IBM Tivoli Directory Server. You can use a local or remote IBM Tivoli Directory Server or MS Active Directory Server. – IBM HTTP Server Plugin The IBM HTTP Server Plug-in is used as the interface between IBM HTTP Server and the J2EE server You will install a new instance of IBM HTTP Server Plug-in.1. You will install a new instance of IBM HTTP Server.

The process ID is a string of the format [operation_MMdd_HH. Tivoli middleware installer workspace The Tivoli middleware installer is designed to record the options you select during install in a directory referred to as the workspace. directory names. the Tivoli middleware installer cannot subsequently deploy additional features and products onto the machine at a later time. for example. A process ID is generated each time the Tivoli middleware installer is used to install or uninstall a set of middleware products. where operation is a string indicating the operation being performed. It also separates logs and other generated files that are related to different invocations of the Tivoli middleware installer. v Configure VMM after the J2EE server and the Directory server have been installed and configured. v Install IBM Agent Controller. you must install all of the middleware intended for that system at one time.59] An uninstallation started on December 16 at 9:59am In addition to installing and configuring Tivoli Asset Management for IT middleware. and then later decide you would also like to add IBM Tivoli Directory Server to that same system. and then configure the components selected as a single deployed application. “IBM Agent Controller overview. If you deploy a Tivoli Asset Management for IT component using the Tivoli middleware installer on a system. dd is a two-digit number (1-31) indicating the current day in the month. and mm is a two-digit number (0-59) indicating the current minute.The Tivoli middleware installer deploys software on a single machine. The existing plan must first be completely undeployed through the Tivoli middleware installer before a different set of features and products can be deployed. you will need to perform the following tasks. The process ID is used to group logs and other generated files that are related to the same invocation of the Tivoli middleware installer. such as ″INSTALL″ or ″UNINSTALL″. DB2. HH is a two-digit number (0-23) indicating the current hour. the Tivoli middleware installer must be invoked on each machine in the topology configuration you have chosen.45] An installation started on September 24 at 3:45pm v [UNINSTALL_1216_09. the Tivoli middleware installer performs additional tasks. MM is a two-digit number (1-12) indicating the current month. To deploy Tivoli Asset Management for IT middleware on multiple machines. you will have to undeploy DB2 before redeploying it in the same Tivoli middleware installer deployment plan that included IBM Tivoli Directory Server. Refer to Chapter 6. When installing Tivoli Asset Management for IT middleware on a system. If you choose to not run the Tivoli Asset Management for IT middleware installer because you intend to perform the necessary configuration on existing middleware resources manually. such as file names. Once a plan has been deployed. The process ID will appear on the filesystem in various places related to logs and generated files. 26 Installation Guide for IBM WebSphere Application Server: . and log messages. Ensure you have a strategy for deploying Tivoli Asset Management for IT middleware for each system you plan to use in your Tivoli Asset Management for IT deployment. Here are some examples of process ID values: v [INSTALL_0924_15.mm]. Refer to “Manually configuring Virtual Member Manager on WebSphere” on page 108 for more information.” on page 135 for more information.

In addition. If you have not defined a workspace that is centrally located and accessible to all the systems that will be receiving Tivoli Asset Management for IT middleware. log files native to the Tivoli Asset Management for IT middleware itself are also contained in this directory. the existing deployment plan is deleted and replaced with the new deployment plan. Topology File The topology file is a properties file that describes the configuration parameters of the Tivoli Asset Management for IT middleware deployment. and target machine information. the deployment plan configuration files will be deleted and regenerated when the deployment plan is redeployed. configuration parameters for those steps.xml. The deployment plan configuration files contain information about the deployment plan itself. This file is created and then updated after every deployment or undeployment.The composition and details of the deployment. the existing deployment plan is deleted and replaced with the new deployment plan. When deployment steps are changed. Chapter 4. Tivoli Asset Management for IT middleware installation 27 . This file is saved in <workspace>/topology. the Tivoli middleware installer workspace is defined as: Windows C:\ibm\tivoli\mwi\workspace UNIX /ibm/tivoli/mwi/workspace The workspace can be defined on a shared resource that is made available to all the systems that will run the Tivoli middleware installer. By default. this file will have to be copied to the workspace of each machine where Tivoli Asset Management for IT middleware is being deployed. as well as any logs generated by the Tivoli middleware installer process are located in the workspace. Logs Log files that contain information about the deployment can be found in the workspace directory. The contents of this file can be used by the Tivoli Asset Management for IT installation program to populate its panels with meaningful default values. Tivoli Asset Management for IT middleware deployment plan overview The deployment plan resides in the workspace directory and is generated from deployment choices selected in the Tivoli middleware installer. It is generated through the Tivoli middleware installer and it resides in the workspace directory. The workspace contains the following items: Deployment Plan The deployment plan is a collection of installation steps. which includes reconfiguring existing deployment choices. Each step is responsible for installing and uninstalling one portion of the middleware. When deployment choices are changed. Whenever a deployment plan is modified. The plan is a series of deployment steps and configuration parameters. Locating the workspace on a shared resource avoids the need to copy files such as the topology file manually from one machine to another.

This method of executing the deployment plan is recommended in most instances. complete the following steps: 1. you have several options for executing it.5 and the Java 1. and also set the maximum allowable file size to unlimited. This method of executing the deployment plan should be reserved for advanced users that have a need to modify deployment plan parameters that are not configurable through the Tivoli middleware installer. Create the plan using the Tivoli middleware installer and then have it execute the plan by installing and configuring the middleware selected. Have the Tivoli middleware installer execute the deployment plan after it has been generated This is the most common method of implementing the deployment plan. You must have Ant 1.5 JRE installed in order to execute a deployment plan outside of the Tivoli middleware installer. This option also includes configuring existing instances of middleware present in your environment that will be used with Tivoli Asset Management for IT. Edit the /etc/security/limits file by opening it in a text editor. Have the Tivoli middleware installer create the deployment plan and then componentize and distribute it The deployment plan consists of a collection of XML files that can be used to deploy middleware either through the Tivoli middleware installer or by Apache Ant. 28 Installation Guide for IBM WebSphere Application Server: . and then make changes to the parameters below using the values listed. Locate the section for the root user.6. you need to increase the default number of file descriptors allowed for the root user. Ant uses XML to describe build tasks and dependencies. Ant is an open source software tool used to automate the software build process. Options for invoking the deployment plan Once the deployment plan has been generated using the information you entered in the Tivoli middleware installer. To increase the allowable file size and number of allowable descriptors for the root user in AIX. Increasing AIX file size and number of descriptors For Tivoli Asset Management for IT to function correctly.Once the deployment plan has been generated using the information you entered in the Tivoli middleware installer. you have the option to have the Tivoli middleware installer execute it. 2. This method of executing the deployment plan is recommended in most instances. Preparing UNIX systems for Tivoli Asset Management for IT middleware Certain UNIX parameters must be set to specific values to create an environment on the system that can accommodate Tivoli Asset Management for IT and its associative middleware.

You must log out as root and log back in for these changes to take effect. This results show a total of 5632 Mb of paging space available to the system. or. there are a total of 44 Logical Partitions that are each 128 Mb in size. Save and exit the file. For example. use the following command: chps -s xx yyy Where xx is the number of logical partitions to add and yyy identifies the logical volume. you must increase the default paging space for the AIX system to a minimum of 4 GB. the total amount of physical memory in the system. Chapter 4. issue the following command: lsps -a This command will result in output similar to the following: Page Space hd6 Physical Volume hdisk0 Volume Group rootvg Size 5632MB %Used 2 To determine the size of a logical partition.root: fsize = -1 nofiles = 8192 3. Tivoli Asset Management for IT middleware installation 29 . To add more logical partitions. you will add more logical partitions to the system. issue the following command: lslv hd6 This command will result in output that will include partition information similar to the following: LPs: PP SIZE: 44 128 megabyte(s) In the example output. preferably. To determine the current amount of paging space available to the server. Verify the settings from a command window by issuing the following command: ulimit -a Output from the ulimit command should be similar to the following: time(seconds) file(blocks) data(kbytes) stack(kbytes) memory(kbytes) coredump(blocks) nofiles(descriptors) unlimited unlimited 2097152 32768 unlimited 2097151 8192 Increasing AIX paging space To successfully install and run Tivoli Asset Management for IT. A value of -1 for the fsize parameter indicates no limit. In order to add more paging space. 4.

If you receive this error.so. and then re-enable SELinux by using the setenforce 1command. not an installation requirement so this step can be run at any time before full operation of the product. Without asynchronous I/O. which results in adding 1280 Mb to the paging space.chps -s 10 hd6 adds 10 logical partitions to the logical volume hd6. Open a terminal and run the following command: smit chgaio 3. If you do not have this library installed. Click OK. Enabling asynchronous I/O on AIX Tivoli Directory Server requires asynchronous I/O be enabled on AIX systems. If this is the case. locate the RPM package for your system that contains this library and install the package. DB2 and Oracle database instances cannot be started successfully. This library is included as part of Red Hat Enterprise Linux v4 update 4. Reboot the system to enable the changes. To turn asynchronous I/O on follow these steps: 1.5 library installed. 5. Configuring the JRE in Linux In some cases. 6. Checking for required libraries on Linux The Tivoli Asset Management for IT middleware installation program requires the libstdc+. Exit SMIT.so. Log into the system as root. you will receive an error indicating that the Tivoli Asset Management for IT middleware installation program is unable to run in graphical mode. From the System Management Interface Tool (SMIT) dialog box. select Configure Defined Asynchronous I/O. and then click Enter. implement one of the following solutions: v Temporarily disable SELinux by using the setenforce 0 command. change STATE to be configured at system restart from defined to available. 30 Installation Guide for IBM WebSphere Application Server: . Tivoli middleware installer will fail with an error message stating that the Java Runtime Environment (JRE) could not be found on the system. 8. 4. It is an operational requirement. check the /usr/lib/ directory to determine if you have the libstdc+. Run the following command from the command line: smit aio 7. 2. the Tivoli middleware installer will fail on RHEL 5 systems. or other systems with SELinux enabled. From the System Management Interface Tool (SMIT) dialog box.5 system library to be present on a Linux system in order to launch the Tivoli Asset Management for IT middleware installation program user interface. You only need to perform this step if the system will host the IBM Tivoli Directory Server. If you cannot locate this library on your system. run the install. In one failure scenario.

Tivoli middleware installer will fail stating that it cannot find the VM. For Windows systems. On the desktop. click Change. It is recommended that you use the Tivoli middleware installer locally on the system that will host the middleware. fields and labels displayed within the Tivoli middleware installer are not correctly displayed on the panel when installing through remote sessions. you will encounter a subset of the panels included in these instructions that are relevant to the middleware you have chosen to install on a machine. To verify a fully qualified host name. In this case. Chapter 4. If it does not. affects the level of security for the entire system. right-click My Computer. however. v Edit the /etc/selinux/config file and set SELINUX to either permissive or disabled. first minimize and then maximize the install wizard to force it to redisplay the panel. 2. If you intend to deploy Tivoli Asset Management for IT middleware products across an array of machines. In another failure scenario. This solution. complete the following steps: 1. Tivoli Asset Management for IT middleware installation 31 . Refer to the Tivoli Asset Management for IT planning information to learn about using custom values during a custom installation. The Computer Name Changes panel is displayed. In addition. Avoid using localhost for host name values in the installation program. Specify the actual fully-qualified host name of the system on which you are installing. refer to “Reusing middleware” on page 42. The Tivoli middleware installer can also configure existing middleware products. If you intend to reuse existing Tivoli Asset Management for IT middleware products for your Tivoli Asset Management for IT deployment. consult the appropriate documentation for your operating system to ensure that the hostname command returns a fully qualified hostname. From the Computer Name tab. however. choosing which piece of middleware to install on that each particular machine. Select Properties. these instructions assume you are using the Tivoli middleware installer to install a complete set of Tivoli Asset Management for IT middleware for use with Tivoli Asset Management for IT on a single machine. In some cases. 3. For Linux systems. Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer This procedure explains how to use the Tivoli middleware installer to create a deployment plan that is responsible for installing and configuring prerequisite middleware products. This solution. The System Properties panel is displayed. ensure a Windows Primary DNS suffix is defined. If you do experience this phenomenon. you will have to run the Tivoli middleware installer on each machine. ensure that the command hostname -f returns a fully-qualified hostname. If this is the case. affects the level of security for the entire system.v Edit the /etc/selinux/config file and set SELINUX to either permissive or disabled. The instructions provided in this section are for a typical installation using default values. implement one of the following solutions: v Manually issue the chcon -R -t textrel_shlib_t <install_dir/jvm/jre> command.

Enter your fully qualified host name in the Computer name field. Failing to escape special characters contained in an LDAP string used with Tivoli Asset Management for IT will result in Tivoli Asset Management for IT errors. and you do not precede the blank character with an escape character. at the end of a field value. special characters must be preceded by an escape character in order to make it readable by the directory server. or values you enter directly into an directory instance using the directory server’s own tools.sh. and run the following command: launchpad. Therefore. navigate to the root directory of the product disc or the downloaded installation image. click Install the Product.4. if you mistakenly enter an LDAP string that contains a blank. entries in LDIF files.1”. Linux On the DVD titled “Tivoli Asset Management for IT 7. 3. To install the prerequisite middleware products for Tivoli Asset Management for IT. navigate to the root directory of the product disc or the downloaded installation image. 32 Installation Guide for IBM WebSphere Application Server: . From the Welcome panel. From the Computer Name Changes panel. and run the following command: launchpad. In the launchpad navigation pane. and run the following command: launchpad.1”. click Next. Start the launchpad: Windows On the DVD titled “Tivoli Asset Management for IT 7. 7. Refer to the product documentation for your directory server for more information on special characters in LDAP strings. for example. you will encounter Tivoli Asset Management for IT errors that will be difficult to troubleshoot.sh. 5. The DNS Suffix and NetBIOS Computer Name panel is displayed. Many directory server products consider a blank space as a special character that is part of the LDAP string. Important: When entering LDAP values for Tivoli Asset Management for IT installation panel fields. and run the following command: launchpad. follow these steps: 1. a. Click the Middleware link under 1. AIX On the DVD titled “Tivoli Asset Management for IT 7. Click Apply and close the System Properties panel. Install the middleware. c. Launch the Tivoli middleware installer from the launchpad. and then click OK.1”. 2. 6. Verify that the Primary DNS suffix field displays a domain name. and then click More. be aware of the product-specific syntax rules for using special characters in an LDAP string. 4. click OK. navigate to the root directory of the product disc or the downloaded installation image. Select a language for the installation and click OK. b. Login as a user with administrative authority. Sun Solaris On the DVD titled “Tivoli Asset Management for IT 7.1”.exe. navigate to the root directory of the product disc or the downloaded installation image. In most cases.sh.

If no previous workspace location exists in the middleware user preferences node. J2EE Server The J2EE server is the application server used to serve and manage the application. Directory Server The directory server is used to secure the J2EE Server. Tivoli Asset Management for IT middleware installation 33 . It must remain selected in order for you to enable the Directory Server option. Read the license information and select I accept both the IBM and the non-IBM terms if you agree with the terms. specify the directory you will use as the Tivoli middleware installer workspace. enter the Username and Password you will use to deploy the plan with. you will be prompted to supply the directory server you will use to secure it. This topology file can be manually copied by the user to the workspace of the next machine in the topology. Choices include: Database Server The Database Server is used to store details about the attributes and history of each configuration item and the details about the relationships among configuration items. After deployment. If you elect to opt out of maintaining J2EE server through the use of the directory server. 10. and then click Next. select the features to deploy on this machine. This feature should be selected to either install a new directory server locally or reuse a local directory server. This option allows you to use a directory server to secure the J2EE server. From the Install IBM Autonomic Deployment Engine panel. The default location for the workspace will be the last workspace location used by this user. click Next to install the IBM Autonomic Deployment Engine. click Next to configure the parameters displayed. If you choose to only install the J2EE server portion of the Tivoli Asset Management for IT middleware. 8. Chapter 4. Click Next. From the Choose Workspace panel. or an existing instance of Microsoft Active Directory. The Tivoli middleware installer license agreement window is displayed. the Tivoli middleware installer also generates a topology file in this directory. it will be created. 9. 6. then the default location for the workspace will be C:\ibm\tivoli\mwi\ workspace for Windows and /ibm/tivoli/mwi/workspace for UNIX. From the Deployment Plan Summary window. and then click Next. The deployment plan is generated and you will be provided details about the plan. From the Credentials panel. From the Deployment Choices panel. and then click Next. If the selected directory does not exist. 7. you will be unable to install the directory server through the Tivoli Asset Management for IT Middleware installation program. as specified in the middleware user preferences node. Your choices will be to secure with an existing instance of IBM Tivoli Directory Server.5. Secure the J2EE Server using the Directory Server. By default this option is selected. so that information about the deployment of middleware will be available to the Tivoli middleware installer when it is executed on the next machine.

Default for all platforms is 50005. 34 Installation Guide for IBM WebSphere Application Server: .You can choose to enable the option of using the same password as the default user password value in all panels of the Tivoli middleware installer by enabling the Use this password as the value for all subsequent passwords option at the top of this panel. Default for all platforms is ctginst1 Port Enter the port that the Tivoli Asset Management for IT database instance will use. Default fenced user is db2fenc1 12.1 DB2 Administration Server username Enter the DB2 administrative account name. Fenced user (Linux and AIX only) Enter a system user ID that can be used as a DB2 fenced user account. Enter the following configuration parameters for the Tivoli Asset Management for IT database instance. Windows: Default is db2admin Linux: Default is dasusr1 AIX: Default is dasusr1 DB2 Administration Server password Enter the password for the DB2 administrative account.1 AIX: Default is /opt/IBM/db2/V9. and then click Next. Enter information about the DB2 user groups: DB2 administrators group Enter the name of the DB2 administrators group. Windows: Default is db2admin Linux: Default is ctginst1 AIX: Default is ctginst1 Instance username password Enter the password for the Tivoli Asset Management for IT database instance user name. 13. Instance username Enter the user name for the Tivoli Asset Management for IT database instance. Instance name Enter the name of the Tivoli Asset Management for IT database instance. Install location Enter the location to install DB2. 11. Enter the following configuration parameters for DB2 Enterprise Edition Server and then click Next. Windows: Default is C:\Program Files\IBM\SQLLIB Linux: Default is /opt/IBM/db2/V9.

c=US. Enter the following configuration parameters for IBM Tivoli Directory Server.Windows: Default is DB2ADMNS Linux: Default is db2grp1 AIX: Default is db2grp1 DB2 users group (Windows only) Enter the name of the DB2 users group. Chapter 4. 15. Default for all platforms is 389. Directory server secure port Enter the secure port number of the IBM Tivoli Directory Server. Directory server port Enter the port number of the IBM Tivoli Directory Server. Default for all platforms is cn=root. Default for all platforms is ou=SWG. and then click Next. Administration secure port Enter the secure administration port number of the IBM Tivoli Directory Server. Windows: Default is C:\Program Files\IBM\LDAP\V6.1 Administrator distinguished name Enter the distinguished name of the IBM Tivoli Directory Server administrator. Enter the following configuration parameters for IBM Tivoli Directory Server. Default for all platforms is o=IBM. Administrator password Enter the password for the IBM Tivoli Directory Server administrator.1 Linux: Default is /opt/IBM/ldap/V6. Tivoli Asset Management for IT middleware installation 35 . Default for all platforms is 636.1 AIX: Default is /opt/IBM/ldap/V6. and then click Next. Administration port Enter the administration port number of the IBM Tivoli Directory Server. Default is DB2USERS 14. Default for all platforms is 3538. Install location Enter the location to install IBM Tivoli Directory Server. Organizational unit Enter the name of the IBM Tivoli Directory Server organizational unit to use with Tivoli Asset Management for IT. Organization and country suffix Enter the name of the IBM Tivoli Directory Server organization and country suffix to use with Tivoli Asset Management for IT.

o=IBM. LDAP Host Name Enter the host name of the system hosting the LDAP instance to use for WebSphere security. Enter the following configuration parameters for WebSphere Application Server security.ou=SWG. and then click Next. Default is ou=users.c=US Organization container suffix Enter the organizational container suffix of the LDAP instance to use for WebSphere security.o=IBM.o=IBM. Default for all platforms is security. Database name Enter the name of the DB2 database you are using to hold IBM Tivoli Directory Server data.c=US User suffix Enter the user suffix of the LDAP instance to use for WebSphere security.c=US Group suffix Enter the group suffix of the LDAP instance to use for WebSphere security. Default for all platforms is 50006.Default for all platforms is 3539. Default is 389. Instance name Enter the name of the IBM Tivoli Directory Server database instance. Default is cn=root 36 Installation Guide for IBM WebSphere Application Server: .c=US 18. Bind distinguished name Enter the bind distinguished name for binding to the LDAP instance. LDAP base entry Enter the LDAP base entity of the LDAP instance to use for WebSphere security. Instance user password Enter the password for the instance user ID. Directory server port Enter the port number used by the LDAP server to use for WebSphere security. Default for all platforms is idsccmdb. and then click Next. 16. and then click Next.ou=SWG.o=IBM. Port Enter the port number used by the IBM Tivoli Directory Server database instance. Default is ou=groups. Enter the following configuration parameters for WebSphere Application Server security. Enter the following configuration parameters for IBM Tivoli Directory Server database instance. Default is ou=SWG. 17. Default is ou=SWG.

WebSphere Administrator password Enter the password for the WebSphere administrative account. Default for all platforms is ctgNode01.Bind password Enter the password for the bind distinguished name. 20. Tivoli Asset Management for IT middleware installation 37 . 19. Enter the following configuration parameters for WebSphere Application Server. Application server node name Enter the name of the WebSphere application server node. Default for all platforms is ctgCellManager01. Enter the following configuration parameters for WebSphere Application Server Version. Enter the following configuration parameters for IBM HTTP Server. Enter the following configuration parameters for WebSphere Application Server. Chapter 4. Default for all platforms is ctgDmgr01. Application server profile name Enter the WebSphere profile name of the application server. and then click Next. 21. Deployment Manager profile name Enter the WebSphere profile name of the deployment manager server. Windows: Default is C:\Program Files\IBM\WebSphere\AppServer Linux: Default is /opt/IBM/WebSphere/AppServer AIX: Default is /usr/IBM/WebSphere/AppServer WebSphere Administrator username Enter the WebSphere administrative account name. Default for all platforms is wasadmin. Default for all platforms is ctgCell01. Deployment Manager node name Enter the name of the WebSphere deployment manager node. and then click Next. and then click Next. Cell name Enter the WebSphere Cell name. Windows: Default is C:\Program Files\IBM\WebSphere\UpdateInstaller Linux: Default is /opt/IBM/WebSphere/UpdateInstaller AIX: Default is /usr/IBM/WebSphere/UpdateInstaller 22. Install location Enter the location to install WebSphere. Default for all platforms is ctgAppSrv01. Update Installer install location Enter the location where the WebSphere update installer will be installed. and then click Next.

This value cannot be changed. Admin Server port Enter the port to use to administer IBM HTTP Server. and then click Next. Specify a directory to use for Tivoli middleware installer temporary files and extracted middleware installation images. Default for all platforms is 8008. Enter the following configuration parameters for IBM Agent Controller. Profile name Enter the profile name. 28. 24. Default for all platforms is 80. 27. Enter the following configuration parameters for WebSphere Application Server plugin for the IBM HTTP Server. and then click Next. If you selected the option to copy install images from the source media. and then click Next. and then click Next. 23. If you selected the option to specify a directory that already contained the middleware images. 26. and then click Next. specify the source and destination directories. Copy the middleware install images from the source media to a specified directory Select this option to copy the Tivoli Asset Management for IT middleware images from the product media to a directory that you will specify. specify that directory. Default for all platforms is ctgAppSvr01. Windows: Default is C:\Program Files\IBM\HTTPServer Linux: Default is /opt/IBM/HTTPServer AIX: Default is /usr/IBM/HTTPServer HTTP port Enter the port used by the IBM HTTP Server. and then click Next. select Deploy the plan.Install location Enter the location to install IBM HTTP Server. 38 Installation Guide for IBM WebSphere Application Server: . Install location Enter the location to install IBM Agent Controller. From the Deployment Plan Operation panel. Windows: Default is C:\Program Files\IBM\AgentController Linux: Default is /opt/IBM/AgentController AIX: Default is /opt/IBM/AgentController 25. Specify a directory containing all the required middleware install images Select this option if you intend to specify a filesystem directory that already contains all of the Tivoli Asset Management for IT middleware installation images. Specify the location of the Tivoli Asset Management for IT middleware images. and then click Next.

User interface logs The logs generated by the Tivoli middleware installer user interface are located in the workspace directory. The primary log file for the deployment plan is DeploymentPlan.log file is the high-level log file that was generated by the most recent invocation of the Tivoli middleware installer. 30. Tivoli middleware installer logs Tivoli middleware installer log files are located in the workspace directory that was defined in the Tivoli middleware installer. Logs for steps run by the user interface In addition to collecting input from the user. Examples of system checks run by the user interface runs include: v dependency checking to ensure the operating system meets the deployment requirements v inventorying the software on the system to locate existing instances of middleware products deployed by the Tivoli middleware installer v checking the available disk space to ensure there is enough for the deployment Each of these checks is produced in the form of a step so that it can also be run as part of the deployment plan. Log files named mwi. The different types of log files are described below. The log files generated by a step are located in the same subdirectory and follow the same pattern as a step that is run as part of the deployment plan. and then click Deploy to initiate the installation and configuration of the middleware you selected.log. When the user interface runs a step.log1 is produced after the second invocation of Tivoli middleware installer. a high-level log file that lists the steps invoked as part of the deployment plan. click Finish to exit. Each time the deployment plan is used to install or uninstall middleware products. Tivoli Asset Management for IT middleware installation 39 . From the Deployment Plan and Parameter Configuration summary panel. Chapter 4. 29. An entry in this log file may direct you to a lower-level log file. The mwi. a process ID is assigned and log files are generated. for example. The log files for the deployment plan are located in the subdirectory logs/processID. review the contents of the summary. the user interface of the Tivoli middleware installer also performs several system checks. and so on. examine this log file first.log file from earlier invocations of the Tivoli middleware installer So. Logs for the deployment plan The deployment plan is located in the directory <Workspace Directory>/hostname/deploymentPlan.log0 is produced after the first invocation of Tivoli middleware installer. where hostname is the hostname of the current system. it copies the step into a subdirectory of the workspace directory. are copies of the mwi. mwi. If an error occurs. mwi. Once the deployment completes successfully. where X is a number.You can also elect to make changes to the deployment plan or parameters you have previously configured from this panel.logX.

and check. where operation is the ANT target in the step ANT script that invokes this substep.log. you can use the db2start command from a command line to start CTGINST1. which contains many entries. Some steps may provide a message log file named stepID_processID. 2. Click Start. The log files for the step are located in the logs subdirectory. Log in as a user with Administrative permissions. Each substep is located in the directory <Workspace Directory>/hostname/ deploymentPlan/MachinePlan_hostname/stepNum_stepID/operation/ substepNum_substepID. Alternatively. b. Logs for substeps Each step contains one or more substeps. usually including information about the input parameters and the substeps invoked. Starting Tivoli Asset Management for IT middleware on Windows This procedure describes how to start middleware on Windows.DB2COPY1 . The primary log files for the machine plan are named MachinePlan_hostname_processID. Start servers by executing the following scripts in the order in which they are listed: Start ctginst1 a. The log files for the machine plan are located in the logs subdirectory. Typical values for operation are install. The log files for the substep are usually located in a subdirectory named processID/logs.msc. All steps will provide a trace log file named stepID_processID. Logs for steps in the deployment plan Each step in the deployment plan is located in a directory named <Workspace Directory>/hostname/deploymentPlan/ MachinePlan_hostname/stepNum_stepID. substepNum is the sequence number of this substep in the processing order of the step. Start ITDS Admin Daemon a. and substepID identifies the substep. 40 Installation Guide for IBM WebSphere Application Server: . Click Start.Logs for the machine plan The machine plan is located in the directory <Workspace Directory>/hostname/deploymentPlan/MachinePlan_hostname. and select Run. where stepNum is the sequence number of this step in install processing order of the deployment plan and stepID identifies the step. and click OK. which contains a few entries that summarize the result of invoking the step. and select Run. should you need to restart any middleware services. These log files contain the output generated by ANT when running the machine plan ANT script. To properly start middleware products on Windows.message. perform the following steps: 1.CTGINST1-0. Type services. c. Log files generated by the native middleware installation programs will also be kept here. The substeps perform the actual install. Select DB2 . uninstall and checking work for the Tivoli middleware installer. uninstall. and click Start the service.

you can type apache from the command line to start the HTTP Server . c. Tivoli Asset Management for IT middleware installation 41 . c. and click Start the service. you can use the following command from the command line to start the ITDS instance: idsslapd -I idsccmdb Important: The IBM Tivoli Directory Server Instance must remain as a manual startup type. and click Start the service.ctginst1 -c db2start Start ITDS Admin Daemon <ITDS_HOME>/sbin/idsdiradm -I idsccmdb Start ITDS server daemon: ibmslapd <ITDS_HOME>/sbin/ibmslapd -I idsccmdb Chapter 4.idsccmdb. Start HTTP Server and webserver1 a. It must be started manually in order to synchronize correctly with the database in the context of Tivoli Asset Management for IT. Type services.bat Start MXServer <WAS_HOME>\profiles\ctgAppSrv01\bin\startServer. Alternatively.msc. Log in as root. Select IBM Tivoli Directory Server Instance V6. and click Start the service. To properly start middleware products on Linux and UNIX systems.bat Start Node <WAS_HOME>\profiles\ctgAppSvr01\bin\startNode.msc.msc.1 .1 .1. 2. b. Alternatively.b. Alternatively. and click OK. Select IBM HTTP Server 6.bat MXServer Starting Tivoli Asset Management for IT middleware on UNIX This procedure describes how to start middleware on Linux and UNIX platforms. Start servers by executing the following scripts in the order in which they are listed: Start ctginst1 instance su . Select IBM Tivoli Directory Admin Daemon V6. and click OK. Click Start and select Run b. Type services. you can use the following command from the command line to start the ITDS admin daemon: idsdiradm -I idsccmdb Start the ITDS instance: a. and select Run. should you need to restart any middleware services. perform the following steps: 1. Click Start. and click OK.idsccmdb. Start Domain Manager <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. Type services. c.

sh Start webserver1 <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh MXServer -username <username> -password <password> Reusing middleware If you intend to reuse existing Tivoli Asset Management for IT middleware servers. To have the Tivoli middleware installer configure an existing DB instance for reuse with Tivoli Asset Management for IT. and it will configure the existing instance for use with Tivoli Asset Management for IT. Reusing DB2 If you have an existing DB2 installation that you would like to reuse for Tivoli Asset Management for IT. Information found in “Tivoli Asset Management for IT installation with manual middleware configuration” on page 86 also applies if you decide that you want to reuse existing Tivoli Asset Management for IT middleware servers but you want to configure them to work with Tivoli Asset Management for IT manually instead of allowing the Tivoli Asset Management for IT installation program to configure them. 42 Installation Guide for IBM WebSphere Application Server: . Login as a user with administrative authority. The Tivoli middleware installer will identify instances of middleware that already exist on the system that are compatible with Tivoli Asset Management for IT. You cannot use the Tivoli middleware installer to configure existing Oracle. 2. Ensure that all of your middleware is at the level described in “Tivoli Asset Management for IT component requirements” on page 3.sh webserver1 -username <username> -password <password> Start MXServer <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.sh Start Node <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.Start HTTP Server Linux /opt/IBM/HTTPServer/bin/apachectl start AIX /usr/IBM/HTTPServer/bin/apachectl start Sun Solaris /opt/IBM/HTTPServer/bin/apachectl start Start Deployment Manager <WAS_HOME>/profiles/ctgDmgr01/bin/startManager. MS SQL. complete the following steps: 1. they must be configured prior to running the Tivoli Asset Management for IT installation program. run the Tivoli middleware installer on the system. or Microsoft Active Directory servers. Launch the Tivoli middleware installer from the launchpad. Refer to “Tivoli Asset Management for IT installation with manual middleware configuration” on page 86 for more information about those servers. This section contains information about configuring existing DB2 and ITDS servers for use with Tivoli Asset Management for IT using the Tivoli middleware installer.

3. Proceed through the Tivoli middleware installer panels as instructed in “Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer” on page 31, until you reach the Deployment Choices panel. 4. From the Deployment Choices panel, select Database Server, and then click Next. The Tivoli middleware installer will display any instances of DB2 found on the system. 5. From the Installation drop-down menu, select the appropriate instance to reuse, and then click Next. 6. Complete the installation by proceeding through the remainder of the Tivoli middleware installer panels. Refer to “Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer” on page 31 for more information. Note that if you are reusing an existing DB2 server with Tivoli Asset Management for IT, the following users and groups must already exist on the system. Users v db2admin v dasusr1 (UNIX) v db2fenc1 (UNIX) Groups v db2admns (Windows) v dasadm1 (UNIX) v dbgrp1 (UNIX) v db2fgrp1 (UNIX) If these users do not exist on the system, you will have to create them prior to running the Tivoli Asset Management for IT installation program.

Reusing Oracle
If you have an existing Oracle 10g instance that you would like to reuse for Tivoli Asset Management for IT, you will have to manually configure it. Refer to“Manually configuring Oracle 10g” on page 93 for information. For an existing Oracle 9.2 instance, refer to “Manually configuring Oracle9i Rel2” on page 95

Reusing IBM Tivoli Directory Server
If you have an existing IBM Tivoli Directory Server installation that you would like to reuse for Tivoli Asset Management for IT, run the Tivoli middleware installer on the system. The Tivoli middleware installer will identify middleware that already exists on the system that is compatible with Tivoli Asset Management for IT, and it will configure it for use with Tivoli Asset Management for IT. Note: The Tivoli middleware installer will create a new instance on the existing IBM Tivoli Directory Server that you identify. This new instance will contain default Tivoli Asset Management for IT LDAP information. If you intend to use Tivoli Asset Management for IT with an existing IBM Tivoli Directory Server instance that contains your organization’s LDAP information, do not run the Tivoli middleware installer to configure the existing IBM Tivoli Directory Server. To use the existing IBM Tivoli Directory Server instance that contains your organization’s
Chapter 4. Tivoli Asset Management for IT middleware installation

43

LDAP information with Tivoli Asset Management for IT, refer to “Manually configuring IBM Tivoli Directory Server” on page 99. To have the Tivoli middleware installer configure an existing IBM Tivoli Directory Server instance for reuse with Tivoli Asset Management for IT, complete the following steps: 1. Login as a user with administrative authority. 2. Launch the Tivoli middleware installer from the launchpad. 3. Proceed through the Tivoli middleware installer panels as instructed in “Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer” on page 31, until you reach the Deployment Choices panel. 4. From the Deployment Choices panel, select Directory Server, and then click Next. The Tivoli middleware installer will display any instances of IBM Tivoli Directory Server found on the system. 5. From the Installation drop-down menu, select the appropriate instance to reuse, and then click Next. 6. Complete the installation by proceeding through the remainder of the Tivoli middleware installer panels. Refer to “Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer” on page 31 for more information.

Reusing Microsoft Active Directory
If you have an existing Microsoft Active Directory instance, you can use it to secure WebSphere when you install it on the system. The Tivoli middleware installer will prompt you for LDAP configuration parameters to use with WebSphere. To have the Tivoli middleware installer configure an existing Microsoft Active Directory instance to secure WebSphere, complete the following steps: 1. Login as a user with administrative authority. 2. Launch the Tivoli middleware installer from the launchpad. 3. Proceed through the Tivoli middleware installer panels as instructed in “Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer” on page 31, until you reach the Deployment Choices panel. 4. From the Deployment Choices panel, deselect the Directory Server deployment option, and then click Next. In the next panel, will be given the choice of selecting an existing instance of IBM Tivoli Directory Server or Microsoft Active Directory to secure WebSphere. 5. Select Secure with Active Directory, and click Next. 6. Supply the following configuration values for WebSphere security, and then click Next. LDAP Hostname Enter the fully qualified name of the machine hosting Microsoft Active Directory. Directory server port 389

44

Installation Guide for IBM WebSphere Application Server:

LDAP base entity DC=itsm,DC=com User suffix OU=Users,OU=SWG,DC=itsm,DC=com Group suffix OU=Groups,OU=SWG,DC=itsm,DC=com Organization container suffix DC=itsm,DC=com In this example. itsm is the domain name. You need to replace itsm with the name of your own domain. 7. Supply the following configuration values for WebSphere security, and then click Next. Bind distinguished name CN=Administrator,CN=Users,DC=itsm,DC=com This value assumes that the Administrator user is already a member of the itsm domain. Bind password Enter the password for the Administrator user on the system hosting Microsoft Active Directory. In this example. itsm is the domain name. You need to replace itsm with the name of your own domain. 8. Complete the installation by proceeding through the remainder of the Tivoli middleware installer panels. Refer to “Installing and configuring Tivoli Asset Management for IT middleware with the Tivoli middleware installer” on page 31 for more information. Note that prior to running the Tivoli Asset Management for IT installation program, you must manually create the users and groups listed in “Manually configuring Microsoft Active Directory” on page 102. This step can be performed after you have installed middleware using the Tivoli middleware installer, but it must be completed before you begin using the Tivoli Asset Management for IT installation program.

Uninstalling Tivoli Asset Management for IT middleware
Uninstalling middleware consists of running the Tivoli middleware installer and using it to undeploy the previously deployed deployment plan. Note: You must use the Tivoli middleware installer to uninstall any Tivoli Asset Management for IT middleware installed by the Tivoli middleware installer. The Tivoli middleware installer creates a registry when installing Tivoli Asset Management for IT middleware. If you use the native middleware uninstall programs, this registry will be out of sync with what is deployed. This will cause errors if you then try to reinstall Tivoli Asset Management for IT middleware using the Tivoli middleware installer. Note: At points during the uninstall process, the Tivoli middleware installer uninstall progress bar might appear to pause. This is normal behavior. In most cases, the Tivoli middleware installer uninstall progress bar will resume shortly

Chapter 4. Tivoli Asset Management for IT middleware installation

45

1”. the Tivoli Asset Management for IT product package includes installation images for the following middleware products: v IBM DB2 9. and run the following command: launchpad. 9. a. Click the Middleware link under 1.after pausing. complete the following steps: 1. If you suspect your uninstall process has experienced an error. such as redeploying components. select Undeploy the plan. From the Welcome panel. click Next to select a new operation. From the successful undeployment panel. AIX and Sun Solaris. Installing Tivoli Asset Management for IT middleware on zLinux (Linux/390) While the Tivoli Asset Management for IT middleware installation program does not support the automated installation of Tivoli Asset Management for IT middleware on zLinux systems. To undeploy Tivoli Asset Management for IT middleware.sh. Click Next. Launch the Tivoli middleware installer from the launchpad. refer to the Tivoli middleware installer log files. Start the launchpad: v Windows: On the DVD titled “Tivoli Asset Management for IT V7. 3. In the launchpad navigation pane. v Sun Solaris: On the DVD titled “Tivoli Asset Management for IT V7.sh. To uninstall the J2EE server. navigate to the root directory of the product disc or the downloaded installation image.1”. 8. navigate to the root directory of the product disc or the downloaded installation image. specify the workspace directory containing the currently deployed plan. 5. The Tivoli middleware installer license agreement window is displayed. v AIX : On the DVD titled “Tivoli Asset Management for IT V7.1”. Read the license information and select I accept both the IBM and the non-IBM terms if you agree with the terms.exe. From the undeployment preview panel.1”. 6. From the Choose Workspace panel.1 46 Installation Guide for IBM WebSphere Application Server: . c. click Install the Product. The default location for the workspace will be the last workspace location specified. navigate to the root directory of the product disc or the downloaded installation image. click Next. v Linux: On the DVD titled “Tivoli Asset Management for IT V7.1 v IBM Tivoli Directory Server 6. navigate to the root directory of the product disc or the downloaded installation image.sh b. and run the following command: launchpad. Install the middleware. and then click Next. Do not uninstall the directory server until the J2EE server has been uninstalled. Login as Administrator on Windows and root on Linux. From the Select Operation panel. ensure the directory server (IBM Tivoli Directory Server or Active Directory) is active. click Next to undeploy the plan. Select a language for the installation and click OK. 4. and run the following command: launchpad. The default location for the workspace is c:\ibm\tivoli\mwi\ workspace 7. 2. and run the following command: launchpad. or click Cancel to exit the Tivoli middleware installer. and then click Next.

consider the following: v Refer to the relevant information for installing DB2 on Linux at the DB2 9 Enterprise Edition infocenter: http://publib. v The DB2 product image must be available.1 Middleware for zLinux product DVD.4 or higher. Before you start the DB2 Setup wizard.com/infocenter/dzichelp/v2r2/index. v You must have root authority to perform the installation. Installing and configuring DB2 on zLinux Use this information to successfully install and configure DB2 on zLinux. and communications prerequisites must be met. The NAS client can be downloaded from https://www6. while WebSphere uses IBM Tivoli Directory Server for security. memory. To install DB2 version 9 on your zLinux system. you can also reuse those resources in your Tivoli Asset Management for IT deployment. IBM Tivoli Directory Server uses DB2 as its data repository. hardware. v The DB2 Setup wizard is a graphical installer (Available only on Linux for x86 and Linux on AMD 64/EM64T. Refer to the DB2 9 Enterprise Edition infocenter to ensure you meet all hardware and software prerequisites. If the Tivoli Asset Management for IT 7.0 and up The use of XML features is restricted to a database that is defined with the code set UTF-8 and has only one database partition. You must have X windows software capable of rendering a graphical user interface for the DB2 Setup wizard to run on your machine.jsp.com/dl/dm/dmnas-p. If you have existing DB2 and Tivoli Directory Server instances at the appropriate level in your network. and disk requirements. For example. Ensure that you have properly exported your display. You will have to copy the images off of the product media provided and uncompress them onto your system.4 and up – Firefox 1.0 and up – Netscape 7. v One of the following browsers is required to view online help and to run First Steps (db2fs): – Mozilla 1. mount your Tivoli Asset Management for IT 7.).software.ibm.boulder. v Ensure that your system meets installation. Tivoli Asset Management for IT middleware installation 47 .v WebSphere Application Server ND 6.1 Using the native installation program for each product. v (DB2 Clients only) If you plan to use Kerberos Authentication. export DISPLAY=<youripaddress>:0. The DB2 Setup wizard is used to define your installation preferences and to install your DB2 product on your system. Features include: Chapter 4. you require IBM Network Authentication Service (NAS) client version 1. Ensure that the X windows server is running.1 Middleware for zLinux DVD does not automount. certain operating system. you could install middleware manually in the order shown above if you choose to deploy Tivoli Asset Management for IT in an environment where zLinux systems will host Tivoli Asset Management for IT middleware.ibm.

exceptions and trap information). 9.tar. Log in as root. 6.log file captures all DB2 installation information including errors. The db2setup. Review the license agreement displayed.tar file down to a local directory on your system. v Setting up database partitioning options for the DB2 instance. Click Next. To invoke the installation help. Your DB2 product will be installed. By installing multiple languages. Unpack the file: tar -xvf DB2_Enterprise_Svr_Ed_Linux_zSeries. 48 Installation Guide for IBM WebSphere Application Server: . you can view installation prerequisites and the release notes. follow these steps: 1.err file captures any error output that is returned by Java (for example. in the /tmp directory. 7. and learn about DB2 Version 9 features. and then click Next. v Creating response files. v Setting up the DB2 Administration Server (including DAS user setup). v Setting up and configuring your instance setup and configuration (including instance user setup). 4. 2. The Software License Agreement panel is displayed. You can specify the location of the log files. You can click Cancel at any time to end the installation.1 directory. you can view the interface and messages in your preferred languages. Click Install a Product. The IBM DB2 Setup launchpad opens. compact.1 Middleware for zLinux DVD in your DVD-ROM drive.err will be located. 10. click Help or press F1. Copy the DB2_Enterprise_Svr_Ed_Linux_zSeries. The db2setup. Change directory to linux390\DB2-ESE_9. To install DB2 on zLinux. From this window. or custom). v Setting the user interface and product messages. 11. 3.0 on the DVD. by default. Installation help is available from the DB2 Setup wizard installation panels to guide you through the steps. in the /opt/IBM/db2/V9. The Install a Product window will display the products available for installation. v Selecting DB2 installation type (typical. The Select the installation type panel is displayed. by default. db2setup.v A launchpad from which you can view installation notes and release notes. v Preparing the DB2 tools catalog.log and db2setup. The user interface and product messages are available in several languages and are installed in the languages that you choose. Insert the Tivoli Asset Management for IT 7. Create a user (recommended value is maximo with a password of maximo) on the system and assign the new user to a group with administrative authority. The installation logs. select Accept. or you can proceed directly to the installation. 5. 8. v Selecting DB2 product installation location. v Setting up Administration contact and health monitor notification.1. You may want to review the installation prerequisites and release notes for late-breaking information. Launch the DB2 Enterprise Server Edition installation by clicking Install New. The Welcome to DB2 setup wizard panel is displayed./db2setup to start the DB2 Setup wizard. Type .

Tivoli Asset Management for IT middleware installation 49 . The Set user information for the DB2 instance owner panel is displayed. and then click Next. Select Single partition instance. Provide the following information. 16. 15. and then click Next. Select Typical: 410 . The Set up a DB2 instance panel is displayed. refer to the installation wizard panel help by using the F1 function key. If it does not already exist on the system. Directory Designate a directory for installing DB2. 17.8 characters. The user name should consist of 1 . and then click Next. Group name Enter a primary group for the user. 13. User name Enter a user name to associate with the DB2 administration server. You will have to enter a location and file name to store response file values. Password Create a password for the user. response file creation. New user Select New user to enable the fields for creating a new DB2 user. Select Install DB2 Enterprise Server Edition on this computer and save my settings in a response file. The default is dasusr1. UID Leave Use default UID checked to have the installation program generate a UID for the user. The Selection installation. or both panel is displayed. GID Leave Use default GID checked to have the installation program generate a GID for the group. If you wish to set up the DB2 instance across multiple partitions. 18. The default is /home/dasusr1. Provide the following information. and then click Next. 19.8 characters Home directory Enter a directory to use for storing information about the database instance. and then click Next. this path is /opt/IBM/db2/V9. Chapter 4.500 MB. The default is dasadm1. Select Create a DB2 instance. The Select the installation directory panel is displayed. The user name should have SYSADM authority so it can start and stop instances. it will be created. 14. Enter a path and filename for the response file. By default. Provide the following information. The Set up partitioning options for the DB2 instance panel is displayed. The password should consist of 1 .12. The Set user information for the DB2 Administration Server panel is displayed. and then click Next. and then click Next.1.

User name Enter a user name to associate with the DB2 instance.8 characters 50 Installation Guide for IBM WebSphere Application Server: . The default is db2fenc1. Group name Enter a primary group for the user. it will be created. The user name should have SYSADM authority so it can start and stop instances. The Set user information for the fenced user panel is displayed. The password should consist of 1 . GID Leave Use default GID checked to have the installation program generate a GID for the group.New user Select New user to enable the fields for creating a new DB2 user. GID Leave Use default GID checked to have the installation program generate a GID for the group. The default is ctginst1. Password Create a password for the user. UID Leave Use default UID checked to have the installation program generate a UID for the user. and then click Next.8 characters Home directory Enter a directory to use as the home directory of the database instance user. The default is /home/ctginst1. The default is db2fgrp1. it will be created. 20. User name Enter a user name to assign as the fenced user.8 characters. The password should consist of 1 . New user Select New user to enable the fields for creating a new DB2 user. The user name should have SYSADM authority so it can start and stop instances. The user name should consist of 1 . Provide the following information. If it does not already exist on the system. Group name Enter a primary group for the user.8 characters. The user name should consist of 1 . The default for UNIX is db2grp1. Password Create a password for the user. UID Leave Use default UID checked to have the installation program generate a UID for the user. If it does not already exist on the system.

gz d. install DB2 Fix Pack 2. After the Fix Pack installation has concluded. 23. The Start copying files and create response file panel is displayed. f. Notification SMTP server Enter the name of the SMTP server that will be responsible for sending database notifications to the database administrator. stop all instances associated with this copy. When prompted.Home directory Enter a directory to use as the home directory of the fenced user. Select Set up your DB2 server to send notifications. Uncompress the file: gzip -dfv v9fp2_linux390_universal_fixpack. 22. Select New contact. su .tar e. The Prepare the DB2 tools catalog panel is displayed. cd to universal/disk1 then run ./installFixPack to start the Fix Pack installation.tar. c. After successfully completing the DB2 installation. and then click Next. g.gz file down to a local directory on your system. a. Administration contact list location Local Remote Select Remote and then provide the fully qualified name of the remote DB2 server to use an existing contact list that will be used remotely. Chapter 4. Name Enter the user name of the individual assigned to receive notifications related to the state of the DB2 instance The default is ctginst1. 21. provide the following information. 24. The default is /home/db2fenc1.tar.db2inst1 db2stop Select Local to create a contact list on the local machine. Select Do not prepare the DB2 tools catalog. Click Finish to initiate the installation. Change directory to linux390\DB2-Universal_9. refer to the installation wizard panel help for more information by using the F1 function key.1_Fixpacks on the zLinux Middleware DVD. E-mail address Enter the e-mail address for the contact entered in the Name field. The Set up notifications panel is displayed. b. Tivoli Asset Management for IT middleware installation 51 .. Unpack the file: tar -xvf v9fp2_linux390_universal_fixpack. 25. and then click Next. and then click Next. The Specify a contact for the health monitor notification panel is displayed. provide the following information. If you wish to set up the DB2 tools catalog. Copy the v9fp2_linux390_universal_fixpack. enter the install location of DB2.

so plan accordingly when you are designing your Tivoli Asset Management for IT deployment. and create a default directory server instance. consult the IBM Tivoli Directory Server product information for conducting an IBM Tivoli Directory Server custom installation. Typical Use the Typical installation path if you want to accept default settings. follow these steps: 1. Note that IBM Tivoli Directory Server cannot make use of a remote DB2 server as its data repository. Change directory to linux390 on the DVD. Custom Use the Custom installation path if you want to select components for installation and create a directory server instance using the Instance Administration Tool. Start the DB2 instances.1 using the Custom installation path.tar file down to a local directory on your system. This section will detail how to install IBM Tivoli Directory Server using the Custom installation path on a machine that is not hosting other Tivoli Asset Management for IT prerequisite components. When you use this tool you can customize the directory server instance. the following operating system. Typical installation does not allow you to select features for installation. Tivoli Asset Management for IT is not designed to interact with a system that has two different active copies of DB2 running at the same time. Copy the tds61-linux-s390x-CD1_w_entitlement. 4.1 on your zLinux system. 3. 2. Run update: <DB2DIR>/instance/db2iupdt -e 26. To install IBM Tivoli Directory Server V6. There are two installation paths used in the IBM Tivoli Directory Server installation program.1 Middleware for zLinux DVD in your DVD-ROM drive.h. Installing and configuring IBM Tivoli Directory Server on zLinux Use this information to successfully install and configure IBM Tivoli Directory Server on zLinux. Also. and communications prerequisites must be met: Table 11. Prerequisite Comments To install IBM Tivoli Directory Server 6. install all the IBM Tivoli Directory Server components that are not already installed. hardware. Log in as root. Insert the Tivoli Asset Management for IT 7. 52 Installation Guide for IBM WebSphere Application Server: . For more information about reusing an existing DB2 server for use with IBM Tivoli Directory Server.

Select Do not specify. The Select WebSphere Application Server panel is displayed. 10. Prerequisite Comment To install WebSphere Application Server Deployment Manager.sh If you prefer. and then click Next. Tivoli Asset Management for IT middleware installation 53 ./install_tds. Click Finish.1. and then click OK. change directories to the appropriate directory and type . you can specify a temporary directory other than the system temporary directory. follow these steps: 1. /opt/IBM/ldap/V6. Click Next. The Tivoli Directory Server instance creation tool will now launch./install_tds. The License Agreement panel is displayed. 15. Be sure that you have at least 400® MB of free space in this directory.1 (32-bit) on your zLinux system. and communications prerequisites must be met: Table 12. 7. Log in as root. 13. 8. hardware. Select the language you want to use during IBM Tivoli Directory Server installation. and then click Next. where directory is the directory you want to use for temporary space.1 directory. 12. To use this option. This section provides instructions for installing WebSphere Application Server Deployment Manager on zLinux. Read the software license agreement. De-select DB2 V9. Click Install. Chapter 4. not in IBM Tivoli Directory Server. and Tivoli Directory Integrator. This is the language used in the installation program. Embedded WebSphere Application Server./install_tds. 16. 14.1/sbin/ibmslapd -I idsccmdb Installing and configuring WebSphere Application Server Deployment Manager on zLinux Use this information to successfully install and configure WebSphere Application Server Deployment Manager on zLinux. Unpack the file: tar -xvf tds61-linux-s390x-CD1_w_entitlement. Create the idsccmdb ITDS instance.1/tds directory and then type . Select Custom and then click Next.sh -is:tempdir /opt/tmp The Select Language panel is displayed. Start ITDS. Refer to “Manually configuring IBM Tivoli Directory Server” on page 99 for more information. the following operating system. 9. select I accept both the IBM and the non-IBM terms. Change to the /tdsV6. You will install the products separately. The Welcome panel is displayed. For example: . The Summary panel is displayed. and then click Next. 11.tar 6. To install WebSphere Application Server Deployment Manager V6. IBM Tivoli Directory Server will be installed into the /opt/IBM/ldap/V6.5.1/sbin/idsdiradm -I idsccmdb /opt/IBM/ldap/V6.sh -is:tempdir directory at a command prompt. I will manually deploy at a later time. The language used in IBM Tivoli Directory Server is determined by the language pack you install.

Select None as your environment. Change directory to linux390/WS-WAS_ND_6. the following prerequisite tasks must first be completed: 54 Installation Guide for IBM WebSphere Application Server: . and then click Next.tar. Spaces are not supported in the name of the installation directory. 5.1. 3. 11. 14. 4. This section provides instructions for creating two profiles that will be expected by the Tivoli Asset Management for IT installation program. 13. Uncompress the file: gzip -dfv WAS-ND_linux390x_Custom_v6113. select Accept.gz file down to a local directory on your system. Review the license agreement displayed. Creating profiles using 64-bit WebSphere Application Server Deployment Manager for zLinux Use this information to successfully create profiles using 64-bit WebSphere Application Server Deployment Manager for zLinux.2. 10.tar 7. Enter the . Click Finish. 12. and then click Next. Symbolic links are not supported. To create 64-bit WebSphere Application Server Deployment Manager profiles on your zLinux system. The Software License Agreement panel is displayed. 8.1 Middleware for zLinux DVD in your DVD-ROM drive. The Welcome to the IBM WebSphere Application Server Network Deployment install wizard panel is displayed. Click Next. /WAS.0. The Prerequisite Check panel is displayed.tar. deployment manager profile. The Installation Directory panel is displayed.gz 6. 9. Unpack the file: tar -xvf WAS-ND_linux390x_Custom_v6113. The default is /opt/IBM/WebSphere/ AppServer. Click Yes to indicate that you want to proceed. Click Next. Copy the WAS-ND_linux390_Custom_v6113. Confirm that your operating system is supported and that you have installed all necessary patches. Do not use symbolic links as the destination directory. where you unpacked the tar file to start the WebSphere Setup wizard. The Installation Summary panel is displayed. Insert the Tivoli Asset Management for IT 7. Selecting None means you will be creating the Tivoli Asset Management for IT deployment cell. and then click Next. The WebSphere Application Server Environments panel is displayed. and then click Next./install command from the WebSphere directory. Enter the installation path for IBM WebSphere Application Server Network Deployment. 15.13_Custom_ISCAE71 on the DVD. The Installation Results panel is displayed. for example. and the application server profile using the profile management tool.

sh -username <username> -password <password> <WAS_HOME>/profiles/ctgDmgr01/bin/ startManager. but with an extra space. as can happen when cutting and pasting an example. you might intend the value “WC_adminhost=9060”.sh -listProfiles To create profiles. It is important that you ensure no spaces appear after any value in this file. Tivoli Asset Management for IT middleware installation 55 . For example.sh 2.sh -delete -profileName <profile name> <WAS_HOME>/bin/manageprofiles. Profile commands Task Delete a profile Refresh the profile registry (for example. a. If there is an extra space trailing any of the values. The 64-bit version of IBM WebSphere Network Deployment for zLinux includes the manageprofiles command line tool which you will use to create profiles required by Tivoli Asset Management for IT.Table 13.sh -validateAndUpdateRegistry <WAS_HOME>/bin/manageprofiles. <WAS_HOME>/bin/setupCmdLine.sh Restart servers after augmenting the ctgDmgr01 profile. Create a profile ports file for the ctgDmgr01 profile. Create a new text file named _portdef_DMgr.props and enter the following text: CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9403 WC_adminhost=9060 DCS_UNICAST_ADDRESS=9352 BOOTSTRAP_ADDRESS=9809 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9401 CELL_DISCOVERY_ADDRESS=7277 SOAP_CONNECTOR_ADDRESS=8879 Chapter 4. Command <WAS_HOME>/bin/manageprofiles. The following commands can be useful for managing profiles: Table 14. after deleting a profile) List existing profiles Command <WAS_HOME>/bin/manageprofiles. This file will be used by the manageprofiles command to set the ports that will be used by this profile. follow these steps: 1. Source the setupCmdLine.sh script in the bin directory of the <WAS_HOME> folder to set the WebSphere Application Server environment to the configuration instance. that value will be “WC_adminhost=9060<sp>” where <sp> denotes a blank space.sh -augment -templatePath <WAS_HOME>/ profileTemplates/iscae71 -profileName ctgDmgr01 -serverName dmgr <WAS_HOME>/profiles/ctgDmgr01/bin/ stopManager. WebSphere will use that space as the last character of that value. Prerequisite Task Augment the ctgDmgr01 profile.

6.sh -create -templatePath <WAS_HOME>/profileTemplates/managed -hostName yourfullyqualifiedhost -profileName ctgAppSrv01 -profilePath <WAS_HOME>/profiles/ctgAppSrv01 -cellName ctgNodeCell01 -nodeName ctgNode01 -portsFile <WAS_HOME>/_portdef_AppSvr.sh -create -templatePath <WAS_HOME>/profileTemplates/dmgr -hostName yourfullyqualifiedhost -profileName ctgDmgr01 -profilePath <WAS_HOME>/profiles/ctgDmgr01 -portsFile <WAS_HOME>/_portdef_DMgr. This file will be used by the manageprofiles command to set the ports that will be used by this profile. Place the file in the <WAS_HOME> directory. <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.props and enter the following text: CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=9201 DCS_UNICAST_ADDRESS=9353 NODE_DISCOVERY_ADDRESS=7272 NODE_IPV6_MULTICAST_DISCOVERY_ADDRESS=5001 BOOTSTRAP_ADDRESS=2809 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=9901 SOAP_CONNECTOR_ADDRESS=8878 NODE_MULTICAST_DISCOVERY_ADDRESS=5000 ORB_LISTENER_ADDRESS=9101 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9202 b. ORB_LISTENER_ADDRESS=9100 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=9402 WC_adminhost_secure=9043 b. 5. 7.sh 56 Installation Guide for IBM WebSphere Application Server: . Create the ctgDmgr01 profile using the manageprofiles command: <WAS_HOME>/bin/manageprofiles.sh Create a profile ports file for the ctgAppSrv01 profile. Create the ctgAppSrv01 profile using the manageprofiles command: <WAS_HOME>/bin/manageprofiles. start the ctgAppSrv01 node. Place the file in the <WAS_HOME> directory.3. 4. Create a new text file named _portdef_AppSvr. 8.props -cellName ctgCell01 -nodeName ctgCellManager01 -enableAdminSecurity ″false″ -adminUserName wasadmin -adminPassword wasadmin Start the ctgDmgr01 server: <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh Launch firststeps. a.props -dmgrHost yourfullyqualifiedhost -dmgrAdminUserName wasadmin -dmgrAdminPassword wasadmin -dmgrPort 8879 -isDefault If it is not already started.sh to verify installation: <WAS_HOME>/profiles/ctgDmgr01/firststeps/firststeps.

HTTP Port 80 HTTP Administration Port 8008 The Setup HTTP Administration Server panel is displayed. This section provides instructions for installing IBM HTTP Server on zLinux.Installing and configuring IBM HTTP Server on zLinux Use this information to successfully install and configure IBM HTTP Server on zLinux. 7. Log in as root on the machine where you have installed WebSphere. 5. 6. The Port Values Assignment panel is displayed. Install the IBM HTTP Server Plug-in for IBM WebSphere Application Server Disable In an environment where you have multiple deployment manager profiles. Specify the following values and then click Next. The default is /opt/IBM/HTTPServer. To install IBM HTTP Server.sh 3. Specify the install location information and click Next. 2. Log into the WebSphere Administration Console and ensure the ctgDmgr01 deployment manager is running and the SOAP port is set to listen at the correct port (8879 is the default). 8. Click Next. launch the IBM HTTP Server installation program: <WebSphere Image Directory>/IHS/install The Welcome panel is displayed. 11. and click Next. use the following command: <WAS_HOME>/profiles/ctgDmgr01/bin/startManager. 10. Setup IBM HTTP administration server to administer IBM HTTP Server Enabled Create a unique user ID and group for IBM HTTP Server administration Enabled User ID wasadmin Group ihsadmin The IBM HTTP Server Plug-in for WebSphere Application Server panel is displayed. Specify the following values. it is more practical to run the Web server plug-ins installation task separately by running the plug-in installation program after Chapter 4. 9. follow these steps: 1. Tivoli Asset Management for IT middleware installation 57 . Accept the license agreement and click Next System prerequisites check panel is displayed. Click Next. Create a User ID for IBM HTTP Administration server authentication and click Next. and click Next. From a command line. Specify the following values. The License Agreement panel is displayed. 4. If the deployment manager needs to be started.

and then click Next.pak For more information about deployment scenarios for IBM HTTP Server.exiting the IBM HTTP Server installation program. Accept the license agreement and click Next From the system check panel.conf. 9. 6. this directory is listed as /opt/IBM/WebSphere/AppServer. To install the WebSphere Plug-in.1. Log in as root on the machine where you have installed WebSphere. Accept the default. 10. Click Next. The License Agreement panel is displayed.conf file Browse to the location of the httpd.html . if your WebSphere environment only contains the single deployment manager profile used for Tivoli Asset Management for IT.jsp?topic=/ com. However. 13. Select ctgDmgr01 from the drop-down list.1. 4. The select profile panel is displayed. and click Next.ibm.websphere. for example). Browse to the directory where you installed WebSphere. and then lick Next. Specify the following: Select the existing IBM HTTP Server httpd. The input summary panel is displayed. 12. By default. This section provides instructions for installing the WebSphere Plug-in on zLinux. By default. The web server install path panel is displayed. Browse to the directory where you installed IBM HTTP Server.ihs. 7. The Web server plugin-cfg. 8. Install the following IBM HTTP Server fixpack: linux390\WSWAS_IHS_6.ibm.0_FP13\6.0-WS-IHS-LinuxS39064-FP0000013.boulder. 12. 11. Click Next. launch the WebSphere Plug-in installation program: <WebSphere Image Directory>/plugin/install The Welcome panel is displayed. this directory is listed as /opt/IBM/HTTPServer/Plugins. Specify the Web server port 80 The Web server definition panel is displayed. 14. and then click Next. follow these steps: 1.doc/info/welcome_ihs. you can leave the WebSphere plug-in option selected. Specify a unique Web server definition name (webserver1.conf file. The Installation Summary panel is displayed. By default. and then click Next. and then click Next. 58 Installation Guide for IBM WebSphere Application Server: . From a command line.com/infocenter/wasinfo/v6r1/index.xml file panel is displayed. 3. refer to http://publib. which will launch the Web server plug-ins installation task when you click Next. Click Finish. The web server configuration file panel is displayed. click Next Select WebSphere Application Server machine (local). The WebSphere install path panel is displayed. Installing and configuring the WebSphere Plug-in on zLinux Use this information to successfully install and configure the WebSphere Plug-in on zLinux. 2. 5. this file is located at /opt/IBM/HTTPServer/conf/httpd.

/configurewebserver1. Tivoli Asset Management for IT middleware installation 59 . 5. When the installation is complete. 20. From the summary panel. 3. Enter the install directory path.0_FP13\6. Accept the license agreement./setup. Change directory to linux390/Rational-AgentController_7. Type . 10. and then click Next.bin to start the setup wizard.sh file to <WAS_HOME>/bin/ Change directory to <WAS_HOME>/bin and then execute the following command: . Installing and configuring IBM Agent Controller on zLinux Use this information to successfully install and configure IBM Agent Controller on zLinux. Insert the Tivoli Asset Management for IT 7. 7.sh Start the deployment manager <WAS_HOME>/profiles/ctgDmgr01/bin/startManager. Click Next. 19. 11. 18. The license agreement panel is displayed. Log in as root. 17. 6. 9.sh Start the HTTP servers: /opt/IBM/HTTPServer/bin/adminctl start /opt/IBM/HTTPServer/bin/apachectl start Login to the WebSphere administrator console and ensure that webserver1 has started.0 or later for the WebSphere version. To install IBM Agent Controller . This section provides instructions for installing IBM Agent Controller on zLinux. Click Next. Install the following WebSphere Plug-in fixpack: linux390\WSWAS_Plugins_6.0-WS-PLG-LinuxS39064-FP0000013.1 Middleware for zLinux DVD in your DVD-ROM drive. Chapter 4. 2. Select V6. The security panel is displayed. Click Finish. Choose Any computer for the access list. Click Next. when the process is complete.13. click Finish.sh Copy the /opt/IBM/HTTPServer/Plugins/bin/configurewebserver1.pak 16. and then click Next. click Install. The Welcome panel is displayed. 13. and then click Next. follow these steps: 1. 15. 4.1. 14. The IBM Agent Controller is used to retrieve log and trace data for use by the log and trace analyzer. and then click Next. The installation summary panel is displayed.0.1. 8. Restart deployment manager: Stop the deployment manager <WAS_HOME>/profiles/ctgDmgr01/bin/stopManager. v wasadmin v root v maximo 12. Enter the following user IDs and then click Next.3/linux_s390 on the DVD.

Refer to “Manually configuring Virtual Member Manager on WebSphere” on page 108 for information on adding an IBM Tivoli Directory Server repository to VMM.bat MXServer -username <username> -password <password> Alternatively you can start MXServer from the WebSphere administrative console: 1.sh webserver1 -username <username> -password <password> Windows <WAS_HOME>profiles\ctgAppSrv01\bin\startServer. Start the Deployment Manager: UNIX <WAS_HOME>/AppServer/profiles/ctgDmgr01/bin/startManager.Installing and configuring Virtual Member Manager on WebSphere on zLinux Use this information to successfully install and configure Virtual Member Manager on WebSphere on zLinux.bat 3.bat 2.sh Windows <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. Start the App Server : UNIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer. WebSphere management IBM provides comprehensive information on running and administering WebSphere at this URL: http://publib.ibm. complete the following steps: 1. To start the MXServer application .bat webserver1 -username <username> -password <password> 4. Start the Node: UNIX <WAS_HOME>r/profiles/ctgAppSrv01/bin/startNode.sh MXServer -username <username> -password <password> Windows <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer. To start the administrative console. Virtual Member Manager (VMM) provides you with the ability to access and maintain user data in multiple repositories.boulder. open a browser window and enter the following URL: http://<machine_name>:9060/ibm/console 60 Installation Guide for IBM WebSphere Application Server: .com/infocenter/wasinfo/v6r1/index.sh Windows <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode. and federate that data into a single virtual repository.jsp Starting the WebSphere Application Server An application server named MXServer was created during installation. Start the web server: UNIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startServer.

and click OK.bat <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode. 4.sh <WAS_HOME>/profiles/ctgAppSrv01/bin/stopNode. Server HTTP Server Go To Windows <HTTP_SERVER_HOME>\bin\apache -k start \<HTTP_SERVER_HOME>\bin\apache -k stop UNIX <HTTP_SERVER_HOME>/bin/apachectl start <HTTP_SERVER_HOME>/bin/apachectl stop Deployment Manager Windows <WAS_HOME> \profiles\ctgDmgr01\bin\startManager. verify that these server processes are running.idsccmdb -c db2start Chapter 4.bat UNIX <WAS_HOME>/profiles/ctgDmgr01/bin/startManager.sh ITDS Instance Windows 1. and select Run. 3. Before you start the Administrative console.Where <machine_name> is the host name of the WebSphere Application Server and 9060 is the default port number for the Administrative Console.CTGINST1-0. 5. Click Start. if one is required. click Stop.idsccmdb. and click OK. the name of the WebSphere Application Server. Click Start.msc.1 . Notice that the icon in the Status column changes to running 6. UNIX su . 2. Notice that the icon in the Status column changes to stopped. and click Start the service. and select Run.DB2COPY1 . 2. 3.sh <WAS_HOME>/profiles/ctgDmgr01/bin/stopManager. 2. 3. Type services. Select DB2 . Type services.bat <WAS_HOME> \profiles\ctgDmgr01\bin\stopManager. UNIX Directory Server Database /ldap/V6. From the administrative console navigation pane. Enter an administrative user ID and password to login.msc. Select IBM Tivoli Directory Server Instance V6. Click Start.sh Node Agent Windows <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode.1/sbin/ibmslapd -I idsccmdb Windows 1. Select the check box next to MXServer. and click Start the service. To stop the WebSphere Application Server. Tivoli Asset Management for IT middleware installation 61 . Table 15. click Servers → Application Servers.bat UNIX <WAS_HOME>/profiles/ctgAppSrv01/bin/startNode.

Has monitor permissions and can change the run-time state. . you can determine their level of access by assigning roles. Admin Role Administrator Operator Configurator Monitor deployer adminsecuritymanager Description Has operator permissions. the operator can start or stop services. Users granted this role can perform both configuration actions and runtime operations on applications. However. Once you have enabled VMM for WebSphere security. Has the least permissions. click Users and Groups in the console navigation tree and then click either Manage Users or Manage Groups. Until you enable security. an administrator cannot assign users and groups to the administrative user roles and administrative group roles including the adminsecuritymanager role.To start the Administrative Console. and infrastructure → Administrative Group Roles to view the available administrative group roles. VMM must have been configured on the WebSphere server prior to securing the console. you perform several steps to secure the console. you can login with any user ID. Using the adminsecuritymanager role. Simply click Security → Secure administration. complete the following steps: 1. You can use the Administrative Group Roles page to give groups specific authority to administer application servers through the administrative console. Open a browser window. After you decide which users you want to access the console. configurator permissions. However. and the permission that is required to access sensitive data. a user must enter a valid administrator user ID and password to access the console. Table 16. Fine-grained administrative security is available using wsadmin only. The user ID does not have to be a valid system user. you can assign users and groups to the adminsecuritymanager role on the cell level through wsadmin scripts and the administrative console. iscadmins Note: To manage users and groups. you can assign users and groups to the administrative user roles and administrative group roles. First you identify users (or groups) that are defined in the active user registry. and enter the following URL: http://<machine_name>:9060/ibm/console Where <machine_name> is the host name of the WebSphere Application Server and 9060 is the default port number for the Administrative Console. For example. applications. Has administrator privileges for managing users and groups from within the administrative console only. Enter a user ID to login. Securing the WebSphere Administrative Console You can secure the Administrative Console so that only authenticated users can use it. 2. 62 Installation Guide for IBM WebSphere Application Server: . This role primarily confines the user to viewing the application server configuration and current state. The roles determine the administrative actions that a user can perform. After enabling security. Has monitor permissions and can change the application server configuration.

4. 6. Select Applications → Enterprise applications → application_name. select MXServer and click Start. Users and groups are associated with roles defined in an application when the application is installed or configured. Restart all the application servers. for example. 4.log) restart restarts the existing service automatically if the service fails when set to true. Mapping users or groups to a role authorizes those users or groups to access applications defined by the role. C:\Program Files\IBM\WebSphere\AppServer\profiles logRoot folder location of MXServer log file.Complete the following steps to map users and groups to security roles: 1. Open a command prompt window. Click >> to add users from the Available list to the Selected list. Run the WASService command with the following parameters: serverName name of Maximo application server. and click Stop. for example. for example. 3. For example: C:\Program Files\IBM\WebSphere\AppServer\bin 8. Select MXServer. 3. Use the Search pattern field to display users in the Available list. This action creates a server log folder used by the WASService command. Tivoli Asset Management for IT middleware installation 63 . Select the role and click either Look up users or Look up groups. Configuring the WebSphere Application Server to run as a Windows service To configure the WebSphere Application Server to run as a Windows service. 9. Enter an administrative user ID and password. C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 wasHome home folder for MXServer. Under Detail properties. Different roles can have different security authorizations. 2. In the Application Servers pane. Navigate to the bin folder where you installed the Maximo application server. 7. click Security role to user/group mapping. Start the WebSphere Administrative Console by opening a browser window and entering the following URL http://<machine_name>:9060/ibm/console 2. 5. C:\Program Files\IBM\WebSphere\AppServer\logs\ manageprofiles\ctgAppSrv01 logFile log file name for MXServer (startServer. complete the following steps: 1. Enter the WASService command using the following syntax: Chapter 4. MXServer profilePath the profile directory of the server. Click Servers → Application Servers in the navigation pane.

log) 64 Installation Guide for IBM WebSphere Application Server: . Open a Services window and double-click MXServer. 4. Before you run the WASService command. b. 7. Change the Startup type field value to Automatic. Navigate to the bin folder where you installed the Node Agent. In the System Administration pane. Start the WebSphere 6. 6. C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 wasHome home folder for MXServer. Then perform the following actions: a. complete the following steps: 1. Configuring the WebSphere node agent to run as a Windows service A node agent is a server running on every host computer in the deployed network. select nodeagent in the Administration pane. Click Start to start the service. 11. Run the WASService command with the following parameters: serverName name of node agent. 5.1 Administrative Console by opening a browser window and entering the following URL: http://<machine_name>:9060/ibm/console 2. and you will see a confirmation message. for example. and click Start. For example: C:\Program Files\IBM\WebSphere\AppServer\bin 8. c. Click System Administration in the navigation pane. Open a command prompt window. for example. and click Stop. C:\Program Files\IBM\WebSphere\AppServer\profiles logRoot folder location of node agent log file. select the name of the Node Agent (for example.log restart true 10. Press <Enter> after you type the WASService command. for example. 3. Enter an administrative user ID and password. nodeAgent profilePath the profile directory of the server. nodeagent). for example. To configure the WebSphere node agent to run as a Windows service. It performs administrative functions.WASService add MXServer serverName MXServer profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\ ctgAppSrv01wasHome <D:>\IBM\WebSphere\AppServer logRoot C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ ctgAppSrv01 logFile C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ ctgAppSrv01\startServer. C:\Program Files\IBM\WebSphere\AppServer\logs\manageprofiles\ ctgAppSrv01 logFile log file name for node agent (startServer. Click OK.

nodeAgent. Tivoli Asset Management for IT EAR and WAR files EAR File maximo. Tivoli Asset Management for IT middleware installation 65 . WebSphere Portal Server needs to be hosted on a system other than the system hosting the Tivoli Asset Management for IT J2EE server. Change the Startup type field value to Automatic. rebuilt. 9.ear Description This EAR file contains the maximo. The following EAR files are deployed by the Tivoli Asset Management for IT installation and the Process Solution installation programs and are candidates for being modified. Open a Services window and double-click the Node Agent service.log restart true 10. Click Start to start the service. WebSphere Portal Server overview An existing WebSphere Portal Server system can be configured to work with your Tivoli Asset Management for IT deployment after it has been successfully installed. for example.war file which is for Tivoli Asset Management for IT Help Location <TAMIT_HOME>\maximo\ deployment\default maximohelp. b. WebSphere Portal Server must be configured to use a version of WebSphere that it supports. and redeployed: Table 17. Then perform the following actions: a. You can access Tivoli Asset Management for IT applications through the WebSphere Portal Server interface transparently. Tivoli Asset Management for IT deployed on WebSphere Portal Server Tivoli Asset Management for IT deployed on WebSphere Portal Server After Tivoli Asset Management for IT has been completely deployed. Press <Enter> after you type the WASService command. c. centralizing Tivoli Asset Management for IT application access alongside other service-oriented applications used by your organization.ear <TAMIT_HOME>\maximo\ deployment\default Chapter 4. Enter the WASService command using the following syntax: WASService add NodeAgent serverName nodeagent profilePath C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 wasHome <D:>\IBM\WebSphere\AppServer logRoot <D:>\IBM\WebSphere\AppServer\logs\nodeagent logFile <D:>\IBM\WebSphere\AppServer\logs\nodeagent\ startServer.war file which includesTivoli Asset Management for IT base tasks. Click OK.restart restarts the existing service automatically if the service fails when set to true. 11. the user interface for any Tivoli Asset Management for IT application can be accessed through a portlet hosted on an existing WebSphere Portal Server instance. This EAR file contains the maximohelp. and you will see a confirmation message.

To create a page with a portlet for a Tivoli Asset Management for IT application you wish to access through WebSphere Portal Server, ensure you have a working and active Tivoli Asset Management for IT deployment, and then complete the following steps: 1. From the Tivoli Asset Management for IT administrative workstation, open a Web browser and access the WebSphere Portal Server Administration tool.
http://<hostname>:<portnumber>/wps/portal

2. Log in as the WebSphere Portal Server administrator. 3. From the WebSphere Portal Server welcome page, click Administration, found at the bottom of the user interface. 4. From the WebSphere Portal Administration page, click Web Modules, found under the Portlet Management heading of the navigation pane. 5. From the Manage Web Modules page, you see a table listing all of the web modules that have been installed on the server. Click Install to install a new module. 6. From the Select War File page, using the Browse button, locate the Tivoli Asset Management for IT WAR file you intend to deploy. War files will be located on the Tivoli Asset Management for IT Administrative system. Once you have located the intended War file, click Next. In this example, we are deploying the War file maximo.war. 7. From the War file content summary page, review the War file contents, and then click Finish. If the deployment is successful, you will be returned to the Manage Web Modules page. A message will be displayed confirming that the War file was correctly deployed. For each War file you deploy, you will need to edit its maximointegration .properties file. This file is found in the deployment directory created after the deployment of each War, under the WEB-INF directory. 8. Open the appropriate maximointegration.properties file in a text editor, and edit the following properties: maximo_host_name Ensure this value is the same as the host name used to access the Maximo servlet on WebSphere Application Server. maximo_port Ensure this value is the same as the port used to access the Maximo servlet on WebSphere Application Server. maximo_url_protocol This value defaults to http, but you should change it to https in order to access a secure environment. The process of editing the maximointegration.properties file will have to be repeated for every War file you deploy in WebSphere Portal Server. The next step is to create a new page and place a portlet for the Tivoli Asset Management for IT application on a new portal page. 9. Click Administration, found at the bottom of the user interface. 10. Click Manage Pages, found under the Portal User Interface heading of the navigation pane. 11. From the Manage Pages page, click the Context Root entry found in the My Pages table. 12. Click New Label.

66

Installation Guide for IBM WebSphere Application Server:

13. Enter Tivoli Asset Management for IT 7.1 in the Title field of the Page Properties window, and then click OK. A new label titled Tivoli Asset Management for IT 7.1 will be created and displayed in the Pages in Context Root table. 14. From the Pages in Context Root table of the Manage Pages page, click Tivoli Asset Management for IT 7.1. 15. Click New Page. 16. In the Title field of the Page Properties window enter a title that identifies the Tivoli Asset Management for IT application, and then click OK. We are creating a page for the Tivoli Asset Management for IT Change application. 17. Click the Edit Page Layout icon located to the right of the new entry in the Pages in Tivoli Asset Management for IT 7.1 table. 18. From the Edit Layout page, click Add Porlets. 19. Use the search feature of this page to locate the appropriate portlet, select it in the table, and then click OK. 20. From the Edit Layout page, click Done. You can now launch the portlet from the WebSphere Portal Server Launch menu.

Chapter 4. Tivoli Asset Management for IT middleware installation

67

68

Installation Guide for IBM WebSphere Application Server:

This deployment option does not require you to spread the Tivoli Asset Management for IT deployment across several systems. All middleware used in conjunction with Tivoli Asset Management for IT must have been installed on the system using the Tivoli middleware installer using default values. The Tivoli Asset Management for IT installation program records choices you make about your Tivoli Asset Management for IT deployment and configuration parameters associated with those choices. There are two installation paths available to you when installing Tivoli Asset Management for IT. You will not have the option of using existing middleware within your organization with Tivoli Asset Management for IT. entries in LDIF files. Deploying through the custom installation path also allows you to modify default installation values.Chapter 5. some of which probably already host middleware products that you wish to use with your Tivoli Asset Management for IT deployment. 2008 69 . Important: When entering LDAP values for Tivoli Asset Management for IT installation panel fields. Tivoli Asset Management for IT installation program overview The Tivoli Asset Management for IT installation program provides an interface for installing and deploying Tivoli Asset Management for IT. the Tivoli Asset Management for IT installation program must be run from a Windows system. While you can deploy Tivoli Asset Management for IT in a distributed environment consisting of predominately UNIX systems. The Tivoli Asset Management for IT installation program can automate the configuration of middleware for use with Tivoli Asset Management for IT. If you choose not to have the Tivoli Asset Management for IT installation program automatically configure middleware. and then installs and deploys Tivoli Asset Management for IT based upon the information you entered. 2007. In most cases. For a list of values being set when using this option. in order © Copyright IBM Corp. be aware of the product-specific syntax rules for using special characters in an LDAP string. If you intend to override default values used by the simple deployment path. refer to “Tivoli Asset Management for IT simple install path values” on page 70. Custom A custom deployment typically involves deploying Tivoli Asset Management for IT across several systems. configure that piece of middleware manually prior to the installation of Tivoli Asset Management for IT. you will have to use the custom deployment path instead. You can enter the name of the local host as the destination for all Tivoli Asset Management for IT components that are to be installed using the Tivoli middleware installer and the Tivoli Asset Management for IT installation program. Simple A simple deployment consists of installing all middleware on one system. Tivoli Asset Management for IT will be installed using default values provided by the Tivoli middleware and Tivoli Asset Management for IT installation programs. or values you enter directly into a directory instance using the directory server tools.

you will encounter Tivoli Asset Management for IT errors that are difficult to troubleshoot. for example. if you cancel the installation program after entering values across several installation panels. at the end of a field value. Failing to escape special characters contained in an LDAP string used with Tivoli Asset Management for IT result in Tivoli Asset Management for IT errors. You will be able to provide values where indicated. Tivoli Asset Management for IT simple install path values If you elect to install Tivoli Asset Management for IT using the simple install path.to make them readable by the directory server. Refer to the product documentation for your directory server for more information on special characters in LDAP strings. Many directory server products consider a blank space as a special character that is part of the LDAP string.properties. special characters must be preceded by an escape character. Therefore. the following values are set. Therefore. These values are populated into the panel fields of the Tivoli Asset Management for IT installation program on subsequent uses of the program . Table 18. if you mistakenly enter an LDAP string that contains a blank. the installation program will recall the values the next time you start up the Tivoli Asset Management for IT installation program (except for the Tivoli Asset Management for IT install directory and the shortcut option chosen). and you do not precede the blank character with an escape character. Information that you input into the Tivoli Asset Management for IT installation program is stored in the maximo.properties file and the Maximo database. You can restore the default values in the Tivoli Asset Management for IT installation program by deleting <TAMIT_HOME>/maximo/applications/maximo/ properties/maximo. Tivoli Asset Management for IT Simple Install Path Values Category Deployment Option Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration Field Deployment Database Type Host name Port Database Name Instance User ID Automate Database Configuration Remote Access User ID yes Yes 50005 maxdb71 ctginst1 Yes Value simple DB2 Yes Provided by User? 70 Installation Guide for IBM WebSphere Application Server: .

1 Yes Provided by User? Windows db2admin UNIX ctginst1 Database Configuration Database Configuration Database Configuration Database Configuration Database Configuration WebSphere Connectivity WebSphere Connectivity WebSphere Configuration db2admin Data tablespace name maxdata Data tablespace size medium Temporary tablespace maxtemp name Temporary tablespace 1000 size Host name SOAP Port WebSphere server home directory 8879 Yes Windows C:\Program Files\IBM\ WebSphere\ AppServer Linux /opt/IBM/ WebSphere/ AppServer /usr/IBM/ WebSphere/ AppServer AIX Sun Solaris /opt/IBM/ WebSphere/ AppServer WebSphere Configuration WebSphere Configuration WebSphere Configuration WebSphere Configuration User name Profile name wasadmin ctgDmgr01 Yes Automate WebSphere yes Configuration Remote Access User ID Yes Chapter 5.Table 18. Tivoli Asset Management for IT Simple Install Path Values (continued) Category Database Configuration Field Database Install Directory Value Windows C:\Program Files\IBM\ SQLLIB UNIX Database Configuration Instance Administrator User ID Windows Service User ID /opt/IBM/ db2/V9. Tivoli Asset Management for IT installation program overview 71 .

the Tivoli Asset Management for IT installation program can configure existing instances of prerequisite products. Tivoli Asset Management for IT Simple Install Path Values (continued) Category WebSphere Application Server Configuration WebSphere Application Server Configuration WebSphere Application Server Configuration WebSphere Application Server Configuration WebSphere Application Server Configuration Integration Adapter JMS Configuration Integration Adapter JMS Configuration Security Configuration Security Configuration Maximo Configuration Configuration Step Field Web server port Value 80 Provided by User? Web server name webserver1 Node name ctgNode01 Cluster name MAXIMOCLUSTER Application server MXServer This value cannot be changed. meajmsds JMS DataSource name Persist JMS messages no Use Default Schema Create Users automatically Install directory Run Configuration Now yes yes C:\IBM\SMP yes Yes Installing Tivoli Asset Management for IT This procedure explains how to use the Tivoli Asset Management for IT installation program to install Tivoli Asset Management for IT. including those from other vendors. a dialog box detailing the error appear. that you want to use with Tivoli Asset Management for IT. You will not be permitted to continue in the Tivoli Asset Management for IT installation task until the errors are resolved. The instructions provided are for a multiple machine installation using default values and assume that you choose to have the Tivoli Asset Management for IT installation program automatically configure middleware across multiple machines to work with Tivoli Asset Management for IT. In addition to configuring new instances of Tivoli Asset Management for IT middleware products installed by the Tivoli middleware installer.Table 18. If any errors are encountered. If you do not allow the Tivoli Asset Management for IT installation program to configure middleware automatically. it still performs programmatic checks to verify that the documented manual steps were performed properly. 72 Installation Guide for IBM WebSphere Application Server: .

you might encounter ever increasing system memory usage linked with DB2. – For UNIX systems. refer to the DB2 product documentation. ensure you have addressed the following prerequisite conditions: v For Linux systems. Tivoli Asset Management for IT installation program overview 73 . rexec. For example if you plan to create the Maximo database in a DB2 instance (ctginst1 is recommended). It must have SYSADM authority. add root to the DB2GRP1 group prior to starting the Tivoli Asset Management for IT installation program. For more information about creating this user. ensure that one of these protocols is running and accepting remote logins using a user name and password configured on the target machine. For example. and you want to use the fully automated database configuration capabilities of the Tivoli Asset Management for IT installation program. the fenced user must be db2fenc1. create the instance user on the DB2 server before starting the Tivoli Asset Management for IT installation program. and Windows SMB. ensure that the following conditions are met: Chapter 5. For more information about creating this user. and schema. v If you are using DB2 with Tivoli Asset Management for IT. the user must belong to the DB2ADMNS group. consult the appropriate documentation for your operating system to ensure that the hostname command returns a fully qualified host name. This requires the ID to be a member of the group defined by the sysadm_group configuration parameter for the DB2 instance you plan to use. It is used to create the DB2 instance. as defined by DB2. refer to the DB2 product documentation. create a user (including the home directory for the user) on the UNIX DB2 server prior to starting the install. If you experience this behavior. which includes rsh. enable a Remote Execution and Access (RXA) service for each system on which you intend to install Tivoli Asset Management for IT middleware. on Windows.The Tivoli Asset Management for IT installation program can only be run from a Windows-based system. RXA requires that the target system enable at least one of the protocols supported by RXA. – The user ID specified as the Instance administrator user ID that you enter on the DB2 Administration panel of the Tivoli Asset Management for IT installation program must have DB2 administration authority. Before you begin. database. – The user ID specified on the Remote Access Authorization panel of the Tivoli Asset Management for IT installation program must have DB2 administration authority. If it does not. ensure that the command hostname -f returns a fully qualified host name. which is referred to as SYSADM authority in the DB2 product documentation. set the following DB2 property and then restart the DB2 server: db2 update dbm cfg using KEEPFENCED NO v If you are using Oracle with Tivoli Asset Management for IT. v For all DB2 installations. ensure that the following conditions are met: – For DB2 UNIX installations. Before you start the Tivoli Asset Management for IT installation program. Default installations of AIX systems might not include a suitable protocol and must have RXA compatible protocols enabled. configure RXA to work over SMB. v The middleware environment is installed and running properly. v If you plan to take advantage of the Tivoli Asset Management for IT installation program feature that automates the configuration of Tivoli Asset Management for IT middleware. – For UNIX systems. SSH. If the remote system is a Windows machine.

and run the following command: launchpad. click Install the Product.exe. By default. From the Import Middleware Configuration Information panel. v If you are using MS SQL Server 2005 with Tivoli Asset Management for IT. click Next. ensure the users and groups listed in “Manually configuring Microsoft Active Directory” on page 102 have been manually created in the Microsoft Active Directory instance. v For IBM WebSphere Network Deployment. a. this port is not enabled.microsoft. Avoid using localhost for host name values in the install program. Start the launchpad: v On the DVD titled “Tivoli Asset Management for IT V7. Specify the actual fully qualified host name of the system for all host name values.1”. ensure that the following conditions are met: – Ensure the MS SQL Server 2005 service pack 2 is installed. The middleware default information will not be used if you select the Simple deployment path. Enable this port. Note that if you select this feature while installing Tivoli Asset Management for IT by way of RXA.– Ensure the Oracle 10gR2 patch 3 is installed. 4. Refer to http://msdn. Select a language for the installation and click OK. specify that you want to use field values you input into the Tivoli middleware installer as default values for those same fields in the Tivoli Asset Management for IT installation program. Import Middleware Configuration Information Select this check box if you want to allow the Tivoli Asset Management for IT installation program to reuse values entered for DB2 in the Tivoli middleware installer. In the launchpad navigation pane. b. Click Tivoli Asset Management for IT. User ID Enter the User ID that was used to run the Tivoli middleware installer. From the Introduction panel. 5. It must reside locally on the remote system.aspx for instructions. Launch the Tivoli Asset Management for IT installation program from the launchpad. follow these steps: 1. v If you are using Microsoft Active Directory to secure WebSphere. To install Tivoli Asset Management for IT.com/en-us/library/ms177440. 74 Installation Guide for IBM WebSphere Application Server: . Host name Enter the fully qualified host name of the system where the Tivoli middleware installer was run. navigate to the root directory of the product disc or the downloaded installation image. ensure that the following task is complete: – Ensure that the Cell and all related nodes are actively running. – Tivoli Asset Management for IT uses port 1433 when configured with SQL Server. c. 2. Login as Administrator on the Tivoli Asset Management for IT administrative system. the Workspace Location that you specify cannot be located on a networked drive of the remote system. 3.

Tivoli Asset Management for IT installation program overview 75 . The default is 50005 Database name Enter the name of the database to use with Maximo. This deployment option is typically only used for demonstration. From the Choose Install Folder panel. select the Custom deployment topology. and then click Next. C:\ibm\tivoli\mwi\ workspace. The path you specify must not contain spaces. From the Maximo Database panel. Oracle Select this choice to use Oracle as the Maximo database. enter configuration information about the database. By default. Where Would You Like to Install? Enter the path to install Tivoli Asset Management for IT. or training purposes. For example. Custom Select custom if you want to deploy Tivoli Asset Management for IT components across several systems. DB2 Host name Enter the host name of the machine hosting DB2. SQL Server Select this choice to use MS SQL Server 2005 as the Maximo database. and then click Next. This file is found in the workspace that was defined during the Tivoli Asset Management for IT middleware installation task. 6. From the Choose Deployment panel. 7. 9. Each database will have its own unique set of configurable parameters and values. This deployment option is typically used in a production environment. and then click Next. and then click Next. proof-of-concept. The default database name is maxdb71.Password Enter the password of the User ID that was used to run the Tivoli middleware installer. Port Enter the port being used by DB2 instance. 8. Chapter 5. Workspace Location Enter the location of the topology file that contains the values entered for the Tivoli middleware installer. specify the directory you use to install Tivoli Asset Management for IT. The database is created if it does not exist. The host name must be fully qualified. From the Maximo Database Type panel. select the product that you use for the Maximo database. this value is C:\IBM\SMP. Simple Select simple if you want to deploy all Tivoli Asset Management for IT components on a single system. DB2 Select this choice to use IBM DB2 UDB as the Maximo database.

the user and its associated home directory must exist on the DB2 server. Database user ID Enter the user ID used for Maximo to access DB2. Default for all platforms is maximo. This user ID cannot be the same one used as the instance administrator user ID. Database user ID Enter the user ID used to access SQL Server.Instance Enter the name of the database instance to be used with Maximo. SQL Server Host name Enter the host name of the machine hosting SQL Server. The default is 1521 Instance Enter the name of the database instance to be used with Maximo. The host name must be fully qualified. 76 Installation Guide for IBM WebSphere Application Server: . Port Enter the port being used by SQL Server. Database password Enter the password for the user ID used to access Oracle. Oracle Host name Enter the host name of the machine hosting Oracle. The default database name is maxdb71. however. The default instance name is ctginst1. This user ID is created if it does not exist. Database password Enter the password for the user ID used to access DB2. Database user ID Enter the user ID used for Maximo to access Oracle. This user ID is created if it does not exist. This instance is created if it does not exist. The host name must be fully qualified. Port Enter the port being used by Oracle. Default for all platforms is maximo. The default is 1433 Database Name Enter the name of the database to use with Maximo. The default instance name is ctginst1. Default for all platforms is maximo.

this value might be db2admin. enter configuration information about the database. From the Database Administration panel.1 Instance administrator user ID Enter the administrator user ID for the DB2 instance. you must configure a database manually prior to the installation of Tivoli Asset Management for IT. this user must be a member of the DB2ADMNS group (Windows) or the db2grp1 group (UNIX). From the Remote Access Authorization panel. Examples of automated tasks include creating tablespaces. Refer to “Enabling remote configuration” on page 21 for details about how to ensure successful remote access between the Tivoli Asset Management for IT installation program and the remote server. the installation will verify that you have not completed these pre-install tasks and you will receive errors. Chapter 5. and then click Next. If you’re using DB2 for the Maximo database. and then click Next. 11. From the Automate Database Configuration panel. this value might be C:\Program Files\IBM\SQLLIB Linux On Linux. 12. Windows On Windows. Windows On Windows. creating database schemas. Password Enter the password for the user ID. DB2 Installation directory Enter the directory where DB2 is installed. 10. select Automate database configuration. Tivoli Asset Management for IT installation program overview 77 . and then click Next. Database password Enter the password for the user ID used to access SQL Server. If you choose not to have the Tivoli Asset Management for IT installation program automatically configure the database. creating database tables. enter authorization information for the automatic database configuration feature. This step allows the Tivoli Asset Management for IT installation program to configure the database automatically for use by Tivoli Asset Management for IT.This user ID is created if it does not exist. creating users. If you do not elect to automate the database configuration and you have not manually configured the database prior to selecting Do not automate database configuration from within the Tivoli Asset Management for IT installation program. and so on. This user ID must have administrative rights on the machine you are accessing. User ID Enter a valid user ID that gives the Tivoli Asset Management for IT installation program access to the system that is hosting the database to be used with Tivoli Asset Management for IT. this value might be /opt/IBM/db2/V9. this value might be /opt/IBM/db2/V9.1 AIX On AIX. Complete these manual tasks prior to restarting the Tivoli Asset Management for IT installation program.

2. The default is db2admin. the default is sys. Oracle Software Owner ID Enter the user ID of the user that was used to install Oracle. this value might be C:\oracle\product\10. Windows service user ID Enter the user ID used to start the DB2 service on Windows. Windows On Windows. this value might be /opt/app/oracle/ product/10. For all platforms. this value might be /opt/app/oracle/ product/10.0/oradata AIX On AIX.2. SQL Server SQL Server administrator Enter the administrator user ID for MS SQL Server. this value might be ctginst1 This user ID cannot be the same one as is as the database user ID. Windows service password Enter the password for the user ID used to start the DB2 service on Windows. this value might be /opt/app/oracle/product/10. SQL Server administrator password Enter the password for the administrator user ID for MS SQL Server.0/oradata Sun Solaris On Sun Solaris. For all platforms. Instance administrator password Enter the password for the DB2 instance administrator user ID. AIX: On AIX. Default is sa. Oracle Installation directory Enter the directory where Oracle is installed. 78 Installation Guide for IBM WebSphere Application Server: .Linux On Linux. this value might be ctginst1. Administrator Password Enter the password for the administrator user ID for Oracle.2. This user ID must have administrative authority on the system.0/oradata Administrator User ID Enter the administrator user ID for Oracle.2. the default is oracle Oracle Owner Password Enter the password for the user ID of the user that was used to install Oracle.0\oradata Linux On Linux.

the default is MAXDATA.0\oradata\dbs Chapter 5. Oracle Instance Location Enter the path where the database instance is loaded. For all platforms. Data tablespace size Enter a size for the tablespace by selecting one of the following values: v small (3000Mb) Select this size if supporting between 1-20 users v medium (5000Mb) Select this size if supporting between 20-100 users v large (8000Mb) Select this size if supporting 100+ users Tablespace size is measured in Mb.2. For all platforms. it is created. Temporary tablespace size Enter a size for the temporary tablespace. Temporary tablespace name Enter the name for the temporary tablespace to be created for DB2. and then click Next. Windows On Windows. Default value is maxdb71_dat Data file initial size Select the initial size of the MS SQL Server data file. Default is maxdb71_log 13. Tivoli Asset Management for IT installation program overview 79 . enter information about the tablespace of the database. If the tablespace does not exist. Temporary tablespace size is measured in Mb. From the Database Tablespace panel. this value might be C:\oracle\product\10. Default is set to Medium (1000 MB) Log file name Enter the name for the MS SQL Server log file. DB2 Data tablespace name Enter the name of the tablespace that will be created in DB2 for Maximo. This value must be set to 1000Mb. it is created.Data file name Enter the name of the MS SQL Server data file. the default is MAXTEMP. If the tablespace does not exist. Temporary tablespaces hold data during sorting or collating actions.

14. enter host information about the WebSphere server. From the WebSphere Connectivity panel.0/oradata Tablespace name Enter the name of the tablespace that is created in Oracle for Maximo. this value might be /opt/app/oracle/product/10.2. Temporary tablespace name Enter the name for the temporary tablespace to be created for Oracle. For all platforms.Linux On Linux. and then click Next. 80 Installation Guide for IBM WebSphere Application Server: .2. you can provide the IP address for the system. Temporary tablespace size is measured in Mb.0/oradata AIX On AIX. 15. SOAP port Enter the SOAP port of the WebSphere system. the default is 100Mb. select IBM WebSphere Application Server. For all platforms. the default is maxdata Tablespace Size Enter a size for the tablespace by selecting one of the following values: v small (500Mb) Select this size if supporting between 1-2 users v medium (1000Mb) Select this size if supporting between 20-100 users v large (5000Mb) Select this size if supporting 100+ users Tablespace size is measured in Mb. Temporary tablespaces hold data during sorting or collating actions. The Tivoli Asset Management for IT installation program now connects to the database server and validate all of the information you have entered. the default is maxtemp Temporary tablespace size Enter a size for the temporary tablespace. this value might be /opt/app/oracle/ product/10. From the Maximo Application Server Type panel. The default value for this field is 8879.0/oradata Sun Solaris On Sun Solaris. Host name Enter the fully qualified host name of the system hosting WebSphere. this value might be /opt/app/oracle/ product/10.2. For all platforms. Alternatively. which will be used for sort operations.

Password Enter the password for the administrative user ID used to access the WebSphere server. this value might be C:\Program Files\IBM\WebSphere\AppServer Linux On Linux. select Automate WebSphere configuration. and then click Next. Web server port Enter the Web server port used by WebSphere. This user ID must have administrative rights on the machine you are accessing. From the Automate WebSphere Configuration panel. copying the WebSphere keystore file from the machine where WebSphere is installed to the administrative workstation. 19. Chapter 5. and then click Next. This allows the Tivoli Asset Management for IT installation program to configure WebSphere automatically for use by Tivoli Asset Management for IT. 17. WebSphere installation directory Enter the directory where WebSphere is installed on the host system. If you choose not to have the Tivoli Asset Management for IT installation program automatically configure WebSphere. and so on. and then click Next. you will have to configure WebSphere manually prior to the installation of Tivoli Asset Management for IT. this value might be /usr/IBM/WebSphere/ AppServer Sun Solaris On Sun Solaris. enter the following information. Configuration tasks include creating a profile. From the WebSphere Application Server Configuration panel. enter values for the following fields. this value might be /opt/IBM/WebSphere/ AppServer AIX On AIX. Tivoli Asset Management for IT installation program overview 81 . running WebSphere as a Windows service. Operating system password Enter the password for the system user ID. 18. From the WebSphere Deployment Manager configuration panel.16. Operating system user ID Enter a valid user ID that gives the Tivoli Asset Management for IT installation program access to the system that is hosting WebSphere. Default for all platforms is ctgDmgr01. Default for all platforms is wasadmin. this value might be /opt/IBM/WebSphere/ AppServer User ID Enter the administrative user ID used to access the WebSphere server. setting up JMS queues. enter authorization information for WebSphere configuration. Profile name Enter the name of the WebSphere profile. Windows On Windows. and then click Next. From the WebSphere Remote Access Authorization panel.

The next several steps of this Tivoli Asset Management for IT installation procedure assume you are allowing the Tivoli Asset Management for IT installation program to configure the JMS implementation to persist messages. Enter the name of the database to be used by JMS. If you later decide that you would like to persist JMS messages. indicate whether application server security should be enabled automatically. Default for all platforms is MAXIMOCLUSTER. 21. 20. From the DB2 Database Server Configuration panel. Cluster name Enter the name of the WebSphere cluster containing the application server. Note: The JMS DataStore can only be created as a DB2 database. you will have to configure the JMS implementation manually. Default for all platforms is ctgNode01. enter the following information. The cluster and application server will be created if they do not exist. 82 Installation Guide for IBM WebSphere Application Server: . From the Security panel. Default for all platforms is webserver1 Node name Enter the name of the WebSphere node containing the application server. enter the following information. Port Enter the port used to access the database server. Do not persist JMS messages Select this option if you do not want the Tivoli Asset Management for IT installation program to set the JMS implementation to persist messages automatically. A database will not be used to persist messages. The cluster name is optional. and then click Next. and then click Next. Default is intjmsds. 22. Select whether the JMS datastore should be persisted.Default for all platforms is 80 Web server name Enter the name of the Web server. and then click Next. From the Integration Adapter JMS Configuration panel. JMS DataSource name A JMS server requires a DB2 data repository to be configured to maintain messages. Persist JMS messages Select this option of you want the Tivoli Asset Management for IT installation program to set the JMS implementation to persist messages. Default for all platforms is 50005. Host name Enter the fully qualified host name of the server hosting the JMS datastore.

Linux On UNIX. and then click Next. and then click Next. If the user does not exist. Windows On Windows. Password Enter the password for the User ID used to access the database server. For all platforms. it will be created for you. User ID Enter a valid user ID that will allow the Tivoli Asset Management for IT installation program to access the system that is hosting the JMS database. From the Maximo panel. this value might be C:\Program Files\IBM\SQLLIB Linux On Linux. This user ID should have administrative rights on the machine you are accessing. enter the following configuration information. Default for all platforms is the database user ID you entered when you selected your database type.Database name Enter the name of the database serving as the JMS datastore. From the DB2 Database Server Remote Access Authorization panel. the default is ctginst1 Instance administrator user ID Enter the administrator’s user ID for the JMS database instance. this user must be a member of the DB2ADMNS group. User ID Enter the user ID used to access the database server. Chapter 5. 23. this value might be db2admin. and then click Next. 24. 25. Tivoli Asset Management for IT installation program overview 83 . this user must be a member of the db2grp1 group Password Enter the password for the user ID. this value might be ctginst1. From the DB2 Database Instance Configuration panel. Installation directory Enter the installation directory for the DB2 server that is hosting the JMS database that contains the instance to be used with WebSphere. this value might be /opt/IBM/db2/V9. enter the following information. Windows On Windows.1 Instance Enter the JMS database instance to be used with WebSphere. enter authorization information for the automatic configuration feature. For Unix. Default for all platforms is maxsibdb. For Windows. Instance administrator password Enter the password for the JMS database instance administrator’s user ID.

Installation directory Select the folder where Maximo will be installed. C:\IBM\maximo is the default value. The path you specify must not contain spaces. SMTP server Enter the mail server configured to work with Tivoli Asset Management for IT. This server will be used to send workflow and process notifications. This field is optional. Workflow administrator e-mail Enter the E-mail address of the person assigned to the role of Tivoli Asset Management for IT Workflow Administrator. This address will be used for workflow notifications. This field is optional. Administrator e-mail Enter the E-mail address of the person assigned to the role of Tivoli Asset Management for IT Administrator This field is optional. If you choose to not configure optional properties at this time, you can configure them in the Tivoli Asset Management for IT user interface using the System Properties application. The relevant properties are: v mail.smtp.host v mxe.workflow.admin v mxe.adminEmail 26. From the Run Configuration Step panel, select when you would like to configure Tivoli Asset Management for IT, and then click Next. Run the configuration step now Tivoli Asset Management for IT will be configured when you select this option and press Next. Do not run the configuration step now You will have to configure Tivoli Asset Management for IT after you have completed the Tivoli Asset Management for IT installation task. The Tivoli Asset Management for IT installation program is used to complete three tasks: gathering information about your Tivoli Asset Management for IT deployment and configuration, copying files to your local system, and performing configuration tasks using the values you have specified. By selecting Do not run the configuration steps now, you can instruct the Tivoli Asset Management for IT installation program to gather your configuration information and copy Tivoli Asset Management for IT files to your local system now, and then allow you to run the configuration step at a later date. The configuration values that you enter are stored in the <Maximo_Home>\applications\maximo\properties\ maximo.properties file. You can execute the configuration steps outside of the Tivoli Asset Management for IT installation program by using the taskrunner utility, located in the <TAMIT_HOME>\scripts directory. Simply run the taskrunner utility from the command line, and it will use the configuration values stored in the maximo.properties file to configure Tivoli Asset Management for IT.

84

Installation Guide for IBM WebSphere Application Server:

<TAMIT_HOME>\scripts\taskrunner

If there is an installation failure, the taskrunner utility can be run again after the error conditions have been rectified. The taskrunner utility will resume the install at the point where the last successfully completed task was recorded in the previous attempt. 27. From the Choose Shortcut Folder panel, select the type of shortcut you would like to arrange for Tivoli Asset Management for IT, and then click Next. In a new Program Group Select this option and enter the name of a new program group if you would like to create Tivoli Asset Management for IT shortcuts in a new program group. In an existing Program Group Select this option and choose the name of an existing program group to store Tivoli Asset Management for IT shortcuts. In the Start Menu Select this option to create shortcuts for Tivoli Asset Management for IT in the Start menu. In order to use the Start Menu shortcut in conjunction with Internet Explorer, ensure that you have added the Tivoli Asset Management for IT URL to the trusted sites Web content zone and disable the option of requiring server verification for all sites in the zone. On the Desktop Select this option to create shortcuts for Tivoli Asset Management for IT on the desktop. In the Quick Launch Bar Do not select this option. Selecting this option does not create a shortcut in the Quick Launch bar. Other Select this option and use the Choose... button to select another location to create Tivoli Asset Management for IT shortcuts. Don’t create icons Select this option if you do not want any Tivoli Asset Management for IT shortcuts created. Create Icons for All Users Select this option if you would like Tivoli Asset Management for IT desktop icons to appear on the desktop for all system users. 28. From the Input Summary panel, review the information you have provided to the Tivoli Asset Management for IT installation program, and then click Next. Use the Previous button to return to previous panels to change anything. 29. From the Pre-Installation Summary panel, review the installation information presented, and then click Install. The installation now begins. Progress can be monitored by viewing messages displayed above the progress bar. 30. From the Install Complete panel, click Done. Once the Tivoli Asset Management for IT installation program has completed installation and configuration tasks, it exits. Logs can be found at <TAMIT_Home>/logs.

Chapter 5. Tivoli Asset Management for IT installation program overview

85

Tivoli Asset Management for IT installation with manual middleware configuration
You can elect to have your database server configured automatically by the Tivoli Asset Management for IT installation program. Alternatively, you can choose to configure your database server manually to work with Tivoli Asset Management for IT. All other middleware components, that is, the directory server and the J2EE server, must be configured manually to work with Tivoli Asset Management for IT prior to using the Tivoli Asset Management for IT installation program. The information contained in this section provides details on how to manually configure Tivoli Asset Management for IT middleware prior to running the Tivoli Asset Management for IT installation program. Also included in this section is a procedure describing how to advance through the Tivoli Asset Management for IT installation program to complete the Tivoli Asset Management for IT deployment. Before you begin, ensure you have addressed the following prerequisite conditions: v You have designated a Windows-based machine that will be used to launch the Tivoli Asset Management for IT installation program. v All of your middleware is at the level described in “Tivoli Asset Management for IT component requirements” on page 3.

Manually configuring the database server
If you choose to not have the Tivoli Asset Management for IT installation program automatically configure the database server, you must complete the manual configuration before you use the Tivoli Asset Management for IT installation program . For DB2 on UNIX systems, ensure you have a minimum of 8 GB (binary) free of space in the DB2 database instance home directory (/home/ctginst1) in order to meet the default tablespace disk space requirements of the DB2 install. For DB2 on Windows, ensure you have a minimum of 8 GB of free space in the DB2 installation directory.

Manually configuring DB2 9.1
To configure an existing DB2 9.1 server for use with Tivoli Asset Management for IT, complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. Create system users. a. Log into the system as a user that has administrative permissions on the system. b. DB2 requires user accounts that are operating system user accounts. Create operating system users named ctginst1 and maximo, using user management tools available on the system. For AIX, use SMIT to add the users. For the ctginst1 user, assign the primary group as db2grp1 and secondary groups of staff and dasadm1. For the maximo user, it is not necessary to assign a specific group. After the user IDs have been created, log into the system using the user IDs and change the password for each account. 2. Create the DB2 instance: a. Use the following command to create the DB2 instance:

86

Installation Guide for IBM WebSphere Application Server:

and then click Next. if you do not want to use the database path as the storage path. select Yes.Windows db2icrt -s ese -u db2admin. Create a database a. From the Specify a name for your new database panel. and then select Create Database? With Automatic Maintenance. This creates a Unicode database with a code set of UTF-8. Alternatively. If you specify a path. Chapter 5. Click Next. c. From the DB2 Control Center. specify a different directory. Open up the DB2 Control Center for the instance you plan to use: Windows 1) Open a command window. f. d. e. Set the listening port for the instance Windows db2 update dbm cfg using svcename 50005 c. From the Select your maintenance strategy panel. I can specify an offline maintenance window of at least an hour when the database is inaccessible. g. 2) Source the instance you plan to use. Enable the Enable database for XML option. enter maxdb71 for both the Database name and Alias fields. From the Specify where to store your data panel. right-click the Databases folder located below the instance name. 2) Type the following command: set DB2INSTANCE=ctginst1 db2set DB2COMM=tcpip 3) Type the following command: db2cc UNIX 1) Open a command window.50005 ctginst1 Linux db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 ctginst1 AIX db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 -w 64 ctginst1 b. click Next. Start the ctginst1 database instance: Windows db2start UNIX su .<pwd> -r 50005. Tivoli Asset Management for IT installation program overview 87 . the directory must exist.ctginst1 db2start 3. Set instance service to start automatically Windows sc config ctginst1-0 start= auto d. 3) Type the following command: db2cc b.

j. enter the name of the SMTP server that is used to communicate DB2 messages concerning this database.3 systems.. m. Enter 4. select the LOCKLIST value and click the button labeled with the ellipsis (. From the Database Configuration panel. review the choices you have made. Enter 1024. and then click Next. Enter 1024. click OK. and click Grant All. and then click OK. From the Database Configuration panel. click Add User. Configure the database. b.. Highlight the user. The database is then created. c. right-click it and select Authorities. 6. i. su to ctginst1 and use the following command: db2 create database maxdb71 using codeset UTF-8 territory us pagesize 32 K 4. and then click OK. a.3 systems is to configure it remotely from a system that can run the DB2 Control Center. select the LOGFILSIZ value and click the button labeled with the ellipsis (. l. j..) in the Value column. and then click OK. Click OK.) in the Value column. c. k. and then click Finish. g.. The best way to configure the database on AIX 5. use the following command to create the DB2 instance. Enter 4096. d. For AIX 5.. a. e.. and then click OK.. From the Specify when offline automatic maintenance activities can run. provide scheduling details for offline maintenance. From the Database Configuration panel. From the User tab of the Database Authorities window. From the Database Configuration panel. From the Database Configuration panel. using the DB2 client. maximo. Create tablespace. select the APPLHEAPSZ value and click the button labeled with the ellipsis (. in the Database Authorities window. and then click Next. select the APP_CTL_HEAP_SZ value and click the button labeled with the ellipsis (. and then click OK. Click Close.h. From the Provide a valid SMTP server panel.) in the Value column. select the user maximo. From the Add User dialog. n. you cannot launch the DB2 Control Center locally. 88 Installation Guide for IBM WebSphere Application Server: . and choose Configure Parameters. f.3 systems. b. h.) in the Value column. Enter 30000. d. db2icrt –a SERVER –s ese –p 50005 –u db2fenc1 ctginst1 To create the database on AIX systems. and then click OK. Restart the database by right-clicking the ctginst1 instance. and then clicking Start. Once the database has restarted. i. select the LOGSECOND value and click the button labeled with the ellipsis (. Add users to the database. clicking Stop.) in the Value column. From the Review the actions that will take place when you click Finish panel. e.. For AIX 5. Right-click the maxdb71 database created in the previous step. 5.. From the Database Configuration panel..

e. e. d. b. c. f. Select the maximo user and then click Grant all h. Ensure the Create buffer pool immediately choice is selected. and then click Next. Chapter 5. f. From the right-click menu. Click Add User. k. This name must be the same as was used for the Database User ID. and then click Next. select Create. d. 9. From the DB2 Control Center. h. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option. From the Privileges drop-down menu. Specify MAXBUFPOOL as your new buffer pool. a. 8. Select System temporary as the type of tablespace and then click Next. Right-click on the new schema name and select Privileges. g. and leave Extent size as 32. select Create. Create a temporary table space. Highlight the newly created buffer pool and click Next. select No Grant. Tivoli Asset Management for IT installation program overview 89 . and then change the Page size value to 32 and the Size in 32 KB pages value to 4096. From the right-click menu. l. select Create. Select Regular as the type of tablespace and then click Next. and then click Next. Specify MAXDATA as your new tablespace. locate and right-click the Schema entry under the DB2 database that you created for use with Tivoli Asset Management for IT. and then click Next. d. Click Create to create a buffer pool for the tablespace. From the right-click menu. i. From the Specify the extent and prefetch sizes for this table space panel. a. locate and right-click the MAXDATA Table Spaces entry under the DB2 database that you created for use with Tivoli Asset Management for IT. b. From the DB2 Control Center. c. a. g. Click Finish. j. and then click OK. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Tivoli Asset Management for IT. From the Privileges drop-down menus. Select the user maximo. and then click OK. choose the Between 200 MB and 2 GB option. Click OK. select Privileges.a. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Tivoli Asset Management for IT. From the DB2 Control Center. c. e. and then click OK. Grant permissions for the table space. and then click OK. b. c. Create a schema. and then select the maximo user. select Yes. select Add User. and then click Next. From the DB2 Control Center. and then click OK. Specify MAXTEMP for your new tablespace. From the right-click menu. d. Specify a name for your new schema. b. 7. From the dialog box. Define a hard drive specification by choosing Server (SCSI).

assign the primary group as db2grp1 and secondary groups of staff and dasadm1. For the maximo user. After the user IDs have been created. 2. i. b. Also run the db2iupdt command to update the DB2 instance. Create operating system users named ctginst1 and maximo.<pwd> -r 50005. After you have installed the fix pack. Select the previously created bufferpool (MAXBUFPOOL). Install the appropriate fix pack. Refer to the tables presented in “Tivoli Asset Management for IT component requirements” on page 3. Log into the system as a user that has administrative permissions on the system. Define a hard drive specification by choosing Server (SCSI). Click Finish. a.e. use SMIT to add the users. g. and then run the following command: Windows C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1 UNIX <DB2DIR>/instance/db2iupdt ctginst1 Manually configuring DB2 8. and click Next. 10. and then click Next. DB2 requires user accounts that are operating system user accounts. Use the following command to create the DB2 instance: Windows db2icrt -s ese -u db2admin. it is not necessary to assign a specific group. Create system users. Create the DB2 instance: a. Set the listening port for the instance Windows db2 update dbm cfg using svcename 50005 90 Installation Guide for IBM WebSphere Application Server: . For AIX. For the ctginst1 user. h. and leave Extent size as 32. complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. using user management tools available on the system. f. and then click Next. Start by first stopping all processes that are running for the database instance (ctginst1). choose the Between 200 MB and 2 GB option. From the Specify the extent and prefetch sizes for this table space panel.2 server for use with Tivoli Asset Management for IT. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option. and then click Next. run the dasupdt command to update the DB2 Administration Server to the applied fix pack. log into the system using the user IDs and change the password for each account.2 To configure an existing DB2 8.50005 ctginst1 Linux db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 ctginst1 AIX db2icrt -a SERVER -s ese -p 50005 -u db2fenc1 -w 64 ctginst1 b.

) in the Value column.. Enter 4. Start the ctginst1 database instance: Windows db2start UNIX su . d. From the Database Configuration panel. i..ctginst1 b. e. m. Enter 30000. From the Database Configuration panel. Click Close. j. select the APP_CTL_HEAP_SZ value and click the button labeled with the ellipsis (.. From the Database Configuration panel. f. and then click OK. Create the database: Windows a.ctginst1 db2start 3. select the LOCKLIST value and click the button labeled with the ellipsis (. Now type db2cmd to open the DB2 Command Window: c. Open a command window and type the following command: su . Right-click the maxdb71 database and choose Configure Parameters. h. select the LOGSECOND value and click the button labeled with the ellipsis (. From the new instance window issue the following commands: db2start db2 create db maxdb71 using codeset utf-8 territory us pagesize 32 k 4. From the DB2 Control Center. From the new instance window issue the following commands: db2start db2 create db maxdb71 using codeset utf-8 territory us pagesize 32 k UNIX a. n.) in the Value column.. k.) in the Value column. g. navigate to All Systems ? <DB2 server> ? Instances ? CTGINST1 ? Databases ? MAXDB71 c.) in the Value column. l. From the DB2 Command Window. and then click OK. select the LOGFILSIZ value and click the button labeled with the ellipsis (. Open a command window and type the following command: set DB2INSTANCE=ctginst1 b. and then click OK. a.. click OK. and then click OK. Chapter 5. Enter 1024. and then click OK. Set instance service to start automatically Windows sc config ctginst1-0 start= auto d. Tivoli Asset Management for IT installation program overview 91 . From the Database Configuration panel...c. Configure the database.. From the Database Configuration panel. select the APPLHEAPSZ value and click the button labeled with the ellipsis (. Enter 1024. type the following command: db2cc b. From the Database Configuration panel.) in the Value column.. o. Enter 4096..

From the right-click menu. j. Size to 3000Mb. e. o. g. click Add. a. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Tivoli Asset Management for IT. 92 Installation Guide for IBM WebSphere Application Server: . 6. From the Space management panel. Click OK. Select the previously created bufferpool (MAXBUFPOOL). click Add. and then click Next. From the right-click menu. enter /home/ctginst1 as the location of the file. 7. click Add User. From the Containers panel. clicking Stop. Set the Type to File. Restart the database by right-clicking the ctginst1 instance. select the user maximo. and then change the Page size value to 32 and the Size in 32 KB pages value to 4096. and File name to CTGDAT. Once the database has restarted. click Next. and then clicking Start. k. specify Database-managed space. right-click it and select Authorities. Specify MAXDATA as your new tablespace. From the Containers panel. a. and then click Next. d. Specify MAXBUFPOOL as your new buffer pool. From the Summary panel. and File name to CTGTMP. maximo in the Database Authorities window. p. Click OK. Size to 5000 Mb. h. specify Database-managed space and click Next. and click Grant All. From the Specify the extent and prefetch sizes for this table space panel. c. f. and then click Next. b. a. d. Define a hard drive specification by choosing Server (SCSI). select Create. locate and right-click the Table Spaces entry under the DB2 database that you created for use with Tivoli Asset Management for IT. e. From the User tab of the Database Authorities window. Specify MAXTEMP for your new tablespace. Create tablespace. select Create. 5. For UNIX. Select System temporary as the type of tablespace and then click Next. Highlight the user. From the DB2 Control Center. i. Create a temporary table space.p. e. b. h. From the Add User dialog. l. Click Create to create a new buffer pool for the tablespace. Specify the dropped table recovery option for the tablespace by enabling the Enable dropped table recovery option. and then click OK. n. From the DB2 Control Center. f. Select Regular as the type of tablespace and then click Next. d. Set the Type to File. Highlight the newly created buffer pool and click Next. c. and click Next. and then click Next. Ensure the Create buffer pool immediately choice is selected. m. Add users to the database. g. and then click Next. and then click Next. and then click OK. c. From the Space management panel. click Finish. b.

After you have installed a fix pack. l. you will also need to run the db2iupdt command to update the DB2 instance. complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. select Privileges. Click OK. Right-click on the new schema name and select Privileges. select Create. c. This name should be the same as was used for the Database User ID. From the Privileges drop-down menus. Click Add User. and then click Next.For UNIX. select Yes. locate and right-click the MAXDATA Table Spaces entry under the DB2 database that you created for use with Tivoli Asset Management for IT. Tivoli Asset Management for IT installation program overview 93 . a. run the dasupdt command to update the DB2 Administration Server to the applied fix pack. and then run the following command: Windows C:\Program Files\IBM\SQLLIB\BIN\db2iupdt ctginst1 UNIX <DB2DIR>/instance/db2iupdt ctginst1 Manually configuring Oracle 10g If you are using Oracle 10g Rel2. Define a hard drive specification by choosing Server (SCSI). and then click OK. j. ensure the Oracle 10g Rel2 patch 3 is installed To configure an existing Oracle 10g Rel2 or 10g Rel1 server for use with Tivoli Asset Management for IT. From the dialog box. Specify a name for your new schema. e. Select the maximo user and then click Grant all h. c. If you installed a fix pack. From the DB2 Control Center. Select the user maximo. e. and then click OK. click Finish. select No Grant. and then click OK. enter /home/ctginst1 as the location of the file. d. Create a schema. 9. and then select the maximo user. i. Click OK. click Next. g. From the Privileges drop-down menu. From the Summary panel. and then click Next. locate and right-click the Schema entry under the DB2 database that you created for use with Tivoli Asset Management for IT. From the Specify the extent and prefetch sizes for this table space panel. and then click OK. 8. f. Log in as a dba. Refer to the tables presented in “Tivoli Asset Management for IT component requirements” on page 3. Start by first stopping all processes that are running for the database instance (ctginst1). d. Install the appropriate fix pack. b. select Add User. From the DB2 Control Center. such as sys or system. 10. a. From the right-click menu. k. Grant permissions for the table space. Chapter 5. From the right-click menu. b.

Java Pool Set this value to 33554432. g. From the Creation Options panel. s. r. cursor_sharing Change this value to FORCE nls_length_semantics Change this value to CHAR open_cursors Change this value to 1000 From the Initialization Parameters panel. select Custom. From the Database Storage panel. d. and then click Close. Ensure File System is selected as the storage mechanism to use for the database. click Finish. b. and then click Next. and then click Next. Click All Initialization Parameters. Click Show Advanced Parameters. and then click Next. f. a. p. l. Click Next. enter a password for Oracle users.. Leave the defaults selected. j. k.. e. Ensure Use Database File Locations from Template is selected as the value to use for database file location. click Next. From the Memory tab. 94 Installation Guide for IBM WebSphere Application Server: . Select Create a Database. Buffer Cache Set this value to 36000000. q. Shared Memory Management Set this value to Manual. Ensure Use the Same Password for All Accounts is selected. provide the following values (measured in bytes).2. m. t. Leave defaults selected for the database recovery options panel. o. and then click Next. and then click Next. h. and then click Next. click Next. and click Next. Shared Pool Set this value to 157286400. n. Enter ctginst1 for both the Global Database Name value and the SID value. and then click Next. Locate the following parameters. Create a new database for use by Tivoli Asset Management for IT. click OK.. and then click the Character Sets tab. Large Pool Set this value to 8388608. PGA Size Set this value to 37748736. i. click Next. From the Sample Schemas panel. From the Confirmation panel. From the Database Character Set tab. c. select Use Unicode (AL32UTF8). Open the Oracle Database Configuration Assistant. Select General Purpose. change them to the values indicated.

0\oradata\ctginst1\maxtemp. and then click Next. d. 5. complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. grant create procedure to maximo. and click Next. Click Exit to exit the Database Configuration Assistant. Create a tablespace using the following command in SQL*Plus: Create tablespace maxdata datafile ’C:\oracle\product\10.u. grant create synonym to maximo. e. Open the Oracle Database Configuration Assistant.0\oradata\ctginst1\maxdata.0. Log into SQL *Plus using the following information: User Name system Password Password you entered in step 2g. Tivoli Asset Management for IT installation program overview 95 . grant execute on ctxsys. Chapter 5. grant create table to maximo. grant alter session to maximo. ensure Oracle 9. Host String ctginst1 4. Leave the default of Dedicated Server Mode selected. The directory specified in the example should be changed to the location where the database will reside. and then click Next. grant create view to maximo. Create a new database for use by Tivoli Asset Management for IT. Click Next. grant create job to maximo. The directory specified in the example should be changed to the location where the database will reside. and then click Next. Create the maximo user and grant permissions using the following command in SQL*Plus: Create user maximo identified by maximo default tablespace maxdata temporary tablespace maxtemp.2. Select Create a database.ctx_ddl to maximo.2. grant create sequence to maximo. 6.8 is installed To configure an existing Oracle Oracle9i Rel2 server for use with Tivoli Asset Management for IT. grant create trigger to maximo.dbf’ size 1000M autoextend on maxsize unlimited. a. alter user maximo quota unlimited on maxdata. grant create session to maximo. 3. Enter ctginst1 for both the Global Database Name value and the SID value. The database has been successfully created. Select General Purpose.dbf’ size 1000M autoextend on. f. Manually configuring Oracle9i Rel2 If you are using Oracle9i Rel2. c.2. Create a temporary tablespace using the following command in SQL*Plus: Create temporary tablespace maxtemp tempfile ’C:\oracle\product\10. b.

Java Pool Set this value to 32. click OK. and then click OK. select Custom. Create a temporary tablespace using the following command in SQL*Plus: create temporary tablespace maxtemp tempfile ’C:\oracle\oradata\maxtemp\maxtemp. and then click Close. The database has been successfully created. From the Creation Options panel. Click Next. and click Finish. Click Exit to exit the Database Configuration Assistant. select the Create Database option. Create a tablespace using the following command in SQL*Plus: Create tablespace maxdata datafile ’C:\oracle\oradata\maxdata\maxdata. The directory specified in the example should be changed to the location where the database will reside. Unlock the CTXSYS account by removing the check mark in the Lock Account? column for that entry. 3. l. o. Large Pool Set this value to 8. From the Confirmation panel. The directory specified in the example should be changed to the location where the database will reside.dbf’ size 1000M autoextend on maxsize unlimited. PGA Size Set this value to 36. enter the following values (M Bytes). j. Buffer Cache Set this value to 36. i. The database has been successfully created. n. click Next. Shared Pool Set this value to 150. m. From the Memory tab.dbf’ size 1000M autoextend on. Locate the following parameters. From the Database Storage panel. q. p. nls_length_semantics Change this value to CHAR open_cursors Change this value to 1000 k. 2. and then click Next. Create the maximo user and grant permissions using the following command in SQL*Plus: 96 Installation Guide for IBM WebSphere Application Server: . 4. Once the database has been successfully created. Select the Character Sets tab and select Use Unicode (AL32UTF8) as the Database Character Set. h. click Password Management.g. Click All Initialization Parameters. enter a password for the account. change them to the values indicated.

e. Right-click SQL Server (<instance name>) and then click Restart. so that the appropriate port can be opened in the firewall. Verify that you enabled the Full-text Search setting during the installation of Microsoft SQL Server 2005. Since Tivoli Asset Management for IT requires SQL Server to listen on a static port. grant create procedure to maximo. g. Manually configuring SQL Server Ensure the MS SQL Server 2005 service pack 2 is installed. from inside SQL Server Enterprise Manager. or from the command prompt by executing isqlw. Click OK. From the SQL Server Configuration Manager navigation pane. grant connect to maximo. grant create table to maximo. configure the Database Engine to listen on a specific port. f. click SQL Server 2005 Services. 2. and then double-click TCP/IP. alter user maximo quota unlimited on maxdata. From the SQL Server Configuration Manager navigation pane. grant execute on ctxsys.ctx_ddl to maximo. Type the following command: select FULLTEXTSERVICEPROPERTY ( ’IsFulltextInstalled’ ) Chapter 5. Open SQL Query Analyzer. perform the following steps: a. h. grant create job to maximo. b. To configure an existing SQL Server 2005 server for use with Tivoli Asset Management for IT. which means they select an available port when the SQL Server service is started. You can run SQL Query Analyzer from the Start menu. If enabled. grant alter session to maximo. If the TCP Dynamic Ports field contains a value of 0. a. Configure the listener port. grant create view to maximo. Open Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager b. that IP address is using dynamic ports. For each IP address listed. grant create session to maximo. Named instances of the SQL Server Database Engine and SQL Server Compact Edition are configured for dynamic ports. this field must be blank. To determine if Full-text Search is installed on your existing Microsoft SQL Server database. expand SQL Server 2005 Network Configuration > Protocols for <instance name to be used with Tivoli Asset Management for IT>.create user maximo identified by maximo default tablespace maxdata temporary tablespace maxtemp. grant create synonym to maximo. Tivoli Asset Management for IT installation program overview 97 . grant create sequence to maximo. grant create trigger to maximo. the default instance of the Microsoft SQL Server Database Engine listens on TCP port 1433. to stop and restart SQL Server. In the TCP/IP Properties dialog box. enter 1433 for the TCP Port field. complete the following steps prior to launching the Tivoli Asset Management for IT installation program: 1. click the IP Addresses tab d. For each IP address listed. c. ensure the TCP Dynamic Ports field is blank. When connecting to a named instance through a firewall.

In the event that you did not install Full-text Search (the resulting value is zero). b. 4. Navigate through the installation dialog boxes and from the Setup Type dialog box. c. 3. b. Click Execute. f. b. c. you must do so at this time. Check the Full-Text Search option. You finish the installation process by choosing to restart the server.SQL. Select the Tivoli Asset Management for IT database (maxdb71) from the Available Databases drop-down menu. a. Click Execute. The following steps provide a general guideline describing how you can change this and other settings after having installed SQL Server. In the Database Properties dialog box. d.DataFilegroupName=<your logical name> 98 Installation Guide for IBM WebSphere Application Server: . Click Add.MAXIMO go e. Enter the following script to change the database owner to maximo. d. Enter the following script to create the Maximo user. c. For the maxdb71 Logical Name. Note: If you add additional logical names to the database and set their file group to a value other than PRIMARY. f. Complete remaining installation steps. modify the log settings to accommodate your production environment. Tivoli Asset Management for IT does not have multilingual support when deployed with SQL Server. unrestricted growth. Run the Tivoli Asset Management for IT installation program and choose the Do not run the configuration step now option. Click New Query. Insert the Microsoft SQL Server 2005 CD-ROM onto the server where you had it installed originally. e. 2. Open SQL Server Enterprise Manager Studio (Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio). and select New Database. Create a SQL Server Database for Maximo a. and also set the value of the Autogrowth field to By 1MB. sp_addlogin MAXIMO. sp_changedbowner MAXIMO go g. select Custom. Right-click the Databases folder from the tree view. in the General tab. specify a unique database name (for example maxdb71) d. change the Initial size attribute to 500 (MB) . you will have to complete the following steps after you have completed setting up the database and created the Maximo user: 1.properties file: Database. If you prefer. Add the following property to the <TAMIT_HOME>\maximo\applications\ maximo\properties\maximo. Note that because SQL Server does not support UTF-8. Open SQL Server Enterprise Manager Studio (Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio). Create the Maximo User for SQL Server a.

Chapter 5. 2. On the Create a new directory server instance window. special characters must be preceded by an escape character in order to make it readable by the directory server. or values you enter directly into an directory instance using the directory server’s own tools. Note that these additional steps must be completed only if you have added additional logical names to the database and set their file group to a value other than PRIMARY. entries in LDIF files. and idsldap groups. 1. and you do not precede the blank character with an escape character. The user idsccmdb must have root assigned as its primary group. and then click Next.1 > Instance Administration Tool. 4. Therefore.3. db2grp1. 3.1/sbin/idsxinst at the command line. for example. UNIX Create the user idsccmdb and make it a member of the root. at the end of a field value. Manually configuring the directory server You must complete the manual configuration of the directory server before you use the Tivoli Asset Management for IT installation program if you choose to not have the Tivoli Asset Management for IT installation program automatically configure it. Refer to the product documentation for your directory server for more information on special characters in LDAP strings. located in the <TAMIT_HOME>\scripts directory. you must create a new ITDS instance. be aware of the product-specific syntax rules for using special characters in an LDAP string. From the Instance Administration Tool. Execute the configuration steps outside of the Tivoli Asset Management for IT installation program by using the taskrunner utility. Failing to escape special characters contained in an LDAP string used with Tivoli Asset Management for IT will result in Tivoli Asset Management for IT errors. create a user on the system and assign it to the appropriate group. Using your preferred method./opt/IBM/ldap/V6. if you mistakenly enter an LDAP string that contains a blank. Many directory server products consider a blank space as a special character that is part of the LDAP string. click Create a new directory server instance. and then start the tool Windows Select Programs > IBM Tivoli Directory Server 6. Manually configuring IBM Tivoli Directory Server To configure IBM Tivoli Directory Server prior to launching the Tivoli Asset Management for IT installation program. ensure you are logged in as an administrator on the system. In most cases. you will encounter Tivoli Asset Management for IT errors that will be difficult to troubleshoot. UNIX Type . Tivoli Asset Management for IT installation program overview 99 . Windows Create the user idsccmdb and make it a member of the Windows Administrators group. click Create. If the Instance Administration Tool is not already started. Important: When entering LDAP values for Tivoli Asset Management for IT installation panel fields.

complete the following fields. Server port number Enter 389 as the contact port for the server. User name Select idsccmdb as the system user ID of the user who will own the directory server instance. and then click Next. From the TCP/IP settings for multihomed hosts panel. From the Configure administrator DN and password window panel. and then click Next. complete the following fields. and then click Next. Database user name Enter idsccmdb as the database user. From the DB2 instance details panel. From the Option steps panel. 7. 100 Installation Guide for IBM WebSphere Application Server: .5. 9. From the Configure database panel. Configure database You will configure the database for the directory server instance now. 11. On the TCP/IP port settings panel. and then click Next. Install location Enter the location where the directory server instance files will be stored. 10. Password Enter the password for the idsccmdb user. and then click Next. Administrator Password Enter a password for the Administrator DN. 8. Configure admin DN and password You will configure the administrator DN and password for the directory server instance now. complete the following fields. Instance description Enter a brief description of the instance. leave the following options selected. select Listen on all configured IP addresses. 6. and then click Next. complete the following fields. From the Instance details window. Administrator DN Enter cn=root for the administrator distinguished name. This name will also be the name of the directory server instance. and then click Next. Server secure port number Enter 636 as the secure port for the server. Encryption seed string Type a string of characters that will be used as an encryption seed. Admin daemon port number Enter 3538 as the administration daemon port. This value must be a minimum of 12 characters. enter idsccmdb as the value for the DB2 instance name field. Admin daemon secure port number Enter 3539 as the administration daemon secure port.

c=US 13. Important: Before you begin this procedure. Tivoli Asset Management for IT installation program overview 101 .c=US v ou=users v ou=groups Define the following users and groups and their positions within the ou=users and ou=groups DN’s you created.idsccmdb UNIX V6. and then click Finish to create the idsccmdb instance. Create and save an LDIF file.Database name Enter idsccmdb as the database to be used with this directory instance. ensure you have the following users and groups created in your LDAP repository: Table 19. Launch the IBM Tivoli Directory Server Configuration Tool: Windows Select Programs > IBM Tivoli Directory Server 6. Select Manage suffixes. Ensure the server is stopped.1/sbin/idsxcfg at the command line./opt/IBM/ldap/V6.1 . Windows IBM Tivoli Directory Server Instance V6. complete the following fields. Click Close to close the window and return to the main window of the Instance Administration Tool. 12. From the Database options panel. 22. Click Configure. UNIX Type . 15. 21. Character-set option Leave the Create a universal DB2 database (UTF-8/UCS-2) option selected.1 > Instance Administration Tool. o=IBM. 16. type the following suffix. and then click Add. These users and groups are defined in order for VMM to be used to secure Tivoli Asset Management for IT. From the Verify settings panel. From the Manage suffixes panel.o=IBM. Add the following DNs: v ou=SWG. Click Close to exit the Instance Administration Tool. review the instance creation details provided. 18. and then click Next. 20. 14. 19. Tivoli Asset Management for IT required users and groups User wasadmin maxadmin mxintadm MAXADMIN (must be uppercase) MAXADMIN (must be uppercase) Groups Chapter 5.1 ibmslapd server daemon 17. Click OK. Database install location Enter the location where you installed DB2.

Open the domains security policy for editing by selecting Start > Administrative Tools > Domain Security Policy.c=us ou: SWG objectClass: top objectClass: organizationalUnit dn: ou=groups. Note: If you create the LDIF file on Windows. as shown in the table below: 102 Installation Guide for IBM WebSphere Application Server: . o=ibm.ou=SWG. complete the following steps prior to running the Tivoli Asset Management for IT installation program: 1. navigate to Security Settings > Account Policies > Password Policy.ou=SWG. o=ibm.ou=users. For each password policy setting displayed. Manually configuring Microsoft Active Directory If you choose to manually configure a Microsoft Active Directory resource for use with Tivoli Asset Management for IT. o=ibm. 24. 25. Click Import.ou=SWG. 2. ensure that you remove the ^M characters from the file before using.c=us ou: users objectClass: top objectClass: organizationalUnit dn: cn=wasadmin. Use the browse button to locate the LDIF file. From the Default Domain Security Settings interface. click Import LDIF data.c=us ou: groups objectClass: top objectClass: organizationalUnit dn: ou=users. 26. From the IBM Tivoli Directory Server Configuration Tool. Tivoli Asset Management for IT required users and groups (continued) User maxreg Groups Here is an example of the default base ldif data: dn: o=ibm. Close the IBM Tivoli Directory Server Configuration Tool and restart the server. right-click the setting.c=us uid: wasadmin userpassword: wasadmin objectclass: organizationalPerson objectclass: inetOrgPerson objectclass: person objectclass: top title: WebSphere Administrator sn: wasadmin cn: wasadmin 23.c=us objectClass: top objectClass: organization o: IBM dn: ou=SWG. 3. and set it to the appropriate value.Table 19. o=ibm. select Properties.

and then click OK: Chapter 5. Enter Groups as the name for the new OU then click OK. Create a users object under the SWG organizational unit: a. 10. An alert dialog box will appear. Click OK. In the Active Directory Users and Computers user interface. Edit the domain functional level of the domain by selecting Action > Raise Domain Functional Level. 12. When the domain raise task has completed.Group dialog. Right-click the SWG OU. On the properties panel. Tivoli Asset Management for IT installation program overview 103 . right-click the domain you want to work with and select New > Organizational Unit. you can simply reboot the system. Create the MAXADMIN group: a. 8. alternatively. Right click the Groups OU and select New > Group. On the properties panel. b. 9. set the check box Define this policy setting to checked and ensure that the value Disabled is selected. On the properties panel. 11. From the New Object . and then click Raise. 14. On the properties panel set the check box Define this policy setting to checked and set the value to 7. Open the Active Directory Users and Computers user interface by selecting Start > Control Panel > Administrative Tools > Active Directory Users and Computers and then select the domain that you will be working with. 7. b. Open a command prompt window and type gpupdate /force. click OK. 5. set the check box Define this policy setting to checked and ensure that the value Disabled is selected. SWG. 13. Enter Users as the name for the new OU then click OK. Enter a name for the new Organizational Unit (OU). Create a groups object under the SWG organizational unit: a. or. set the check box to unchecked. and select New > Organizational Unit. b. enter the following values. Select Windows Server 2003 from the Select an available domain functional level dropdown menu. and select New > Organizational Unit. Right-click the SWG OU. for example. 6. set the check box to unchecked. The Raise Domain Functional Level dialog box will appear. set the check box for Define this policy setting to unchecked. Policy Setting Enforce password history Value Not Defined Step On the properties panel. On the properties panel.Table 20. Maximum password age Minimum password age Minimum Passsword length Not Defined Not Defined 7 characters Password must meet complexity requirements Disabled Store passwords using reversible encryption Disabled 4. and then click OK.

This value must be capitalized. enter the following information.Group dialog. This value must be capitalized and must be different than the name entered above for Group name. From the New Object .User dialog. Group scope Global Group type Security 15. Full name Enter wasadmin. Group scope Global Group type Security 16. User login name Enter wasadmin in the first field. Leave the default value of the second field. b. Last name Leave this field blank. Group name (pre-Windows 2000) Enter MAXIMOUSERS as the pre-Windows 2000 group name. This value must be capitalized. c. and then click OK: Group name Enter MAXIMOUSERS as the group name. Right click the Groups OU and select New > Group. and then click Next: 104 Installation Guide for IBM WebSphere Application Server: . Initials Leave this field blank. User login name (pre-Windows 2000) This field will be filled with the same value (wasadmin) entered for the User login name. Right click the Users OU and select New > User. b. From the New Object . Create the wasadmin user: a. From the next panel. Group name (pre-Windows 2000) Enter MAXADMINPRE2K as the pre-Windows 2000 group name. and then click Next: First name Enter wasadmin. This value must be capitalized. enter the following values. Create the MAXIMOUSERS group: a. enter the following values.Group name Enter MAXADMIN as the group name.

Create the maxadmin user: a. 17. From the New Object . 18. and click Finish. Review the password settings in the summary panel.Password Enter a 7 character password for wasadmin. enter the following values. User must change password at next logon Ensure this checkbox is deselected. and then click Next: Chapter 5. and click Finish. Full name Enter maxadmin. d. enter the following information.User dialog. and then click Next: First name Enter maxadmin. From the next panel. d. User cannot change password Ensure this checkbox is selected. Password never expires Ensure this checkbox is selected. User login name (pre-Windows 2000) This field will be filled with the same value (maxadmin) entered for the User login name. Create the mxintadm user: a. b.User dialog. Right click the Users OU and select New > User. Review the password settings in the summary panel. b. Tivoli Asset Management for IT installation program overview 105 . User login name Enter maxadmin in the first field. Last name Leave this field blank. enter the following values. c. Password never expires Ensure this checkbox is selected. User cannot change password Ensure this checkbox is selected. Account is disabled Ensure this checkbox is deselected. Account is disabled Ensure this checkbox is deselected. Initials Leave this field blank. and then click Next: Password Enter maxadmin as the password for the maxadmin user. Leave the default value of the second field. Right click the Users OU and select New > User. From the New Object . User must change password at next logon Ensure this checkbox is deselected.

From the next panel. enter the following values. Create the maxreg user: a. User login name Enter maxreg in the first field. From the next panel. Leave the default value of the second field. enter the following information. and click Finish. Initials Leave this field blank. 19. d. Full name Enter maxreg. and then click Next: First name Enter maxreg. enter the following information. Account is disabled Ensure this checkbox is deselected. and then click Next: Password Enter a 7 character value as the password for the mxintadm user. Right click the Users OU and select New > User. User must change password at next logon Ensure this checkbox is deselected.First name Enter mxintadm. Full name Enter mxintadm. Leave the default value of the second field. Initials Leave this field blank. Password never expires Ensure this checkbox is selected.User dialog. b. User login name Enter mxintadm in the first field. User login name (pre-Windows 2000) This field will be filled with the same value (maxreg) entered for the User login name. From the New Object . Review the password settings in the summary panel. User login name (pre-Windows 2000) This field will be filled with the same value (mxintadm) entered for the User login name. c. c. User cannot change password Ensure this checkbox is selected. Last name Leave this field blank. and then click Next: 106 Installation Guide for IBM WebSphere Application Server: . Last name Leave this field blank.

Click OK to add the users. select the Members tab and then click Add. Add users to the MAXADMIN group: a. From the MAXIMOUSERS properties dialog. Review the password settings in the summary panel. Click on the Groups object under the SWG OU. b. Computers. g. Click OK to add the users. e. 21. c. f. User must change password at next logon Ensure this checkbox is deselected. select the Members tab and then click Add. Ensure you are selecting the maxadmin user and not the maxadmin group from this list. Click on the Groups object under the SWG OU. g. select the maxadmin. Double-click the MAXIMOUSERS group listed in the Groups pane. From the Select Users. and maxreg users. From the Search results list. From the Select Users. click Find Now. click Find Now. Password never expires Ensure this checkbox is selected. Contacts. b. Double-click the MAXADMIN group listed in the Groups pane. 20. or Groups dialog. From the MAXADMIN properties dialog.Password Enter a 7 character value as the password for the maxreg user. Manually configuring the J2EE server You must complete the manual configuration of the J2EE server before you use the Tivoli Asset Management for IT installation program if you choose to not have the Tivoli Asset Management for IT installation program automatically configure it. Contacts. select the maxadmin and mxintadm users. d. Tivoli Asset Management for IT installation program overview 107 . Microsoft Active Directory configuration is complete and you are now ready to install the remaining Tivoli Asset Management for IT middleware and configure the J2EE server to use Microsoft Active Directory. Account is disabled Ensure this checkbox is deselected. click Advanced. Add users to the MAXIMOUSERS group: a. On the Advanced panel. and click Finish. mxintadm. From the Search results list. Computers. On the Advanced panel. e. 22. c. f. d. or Groups dialog. click Advanced. User cannot change password Ensure this checkbox is selected. Chapter 5. and then click OK. Ensure you are selecting the maxadmin user and not the maxadmin group from this list. You can now exit out of the Active Directory Users and Computers user interface. d. and then click OK.

Click Next. Click Next. 18.p12 Launch the profile creation wizard. and Cell name. During the installation process. close the output window. follow these steps: IBM WebSphere Network Deployment 1. Select the create a deployment manager option. 13. perform Virtual 108 Installation Guide for IBM WebSphere Application Server: . then it will. Specify a unique node name and the computer name (or IP address) of the machine where you are performing this installation. 4. 9. Click Next. Click Next. Click Next. Click Exit. Click the Installation verification link. Host name. Accept the default values or specify the appropriate information. the Tivoli Asset Management for IT installation program provided you with the option of automatically configuring Tivoli Asset Management for IT middleware. If another First steps window is open. 24. Click Next in the Profile summary dialog box. Click Next. Click Next in the Welcome dialog box. Accept the default values or specify the Node name. 22. Manually configuring Virtual Member Manager on WebSphere This procedure provides task information for manually configuring Virtual Member Manager (VMM) to secure Tivoli Asset Management for IT. Specify a unique Profile name and select the Make this profile the default check box. 16. 20. Click Finish. Accept the default directory path. You will use this context when invoking the console through a browser. Note the Administrative port number. 19. Click Finish. 14. Accept the default value or specify a Profile name. 12. After Installation Verification completes. 8. 6. 3. Review the assigned port numbers. 15. Review the port number listings. Select the Launch the First steps console check box. close it. Click Next in the Welcome dialog box. Manually copy the keystore file from the IBM WebSphere Network Deployment deployment manager host to a temporary directory on the Tivoli Asset Management for IT administrative system where you are installing Tivoli Asset Management for IT: 2. 11. 21. Click Next. Accept the default installation location. among other tasks. <WAS_home>/profiles/ctgDmgr01/etc/trust. If you elected to have the Tivoli Asset Management for IT installation program automatically configure Tivoli Asset Management for IT middleware. 23. Click Next. Click Next in the Profile summary dialog box. Click Next. Select the Launch the First steps console option. Use the launchpad command and click the Profile creation wizard to open the First Steps window (if not open already) . 17. Click Next. 5. Select the Run the Application Server as a Windows service and log on as a local system account. 10. Click Next. Click Next. Select Create a custom profile.To configure the J2EE server prior to launching the Tivoli Asset Management for IT installation program. 7.

it must be done only after a successful Tivoli Asset Management for IT installation. Enter the following values. 2. Note that if you intend to configure VMM to use SSL with a federated LDAP repository. The federated repository consists of a single named realm. which is a starting point within the hierarchical namespace of the virtual realm. You will also have to modify the VMMCRONTASK as shown in “Manually configuring the VMMSYNC cron task for Microsoft Active Directory” on page 132. Tivoli Asset Management for IT installation program overview 109 . you must first add the LDAP directory to the list of repositories available for configuration for the federated repository and then add the root of baseEntries to a search base within the LDAP directory. Do not configure a WebSphere VMM LDAP federated repository to use SSL with an LDAP directory prior to installing Tivoli Asset Management for IT. Chapter 5. Configure SSL after the Tivoli Asset Management for IT installation program has completed successfully. a subtree within that repository. and federate that data into a single virtual repository. Login to the admin console. Click Add to create new repository definition under the current default realm. If you elected to manually configure Tivoli Asset Management for IT middleware for use with Tivoli Asset Management for IT. Multiple base entries can be added with different search bases for a single LDAP directory. If you are configuring VMM to use Microsoft Active Directory. which is a set of independent user repositories. Important: Before you begin this procedure. in this example. Each repository may be an entire external repository or. located under Related Items. The root of each repository is mapped to a base entry within the federated repository. and then click Configure. To add the IBM Tivoli Directory Server to VMM. in the case of LDAP. you will have to manually configure VMM.Member Manager (VMM) configuration for you. then navigate to Security > Secure administration. complete the following steps: 1. VMM provides you with the ability to access and maintain user data in multiple repositories. Click Manage repositories. To add an LDAP directory to the VMM virtual repository. Locate the User account repository section and select Federated repositories from Available realm definition. Repository identifier Enter ISMITDS. The instructions provided here are for IBM Tivoli Directory Server. applications. If VMM is configured to use SSL with a federated LDAP repository prior to completing the Tivoli Asset Management for IT installation. 5. Directory type Select the directory type. IBM Tivoli Directory Server Version 6 Primary host name Enter the fully-qualified host name or IP address of the IBM Tivoli Directory Server server. and infrastructure. 4. 3. substitute values you used in “Reusing Microsoft Active Directory” on page 44 and “Manually configuring Microsoft Active Directory” on page 102 where appropriate in this procedure. and then click Apply and the click Save. the installation will fail. ensure you have a wasadmin user created in your LDAP repository.

From the Federated repositories configuration page. 10.ou=SWG. Bind distinguished name Enter cn=root Bind password Enter the password for the bind distinguished name. Distinguished name of a base entry that uniquely identifies this set of entries in the realm ou=SWG. Return to the Federated repositories page by clicking Security ? Secure administration.c=US. 110 Installation Guide for IBM WebSphere Application Server: . Certificate mapping Select EXACT_DN 6. and then click PersonAccount. Ignore case for authorization Select this check box.: Realm name Enter ISMRealm. Locate the Repositories in the realm section and click Add Base entry to Realm. Repository Select ISMITDS.c=US 9.c=US Distinguished name of a base entry in this repository ou=SWG. Note that if there is an existing file repository entry in the Repositories in the realm table.o=IBM. Enter the following values. Base entry for the default parent Enter ou=users. enter the following values and then click Apply and then click Save. Click Supported entity types. after creating the new entry. applications. Support referrals to other LDAP servers Set this to ignore. and then clicking Configure. you must select it click Remove. and save the change. and infrastructure. From the PersonAccount configuration page. 7. Server user identity Select Automatically generated server identity. Primary administrative user name Enter wasadmin. enter the following values: Entity type Verify that the value is PersonAccount.Port Enter 389. and then click Apply and then click Save.o=IBM. This value should be a valid user from the configured LDAP repository. 11. 8. Login properties Leave this value blank. Relative Distinguished Name properties Enter uid.o=IBM. selecting Federated repositories from the Available realm definitions drop-down list.

bat b. Restart WebSphere and the managed nodes: a. select Federated repositories. <WAS_HOME>\profiles\ctgDmgr01\bin\startManager. Enable Enable application security. 16. e. During the installation process. Tivoli Asset Management for IT installation program overview 111 . Click Supported entity types. Navigate to Security > Secure administration.bat Note: Substitute UNIX path and file extension values where appropriate. Relative Distinguished Name properties Enter o. Click Set as current. Relative Distinguished Name properties Enter cn.o=IBM.cn. 15. Click OK and then click Save 18. <WAS_HOME>\profiles\ctgAppSrv01\bin\startNode. You have now successfully completed setting up VMM. The next step is to perform post J2EE server tasks. 21.ou=SWG. then it will. applications. 17.12. Click Supported entity types. enter or verify the following values: Entity type Verify that the value is OrgContainer. the Tivoli Asset Management for IT installation program provided you with the option of automatically configuring Tivoli Asset Management for IT middleware. among other tasks. and infrastructure configuration page. and then click Save. and then click OrgContainer. Enable Enable administrative security. and infrastructure.c=US. perform J2EE Chapter 5.dc. <WAS_HOME>\profiles\ctgDmgr01\bin\stopManager. 14. <WAS_HOME>\profiles\ctgAppSrv01\bin\stopNode. Deselect Use Java 2 security to restrict application access to local resources.c=US. 19. From the Secure administration.bat d. complete the following: a.ou. From the OrgContainer configuration page. Base entry for the default parent Enter ou=SWG. d. c. 20. Base entry for the default parent Enter ou=groups. and then click Group. Click OK and then click Save 13. From Available realm definition.o=IBM. If you elected to have the Tivoli Asset Management for IT installation program automatically configure Tivoli Asset Management for IT middleware. applications. b. Performing post installation tasks for the J2EE server Use this procedure to perform post installation steps for the J2EE server.bat c. From the Group configuration page. Click Apply. enter the following values: Entity type Verify that the value is Group.

g. f. b. 6. 3. Click New. e. From the System administration link in the tree view click Deployment manager. Click OK. d. Click Save in the messages box. From the Servers link in the tree view click Application servers. Click Process Definition. Accept default settings and click Next. b. Click MXServer in the main window. Click Java Virtual Machine. f. d. Click Start. Check the Synchronize changes with Nodes check box. Select the checkbox beside MXServer. Accept all default settings and click Next. This step is only necessary if you did not install WebSphere using the Tivoli middleware installer. Start the application server: a. b. Edit JVM Memory Settings for the application server a. Click Save in the messages box.server configuration for you. Identify the HTTP Transfer Port Numbers: 112 Installation Guide for IBM WebSphere Application Server: . g. expand the Java and Process Management link. you will have to manually configure the J2EE server. Expand the Servers link and click Application servers. Click Process Definition. From the Servers link in the tree view click Application servers. Enter a username to login. j. c. If you elected to manually configure Tivoli Asset Management for IT middleware for use with CCMDB. Type MXServer and click Next. Click Java Virtual Machine. 5. Create the MXServer Application Server. c. Click Preferences. c. a. This URL address depicts the default port number (9060) and context (admin) for the Administrative Console. e. expand the Java and Process Management link. b. i. Click Save. c. e. Note the browser will be redirected to a secure port (9043). f. 4. From the Server Infrastructure group. h. Scroll down and type 512 for Initial Heap Size and 1024 for Maximum Heap Size and click OK. and then click Apply. d. From the Server Infrastructure group. 2. Invoke a browser window and open the Administrative Console by typing in the browser address bar: http://<machine_name>:9060/admin. 1. Click Finish. Scroll down and type 512 for Initial Heap Size and 1024 for Maximum Heap Size and click OK. Edit JVM Memory Settings for the deployment manager a.

create and configure JMS message queues for you. Click OK. Click Apply and then click OK. In the General Properties section. Note the default port number as it appears with WC_defaulthost (9080). and click MXServer from the main window. Click New. From the Virtual Hosts window. p. From the navigational breadcrumb trail. u. b. Start the WebSphere application server. w. Tivoli Asset Management for IT installation program overview 113 . Click Save. j. Click New.a. click maximo_host. If you elected to have the Tivoli Asset Management for IT installation program automatically configure Tivoli Asset Management for IT middleware. v. Manually configuring JMS queues This procedure provides details on steps to configure JMS queues. i. During the installation process. Click OK. Type * (asterisk) for Host Name and type 9080 for the port number. h. o. f. Expand the Environment link from the tree view. Open the Web Container Settings and click Web container transport chains. Click OK. If you elected to manually configure Tivoli Asset Management for IT middleware for use with Tivoli Asset Management for IT. l. e. type maximo_host in the Name box. Type * (asterisk) for Host Name and type 9044 for the port number. Click New. the Tivoli Asset Management for IT installation program provided you with the option of automatically configuring Tivoli Asset Management for IT middleware. Type * (asterisk) for Host Name and type 9061 for the port number. click maximo_host. you will have to manually configure these message queues. Create the virtual host. b. Expand Servers > Application servers. then it will. c. g. Click New. Click New. complete the following steps: 1. Click the Host Aliases link. k. Click OK. Type * (asterisk) for Host Name and type 9443 for the port number. 7. r. q. which must be completed prior to deploying Tivoli Asset Management for IT EAR files. To configure the JMS queues. d. x. m. d. c. y. Click Virtual Hosts. Chapter 5. t. Click New. s. Click Save. Click Apply. Type * (asterisk) for Host Name and type the HTTP port number (by default 80). n. a. among other tasks. Click OK.

A bus is a group of interconnected servers and clusters that have been added as members of the bus. 6. From the WebSphere Administrative Console. 9. Click Save. 8. 10. 11. v Auto-generated. 7. 9. Deselect the Bus security check box. enter your User ID. click Next. click Bus members. selecting MXServer. 4. Launch Internet Explorer and open the WebSphere Administrative Console by typing the following URL: http://<machine_name>:<port_number>/ibm/console For example. This action opens the Welcome screen for the WebSphere Administrative Console. Click Finish. Click Service Integration > Buses to open the Buses dialog. then click Log in. intjmsbus inherits the Global Security setting of the cell. Click Save. for example. intjmsbus. Under Topology. This step propagates the JMS bus setup to the cluster configuration. and then clicking Start. and then click Apply. please enter your information login screen. Confirm that build completed screen displays the following: v Bus name. Click New to open the Buses > New dialog box where you can add a new service integration bus. 114 Installation Guide for IBM WebSphere Application Server: . Select the Synchronize changes with Nodes option. Select intjmsbus. 5. 13. 10. Click OK. Change the value of the High message threshold field to a minimum value of 500. Adding a server to the service integration bus Complete the following steps to add a server to the service integration bus: 1. 4. 11. At the Welcome. and then click Next. click Service Integration > Buses to open the Buses dialog box 2. 8. Start the MXServer server by navigating to Servers > Application Servers.000 messages. 4BCAC78E15820FED. Click the Server drop-down arrow. 5. and then click Next. Click intjmsbus to open the Buses > intjmsbus dialog box. and select the server name ctgNode01:MXServer to add to the bus. 12. 7. Check that the File store radio button is selected. Enter intjmsbus as the name of the new bus in the Name field. enter a URL similar to the following: http://localhost:9060/ibm/console 3. If you leave this box checked. for example. Click Next. Click Finish. From the Provide the message store properties panel. and then click Apply. v The Secure field is unchecked. 6. click Add to open the Add a new bus member dialog box. 12. 3.2. unique ID (UUID). Click System administration > Console preferences. In the Buses > intjmsbus > Bus members dialog box.

If the number of messages awaiting processing exceeds the High Message Threshold you set. 14. Review your selections. v Change the Maximum failed deliveries value to 1. You can determine an optimal message threshold setting by monitoring the messaging in/out queues and the impact of the message threshold setting on system performance. 7. for example. 13. 10. 11. Tivoli Asset Management for IT installation program overview 115 . lower the threshold value if a higher value is degrading system performance. Navigate the path Buses > intjmsbus > Destinations. 8. If you decide to change the High message threshold setting after the initial configuration. Click intjmsbus to open the Buses > intjmsbus dialog box. 6. then click Finish to complete the creation of the CQINBD bus destination queue. the application server will take action to limit the addition of new messages in the processing queues. you must open the Additional Properties menu in the Administrative Console and change the threshold value for each child configuration. Type CQINBD in the Identifier field and Continuous Queue Inbound in the Description field. is a virtual place within a service integration bus where applications can attach and exchange messages. Click OK. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. 3. you may want to enter a higher message threshold value. A bus destination. 5. 2. then click Next to open the Create a new queue for point-to-point messaging dialog box. 12. Click New to open the Create new destination dialog box. for example CQINBD. click Service Integration > Buses to open the Buses dialog box. Click Apply. You might. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. Depending on your message requirements. 9. Click Save. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer as the bus member that will store and process messages for the CQINBD bus destination queue. and click Next to open the Create new queue dialog box. Chapter 5. Creating the service integration bus destination for the continuous inbound (CQINBD) queue To add a logical address for the continuous inbound bus destination queue (CQINBD) within the JMS bus. then click CQINBD to open the configuration dialog box where you must make the following changes: v Click None as the Exception destination value. From the WebSphere Administrative Console. Note that you must use this value and it must contain only uppercase letters. complete the following steps: 1. Leave Queue checked as the destination type. Click Next to open the Confirm queue creation dialog box. Click Save. 4.

click Service Integration > Buses to open the Buses dialog box. Navigate the path Buses > intjmsbus > Destinations. Click intjmsbus to open the Buses > intjmsbus dialog box. Click intjmsbus to open the Buses > intjmsbus dialog box. 5. Leave Queue checked as the destination type. Click Save. Click Next to open the Confirm queue creation dialog box. A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. Click New to open the Create new destination dialog box. 10. Enter SQINBD in the Identifier field and Sequential Queue Inbound in the Description field. 11. then click Finish to complete the creation of the SQINBD bus destination queue. then click Next to open the Create a new queue for point-to-point messaging dialog box. click Service Integration > Buses to open the Buses dialog box. for example SQOUTBD. and click Next to open the Create new queue dialog box. 2. Click New to open the Create new destination dialog box. Creating the service integration bus destination for the sequential outbound (SQOUTBD) queue To add a logical address for the sequential outbound bus destination queue (SQOUTBD) within the service integration bus. 6. is a virtual place within a service integration bus where applications can attach and exchange messages. Note that you must use this value and it must contain only uppercase letters. 12. complete the following steps: 1. 116 Installation Guide for IBM WebSphere Application Server: . 5. 3. then click SQINBD to open the configuration dialog box where you must make the following changes: v Click None as the Exception destination value. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer 8. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. 2. Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. 4. Click Apply. From the WebSphere Administrative Console.Creating the service integration bus destination for the sequential inbound (SQINBD) queue To add a logical address for the sequential inbound bus destination queue (SQINBD) within the service integration bus. Review your selections. 3. From the WebSphere Administrative Console. Leave Queue checked as the destination type. complete the following steps: 1. A bus destination. 4. v Change the Maximum failed deliveries value to 1. 7. 9. and click Next to open the Create new queue dialog box.

4. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer as the bus member that will store and process messages for the SQOUTBD bus destination queue. 5. From the Scope drop-down list select Cell=ctgCell01 3. Enter the following information. Note this value must only contain uppercase letters. then click Next to open the Create a new queue for point-to-point messaging dialog box. 8. and then click OK. v Change the Maximum failed deliveries value to 1. 1. and click OK. Click Next to open the Confirm queue creation dialog box. Enter SQOUTBD in the Identifier field and Sequential Queue Outbound in the Description field. Name Enter intjmsconfact. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. Tivoli Asset Management for IT installation program overview 117 . 9. Enter the following information.6. Bus name Select intjmsbus. JNDI name Enter jms/maximo/int/cf/intcf. 3. 10. Click Apply. click Resources → JMS → Connection factories. Click Save. Verify that the Default Messaging Provider is selected and click OK. 5. Click New. From the WebSphere Administrative Console. click Resources > JMS > Queues. Creating the continuous inbound (CQIN) JMS queue You must create a JMS queue (CQIN) as the destination for continuous inbound point-to-point messages. 12. Creating the JMS connection factory You add a connection factory for creating connections to the associated JMS provider of point-to-point messaging queues. From the WebSphere Administrative Console. 2. Verify that the Default Messaging Provider is selected and click OK. 2. Click New. Note that you must use this value and it must contain only uppercase letters. 6. Chapter 5. 11. then click Finish to complete the creation of the sqinbd queue. From the Scope drop-down list. Navigate the path Buses > intjmsbus > Destinations. then click SQOUTBD to open the configuration dialog box where you must make the following changes: v Click None as the Exception destination value. 7. Click Save. select Cell=ctgCell01. 1. Review your selections. Name Enter CQIN. 4.

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

Click Destinations under Destination resources to open the Buses > intjmsbus > Destinations dialog box. Click New to complete the General Properties section for the new JMS activation specification. From the WebSphere Administrative Console. Click OK. Creating the service integration bus destination for the inbound error queue (CQINERRBD) queue To add a logical address for the inbound error queue (CQINERRBD) queue within the JMS bus. 5. From the Scope drop-down list. and then click OK. Chapter 5. 8. restart MXServer under Servers → Application servers. 9. Start the bus member for the ctgNode MXServer intjmsbus if it is not started. Creating JMS activation specification for the continuous inbound queue (CQIN) You must activate the continuous inbound queue (CQIN) before it can receive messages. select Cell=ctgCell01. If you cannot start ctgNode MXServer intjmsbus. click Resources → JMS → Activation Specifications. 4. 3. You must now restart these processes for the update to take effect. Ensure to stop all IBM-related processes and daemons. Enter the following information. Tivoli Asset Management for IT installation program overview 119 . Error queues You can create an optional error queue that will receive redirected messages from the continuous queue (cqin) when the messages go in error. Click intjmsbus to open the Buses > intjmsbus dialog box. 2. Complete the following steps to activate the CQIN queue: 1. 2. This value must be lowercase. Click Save. complete the following steps: 1. 7. Name intjmsact This value is case-sensitive. 3. From the WebSphere Administrative Console. click Service Integration > Buses to open the Buses dialog box.7. Click Save. JNDI name intjmsact Destination type Queue Destination JNDI name jms/maximo/int/queues/cqin Bus name intjmsbus Maximum concurrent endpoints 10 6.

8. Verify that the Default Messaging Provider is selected and click OK. JNDI name Enter jms/maximo/int/queues/cqinerr Bus name Select intjmsbus. 7. Click Apply. and click OK. Leave Queue checked as the destination type. Navigate the path Buses > intjmsbus > Destinations. 1. Click Save. 13. 15. Click OK. select Cell=ctgCell01. Click New. then click Next to open the Create a new queue for point-to-point messaging dialog box. From the WebSphere Administrative Console. 3. Creating the error (CQINERR) JMS queue After creating the Error Queue Bus Destination. 17. 18. 9. Enter the following information. From the WebSphere Administrative Console. Click New to open the Create new destination dialog box. Note this value must only contain uppercase letters. 2. Enter CQINERRBD in the Identifier field and Error Queue Inbound in the Description field. 5. then click CQINERRBD to open the configuration dialog box where you must make the following changes: v Click Specify and enter CQINERRBD as the exception destination value. A bus destination is a virtual place within a service integration bus where applications can attach and exchange messages. Specify CQINERRBD as the exception destination. This is the maximum number of times you want the system to process a failed messaging attempt before forwarding the message to the exception destination. then click Finish to complete the creation of the CQINERRBD bus destination queue. 4. Select the Bus Member pull-down and choose Node=ctgNode01:Server=MXServer Click Next to open the Confirm queue creation dialog box.4. Select CQINBD. From the Scope drop-down list. Click Save. Note that you must use this value and it must contain only uppercase letters. 14. 12. click Service Integration > Buses to open the Buses dialog box. v Change the Maximum failed deliveries value to 5. 16. . 5. Review your selections. 6. and click Next to open the Create new queue dialog box. you create the Error queue. click Resources → JMS → Queues. Name Enter CQINERR. Set the Maximum failed deliveries value to 5. 10. 11. 120 Installation Guide for IBM WebSphere Application Server: . Click intjmsbus to open the Buses > intjmsbus dialog box.

com/ infocenter/wasinfo/v6r1/index.boulder. From the Scope drop-down list. JNDI name Enter intjmsacterr Destination type Enter Queue. Complete the following steps to activate the CQINERR queue: 1. Enter the following information. including the usage of products other than DB2. complete the following steps: 1. This value must only contain lowercase letters. Chapter 5. Name Enter intjmsacterr. Creating JMS activation specification for the inbound error queue (CQINERR) You must activate the continuous inbound queue (CQINERR) before it can receive messages.jsp?topic=/com.ibm. Open DB2 Control Center b. to complete the General Properties section for the new JMS activation specification. 5. Tivoli Asset Management for IT installation program overview 121 . 2.ibm. From the WebSphere Administrative Console. For example. Click OK. 7. 3. Click OK. click Resources → JMS → Activation Specifications. To create a datasource for the persistence store.pmc.html and http://publib. c.boulder.Queue name Select CQINERR. Right-click the Databases folder and select Create Database → Standard. Create a system user and password on the machine hosting the database server. you will need to create a datasource in order to store JMS messages in a DB2 database.nd. select Cell=ctgCell01.doc/tasks/tjm0035_. 7.doc/info/ welcome_nd.ibm. 6. 6. Navigate down to the Databases folder listed under your system. Click New. Click Save. mxsibusr/mxsibusr. Click Save. Create and configure the database. 4.websphere. Click OK. Create a database named maxsibdb using default settings.html If you chose to manually configure WebSphere. a. For more information about WebSphere message storage.com/infocenter/wasinfo/v6r1/ index.nd. Manually creating a datasource for the persistence store You have the option of having WebSphere use a DB2 database to store JMS messages. and click OK. d.websphere. Destination JNDI name jms/maximo/int/queues/cqinerr.ibm. refer to http://publib. 2.jsp?topic=/com.

Verify that you can connect to the database using the mxsibusr user by right-clicking maxsibdb and selecting Connect. Configure J2C authentication data and JDBC provider in WebSphere. Right-click DB Users and select Add. j. Click Apply. b. Click Finish. 122 Installation Guide for IBM WebSphere Application Server: . Click Apply. Specify the following values: Database type DB2 Provider type DB2 Universal JDBC Driver Provider Implementation type XA data source Name maxJdbcProvider k. d. Open and login to the WebSphere Administrative Console. Click New. n. o. click on Java Authentication and Authorization Service → J2C authentication data. a. and infrastructure. Click Save.e. i. 3. Click Next. Click Next. Description SIB database user alias. m. e. Click New. Click Scope and then select Cell=ctgCell01. From the WebSphere Administrative Console navigation pane. l. f. f. j. expand the maxsibdb database and select User and Group objects. Once the database has been created. c. and then click Save. h. g. Complete the following fields in the User identity form. h. Select mxsibusr from the User drop-down list. Alias maxJaasAlias User ID mxsibusr Password Password you created for mxsibusr. i. Fill in the WebSphere variable ${DB2UNIVERSAL_JDBC_DRIVER_PATH} field with a value of <WAS_HOME>ctgMX\lib. For example. applications. navigate to Resources → JDBC → JDBC Providers. Navigate to Security → Secure administration. C:\Program Files\IBM\WebSphere\AppServer\ctgMX\lib. Under the Authentication header. g. Grant all authorities to the mxsibusr with the exception of Security administrator authority.

jar. c. Click Save. and correct the Class path if required for both db2jcc. users. From the Component-managed authentication alias and XA recovery authentication alias drop-down list. Tivoli Asset Management for IT installation program overview 123 . Port number Specify the DB2 port number. Specify the following values: Database name maxsibdb Driver type 4 Server name Specify the DB2 server host name. i. navigate to Resources → JDBC → Data sources. Configure WebSphere: a. b. 6. Installing Tivoli Asset Management for IT without middleware autoconfiguration This procedure will instruct you on installing Tivoli Asset Management for IT and choosing to not have the Tivoli Asset Management for IT installation program autoconfigure the Tivoli Asset Management for IT middleware servers. You might elect to not have the Tivoli Asset Management for IT installation program autoconfigure Tivoli Asset Management for IT middleware if your organization has specific policies and procedures that govern how you create databases. and so on. For example. Go back to Resources → JDBC → JDBC Providers → maxJdbcProvider. Open a command prompt and copy <DB2_HOME>/java/db2jcc. h. and then clicking Test Connection. Specify the following values: Data source name intjmsds JNDI name jdbc/intjmsds e. Click New. Chapter 5. Click Finish. and then click Next. database instances. Ensure that each jar file has the full path from ${DB2UNIVERSAL_JDBC_DRIVER_PATH} 5. l. Choose Select an existing JDBC provider. j.jar and <DB2_HOME>/java/db2jcc_license_cu.jar and db2jcc_license_cu.4. Click Next. k.jar to the <WAS_HOME>\ctgMX\lib directory. select maxJaasAlias f. 50005. Verify the datasource by selecting intjmsds. g. and then select maxJdbcProvider from the drop-down list. within your organization. From the WebSphere Administrative Console. Ensure the Use this data source in container managed persistence (CMP) option is enabled. Click Scope and then select Cell=ctgCell01. Click Next. d.

2. This file is found in the workspace that was defined during the Tivoli Asset Management for IT middleware installation task. and run the following command: install. proof-of-concept. 6. Login to the Tivoli Asset Management for IT administrative workstation as Administrator. follow these steps: 1.1”. and then click Next. 5. c. Alternatively.exe. select the Custom deployment topology. click Next.If you intend to use DB2 on UNIX systems with Tivoli Asset Management for IT. a. This deployment option is typically only used for demonstration. navigate to the root directory of the product disc or the downloaded installation image. Workspace Location Enter the location of the topology file that contains the values entered for the Tivoli middleware installer. From the Import Middleware Configuration Information panel. Launch the Tivoli Asset Management for IT installation program from the launchpad. From the Introduction panel. To install Tivoli Asset Management for IT. From the Choose Deployment panel. Import Middleware Configuration Information Select this check box if you want to allow the Tivoli Asset Management for IT installation program to reuse values entered in the Tivoli middleware installer. Start the launchpad: v On the DVD titled “Tivoli Asset Management for IT V7. 3. On the DVD titled “Tivoli Asset Management for IT V7. and run the following command: launchpad. The middleware default information will not be used if you select the Simple deployment path. Host name Enter the host name of the system where the Tivoli middleware installer was run. you must add root to the DB2GRP1 group prior to starting the Tivoli Asset Management for IT installation program. navigate to \Maximo\. Simple Select simple if you want to deploy all Tivoli Asset Management for IT components on a single system.exe. C:\ibm\tivoli\mwi\ workspace. click Install the Product. or training purposes. specify that you want to use field values you input into the Tivoli middleware installer as default values for those same fields in the Tivoli Asset Management for IT installation program. 124 Installation Guide for IBM WebSphere Application Server: . 4. Select a language for the installation and click OK. Click Tivoli Asset Management for IT. b. In the launchpad navigation pane. For example. User ID Enter the User ID that was used to run the Tivoli middleware installer.1”. Password Enter the password of the User ID that was used to run the Tivoli middleware installer. you can launch the Tivoli Asset Management for IT installation program directly.

and then click Next. This instance will be created if it does not already exist. select the product that you will be using for the maximo database. The database will be created if it does not already exist. Instance Enter the name of the database instance to be used with Maximo. Default for all platforms is maximo. however. DB2 Select this choice to use IBM DB2 UDB as the Maximo database. Where Would You Like to Install? Enter the path to install Tivoli Asset Management for IT. specify the directory you will use to install Tivoli Asset Management for IT. Tivoli Asset Management for IT installation program overview 125 . Database Password Enter the password for the user ID used to access DB2. and then click Next. and then click Next. DB2 Host name Enter the host name of the machine hosting DB2. This user ID cannot be the same one used as the instance administrator user ID. Port Enter the port being used by DB2 instance. Oracle Select this choice to use Oracle as the Maximo database. The default is 50005 Database Name Enter the name of the database to use with Maximo. 8. The host name must be fully qualified. Chapter 5. Database User ID Enter the user ID used for Maximo to access DB2. From the Maximo Database Type panel. The default instance name is ctginst1. 9. The path you specify must not contain spaces. Each database will have its own unique set of configurable parameters and values. the user and its associated home directory must already exist on the DB2 server. 7. From the Maximo Database panel. By default. this value is C:\IBM\SMP. This user ID will be created if it does not already exist. SQL Server Select this choice to use MS SQL Server 2005 as the Maximo database. enter configuration information about the database. The default database name is maxdb71.Custom Select custom if you want to deploy Tivoli Asset Management for IT components across several systems. From the Choose Install Folder panel. This deployment option is typically used in a production environment.

The default is 1433 Database Name Enter the name of the database to use with Maximo. After you have entered configuration information for the database that was selected. This user ID will be created if it does not already exist. select Do not automate database configuration. If you have not manually configured the database prior to selecting Do not automate database configuration from within the Tivoli Asset Management for IT installation program. This user ID will be created if it does not already exist. Default for all platforms is maximo. Database Password Enter the password for the user ID used to access Oracle. the installation will verify that you have not completed these pre-install tasks and you will be reminded to complete them prior to restarting the Tivoli Asset Management for IT installation program. The host name must be fully qualified. The host name must be fully qualified. and then click Next. Password Enter the password for the user ID used to access SQL Server. 10. Database User ID Enter the user ID used for Maximo to access Oracle. The default instance name is ctginst1. From the Automate Database Configuration panel. Note that this step assumes you have already created a database instance. Default for all platforms is maximo. User ID Enter the user ID used to access SQL Server. the Tivoli Asset Management for IT installation program will connect to the database server to validate the information you have entered. Port Enter the port being used by Oracle. The default database name is maxdb71. SQL Server Host name Enter the host name of the machine hosting SQL Server. tablespaces. Refer to “Manually configuring the database server” on page 86.Oracle Host name Enter the host name of the machine hosting Oracle. a database. Port Enter the port being used by SQL Server. a user. 126 Installation Guide for IBM WebSphere Application Server: . The default is 1521 Instance Enter the name of the database instance to be used with Maximo. and schema for use with Tivoli Asset Management for IT.

On AIX. and so on. 13. Once the database validation task has completed. From the Remote Access Authorization panel. this value might be C:\Program Files\IBM\WebSphere\AppServer Linux On Linux. enter authorization information for WebSphere configuration. select Do not automate WebSphere configuration. running WebSphere as a Windows service. and then click Next. Windows On Windows. 12. 14. this value might be /opt/IBM/WebSphere/ AppServer User ID Enter the administrative user ID used to access the WebSphere server. and then click Next. enter host information about the WebSphere server. Tivoli Asset Management for IT installation program overview 127 . Host name Enter the fully-qualified host name of the system hosting WebSphere. you will have had to configure WebSphere manually prior to the installation of Tivoli Asset Management for IT. from the WebSphere Connectivity panel. you can provide the IP address for the system. Configuration tasks include creating a profile. this value might be /usr/IBM/WebSphere/ AppServer Chapter 5. WebSphere installation directory Enter the directory where WebSphere is installed on the host system. Operating system password Enter the password for the system user ID. enter values for the following fields. Alternatively. and then click Next. this value might be /opt/IBM/WebSphere/ AppServer AIX HP-UX On HP-UX. SOAP port Enter the SOAP port of the WebSphere system. From the Automate WebSphere configuration panel.11. and then click Next. The default value for this field is 8879. Remember that in choosing not to have the Tivoli Asset Management for IT installation program automatically configure middleware. Operating system user ID Enter a valid user ID that will allow the Tivoli Asset Management for IT installation program to access the system that is hosting WebSphere. this value might be /opt/IBM/WebSphere/ AppServer Sun Solaris On Sun Solaris. This user ID should have administrative rights on the machine you are accessing. copying the WebSphere keystore file from the machine where WebSphere is installed to the administrative workstation. setting up JMS queues. From the WebSphere Deployment Manager configuration panel.

o=IBM. From the Security panel. Leave this option selected. 15. and then click Next.c=us. and then click Next. enter the following information.Default for all platforms is wasadmin. From the WebSphere Application Server Configuration panel. Create the required users. Web server port Enter the Web server port used by WebSphere. Default for all platforms is MAXIMOCLUSTER. You will be required to manually configure VMM to work with your custom schema and also manually configure the VMM synchronization crontask. You will need write access to VMM. Default for all platforms is 80 Web server name Enter the name of the Web server. Selecting this option indicates that you wish to have Tivoli Asset Management for IT default users created automatically by the Tivoli Asset Management for IT installation program. Use the default schema. you should deselect this option. ou=swg. Default for all platforms is ctgDmgr01. Cluster name Enter the name of the WebSphere cluster containing the application server. Default for all platforms is webserver1 Node name Enter the name of the WebSphere node containing the application server. You’ll be prompted to manually configure security. indicate application server security should not be enabled automatically. 128 Installation Guide for IBM WebSphere Application Server: . The cluster name is optional. Selecting this option indicates that WebSphere Virtual Member Manager (VMM) has been configured using the default schema supplied with Tivoli Asset Management for IT with a default VMM base entry. Leave this option selected. Password Enter the password for the administrative user ID used to access the WebSphere server. The cluster and application server will be created if they do not exist. If you have elected to supply your own schema for use with VMM. Profile name Enter the name of the WebSphere profile. Default for all platforms is ctgNode01. 16.

c=US member: uid=mxintadm.ou=SWG.c=US cn: maxadmin dn: cn=maximousers.ou=users. From the Integration Adapter JMS Configuration panel. Users must be created prior to advancing past the Security panel.ou=users. Default is intjmsds.ou=SWG.ou=SWG.ou=groups. Chapter 5.o=IBM. o=ibm. 17.ou=SWG.o=IBM.ou=users.ou=SWG.c=US cn: maximousers Refer to “Synchronizing data” on page 156 for synchronization tasks you will have to complete post installation if you choose to customize your schema.c=US member: uid=maxadmin.c=us userPassword: maxadmin uid: maxadmin objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxadmin cn: maxadmin dn: uid=mxintadm.c=us userPassword: mxintadm uid: mxintadm objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: mxintadm cn: mxintadm dn: uid=maxreg.o=IBM.ou=SWG.o=IBM.ou=users. o=ibm. and then click Next. JMS DataSource name A JMS server requires a DB2 data repository to be configured to maintain messages.ou=SWG. Select whether the JMS datastore should be persisted. Here is an example of the default add on ldif data you would have to modify and import into your LDAP repository if you elected to customize the schema and create your own users manually. o=ibm.o=IBM. enter the following information.ou=users.If you have elected to create users manually. dn: uid=maxadmin.ou=groups.ou=SWG.ou=users. Enter the name of the database to be used by JMS.ou=SWG.c=US member: uid=maxreg. o=ibm.c=us objectClass: groupofnames objectClass: top member: uid=dummy member: uid=mxintadm. Tivoli Asset Management for IT installation program overview 129 .ou=SWG.c=us objectClass: groupofnames objectClass: top member: uid=dummy member: uid=maxadmin.ou=users.ou=users. o=ibm.c=us userPassword: maxreg uid: maxreg objectClass: inetorgperson objectClass: top objectClass: person objectClass: organizationalPerson sn: maxreg cn: maxreg dn: cn=maxadmin. you should deselect this option.

19. Note: The JMS DataStore can only be created as a DB2 database. From the Maximo panel. Host name Enter the fully qualified host name of the server hosting the JMS datastore. enter the following information. and then click Next. Password Enter the password for the User ID used to access the database server. The next several steps of this Tivoli Asset Management for IT installation procedure assumes you are allowing the Tivoli Asset Management for IT installation program to configure the JMS implementation to persist messages. Port Enter the port used to access the database server. This server will be used to send workflow and process notifications. Select the installation folder Select the folder where Maximo will be installed. 18. User ID Enter the user ID used to access the database server. From the DB2 Database Server Configuration panel.p12 keystore. This field can be left blank. C:\IBM\maximo is the default value. Do not persist JMS messages Select this option if you do not want the Tivoli Asset Management for IT installation program to set the JMS implementation to persist messages automatically. Default for all platforms is 50000. If you later decide that you would like to persist JMS messages. you will have to configure the JMS implementation manually. Default for all platforms is mxsibusr. Database name Enter the name of the database serving as the JMS datastore. 130 Installation Guide for IBM WebSphere Application Server: . Refer to “Manually creating a datasource for the persistence store” on page 121 for more information. From the WebSphere keystore file panel. and then click Next.Persist JMS messages Select this option of you want the Tivoli Asset Management for IT installation program to set the JMS implementation to persist messages. The path you specify must not contain spaces. 20. SMTP server Enter the mail server configured to work with Tivoli Asset Management for IT. navigate to where you copied the trust. enter the following configuration information. Default for all platforms is maxsibdb. and then click Next.

select the type of shortcut you would like to arrange for Tivoli Asset Management for IT. Chapter 5. and it will use the configuration values stored in the maximo.host v mxe. The relevant properties are: v mail. Run the configuration step now Tivoli Asset Management for IT will be configured when you select this option and press Next. Admin E-Mail Enter the E-mail address of the person assigned to the role of Tivoli Asset Management for IT Administrator This field is optional. You can execute the configuration steps outside of the Tivoli Asset Management for IT installation program by using the taskrunner utility. and then click Next. This address will be used for workflow notifications. The Tivoli Asset Management for IT installation program is used to complete three tasks: gathering information about your Tivoli Asset Management for IT deployment and configuration. and then allow you to run the configuration step at a later date.adminEmail 21. and performing configuration tasks using the values you have specified. This field can be left blank. By selecting Do not run the configuration steps now. the taskrunner utility can be run again after the error conditions have been rectified. 22. If you choose to not configure optional properties at this time. Tivoli Asset Management for IT installation program overview 131 . you can instruct the Tivoli Asset Management for IT installation program to gather your configuration information and copy Tivoli Asset Management for IT files to your local system now.properties file. From the Run Configuration Step panel.smtp.properties file to configure Tivoli Asset Management for IT. The taskrunner utility will resume the install at the point where the last successfully completed task was recorded in the previous attempt. located in the <TAMIT_HOME>\scripts directory. <TAMIT_HOME>\scripts\taskrunner In the event of an installation failure. Do not run the configuration step now You will have to configure Tivoli Asset Management for IT after you have completed the Tivoli Asset Management for IT installation task.admin v mxe. select when you would like to configure Tivoli Asset Management for IT. From the Choose Shortcut Folder panel. copying files to your local system.workflow. and then click Next. Simply run the taskrunner utility from the command line. you can configure them in the Tivoli Asset Management for IT user interface using the System Properties application.Workflow Admin E-Mail Enter the E-mail address of the person assigned to the role of Tivoli Asset Management for IT Workflow Administrator. The configuration values that you enter are stored in the <Maximo_Home>\applications\maximo\properties\ maximo.

button to select another location to create Tivoli Asset Management for IT shortcuts. review the installation information presented. 23. and then click Install. Create Icons for All Users Select this option if you would like Tivoli Asset Management for IT desktop icons to appear on the desktop for all system users. 25. 24. In the Start Menu Select this option to create shortcuts for Tivoli Asset Management for IT in the Start menu. Manually configuring the VMMSYNC cron task for Microsoft Active Directory This topic details how to manually configure the VMMSYNC cron task for Microsoft Active Directory. In an existing Program Group Select this option and choose the name of an existing program group to store Tivoli Asset Management for IT shortcuts. ensure that you have added the Tivoli Asset Management for IT URL to the trusted sites Web content zone and disable the option of requiring server verification for all sites in the zone.. From the Pre-Installation Summary panel. review the information you have provided to the Tivoli Asset Management for IT installation program. From the Input Summary panel.. it will exit. Don’t create icons Select this option if you do not want any Tivoli Asset Management for IT shortcuts created. The installation task will begin. VMMSYNC is the cron task that schedules the synchronization between Tivoli Asset Management for IT and the LDAP repository and is configured through the Maximo Console. Once the Tivoli Asset Management for IT installation program has completed installation and configuration tasks. click Done. Use the Previous button to return to previous panels to make any changes. This procedure is required if you use Microsoft Active Directory 132 Installation Guide for IBM WebSphere Application Server: . From the Install Complete panel. and then click Next. Other Select this option and use the Choose. On the Desktop Select this option to create shortcuts for Tivoli Asset Management for IT on the desktop. In order to use the Start Menu shortcut in conjunction with Internet Explorer.In a new Program Group Select this option and enter the name of a new program group if you would like to create Tivoli Asset Management for IT shortcuts in a new program group. Do not select this option. Logs can be found at <TAMIT_Home>/logs. Progress can be monitored by viewing messages displayed above the progress bar. In the Quick Launch Bar This option should not be used. Selecting this option will not create a shortcut in the Quick Launch bar.

dc=itsm.vmm. refer to “Synchronizing data” on page 156. For more general information about configuring the VMMSYNC cron task.DefaultVMMSyncAdapter SynchClass psdi. <basedn>ou=Groups.dc=com SynchAdapter psdi.VMMSynchronizer UserMapping Edit the <basedn> entry of the XML file.as your directory server. Navigate to the Cron Task Setup application by selecting Go To > System Configuration > Platform Configuration > Cron Task Setup.dc=com</basedn> UserSearchAttribute Uid You will have to click the arrow located in the header of the Cron Task Parameters table to view all parameters. To modify the VMMSYNC cron task for Microsoft Active Directory. The steps below detail how to reconfigure the VMMSYNC cron task for use with Microsoft Active Directory.dc=itsm.vmm.security.security.dc=itsm. <basedn>ou=Users. Credential Password for wasadmin in LDAP GroupMapping Edit the <basedn> entry of the XML file. 2.ou=SWG.ou=SWG. Tivoli Asset Management for IT installation program overview 133 . Log into the Maximo console as maxadmin. Click the save icon. 3.ou=SWG.ou=Users. The updated parameters will be used at the next scheduled synchronization. 4.dc=com</basedn> GroupSearchAttribute cn Principal cn=wasadmin. Chapter 5. complete the following steps: 1. Click the VMMSYNC cron task and configure the following values: Active? Enable the Active? option by selecting the checkbox.

134 Installation Guide for IBM WebSphere Application Server: .

the installation program prompts you to uninstall that version and invoke a manual install of the latest IBM Agent Controller. Summary of situations requiring a manual installation of the IBM Agent Controller v Using another supported software v That software has its own log parser v You have a previous version of IBM Agent Controller installed already For more information about invoking the launchpad see.3. In order to import log and trace data. Examples of supported distributions include: v Red Hat Linux Advanced Server v2.2.0 and v4. IBM Agent Controller supported platforms This topic supplies a list of the supported platforms for installing IBM Agent Controller. if you are using another supported software like Oracle. The IBM Tivoli middleware installer installs the Agent Controller during the installation of the following: v IBM Tivoli Directory Server v WebSphere Application Server v DB2 In some circumstances you must manually invoke the IBM Agent Controller installation program using the launchpad application. If you have a previous version. v5. 2008 135 .4 and 2. 2007.6 kernel. You can install IBM Agent Controller on the following supported platforms: v AIX v5. This is also the case if you have a previous version of an Agent Controller installed. IBM Agent Controller overview The IBM Agent Controller (AC) imports log and trace information from remote systems to the IBM Log and Trace Analyzer application. V5R3 and V5R4 on iSeries® Linux 2. or if your product has its own log parser.0 v SuSE Linux Enterprise Server (SLES) v9 on Intel IA32 v SuSE Linux Enterprise Server (SLES) v8 on zSeries (32-bit) v Windows 2000 Server or Advanced Server (SP4) on Intel IA32 © Copyright IBM Corp. For instance. V1R5. Microsoft SQL. then IBM Agent Controller has to be manually installed on that remote location in order to import log and trace data.1 on Intel IA32 v Red Hat Enterprise Linux AS release 3 on PowerPC (64-bit) v Red Hat Enterprise Linux (RHEL) v3.Chapter 6. and 5L on PowerPC® (32-bit) v z/OS® V1R4. Installing the IBM Agent Controller and the list of supported platforms. the IBM Agent Controller must be installed and running on every server from which you wish to retrieve log file information using the log and trace analyzer. V1R6 and V1R7 on zSeries® (32-bit) v OS/400® V5R2. Microsoft Active Directory.

0 on SPARC Planning for serviceability Serviceability refers to problem analysis from a central point using data collected from a wide range of sources. such as Operational Management Products (OMPs). You can customize the serviceability provided by Tivoli Asset Management for IT by choosing where to deploy instances of the IBM Agent Controller which work with the Log and Trace Analyzer hosted on the IBM WebSphere Network Deployment manager. IBM Agent Controller gathers information from log files residing on remote servers and passes it on to the Log and Trace Analyzer. during normal usage of Tivoli Asset 136 Installation Guide for IBM WebSphere Application Server: .v v v v v v Windows 2000 Professional (SP3) on Intel IA32 Windows Server 2003 Standard and Enterprise (SP1) on Intel IA32 Windows Server 2003 Enterprise x64 Edition (SP1) on EM64T (64-bit) Windows XP Professional (SP2) on Intel IA32 HP-UX v11. IBM Agent Controller TADDM Log and Trace Analyzer IBM Agent Controller WebSphere Application Server Node WebSphere Deployment Manager IBM Agent Controller Database IBM Agent Controller Directory Server IBM Agent Controller WebSphere Application Server Node IBM Agent Controller Operational Management Product Figure 4. You can choose to install IBM Agent Controllers on other resources.Log files for the Tivoli Asset Management for IT installation program can be found in <TAMIT_HOME>\logs. By default. v11i on PA-RISC Sun Solaris v8. After installation. the IBM Agent Controller agent is installed on machines where you have run the Tivoli middleware installer. and the database server. from which you want to retrieve log files. or other nodes located on the IBM WebSphere Network Deployment cluster.0. v9. and v10. Tivoli Asset Management for IT Serviceability Log files for the Tivoli middleware installer can be found in the workspace directory you defined when you ran the installation program. the directory server. which includes the application server.

Start the installation program by running setup. 11.linux_ia32_V7. use a Windows logon ID with Administrator authority.0 or later and click Next.3.3. 8. you might find it useful to examine the application server logs generated for the MXServer application server. Before installing the Agent Controller. Log in.1 directory on the Tivoli Asset Management for IT 7. The following list identifies the installation files in the directory: For platform Windows on Intel IA32 Windows on EM64 AIX Linux on Intel IA32 Installation files ibmrac. On Windows operating systems. Change the directory to the directory where you unzipped the installation files for the appropriate operating system. read the terms of the license agreement and. The following list identifies the options: Option This computer only Description Allows only the local host to access the Agent Controller.0. 9. The Agent Controller installation files are located in the Rational-AgentController_7. 5. IBM Agent Controller overview 137 . if you agree with the terms. Installing IBM Agent Controller Installing the IBM Agent Controller allows you to import log and trace information from remote systems and view the information using the Log and Trace Analyzer.1 DVD. 1.1. 10.win_em64t_V7.3. On the license agreement page.aix_powerpc_V7. Click Next.exe (Windows) or setup. Chapter 6. On the Access List page.zip ibmrac.Management for IT.0. 7. specify which hosts can access the Agent Controller. if you have a previous version of the Agent Controller installed. 4.3.1. Close all Eclipse platforms. Locate the installation files. On Linux and AIX systems. Type or browse to the location where the Agent Controller should be installed and click Next.zip 2.win_ia32_V7.3.0. click I accept the terms of the license agreement and click Next.bin (Linux and AIX) A welcome page is displayed. use the root ID. Extract the installation files to the following directories: For platform Windows on Intel IA32 Windows on EM64 AIX Linux on Intel IA32 Directories <temp_dir>\win_ia32 <temp_dir>\win_em64t <temp_dir>/aix_powerpc <temp_dir>/linux_ia32 3.zip ibmrac. click V6. On the Select the version of WebSphere Application Server page. You must accept the terms of the license agreement to continue the installation.0. 6.1.1.0. you must uninstall the previous version.zip ibmrac.

for example. For platform Linux Installation files The Agent Controller server requires the directories of the JRE that contain executable libraries. Refer to the Agent Controller documentation for instructions to complete this task. to be added to the library path environment variable. security is enabled by default but changeable. the Agent Controller system service is started automatically. security is enabled.so. Allows any client to access the Agent Controller. If security is disabled. If security is enabled. type a comma-separated list of users that can connect to the Agent Controller. 12.Option Specific computers Any computer Description Allows a specified list of clients to access the Agent Controller. specify the security setting. 13. If you selected the other options on the Access List page. communication are not encrypted and access control is limited to the defined host list. on the Security page. 14. Click Next. If you selected Any computer in the previous step. These user are required to authenticate to use the tool. Starting IBM Agent Controller On Windows operating systems. On the Security page. LDAP. Set the appropriate environment settings. LD_LIBRARY_PATH=/opt/IBMJava2-141/jre /bin/classic:/opt/IBMJava2-141/jre/bin: $LD_LIBRARY_PATH export LD_LIBRARY_PATH 138 Installation Guide for IBM WebSphere Application Server: . On Linux and AIX operating systems the Agent Controller must be started manually. complete the following steps: 1. selecting the Any computer option requires that you disable the Agent Controller user authentication after the installation process is complete. To disable security. Click Finish to close the installation program. Note: If you use an authentication mechanism. The following example shows the path variable setting based on default installation locations of the JVMs supported for the Linux platform. Review the summary information and click Install. 15. The JRE you specify is used by the Agent Controller for launching Java applications. This option is the default. such as libjvm. You must enter a path that matches the path for the JRE you specify when you installed the Agent Controller. refer to the Agent Controller documentation. Click Next. To start the Agent Controller on a Linux or AIX operating system.

The JRE you specify is used by the Agent Controller for launching Java applications. the LDR_CNTRL environment variable needs to be set to USERREGS to work properly with the Agent Controller. use the Windows Services dialog.so. and stop IBM Rational Agent Controller. To set this variable. Change to the installation location bin directory and run the following command:. such as libjvm. to be added to the library path environment variable. do the following: v On Linux or AIX systems. change to the installation location bin directory and run the following command: . which is part of the Control Panel.sh v On Windows system.sh To stop the Agent Controller process. IBM Agent Controller overview 139 . LIBPATH=/usr/java14/jre/bin:/usr/java14 /jre/bin/classic: $LIBPATH export LIBPATH 2. Chapter 6.For platform AIX Installation files For certain JVMs.sh script: export LDR_CNTRL=USERREGS In addition. run the following command before running the RAStart./RAStart. The following example shows the path variable setting based on default installation locations of the JVMs supported for the AIX platform./RAStop. You must enter a path that matches the path for the JRE you specify when you installed the Agent Controller. the Agent Controller server requires the directories of the JRE that contain executable libraries.

140 Installation Guide for IBM WebSphere Application Server: .

Backup Middleware Servers and Administrative Workstation Create backups for impacted J2EE. running database scripts that load the process solution content into the Maximo database. Installation artifacts are the files and content that are installed into your Tivoli Asset Management for IT environment to enable the services management functionality of the Process Manager Product or Integration Module. accessible from the launchpad. The actual middleware servers whose login information is required depend on the process solution package being installed. optional sample data can be installed. Before using the process solution installation program When you perform a deployment operation using the process solution installation program. database. when you install directly from the product DVD. and directory servers before you deploy a process solution package using the process solution installation program. You must know the administrative user IDs and passwords for the impacted middleware servers. Process solution packages A process solution package is a self-contained ZIP file of installation artifacts and deployment logic that can be deployed using the process solution installation program. Additionally. © Copyright IBM Corp. Review the following steps before invoking the process solution installation program. database. 2007. and directory middleware servers. you are running actions that modify the configuration and content of your J2EE. The deployment logic are the actions that are carried out in order to deploy the process solution into the Tivoli Asset Management for IT environment. Process solutions can be partitioned into Process Manager Products and Integration Modules. The process solution installation program ensures that any required login information is specified before continuing with the deployment operation. Typically. 2008 141 . Process solution package installation These topics provide information about installation of packaged process solution.Chapter 7. Note: Separately deploying a process solution package is only needed if you run the PSI install outside the launchpad. for instance. Process solution packages can be installed and deployed through the process solution installation (PSI) wizard. Have Middleware Login Information Available The process solution installation program requires access to middleware servers in order to automate the deployment of the process solution package. and adding users and groups for security. these actions include building and deploying J2EE applications.

A progress panel will inform you of the deployment progress of the installation. Leave the Package Options box unchecked to have the EAR files redeployed and Maximo database updated by the process solution installation program and click Next. the process solution installation programs attempt to connect to the middleware servers using the middleware login information that you specify. and then click OK. Read the license information and select I accept the terms in the license agreement if you agree with the terms. The system is checked to insure that the package has not already been deployed. a package options panel is displayed that details the deployment options that the package supports. 7. From the Pre-Install Summary panel. After the credentials have been verified. At this point. Select a language for your installation. From the Launchpad. enter the credentials for which you are being prompted.Ensure Middleware Servers Are Started Start any impacted middleware servers before running the process solution installation programs Before the actions associated with a package are executed. The process solution installation program license agreement window is displayed. Click Next. 6. The Process Solution Installation Install Anywhere Installer executes on the Maximo administrative workstation. In this case. The process solution installation program then performs a system check to ensure that all system requirements necessary for the package to be installed are present. 5. Installing process managers using the process solution installation wizard Complete the following steps to install a process solution package into Tivoli Asset Management for IT using the process solution installation wizard: 1. 3. the process solution installation programs display error messages and do not continue on with the deployment actions. the process solution installation wizard validates the credentials by connecting to the middleware servers using the supplied credentials. 142 Installation Guide for IBM WebSphere Application Server: .1 package. Enable Tivoli Asset Management for IT License for usage. 4. From the Middleware Login Information panel. Click Next to advance. From the Package Validation Results panel. the PSI package selected is a base install of the Tivoli Asset Management for IT 7. the process solution installation program begins the package installation process. The launch script is deployed and configured by the Tivoli Asset Management for IT installation program. No post-installation configuration is required. review and verify the information displayed. The process solution installation program performs a series of validation checks to verify that the package you selected is valid. and then click Next. Once you have entered the requested user IDs and passwords. and then click Next. and then click Next. 2. review and verify the information displayed. launch the process solution installation program by clicking the link under 3. If the targeted middleware servers are not started or if connections to the middleware servers cannot be established with the specified middleware login information.

a ″. Note that you might discover numerous (10-20) package log files generated for any particular package installed. click Done to exit the process solution installation wizard. These log files are typically vital to the proper debugging of package issues. provided there was no error output (or there was ONLY error output). a message is displayed for the step that failed. .out″ and ″. The deployment of the Process Solution Package you were installing has already completed and the progress bar can be safely ignored. from the Package Successfully Deployed panel.err″ file. Process solution package installation 143 .out files contain the contents of the Standard Output stream as output by the external command. refer to the log files kept in the following locations: Table 21. When the installation has completed successfully.err files contain the contents of the Standard Error stream. Process solution installation logs If you experience any problems or encounter any error messages during the use of the process solution installation program.8. . It is normal for one to be blank. you see an installation progress bar displayed briefly after you click Done. both with the same pre-extension filename. In some cases. The Process Solution Installation Wizard is actually terminating and no installation activities are being performed. Log type Package log Description Location These are log files containing <TAMIT_HOME>\solutions\ the StdOut/StdErr output of logs\<PACKAGE_NAME>\ external commands launched by the package as it is processed by the Deployment Engine. In general. Chapter 7. logs will have two parts. If there is a package failure.

log C:\Program Files\IBM\Common\acsi\ logs\<USERNAME>\ de_trace. if your WebSphere Application Server was installed in ″C:\IBM\WebSphere\ AppServer\″. if you installed under the user name ″Administrator″. such as database connections. <WAS_HOME>\profiles\ <PROFILE>\logs\ AboutThisProfile.log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ SystemOut. This runtime has its own logging system.Table 21. and other failures experienced by the WebSphere Application Server in its day-to-day running. the logs would be found under: C:\Program Files\IBM\Common\acsi\ logs\Administrator\ de_msg.log So for instance. These logs are often helpful in the diagnosis of errors in particular EAR files or other back-end operations.txt 144 Installation Guide for IBM WebSphere Application Server: .log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ SystemErr.txt <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ startServer.log <WAS_HOME>\profiles\ <PROFILE>\logs\ <SERVER_NAME>\ stopServer. and your server name was ″server1″. you would provide the following logs:: C:\IBM\WebSphere\ AppServer\profiles\ AppSrv01\logs\ AboutThisProfile.log So for instance. PSI utilizes the IBM technology as the means to install and keep track of installed packages.log WebSphere Application Server Logs These are logs kept of connections. (continued) Log type Solution Install/Deployment Engine Logs Description These are logs kept by the IBM Solution Installer/Deployment engine runtime. your profile name was ″AppSrv01″. exceptions. Location C:\Program Files\IBM\Common\acsi\ logs\<USERNAME>\ de_msg.

Chapter 7. If this automated deployment happens to fail.traceout C:\IBM\SMP\wasclient\ logs\wsadmin.traceout <TAMIT_HOME>\ wasclient\logs\ wsadmin.log <TAMIT_HOME>\ wasclient\logs\ CTGIN_wsadmin.valout Tivoli Asset Management for There are also a few logs IT Logs kept by Tivoli Asset Management for IT. Process solution package installation 145 . the logging information would be written to the file: C:\IBM\SMP\maximo\ tools\maximo\log\ updatedb20070419170607. WAS Thin Client Logs The WAS thin client is the mechanism by which the process manager packages communicate with the WebSphere Application Server. the exact actions the Thin Client took and the associated responses from the WebSphere Application Server are stored in logs. It is useful to have a log comprised of only the information related to the success or failure of current package installation to facilitate problem determination.valout So if your Tivoli Asset Management for IT install location were ″C:\IBM\SMP″. and the package executed the ″UpdateDB″ command on April 19th at approximately 5:06:07PM. (continued) Log type Description Location <TAMIT_HOME>\maximo\ tools\maximo\log\ updatedb<TIMESTAMP>. and failure of a few back-end commands provided by Tivoli Asset Management for IT. success.log So if your Tivoli Asset Management for IT install location was ″C:\IBM\SMP″. These are useful in tracking the progress. It is a good practice to rename existing logs before attempting a package install.traceout C:\IBM\SMP\wasclient\ logs\wsadmin. the following log files would contain the Thin WAS Client tracing information: C:\IBM\SMP\wasclient\ logs\ CTGIN_wsadmin.traceout <TAMIT_HOME>\ wasclient\logs\ wsadmin.Table 21.

146 Installation Guide for IBM WebSphere Application Server: .

Install Tivoli Integration Composer.1. The separate Integration Composer DVD. as described in this section. Installing Integration Composer with the Integration Composer DVD You can use theIBM Tivoli Integration Composer DVD provided with Tivoli Asset Management for IT to install Integration Composer. When installing Integration Composer. complete the steps that follow. is the preferred option for installation. Do not use this installation option if you have a 64-bit operating system. use the Integration Composer DVD provided with the Tivoli Asset Management for IT package. You do not need to remove the previous version first. 1. To avoid losing any of your current data.1 will upgrade the previous version of Integration Composer. and. 2007. The installation guide on the Integration Composer DVD provides important installation information. will upgrade the previous version of Integration Composer.Chapter 8.1. Note. © Copyright IBM Corp. which explains in detail how to install Integration Composer. Please refer to this guide for installation instructions. which provides documentation in addition to an installation program. Installing Integration Composer with the Launchpad This section explains the procedure for installing Integration Composer with the Launchpad. or the separate Integration Composer DVD can be used to install it. Upgrade note: Installing Integration Composer 7. To install Integration Composer with the Launchpad. Upgrade note: Installing Integration Composer 7. You can use the IBM Tivoli Asset Management for IT Launchpad. To install Integration Composer. IBM Tivoli Asset Management for IT includes two DVDs for installing Integration Composer. Insert the Launchpad DVD into the server where you will install Integration Composer. The other installation option is to use one of the Integration Composer installation DVDs provided with the IBM Tivoli Asset Management for IT package. launch the Integration Composer installation program by clicking the link under 3. IBM Tivoli Integration Composer must be installed on a separate server.1. To avoid losing any of your current data. You do not need to remove the previous version first. back up your Integration Composer data\dataschema and data\mappings directories before installing. 2008 147 . however. from the Launchpad. Integration Composer installation The IBM Tivoli Asset Management for IT Launchpad can be used as an interface for installing Integration Composer. there are two options. one for Windows and one for UNIX. back up your Integration Composer data\dataschema and data\mappings directories before installing. This DVD includes an IBM Tivoli Integration Composer Installation Guide. that you cannot use the Launchpad to install Integration Composer if you have a 64-bit operating system.

The error states: Windows error 3 occurred while loading the Java VM. On the IBM Tivoli Integration Composer window. type the directory where IBM Java SDK 5. Later.) Then click Next. Then click Next. depending on the type of database you chose in the previous step. select your language from the drop-down list at the bottom and click OK. On the Database Login Information window. 6. Table 22. select one of the following options and click Next: v Yes. disable software updates 148 Installation Guide for IBM WebSphere Application Server: .0 Service Release 5 currently installed on the Integration Composer server. This Database Login Information window is where you define the parameters for connecting to the Maximo database. an error window displays and the installation ends. The following table defines the fields that the installation program displays for the supported databases. To correct the problem. 3. On the Introduction window. 4. this is the session identifier (SID) for the database. 5. The Database Login Information window is displayed. On the Update Software Instances window. accept the default location or type a file path to specify the directory where you want to install Integration Composer. Note: If you do not have the prerequisite IBM Java SDK 5. On the Database Type window.2. (Alternatively. Login specifications for the Maximo database Field Database Server Name Port Number Database Name (SID) or Database Name Database Username Database/Schema Owner Description Name of the server on which the Maximo database resides Port number of the server on which the Maximo database resides For Oracle databases. The fields displayed in this window vary slightly. install IBM Java SDK 5. On the Choose IBM SDK Location window. review the information and click Next. On the Choose Install Folder window.0 Service Release 5 is located. select the database you intend to use with Integration Composer and click Next. Tip: Make note of the values that you specified here. that is.0 Service Release 5 on your operating system and run the setup command again. when you launch Integration Composer. type login specifications for the database and click Next. the database instance For SQL Server or IBM databases. this is simply the name of the database Valid user name for signing in to the Maximo database Database or schema owner 7. or click Choose to browse and select the directory. use the values entered in these fields to define connection parameters for the Maximo database. 8. you can click Choose to browse and select the location you want.

don’t disable software updates If you select this option. when Integration Composer imports data into the Maximo database. click Done. Integration Composer updates existing software records. On the Begin Installing window. click Install to begin installing Integration Composer. On the Preinstallation Summary window. when Integration Composer imports data into the Maximo database.If you select this option. 9. Chapter 8. 10. v No. the Installation Complete window is displayed. you can click Cancel to end the installation. review the installation details and click Next. IBM Tivoli Integration Composer installation 149 . 11. When installing is finished. On the Installation Complete window. The Installing Integration Composer progress window displays during installation. Integration Composer inserts or deletes software records but does not update software records. This option is preferred. Note: If necessary.

150 Installation Guide for IBM WebSphere Application Server: .

use the Tivoli Asset Management for IT language pack installation program before you perform post installation steps described in Chapter 10.1 4. start that server or service. Because language pack installation can several hours to complete. Also. You cannot change the base language at a later time. Important: If you plan to add language support to Tivoli Asset Management for IT. you can add language support to Tivoli Asset Management for IT user interface using the Tivoli Asset Management for IT language pack installation program. The language pack installation program will first uninstall the base and additional languages installed by the process solution installation wizard from the failed installation attempt. decide which additional languages you will need prior to starting the language pack installation. Each additional language selected will increase the amount of time to complete the installation will take. complete the following steps: 1. click the Tivoli Asset Management for IT Language Pack installer link under 2. To use the Tivoli Asset Management for IT language pack installation program to install the Tivoli Asset Management for IT language pack. From the Base Language panel. This is not necessary and only increases the installation time. 2007. 2. © Copyright IBM Corp. and perform a reinstall. Ensure all Tivoli Asset Management for IT middleware servers and services are running. This choice is only for use during the installation and its selection will not affect the languages being installed. 6. Tivoli Asset Management for IT language pack installation program overview After you have successfully deployed Tivoli Asset Management for IT. “Tivoli Asset Management for IT post installation tasks. MXServer must be started prior to running the Tivoli Asset Management for IT language pack installation program. select a base language to be used with Tivoli Asset Management for IT. 2008 151 .” on page 153. click Next. From the Welcome panel. Install IBM Tivoli Asset Management for IT 7. 3. Login as Administrator on the Tivoli Asset Management for IT administrative system. Installing the language pack This procedure provides task information for installing the Tivoli Asset Management for IT language pack. and then click OK. This is the only opportunity you will have to select a base language. If you encounter a failure resulting from an inactive Tivoli Asset Management for IT middleware server or service. Select a language for the install. do not add as an additional language the language you select as your base.Chapter 9. and then rerun the language pack installation program. 5. and then click Next. On the launchpad.

select 0 or more additional languages to be supported. and then click Next. 8. shortcut elements appearing in the Tivoli Asset Management for IT UI. you might still encounter instances in the Tivoli Asset Management for IT UI where items are displayed in the language you identified as the base language of the machine. menu choices. Doing so would be redundant. review the information and then click Next. This problem is a known limitation and does not indicate that the Tivoli Asset Management for IT language pack installation failed. click Install. for example. in practice.7. While no error will occur during installation. From the Pre-install Summary Panel. From the Additional language selection panel. 9. 152 Installation Guide for IBM WebSphere Application Server: . From the language selection summary panel. In some cases. You are not prevented from selecting the language you specified in the Base Language panel as an Additional Language. and you set the locale or your machine to a language that was installed as an additional language. only display in the base language designated or in English only. Even if you added additional languages through the language pack installation program. do not specify the base language as an additional language.

Tivoli Asset Management for IT users and groups User wasadmin maxadmin (maxadminusr for MS Active Directory) mxintadm maxreg maxadmin maxadmin Groups The default password for each user ID is the same as the User Name (for example. To sign in. use the Tivoli Asset Management for IT language pack installation program before you perform these post installation steps. there are several data configuration tasks you must complete prior to using Tivoli Asset Management for IT.” on page 151 for more information about the Tivoli Asset Management for IT language pack installation program.Chapter 10. maxadmin is both the user name and default password).” on page 151 Important: If you plan to add language support to Tivoli Asset Management for IT. Note: User names and passwords are case sensitive. Tivoli Asset Management for IT contains the following default user IDs. “Tivoli Asset Management for IT language pack installation program overview. Tivoli Asset Management for IT post installation tasks There are several post installation tasks that need to be completed following a successful Tivoli Asset Management for IT deployment. Navigate to the Tivoli Asset Management for IT log in URL. © Copyright IBM Corp. The default user names and passwords are lowercase. which are members of the specified security group: Important: Before you begin this procedure. 2. complete the following steps: 1. v “Initial data configuration” v Chapter 9. 2007. Open a browser window. Signing in using a default user ID User management is managed though the directory server you have configured to use with Tivoli Asset Management for IT. Refer to Chapter 9. 2008 153 . When first installed. ensure you have the following users and groups created: Table 23. “Tivoli Asset Management for IT language pack installation program overview. Initial data configuration Once you have successfully installed and configured Tivoli Asset Management for IT components.

3. Click New Row. Click Save. The software displays an empty start center. Open the Organizations application by selecting Goto → Administration → Organizations. 4. 3. 2. Open the Currency Code application for Users by selecting Goto → Financial → Currency Code. Create currency codes You must define a currency code for an organization. Enter an organization name in the Organization field. To define an organization. 8. Enter the base currency you defined in the Base Currency 1 field. USD. 154 Installation Guide for IBM WebSphere Application Server: . 6. complete the following steps: 1. Enter the default item status of PENDING in the Default Item Status field. For example. 3. Enter COMPANY in the Type field. Enter the user name maxadmin (lower case). 10. ENGLENA. Enter a currency name. For example. 4. 5. For example. complete the following steps: 1. For example. Open the Sets application for Users by selecting Goto → Administration → Sets. Click the New Organization icon in the toolbar. for example. 2. for example. 9. 4. Enter the password maxadmin (lower case) and click Enter. Enter the item set you defined in the Item Set field. Enter a company set name. Click New Row. Create an organization You must define at least one organization for Tivoli Asset Management for IT. 6. To define a currency code for an organization. Enter an item set name. Enter the company set you defined in the Company Set field. 3. USD.For example: http://hostname:<port>/maximo. 5. 4. Click Save. For example. IT Comps. 8. IT Items. B901. Create item and company sets You must define item and company sets for an organization. 2. Click New Row. IT Comps. 7. for example. 7. Click on Sites tab. Click New Row. To define a currency code for an organization. Enter ITEM in the Type field. IT Items. complete the following steps: 1. Enter a site name in the Site field.

complete the following steps: 1. For example. For example. Select Active. 1234. Click New Row. 7. Click Save. complete the following steps: 1. 2. To create a general ledger account. Open the Users application by selecting Goto → Security → Users. 9. Open the Database Configuration application by selecting Goto → System Configuration → Platform Configuration → Database Configuration. To create a general ledger account component. Click New Row. 7. Enter a type for the component. From the Clearing Account field. 4. 4. 3. 13. Select your General Ledger Account. 5. For example. For example. Select GL Account Configuration from the Select Action drop-down menu. MYCOMPONENT 5. 3.11. Click New Row. ALN. Open the Organizations application by selecting Goto → Administration → Organizations. 2. 2. Open the Chart of Accounts application by selecting Goto → Financials → Chart of Accounts. 11. Select GL Component Maintenance from the Select Action drop-down menu. 12. Create default insert site You must create a default insert site for Tivoli Asset Management for IT. 10. click ENGLENA. Create a general ledger account You must create a general ledger account for Tivoli Asset Management for IT. For example. 6. Enter a numerical length for the component. 6. Chapter 10. 5. To create a default insert site. Click Save. Click OK. Search for maxadmin and then select it to open the record for maxadmin. Add a GL Component value and then click OK. 8. select the General Ledger Account you just created. Click Save. Enter a component name in the Component field. complete the following steps: 1. Click the organization name you created. Click on the name of your organization to select it. Create a general ledger account component You must create a general ledger account component for Tivoli Asset Management for IT. Tivoli Asset Management for IT post installation tasks 155 . For example. ENGLENA.

For example. 14. 9. 10. For example. Set the Work Type as UR. Set Complete Status as COMP. Sign out as MAXADMIN. 2. 5. 6. complete the following steps: 1. 6. 5. Set the Work Type as AR. B901. 12. For example. 2. 1. 156 Installation Guide for IBM WebSphere Application Server: . Open the WebSphere Admin Console and restart the MXServer application server. Click Save. If you receive an error message that indicates that the record is being updated by another user. Select PMCFGWO as the Work Order class. 3. To create a Work Type. Set Complete Status as COMP. Search for the organization you created. even though you have granted the MAXADMIN group permission to create start center templates. 13. 15. Click Save. the actions are not visible until you sign in again. Click New Row. Create a Work Type You must create a Work Type for Tivoli Asset Management for IT. 7. Click on the name of the organization to open the record for that organization. for example. Sign in as MAXADMIN. and the Tivoli Asset Management for IT VMM crontask. Click OK. Open the Organizations application by selecting Goto → Administration → Organizations. 11. B901. Synchronizing data The scheduled synchronization of data that occurs between LDAP repositories and Tivoli Asset Management for IT is governed by the federated repositories managed by VMM in WebSphere. Enter a the site you created earlier in the Default Insert Site field. Enter a the site you created earlier in the Storeroom Site for Self-Service Requisitions field. Select Work Order Options → Work Type from the Select Action drop-down menu. 16. you must sign out and sign in again in order to see the changes. Set Start Status as INPRG. Set Start Status as INPRG. Select PMCFGWO as the Work Order class. ENGLENA. log out as MAXADMIN and then log back in. 4.3. Signing out and signing in When you make changes to a security group that your user ID is a member of. 8. Click New Row. 4.

Locate the VMMSYNC cron task.For specific information on configuring the VMMSYNC cron task for Microsoft Active Directory.ou=SWG. and hit Enter.o=IBM. navigate to Go To > System Configuration > Platform Configuration > Cron Task Setup 4. GroupSearchAttribute This value is the LDAP group object attribute used to search for groups under the configured directory sub-tree. 5. This value can be any WebSphere administrative user that has authorization to connect to the local VMM service.c=US This is the user required by the CronTask application to connect to the local VMM service. Tivoli Asset Management for IT post installation tasks 157 .security. Group Chapter 10. Uid SynchAdapter This value is the Java class that writes LDAP data to the database. 6. Ensure the following values are used for each field: Principal cn=wasadmin. In this case. enter the password for wasadmin.o=IBM.ou=SWG.security. Log into Tivoli Asset Management for IT using the maxadmin user ID. Change the following object entries: Basedn This defines the LDAP sub-tree under which the VMM Crontask will search for group objects. and click it.c=US Filter This is the VMM object class that the service uses to search for group objects in LDAP. cn UserSearchAttribute This value is the LDAP user object attribute used to search for users under configured directory sub-tree.VMMSynchronizer Group Mapping This field contains XML mapping files that map LDAP object attributes to database repository table columns. Credential This should be the password used for the Principal account.ou=users. To configure the synchronization schedule between LDAP repositories and Tivoli Asset Management for IT. ou=groups. psdi. complete the following steps: 1. psdi. 3. refer to “Manually configuring the VMMSYNC cron task for Microsoft Active Directory” on page 132.DefaultVMMSyncAdapter SynchClass This value is the Java class that connects to the VMM local service to search for required objects.vmm. Type VMM in the Cron Task field.vmm. From the Tivoli Asset Management for IT interface. Open a Web browser and point to http://hostname:9081/maximo. 2.

enable.ou=SWG.xml files should reside. Change the following object entries: Basedn This defines the LDAP sub-tree under which the VMM Crontask will search for user objects. Modifying the config. config. 3. Open the WEBSPHERE_HOME\AppServer\systemApps\isclite. it is necessary to specify the location where the resource definition files will reside in the config.ibm. To modify. First steps to using Log and Trace Analyzer Before you begin using Log and Trace Analyzer and the Log and Trace Analyzer Resource Set Generator follow the guidelines in this topic.xml file at the following location: AGENTCONTROLLER_HOME\plugins\com. Make changes to the Schedule field of the crontask if you want to change the interval.xml file would be found under the C:\Program Files\IBM\AgentController\plugins\com. By default. the crontask will perform its task every 5 minutes. Set the task to active.properties ConfigFileDir key is not already set. 158 Installation Guide for IBM WebSphere Application Server: .properties file If you have not invoked the Resource Set Generator. PersonAccount 7. This file designates where the logAnalyzerConfig. For example. ou=users.ccmdb\config directory.properties file with the path where the resource set definition files reside if the config.ccmdb\config.properties file 2. This location is used by the Log and Trace Analyzer to locate the resource definition files during the creation of a resource set.User Mapping This field contains XML mapping files that map LDAP object attributes to database repository table columns. Log and Trace Analyzer creates a configuration file called. If the ConfigFileDir key has a # symbol in front of # ConfigFileDir = d:/config. Before you begin.properties. remove the # to enable the ConfigFileDir properties key. where AGENTCONTROLLER_HOME = C:\Program Files\IBM\AgentController the logAnalyerConfig. The Log and Trace Analyzer Resource Set Generator updates the config. and set the path for the resource definition files perform the following: 1. ensure that the IBM Agent Controller (AC) has been properly installed on all of the remote systems from which you want Log and Trace Analyzer to gather information and you have completed the post installation requirements.war\config. it creates a resource set definition called the logAnalyzerConfig.ear\ PortalLogTraceAnalyzer.c=US Filter This is the VMM object class that the service uses to search for user objects in LDAP. Locate the ConfigFileDir properties key.ibm. Locations of the resource set definition files After the Middleware installer installs the AC.properties file.o=IBM.

Choose a path to save the resource definition files that the Log and Trace Analyzer Resource Set Generator creates and where you will manually copy the logAnalyzerConfig. logAnalyzerConfig. v For Windows. 3.bat (Windows) and ctxgen.2.xml files created by the Middleware installer into the directory specified for the ConfigFileDir. Set the WEBSPHERE_HOME environment variable to the directory where WebSphere Application Server is installed. Run the ctxgen command on the command line to start the Log and Trace Analyzer Resource Set Generator. edit the sample configuration files packaged with the tool. you can choose a sequential naming convention like: logAnalyzerConfig1. modify the name of the file to logAnalyzerConfigN. replace TRACE=off=disabled with ″TRACE=info=enabled.xml.xml. edit the ctxgen.xml files generated by the Middleware installer. Starting the Log and Trace Analyzer Resource Set Generator The Log and Trace Analyzer is located in a zip file in the LPCT directory of the Tivoli Asset Management for IT 7.sh (Linux) file in the bin directory where the tool is installed.sh script file by entering chmod +x bin/ctxgen. 4. Skip step 4.1 DVD media. replace set TRACE=off=disabled with set TRACE=info=enabled. After you create a configuration file perform the following: 1.zip. In order to avoid naming collision when copying the file.xml and logAnalyzerConfig2. Ensure that you manually copy the logAnalyzerConfig. Optional: To display debugging information in the standard output. Before you start the Log and Trace Analyzer Resource Set Generator. The name of the zip file is: context_file_generation_tool-AC-4.2.xml files generated by the Middleware installer to that directory.Note: If the key does not have # ConfigFileDir = d:/config then the Resource Set Generator may have already been invoked and has set the path. For example. Copying resource definition files to ConfigFileDir location Copy the resource set definition files. 4. Tivoli Asset Management for IT post installation tasks 159 . For Linux.sh at the command line. 2. modify the permissions for the ctxgen. Chapter 10. v For Linux.

160 Installation Guide for IBM WebSphere Application Server: .

program. Consult your local IBM representative for information on the products and services currently available in your area. in writing.S.S. program.A. or service may be used. Minato-ku Tokyo 106-0032. or service that does not infringe any IBM intellectual property right may be used instead. or service is not intended to state or imply that only that IBM product. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. it is the user’s responsibility to evaluate and verify the operation of any non-IBM product. 2007. these changes will be incorporated in new editions of the publication. You can send license inquiries. © Copyright IBM Corp. program. BUT NOT LIMITED TO. or service. IBM may have patents or pending patent applications covering subject matter described in this document. However. or features discussed in this document in other countries. this statement may not apply to you. Changes are periodically made to the information herein. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND. program. INCLUDING. NY 10504-1785 U. to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Any functionally equivalent product. Any reference to an IBM product.A. 2008 161 . This information could include technical inaccuracies or typographical errors. For license inquiries regarding double-byte (DBCS) information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. The furnishing of this document does not grant you any license to these patents. contact the IBM Intellectual Property Department in your country or send inquiries. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. EITHER EXPRESS OR IMPLIED. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. Some states do not allow disclaimer of express or implied warranties in certain transactions. IBM may not offer the products. services. in writing. to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. therefore.Notices This information was developed for products and services offered in the U.

the examples include the names of individuals. Furthermore. the results obtained in other operating environments may vary significantly.A. some measurements may have been estimated through extrapolation. should contact: IBM Corporation Software Interoperability Coordinator. payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice. COPYRIGHT LICENSE: This information contains sample application programs in source language. which illustrate programming techniques on various operating platforms. marketing or distributing application programs conforming to the application programming interface for the operating 162 Installation Guide for IBM WebSphere Application Server: . for the purposes of developing. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.S. You may copy. Users of this document should verify the applicable data for their specific environment. IBM has not tested those products and cannot confirm the accuracy of performance. and products. are current and are subject to change without notice. modify. This information contains examples of data and reports used in daily business operations. and distribute these sample programs in any form without payment to IBM. Any performance data contained herein was determined in a controlled environment. The information herein is subject to change before the products described become available. Dealer prices may vary. compatibility or any other claims related to non-IBM products. Therefore. subject to appropriate terms and conditions. including in some cases. their published announcements or other publicly available sources. brands. All IBM prices shown are IBM’s suggested retail prices. using. and represent goals and objectives only. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems.Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged. IBM International Program License Agreement. Actual results may vary. This information is for planning purposes only. companies. To illustrate them as completely as possible. Department 49XA 3605 Highway 52 N Rochester. Information concerning non-IBM products was obtained from the suppliers of those products. Such information may be available. MN 55901 U. or any equivalent agreement between us.

platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: © (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights reserved. If you are viewing this information softcopy, the photographs and color illustrations may not appear.

Trademarks
For trademark attribution, visit the IBM Terms of Use Web site (http://www.ibm.com/legal/us/) The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, the IBM logo, AIX, Tivoli, the Tivoli logo, and WebSphere are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Intel, the Intel logo, and Pentium are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft, Windows, the Windows logo, and Internet Explorer are trademarks of Microsoft Corporation in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others.

Notices

163

164

Installation Guide for IBM WebSphere Application Server:

Index A
Agent Controller 59 Installing 137 Starting 138 Stopping 138

D
DB2 47

I
IBM Agent Controller 59 IBM HTTP Server 57 IBM Tivoli Directory Server 52 IHS 57 installing 46 prerequisite software products 31 installing Integration Composer with the DVD 147 installing Integration Composer with the Launchpad 147 ITDS 52

M
middleware 31, 46

P
Plug-in 58 prerequisite 31

V
Virtual Member Manager VMM 60 60

W
WAS 53, 54 WebSphere Application Server Deployment Manager 53, 54 WebSphere Plug-in 58

Z
zLinux 46 creating profiles 54 installing 47, 52, 53, 57, 58, 59, 60

© Copyright IBM Corp. 2007, 2008

165

166 Installation Guide for IBM WebSphere Application Server: .

.

Printed in USA .

Sign up to vote on this title
UsefulNot useful