Installing and Configuring DB2 10, WebSphere Application ...€¦ · Installing and Configuring DB2 10, WebSphere Application Server v8 & Maximo Asset Management 4 Installing Maximo

IBM® Tivoli® Software

Maximo Asset Management

Installing and Configuring DB2 10,

WebSphere Application Server v8

& Maximo Asset Management

Document version 1.0

Rick McGovern Staff Software Engineer IBM Maximo Asset Management L3

Installing and Configuring DB2 10, WebSphere Application Server v8 & Maximo Asset Management

2

© Copyright International Business Machines Corporation 2012.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.


3

Contents

Installing Maximo 7.5.x, WebSphere Application Server 8 and DB2 10 on Windows Server....................... 4

Phase 1: Install DB2 10.............................................................................................................................. 4

Phase 2: Install and Configure WebSphere Application Server v8, HTTP Server & Plugins....................12

Phase 3: Configure WebSphere Application Server v8 for Maximo .......................................................26

Phase 4: Install Maximo ..........................................................................................................................43

Phase 5: Install Maximo FixPack 7.5.0.3 or later ....................................................................................49

Appendix: Security and post installation notes ......................................................................................51


4

Installing Maximo 7.5.x, WebSphere Application Server 8 and DB2 10 on Windows Server

Phase 1: Install DB2 10 Obtain the DB2 10 install media, at the time of the writing of this guide the latest DB2 10 version is DB2 10.1.

Place the installer in a temp folder and extract the zip:

Once extracted, go the server directory and click on setup.exe; e.g. C:\temp\SERVER.

On the welcome screen select install a product and select DB2 Enterprise Server Edition, which will be the second selection.

Click Next on the welcome screen.


5

Accept the license agreement then pick custom install.

Select the option to install DB2 on this computer


6

On the next screen remove any references to program files for the installation directory. For example: C:\IBM\SQLLIB\ needs to replace the default C:\Program Files\IBM\SQLLIB\

Click Next on the language screen and accept the default of English.

On the SSH installation folder, again remove any references to Program Files in the install path.


7

Accept the defaults on the DB2 copy screen and click Next.

Accept the default to use the IBM website for help and click Next.


8

On the Set User Information screen enter a password for db2admin and write it down for reference.

Accept the defaults and click Next on the DB2 instances screen.


9

Deselect setup the DB2 server to send notifications and click Next.

Deselect Enable Operating System Security on the next panel.

Click Install on the final panel, DB2 will begin the installation process.


10

Click Next on the Setup is Complete screen.

Click Finish on the Final Screen.

The final step is to apply the DB2 license.


11

Copy your license file to a location on the machine where DB2 is installed.

Open a new DB2 Command Prompt by typing “db2cmd” from the Run prompt of Windows.

In the command window type db2licm –a C:\db2ese_c.lic (or path to the license file).

A message the license was successfully installed will be presented.

DB2 is now installed.


12

Phase 2: Install and Configure WebSphere Application Server v8, HTTP Server & Plugins NOTE: Java 1.6 must be installed on the windows server before installing WAS 8.

Obtain the WebSphere install media. There should be a total of 9 zip files – 4 WAS Network Deployment zips, 4 Supplements zips and one for the IBM Installation Manager.

Unzip the IBM Installation Manager file. Then proceed to create two directories for WAS and the supplements zips. Unzip the 4 WAS zips to the WAS folder, and the 4 Supplements to the supplements folder.

The directories will look like this:


13

In order to install WebSphere 8 the IBM Installation Manager must first be installed. Go to the WAS8_Win_Installer directory and click on install.exe.


14

On the Install packages screen accept the defaults to install IBM Installation Manager and click Next.

Accept the license agreement and click Next.

On the next screen again remove any references to Program Files(x86) in the install path. Click Next.


15

Click Install on the final screen.

Once the installation completes, select restart the IBM Installation Manager. Also close the First Steps window.

On the Welcome Screen go the file menu and select Preferences.

In the Repositories window click Add Repository.

Navigate to the folder you extracted the 4 WAS zips to and select the repository.config file located there.


16

Click OK on the Add Repositories window, and then click OK again on the preferences panel.

Click Install on the main IBM Installation Manager panel.


17

On the next screen select both checkboxes for WebSphere then click on Check for Other Versions, Fixes and Extensions button to get the product updates

The installer will retrieve updates from the web, in this guide the latest version is 8.0.0.4. Click OK on the Search results dialog. Then click Next.


18

On the Install Packages Screen select all files, these are fixes for WebSphere.

Click Next. Accept the license agreement and click Next again.

On the first Install Packages screen remove any references to Program Files and click Next. E.g. C:\IBM\IMShared

Do the same on the second Install Packages screen removing all program files references.

Click Next. Accept English as the default language and click Next.


19

Click Next on the final install packages screen.

Click Install on the next screen. This will install WAS and update it to v8.0.0.4.

Note that it may take some time for the installer to download and install the updates.

Once complete select None on the Which Program do you want to start pane and click finish. Note: the WAS profiles will be setup after installing the supplements.


20

The main IBM Installation Manager screen will be shown. Choose File, Preferences and add the repository.config file from the Supplements directory to the repository list.

Click OK on the dialogs to add the repository and once back on the main IBM Installation Manager Screen click Install again. On the Install packages screen select all packages except Application Client and IBM WebSphere Network Deployment.


21

Again click the button to Check for Other Versions, Fixes, and Extensions. This will detect any updates and install them.


22

Click OK on search results and click Next. On the next screen select all product fixes and click Next.

Accept the License Agreement on the next screen and click Next.

On the next screen once again remove Program Files(x86) from all the installation paths.


23

Note: You need to select each top level package and change each path individually. Click Next when done.

Click Next again on the subsequent screen.


24

Accept the defaults on the next screen and click Next again.

Accept the default on the next screens and click Next twice to show each component.


25

The installer will begin collecting files from the repository. Ensure on the final screen all information is correct and press the Install button.

The installer will now collect updates and install the packages. Once the install completes select None for which program do you want to start and click Finish.


26

Close the IBM Installation Manager.

Phase 3: Configure WebSphere Application Server v8 for Maximo There are two major differences in the way WAS 8 is configured vs. WAS 7 for Maximo v7.5.

The first is the way the plugin is configured; the second is a setting in the Application Server itself.

The first step is to create the WAS profiles. Click on Start / All Programs / IBM WebSphere Application Server Network Deployment / WebSphere Customization Toolbox.


27

Select and launch the Profile Management Tool. It will be the first option in the Toolbox.

On the Profiles screen click Create. Select Management and click Next.


28

Choose Deployment Manager on the next screen and click Next.

Click Advanced Profile Creation and click Next.

Accept the default to deploy the Administrative Console and click Next.

On the Profile name and location screen add ctg to the Dmgr01 path as shown in the screen below. Make sure to modify BOTH lines as shown in the screenshot below.

Accept the defaults on Node, Host and cell names and click Next.


29

Accept the default to enable administrative security and add the user wasadmin and a password. Make note of this password as it will be used when Maximo is installed.

Click Next and accept the defaults on the next three screens for Security Certificates and Port Values

Accept the default to run as a Windows service and click Next.

Verify the information in the final screen and click Create.

Once complete, leave the check box for Launch the First Steps console and click Finish.


30

The first steps console is launched, select Installation Verification and wait for it to complete successfully. Then close the first steps console and installation verification windows.

Back on the Profile Management tool, click on Create again.

Select Custom Profile. Click Next.

Click Advanced Profile Creation. Click Next.


31

Change the default name and path for the custom profile from Custom01 to ctgAppSrv01 on both lines. Also click the check box to make this profile the default.

Click Next on node and host name, note that the node name is <machine_name>Node01.


32

Enter wasadmin and the password from earlier in the next screen – leave the Federate this node later checkbox UNCHECKED.

Click Next and accept the defaults on the next three screens for Security Certificates and Port Values.

Verify the information on the final panel and click Create.

Deselect launch the first steps console and click finish.

Close the WebSphere profile creation window.

The next step is to configure HTTP Server and the Plugins.

Go to Services and start the IBM HTTP Server service.


33

Open a command prompt and change to the WebSphere Customization Toolbox directory:

cd C:\IBM\WebSphere\Toolbox\WCT

The run the command: wct -perspective com.ibm.ws.wct.plugins.perspective

This will launch the plugin configuration wizard.


34

Click Add.

Give the profile a name like MAIN.

Enter or select the directory containing the plug-ins; C:\IBM\WebSphere\Plugins

Click Finish.

Note the top pane is now populated. The Create button is now available, click it.


35

Select IBM HTTP Server v8 in the Web Server selection window and click Next.

On the Web Server File Selection Window enter or select the following directory:

C:\IBM\HTTPServer\conf\httpd.conf

Leave the port number as 80 and click Next.

On setup IBM HTTP Administrative server deselect Create a user ID and click Next.

Accept the default service settings, click Next.

Accept the default Web server definition name, webserver1. Click Next.


36

On Configure Scenario Selection select (Local) Installation Location of WebSphere Application Server and enter or browse to the WAS application server directory; e.g. C:\IBM\WebSphere\AppServer. Click Next.

On the Profile Selection screen select ctgAppSrv01 from the dropdown, click Next.


37

Review the configuration summary information. Then click Configure.

Deselect launch the plugins configuration roadmap and click Finish.

Webserver1 will now be shown in the Web Server Plugin Configuration tab.


38

Close the WebSphere Customization Toolbox.

Go back to Services and start the IBM HTTP Administration service and the IBM HTTP Server.

Locate the application server configuration script, for example: C:\IBM\WebSphere\Plugins\bin\configurewebserver1.bat

Then copy the script to the application server bin directory, for example: C:\IBM\WebSphere\AppServer\bin

Open a command prompt and change directory to C:\IBM\WebSphere\AppServer\bin and then run the configurewebserver1 file with the following parameters:

configurewebserver1 -profileName ctgAppSrv01 -user wasadmin -password <wasadmin_password>

Close the command prompt once configuration is complete.


39

Launch a browser. Log in to the administrative console for the application server, for example:

http://<hostname or IP>:9060/admin.

Enter the user wasadmin and the password.

In the WAS console, click Servers > Server Types > Web servers. Stop the web server.

Select webserver1 and click the Generate plugins button.

Select webserver1 a second time and click the Propagate Plugins button. Start the web server.


40

Still within the WAS admin console, navigate to Server Types / WebSphere Application Servers and click the New button.

Enter the server name as MXServer and click Next.

Accept the default value on the next screen and click Next.

Leave the check box to generate unique ports checked and click Next.

Click Finish on confirm new server. Save.

Once back on the Application Servers screen click on MXServer.

On the next screen click on Session management. (On the right of the screen at the top)


41

In the next screen click on the Enable Cookies link – leave it checked.

On the next screen DESELECT the check box to set session cookies to HTTP Only to prevent cross-site scripting attacks. Maximo will not start properly if this check box is left checked.


42

Click Apply and click save.

The final step of WAS configuration is to create the virtual host.

Navigate in the WAS console to Environment / Virtual hosts and click New.

Enter the name as maximo_host and click apply and save.

Click on maximo_host and then host aliases on the right of the screen.

Enter two new aliases, one with port 80, the other with port 9080 and click apply and save.


43

The WebSphere Application Server is now configured for Maximo installation.

Phase 4: Install Maximo Note: These instructions are for Maximo Asset Management. For Smart Cloud Control Desk please refer to the Smart Cloud Control Desk Installation Guide.

Launch the Maximo 7.5 PSI install program, for example install_win64.exe.

Click OK and follow along with the install accepting the defaults until the deployment types screen is displayed. Select Custom and click Next.

Enter the fully qualified hostname and the password of the Administrator user for Windows. Leave the import option unchecked. Click Next.

Accept the default for DB2 and do not select the disable non-English support, click Next.


44

Enter the DB2 server hostname and password for the maximo user. Remember to record the password. Click Next.

Select Automate database creation and configuration, click Next.


45

On the Remote Access Authorization screen enter the Windows administrative user and password.


46

Remove Program Files from the default location field on the DB2 Administration screen and enter the password for db2admin; this is the same as the one entered during DB2 installation. Click Next.

Accept the DB2 Table space defaults and click Next.

Select WebSphere Application Server on the Application Server Types screen and also select automate configuration and click Next.


47

On the WebSphere connectivity screen enter the fully qualified hostname or IP of the WAS server and enter the wasadmin password. Click Next.

On the WebSphere remote access screen enter the Windows Administrator, password and WebSphere Installation directory. For example C:\IBM\WebSphere\AppServer. Click Next.


48

On the WebSphere Application Server Configuration screen add the machine name to the Node name in the Node name field and replace ctg with it. Example: if the machine name is qaserver1 then change ctgNode01 to qaserver1Node01. Click Next.

On the Security screen select use Maximo Internal authentication. Click Next.


49

On the Specify Maximo Users screen enter in passwords for the maximo database users, remember to note the passwords used. Click Next.

Select Do not persist JMS messages on the next screen, click Next.

It is optional to enter the SMTP server on the next screen, enter information or click Next.

On Run Configuration Step leave all 3 checkboxes unchecked and click Next.

Click Next on Import Summary.

Click Install. Maximo will be installed and will be deployed and running when successfully completed. From this point the install will take 1-2 hours depending on network and machine speeds.

Phase 5: Install Maximo FixPack 7.5.0.3 or later Note: These instructions are for Maximo Asset Management. For Smart Cloud Control Desk please refer to the Smart Cloud Control Desk FixPack Installation Guide.

Maximo has been installed at the v7.5.0.0 base at this point.

Support for WAS 8 was added in FixPack 7.5.0.3 so Maximo FixPack 7.5.0.3 or later must be applied.

Login to the WAS console again and stop MXServer.


50

Obtain the latest Maximo 7.5.x FixPack; it is 7.5.0.3 at the time of writing.

Run the FixPack installer and allow it to finish. It will deploy the EAR automatically and start the Application Server.

At this point Maximo is now successfully installed at the v7.5.0.3 level and is ready for use.


51

Appendix: Security and post installation notes The methods used in this install use native Maximo security. If the user wishes to add another security implementation such as LDAP or Tivoli Directory Server, then the user must ensure that both WAS 8 and DB2 support that version. Please see the documentation for WAS 8 and DB2 to ensure proper support.

The Application Node for WebSphere will need to be started manually if the computer is rebooted. To do this open a command prompt, change the directory to C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\bin and run the command startNode.bat. To register the Node as a windows service please consult the IBM WebSphere Installation Guide for Maximo 7.5.

The Service for the DB2 instance will be set to manual start in Services. Go to Administrative Tools / Services and find the service DB2 – DB2COPY1 – CTGINST1 -0. Change its properties for startup type from manual to automatic.

Users who wish to configure Maximo Enterprise Adapter or install Maximo Industry Solutions should consult the appropriate Installation or System Administration Guides.


52

® © Copyright IBM Corporation 2012 IBM United States of America Produced in the United States of America US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

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

IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.

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 PAPER “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes may be made periodically to the information herein; these changes may be incorporated in subsequent versions of the paper. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this paper at any time without notice. Any references in this document to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. 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.

IBM may have patents or pending patent applications covering subject matter described 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: IBM Director of Licensing IBM Corporation 4205 South Miami Boulevard Research Triangle Park, NC 27709 U.S.A. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. If you are viewing this information softcopy, the photographs and color illustrations may not appear.


53

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Other company, product, or service names may be trademarks or service marks of others.

Documents

Installing and Configuring DB2 10, WebSphere Application ...€¦ · Installing and Configuring DB2 10, WebSphere Application Server v8 & Maximo Asset Management 4 Installing Maximo