Waiting for engine...
Skip to main content

Implementing Secure Listen

Developers can implement listeners and deploy them to execution workers running in Runtime clouds.

Secure Listen​

Secure Listen enables any supported connector having a Listen operation to deploy to, listen on, and execute from an Execution worker running in a Runtime cloud. Previously, execution workers could execute Listener processes for some connector (JMS, Web Services Server, Flow Services Server, etc.). However, the Listener itself was not running on the Execution worker. Since you can enable public and private runtime clouds for a multi-tenant environment (subordinate accounts of the account owning the Cloud where attachments may be added to the Runtime cloud), listeners built with the Connector SDK could not deploy to and run in those environments. Because of this, Runtime cloud nodes were protected from being disrupted because no security manager was in place.

note

The Microsoft Azure Service Bus and Salesforce Platform Events connectors already feature multi-tenant support for private runtime clouds and Runtime clusters, do not have an Execution worker, and are not affected by the Secure Listen feature.

Connector requirements​

For a connector to implement Secure Listen, it must be:

  • Built using the Connector SDK and use the Listener API to build and submit payloads.
  • Owned by the account that owns the Runtime cloud, be shared as a connector resource from the account owning the Runtime cloud, or be owned by a subordinate account from the account owning the Runtime cloud.
  • Either a public connector (available to all users) or a private connector (available to the current account or shared with the account as a connector resource within its account group).

Runtime cloud requirements​

For a Runtime cloud to implement Secure Listen, it must:

  • Be enabled to support Secure Listen by setting the com.boomi.container.listen.secure.enabled container property to True. To learn more, see the topic Configuring at Runtime cloud for Secure Listen.

    Attention: By default, new Runtime clouds automatically enable Secure Listen and set this property to True. When set to True, the Runtime cloud and any single tenant containers (Runtime cloud node's main JVM or Execution worker JVM) support single tenant connectors allowing the listeners to run. To maintain backward compatibility, Clouds having this property previously set to True or False is respected, and is not changed. If required, you must manually change the setting.

  • Have the Execution Workers Enabled property in the Properties panel, Advanced tab of Runtime Management (com.boomi.container.worker.enabled) selected. This ensures processes can listen and execute from the Runtime cloud environment using the workers. To learn more, refer to the Properties panel, Advanced tab page.

Important: Do not set a value for the Listener Startup Mode property in the Properties panel, Advanced tab of Runtime Management (com.boomi.container.startListeners). To learn more, see the topic Properties panel, Advanced tab.

Runtime cloud Attachment requirements​

For a Runtime cloud Attachment to implement Secure Listen, it must:

  • Have the Execution workers property value in the Attachment Quotas tab of Cloud Management set to at least one.
  • Have the Minimum Execution Workers property value in the Attachment Quotas tab of Cloud Management set to at least one.
  • Have the Execution Worker Warmup Enabled property value in the Attachment Quotas tab of Cloud Management set to True.

To learn more, refer to the Attachment Quotas tab.

Secure Listen implementation process​

Use these steps to understand how Secure Listen works and the implementation process:

  1. Set up a basic runtime in a Runtime cloud.
  2. Enable Secure Listen in the Runtime cloud.
  3. Select the Execution Workers Enabled check box in the Properties panel, Advanced tab of Runtime Management (com.boomi.container.worker.enabled). To learn more, refer to the Properties panel, Advanced tab page.
  4. Share the Runtime cloud as a resource to a subordinate account.
  5. Add an attachment of the Runtime cloud to a subordinate account and configure the attachment settings. To learn more, refer to the Runtime cloud Attachment requirements section.
  6. Verify on the Workers panel that there is an active worker. To learn more, refer to the Workers panel page.
  7. Build a connector having a Listen operation using the Listener API. To learn more, refer to Building a connector and Implementing the Listen operation.

Next Steps​

On this Page