Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX

Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX White Paper Gina Benzonelli, IBM Tivoli Worldwide Education August 2005 Copyright Notice Copyright © 2005 IBM Corporation, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation. Trademarks The following are trademarks of IBM Corporation or Tivoli Systems Inc.: IBM, Tivoli, AIX, Cross-Site, NetView, OS/2, Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli Ready, TME. In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. C-bus is a trademark of Corollary, Inc. in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Lotus is a registered trademark of Lotus Development Corporation. PC Direct is a trademark of Ziff Communications Company in the United States, other countries, or both and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. SET and the SET Logo are trademarks owned by SET Secure Electronic Transaction LLC. For further information, see http://www.setco.org/aboutmark.html. Other company, product, and service names may be trademarks or service marks of others. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A. Printed in Ireland. Table of Contents About This Paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Embedded Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Choosing Embedded Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 DB2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 WebSphere Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Embedded Installation Final Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 DB2 Final Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 WebSphere Final Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Software Repository for Embedded Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 IBM DB2 Version 8.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 IBM WebSphere Server 5.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Ensure File Permissions are Correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Supported Operation System Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Step-By-Step Instructions for Embedded Installation on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Prepare Installation Repository and Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Create Required Groups and Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Install WSAM 3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Post-Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Restarting Failed Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Additional Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 • • • • • I Table of Contents II • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper: Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX About This Paper This paper is intended to document the steps involved when using the embedded installation option provided with IBM WebSphere Studio Application Monitor (WSAM) 3.2. Step-by-step instructions are included for using the embedded installation on a Red Hat Linux system. Using the embedded installation option on other platforms will be similar, but may involve different steps, depending on the platform. A similar white paper titled Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on Windows documents the process for embedded installation in a Microsoft Windows environment. In addition to providing a cookbook for installing WSAM, this paper will give you a better picture of the resulting environment that the embedded installation configures on your Managing Server. Anyone who is new to the embedded installation option of WSAM and would like to use this feature, or needs more information as to whether or not to use this feature, will benefit from reading this paper. Introduction IBM WebSphere Studio Application Monitor (WSAM) provides comprehensive J2EE diagnostics and problem determination. It can detect, analyze and fix application problems in real time, often before they affect users. WSAM also provides composite application monitoring, allowing you to view correlated traces of composite transactions that span several subsystems. WSAM architecture consists of a Managing Server which collects data from various application servers (IBM WebSphere, BEA WebLogic, IBM CICS and IBM IMS). Each application server has a WSAM Data Collector installed and running; the Data Collector collects and forwards the data to the Managing Server. This paper discusses the installation of the Managing Server only; refer to the product documentation for instructions on installing the Data Collectors. • • • • • 1 White Paper Embedded Installation The Managing Server requires a database product to store the collected data (DB2 or Oracle). Additionally, it requires a J2EE server (WebSphere or WebLogic) to run the Visualization Engine, which is a J2EE application that provides the WSAM Web-based user interface. In a production environment, the processes that make up the Managing Server may be distributed across multiple systems. The database server, Visualization Engine, Kernel Server, and so on can be installed on separate physical systems. However, in test and demonstration environments, all components of the Managing Server are usually installed on one system. To provide a quick and consistent method of installing and configuring a Managing Server, version 3.2 of WSAM provides an embedded installation option. This option will install prerequisite software (IBM DB2 8.1.3 and IBM WebSphere 5.1.1) as part of the WSAM Managing Server installation. The WSAM installation program offers the flexibility of selecting which components you want it to install. For example, if you like the DB2 configuration from the embedded installation, but the WebSphere configuration will not suit your environment, you can choose to install WebSphere manually, and let the WSAM installation install DB2. 2 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper Choosing Embedded Installation To use the embedded installation option, simply run the Managing Server installation program (for example, install-MS.sh on UNIX). The WSAM installation program will give you the option of installing DB2 or WebSphere, or both. Note that in order to take advantage of the embedded installation, you must not have DB2 or WebSphere previously installed on the target system. If the WSAM installation program detects the existence of DB2 or WebSphere, it will disable that option during the installation process. Below is an example of the WSAM installation window when both DB2 and WebSphere are previously installed. DB2 Configuration One of the more restrictive requirements for the embedded installation on UNIX is that the DB2 instance owner where the WSAM database (octigate) is located must also own the octigate database tables (the database schema user). In a non-embedded WSAM installation, you can select a separate user as the database schema user (amuser by default). This account owns the octigate database and the WSAM product files, while another account (db2inst1 by default) is the instance owner. When using the default values provided during the WSAM embedded installation, the resulting Managing Server will use the db2inst1 account in place of the amuser account. This means that you must start and stop the Managing Server processes (am-start.sh and am-stop.sh) while logged in as db2inst1. In this configuration, there is no amuser account. Whenever you read instructions in the product documentation that refer to the amuser account, you will use the db2inst1 account instead. Alternately, you may decide to use another account (such as amuser) as the WSAM user, by specifying it as the DB2 instance owner during the WSAM embedded installation. In this case, amuser will own both the instance and the database. There will be no db2inst1 account; you will use amuser in its place. • • • • • ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX 3 White Paper If you would like to use the embedded installation, but do not want to use the same account for both instance and database owner, the easiest solution is to use the DB2 installation program to install DB2 before using the WSAM embedded installation for WebSphere and WSAM. The DB2 installation program will also create all required users and groups that you need for DB2, so it could actually save you some steps. (The embedded installation will not create the default DB2 groups for you.) Note that you will have to create the alternate account (such as amuser) manually before installing WSAM in this scenario. WebSphere Configuration Some of the default values provided for WebSphere in the embedded installation may cause you problems if you do not expect the values to vary from the norm. For example, the embedded installation will offer /opt/IBM/WebSphere/AppServer as the default installation directory for WebSphere, when it is usually /opt/WebSphere/AppServer. More important are the port numbers used. In a default WebSphere installation, port 9090 is used for the WebSphere administrative console (port 9043 for HTTPS). The embedded installation offers port 9190 as the default port number. If you accept port 9190 as the WebSphere administrative console port, the corresponding HTTPS port for the console will be 9443. It is important to note that when you accept port 9190 as the WebSphere administrative console port, the subsequent WSAM installation will use port 9080 for the WSAM monitoring console. This port is usually 9081. However, if you change the WebSphere administrative console port to 9090 during embedded installation, the WSAM monitoring console port will be set to the usual 9081, and you can access the WSAM monitoring console at http://hostname:9081/am/home. The embedded installation will also skip installation of the IBM HTTP Server, so you must use WebSphere for your HTTP server, or install and configure an HTTP server manually. Embedded Installation Final Configuration As you go through the process of using the WSAM embedded installation, you will notice that you will not be able to configure as many options in DB2 or WebSphere as you would have by installing the products separately. There are even some WSAM options that you cannot select during an embedded installation. Before choosing embedded installation, make sure that the resulting WSAM environment is sufficient for your purposes. It may be easier to install the prerequisite products separately if you have to spend a significant amount of time to reconfigure the environment that results from an embedded installation. The following tables show the main configuration settings that may be of interest to you when using the embedded installation to install DB2 and WebSphere. These values are for Intel-based Linux systems (default installation locations may change for other platforms). A column is also included (Manual Default Installation) that shows the value that would result if you took the default or typical values when installing each product manually. 4 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper Values that are marked with an asterisk (*) indicate that the value is not configurable during the embedded installation. Values that are not marked with an asterisk can be changed during the interactive installation process. DB2 Final Configuration Parameter Installation Location Instance name and owner Octigate database owner Embedded Installation /opt/IBM/db2/V8.1* db2inst1 Instance owner* (db2inst1 by default) Manual Default Installation /opt/IBM/db2/V8.1 db2inst1 amuser WebSphere Final Configuration Parameter Installation Location Account that runs WAS Admin Console Port (HTTP/ HTTPS) Node name/cell name IBM HTTP Server installed Embedded messaging Deploy Tool, Ant Utilities Sample Applications Global Security Active WSAM URL Embedded Installation /opt/IBM/WebSphere/AppServer root 9190/9443 host name* No* No* No* No* No* http://hostname:9080/am/home Manual Default Installation /opt/WebSphere/AppServer root 9090/9043 host name Yes Yes Yes Yes No http://hostname:9081/am/home ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 5 White Paper Software Repository for Embedded Installation The first step in using the embedded installation is to obtain the correct set of installation files. WSAM 3.2 ships with the correct versions of IBM DB2 and IBM WebSphere that the embedded installation requires. It is especially important to use the provided version of DB2, even if you have your own copy available. You may have obtained the prerequisite products from a CD, or you may have downloaded the products as tar files. If your product files are on CD, you must create a software repository on an available disk; installation directly from CD is not supported. Copy the DB2, WebSphere, and WSAM installation files to a disk that is accessible by the target system that will become the Managing Server. If you have downloaded the files, untar them into separate directories (for example, WSAM, DB2, and WAS). IBM DB2 Version 8.1.3 The version of DB2 that is included with WSAM 3.2 is a cumulative DB2 package which includes DB2 version 8.1 with Fixpack 3. When you install this version of DB2, the resulting version of DB2 is 8.1.3; Fixpack 3 is included in the base installation. You must use this cumulative version of DB2 because the WSAM embedded installation will query you for only one location for DB2; it will not allow you to specify an additional location for a fix pack. If you specify your own copy of DB2, the embedded installation will fail. Of course, once the embedded installation is complete, you can apply additional fix packs to upgrade DB2. WSAM 3.2 supports IBM DB2 Enterprise Server Edition (ESE) with Fixpack 5 or later, or IBM DB2 ESE 8.2. IBM WebSphere Server 5.1.1 The version of WebSphere that is included with WSAM 3.2 is IBM WebSphere Application Server 5.1 Base Edition with Fixpack 1. The embedded installation will first install version 5.1, and then apply Fixpack 1. In this case, you can optionally provide your own files for WebSphere 5.1 and Fixpack 1, or use the files provided with WSAM. Ensure File Permissions are Correct Once you have created your software repository, make sure that the resulting repository is owned by the root user and that the executable files have the execute (x) flag set. 6 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper Supported Operation System Level You should make sure that the operation system is a supported version for WSAM 3.2. In our example, we are installing on Red Hat Enterprise Linux AS version 3.0, which includes Update 5. If you are using RHEL 3, you should read the IBM technote that specifies how to prepare your RHEL 3 system for WebSphere 5.1.1. In general, you need to apply at least Update 1 to your system; since we have Update 5, we did not have to make any additional changes to our system before using the embedded installation. To read the technote Preparing Red Hat Enterprise Linux 3 (RHEL 3) to run WebSphere Application Server V5.1 products, go to: http://www-1.ibm.com/support/docview.wss?uid=swg21164634 ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 7 White Paper Step-By-Step Instructions for Embedded Installation on Linux Prepare Installation Repository and Operating System 1. It makes for an easier installation if you are logged in as root while following these steps. File ownership becomes less troublesome when creating directories and untarring files. Any potential file ownership errors can be averted by untarring any required files after moving them to the target repository (especially if they were downloaded by another account, or to a remote system). 2. Obtain the cumulative IBM DB2 ESE 8.1.3 installation files from your WSAM 3.2 product media. Copy the files to a hard drive that is accessible by the target system. In our example, we copied the files to the /data/DB2 directory, and untarred them there. 3. Obtain the installation files for IBM WebSphere Application Server 5.1 Base Edition. Copy the files to the installation hard drive; in our example we copied the files to /data/WAS51 and untarred them there. 4. Obtain the installation files for Fixpack 1 of IBM WebSphere Application Server 5.1. Copy the files to the installation hard drive; in our example we copied the files to /data/WAS51FP1. 5. Obtain the installation files for IBM WebSphere Studio Application Monitor 3.2. Copy the files to the installation hard drive; in our example we copied the CD contents to /data/ WSAM32. 6. Untar any of the installation files, if you downloaded them as tar files. Make sure that the file ownership and permissions are correct. If root does not own the installation repository directories, chown the directories to root. Most of the untarred installation files should be owned by root; some of the DB2 files are owned by bin; you do not need to change these file ownerships. 7. Ensure that the operating system you are installing the product on is compatible with WSAM 3.2, DB2 8.1.3, and WebSphere 5.1.1. In particular, if you are using RHEL 3.0, make sure that you have at least Update 1 applied. In our example, we used RHEL 3.0 AS with Update 5 installed. Create Required Groups and Users WSAM requires that the operating system account admin be created before installing the Managing Server. In addition, the embedded installation will not create the default groups that DB2 users dasusr1, db2inst1, and db2fenc1 use in a default DB2 installation. (It will create those users, however.) While you may use existing groups for these users, we will 8 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper create the default groups for DB2 in this example, as well as creating an amuser group for the WSAM admin user. In our example, we will use the default value of db2inst1 for both instance and database owner. Note that you may choose to use amuser instead, to maintain consistency with most of the product documentation. 8. Create new groups for WSAM (this is not specifically required). The amuser group will be used for the admin account, and the other three groups are the groups that a default DB2 installation would create. Note that these DB2 groups are also the default values that the embedded installation will use; however it will not create them for you. groupadd groupadd groupadd groupadd amuser dasadm1 db2grp1 db2fgrp1 9. Create the admin user, and set its password. (Again, the admin user is not required to belong to the amuser group.) Note that you must create this user before starting the WSAM installation. useradd -g amuser -d /home/admin -m -s /bin/bash admin passwd admin (enter the password twice) Install WSAM 3.2 10. While logged in as root, move to the WSAM installation directory. In our example, it is /data/WSAM32. 11. Move to the Installer-MS/bin directory. The installation program will launch a Java GUI program, so if you are remote to the target system, make sure that you have set the DISPLAY variable correctly on the target system, and have executed the xhost + hostname command on the local system (where hostname is the name of the target system). 12. Run the script install-MS.sh. ./install-MS.sh ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 9 White Paper 13. The installation program will launch with the initial installation windows. 10 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper 14. Select to install both DB2 and WebSphere. 15. In the next window, you will specify the account which will run the WebSphere Application server. Below are the default values provided by the WSAM installation. In our example, we will change the WebSphere Admin Console Port. ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 11 White Paper 16. We accept the WSAM default location of /opt/IBM/WebSphere/AppServer, but change the Admin Console Port from 9190 to the WebSphere default of 9090. 17. Next, you will enter a password for the DB2 Admin User dasusr1. If you did not previously create the dasadm1 group, you must change the group name to an existing one. While you can also change the names and home directories of the DB2 users, we will choose to keep all default values in our example. 12 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper 18. Enter a password for the DB2 fence user db2fenc1. If you did not previously create the db2fgrp1 group, change the group name to an existing one. 19. The next window will specify the DB2 instance user. This will be both the instance owner and WSAM database user. The default value is db2inst1, but you may specify amuser if you prefer. In our example, we are using db2inst1. If you did not previously create the db2grp1 group, specify an existing group. ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 13 White Paper 20. Specify the location of the DB2 8.1.3 consolidated installation files. In our example it is /data/DB2. This is the directory where the files db2setup and db2_install are located. 21. Specify the location of the WebSphere 5.1 installation files. The directory specified should contain the license.txt and readme.html files. Do not specify the linuxi386 subdirectory. Also specify the location of Fixpack 1 for WebSphere 5.1. Specify the directory that contains the updateWizard.sh and updateSilent.sh files. Do not specify the fixpacks subdirectory. 14 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper 22. The WSAM embedded installation program is now prepared to install DB2 and WebSphere. Select Install. 23. You should now see a message indicating that DB2 is being installed. At this point, if there are any file permission problems, you will receive an error message, and the installation will be canceled. 24. Once DB2 installs successfully, you will see a message indicating that WebSphere is being installed. This should take much longer than the DB2 installation. ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 15 White Paper 25. If either installation fails, you can check the log files located in the /tmp/ibm_am_installer_ms directory. If the DB2 installation failed, you may find useful information in the /tmp/db2setup.log file as well. 26. Once DB2 and WebSphere have been successfully installed, the Managing Server installation will begin. Select to install both the Visualization Engine and create the local database. 27. Enter the name of the application server that will be created within WebSphere to host the Visualization Engine. We used the default value of server_wsam: 16 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper 28. The default installation location for WSAM on Linux is /opt/ibm/wsam. Since this does not seem very consistent (DB2 is installed in /opt/IBM/db2, and we chose to install WebSphere in /opt/IBM/WebSphere/AppServer) we will change the default value to /opt/IBM/wsam. 29. Because we are installing all Managing Server components on one system, we leave the default values for primary and secondary Kernel Servers (our Managing Server host name miranda). We will also use the default port range. ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 17 White Paper 30. On Linux systems, the WSAM installation will offer to edit the sysctl.conf file in order to change kernel parameters for DB2 performance. We selected the default of Yes. 31. We are now ready to install the Managing Server. Since the embedded installation program installed WebSphere and DB2, it does not need to ask for specific information such as host name, SOAP port and node name for WebSphere, and instance owner and JDBC driver file for DB2. 18 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 White Paper 32. During the Managing Server installation, you will not see any additional messages. When the installation is complete, you will see the Post-Installation Summary. Your Managing Server installation is now complete. Post-Installation Steps 33. After the embedded installation, the WebSphere application server server1 should be started. However, the application server that hosts the WSAM Visualization Engine (server_wsam) will be initially stopped. 34. Before starting the server_wsam application server, you need to configure the WebSphere headless JVM parameter in the new server_wsam application server. a. Open the WebSphere administrative console. In our case, the administrative console is using port 9090. http://hostname:9090/admin b. Select the following menu path: Servers >> Application Servers >> server_wsam >> Process Definitions >> Java Virtual Machine ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 19 White Paper c. Enter the following value in the Generic JVM arguments field: -Djava.awt.headless=true 35. Save your changes in the master configuration before exiting the WebSphere administrative console. 36. Start the Managing Server processes. To do this, you must be logged on as the database owner. In our case, this is db2inst1; if you changed the default user to amuser, then you will log in to the amuser account. su - db2inst1 cd /opt/IBM/wsam/bin ./am-start.sh 37. Wait until all of the processes have started (note that you will not get your prompt back; press Enter to return to the prompt). Then exit from the db2inst1 shell. • • • • • exit Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005 20 White Paper 38. You should now be logged in as root. The root account will start the server_wsam application server (since root is the WebSphere user in our case). However, it must have the DB2 environment set so that the Visualization Engine application can access the WSAM database. We will source the db2inst1 environment in order to set up the correct DB2 environment variables. Then we will start server_wsam. source ~db2inst1/.bashrc cd /opt/IBM/WebSphere/AppServer/bin ./startServer.sh server_wsam 39. You are now ready to access the WSAM Managing Server console (Visualization Engine). Because the embedded installation did not install the IBM HTTP Server, we will use the internal WebSphere HTTP server to launch the console. Our WSAM console is configured on port 9081. Note that if you did not change the default value for WebSphere Admin Console, then the WSAM console will be at port 9080. http://hostname:9081/am/home Restarting Failed Installations If your installation fails, your installed products may be in an unknown state, and running the WSAM installation program again (after fixing any problems) may not succeed. For example, if your DB2 installation succeeded, and your WebSphere installation failed, the DB2 instance will be in the stopped state. Your subsequent WSAM installation will fail if you do not first start the instance. In a situation where one or more of the components failed to install, you may be better off removing the partially installed software, and starting again. Some steps to take to remove the partially installed software include: WebSphere • • • • Stop any running application servers. Move to the /opt/IBM/WebSphere/AppServer/bin/_uninst directory. Run the program uninstall. Remove the /opt/IBM/WebSphere directory. ©Copyright IBM Corp. 2005 Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX • • • • • 21 White Paper DB2 • • • • • Move to the directory in your software repository where the DB2 installation files are located (not the installed location of /opt/IBM/db2/V8.1). Run the program db2_deinstall. Remove the /opt/IBM directory (if there is nothing left in that directory that you need). Remove the /var/db2 directory. Edit the /etc/services file and make sure that the entries created by the DB2 installation are deleted. This is very important, because any subsequent embedded DB2 installations will attempt to use the same ports, and will fail if they already exist. Additional Cleanup • • If the WSAM installation location is not under /opt/IBM, delete the WSAM installed files. You may want to delete any WSAM files in the /tmp directory, such as any ISMP files, or the ibm_am_installer_ms directory. 22 • • • • • Embedded Installation for IBM WebSphere Studio Application Monitor 3.2 on UNIX ©Copyright IBM Corp. 2005