Detailed DB Schema for BW

现在的位置: 首页 > 综合 > 正文

Detailed DB Schema for BW

2013年10月06日 ⁄ 综合 ⁄ 共 15370字 ⁄ 字号小中大 ⁄ 评论关闭

Detailed DB Schema for BW (BPO, Transaction, and etc.)

The Integration
Server provides a persistence service, which is used to store states and
objects in a relational database.

BusinessWare server (bserv) and channel server (chanserv) do not use
database persistence.

The following
objects are persisted:

1. Application
state

a. BPOs
used in stateful process models

b. Data
Objects (DO) used either in stateful or stateless process models

c.
Timers in stateful process models

d.
Tasks and activities in BusinessWare Task Manager projects

2. Connector state

a.
Source and target connector states

a.
Channel position is stored here when a source connectors are is used

3. Integration
Server internal state

a.
In-doubt transactions

b. Next
available service-id for remote objects created by the Java Transaction Service
(JTS) subsystem in the transaction manager

c.
Target connector transactional state

Objects in
categories (1c), (1d), (2), and (3) are considered internal to BusinessWare and
database tables for those objects should be modified only with extreme care. In
addition, BusinessWare-specific, that is, non-customer specific, fields of BPOs
are also considered internal and should also be modified with extreme care.

DB schema for BPO,
DO is automatically generated by the BusinessWare persistence service.
Table names for BPOs and DOs are provided by
the modeler during design time as part of the Object Table associated with a
stateful process model.

The table names
for BusinessWare internal tables are fixed.

The O-R mapping
tool keeps track of the Java implementation classes and table names in the
following meta-tables:

vitria$table
—keeps track of the Java implementation class and the table name. There is an
entry for every table used by BusinessWare.

Name	Data Type	Size	Nulls
id (key)	int, NUMBER(11)	4
impclass	varchar	255
mappedtablename	varchar	255
tablename	varchar	255

vitria$column
—describes the logical schema for the table. There is an entry for every
<table, column> pair.

Name	Data Type	Size	Nulls
tname (key)	varchar	255
cname (key)	varchar	255
cnum	int	4

vitria$tableid
—used to store the next unique ID. This table has only one row. This is for
non-Oracle databases only.
In case of
Oracle, the sequence vitria$tableid_seq is created.

Name	Data Type	Size	Nulls
OID	numeric	9(19.0)	x

The O-R mapping
tool keeps track of the Java implementation classes and table names in the
following meta-tables:

vtconnectorstate -
com.vitria.connectors.framework.common.ConnectorState

·

Insert and updates on
vtconnectorstate table happens all the time.

·

Max Number of rows here are =
number of source connectors + number of instances created

·

Delete is never called on this
table

·

No choice of persistence for
individual connectors I.e. once Integration server is persisted to Db all
connectors by default get DB persistence and every one gets a uniuqe id
assigned

Name	Data Type	Size	Nulls
connectorid (key)	varchar	100
instanceid (key)	varchar	100
jndiname	varchar	8000	x
state	image (BLOB)	16	x
xid	varchar	255	x
txmarker	int	4	x

vitria1 (vtTransactionState) -
com.vitria.services.jta.log.TransactionLogRecordImpl.

·

This table stores the in-doubt
transactions at the beginning of each transaction and removes it after
successful commit.

·

Delete and Inserts are always
called at end and beginning of a new transaction on Transaction state table
(vitria1)

Name	Data Type	Size	Nulls
appid (key)	varchar	100
xid (key)	varchar	100
xidformat (key)	int (NUMBER(11))	4
rsids	image (BLOB)	16	x
outcome	int	4	x
coordservid	int	4	x
coordaddr	varchar	255	x
recoverycoordior	text (CLOB)	16	x

vitria2 (vtJTSServideId) -
com.vitria.services.jts.ServiceId.
For
interoperability with other JTS compliant applications, the transaction manager
uses this table for obtaining the next unique service id for exporting Object
Transaction Service (OTS) coordinator and recovery objects. The table has only
one row.

Name	Data Type	Size	Nulls
appid (key)	varchar	100
lastusedservid	int	4	x

PROCESSTIMER -
com.vitria.container.timer.TimerInstance

Name

Data Type

Size

Nulls

vtoid (key)

varchar

100

objectiId

varchar

255

state

varchar

255

model

varchar

255

projectName

varchar

255

duration

numeric

9(19.0)

created

numeric

9(19.0)

expiration

numeric

【上篇】POJ 2901 Hotel
【下篇】sql SQL分割字符串

作者: pubes

该日志由 pubes 于11年前发表在综合分类下，最后更新于 2013年10月06日.
转载请注明: Detailed DB Schema for BW | 学步园 +复制链接

抱歉!评论已关闭.

返回首页

（其他合作也可洽谈）

必威体育

必威电竞

学步园