Index

A B C D E F I M N O P R S T U V W

A

ABCS

application interfaces, 4.4.3

architecture, 4.2, 4.4

BPEL, 4.6.2

characteristics, 4.3

customizing processing, 4.7

definition

extending processing, 4.7

implementation, 4.5

implementation technologies, 4.6

internationalization, 4.4.8

localization, 4.4.8

message consolidation and decomposition, 4.4.9

Oracle Mediator, 4.6.1

participating application's service granularity, 4.4.1

participating applications invoking, 4.9

processing multiple instances, 4.8

provider, 4.1, 4.5.2

requester, 4.1, 4.5.1

responsibilities, 4.1

support for EBMs, 4.4.2

support for insulating the service provider, 4.4.5

support for logging and monitoring, 4.4.4

support for multiple application instances, 4.4.10

support for security, 4.4.6

transformations, 4.10

validations, 4.4.7

VETORO pattern, 4.2

ABCS implementation technologies

BPEL, 4.6.2

Oracle Mediator, 4.6.1

ABCS transformations, 4.10

dynamic data cross-referencing, 4.10.3

implementation approach, 4.10.1

static data cross-referencing, 4.10.2

structural transformation, 4.10.4

Activity Service, 1.7.2

implementing, 1.7.6

AIA

conceptual services, 1.6.2

deliverables, 1.2

features, 1.2

goals, 1.2

integration styles, 1.4

Reference Process Models, 1.5

service artifacts, 1.8

Shared Service Inventory, 1.7

Application Business Connector Service

See ABCS

asynchronous fire-and-forget patterns, 3.8.2

asynchronous operations, 5.1

asynchronous request-delayed response pattern, 5.6

asynchronous request-delayed response patterns, 3.8.3

B

backward compatibility, 7.1.1

batch processing, 8

bulk data integration, 1.4.5

bulk data replication, 1.3.3

bulk upload of recurring transactions, 1.3.3

business activity, 1.5.2

business component in EBO, 2.1.1

business process, 1.5.1

business task, 1.5.3

C

choosing an integration pattern, 1.3.8

common components

impact of customization, 2.1.2

common components in EBO, 2.1.2

composite business flow, 1.5.4

Composite Business Process, 1.8.1

conceptual services, 1.6.2

customer extensions, 6.2.1

customizing ABCS processing, 4.7

D

data aggregation, 5.5

data enrichment, 5.4

data model, 2.1

Data Service, 1.7.3

implementing, 1.7.7

data-centric integrations, 1.3.3

decision tree for integration patterns, 1.3.8

direct connectivity, 1.4.2

direct integration, 1.4.1, 1.4.3

dynamic data cross-referencing, 4.10.3

E

EBF

definition, 1.8.3

processes, 3.6

EBM

action, 2.2.1

architecture, 2.2.1

considerations, 2.2.1

data area element, 2.2.1

definition

header, 2.3

transport protocols, 2.2.1

EBM Header

functions, 2.3

EBO

business component, 2.1.1

characteristics, 2.1

common components, 2.1.2

definition

how they work, 2.1

reference components, 2.1.3

XML schema file format, 2.1

EBS

architecture, 3.5

asynchronous fire-and-forget patterns, 3.8.2

asynchronous request-delayed response patterns, 3.8.3

content-based selection of the service provider, 3.5.3

definition, 1.8.2

implementation, 3.7

message exchange patterns, 3.8

operations, 3.2

overview

purpose, 3.5.4

responsibilities, 3.7.1

substituting one service provider with another, 3.5.2

synchronous request response patterns, 3.8.1

types, 3.4

verbs, 3.3

Enterprise Business Flow

See EBF

Enterprise Business Message

See EBM

Enterprise Business Object

See EBO

Enterprise Business Service

See EBS

entity services, 3.4.1

characteristics, 3.4.1

standard activities, 3.4.1

extending ABCS processing, 4.7

extensibility, 6.1

extensions

customer, 6.2.1

industry-specific, 6.2.2

process, 6.5

routing, 6.6

schema, 6.2

transformation, 6.3

transport/flow, 6.4

extensions in the use case, 6.3.1

F

fire-and-forget, 5.3

message routing, 5.3.1

message splitting and routing, 5.3.2

forward compatibility, 7.1.1

I

implementing extensions

customer-specific, 6.2.1

industry-specific, 6.2.2

industry-specific extensions, 6.2.2

initial data synchronization, 1.3.3

integration

bulk data, 1.4.5

high-volume without Xref table, 1.4.5.1

point-to-point, 1.4.5.1

using Foundation Pack, 1.4.4

with no middleware, 1.4.2

Integration Accelerators, 1.4.1

direct integrations, 1.4.1

Partial Process Integration Pack, 1.4.1

Process Integration Pack, 1.4.1

integration flow concept, 1.3.1

integration styles, 1.3.2

data-centric integrations, 1.3.3

integration through native interfaces, 1.3.4

process-centric integration, 1.3.7

reference data query, 1.3.6

through Web Services, 1.3.5

interaction patterns

asynchronous request - delayed response pattern, 5.6

data aggregation, 5.5

data enrichment, 5.4

fire-and-forget, 5.3

message exchange patterns, 5.1

message routing, 5.3.1

message splitting and routing, 5.3.2

publish and subscribe, 5.6

request/response, 5.2

synchronous response, 5.2.1

M

major versions, 7.1.1

mediator service, 1.4.4

message exchange patterns, 3.8, 5.1

asynchronous fire-and-forget pattern, 3.8.2

asynchronous operations, 5.1

asynchronous request-delayed response pattern, 3.8.3

synchronous operations, 5.1

synchronous request response pattern, 3.8.1

message routing, 5.3.1

message splitting and routing, 5.3.2

message-level security, 9.1.3

minor versions, 7.1.1

N

namespaces, 7.1.2

naming conventions for service versioning, 7.2.1

native application interfaces, 1.4.2

native interfaces, 1.3.4

O

operations, 3.2

Oracle Application Integration Architecture

See AIA, 1.1

Oracle Data Integrator, 1.3.3.1

Oracle Golden Gate, 1.3.3.1

Oracle Mediator, 4.6.1

P

Partial Process Integration Pack, 1.4.1

participating applications invoking ABCS, 4.9

participating applications versioning, 7.3

point-to-point integration, 1.4.5.1

pre-built data-centric integrations, 1.3.3.1

pre-built Integration Accelerators, 1.4.1

process extensions, 6.5

Process Integration Pack, 1.4.1

process services, 1.7.1, 3.4.2

characteristics, 3.4.2

implementing, 1.7.5

process-centric integration, 1.3.7

processing multiple instances, 4.8

provider ABCS, 4.1, 4.5.2

publish and subscribe, 5.6

R

reference components

attributes, 2.1.3

reference components in EBO, 2.1.3

reference data query, 1.3.6

Reference Process Models, 1.5

requester ABCS, 4.1, 4.5.1

request/response, 5.2

synchronous response, 5.2.1

routing extensions, 6.6

S

schema extensions, 6.2

schema in the use case, 6.2.3

schema versioning, 7.1

major, 7.1.1

minor, 7.1.1

namespaces, 7.1.2

version number, 7.1.1

security, 9

end-to-end, 9.1.1

message-level, 9.1.3

point-to-point, 9.1.1

transport-level, 9.1.2

service consumer, 1.6.1

service portfolio, 1.6.2

service versioning, 7.2

naming conventions, 7.2.1

Shared Service Inventory, 1.7

static data cross-referencing, 4.10.2

structural transformation, 4.10.4

synchronous operations, 5.1

synchronous request response patterns, 3.8.1

synchronous response, 5.2.1

T

transformation extensions, 6.3

transformations

ABCS, 4.10

dynamic data cross-referencing, 4.10.3

implementation approach, 4.10.1

static data cross-referencing, 4.10.2

structural transformation, 4.10.4

transport/flow extensions, 6.4

transport-level security, 9.1.2

U

use case

extensions, 6.3.1

schema, 6.2.3

Utility Service, 1.7.4

V

verbs, 3.3

versioning

backward compatibility, 7.1.1

forward compatibility, 7.1.1

major, 7.1.1

minor, 7.1.1

namespaces, 7.1.2

participating applications, 7.3

schema, 7.1

service versioning, 7.2

version number, 7.1.1

VETORO pattern, 4.2

W

Web Services, 1.3.5