Axis RightFax 8.5 Guía de instalación descargar pdf (Pagina 97)

13-21

performance. For example, that the Finder Page Size is set to 500. Aside from the delay in retrieving

that many records, the overhead of having a fetch size of 500 when the number of records may be

much smaller may exceed the savings in round trips. The maximum property provides a system-wide

constraint on the fetch size.

For updates and inserts, the application can use Oracle Batch updates to minimize round trips and

increase modification speed. The following properties control batch updates:

glog.sql.update.batch.on = true

glog.sql.update.batch.maximum = 30

The on property specifies whether the application should use the batch updates. If set to true, inserts

and updates will be batched whenever possible. The maximum property provides a system-wide

constraint on the batch size. Note that batch updating adds overhead when database operations

produce errors. Since the batch updating feature cannot provide information as to which record failed

the batch, on failure the application retries the update one-by-one to find the errant record.

Integration

Suppressing Persistence XML

There is a capability to suppress storing the full transmission XML in the i_transmission table, and

the full transaction XML in the i_transaction table for the RemoteQuery interface. Each of these

should reduce the space used by the raw XML in the database and help performance by reducing the

time to persist a transmission.

The full transmission XML is suppressed by setting the following property:

glog.integration.transmission.suppressPersistFullXml = true

Note: The TransmissionHeader will be stored in the i_transmission table even when this

property is enabled.

The Remote Query Transaction XML is suppressed by setting the following property:

glog.integration.transaction.suppressPersist.RemoteQuery = true

As of Oracle Transportation Management version 6.0, both of these properties are enabled by default.

Synchronization of Master Data

Repetitive updates of embedded elements like locations and items should be avoided since they

produce unnecessary processing. Location and item masters should be synchronized independently of

orders instead of embedding within the order. This practice will reduce inserts into I_TRANSACTION

and I_LOG tables, thus increasing performance by reducing storage needs.

OutXMLProfile for Outbound Integration and Notification

Out XML Profiles allow you to generate outbound XML and exclude portions of outbound XML with a

high degree of control. This is done by specifying what XML builder class files should be excluded when

generating XML documents or by selecting an XML template on which you can base the outbound XML.

Outbound XML includes integration and notification. Unnecessarily large outbound integration is a

common cause of performance issues. Reducing the size of the XML will greatly reduce the load on the

database and application server.

1 2 ... 92 93 94 95 96 97 98 99 100 101 102 ... 105 106

Sin comentarios

Axis RightFax 8.5 Guía de instalación Pagina 97