Skip to main content
Feedback

Configuring Secure Listen Property for a Runtime cloud

To enable the connector on a Private runtime cloud, change its security policy to Low. If you are using Private runtime cloud with execution worker enabled, you can perform Secure Listen operation by configuring the secure listen property in the Runtime Management.

Note: Make sure you have the Runtime Management privilege to set the properties

Before you begin

Verify that you have the Runtime Management privilege.

Procedure

  1. Go to Manage > Runtime Management.

  2. Do one of the following:

    1. If you are the owner of a Private runtime cloud, select your Cloud from the list on the left.

    2. If you are an account owner, select your basic runtime from the list on the left.

  3. Do one of the following:

    1. Private runtime cloud Owner: Open the Properties panel.

    2. Account Owner: Open the Account Properties panel.

  4. Click the Custom tab.

  5. To enable the Secure Listen container property for a runtime cloud:

    1. Click Add A Property in the Container Properties section.

    2. In the Property Name field, type as com.Boomi.container.listen.secure.enabled.

    3. In the Property Value field, enter True.

    By default, this property is set to False and the runtime cloud and listener feature does not change. 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.

  6. Click the Advanced tab.

  7. In the dropdown box, select the execution workers Enabled property from the list and click Add a Property.

  8. Select the check box in the Property Value field next to the property name. By selecting the check box for this property, the runtime cloud can use execution workers. execution workers are required when the com.Boomi.container.listen.secure.enabled container property is set to True on the Custom tab.

  9. Click Save.

Next Steps

The changes to many of these properties do not take effect until the basic runtime or private runtime cloud is restarted, you are prompted to restart. You have the option to restart now or restart later. Only basic runtime and Cloud owners can restart them. Accounts that have a basic runtime in a Cloud cannot restart the Cloud. For more details, refer to Enabling Secure Listen for an AtomCloud topic.

On this Page