Friday, February 20, 2015

Web Sphere Application Server 8.0 Installation Companion

 

1.0 Introduction

The objective of this work product is to:

  • Provide the installation and configuration instructions for WebSphere Application Server 8.0

1.1 References

The following documents were referenced in preparation of this document:

2.0 Installation Plan

2.1 Scope

The Software Installation and Configuration Documentation were prepared in order to capture the installation process and configuration of WebSphere® Application Server in the development environment. This document provides the basic installation process required for development environment. Detail documentation regarding the software is available in the vendor provided installation and administration manuals.

This document does not provide the security, scalability and other configuration requirements that are required for a production or test environment.

2.2 Pre-Installation Activities

The following is a list of tasks to be completed before beginning the installation process:

  • Most IBM and Oracle software do not use the keys for licensing. Licensing should be procured by the client depending on the number of products installed and the number of CPU's used on the server. Some of the products may have other assemblies bundled in it.
  • Purchase a copy of the IBM WebSphere Application Server software from IBM. The license may be purchased for 2 cpu’s. IBM may deliver the software’s either in CD’s or software electronic downloads.

2.4 Security

  1. Matrix of ports containing the Port number, Protocol and URL is shown below in Exhibit 4 below

Exhibit 4: Matrix of Ports

IP, Host Name and Location

Port Number

Protocol

Comment

URL

hostname

9061,9081

http

9061 – admin host, 9081 – default host

http://hostname:9061/ibm/console

hostname

9044,9444

https

9044 – admin host secure, 9444 – default host secure

https://hostname:9044/ibm/console/logon.jsp

hostname

9062,9082

http

9062 – admin host, 9082 – default host

http://hostname:9062/ibm/console

hostname

9045,9445

https

9045 – admin host secure, 9445 – default host secure

https://hostname:9045/ibm/console/logon.jsp

2.5 Software Inventory

The table below provides the list of software required for the installation.

Exhibit 5: Software Inventory

Software Title

Release Number

WebSphere® Application Server

8.0.0.0

   

2.6 Hardware Inventory

The table below provides the list of hardware required for the installation.

Exhibit 6: Hardware Inventory

Software

Vendor

Model

CPU

RAM

OS

WebSphere® Application Server

Vmware

VM

2

2

Windows 2008

It is very important to have the minimum amount of required memory to install the product.

2.7 Network Inventory

The table below provides information on the network requirements for installation.

Exhibit 7: Network Inventory

Software

Environment

IP Address

Domain

WebSphere® Application Server

DEV

XXX.XXX.XXX.XXX

GLB


3.0 INSTALLATION and Configuration

This section outlines the installation and configuration processes for the WebSphere® tools MQ and Eclipse. In addition, this section outlines the installation testing processes for each of the tools.

3.1WebSphere® Application Server Installation

WebSphere® Application server MQ is a messaging framework that provides reliable application integration by passing messages between applications and web services. It reduces the risk of information loss and the need to reconcile IT systems communication. It achieves this by using queuing and transactional facilities to preserve the message integrity across the network. It provides local and remote queuing to support guaranteed delivery, traceability, and error recovery.

The following list provides the installation steps:

3.2WebSphere® Application Server Installation

The following list provides the installation steps:

Download from: 

http://www14.software.ibm.com/webapp/download/preconfig.jsp?id=2010-03-30+14%3A40%3A55.882659R&S_TACT=104CBW71&S_CMP=rss

Click continue to download the software.

clip_image002

Click continue and accept the terms and conditions and say confirm to go next.

clip_image004
clip_image006
Select the following downloads and use the HTTP Download Director so that you downloads can resume if connection is lost.
IBM WebSphere Application Server 8.0 Beta (Part 1 of 3)
beta.was.repo.8000.base_1_Oct22_2010.zip (all 3 parts are required) (841 MB)
IBM WebSphere Application Server 8.0 Beta (Part 2 of 3)
beta.was.repo.8000.base_2_Oct22_2010.zip (all 3 parts are required) (845 MB)
IBM WebSphere Application Server 8.0 Beta (Part 3 of 3)
beta.was.repo.8000.base_3_Oct22_2010.zip (all 3 parts are required) (862 MB)

clip_image008
IBM Installation Manager for Windows on Intel
iim.win32.x86_1.4.2000.20100901_0107.zip (97 MB)


clip_image010

Unzip the IBM Installation Manager into c:/temp and run install

clip_image012
You will then be presented with the loading screen.
clip_image013

Once loaded, “Click Next" as shown below
clip_image015

Accept the license and click Next to continue
clip_image017

Select an appropriate path into which the installer will be installed.
clip_image019
Click install as shown below
clip_image021Tt

Installation has now completed, close and run the Installation Manager
clip_image023
Or click "Restart Installation Manager" button
When the IIM loads it will ask for a username and password to connect to the online IBM repository. We do not want to do this as we have already downloaded the files.
Click File-Preferences to change the location of the repository files
clip_image025
Make sure that you expand all the downloaded files into a known location:
Click Add a repository. In my example I chose the C:\temp\was8_repo\C:\temp\was8_repo\repository.config which is where the installation is located
clip_image027
We can now see that the repository is located
clip_image029
You can now click Install
clip_image030
When you click install you can see the following
clip_image032
Ensure that version 8.0.0.0 is selected

Accept the terms and click next to proceed the installation

clip_image034

Click Next to continue and select an appropriate installation location
clip_image036

Select everything but the samples
clip_image038
Continue until the installation starts
clip_image040
When the application server binaries have been installed, then you have the option to start the Profile Management Tool to create a profile.
Leave the "Profile Management Tool to create a profile" radio-option selected and click Finish
clip_image041
Select Profile Management Tool from the tools list and click Launch Selected Tool
clip_image042
Click Create as shown above
clip_image043
Click Application Server. At this stage we are not creating a management node. On the next step click the advanced profile creation option.
clip_image044
Why Advanced?
Create application server using default configuration settings or specify your own values for settings such as the location of the profile and names of the profile, node and host. You can assign your own ports. You can optionally choose where to deploy the administrative console and sample application and also add web-server definitions if you wish. Web server definitions are used with IBM HTTP Server. You can search my site to learn more.
clip_image045
As shown above I also ensure that snoop is installed as it is a great application for testing that your server is running correctly. You can search my website for SSL secrets and this document will explain how to use snoop as part of workload management.

On the next screen ensure that Development is selected for runtime tuning to allow our server to start quickly, since it is a local test server, not production.

clip_image046
clip_image047
You can override the default assigned node name and hostname, I have left mine defaulted.
clip_image048
I used wasadmin/wasadmin for username/password
clip_image049
I then left the SSL as defaulted for both step 1 and step 2 of the SSL configuration screens
clip_image051
In my case I already had WebSphere 7 installed locally so mu ports where adjusted by and offset of 1.
clip_image053
I personally have limited resources for automatic starting, so I have requested the installer no install the windows service. We can use local bat files to start and stop the server. Up to you to decide. I find the service style takes too long to stop and start.
clip_image055
You can click next until the end where you can select Create to begin the installation of the profile. I skipped the Web Server definition screen as we are not going to install IHS in this example. Look at my SSL articles to understand how to install IHS.
clip_image056
By launching the first step console you can check that the server will run. You will also see that a new profile has been created called AppSrv01
clip_image057
clip_image058
It can be a good idea to run the Installation Verification,the sever will be started automatically using the following command:
cmd.exe /c "C:\IBM\WebSphere\AppServer\profiles\AppSrv01\bin\startServer.bat" server1 -profile Name AppSrv01
clip_image059
As shown above the server has started successfully, we can now log into the admin console by opening the following URL:
http://localhost::9061/ibm/console
The server will redirect to https://localhost:9044/ibm/console/logon.jsp, the HTTPS port. You will need to accept the security exception since we are using a private SSLcertificate.
clip_image060
You will notice the new login screen, log in using wasadmin/wasadmin and see what the new IBM WebSphere Application Server version 8 Beta has to offer.

 

Installing WebSphere Application Server Network Deployment



Installing WebSphere Application Server Network Deployment

Install WebSphere Application Server Network Development version 8 and upgrade to fix pack 2.
Before you begin
IBM Installation Manager 1.5.2 must be installed prior to installing WebSphere application Server Network Deployment.
Procedure
1.    Download the WebSphere Application Server Network Deployment version 8 Passport Advantage.
2.    Extract the downloaded files to a location on your drive, for example, /opt/software/was80nd.
3.    Download the WebSphere Application Server fix pack 2 from ibm.com.
4.    Extract the downloaded files to a location on your drive, for example, /opt/software/8.0.0-WS-WAS-FP0000002.
5.    Launch IBM Installation Manager and click File > Preferences.
6.    Click Add Repository and add the following repository.config files to the list.
7.  /opt/software/was80nd/repository.config
/opt/software/8.0.0-WS-WAS-FP0000002/repository.config
8.    Click OK, and then Install.
9.    Select IBM WebSphere Application Server Network Deployment and Version 8.0.0.2 check boxes. Click Next.
10. Read and accept the terms in the license agreement. Click Next.
11. Select Create a new package group and change or accept the default installation directory. Click Next.
12. If desired, select additional languages to install and then click Next.
  1. Select the following features in the Select the features to install page:

14. In the Summary page, review the summary information and then click Install.
15. After the installation completes, under Which program do you want to start select None to not create a new profile when this installation is finished. We will use the Profile Management Tool to do this. Click Finish.
Creating the deployment manager profile
Create a deployment manager profile and enable the administrative security by assigning a username and password.
Procedure
1.    Launch the Profile Management Tool (IBM WebSphere > IBM WebSphere Application Server Network Deployment V8.0 > Tools > Profile Management Tool).
2.    Click Create and then select Management. Click Next.
3.    Select Deployment manager and then click Next.
4.    Select Typical profile creation, click Next.
5.    Select the Enable administrative security check box and use admin/admin for user name and password. Click Next.
6.    In the Summary page, click Create. Wait until the installation completes, clear the check box for Launch the First Steps console and then click Finish. Now you created a Deployment Manager profile named Dmgr01
Creating and federating a custom profile to act as CLM node 1
Create a Websphere Application Server profile that will host the first node in the CLM cluster.
Before you begin
To get a WebSphere Application Server node federated, you must synchronize the clock of current node with the clock of the deployment manager using the Network Time Protocol (NTP) service. For more information about NTP, visit http://www.ntp.org/.
Also ensure the Deployment Manager is started and running.
Procedure
1.    Launch the Profile Management Tool and click Create.
2.    Select Custom profile and then click Next.
3.    Select Typical profile creation, click Next.
4.    Select Federate this node later, click Next and then click Create.
5.    After installation completes, clear the check box for Launch the First Steps console, click Finish.
6.    Ensure the Deployment Manager server is started.
7.    Open a terminal window and change directory to opt/IBM/WebSphere/AppServer/profiles/Custom01/bin, run the following command:
./addNode.sh machine2HostName 8879
8.    Enter admin/admin for the deployment manager administrative user name and password when prompted.
9.    After the node has been successfully federated, open the Deployment Manager Integrated Solutions Console.
10. Navigate to Servers > Server Types > WebSphere application servers, click New.
11. Select the node you just federated and enter server1 in the Server Name field. Click Next.
12. Accept the default server template and click Next.
13. Click Next in the succeeding pages accepting the default settings.

14. In the Confirm new server page, click Finish.
15. Save directly to the master configuration, then click OK.


Creating and federating a custom profile to act as an additional CLM node
Create a Websphere Application Server profile that will host the additional node in the CLM cluster.
Before you begin
To get a WebSphere Application Server node federated, you must synchronize the clock of current node with the clock of the deployment manager using the Network Time Protocol (NTP) service. For more information about NTP, visit http://www.ntp.org/.
Also ensure the Deployment Manager is started and running.
Procedure
1.    Launch the Profile Management Tool and click Create.
2.    Select Custom profile and then click Next.
3.    Select Typical profile creation, click Next.
4.    Select Federate this node later, click Next and then click Create.
5.    After installation completes, clear the check box for Launch the First Steps console, click Finish.
6.    Ensure the Deployment Manager server is started.
7.    Open a terminal window and change directory to opt/IBM/WebSphere/AppServer/profiles/Custom01/bin, run the following command:
./addNode.sh machine2HostName 8879
8.    Enter admin/admin for the deployment manager administrative user name and password when prompted.
9.    After the node has been successfully federated, open the Deployment Manager Integrated Solutions Console.
10. Navigate to Servers > Server Types > WebSphere application servers, click New.
11. Select the node you just federated and enter server2 in the Server Name field. Click Next.
12. In the Select a server template page, select the template you created in Creating the CLM server template for clustering and click Next.
13. Click Next in the succeeding pages accepting the default settings.
14. In the Confirm new server page, click Finish.
15. Save directly to the master configuration, then click OK.
16. Go to Machine 3 and copy the Jazz Team Server installation directory you installed in Installing the IBM Rational solution for CLM V4.0 on server1.
17. Go to Machine 4 and paste the Jazz Team Server installation directory you just copied, making sure that you keep the directory structure as Machine 3.
Creating the CLM cluster
Create a WebSphere Application Server cluster with server1 and server2 as nodes.
Procedure
1.    Open the Deployment Manager Integrated Solutions Console and navigate to Servers > Clusters > WebSphere application Server clusters, click New.
2.    Enter a name for Cluster name and clear the Prefer local checkbox. Click Next.
3.    Enter a name for the first Member name.
4.    Select the node you created on Machine 3.
5.    Select the radio button for Create the member using an existing application server as a template and select the server on Machine 3 (server1) as a template. Click Next.
6.    Enter a name for the second Member name.
7.    Select the Node you created on Machine 4. Click Add Member, and then click Next.
8.    In the Summary page, click Finish and then save directly to the master configuration.