Page History

...

The secondary server accepts no client connection while in its hot-standby (passive) role, but is prepared for an immediate transition to the Active role as soon as it detects that the Active Server is unavailable. If the primary fails, all Fiorano applications fail over from the primary and reconnect to the designated secondary backup broker.
The primary and secondary broker-pair use the replication channel to routinely seek the heartbeat of the other and watch for any interruption in the data flow or connection to switch states. A locking mechanism (explained below) can also be employed to determine the state of the servers.

...

• Upon startup, the Server enters into WAITING state. In this state, the server waits for its backup server to connect to it. This is the initial synchronization state, which is required to sync up the primary server with the secondary avoiding any message loss. This server changes state if one of the following occurs:
  • Switch to PASSIVE SYNC state: If the HA channel is established and the other server is in the STANDALONE state.
  • Switch to PASSIVE(STANDBY) SYNC or ACTIVE SYNC state: If the HA channel is established and the other server is also in WAITING state, then the servers assumes themselves as being in Active or Passive roles depending on the Repository Timestamps (whichever server has the latest timestamp is assumed to be the primary).
    If the repository does not have Timestamps (the server-store is cleaned up), then the server which is configured as primary turns to ACTIVE SYNC.

• When the Server is actively serving clients and its backup server is not running or if the HA transport channel is broken and it has the lock over the lockfile, the state of the server is STANDALONE. If the server in STANDALONE state establishes the HA channel and the other server is in WAITING state, then the STANDALONE server shifts to ACTIVE SYNC state. A passive (standby) server can switch to STANDALONE if the other server is not running or if the transport channel is broken and it acquires the lock over the LockFile.
• When the Server is in ACTIVE SYNC state, the server starts synchronizing its data with the backup server which is in PASSIVE SYNC. The Server in ACTIVE SYNC continues to serve its clients. Completion of the Runtime Synchronization Protocol causes a transition of the backup server to the ACTIVE state and the server in PASSIVE SYNC state moves to PASSIVE state.
• Once the Primary Server completes the synchronization, it enters into the ACTIVE state and begins actively transmitting state information and Call Replications onto the PASSIVE Server. At this point, if there is a failure of the ACTIVE server, the Hot Standby PASSIVE Server is ready to move into the STANDLONE STANDALONE state and starts accepting requests from the clients.
• An active server can switch to the WAITING state if the transport channel is broken and it loses the lock over the LockFile. A STANDALONE server can switch to the WAITING state if it loses the lock over the lock file.
• Whenever there is a change in the server state, it broadcasts the present and previous state to the Backup Server. The Server transition is a function of its own state, the present and previous state of the Backup Server and whether or not it holds the lock over the LockFile.

...

...

1. Create directory "dirA" which is to be shared and Login as root.

2. Check the status of the Network File System server using the command below:

   Code Block
   $ /etc/init.d/nfs status

3. If the server has not been started, start it using the command below:

   Code Block
   $ /etc/init.d/nfs start

4. Open NFS Server Configuration.

   Code Block
   $system-config-nfs

5. Add the path of the directory to be shared, permissions, and host(s).

   Code Block
   $chmod o+rwx path_of_dirA -R

...

1. Create directory "dirB" where contents of MachineA:<path_of_dirA> need to be stored.

2. Login as root and open the File Systems Table.

   Code Block
   $vi /etc/fstab

3. Add an entry in the format below:

   Code Block
   MachineA: path_of_dirA path_of_local_dirB nfs defaults

   Code Block
   title Example
   192.168.1.209:/home/user1/Desktop/dirA/ /home/user2/Desktop/dirB/ nfs defaults

4. Run mount command:

   Code Block
   $mount -a

Shared DB in the third Machine

When DB is stored in on a third machine, instead of primary or secondary, two machines have to be allowed to access this shared resource. While adding the hosts to the NFS server configuration, add the corresponding netmask.

...

1. Create the directory that needs to be shared and login as root.
2. Edit the samba configuration file (open /etc/samba/smb.conf to edit).
3. Add the sharing details at end of the file.

Template A template is provided below, followed by an example:

...

1. Open the HA profile (replicated).
2. Right-click the profile and click Openclick the FES Replicated HA option.
   Image Removed
   Image Added
   Figure 3: Selection of FES Replicated HA
    
3. The FES Replicated HA dialog box gets displayed.
   
   
   Figure 4: FES Replicated HA dialog box

...

• BackupHAIPAddress - IP Address of backup server in HA mode. This parameter is mandatory to run HA.
• BackupHAPort - Port of the Backup server on which peer is listening for status requests send by another server. [This parameter is same as the 'Port' parameter but it specifies the port used by the backup server]
• Port - This is the port on which the HA Manager is going to listen for connections from its backup server. Once the connection is established, it starts serving as the back channel for broadcasting the state of the servers to the backup server whenever there is a state transition.
• BackupRMIServerPort - Port used by the backup server to bind the Mx4J RMI Connector.
• RMIServerPort – Port used by the server to bind the Mx4j Rmi RMI Connector.
• LockFile - Full path of the file which will be used for determining the HA states. This file should be present in the third machine and always available to the HA servers with all permissions. This parameter is mandatory to run HA. [Also, See 'GatewayServerIPAddress' parameter while configuring.]
• GatewayServerIPAddress -IP address of Gateway machine. This is used to detect network failures. It is recommended that the IP address specified should be of belong to a machine that is always available on the network. It is mandatory to specify this parameter. This parameter should always be the IP Address of the machine hosting the LockFile.
• GatewayServerPort - In Replication HA mode, network failure is detected by using the gateway server machine. Specifies the port on which gateWay machine is listening for incoming requests
• PingInterval - Time interval (in ms) after which the remote server is pinged in Replication HA mode.
• ActiveLockReAcquistionInterval - This parameter indicates the wait Interval between each attempt to acquire the lock for active server. This value should be in multiples of pingInterval/2 otherwise, server may try to acquire the lock on the next multiple of pingInterval/2.
• PassiveLockAcquistionInterval - This parameter indicates the wait Interval for the passive server to acquire the lock when the link between active and passive server is down. This value should be greater than '2*ActiveLockReacquisitionInterval', otherwise, an exception will be thrown. Server won't The server will not start if this value is not set properly.
• AppRepositoryPath - Path of the enterprise server application repository. FES stores event process information in this directory. Bydefault By default, its value is $FIORANO_INSTALL_DIR/server/repository/applications.
• Component RepositoryPath - Specifies the Component Repository Path. FES stores services' information in this directory. By default its value is $FIORANO_ INSTALL_DIR/server/repository/components
• FPSRepositoryPath - Path of the Fiorano Peer server Configurations repository. FES stores peer server configurations in this directory.By default its value is $FIORANO_INSTALL_DIR/runtimedata/EnterpriseServers/<ProfileName>/FES/peers.
• ApplicationSyncType - Sync Type for Application Repository 0 - FULL SYNC - The Active Application Repository is replaced on the Passive Application Repository 1 - PARTIAL_SYNC - Only the new Applications in the Active Application Repository is updated on the Passive Application Repository 2 - NO_SYNC - No Synchronization will happen between the Active and Passive Repository. Assumes that there is no Application Edited/Removed/Added.
• ComponentSyncType - Sync Type for Component Repository 0 - FULL SYNC - The Active Component Repository is replaced on the Passive Component Repository 1 - PARTIAL_SYNC - Only the new Components in the Active Component Repository is updated on the Passive Component Repository 2 - NO_SYNC - No Synchronization will happen between the Active and Passive Repository. Assumes that there is no Component Edited/Removed/Added.The user can configure both Primary and Secondary FES from a single screen.

...

1. Open Primary and Secondary FES profiles. Select both of them, right-click and click the FES Replicated HA option.
   Image Removed
   Image Added
   Figure 6: FES Replicated HA option
    
2. The dialog box that gets opened contains properties for both FES HA Primary and FES HA Secondary.
    
   Image RemovedImage Added
   Figure 7: FES Replicated HA dialog box
    
3. Save the profile after making the changes required.

...

1. Open the HA profile (replicated).
2. Right-click the profile and click the FPS Replicated HA option.
   Image Removed
   Image Added
   Figure 8: FPS Replicated HA dialog box
    
3. Make the changes required in the FPS Replicated HA dialog gets displayed
4. Save the profile.

...

• BackupServerIp - Specifies the backup server ipIP. This IP is configured in backup-url for default connection factories.
• BackUpServerPort - Specifies the backup server port. This port is configured in backup-url for default connection factories.
  This can be changed by modifying the backup server profile.
  1. Open the Backup Server profile in the Fiorano Studio Profile Manager.
  2. Navigate to <ProfileName> > Fiorano > socketAcceptors > port-1 > ConnectionManager > Properties of ConnectionManager
  3. Change the Port parameter.

• BackupHAIPAddress - IP Address of backup peer server in HA.
• BackupHAPort - Port of the Backup Peer server on which peer is listening for status requests send by another server. This parameter is same as the 'Port' parameter but it specifies the port used by the backup server
• Port - This is the port on which the HA Manager is going to listen for connections from its backup server. Once the connection is established, it starts serving as the back channel for broadcasting the state of the servers to the backup server whenever there is a state transition.
• BackupRMIServerPort - Port used by the backup server to bind the Mx4J RMI Connector.
• RMIServerPort – Port used by the server to bind the Mx4j Rmi RMI Connector.
• LockFile - Full path of the file which will be used for determining the HA states. This file should be present in the third machine and always available to the HA servers with all permissions. This parameter is mandatory to run HA. [Also, See GatewayServerIPAddress parameter while configuring.]
• GatewayServerIPAddress - IP address of Gateway machine. This is used to detect network failures. It is recommended that the IP specified should be of belong to a machine that is always available on the network. It is mandatory to specify this parameter. This parameter should always be the IP Address of the machine hosting the LockFile.
• GatewayServerPort - In Replication HA mode, network failure is detected by using the gateway server machine. Specifies the port on which gateWay machine is listening for incoming requests
• ActiveLockReAcquistionInterval - This parameter indicates the wait Interval between each attempt to acquire the lock for active server. This value should be in multiples of pingInterval/2 otherwise, server may try to acquire the lock on the next multiple of pingInterval/2.
• PassiveLockAcquistionInterval - This parameter indicates the wait Interval for the passive server to acquire the lock when the link between active and passive server is down. This value should be greater than '2*ActiveLockReacquisitionInterval', otherwise, an exception will be thrown. Server won't The server will not start if this value is not set properly.
• PingInterval - Time interval (in ms) after which the remote server is pinged in Replication HA mode.
• PrimaryURL – The primary URL of MQ server [i.e the FES] from which configuration should be loaded
• BackupURL(s) – The backup URL(s) of MQ server [i.e the FES] from which configuration should be loaded.

...

The figure below illustrates a successfully started Fiorano HA Peer Server.

Image RemovedImage Added
Figure 9: Fiorano HA Peer Server console

...