Adding server groups
Create server groups for Campaign to complete test runs of interactive flowcharts. Define the location of at least one runtime server in the server group.
*
You must fully install and deploy Marketing Platform for each server group. If you install multiple Interact server groups, you must fully install and deploy Marketing Platform for each runtime server group. Each Interact runtime server can be associated with one design time environment only.
You must define the locations of the Interact runtime servers on the Configuration page in Marketing Platform. The design time environment must be able to access the runtime servers for deploying and completing test runs of interactive flowcharts.
You must create at least one server group, and the server group must contain at least one Interact runtime server that is defined by the instance URL.
You can have multiple server groups. For example, you can have one server group to interact with your website, one server group to interact with your call center, and one server group for testing. Each server group can contain multiple instance URLs, and each instance URL can represent one instance of Interact runtime.
If you have multiple Interact design time systems running in your environment, an Interact runtime server that is configured with a design time cannot be configured with any other design time. If two different design times send deployment data to the same Interact runtime, the deployments can become corrupted and undefined behavior occurs.
For every server group in the Interact design time configuration, you must specify the JNDI name for the user profile tables. This is necessary to support runtime features in Interact, such as global offers, offer suppression, score override, and SQL offers in the Interact List process box.
Create server groups by setting the serverGroup configuration property in the Campaign > partitions > partitionN >Interact > serverGroups template category. The name is used only for organizational purposes. However, you can use the same name for the property as the serverGroupName property to avoid confusion.