Err while configuring Federated LDAP repository

[vino...@in.ibm.com]

Getting the below error while configuring Federated LDAP :

wp-create-wimconfig-ldap:
Tue Oct 28 13:00:35 EDT 2008
[wplc-create-federated-ldap-repository] Task parameters:
[wplc-create-federated-ldap-repository] Global attributes:
[wplc-create-federated-ldap-repository] cell="node1"
[wplc-create-federated-ldap-repository] engineinstalllocation="C:/IBM/WebSph
ere/wp_profile/ConfigEngine"
[wplc-create-federated-ldap-repository] pathseparator=";"
[wplc-create-federated-ldap-repository] osarch="x86"
[wplc-create-federated-ldap-repository] node=""
[wplc-create-federated-ldap-repository] server=""

[wplc-create-federated-ldap-repository] Instance attributes (Set 1 of 1):
[wplc-create-federated-ldap-repository] ignoreDuplicateIDs="false"
[wplc-create-federated-ldap-repository] ldapServerType="IDS6"
[wplc-create-federated-ldap-repository] attribute=[
[wplc-create-federated-ldap-repository] [ sslConfiguration="" ]
[wplc-create-federated-ldap-repository] [ returnToPrimaryServer="true" ]
[wplc-create-federated-ldap-repository] [ supportExternalName="false" ]
[wplc-create-federated-ldap-repository] [ isExtIdUnique="true" ]
[wplc-create-federated-ldap-repository] [ translateRDN="false" ]
[wplc-create-federated-ldap-repository] [ searchTimeLimit="120000" ]
[wplc-create-federated-ldap-repository] [ supportSorting="false" ]
[wplc-create-federated-ldap-repository] [ searchCountLimit="500" ]
[wplc-create-federated-ldap-repository] [ searchPageSize="" ]
[wplc-create-federated-ldap-repository] [ default="${federated.ldap.default}" ]

[wplc-create-federated-ldap-repository] [ supportTransactions="false" ]
[wplc-create-federated-ldap-repository] [ primaryServerQueryTimeInterval="15" ]

[wplc-create-federated-ldap-repository] [ loginProperties="uid" ]
[wplc-create-federated-ldap-repository] [ supportPaging="false" ], ]
[wplc-create-federated-ldap-repository] customproperty=[ *** NONE_SPECIFIED
[wplc-create-federated-ldap-repository] id="fedldap"
[wplc-create-federated-ldap-repository] com.ibm.websphere.wim.exception.WIMConfi
gurationException: CWWIM5015E Login properties are not valid: [uid].[wplc-create-federated-ldap-repository] at com.ibm.ws.wim.config.ConfigV
alidator.validateLoginProperties(ConfigValidator.java:539)
[wplc-create-federated-ldap-repository] at com.ibm.ws.wim.config.ConfigV
alidator.validateRepositoryParams(ConfigValidator.java:160)
[wplc-create-federated-ldap-repository] at com.ibm.ws.wim.config.LDAPRep
ositoryConfigHelper.createIdMgrLDAPRepository(LDAPRepositoryConfigHelper.java:78
)
[wplc-create-federated-ldap-repository] at com.ibm.ws.wim.config.command
s.LDAPRepositoryConfig.createIdMgrLDAPRepository(LDAPRepositoryConfig.java:61)
[wplc-create-federated-ldap-repository] at com.ibm.ws.wim.config.command
s.IdMgrRepositoryConfigCommandsProvider.createIdMgrLDAPRepository(IdMgrRepositor
yConfigCommandsProvider.java:162)
[wplc-create-federated-ldap-repository] at sun.reflect.NativeMethodAcces
sorImpl.invoke0(Native Method)
[wplc-create-federated-ldap-repository] at sun.reflect.NativeMethodAcces
sorImpl.invoke(NativeMethodAccessorImpl.java:79)
[wplc-create-federated-ldap-repository] at sun.reflect.DelegatingMethodA
ccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[wplc-create-federated-ldap-repository] at java.lang.reflect.Method.invo
ke(Method.java:618)
[wplc-create-federated-ldap-repository] at com.ibm.websphere.management.
cmdframework.provider.SimpleCommandProvider.executeReal(SimpleCommandProvider.ja
va:147)
[wplc-create-federated-ldap-repository] at com.ibm.websphere.management.
cmdframework.provider.SimpleCommandProvider.execute(SimpleCommandProvider.java:1
33)
[wplc-create-federated-ldap-repository] at com.ibm.websphere.management.
cmdframework.provider.SimpleAdminCommand.execute(SimpleAdminCommand.java:57)
[wplc-create-federated-ldap-repository] at com.ibm.ws.management.cmdfram
ework.impl.RemoteCommandMgrImpl.execute(RemoteCommandMgrImpl.java:120)
[wplc-create-federated-ldap-repository] at sun.reflect.NativeMethodAcces
sorImpl.invoke0(Native Method)
[wplc-create-federated-ldap-repository] at sun.reflect.NativeMethodAcces
sorImpl.invoke(NativeMethodAccessorImpl.java:79)
[wplc-create-federated-ldap-repository] at sun.reflect.DelegatingMethodA
ccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[wplc-create-federated-ldap-repository] at java.lang.reflect.Method.invo
ke(Method.java:618)
[wplc-create-federated-ldap-repository] at sun.reflect.misc.Trampoline.i
nvoke(MethodUtil.java:62)
[wplc-create-federated-ldap-repository] at sun.reflect.GeneratedMethodAc
cessor94.invoke(Unknown Source)
[wplc-create-federated-ldap-repository] at sun.reflect.DelegatingMethodA
ccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[wplc-create-federated-ldap-repository] at java.lang.reflect.Method.invo
ke(Method.java:618)
[wplc-create-federated-ldap-repository] at sun.reflect.misc.MethodUtil.i
nvoke(MethodUtil.java:265)
[wplc-create-federated-ldap-repository] at javax.management.modelmbean.R
equiredModelMBean.invokeMethod(RequiredModelMBean.java:1090)
[wplc-create-federated-ldap-repository] at javax.management.modelmbean.R
equiredModelMBean.invoke(RequiredModelMBean.java:971)
[wplc-create-federated-ldap-repository] at com.sun.jmx.mbeanserver.Dynam
icMetaDataImpl.invoke(DynamicMetaDataImpl.java:231)
[wplc-create-federated-ldap-repository] at com.sun.jmx.mbeanserver.MetaD
ataImpl.invoke(MetaDataImpl.java:238)
[wplc-create-federated-ldap-repository] at com.sun.jmx.interceptor.Defau
ltMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833)
[wplc-create-federated-ldap-repository] at com.sun.jmx.mbeanserver.JmxMB
eanServer.invoke(JmxMBeanServer.java:802)
[wplc-create-federated-ldap-repository] at com.ibm.ws.management.AdminSe
rviceImpl$1.run(AdminServiceImpl.java:1081)
[wplc-create-federated-ldap-repository] at com.ibm.ws.security.util.Acce
ssController.doPrivileged(AccessController.java:118)
[wplc-create-federated-ldap-repository] at com.ibm.ws.management.AdminSe
rviceImpl.invoke(AdminServiceImpl.java:974)
[wplc-create-federated-ldap-repository] at com.ibm.ws.management.connect
or.AdminServiceDelegator.invoke(AdminServiceDelegator.java:139)
[wplc-create-federated-ldap-repository] at sun.reflect.GeneratedMethodAc
cessor107.invoke(Unknown Source)
[wplc-create-federated-ldap-repository] at sun.reflect.DelegatingMethodA
ccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[wplc-create-federated-ldap-repository] at java.lang.reflect.Method.invo
ke(Method.java:618)
[wplc-create-federated-ldap-repository] at com.ibm.ws.management.connect
or.soap.SOAPConnector.invoke(SOAPConnector.java:351)
[wplc-create-federated-ldap-repository] at com.ibm.ws.management.connect
or.soap.SOAPConnector.service(SOAPConnector.java:205)
[wplc-create-federated-ldap-repository] at com.ibm.ws.management.connect
or.soap.SOAPConnection.handleRequest(SOAPConnection.java:55)
[wplc-create-federated-ldap-repository] at com.ibm.ws.http.HttpConnectio
n.readAndHandleRequest(HttpConnection.java:680)
[wplc-create-federated-ldap-repository] at com.ibm.ws.http.HttpConnectio
n.run(HttpConnection.java:484)
[wplc-create-federated-ldap-repository] at com.ibm.ws.util.ThreadPool$Wo
rker.run(ThreadPool.java:1473)
[wplc-create-federated-ldap-repository] Create LDAP repository failed.
[wplc-create-federated-ldap-repository] at com.ibm.wplc.deploy.tasks.imp
l.FederatedRepositoryLdapCreateImpl.execute(FederatedRepositoryLdapCreateImpl.ja
va:45)
[wplc-create-federated-ldap-repository] at com.ibm.wplc.deploy.tasks.Abs
tractBaseAdminTask.executeTask(AbstractBaseAdminTask.java:495)
[wplc-create-federated-ldap-repository] at com.ibm.wplc.deploy.tasks.Abs
tractBaseWsAdminWrapperTask.executeTask(AbstractBaseWsAdminWrapperTask.java:265)

[wplc-create-federated-ldap-repository] at com.ibm.wplc.deploy.tasks.Abs
tractBaseAdminTask.execute(AbstractBaseAdminTask.java:156)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.UnknownE
lement.execute(UnknownElement.java:275)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Task.per
form(Task.java:364)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Target.e
xecute(Target.java:341)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Target.p
erformTasks(Target.java:369)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Project.
executeSortedTargets(Project.java:1216)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.helper.S
ingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Project.
executeTargets(Project.java:1068)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.taskdefs
Ant.execute(Ant.java:382)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.taskdefs
CallTarget.execute(CallTarget.java:107)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.UnknownE
lement.execute(UnknownElement.java:275)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Task.per
form(Task.java:364)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Target.e
xecute(Target.java:341)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Target.p
erformTasks(Target.java:369)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Project.
executeSortedTargets(Project.java:1216)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Project.
executeTarget(Project.java:1185)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.helper.D
efaultExecutor.executeTargets(DefaultExecutor.java:40)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Project.
executeTargets(Project.java:1068)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Main.run
Build(Main.java:668)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Main.sta
rtAnt(Main.java:187)
[wplc-create-federated-ldap-repository] at org.apache.tools.ant.Main.sta
rt(Main.java:150)
[wplc-create-federated-ldap-repository] at com.ibm.wps.config.ConfigEngi
ne.process(ConfigEngine.java:828)
[wplc-create-fede...................

Below are the configuration details:

# The id specifies a unique identifier for the repository within the cell
# Characters that are not allowed in normal XML strings ( & " ' ) cannot be used in the repository ID.
federated.ldap.id=fedldap

# Specifies the host name of the primary LDAP server. This host name is either an IP address or a domain name service (DNS) name.
federated.ldap.host=localhost

# Specifies the LDAP server port.
federated.ldap.port=389

# Specifies the distinguished name for the application server to use when binding to the LDAP repository.
federated.ldap.bindDN=uid=wpsbind,cn=users,dc=ibm,dc=com

# Specifies the password for the application server to use when binding to the LDAP repository.
federated.ldap.bindPassword=wpsbind

# Specifies the type of LDAP server to which you connect
# This must be one of the following values: SECUREWAY,IDS4,IDS51,IDS52,IDS6,ZOSDS,DOMINO5,DOMINO6,DOMINO65,DOMINO7,NDS,SUNONE,AD2000,AD2003,ADAM,CUSTOM
federated.ldap.ldapServerType=IDS6

# The LDAP base entry.
federated.ldap.baseDN=dc=ibm,dc=com

[ff...@us.ibm.com]

Post ConfigTrace.log, security.xml, wimconfig.xml, and wkplc.properties here, if you don't mind.

-FF

The postings on this site are my own and do not necessarily represent the positions, strategies or opinions of IBM.

[vino...@in.ibm.com]

attached ConfigTrace.log

[vino...@in.ibm.com]

wimconfig file attached

[vino...@in.ibm.com]

wkplc file attached

[vino...@in.ibm.com]

security.xml attached

[ff...@us.ibm.com]

You had run different configuration tasks multiple times. security.xml indicates you already had standalone LDAP configured. Also I saw property extension was configured in wimconfig.xml.

What is the state this system is in? Can you start it up? Can you log in?

If a system is messed up, running more tasks only makes it worse, not better. So we need to know the history and whether it's still working.

[vino...@in.ibm.com]

i am able to start the server and login to portal.
Yes currently its configured to standalone LDAP and also i have run LookAside thing.

Now the requirement is i need create groups in the DB repository (since LDAP is read only). For that i am referring : http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/security/app_group.html

My Use case is : LDAP already has User(UID) using which authentication happens....however after login we need to capture extra fields that should not be in LDAP (as its Read only) also we need to create group that will also not be part of LDAP. So now we need to add this User to the new Group (which not part of LDAP).

Thanks

[ff...@us.ibm.com]

You have to switch the standalone LDAP configuration to federated first. The task to run is not "wp-create-ldap", but rather "wp-modify-federated-security" and the relevant InfoCenter section is
http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/security/win_mod_fed_sec.html

After successfully converting the security, then you need to add a database repository, such as DB2, for the application groups. This is different from LookAside, which is called property extension in 6.1 and used to store additional user and group attributes.

[vino...@in.ibm.com]

Ok, Will follow the steps.

For my usecase i need to use LookAside (for additional attributes) + DB repository (for storing Groups and Users created from Portal) right ?.

[ff...@us.ibm.com]

Yes, I believe you need both property extension and database repository.

[vino...@in.ibm.com]

I ran the following steps :

Step 1 : To Federate LDAP from existing Standalone LDAP

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/security/win_mod_fed_sec.html

Step 2 : To create DB Repository for storing Groups :

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/install/win_add_db_ureg.html

Step 3 : Enabling application groups (for say If DB repository is used for groups with members from other repository like LDAP) :

http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/index.jsp?topic=/com.ibm.wp.ent.doc/security/app_group.html

Results :

Step 1 got Passed
Step 2 got Passed
Step 3 : When i directly run

"ConfigEngine.bat wp-update-group-repository-relationship –Drepository.id=fedldap –Drepository.forgroups=vmmdb" I am getting error :

[wplc-update-group-repository-binding] attribute=[
[wplc-update-group-repository-binding] [ repositoriesForGroups="${repository.fo
rgroups}" ], ]
[wplc-update-group-repository-binding] customproperty=[ *** NONE_SPECIFIED *
** ]
[wplc-update-group-repository-binding] trimSpaces= *** NOT_SPECIFIED ***
[wplc-update-group-repository-binding] id="${repository.id}"
[wplc-update-group-repository-binding] Repository ${repository.id} not found in
the WIM Repository System
[wplc-update-group-repository-binding] at com.ibm.wplc.deploy.tasks.impl.Federa
tedUpdateRepositoryForGroupsImpl.execute(FederatedUpdateRepositoryForGroupsImpl.
java:40)
[wplc-update-group-repository-binding] at com.ibm.wplc.deploy.tasks.AbstractBas
eAdminTask.executeTask(AbstractBaseAdminTask.java:495)
[wplc-update-group-repository-binding] at com.ibm.wplc.deploy.tasks.AbstractBas
eWsAdminWrapperTask.executeTask(AbstractBaseWsAdminWrapperTask.java:265)
[wplc-update-group-repository-binding] at com.ibm.wplc.deploy.tasks.AbstractBas
eAdminTask.execute(AbstractBaseAdminTask.java:156)
[wplc-update-group-repository-binding] at org.apache.tools.ant.UnknownElement.e
xecute(UnknownElement.java:275)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Task.perform(Tas
k.java:364)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Target.execute(T
arget.java:341)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Target.performTa
sks(Target.java:369)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Project.executeS
ortedTargets(Project.java:1216)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Project.executeT
arget(Project.java:1185)
[wplc-update-group-repository-binding] at org.apache.tools.ant.helper.DefaultEx
ecutor.executeTargets(DefaultExecutor.java:40)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Project.executeT
argets(Project.java:1068)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Main.runBuild(Ma
in.java:668)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Main.startAnt(Ma
in.java:187)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Main.start(Main.
java:150)
[wplc-update-group-repository-binding] at com.ibm.wps.config.ConfigEngine.proce
ss(ConfigEngine.java:828)
[wplc-update-group-repository-binding] at com.ibm.wps.config.ConfigEngine.main(
ConfigEngine.java:236)
[wplc-update-group-repository-binding] at sun.reflect.NativeMethodAccessorImpl.
invoke0(Native Method)
[wplc-update-group-repository-binding] at sun.reflect.NativeMethodAccessorImpl.
invoke(NativeMethodAccessorImpl.java:79)
[wplc-update-group-repository-binding] at sun.reflect.DelegatingMethodAccessorI
mpl.invoke(DelegatingMethodAccessorImpl.java:43)
[wplc-update-group-repository-binding] at java.lang.reflect.Method.invoke(Metho
d.java:618)
[wplc-update-group-repository-binding] at com.ibm.ws.bootstrap.WSLauncher.main(
WSLauncher.java:263)
[wplc-update-group-repository-binding] at sun.reflect.NativeMethodAccessorImpl.
invoke0(Native Method)
[wplc-update-group-repository-binding] at sun.reflect.NativeMethodAccessorImpl.
invoke(NativeMethodAccessorImpl.java:79)
[wplc-update-group-repository-binding] at sun.reflect.DelegatingMethodAccessorI
mpl.invoke(DelegatingMethodAccessorImpl.java:43)
[wplc-update-group-repository-binding] at java.lang.reflect.Method.invoke(Metho
d.java:618)
[wplc-update-group-repository-binding] at com.ibm.wps.config.launch.WpsConfigLa
uncher.process(WpsConfigLauncher.java:243)
[wplc-update-group-repository-binding] at com.ibm.wps.config.launch.WpsConfigLa
uncher.main(WpsConfigLauncher.java:459)

BUILD FAILED
C:\IBM\WebSphere\wp_profile\ConfigEngine\config\actions\wp_security_pub.xml:2263
: Groups association failed.

Note : Till now i am able to start service and logon to portal

Any clues on the above error ??.

Thanks.

[redkn...@gmx.net]

for some reasons the environment does not pick up the -D parameters. can you please add them to wkplc.properties and rerun the task

[vino...@in.ibm.com]

i added entries (repository.forgroups=vmmdb
repository.id=fedldap) to wkplc.properties file and ran the command again. Now i am getting below error:

[wplc-update-group-repository-binding] trimSpaces= *** NOT_SPECIFIED ***

[wplc-update-group-repository-binding] id="fedldap"
[wplc-update-group-repository-binding] Repository fedldap not found in the WIM
epository System
[wplc-update-group-repository-binding] at com.ibm.wplc.deploy.tasks.impl.Feder
tedUpdateRepositoryForGroupsImpl.execute(FederatedUpdateRepositoryForGroupsImpl
java:40)
[wplc-update-group-repository-binding] at com.ibm.wplc.deploy.tasks.AbstractBa
eAdminTask.executeTask(AbstractBaseAdminTask.java:495)
[wplc-update-group-repository-binding] at com.ibm.wplc.deploy.tasks.AbstractBa
eWsAdminWrapperTask.executeTask(AbstractBaseWsAdminWrapperTask.java:265)
[wplc-update-group-repository-binding] at com.ibm.wplc.deploy.tasks.AbstractBa
eAdminTask.execute(AbstractBaseAdminTask.java:156)
[wplc-update-group-repository-binding] at org.apache.tools.ant.UnknownElement.
xecute(UnknownElement.java:275)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Task.perform(Ta
k.java:364)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Target.execute(
arget.java:341)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Target.performT
sks(Target.java:369)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Project.execute
ortedTargets(Project.java:1216)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Project.execute
arget(Project.java:1185)
[wplc-update-group-repository-binding] at org.apache.tools.ant.helper.DefaultE
ecutor.executeTargets(DefaultExecutor.java:40)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Project.execute
argets(Project.java:1068)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Main.runBuild(M
in.java:668)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Main.startAnt(M
in.java:187)
[wplc-update-group-repository-binding] at org.apache.tools.ant.Main.start(Main
java:150)
[wplc-update-group-repository-binding] at com.ibm.wps.config.ConfigEngine.proc
ss(ConfigEngine.java:828)
[wplc-update-group-repository-binding] at com.ibm.wps.config.ConfigEngine.main
ConfigEngine.java:236)
[wplc-update-group-repository-binding] at sun.reflect.NativeMethodAccessorImpl
invoke0(Native Method)
[wplc-update-group-repository-binding] at sun.reflect.NativeMethodAccessorImpl
invoke(NativeMethodAccessorImpl.java:79)
[wplc-update-group-repository-binding] at sun.reflect.DelegatingMethodAccessor
mpl.invoke(DelegatingMethodAccessorImpl.java:43)
[wplc-update-group-repository-binding] at java.lang.reflect.Method.invoke(Meth
d.java:618)
[wplc-update-group-repository-binding] at com.ibm.ws.bootstrap.WSLauncher.main
WSLauncher.java:263)
[wplc-update-group-repository-binding] at sun.reflect.NativeMethodAccessorImpl
invoke0(Native Method)
[wplc-update-group-repository-binding] at sun.reflect.NativeMethodAccessorImpl
invoke(NativeMethodAccessorImpl.java:79)
[wplc-update-group-repository-binding] at sun.reflect.DelegatingMethodAccessor
mpl.invoke(DelegatingMethodAccessorImpl.java:43)
[wplc-update-group-repository-binding] at java.lang.reflect.Method.invoke(Meth
d.java:618)
[wplc-update-group-repository-binding] at com.ibm.wps.config.launch.WpsConfigL
uncher.process(WpsConfigLauncher.java:243)
[wplc-update-group-repository-binding] at com.ibm.wps.config.launch.WpsConfigL
uncher.main(WpsConfigLauncher.java:459)

BUILD FAILED
C:\IBM\WebSphere\wp_profile\ConfigEngine\config\actions\wp_security_pub.xml:226

: Groups association failed.

[vino...@in.ibm.com]

Sorry since i had earlier configured LDAP (and after that i federated) i should have used the same ldapid. Now i am able to proceed further but i get the below towards last of script execution.

wp-update-group-repository-relationship:
Thu Oct 30 15:43:53 EDT 2008
[wplc-update-group-repository-binding] Task parameters:
[wplc-update-group-repository-binding] Global attributes:
[wplc-update-group-repository-binding] cell="node1"
[wplc-update-group-repository-binding] engineinstalllocation="C:/IBM/WebSphe
re/wp_profile/ConfigEngine"
[wplc-update-group-repository-binding] pathseparator=";"
[wplc-update-group-repository-binding] osarch="x86"
[wplc-update-group-repository-binding] node=""
[wplc-update-group-repository-binding] server=""

[wplc-update-group-repository-binding] Instance attributes (Set 1 of 1):
[wplc-update-group-repository-binding] ignoreDuplicateIDs="false"
[wplc-update-group-repository-binding] attribute=[
[wplc-update-group-repository-binding] [ repositoriesForGroups="vmmDb" ], ]

[wplc-update-group-repository-binding] customproperty=[ *** NONE_SPECIFIED *
** ]

[wplc-update-group-repository-binding] trimSpaces= *** NOT_SPECIFIED ***

[wplc-update-group-repository-binding] id="mainldap"
[wplc-update-group-repository-binding] Groups association modified successfull.
[wplc-update-group-repository-binding] Status = Complete

BUILD FAILED
Target `?Drepository.id=mainldap' does not exist in this project.

Total time: 15 seconds
isIseries currently set to: null
uploading registry
Created admin client: com.ibm.ws.management.AdminClientImpl@796a796a
Created config Service Proxy: com.ibm.websphere.management.configservice.ConfigS
erviceProxy@197e197e
CELL: node1
Websphere:_Websphere_Config_Data_Type=Registry,_Websphere_Config_Data_Id=cells/n
ode1|registry.xml#Registry_1216915293437,_WEBSPHERE_CONFIG_SESSION=anonymous1225
395836171
----------------------------------------------------------------------------------------------

FYI, below is the list of configured repositories :

wp-query-repository:
Thu Oct 30 15:49:28 EDT 2008

iseries-switch-back:
Thu Oct 30 15:49:29 EDT 2008
[wplc-query-federated-repository] Task parameters:
[wplc-query-federated-repository] Global attributes:
[wplc-query-federated-repository] cell="node1"
[wplc-query-federated-repository] engineinstalllocation="C:/IBM/WebSphere/wp
_profile/ConfigEngine"
[wplc-query-federated-repository] pathseparator=";"
[wplc-query-federated-repository] osarch="x86"
[wplc-query-federated-repository] node=""
[wplc-query-federated-repository] server=""

[wplc-query-federated-repository] Instance attributes (Set 1 of 1):
[wplc-query-federated-repository] ignoreDuplicateIDs= *** NOT_SPECIFIED ***

[wplc-query-federated-repository] attribute=[ *** NONE_SPECIFIED *** ]
[wplc-query-federated-repository] customproperty=[ *** NONE_SPECIFIED *** ]
[wplc-query-federated-repository] trimSpaces= *** NOT_SPECIFIED ***
[wplc-query-federated-repository] Existing Federated Repositories
[wplc-query-federated-repository] Repository Name : {Details}
[wplc-query-federated-repository] *******************************
[wplc-query-federated-repository] mainldap : {specificRepositoryType=IDS6, repos
itoryType=LDAP, host=localhost}
[wplc-query-federated-repository] vmmDb : {specificRepositoryType=db2, repositor
yType=DB, host=jdbc/vmmfeddbDS}
[wplc-query-federated-repository] Status = Complete

[ff...@us.ibm.com]

It looks like the character before "Drepository.id=mainldap" is not a real hyphen. Try removing it and enter it from your keyboard.

[vino...@in.ibm.com]

Thanks for you continious, it worked.
Now having done all this setup (LDAP + LookAside + DB Respository (storing groups)) while updating the attributes in to LookAside DB i get some VMM error. Please find the same attached.

[ff...@us.ibm.com]

How did you update the attribute? What's the name of the attribute? You need to look into SystemOut.log, not SystemErr.log.