Partitions for IBM eMessage: Overview

Creating partitions for IBM eMessage allows you to isolate and secure data for different groups of users. Each partition appears to users as a separate instance of IBM 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 IBM 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, IBM eMessage users working in partition1 can select email recipients from customer tables configured in partition1, but not in partition2. HCL 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 IBM eMessage and how partitions for IBM eMessage relate to partitions for Unica Campaign. You should also be familiar with the workflow for creating and configuring multiple partitions for IBM eMessage.

Characteristics of partitions for IBM eMessage

Note the following when you create and configure new partitions for IBM eMessage.

  • You create partitions for IBM eMessage differently than you do for Unica Campaign.

    You create new partitions for IBM eMessage using a partition template available in the eMessage configuration properties in Unica Platform.

  • The name of each IBM eMessage partition must exactly match the name of its corresponding Unica Campaign partition.

  • Each partition that you create for IBM eMessage must be able to connect to IBM Hosted Services.

    You must request a separate IBM Hosted Services account for each partition. will provide a user name and password connected to the account. You must configure a Unica Platform data source that can provide these access credentials automatically when IBM eMessage connects to IBM Hosted Services.

    For more information about how to request an account, see the IBM eMessage Startup and Administrator's Guide.

Relationship to partitions in Unica Campaign

Each partition in IBM eMessage operates in conjunction with a specific partition created in the Unica Platform for Unica Campaign. The Unica Campaign partition provides the following.

  • Unica Campaign schema that contains the eMessage system tables
  • File structure for Unica Campaign in the partition, including directories used by IBM eMessage to create and process recipient lists
  • Configuration properties associated with creating recipient lists and enabling IBM eMessage within the partition

Because IBM eMessage operates with Unica Campaign within a specific partition, the IBM eMessage and Unica Campaign partition structures must specify the same name. The partition names must match exactly.