Installation and configuration of Websphere application server deployment manager profile with clustering

Description:

Following steps will guide you to graphically install WebSphere application server and configure clustering on single node along with IHS configuration.

Used soft-wares: 

WebSphere Application server ND 7 installable (It is bundled with IHS)

Update Installer (7.0.0.33-WS-UPDI-WinIA32)

Latest fixpacks (WAS,SDK,IHS,Plugin)

This entire setup will be done with the following steps:

-> Installation and configuration of WAS ND deployment manager profile

-> Installation and configuration of IHS and Plugins

-> Integration of webserver with IHS

-> Creating clusters (Load balancing)

Steps to Install WebSphere Application server:

-> Extract the installable zip folder.

-> Run the launchpad.exe

-> Click on WAS Installation.

-> This will open the installation wizard, Click on Next.

-> A per-requisite check will be done, It might show a warning incase if the os does not meet the required pre-requisites.

Warning: A supported operating system was not detected.

Don't worry, As at times  Support for your operating system might have been added after the release of the product. You can always go back to the system requirements webpages for more information.

-> Next comes the optional features, You can check then and uncheck them based on your requirements.

->   Add the PATH for product installation.

 

-> Next comes the major decision making time,  whether you need a cell profile or deployment manager profile or a custom profile or a application server profile. I am going with cell profile as I need a deployment manager and a managed node.

-> If you need the admin security, ie, To authenticate while logging into deployment manager console and to authenticate while stopping the server, Then you can enable the admin security and input the userid and password. This can be disabled if required after the installation from either admin console or the configuration files.

-> There comes the Installation summary, You can re-validate the paths and click on next.

-> Installation will complete successfully and the folder structure "c:\Program Files\WebSphere\AppServer" will be created.

-> This installation will create a deployment manager profile and a application server profile.

C:\Program Files\WebSphere\AppServer\profiles

 

 -> Start the deployment manager to access the console

C:\Program Files\WebSphere\AppServer\profiles\Dmgr01\bin\startManager.bat

Console URL : http://<Hostname>:9060/ibm/console/login.do

When you click on WebSphere application server, You can see that the node is automatically federated to the dmgr during the installation. The status is seems to be unknown as the node agent is not up and running.

-> Start the Nodeagent :

 C:\Program Files\WebSphere\AppServer\profiles\AppSrv01\bin\startNode.bat

Now refresh the console, The you can see the status of the server as red . ie, server is not running. 

-> Start the server :

C:\Program Files\WebSphere\AppServer\profiles\AppSrv01\bin\startServer.bat server1

By default the server name is created as server1. Incase if you have created a custom profile with different server name, You can use the serverStatus.bat -all command to see what all servers are listed. Based on the servername, you can input the startup parameters to the startServer.bat script. After refreshing the console, You can see a green button for the server status. It means the server is up and running.

Now the server configuration is completed successfully.

Incase if you are planning to have an IHS webserver in-front of the application server, Then click here.

To create clusters, Click here.

                                 (: Happy learning :)