|
To import partition and data source templates supplied with Campaign, which you can then modify and duplicate using the Configuration page.
|
|
To register (import configuration properties for) IBM® EMM products, if the product installer is unable to add the properties to the database automatically.
|
|
To delete categories that do not have the Delete Category link. You do this by using configTool to export your configuration, then manually deleting the XML that creates the category, and using configTool to import the edited XML.
|
|
This utility modifies the usm_configuration and usm_configuration_values tables in the Marketing Platform system table database, which contain the configuration properties and their values. For best results, either create backup copies of these tables, or export your existing configurations using configTool and back up the resulting file so you have a way to restore your configuration if you make an error when using configTool to import.
|
|
Only categories and properties within an application may be deleted using this command, not whole applications. Use the -u command to unregister a whole application.
|
|
To delete categories that do not have the Delete Category link on the Configuration page, use the -o option.
|
|
When you use the -r option, the registration file must have <application> as the first tag in the XML.
|
|
The registration file for the Marketing Platform is named Manager_config.xml, and the first tag is <Suite>. To register this file on a new installation, use the populateDb utility, or rerun the Marketing Platform installer as described in the IBM® Marketing Platform Installation Guide.
|
|
After the initial installation, to reregister products other than the Marketing Platform, use configTool with the -r option and -o to overwrite the existing properties.
|
|
Import configuration settings from a file named Product_config.xml located in the conf directory under the Marketing Platform installation.
|
|
Import one of the supplied Campaign data source templates into the default Campaign partition, partition1. The example assumes that you placed the Oracle data source template, OracleTemplate.xml, in the tools/bin directory under the Marketing Platform installation.
|
|
|
Export an existing Campaign partition (complete with data source entries), save it to a file named partitionTemplate.xml, and store it in the default tools/bin directory under the Marketing Platform installation.
|
|
Manually register an application named productName, using a file named app_config.xml located in the default tools/bin directory under the Marketing Platform installation, and force it to overwrite an existing registration of this application.
|
Copyright IBM Corporation 2015. All Rights Reserved.
|