Page History

Configuring Document Tracking

It is recommended to use an external database for document tracking, which can be configured by providing the database configuration details in sbwdb.cfg file located in the Enterprise Server profile. To configure document tracking in this manner, perform the following actions:

1. Configure sbwdb.cfgfile in the FES profile located at FIORANO_HOME/esb/server/profiles/<PROFILE NAME>/FES/conf by enabling all the properties related to the respective database and disabling the default settings.
   
   

   Tip

   For example, to use an Oracle database, uncomment the following line: Code Block #JDBC_DRIVER=oracle.jdbc.driver.OracleDriver comment out the default one below: Code Block JDBC_DRIVER=org.h2.Driver Image Added Figure 1: sbwdb.cfg file data after commenting and commenting out properties for Oracle DB Follow the same process for all the properties where Oracle-specific details are enabled and disable the defaults. Note For an HA profile, configure these settings in the secondary profile too. To store the message as XML, set the REPRESENTABLE_DATA_TYPES property (property #12) to 'true'. Retaining the value as 'false' allows to store the message as a blob. Image Added Figure 2:  sbwdb.cfg file data with REPRESENTABLE_DATA_TYPES set to 'true'

   
   
   

2. Add the driver in FES server classpath in the FIORANO_HOME/esb/server/bin/server.conf under <java.classpath> section. 

   Tip
   Place the file in the FES machine to use the path here. Both absolute and relative paths will work.

   
   
   

3. Restart the server.

   Note
   Check the server logs to ensure that there are no error messages during the startup.

Creating SBW Tables Manually

If the server does not have enough permissions to create the sbw tables, then tables can be manually created using the following SQL queries:

create table TES_SBW_SCHEMA_VERSION (VERSION integer)
create table TIFOSI_DB_HEALTH (HEALTH varchar(800))

If REPRESENTABLE_DATA_TYPES is set to 'false', then use the following query to create WF_INST_EVENT_HISTORY table:

create table WF_INST_EVENT_HISTORY (EVENT_ID integer, WORKFLOW_INSTANCE_ID varchar(800), WORKFLOW_ID varchar(800), USER_DEFINED_DOC_ID varchar(800), SERVICE_INST_ID varchar(800), STATE_ID varchar(800), STATE_COMMENT varchar(800), STATE_EVENT_DATE varchar(800), DOCUMENT_ID varchar(800), WORKFLOW_STATUS varchar(800), IN_TIME DATE, OUT_TIME DATE, TOTAL_TIME varchar(800), WF_VERSION varchar(800), DOCUMENT BLOB, HAS_BEEN_RESET varchar(4))

If REPRESENTABLE_DATA_TYPES is set to 'true', then use the following query to create WF_INST_EVENT_HISTORY table:

create table WF_INST_EVENT_HISTORY (EVENT_ID integer, WORKFLOW_INSTANCE_ID varchar(800), WORKFLOW_ID varchar(800), USER_DEFINED_DOC_ID varchar(800), SERVICE_INST_ID varchar(800), STATE_ID varchar(800), STATE_COMMENT varchar(800), STATE_EVENT_DATE varchar(800), DOCUMENT_ID varchar(800), WORKFLOW_STATUS varchar(800), IN_TIME DATE, OUT_TIME DATE, TOTAL_TIME varchar(800), WF_VERSION varchar(800), HAS_BEEN_RESET varchar(4))
ALTER TABLE WF_INST_EVENT_HISTORY ADD MESSAGE XMLTYPE XMLTYPE MESSAGE STORE AS CLOB
ALTER TABLE WF_INST_EVENT_HISTORY ADD MESSAGE_HEADERS XMLTYPE XMLTYPE MESSAGE_HEADERS STORE AS CLOB
ALTER TABLE WF_INST_EVENT_HISTORY ADD MESSAGE_ATTACHMENTS XMLTYPE XMLTYPE MESSAGE_ATTACHMENTS STORE AS CLOB
ALTER TABLE WF_INST_EVENT_HISTORY ADD MESSAGE_CFWD_PROPERTIES XMLTYPE XMLTYPE MESSAGE_CFWD_PROPERTIES STORE AS CLOB
ALTER TABLE WF_INST_EVENT_HISTORY ADD MESSAGE_CFWD_SRC_CONTEXT XMLTYPE XMLTYPE MESSAGE_CFWD_SRC_CONTEXT STORE AS CLOB

Document Tracking in Event Processes

Once the server is setup as explained in the above section, follow the below instructions to configure tracking in Event Processes.

Document Tracking in Workflow

A workflow in Fiorano terminology consists of an entry point, an end point and intermediary points between them.

The entry and intermediary points are defined as Workflow Items and the end point is defined as a Workflow End. To track the documents going through the Service Instances, document tracking can be enabled on service instance ports. If tracking is enabled, the documents that pass through that port are stored in a database. By default these documents are stored in the H2 database that runs inside the Enterprise Server. It is recommended to use an external database for document tracking, which can be configured by providing the database configuration details in sbwdb.cfg file located in the Enterprise Server profile. 

A workflow starts with Workflow Item and ends at Workflow End. A workflow is defined within an Event Process scope through which a large number of documents pass. Whenever a new document enters into the workflow, a new workflow instance is generated. Each workflow instance has a unique ID assigned by the Fiorano Platform environment. In a state enabled workflow, all the states that these workflow instances traverse are stored for tracking purposes.

...

1. Select the Service Instance Port on which document tracking has to be enabled; the Properties pane appears (if the Properties pane does not appear, navigate through Window > Show View > Others).
2. To enable Document Tracking, select Workflow Item/Workflow End option in the Workflow property drop-down list.
   
   
   Figure 13: Enabling Document Tracking
    

3. In the sample Event Process shown below, the workflow starts at Feeder output port. The SMTP output port is marked as an intermediary point and the workflow ends at Display input port.
   
   
   Figure 24: Event Process with Document Tracking enabled

   Tip
   The ports of Workflow Items are filled with the color green and that of Workflow Ends are shown in the color red.

In the Event Process, the state tracking is enabled for Feeder1 output port, SMTP1 output port and Display1 input port. All the messages which pass through these are tracked.

Workflow Data Type

The default Workflow data type (Properties > General > Workflow Data Type) is set to 'Message Body'. This implies that only the JMS message body is tracked. This can be configured by clicking the button against the Workflow Data Type property to track Message Header, Message Body, Attachments, Application Context or all of these items.

Figure 35: Document Tracking Properties

...

Re-injecting

...

failed document

In a workflow, in case a document fails, it can be re-injected from the Document Tracking tab in the Dashboard.

Deleting Document Tracking

...

data 

To avoid issues like Low Disk Space error, you may require to free some disk space by discarding old entries in the Document Tracking Database.

...