Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Adeptia connect 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 intermediate data is stored in the following folders:

Repository Folder

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

Recovery Folder

During execution of a process flow, its current state is stored in a recovery file. This recovery file is stored in a recovery folder. Whenever a process flow aborts due to Kernel shutdown, the Recovery feature handles it automatically with the help of the recovery files. These files, remains in the recovery folder unless the process flow execution is completed. This folder should be shared among all the nodes of the cluster.

Rerun Folder

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 Dataabpm.webservice.wsdlDeployPath
Attachmentsabpm.webservice.metro.soapattachment.location
File Reference abpm.filereferences.basefolder.location
EDI Dataabpm.solution.edi.dataFile.location
Non-EDIabpm.solution.nonedi.dataFile.location
EDI Archiveabpm.solution.edi.repository.archive.path
Security (KeyStore and KeyManager)abpm.security.repository
Jasper Reportabpm.reporting.repository
FTP Logsabpm.ftpDebugOut.file.location
SAPabpm.sap.idoc.repository
Process Flow Archive Repositoryabpm.transaction.repository.archive.path
  • No labels