Open topic with navigation

TIBCO® BPM Enterprise 5.5.0

# Event Publication Configuration

Event Publication table (ep_event) is a database table to which events are published, when the events are properly configured with a set of properties. A broker can then be produced as a microservice that reads and deletes events from this event publication table and publishes them, as required.

## Schema

The schema for ep_event is:

    CREATE SEQUENCE ep_event_seq START WITH 1 INCREMENT BY 1;

    CREATE TABLE ep_event
    (
     id             numeric(28)	             DEFAULT nextval('ep_event_seq'),
     format_version integer                     DEFAULT 1,
     creation_time  timestamp without time zone DEFAULT current_timestamp,
     details        text                        NULL,
     CONSTRAINT pk_ep_event PRIMARY KEY (id)
    )WITH (OIDS=FALSE);

The actual event data is provided in the details field as JSON. Check the following sample entry in the details column.

    {
      "hostName": "bpm-ace",
      "messageCategory": "PROCESS_INSTANCE",
      "componentId": "BX",
      "creationTime": "2021-04-08T04:15:57.199+0000",
      "componentClassName": "com.tibco.bx.n2.ec.BxAuditTrail",
      "procId": 302,
      "moduleName": "SampleBPMProject",
      "methodId": "processInstanceStateChange",
      "managedObjectVersion": "1.0.0.20200521145425675",
      "principalId": "tibco-admin",
      "simpleClassName": "BxAuditTrail",
      "uuid": "1cb15214_716e_4d0f_a602_cb999d390436",
      "threadId": 268,
      "parentContextId": "d9e8039e_4e92_4f13_bb6b_6b18bd650416",
      "parentObjectId": "p:0a218e",
      "managedObjectName": "SampleBPMProjectProcess",
      "rootProcessInstanceId": "",
      "correlationId": "ca20227d_8919_40dc_a727_9a4fb4708213",
      "applicationName": "ContainerEngineApp",
      "severity": "AUDIT",
      "processInstanceId": "409",
      "procInstanceId": 409,
      "methodName": "processInstanceStateChange",
      "messageId": "BX_INSTANCE_PROCESS_STARTED",
      "contextId": "549e08f5_94f6_4c3c_9a9d_1649b01043a8",
      "eventType": "MESSAGE",
      "message": "Process Instance started.",
      "processPriority": "NORMAL",
      "threadName": "ce_4",
      "managedObjectId": "p:0a20bd",
      "hostAddress": "172.18.0.4"
    }

## Configure Profile Property

Configure the publishRulesConfig.profiles property on the logging component to control what event should be published. It needs to be set with a comma-separated list that consists of one or more of the following values:

Property | Default | Description
--- | --- | ---
publishRulesConfig.profiles | None | A list of possible values for the property include: PROCESS_INSTANCE, PROCESS_INSTANCE_TASKS, PROCESS_INSTANCE_EXCEPTIONS, CASE, WORK_ITEM, SYSTEM_LOGIN, SYSTEM_OTHER, STATS, DEPLOYMENT, SYSTEM_CONFIG Note: You can have more than one property value for event publication. In case of more than one property value, make sure that the values are separated by a comma.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO® BPM Enterprise

Copyright © 2015-2024. Cloud Software Group, Inc. All Rights Reserved.