Multilingual JCO connection setup

We want to make our Portal multilingual with the following setup. We have Portal 7.31 installed with following technologies,
- Java web dynpro applications using JCO destinations using user mapping (one hard coded userid/password), language specified in JCO destination is English.
- DynPage HTMLB applications using System landscape connection to SAP using user mapping (one hard coded userid/password). "Master locale" specified in the Landscape object is English
I wanted to change the language attribute in the JCO connection and landscape object so that the RFCs know the language required to send the data back. For JCO connections I can make another french language JCO destination and use that when user switches to french, probably I can do the same thing in case of system landscape object. Is this the right approach?
Would leaving the JCO destination language empty use the Portal user's language preference? Even though I am using a hardcoded userid/password?
Any help and direction appreciated.

hi,
In the J2EE Engine the RFC functions are implemented by the JCo RFC Provider service, which is used for processing ABAP to Java requests. A feature is provided for receiving calls from the SAP systems this is done by registering the J2EE Engine as a RFC destination.
The JCo RFC Provider Service processes calls from the SAP systems. It dispatches the calls to a stateless session bean, which is registered in the J2EE Engine naming system. By naming convention the JNDI name used is identical to the name of the SAP function module.
cheers,
jo

Similar Messages

All the sytem objects & JCO connections not working in Portal

Hi,
Can any body tell me,
Last we we had copied the client copy from EIK 100 ( Production R3 server ) to EIT 900( Testing R3 server). From that movement.All the System object which are created in portal server to access the EIT 900 in R3 servers not giving the data .Even the JCO connections which are used to connect the the EIT 900 is not giving the data.
So , cany any body have idea where we need to check , how to trouble shoot this problem.
Regards
Vijay

Hi Brad,
Thanks for the reply.
Can u please tell me , both the servers are have the sld connection.
SLD connections are in the following setup.
TestServer(Portal) ---> EIT900(R3 Test Server)
Production(Portal) --->EIK100(R3 Production Server)
Can u please tell where will be the problem how i need to trouble shoot.
i have added one image of the JCO connections, all the connections got disabled. wht might be the reason.
I have added the bitmap of JCO connections in the following path for your reference.
JCO connections disabled.gif
Regards
Vijay

Authentication method for JCo connection in XSS installation

Hi All,
I have a query which perplexes me. I am implementing XSS (ESS/MSS) on SAP Portal EP6 SR1 with an ECC5 backend for prototype purposes.
When I follow SAP's help steps to setup JCo connections, it states that for the metadata connection you should use a security authentication method of 'User/Password', but for the application data connection you should use a security authentication method of 'Ticket'.
Does anyone know why the difference in methods here? Is it possible to use 'User/Password' for both? Any thoughts would be appreciated.

Hi john,
User -ID /Pwd method can be used to access the backend for both types of Data as per your scenario.
User -ID /Pwd method and logon tickets both can be used to access data in backend.
The difference lies in the scenario with which you are accessing the back-end.
If all your portal users are same as backend users then you can select Logon ticket methods.
If they are going to be different then you need User-ID /Pwd method .
Check the following link to get a clear picture:
<a href="http://help.sap.com/saphelp_ep50sp2/helpdata/en/4d/dd9b9ce80311d5995500508b6b8b11/frameset.htm">Scenario to use type of SSO</a>
Hope it helps.
Regards,
Vivekanandan

JCO connection error:Couldn't create JCOClientConnection for logical System

Hi All,
We are facing a production outage issue.
We have a Federated Portal Network setup where one of our producer goes down automatically (seems on heavy load).
On this Producer server we have 3 Web Dynpro applications deployed and default trace is full with JCO connection error   saying Could   not create JCOClientConnection for logical System: CSVMR_WD_MODELDATA_DEST.
We had issue with max allowed JCO connections so we changed the below mentioned parameters for JCO connection settings in portal:
u2022     Minimum value of JCo Pool Size in total = 80
u2022     Minimum value for CPIC_MAX_CONV per SAP Web AS = 320
u2022     Maximum Number JCo Connections = 160
Please let us know if we are missing on some settings, any help in this regard is appreciated.
Regards,
Priyanka

Hi,
As you have already increased the maximum number of connections/pool size but still you are facing this problem. I would suggest you to check the web dynpro application which might not be able to release/disconnect the JCO connection.
Please check this [Thread|How to close a model object connection for Adaptive RFC?; for more details.
Regards
Puneet

JCO Connection giving error when try to edit or preview it.

Hi,
We have in our project PD6(Portal) only java stack & CD1(ECC6.0) system is acting as respective backend.
The JCO connection has already been configured for it,but when I try to edit or preview one of the JCO connection it is giving below error.
Error :
500   Internal Server Error
Failed to process request. Please contact your system administrator.
Root Cause
The initial exception that caused the request to fail, was:
   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:251)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
    ... 45 more
Detailed Error Information
Detailed Exception Chain
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:251)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
     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:321)
     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:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Please let us know your input on this.
Regards
Nilesh

Likely Cause would be some fields for the backend system used to setup the JCO destination are not updated properly (i.e.
empty) in SLD. Once you have configured your SLD please also ensure that you have selected the relevant u201CMessage Server Connectionu201D. The Message Server, System Name and Logon Group must not be left empty. Ensure that SLD contains up-to-date and complete information about backend systems.
Check that the SLD is setup properly, check whether you have registered the system through config tool into SLD If not please register system into SLD so that all the parameters are transfered to SLD automatically. You need to do this even the u201CTest Connectionu201D to SLD is successful. Once you are registered you should be able to create the JCO destinations with out any issue.
Thank you.
Shyam

Jco connection Test error

Hi Exports,
When I test the Jco connection below error message getting,
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=csslecc GROUP=SPACE R3NAME=ECC MSSERV=sapmsECC PCS=1 ERROR service 'sapmsECC' unknown TIME Fri Aug 28 04:38:05 200 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2: service 'sapmsECC' not found SYSTEM CALL getservbyname_r COUNTER 1
Kindly help me to solve this problem.
Thanks
Jibin.

Hi Jibin
This is mostly likely due to JCO or network setup rather than the ESS/MSS application
Please see the following link
http://help.sap.com/saphelp_nw2004s/helpdata/en/f6/daea401675752ae10000000a155106/frameset.htm
In particular check network services as per note
Note 52959 - sapms..., sapdp.., sapgw.. unknown (or not found)
Please check JCO connection settings as well as per
Note 723562 - SAP Java Connector: Configuration and Requirements
Please check availability of message server and that user terminal can ping Portal server
and Portal server can ping ECC server
Hope this helps
Best wishes
Stuart

Problem testing Metadata in JCO connections (Flightlist)

Hello:
I have the sneak preview WAS Server Java 6.4 (J2EE) and I have also installed the MINIWAS 6.2. I have successfully setup the SLD and imported the 2 zip files. I can start SAP, and through SM59 test connect to SLD_NUC. I can use RZ70 to 'send' info. I can successfully load, build, archieve the Flightlist demo. I can go to http://localhost:50000/Webdynepro/welcome... and create and test the Model data under JCO connections (not using load balancing). When I test 'metadata_dest' I get the RFC_error_communication Group Public not found. I tried your fix (services file sapmsBSP 3200 from another post), but this makes it not possible to connect to sap since I think SAP listens on port 3200. Any thoughts? Can I spoof my single server system to think its has load balancing?
Thanks
Russ Wagner
Canada

Hi,
If in SMLG menu "goto->load distribution" the field "current logon instance" is empty run report RSRZLLG0_ACTUAL without the flag FRCE_SAV...
After the run the field should be the name of your instance...
check with:
lgtst -H pc -S sapmsnsp -D 1
the output should be:
list of reachable application servers
[pc_NSP_00] [pc] [192.168.1.6] [sapdp00] [3200] [DIA UPD ENQ BTC SPO ICM ]
list of selectable logon groups with favorites
[SPACE] [192.168.1.6] [3200] [700]
bye
sambarza

JCO Connection for web-dynpro tutorials (EP 6.0 SP9 downlaod from SDN)

Hello,
I have a question regarding JCO connections for web-dynpro example/tutorials. I have installed WAS 6.40 sneak preview from EP 6.0 SP9 download from SDN. Installation instruction says: Choose "No SLD available"
but the web-dynpro example/tutorial asks to create JCO connections by going to web-dynpro -> content admin..etc on http:<host>:50000..Here, all the tabs relating to creating JCO connections appear to be "protected" on my screen. so I can't do anything further. By going to http:<host>:50000/sld, I also tried to add SLD server..but that is not helping. There is some "import" button, but which CIM file (in which folder etc) am i supposed to import for a simple test system? What are the steps for a bare minimum setup so that I can use the WAS 6.20 system at work-place as my backend & try out the web-dynpro examples? Do I really need SLD setup? Where is documentation about all this after one installs the WAS 6.40 JAva? I was expecting it somewhere at least in the eclipse IDE help-documentation..None of the web-dynpro tutorials explain this !
thanks

Thanks everybody.
NagaKishore, after doing all the steps, when I goto
localhost:50000-> web dynpro -> content administartor, and try to "maintain JCO Destinations" I am getting this error: (full stack trace not included)
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
Error stacktrace:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:438)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:634)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:598)
     at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:120)
     at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:238)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

JCo connection broke after deployment

At this moment we do not have setup the JDI environment (we are busy with it). When we do a deploy of Java WD with EAR files through SDM or we do it via NWDS our JCo connection is broken every time.
Initially we have set the JCo connections to 'ticket' but after we make changes to a WD and deploy it via SDM or NWDS the JCo connection is set back to UID/PW. Does anybody have any idea why this happens?
Kind regards,
Dave Arends

Hi Dave,
The configuration for JCO as JCO destinations is done on the content administrator and is independent of the application itself. So I dont understand deploying the application interferes with JCO.
Regards,
Arun

JCO connection pool is exhausted

hi
I am using RFC module in my web dynpro application. When the application is used for sometime, the JCO connection will get exhusted. The JCO connection will not release itself. I can't find any method in web dynpro to release the connection manually. How can I solve this problem?

Hi,
What is scope of the connection. View properties of MODELDATA and METADATA destinations.
You can change the scope of the connection..
or
wdContext.current<BAPI INPUT>Element().modelObject().modelInstance().disconnectIfAlive();
For more ways , give a forum search.. There are a lot of close forum posts.. Gud luc..
Regards
Bharathwaj

Problem with JCo Connection Pool

Hi,
I have a problem with using an RFC Model in my WebApplication. So sometimes the access to the function block works, and sometimes it doesn't work. Now I know, that there is a problem with the connection pool. Look at this message:
com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool WD_X24_MODELDATA_DEST_CPIC_REKTO_DE_useDefinedUser is exhausted. The current pool size limit (max connections) is 10 connections.
So it looks like a problem with closing the JCo Connections after using. Do know where the problem is? Because I'm using many other function blocks with no problems.

Hello,
You need to increase the pool size via Visual Administrator.
Server 0 -> Services -> JCO RFC Connections.
Change the pool size from there. I believe a restart is in order.
Regards,
Jan

Unable to close metadata jco connection

Hi Experts,
when checking the JCo Connection Pools in Web Dynpro Console, I found that all MetaData JCo are in use and unable to disconnect automatically.
the following is metadata jco destination setting
Maximal Pool Size 1
Maximum Connections 5
Connection Timeout 60
Maximum Wait Time 10
how can i do to close these jco connection?

Hi Sidney,
I dont really understand why you want to remove the Jco connections. If you click on the "Remove" button as posted earlier by someone, it will completely remove your Jco configurations and you have to create them again on your own. SO, dont do that.
If you want to disconnect the Jco connection in webdynpro java, we can do that by using the following piece of code at the end of the connection process.
As far as I know, by default the Jco connections gets disconnected after certain time limit. Because, I never had to disconnect the Jco whenever I used one.
wdContext.currentModelElement().modelObject().modelInstance().disconnectIfAlive()
Regards,
Gopal.

How to use a JCO connection pool in an EJB?

Hi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
Lars

Hi *,
I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
Kind regards,
Lars

Single Webdynpro Application with multiple JCO Connection ?

Hi Experts,
I have a strange requirement ......
We have a Webdynpro Application which is connected to
say (using JCO connection)
client:- A
now i want to connect the same Webdynpro application to
Client:- B which is again in the same server as the client A.
Please help me how to handle this.
how it possible to connect a single Webdynpro application to two different clients using JCO Connection.
Please help.
Points would be rewarded to helpful answers.
Regards,
Sanjyoti.

Hi experts
                    We have to use wd application for both client at a same time e.g. as follow
Client A -
> Travel app--->Featches data from A for   employee hired in client A ,in same server as B
Client B -
> Travel app--->Featches data from B for   employee hired in client B , in same server as A
we are using same EP for both client but using diffrent roles for employees of both client.
Please reply asap.

Error while obtaining JCO connection when creating JCO connection

Hey,
im having a problem when creating a JCO connection in the Web Dynpro Content Administrator. Creating the Modeldata (Application Data Data type) JCO Worked but when creating the JCO for the RFC Metadata (Dictionary Meta data) there is a problem:
In step 3.2 Msg server connection I cannot specify a system name and logon group, only the message server can be selected with the dropdown box.
After pushing the finish button i get the following stacktrace:
Failed to create new JCO client connection WD_RFC_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:150) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) 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.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at
com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:95) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_RFC_METADATA_DEST at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) 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:248) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more
We are running WebAS 640 SP 14 on Unix.
Greetings,
Hannes
Message was edited by: Hannes Defloo

Hi
Please configure your SLD. Your SLD holds the system definition. Define a SAP WebAS abap system and then try to create a Metadata connection using WebDynpro content administrator. Now you will be able to see the msg server defined in the dropdown. Also ensure that you have the message server entry in your services file.
Refer these links for SLD
http://help.sap.com/saphelp_nw04/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
Hope that helps.
regards
Ravi

Multilingual JCO connection setup

Similar Messages

Maybe you are looking for