Oracle Application Server InterConnect User's Guide 10g (9.0.4) Part Number B10404-01 |
|
This chapter describes how to use iStudio to create, publish, and subscribe to events. This chapter discusses the following topics:
An event is an integration point used to model the Publish/Subscribe paradigm. An event has associated data that is the common view of all the data to be exchanged through this event. In other words, the data associated with an event in the common view must be a superset of the data of participating applications.
For example, App1
and App2
publish customer names and App3
subscribes to it. If App1
publishes First Name
, Last Name
, and Middle Initial
, and App2
publishes First Name
, Last Name
, Prefix
, and Suffix
, the event could be defined as follows:
New Customer Event Prefix First Name Last Name Middle Initial Suffix
Note: Standard application-independent definitions can be used for event-associated data in the common view such as Open Applications Group XML business object definitions. |
Event maps allow application data to be mapped to an OracleAS InterConnect event without the application having to know about the OracleAS InterConnect event itself. For example, if an application is publishing a Create_Customer
event, it does not have to explicitly state that the message it is publishing corresponds to an OracleAS InterConnect Create_Customer
event. Instead, using iStudio, certain fields in the application view can be associated to help OracleAS InterConnect determine which event the message maps.
In addition, if an application publishes exactly the same structure of data for two or more events, event maps help OracleAS InterConnect distinguish which message corresponds to which event. For example, an application publishes the same Customer Application Data Type regardless of whether it is a Create_Customer
or an Update_Customer
event. Through event map, OracleAS InterConnect can determine which messages correspond to Create_Customer
and Update_Customer
.
To create an event:
Enter the information in the following fields:
Business Object--The name of the category to which the event belongs. Select a category from the drop down list.
Event Name--The name of the event. Only alphanumeric characters can be used.
OAI/V1--The owner and version number of the Business Object. This field cannot be edited.
The publish/subscribe paradigm is an existing technology for exchanging information between a provider (publisher) and a set of users (subscriber). This paradigm is one of the most common ways for adapters to communicate with each other through the hub.
Publishing an event in an application in iStudio involves using the Publish Wizard. To start the Publish Wizard:
Application--The name of the application that is publishing the event.
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 application using a user-defined bridge.
XML--OracleAS InterConnect communicates with the application using XML data described through a data type definition (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 Event page, the Define Application View page displays:
Once an event is selected to publish, 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.
The Event Map dialog displays:
Mapping involves copying the individual fields or simple shape-change transformations. After clicking Next on the Define Application View page, the Define Mapping page displays:
Click New to define new mappings. The Mapping Parameters dialog 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:
|
Subscribing to an event in an application in iStudio involves using the Subscribe Wizard. To subscribe to an event in an application:
Application--The name of the application subscribing to the event.
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 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 event to subscribe to, the Define Application View page displays:
Once an event is selected to subscribe to, 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.
Mapping can either involve copying the individual fields or simple shape change transformations. After clicking Next on the Define Application View page, the Define Mappings page displays:
|
![]() Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|