Progress Sonic 8.5 Installation and Upgrade Guide - Product ...

Chapter 4: Setting Up Containers
Note Containers That Connect Over Management Routing Nodes — When you are defining
a container that intends to use a management routing nodes.
On the broker that will route to the management node, the required properties are:
● CENTRAL_CONNECTION — Set to true
On the containers that will connect to the local broker connected to the management node
to handle management routing, the required properties are:
● DOMAIN_NAME — The domain that will manage the configuration.
● ConnectionURLs — List of acceptors on brokers in the management routing node.
● CONTAINER_PATH — Folder path and name of the container plus @ followed by the
routing node name.
● MANAGEMENT_NODE — Specifies the routing definition for the management node on the
management routing brokers.
◆ To create a setup file for a new container configuration
1. In your preferred text editor, enter name=value pairs for at least the required setup
properties. For example, for container ct001 that does not exist in the domain:
DOMAIN_NAME=Domain1
ConnectionURLs=tcp://myDMhost:2506
CONTAINER_PATH=/Containers/ct001
LOG_FILE=./Domain1.ct001.log
CREATE_IF_DOES_NOT_EXIST=true
2. Add other properties as appropriate.
3. Save the file in the form container_name.setup. For this example, ct001.setup.
4. Position the file so that it can be read on its intended host system where a Sonic
Launcher installation is available.
◆ To edit a generated setup file for a container
1. In your preferred text editor, open the generated setup file.
2. Do not change the specified properties as the file was generated from an existing
configuration.
3. Confirm that the property CREATE_IF_DOES_NOT_EXIST is either not in the file, or—if it
is in the file—it is set to false.
4. Add additional properties as appropriate.
130 Progress Sonic Installation and Upgrade Guide 8.5