Fixing an invalid Bind account

We have been going through a bunch of password changes and mistakenly change the password on a account in one environment that broke another environment. One of the things I learned (other then never reuse accounts ! ) was that when the bind account is invalid, even the wasadmin account will not be able to access the console. The environment we were working in was development and needing a fix I tried to edit the profiles\Dmgr01\config\cells\Cell01\wim\config\wimconfig.xml and updated the value for bindPassword and the bind account to a value from another instance .  What made this interesting was the fact that I was able to use a encrypted password from a WebSphere 6.1 environment in a WebSphere 7.0 environment. I was also able to update the bind password value with a clear text copy, allowing me access to the console. After I entered the console I went to
Secure administration, applications, and infrastructure > Federated repositories > repository
 and was then able to re encrypt the password by reentering it in the bind password box, clicking apply and then save.

Understanding Maximo LDAPSYNC

Great technote from IBM on how the LDAPSYNC process syncs with Microsoft Active Directory Global Catalog. When I first started looking into this I was a little confused by the XML in the LDAPSYNC cron task. I was not sure what to add and where to add it but this cleared up much of my confusion.  Interesting points I found were

• LDAPSYNC connects to the Microsoft Global Catalog on port 3268
• LDAPSYNC can be configured to access the LDAP server directly, however; this does not follow Microsoft recommendations
• Maximo administrators can map additional information from the LDAP server to Maximo using the SYNC task.

http://www-304.ibm.com/support/docview.wss?uid=swg21358601

Connecting Maximo to an LDAP instance

Just found this great field guide on setting up Maximo to connect to an LDAP instance.
http://www-304.ibm.com/support/docview.wss?uid=swg27023563