Skip to Content

The parameter "jco.server.unicode" in jco 3.0 where is finished ?


I'm passing my java code from jco 2.0 to jco 3.0

I see that in the interfarce ServerDataProvider there isn't the parameter "jco.server.unicode"

I would know where it is possible to set it or if it isn't necessary to set it and why

Thank you

Best Regards

Fabrizio Bellini

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Jan 12, 2016 at 03:42 PM

    Hello Fabrizio,

    in JCo 3.0 a server no longer needs to specify jco.server.unicode as it can deal with both non-unicode and unicode clients. In 2.x it was required to determine whether it is non-unicode or unicode in order to make sure that the data received was interpreted correctly. A JCo 3.0 Server does now automatically recognize the partner type correctly.

    Best regards,


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 12, 2016 at 08:24 PM

    Markus is right, but I would like to add that it is still mandatory to set the "Unicode" option in transaction SM59 of a Unicode AS ABAP system for all RFC destinations that target a JCoServer program.

    This configuration part did not change with JCo 3.0.

    Best regards,


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.