Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Currently, there are three ORCH tables in DBthe database:

Table of Contents

ORCH_REQUEST_DEF

PACE_MASTERDBO.ORCH_REQUEST_DEF table contains definitions of orchestration requests. It has a parent table EGLtable EGL_SCHED_DEF. Due to the fact that Orchestration is a data driven process, any time a request for Orchestration arrives, it has to be treated as a request to create a schedule in terms of Process Center framework.

Column Name

Column Type

NULL

Nullable

Comments

INSTANCE

NUMBER(38,0)

NOT NULL

N

A sequence number for orchestration request

SCHED_DEF_INSTANCE

NUMBER(38,0)

NOT NULL

N

Reference to

a EGL

a EGL_SCHED_DEF table instance field

CORRELATION_ID

VARCHAR2(255)

NOT NULL

N

Unique correlation identifier

BUS_TASK_ID

VARCHAR2(255)

NOT NULL

N

Unique business identifier, user readable

PROC_SEQ_NUMBER

NUMBER(38,0)

NULL


Processing Sequence Number

SEQ_NUMBER

NUMBER(38,0)

NULL


Sequence identifier

TOT_COUNT

NUMBER(38,0)

NULL


Total Count

SENT_BY

VARCHAR2(255)

NULL


Send By

REPLY_TO

VARCHAR2(255)

NULL


Reply To

PROC_STATUS

VARCHAR2(10)

NOT NULL

N

One of SUCCESS, FAILURE, NO_DATA

CF_NAME

VARCHAR2(1000)

NULL


Name of the unique temporary control file

UPDATE_DATE

DATE

NOT NULL

N

Date last updated

UPDATE_SOURCE

VARCHAR2(255)

NOT NULL

N

User ID who updated the record

ORIG_CORRELATION_ID

VARCHAR2(255)

NULL


Original correlation identifier

Primary key: INSTANCE
Unique index: CORRELATION_ID
Non-unique index: ORIG_CORRELATION_ID

ORCH_REQUEST_PARAMS

The PACE_MASTERDBO.ORCH_REQUEST_PARAMS contains a list of parameters for each orchestration request. Once again, the fact that it is a data driven architecture makes the list of parameters impossible to be predefined. So, most important and common parameters are captured in the ORCHthe ORCH_REQUEST_DEF table and all other parameter parameters are be stored in a one-to-many relationship child table as key-value pairs.

NULLNOT NULLNOT NULL the NOT NULLNULLNULLNOT NULLNOT NULL
Column NameColumn TypeNullableComments
INSTANCENUMBER(38,0)NSequence number for the orchestration parameter record
ORCH_INSTANCENUMBER(38,0)NSequence number for the orchestration request. Identifies the request in ORCH_REQUEST_DEF table.
PARAMETER_NAMEVARCHAR2(255)NParameter name.
PARAMETER_VALUEVARCHAR2(4000)
Parameter value.
PARAMETER_BLOB_VALUEBLOB
Parameter value in case of a blob.
UPDATE_DATEDATENDate last updated
UPDATE_SOURCEVARCHAR2(255)NUser ID who updated the record

Primary key: INSTANCE
Unique index: ORCH_INSTANCE, PARAMETER_NAME

ORCH_QUEUE

The PACE_MASTERDBO.ORCH_QUEUE table contain the contains a list of orchestration requests. It has its Its parent table EGLis EGL_SCHED_QUEUE.

Column Name

Column Type

NULL

Nullable

Comments

INSTANCE

NUMBER(38,0)

NOT NULL

N

Sequence number for orchestration request

SCHED_QUEUE_INSTANCE

NUMBER(38,0)

NOT NULL

N

Reference to

a EGL

a EGL_SCHED_QUEUE table instance field

ORCH_REQ_DEF_INSTANCE

NUMBER(38,0)

NOT NULL

N

Reference to

a ORCH

a ORCH_REQUEST_DEF table instance field

ORCH_STATE

BLOB

NULL


State of orchestration workflow

STATUS

NUMBER(38,0)

NULL


Current detailed status of workflow

CREATE_DATE

DATE

NOT NULL

N

Date created

UPDATE_SOURCE

VARCHAR2(255)

NOT NULL

N

User ID who updated the record

UPDATE_DATE

DATE

NOT NULL

N

Date last updated

ORCH_STATE_CLOB

CLOB

NULL


State of orchestration workflow in case of a clob

CORRELATION_ID

VARCHAR2(255)

NULL


Unique correlation identifier

PROCESS_CORRELATION_ID

VARCHAR2(255)

NULL


Process correlation identifier

ORIG_CORRELATION_ID

VARCHAR2(255)

NULL


Original correlation identifier

Primary key: INSTANCE
Unique index: SCHED_QUEUE_INSTANCE
Unique index: ORCH_REQ_DEF_INSTANCE
Non-unique index: CORRELATION_ID
Non-unique index: PROCESS_CORRELATION_ID
Non-unique index: ORIG_CORRELATION_ID---


Joins between ORCH tables: