Problems configuring mobile administrator

[Former Member]

Hello,

I am trying to configure mobile administrator in netweaver administrator.

I followed MI25_SPS18_Inst_NewTech guide.

When trying to create RFC Connections ME_MONITORS_METADATA_DEST and ME_MONITORS_MODELDATA_DEST in WebDynpro content administrator I get an following exception creating JCO connection for ME_METADATA_DEST:

Failed to create new JCO client connection ME_MONITORS_METADATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:149) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:344) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for ME_MONITORS_METADATA_DEST at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:678) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:229) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.(JCOClientConnection.java:111) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:147) ... 33 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:587) ... 38 more

If I reenter content administrator after closing and reopening the browser window, the connection is shown as active, but a connection test fails with message

"com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection."

If I try to change this connection (which is present in SLD then and shown as inactive in content administrator) I get a success message stating "JCo destination 'null' was successfully updated in SLD".

The connection then is shown as active in content administrator, but a test fails again.

As a result mobile administrator does not work

Any suggestions what I'm missing/doing wrong?

UPDATE:

I managed to create the connections so that the test is sucessful, by setting (and using for connection) a logon group in ABAP-Stack,but the main Problem reamins: Mobile administrator is unusable as

- page hierarchy grouping gives error: "Exception in method getHierarchy."

- page parametersets gives errors: "com.sap.engine.services.ejb.exceptions.BaseEJBException: Exception in method getOVSConfigurationTemplateServiceList.

java.lang.NullPointerException "

- page mobile components does not show any components

- page mobile archive converter shows message:

"Lesen initialer Einstellungen von Middleware nicht möglich" (Reading of initial settings from middleware not possible)

and so on...

Any help is apreciated

regards

Niels Oberbäumer

Message was edited by:

Niels Oberbäumer

[satyendra_dhar · Accepted solution]

Hi Niels,

Definetly this is the problem with SAPJRAFactory_EN or DE please check the properties again.

Please go through the link available in my previous reply and make the properties correct.

Check for the following entries according to your installation type-:

Standard Installation (Not a Cluster)

Parameters - Value

SAPClient - <Client>, for example, 000

ServerName - <Server Name>, for example, bcemain.wdf.sap.corp

<b>PortNumber - <System Number>, for example. 01</b>

Language - <Language Key>, for example, EN

UserName - <User Name>.use service user with RFC Autorizatn

<b>Password - <User Password></b>

Installation on a Cluster

Parameters - Value

SAPClient - <Client>, for example, 000

SystemID - <System ID>, for example, BCE

MessageServer - <Message Server>, for example, bcemain.wdf.sap.corp

Language - <Language Key>, for example, EN

UserName - <User Name>. service user with RFC authorization

Password - <User Password>

Restart the engine after making the settings correct.

Regards,

Satyendra

[Former Member]

Hello,

thanks for your help, I had missed to set the PortNumber parameter.

best regards

Niels Oberbäumer

[Former Member]

Hello,

looking into ST22 was a good hint, I really had authorization failures.

Just to be sure that there are no more authorization problems I assigned SAP_ALL to the user.

Effect is: No more dumps, but behaviour of mobile administrator did not change.

@Satyendra Dhar: The message shown in archive converter was already at the end of my initial post:

- page mobile archive converter shows message:

"Lesen initialer Einstellungen von Middleware nicht möglich" (Reading of initial settings from middleware not possible)

regards

Niels Oberbäumer

[Former Member]

Have a look in transaction st22 if any runtimerror occured. i had the same problem due to some missing rfc authorizations.

at least this error can be solved by assigning the right authorizations:

Lesen initialer Einstellungen von Middleware nicht möglich

have a look for RFC_NO_AUTHORITY warnings.

Philipp

[satyendra_dhar]

Hi Niels,

A BaseEjb exception can only occur when middleware in not reachable.

Reason and solution for the above are-:

1. SAPJRAFactory_LANG(i e EN) settings are not correct, make them correct according to your installation type of J2ee-Engine (Cluster or Standalone).

Here is the link to configure it-:

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/1d7d843fce3566e10000000a11466f/frameset.htm

2. Check if your user (Configured in SAPJRA) has sufficient Authorization in middleware, Please check for the role S_RFC.

3. Restart the engine after doing above steps.

If you get the same error again then please send the property list you set in SAPJRA.

Also copy the message if any you are getting on MobileArchiveConverter screen.

Please reward points if this helps!!

Regards,

Satyendra