Index

A

ACID requirements, 45-46, 115

implementing, with DTC, 77

long-running transactions and, 49

satisfying, when coordinating different data states/ messaging systems, 47

satisfying, when transaction is widely dispersed, 47

software designed for, 46

transaction compensation and, 48

Transactional Delivery capability and, 115

Active Directory Service Interfaces (ADSI), 72

Active Directory, 72, 94

active event handling, 122

addressing, 111

aggregation, 108, 40

complexity of, 40

processing requirements for, 40

system monitoring and, 63

Analysis Services, 71-72, 93

APIs, vs. direct data access, 13

application configuration, 126-127

application integration

architectural issues, 14

automated. See automated application integration

benefits of, 3

business process-level. See business process integration

choosing appropriate type of, 5

communications-level. See communications integration

data-level. See data integration

defined, 3

efficiency of, 5

environments. See environments

fully automated, 5-6

governance processes, establishing, 15

implementing. See implementing application integration

integration hub environment, 8-9

manual, 4-5

mapping business process requirements to, 23

Microsoft technologies for. See Microsoft technologies

open standards, basing on, 11. See also Web services

organizing, 14

people and, 5-6

point-to-point environment, 7-8

requirements for, 10

scalability of. See scalability

semi-automated. See semi-automated application integration

structuring, 7-10

technical issues, 14

application programming interfaces (APIs), vs. direct data access, 13

applications

ACID requirements. See ACID requirements

communication, 26-28

composed. See composed applications

directory-enabled, creating, 72

enabling communication between, by rewriting with APIs vs. creating communications adaptors, 27

enabling to convert incoming/ outgoing data into intermediary format, 25

enabling to understand data from other applications, lack of scalability of, 25

failures, detecting, 65

functionality for receiving and interpreting messages. See composed applications

functionality, combining, 40

internal resources, accessing with program calls, 12

Microsoft. See Microsoft technologies

reusing parts of, 40

architectural issues, 14

ASP.NET state management, 78

asynchronous communication

benefits of, 29

capabilities required for, 29

vs. synchronous communication, 28

atomic transactions. See ACID requirements

Atomicity, Consistency, Isolation, and Durability requirements. See ACID requirements

authentication, 56-57, 117

in BizTalk Server, 91

choosing appropriate type of, 56

HTTP Basic, 56

Kerberos, 56

Microsoft technologies and, 91

multifactorial, 56-57

not integrated with operating system, 57

password management, 57

requiring multiple factors for, 56-57

security of, increasing, 56

token-based security and, 58

authorization, 57-58, 117

data-level, 58

functional-level, 58

implementation of, 58

levels of, 57-58

Microsoft technologies and, 90-91

role-based, 57

system-level, 57

automated application integration, 5-6

choosing appropriate level of, 5

integration hub environment, 8-9

point-to-point environment, 7-8

scalability and, 6

situations where inappropriate, 5-6

structuring, 7-10

automated provisioning, 124

automating data transformation, 71

automation, 5-6

increasing, 29-30