Skip to main content
Kofax

Trigger Mappings are not restored with Management Console backup

Article # 3049755 - Page views: 19

Issue

Trigger Mappings are not restored with Management Console backup.

 

Cause

Management Console backup files created in versions 10.3.0.0 - 10.3.0.9 do not include trigger mapping data.

This issue was fixed in version 10.3.0.10

 

Solution

For the affected version use the following workaround to create a backup that will contain all correct data.

For the enterprise Management Console (i.e. deployed into Tomcat)

This procedure restores trigger mappings and applies to the Management Console deployed on Tomcat that contains attended robots with trigger mappings.

  1.     Stop Tomcat and back up your database before continuing.
  2.     Before installing the new (e.g.11.2.0) .war file, open it and modify the version.properties file, which resides in WEB-INF\classes, to match the version you are upgrading from.
       For example, if you are upgrading from 10.3.0.5, the text in the file must be: fullVersion=10.3.0.5 266
  3.     Install the updated ManagementConsole.war file on Tomcat. It will start a Management Console of new version (e.g. 11.2.0) with the old database.
  4.     Create a backup to contain all data including the trigger mappings.
  5.     Install a new (e.g.11.2.0) Management Console with an empty database (without changes to the .war file).
  6.     Restore the backup created in Step 4.
For the development Management Console (i.e. embedded Management Console)

This procedure restores trigger mappings and applies to the embedded Management Console that contains attended robots with trigger mappings.

  1.    Stop the original Management Console and back up the folder:
        C:\<username>\AppData\Local\Kapow\10.3.0.x_<build number>
        to
        C:\<username>\AppData\Local\Kapow\10.3.0.x_<build number>_original
  2.     Install the new version of Kofax RPA (e.g.11.2.0) and do not start the Management Console.
  3.     Open the ManagementConsole.war file, which resides in <program folder>\RPA <version numer> <build number>\WebApps, and modify the version.properties file, which resides in WEB-INF\classes, to match the version you are upgrading from.
        For example, if you are upgrading from 10.3.0.5, the text in the version.properties file must be: fullVersion=10.3.0.5 266
  4.     Delete all files from:
        C:\Users\<username>\AppData\Local\Kapow\10.3.0.x_<build number>\Temp
  5.     Add the updated ManagementConsole.war file to the original version to:
        <program folder>\Kapow 10.3.0.x <build number>\WebApps\
  6.     Start the Management Console original version. It will start a Management Console with the old database.
  7.     Create a backup to contain all data including the trigger mappings.
  8.     Install a new (e.g. 11.2.0) Management Console with an empty database (without changes to the .war file).
  9.     Restore the backup created in Step 7.

Level of Complexity 

Moderate

 

Applies to  

Product Version Build Environment Hardware
RPA 10.3 and later      

References

Add any references to other internal or external articles

 

 

Article # 3049755
  • Was this article helpful?