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

[fabrizio_bellini]

Goodmorning,

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

[MarkusTolksdorf · Accepted solution]

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,

Markus

[HAL9000]

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,

Stefan