Documentation

##### WSO2 WSAS 2.2-RC1

- Release Notes
- Contents
- Home

##### Downloads

- Releases

##### Documentation

- User Guide
- FAQs
- Installation Guide
- Source
- Running Behind a Proxy
- Data Services Guide
  - RDBMS Data Source
  - CSV Data Source
  - Excel Data Source
  - JNDI Data Source
- EJB Guide
- Clustering Guide
- JMX Guide
- XKMS Guide
- Changing Keys

##### Samples

- Chad
- Commodity Quote
- Data Services
- Flickr
- Javascript
- Jaxws
- JiBX
- Mtom
- STS
- Trader
- Tiny URL
- Metadata Exchange
- WS-Transfer
- XML Key Managment Specification
- Cluster Management

##### API Documentation

- Java Docs

##### Tools

- Code Generation
- Change Password
- Eclipse IDE Integration
- TCP Monitor
- WSDL2Code
- WSDL View
- Try It
- AAR Validation
- MAR Validation

##### Resources

- News

##### Get Involved

- Mailing Lists
- Integration

##### Project Information

- Project Team
- Issue Tracking
- License

# Cluster Management Sample Guide

## INTRODUCTION

We will use this sample to demonstrate the capabilities of WSO2 Web Services Application Server in a clustered configuration, highlighting the key features that are made possible using the admin.sh/admin.bat script. When WSAS is configured to run in clustered mode, the deployed services are said to be alive in a clustered environment. Clustering is enabled by editing the the WSO2WSAS/conf/axis2.xml file. i.e. Uncomment the <cluster> element. Then restart WSAS. Each WSAS instance in the cluster (a.k.a. a node) has the NodeManager service running. the script admin.sh/bat in WSO2WSAS_HOME is used to invoke the NodeManagerClient.

## Instruction

The four scripts given in the folder are samples of how you can use the admin.sh/bat script to do several things.

1. Reload a Configuration
   Copy the reloadconfiguration/reloadconfiguration.bat to WSO2WSAS_HOME/bin and run it. This will reload the Axis2 configuration for all nodes in the cluster with any configuration changes you may have made to the central URL repository & database.
2. Load Service Groups
   Copy the loadservicegroups/loadservicegroups.bat to WSO2WSAS_HOME/bin and run it. This will load the specified service groups on all nodes from a central URL repository & database.
3. Unload Service Groups
   Copy the unloadservicegroups/unloadservicegroups.bat to WSO2WSAS_HOME/bin and run it. This will remove the echo & version service groups from all nodes.
4. Apply Service Policy
   Copy the applyservicepolicy/applyservicepolicy.bat and policy.xml file to WSO2WSAS_HOME/bin and run the script. This will apply the specified policy to the version service on all nodes in the cluster.