BEA WebLogic User Manual page 42

Establishing a Target for SAP
The Advanced tab contains the following fields:
•
•
•
•
3-8
Connection pool size. This field is used to specify the number of client
connections in a pool you want to make available to SAP for Web service calls.
A default connection pool size of 1 is available by default. If you want to use a
connection pool size that is greater than 1, enter the value in this field.
Connections to an R3 server take up valuable resources on both the client and the
remote server. The section of SAP documentation "Memory Management
(BC-CST-MM)" explains in detail the resources required on the SAP system. A user
logon also consumes processing time. You can create a pool of connections that
will be continually recycled to minimize the resource and time constraints. The size
of the connection pool will be determined by the size of your SAP server, available
memory, maximum logons and the size of your client Java Virtual Machine. In
estimating the size of the pool, you may calculate pool size by the amount of server
resources to be consumed, the number and size of the documents to be received,
and the size of your Java Virtual Machine.
Connection pool name. Enter a name for your connection pool only if you
specified a connection pool size that is greater than 1.
BAPI Exception Handling. If your application is Java centric, you can select Throws
Exception so that code components may catch the exception and react
accordingly. If your application is document based, you can select Creates
Document to have an XML document created that contains the Java exception. It is
up to your application to read the XML document and obtain the error.
Commit with Wait. All SAP Business Objects that change data must commit work
to the database. Some BAPI's developed in version 3.1 of the R/3 system, use an
internal commit behavior and their commit behavior cannot be changed by the
adapter. As soon as they are called, they commit the work they have done. BAPI's
developed since release 3.1 use the external commit method. The adapter issues a
commit command, and the commit is put in the database que. If there is some
application error in the first part of the commit, the error message "Posting could
not be carried out" will be returned, and the adapter will roll back the transaction. If
in writing to the database a database error occurs, a short dump will be issued in
the database records of SAP, but no message will be returned to the adapter about
the failure. If a high degree of accuracy is needed in your application, select "With
Wait" , and the adapter will wait until all records have been physically written to the
database before returning from the function call. The "Commit With Wait" has a
definite performance impact on your adapter performance, use it with
deliberation. The commit behavior of BAPI's is found in SAP documentation under
"Bapi Programming Guide and Reference (CA-BFA)" .
This option is disabled by default.
BEA Systems, Inc.