Terminology in Oracle EBS Web ADI
(Copyright notice, I original or translation of the article to be reproduced, such as reproduced for personal study, please specify the source; otherwise please contact me, violators will investigate)
asynchronous invocation
Asynchronous calls are like this, and unlike processes in an Oracle application that introduce data from an interface table, uploading data to an interface table is a separate process (for example, they do not occur at the same time).
When the upload starts, the ingestion program is called and the request ID is returned to the user. Oracle applications will continue to run the ingest program in the background, and users need to manually check that the ingest is not handled correctly. That means that the commit upload and the ingestion program completion are not synchronized, so asynchronous terminology is used.
Client
Some software requires another part of the software to perform some functions (server side). The client passes the parameters to the server.
Content
This is the information that will be downloaded to the viewer. Multiple content can be defined as a separate content class. Content is either passed to or selected in the Create Document page process, which determines the content class that will be used to obtain the content data.
Content column
The name defined in the metadata to represent a column that exists in the content. The user mapping content is listed in the interface column/API parameter so that the data is downloaded to the appropriate field in document.
Content column
This is the Java code that contains the business and processing rules that can be inserted into the Web adi download architecture. This code processes the parameters that are passed into the Web Adi to get information from the selected content.
Create a Document page flow
This page stream contains a series of Web Adi interfaces through which the end user can choose from several parameters to create documents on the client machine. User-selectable parameters include: Language, Viewer, integrator, layout, content, and mapping. Depending on the content you choose, you may also need some additional parameters.
Document creation Shortcut settings
The parameters for these settings are all used to create the document page flow. These parameters or when the user selects a document creation shortcut from the document page in which the document page flow is created, or when the Create document page stream is called directly from the app or form, is passed to the Create Document page stream (digression: The document page is the first page in the document page flow that is created. However, it is not displayed until the shortcut is saved).
Dynamic parameters
A dynamic parameter is a parameter that is defined with metadata and stored in the Web Adi store, but its value must be dynamically determined at run time.
Integrated device
An integrator is a web Adi concept that encapsulates all the information needed to pass data between desktop applications and Oracle applications. The definition of an integrator may contain information about open interface tables, validation, business rules, and data that can be downloaded.
Integrator Developer
An integrator developer is a developer who defines the metadata that is needed in the Web Adi. Metadata includes: integrators, table/view definitions, layouts, mappings, SQL statements, and parameters. An integrator developer is typically a system administrator, or a user who understands the knowledge of Web ADI, tables, and related product business rules.
Interface
Interface is a web Adi concept for uploading data from a specific API or interface table/view to a column definition in a database. You can define multiple interfaces for a single generator.
Language
This is the language in which the generated document is used, and all interactions within the document use that language.
Layout
A layout tells the Web Adi which columns are displayed in the Desktop app document, and how the columns are displayed, including formatting. WEB Adi provides a series of interfaces to users and integrator developers to create their own layouts. Integrator developers can provide built-in layout data.
Mapping
A mapping is used to define a connection between a content column and a column in the table/api interface. For example, a column in an SQL query that will be downloaded into an MS Excel spreadsheet is mapped to a column in an Open Interface table (the downloaded information is uploaded to the table).
Parameters
A parameter is a name/value pair that is used to pass information on the client and server side. The parameter can be a text name or a position in a list. Parameter values must have a data type that is recognized by both the client and the server.
Typically, a description of the parameter value is available to the user.
Example: param name = "Bne:integrator", datatype = string, param value = 231:journals_11i with description "journals for Applica tions 11i ".
Service side
Some software that serves the client. The server receives parameters from the client.
Static parameters
A static parameter is a parameter that is completely defined in metadata and stored in the Web Adi store. A static parameter can be read, and its value can be obtained immediately by the stored default value or by a specific value stored.
Synchronous invocation
Synchronous calls occur when the data is uploaded to the interface table and introduced to Oracle applications in the same process. A synchronous call must commit the ingest and wait for the ingestion program to finish running, and decide whether the introduction succeeds or fails and returns these details to the user. In this case, the user does not have to manually check whether the ingestion program was completed successfully.
Viewer
A viewer is a web Adi concept, which is a desktop viewing application that generates documents (here is Excel, primarily supported by Excel and Word).
