000035119 - During migration from RSA Identity Governance and Lifecycle 6.9.1x to 7.0.1  the workflow node loses its configuration

Document created by RSA Customer Support Employee on May 9, 2017
Version 1Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000035119
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: 7.0.1
 
Issue
  • Queries on SQL Select nodes are empty
  • Node images are from an old development tool
User-added image

  • Decision Nodes have no configuration under status or process
            User-added image
Using the Browser Development tool (F12) shows the following stack in the Console option:
app.js:1 Uncaught TypeError: Cannot read property 'symbols' of undefined
at ak.onRecordLoaded (app.js:1)
at ak.notify (app.js:1)
at ak.react (app.js:1)
at ak.notify (app.js:1)
at ak.onTick (app.js:1)
at app.js:1
at app.js:1

During migration a new system node was created as a general node but no System Operating Node (SON) is active.  Go to Admin > System > Server Nodes tab and a similar configuration should be displayed.
      User-added image
CauseThere is no active SON and workflow configuration scripts cannot be updated without an active SON.
This issue may happen on either an in place upgrade or when a database is exported from a system on 6.9.1 or earlier to another system on 7.0.0 or later.
ResolutionPromote the new system to a SON using the following steps:
  1. Go to Admin > System > Server Nodes.
  2. Click on Make next SON button next to the new system name.
  3. Restart the application          
$ acm restart

  1. On restart, the workflow should be upgraded properly and workflow node display configuration options are as expected.
  2. The aveksaServer.log should contain the following message:
[com.aveksa.server.workflow.WorkflowServiceProvider] Importing workflow archive ACMWorkflow.zip....

  1. Once the application is restarted, Go to Admin > System > Server Nodes tab.
  2. Remove the invalid original node by clicking on the Delete button.
Workaround    

Attachments

    Outcomes