Creating partitions for eMessage allows you to isolate and secure data for different groups of users. Each partition appears to users as a separate instance of
eMessage, with no indication that other partitions exist on the same system. Because each partition has its own set of configuration properties, you can customize
eMessage for each group of users.
Users within each partition can access only those functions, data, and customer tables configured for the partition. For example, if you create partitions named partition1 and
partition2,
eMessage users working in
partition1 can select email recipients from customer tables configured in
partition1, but not in
partition2.
IBM® does not recommend creating multiple partitions if users need to share data.
When you work with multiple partitions, you should understand characteristics that are unique to partitions for eMessage and how partitions for
eMessage relate to partitions for
Campaign. You should also be familiar with the workflow for creating and configuring multiple partitions for
eMessage.
You must request a separate IBM® EMM Hosted Services account for each partition.
IBM® will provide a user name and password connected to the account. You must configure a
Marketing Platform data source that can provide these access credentials automatically when
eMessage connects to
IBM® EMM Hosted Services.
Each partition in eMessage operates in conjunction with a specific partition created in the
Marketing Platform for
Campaign. The
Campaign partition provides the following.
Because eMessage operates with
Campaign within a specific partition, the
eMessage and
Campaign partition structures must specify the same name. The partition names must match exactly.