Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Configuring WebSphere Portal 5.1 to use an Active Directory LDAP server

15 views
Skip to first unread message

AlexH

unread,
Mar 11, 2005, 11:23:50 AM3/11/05
to

I'm trying to configure a WebSphere Portal 5.1 installation to use an
Active Directory server as its LDAP server following the instructions
in the 'WebSphere Portal information center'
(http://publib.boulder.ibm.com/infocenter/wp51help/index.jsp) (Enabling
security -> LDAP user registry -> Configuring LDAP with/without realm
support -> Active Directory) and it's breaking in a way I don't
understand, so I'm posting this here in the hope someone might point me
in the correct direction...

The validation step succeeds but when I run
Code:
--------------------
WPSConfig.bat enable-security-wmmur-ldap
--------------------
I get the following error: (after quite a lot of output)


Code:
--------------------

action-create-deployment-credentials:

[xmlaccess] EJPXB0006I: Connecting to URL [url]http://<hostname cut>:9081/wps/config

[xmlaccess] EJPXB0002I: Reading input file C:\WEBSPH~1\PORTAL~1\config\work\crea

teDeploymentCredentials.xml

[xmlaccess] EJPXB0012E: Received error response code 503

[xmlaccess] java.net.ConnectException: HTTP status not ok: 503



BUILD FAILED

file:../config/actions/wps_cfg.xml:440: EJPXB0016E: An error occurred on the cli

ent: HTTP status not ok: 503


--------------------


By this stage it has successfully restarted the portal server which
logs the following error:


Code:
--------------------

2005.03.11 16:01:45.616 I com.ibm.wps.logging.LogManager init



--------------------------------------------------------------------------------

IBM WebSphere Portal 5.1



Licensed Materials - Property of IBM

5724-E76 and 5724-E77

(C) Copyright IBM Corp. 2001, 2004 - All Rights Reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

--------------------------------------------------------------------------------

Build Level:

wp510_083 (2004-11-19 11:38)

--------------------------------------------------------------------------------



2005.03.11 16:01:45.616 I com.ibm.wps.logging.LogManager init

Trace specification: *=all=disabled



2005.03.11 16:01:48.890 I com.ibm.wps.services.credentialvault.DefaultVault loadEncryptionExit

EJPSK0012I: Configuration file /defaultvault not found. System defaults to the DefaultEncryptionExit.



2005.03.11 16:01:48.890 I com.ibm.wps.services.credentialvault.VaultAdapterManager loadVaultAdapter

EJPSK0023I: Vault adapter type default was loaded successfully: WPS Default Vault Implementation



2005.03.11 16:02:03.910 E com.ibm.wps.engine.Servlet init

EJPFD0016E: Initialization of service failed. - StackTrace follows...



2005.03.11 16:02:03.910 E com.ibm.wps.engine.Servlet init

com.ibm.wps.util.DataBackendException: EJPSG0015E: Data Backend Problem java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
com.ibm.ejs.container.CreateFailureException: ; nested exception is:
java.lang.reflect.InvocationTargetException

at com.ibm.wps.services.puma.RealmAwareURManager.initRealms(RealmAwareURManager.java:122)

at com.ibm.wps.services.puma.RealmAwareURManager.<init>(RealmAwareURManager.java:82)

at com.ibm.wps.services.puma.PumaServiceImpl.init(PumaServiceImpl.java:126)

at com.ibm.wps.services.Service.init(Service.java:109)

at com.ibm.wps.services.Service.init(Service.java:85)

at com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:361)

at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:269)

at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:125)

at com.ibm.wps.engine.Servlet.init(Servlet.java:204)

at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:82)

at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147)

at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270)

at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecycleServlet.java:113)

at com.ibm.ws.webcontainer.servlet.ServletInstance.init(ServletInstance.java:189)

at javax.servlet.GenericServlet.init(GenericServlet.java:258)

at com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java:876)

at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:224)

at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:542)

at com.ibm.ws.webcontainer.webapp.WebApp.loadServletManager(WebApp.java:1279)

at com.ibm.ws.webcontainer.webapp.WebApp.init(WebApp.java:283)

at com.ibm.ws.webcontainer.srt.WebGroup.loadWebApp(WebGroup.java:403)

at com.ibm.ws.webcontainer.srt.WebGroup.init(WebGroup.java:212)

at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:1005)

at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:136)

at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:356)

at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:505)

at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:808)

at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:354)

at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:578)

at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:299)

at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:256)

at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)

at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)

at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)

at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)

at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)

at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:243)

at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)

at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)

Caused by: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
com.ibm.ejs.container.CreateFailureException: ; nested exception is:
java.lang.reflect.InvocationTargetException

at com.ibm.CORBA.iiop.UtilDelegateImpl.mapSystemException(UtilDelegateImpl.java:162)

at com.ibm.CORBA.iiop.UtilDelegateImpl.wrapException(UtilDelegateImpl.java:684)

at javax.rmi.CORBA.Util.wrapException(Util.java:296)

at com.ibm.websphere.wmm.objects._MemberService_Stub.getConfigurationData(_MemberService_Stub.java:2299)

at com.ibm.wps.services.puma.DefaultWMMAccessBean.getConfigurationData(DefaultWMMAccessBean.java:257)

at com.ibm.wps.services.puma.RealmAwareURManager.initRealms(RealmAwareURManager.java:92)

... 44 more

Caused by: com.ibm.ejs.container.CreateFailureException: ; nested exception is:
java.lang.reflect.InvocationTargetException

at com.ibm.ejs.container.StatelessBeanO.<init>(StatelessBeanO.java:151)

at com.ibm.ejs.container.CMStatelessBeanO.<init>(CMStatelessBeanO.java:53)

at com.ibm.ejs.container.CMStatelessBeanOFactory.create(CMStatelessBeanOFactory.java:40)

at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:685)

at com.ibm.ejs.container.EJSHome.createBeanO(EJSHome.java:772)

at com.ibm.ejs.container.activator.UncachedActivationStrategy.atActivate(UncachedActivationStrategy.java:78)

at com.ibm.ejs.container.activator.Activator.activateBean(Activator.java:516)

at com.ibm.ejs.container.EJSContainer.preInvoke_internal(EJSContainer.java:2778)

at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2489)

at com.ibm.ejs.container.EJSContainer.preInvoke(EJSContainer.java:2474)

at com.ibm.websphere.wmm.objects.EJSRemoteStatelessMemberService_14d751a3.getConfigurationData(Unknown Source)

at com.ibm.websphere.wmm.objects._MemberService_Stub.getConfigurationData(_MemberService_Stub.java:2292)

... 46 more

Caused by: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.ibm.ejs.container.StatelessBeanO.<init>(StatelessBeanO.java:144)

... 57 more

Caused by: javax.ejb.CreateException: java.lang.NullPointerException

at com.ibm.ws.wmm.objectimpl.MemberServiceBeanBase.ejbCreate(MemberServiceBeanBase.java:182)

... 63 more



2005.03.11 16:02:16.863 I com.ibm.icm.jcr.service.ServiceManager init()

interface com.ibm.icm.jcr.service.lock.LockManagerService



2005.03.11 16:03:55.271 I com.ibm.wps.command.xml.XmlCommandServlet init

Initialization failed! - StackTrace follows...



2005.03.11 16:03:55.271 I com.ibm.wps.command.xml.XmlCommandServlet init

java.lang.Exception: ServiceManager: Previous initialization was not successful.

at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:178)

at com.ibm.wps.services.ServiceManager.init(ServiceManager.java:125)

at com.ibm.wps.command.xml.XmlCommandServlet.init(XmlCommandServlet.java:91)

at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:82)

at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147)

at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270)

at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecycleServlet.java:113)

at com.ibm.ws.webcontainer.servlet.ServletInstance.init(ServletInstance.java:189)

at javax.servlet.GenericServlet.init(GenericServlet.java(Inlined Compiled Code))

at com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java(Compiled Code))

at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:224)

at com.ibm.ws.webcontainer.webapp.WebAppServletManager.getServletReference(WebAppServletManager.java:455)

at com.ibm.ws.webcontainer.webapp.WebApp.getServletReference(WebApp.java:652)

at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcherInfo.calculateInfo(WebAppRequestDispatcherInfo.java:187)

at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcherInfo.<init>(WebAppRequestDispatcherInfo.java:68)

at com.ibm.ws.webcontainer.webapp.WebApp.getRequestDispatcher(WebApp.java:1464)

at com.ibm.ws.webcontainer.webapp.WebApp.getRequestDispatcher(WebApp.java:1423)

at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)

at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)

at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)

at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)

at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)

at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:615)

at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)


--------------------


Same result whether or not I request realm support and whether or not I
configure access to the LDAP server via SSL. The WebSphere Portal
server and the Active Directory server should be reasonably "clean"
because both were installed afresh for the purpose of setting this
deployment up (it's a test deployment). It's using the default
Cloudscape database.

Any ideas what I've done wrong?

--
AlexH
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message951721.html

jonmadison

unread,
May 31, 2006, 7:59:01 PM5/31/06
to

i am currently having the same issue (after transferring from cloudscape
to Oracle). did you ever have this resolved?

Thank you.

j.

AlexH wrote:
> [B]I'm trying to configure a WebSphere Portal 5.1 installation to use

> Any ideas what I've done wrong? [/B]

--
jonmadison

jonmadison

unread,
May 31, 2006, 9:21:02 PM5/31/06
to

for anyone else researching and stumbling upon this thread: the solution
is that you must enable JServer/Oracle JVM in your database.

see http://tinyurl.com/lr69f

jonmadison wrote:
> *i am currently having the same issue (after transferring from


> cloudscape to Oracle). did you ever have this resolved?
>
> Thank you.
>

> j. *

0 new messages