on 07-13-2005 1:49 AM
I have a Java servlet that is being deployed in the J2EE stack on the same system that is running the ABAP stack. When the servlet connects to the ABAP stack on the same system, the JCO Client attributes indicate that the connection type is always a '3' (R/3 connection), and not the 'F' (fast = shared memory pipe) that I expect. I don't see any mention in the SAP docs of any explicit steps that I need to take in order to enable or use fast RFC. Even though it is not officially supported, I tried to explicitly set the jco.client.type property to F before making the JCO client connection, but this didn't seem to help. Any idea how to control whether fast RFC is used?
There is a tool available on the service marketplace to test and check fast RFC in your cluster. See SAP Note 578340:
*******
SAP Note 578340
simple tool checking J2EE Engine, JCO&RFC versions, FastRFC
Symptom
FastRFC does not work
Solution
This is a tool that:
o gives information about the current status of the cluster
o displays a list with the running server and dispatcher
nodes in the cluster (for each element - cluster name and id, ip address, and join port)
o for each server node in the cluster displays
- the system properties
- SAP J2EE Engine version information
- JCo and RFC information
o tests standard and fast RFC - uses FastRFC to call
function modules on the ABAP side.
The tool also tests the FastRFC connection on every server node.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.