Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

Apptivity 3.x

CAUSE:

DM has a property that specifies whether a given instance is serving as a primary or a backup.  The backup DM has properties that point to the primary.  If the primary instance goes down, the backup takes over.  Currently there is no way to set the backup DM properties through the Apptivity IDE.  You can however, do this on the command line or in a properties file.

FIX:

Create a properties file (dm1.properties) for the primary Distribution Manager (dm1) with the following properties:


apptivity.dmanager.host=pclab1
apptivity.dmanager.port=3111

(substitute your host name for pclab1 and the port you want to use)

Start up the DM with the following command line (all on one line):


java -Dapptivity.properties.file=dm1.properties
properties.apptivity.dmanager.DistributionManager

Create another properties file for the backup Distribution Manager (dm2).  It should contain the following:


apptivity.dmanager.host=pclab1
apptivity.dmanager.port=3222
apptivity.dmanager.mode=backup
apptivity.naming.port=3111
apptivity.naming.host=pclab1

The mode and the port are required parameters.  If you are running the backup on the same machine as the primary, it must have a different port number.

The command for starting the second DM is:


java -Dapptivity.properties.file=dm2.properties
properties.apptivity.dmanager.DistributionManager

A properties file for the Connection Manager (cm1.properties) should contain the following properties:


apptivity.cmanager.host=pclab1
apptivity.cmanager.port=4111
apptivity.cmanager.cfactoryName=AppName
apptivity.naming.port=3111
apptivity.naming.host=pclab1
apptivity.naming.port.alt=3222
apptivity.naming.host.alt=pclab1

You could then start up that Connection Manager with:


java -Dapptivity.properties.file=cm1.properties
progress.apptivity.cmanager.ComponentManager

If the primary Distribution Manager fails, the backup DM then takes over and becomes the primary server.