on 05-24-2005 3:02 PM
Hi everybody, i have the following lanscape:
- R/3 4.7 enterprise.
- Solution Manager 3.1
- Portal 6.0 SP9 on WebAS 6.40
and i'm trying to connect a web dynpro application with the R/3 system.
I've done the flight list tutorial and when i execute the app it gives me an exception:
'com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type extern:com.sap.tut.wd.flightlist.model.types.FlightModel:com.sap.tut.wd.flightlist.model.types.Bapisfldat could not be loaded: com.sap.dictionary.runtime.DdException:'
i call the SMGW transaction then i go to: GoTo>Parameters>Display. The gateway is gramsap01 and the service is sapgw01
in the sld configuration i have the following:
under RFC Gateway: server is gramsap01 and service sapgw00(it works to Solution Manager System)
How can i add another RFC Gateway??? because in the J2EE Admin under sld data suplier>runtime>rfc settings i only have that works for solution manager.
And under jco rfc provider>runtime>available rfc destinations i have 2 destinations one for Solution Manager and one for R/3(sapsldapi_<sysid>)
i hope somebody can helps me solve this problem.
thx.
rgds.
P.S: i forgot that in the webdynpro console i have created the JCO connections for the application and tested succesfully.
Gregory(Peck).
Hi Gregory,
You said :
And in the server where are installed EP 6.0 SP9 on WAS 6.40 i have the following entry in SERVICES file:
- sapmsNW1 3601/tcp # SAP System Message Port
Here NW1 is your SAP R/3 system's ID??
If yes then change port 3601 to 3600 and then try it.
Do not forget to restart J2EE Engine.
And also check one blank line after last entry in your services file.
Regards,
Bhavik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gregory,
The problem is you have not made entry in services file for your gateway service "sapms<SID>" where SID is the System ID of your SAP R/3 system.
Do one thing ,
go to windows/system32/drivers/etc folder.
there uyou can find SERVICES file.
In this file make new entry at the last.
sapms<SID> 3600/tcp
After writing this line press enter for new blank line.
Now restart your J2EE server and then check your JCO connection.It will work.
Regards,
Bhavik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ravi, Bhavik, thx.
Ok, in the server where are installed Solution Manager 3.1 and R/3 4.7 i have the following entries in SERVICES file:
- sapmsGRA 3600/tcp # SAP System Message Port
- sapmsGR2 3601/tcp # SAP System Message Port
And in the server where are installed EP 6.0 SP9 on WAS 6.40 i have the following entry in SERVICES file:
- sapmsNW1 3601/tcp # SAP System Message Port
I dont know if i need to push another entrie in these files.
rgds
Gregory.
Hi gregory
Well your Message server has to be configured. The message server information of SAP should be maintained in the services file.
Do you have any kind of Basis Support. If you dont have i will help you out.
What you can do is . Go to C:\Winnt and create a sapmsg.ini file. just ensure u have a entry like
[Message Server]
GR2=<SAP APPlication server name>
Save it. Also check your SAPLOGON.INI. You should have a entry for the Message server. Once you are done. Just try the steps i had mentioned previously to see if it works.
regards
ravi
Hi
That seems to be ok. Now are you able to see it in SAP logon pad when you click on the groups button.
When u click on the groups button enter system id as GR2 and message server should be the name of your R/3 application server and not sapmsGR2. Check and let me know
I will also check if there any other settings to be done.
regards
ravi
Hi greg
I will see what needs to be set for bringing up the logon groups of the message server. Its just a message server config prob and it can be sorted out.
I guess i will have to give the solution tomm.
Meantime check out this link. Talks about Msg server config.
http://help.sap.com/saphelp_46c/helpdata/en/80/897415dc4ad111950d0060b03c6b76/frameset.htm
regards
Ravi
Hi
What are the names of the JCO Connections.
You seem to have a problem with the Metadata.
Flight Tutorial uses "WD_FLIGHTLIST_MODELDATA_DEST" and "WD_FLIGHTLIST_RFC_METADATA_DEST". Check these names properly in your WebDynpro content administrator and see if you are able to test the connections. If you are directly using the tutorial then you have to use these connection names.
Is your SAP R/3 configured as a ABAP Technical System under SLD. Please check that too.
Steps to check :
See if your SLD is configured.
See if a ABAP Technical system has been defined in SLD. This can be configured to point to your R/3.
Check if the JCO Connections are defined properly and use the technical system maintained in SLD.
BTW why do you require to add another gateway. Can you elaborate on that.
Hope that helps you solve your problem. Let us know if you require more clarifications.
regards
ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ravi.
In the webdynpro content administrator for flightlist app are defined the "WD_FLIGHTLIST_MODELDATA_DEST" and "WD_FLIGHTLIST_RFC_METADATA_DEST".
I click on "Test Connection" buttom and it gives me the following message:
"Connection for 'WD_FLIGHTLIST_MODELDATA_DEST' was sucessfully tested with user '<username>'" and the same for "WD_FLIGHTLIST_RFC_METADATA_DEST".
In the SLD page under technical landscape>web as abap is defined the R/3 system. And under administration>server settings>ABAP Connection Parameters, parameter are set for solution manager. And in the namespaces only have one: 'sld/active'.
thx and rgds
Gregory
Hi Kishore. I found that i've been using Application Data. I changed to Dictionary MetaData and it gives me the following error:
'com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=gramsap01 GROUP=PUBLIC R3NAME=GR2 MSSERV=sapmsGR2 PCS=1 ERROR service 'sapmsGR2' unknown TIME Tue May 24 16:40:42 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 MODULE ninti.c LINE 494 DETAIL NiPGetServByName2: service 'sapmsGR2' not found SYSTEM CALL getservbyname_r COUNTER 1'
Do u know why? or what i have to do?
I hope u can help me.
rgds.
Gregory.
Sorry again but i do click Test button right now and gives me the following error(not the same above, similar):
'com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=gramsap01 GROUP=PUBLIC R3NAME=GR2 MSSERV=sapmsGR2 PCS=1 ERROR service '?' unknown TIME Tue May 24 16:46:16 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1'
Gregory.
Hi Gregory
Well this is a problem that your Message Server is not configured properly.
Ensure that in your
C:\WINNT\SYSTEM32\DRIVERS\ETC\SERVICES file there is a line like
sapmsGR2 tcp\3601
where 36+<instance number> is your message server port.
Then Go to SAP logon pad.Select your System name say "DEV" and then click on groups. In the window that appears Enter system id as "GR2".
In the MEssage server enter your SAP application server hostname and click on Generate List
If your message server is configured properly then you should get the logon groups. If you get a error when you click on Generate List button then contact your Basis and ask them to help you in configuring the message server.
In addition also check out the following thread in the forum. It talks about the same problem.
https://www.sdn.sap.com/sdn/collaboration.sdn?node=linkFnode6-1&contenttype=url&content=https://
hope that helps you.
regards
ravi
Hi Gregory,
It seems that your JCO connections working properly.So, re import the model once again and if it needed then restart your J2EE server.
Then it will work.
Regards,
Bhavik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gregory
Try re importing the model in you webdynpro application and execute it.
Kishore
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry when i said 'i call the SMGW transaction' is in the R/3 System,
doing the same in the Solution Manager System, the gateway is gramsap01 and the service is sapgw00.
thx.
Gregory.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.