Detailed DB Schema for BW

最新推荐文章于 2026-04-08 05:00:43 发布

原创最新推荐文章于 2026-04-08 05:00:43 发布 · 759 阅读

0 ·

本内容遵循CC 4.0 BY-SA版权协议

标签

#schema #transactions #list #table #permissions

BusinessWare 专栏收录该内容

9 篇文章

订阅专栏

本文介绍BusinessWare集成服务器的数据库方案，包括应用状态、连接器状态及内部状态等对象的持久化方式，并提供数据库表结构和权限配置指导。

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	x
state	varchar	255	x
model	varchar	255	x
projectName	varchar	255	x
duration	numeric	9(19.0)	x
created	numeric	9(19.0)	x
expiration	numeric	9(19.0)	x
componentName	varchar	255	x
componentType	varchar	255	x

Role Definition for each Database (BW, Operation Management)

If Oracle is used for Integration Server persistence, the Oracle 9 user specified in the database resource must have either DBA privilege or the set of permissions shown below to work with XA.

Execute the query “select * from SYS.DBA_PENDING_TRANSACTIONS;” and if this works then XA is configured properly. If XA is not setup, you need to ask you DBA to run the scripts to enable setup XA on your systems.

TABLE_NAME PRIVILEGE

---------------------------------------

DBA_2PC_PENDING SELECT

DBA_PENDING_TRANSACTIONS DELETE

DBA_PENDING_TRANSACTIONS INSERT

DBA_PENDING_TRANSACTIONS SELECT

DBA_PENDING_TRANSACTIONS UPDATE

DBA_PENDING_TRANSACTIONS REFERENCES

DBA_PENDING_TRANSACTIONS ON COMMIT REFRESH

DBA_PENDING_TRANSACTIONS QUERY REWRITE

DBA_PENDING_TRANSACTIONS DEBUG

DBA_PENDING_TRANSACTIONS FLASHBACK

JAVA_XA EXECUTE

V$PENDING_XATRANS$ SELECT

V$XATRANS$ DELETE

V$XATRANS$ INSERT

V$XATRANS$ UPDATE

V$XATRANS$ REFERENCES

V$XATRANS$ ON COMMIT REFRESH

V$XATRANS$ QUERY REWRITE

V$XATRANS$ DEBUG

V$XATRANS$ FLASHBACK

V$XATRANS$ SELECT

The following system privileges are also needed for this database user:

· CREATE TABLE

· CREATE SESSION

· CREATE SEQUENCE

· FORCE TRANSACTION

Oracle requires the following minimum patch sets to support XA properly:

· Oracle 8.1.7.4

· Oracle 9.1.0.5

· Oracle 9.2.0.5

· Oracle 10.1 (requires using the 9.2.x driver due to an Oracle bug in the 10g driver as of BW 4.3).

The JDBC driver should be ojdbc14.jar (preferably 9.2.0.5) because that is the only driver supported with JDK 1.4.x.

To grant the SELECT privilege on the system view "DBA_PENDING_TRANSACTIONS", you must logon to Oracle as "SYS" user using

Oracle's tool likes SQL*Plus and issue the following command (Note: the default password for "SYS" user is "CHANGE_ON_INSTALL")

sqlplus sys/change_on_install

SQL GRANT SELECT ON dba_pending_transactions to myuserid

The permissions on the DBA_PENDENING_TRANSACTION is needed for transaction recovery. So if you don’t have permission on this table, your integration server will still start but will fail to recover any in-doubt transactions.