Index_B


B

backward compatibility, 126

baselining, 121-122

Batching/Unbatching capability, 115

batching/unbatching documents, 89, 115

BizTalk Server 2004, 70

adapters, 88

Analysis Services, 71-72

authentication, 91

batching/unbatching documents, 89

BizTalk Explorer, 92

BPEL4WS support, 80

Business Activity Management, 66-67, 93, 122

business rules, implementing with, 77

connection management, 89-90

contract management, 80

dehydration/rehydration, 79

encoding/decoding documents, 89

event processing, 79

file transfer, 88

functoids, 83

Health and Activity Tracker, 94

Mapper interface, 82

message delivery, 112

message forwarding, 84-112

message queuing, 46-47, 73, 113

message routing, 84, 110

MessageBox, 84

orchestration, 78

orchestration ports, 86

parsers provided by, 81

pipelines. See pipelines

receive ports vs. receive locations, 85

request/reply, 88-89

schema definition, 81

send ports, 86

serialization/deserialization, 88

SharePoint and, 75

SQL Server 2000 Analysis Services and, 93

SSO system, 91

system monitoring, 94

transaction compensation and, 77

transactional delivery, 88

transports, handled as adapters, 88

Visual Studio .NET and, 70

Web services support, 70, 74

XSLT and, 73

BPEL4WS support in BizTalk Server, 80

bridging protocols, 90

business actions and journals, 39

Business Activity Management, 66-67, 93, 122

business application event handling, 93

business process exception handling, 5

business process integration, 18-24. See also business processes

capabilities required for, 24

defining business processes. See defining business processes

Microsoft technologies capabilities for, 76

Business Process Modeling Notation (BPMN), 22

business processes

activities consisting of, 18

automating, 5-6

complex, example of, 21

complexity of, 19

coordinating activities of, 97

defining, 18-19, 22

determining whether state must be saved, 18

event handling, 67

integrating related applications in, 18

interacting directly with users, 101

languages commonly used for, 22

long-running. See long-running transactions

mapping to application integration requirements, 23

modeling, 19-22

naming conventions, 18

notation for, 22

requiring integration of multiple applications, example of, 23

standards for, 22

without human intervention. See straight-through processing (STP)

business processing capabilities, 97. See also specific capabilities

in composed applications, 41, 42

in data synchronization, 35, 36

rules definable in, 100

in straight-through processing (STP), 31

business rules, 100-101

implementing, 77

specifying without writing excessive code, 100




Microsoft Corporation - Guidelines for Application Integration
Microsoft Corporation - Guidelines for Application Integration
ISBN: N/A
EAN: N/A
Year: 2003
Pages: 50

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net