Loading CEM Web Services in SoapUI 5.0 gives an 'Unexpected element : OPEN_TAG' Exception."

Document ID : KB000004135
Last Modified Date : 19/04/2018
Show Technical Document Details

When trying to load the CA CEM Web Services WSDL URL in a SoapUI 5.0 project, it throws the following exception:

Error loading [http://chear01-e7440:8081/wily/cem/webservices/ConfigurationDataOutService]: org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected element: OPEN_TAG

Below is a snippet of the error stacktrace in the SoapUI error.log file:

org.apache.xmlbeans.XmlException: org.apache.xmlbeans.XmlException: error: Unexpected element: OPEN_TAG

at com.eviware.soapui.support.xml.XmlUtils.createXmlObject(XmlUtils.java:210)
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.readCleanWsdlFrom(WsdlLoader.java:123)
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:101)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:488)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:477)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:94)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:209)
at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:131)
at java.lang.Thread.run(Unknown Source)


Steps to reproduce the issue:

1. Start the Introscope Enterprise Manager.

2. Expose all the CA CEM Web Services in a browser and make sure they have loaded successfully.

3. Open SoapUI 5.0 and create a new SOAP Project

4. Enter the CEM web service WSDL URL and click OK.


5. Observe the following error being thrown: 


NOTE: This problem only affects the CEM Web Services. The Introscope Web Services WSDL URL can be loaded successfully with SoapUI.

SoapUI 5.0
All supported APM releases with CEM.

The error is likely due to certain formatting in the CEM Web Service WSDL failing the SoapUI parse validation.


To work around the issue, save the successfully parsed xml from the browser window as a .xml file, and then open it with SoapUI.

Additional Information:

Although the above steps will address the exception, the user may still encounter problems with CEM Web Services authentication in SoapUI due to how CEM Web Services which uses Form-based authentication.

To overcome this authentication problem, please see https://comm.support.ca.com/kb/how-to-overcome-the-cem-web-services-authentication-problem-in-soapui/kb000037213 for more details.

If using SoapUI is not required, a better alternative to retrieve CEM data would be to write your own Web Service client code. using the CEMExportTool, or  using the CEM UI > Export Data tab.