JCO server problems

Hello,
We've developed JCO server which serve as a bridge between SAP R/3 and MS SQL database system. In R/3 system is created TCP/IP destination and JCO server connects to this destination as a registered program.
In our test environment everything works fine. In customer production environment I face this behaviour:
After installation of solution it works. But after "some time", when I try to test destination in SM59 and I've got this error:
SM59 - test connection
connection to partner broken / CPI-C error CM_PRODUCT_SPECIFIC_ERROR
COMPONENT      NI (network interface)
COUNTER        2422932
ERROR TEXT     Connection reset by peer
ERROR NUMBER   232
MODULE         niuxi.c
LINE           1204
RETURN CODE    -6
What is interesting, problem persist, if i turn off JCO server (I expect error message, that no program is registered!),.... so I change the registered program ID (in SM59), change this in configuration of JCO server - it works.. but again after some time I've got that error.
R/3 version is 4.6c
Can you give suggestions, how to solve this problem (where should be the problem)?
Thanks for any answer.
Best Regards,
Juraj

Hi,
It gives me the correct IP when I ping yes. It's only when the SLD tries to resolve IP via JCO destinations. Yesterday I put in all hosts in my landscape into the hosts file of the SLD, disabled the NIC that it shouldn't be using and restarted.
Still it tries to resolve hosts in my landscape to 10.150.83.XXX. How is this possible??
Thanks - any other ideas?
.: HP

Similar Messages

JCo Server Shutdown

I have implemented a JCo Server using Example 5 in Jco Documentation.
The Server shuts down automatically every other day with no dumps leading no trails on how to debug.when we restart, it runs just fine.
my hunch is that the threads are not properly handled or not releasing the memory, i m not sure.
Does any one had similar problem or any clues ?
Thanks,
Sujatha

hi:
I also encountered a JCO Server problem which likes your problem above when SAP R/3 call java function.
The SAP R/3 is 4.6c, the JCo package version is 2.0.7.
In my java program, I start a Jco server and register that Jco server in R/3 sm59. In sm59 I register that connection as a TCP/IP connection.
In the RZ11, I get the gateway information.
My java program is a servlet program, which is running on the WAS640. The program is referred to JCO example 5. I attach the original code in the attachment.
When I start the Jco server, I get successful connection information in sm59. At that time, the ABAP program can call java program successfully.
But unluckily I find that link is not stable. Maybe after an hour or several hours, when I run the ABAP program again, RFC error message will popup. At that time I test the connection in sm59, an error message will show the connection is not registered. Also in SMGW I cant find the java rfc connection. Then, I have to restart the jco server, establish a new rfc connection.
I dont know what happen. I think maybe it is my program problem(I search the JCO help and try to find a function setting the timeout. But I dont find any). Maybe there is something to do with basis (I dont know whether there is a timeout configuration in r/3 or there is a background job will clean up the java connection).
Would you please give me some advices. I really dont know how to fix that problem. Thank you for your help.

JCO.Server within Tomcat problem

Hello.
I have implemented a JCO Server as a servlet and it is working just fine. However, it refuses to allow other servlets to connect to SAP. It grabs a hold of sapjcorfc.dll and will not let go. So that when I run a servlet that needs to call a BAPI I get the following error message:
java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [Native Library C:\WINDOWS\system32\sapjcorfc.dll already loaded in another classloader]. java.library.path [C:\Program Files\Java\jdk1.5.0_10\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Java\jdk1.5.0_10\bin]
com.sap.mw.jco.JCO.<clinit>(JCO.java:776)
Anyone have any idea how I can tell the JCO server not to be so selfish. I tried the JCO Library 2.0.9 and 2.1.8 with same results. This is obviously running on Windows, XP variety. Tomcat 5.5 and Java 1.5.
Thank you in advance.
Rudy

> Hi Rudy,
>
> You are a little bit off topic here,
Sorry <blush> I thought I might be, but I was getting desperate. I posted it in the Java Programming but didn't get much there.
> anyway please check
> <a href="/thread/2 [original link is broken]
> 61626">this</a> thread and especially the two SAP
> notes mentioned there.
Thank you. This hint is what I was looking for. I was hoping to be able to get to it today, but I guess it'll have to wait till Monday. In the meantime I found another solution in the OSS notes yesterday. It seem as though the classloader for the sapjcorfc.dll will look for it in the same directory as sapjco.jar first. So I deleted it from the system32 folder and copied it into WEB-INF\lib folder of each project and voila it worked. Although I still want to figure out what this solution is as well.
>
> HTH!
>
> -Vladimir
Spasibo Volodya.

Scenario SAP R/3 --(RFC)-- XI--(RFC)-- JCo.Server

Hello,
I am wondering if anyone can send me some feeback for such scenario. SAP R/3 version is 4.6c, SAP XI is 3.0 and JCo are 2.0.12.
I am having some trouble which I think are link to the fact that the SAP XI is Unicode and not the JCo.Server ... However I was thinking SAP XI will adapt, since it works well for scenario SAP R/3 (RFC)> XI (RFC)> SAP R/3.
Thanks for your feeback.

Hi Grégory,
I guess I faced a similar problem, the problem was that in the receiver RFC adapter you have to specify both an RFC target system and a system to lookup the metadata.
The target RFC system hat to have the same unicodeness of the metadata lookup system that means in your case that if jco server is non unicode also you R3 has to be non unicode otherwhise it will not (never) work, because this is a mandatory requirement of the RFC adapter.
In my case this was not possible so I was redirecting the RFC call to the ABAP stack of XI (where I had exposed the same function module which was simply recalling the same function module to the target system) and it worked/works.
Regards,
Sergio

RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'

Hi, All
the system is PI 7.0 EHP1 oraclei Win2003 server, I configured SLD but I run RZ70, having error "RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA' ". I know there are lot of tread about this error, but none of themsolve my problem. all JCO, RFC connections and SDL DATA supplier(VA) seem OK. error message in SM21 is "Could not send SLD data"
detail from SM21
The system could not send the data that has been collected automatical
for the System Landscape Directory (SLD). Check whether the gateway
configured in transaction RZ70 has been started and whether the SLD
bridge has been registered with this gateway.
You can use transaction SM59 to check this in the sending system for t
implemented RFC destinations. The RFC destinations have the standard
names "SLD_UC" for Unicode sending systems and "SLD_NUC" for non-Unico
sending systems. If a different RFC destination has been entered in
RZ70, check this destination instead.
You can use the Gateway Monitor to check the target gateways. In ABAP
systems, this monitor is started with transaction SMGW, or you can use
the external SAP program "gwmon". Check whether the specified gateway
has an active registration.
OF COURSE I checked RFC of SLD_UC and SMGW
any different ideas
Regards
ABH

Hi
Please check the following notes are implemented
Note 906454
Note 907729
You may be aware but if you are not --->RZ70 creates the required SLD* RFCs during runtime - therefore if you have defined these RFCs manually first using the same namespace you can get RFC conflicts which result in a failed submission
Please also check the user in the RFC is known to both systems and has required authorization to write to SLD
Generally with SLD you have to install or select a suitable gateway to handle incoming data supply traffic
Also the gateway you are using has be known to SLD and reflected in RZ70 - i.e these defintions have to be the same
It is also recommended to delete all references to SLD_* RFCs in data supplier and target SLD
after a failed submission attempt to allow RZ70 to recreate these consistently once the above has been checked
Best wishes
Stuart

"jco.server.unicode" is gone in JCO 3.0.5??!!

Recently we have migrated from   JCO 2.1.8 to 3.0.5.   Currently we are witnessing some problems with communications from non-Unicode Sap systems.
In the previous version (JCO 2.1.8) JCoIDoc.Server had a property "jco.server.unicode" in the latter one the property is gone.
AS far as I understand, JCo3 Server based on the data sent form a client recognizes encoding and applies proper conversion. However when we try to establish a non-Unicode connection ( from a Unicode enabled system), through setting In the SM59 transaction (tab MDMP & Unicode) u201ECommunication Type with Target Systemu201D to Non-Unicode, we are getting the following error :
com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????
????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
        at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
        at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
        at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
        at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
        at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
        at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
        at java.lang.Thread.run(Thread.java:619)
11:15:20,062 ERROR Sap server details
Class: com.syncron.bpe.engine.extinterface.sap.idoc.SapIDocServer
Program id: GIM
Thread name: JCoServerThread-1
Registered (at gateway) connection count: 5
Max thread count: 1
Exception occured
com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: IDocException occurred (raised by system karbie-nc6400|a_rfc)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:639)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2395)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
        at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
        at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
        at java.lang.Thread.run(Thread.java:619)
Caused by: RfcException: karbie-nc6400
    message: IDocException occurred
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by karbie-nc6400|a_rfc
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2785)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
        ... 4 more
Caused by: RfcException: karbie-nc6400
    message: IDocException occurred
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by karbie-nc6400|a_rfc
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3329)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
        ... 7 more
Caused by: com.sap.conn.idoc.IDocRuntimeException: IDocException occurred
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:151)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
        ... 8 more
Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "???????
???????????????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
        at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
        at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
        at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
        at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
        ... 10 more
With JCO 2.1.8 we used to solve it through setting the mentioned "jco.server.unicode"   to 1, in the current one it seems that there is not much to configure regarding encoding.
Please advice.

In unicode ABAP backend systems you always have to set the destination in SM59 to "Unicode" if the communication partner is JCo. There is no choice for setting the Non-Unicode option. It won't work.
JCo3 does not require a manual setting of the "jco.server.unicode" property any longer. Therefore the property has been deleted. In JCo3 you don't have to take care for this anymore.

JCo server programming, properties and connection settings

Greetings, SAP professionals.
The reason I come to this forum is that I'm hoping to gain some insights into the use of the SAP Java Connector (JCo). I am a developer who was tasked with making a new component for a systems integration application. As is typical of integration software, our app can link together various different systems using a variety of protocols, as well as providing the means to apply business logic on messages passed from one location to another. We already have a connector acting as an SAP client which was implemented using JCo. Now, we were asked to develop a new component: a server capable of accepting RFCs from a remote SAP system acting as client. The server is to be created using the JCo classes, so basically an extension of JCo.Server, with some logic for creating function templates from configuration files.
However, while I'm understanding the structure of the Java API, it's not entirely clear to me just what the classes do. I've found the JavaDoc for JCo to be mostly descriptive of the interface of classes and methods, but not really explaining what these achieve, or how. So I'm hoping to be set straight, as I fear I'm kind of misunderstanding the functionality of JCo... Being mainly an integrations developer, I unfortunately often have to settle for gaining a superficial knowledge of a variety of systems to quickly interface with them, so I don't have any prior knowledge of SAP but still need to be able to implement something with JCo without too much delay.
The most important question I have is this: when a JCO.Server implementation is started, does it act as a fully standalone component capable of receiving calls, or does it merely act as a sort of listener for some main SAP system? I'm not talking about a reliability on the two .dll files (or .so for Linux) that are required for the use of JCo, I just wish to know if the JCo package is entirely self-sufficient for server functionality or if it is intended to be linked to some SAP system.
A second problem I have is that the parameters passed to various constructors aren't clear to me... I'm not familiar with SAP terminology, nor have I worked with any client apps that make use of an SAP system.
The meaning of client strings, gwhost, gwservice, ashost, system IDs and program IDs mostly elude me, especially when it comes to knowing what client parameters must match what server parameters.
In order to familiarize myself with the classes, I've tried playing around with them a bit trying to create a small test app that first starts a JCO.Server instance, then tries to make a remote function call to it with a JCO.Client (within the same class, for simplicity and debugging purposes). I was wondering if this actually makes sense... Would a JCo client be capable of connecting to a JCo server, all running purely in Java, or is that nonsense?
To eliminate some common troubleshooting options, I'll quicly describe the steps I've taken:
Both librfc32.dll and sapjcorfc.dll were placed in the Windows system32 folder. Maybe only librfd32 needs to be placed there, but I copied both anyway to make sure.
The directory containing the jar file and both dll files is included in my environment path variable.
I've added a line to the C:\Windows\system32\drivers\etc\services file as follows:
sapgw00 3300/tcp #SAP System Gateway Port
I've opened port 3300 in my Windows firewall. In fact, I also tested with the firewall completely turned off.
However, I do not manage to get my test class to work. I've tried ports 3300, 3200 and 3600. I've tried various permutations of the client and server properties. I've tried removing the line from the services file, which would prompt the client to state upon connecting that the service "sapgw00" is unknown. When I add it back in, the error changes to "partner not reached", so it is definitely picking something up.
The server itself starts just fine, but connecting through a client doesn't work. My class source code is posted below. Maybe what I'm trying to do doesn't make any sense, but at the moment it's my best guess.
I realize this is a pretty long post and the class, while not exactly big, also implies a bit of reading of its own. But if anyone could give me any answers that are new to me, I'd be hugely grateful. Right now I'm kind of stuck, and just setting up the service and letting our customer test on it is a somewhat slow approach that can't match developing and testing on one and the same host.
Preliminary thanks to everyone who took the effort to read this.
//Start of code
import java.util.Properties;
import com.sap.mw.jco.IFunctionTemplate;
import com.sap.mw.jco.IMetaData;
import com.sap.mw.jco.IRepository;
import com.sap.mw.jco.JCO;
public class Test {
 public static void main(String[] args) {
 Test test = new Test();
 ServerThread serverThread = test.new ServerThread();
 serverThread.start();
 while(!serverThread.isReady) {
 try {
 Thread.sleep(5000);
 } catch(final InterruptedException i) {
 System.out.println("Rudely awakened");
 try {
// JCO.Function func = getSampleFunction(test, "STAY");
// serverThread.server.handleRequest(func);
// System.out.println(func.getExportParameterList().toXML());
// func = getSampleFunction(test, "STOP");
// serverThread.server.handleRequest(func);
// System.out.println(func.getExportParameterList().toXML());
 final Properties clientProps = getClientProps();
 JCO.Client client = JCO.createClient(clientProps);
 client.connect();
 IRepository rep = JCO.createRepository("1", client);
 IFunctionTemplate templ = rep.getFunctionTemplate("TEST_FUNC");
 JCO.Function function = templ.getFunction();
 function.getImportParameterList().setValue("STAY", "FIELD1");
 client.execute(function);
 JCO.Function function2 = templ.getFunction();
 function2.getImportParameterList().setValue("STOP", "FIELD1");
 client.execute(function2);
 } catch(final Exception e) {
 e.printStackTrace(System.out);
 serverThread.requestStop();
 while(serverThread.isAlive) {
 try {
 Thread.sleep(5000);
 } catch(final InterruptedException i) {
 System.out.println("Rudely awakened");
 } finally {
 private static Properties getClientProps() {
 final Properties props = new Properties();
 props.setProperty("jco.client.client", "100");
 props.setProperty("jco.client.user", "");
 props.setProperty("jco.client.passwd", "");
 props.setProperty("jco.client.lang", "");
 props.setProperty("jco.client.sysnr", "00");
 props.setProperty("jco.client.ashost", "/H/localhost/S/sapgw00");
 props.setProperty("jco.client.gwhost", "localhost");
 props.setProperty("jco.client.gwserv", "sapgw00");
 return props;
 public class ServerThread extends Thread {
 public void run() {
 isAlive = true;
 IRepository repos = new TestRepository("testrep");
 repos.addFunctionInterfaceToCache(getFunctionInterface());
 server = new TestServer(repos);
 server.start();
 System.out.println("Server successfully started");
 isReady = true;
 while(!stop) {
 try {
 Thread.sleep(1000);
 } catch(final InterruptedException i) {
 System.out.println("Wouldn't let me sleep...");
 stop = server.stopRequested;
 server.stop();
 isAlive = false;
 System.out.println("Server successfully stopped");
 public void requestStop() {
 server.requestStop();
 public TestServer server;
 public boolean isReady = false;
 public boolean isAlive = false;
 public class TestServer extends JCO.Server {
 public TestServer(IRepository rep) {
 super("localhost", "sapgw00", "PROGID", rep);
 public void handleRequest(JCO.Function fct) {
 try {
 JCO.ParameterList importParams = fct.getImportParameterList();
 final String importXML = importParams.toXML();
 System.out.println("XML representation of import parameters: ");
 System.out.println(importXML);
 final String input = importParams.getString("FIELD1");
 System.out.println("FIELD1 value: " + input);
 JCO.ParameterList exportParams = fct.getExportParameterList();
 if(input.equals("STOP")) {
 exportParams.getField("FIELD2").setValue("OK");
 stopRequested = true;
 catch(JCO.AbapException ex) {
 throw ex;
 catch(Throwable t) {
 throw new JCO.AbapException("SYSTEM_FAILURE", t.getMessage());
 public boolean checkAuthorization(String functionName, int authorMode, String partner, byte[] key) {
 System.out.println(functionName + " " + partner);
 return true;
 public void requestStop() {
 stopRequested = true;
 public boolean stopRequested = false;
 public class TestRepository extends JCO.BasicRepository implements IRepository {
 public TestRepository(String name) {
 super(name);
 public static IMetaData getFunctionInterface() {
 JCO.MetaData metaData = new JCO.MetaData("TEST_FUNC");
 metaData.addInfo("FIELD1", IMetaData.TYPE_STRING, 4);
 metaData.setFlags(0, IMetaData.IMPORT_PARAMETER);
 metaData.addInfo("FIELDX", IMetaData.TYPE_STRING, 8);
 metaData.setFlags(1, IMetaData.IMPORT_PARAMETER & IMetaData.OPTIONAL_PARAMETER);
 metaData.addInfo("FIELD2", IMetaData.TYPE_STRING, 2);
 metaData.setFlags(2, IMetaData.EXPORT_PARAMETER);
 return metaData;
 public static JCO.Function getSampleFunction(Test test, String s) {
 TestRepository testRep = test.new TestRepository("testrepository");
 testRep.addFunctionInterfaceToCache(getFunctionInterface());
 JCO.Function func = testRep.getFunctionTemplate("TEST_FUNC").getFunction();
 func.getImportParameterList().setValue(s, "FIELD1");
 return func;
 private static boolean stop = false;

If I understood you correctly, you want to provide a "service" that can be called from SAP. To provide this service you've chosen to implement an (external) RFC server program via JCo. One common method for RFC server programs is to register in SAP on the gateway - you do this by supplying the three parameters
<ol>
<li>jco.server.gwhost - SAP gateway host on which the server should be registered (so this would be the server name or IP address of the SAP gateway; localhost is only correct, if your RFC server program runs on the same server as the SAP gateway)</li>
<li>jco.server.gwserv - Gateway service, i.e. the port on which a registration can be done</li>
<li>jco.server.progid - Program ID under which your RFC server program can be reached (free, made-up case sensitive name, that should represent the service your RFC server is providing)</li>
</ol>
So essentially you're creating a listener, that is registered in SAP and waits for any invocations. Within SAP they will define a RFC destination, which basically represents a TCP/IP connection pointing to the SAP gateway where you registered with the given program ID. If you want more details, check the SAP help pages for <a target="_blank" href="http://help.sap.com/saphelp_nw04/helpdata/en/22/04262b488911d189490000e829fbbd/content.htm">RFC destinations</a> (you're looking for destination type T, see explanations <a target="_blank" href="http://help.sap.com/saphelp_nw04/helpdata/en/22/042652488911d189490000e829fbbd/content.htm">here</a>).
Usually gateway host and service (port) are given to you by the SAP basis folks and you tell them which program ID you're using. They will then enter those parameters in an RFC destination of type T in SAP. So no need for any of the client parameters you've mentioned. Although, I'd like to repeat, it's usually handy to also have SAP logon parameters maintained on your RFC server program, so that you can utilize the repository data from SAP (might be irrelevant in your case).
Hope this clarifies it a bit...

JCO.Server appends null character to string

I am a complete SAP and JCO newbie so I'll try making as much since as I can, given the fact that I'm not familiar with SAP terminology and technology. I've been lent as a developer to another group which needs a legacy application rewritten. The application processes a RFC and decrypts the RFC encrypted payload and returns it along with a status code.
I have made progress - I'm able to register my server with the SAP runtime and using the SAP GUI application and the help of a SAP developer, I'm able to make an RFC call to my application. I'm able to read the parameters sent from SAP and write parameters back.
The problem is that one of the parameters I'm writing back (java.lang.String) appears to have and extra character on SAP side. On the GUI it appears as a '#' (pound) sign. The SAP developer told me the string is terminated with a null character which I know is a C/C++ thing but not a Java thing. I don't think it is a Unicode issue. The Java server is not running in Unicode mode and any attempt to set the jco.server.unicode property (I may have forgotten the exact name) to a value of 1 causes the RFC to fail.
I think the issue is likely to be the manner in which I defined the function parameters or the manner in which I write them. The following are code snippets:
Defining the function:
JCO.MetaData metadata = new JCO.MetaData(Constants.FUNCTION_DECRYPT);
metadata.addInfo(Constants.PARAMETER_SCHEME,      JCO.TYPE_INT,    255,   0, 0, JCO.IMPORT_PARAMETER, null);
metadata.addInfo(Constants.PARAMETER_ENCRYPTED,   JCO.TYPE_STRING, 255,   0, 0, JCO.IMPORT_PARAMETER, null);
metadata.addInfo(Constants.PARAMETER_DECRYPTED,   JCO.TYPE_STRING, 255,   0, 0, JCO.EXPORT_PARAMETER, null);
metadata.addInfo(Constants.PARAMETER_RETURN_CODE, JCO.TYPE_INT,    255,   0, 0, JCO.EXPORT_PARAMETER, null);
Server request handling code:
protected void handleRequest(JCO.Function function)
                // Obtaining import/export parameter lists.
                JCO.ParameterList input = function.getImportParameterList();
                JCO.ParameterList output = function.getExportParameterList();
                // Getting scheme and encrypted text parameters.
                int scheme       = input.getInt(Constants.PARAMETER_SCHEME);
                String encrypted = input.getString(Constants.PARAMETER_ENCRYPTED);
                // Decoding base 64 string.
                byte[] bytes = Base64.decode(encrypted);
                // Obtaining cipher by scheme and decrypting the text.
                AppCipher cipher = ApplicationConfiguration.getDecryptor(scheme);
                if(cipher == null)
                                logger.error("Unable to get cipher due to an unknown encryption scheme: " + scheme);
                else
                                byte[] decrypted = cipher.decrypt(bytes);
                                String plainText = new String(decrypted);
                                // Setting decrypted value information and return code.
                                output.setValue(plainText, Constants.PARAMETER_DECRYPTED);
                                output.setValue(Constants.RETURN_CODE_SUCCESS, Constants.PARAMETER_RETURN_CODE);

I seem to have made progress. If I define the parameter type as JCO.TYPE_CHAR instead of JCO.TYPE_STRING, it works:
metadata.addInfo(Constants.PARAMETER_DECRYPTED,   JCO.TYPE_CHAR,   255,   0, 0, JCO.EXPORT_PARAMETER, null);
That is the only change I made. I'm still setting the parameter value as java.lang.String. I hope this won't cause issues elsewhere. I was also able to change the field definition and set it as a byte array. However, that had the problem of having to define the exact length of the byte array in the field metadata otherwise the remaining bytes would appear as null bytes on SAP side.

JCo Server does not start

Hi,
I'm trying to create and start a JCoIDoc.Server on a Web Application Server 700 system. Because I could not find the required classes in the trfc.jar archive on the server I downloaded and packaged the required java connector classes sapidoc.jar and sapidocjco.jar in my EAR file.
The deployment works fine and the server should be started automatically by a servlet. There are no error entries in the logfile. In addition I can see my own entries in the logfile that the servlet was executed an the server started.
Nevertheless I can not send anything from an ECC 5.0 system to my java connector server. Using the "netstat -a" command in a DOS console on the Java server I can not even see that the port for incomming idocs is listening.
Having a look at the ECC 5.0 system using transaction "smgw" I do not see the my JCo Server
Has anybody an idea what goes wrong or if I forgot anything to realize? The code is quite similar to the jco sample code.
Or is it in general not possible to start a JCoIDoc.Server on a Web Application Server 700 system?
Best regards,
Markus

you should have no problem doing this....
However -- as you downloaded the Idoc libraries instead of extracting them for the tar...?
a) make sure they are accessible (on the classpath) They may need to be in the same directory as the JCO...
b) make sure they are compatible... read up on the download page and in sapnotes which version exactly you need...
Or ask your friendly basis admin where he stashed them and use the ones coming with the installation...
Enjoy

JCO Server and SAP trfc queue

Hi,
we are sending IDocs from our sap system to a JCO server. Let's assume we are sending 1000 IDocs to it. After sending there are no IDocs in the trfc-queue and the status of all IDocs is "green". Can we assume the JCO server received all 1000 IDocs? Is an empty trfc-queue always an indicator for a successfull sending process even there are some problems with a weak network(network interruptions). I know IDocs are tansaction based. For my understanding a transaction is okay or not. So an empty trfc queue should indicate everything went fine and all IDocs were received?
I appreciate any comments on that issue ...
-Steffen

If the status of all idocs is green which indicates the communication layer is ok. As you said, the idocs are transaction based. You need to make use of transaction id to confirm everything is fine from the viewpoint of your business logic.
Dennis

JCo encoding problem

Hi,
I have a problem where a login over JCo fails when I have the character u20AC in the password.
This is a bit strange, because the JCo Client itself has the UTF-16 encoding, and the password is UTF-8. The password is UTF-8 because it also contains Ä which works.
I set up a test password with umlauts, and all umlauts seem to work. Everytime I have a u20AC or even &, the login fails.
I tried setting "jco.client.unicode" to 1, but this didn't seem to work. I am not even sure the property "jco.client.unicode" even exists, although there is a "jco.server.unicode" which in my case is not helpful - I'm creating a client, not a server.
The remote SAP System is a Unicode system by the way.
Any ideas? Oh, I am using JCo 2.1.8.
T00th

Stefan,
thanks a lot for the explanation, now we know at least what happens. As this seems so crappy though, I cannot help but rant a little...
If JCo would do the logon with UTF-16/Unicode by default, you won't be able to logon to a Non-Unicode system without specifying the jco.client.codepage parameter.
Not really as long as a proper code page conversion from UTF-16 to the code page used by the system would've been implemented on the server side. Instead of choosing codepage 1100 the more natural choice seems UTF-8.
As far as I know since application server 6.10 the server "knows" about Unicode (e.g. see [here|http://help.sap.com/saphelp_nw04/helpdata/en/cb/56453c3ff4110ee10000000a11405a/frameset.htm]). Anyhow, if I understood you correctly you can actually set the code page for the logon data using jco.client.codepage, but what happens when you use Unicode codepages on non-Unicode systems?
OSS note [794411 - Supported codepages of SAP Java Connector 2.1 and 6.x|https://service.sap.com/sap/support/notes/794411] seems to list the supported codepages for JCo 2.1.x (stops at 2.1.5 though, maybe no changes after that). UTF-8 is not listed (i.e. 4110), yet no error occurs when I specify this on JCo 2.1.8 when connecting to a non-Unicode SAP 4.7 system (kind of expected an exception).
Finally OSS note [975768 - Deprecation of Java features with non-Unicode Backend|https://service.sap.com/sap/support/notes/975768] seems to put an end to all that madness. Well let's hope JCo follows and deprecates the jco.client.codepage parameter as soon as possible...
Here's something funny though: When using JCo 3.0.5 I get client codepage 1100 when connecting to a non-Unicode 4.7 system and client codepage 4102 when connecting to a Unicode ECC 6.0 system (without setting jco.client.codepage). So maybe this is just a concern for JCo 2.x, but still it seems odd that we have codepage references in JCo 3.0.5 (DestinationDataProvider.JCO_CODEPAGE, JCoCustomDestination.setCodepage(String) and others).
Cheers, harald

JCO.SERVER could not find the server function

Hi,
I am calling "BAPI_COMPANY_GETDETAIL".thuough the zprogram"ZBAPI_COMPANY_GETDETAIL"
REPORT ZBAPI_COMPANY_GETDETAIL.
DATA:BEGIN OF ITAB,
RCOMP LIKE T880-RCOMP,
END OF ITAB.
ITAB-RCOMP = 99999.
CALL FUNCTION 'BAPI_COMPANY_GETDETAIL'
EXPORTING
COMPANYID = ITAB.
IMPORTING
COMPANY_DETAIL =
RETURN =
The Details I Gave......
In SM59 of R/3:
PROGRAMID:LCRSAPRFC_PIT
GATEWAYHOST:PITEST
GATEWAYSERVICE:sapgw01
Tested the connection and it is running
ID:
In Communication Channel.
Application server (Gateway):PITEST
Application server Service (Gateway):
PROGRAMID:LCRSAPRFC_PIT
RFC Metadata Repository parameter.
ip of XI Server
System No Xi System NO
username
pwd
In SM58 I find the Following error.
"JCO.SERVER could not find the server function BAPI_COMPANY_GETDETAIL.
I Tested RFC ADAPTOR in RWG and it is ok.
I do not Understand where the problem is.
Please clarify.
Thanks,
Srinivasa

Thanks for the reply,
Yes RFC is in the Sender side.
I am calling "BAPI_COMPANY_GETDETAIL".thuough the zprogram"ZBAPI_COMPANY_GETDETAIL"
REPORT ZBAPI_COMPANY_GETDETAIL.
DATA:BEGIN OF ITAB,
RCOMP LIKE T880-RCOMP,
END OF ITAB.
ITAB-RCOMP = 99999.
CALL FUNCTION 'BAPI_COMPANY_GETDETAIL'
EXPORTING
COMPANYID = ITAB.
IMPORTING
COMPANY_DETAIL =
RETURN =
The Details I Gave......
In SM59 of R/3:
PROGRAMID:LCRSAPRFC_PIT
GATEWAYHOST:PITEST(XI system name)
GATEWAYSERVICE:sapgw01
Tested the connection and it is running
ID:
In Communication Channel.
Application server (Gateway):PITEST(XI system name)
Application server Service (Gateway):
PROGRAMID:LCRSAPRFC_PIT
RFC Metadata Repository parameter.
ip of XI Server
System No Xi System NO
username
pwd
In SM58 I find the Following error.
"JCO.SERVER could not find the server function BAPI_COMPANY_GETDETAIL.
I Tested RFC ADAPTOR in RWG and it is ok.
I do not Understand where the problem is.
These is what I gave,

JCo Server High Availability

How can I make the JCo server implement "High Availability" functionality. The SAP Server which the makes calls to the JCo Server is HA-aware. So if there is a failover, the SAP Server switches over to the other instance but the JCo server keeps sending the message "Server unavailable". Is there a solution for this problem.
Thanks.

Single Appliance not necessarily means Single Point of Failure, an appliance with HW Redundancy could handle failure and provide High Availability, if only configured well.
Does Symantec BrightMail Appliance provide such redundancy configuration?
You will have to ask their support or in a Symantec Forum.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

JCO.Server could not find server function "ZVERIFY_FILE"

Hi Experts,
I am facing one problem, i have created on TCP/IP connection with connection type T and given it some Program Id.
I have register this Program id On SRM server.
Now from this server i want to call one JAVA file, for that purpose i have installed JCO on the server.
My server file looks like,
import com.sap.mw.jco.*;
//import com.tcs.jns.JSignNS;
//import com.tcs.jns.JSignNSException;
//import com.tcs.jns.CertDetails;
// added by paresh on 16.1.2009
import java.io.FileOutputStream;
import com.tcs.jie.jverify.JVerify;
import com.tcs.jie.jsign.JSign;
public class ds_listener extends JCO.Server {
Create an instance of my own server
@param gwhost (gateway host)
@param gwserv (gateway service number)
@param progid (program id)
@param repository (repository used by the server to lookup the definitions of an inc)
 public ds_listener(String gwhost, String gwserv, String progid, boolean isUnicode, IRepository repository) {
 super("sapdev14", "sapgw01", "DS_RFC", repository); this.setProperty("jco.server.unicode", isUnicode?"1":"0");
 /** Overrides the default method. */
 static ds_listener serverConnections[] = new ds_listener[1];
 protected void handleRequest(JCO.Function function) {
 JCO.ParameterList input = function.getImportParameterList();
 JCO.ParameterList output = function.getExportParameterList();
 if (function.getName().equals("ZVERIFY_DATA")) {
 try{
 JVerify JNS = new JVerify();
 String dbPath = "/home/admin/FormSigner_23Apr/FormSigner_Release/certdbs";
 //boolean res = JNS.init (dbPath); // commented by paresh on 16.1.2009 as its obsolute
 //initialize method has to be called before calling any other method of the API
 String recdSignature = input.getString("SIGNATURE");
 boolean ret_update = JNS.updateSignature(recdSignature.getByetes());
 if (ret_update){
 int count = JNS.getSignerCount();
 boolean ret_verify_sign = false;
 while(count > 0){
 ret_verify_sign = JNS.verifySignature(count - 1);
 if (ret_verify_sign){
 ret_verify_sign = false;
 count = count - 1;
 }else
 break;
 if (count == 0){
 String decoded_data = new String(JNS.getDecodedData());
 output.setValue("X", "STATUS");
 output.setValue(decoded_data, "DATA");
 }else{
 output.setValue(" ", "STATUS");
 output.setValue("Error in Signature Verification. Please check Certificate Validity of every signer.", "DATA");
 }catch (Exception e1){
 output.setValue(" ", "STATUS");
 output.setValue(e1.getMessage(), "DATA");
 }else if(function.getName().equals("ZVERIFY_FILE")) {
 try{
 JVerify JNS = new JVerify();
 String dbPath = "/home/admin/FormSigner_23Apr/FormSigner_Release/certdbs";
 //boolean res = JNS.init (dbPath); // commented by paresh on 16.1.2009 as its obsolute
 //initialize method has to be called before calling any other method of the API
 String recdSignature = input.getString("SIGNATURE");
 boolean ret_update = JNS.updateSignature(recdSignature.getBytes());
 if (ret_update){
 int count = JNS.getSignerCount();
 boolean ret_verify_sign = false;
 while(count > 0){
 ret_verify_sign = JNS.verifySignature(count - 1);
 if (ret_verify_sign){
 ret_verify_sign = false;
 count = count - 1;
 }else
 break;
 if (count == 0){
 output.setValue("X", "STATUS");
 }else{
 output.setValue(" ", "STATUS");
 }catch (Exception e1){
 output.setValue(" ", "STATUS");
 }else{
 return ;
Start the server
 public static void startServers() {
 JCO.addClientPool("POOL",3,"200","sisldp","paresh1234","EN","sapdev14","01");
 IRepository repository = JCO.createRepository("REP", "POOL");
 for (int i = 0; i < serverConnections.length; i++) {
 // Server listens for incoming requests from system 1
 // (Change gateway host, service, and program ID according to your needs)
 serverConnections = new ds_listener(
 "sapdev14",//gateway host, often the same as host
 "sapgw01", //gateway service, generally sapgw+<SYSNR>
 "DS_RFC", // corresponds to program ID defined in SM59
 true, // or false for non unicode listener
 repository);
 serverConnections.start();
 public static void main(String[] args) {
 startServers();
The file have no error as i have compiled it on server, its listener file given in JCO with some modification.
I have tested the connection from SM59 it's working fine,but when i call my any of the 2 function(ZVERIFY_DATA & ZVERIFY_FILE) defined in my java file then i am getting an error "JCO.Server could not find server function 'ZVERIFY_FILE'" on SRM screen.
Can anyone tell me what can be the reason????
please help, i am in real trouble.

Hi,
This is may be of the wrong FunctionModule name means check in case also,it may be case sensitive.
And check whether it is remotely enabled or not and check the RFC destination.
For more details refer these threads.
JCO.Server could not find server function 'SET_SLD_DATA'
JCO.Server could not find server function
Problems with sender RFC
Thanks.

JCo server as a stand alone service

Hi All,
I have a JCo server that is connecting to the R/3 system - working fine - no problems with that. I am currently running it at the cmd prompt. The problem is if somebody logs out of the server, the JCO server is shutdown. Instead, I want to run this as a service in the J2EE Engine so that it is up and running all the time with the J2EE server. How can I do this (apart from making it a servlet). Any other ideas on this ??
Thanks,
MV.

Hello,
if you are on J2EE 1.4+ you could use a resource adapter
regards franz

JCO server problems

Similar Messages

Maybe you are looking for