📄 releasenotes.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML> <HEAD> <TITLE>SAP Java Connector Release Notes</TITLE> <META http-equiv=Content-Type content="text/html; charset=windows-1252"> <link rel="stylesheet" type="text/css" href="jco.css"> </HEAD><BODY><table cellSpacing=0 cellPadding=0 border=1><tr><td><table cellSpacing=0 cellPadding=0 border=0><tr> <td vAlign="top" ><IMG height="80" src="images/father_son.jpg" width=115 border=0></td> <td vAlign="bottom"><IMG height="25" src="images/ebusiness.gif" width=375 border=0></td> <td vAlign="top" ><IMG height="80" src="images/skateboard.jpg" width=240 border=0></td></tr><tr bgcolor="#ffac1e"><td vAlign="top" colspan=3> </td></tr><tr><td colspan=3><table cellSpacing=0 cellPadding=0 border=0><tr><!-- ################################################################################ --><!-- ### LEFT TOOLBOX START ### --><!-- ################################################################################ --><td align="right" valign="top" width=115 bgcolor="#4c4c4c"><table cellSpacing=0 cellPadding=5 border=0><tr><td valign="top" align="left"> </td></tr><tr><td><table style="align: top" cellSpacing=0 cellPadding=0 width=100 align=left border=0> <tr><td align=right><a class=white style="LETTER-SPACING: normal" href="intro.html"> Home </a></td></tr> <tr><td align=right><a class=white style="LETTER-SPACING: normal" href="installation.html"> Installation </a></td></tr> <tr><td align=right><a class=white style="LETTER-SPACING: normal" href="configuration.html">Configuration</a></td></tr> <tr><td align=right><a class=white style="LETTER-SPACING: normal" href="security.html"> Security</a></td></tr> <tr><td align=right><a class=white style="LETTER-SPACING: normal" href="documentation.html">Documentation</a></td></tr> <tr><td align=right><a class=white style="LETTER-SPACING: normal" href="examples.html"> Examples </a></td></tr> <tr><td align=right><a class=white style="LETTER-SPACING: normal" href="releasenotes.html"> Release Notes</a></td></tr> <tr><td> </td> <tr><td> </td></table></td></tr><!-- ################################################################################ --></table></td> <!-- ### LEFT TOOLBOX END ### --><!-- ################################################################################ --><!-- ################################################################################ --><!-- ### WORK AREA START ### --><!-- ################################################################################ --><td valign="top" colspan=2 height=200><table cellSpacing=0 cellPadding=2 border=0 width=500><!-- ################################################################################ --><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Release Notes 2.1.8</SPAN></td></tr><tr><td valign="top" align="left"><HR class="separator" noshade></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Additional connection parameter</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0 width="100%"> <tr><td class="faqw"> The RFC connection parameter <tt>WAN_CONN</tt> is supported now. If this connection parameter is set to <tt>1</tt>, the compression of tables is initiated if the table size is over 250 bytes. With the default value <tt>0</tt> only tables over 8 kB will be compressed. </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Bugfix in tRFC processing</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0 width="100%"> <tr><td class="faqw"> <tt>onConfirmTID</tt> and <tt>onRollback</tt> might have caused a native crash on some platforms with an error message like <br> <tt>*** glibc detected *** free(): invalid pointer</tt> </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Bugfix in error handling</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0 width="100%"> <tr><td class="faqw"> An error in the error handling might have caused a native crash, if the system ran out of memory. </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>NullPointerException in JCO.Repository fixed</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0 width="100%"> <tr><td class="faqw"> <tt>JCO.Repository.getFunctionTemplate()</tt> and <tt>JCO.Repository.getStructureDefinition()</tt> threw a <tt>NullPointerException</tt> under some circumstances.<br> <em>Note:</em> The NullPointerException occurred only if the client connection belonged to a pool. The best way to resolve this issue is to change the application code and create the repository with the available pool instead of creating with one pooled client connection. Therefore the repository would be able to allocate the client connections during the remote calls only, which would allow to work to full capacity. </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Release Notes 2.1.7</SPAN></td></tr><tr><td valign="top" align="left"><HR class="separator" noshade></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Support for additional platforms</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0 width="100%"> <tr><td class="faqw"> Windows Server 2003 for Intel EM64T and AMD64 CPUs and furthermore Sun Solaris for Intel EM64T and AMD64 CPUs are supported now. For details please see SAP note <a href="http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200001679342002">549268</a>. </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Bugfix in JCO.Client.reset</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0 width="100%"> <tr><td class="faqw"> <tt>JCO.Client.reset</tt> led to an error with connections to SAP System releases < 4.0. </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Bugfix in handling of logon parameters containing quotes</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0 width="100%"> <tr><td class="faqw"> User name or password logon parameters containing one or more quote characters (<tt>"</tt>) led to an <tt>RFC_ERROR_LOGON_FAILURE</tt> saying that the name or password was incorrect. </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Release Notes 2.1.6</SPAN></td></tr><tr><td valign="top" align="left"><HR class="separator" noshade></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Support for additional platforms</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0> <tr><td class="faqw"> Linux X86_64 for Intel EM64T and AMD64 CPUs and Linux on Power 64bit are supported now. For details please see SAP note <a href="http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200001679342002">549268</a>. </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Release Notes 2.1.5</SPAN></td></tr><tr><td valign="top" align="left"><HR class="separator" noshade></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Support for long and mixed case passwords</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0> <tr><td class="faqw"> Now JCo supports long and mixed case passwords (up to 40 characters instead of only 8) that will be introduced with the forthcoming SAP kernel release. JCo does not automatically convert characters in the password logon parameter to upper case any longer.<p> <em>The non-conversion may cause logon problems with SAP kernel releases up to 6.40, because these releases assume to get the logon passwords always in upper case. SAP note <a href="http://service.sap.com/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200001605522004">792850</a> describes the required minimum kernel patch level for this problem to be fixed.</em></p> </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>New codepage 8450 supported</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0 width="100%"> <tr><td class="faqw"> The SAP codepage 8450 (Simplified Chinese [GB2312-80]) is additionally supported now. </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Release Notes 2.1.4</SPAN></td></tr><tr><td valign="top" align="left"><HR class="separator" noshade></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>New codepages supported</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0> <tr><td class="faqw"> The SAP codepages 6230, 6240, 6250, 6300, 6400, 6600 and 6700 are additionally supported now.<p> <em>These codepages are the so called unambiguous blended codepages that do not offer full round trip capability. That means there are more or less characters in each codepage that could be mapped to multiple SAP byte sequences. The conversion direction SAP byte sequence -> Java unicode only contains unambiguous mappings, but the other direction Java unicode -> SAP byte sequence may contain ambiguous mappings. (e.g. in SAP codepage 6300, character <tt>SECTION SIGN</tt>: SAP code x'A7 or x'8198 -> U+00A7 -> x'A7).</em> </td></tr></table></div></td></tr><tr><td valign="top" align="left"> </td></tr><tr><td valign="top" align="left"><SPAN class=head>Support for authorization trace</SPAN></td></tr><tr><td valign="top" align="left"><div class="textblack"><table cellSpacing=0 cellPadding=2 border=0> <tr><td class="faqw"> New methods are introduced to support the authorization trace in the SAP system. <ul> <li><code>JCO.Client.startAuthorizationTracing()</code> <li><code>JCO.Client.endAuthorizationTracing()</code> <li><code>JCO.Client.isAuthorizationTracingEnabled()</code> </ul> <br> <em>The methods can be used only if authorization tracing is enabled in the SAP system. The authorization trace is provided for the internal using by SAP. </em> </td></tr>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -