Quantcast
Channel: PTC Community: Message List - Windchill
Viewing all articles
Browse latest Browse all 8876

Re: Rehost Info*Engine Adapter Setting

$
0
0

Brian,

 

I have managed to get everything related to the corporate LDAP adapter to properly rehost except for the password.  After repeating this process many times (virtual machines with snapshots are wonderful!), I was able to determine several things:

 

  1. ALL adapter properties must be included in the rehost.properties file.  If you leave some out, the rehost tool will mangle them.  Some properties get their values changed and others get truncated.  By listing ALL the properties and values, everything stays intact - even if nothing is changing.
  2. The LDAP adapter's properties are stored in the configuration node of the Windchill Directory Server.  Once you know where they are it's very easy to copy and paste them from production to test and also to copy these same lines to the rehost.properties file.
  3. The corporate LDAP connector's password is stored in the Windchill "mapcredentials.admin.adapters" property, not in Windchill DS.  The rehost tool resets this password to the same one entered for the administrative and enterprise LDAP adapters.  At this point I have not been able to figure out how to get the rehost tool to accept a different password for the corporate LDAP adapter. (I have a case open with PTC on this.)  My current solution for now is to recreate the property from a Windchill shell after rehosting prior to startup.  Below is the syntax I use for this.

 

xconfmanager -s "mapcredentials.admin.adapters=com.tm.Ldap^cn=Manager^password_goes_here"
xconfmanager --add "mapcredentials.admin.adapters=com.tm.EnterpriseLdap^cn=Manager^password_goes_here"
xconfmanager --add "mapcredentials.admin.adapters=com.tm.ActiveDirectory^cn=Windchill,ou=Users,dc=tm,dc=com^password_goes_here"
xconfmanager -p

Viewing all articles
Browse latest Browse all 8876

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>