Components are the most important elements of the application that provide the functional behaviour of application. They have no physical presence and are stored in digital form within the application. There are two main components of Adeptia Suite - Kernel and WebRunner that helps in running Adeptia Suite by grouping multiple servers, hence providing high-availability and scalability of the resources. This short section introduces Adeptia Suite components.
...
Kernel in Clustering mode (for information on Clustering, refer to Clustering Deployment Guide)
When you enable clustering, the execution of process flow is distributed among Kernels of each instance of Adeptia Suite server. All the requests first go to the Primary Node, which in turn, distributes the jobs among all other kernels. It is the Primary Node, which manages Scheduling of Events and Queue Processing. If any node goes down, the Primary Node identifies the process flow (running on that node), recovers them, and again distributes the execution among the available nodes.
...
- Adeptia Suite does not provide Clustering or Fail-over setup for the databases, however, you can set 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 maintain logs of the design time and run time activities that you run within Adeptia Suite. For example, Process flow log, event log, and more. Adeptia Suite writes all these logs to the log database.
Log database in Clustering mode
...
Adeptia Suite stores intermediate data to be used throughout the process flow execution. This 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 can be accessed by all the nodes of a cluster. Depending on your operating system, you may use any of the File Sharing services. Some of the popular options include NFS, Samba / CIFS, and SSHFS.
...
The process flows may be aborted due to various reasons (for example, 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 and should be shared among all the nodes of the cluster.
Others
When applicable, the following additional folders must also be shared amongst all the nodes of the cluster.
| Folder Containing | Property |
|---|---|
| Web Services Data | abpm.webservice.wsdlDeployPath |
| Attachments | abpm.webservice.metro.soapattachment.location |
| File Reference | abpm.filereferences.basefolder.location |
| EDI Data | abpm.solution.edi.dataFile.location |
| Non-EDI | abpm.solution.nonedi.dataFile.location |
| EDI Archive | abpm.solution.edi.repository.archive.path |
| Security(KeyStore and KeyManager) | abpm.security.repository |
| Jasper Report | abpm.reporting.repository |
| FTP Logs | abpm.ftpDebugOut.file.location |
| SAP | abpm.sap.idoc.repository |
| Process Flow Archive Repository | abpm.transaction.repository.archive.path |
...