Oracle Application Server InterConnect User's Guide 10g (9.0.4) Part Number B10404-01 |
|
This chapter describes using iStudio to create, invoke, and implement procedures. This chapter discusses the following topics:
A procedure is an integration point used to model the Request/Reply paradigm. This is a modeling paradigm only, no actual procedures are called. An application can either invoke a procedure to model sending a request and receiving a reply, or implement a procedure to model receiving a request and sending a reply. Similar to events, a procedure has associated data. While an event is only associated with one data set, a procedure has two data sets--one for the request or IN
data and one for the reply or OUT
data.
For example, if a Get_Address
procedure is defined so that the request contains the social security number, SSN
, for a person and the reply contains the address in four fields--Street
, City
, Zip
, State
, then the procedure is defined as follows:
get Address Procedure SSN IN Street OUT City OUT Zip OUT State OUT
Procedures can be used to implement both synchronous and asynchronous Request/Reply.
Note: Standard application-independent definitions can be used for procedure-associated data in the common view such as Open Applications Group XML business object definitions. |
To create a procedure:
Enter information in the following fields:
Business Object Name--The name of the category to which the procedure belongs. Select from the drop down list.
Procedure Name--The name of the procedure. Only alphanumeric characters can be used.
OAI/V1--The owner and version number of the procedure. This field cannot be edited.
An adapter can activate a procedure which is developed by a user or provided as part of an adapter package, as part of the processing of an integration event or common view.
A common view procedure is an event that can be invoked or implemented through the use of a request/reply paradigm, also know as synchronous invokation. The procedure is modeled as an integration business event with the parameter for the invokation and return of the result once the procedure has been executed.
The following example describes how to model an integration event or common view as a procedure.
Invoking a procedure in iStudio involves using the Invoke Wizard. To start the Invoke Wizard:
Application--The name of the application invoking the procedure. Select an application from the drop down list.
Message Type--This field specifies the mode of communication between OracleAS InterConnect and the application. Select from the following message types:
Database--OracleAS InterConnect communicates with the application using the database.
Generic--OracleAS InterConnect communicates with the application using a user-defined bridge.
XML--OracleAS InterConnect communicates with the application using XML data described through a DTD using the FTP, SMTP, HTTP, MQ Series, or user-defined adapters.
AQ--OracleAS InterConnect communicates with the application through Oracle Advanced Queues using the Advanced Queue adapter. The payload can be Oracle Objects where fields may be XML or RAW XML.
D3L--The adapter communicates with the application using D3L.
After clicking Next on the Select a Procedure page, the Define Application View page displays:
Once a procedure is selected to invoke, the application view is defined. The application view page is initially an empty table. Define the attributes using Add or import the definitions from a database or an API Repository using Import.
See Also:
Mapping arguments involves copying the individual fields or simple shape-change transformations. After clicking Next on the Define Application View page, the Define Mapping IN Arguments page displays:
To map fields in the application view to fields in the common view, use a transform. For example, to map fields in the FirstName
and LastName
in the common view to Name
in the application view, use the ExpandFields
transform.
See Also:
|
The following steps illustrate this example:
ExpandFields
.
The transformation may have parameters. If the Apply button is clicked, the Mapping Parameters dialog displays:
In the Parameters field, enter the values for the transformation parameters. For example, a blank value indicates a value for the separator parameter.
Mapping arguments involves copying the individual fields or simple shape-change transformations. Use this page to map the common view return arguments to the application view return arguments.
Implementing a procedure in iStudio involves using the Implement Wizard. To start the Implement Wizard:
Use this page to select a procedure to implement.
Application--The name of the application implementing the procedure. Select an application from the drop down list.
Message Type--This field specifies the mode of communication between OracleAS InterConnect and the application. Select from the following message types:
Database--OracleAS InterConnect communicates with the application using the database.
Generic--OracleAS InterConnect communicates with the application using a user-defined bridge.
XML--OracleAS InterConnect communicates with the application using XML data described through a DTD using the FTP, SMTP, HTTP, MQ Series, or user-defined adapters.
AQ--OracleAS InterConnect communicates with the application through Oracle Advanced Queues using the Advanced Queue adapter. The payload can be Oracle Objects where fields may be XML or RAW XML.
D3L--The adapter communicates with the application using D3L.
After selecting the procedure to implement, the Define Application View page displays:
Initially, this page is an empty table, used to define the application view. Attributes can be defined by using Add. Attribute definitions can be imported from a database or an API Repository by using Import.
Mapping may involve copying individual fields, or simple shape-change transformations. After clicking next on the Define Application View page, the Define Mapping IN Arguments page displays:
Use this page to define mapping IN
arguments.
After clicking Next on the Define Mapping IN Arguments page, the Define Mapping OUT Arguments page displays:
Use this page to define mapping OUT
arguments.
After clicking Next on the Define Mapping OUT
Arguments page, the Define Stored Procedure page displays:
If the message type selected was database, the data is received by a stored procedure. In this stored procedure, the action performed when the values are returned to the application can be specified. The adapter invokes the stored procedure at runtime with the appropriate data.
The following arguments will be returned:
iStudio generates stored-procedure stubs to enable an application to interface with the OracleAS InterConnect run-time easily. These stubs are exported to a file using the export functionality.
To export stored procedures:
To view the directory page, click Browse.
|
![]() Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|