APPLICATION INTEGRATION ARCHITECTURE CONCEPTS(INTEGRATION IS THE KEY)

EBM CONCEPTS :

->Structured XML message for message interchange between applications and services.
->Specific content of an EBO that is needed to perform specific activity
->EBM payload is restricted view of EBO content.It includes only the content that is necesary to perform the specific operation.
->EBM includes -header and data area.Header = message metadata.Dataarea=defines the action verb and contetnt payload.
->EBM messaging model is based on OPEN APPLICATIONS GROUP INTEGRATIONS ->SPECIFICATIONS,BUSINESS OBJECT DOCUMENT.

What is EBM header?

Tracking important information
Auditing
Source and target systems
Error handling

Contents of EBM metadata(header) :

EBMID,EBMName,EBOName,and CreationDatetime


EBM Data Area:

AIA verb: Create,update,delete,query(single),query(list)sync,validate,process

Payload :Complete EBO(Create),Unique identifier(delete) etc etc.


What is differenece between single and List EBM:

There are distinct operations and payloads for processing a single object as compare dto multiple instances.

Examples -
CreateSalesOrderEBM - processes single object
CreateSalesOrderListEBM- multiple instances of object

EBS(ENTERPRISE BUSINESS SERVICES):

They provide an integration to the customer's choice at backend.Simply they are routers.
They provide loose coupling of requesters and providers.
EBS are generally coarse grained and typically perform a business activity :creating account in billing system
Operate only on Application indepenedent cannonical objects.Deal with EBMS not ABMS.

Process are as follows (EBS):

EBS receives the message from calling application.
Sends the EBM to the appropriate ABCS.
ABCS transforms EBM to ABM and sends ABM to the praticipating applications.
After response comes back,EBS receives the response and returns EBM to the calling application

Responsibilities (EBS ):

Receive request from calling application
Evaluate the routing rules.
Identify the service provider
Enrich the EBM with service provider details.
Route the message to relevant service provider
Receive the response in request response pattern

 Advantage:

•Business driven

•Location Transparency

•Single purpose

•Loosely coupled

•Reusable

•Composable

•Standards based

•Technology neutral

 


EBS types :

1> Entity services :

Entity services expose operations that act on specific EBO.
Entity services are routed as mediator routing services.
Entity services receive and return messages in form of EBM'S.
Example entity EBS includes Customer,Party,ITEM,Sales.

2> Process Services:

Each enterprise business flow has enterprise business services.
EBF orachestrates multiple EBS to implement certain business function.EBF are not long running processes,they are short lived.
Process services are implemented as mediator.
Process services receive and return messages in form of EBM's.


EBO(ENTERPRISE BUSINESS OBJECTS)

-> Oracle has developed many standard objects and services called Enterprise Business Objects.
->AIA foundation pack provides standard Enterprise Business Repository where all the objects and services are stored.
->With AIA one can build own custom business process integrations

Components:

->A library of common objects and services
->A integration management infrastructure
->A proven methodology based on yrs of exp.
->Infrastructure components
->Prebuilt reference.

AIA advantages :

Minimize risk
Reduce costs
Application design and not technology.



What is PIP?

A PIP is a collection of multiple Pre-build processes based on Service Oriented Integration. It combines multiple services, applications, or systems

 

HOW TO SET ENVIORMENT VARIABLES(ANT)

1>Go to my computer

2>Right click,select advanced system settings

3>Click advanced

4>Select enviorment variables

5>Select new

6>Give variable name  eg: ANT_HOME,give value :D:\ant(path where ant file resides)

7>Go down,select path ,go at end give ; then this path->%ANT_HOME%\bin;

8>You have to create another variable select new: give name eg:java_home,value:C:\Oracle\Middleware\jdk160_29

(2nd variable to set jdk160_29 ,ie jre path otherwise it will throw java.exe error)

9>Click ok,then test it,go to ant path(mine: D:\ant) ,type :ant -v or ant -h ,it should reply something

BPEL HUMAN WORKFLOW 11g Tutorial

In SOA 10g, human workflow is an independent component. It had to be deployed and configured separately. In SOA 11g, it’s tightly integrated with other components through the SCA architecture. The main components of SOA 11g human workflow are shown in the following figure.  On the left are the workflow initiators (typically BPEL or a mediator). However, the Human Task component is also exposed as a SOAP service that can be invoked independently. In the middle is the core human workflow component that is formed by a combination of workflow services. We will discuss about these services later. On the right, there are the client applications that present the user the necessary web (or another) interfaces to act on the task.

• BPEL invokes human task component when a manual task needs to be performed

• A task is created in the Human Task service component. (The task metadata is used by the component to manage lifecycle of the task)

• The Human task service component identifies the necessary users/roles/groups using an identity service and assigns the task

• These tasks are presented to the user through the client apps. (Oracle BPM worklist is the default app)

Human workflow Features

Here is a list of features that are supported by human workflow.  (http://docs.oracle.com/cd/E23943_01/dev.1111/e10224/bp_introhwf_shared.htm#CIHGEFCI). 

• Human interactions with processes, including assignment and routing of tasks to the correct users or groups

• Deadlines, escalations, notifications, and other features required for ensuring the timely performance of a task (human activity)

• Presentation of tasks to end users through a variety of mechanisms, including a worklist application (Oracle BPM Worklist)

• Organization, filtering, prioritization, and other features required for end users to productively perform their tasks

• Reports, reassignments, load balancing, and other features required by supervisors and business owners to manage the performance of tasks

These descriptions are at 1000 foot level. The real question is what’s behind the curtain that’s providing these capabilities? Let’s dive into the human workflow architecture to understand the inner workings.

Architecture

At the core, the human workflow is made up of several workflow services that are orchestrated to provide the different capabilities. 

Service Name	Description
Task Service	Primary service that manages the lifecycle of a Task. This service is invoked by the BPEL to initiate a Task.
Task Routing Service	Task Routing, Assigning and escalations are taken care by this service
Task Query Service	Queries tasks based on several criteria. (Used by client apps)
Task Metadata Service	Provides metadata of the task
Identity Service	This service is part of security infrastructure of the weblogic server.
Notification Service	Sends notifications through User Messaging services
User Metadata Service	Maintains metadata about workflow users. (Vacations, preferences, delegation rules…)
Runtime Config Service	Manages metadata used by task service
Evidence service	Provides storage services for audit trail. Supports digital signatures.

  

The following figure shows how the different components of human workflow are tied together with SOA 11g infrastructure components.: