SecureBridge Agent Manager Migration Utility

If you are a licensed user of SecureBridge and you are upgrading to AC v3.4, you need to use SecureBridge Agent Manager Migration Utility to be able to make the older version of the SecureBridge compatible with that in AC v3.4.

It is recommended that you take backup of all configuration files before running this utility.

Follow the steps below to run the migration utility:

  1. Open Command Prompt (Windows) or Terminal (Linux).
  2. Go to the directory ...<AdeptiaInstallFolder>/ AdeptiaServer/ServerKernel folder.
  3. Run the following command:

    For Windows:
    migrationutility.bat –agentmanagermigration <path of the build directory of Connect Server> skipLogTables=false

    For Linux:
    ./migrationutility.sh –agentmanagermigration <path of the build directory of Connect Server> skipLogTables=false

    In case you want to migrate the log tables, set the value of skipLogTables to true. By default, the value is set to false.
  4. After successful migration, it displays a message on console saying Successfully completed the Agent Manager migration.

  5. In case of any error while migrating the Agent Manager, it displays an error message, Error while migrating the Agent Manager, on the console. For more details, check the log file agentmanagermigration.log generated at ...<AdeptiaInstallFolder>/ AdeptiaServer/ServerKernel location.

Post migration changes in SecureBridge

The utility brings the following changes into effect. 

Database table related changes

The data from the older tables is migrated to the corresponding new tables in the log and backend database.  

Old tableNew table
Backend database
agentInfoAC_AGENT_INFO
Log database
agentactionAC_AGENT_ACTION
agentdiagnosticsAC_AGENT_DIAGNOSTICS
transactionlogAC_TRANSACTION_LOG

Configuration related changes

The utility overwrites the default values for the properties under the Agent Manager Hub section in server-configure.properties file with the older properties' values defined in hubConfiguration.properties file.

The table below contains the updated property names in the server-configure.properties file corresponding to the ones in older hubConfiguration.properties file.

Old configuration property (hubConfiguration.properties)

New configuration property (server-configure.properties)

enableEmailNotificationabpm.services.agentmanager.emailNotification.enabled
maxMissHeartbeatTimeInSecabpm.services.agentmanager.maxMissHeartbeatTimeInSec
notificationIntervalInSecabpm.services.agentmanager.notificationIntervalInSec
recipientsEmailabpm.services.agentmanager.recipientsEmail
mailSubjectabpm.services.agentmanager.mailNotificationSubject
mailBodyContentTypeabpm.services.agentmanager.mailBodyContentType
mailBodyHeaderabpm.services.agentmanager.mailBodyHeader
mailBodyHeaderDownabpm.services.agentmanager.mailBodyHeaderDown
mailBodyHeaderUpabpm.services.agentmanager.mailBodyHeaderUp
mailBodyFooterabpm.services.agentmanager.mailBodyFooter
ignoredTransactionIdabpm.services.agentmanager.ignoredTransactionId
saveAgentDiagnosticsInfoabpm.services.agentmanager.saveAgentDiagnosticsInfo
dashbordRefreshTimeInSecabpm.services.agentmanager.dashbordRefreshTimeInSec
postNotificationDataabpm.services.agentmanager.postNotificationData
postNotificationDataUrlabpm.services.agentmanager.postNotificationDataUrl