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.

13. 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.