Character Encoding and Byte Order

5-12 Oracle Fusion Middleware Users Guide for Technology Adapters order to be used, by using the Adapter Configuration Wizard. When encoding and byte order are not specified, the default values are US-ASCII and BIG_ENDIAN. To specify the encoding and byte order values, which are applicable only if you are using translation, you must perform the following steps in the Protocol page of the Adapter Configuration Wizard:

1. In the EncodingByteOrder section of the Protocol page, select the Specify

EncodingByte Order option, as shown in Figure 5–11 . Figure 5–11 The Adapter Configuration Wizard - Protocol Page 2. Perform one of the following tasks to set the encoding:

a. To use the encoding specified in the schema file, leave Encoding unchecked.

b. To specify the encoding using the Adapter Configuration Wizard, select Encoding , and then select an encoding type from the Encoding list. 3. Perform one of the following tasks to set the byte order:

a. To use the byte order specified in the schema file, select Use Byte Order Value

from the schema . b. To specify the byte order using the Adapter Configuration Wizard, select ByteOrder , and then select a byte order from the ByteOrder list.

4. Click Finish.

Once you click Finish, the Configuration Wizard displays a page that indicates that you have finished configuring the Socket Adapter.

5.3.4 Performance Tuning

The Oracle Socket Adapter supports performance tuning features, including: ■ Section 5.3.4.1, Configuring Oracle Socket Adapter Connection Pooling Note: If you select Encoding, then the encoding type specified using the Adapter Configuration Wizard takes precedence over the encoding type specified in the NXSD file. Oracle JCA Adapter for Sockets 5-13 For more information about performance tuning, see Oracle Socket Adapter Tuning in the Oracle Fusion Middleware Performance and Tuning Guide.

5.3.4.1 Configuring Oracle Socket Adapter Connection Pooling

One way to optimize Oracle Socket Adapter performance is by using a Connection Pool. You can use a connection pool as long as the socket server you are connecting to does not close the socket with each interaction. A connection pool lets you use a socket connection repeatedly, avoiding the overhead of creating a new socket for each interaction. You must configure the connection pool for the Oracle Socket Adapter using the Oracle WebLogic Server console. How to configure Oracle Socket Adapter connection pooling: 1. Log into your Oracle WebLogic Server console. To access the console navigate to http:servername:portnumberconsole.

2. Click Deployments in the left pane for Domain Structure. The Summary of

Deployments page is displayed. Figure 5–12 Oracle WebLogic Server Console - Summary of Deployments Page

3. Click SocketAdapter. The Settings for SocketAdapter page is displayed.

4. Click the Configuration tab.

5. Click the Outbound Connection Pools tab, and expand

javax.resource.cci.ConnectionFactory to see the configured connection factories, as shown in Figure 5–13 : Note: The Connection Pool feature is applicable to outbound interactions only.