
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
Inbound Integration Options
Large Transmission Servlet
The LargeTransmissionServlet can be used for sending exceptionally large transmission(s) into Oracle
Transportation Management. The difference with WMServlet is that parsing of the XML is handled in
the servlet, and there is suppression of storing the complete transmission in the database. The
individual transactions are stored in the database. It persists only the individual transactions, not the
transmission. Refer to the Integration Guide for more information on this subject.
Oracle Advanced Queuing
Oracle Advanced Queuing (OAQ) provides an alternate way of sending and receiving XML
transmissions to/from Oracle Transportation Management. The main benefit to using OAQ is the added
level of guaranteed message delivery provided by a persistent message queue. An additional benefit is
the elimination of the web and application server from the processing of persisting a transmission.
This has the benefit of reducing the load on the web and application servers. Refer to the Data
Management Guide for details on the setup for use of Oracle Advanced Queuing.
Web Services
You can send data to Oracle Transportation Management via a web service call to the Oracle
Transportation Management application server. The performance advantage of this approach is the
elimination of the web tier from the process of persisting the XML. This should increase UI
performance by reducing the overall load on the web server. Refer to the Integration Guide for more
information on this subject.
User Interface
Finder Page Size
A Finder Page is the Oracle Transportation Management terminology for the standard result page
which is returned when running an Oracle Transportation Management finder query. The number of
records returned per page is configurable via the “Finder Page Size” user preference. Increasing this
from the default value of 25 has a direct impact on the performance of loading this page due to the
increased amount of data that needs to be processed and displayed. Values greater than 100 are likely
to make the performance unacceptable.
User Favorites
Favorites allow you to limit initial Find () results so that your favorite results are displayed first. For
example, you can create a favorite for locations. In that favorite you specify the top 10 locations which
you use on a regular basis. Then whenever you use the Find () button the system first displays those
10 locations. If you want to find a different location you are given the option to search for more
locations.
Adding Search Fields to Finders (Grid-Flattening)
Grid flattening enables administrators to present "pseudo fields" for search, result, and other manager
pages that are customized to the needs of their users. Pseudo fields "flatten" a grid by presenting field
labels that are more specific than the default fields. For example, a PO Number field could be added to
the order base search page, so users can search for purchase orders directly by their numbers. Grid
flattening is used to make it appear as if data from a child database table is on a parent database
table. Using grid flattening on search and result pages should be done with caution since the resulting
query is more complex and therefore susceptible to slower performance.
Comentarios a estos manuales