Topic
3 replies Latest Post - ‏2014-06-09T23:48:35Z by simagawa
SimonConnock
SimonConnock
2 Posts
ACCEPTED ANSWER

Pinned topic RM Components after upgrade

‏2014-05-28T08:32:25Z |

We've just upgraded our rather old Records Manager 4.5 environment to IER 5.1.2 (running on P8 5.2). The upgrade procedure (I think) leaves the RM components (RM_Operations and RM_Workflow_Util) under the control of the legacy Component Manager (pretty much as it was in RM 4.5).

Is it worth converting these to the new integrated Component Manager (so they are processes by the CM running as part of the Content Plafform Engine)? Is there a documented procedure to do this?

We still use the IER Web Application but will shortly be installing Content Navigator/Case Manager so could take advantage of the new IER Navigator plug-in. Be nice to have everything under the control of the integrated CM.

  • simagawa
    simagawa
    4 Posts
    ACCEPTED ANSWER

    Re: RM Components after upgrade

    ‏2014-06-04T20:29:38Z  in response to SimonConnock
    Migration of Component Manager from version 1 to version 2 is not required when running IER 5.1.2 and CPE (P8) 5.2.  Both pieces of software will run with either verion of Component Manager.
     
    If, after having upgraded PE to 5.2, you wish to migrate to Component Manager version 2, you can follow the steps documented here:
     

    Hope this helps.

    • SimonConnock
      SimonConnock
      2 Posts
      ACCEPTED ANSWER

      Re: RM Components after upgrade

      ‏2014-06-05T07:30:25Z  in response to simagawa

      Thanks for the response. Understand its not required however in the medium term we will probably migrate all our component queues to the integrated CM so it would be good to get these RM guys in there too.

      I'm aware of the link specified above (and have successfully performed that process on some of our custom Java component queues) however I think the RM components appear to be a special case in that their adapter type is not "Java" but rather "RM Adapter" (in the legacy queues).

      We have another environment where we performed a new install of IER (rather than an upgrade) along with Content Navigator and the IER plug-in and there the RM Component queues do use the integrated CM (and work fine). In that environemnt the Adapter type is "RM Component".

      Doesn't seem to be an obvious mechanism to turn the legacy "RM Adapter" queues into integrated "RM Component" ones.

      Updated on 2014-06-05T09:19:32Z at 2014-06-05T09:19:32Z by SimonConnock
      • simagawa
        simagawa
        4 Posts
        ACCEPTED ANSWER

        Re: RM Components after upgrade

        ‏2014-06-09T23:48:35Z  in response to SimonConnock
        If you have migrated a legacy workflow system to the current version of the workflow system by associating the connection point with an object store, you can run the Configure Workflows task from IER Configuration Manager to reconfigure RM Components queues from the adapter type "RM Adapter" to use the adapter type "RM Component" for the new version of component manager.  You need to check the box to Reconfigure existing workflow component queue in the Configuration Workflows.
         
        If your legacy workflow system and connection point is not associate with an object store, you can reconfigure the RM Component queues from "RM Adapter" to use the adapter type "RM Component" manually.  The steps require you to create a code module for the required jar files and re-import the configuration XML file.  We can provide this manual procedure if necessary.