Setting up multiple partitions

Configure multiple partitions in Campaign to isolate and secure data for different groups of Campaign users. As each partition has its own set of configuration properties, you can customize Campaign for each group of users.

Before you configure additional partitions in Campaign, complete the following tasks for each partition that you are configuring:

Create database or schema for the Campaign system tables

Create ODBC or native connections

Create JDBC connections in the web application server

Complete the following tasks to set up multiple partitions for Campaign:

Create the system tables database and any other data sources required for your partitions. Then configure the JDBC and ODBC or native connections required to access your data sources.

For each partition, create a different schema in your database to hold the system tables.

Use the database-specific scripts packaged with Campaign to create and populate the system tables.

Complete the following tasks to create a directory structure for each additional partition:

Save a clean copy of the original partition1 directory to serve as a backup.

In the partitions directory under your Campaign installation, create a duplicate of the default partition1 directory for each partition that you are adding, ensuring that you include all subdirectories.

Name each partition directory with a unique name. Use these exact same names for the partitions when you later create their configuration trees on the Configurations page.

If you want to create a second partition and created the directory named Campaign/partitions/partition2, when you create the configuration tree on the Configurations page, you must use the name "partition2" to identify this partition.

Delete any files that exist in the duplicate partition subdirectories.

Complete the following tasks to use the partitionTool utility with the -s option to clone the default partition:

If you decide not to use this option, you must stop the web application server where Marketing Platform is deployed before performing this procedure.

Set the JAVA_HOME environment variable, either in the setenv script located in the tools/bin directory of your Marketing Platform installation, or in the command line window in which you run the partitionTool utility.

Open a command line window and run the utility from the tools/bin directory under your Marketing Platform installation. Use the appropriate command and options (as described in the Marketing Platform Administrator's Guide) to achieve your desired results.

partitionTool -c -s partition1 -n partition2

Repeat this procedure for each new partition you need to create.

When you are finished, stop and restart the application server where Marketing Platform is deployed to see the groups that were created.

For complete information on using this utility, see partitionTool.

Complete the following tasks to create the partition structure on the Configuration page by using the New partitionTemplate for each new partition:

On the Configuration page, navigate to Campaign > partitions and click (partitionTemplate).

If you do not see the (partitionTemplate) property in the list, use the configTool utility to import the partition template, using a command similar to the following:

configTool -i -p "Affinium|Campaign|partitions" 
		-f <CAMPAIGN_HOME>/conf/partitionTemplate.xml

Replace CAMPAIGN_HOME with the actual path to your Campaign installation.

The configTool utility is found in the tools directory under your IBM® Marketing Platform installation. See the IBM® Marketing Platform Administrator's Guide for information on using this utility.

In the right pane, you see the partitionTemplate pane with an empty New category name field.

Enter the name for the new partition, using the same name that you used when creating the partition's directory structure in the file system in Setting up multiple partitions.

Click Save Changes.

You see the new partition structure, with the same categories and properties as in the partition template.

Configuring data source properties for partitions

Setting up system users for Campaign

Using IBM Cognos Reports for multiple partitions