[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1371
  • Last Modified:

wp-modify-ldap-security fails on Websphere 6.1 to Domino 5

Server: Solaris 10, 64 bit
App: Websphere Application server 6.1

Server: win2000
App: Domino Ldap r5

I have followed "the book" of setting up the enviroment for websphere to talk to the ldap.
When i run the command validate-ldap I get a build sucessful. But when I run the command wp-modiflyldap-security it fails with this output:
BUILD FAILED
/usr/prog/ibm/websphere/wp_profile/ConfigEngine/config/actions/wp_security_pub.xml:112: The following error occurred while executing this line:
/usr/prog/ibm/websphere/wp_profile/ConfigEngine/config/actions/wp_security_pub.xml:1568: Failed to validate object class.

There is no other logfil that can give me a more detailed solution. the ConfiTrace.log shows nothing. The wp_security_pub.xml only shows what command it fails on.

I found a tech note to remove one objectclass http://www-01.ibm.com/support/docview.wss?rs=688&uid=swg21318615 but this did not help me. I have been googling the net without any help. Has anyone out here been threw a problem similar? Attached a copy & paste of my wkplc.properties file (only of the ldap config.)

Anyhelp is very much thankful!
ldap-prop-case.doc
0
sashadelenn
Asked:
sashadelenn
  • 5
1 Solution
 
sashadelennAuthor Commented:
after starting the portal and running the task wp-modify again I get  now this output:

BUILD FAILED
/usr/prog/ibm/websphere/wp_profile/ConfigEngine/config/actions/wp_security_pub.xml:112: The following error occurred while executing this line:
/usr/prog/ibm/websphere/wp_profile/ConfigEngine/config/actions/wp_security_pub.xml:1568: com.ibm.websphere.management.exception.ConfigServiceException: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the discard operation on ConfigService MBean because of insufficient or empty credentials.

I have the correct cred. for this enviroment. :(
0
 
sashadelennAuthor Commented:
changed the was user and password, it went threw, but i get again the :
BUILD FAILED
/usr/prog/ibm/websphere/wp_profile/ConfigEngine/config/actions/wp_security_pub.xml:112: The following error occurred while executing this line:
/usr/prog/ibm/websphere/wp_profile/ConfigEngine/config/actions/wp_security_pub.xml:1568: Failed to validate object class.

on wp-modify..... :(
0
 
SysExpertCommented:
maybe you need a newer version of Domino.

R5 is pretty ancient....

 
I hope this helps !
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
sashadelennAuthor Commented:
hehe, I know it is old :P It will be by the summer overtaken by sun directory server. But I need to migrate my excisting webpshere from 5.1 to 6.1. Only thing that is getting me stuck is the ldap config.
0
 
sashadelennAuthor Commented:
Still getting with wp-modify

[wplc-validate-ldap-objectclasses]   Instance attributes (Set 1 of 1):
[wplc-validate-ldap-objectclasses]     attribute=[ *** NONE_SPECIFIED *** ]
[wplc-validate-ldap-objectclasses]     port="389"
[wplc-validate-ldap-objectclasses]     customproperty=[ *** NONE_SPECIFIED *** ]
[wplc-validate-ldap-objectclasses]     bindPassword="PASSWORD_REMOVED"
[wplc-validate-ldap-objectclasses]     objectClasses=";dominoGroup;dominoPerson;"
[wplc-validate-ldap-objectclasses]     SSLEnabled="false"
[wplc-validate-ldap-objectclasses]     ignoreDuplicateIDs= *** NOT_SPECIFIED ***
[wplc-validate-ldap-objectclasses]     bindDN="cn=wpsbind,o=student"
[wplc-validate-ldap-objectclasses]     host="hostname"
[wplc-validate-ldap-objectclasses]     trimSpaces= *** NOT_SPECIFIED ***
[wplc-validate-ldap-objectclasses] javax.naming.ServiceUnavailableException: hostname:389; socket closed; remaining name ''
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.ldap.Connection.readReply(Connection.java:410)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:611)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:534)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1944)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1806)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.ldap.LdapCtx.buildSchemaTree(LdapCtx.java:1583)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.ldap.LdapCtx.getSchemaTree(LdapCtx.java:1557)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.ldap.LdapCtx.c_getSchema(LdapCtx.java:1498)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_getSchema(ComponentDirContext.java:415)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getSchema(PartialCompositeDirContext.java:402)
[wplc-validate-ldap-objectclasses]       at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.getSchema(PartialCompositeDirContext.java:391)
[wplc-validate-ldap-objectclasses]       at javax.naming.directory.InitialDirContext.getSchema(InitialDirContext.java:187)
[wplc-validate-ldap-objectclasses]       at com.ibm.wplc.val.tasks.ValidateLDAPObjectClassImpl.getLDAPObjectClasses(ValidateLDAPObjectClassImpl.java:115)
[wplc-validate-ldap-objectclasses]       at com.ibm.wplc.val.tasks.ValidateLDAPObjectClassImpl.execute(ValidateLDAPObjectClassImpl.java:60)
[wplc-validate-ldap-objectclasses]       at com.ibm.wplc.deploy.tasks.AbstractBaseAdminTask.executeTask(AbstractBaseAdminTask.java:495)
[wplc-validate-ldap-objectclasses]       at com.ibm.wplc.deploy.tasks.AbstractBaseWsAdminWrapperTask.executeTask(AbstractBaseWsAdminWrapperTask.java:301)
[wplc-validate-ldap-objectclasses]       at com.ibm.wplc.deploy.tasks.AbstractBaseAdminTask.execute(AbstractBaseAdminTask.java:156)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Task.perform(Task.java:364)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Target.execute(Target.java:341)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Target.performTasks(Target.java:369)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:37)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:382)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:107)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Task.perform(Task.java:364)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:64)
[wplc-validate-ldap-objectclasses]       at com.ibm.wps.config.If.execute(If.java:70)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Task.perform(Task.java:364)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Target.execute(Target.java:341)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Target.performTasks(Target.java:369)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[wplc-validate-ldap-objectclasses]       at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)


No ideas anyone of what I am doing wrong? Domino 5 is supported.. so that is not the problem. It seems a objectclass is wrong, but I dont understand the error.
0
 
vtoalCommented:
There are some limitations to R5's LDAP. It is LDAP V3 compatible but did not support all the features. One of the weaknesses was that you could not authenticate against directories that were accessible via directory assistance in LDAP, only against the main Domino directory.

Also, if you look at the SW/HW requirements in the WAS 6.1 documentation you will see that it requires a Domino server R6.5.4 or higher  as an LDAP source. Your R5 server will just not do.
0
 
sashadelennAuthor Commented:
I am now looking into upgrading domino to v8.5. The v5 is not supported with websphere v6.1.
I really dont know how i missed that big text!! >:(
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now