1 ACCEPTED SOLUTION
Accepted Solutions
Hi Shussaini,
Your reply was helpful, I asked my sys admin to look closely at the certificates and he did find a missing intermediate certificate on the HTTP server side as well as in the java trust store. It helped with some of the errors, the remaining errors were pointing to the WINDCHILL_URL, USERNAME and ContextOID. These Jasper Parameters need to be configured specifically to your system and since the PTC Documentation does not clarify much of this, I will do my best to describe the steps so future users don't waste precious time trying to figure this out. Windchill 12.0.2.1 & Jasper Studio 6.20.5 Community edition.
On the Input Parameters GUI in your Jasper Report, follow these guidelines.
- For the WINDCHILL_URL it must be the FQDN of your server + the path to the ReportServlet, in my case it is https:
https://plm.yourcompany.com/Windchill/servlet/ReportServlet
Article - CS366437 - When authoring Jasper Report using Report Task, what should be the value of WINDCHILL_URL parameter in Windchill 12 (ptc.com) - For the USERNAME it must be the same as the one entered in the auth.properties file, this is the same credentials used for CAD-workers if they are used. Simply type the username in the Jasper Parameter field and the auth.properties will do the rest. eg. orgadmin.
- ContextOID: This is the specific OID of the object you expect to preview in your report. My object is a change notice (change order) with a number ECO22-0400 so when you are on the details page you will find its OID lurking in the URL.
eg. https://plm.yourcompany.com/Windchill/app/#ptc1/tcomp/infoPage?oid=VR%3Awt.change2.WTChangeOrder2%3A12454440&u8=1
Keep the text in red after the OID= and also keep the URL formatted special characters %3A shown twice in this example. Paste it in the ContextOID field of the Jasper Input Parameter GUI. - If you have a LOCALE it is most commonly English US, so the value of that is en_US (I believe it is case sensitive)
- If you have isDraft among your input parameters, I put YES, I think you can put NO, just don't leave it empty (Null).
Special note for item #1 on the list. My tests are done from my PC where I am a trusted admin of our PLM(s), in order for you to be able to connect to the Windchill server, Windchill must first TRUST your PC using its IP address (or FQDN). to do this you have to add your IP to the wt.auth.trustedHosts property.
<Property name="wt.auth.trustedHosts" overridable="true"
targetFile="codebase/wt.properties"
value="<Your CAD Worker FQDN><Your PCs IP>"/> (separating the values with a comma worked for me)
https://www.ptc.com/en/support/article/CS182327?source=search (information of property wt.auth.trustedHosts)
https://www.ptc.com/en/support/article/CS94147?source=search (How to use xconfmanager to change the Windchill property files in Windchill)
Enjoy Reporting
Ian Blackie
Hi Shussaini,
Your reply was helpful, I asked my sys admin to look closely at the certificates and he did find a missing intermediate certificate on the HTTP server side as well as in the java trust store. It helped with some of the errors, the remaining errors were pointing to the WINDCHILL_URL, USERNAME and ContextOID. These Jasper Parameters need to be configured specifically to your system and since the PTC Documentation does not clarify much of this, I will do my best to describe the steps so future users don't waste precious time trying to figure this out. Windchill 12.0.2.1 & Jasper Studio 6.20.5 Community edition.
On the Input Parameters GUI in your Jasper Report, follow these guidelines.
- For the WINDCHILL_URL it must be the FQDN of your server + the path to the ReportServlet, in my case it is https:
https://plm.yourcompany.com/Windchill/servlet/ReportServlet
Article - CS366437 - When authoring Jasper Report using Report Task, what should be the value of WINDCHILL_URL parameter in Windchill 12 (ptc.com) - For the USERNAME it must be the same as the one entered in the auth.properties file, this is the same credentials used for CAD-workers if they are used. Simply type the username in the Jasper Parameter field and the auth.properties will do the rest. eg. orgadmin.
- ContextOID: This is the specific OID of the object you expect to preview in your report. My object is a change notice (change order) with a number ECO22-0400 so when you are on the details page you will find its OID lurking in the URL.
eg. https://plm.yourcompany.com/Windchill/app/#ptc1/tcomp/infoPage?oid=VR%3Awt.change2.WTChangeOrder2%3A12454440&u8=1
Keep the text in red after the OID= and also keep the URL formatted special characters %3A shown twice in this example. Paste it in the ContextOID field of the Jasper Input Parameter GUI. - If you have a LOCALE it is most commonly English US, so the value of that is en_US (I believe it is case sensitive)
- If you have isDraft among your input parameters, I put YES, I think you can put NO, just don't leave it empty (Null).
Special note for item #1 on the list. My tests are done from my PC where I am a trusted admin of our PLM(s), in order for you to be able to connect to the Windchill server, Windchill must first TRUST your PC using its IP address (or FQDN). to do this you have to add your IP to the wt.auth.trustedHosts property.
<Property name="wt.auth.trustedHosts" overridable="true"
targetFile="codebase/wt.properties"
value="<Your CAD Worker FQDN><Your PCs IP>"/> (separating the values with a comma worked for me)
https://www.ptc.com/en/support/article/CS182327?source=search (information of property wt.auth.trustedHosts)
https://www.ptc.com/en/support/article/CS94147?source=search (How to use xconfmanager to change the Windchill property files in Windchill)
Enjoy Reporting
Ian Blackie
