
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
The Oracle Transportation Management web server uses the Oracle HTTP Server (OHS) web server
and the Tomcat Java servlet engine to manage the user interface and communications with the
application server.
Application Server
The application server controls the application logic and communicates that logic between the web
server and the Oracle Database. The application server runs Oracle WebLogic Server software to
manage system-level details and operates at the center of the Oracle Transportation Management
multi-tier architecture. In this architecture, business logic is executed in the application server, rather
than in client applications. The resulting "thin" client, allows the client to manage the presentation
layer, the application server to manage the business logic, and the back-end data services to manage
the data.
Database Server
The database server is the central repository for all the data entered in Oracle Transportation
Management. The database server communicates with the application server to deliver the
appropriate data to the user based on the Oracle Transportation Management application logic. The
database server also communicates with the integration server to handle the import and export of
Oracle Transportation Management data with other systems.
Please see the Technical Architecture Guide for the supported databases.
Integration Server
The integration server is responsible for:
Accepting Oracle Transportation Management XML from an Enterprise Application Integration
(EAI) solution.
Persisting XML transmission to a staging table.
Accepting requests from the Oracle Transportation Management application server to build
Oracle Transportation Management XML from staged data.
Sending Oracle Transportation Management XML to an EAI solution.
The EAI solution is used as a secure data pipeline and data transformation engine and is responsible
for:
Sending and receiving EDI flat files to and from an EDI Van.
Transforming EDI flat files to Oracle Transportation Management XML.
Login security (communication is permitted only from registered IP addresses).
Encryption security (using https).
Guaranteed delivery (only if a partner server is on the remote side).
The integration server’s job is to safely store XML transmissions and transform the XML transmissions
into internal tables. The Oracle Transportation Management application server is responsible for
initiating jobs that move data to and from staging tables and notifies the application server when new
data has arrived in the staging table. The application server must notify the Integration server when it
has moved new data to the staging table.
The integration server does not perform data validation. Data validation occurs when data is
transferred from the staging table to the application server tables. The staging table does not enforce
referential integrity or constraints.
Comentarios a estos manuales