Skip Navigation Links | |
Exit Print View | |
Configuring Oracle Java CAPS Master Index (Repository) Connectivity and Environments Java CAPS Documentation |
Configuring Oracle Java CAPS Master Index (Repository) Connectivity and Environments
Master Index (Repository) Environment Overview
Defining Connectivity Components for a Master Index (Repository)
Defining Master Index (Repository) Server Connectivity Components
Creating the Master Index Server Connectivity Map
Connecting Master Index Server Connectivity Map Components
Defining Collaboration Client Connectivity Components for a Master Index (Repository)
Adding Master Index Methods to a Java Collaboration
Creating the Collaboration Client Project Connectivity Map
Connecting Collaboration Client Connectivity Map Components
Adding the JMS Topic to the Collaboration Client Connectivity Map
Configuring the Outbound Collaboration
Defining Business Process Client Connectivity Components
Including Master Index Methods in a Business Process
Connecting the Business Process Components
Creating the Business Process Client Connectivity Map
Connecting Business Process Client Connectivity Map Components
Creating the Environment for a Master Index Application (Repository)
Adding a Logical Host to a Master Index Environment (Repository)
Adding Servers to a Master Index Environment (Repository)
Adding an External System to a Master Index Environment (Repository)
Adding a Database External System to the Master Index Environment (Repository)
Once the master index server project is generated, you need to create a Connectivity Map that defines the flow of the application. You can also create connectivity components that define how data is transformed, routed, and processed between the master index application, Business Processes or Collaborations, and external systems. The following topics describe the connectivity components used in conjunction with a master index application.
The project that defines the master index application is known as the server project; the projects that define external system connectivity with the master index application through Collaborations or Business Processes are known as client projects.
Data can be processed by the master index application in four ways:
Data is processed through the Enterprise Data Manager (EDM). This process is defined by the Connectivity Map in the master index server project.
Data is processed from the external systems that share information with the master index application through Java Collaborations. This process is defined by the Connectivity Maps in the Collaboration client projects.
Data is processed from the external systems that share information with the master index application through a Business Process. Using Business Processes, you can also develop Oracle Java CAPS Composite Page Designer web pages to access data in the master index database. These processes are defined by the Connectivity Map in a Business Process client project.
A master index application can publish messages to a JMS Topic to broadcast to external systems. The topic is included in both the master index server project and client projects for the external systems receiving the broadcasts.
The connectivity components of a master index server project include the master index application files. Optional components include a JMS Topic and a database Adapter. The client projects that connect to the master index application use standard connectivity components of a Java CAPS project, with the addition of a master index method OTD. For more information about Connectivity Maps, see Adding and Connecting Project Components in Developing Oracle Java CAPS Projects.
The master index server project can include the following connectivity components:
Connectivity Map - Graphically describes the relationship between the web application components and the master index application components.
Application file - Contains the logic used by the master index application to process data into and out of the master index database. This file is automatically created when you generate the master index project.
Web application file - Contains the logic used by the Enterprise Data Manager (EDM) to process data and access the master index logic and database. This file is automatically created when you generate the master index project.
Oracle Adapter or SQL Server Adapter - Provides connectivity to the master index database. These components are optional since you can define the database connection pool through the GlassFish Application Server.
JMS Topic - A message destination conforming to the publish-and-subscribe (pub/sub) messaging paradigm. In this case, the master index application publishes to the Topic to broadcast messages to external systems. Note that master index applications publish to Topics, not to Queues. This component is optional.
The master index client projects can include any of the following connectivity components:
Connectivity Map - Graphically describes the relationship between the External Applications, Queues and Topics, Services, Web Connectors, and master index application. The Connectivity Map also contains the configuration information for each component’s connections, such as the polling interval and transactional behavior.
Master index application - Represents the master index application accessed by the client project. Each Collaboration or Business Process client project in the master index system must include the master index application in its Connectivity Map in order for those components to exchange information with the master index application.
Service - Provides a framework for a process or a Collaboration that contains the information required to execute a set of business rules.
Collaboration - Business rules describing the logic to be executed on the Object Type Definitions. These business rules include the data transformation and method calls to be executed by the Services and determine how data is processed into the master index database.
Object Type Definitions (OTDs) - Meta-data containers that describe external objects, including both data structure and methods. A custom method OTD is created in the master index project for use in the client projects to define how data is processed between the master index application and external systems. A custom OTD is also created to publish messages from the master index application to a JMS Topic.
External Applications - Logical representations of external software applications (called external systems) that are integrated by the Java CAPS system. External Applications allow the master index application to connect with external systems and are linked to a Service by means of an Adapter.
JMS Queues - A message destination conforming to the point-to-point (p2p or PTP) messaging paradigm. This means that one sender delivers a message to exactly one receiver.
JMS Topics - A message destination conforming to the publish-and-subscribe (pub/sub) messaging paradigm. This means that one publisher broadcasts messages to multiple subscribers, ensuring that all subscribers receive a message. Client projects can include a JMS Topic to which the master index application publishes, giving the external systems access to all data updates.
JMS Client - An internal link between a Service and a Message Destination (that is, a JMS Topic or Queue).
Adapters - An application-specific adapter linking an external application with Java CAPS.
Business Processes - A collection of actions and messages that revolve around a specific business task and that flow in a specific pattern to accomplish a business goal.
Web Connectors - A graphical representation of a set of Oracle Java CAPS Composite Page Designer web pages and activities.