M Drive problem, LDAP stuff, Installation Areas
- M drive problem appears to be a networking problem at Eric's location
- Condensed Client release areas to one release area
- Attempted to access LDAP through Perl
M drive problem appears to be a networking problem at Eric's location
Today Eric sent over somebody to install and setup Weblogic on my desktop in an attempt to reproduce the problem with Jbuilder writing to the M drive. After much installation, setup and configuration the problem was not reproducable. IOW it worked like a champ from my desktop.
During the installation we copied over the VIP sources instead of using the sources in the vob and we got these from Eric's desktop. It took a very long time leading me to further believe that there are networking problems either on Eric's desktop or somewhere between his desktop and the servers.
Condensed Client release areas to one release area
On //rtnlprod03/CC_REL_2003.6 there exists the following client release areas:
- Training-client
- asap-tavant-client
- resolve-client
- asap-integration-client
- eag-client
- scc-client
- asap-qa-client
- pmo-client
- vip-client
and a server area:
- pmo-server
TUP exists at //rtnlprod03/sqldb/TUP and XDE-Java at //rtnlprod03/sqldb/XDE-Java.
The Clearcase client and server installation areas have all been condensed to one Server and one Client installation area (//rtnlprod03/CC_REL_2003.6/Server and Client). Instead we now have .reg file that set the uniquely different configuration settings for the various groups in the CM_TOOLS vob under etc with names like ASAP.reg, SCC.reg, EAG-ESB.reg. After a client install we will send a link to these files that will cause the settings to be installed on their desktop.
Currently the various client reg files have only the setting of Region, RegBackup and CLEARCASE_PRIMARY_GROUP.
Attempted to access LDAP through Perl
I installed Perl modules to deal with LDAP in the hopes of being able to set up a web page that will list out the membership of the various CC groups from Active Directory. Trouble is I do not know the server name of Active Directory nor the distinguished name to use in order to access this data.