System Event Publisher Service

   Journey Manager (JM) The transaction engine for the platform. |   System Manager / DevOps |  18.11 This feature was updated in 18.11.

Manager allows you to create and configure a System Event Publisher as a service to publish events to various queues, such as AmazonAmazon Web Services (AWS) is a comprehensive, evolving cloud computing platform provided by Amazon. It provides a mix of infrastructure as a service (IaaS), platform as a service (PaaS) and packaged software as a service (SaaS) offerings. or AzureMicrosoft Azure is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.. Different System Event Publishers have the same configuration with the exception to a service connection.

Manager comes with the following ready-to-use System Event Publishers:

• AWS SQS System Event Publisher service
• Azure System Event Publisher service

To create a System Event Publisher service:

1. Select Services > Core Global Services.
2. Click New.

   

3. Select the System Event Publisher service type from the Service Type dropdown list.
4. Select a System Event Publisher template from the Service Template dropdown list to automatically prefills the new service with the default parameters.
5. Edit the service name in the New Name field, which is by default the name of a service template.
6. Enter a unique name in the Version Number field.
7. Select an organization for this service from the Organization dropdown list, or leave it blank for the global service.
8. Click Save to update the changes.

To configure a System Event Publisher service:

1. Select Services > Core Global Services.
2. Locate a System Event Publisher service and click Edit.
3. Select the Service Definition tab to configure the service.

   

4. Select a service connection from the Service Connection dropdown list, which the service will use to publish the events. Alternatively, click the Edit link to configure the selected service connection.
5. Click Save to update the changes.
6. Select the Parameters Edit tab to configure the service parameters.

   

Note

You can edit the parameters in the Parameters tab as well.

7. Select Audit Log Publish to publish audit log events. It is not selected by default.
8. Specify a queue name in the Audit Log Queue field to publish audit log events to, or leave it blank to use the default queue specified in the Queue Name of this service connection.
9. Select Job Publish to publish job events.
10. Specify a queue name in the Job Queue field to publish job events to, or leave it blank to use the default queue specified in the Queue Name of this service connection.
11. Select Submission Error Log Publish to publish the submission error log as part of a submission event. The Submission Publish checkbox below must also be selected. It is selected by default.
12. Select Submission Event Log Publish to publish the submission event log as part of a submission event. The Submission Publish checkbox below must also be selected. It is selected by default.
13. Select Submission Form Data Map Publish to publish the submission form data map as part of a submission event. The Submission Publish checkbox must also be selected. It is selected by default.
14. Select Submission Groovy Log Data Publish to publish added submission groovy service log data as part of a submission event. The Submission Publish checkbox must also be ticked. It is selected by default.
15. Select Submission Groovy Log Publish to publish added submission groovy service logs as part of a submission event. The Submission Publish checkbox below must also be selected. It is selected by default.
16. Select Submission Milestone Publish to publish added submission milestones as part of a submission event. The Submission Publish checkbox below must also be selected. It is not selected by default.
17. Select Submission Property Publish to publish submission properties as part of a submission event. It is not selected by default.
    Note

    You also must select the Submission Publish checkbox below for the Submission Property Publish setting to take effect.

Adding all properties to the event can significantly increase its size, which, in turn, may cause a system event publisher delivery error when using AWS. It depends on the underlying queue configuration. For AWS, if a message size exceeds the maximum allowed, an error will occur, for example, One or more parameters are invalid. Reason: Message must be shorter than 262144 bytes.

18. Select Submission Publish to publish submission events. It is selected by default.
19. Specify a queue name in the Submission Queue field to publish submission events to, or leave it blank to use the default queue specified in the Queue Name of this service connection.
20. Select Submission Request Log Publish to publish added submission request log as part of a submission event. The Submission Publish checkbox below must also be selected. It is selected by default.
21. Select System Health Publish to publish hourly system health events. It is not selected by default.
22. Specify a queue name in the System Health Queue field to publish system health events to, or leave it blank to use the default queue specified in the Queue Name of this service connection.
23. Select User Auth Publish to publish user authentication events.  |   18.11 This feature was introduced in 18.11.
24. Specify a queue name in the User Auth Queue field to publish authentication events to, or leave it blank to use the default queue specified in the Queue Name of this service connection.  |   18.11 This feature was introduced in 18.11.
25. Click Save to update the changes.

Next, learn how to configure an AWS SQS System Event Publisher service.