This chapter lists and describes best practices that are specific to the Oracle Application Adapter for SAP R/3. It contains the following topics:
Connection pooling is established for a session by setting the session attribute of the standard jdeRequest element. When the session attribute is an empty string, a new session is started. On the server, the SessionManager singleton class creates a new instance of a session object given the user name, password, and environment name. The session can be reused before it expires to avoid the overhead of session initialization. You can specify the session ID in the session attribute for an established session in an earlier request.
Session expiration is addressed by the sessionidle attribute of the standard jdeRequest element. This attribute, when given on a session creation request, specifies the amount of time in seconds that a session is allowed to be idle. If the SessionManager determines that a session has not had any requests processed in this amount of time, then it terminates the session and frees all associated resources. For more information, see the J.D. Edwards OneWorld Interoperability Guide.
Run time settings in the jde.ini file on the server control the load balancing configuration. These settings are in the [JDENET] and applicable [JDENET_KERNEL_DEFx] sections. All relevant settings are listed and described in the preceding section. You can control two types of processes:
Network jobs (JDENET_n)
Dedicated kernel process jobs (JDENET_k)
For more information, see the J.D. Edwards OneWorld System Administration Guide.
The Oracle Application Adapter for SAP R/3 supports standard JDE security.Security is managed by user profiles defined in the system. For more information, see the J.D. Edwards OneWorld Server and Workstation Administration Guide.
Multiple connections and multiple users depends on the user profiles that are defined in J.D. Edwards OneWorld. For more information, see the J.D. Edwards OneWorld Server and Workstation Administration Guide.
The J.D. Edwards XML solution supports well-formed XML documents. It also supports UTF8 and UTF16 Unicode standards for inbound processing and UTF8 standards for outbound processing.
Each transaction is assigned session ID by J.D. Edwards OneWorld. As a best practice, use application P92002 to investigate server-side error messages.