Creating a Shared Resource to Publish BPM Audit Data (Non-SSL)

You can create shared resources on TIBCO Administrator and use them to publish BPM audit data to a secure destination.

This is achieved by
  • creating shared resource templates on TIBCO Administrator for the following:
    • JNDI connection configuration
    • JMS connection factory
    • JMS destinations

  • On TIBCO Enterprise Message Service (EMS):

    • The required topics and queues must be created.
    • The JNDI Names for the connection factories, queues and topics must be created.

Procedure

  1. Add the new destination to ECPublicationJMS.properties file. For example, 
    connectionFactory=publication/SSLTopicConnectionFactory

jmsDestinationResourceNames=publication/ECSSLTopicJNDI;publication/ECSSLQueueJNDI
    See Publishing BPM Audit Data Using an Administrator Shared Resource for more information about this file.
  2. Create the queues, topics and JNDI names using tbemsadmin. For example, 
    connect tcp://localhost:7222
    1. Create a topic. For example, 
      create topic ECSSLTopic
create jndiname ECSSLTopicJNDI topic ECSSLTopic
    2. Create a queue. For example, 
      create queue ECSSLQueue
create jndiname ECSSLQueueJNDI queue ECSSLQueue
  3. Add a resource template of type JNDI Connection Configuration. The resource template name must be prefixed with ec/publication, for example ec/publication/<custom name>.
    The JNDI Provider URL should be the URL of the TIBCO EMS server .
  4. Add a resource template of type JMS Connection Factory. The resource template name must be prefixed with ec/publication, for example ec/publication/<custom name>.
    • The connection factory in the ECPublicationJMS.properties file should point to the name of the shared resource without the ec/ prefix. In this example, publication/sslConnectionFactory.
    • The JNDI connection configuration should point to the one you created in Step 3
  5. Add a resource template of type JMS Destination . The resource template name must be prefixed with ec/publication, for example ec/publication/<custom name>.
    • The destination JNDI Name must match the JNDI name for the destination in Step 2.
    • The JNDI connection configuration should point to the one created in Step 3.
  6. Add a resource template of type JMS Destination . The resource template name must be prefixed with ec/publication, for example ec/publication/<custom name>.
    • The destination JNDI Name must match the JNDI name for the destination inStep 2.
    • The JNDI connection configuration should point to the one you created in Step 3.
  7. Enable event publication in the ECPublicationJMS.properties file. For example, 
    PublicationEnabled=true
  8. Configure theec-event-rules.xml file. For example,
    Each target can have a qualifier.The qualifiers must match the names of the shared resources for the JMS Destinations (without the "ec/" prefix). in this example, as created in Step 2. If you exclude the qualifier, the rules you configure will apply to all destinations.