SAP Integration via Enterprise Gateway SAP is one of the most popular enterprise resource planning (ERP) solutions available on the market today. Businesses looking. SAP Java Connector (SAP JCo) is a middleware component that enables the development of SAP-compatible components and applications in Java.

Supported Platforms SAP JCo 3.0 removes 32-bit support on Unix platforms. Only Linux (with Intel processors) and Windows (with Intel processors) now support the 32-bit SAP JCo. All other platforms require true 64-bit processing throughout. Some JVM settings cause the JVM to read as “mixed mode”, which is not compatible with SAP JCo. Some platforms require a specific flag of –d64 to enable complete 64-bit processing in the JVM.

For more information on supported platforms with SAP JCo 3.0, see. For supported JVM information that corresponds to each operating system, refer to SAP Note #1077727 in the SAP Service Marketplace. If a specific JVM is not included on the list of supported JVMs, then it is not supported by SAP R/3. Connection Pooling SAP JCo 3.0 introduces changes to the connection methodology that is used by the client (connections to SAP R/3).

Instead of connecting directly to the SAP R/3 server, clients now open a connection to a logical destination on the SAP JCo, which handles all SAP R/3 connection and pooling tasks. Connection pooling is now done per iWay target destination. However, the total number of all open connections count towards the SAP R/3 open connection limit. The Connection pool size parameter value in the destination target is the maximum number of peak connections that can be opened by the logical destination.

The SAP JCo does not allocate connections in advance, instead the initial request opens the first connection. Only if this first connection is busy when the next request arrives does another connection open, up to the peak limit. If the limit is reached, then the Connection wait time parameter value marks the time when all connections are in use, and another connection request arrives, before a “resource allocation” exception is generated. In addition, the Connection timeout parameter value is the maximum amount of time for a connection to remain active, whether in use or not. If there are longer running requests, then consider increasing this parameter value. If a number of very short requests are run, then decrease this parameter value for maximum performance and resource utilization.

Server Threads The SAP R/3 outbound Gateway creates one active connection per RFC destination for non SAP R/3 systems. For maximum throughput, the Thread count parameter is set to three (three server threads per RFC destination). This parameter can be found in the Advanced tab of Application Explorer when configuring channels. Usually, this leaves one thread to listen for requests, one thread to process a current request, and one thread to clean up from processing. In cases where a large amount of traffic on a particular RFC destination is required, there are a few SAP R/3 techniques that can be used for these situations. When more than one Program ID with the same name is registered for one SAP Gateway, the Gateway can be enabled for a 'load balancing' scenario, depending on the parameters in the Gateway profile on the SAP R/3 system.

It is recommended to consult your SAP R/3 system administrator for more information, but the profile will either be set to 0 (no load balancing), 1 (lowest counter), or 2 (lowest load). Your SAP R/3 system administrator can provide you with the required information on how to configure your destinations to take advantage of each situation. In addition to Gateway load balancing, the amount of SAP Gateway threads can be increased as well. Consult your SAP R/3 system administrator for more information. If the amount of threads is increased, then try and keep the ratio of Gateway threads to server threads at the same 1:3 ratio. For example, if the Gateway has 3 active threads for destination “X”, on the outbound server channel side, the server thread count is now 9. Serial Number For Dss Player Pro there. If load balancing is not enabled and you register multiple server channels with the same Program without performing Oracle schema validation, then it is possible to receive IDocs in the wrong channel because there is no routing on the channels or destinations.