Repository Trigger Properties in the sharedConfig.properties File - EnterWorks - EnterWorks Process Exchange (EPX) - Precisely EnterWorks - 10.5

EnterWorks Classic Administration Guide

Product type
Software
Portfolio
Verify
Product family
EnterWorks
Product
Precisely EnterWorks > EnterWorks
Precisely EnterWorks > EnterWorks Process Exchange (EPX)
Precisely EnterWorks
Version
10.5
Language
English
Product name
Precisely EnterWorks
Title
EnterWorks Classic Administration Guide
Topic type
Configuration
Administration
First publish date
2007

Anytime you modify sharedConfig.properties file, restart services and clear the data cache afterward.

A screenshot of a social media post Description automatically generated

The settings in the sharedConfig.properties file that affect Triggers are:

  • allow.external.event.handler: This enables or disables external event handling. If it is false, all the event handler settings will be ignored.

  • allow.external.event.links:

  • external.event.handlers: Lists the names of the defined events. To disable a particular event, remove it from this list. The names must match the handlerName specified in:

external.event.<handlerName>.<property>

  • Settings for individual Triggers:

    • external.event.<handlerName>.passInDBSessionInd: If this is set, the database session is passed to the trigger’s doWork() method as an argument. This session provides access to the EPIM database without having to open another connection.

    • external.event.<handlerName>.type: This is always set to 0 (zero).

    • external.event.<handlerName>.sync: This is the event synchronous/asynchronous indicator:

      • If it is set to true, the event is a synchronous event, which means that if a user saves a record in the UI, the UI will not refresh until after the trigger has completed processing. Any changes the trigger made to the record being edited will be shown in the editor (if the editor is kept open).

      • Otherwise, it is an asynchronous event, which means that if a user saves a record in the UI, the UI will refresh immediately, potentially before the trigger has completed processing. If the trigger changes the record being edited, those changes will not be reflected in the editor (if the editor is kept open).

    • external.event.<handlerName>.classname: The java class name. The class must be accessible from the EnableServer Tomcat or EnableServer JBoss services.

      • To be accessible for the EnableServer Tomcat service, the class must be a JAR file and be placed in the folder:

<drive>:\Enterworks\EnableServer\tomcat\webapps\webcm\WEB-INF\lib

  • To be accessible for EnableServer JBoss service, the class must be injected into the epimServer.ear file. Execute the following for each EnableServer JBoss service:

<install_drive>:\Enterworks\bin\DeployServicesJar.bat

  • external.event.<handlerName>.target.repository: The name of the repository the trigger is registered to.

Any time you modify sharedConfig.properties file, restart services afterward.