BES Implementation

From VCGR Wiki

Execution Engine

In the new BES Implementation, bes's will be configured with an execution engine. This will be a class with a well known interface that will be instantiated once in the server configuration file, and reference by name from the BES service configuration in the same file. This way, we can easily configure the number of running BES activities at any given time.

Database Design

The following shows the schemas of the proposed BES tables. Notice that the distinction between BES and BES activity is no longer clear cut. This is intentional. As far as the execution engine and the BES goes, there is no reason to seperate the two. They are seperate port types for convenience, but both reference the same conglomerate state behind the scenes.

besactivitiestable

column name	column type
activityid	VARCHAR(256)
besid	VARCHAR(256)
jsdl	BLOB(256K)
owners	BLOB(128K)
callingcontext	BLOB(128K)
state	BLOB(256K)
submittime	TIMESTAMP
suspendrequested	SMALLINT
terminaterequested	SMALLINT
activitycwd	VARCHAR(256)
executionplan	BLOB(256K)
nextphase	INTEGER
activityepr	BLOB(128K)
activityservicename	VARCHAR(128)
jobname	VARCHAR(256)

besactivityfaultstable

column name	column type
faultid	BIG INTEGER
besactivityid	VARCHAR(256)
fault	BLOB(32K)

bespolicytable

column name	column type
besid	VARCHAR(256)
userloggedinaction	VARCHAR(64)
screensaverinactiveaction	VARCHAR(64)