Job business objects
The DataConnect Job Control (DC_JOB) table manages the jobs that move data from staging tables into the IBM® TRIRIGA® database. A business object must exist in the triDataConnectJob module for each integration process. Creating the business object in the triDataConnectJob module is a one-time task for the integration process.
You need a DataConnect Job Control business object for each integration process. For example, if you are populating purchase orders from an external source, you might have a cstPurchaseOrderJob business object as your DataConnect Job Control business object. Then, the process might pull in data for the cstPurchaseOrderBody and cstPurchaseOrderLine business objects (both with the Has Staging Table property on).
- Open the triDataConnectJob module through the Data Modeler.
- Create the business object in the triDataConnectJob module.
After you create the new business object, you can create a form and menu navigation for the business object. DataConnect is delivered with a base form and a base menu for the base triDataConnectJob business object.
- Null -> triDCStartProcessing -> In-Process
- In-Process -> triDCCompleted -> Completed
- In-Process -> triDCFailed -> Failed
All fields in the first section are read-only. The second section contains log records for that DataConnect job. The log records are triDataConnectLog records in triLog. Click a line item to see the details for that event. By default the second section shows issues that are found during the DataConnect run. However, when you select DataConnect Runtime in the Platform Logging managed object in the IBM TRIRIGA Administrator Console, the second section also shows positive information about records that were inserted or updated.
Logging levels for the various agents is determined by the platform log settings and the log4j settings on the server where the agent is running. DataConnect uses two agents. One is the DataConnect Agent, which creates the job object and provides it to the Workflow Agent asynchronously through an event. Its job is over when the job object is created and the event is posted. The second agent, the Workflow Agent, runs the business logic (the workflows) and then the DataConnect tasks that create and update objects in the IBM TRIRIGA database. If you want to see reporting on your job objects even when there are no issues, you must set the DataConnect Runtime logging on the server of the Workflow Agent. Setting it on the server of the DataConnect Agent has no effect since the Workflow Agent is running the workflow and creating or updating the objects from the staging tables.