configuration.html

SAP ERP的二次开发

            numbers and dates of the JCo middleware and the JCo library must be equal).
        <li>The version of the <tt>rfccm</tt> | <tt>librfc32</tt> library found via the OS specific
            library path environment variable is too old (for example you forgot to copy the <tt>librfc32.dll</tt>
            to the <tt>&lt;WinDir&gt;\system32</tt> directory and an older version is loaded from there).
        <li>The <tt>sapjcorfc</tt> library, the <tt>rfccm</tt> | <tt>librfc32</tt> library or
            both lack the execute permission flag.
        <li>The <tt>sapjcorfc</tt> library, the <tt>rfccm</tt> | <tt>librfc32</tt> library or both do
            not have the same bit width as the JVM.
        <li>The <tt>sapjcorfc</tt> library, the <tt>rfccm</tt> | <tt>librfc32</tt> library or both were
            from a different JCo distribution and are not for use with your operating system and/or
            your hardware processor.
        <li>The <tt>sapjcorfc</tt> library, the <tt>rfccm</tt> | <tt>librfc32</tt> library or both require
            a higher operating system version.
    </ul>
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Version dialog</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        You can check if JCo is installed correctly by starting its About dialog. This can conveniently be done
        by using the command<br><br>
           <code>&nbsp;&nbsp;&nbsp;java -jar {sapjco-install-path}/sapjco.jar</code><br>
        or<br>
           <code>&nbsp;&nbsp;&nbsp;java -classpath {sapjco-install-path}/sapjco.jar com.sap.mw.jco.About</code><br><br>

        The command will pop up a dialog containing all relevant JCo version information. On non-windowing systems
        you can get the same information printed to the console by typing<br><br>
           <code>&nbsp;&nbsp;&nbsp;java -jar {sapjco-install-path}/sapjco.jar -stdout</code><br>
        or<br>
           <code>&nbsp;&nbsp;&nbsp;java -classpath {sapjco-install-path}/sapjco.jar com.sap.mw.jco.About</code><br>
           <code>&nbsp;&nbsp;&nbsp;-stdout</code><br><br>

        There should be no exception or error thrown and all versions should be listed with their correct version
        numbers and date. Otherwise please see the above chapter "runtime loading mechanism" for possible installation
        or configuration errors.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Network configuration</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
    JCo uses the native RFC library for its RFC communication. The RFC library for its part uses the CPI-C
    protocol based on TCP/IP for its low level network communication. Usually the TCP/IP protocol is a
    communication service provided by the operating system. So, as a prerequisite for JCo to work, the TCP/IP
    service must be configured.<br>
    If you have a working SAPGUI installed on your machine all necessary TCP/IP configuration steps should have
    been already made during its installation process. But if you install JCo from scratch on a new system, you
    have to take care of the following:<p>
    <ul>
        <li>Make sure that the SAP application, message and gateway servers or alternatively the SAP router
            can be reached physically by using their IP addresses (<tt>ping&nbsp;&lt;nnn.nnn.nnn.nnn&gt;</tt>).
            If this won't work please ask your network administrator for help.
        <li>If desired, make sure that the SAP application, message and gateway servers or alternatively the SAP
            router can also be reached by using their logical host names (<tt>ping&nbsp;&lt;hostname&gt;</tt>).
            If they cannot be reached this way please check your DNS (Domain Name Service) service entries or
            maintain the respective host name in your local hosts file (for Windows systems:
            <tt>&lt;WinDir&gt;\system32\drivers\etc\hosts</tt>).
        <li>If you would like to use the load balanced log on, check if the SAP message server service and its
            TCP port is defined in the services file. There must be an entry of format <tt>"sapms&lt;SID&gt;&nbsp;&lt;portnumber&gt;/tcp"</tt>
            in the services file where <tt>&lt;SID&gt;</tt> = 3-letter SAP System ID. (In Windows systems the
            services file is usually stored at <tt>&lt;WinDir&gt;\system32\drivers\etc\services</tt>.)
        <li>If you would like to omit the message server host name in your log on parameters for a load
            balanced log on, please maintain an entry of format <tt>"&lt;SID&gt;=&lt;hostname&gt;"</tt> in the file
            <tt>sapmsg.ini</tt> where <tt>&lt;SID&gt;</tt> = 3-letter SAP System ID. The RFC library will try
            to read a missing message server host name from this file. It will be searched in the current
            working directory or in the directory specified by the shell environment variable
            <tt>RFC_LOGON_INI_PATH</tt>.
    </ul>
    For more information on the SAP technical infrastructure, network communication and configuration please have a
    look at the SAP Service Marketplace section "Network Integration" at
    <a href="http://service.sap.com/network">http://service.sap.com/network</a>.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Application configuration for Unicode SAP Systems</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        Generally you should make sure that your repositories always hold the correct meta data for the related
        future RFC client calls and/or server requests. Usually this is done by creating standard dynamic
        <tt>JCO.Repository</tt> instances with a <tt>JCO.Client</tt> or better a <tt>JCO.Pool</tt> which are
        connected to the same SAP backend system as the corresponding future application client calls and/or
        server requests. It is especially important that you don't mix up Unicode and non-Unicode calls. For
        doing RFC calls to and from a Unicode SAP Systems you will also need a corresponding repository holding
        the appropriate Unicode meta data. For RFC calls to and from Non-Unicode SAP Systems you will need
        a repository holding the appropriate Non-Unicode meta data.<p>
        If you would like to do RFC outbound calls from a Unicode SAP System to a <tt>JCO.Server</tt> instance,
        the server must be created using the additional server property <tt>jco.server.unicode=1</tt>. Furthermore
        you have to set the <tt>&nbsp;Unicode&nbsp;</tt> option for your RFC destination in transaction <tt>SM59</tt>.
        This option can be found on the Tab <tt>"Special Options"</tt>, section <tt>"Character Width in Target System"</tt>.<p>
        For RFC outbound calls from a Non-Unicode SAP System to a <tt>JCO.Server</tt> instance or for any inbound
        RFC calls to Non-Unicode or Unicode SAP Systems you don't have to do any special configuration tasks.
    </td></tr>
</table></div>

<tr><td valign="top" align="left">&nbsp;</td></tr>
<tr><td valign="top" align="left"><SPAN class=head>Tracing mechanisms</SPAN></td></tr>
<tr><td valign="top" align="left">
<div class="textblack"><table cellSpacing=0 cellPadding=2 border=0>
    <tr><td class="faqw">
        JCo's tracing mechanism can be turned on by setting the following java environment
        properties at startup:<br><br>
           <code>&nbsp;&nbsp;&nbsp;-Djco.trace_level=N&nbsp;(where 0 &le; N &le; 10 with 10 = most detailed trace)</code><br><br>
        and optionally<br><br>
           <code>&nbsp;&nbsp;&nbsp;-Djco.trace_path=&lt;PATH&gt;</code><br><br>
        If a trace path is set the JCo traces will be written to one or multiple files named
        <tt>JCO&lt;date&gt;_&lt;time&gt;.&lt;no&gt;.trc</tt> in the specified <tt>PATH</tt> directory. Otherwise the JCo
        traces will be written to the standard output stream (default is an output to the console).<br>
        The same tracing behavior can be achieved by modifying the program code calling the JCo APIs
        <tt>JCO.setTraceLevel(int)</tt> and/or <tt>JCO.setTracePath(String)</tt> accordingly.<p>
        The RFC library tracing mechanism can be turned on by setting the shell environment variable <tt>RFC_TRACE=1</tt>
        before starting the JCo Java process. For a more detailed output, you may additionally set the shell environment
        variable <tt>RFC_TRACE_DUMP=1</tt>. The RFC library trace files are named <tt>rfc&lt;processID&gt;_&lt;threadID&gt;.trc</tt>
        and will be written to the current working directory or - if set additionally - to the directory specified by the shell
        environment variable <tt>RFC_TRACE_DIR=&lt;PATH&gt;</tt>. In case the shell environment variable <tt>RFC_TRACE</tt>
        is set to 1 then all connections will be traced by the RFC library. If you would like to trace only a special
        connection, you can turn on the RFC tracing individually by calling the <tt>setTrace(true)</tt> method of the
        appropriate <tt>JCO.Client</tt> or <tt>JCO.Server</tt> instance before connecting it or create these instances
        by using the additional properties <tt>jco.client.trace=1</tt> or <tt>jco.server.trace=1</tt>.
        <p>
    </td></tr>
</table></div>

<!-- ################################################################################ -->
</table></td> <!-- ### WORK AREA END                                              ### -->
<!-- ################################################################################ -->

</td></tr></table>
</tr></table>
</td></tr></table>
</body>
</html>