Page Comparison

Figure 1: Clustering Architecture
 

Anchor
_Ref392234873 _Ref392234873

Components

Clustering provides high-availability, scalability, and manageability of the resources and applications by grouping multiple servers that are running Adeptia Suite. There are a number of components, which make that possible. Important components of clustering service include the following: 

...

• • Adeptia Suite does not provide Clustering or Failover setup for the databases, however, you can set that up according to the database you use. For load sharing purposes, it is recommended to configure master/slave or replication (refer to the related database documentation).

Log Database:

Adeptia Suite maintains logs of all the design time and run time activities that you run within Adeptia Suite. For example Process flow log, event log, etc. Adeptia Suite writes all these logs into the log database. All the nodes of the cluster should use same log database. In addition, for load sharing purposes, it is recommended to configure master/slave or replication (refer to the related database documentation).

Anchor
SharedL SharedL

Shared Location

...

To enable cluster, it is important that you Adeptia Suite stores intermediate data to enable fail over capabilities and scalability. This data is used throughout the process flow execution. It is important that the intermediate data can be accessed by all the nodes of a cluster. So, before enabling a cluster, you must set up a shared location that has both Read and Write permissions, and that can be accessed accessed by all the nodes of a cluster. Depending on your operating system and needs, you may use any of the File File Sharing services. Some of the popular options are as follows:

...

It will allow you to use Windows and Unix machines to access the remote folder. It's easy to automount it on init (just input the apropriate values at /etc/fstab, including username=<your-samba-username>,password=<your-samba-password> in the options column.
 

include NFS, Samba / CIFS, and SSHFS.

The intermediate data is stored in the following folders:

Repository Folder

When the process flow is executed, data from the source is converted to the intermediate form and then it is dispatched to the target. The intermediate data is stored in a repository folder. This should be a shared folder in the network, which can be accessed by all the nodes of the cluster. There should not be any username/password required to connect to this folder.

...

The process flows may also be aborted due to any other reason e.g., incorrect data mapping or schema definition. While execution, at every checkpoint, the Process Flow stores its current state in a rerun file. With the help of these files you can rerun the process flow. These files are stored in a rerun folder, this folder should also be shared among all the nodes of the cluster.