Maximo Open Forum

Hello,
In this "beta" version the cloning of the TECHMOBILE mobile application does not work for me. 
This is the part of the log that explains the problem:

Caused by: org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.
    at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) ~[xercesImpl.jar:?]
    at org.apache.xerces.jaxp.
DocumentBuilderImpl.parse(Unknown Source) ~[xercesImpl.jar:?]
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:122) ~[?:?]
    at com.ibm.iot.maximo.GraphiteAppService.updateAppXML(GraphiteAppService.java:573) ~[businessobjects.jar:?]
    at com.ibm.iot.maximo.GraphiteAppService.cloneApp(GraphiteAppService.java:501) ~[businessobjects.jar:?]

I know that we are talking about a non-stable release, but have you by any chance already encountered the problem and maybe solved it? 
I have an idea why, is there a way to report it to the labs?

On the 9.1 feature channel, we do allow customers to submit support tickets. The caveat is that it must be a Sev 3 or lower case. 

I wasn't aware we had published a 9.1 version of the config tool. Are you trying to utilize the older 9.0 versions? The reason I ask is we have large updates to the core platform (Maximo Application Framework). Without the updated version of the libraries, you are likely going to see a series of issues on 9.1. The version of the config tool is tightly dependent on the version in Maximo.

In 9.1, one of our major plans (normal roadmap disclaimers apply) is to enable the config tool in the MAS OpenShift cluster. This is to ensure customers use the correct version of the image and eliminate the need for developers to run the images locally on their machine. This work is not yet completed though so is not available in the feature releases yet. 

Yes, we are using the very latest version of maf-tools, but it is still at version 9.0.x.
Thank you very much for the information about the upcoming v9.1; since there are such deep changes, I think it makes little sense to open a ticket rather than wait for the release of the new maf-tools.
In the meantime, we'll try to work around these kinds of problems.