Preface |
Preface
|
Preface
|
Chapter 1 |
1
|
TP and ACMS Concepts
|
1.1
|
Transaction Processing Concepts
|
1.1.1
|
ACID Transactions
|
1.1.2
|
Logical View of a Transaction Processing System
|
1.1.3
|
Application Development Life Cycle
|
1.2
|
ACMS Application Development Concepts
|
1.2.1
|
Writing ACMS Definitions
|
1.2.2
|
Composition of ACMS Definitions
|
1.2.3
|
ACMS Workspaces
|
1.3
|
ACMS Integration with DECforms
|
1.3.1
|
DECforms Concepts
|
1.3.2
|
ACMS Interaction with DECforms
|
1.3.3
|
Distributed Forms Processing
|
1.4
|
ACMS Integration with Resource Managers
|
1.4.1
|
Rdb Database Management Concepts
|
1.4.2
|
ACMS Interaction with a Resource Manager
|
1.4.3
|
Distributed Resource Managers
|
1.5
|
ACMS Distributed Transactions
|
1.5.1
|
Coordination of Multiple Resource Managers
|
1.5.2
|
Coordination of ACMS Task Queues
|
1.6
|
Interactive Transaction Handling
|
1.7
|
Recovery
|
1.8
|
ACMS Run-Time System
|
1.8.1
|
Command Process (CP)
|
1.8.2
|
Application Execution Controller (EXC)
|
1.8.3
|
Procedure Server Process (SP)
|
Chapter 2 |
2
|
ACMS Application Design
|
2.1
|
Understanding the ACMS Application Development Cycle
|
2.2
|
Relating Application Design and Database Design
|
2.3
|
Using Software in the Design of ACMS Applications
|
2.4
|
Identifying the Steps in the ACMS Application Design Process
|
Chapter 3 |
3
|
Creating a Requirements Specification
|
3.1
|
Defining the Business Problem
|
3.2
|
Analyzing the Work Requirements
|
3.2.1
|
Business Areas
|
3.2.2
|
Business Functions
|
3.2.3
|
Analyzing Business Activities
|
3.3
|
Defining Additional Requirements for Business Functions
|
3.3.1
|
Defining Run-time Requirements
|
3.3.2
|
Defining Implementation Requirements
|
3.4
|
Analyzing Data Entities
|
3.5
|
Completing the Requirements Analysis
|
Chapter 4 |
4
|
Creating a Functional Specification
|
4.1
|
Identifying TP Functionality
|
4.2
|
Mapping Business Functions to Transactions
|
4.2.1
|
Determining the Need for Distributed or Nondistributed Transactions
|
4.2.2
|
Determining the Processing Immediacy for Each Business Function
|
4.2.3
|
Defining Transactions to Avoid Lock Contention
|
4.2.4
|
Identifying Transactions Within Each Business Function
|
4.2.5
|
Identifying Transactions in the AVERTZ Application
|
4.3
|
Using Distributed Forms Processing
|
Chapter 5 |
5
|
Mapping Business Functions and Transactions to ACMS Tasks
|
5.1
|
Deciding on the Relationship Between Business Functions and Tasks
|
5.2
|
Planning Tasks for an Application
|
5.2.1
|
Considering User-Supplied Information When Designing Tasks
|
5.2.2
|
Considering Transactions When Designing Tasks
|
5.2.3
|
Considering Flow Control When Designing Tasks
|
5.2.4
|
Considering Task-Level Work and Procedure-Level Work When Designing Tasks
|
5.3
|
ACMS Tasks for the AVERTZ Application
|
5.3.1
|
The Reservation Task
|
5.3.2
|
The Checkout Task
|
5.3.3
|
The Checkin Task
|
5.3.4
|
Get Reservation Task
|
5.3.5
|
The Complete Checkout Task
|
Chapter 6 |
6
|
Designing ACMS Tasks
|
6.1
|
Choosing Single-Step or Multiple-Step Tasks
|
6.2
|
Controlling Task Flow
|
6.2.1
|
Step Sequencing
|
6.2.2
|
Conditional Processing
|
6.2.3
|
Task-Call-Task Feature
|
6.2.3.1
|
Allowing the User to Call a Task
|
6.2.3.2
|
Customizing Menus
|
6.2.3.3
|
Enhancing Security Checking
|
6.2.3.4
|
Creating Common Library Tasks
|
6.3
|
Designing Procedure Servers for Step Procedures
|
6.3.1
|
Designing Procedure Servers
|
6.3.1.1
|
Designing Step Procedures
|
6.3.1.2
|
Grouping Step Procedures in a Procedure Server
|
6.3.1.3
|
Setting the Number of Server Processes for a Procedure Server
|
6.3.2
|
Retaining and Releasing Server Context
|
6.3.3
|
Working in a Task or a Step Procedure
|
6.4
|
Designing and Using Workspaces
|
6.4.1
|
Workspace Size
|
6.4.2
|
Workspace Structure
|
6.4.3
|
Using Task, Group, or User Workspaces
|
6.4.4
|
Declaring and Referring to Workspaces
|
6.4.5
|
Specifying Access for Workspaces
|
6.5
|
Using Task Queuing
|
6.6
|
Designing Distributed Transactions
|
6.6.1
|
Locating Transaction Control
|
6.6.2
|
Choosing an Access Method to Remote Data
|
6.6.3
|
Distributed Transactions in the AVERTZ Application
|
6.7
|
Handling Exceptions
|