ProcessDataFileWriter

The ProcessDataFileWriter handler always works in combination with ProcessDataExtractor, which extracts the entire process instance or event data. All data of a single process instance including worksteps, workitems and application data is written within a single XML tag. This may be useful for transformation to HTML format and viewing it from a browser. But it may not be useful for data warehouse applications. ETL tools require data of a single database table to be stored together for easy data loading. All the data of the qualified process instances or events are stored in ProcessData_<jobid>.xml file. The jobid is unique for each archiver run.

Sample Process XML generated by Data FileWriter

A snapshot of process XML structure is given below.
<list id="1">
<com.savvion.bm.archiver.models.ProcessInstance id="2">
<workSteps id="5">
    <com.savvion.bm.archiver.models.WorkStepInstance id="6">
        <name>Evaluate Resume</name>
            …
        <workItems id="9">
            <com.savvion.bm.archiver.models.WorkItem/>
        </workItems>
    </com.savvion.bm.archiver.models.WorkStepInstance>
</workSteps>
    <events id="21">
        <com.savvion.bm.archiver.models.Event id="22"/>
    </events>
    <processNotes id="36"/>
    <runtimeAlerts id="37"/>
</com.savvion.bm.archiver.models.ProcessInstance>
</list>

Sample Event XML generated by Data FileWriter

A snapshot of event XML structure is given below:

<list id="1">
    <com.savvion.bm.archiver.models.Event id="2">
        <id>1</id>
        <eventType>P_CREATED</eventType>
        <eventCreator>BP Server</eventCreator>
        <createdDate>1219992776519</createdDate>
        <instanceId>0</instanceId>
        <templateId>28</templateId>
        <workStepId>0</workStepId>
        <context class="hashtable" id="3">
         <entry>
            <string>PROCESSTEMPLATENAME</string>
            <string>Hiring</string>
        </entry>
        </context>
    </com.savvion.bm.archiver.models.Event>
</list>