Disabling and Re-Enabling LDAP features

Use these instructions as an addendum to IBM infocenter documentation for enabling / disabling and re-enabling LDAP feature in WCS

Toolkit Scenario #1

#1 You have enabled LDAP feature by using enablementscript "–DfeatureName=ldap"
#2 You would like to now disable LDAP feature


1. Modify WCDE_ENT70\workspace\WC\xml\config\wc-server.xml in the MemberSubSystem element :
Change to
<MemberSubSystem
AuthenticationMode="DB" ProfileDataStorage="DB" ... And then restart
here is a snippet of configuration for LDAP and Database, comment out the section accordingly and restart Toolkit instance




2.  You need to now modify the Database account UID formats if you previously used it to login against LDAP.

update USERREG.LOGONID values to short format where LOGONID like 'uid=%'

Toolkit Scenario #2

(a) Find the following two lines in                                  
components/common/xml/enableFeatureForToolkit.xml and markup (comment
out) the unless attributes. comment out is like <!-- AAAA -->        
                                                                     
    <target name="enableFeatureFDG" depends="getWASAdminUserPassword,
CheckPrereqInDBEAR" unless="isFullyEnabledInDBEAR${featureName}">    
    <target name="featureEnablementInToolkitWorkspace"                
depends="CheckPrereqInEAR" unless="isFeatureEnabledInEAR${featureName}">
                                                                     
(b) Find the following section and mark up the if-then check          
    <target name="featureEnablementInServer" >                        
         <if>                                                        
                <equals arg1="${enablementStatusInAppServer}"        
arg2="false"/>                                                        
         <then>     Here is a snippet of modified section of components/common/xml/enableFeatureForToolkit.xml                                                  

                                                                   
3. rerun the enable feature command.

Server Scenario #1