Upgrading NexJ Contact to version 6.1

During the upgrade process, you will need to update the environment files, back up and update the application servers, and back up and upgrade the databases for your deployment.

Note: As a best practice, it is recommended that you upgrade the Push Redirector to match your application framework version when you upgrade the application.
To upgrade to version 6.1:
  1. Update the environment file or the connections file to remove old or deprecated connections.
    For more information, see Removing obsolete connections for version 6.1.
  2. Update the environment file or the connections file with new data source connections, channel connections, and SOA connections.
    For more information, see Adding new connections for version 6.1.
  3. Update the environment file or the server and connection files with other changes required to support new functionality.
    For more information, see Updating the server information for version 6.1.
  4. Back up application server files.
  5. Back up all databases.
  6. Optional: Add required mixins to your models.

    If you do not add the mixins to the model, you will be prompted to do so when you deploy the model.

    For more information, see Adding mixins to models.

  7. Create new data sources.
    The following data sources are required to support new features:
    • rules:Rules
    • uicomp:UIComponent
    • ilm:LeadManagement
    • flow:Flow
    • call:Call

    For more information, see Creating new required data sources for NexJ Contact version 6.1.

  8. If required, you can encrypt previously unencrypted columns in existing tables.
    Note: This functionality is currently available only for the Microsoft SQL Server.

    For more information, see Upgrading column encryption.

  9. Upgrade existing databases.
    The following databases need to be updated:
    • DefaultRelationalDatabase
    • BI_1_BI_Database
    • Conversation
    • ecr:ECR
    • msg:Messaging

    For more information, see Upgrading existing data sources for version 6.1.

    Note: Several columns were moved from frequently used tables in the default relational database to one of the newly created extension tables. This may affect your database upgrade process. For more information, see: Moving columns to extension tables.
  10. Upgrade the application servers.
  11. Deploy the application.
  12. Start the application and verify that it has been successfully deployed.

To ensure that ad hoc reporting is accurate after the upgrade, you need to manually synchronize NexJ Contact with the BI data sources. In NexJ Admin Console, on the Synchronization screen, issue the Send snapshot to the external system command for the BI target.

Warning: A full snapshot synchronization may be resource-intensive and take a long time to complete. Consider scheduling it during a planned down time. Alternatively, you can send snapshots for specific links, if you know which specific tables have new or changed columns.

After completing these steps, you can now run version 6.1 of NexJ Contact.