Saturday 4 April 2015

Disabling or enabling a high availability manager -MS

A unique HAManagerService configuration object exists for every core group member. The enable attribute in this configuration object determines if the high availability manager is enabled or disabled for the corresponding process. When the enable attribute is set to true,the high availability manager is enabled.when the enable attribute is set to false, the high availability manager is disabled. By default ,the high availability manager is enabled. if the setting for the enable attribute is changed, the corresponding process must be restarted before the change goes into effect.You must use the wsadmin tool to disable or enable a high availability manager.
First You must ensure you need to use a high availability manager to manage members of a core group.
to Avoid the trouble : when you disable the high availability manager,make sure that you disable it for all the servers in core group so that all members are disabled. Do not disable the high availability manager for select members of the core group.

Procedure to disable or enable  high availability manager

1.In the administrative console, navigate to the Core Group Service Page for the Process
      
  From Deployment manger ,
              for  Deployment Manager click System Administration -> Deployment manager -> Core group service
            for Node Agent click System Administration -> Node agent-> node_agent-> Core group service
            for an application server click Servers->Server Types-> WebSphere application servers-> server_name -> Core group service

2.If you want to disable the high availability manager for this process, deselect the Enable service at server start up option.

3.If you want to enable the high availability manager for this process, select the Enable service at server start up option.

4. Click on OK and  then click Review.

5.select Synchronize changes with nodes , and then click Save.

6. Restart all of the processes for which you changed the Enable service at server start up property setting.

Now processes start with the high availability manager in the changed state.

Verify                                              
check the Systemout  log file for following messages:

           HMGR005l: The Single Server DCS Core Stack Transport has been started for core group DefaultCoreGroup

The Above message indicates that the high availability manager is disabled because the hihg availability manager communication transport can only establish communication with a single server process.

   HMGR001l: The DCS Core Stack Transport has been started for core group DefaultCoreGroup There are x members.

The above message indicates that the high availability manager is enabled because the high  availability manager communication transport can establish communication with multiple server processes. X indicates the numbers of server processes with which communication is established.

No comments:

Post a Comment