Overview

This tutorial walks through a single-node installation of IBM Connections on a Red Hat Enterprise Linux 6.3 64-bit system. There are nine lessons in this tutorial. This is Lesson 2 - Installing WebSphere Application Server (WAS).

Lesson objectives

WebSphere Application Server (WAS) is one of several applications required to install and configure an IBM Connections environment. In this lesson, you will:

• Install WebSphere Server
• Enable administrative security
• Verify successful installation

At the end of this lesson, you will be able to install and configure WAS.

System requirements

Resources

Task 1: Begin Installation

Begin installation of WAS using the Launchpad

Step	Action
1	Login as user root.
2	Go to the directory where the C1G35ML.tar.gz file was extracted (probably /opt/install/WAS - refer to first tutorial “Preparing Your System” Task 3, Step 3)
3	Start the launchpad.sh shell script: [root@connections4 WAS]# ./launchpad.sh Result: The installation wizard dialogue will appear.* Note: If you encounter the error “Unable to find supported browser”, please refer to appendix A to correct the problem and return here.
4	On the Installation Wizard Welcome dialogue, click Next.
5	Accept the terms of the license agreement. Click Next.
6	A warning will appear because the RHEL 6.3 OS is not officially supported. Ignore the warning and click Next.
7	When prompted for installation directory, enter /opt/IBM/WebSphere/AppServerDemo. Click Next.
8	At the Optional Features Installation dialogue, select Install the Sample applications. Click Next.
9	At the WAS Environments dialogue, select Cell (deployment manager and a managed node). Click Next.
10	At the Enable Administrative Security dialogue, enter wasadmin for the User name and enter a password. We chose to install sample applications, so a password is also needed there (suggest using the same password). Click Next.
11	We are not using Centralized Installation Manager (CIM). Click Next.
12	At the Installation Summary dialogue, select “Verify my permissions to perform the installation” (default). Click Next.
13	The permissions check should succeed. Click Next.
14	The IBM WebSphere Application Server installation begins. This step takes ~5 - 10 minutes.
15	The installation completes and displays a Success message. I has successfully installed the WAS Network Deployment as a Cell. Click Finish.
	Result: The First steps dialogue will display.

Task 2: Verify the Installation

Step	Action
1	At the First steps dialogue, click Installation verification.
2	The Installation verification should complete quickly.* Close the dialogue. *For an explanation on any errors or warnings detected, see Appendix C.
3	Result: You are returned to the First steps dialogue.

Task 3: Start the Administrative console

Step	Action
1	On the First steps dialogue, click Administrative console. Note: If you encounter the error “No supported browser was detected”, please refer to Appendix B to correct the problem then return here.
2	Clicking Administrative Console should start the browser. You will receive a dialogue stating that the connection is untrusted. Click Add Exception.
3	A subsequent confirmation dialogue will display. Click Confirm Security Exception.
4	At the Integrated Solutions Console (ISC), enter credentials. Click Log in.
5	Result: You are now logged into the ISC and will see a dialogue similar to that shown below.

Task 4: Confirm that Deployment Manager is running

Step	Action
1	From the directory: /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/bin type ./serverStatus.sh -all -user wasadmin -password passw0rd [Enter]
2	You should see the following: The Deployment Manager "dmgr" is STARTED

This concludes Lesson 2.

Please continue on to Lesson 3: Installing IBM HTTP Server and Plugin.

Appendix A

Starting the launchpad.sh shell script may result in the error:

“Unable to find supported browser”.

This is usually a result of the Firefox browser being updated to Version 10 or later. Check the version of Firefox. If using v.10 or greater, edit the browser.sh shell script (using vi or gedit) so it contains the following string in the supportedFirefoxVersion case statement:

*Firefox\ [1-9][0-9].*) return 0;;

The function should then look like this:

supportedFirefoxVersion()
{
case "$*" in
*Firefox\ [1-9].*) return 0;;
*Firefox/[1-9].*) return 0;;
*Firefox\ [1-9][0-9].*) return 0;;
...

See link below for more information.

http://www-01.ibm.com/support/docview.wss?uid=swg21595098

Appendix B

Following the installation, choosing options from the First steps dialogue may result in the error:

“No supported browser was detected” (see below).

This is usually a result of the Firefox browser being updated to Version 10 or later. Check the version of Firefox. If using v.10 or greater, edit the fbrowser.sh shell script* (using vi or gedit) so it contains the following string in the supportedFirefoxVersion case statement:

*Firefox\ [1-9][0-9].*) return 0;;

The function should then look like this:

supportedFirefoxVersion()
{
case "$*" in
*Firefox\ [1-9].*) return 0;;
*Firefox/[1-9].*) return 0;;
*Firefox\ [1-9][0-9].*) return 0;;
...

*You will likely have multiple copies of the fbrowser.sh file. To determine the location of the correct file to modify, check the path entered in step 3 above. Appended to this will be a /profiles/Dmgr01/firststeps/ directory. This is the location of the fbrowser.sh file that must be modified. So for this tutorial, locate and modify this file:

/opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/firststeps/fbrowser.sh

IMPORTANT: Once fbrowser.sh is modified, you must close the First steps dialogue and restart it. To restart, run the firststeps.sh shell script located in the same directory as the fbrowser.sh shown above. See image below.

Appendix C

Q: What are the errors / warnings I see during the Installation verification step?

A: The Installation Verification Tool (IVT) scans the SystemOut.log file to determine if there are any issues to be aware of. It's very common for IVT to flag errors or warnings, but usually these are benign. For example, in our case, the IVT tools detected two errors/warnings (see graphic below).

Notice the first line shows the location of the SystemOut.log file. On my system it's located in /opt/IBM/WebSphere/AppServerDemo/profiles/Dmgr01/logs/dmgr .

The following two lines show the following errors/warnings:

WSKeyStore W CWPK10041W: One or more key stores are using the default password.

ThreadPoolMgr W WSVR0626W: The Threadpool setting on the ObjectRequestBroker service is deprecated.

These are accurate messages. If we open the SystemOut.log file (using either vi or gedit) and search for either WSKeyStore or ThreadPoolMgr, we will find both warnings:

[11/29/12 14:36:44:518 GMT-05:00] 00000000 WSKeyStore W CWPKI0041W: One or more key stores are using the default password.

…

[11/29/12 14:36:52:993 GMT-05:00] 00000000 ThreadPoolMgr W WSVR0626W: The ThreadPool setting on the ObjectRequestBroker service is deprecated.

…

This verification step brings to your attention configuration related items that you should be aware of.