A management module does not load after moving a JAR file from one EM to another with a different release.

Document ID : KB000006490
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

 After moving a Management Module .JAR from one Introscope version to another with a different release, the following error shows in the logs and the Management Module does not load:

[ERROR] [PO Async Executor] [Manager] XML Problem while parsing at line 2 and column 394: schema_reference.4: Failed to read schema document 'bundle://com.wily.introscope.em/com/wily/introscope/server/enterprise/entity/bundle/IntroscopeManagementModules4.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.

6/27/16 05:24:38.808 PM BRT [ERROR] [PO Async Executor] [Manager.Bootstrap] XML problem while parsing /CA/Introscope/9.5.0.0/MOM/deploy/weblogic11.jar

Environment:
APM Introscope from 9.x to 10x
Cause:

  The error messages are due to the Management Module XML Schema Definition (xsd) having changed between the releases it was built. e.g.

 The dashboards created in 9.1x use or reference IntroscopeManagementModules2.0.xsd. But the ones created in 9.5x use IntroscopeManagementModules3.0.xsd.

Resolution:

The best option here would be rebuilding these Management Modules in the current release.

  -Upgrade your Introscope to match with your Management build, Eg: Upgrade your Introscope to use the .JAR build in newer release. It will match the Management Module XML Schema Definition (xsd).

 

-   In the management Module XML for the 9.1.x EM, you will find this line mentioning XSD:

  <ManagementModule xmlns:introscope="generated://introscope.xsd" xmlns:ns1="http://www.w3.org/2005/11/its" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" DescriptionContentType="text/plain" Editable="true" IsActive="true" Version="2.0" xsi:noNamespaceSchemaLocation="bundle://com.wily.introscope.em/com/wily/introscope/server/enterprise/entity/bundle/IntroscopeManagementModules3.0.xsd">

 

 You can try to change the highlighted text to another version if you desire.  In this example you would change the version to 3.0.

Additional Information:

However, doing this is not tested or supported and may very well lead to subsequent additional errors for which Support can only provide limited assistance.

 For further assistance, contact CA Support.

 In summary, the Management Modules are not backward compatible to an earlier APM version.