Procedure: Fast Upgrade Unica Journey

Note: If you already have Journey, you can perform a Fast Upgrade only if your existing version is 12.1.7, 12.1.8, or 12.1.9. If your existing version is earlier than 12.1.7, contact Unica support for a utility to perform the Fast Upgrade.

Before you begin

  1. Ensure that Unica Platform is upgraded successfully on the target setup.
  2. Install Journey 25.1.1 on the target setup.
  3. Take a backup for base Journey system database and Journey report database.
  4. Ensure that the Journey files folder (<Journey_installation_Location>/Files) are copied from the base system to the target system.
  5. Ensure that the base Kafka logs files are copid from base to target setup.
  6. Drop the Journey system schema and report schema and create new schema.
  7. Restore the backed up database schema on target system.
    Note: We recommend that you maintain the same schema names for Journey system schema and Journey report schema.
  8. The operating system must be same (Linux-to-Linux / Windows-to-Windows). Cross operating system migration is not supported.
    Attention: Ensure that you back up the Ignite base work directory for Web and Engine.
    Note: If you to use different schema names other than target schema name, perform all the suggested database upgrade steps and update the same database schema names in the application server files and the engine application.properties file.

Upgrading the Unica Journey database manually

About this task

Once the base Journey database (Journey system and Journey report) is restored on the target database, depending on the provided upgrade path, perform the following steps for executing delta database scripts:

Procedure

  1. For Source Version 12.1.7 and Upgrade Path 12.1.7 to 25.1.1:
    Run the SQL scripts, specific to your database setup, from the mentioned location on the target database. Ensure that the source database is restored on the target database setup.
    Example: If your database setup has MariaDB, run the following scripts:
    • From the <Journey_installation_Location>/Web/ddl/upgrade1217to1218/ location, run the journeyMariaDBUpgrade12.1.8.sql on Journey system database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade1218to1219/ location, run the journeyMariaDBUpgrade12.1.9.sql script on Journey system database, and run the journeyReportMariaDBUpgrade12.1.9.sql script on Journey report database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade1219to12110/ location, run the journeyMariaDBUpgrade12.1.10.sql on Journey system database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade12110to251/ location, run the journeyMariaDBUpgrade25.1.sql on Journey system database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade25101to2511/ location, run the journeyMariaDBUpgrade25.1.1.sql on Journey system database.

  2. For Source Version 12.1.8 and Upgrade Path 12.1.8 to 25.1.1:
    Run the SQL scripts, specific to your database setup, from the mentioned location on the target database. Ensure that the source database is restored on the target database setup.
    Example: If your database setup has MariaDB, run the following scripts:
    • From the <Journey_installation_Location>/Web/ddl/upgrade1218to1219/ location, run the journeyMariaDBUpgrade12.1.9.sql script on Journey system database, and run the journeyReportMariaDBUpgrade12.1.9.sql script on Journey report database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade1219to12110/ location, run the journeyMariaDBUpgrade12.1.10.sql on Journey system database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade12110to251/ location, run the journeyMariaDBUpgrade25.1.sql on Journey system database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade25101to2511/ location, run the journeyMariaDBUpgrade25.1.1.sql on Journey system database.

  3. For Source Version 12.1.9 and Upgrade Path 12.1.9 to 25.1.1:
    Run the SQL scripts, specific to your database setup, from the mentioned location on the target database. Ensure that the source database is restored on the target database setup.
    Example: If your database setup has MariaDB, run the following scripts:
    • From the <Journey_installation_Location>/Web/ddl/upgrade1219to12110/ location, run the journeyMariaDBUpgrade12.1.10.sql on Journey system database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade12110to251/ location, run the journeyMariaDBUpgrade25.1.sql on Journey system database.

    • From the <Journey_installation_Location>/Web/ddl/upgrade25101to2511/ location, run the journeyMariaDBUpgrade25.1.1.sql on Journey system database.

    Here, the target database is ready with database upgrade scripts.

  4. Run the Database Mingration utility (only if the source version is earlier than 12.1.9):
    From the <Journey_installation_location>/tools location, open the migration.properties file and provide the following details:
    • Database Type
    • Database URL
    • Database_Username
    • Database_Password
    • Journey_Base_Vesion
    • Journey_Current_Vesion
  5. Run the DataMigrationUtility.jar file using the following command and verify if the migration utility is sucessful: 
    java -jar DataMigrationUtility.jar <Fully qualified path of the Migration.properties file>

Fast Upgrade

Procedure

  1. Copy the Ignite work directory from Source System to Target System of Web and Engine.
    Location:
    • /<Journey_Installation_Location>/Web/ignite
    • /<Journey_Installation_Location>/Engine/temp
  2. In the application server, update the JNDI details (schema / SID, userid, password) for Journey JNDI as per the new database schema used with version 25.1.1 environment.
  3. Provide the correct path of the Ignite and temp work directory in application.properties of Web and Engine.
  4. As mentioned earlier, ensure that the Journey files folder ( in the location <Journey_installation_Location>/Files) are copied from the source system to the target system.
  5. As mentioned earlier, ensure that the source Kafka logs are copied from the source setup to the target setup.
  6. Start the kafka services and ensure that the kafka services have started error-free.

Setting the Journey – Help About > Version

About this task

Change the Unica Journey version in the Unica Platform registration:

Procedure

  1. Export the version configuration using the following command on clean 25.1.1 environment: 
    ./configTool.sh -x -p "Affinium|Journey|about" -f "Journey_about.xml"
  2. Edit the Journey_about.xml file generated by the above command. Change the version to 25.1.1.0.0.GA_BUILD".<GA_BUILD>. Replace this with build number referring to version.txt from installation location. 
    <property id="xxxxxx" name="releaseNumber" type="string_property" width="40">
<value>25.1.1.0.0.GA_BUILD</value>
</property>
  3. Import the earlier mentioned edited file using the following command: 
    ./configTool.sh -v -i -o -p "Affinium|Journey" -f "Journey_about.xml"
  4. Once the Journey Web application is up and running, acccess the About page to check the Journey build version.

Post Upgrade Steps

Procedure

  1. On the target setup, navigate to the Journey node Affinium|Journey|navigation and update the new setup navigation URL:
    • serverURL
    • serverURLInternal
  2. Change the Platform client ID and Platform client Secret in the application.properties of Web and Engine. 
    cd <Platform_Installation_Location>/tools/bin
./clientDetails.sh -a Journey
    OUTPUT

ClientID: 495524
ClientSecret: BcjdpWqWfzPiY8M
AppName: Journey
ClientSecret and ClientId generated successfully!!
  3. Start the application server to start Journey Web and verify if you can navigate to all Journey menu items, and if you can create Journeys and perform operations on Journeys.
  4. To start the engine, encrypt the database password by running the utility and update the encrypted passwords in Journey Engine application.properties file 
    cd <Journey_Installation_Location>/tools
./JourneyEncryptionUtility.sh <Journeys_SystemDB>
./JourneyEncryptionUtility.sh <Journeys_ReportDB>
  5. Before starting the Journey Engine, complete the following steps:
    1. Navigate to the <Ignite_Home>/work/db directory. Verify if there are multiple folders in the system. If there are multiple folders, choose the latest one.
    2. Confirm if any folder like nodexx-xxxx-xxxx-xxxx-xxxx-xxxxxx exists.
    3. Also confirm if there are multiple folders in the system. If there are multiple folders, choose the latest one.
    4. Copy the name of the folder.
    5. Open application.properties file of Journey Engine and add the following properties:
      journey.data.migration.required= true
ignite.upgrade.node= <the name of the node folder which is copied from ignite work/db directory>
    6. Run the Journey Engine JAR again. In this run, the JAR will work as a migration utility.
    7. Verify the logs for errors. Ideally, there will not be any errors.
    8. Wait for the utility to complete running.
    9. If the utility executes without error, remove the entry journey.data.migration.required from the application.properties file.
  6. Start the Journey Engine. The Journey Engine should started successfully.
  7. Verify that the old migrated Journey is processing the data.
  8. Verify that the newly created Journeys are processing data.