Null pointer while maintaining JCO destination

[Former Member]

Hi Gurus,

When i tried to maintain the JCO destination in webdynpro i get Null pointer exception.

I've checked the SLD connection and it is working fine. The Visual administrator CIM client test was succesfull.

I've created a JCO previously and that JCO test connection is working fine. But now Editing that JCO also gives the same error.

Kindly help in this regard.

java.lang.NullPointerException

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)

at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)

at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)

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

at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)

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

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)

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

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

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

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

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)

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:401)

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

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

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

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

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(AccessController.java:207)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

In the default trace i can find these errors.

#1.5^H#001D0910D3F700670000002A0000596A00044C01B28108BF#1209470080321#com.sap.engine.services.security.roles.SecurityRoleImpl##com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_ADMIN#234##ssscvbid.corp_SCV_6614950#J2EE_ADMIN#0c74228015e311ddccdf001d0910d3f7#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.ERROR#sap.com/com.sap.lcr*sld#LcrUser# #1.5^H#001D0910D3F7004C000000250000596A00044C01B283EC9A#1209470080511#com.sap.engine.services.security.roles.SecurityRoleImpl##com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_ADMIN#235##ssscvbid.corp_SCV_6614950#J2EE_ADMIN#0c9a482015e311dd876d001d0910d3f7#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.ERROR#sap.com/com.sap.lcr*sld#LcrUser# #1.5^H#001D0910D3F7004D000000210000596A00044C01B286ABDA#1209470080691#com.sap.engine.services.security.roles.SecurityRoleImpl##com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_ADMIN#236##ssscvbid.corp_SCV_6614950#J2EE_ADMIN#0cb5bf6015e311dd963e001d0910d3f7#SAPEngine_Application_Thread[impl:3]_18##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.ERROR#sap.com/com.sap.lcr*sld#LcrUser# #1.5^H#001D0910D3F70061000000270000596A00044C01B289A982#1209470080887#com.sap.engine.services.security.roles.SecurityRoleImpl##com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_ADMIN#237##ssscvbid.corp_SCV_6614950#J2EE_ADMIN#0cd3a7a015e311ddb6e4001d0910d3f7#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.ERROR#sap.com/com.sap.lcr*sld#LcrUser#

#1.5^H#001D0910D3F70063000000250000596A00044C01B28C66B7#1209470081066#com.sap.engine.services.security.roles.SecurityRoleImpl##com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_ADMIN#238##ssscvbid.corp_SCV_6614950#J2EE_ADMIN#0cef1ee015e311dd9ea7001d0910d3f7#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.ERROR#sap.com/com.sap.lcr*sld#LcrUser# #1.5^H#001D0910D3F70050000000B10000596A00044C01B2901E4A#1209470081310#com.sap.engine.services.security.roles.SecurityRoleImpl##com.sap.engine.services.security.roles.SecurityRoleImpl#J2EE_ADMIN#239##ssscvbid.corp_SCV_6614950#J2EE_ADMIN#0d0bcea015e311dda9dc001d0910d3f7#SAPEngine_Application_Thread[impl:3]_7##0#0#Error#1#/System/Security/Audit/J2EE#Java###: Authorization check for caller assignment to J2EE security role [ : ].#3#ACCESS.ERROR#sap.com/com.sap.lcr*sld#LcrUser#

#1.5^H#001D0910D3F70070000000290000596A00044C01B290461B#1209470081319#com.sap.tc.webdynpro.sessionmanagement#sap.com/tc_wddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#J2EE_ADMIN#150##n/a##4e1dc93015e211dd96fc001d0910d3f7#SAPEngine_Application_Thread[impl:3]_38##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of Web Dynpro application . The causing exception is nested.

[EXCEPTION]

Answers will be rewarded

Regards,

Karthik Vembu

[Former Member]

Hi Anil/nikhil,

Thanks for the reply... I've tested the CIM client settings in Visual admin and it is successfull.

When i click the create Jco or Maintain Jco connection in the webdynpro console it is giving these errors.

Let me know if there are any solutions.

Regards,

Karthik Vembu

[Former Member]

Hi Karthik,

Have you find the solution for the error. If you fix the error then please post the solution.

Thanks,

Abdul

[Former Member]

Hi,

First You Configure SLD Correctly.If You Have ECC And BW.You Maintaing Two WEBAS ABAP Systems.

You Create WEB AS ABAP System In SLD And Maintain Connection Properties Of ECC.And

Similarly For BW Also.

The Given Below Links To Help You SLD Cofiguration For J2EE

http://www.sapsecurityonline.com/solution_manager/solution_manager_sld.html

/message/5050606#5050606 [original link is broken]

3.If You Want To Create JCO Destinations.You Go To Login Portal

Content Administration->Webdynpro->Create JCO Destinatiion

A.General Data -> Specify Model Name,Client And JCO Pool Configuration

B.Specify J2EEE Cluster

C.Destination type

Data Type-> Application DataModel,Dictionary MetaDataMetadata

Destination Type->Load Balancing Or Single Server

D.Specify Either Application Server Or Message Server

E.SecurityUsername,password,confirm password,language

F.SummaryWhole Information

Similarly Metadata Created Follow Same Steps As Above

After Creating JCO Destinations, Go For Maintain JCO Destination And test The JCO Destinations Works Fine Or Not you Con Test.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-tec...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c51...

http://help.sap.com/saphelp_nw04/helpdata/en/77/931440a1c32402e10000000a1550b0/frameset.htm

It's Useful Rewards Points

Bye

Thanks

SubbaRao

[nikhil_bose]

go to http://<server>:<port>;

\webdynpro \content administrator

click Maintain JCo Connections and find your project from the data source dropdown menu.

your JCo destinations are listed there. test & ping both connections and post the error

nikhiL

[Former Member]

Hi Karthink,

According to the trace file i think there's a problem with the JCo you have created.

Please check the following process and configure SLD properly.

Configure SLD for JCo and Creation of JCo Destinations

To create JCo connections you need to configure SLD (System Landscape Directory) first and then create JCo destinations.

First let’s see as how to configure SLD.

Start Visual Administrator.

To start it

1) Go to Server Installed path i.e. usr\sap\<systemid>\<systeminstance>\J2ee\admin

2) Choose go.bat and start it.

3) Under Global Server Configuration, choose <Serverid>.

4) Choose Services under it.

5) Find SLD Data Supplier.

6) Under System Landscape Directory select HTTP Settings.

7) Give all the required fields like Host Name, Port Number, User Name and Password.

8) Similarly choose CIM Client Generation Settings and give Host Name, Port Number, User Name and Password.

9) You can test the SLD is configured properly or not. Just click CIM Client Test.

10) Save the settings and close Visual Administrator.

Now that you have configured SLD through Visual Administrator, we can create JCo Connections. To create JCo connections

1) You will need Super Administrator permissions to create JCo’s.

2) Log on to the Portal.

3) Go to Content Administration &#61664; Web Dynpro

4) Since we have configured SLD, now we can see a button to “Create JCo Destination”. Click it

5) Now you can observe Create new JCo Destination on right side panel.

6) Give the Following Details.

a) General Data:

Name: Give the name of JCo

Client: Give the Client number to which system you want to create JCo for. Click Next.

b) J2EE Cluster: Check the Use Local J2EE engine. Click Next.

c) Connection Type: Select Dictionary Meta Data. Click Next.

d) Application Server Connection: Select the existing Message Server and Logon Group.

It might sometimes happen that Message Server and Logon Group is not configured to configure them, follow the process

For Message Server:

i. Log on to SDL through portal i.e. http://<servername>:<portnumber>/sld

ii. Choose Technical System. Click it.

iii. You will observe New Technical System button, click it.

iv. System Type: Select Web AS ABAP , if you want to connect to R/3 System and incase you are using Java application use Web AS Java

v. General: Log on to R/3 System through SAP Log on pad. Go to System &#61664; Status, check for SID, Installation Number and Database Host Name.

vi. Central Servers: Give Host Name and Port Number and Instance Number.

For Logon Group:

i. Click on Add New Logon Group, this will open a row in the table.

ii. Log on to R/3 through Logon pad and get Logon Groups ids and the transaction code is “SMLG”.

vii. Application Servers: Click on Add Application Server and then give Host Name and Instance Number of R/3 System.

viii. Clients: Give Client number (System id) and Logical Client Name (which we can get from SMLG code). And click finish.

7) Message Server Connection:

i. Name: Give the logon name of R/3 System

ii. Password & Confirm Password: Give appropriate password of R/3 System.

8) Click Finish.

regards

Anil