Community Tip - You can change your system assigned username to something more personal in your community settings. X
Hi,
My company recently upgraded to Windchill 10.0 from Windchill 9.1
Previous, we are able to quickly bring up a document if we knew it's number by doing opening the following URL:
http://yyyyy.com/Windchill/netmarkets/jsp/cochlear/DocByBasisRef.jsp?basisref=123456
The "BasisRef" variable was a customisation, so they documents could retain their legacy database reference.
Is there a way something similar can be done in Windchill 10.0?
I know that each document gets a unique ID, which appears after the WTDocument%3A tag, but I only have the actual number.
http://yyyyycom/Windchill/app/#ptc1/tcomp/infoPage?oid=OR%3Awt.doc.WTDocument%3A209042924&u8=1
Ideally, if there is a way to search with a URL query like this, that would be great:
http://yyyyycom/Windchill/app/#ptc1/tcomp/infoPage?oid=OR%3Awt.doc.WTDocument?number=123456
Thanks in advance!
Dear Wilson,
This is probably a JSP customization that should be compatible with 10.
First you need to copy the jsp from the old system to the new installation
codebase/netmarkets/jsp/.....
then retry this link.
Note that if you are planning to adjust the jsp file, make sure you switch to dev mode on the tomcat and never work directly on a production system.
It may or may not work, depending on the other supporting files you might need. When you try to access it, it should provide you an error that will help you determine other resources you may need to copy.
Best Regards,
Simon
Hi Simon,
2 questions:
Why to switch to dev mode in Tomcat?
How to switch to dev mode in Tomcat?
Thanks,
Ravin
Any JSP page is compiled into Java by the tomcat engine. It decides to do this if there is no java code available in the work area or the date and timestamp of the source file is later than the current available compiled version. However this last check is only relevant if the tomcat is put into dev mode. If you type "tomcat" into the WHC then it gives you the command. As it has a very slight overhead (really nothing) a production system should never be put in dev mode, when we deploy new or updated JSP our install process deletes the tomcat cache for the pages concerned, Deleting the whole work directory is another option but it requires the tomcat engine to recompile all pages that mean a few moments waiting for each page the first time it is used.
Here is the extract from the WHC
Regards,
Simon
Running Tomcat in Development Mode
To change to development mode:
After development is complete, return to normal operation by entering
ant -f config.xml configureJspEngine -Dmode=prod