IEP Service Engine-Specific Database Tables

When you start the IEP Service Engine for the first time, the following tables are created in the IEP database. These tables apply to the IEP Service Engine as a whole.

Do not delete or alter these tables.

EMS_PLAN Table

The EMS_PLAN table maintains information about the event processes that are deployed to the IEP Service Engine. The EMS_PLAN table contains the following columns:

• ID. An integer that uniquely identifies the event process.

• INSTANCE_ID. A value that represents the event process.

• NAME. The name of the event process.

• CONTENT. The XML content of the event process. The value is displayed in binary format.

• LAST_ACTIVATION. The last time the event process was started.

• STATUS. The status of the event process definition. The valid values are started, stopped, deployed, and undeployed.

• ENGINE_ID. The ID of the cluster node that is running the event process. If you are not running IEP in cluster mode, then the value is stand-alone.

EMS_OUTPUT Table

The EMS_OUTPUT table maintains information for event processes that have a Table Output operator. The EMS_OUTPUT table contains the following columns:

• PLAN_INSTANCE_ID. The instance ID of the event process that has the Table Output operator.

• OUTPUT_NAME. The name of the table.

• OUTPUT_DESCRIPTION. The description of the table.

• LAST_UPDATED. The last time the output table was updated.

EMS_ENGINE Table

The EMS_ENGINE table is used when you are running IEP in cluster mode. The EMS_ENGINE table contains the following columns:

• ID. A value that uniquely identifies the IEP instance (instance1, instance2, and so on). If you are not running IEP in cluster mode, then the value is stand-alone.

• INSTANCE_LOCATION. The IP address of the computer where the IEP instance is running.

• LEASE_EXPIRATION. A timestamp that the cluster nodes use to determine which IEP instance is active.

EMS_TOKEN Table

The EMS_TOKEN table is used when you are running IEP in cluster mode. The EMS_TOKEN table contains the following columns:

• ID. The unique identifier of a token that can be acquired and released by cluster nodes.

• NAME. The name of a token that can be acquired and released by cluster nodes.