Websphere8 Installing the Java EE program from the installation to the deployment test cluster application (very detailed)

Directory
1.preparing the installation files
2.Installing installation Manager
3.specifying the installation repository for Installation Manager
4.Create a Deployment Manager profile
5.Create a custom profile and federate it to the deployment Manager
6.Create an Application Server (standalone) profile
7.Standalone server node to Deployment Manager
8.Start Node
9.Create a cluster
10.install and simply test applications on a cluster
11.Configuring the IBM HTTP Server plug-in and Management Server
preparing the installation files
To open the IBM Web site to download WebSphere, download the following files:
IBM WebSphere application Server Network Deployment Trial, including Liberty profile v8.5 (Part 1 of 3)
IBM WebSphere application Server Network Deployment Trial, including Liberty profile v8.5 (Part 2 of 3)
IBM WebSphere application Server Network Deployment Trial, including Liberty profile v8.5 (Part 3 of 3)
WebSphere Customization Toolbox v8.5 (Part 1 of 2)
WebSphere Customization Toolbox v8.5 (Part 2 of 2)
Web Server plug-ins for IBM WebSphere application Server v8.5 (Part 1 of 2)
Web Server plug-ins for IBM WebSphere application Server v8.5 (Part 2 of 2)
IBM HTTP Server for WebSphere Application Server v8.5 (Part 1 of 2)
IBM HTTP Server for WebSphere Application Server v8.5 (Part 2 of 2)
Installation Manager 1.5.2 for Windows
Installing installation Manager
Unzip installation Manager 1.5.2 for Windows and install directly next, this is nothing to say,






specifying the installation repository for Installation Manager
Installation Manager is just an installer that uses this installer to install WebSphere and open Installation Manager

preferences for selecting files

Select the repository from the left menu and click the button to add the repository

Select Repository dialog box, click Browse

Select Repository.config in the following files and add them all to the repository
IBM WebSphere application Server Network Deployment Trial, including Liberty profile v8.5 (Part 1 of 3)
WebSphere Customization Toolbox v8.5 (Part 1 of 2)
Web Server plug-ins for IBM WebSphere application Server v8.5 (Part 1 of 2)
IBM HTTP Server for WebSphere Application Server v8.5 (Part 1 of 2)

Click Install, select all packages

Then direct next, Next, default selection.
Create a Deployment Manager profile
If the above installation is successful, now we start to configure, first of all, what is the Deployment Manager

Deploymentmanager has the ability to manage multiple federated nodes. The DM can manage nodes across multiple systems and platforms. A node managed by a DM can only be managed by a single DM and must be federated to the unit of that DM.

Start Profile Management tool: Start > All Programs > IBM WebSphere > IBM WebSphere Application Server
Network Deployment > Tools > Overview Management Tools

Select Environmental management. Click Next

Select the server type Deployment Manager. Click Next

In the profile creation option, select Advanced Profile creation and click Next

Select the deployment Management Console. Click Next

Enter the profile name and the specified directory (accept the default). Click Next

Enter the node name, host name, and cell name (accept the default value). Node names and cell names can be specified randomly, but host names use the current host
Name. Ensure that the hostname can be ping-through. Click Next

Start administrative security. Enter your username/password and click Next

Leave the default value, next



To cancel the "Run Deployment Manager process as a Windows Service" option, click Next

Review profile summary information. After confirming, click Create to start creating profile

Once created, select the start the first step console option and click Finish

The newly created profile Dmgr01 appears in the Profiles list

Start the Deployment Manager service and click Start Deployment Manager above

Wait for the service to start to complete. Close the first step output console

Create a custom profile and federate it to the deployment Manager

A custom profile is an empty node that must be federated into a DM cell to run. Compared to a standalone server profile, there is no default server on the node that customizes the profile. There are no default applications on custom nodes. by co-customizing the profile, it becomes a managed node. After federation, the custom profile will have the node agent process, but there is no server process. You must use the management console of the DM to customize the empty nodes for production or other purposes. After the node agent is started, it responds to commands issued from the DM.

Go to Profile Management tool, click Create, select Custom profile, then click Next

Select the Advanced Profile creation option and click Next

Specifies the profile file name and directory (CUSTOM01). Click Next

All that remains is the default and the next step. After creation is complete, you are prompted to create a success. Click Finish

The newly created custom profile appears in the Profile Manager's profile list.

Create an Application Server (standalone) profile
Go to Profile Management tool, click Create, select profile type Application Server, click Next

In profile creation options, select Advanced Profile creation, click Next

Accept the default value. Click Next

Specifies the profile file name and the profile path. Accept the defaults and click Next

Specify the node name, server name and host name, accept the default, and click Next

To enable administrative security, enter an administrator username/password and click Next

Continue to the next step, accept the defaults, go here to cancel running the application server process as a Windows service, click Next

In the Web server definition, do not create a Web server definition, click Next

Click Create

After the profile has been created successfully, cancel the start of the "first step" console option and click Finish

Federated Standalone server node to Deployment Manager
The following actions also apply to situations where a custom profile is created but not yet federated to the deployment manager, and you can use the command AddNode to
Federated Node Federation to the deployment Manager
Open a Command window, change the current directory to the bin directory of the Deployment Manager profile, and execute the following command to view the status of the Deployment Manager.
Command: Serverstatus.bat-all-username Admin-password admin
If started, the command status returns "Deployment Manager" Dmgr "in started State"

If it does not start, the command returns "unable to access deployment Manager dmgr". It seems to have stopped "

If the deployment Manager "Dmgr" does not start, execute the following command to start the Deployment Manager
Startmanager.bat

Open a Command window and change the current directory to the bin directory of the application server profile.
Enter a command to view the startup status Serverstatus.bat-all-username Admin-password admin

If the server is in a stopped state, continue. Otherwise, execute the following command to stop the application server Server1
Stopserver.bat server1-username Admin-password Admin

After the application server stops, execute the following command to federate the node to the deployment Manager.
Addnode.bat Li 8879-username Admin-password admin
Li is host name, 8879 is port, default

Start Node
Before we created the 2 nodes of CUSTOM01 and APPSRV01, let's start the 2 nodes and prepare for the cluster.
First, go to the bin directory of CUSTOM01, execute the command serverstatus.bat-all-username Admin-password Admin to see if the node is started, if it does not start the execution Startnode.bat

In the Bon directory to APPSRV01, perform the same operation as before.
Create a cluster
The exciting step is to create the cluster. But before that,Please start the Deployment Manager and each node server first。 (DMGR01,CUSTOM01 and APPSRV01)
To access the Deployment Manager console

Enter your account password

After entering the management console, click on the menu: System Management > node, show node synchronization status and related node information

From the menu access: System Management > Node agent, you can view the status of Node agent

Access servers > Clusters > WebSphere Application Server cluster to display the current list of clusters. Because we did not create the cluster, the current list is empty. Click New.

Enter the cluster name testcluster, select Configure HTTP session memory to memory copy

Defines the first member of a cluster. Enter the member name (Application server name), where the node is located, and the weight information. Click Next

Create additional members. Enter the member name (NODE02SERVER1), select the node (LINODE02), and click Add Member

The list of members is updated, and multiple members can be added repeatedly. Click Next when you are done

Click Finish to start creating the cluster, and when the creation is complete, the newly created cluster appears in the list. The message window shows that changes need to be saved. Click Save Connection

After the save is complete, the display cluster is not started. Select the newly created cluster, then click Start, a little slow, wait patiently

The arrows become pure green, indicating that the nodes are all started. Otherwise, partially started. Reasons need to be identified.

Access Menu Server > Server type > WebSphere application Server, display the list of servers. It adds the 2 cluster members we just created.

install and simply test applications on a cluster
The cluster has been created, so tired, let's install the application
Access Menu Applications > Application types > WebSphere Enterprise applications, displays a list of enterprise applications. Click Install to install the enterprise application.

Select Local file System, find a war package, click Next
On the Select installation path, select Quick Install

Review the installation options. We do not make changes here, click Next

In the Map module to server step, select Cluster Testcluster, then select all modules, click Apply, then next, finish.
When you are done, click Save

Return to the list of enterprise applications and launch the application you just installed

View service port configuration for cluster members (application server)
Access server > Server type > WebSphere application Server, display the list of servers. Click Server Node01server1

Displays server details. Click on the port under communication


Displays the port information. The Application service port is: Wc_defaulthost, and the corresponding HTTPS service port is wc_defaulthost_secure.
Repeat the steps above to see the port number of the Node02server1.
Now open the browser, access the application Http://localhost:9081/snoop and Http://localhost:9082/snoop if the display is OK, the application and the cluster are working properly.
Configuring the IBM HTTP Server plug-in and Management Server
So far, we have configured the cluster environment. 2 Application servers access the application through different ports. The last step is to forward the Web request, allowing the application to be accessed via the default port 80. Without this step, what's the point of clustering?
Start the Web server plug-in configuration tool. Through the Start menu: Start > All Programs > IBM websphere > WebSphere customization Toolbox V8.0 > Tools > Web Server plug-in configuration tool
In the Web server plug-in Configuration Tool main window, click Add to configure the Web server plug-in runtime location

In the Add Web server plug-in Location dialog box, enter the installation root of Web server plugins and enter any meaningful name in the name. Click Finish

When the Web server plug-in that you just added runs, click Create in the Web server plug-in Configuration tab

Select the Web server type. We are using IBM HTTP Server V8, click Next

Specifies the configuration file full path $ihs_home/conf/httpd.conf for IBM HTTP server. Click Next

Configure the Management Server for IBM HTTP server. Enter the port and Admin user username/password and click Next

Set up the IBM HTTP Server Management Server. Register the Management Server as a Windows service. Click Next

Specify a unique Web server definition name, enter WebServer1 here, and click Next

Our current IHS and application servers are installed on a single machine, so check the (local) installation location of the WebSphere Application server and browse or enter the installation directory of was directly. Click Next

Choose to configure the Web server definition to that profile.

Click Configure, Complete!
View the IHS profile $ihs_home/conf/httpd.conf, whether the plug-in configuration is added to the configuration file (at the end)

Copy the configuration script that you just generated ibm\websphere\plugins\bin\configureweb_server_definitionname.bat to Ibm\websphere\appserver\ Bin (This example is Configrewebserver1.bat)
Open a Command window, change the current directory to the was directory where the Configrewebserver1.bat is located, and then run the script

Log in to the management console of the Deployment Manager, access the menu server > server type > Web server, and display a list of Web servers. You can see that our defined Web server WebServer1 appears in the list. If it does not start, you can start the Web server by selecting the Web server and then clicking the Start button.
Then, in the Windows service, locate the Web Server service to start.

It's done, but remember when we installed the application, we only chose the cluster testcluster, we didn't choose our web server, so you can access the http://lcoalhost/application now or not.
Locate the installed application, click on the Details page, click the Management module under the module

Select the cluster, application server and Web server (multiple options) in the cluster and server, then check the application module, click Apply, OK, and save the configuration changes.

Websphere8 Installing the Java EE program from the installation to the deployment test cluster application (very detailed)