Monday 26 August 2013

Error 500: An error occurred while processing request: /ibm/console/applicationServerCollection.do


Hi all,

This is the scenario where I was getting following error while trying to navigate any of the tab from Websphere Administration console.

Error 500: An error occurred while processing request: /ibm/console/applicationServerCollection.do



when I checked the log files I have also got another error:

0000001a WorkSpaceMast E Unable to create temp file for document:

Unable to create temp file for document


Cause:

After Net surfing I figured out the error is mainly because of the permissions issue.
Normally we have different WAS user for start and stop the WAS services. But sometime if we start and stop the services with root user, the permissions of some files getting changed to root.
In this case some files are owned by root user which is preventing the WAS user to write the files to tmp directory which are created while deploying the application.

Solution:

First we check the permissions of the following files ans change the owner to the WAS user:WAS group.
  • <was_install_root>/Appserver/config/temp
  • <was_install_root>/Appserver/logs/ffdc
Or
If possible try to change ownership of everything under <was_install_path>/Appserve to the WAS user:WAS group

In my case it is working fine and hope this will help you to resolve your issue.

Effort only fully releases its reward after a person refuses to quit.”

Regards,
Akhilesh B. Humbe

Monday 5 August 2013

Could not make a connection to the IBM HTTP Administration server on node

Hi all,

I am currently using IBM Http Server v8.0 and configured it with a standalone WebSphere Application Server.I created a web server using WebSphere Application Server (WAS) v8.5 administrative console. And now I am unable to start or stop the IHS web server as well as not getting configuration file (Path :Server >Server Type >Web Server >webserver1 >configuration file ) from the WAS admin console. And getting the error  Could not make a connection to the IBM HTTP Administration server on node while trying this.



Cause:

When you Install the IBM HTTP server, same time it is necessary to configure the IHS Admin Server on the same system.. For previous versions of IBM HTTP Server (IHS), including v7.0 and prior, when you installed IHS it would automatically configure the IHS Admin Server. IHS Admin server working as the communication agent between IHS ans WAS. When you are using IHS on a WebSphere Node (part of a WAS ND Cell), it is not necessary to use the IHS Admin Server, because the WAS node agent does the administration but in case of standalone Websphere application server we need to configure it.

When you install IHS v8.0 it does NOT automatically configure the IHS Admin Server. So, you must do this yourself using one of the following methods. You can use the new Plug-in Configuration Tool (PCT) which is part of the new WebSphere Customization Toolbox (WCT) or you can use the htpasswd.bat in command line Interface.

Note: The cause may be you are configured it properly but the windows services IBM HTTP Administration for Websphere Application server is not started, so first confirm it and then go forword.

I have done this on the Windows operating system using WebSphere Customization Toolbox (WCT) with following steps :

Prerequisite:

When we use an administrative user for installation on a Windows operating system, a Windows service is automatically created to autostart the application server or for that the installer user account must have the following user rights:
  • Act as part of the operating system
  • Log on as a service
For this click on Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignments and set the advanced options and then.

  1. Install IBM Installation Manager.
  2. Install your WebSphere Application Server product.
  3. Install IBM HTTP Server or another supported web server.
  4. Install the web server plug-ins.
  5. Install the WebSphere Customization Toolbox.
Procedure:
  1. Open the Websphere Customization Toolbox, and launch the Web Server Plug-ins Configuration Tool.
    Select a Web Server Plug-ins runtime location. If the location of a previously installed web server plug-in that you want to use is not in the list Click Add. Enter a name for the web server plug-in location.


  2. Enter the location or Click Browse, find the location, and click OK.


  3. Click Create.
  4. Select the type of web server that you are configuring, and click Next.


  5. Click Browse to select the configuration file, verify that the web server port is correct, and then click Next when you are finishedSelect the file and not just the directory of the file. Some web servers have two configuration files and require you to browse for each file.
    For IBM HTTP Server: IHS_root/conf/httpd.conf


  6. Select Setup IBM HTTP Server Administration Server. Specify a port number on which the IBM HTTP administration server will communicate and Optionally, select Create a user ID for IBM Server Administration Server authentication and enter a user ID and password to authenticate to the IBM HTTP Server administrative server from the administrative console.Click Next.


  7. Specify the system user ID and group to have write permission to IBM HTTP Server, the IBM HTTP administrative server, and the web server plug-in configuration files. And Set up the IBM HTTP Server Administration Server to run as a Window service if you want. Click Next.


  8. Specify a unique name for the web server definition, and click Next.


  9. In Select the configuration scenario click Browse, find the installation location of WebSphere Application Server (app_server_root), and click OK. Click Next.


  10. Select the profile to configure with the current web server plug-in, and click Next.


  11. Review the summary information, and click Finish.


  12. If a problem occurs and the installation is unsuccessful, examine the logs in the plugins_root/logs directory. Correct any problems and re-configure.
  13. If all goes properly, point your browser to http://Host_name_of_Web_server_machine/snoop to test the web server plug-in.

Hope this will help you to fix the problem.

Effort only fully releases its reward after a person refuses to quit.”

Regards,
Akhilesh B. Humbe









Sunday 7 July 2013

How to Manually generate javacores for WAS processes ?


This is the method recommended in situations where the server hangs shortly after startup. It is also recommended when other not work, or when the system is under extremely heavy load.

This method uses an alternative method for starting an application server in a mode which accepts the Ctrl + Break keyboard combination to trigger a javacore. This method requires some preparation steps, and the affected server will need to be restarted. This method has the advantage that generating javacores does not require the additional overhead of using another tool (such as the administrative console or wsadmin tool).

Procedure:

  1. Open the command prompt.

  2. Navigate to "bin" subdirectory under the server's profile root (<WAS_HOME>\profiles\<PROFILE_NAME>\bin)

  3. From the "bin" subdirectory, execute the one of the following commands. Choose the command from the list below based on the type of server that the javacore will be generated from.

    Application Servers
    startServer.bat SERVER_NAME -script

    Nodeagents
    startNode.bat -script

    Deployment Managers (DMGR)
    startManager.bat -script

  4. This will generate a script named start_<SERVER_NAME>.bat in the current directory.

  5. Stop the server that requires the javacore.

  6. Using the new script, start the application server (or nodeagent or deployment manager).
    start_ server1 .bat

  7. While the server is running, from the same command prompt window, issue the keyboard combination Ctrl + Break. Output on the screen should immediately display that a javacore is being generated.

  8. Repeat step 7 as many times as required to collect javacores.

  9. Note the location of the javacores and collect them. They will usually be output to the current directory or the profile root.
  1. The server can be stopped either by issuing a stopServer.bat command, or terminated immediately with a keyboard combination Ctrl + C.

Hope this post will help for your environment.

Related Post:

Effort only fully releases its reward after a person refuses to quit.”

Regards,
Akhilesh B. Humbe

Generating Heapdump, javacore and coredump by using WAS console.

It is much more easy to generate heapdump, coredump and javacores with WAS v8.0 and v8.5
You can produce javacores (and heapdumps and coredumps) from the admin console by following the steps below, referenced in the Information Center article Collecting Java dumps and core files using the administrative console.

Procedure:

  1. Navigate to Troubleshooting > Java dumps and cores
  2. Select the server(s) to collect dumps from
  3. Click on Java Core, System Dump, or Heap Dump to produce the specified file.
  4. Navigate to "bin" subdirectory under the server's profile root and collect the dump file.

Related Post:

Effort only fully releases its reward after a person refuses to quit.”

Regards,
Akhilesh B. Humbe

Wednesday 3 July 2013

WebSphere Application Server V8.5 Fix Pack Installation

Hi all,

Here we are going to discuss the scenario where I installed the fix pack_2 on Websphere Application server v8.5. For Installation we are using Installation manager instated of Update Installer. Installation manager is much simpler than Update Installer which was we used for v7.

Prerequisites:
  1. Install IBM Installation Manager.
  2. Install Websphere Application Server v8.5

Procedure:
  1. To install Fix Pack 8.5.0.x using a local repository, download the respective .zip files for your respective products

    Note: If part1 and part2 .zip files exist, unzip the part1 and part2 .zip files to the same folder on your local machine. Both .zip files are required for installation of the fix pack. When unzipping part2, the Windows operating system might warn you that a directory with the same name already exists. Allow the tool to merge the directories; the tool does not overwrite any files.

  2. Then point Installation Manager to the repository.xml file on your local machine. To add the repository:
    Start Installation Manager and in the top menu, click File > Preferences.

  1. Select Repositories. Click Add Repository.
    Enter the path to the repository.xml file in the location containing the repository files and click ok

Note: Before Starting Installation  Stop all WebSphere Application Server and IBM HTTP Server processes and backup the configuration files 
  1. On Installation Manager Home Screen Click on Update Logo.

  1. In Update Packages screen it will list you the Package you Install. Check the package and click on Next.

  1. Accept the terms in license agreement and click Next. Then on successive screen check the dependencies and Installation Directory, Shared Resource Directory and click on Update.

  1. After successful Update you will get the following Screen showing updated version of your Environment click Finish.


Hope this will help you to Install the latest fix pack using Installation Manager in your environment. And follow the same steps to update the supplements (Web Server Plugins/JDK ) also.
Related Topic



Effort only fully releases its reward after a person refuses to quit.”

Regards,
Akhilesh B. Humbe

Sunday 23 June 2013

Moving a profile to a new host in Websphere Application Server


Hi all,

I have a scenario where I am working with two servers and both are having same setup one is my primary and second is standby. Antecedently my profile is crashed on primary setup while doing some R&D. It is best practice to take backup of your profile before doing any changes but I didn't. After a lot of searching I got a solution to move profile from one server to different. Then I recover my profile by moving standby profile to primary. Here is the process I followed.

Procedure:

  1. Stop all the processes running related to the profile of witch you want to move.
  2. Then run the manageprofiles command with the backupProfile option, and specify the profile
    Name to be backed up and the backup file name with appropoiate location.
    manageprofile.bat -backupProfile -profileName AppSrv02 -backupFile D:\IBM\WebSphere\AppServer\profiles\AppSrv02Backup.zip
  1. When the backup has finished, transfer the backup file from the one server to the another
    server.and run manageprofiles using the restoreProfile option as follows
    manageprofile.bat -restoreProfile -backupFile D:\IBM\WebSphere\AppServer\profiles\AppSrv02Backup.zip
  1. start up wsadmin without connecting to a WebSphere process
    wsadmin.bat -conntype NONE -lang jython
  2. Once wsadmin is ready, invoke the changeHostName utility command for the AdminTask object as
    shows below.
    wsadmin>AdminTask.changeHostName ('[-interactive]')
    *Node Name (nodeName): Node Name of your Profile
    *Host Name (hostName): New host name
    System Name (systemName): (oprional)
    Regenerate Certificates (regenDefaultCert):(oprional)

    Press F to finish.
  1. Invoke the AdminConfig.save() utility command to save changes.
  2. Start the application server and you can see the changes reflected in the admin console

Hope this will help you to change you the only hostname of your profile also.



Effort only fully releases its reward after a person refuses to quit.”

Regards,
Akhilesh B. Humbe

Wednesday 12 June 2013

How to Delete Websphere Application Server Profile ?


Hi all,

Here we are going to discuss how to delete the profile in Websphere Application server environment. I used the following to remove application server profile.

Note: Before deleting profile we need to stop all services associate with it.
e.g. Stop the Application server and webServer if configured.

Procedure:
  1. First list all profiles on a server:
    List the profile using one of these commands
    Windows: was_install_dir\bin\manageprofiles.bat –listProfiles
    UNIX/Linux: was_install_dir/bin/manageprofiles.sh –listProfiles
  2. Remove a WebSphere Application Server profile:
    Delete the profile using one of these commands:
    On Windows: was_install_dir\bin\manageprofiles.bat –delete –profileName profile
    On UNIX/Linux: was_install_dir/bin/manageprofiles.sh –delete –profileName profile
  3. Ensure that references to the deleted profile are removed from the profile registry by running the following command:
    On Windows: was_install_dir\bin\manageprofiles.bat –validateAndUpdateRegistry
    On UNIX/Linux: was_install_dir/bin/manageprofiles.sh –validateAndUpdateRegistry
  4. Delete the profile directory tree (if it was not deleted by the previous action).
    Delete the profile Directory using one of these commands:
    On Windows: was_install_dir\profiles\rmdir /s profileDirectory
    On UNIX/Linux: was_install_dir\profiles\rm -R profileDirectory

Hope this will help you to delete the profile in your environment and for more option of manageprofile run the command manageprofiles.bat –help

Effort only fully releases its reward after a person refuses to quit.”

Regards,
Akhilesh B. Humbe

Monday 3 June 2013

What is Edge Side Include (ESI) ?

ESI caching is an in-memory caching solution that is implemented through the web server plug-in. The ESI processor can cache pages or fragments of pages at the HTTP server layer.
The Web server plug-in contains a built-in ESI processor. The ESI processor can cache whole pages, as well as fragments, providing a higher cache hit ratio. The cache implemented by the ESI processor is an in-memory cache, not a disk cache, therefore, the cache entries are not saved when the Web server is restarted.

When a request is received by the Web server plug-in, it is sent to the ESI processor, unless the ESI processor is disabled. It is enabled by default. If a cache miss occurs, a Surrogate-Capabilities header is added to the request and the request is forwarded to the WebSphere Application Server. If servlet caching is enabled in the application server, and the response is edge cacheable, the application server returns a Surrogate-Control header in response to the WebSphere Application Server plug-in.

The value of the Surrogate-Control response header contains the list of rules that are used by the ESI processor to generate the cache ID. The response is then stored in the ESI cache, using the cache ID as the key. For each ESI include tag in the body of the response, a new request is processed so that each nested include results in either a cache hit or another request that forwards to the application server. When all nested includes have been processed, the page is assembled and returned to the client.

The ESI processor is configurable through the WebSphere Web server plug-in configuration file plugin-cfg.xml. The following is an example of the beginning of this file, which illustrates the ESI configuration options.

After the basic of ESI now the question is How do I use the application cache monitor to display static content on the plug-in Edge Side Include (ESI) cache and clear the plug-in ESI cache without a restart of the web server?

There is default application, the cache monitor application is located in the installableApps directory and is installed as "Dynamic Cache Monitor: The main functions of the "Dynamic Cache Monitor" (CacheMonitor) application as it relates to the static caching in the plug-in ESI cache are:
  • You can manually change the state of the cache without having to restart the web server
  • You can display what is being cached in the plug-in ESI Cache
These functions are only related to static caching in the plug-in ESI. There are additional function related to dynamic caching referenced in the information center topic Cache monitor.
To manage and monitor static caching in the plug-in ESI cache using the WebSphere Application Server application cache monitor go through the following steps.

1. Both the CacheMonitor.ear (Dynamic Cache Monitor ) and DyncCacheEsi.ear     (DyncCacheEsi) applications must be installed. 


2. Change the 3 critical values for management of the plug-in ESI cache and for monitoring using the cache monitor application in the plugin-cfg.xml file



Set esiEnable =true
esiEnable will enable or disable the ESI processor. ESI is enabled by default. If ESI is disabled, then the other ESI options are ignored.

Set esiMaxCacheSize= 1024
esiMaxCacheSize is the maximum size of the cache in 1K byte units. The default maximum size of the cache is 1 megabyte. Each web server process will contain its own cache, so consideration should be given to the cache size as it related to the number of plug-in processes. If the response content has a content-length response header, the web server plug-in checks for the response content size. If the size of the response content body is larger than the available ESI caching space, the response is passed through without being handled by ESI.

Set esiInvalidationMonitor =true
esiInvalidationMonitor, specifies if the ESI processor should receive invalidation from the application server.

3. Following are 3 methods by which entries are removed or made invalid from the ESI cache:

Expired timeout
The default Timeout values is set to 300 seconds. You can change the timeout value by adding the property com.ibm.servlet.file.esi.timeOut to the Java virtual machine (JVM) command line parameters. The following example shows how to set a one minute timeout on static data cached in the plug-in:

-Dcom.ibm.servlet.file.esi.timeOut=60

Purge entry to make room for newer entries:
When the plug-in ESI cache is filled, entries will be purged from the cache based on their pending expiration (those closest to expiration will be purged first).

Explicit invalidation:
The application server or cache monitor application sends an explicit invalidation for a group of entries. For this mechanism to be enabled, the esiInvalidationMonitor property must be set to true and the cache monitor DynaCacheEsi.ear applications must be installed on the application server. The DynaCacheEsi application is located in the installableApps directory and is named DynaCacheEsi.ear .

4. Go to the WebSphere Application Server > Server_Name > Web container and enable servlet Caching



5. To display the static plug-in ESI cache :


http://<hostName>:port/cachemonitor/
where hostname is the hostname of the application server or the web server (if the cache monitor application is mapped to a web server) port is the port of the application sever or the web server.


Notes: You must click Refresh from the Edge Statistics Panel to get updated statistics

Effort only fully releases its reward after a person refuses to quit.”
Regards,
Akhilesh B. Humbe

Sunday 2 June 2013

IBM HTTP Server (Web Server) and Websphere Application Server

 Hi all,
Here we are going to discuss very basic concepts of Web server and application server.
Following are very basic questions but normally we confused on this.
  1. What is difference between Web application server and web server ? like we are using IBM WAS and IHS.
  2. Can I use only one of them without using other ? like can I host a JSP on WAS without using IHS ?
The basic answer for this is, a web server just serves content. In particular, it doesn't have a Java web container or ejb container. An application server has these two extra Java pieces. You can use one without the other. However, you cannot run a J2EE application on a web server. You can certainly host a JSP on WAS without using IHS.
 
The Web server:
A Web server handles the HTTP protocol. If user wants to access any application from the Web browser , the Web server receives an HTTP request first and it responds with an HTTP response, such as sending back an HTML page. After processing a request, a Web server may respond with a static HTML page or image, send a redirect, or delegate the dynamic response generation to some other program. When a request comes into the Web server, the Web server simply passes the request to the program (Application) best able to handle it. The Web server doesn't provide any functionality beyond simply providing an environment in which the server-side program(Application) can execute and pass back the generated responses. The server-side program usually provides for itself such functions as transaction processing, database connectivity, and messaging.

While a Web server may not itself support transactions or database connection pooling, it may employ various strategies for fault tolerance and scalability such as load balancing, caching, and clustering features oftentimes erroneously assigned as features reserved only for application servers.
The Application server:
An application server exposes business logic to client applications through various protocols, possibly including HTTP. While a Web server mainly deals with sending HTML for display in a Web browser, an application server provides access to business logic for use by client application programs. The application program can use this logic just as it would call a method on an object (or a function in the procedural world). Such application server clients can include GUIs (graphical user interface) running on a PC, a Web server, or even other application servers. The information traveling back and forth between an application server and its client is not restricted to simple display markup. Instead, the information is program logic. Since the logic takes the form of data and method calls and dynamic HTML, the client can employ the exposed business logic however it wants. In most cases, the server exposes this business logic through a component API, such as the EJB (Enterprise JavaBean) component model found on J2EE (Java 2 Platform, Enterprise Edition) application servers. Moreover, the application server manages its own resources. Such gate-keeping duties include security, transaction processing, resource pooling, and messaging.

Like a Web server, an application server may also employ various scalability and fault-tolerance techniques. The Web container in WebSphere Application Server has an embedded HTTP transport (the so-called WebContainer Inbound Chain), which allows for direct connection to the application without the need for a separate Web server. While using this transport as a Web server is very handy for testing or development purposes it should not be used in production environments. If the users connect directly to the WebContainer Inbound Chain, then they bypass the plug-in and the workload management it performs, as well as the failover and session affinity mechanisms it provides and not to mention the ESI dynamic caching function in the Web server plug-in, if enabled. For performance and security reasons, it is recommended that you use a stand-alone Web server and the HTTP plug-in for the Web server in a production environment.
Effort only fully releases its reward after a person refuses to quit.”
Regards,
Akhilesh B. Humbe

Friday 31 May 2013

Creating Host level Clustering or Horizontal Clustering for Websphere Application server v8.5

Hi all,
Here are the scenario where we going to discuss the horizontal clustering of Websphere Application servers v8.5. Horizontal clustering, sometimes referred to as scaling out, is adding physical machines to increase the performance or capacity of a cluster pool. Typically, horizontal scaling increases the availability of the clustered application at the cost of increased maintenance. Horizontal clustering can add capacity and increased throughput to a clustered application; use this type of clustering in most instances. Here we have two machines Machine A and Machine B

Prerequisites:

Install WAS ND using the new IBM Installation Manager on both machines.
Create a Deployment Manager profile on Machine A.

Steps to create a node profile on Machine A
  1. Before we create the profile we will log into the Administrative console of our running deployment manager. Navigate to the System administration >Deployment Manager and note down the SOAP Port for Node Creation.
  1. Navigate to the System administration section located in the left-hand-side panel of the admin console. In the Nodes screen we get a listing of the available nodes and their status.
  1. Launch the PMT tool. To launch the PMT tool, On Windows you can use the Programs menu and Click Create the start the wizard
  1. Select Custom profile
  1. Click Next to continue on to the Profile Creation options page and select advanced profile creation. We do not want to use the typical profile creation option as we will be given default profile naming conventions and as we will not be able to decide on the location path for the node profile.
  1. Click Next to move onto the Profile Name and Location screen. enter nodeName in the Profile namefield and change the Profile directory path to be as follows: <was_root>/profiles/ nodeName for example: D:\IBM\WebSphere8\AppServer\profiles\node01
  2. We will not set the “Make this profile the default” field as we want the Deployment manager to be the default profile.
  3. Click Next to move on to the Node and Host Name screen. Enter Testnode01 for both he Node name and localhost for HostName of Machine for Hostname fields.
  1. Click Next to define the node federation options. On this screen we define the location of a running deployment manager. We need to know the hostname and SOAP port of the dmgr. If the dmgr is running on the same machine we can use local host of the hostname as specified in your localhost. When you click next the node will be created and automatically federated in to the dmgr’s managed cell. This node becomes a managed node.The federate this node later option can be used if you wish to post pone federation until another time.
Note:A command line tool called addNode.bat or addNode.sh can be used to federate a node.
  1. Click Next.
  1. On the Security Certificate (Part 2)screen the PMT will set a default certificate for the node.
  2. After verifying the certificate definition for the node, Click Next.
  3. The next screen presented is the Port Values screen. Accept the default, but take note of the ports. Key ports have been incremented by 1 from the dmgr ports. Click Next to review the summary and then click Create to being the Testnode01 profile creation process.
  1. Once the profile creation has finished you is it possible run the First Steps. In this example we will not run the FSC. We are going to start the node manually via the command line.
  2. Click Finish. You will see the PMT profile tab now lists the new Testnode01 profile.
  3. Close the PMT.
  4. Now that the Testnode01 profile has been created and federated into the cell. We will look into the Administrative console to see the new node is now listed along with the dmgr node. Open the Administrative console and navigate to the System Administration>Nodes section as we did at the beginning of the module. We can now see Testnode01 has been federated into the cell and is now a managed node.

Note: We did not need to restart the Deployment Manager to see the additional node. In older versions of WAS a restart of the dmgr was a requirement.

Steps to create a node profile on Machine B

Follow the same steps to create the Testnode02 on machine B as described for Machine A. But in step 9 while define the node federation options we need to defile the hostname and SOAP port of the dmgr running on the Machine A. Now that the Testnode02 profile has been created and federated into the cell. We will look into the Administrative console to see the new node is now listed along with the dmgr node. Open the Administrative console and navigate to the System Administration>Nodes section as we did at the beginning of the module. We can now see Testnode02 has been federated into the cell and is now a managed node.



Creating cluster in horizontally scaled Cell design Creating a cluster
It is possible to create a cluster in different ways. In our example we will create a JVM on Testnode01, then upgrade it to a cluster and add another clone.

To create a server, follow these steps:
  1. Select Server Type form the Server section located in the left-hand-side of the administrative console, then click WebSphere Application Servers.
  2. In the Application server listing screen, click New.

  1. Within the Create a new application server screen, select Testnode01 (we have two nodes on this system). Type Testserver01 in the server name field. Click Next.


  1. On the following page, select Default template. In production you would use default.
  2. Click Next
  3. The next screen will present an option to turn toggle the Generate unique ports option. This setting generates unique port numbers for every transport that is defined in the source server, so that the resulting server that is created will not have transports which conflict with the original server or any other servers defined on the same node. When you are installing multiple JVMS on the same systems, you can get conflicts with port numbers. If you design your Cell to allow only one single JVM per node, then you could use the default port options, however this can be problematic.
  4. Review and click Finish.

  1. Once the server has been created, click Save to ensure that the configuration is permanently stored.
  2. You can see that the server is currently stopped.
  1. Validating the node synchronisation
  2. If we quickly navigate to the Nodes view, we will see that the Nodes are now out of Sync. To display Node synchronisation status, then navigate to System Administration > Nodes
  3. Below is what you should see, if any of the nodes turn green it means they are one again in sync with the deployment manager.
  4. After a period of time the node will sync.
  5. It is possible for the node and cell configuration to be out of synchronization after this operation is performed. If problems persist, use Full Resynchronize.
Starting the server
We will not start Testserver01 using the console, then we will stop is via the command line after viewing the logs.
  1. Navigate to Servers > Server Types > WebSphere application servers
  2. Now we need to start the server and view the server’s logs.
  3. Select Testserver01 Click Start
  4. Open a command prompt or shell to <was_root>/profiles/Testnode01/logs/Tesrserver01
  5. Open the SystemOut.log
  6. Once you have opened the server’s log file, then scroll to the bottom of the log file and look for line similar to the following:[01/11/11 11:38:45:528 GMT] 00000000 WsServerImpl A WSVR0001I: Server Testserver01 open for e-business
Creating a cluster and clone from an existing server
In this section we take our existing JVM (Testserver01) and make it into a clone (member) of a cluster.
Steps to create a cluster and convert a server into a clone
  1. Navigate to Servers > Clusters > WebSphere application server clusters as seen below.
A list of clusters is presented. We have no cluster at this point, so it is empty. Click New to start the “Create a new cluster” wizard.

  1. Type the name Testcluster01 into the Cluster name field.
  1. Click Next to move onto the Create first cluster member screen. In this example we want to convert an existing server to become a member of this cluster. Select the create the member using an existing application server as a template option as seen below

  1. Click Next to move onto the screen where you can add additional cluster members. In this case we are going to add a new member to TestNode02.
  2. Click the Add member button to add the new cluster member, the result is as seen below.
  1. Click Next to review the final summary screen, and then click Finish to create the cluster.
  2. Click Save to ensure the new cluster is saved.

  1. The WebSphere application servers clusters view will list the current cluster in the cell.
  2. Make sure you are back on the Cluster view screen and click Start
  3. You can see that the Status is Partially started. This is because each member (clone) will be started in sequence and once both servers (members) as started the console will report a green status meaning the cluster if full started. Full started means that all members of the cluster have started. Below is an example for a fully started cluster
  4. We have now completed the essentials of the cluster creation process. What we need to do now is deploy an application to the cluster so we can verify that the Cluster works and we can access each server’s (cluster members) web-container.
Hope this will help you to create a cluster and we will see how deploy an application to the cluster so we can verify that the Cluster works and we can access each server’s (cluster members) web-container in next blog.

Effort only fully releases its rewards after a person refuses to quit”

Regards,
Akhilesh B. Humbe

Popular Posts