Moving the active-drive

In order to move the active-drive from one location to another(or change the default directory of active-drive), you need to follow the instructions listed below:

Initial steps:
    • Request all users to save their work and log out of EngageOne™ Interactive.
    • Stop all traffic to EngageOne™ SOAP services.
    • Run EngageOne™ Server purge process. If there are more communities present, all of them need to be purged. Just to be clear - it is not absolutely necessary to run purge, but we recommend it in order to reduce the number of rows that need to be modified. There is no need to run Event Monitor purge process.
    • Stop all EO services on all nodes.
    • Create backup of both DB and active-drive.
  2. Copy the active-drive and its contents from old location to new location.
  3. Update deploy.properties file, providing new path for active-drive (active.drive.dir). The file can be found in folder <release-medium>\install.
  4. If you use the active-drive location for any other property (e.g. tls.trust.store.location, tls.key.store.location, eodeliver.share.dir) and you plan to use the new location, you have to update values of those properties before you proceed.

  5. Open the New query tab and run stored procedure usp_u_move_active_drive.

    Example for MS SQL Server:

    exec usp_u_move_active_drive @iv_OLD_ACTIVE_DRIVE_PATH = 
'<existing_active_drive_path>',@iv_NEW_ACTIVE_DRIVE_PATH = 
'<new_active_drive_path>';

    Example for Oracle:

    set serveroutput on;exec usp_u_move_active_drive ('<existing_active_drive_path>', 
'<new_active_drive_path>');

    Before any attempt to execute the procedure, both <existing_active_drive_path> and <new_active_drive_path> have to be replaced with correct paths. After the procedure is successfully executed, something similar to the example below should appear on the console:

    2324 rows have been updated in column Physical_Path in table Doc_Storage_Locations
19980 rows have been updated in column AnswerFilePath in table TDS_RequestChannels
19980 rows have been updated in column PrintFilePath in table TDS_RequestChannels
19980 rows have been updated in column MetricsFilePath in table TDS_RequestChannels
4 rows have been updated in column MessageText in table TDS_RequestChannels
29970 rows have been updated in column ParameterValue in table TDS_RequestParameters

    The numbers can be different, but 6 lines are expected as in the example above. Four of them are related to the TDS_RequestChannels table, the remaining two to Doc_Storage_Locations and TDS_RequestParameters.

  6. Run eos.groovy installation script in order to re-configure all batch, composition, conversion and core bundles present in the environment:

    groovy eos.groovy -b <batch|composition|conversion|core> -p <deploy.properties path> 
-t <single|primary|replica> configure

    IMPORTANT – the script has to be executed against all specified bundles on all nodes. There is no need to re-configure the security and notification bundles (assuming that notification bundle is installed).

  7. Start all EO services and perform all the sanity checks as usual.

    IMPORTANT – it may be necessary to modify the configuration manually (in the EngageOne™ Administration Admin application) if any delivery channel present in the environment is configured in a way that either output or journal files are created within old active-drive structure.