Error in logs while running ETL for RTC & RI
Hi,
In our environment, we are setting up an integration between Rational Insight 1.0.1.1 and RTC 3.0.1. We have done the necessary configurations as per the link below: http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.rational.rcpr.help.doc%2Ftopics%2Ft_postinstall_upgrade_rrdi_ri.html While we run the ETL Jobs its says the job succeeded but no data is loaded. Also, we get the below error in the logs: 11/17/2011 16:50:30,984 INFO com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : CRRRE1219I: Initial URL Request => https://vianmaru.in.ibm.com:9443/jts/rpt/repository/foundation?size=100&jts=true&fields=foundation%2Fcontributor%2F%28%40href%7CuserId%7CuniqueId%7CemailAddress%7CcontextId%7Cmodified%7CitemId%7Cname%7Carchived%29&modifiedsince=2011-11-16T00:00:00.000%2B0530 11/17/2011 16:50:34,421 ERROR com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : org.xml.sax.SAXParseException: The reference to entity "etag" must end with the ';' delimiter. 11/17/2011 16:50:34,421 ERROR com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread : com.ibm.rational.etl.common.exception.ETLException: org.xml.sax.SAXParseException: The reference to entity "etag" must end with the ';' delimiter. com.ibm.rational.etl.common.exception.ETLException: com.ibm.rational.etl.common.exception.ETLException: org.xml.sax.SAXParseException: The reference to entity "etag" must end with the ';' delimiter. at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.exeFetch(PageFetcherThread.java:522) at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.run(PageFetcherThread.java:131) Caused by: com.ibm.rational.etl.common.exception.ETLException: org.xml.sax.SAXParseException: The reference to entity "etag" must end with the ';' delimiter. at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.exeFetch(PageFetcherThread.java:472) ... 1 more Caused by: org.xml.sax.SAXParseException: The reference to entity "etag" must end with the ';' delimiter. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at com.ibm.rational.drivers.jdbc.xml.internal.PageFetcherThread.exeFetch(PageFetcherThread.java:440) ... 1 more When I try posting the URL request sent by RI to RTC in a broweser, it runs fine and gives the right data as given below: ---------------------------------------------------- <foundation> <contributor> <userId>vijay</userId> <uniqueId>7bbe45f7f142d3a11bcdf9e63f314e9b</uniqueId> <emailAddress>vijay@demo.com</emailAddress> <contextId>_8lNyYNwSEd2pIJ5QVwgQGg</contextId> <modified>2011-11-22T15:32:19.640+0530</modified> <itemId>_gvPLOga4EeGQwcTpRyVYbg</itemId> <name>vijay</name> <archived>false</archived> </contributor> <contributor> <userId>admin_user</userId> <uniqueId>df71e353fcd6ce8970498493c15ad9a4</uniqueId> <emailAddress>admin_user@in.ibm.com</emailAddress> <contextId>_8lNyYNwSEd2pIJ5QVwgQGg</contextId> <modified>2011-11-16T16:42:52.041+0530</modified> <itemId>_6_C26xBDEeGbc5G_2Y7IfQ</itemId> <name>admin_user</name> <archived>false</archived> </contributor> </foundation> Please help in resolving this issue. Regards Vinay |
7 answers
What authentication type are you using, you can open the jts301.xdc file through XDC tool. And from the error message, it means Insight get the invalid XML data from the JTS server.
Hi, |
|
We tried both Basic and Form at both ends (RTC& RI) and behavior was the same. Is there any settings that need to be followed on the RTC server is you say that this issue from RTC side. Thanks!!
What authentication type are you using, you can open the jts301.xdc file through XDC tool. And from the error message, it means Insight get the invalid XML data from the JTS server. Hi, |
I ran into almost this same issue last week with RQM - the link returned just fine from RQM but was getting parsing errors from the Insight ETL.
My problem was the authentication type in my XDC file was incorrect, and this was masking a bad password as well. I suggest double checking both of these. |
|
Hi Jackie, Great to know you were able to resolve this issue. What should be the recommended authentication type? We tried with Basic at both ends (RTC Server & RI in XDCs). Thanks!!
I ran into almost this same issue last week with RQM - the link returned just fine from RQM but was getting parsing errors from the Insight ETL. |
|
We used Form based authentication. I see that isn't clearly documented in the setup steps here: https://jazz.net/help-dev/clm/index.jsp?topic=%2Fcom.ibm.rational.rcpr.help.doc%2Ftopics%2Ft_clm301_xdc_odbc.html
We found an odd behavior with my issue last week where if I had the wrong Authentication type (Basic) and the wrong password, when I clicked "Test Connection" it would give a false positive that the connection succeeded even though it really didn't. Using Form authentication would correctly show that the password is wrong. |
|
Ah... I see. You know what when we do Test Connection with Form as authentication type, we get the message "The resource cannot be accessed." Not sure why. Let me try with form again though. Thanks!!
|
This is just a warning. The connection succeeded, but it could not get a
resource as the base url does not point to a resource. There is really no reason to change the authentication at all after you download the files from the CLM server. Type, username, password are all filled on based on your server set-up. The XDC Editor should only be used to define customization, but not for set-up anymore. RRDI does not even ship with it as we provide all the config options in the jazz admin UI. Hope this helps, Peter. On 11/29/2011 7:23 AM, avvinaykumar wrote: Ah... I see. You know what when we do Test Connection with Form as |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.