Procedure: Fast upgrade Marketing Operations

Marketing Operations pre-upgrade

Procedure

  1. Import the Marketing Operations system tables backup from the old version to the system tables schema used in a clean 11.0 environment.
  2. Take a file system backup of the source and the destination of the following folders:

    “MarketingOperations_HOME/ accountattachments" directory.

    “MarketingOperations_HOME/ approvalitems" directory.

    “MarketingOperations_HOME/ assets�? directory.

    “MarketingOperations_HOME/ componentattachments" directory.

    “MarketingOperations_HOME/ images" directory.

    “MarketingOperations_HOME/ invoiceattachments" directory.

    “MarketingOperations_HOME/ planattachments" directory.

    “MarketingOperations_HOME/ programattachments" directory.

    “MarketingOperations_HOME/ projectattachments" directory.

    “MarketingOperations_HOME/ templates" directory.

    “MarketingOperations_HOME/ messages" directory.

    “MarketingOperations_HOME/ conf" directory.

  3. Copy all the required files mentioned in step2 in 11.0from the source folders to the destination MarketingOperations respective folders.
  4. Also copy “MarketingOperations_HOME/ conf/ plan_log4j.xml�? and “MarketingOperations_HOME/ conf/ plan_ehcache.xml�? in 11.0 from source to destination respective folders.
  5. Create a new folder ext_data on a destination server at the - “<PLAN_HOME>\messages\com\ibm\umo\�? path. This new folder at the destination will contain the new 11.0 <UMOConfigurationMessages_<locale>.properties > files.
  6. Copy <UMOConfigurationMessages_<locale>.properties> and <UMOMktObjectConfigurationMessages_<locale>.properties> in 11.0 from the “MarketingOperations_Home/messages/com/ibm/umo/ext�? from the source folder for each local to the respective destination folder (“MarketingOperations_Home/messages/com/ibm/umo/ext ).
  7. If there are marketing objects in the source setup, copy following files on 11.0:mo_creatives_state.xml globalstates.xml sysmenu.xml sysmodules.xml from <MarketingOperations_Home>/conf/en_US from source to 11.0
  8. Perform this step if you have installed Marketing Operations and chose manual database. Ignore this step if you have chosen the automatic database.
    1. Unregister the Marketing Operations - ./configTool.sh -u Plan
    2. Register with 8.6 config:

      ./configTool.sh -r Plan -f "MarketingOperations_Home/conf/plan_registration.xml"

      Use following command:

      configTool.bat -vp -p "Affinium" -f“MarketingOperations_Home/conf /plan_registration.xml"

Upgrading Marketing Operations

Updating JDBC files

About this task

In case you do not want to reuse the Plan schema used in the 11.0 clean installation and rather want to use another user schema, follow the additional steps underneath:

Procedure

  1. Back up the jdbc.properties file from the 11.0 environment (MarketingOperations/tools/bin /umo_jdbc.properties). Update the username of the 11.0 platform system database / schema name in the umo_jdbc.properties file.
    Example of umo_jdbc.properties:

    # Name:

    #umo_data_source.url

    # Description:

    #URL reference for the IBM Marketing Operations system table database.

    #

    # Example values for supported databases are:

    #

    # SQL Server:

    #jdbc:sqlserver://sqlserverHost:1433;databaseName=databaseName

    # IBM DB2:

    #jdbc:db2://db2Host:50000/databaseName

    # Oracle:

    #jdbc:oracle:thin:@oracleHost:1521:databaseName

    umo_data_source.url=jdbc:oracle:thin:@tiger118.nonprod.hclpnp.com:1521:orcl

    # Name:

    #umo_data_source.login

    # Description:

    #Name of login for IBM Marketing Operations database-

    #login account must have database administrative rights.

    # Name of login for IBM Marketing Operations database.

    #login account must have database administrative rights.

    umo_data_source.login=xmsp

    # Name:

    #umo_data_source.password

    #Description:

    #Password for IBM Marketing Operations database

    #for login id provided in umo_data_source.login property

    umo_data_source.password=ENC(+1Kd731xEuzqdDfqjQ9wnw==)

    Note: If you have used the same user in the Platform and Marketing Operations, you can take the encrypted password from the Platform/tools/bin/jdbc.properties file.
  2. Upgrade to 11.0.0.0 config:
    1. Copy the 8.6 plan_registration.xml to the UMO_HOME\conf folder.
    2. Run the commands underneath at Platform_Home/tools/bin:./configTool.sh -vp -p "Affinium|Plan|umoConfiguration" -f MarketingOperations_Home/conf/plan_approvals_settings_10.0.0.2.xml"./configTool.sh -vp -p "Affinium|Plan|umoConfiguration" -f MarketingOperations_Home/conf/plan_workflowservice_settings_10.0.0.2.xml"run config_migration.sh in MarketingOperations_Home/tools/bin
      Prerequisite:set/update UMO_HOME in the config_migration.sh file
      ./config_migration.sh -p MarketingOperations_Home -b 8.6.0.0

Upgrading Marketing Operations database

Procedure

  1. Import the database with the source system tables of the VM containing the fresh installation of 11.0.0.0 Marketing Operations.

    1. Run the umouilistupgrade utility from tools/bin to merge the UMOConfigurationMessages_<locale>.properties and the UMOMktObjectConfigurationMessages_<locale>.properties of 8.6 and 11.0. This utility does not have any parameters: umouilistupgrade.bat
    2. Run the umodbsetup utility to upgrade the database to 11.0.0.0:umodbsetup.bat –t upgrade –m –b 8.6–L en_US(Type the above command in the command prompt. Copy - paste might give an error.)
    3. Execute the command:umodbsetup.bat –t upgrade –b 8.6 If this does not work, you can execute the umo_upgrade_[8.6.0.0.0]_[11.0.0.0.0].sql file on the MO database. This file is located at MarketingOperations_Home\tools.

Marketing Operations post-upgrade

Marketing Operations Configuration changes

About this task

Deploy MO 11.0.0.0 war and run the Marketing Operations Java Upgrade as in the following procedure:

Procedure

  1. Login as admin user.
  2. In (Affinium|Plan|umoConfiguration) update the location for the nodes lised underneath:templatesattachmentFoldersintegrationServices
  3. Update notifyPlanBaseURL in Affinium|Plan|umoConfiguration|notifications.
  4. Update serverURL in Affinium|Plan|navigation.
  5. Goto Settings -> Marketing Operations -> Marketing Operations Upgrade.
  6. Check all the checkboxes.
  7. Click the “Upgrade�? button.

Setting the Marketing Operations – Help About > Version

About this task

Change the Marketing Operations version in the Marketing Platform registration:

Procedure

  1. Export the version configuration using the following command on clean 11.0 environment:configTool.sh -x -p "Affinium|Plan|about" -f <PLATFORM_HOME>/conf/plan_about.xml
  2. Edit the plan_about.xml file generated by the above command. Change the version to 11.0.0.0.0.GA_BUILD".

    <property id="xxxxxx" name="releaseNumber" type="string_property" width="40">

    <value>11.0.0.0.0.GA_BUILD</value>

    </property>

  3. Import this edited xml file using the following command:configTool.sh -v -i -o -p "Affinium|Plan" -f <PLATFORM_HOME>/conf/plan _about.xml

Marketing Operations Post Upgrade Functional check

About this task

Perform UAT on the Marketing Operations application. Ensure that all the Plans, Programs, Projects, Tasks, Approvals are opening and that the data is successfully imported. Ensure if all the configurations nodes are available.