000027962 - KB-1410 Metadata Export/Import does not work properly on 4.0

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027962
Applies ToAffected Versions: 4.0
Issue

When exporting Metadata using Aveksa Compliance Manager 4.0, some data is exported but NOT certain required SQL queries. Without the necessary SQL queries, the resultant .xml file is not complete. This means that this file is not able to be used to 'import' the metadata into another ACM environment (of the same ACM version). Note that exporting/importing Metadata between different ACM versions is not supported. No errors are reported during either the Export or Import of the Metadata.


ResolutionThis is a known problem in version 4.0. It is noted as fixed in version 4.0.1 and higher.
Workaround

There is a workaround for this problem, when running ACM V4.0. The workaround is to copy the 'hibernate-mapping-3.0.dtd' file from the 'jboss/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/classes' directory to the 'jboss/server/default/deploy/aveksa.ear' directory.


 


An example is shown below:


 


 


$ cd /home/oracle/jboss/server/default/deploy/aveksa.ear/aveksa.war/WEB-INF/classes


$ cp hibernate-mapping-3.0.dtd /home/oracle/jboss/server/default/deploy/aveksa.ear/hibernate-mapping-3.0.dtd


 


Note that the ACM Jboss Server will need to be restarted for the workaround to take affect. (An example of this, when logged into the applicance as the oracle user, is shown below).


 


$ sudo service aveksa_server stop


$ sudo service aveksa_server start


 


alternatively, the stop/start can be issued as one command:


 


$ sudo service aveksa_server restart

Attachments

    Outcomes