can't access IDM URL (http://hostname:50000/idm)

[Former Member]

HI!

<br><br><br>

If I try to access the IDM URL I receice an error ( java.lang.NullPointerException):

<br><br><br>

Detailed Exception Chain

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(id=7245dbd16afb11dec682000c29b3ddda, name=com.sap.idm.wd.wf.appl.workflow.Idm). The causing exception is nested. RID=724391e06afb11deb7de000c29b3ddda

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:680)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:239)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)

at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)

at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)

at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)

at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)

at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)

at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:425)

at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)

at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)

Caused by: java.lang.NullPointerException

at com.sap.idm.wd.wf.entrysearch.EntrySearchComp.clearEntries(EntrySearchComp.java:501)

at com.sap.idm.wd.wf.entrysearch.EntrySearchComp.wdDoInit(EntrySearchComp.java:146)

at com.sap.idm.wd.wf.entrysearch.wdp.InternalEntrySearchComp.wdDoInit(InternalEntrySearchComp.java:187)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:160)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)

at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:253)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:371)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:273)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createInstanceIfDemanded(ComponentUsage.java:986)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getViewManagerFor(ComponentUsage.java:650)

at com.sap.tc.webdynpro.progmodel.window.EmbeddedInterfaceView.getUninitializedEmbeddedViewManager(EmbeddedInterfaceView.java:51)

at com.sap.tc.webdynpro.progmodel.window.InterfaceView.manageEmbeddedViewManager(InterfaceView.java:137)

at com.sap.tc.webdynpro.progmodel.window.InterfaceView.initController(InterfaceView.java:55)

at com.sap.tc.webdynpro.progmodel.window.EmbeddedInterfaceView.initController(EmbeddedInterfaceView.java:41)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)

at com.sap.tc.webdynpro.progmodel.window.ViewManager.getView(ViewManager.java:667)

at com.sap.tc.webdynpro.progmodel.window.ViewManager.bind(ViewManager.java:538)

at com.sap.tc.webdynpro.progmodel.window.ViewManager.getView(ViewManager.java:684)

at com.sap.tc.webdynpro.progmodel.window.ViewManager.bindRoot(ViewManager.java:562)

at com.sap.tc.webdynpro.progmodel.window.ViewManager.init(ViewManager.java:182)

at com.sap.tc.webdynpro.progmodel.window.InterfaceView.manageEmbeddedViewManager(InterfaceView.java:141)

at com.sap.tc.webdynpro.progmodel.window.InterfaceView.initController(InterfaceView.java:55)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:364)

at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)

at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:557)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1338)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:146)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)

at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)

at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)

at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:74)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:252)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:677)

... 48 more

<br><br><br>

Any help, please ?

<br><br><br>

regards

[Former Member]

BTW - This is done in the Visual Amin @ services->ConfigurationAdapter->apps (in the right hand pane)->sap.com->tc_idmjmx~app->appcfg-> NOW GO EDIT MODE->right click on the propertysheet application.global.properties and select change.

[Former Member]

Hi!

I have observed that my IDM_DataSource (JDBC Custom dataSource) is in the status RED after a SAP restart.

I suppose this is related in some way to my problem...

If I delete and recreate the IDM_DataSource it became GREEN at the beginning, but every time I restart SAp it's status became RED.

regards

PiCo

[Former Member]

Pierfrancesco,

I can offer some config to check that has caused us issues when we tried to connect the portal to IdM:

Make sure the data source is setup correctly in NW, and that the IdM deployment references it correctly.

Make sure the IdM deployment uses SQL Native client and that the JDBC connection is set up properly.

Hope this helps,

-Geoff

[Former Member]

Hi Geoff,

any suggestion will be apreciated!.

I have followed the installation guide (UI guide) until page 44 where we have:

At page 44 there is:

Initial configuration

Authentication of the users logging on to the Identity Management User Interface is done by the

User Management Engine (UME). What parts of the Identity Management User Interface is

available depends on which UME actions are assigned to the user. The UME action

sap.com_tc_idmjmx~ump.idm_authenticated gives general access to the application and

enables the tab "Self Services".

Before running the User Interface a role needs to be created, giving any authenticated user a

general access to the Identity Management User Interface. To do so, you must have a user that

has a permission to create and assign roles when logged-on the UME.

For details, see SAP NetWeaver Identity Management Security Guide.

Adding user to the identity store

Users must also have an entry in the Identity Center's identity store with an MSKEYVALUE

identical to the user ID in the UME. Whether this user is created in the Identity Center before or

after the role creation is not of importance.

I'm not sure on how to do this last step Adding user to the identity store. The guide is not clear.

Regarding the rest I'm quite sure to have done right in according to the installation on UI.

Any suggestion ?

regards

[Former Member]

What exact verison you use on the Java AS?

As for adding users:

If you don't have a user you simply get an error "Entry does not exist" - but not such an exception.

[Former Member]

My System is:

DB: MS SQL 2005

SAP: NW 7.1 CE EHP1

IDM installation: all in same server

THX

[Former Member]

Pierfrancesco,

I can help you with this:

>

> Hi Geoff,
> any suggestion will be apreciated!.
> Adding user to the identity store
> Users must also have an entry in the Identity Center's identity store with an MSKEYVALUE
> identical to the user ID in the UME. Whether this user is created in the Identity Center before or
> after the role creation is not of importance.
> 
> I'm not sure on how to do this last step Adding user to the identity store. The guide is not clear.
> 
> Regarding the rest I'm quite sure to have done right in according to the installation on UI.
> 
> Any suggestion ?
> 
> regards

In the IdM management console drill down through the hierarchy until you get to the Identity Center node. The second tab on this node is called Workflow. On this tab there is an Add User button, which lets you create a new user record in the identity center by specifying the mskeyvalue of the user. As the guide says, create the user with the same mskeyvalue as the id of the user in UME. When I set up a new identity center I always add my own id to it straight away.

Then the user id will need to have the idm_authenticated ume role in the portal - your basis or sap security team can do this.

As far as the other issue you're having with the IdM datasource in the portal, I'm afraid I can't offer much help with that - I'm trying to learn the portal myself with this new version.

-G

[Former Member]

Hi Geoff....

my problem is that I cannot access to IDM....

How can I do your suggeston with no access to http://hostname:50000/idm ??

When you say IdM console you mean something else ?

please let me kow. I'm stopped here from more than a week !!

Regards

[Former Member]

Hi

Can you give the Settings, like JDBC String?

Also check the other options with the manual.

Furthermore:

Go to: \usr\sap\<System ID>\<Instance Name>\j2ee\cluster\server0\bin\ext\<driver name>

Make sure that the jar is not a 0bit file.

HTH

Chris

[Former Member]

Hi Christian!

to answer to your question:

in my installation the path E:\usr\sap\IM1\J00\j2ee\cluster\server0\bin\... DO NOT EXIST

I have the jdbc driver (sqljdbc.jar) under :

E:\usr\sap\IM1\J00\j2ee\cluster\bin\ext\SQL2005

and the file is not empty. it's size is 570 kb

In addiction I have this stange config in the Application resource Overview of my NWA

the JDBC driver configuration, show me a path to the JDBC DRIVER (created in auto when the driver is created) that is:

E:\usr\sap\IM1\J00\j2ee\cluster\server0\.temp\dbpool\_SQL2005\sqljdbc.jar

BUT this path do NOT exist on my server !!!

Any suggestions ??

regards

PiCo

[Former Member]

>

> Hi Geoff....
> my problem is that I cannot access to IDM....
> How can I do your suggeston with no access to http://hostname:50000/idm ??
> 
> When you say IdM console you mean something else ?
> 
> please let me kow. I'm stopped here from more than a week !!
> 
> 
> 
> Regards

Pierfrancesco,

I'm talking about the IdM Management Console - this is where you create and manage the IC, tasks, jobs, etc.

I'm afraid I am not sure how to help with some of the portal issues you reported, but since you raised the question on how to add a user to the IC I wanted to document that part for you.

The portal front end in 7.1 is great but it's been challening for us as well. The idm connection must be deployed properly, the user must exist in IdM and in UME, they must have the correct role(s) in UME and priv(s) in IdM...

I have a document that covers a lot of the portal config, I'll try to find it and attach it here if the forum allows, otherwise I'm not sure how to get it to you.

-G

[Former Member]

I found the document on Netweaver config, if you think it might be helpful let me know how I can get it to you.

[Former Member]

Hi Geoff!

I can open the management Console, but at the moment there is no MXMC database connected.

I tried to create a new one (but with no help from guide) but I'm not sure on HOW to create.

So the connection do not work...

Can you attach the document somewhere or show me where to find it, please ?

pierfrancesco.cocco_REPLACEWITHAT_realtech.com

regards

PiCo

Edited by: Pierfrancesco Cocco on Jul 16, 2009 8:52 AM

Edited by: Pierfrancesco Cocco on Jul 16, 2009 8:53 AM

[Former Member]

Sent both the webdynpro config guide and the overall install guide which should help you to configure the Identity Center

[Former Member]

Hi!

well...

after I have:

manually started some services related to the IDM and UPgraded the IDM database (with the latest version), now the situation is chanched... and even the error.

Now my jdbc connection is GREEN, but if I try to log IN the IDM (http://hostname:50000/idm)

now I have:

Wellcome
	No tabs are available
	No identity stores are defined for workflow

any suggestions ?

regards

PiCo

[Former Member]

Sounds like you just need to follow the instructions I sent to create the database and then connect to it from within the management console and you will be all set.

Again, don't forget that each user needs the idm_authenticated ume role in the portal AND needs to exist in the IC as I detailed above.

[Former Member]

What Identity Store you have in your JMX config?

[Former Member]

Hi,

I encountered the similar problem when accessing the IDM URL and get the message "No identity stores are defined for workflow".

I have already configure the Management console to connect to the IDM DB and also add my AS-JAVA Administrator ID according to the steps mentioned in page 39 of the "Installing and configuring the IDM User Interface" guide. I have also created the the role with the IDM action "idm_authenticated" and assined to the Administrator ID. But still get the above mentioned error when I tried to login to the IDM URL.

Appreciate your help.

Many thanks.

Rgds,

Leonard

[Former Member]

Hi all,

Manage to resolve my issue by changing the com.sap.idm.jmx.idstoreid from value '2' to '1' in visual admin.

Rgds,

Leonard