Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
In Reply to Ben Bailey:
Hi All,
While, loading PDMLink 9.1 on Windows Server 2003 R2, I entered the fully
qualified DNS hostname incorrectly. A call to Tech Support had me use
xconfmanager to adjust the value of java.rmi.server.hostname. That fixed
the problem of not being able to see the sever remotely, but it looks like
problems still exist with the local LDAP server. I can't create new
users. I get some sort of LDAP error.
Any hope of fixing this? If not, what's the best method for blowing away
a PDMLink install? This is a sandbox, so nothing vital will be lost. Just
my pride...
Ben
In Reply to Rajesh Balasundaram:
The ant command is
ant -f webAppConfig.xml regenAllWebApps
That is good to know however that can't be the whole story. Without changing some configuration file(s) first, running this ant command isn't going to change anything. So the question is: What configuration file(s) need to be changed and what is the format needed to change these files? It is also not obvious to the illiterate ant user (like me) where the webAppConfig.xml file resides. I see at least one of them under the WC_INSTALL_DIR/Apache/ directory. I see the procedure using ant as this:
1. change configuration file(s) that are used by ant
2. run "ant -f webAppConfig.xml regenAllWebApps"
3. restart Windchill, Apache, Tomcat
Step 1 involves lots of time figuring out what actually needs to be done. Or you could just make a 3 second change to Apache's config files. I am assuming that if you actually figure out how to do this changing the "ant" way then the changes would survive a Windchill upgrade. Which would give a lot of points to doing it the ant way.
Best Regards
Rajesh Balasundaram