Đang chuẩn bị liên kết để tải về tài liệu:
Core Banking with Microsoft Technology phần 4

Không đóng trình duyệt đến khi xuất hiện nút TẢI XUỐNG Tải xuống

và triển khai máy chủ quy mô. Trong một số trường hợp, khách hàng sẽ chọn để liên kết nhiều máy chủ với phân nhóm hoặc phần mềm mạng lưới để hỗ trợ một khối lượng công việc nhất định. Trong những người khác, sức mạnh xử lý của máy chủ lớn hơn, khả năng mở rộng sẽ là cần thiết để hỗ trợ hệ thống hình ảnh lớn duy nhất (SSI) cơ sở dữ liệu hoặc để bảo đảm mức độ cao nhất sẵn có . | Human workflow Windows SharePoint Services and Microsoft Office SharePoint Server. System workflow Microsoft BizTalk Server which provides integration services as well. It can also be used with Windows SharePoint Services and other products to create combined human and system workflows. Business rules engine The BizTalk Server BRE. Microsoft also provides a rules engine with Windows Workflow Foundation part of Microsoft .NET Framework 3.0. Business activity monitoring The BizTalk Server BAM together with technologies such as Microsoft Office Excel and Office PerformancePoint Server business intelligence software for displaying BAM information. Process description tools Microsoft Office Visio drawing and diagramming software. In other words Microsoft encompasses within BPM both human workflow and system workflow sometimes also referred to as process flow and has been implementing a strategy to unify both types of workflow into a single workflow engine the one which is now part of the .NET development environment. A good example of what this means can be seen for document-centric workflows which can be defined by end-users through a specialized user interface that is part of workflow development in Microsoft Office SharePoint Designer Figure 13 . Core Banking with Microsoft Technology 29 Figure 13. Workflow Designer user interface in Microsoft Office SharePoint Designer In order to apply these technologies in the context of migration to a next-generation core banking platform a number of prerequisites need to be addressed first. Often the first step consists of making legacy system transactions available as services by removing their user interface and making them accessible using a standard protocol. However the ultimate objective of an SOA-based approach is likely to go beyond this and start to introduce a number of reusable services that can be invoked without unwanted side-effects or unnecessary duplication. An example might be a typical branch banking .