The user can define the application views and transformations between these common objects and their application views.įor convenience and grouping, procedures and events are organized into business objects. Each application can specify the events and procedures it is interested in. To reload the repository, click on a project in the reload menu.Įach component that is integrated with Applications InterConnect is referred to as an application. These are accessed by clicking File - Reload. When a project is opened in a workspace, it is automatically added to the list of recently opened projects. In contrast, each iStudio project stores information about the current repository. Workspaces store user settings and preferences (for example, SAP and DB login credentials) in iStudio. Several people may work on the same project. To create a project, you have to specify the Repository connection information including the repository name and host. In iStudio, a project defines a Repository connection. These sections describe the concepts implemented by iStudio. Figure 2-2 A graphical overview of design time and runtime phases in integrationĪpplications InterConnect modeling is accomplished using iStudio, an easy-to-use graphical tool. At runtime, the adapter retrieves the metadata from the Repository to determine the format of messages, and perform transformations between the various data formats, and route the messages to th3e appropriate queues under OMB. All the specifications are stored as metadata in the Applications InterConnect Repository.įor each application participating in a specific integration, Applications InterConnect attaches an adapter to it. They are:ĭuring the design phase, a developer uses iStudio to define the integration objects, applications which participate in the integration, and the specifications of the data exchanged between applications. If this paradigm is used, a message can be delivered only to one destination.Īpplication integration using Oracle Applications InterConnect involves two phases. Point-to-Point messaging is used when the sending application specifies a destination and the message is delivered only to that destination. The reply is sent using the point-to-point paradigm described below. Even though many applications might be listening for this message, only one of them receives the message and sends a reply. In this paradigm, the application that sends the request blocks-or waits-for a reply. Request/reply messaging is used when an application sends a message and waits for a reply. Using iStudio, you define which application is the publisher and the subscriber for a particular message. This is often referred to as a non-blocking call. Publish/Subscribe messaging is used when an application sends-or publishes-a message to each subscribing application, and does not wait for a reply. The definitions are used at runtime to route the messages appropriately. These paradigms are defined in iStudio at design time. This loose coupled paradigm ensures minimal modifications to integration when an application is modified or a new application is added.įigure 2-1 Hub and spoke integration methodology used in Applications InterConnectĪpplications InterConnect supports three messaging paradigms. Incoming messages likewise are converted from the common view to the application view and sent in to the application for processing. At runtime, the metadata is retrieved from the repository by the adapter and used to map the application view of a specific data object to the common view and sent out as a message. In iStudio, this "application view" of the data is mapped to a common view and stored as metadata in the Applications InterConnect Repository. The model supports a hub-and-spoke architecture at the design level.Įach application possesses a specific format for each data structure used in the application. This chapter contains the following sections:Īpplications InterConnect modeling is primarily based on the definition of a common format for data to be exchanged between interconnected applications.
#ISTUDIO PUBLISHER 1.3 HOW TO#
It also explains how to perform important tasks including publishing and subscribing to an event using iStudio. This chapter describes Applications InterConnect's design time concepts and iStudio, the GUI-based application for creating metadata that describes events, objects and other types of messages that interconnected applications use during runtime.
0 kommentar(er)
