WPSconfig enable-ldap-security build failed with errors. - Websphere

This is a discussion on WPSconfig enable-ldap-security build failed with errors. - Websphere ; Hi, I have problem while configuring the Webshpere portal LDAP with Domino. I have changed the properties for LDAP in wpconfig.properties and run WPSconfig.sh validate-ldap command which give "Build Successful" message. It means that ldap settings are OK. The problem ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: WPSconfig enable-ldap-security build failed with errors.

  1. WPSconfig enable-ldap-security build failed with errors.

    Hi,
    I have problem while configuring the Webshpere portal LDAP with Domino. I have changed the properties for LDAP in wpconfig.properties and run WPSconfig.sh validate-ldap command which give "Build Successful" message. It means that ldap settings are OK. The problem comes when I run the command "WPSconfig.sh enable-security-ldap", which fails with the following message on the console: -

    "action-configure-content-security:
    Sat Oct 03 18:28:10 PKT 2009
    [xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10038/wps/config/
    [xmlaccess] EJPXB0002I: Reading input file /opt/IBM/WebSphere/PortalServer/config/work/ContentAdminGroupsPAC.xml
    Error 404: Initialization of one or more services failed.
    [xmlaccess] EJPXB0015E: Server response indicates an error.
    [xmlaccess] EJPXB0015E: Server response indicates an error.
    [xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10038/wps/config/
    [xmlaccess] EJPXB0002I: Reading input file /opt/IBM/WebSphere/PortalServer/config/work/ContentUserGroupsPAC.xml
    Error 404: Initialization of one or more services failed.
    [xmlaccess] EJPXB0015E: Server response indicates an error.
    [xmlaccess] EJPXB0015E: Server response indicates an error.

    action-init-accesscontrol:
    Sat Oct 03 18:29:16 PKT 2009
    [echo] Calling ContentModelInitializer

    BUILD FAILED
    file:../config/actions/jcr_cfg.xml:1787: Java returned: 1"

    Following is the stack from configTrace.log just before the target "enable-security-ldap" is finished: -

    Target started: action-configure-content-security

    action-configure-content-security:
    [xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10038/wps/config/
    [xmlaccess] EJPXB0002I: Reading input file /opt/IBM/WebSphere/PortalServer/config/work/ContentAdminGroupsPAC.xml
    Error 404: Initialization of one or more services failed.
    [xmlaccess] EJPXB0015E: Server response indicates an error.
    [xmlaccess] EJPXB0015E: Server response indicates an error.
    [xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10038/wps/config/
    [xmlaccess] EJPXB0002I: Reading input file /opt/IBM/WebSphere/PortalServer/config/work/ContentUserGroupsPAC.xml
    Error 404: Initialization of one or more services failed.
    [xmlaccess] EJPXB0015E: Server response indicates an error.
    [xmlaccess] EJPXB0015E: Server response indicates an error.
    Sat Oct 03 18:29:16 PKT 2009
    Target started: action-init-accesscontrol

    action-init-accesscontrol:
    [echo] Calling ContentModelInitializer
    Target finished: action-init-accesscontrol
    Target finished: action-configure-content-security
    Target finished: enable-security-ldap
    ---- Begin dump of properties ----

    Following is stack from SystemOut.log

    [10/3/09 18:29:16:894 PKT] 0000002d WebApp E SRVE0026E: [Servlet Error]-[InitServlet]: com.ibm.content.exception.LoginException: javax.jcr.RepositoryException: Unable to initialize RepositoryFactory due to exception of type: com.ibm.portal.puma.MemberNotFoundException with message: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=default organization.
    at com.ibm.content.mediator.util.LoginUtil.initialize LoginContext(LoginUtil.java:128)
    at com.ibm.content.mediator.ContextMediator.initLogin Context(ContextMediator.java:108)
    at com.ibm.content.mediator.ContextMediator.initConta iner(ContextMediator.java:80)
    at com.ibm.content.mediator.OperationsMediator.getDat aGraph(OperationsMediator.java:70)
    at com.ibm.content.service.transport.LocalPasswordTra nsport.getDataGraph(LocalPasswordTransport.java:99 )
    at com.ibm.content.service.impl.LoginServiceImpl.logi nLocal(LoginServiceImpl.java:163)
    at com.ibm.content.init.ContentModelInitializer.initA ccessControl(ContentModelInitializer.java:882)
    at com.ibm.content.init.servlets.InitServlet.doGet(In itServlet.java:83)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:743)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1282)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:673)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleReques t(WebApp.java:2965)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequ est(WebGroup.java:221)
    at com.ibm.ws.webcontainer.VirtualHost.handleRequest( VirtualHost.java:210)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:1931)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:84)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:472)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:411)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.ready(HttpInboundLink.java:288)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.sendToDiscriminaters(NewConnectionIniti alReadCallback.java:207)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.complete(NewConnectionInitialReadCallba ck.java:109)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.reque stComplete(WorkQueueManager.java:566)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attem ptIO(WorkQueueManager.java:619)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.worke rRun(WorkQueueManager.java:952)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worke r.run(WorkQueueManager.java:1039)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1470)
    Caused by: javax.jcr.RepositoryException: Unable to initialize RepositoryFactory due to exception of type: com.ibm.portal.puma.MemberNotFoundException with message: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,o=default organization.
    at com.ibm.icm.jcr.RepositoryFactory.init(RepositoryF actory.java:361)
    at com.ibm.icm.jcr.RepositoryFactory.getRepository(Re positoryFactory.java:725)
    at com.ibm.content.mediator.util.RepositoryUtil.getRe pository(RepositoryUtil.java:46)
    at com.ibm.content.mediator.util.LoginUtil.initialize LoginContext(LoginUtil.java:87)
    ... 26 more

    To resolve this issue I have updated icm.properties files but when I run the build it again changes the value of "jcr.admin.uniqueName" to the wrong one.

    Please note that that there is not cluster configuration and also there is no DB2 settings are there.
    Can anyone help please????
    Thanks in advance

  2. Re: WPSconfig enable-ldap-security build failed with errors.

    The exception from the SystemOut.log that you've pasted is normal for this point of the script. The "action-configure-content-security" section is what updates icm.properties, among other things, and because it has failed, it has not had a chance to update this yet.

    There should be another exception prior to what you've pasted. "Error 404: Initialization of one or more services failed." means that the wps.ear application failed to start correctly. The exception you pasted comes from the icmjcr.ear applications, which starts after wps.ear.

    Could you upload both the ConfigTrace.log and SystemOut.log?

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

  3. Re: WPSconfig enable-ldap-security build failed with errors.

    Thanks a lot for your reply. Files you requested are attached..............
    Please open them in wordpad instead of notepad.

  4. Re: WPSconfig enable-ldap-security build failed with errors.

    The problem appears to be the values for your PortalAdminId and WasUserId.

    PortalAdminId=wpsadmin
    WasUserid=wasadmin

    You've just put shortnames here and these must be full distinguished names (uid=wpsadmin,ou=users,o=org or cn=wpsadmin,o=org or something like that). Please verify what these values should be with your ldap administrator. From the SystemOut.log this is throwing the following exception, causing Portal not to function:

    =======================
    [10/3/09 18:27:46:382 PKT] 0000000a Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.
    com.ibm.wps.ac.DomainAdministratorNotFoundExceptio n: EJPSB0107E: Exception occurred while retrieving the identity of the domain adminuser/admingroup wpsadmin.
    at com.ibm.wps.ac.impl.AccessControlDataManagementSer viceImpl.convertDNtoObjectID(AccessControlDataMana gementServiceImpl.java:775)
    at com.ibm.wps.ac.impl.AccessControlDataManagementSer viceImpl.initializeDomainConfig(AccessControlDataM anagementServiceImpl.java:662)
    at com.ibm.wps.ac.impl.AccessControlDataManagementSer viceImpl.reinit(AccessControlDataManagementService Impl.java:599)
    Caused by: com.ibm.wps.util.DataBackendException: EJPSG0015E: Data Backend Problem com.ibm.websphere.wmm.exception.InvalidMemberDNExc eption: The syntax of the member DN "wpsadmin" is invalid. Check if the special characters are escaped.
    at com.ibm.wps.services.puma.DefaultURManager.findUse rById(DefaultURManager.java:291)
    at com.ibm.wps.services.puma.PumaServiceImpl.findUser ById(PumaServiceImpl.java:460)
    at com.ibm.wps.services.puma.Puma.findUserById(Puma.j ava:85)
    at com.ibm.wps.ac.impl.AccessControlDataManagementSer viceImpl.convertDNtoObjectID(AccessControlDataMana gementServiceImpl.java:706)
    Caused by: com.ibm.websphere.wmm.exception.InvalidMemberDNExc eption: The syntax of the member DN "wpsadmin" is invalid. Check if the special characters are escaped.
    at com.ibm.ws.wmm.common.MemberDNHelper.formatDN(Memb erDNHelper.java:94)
    at com.ibm.ws.wmm.datatype.impl.BaseMemberIdentifierD ata.formatMemberDN(BaseMemberIdentifierData.java:1 28)
    at com.ibm.ws.wmm.MemberRepositoryManager.getMember(M emberRepositoryManager.java:3225)
    at com.ibm.ws.wmm.MemberRepositoryManager.getMember(M emberRepositoryManager.java:3192)
    =======================

    To correct this, you will need to do the following:

    1. Follow all steps in this technote under the "Standalone" section:

    http://www-01.ibm.com/support/docvie...id=swg21295051

    2. Once the steps in the technote are successful (i.e. disable-security is successful), edit wpconfig.properties and correct the values of PortalAdminId and WasUserid.

    3. Re-execute enable-security-ldap.

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

  5. Re: WPSconfig enable-ldap-security build failed with errors.

    Thanks for your time and reply.
    By your previous message I again analysed wpconfig.properties and there in portal configuration section changed the wpsadmin to it's domino common name and default organization and yes it's solved now. WPSconfig enable-security-build is now successfull and portal is started with all of it's services. I was under the impression that in portal config section we will write only the portal admin user and in LDAP section actually CN with O is written. Anyway's thanks a lot for your help.

    But here is another problem which I am now facing which is about Web Content Manager(WCM).
    After LDAP configuration it was running perfectly fine but suddenly all WCM portlets(including the authoring one) are giving the message "This Portlet is not available". The last thing which i did was to import the LTAP token file in domino, which was successfully imported.
    Sending you SystemOut.log file again...........
    Thanks for your reply and time again.

  6. Re: WPSconfig enable-ldap-security build failed with errors.

    Problem regarding wcm is solved now by updating icm.properties file. I mistakenly chaged wpsadmin entry according to the domino syntax i.e cn=wpsadmin,o=. By brining back it to simple "wpsadmin" and running the enable-security-ldap build again, all wcm portlets are back. I am still confused that is it due to the same reason or it's something else????? I only know that while running the ldap build it updates icm.properties file for wcm and document manager. Is it right???
    Also what if I want to configure Lotus Collaborative Components too??
    thanks

+ Reply to Thread