How do I put CEP and Domain services in maintenance mode in a grid configuration? – meshIQ

A given service by a given name can only appear once in the domain (no duplicates are allowed). A CEP server that belongs to a grid configuration must always be started as part of the grid. It must never be started outside of the grid as a standalone CEP. Doing so will cause the domain server to misidentify it as a duplicate.

Grid configuration allows you to provide uninterrupted management in the event of server failures. See Setting up a grid configuration for setup instructions.

To allow services to be stopped while the primary CEP they are running on is restarted, meshIQ has added a maintenance mode setting. The maintenance mode will prevent failover for these services. While maintenance mode is in effect (is true), all experts under the CEP server are stopped and are displayed with gray icons. When maintenance mode is not in effect (is false), all experts under the CEP server are started and are displayed with green icons.

Maintenance Mode On	Maintenance Mode Off

Setting up a grid configuration

Before you enable maintenance mode, make sure you have set up a grid configuration for failover, as described below. When you are through, the \grid folder will contain subfolders for each CEP that belongs to the domain. For example:

/opt/nastel/AutopilotM6/naming/grid/[grid_name1]/registry.xml

/opt/nastel/AutopilotM6/naming/grid/[grid_name2]/registry.xml

/opt/nastel/AutopilotM6/naming/grid/[grid_name3]/registry.xml

To set up grid configuration:

Stop the CEP and domain services.
On the domain server, create one folder or directory called "grid" under /opt/nastel/AutopilotM6/naming.
Create another folder or directory under /opt/nastel/AutopilotM6/naming/grid. Use a name that accurately represents the collection of services you will be placing in the grid.
In the global.properties file located at /opt/nastel/AutopilotM6, add the two properties below:
```
property server.grid.vote.delay=1500
property server.grid.vote.sample=120000
```
In the node.properties file located on the CEP server at /opt/nastel/AutopilotM6/localhost, add the three properties below. The [grid_name] must be the user-defined name you used in step 3.
```
property server.grid=[grid_name]
property server.grid_enabled=true
property server.grid.pri=0
```
Copy the registry.xml file from the CEP server /opt/nastel/AutopilotM6/localhost directory and paste it into the Domain Server /opt/nastel/AutopilotM6/naming/grid/[grid_name] directory.
On the domain server, edit the $AUTOPILOT_HOME/naming/node.properties file, and add the following property to define the location of the grid. For example:
```
property server.grid.folder = /opt/nastel/AutopilotM6/naming/grid
```

Restart the domain and CEP services.

Setting maintenance mode

There are two ways to set maintenance mode: using a command line and through the user interface.

Set maintenance mode using a command line in apnet.exe

To set maintenance mode using a command line in apnet.exe, use apnet setMaintenanceMode.

Change the maintenance mode to true:

apnet setMaintenanceMode true

Change the maintenance mode to false:

apnet setMaintenanceMode false

To obtain the current maintenance mode status:

apnet isMaintenanceMode

Set maintenance mode through the M6 user console

To set maintenance mode through the M6 user console:

Expand the Domain Server.
Expand the SYSTEM folder.
Expand the DOMAIN_SERVER_GRID.
Expand Actions.
Right-click SetMaintenaceMode and select Choose Run Action....
The Enter Parameters for Action dialog opens.

To change the maintenance mode status:
1. To set the maintenance mode to true, enter "true" in the field and click OK. To confirm that the status was changed, collapse and expand Facts.
2. To set the maintenance mode to false, enter "false" in the field and click OK. To confirm that the status was changed, collapse and expand Facts.