Creating and populating the Marketing Operations system tables

If the automatic database setup fails during the installation of Marketing Operations, you must create and populate Marketing Operations system tables manually. To generate Marketing Operations system tables, you must run the umodbsetup utility.

The umodbsetup utility completes one of the following tasks:

  • Creates the required system tables in the Marketing Operations database and populates the tables with required default data.
  • Outputs the database creation and population scripts to a file that you or your DBA can then run in your own database client.

Configuring environment variables

Before you run the umodbsetup utility, complete the following steps to configure the environment variables properly:

  1. From the <IBM_EMM_Home>\<MarketingOperations_Home>\tools\bin directory, locate and open the setenv file in a text editor.
  2. Verify that the JAVA_HOME variable indicates the correct directory for your installation of Java™, and that the JDBC drivers are the first entry for the DBDRIVER_CLASSPATH variable. For more information about setting this environment variable, see JAVA environment variables.
  3. Save and close the file.
  4. From the <IBM_EMM_Home>\<MarketingOperations_Home>\tools\bin directory, locate and open the umo_jdbc.properties file.
  5. Set values for the following parameters.
    • umo_driver.classname
    • umo_data_source.url
    • umo_data_source.login
    • umo_data_source.password
  6. Save and close the file.

Running the database setup utility

From a command prompt or UNIX™ shell, go to the <IBM_EMM_Home>\<MarketingOperations_Home>\tools\bin directory. Run the umodbsetup utility and provide appropriate input for the parameters that are required for your situation.

For example, the following command runs a full database installation (rather than an upgrade), sets the locale to en_US, and sets the logging level to high:

./umodbsetup.sh -t full -L en_US -l high

Following is a description of all the possible variables for the utility:

Table 1. Variables for the umodbsetup.sh utility
Variable Description
-h Provides help for the utility.
-l

Records the output in the umo-tools.log file from the actions of the umodbsetup utility . This file is in the <IBM_EMM_Home>\<MarketingOperations_Home>\tools\logs directory. This variable specifies the logging level.

You can set the logging level to high, medium, or low.
-L

Sets the default Locale for the installation. For example, use -L de_DE for a German installation.

The valid entries for locales include de_DE, en_GB, en_US, es_ES, fr_FR, it_IT, ja_JP, ko_KR, pt_BR, ru_RU, and zh_CN.

Note: The locale information is case-sensitive and must be used as mentioned in the guide.
-m

Outputs the scripts to a file in the <IBM_EMM_Home>\<MarketingOperations_Home>\tools directory, which you can then run manually. Use this option if there is a reason you must run scripts from your own database client application. When you use this variable, the umodbsetup tool does not run the script.
-t

Type of database installation. Valid values are full and upgrade. For example, -t full
-v

Verbose.
-b

For upgrades only. Identifies the base version of the database that you are attempting to upgrade.

By default, the utility detects the version of the database you are upgrading. However, if an earlier attempt to upgrade the database failed in some way, the version might be the updated one, even though the upgrade failed. When you have correct the problem and run the utility again, you use this variable with the -f variable to specify the correct base version.

For example, -f -b 9.0.0.0
-f For upgrades only. Instructs the utility to use the base version that is specified by the -b variable, overriding the base version that may detect in the database. See the description of the -b variable.
-E

This option is used to encrypt existing password available in file. You can use this option along with other options like -t, -P.

For example, umodbsetup.bat/sh -E
-P

This option is be used to change existing password and encrypt it. If user chooses this option, the tool prompts user to enter new password. The new password is stored in umo_jdbc.properties file after encrypting. Use this option independently as it prompts for new password.

For example, umodbsetup.bat/sh -P

Running the database scripts manually

If you used the -m variable to output the scripts so you can run them from your own database client application, run the scripts now.

Do not deploy the plan.war file before you create and populate the system tables.