JCo connection problem : Urgent

[Former Member]

Hi ...

I am having a problem while trying to create a JCo connection with Dictionary metadata settings. It gives an RFC error. Can anyone tell me how to rectify this?

Satish.

[Former Member]

Hello Gregor, thanks for your response.

As I have posted in another thread....

My 'services' file has the entry sapmsBSP 3600/tcp with a new line after the entry. I have tried 'PUBLIC' and 'SPACE' both upper and lower and mixed case. Again,

I go to the SAP Logon pad, click the GROUPS button, enter System ID and message server, then click Generate List, I get a window opening up saying that "Message Server could not find any Groups"

I see the groups I have created when I return to transaction SMLG, but still can't see them from the stack.

Any further thoughts?

Thanks

Russ

[Former Member]

Hi,

I am facing the same problem while creating the JCO connections.

While creating the JCO Application connection , I am using the parameters for connecting to a remote R/3 system. I am able to connect this server with single server settings.

While creating the Meta data connection , I am specifying the same remote R/3 system for connection. Here i am getting error saying that can not find the message service sapms<SID> on the remote machine. When i checked with the basis guys , they told that the system has been configured for single server. No message server configuration is done for load balancing. In this situation what should i do now?

Thanks,

Mital.

[gregorw]

Hello,

I've posted this Message to the Forum:

asking for the reason why the Meta data connection must be a Connection through a Gateway server. Unfortunately I didn't get an answer yet.

Regards

Gregor

[Former Member]

Hi Gregor,

Can you please tell me the configuration for the message server. I have installed Sneak version 6.40 (90 days trial version). I am totally new to SAP.can you please guide me in this situation. SAP R/3 system installed is configured as a single server. I am not able to find the message service sapms<SID> on that system when i am trying to connect.

Thanks,

Mital.

[Former Member]

Hi Satish,

I am facing the same problem.Please let me know if you are able solve this issue.It would be great if you can send me the instructions to fix this.

[Former Member]

I used the SAP NetWeaver '04 Post-Installation Guide to set up SLD on the Sneak preview WebAS installation. You can find this at

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/documents/a1-8-4/sap system landscape directory on sap web as java 6.40.pdf

or try this shorter url -->

http://smallurl.com?i=14968

[gregorw]

Hello All,

I also had this problem. As I described in this article , it is only possible to use a message serer (load balancing) connection to get the meta data. My solution was to add this line to my local services file (C:\Winnt\system32\drivers\etc\services):

sapmsWA4 3200

Where WA4 is the instance Name of my backend server.

Regards

Gregor

[Former Member]

Hi Gregor:

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 fiel sapmsBSP 3200, but this makes it not possible to connect to sap since SAP listens on port 3200. Any thoughts? Can I spoof my system to think its has load balancing?

Thanks

Russ Wagner

Canada

[gregorw]

Hello Russ,

let's use the SAP Logon Pad to test if you can make a new Connection using the groups function. First login to your MINIWAS 6.2 and start Transaction SMLG and check that you have a valid Logon-Group. More information could be found in the SAP Help at http://help.sap.com/saphelp_webas610/helpdata/en/c4/3a64b4505211d189550000e829fbbd/frameset.htm.

Then open you SAP Logon Pad and click on the button Groups..., enter the Instance name of your MINIWAS 6.2 System in the Field System-ID and enter the Hostname of your MINIWAS 6.2 System in the Field Message-Server. Then click on create list. Now you should see the Logon Group(s) you just have defined. Click on add and try to connect through this new connection.

If that is working, also your connection through the Webdynpro Content Administrator should work.

Regards

Gregor

[Former Member]

Satish,

Here is a solution from Frank Winkler who posted his solution on Apr 21, 2004 2:53 AM. Hopefully this solves your issue. Please see Frank's message attached below:

-

---

frank Winkler

Posts: 4

Registered: 3/1/04

Re: WEB Dynpro JCO connection problem

Posted: Apr 21, 2004 2:53 AM Reply

Hi,

it seems that your JCO-Destinations are not defined in a proper way..

It is important, that you use two JCO-Destinations;

one for the Dictionary Data and the other one for the Application-Data.

You have to define two differnt Destinations, one of Type 'Dictionary Meta Data' and one of Type 'Application Meta Data'. Both point to the same R3 System!

The first one could access the R3 System only via MessageServer, so you have to take care, that accessing the R3-System via MessageServer must work properly.

Hope this helps, Frank.

[Former Member]

Hi,

I know that I need to create two JCo connections. But, when I am trying to create one for Dictionary metadata, I am getting an RFC error. Do I have to do something in SAP to handle this? Please suggest.

Satish.

[Former Member]

Hi,

i suggest you get the RFC-Error in the WebDynpro Console?

Is that right?

Can you post the exact/complete Error Message.

Did you check to logon to the R/3 Sytstem via Message-Server? You can use your SAP-Logon to test this.

In your R/3-System you have to maintain your Logo-Group via SMLG, and by the way Java is cas-sensitive regarding the Name of the Logon-Group you've entered in your JCO-Destination Definition.

(i have created a 'public' Group in my R/3 via SMLG, but JCO always wants to use the 'PUBLIC' one, which didnt work, because JCO can't find the 'PUBLIC' Group. After redifining my R/3 Group from 'public' to 'PUBLIC' everything works)

Hope this helps.

Frank

[Former Member]

Hi Frank,

I did maintain the settings in SMLG, but still am getting the error. I maintained with PUBLIC which is used in the JCo connection. But still gives an error.

com.sap.mw.jco.JCO$Exception:(102)RFC_ERROR_COMMUNICATION:Connect to Message Host Failed"

[Former Member]

Hi Satish,

keep in mind that i also need two days to get JCO-Communication to work...

It seems that your JCO Connection couldn't connect to the message server.

Did you check accessing the R/3 System via MessageServer with your SapLogon?

Have you maintained an corresponding entry in your service file (C:\WINNT\system32\drivers\etc) in a way like

sapmsR45 3600/tcp # my entry for connecting our R45

Explanation:

R45 is our R/3 Development-System

36xx is the coressponding Port for communication, where xx is the systemnumber of the R/3-System

This is my last idea, to solve your problem. Hope this helps.

Frank

[Former Member]

Hi

I think I'm stuck up with the same problem. I seem to be creating both types of connections in the SLD. But when I goto Content Administration, it reports an error saying 'No application servers are maintained in the SLD' and same for the message server.

What am I missing? Please help me !

Thanks & Regards,

Rajit Srinivas.