Media Manager Migration

Update Media Manager

Updating Media Manager File Server

To update the Product 360 - Media Manager File Server, you require the file PIM_<Version>_MediaManager.zip from your Product 360 distribution.

  1. Uncompress the file PIM_<Version>_MediaManager.zip on your computer.

  2. Navigate to the folder \Setup\HMM of the uncompressed archive.

  3. Copy the help%0 and update directories to Volume0 on your file server, to the opasdata directory.

Updating the database

By default Product 360 Server, the Product 360 Media Manager web application and Product 360 Process Engine will perform the database update automatically.

If you have disabled the automatic database update, you have to migrated your database manually. Please refer to Database Migration > Media Manager Database Migration for required update steps.

Migration from versions older than 8.1

If you're migrating from a version older than 8.1, please refer to Database Migration > Media Manager Database Migration for required update steps as well.

Updating the client modules

For hotfix updates client modules are updated automatically on the first start after updating Product 360 - Media Manager. If problems occur the following steps can performed manually.

Changed behavior: For major and minor updates (e.g. from 10.0.0.02 to 10.1.0.0.00) the following steps needs be be executed manually.

Manually updating the client modules (Windows)

  1. Switch to the directory opasdata/update/win/oclnt on your Volume0 (located on Media Manager file server).

  2. Run OPAS_cln.exe.

  3. Follow the subsequent instructions.

Manually updating the client modules (OSX)

  1. Switch to the directory opasdata/update/osx on your Volume0 (located on Media Manager file server).

  2. Mount the image IMM.install.dmg.

  3. Run the included package installer.

  4. Follow the subsequent instructions.

If you are installing new client modules or updating the version, you must re-activate Product 360 - Media Manager. For more details, refer to Activating Product 360 - Media Manager, defining volumes & setting up Funcd.

Updating Funcd

To update the Product 360 - Media Manager Funcd, you require the file PIM_<Version>_ThirdPartySoftware.zip from your Product 360 distribution.

You should always update the Funcd to get the last versions of the third party tools. To update the Funcd and the third party tools proceed as follows:

  1. Uninstall Funcd and the third party tools.

  2. Do the installation like described in Installing Funcd.

Updating web front end

To update the Product 360 - Media Manager web application, you require the file PIM_<Version>_MediaManager.zip from your Product 360 distribution.
The procedure for updating your web front end is as follows:

  1. Uncompress the file PIM_<Version>_MediaManager.zip on your computer.

  2. Stop the Tomcat server.

  3. Make a backup of the web application by renaming e.g. C:\OpasGWebServer to C:\OpasGWebServer_backup.

  4. Navigate to the folder \Setup\webapp package\full of the uncompressed archive.

  5. Unpack the OpasGWebServer.zip to C:\.

  6. Copy and overwrite the configuration files from C:\OpasGWebServer_backup\XOBSessionManager\conf to C:\OpasGWebServer\XOBSessionManager\conf.

  7. Copy and overwrite configuration files from C:\OpasGWebServer_backup\Tomcat\conf to C:\OpasGWebServer\Tomcat\conf.

  8. Delete C:\OpasGWebServer\Tomcat\webapps.

  9. Copy C:\OpasGWebServer_backup\Tomcat\webapps to C:\OpasGWebServer\Tomcat\webapps.

  10. Delete the directory C:\OpasGWebServer\Tomcat\webapps\opas\WEB-INF\lib.

  11. Delete the directory C:\OpasGWebServer\Tomcat\webapps\opas\WEB-INF\classes.

  12. Delete the directory C:\OpasGWebServer\Tomcat\webapps\opas\script.

  13. Navigate to the folder \Setup\webapp package\update of the uncompressed archive.

  14. Unpack opas.zip to C:\OpasGWebServer\Tomcat\webapps\opas and replace existing files.

  15. When you are updating from version < 10.0.0.01 and using MSSQL database you have to apply the following changes in the file C:\OpasGWebServer\Tomcat\webapps\opas\Base.cfg to define the database connection parameters.
    Replace

    <DATABASE_URL>jdbc:jtds:sqlserver://localhost:1433/opasdb</DATABASE_URL>

    with

    <DATABASE_URL>jdbc:sqlserver://localhost:1433;databaseName=opasdb</DATABASE_URL>

  16. Restart the Tomcat server.

Product 360 Media Manager web application will update the Media Manager database to the latest version on the first startup.

If you want to prevent the database update it is necessary to set the property <DB_AutomatedUpdateEnabled> to false in the Base.cfg file

Do copy and not replace the existing opas directory with the archive, because the update package contains only the changed parts of the web front end.

When changing the layout you have to update the layout profiles and re-assign them to the users. You can use the layout distribution in the "Administration" area in the web front end.

Deactivate old modules

The modules: Informatica Media Manager Session Manager, Informatica Media Manager Funcd and Informatica Media Manager Internet are no longer needed for versions >= 8.0. Therefore these services can be deactivated.

Deactivate Session Manager

Open the "Windows Services" and search the service "Informatica Media Manager Session Manger" (Depending on you preinstalled version, the name can differ for example Heiler Media Manager Session Manager). Stop the service if it is running and afterwards set the Startup type to disabled or manual.

Deactivate Internet Funcd

  • If the "Informatica Media Manager Process Watcher" is running as Window service you have to stop this service.

  • Open the Process Watcher module.

  • Stop the automatic mode by clicking cancel.

  • Select Processwatcher > Processwatcher default settings

  • Disable the monitoring of the Inernet funcd in the second pane.

  • Save and close the application.

  • If the "Informatica Media Manager Process Watcher" was running as Window service you have to start this service again.