Preface. + Purpose of this Document. + Who Should Read this Document? + Organization of this Document. + Position of this Document.

Transcription

1

2 Preface + Purpose of this Document This document has been prepared for Interstage CollaborationRing Process Manager (hereafter, referred to as CollaborationRing PM). This product is designed to achieve Enterprise Application Integration (EAI), Business to Business (B2B - an XML-based system for trade between companies) integration, and Business Process Management (BPM) integration. It is one of the component parts of the Integration Layer, part of the Interstage Software Platform suite of products. This document describes the basic information required to design and construct an integrated system by installing CollaborationRing PM. + Who Should Read this Document? This document is intended for users who are planning to install CollaborationRing PM, as well as those who are planning to use it to design a variety of integrated systems. It is assumed that readers of this document have a basic knowledge of the following. Windows(R) UNIX + Organization of this Document This document is organized as follows: Chapter 1: Process Integration and Interstage CollaborationRing Gives an overview of process integration and the Interstage CollaborationRing product structure. Also describes the types of integrated systems that can be achieved using Interstage CollaborationRing. Chapter 2: Overview of CollaborationRing PM In order to provide a basic understanding of CollaborationRing PM, describes CollaborationRing PM architecture and function composition as well as the skills required to use CollaborationRing PM. Chapter 3: CollaborationRing PM Functions Describes CollaborationRing PM component functions. Chapter 4: System Construction by CollaborationRing PM Describes the basic construction of systems using CollaborationRing PM. Chapter 5: CollaborationRing PM Operations Gives an overview of how to run and maintain CollaborationRing PM. + Position of this Document This document is only one component of the information set provided for Interstage CollaborationRing PM. The full information set consists of the following documents: Interstage CollaborationRing Process Manager Guide (this document) (hereafter, referred to as Interstage CollaborationRing PM Guide) Interstage CollaborationRing Process Manager Design Guide (hereafter, referred to as Interstage CollaborationRing PM Design Guide) Interstage CollaborationRing Process Manager Operation Guide (hereafter, referred to as Interstage CollaborationRing PM Operation Guide) Interstage CollaborationRing Process Manager Reference Manual (Process Flow Manager Edition) (hereafter, referred to as Interstage CollaborationRing PM Reference Manual (Process Flow Manager Edition)) Interstage CollaborationRing Process Manager Reference Manual (Enterprise Application Pipeline Edition) (hereafter, referred to as Interstage CollaborationRing PM Reference Manual (Enterprise Application Pipeline Edition)) Interstage CollaborationRing Process Manager Web Services Aggregator Guide (hereafter, referred to as Interstage CollaborationRing PM Web Services Aggregator Guide) TPM Guide + Product Names Actual names of the products and the naming conventions used in this document are as follows: Microsoft(R) Windows(R) Millennium Edition, Microsoft(R) Windows(R) XP Professional, Microsoft(R) Windows(R) XP Home Edition, Microsoft(R) Windows(R) 2000 Server, Microsoft(R) Windows(R) 2000 Advanced Server, Microsoft(R) Windows(R) 2000 Professional, Microsoft(R) Windows Server (TM) 2003, Standard Edition and Microsoft(R) Windows Server (TM) 2003, Enterprise Edition are referred to as Windows(R). i

3 Interstage CollaborationRing Process Manager is referred to as CollaborationRing PM. + Notations Used in this Document In this document, the following expressions are used: Points to note Things that require your attention are expressed in the following format: Things that require your attention are described. Make sure to read this. Reference information Reference information is expressed in the following format: Hints and tips are described. The table below explains symbols commonly used in this document. Symbol Purpose [ ] (square brackets) Encloses an option that can be omitted. -> (arrow) Indicates the result of an operation. { } (vertical bar and curly brackets) + Trademarks Trademarks of other companies: Product Microsoft, Windows, and Windows Server CORBA, Object Management Group, IIOP, and Object Request Broker SAP and R/3 ORACLE UNIX Java, other trademarks containing Java Rational and Rational Rose EBF workflow linkage IWF process history storage The brackets enclose a choice of options; the options are separated by vertical bars. Trademark/Registered Trademark Trademarks or registered trademarks of Microsoft Corporation in the U.S.A. and other countries. Trademarks or registered trademarks of the Object Management Group in the U.S.A and other countries. Trademarks or registered trademarks of SAP AG in Germany and other countries. Registered trademark of Oracle Corporation, USA. UNIX is a registered trademark in the U.S.A and other countries, licensed exclusively through X/Open Company Limited. Java and other trademarks containing Java are trademarks of Sun Microsystems, Inc. in the U.S. or other countries. Registered Trademarks of Rational Software Corporation. Copyright(C) 1999 Information-technology Promotion Agency, Japan Copyright(C) 2000 Information-technology Promotion Agency, Japan These products are merchandised from the results of work by Information-technology Promotion Agency, Japan (IPA). Fujitsu and IPA share the copyright of these products. All other trademarks or registered trademarks used in this document are trademarks or registered trademarks of the respective owner. + Comment of this Document In this document, Enterprise Application Pipeline is referred to as EAP and Process Flow Manager is referred to as CRF. ii

4 + Export Control This document contains technology relating to strategic products controlled by export control laws of the producing and/or exporting countries. This document or a portion thereof should not be exported (or re-exported) without authorization from the appropriate government authorities in accordance with such laws. + High Risk Activity The Customer acknowledges and agrees that the Product is designed, developed and manufactured as contemplated for general use, including without limitation, general office use, personal use, household use, and ordinary industrial use, but is not designed, developed and manufactured as contemplated for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death, personal injury, severe physical damage or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system. The Customer, shall not use the Product without securing the sufficient safety required for the High Safety Required Use. In addition, Fujitsu (or other affiliate's name) shall not be liable against the Customer and/or any third party for any claims or damages arising in connection with the High Safety Required Use of the Product. + Copyright Copyright (C) Fujitsu LIMITED First Edition, October Important Notice Do not copy this document without permission. This document may be changed without notice. iii

5 Chapter 1 Process Integration and Interstage CollaborationRing Against the background of the need to adapt to changing business environments and increased co-operation between businesses, the importance of integrating business applications and systems is ever more pressing. Measures to integrate business applications and data in a single operation started with EAI (Enterprise Application Integration) and have diversified to include XML-based realtime business transactions on the Internet known as BtoB (Business to Business), Web services, and BPM (Business Process Management) among others. The methods and techniques for achieving this kind of integration are referred to as process integration, and Interstage CollaborationRing is a product for achieving this process integration. This chapter describes the concept of process integration, the product structure of Interstage CollaborationRing, as well as what kinds of integrated system can be achieved with Interstage CollaborationRing. 1.1 Overview of Process Integration One of the most pressing administrative issues facing businesses is the linkage and integration of different business systems within an enterprise and between systems in different enterprises. Speed and flexibility are the main requirements in rebuilding systems in an integrated way. Business systems that can respond flexibly and quickly to changes in business structures can make prompt administrative decisions and give an enterprise a harder competitive edge, and it is through process integration that such systems can be constructed Background and Goals Independent business systems developed from multiple applications are run within an enterprise and in related enterprises. For example, call center systems, accounting systems, and sales management systems are in use. Linkage and integration of these various business systems is currently the most pressing issue facing enterprises. Various elements contribute to this issue, and the main elements are shown in the following diagram: [Linkage and Integration of Business Systems] As business environments develop in diverse ways, superior customer service, and the provision of systems that support such service, are required in order to maintain existing customers and attract new customers. This has become a major factor in the survival of an enterprise. The system flow must be structured to suit the flow of business in order to increase business efficiency and speed. All business processes, from the reception of orders to dispatch, billing, DM issue, and so on, must be automated. In order to take maximum advantage of the integrated business environment potential offered by e-business, conventional systems must be further fused with Web- and Internet-based systems. There is a greater need for linkage between business systems both within and outside an enterprise and for collaboration between suppiers and customers. Process integration is an effective means of achieving these business requirements. 1

6 1.1.2 Basic Concept of Process Integration Process integration performs the role of a hub or bus in a business system, acting as a method of linking different in-house business systems as well as trading systems with business partners. This basic method of system integration using a hub or bus is known as EAI. Using this kind of linkage method, the workload involved in linking systems is reduced compared with the work required to develop and maintain linkage programs for each of the various systems. This method can also cope easily with increases in the numbers of business systems to be linked, without any detrimental effects to the system as a whole. Process integration is a method of EAI-based integration that envisages optimized business performance and flexibility in the face of environment changes, as well as other business-friendly features. Implementing process integration to integrate business systems gives rise to further benefits, as described below. +++ Automation of business processes It is possible to automate all business tasks, from receipt of orders, through dispatch, billing, DM issue, and so on. Automation increases the efficiency and speed of business tasks. [Automation of Business Tasks] +++ Support for more aggressive operations through flexible implementation of e-business Speed and flexibility are the prime aims of EAI. When EAI is used, the Internet can of course be used for prompt reception and issue of orders. Also, EAI exhibits considerable power as a means of building a highly competitive supply chain that can respond to changes taking place between trading partners. 2

7 +++ Effective use of existing system resources EAI does not build integrated systems from scratch. EAI effectively makes use of existing system resources and integrates systems. Additionally, when a new system is installed, EAI can quickly reintegrate the systems Components of Process Integration Process integration comprises the components described below. +++ Adapter Provides interfaces for connecting the business applications, packages, databases, systems and so on that exist in an enterprise. As the name implies, it is possible to incorporate different adapters to enable different kinds of connection (for example, for HTTP or FTP). +++ Format Conversion The format (column layout, attributes and length, for example) of handled data differs depending on the business applications and packages. Using format conversion when sending and receiving data however, the data format of sent data can be converted to that of the system of the business partner. By combining format conversions and adapters, it is possible to link fundamentally different business systems constructed separately without the need for substantial change on either side. +++ Sorting (Routing) This is a function for sorting transmitted data that are sent to trading partner systems. It can change the recipient of transmitted data depending on conditions such as the values included in the data and sort data for multiple systems. +++ Process Flow Control This is a function for linking business systems according to the defined process flow. Whereas previously it might only require manual input to integrate multiple business applications, such effort is now also required to integrate not only business applications but also processes such as the confirmation and approval of transactions. When such actions are defined as part of a process flow, process flow control can be used to automate their execution without the need for human intervention, smooothing and simplifying the process of integration. In addition, process flow control visualizes business processes, and this helps in the identification and solving of problems in ongoing processes. This also links up with business process management (BPM) measures, which in turn supports the reform of business activities by realizing the cycle of planning, performance monitoring, evaluation, and result feedback. 1.2 What is Interstage CollaborationRing? Interstage CollaborationRing is a product that implements process integration. It links and integrates business applications and systems either within a business or between related businesses according to a business process model CollaborationRing as Part of Interstage The Interstage software platform consists of three layers: Foundation, Integration, and Development Suite. Interstage CollaborationRing is located in the Integration layer. Interstage CollaborationRing runs on Interstage Application Server Interstage CollaborationRing Product Structure Interstage CollaborationRing consists of the following product groups: Interstage CollaborationRing Process Manager Interstage CollaborationRing Process Manager is the crucial component in Interstage CollaborationRing, implementing, among others: - In-house application integration - XML-based BtoB transactions using the Internet - Task automation through the process flow system, including human workflow. Interstage CollaborationRing Business Connector Interstage CollaborationRing Business Connector is a specialized product for the construction of small- to medium-scale BtoB sites (for example, supplier sites), created by extracting functions relevant to BtoB trading from Interstage CollaborationRing Process Manager. 3

8 1.3 Systems that can be Created Using CollaborationRing PM Using CollaborationRing PM, it is possible to create the following kinds of system: In-house application integration system Business data integration system BtoB trading system Process flow system including human workflow Current EDI Trading System These systems are to be regarded as basic models of integrated systems. The main features of the types of system listed above are explained below In-house Application Integration System An in-house application integration system is a system that uses CollaborationRing PM to link in-house business applications and packages, as well as a variety of other unspecified systems. A typical example of such a system would be integrating ERP packages with existing business applications. If, for example, replacing with an ERP package part of the business applications running on an existing system such as a mainframe, by using the ERP package adapter and sorting functions provided with CollaborationRing PM, you can easily link the ERP package and the business systems remaining in the existing system. In addition, by linking with CollaborationRing PM, it is easy to make a staged transition from existing business applications to the ERP package. [In-house Application Integration System] Business Data Integration System This is a system that uses CollaborationRing PM to gather scattered business data. For example, if you construct a data warehouse for the purpose of data analysis, by using CollaborationRing PM, you can implement efficient methods of data accumulation. CollaborationRing PM provides a wide variety of adapters (for example, for file transfer middleware and messaging middleware). Use of these adapters makes it very easy to connect to a wide variety of systems. In addition, the format conversion function can be used instead of an application when arranging data for registration in a data warehouse. 4

9 [Business Data Integration System] BtoB Trading System CollaborationRing PM supports XML-based trading standards for the Internet such as RosettaNet and ebxml. This makes it possible to quickly construct realtime BtoB trading systems conforming to these standards for use between customers and suppliers. [BtoB Trading System] Current EDI Trading System Trading systems currently in use often include traditional EDI systems. CollaborationRing PM supports the current EDI standards and can link to existing trading partner systems without having any effect on them. In addition, because CollaborationRing PM can conceal differences between linked systems (such as communications order and data format), it is possible to link to new trading partner systems without any ill effect on your own system. [Current EDI Trading System] Process Flow System Including Human Workflow CollaborationRing PM provides a process flow control function that can also be applied to human workflow. This makes it possible to integrate in-house business application processes and human intervention processes in a single business process. For example, by linking processes that require human intervention, such as inspection and approval, with update processes that are performed by business applications, then by setting the business applications to run automatically when an approval procedure is extended, the entire procedure is made more efficient because the potential for updates being missed is removed and it is possible to know the progress of all tasks. 5

10 [Process Flow System Including Human Workflow] 6

11 Chapter 2 Overview of CollaborationRing PM This chapter describes the architecture of CollaborationRing PM and gives an overview of its functions and the technologies it uses in order to provide users with the basic knowledge required to understand what CollaborationRing PM is and how to use it. These descriptions also introduce and explain terminology used in subsequent chapters. 2.1 Architecture The hub-based architecture of CollaborationRing PM is illustrated in the diagram below and its component elements are described thereafter. [Architecture of CollaborationRing PM] +++ Business process A business process is defined as a business system comprising one or more applications, for example an accounting system or a production management system. Each of these systems is considered as one business process. +++ Business document A business document is defined as the contents received and passed either within a business process or between business processes. It is in fact a group of structured data handled during the conduct of business. In an actual business system, order issue forms and inventory forms are examples of business documents. The person who initiates a form creates original data, to which a supervisor or application adds a variety information. This information as a whole is the business document. The following diagram illustrates the structure of a business document: [Business Document Structure] Data from business applications and systems are passed as business documents to CollaborationRing PM by means 7

12 of adapters. This means that it is up to the user who drafts the business document to apply the appropriate adapter. Business documents from CollaborationRing PM are passed to business applications and systems by adapters in a readable format. +++ Business document bus One of the component elements of a business process, the business document bus is defined as a virtual transfer route on which multiple business documents are circulated. Entering new business documents in the business document bus is referred to as "drafting". +++ Activity An activity is defined as a process performed on a business document.. The processing of a form by a business application, or an action such as approving a business document are examples of an activity. Each activity is an independent unit. Connection to the business document bus is made using the "plug and play" concept. Just as an extension board or peripheral device can be used by plugging it into a PC, the various activities can be used as soon as they are connected to the business document bus. [Activity] +++ Process rules Process rules are defined as the rules used to link multiple activities. The following are set in the process rules: Activity processing order and activity selection conditions Business document exchange format Business documents entered in the business documents bus are passed to the appropriate activity according to the process rules. This comprises a single business process Relationship between Components The illustration below shows a simple example of the relationship between business documents, activities, and process rules. The business document is an actual form expressed in XML. The activities include checking the content of the form, and confirming inventory quantities relevant to the form. The process rules determine the processing order of the activities. 8

13 [Relationship between Business Documents, Activities, and Process Rules] 2.2 Component Functions The main component functions of CollaborationRing PM are as follows: Function Overview Process flow manager Enterprise Application Pipeline (EAP) Format conversion function Adapters Trading Partner Manager (TPM) Web Services Aggregator Linkage function with BizTalk Server The key component of CollaborationRing PM. Implements the business document bus. Also provides functions for defining business processes for process integration, managing the execution of processes, and evaluating and analyzing execution results. Acts as a template for defining standardized process models for system linkage. Also provides functions for manipulating and sorting data. EAP acts as a medium for simplifying linkage between systems. Carries out format conversions and character code conversions for data transmitted between integrated systems. Provide interfaces for a variety of connections, such as to business applications, packages, and systems. Adapters are provided for all of the communications protocols and intermediary middleware products used in CollaborationRing PM. Implements business transactions (BtoB trading) using the XML-based BtoB trading standards, RosettaNet, ebxml, and CIDX. Simplifies the construction of work systems to link with Web services. Private UDDI is also supported. This function enables process linkage with BizTalk server. It runs on the computer in which BizTalk Server is installed. The relationship between these functions is shown in the illustration below. 9

14 [Relationship between Functions] Viewed from process flow manager, all other functions are regarded as activities and are connected to the business document bus as such. In addition, when integrating processes using CollaborationRing PM, process flow manager is always used, but whether or not the other functions are used depends on the requirements of the particular integration process. The way in which the functions are used depends in turn on the system being constructed. See sections for more details Functions Used in In-house Application Integration Systems When constructing an in-house application integration system, EAP, format conversion function, and the adapter functions are used in addition to process flow manager. Using the process model for linkage provided with EAP, it is possible to create a two-way link between business applications and ERP packages on the existing system using messaging middleware and file transfer middleware. By using EAP, you can greatly reduce the time required for construction. The format conversion function is used to convert the format and character code of data transmitted between business applications and ERP packages. Adapters are provided for all of the communications protocols and intermediary middleware products supported by the business systems and business applications, and the appropriate adapter is used as required Functions Used in Business Data Integration Systems When constructing a business data integration system, the functions used in addition to process flow manager are the same as in Functions Used in In-house Application Integration Systems above Functions Used in BtoB Trading Systems When constructing a BtoB trading system, TPM and the format conversion function are used in addition to process flow manager. TPM is used for exchanging data according to trading standards such as RosettaNet. The format conversion function is used to convert the format of standards in XML and in localized formats Functions Used in Current EDI Trading Systems When constructing a trading system using current EDI, EAP and the format conversion function are used in addition to process flow manager. EAP is used for controlling the exchange of transaction data files between in-house business systems and trading partner systems. The format conversion function is used to convert the format of data in EDI standards such as UN/EDIFACT and in localized formats. 10

15 2.2.5 Functions Used in Process Flow Systems When constructing a process flow system including human workflow, the format conversion function, EAP function and adapter functions are used in addition to process flow manager. The necessary business applications are developed, and then the developed applications are created as a series of process flow tasks using process flow manager. Apart from process flow manager, other functions are used to register the process results of flow tasks in master databases on associated systems Other Functions Web Services Aggregator and Linkage function with BizTalk Server may or may not be used, depending on the individual system requirements. 2.3 Main Technologies CollaborationRing PM is an open product using both international standards and industry standards. In addition to existing technologies, a variety of more recent technologies is also used. These recent technologies enhance the independence, extensibility, and connectability of applications and business processes. They also make it possible to add speedier and more flexible functions to the business systems that are created. This section gives an overview of these technologies Technology to Ensure Business Document Circulation A number of elements concerning business document circulation must be considered. Firstly, it must be possible to modify business documents in response to future global trends. It must also be possible to send business documents via Internet links between departments and enterprises. In addition, various information is added and updated to a business document complying with the execution of business processes. XML is currently the most suitable technology to meet these requirements with flexibility and is replacing HTML as the standard Internet coding language. With its focus on XML technologies, CollaborationRing PM uses domestic and international EDI standard technologies to guarantee circulation across a broad spectrum Technology for Monitoring and Controlling the Flow of Tasks By defining business processes, it is possible to monitor and control the execution of tasks. In the business process example shown in the diagram below, the business document circulates between users, other departments, and other enterprises. Management of the business process flow can be used to monitor how far (up to which process) the business document has progressed. CollaborationRing PM uses SWAP (Simple Workflow Access Protocol), the international standard for workflow technologies, for the distribution and management of business documents. 11

16 [Monitoring and Controlling the Flow of Tasks] Technologies for Linking with Other Systems Existing business systems use many applications and systems that make use of circulation components developed using Web technologies, Java, EJB (Enterprise Java Beans), or similar. CollaborationRing PM can use open technologies such as Web, Java/EJB, and CORBA (Common Object Request Broker Architecture) technologies to connect to these applications and systems. 12

17 Chapter 3 CollaborationRing PM Functions With CollaborationRing PM it is possible to construct a wide variety of systems, such as in-house application integration systems, business data integration systems, BtoB trading systems, current EDI trading systems, and process flow systems. This chapter describes in detail the functions used to construct systems. 3.1 Process Flow Manager Process flow manager is the core function of CollaborationRing PM. It provides the means for linking business applications and packages, trading partner systems, and so on in accordance with process rules, and for circulating business data as business documents. Additionally, process flow manager supports Web-based human workflow through Web applications developed with JSPs and servlets. This means that, by combining other CollaborationRing PM functions that operate through process flow manager, such as EAP and TPM, groups of in-house business processes and external trading processes, including tasks that require human intervention (such as approval and decision-making), can be integrated as a single business process Components of Process Flow Manager Broadly speaking, process flow manager controls business processes in a three-stage cycle: 1. Business process definition 2. Business process execution 3. Analysis of and feedback from execution results. Accordingly, process flow manager consists primarily of the following three components: Business process designer Business process designer is a function for defining business processes. It consists of process definition tools and add-ins. Business flow controller Business flow controller is a function for controlling the execution of business processes in accordance with a business process definition. Business process analyzer Business process analyzer is a function for analyzing the results of executed business processes. It consists of a variety of operating tools and analytical functions. Process flow manager is distributed to the following two servers: Control server The control server is the server in which the database for managing defined business process information and business documents is located. Each system usually contains one control server, but can contain more, depending on the system requirements. Functions such as EAP and the format conversion function run on the control server. Execution server The execution server is the server on which the business applications run. The execution server can be located on the same machine as the control server or, to reduce the workload in accordance with the demands of a particular business operation, can be spread across multiple independent machines Process Rule Variations A business process is group of individual but related and sequenced business activities (such as responding to estimates and ordering stock) defined by a set of process rules. Because of the many variable conditions that affect business, it is necessary for process rule settings to contain a variety of variations. These variations are provided in the form of the following functions for modifying process rules: UI activities Automatic execution activities Subprocess activities Conditional branching function Parallel execution and integration Timeout monitor Agent settings Recovery by drafter/recovery by approver Dynamic modification function for process rules using variables Dynamic modification function for process routes Mail notification on business document arrival or error detection 13

18 Conditional execution function Activity execution and work timer execution skip function Access control by role [Process Rule Variations] By using these functions, it is possible to create business process definitions that accord to the following business conditions: Business process automating a chain of application processes as a process flow or application flow Business process automating human workflow Business process combining process flow and human workflow Business process changing dynamically to suit business document content and conditions Types of Activity An activity is a unit of processing performed on a business document, and expresses one task in a workflow. Activities can be classified on the basis of how they operate into one of three categories: UI activities Automatic execution activities Subprocess activities [Types of Activity] By using these activities, it is possible to achieve a broad spectrum of process integration, including human workflow, rather than a simple concatenation of business applications. +++ UI activities UI activities bring more freedom to the performance of business document operations because they allow operations to be performed at any time that suits the business situation. When the business process control reaches these UI activities, the business documents accumulate as tasks awaiting operator action. The operator (which could also be an application program) uses the client-type API to process the business documents that have accumulated in the activity. The business documents do not proceed from the activity until the operator has processed them. 14

19 When control is passed to a UI activity, the UI activity can also send mail to all the operators for that activity to notify them that a task has been issued. This is known as the mail linkage function. [UI activities] +++ Automatic execution activities These are activities invoked automatically from process flow manager. Business applications invoked from an automatic execution activity are referred to as automatic execution applications. When business process control reaches an automatic execution activity, the automatic execution application specified in the automatic execution activity starts. The automatic execution activity extracts the required information from the business document, sends this to the automatic execution application in the form of input variables, and waits for the processing results from the automatic execution application. When the results are received, processing advances to the next activity. [Automatic Execution Activities] +++ Subprocess activities Independent business processes can be defined as subprocesses. When business process control reaches a subprocess activity, forms are drafted for the subprocess defined in the subprocess activity, and the subprocess is started. SWAP is used as the protocol to invoke the subprocess. There are two types of subprocess activity: synchronous or asynchronous. If the synchronous type is used, the activity waits for the processing results from the subprocess, and processing does not advance to the next activity until a response is returned from the subprocess. If the asynchronous type is used, processing proceeds immediately to the next activity without waiting for a response from the subprocess. 15

20 [Subprocess Activities] Displaying Business Process Status and Tracing Logs Process flow manager provides the functions below to inform users of business process status and to allow users to trace process history. Displaying business process status Searcing for activities Global history query and log search Trading analysis Each time an activity is called, the process flow manager accumulates that information in the database that manages status updates. By searching this database, it is possible to determine the current status of a business process. Users can specify search conditions to find activities and confirm business document content. For example, if an order request is issued to a trading partner, the analyzer can determine whether the business document is still at the reception point of the other enterprise, whether it is circulating through inventory management tasks, or whether processing has reached the dispatch department, and so on. Thus, users can quickly determine the status of the business document without needing to ask staff at the other company. In the same way, it is also possible to track the progress of a business document as it circulates through multiple systems. [Searching a Database to Determine the Status of a Business Document] In addition, trading analysis provides the statistical information related to workflow. For example, the progress status of processes in inter-company trade is recorded in a trading log, which stores statistical information for the processing time of each process. The results can be used to investigate bottleneck locations and causes of delays in a trading supply chain involving multiple enterprises, and thereby optimize the supply chain. 16

21 [Using Results to Optimize the Supply Chain] 3.2 Enterprise Application Pipeline (EAP) Tasks have a variety of formats and types. Order issue and reception processing between transaction partners, and in-house production management and inventory management are all examples of tasks, and data (business documents) are generated by these tasks. Usually, the processing of the generated data is shared between multiple tasks. If the format of data used for one task differs from the format of the previous task, the data format must be converted. Similarly, even if data is generated by the same task, data distribution processing is required if different contents are to be passed to different tasks (addresses). As the number of linked tasks increases, the processing of data becomes lengthier and more complicated. In addition, the data processing units and timing vary for different tasks. For some tasks, multiple units of data are stored and processed as a batch at a specified time. For other tasks, each data unit is processed immediately (real-time type tasks). EAP provides a process model for standard system linkage, thus reducing the amount of time and effort required to create a link between systems. For example, if you use EAP, there is no need to create the process definition required for system linkage yourself. Note that it is also possible to make additions and modifications to linked tasks without affecting other tasks. 17

22 [EAP Definition] Tasks that can be Linked The tasks that begin and end the EAP function are referred to as leading task and following tasks. A leading task is a task that generates the data that are input into EAP. A following task is the output destination for data processed by EAP. [Tasks that can be linked] Two types of task link to EAP as leading and following tasks: tasks defined as business processes (such as a purchasing workflow) and data transfer tasks. 18

23 +++ Business defined as a business process Business processes can be linked to as leading tasks or following tasks. Two methods are available for linking the main process to EAP as a leading task: Linking through UI activity EAP fetches data from the process waiting for manager processing in the UI activity. Linking by the automatic execution application for real-time linkage provided by EAP The automatic execution application provided by EAP for real-time linkage is incorporated at the end of the business process so that this application automatically links to EAP. This means that there is no need to develop new applications for linkage. To link to a business process as a following task, EAP issues a form for the process. +++ Data transfer tasks It is possible to link to the linkage products and protocols below as leading tasks or following tasks. MessageQueueDirector FTP HTTP, HTTP/S Note that EAP includes FTP Main Functions of EAP EAP includes the following functions to enable flexible linkage of operations and to allow the operating status and environment definitions to be verified with ease. Standard process models for linkage Users can create an environment for linkage by selecting the optimum process model from the GUI. Data processing Performs tasks such as data translation (i.e., format conversion) for data encountered in following tasks, as well as data merging and splitting. Data sorting Performs static sorting for defined recipients and dynamic sorting according to data values. Broadcast sorting (the routing of the same data to multiple recipients) is also possible. User exits Includes user applications before and after data processing. This makes tasks such as conversion data to user-specific format, data backup, and deleting unnecessary data possible for data received by following tasks. Process start timing according to application The time when data processing starts can be selected according to how the data are used. The API or commands can be used to select processing start times to suit either batched tasks, in which data are processed in batches, or real-time tasks that are processed immediately as data are generated. Tracking of processed data The global history query function of process flow manager can be used to track data processed by EAP. High-reliability systems Various types of cluster system can be linked to build highly scalable systems with non-stop operation Business Usage Examples This section describes examples of applying the EAP function to business. +++ Usage in an EDI Server In this example, order reception and issue business documents generated in-house are sent to a trading partner at a time when data transfer is convenient for the trading partner. EAP sends only the business documents addressed to Company A by a batch process at 15:00 hours, as instructed by the linkage instructions from the application. 19

24 +++ Usage in an In-house Server In this example, the sales forms for each product sent from each branch initiate the process on the server that processes the forms. [Using EAP in an In-house Server] 3.3 Format Conversion Function The format conversion function is used to convert the format of business documents exchanged by linked business applications, ERP packages, external systems, and so on. 20

25 [Format Conversion Function] The main features of the format conversion function are as follows: Functions for converting data to and from a variety of formats, such as XML and CSV Data column conversion functions, such as for manipulating data columns and values Character code conversion Support functions for creating format conversion definitions Data Format Conversion The CollaborationRing PM format conversion function provides functions for converting data to and from the following formats: General data (such as fixed length data and headed data) Current EDI trading data (UN/EDIFACT, ANSI X.12) XML data CSV data Data defined by ERP package (R/3 data format) Data Column Conversion The data column conversion function can be used to change the order of data columns, merge multiple data columns into a single column, and convert data column values. Data columns are converted by mapping input data columns and output data columns and by setting conversion rules for each data column. The conversion rules are as follows: Optimize posting This rule converts by setting values to match data column attributes in the output destination record without the need to know attributes or number of digits. Even if the number of digits does not match, data columns are justified to left or right as appropriate to suit data column attributes in the output destination record. Column settings This rule cuts and converts all or part of the input source data column values to the output destination data column. It is possible to set fixed values such as serial numbers, dates, and numerical values as well as data column values. Condition settings This rule is used in combination with other conversion rules to set extra conditions according to data column values of the input source record. Target data are data column values of the input source record, data column values of the output destination record (in which case the values must be set in the preceding conversion process), and fixed values. For example, if there are three or more types of condition expression, set the interim condition results to be output to a temporary destination data column, and use those interim results to specify the subsequent condition expression. The condition expressions are as follows: - Equal to - Equal to or greater than - Equal to or less than - Not equal to - Greater than - Less than Calculation settings This rule performs mathematical operations on data column values of the input source record, data column values of the output destination record (if set), and fixed values, and sets the result of those operations as the data column value of the output destination record. By repeating calculation settings, it is possible to implement more complex formulae. Calculation results that fall within the following range are guaranteed: -2,147,483,648 ~ 2,147,483,647 Column code conversion settings This rule is used when the data column value of the input source record and data column value of the output destination record do not match. For example, if the data column value of the input source record expresses gender in the form Male=1, Female=2, but the data column value of the output destination record expresses gender in the form Male=M, Female=F, this rule converts the value 1 to M, and the value 2 to F. The dictionary for converting column values is a CSV file. Corresponding input source values and output destination values are associated in this file. Note that a function for creating CSV files is provided with the definition tool for creating format conversion definitions. 21

26 User program invocation For user tasks requesting special data column conversions, user programs can be included. You can prepare a user program for each data column of the output destination record. When a user program is invoked, information such as the data columns of the input source record and output destination record are passed as parameters. These parameters are evaluated by the user program to determine output column values Support Functions for Creating Format Conversion Definitions In order to convert format, use the GUI provided for creating definitions to define the input and output data format and to define the conversion rules that for example map the input and output data columns. CollaborationRing PM provides support functions to increase the efficiency of the process of creating definitions, as described below. +++ Using existing data format definition information By importing existing format definition information such as that listed below into the definition tool, it is possible to reduce the workload involved in creating definitions. DTD used as XML schema in BtoB trading standard CSV Data format provided with packaged products +++ Recycling definition information by part If you define a data record as a group of parts (such as header, footer, and so on), you can split the definition into its consituent parts for re-use. This also has the benefit of avoiding duplicate or non-matching definitions and reducing the number of definitions. +++ Multi-stage conversion Multi-stage conversion combines a series of conversion stages (first, data are converted from XML format to general format; next, data columns are converted) as a single conversion process. The multi-stage conversion function allows you to convert data in complex formats without having to prepare special conversion applications. +++ Simultaneous creation of definitions This function allows multiple developers to create definitions simultaneously, which is useful when many data that require definitions and data from a variety of tasks exist. +++ Definition integrity test With this function, you can confirm the integrity of defined information on the computer running the GUI software, rather than having to test on the system in which CollaborationRing PM is installed. 3.4 Adapter Function CollaborationRing PM provides the following adapters: Standard adapters Adapter kit (for general applications) Adapter kit (for component objects) The standard adapters are provided by default with CollaborationRing PM and include adapters for communications protocols such as FTP and CORBA, and for file transfer middleware. These adapters can be used by creating basic definitions. Adapter Kit is a kit for developing adapters, which would be used, for example, to create an adapter to link a business application using an original linkage interface to CollaborationRing PM Standard Adapters The standard adapters provided by CollaborationRing PM support the linkage interfaces listed below. Adapter for: Communications protocols Messaging middleware HTTP, HTTP/S, FTP CORBA, Java/EJB, SOAP SMTP MessageQueueDirector Supports: 22

27 Adapter for: ERP packages R/3 Oracle E-Business Suite Adapter Kit (for General Applications) Supports: Adapter Kit (for general applications) is a kit for developing adapters for existing business applications and packages. Adapter developers are able to concentrate on programming without being required to possess knowledge of Interstage Application Server or the APIs provided with process flow manager. [Adapter Kit (for General Applications)] +++ Adapter Kit (for general applications) components Adapter Kit (for general application) provides the following services: Wizards Skeletons suitable for the various types of program are output if you enter information following the Wizards. As functions of CollaborationRing PM are already described within the skeletons, adapter developers are able to concentrate on programming. In addition, linkage with the process definition can decrease input and output coding processes as the input and output variable name that was input from the process definition tool can be output. [Adapter Kit Wizards] Sample programs Sample coded programs created on the basis of a skeleton are provided. Developers can code by referring to them. 23

28 By referring to a sample, you can easily carry out the following procedures: 1. Use of process definition tool 2. Use of Wizards 3. Coding and compilation 4. Distribution of resources to server 5. Startup of distributed resources 6. Testing +++ Support for creating adapters to link with EAP Using Adapter Kit (for general applications), users can create adapters for systems that link with EAP. [Creating Adapters to Link with EAP] Skeletons suitable for the various types of source program are output if users enter information following the Wizards. Once the user has entered in the skeleton the logic of the system to link to and data to transmit, the adapter is complete. Knowledge of CORBA programming is not required. Users can create three types of adapter: Message collection monitoring adapter For collecting messages after notification is received of the arrival of data from another system. Message collection adapter For collecting data from another system. Message distribution adapter For distributing data to another system Adapter Kit (for Component Objects) Adapter Kit (for component objects) is a kit for developing adapters for a range of applications dealing in services such as EJB and SOAP. This Kit provides a framework that makes it easier to: Create and deploy code that interfaces with a range of application environments, including SOAP, EJB packages, and custom-built applications Refer to and convert the format of business document content. 24

29 [Adapter Kit (for Component Objects)] +++ Adapter Kit (for component objects) components The CollaborationRing PM Adapter Kit (for component objects) consists of the following components: [Adapter Kit (for Component Objects) Components] Executable modules (runtime adapters) The CR adapter executable provides a runtime environment that executes custom-built modules (called pluggables), and performs conversions according to XSLT stylesheets. The pluggables inclusde SOAP service and EJB Session Bean pluggables, as well as custom-built pluggables. By preparing XSLT stylesheets, you can convert XML documents in the executable. The executable is a CORBA server application on the (Java-based) Interstage Application Server. SOAP and EJB pluggables The SOAP and EJB pluggables are means of linking to the SOAP and EJB execution environments. Wizards The Wizards are used to create parameter sets that control the behavior of the CR Adapter executable. The parameters include such information as the name of the activity that invoked the executable and the stylesheet name. Adapter Kit repository The Adapter Kit repository manages the parameter sets created with the Wizard and it provides the amount of repository necessary for each parameter set. SOAP-CR Adapter SOAP-CR Adapter is an adapter that enables a SOAP client program to start a CollaborationRing PM process by a single SOAP invocation. 25

30 3.5 Trading Partner Manager (TPM) TPM provides the foundations for BtoB trading using the XML-based trading standards RosettaNet, ebxml, and CIDX. [Trading Partner Manager] By combining TPM with other functions provided by CollaborationRing PM, you can increase your trading contacts over the Internet whilst still employing your existing business systems. The main functions provided by TPM are: Conforming to BtoB trading standards Trading scenario definitions Working with in-house business processes Trading analysis logs Using these functions, you can create an open and extensible trading environment Conforming to BtoB Trading Standards TPM supports the BtoB trading standards listed below. RosettaNet A trading standard recommended by an international consortium targeting substantial increases in efficiency in the the supply chain of the computer and electronic components industries and semiconductor manufacturers. The foundations provided by TPM conform to the RosettaNet Implementation Framework (RNIF) standards. ebxml (Electronic Business XML) An open, global, XML-based protocol for standardizing international digital trading environments The foundations provided by TPM support ebxml-based BtoB trading. CIDX (Chemical Industry Data exchange) A group based in the United States developing standards in XML and EDI for the chemical industry, mainly concerned with developing standards for digital transactions in the industry. TPM conforms to the Chem estandards recommended for standardization by CIDX and so is suitable for application in BtoB trading in the chemicals industry Trading Scenario Definitions A trading scenario defines in advance the method of trading between your company and a trading partner based on a TPA (Trading Partner Agreement). A trading scenario contains the following information: The type of business document to be exchanged and the method of exchange Details such as the company codes, protocols, and addresses used by your company and your partner company The role of your company Business document attributes TPM provides the scenario definition tool for the quick and easy input of this information into a definition in a GUI environment. TPM also provides scenario templates. Using these templates simplifies the process of defining scenarios Working with In-house Business Processes TPM provides the following means of linking in-house business processes (also known as private processes) and trading scenarios (also known as public processes): API libraries API libraries are libraries that allow defined public processes to be operated from user applications. You can 26

31 use these API libraries to develop applications to link existing business systems to public processes. Linkage with process definitions If you define your trading partner's scenario definition and process definition as subprocesses of your scenario definition and process definition and vice versa, you can use these definitions as a basis for linkage. For example, if your company initiates trading, you can create a link for trading by defining a scenario definition as a subprocess of your company's process definition. If your trading partner initiates trading, they can create a link for trading by defining the corresponding process definition as a subprocess in their scenario definition. Using these means, you can simplify the transition to new BtoB trading systems that use existing trading systems Trading Analysis Logs TPM keeps a record of BtoB trading in the form of logs. You can use trading analysis functions to display and analyze these logs, and so access statistical information for use in improving trading processes. 3.6 Web Services Aggregator CollaborationRing PM provides Web Services Aggregator as a means of simplifying the construction of systems to link with Web services. Web Services Aggregator provides the following functions to enable linkage with Web services: +++ Process Definition Add-in An add-in is provided for defining processes by UML (Unified Modeling Language - a standard modeling language established by the Object Management Group). This add-in is a tool that provides functions for creating CollaborationRing PM process definitions that include Web services. By combining the add-in with the UML tool Rational Rose, you can create process definitions using UML. +++ Web Service Access Components Normally specialist knowledge of networks, XML, and protocols, and programming technology are necessary to use a Web service and UDDI. Web Services Aggregator offers component groups that allow you to use a Web service and UDDI by making simple parameter settings. This means that you can now discover dynamic transaction partners and implement dynamic transactions, and establish the same business processes that are used by processes in other enterprises. +++ Web Service Publisher This is a function that makes CollaborationRing PM business processes available externally as Web services. This means that you can use CollaborationRing PM business processes from external systems. +++ Web Service Performance Analyzer This is a function that analyzes the operating performance of a Web service. You can use the analysis result as information for selecting trading partners. 27

32 [Web Services Aggregator] 3.7 Linkage Function with BizTalk Server CollaborationRing PM provides this function to enable linkage to processes in Microsoft(R) BizTalk Server. You can use this function to link to the schedule for EAI systems constructed by BizTalk Server. [Linkage Function with BizTalk Server] 28

33 Chapter 4 System Construction by CollaborationRing PM Business applications, packages, and systems are integrated in the following ways: Integration of existing business applications and systems Creation of new business systems (such as systems using ERP packages and BtoB trading systems) and their integration with existing business systems Integration including human workflow systems Integration by business process CollaborationRing PM provides methods of accomplishing each of these types of integration, and these methods are described in this chapter, along with an overview of the business applications that run in CollaborationRing PM. 4.1 Integration Types and How to Construct Them There are three methods of integrating business applications and systems using CollaborationRing PM, depending on the function used: System construction with EAP Use this method when constructing in-house application integration systems, business data integration systems, and current EDI trading systems. System construction with process flow manager Use this method when constructing process flow systems. System construction with TPM Use this method when constructing BtoB trading systems. [Integrating Business Applications and Systems] 4.2 System Construction with EAP When integrating business applications and systems with EAP, you can use the standard process models for system linkage provided with EAP to construct systems. In this way, there is no need to create process definitions during construction, and you can also use the GUI software provided by EAP for easily creating the definitions for building the operating environment Linkage Definition With EAP, a linkage relationship is defined by associating the logical nodes that are defined with leading tasks and following tasks. Items such as message queues (when linking by messaging middleware) and IP addresses (when linking by file transfer middleware) for transferring data between partner systems become logical node entities. 29

34 Two sets of information define logical nodes: logical node definitions and node group definitions. A node group definition is multiple nodes grouped together and handled as a single logical node. In addition, an action definition is used to provide the definition information for associating the logical node definition or node group definition that is the input source with the logical node definition or node group definition that is the output destination. These three kinds of definition information are used to define system linkage relationships in EAP. Items defined in a logical node definition include an identifying name for the node and recipient information such as queue name and IP address. A node group definition contains the names of the logical nodes that are grouped within it. An action definition contains the names of the input source and output destination logical nodes and the process model used for linkage. The process model is determined by the input and output interface combination of the linking method (file transfer, messaging, and so on). EAP displays the most suitable process models in a GUI screen, from which you can select the one appropriate to your situation and then define it. You can also specify information such as whether format conversion is available and, if so, the format conversion definition name, as well as sorting conditions and user exits. [Linkage Definition] EAP uses these definitions to achieve linkage. For example, when data are received from a given logical node, data are processed and sorted according to the process model specified in the action definition linked to the logical node, and thus linkage is effected Definitions for EAP Essential definition information, such as whether or not format conversion is performed, changes according to linkage requirements. However as a rule, the following definitions are required for linkage: +++ EAP Definitions These define the behavior of EAP. The following three EAP definitions are available: Logical node definitions Node group definitions Action definitions EAP definitions are created using the GUI software provided with EAP. +++ Format conversion definition This is required if the linkage process for data received from a leading task needs to be converted to a compatible format. There are three types of definition for format conversion: Format definitions for input data (such as columns, attributes, and number of digits) Format definitions for output data (such as columns, attributes, and number of digits) Rule definitions for column conversion GUI software is provided for creating format conversion definitions. Definitions are usually created on the computer in which that software is installed. When the definition is complete, the definition information is verified on that computer, then uploaded to the computer on which CollaborationRing PM is running. Definition information can also be verified on computers not connected to the servers and can be uploaded to the server from a GUI screen. 30

35 +++ Definitions for middleware products These are not actually definitions for CollaborationRing PM. When any kind of third party middleware product is used to link CollaborationRing PM with partner systems, it is necessary to create a definition for that product, according to the instructions of that product. Note that definitions for adapters are generally stored centrally in the EAP definition. 4.3 System Construction with Process Flow Manager This method of system construction is used when integrating business applications using process flow function, as with human workflow systems. The tasks involved are as follows: Design and define business processes Develop business applications to run on process flow manager Construct linkage processes for existing systems This section gives an overview of defining business processes and developing business applications. You can use EAP to establish links to existing systems Business Process Definitions When constructing systems with process flow manager, it is necessary to define business processes to integrate business applications in the process flow. [Business Process Definitions] You can define business processes by using the process definition tool, by using the process definition add-in, or by using API and XML expressions. +++ Definition by process definition tool Using the process definition tool, you can define business processes graphically, using the icons and arrows provided with the tool. 31

36 [Definition by Process Definition Tool] The completed process definition is used after being registered in the control server. There are two methods of registering process definitions created with the process definition tool: By logging into the control server directly and creating and registering definitions By downloading process definitions from the control server to your computer, modifying those definitions to suit your needs, then uploading them to the control server and registering them as new definitions. If the business processes to be defined are complex or long, you can extract parts of the process and define them as independent subprocesses. In the invoking process definition, the subprocesses are defined as subprocess activities. The range of business processes handled by the process flow manager is limited to processes within one control server. The process definition tools also handle business processes within this unit. If you are running multiple control servers, you must create process definitions for each managing control server. In the invoking process definition, the processes defined in other control servers must be defined as subprocess activities. +++ Definition by process definition add-in The process definition add-in is provided as a Rational Rose add-in. It is used to define processes using the standard modeling language UML. When using the Web service linkage function, use the process definition add-in to define the processes that invoke Web services. +++ Definition by API and XML expression Process flow manager provides APIs for creating process definitions and functions for the input and output of process definition information using XML expressions. Using this function, you can prepare user-specific process definition views and define processes dynamically in business programs Overview of Business Applications A defined business process starts processing a business document when the document is initiated. Process flow manager determines the next activity to be executed according to the defined process rules and invokes the business application specified in that activity. This section describes the items below in order to give an overview of the business applications that run on CollaborationRing PM. 32 Business application processes and business documents Client-type API and server-type API Attachment function Guaranteeing business document integrity Duplicate execution prevention function

37 +++ Business application processes and business documents Business documents specified when a business application is drafted are managed in CollaborationRing PM as XML documents comprising management information and job-dependent information, as detailed below. When a business application is invoked from process flow manager, business documents are received from process flow manager and the required information is extracted. Processing is carried out based on this information. The business documents are updated based on these results, and then returned to process flow manager along with the process results. The results are inherited by the next activity, and this completes the business process. Note that business documents are managed according to the process generated when the document was drafted. Business documents managed in this way are sometimes referred to as "process documents". [Postscript Structure using XML Documents] Management information The management information is the part that the process flow manager uses to manage processes. The types of management information are fixed, and additional types cannot be added for different tasks. However, the management information in the customizable character string type provides a degree of freedom to facilitate faster searches. Job-dependent values can be entered here so that job-dependent conditions can be used when searching business processes. Job-dependent information The job-dependent information groups the multiple items of job data expressed in the XML document (actually, an XML fragment). This is also called the business document data. This data can be added to or changed at any time in accordance with business process execution. Individual items of job data are referred to as "user elements" or "variables". These parts are all assigned different tag names for management. Any name that suits the job can be added, as long as the tag names are different. The basic data that can be included as user elements are character data, but are not restricted to document structures that use tags. Any XML document (strictly speaking, XML fragment) can be used as a user element. User elements without an internal tag structure are called character string type; user elements with an internal tag structure are called XML document type. You can use character string type user elements and some management information variables (such as custom attributes) in conditional expressions of process definitions. Storing existing form data CollaborationRing PM provides a service that changes data to Base64 code to enable XML documents to carry business documents in any format that includes binary data. This service can input and output as user elements any business documents that have been changed to Base64 code. Changing to Base64 code adds an overhead to the processing load and data quantity, but enables business documents to be carried in their existing format and avoids the work involved in recoding the document data in XML. 33

38 +++ Client-type API and server-type API Process flow manager provides two types of API for developing business applications: Client-type API Server-type API These APIs can be used when using client-type API libraries and server-type API libraries. The client-type API is the API used for business document operations under initiation. Initiation refers to the situation where invocation from an application is the start point for the operation, for example, when drafting a new business document from a Web browser. The server-type API is used in automatic execution applications invoked automatically from process flow manager according to the process definition. An automatic execution application is an Interstage Application Server distributed object (CORBA server object) with XML document input and output functions. Note that, it is possible to use both server-type API and client-type API to enable an automatic execution application to behave as a client. The main functions of client-type APIs are listed below. You can use them to, for example, start a new process by a drafting operation or search the list of retained conditions. Initialization: Initializes the client-type API by setting user information and client authentication certificates. Process definition operations: Performs operations on business processes such as viewing processes and creating processes. When an application initiates a form, it can refer to the process definition list and process definitions themselves. Activity operations: Performs operations on activities in processes, such as reading out data in business documents and reflecting process results data in business documents. Before initiating a task, the application can obtain a list of the tasks to be managed. Process operations: Performs operations on created processes, such as reading a list of created processes, viewing process status and terminating a process. The application can determine how far a task within a process has progressed, or suspend a task within a process. List searches: It is possible to read a list of process definition to be created, read a list of created processes and read a list of tasks (worklist). The list can be narrowed by setting search conditions. +++ Attachment function It is often the case in e-business transactions that product catalogs are sent as attachments of business documents. Process flow manager manages the attachment file information of each business document to ensure that the latest information is always included. The attachment function retrieves the file information of attachments set in processes corresponding to business documents and provides renewable APIs. The file information that can be set includes the file name, file path, file type, and file comment. The name of the file server in which the file is stored is set with the Management Tool. +++ Guaranteeing business document integrity CollaborationRing PM guarantees the data content passed between activities, even when errors occur, and maintains process status and data content integrity. To this end, CollaborationRing PM uses the database to manage synchronicity between the data content and the process advancement status and detailed history. If the server stops for any reason, or if the server is forcibly stopped due to operational necessity, firstly database recovery processing is performed to recover database content consistency. Then, consistency is recovered between the business document processing advancement status (that is, to which activity has processing advanced) and the passed data content. CollaborationRing PM commits data to the database at the end point of an activity and maintains the managed business document transactions in activity units. 34

39 [Database Recovery Processing following Server Stoppage] +++ Duplicate execution prevention function When attempting to recover status integrity after re-execution, users must consider the possibility that the results generated when a process that has already been executed once is re-executed may differ from the results generated the first time the process was executed. As shown in the following figure, CollaborationRing PM contains support functions that deal with the problem of duplicate updates to databases caused by duplicate execution of automatic execution applications and the problem of duplicate operations from client-type APIs. [CollaborationRing Support Functions handle the Problem of Duplicate Updates] With automatic execution applications, when business applications run on the execution server (OTS linkage server), the execution server (OTS linkage server) can refuse a request for processing if that process has already been 35

40 completed. Thus, duplicate execution invocations are not issued to business applications. For this function to operate effectively, updates to the business database must be synchronized with execution server (OTS linkage server) status management using the global transaction function (Interstage Application Server OTS function). [Duplicate Execution Prevention for Automatic Execution Activities] 4.4 System Construction with TPM You can use TPM to create a BtoB trading system. There are three main tasks: Creating scenario definitions Creating linkage to in-house business processes Developing linkage applications for linkage to in-house systems Creating scenario definitions means defining trading processes (public processes). Creating linkage to in-house business processes and developing linkage applications for linkage to in-house systems mean creating linkage to your company's business systems. TPM provides templates to simplify and speed up system construction. You can customize these templates to suit your method of system construction. For more information on constructing BtoB trading systems, refer to the TPM Guide. 36

41 Chapter 5 CollaborationRing PM Operations CollaborationRing PM operations can be divided into two types: monitoring the CollaborationRing PM system itself and monitoring business processes carried out by CollaborationRing PM. To this end, CollaborationRing PM provides tools for: the centralized monitoring of servers, including linked systems, by linkage to Systemwalker, and for displaying and modifying the status of running business processes. This chapter gives an overview of these operations as well as explaining how to ensure high system availabiliity (HA) and guarantee communication security. 5.1 Monitoring Operations by Linkage to Systemwalker By linking with Systemwalker/Centric MGR, it is possible to manage the organization of the CollaborationRing PM system and to deal with any problems that arise during its operation. Systemwalker/Centric MGR provides the necessary functions for the centralized monitoring of problems in networks, systems, applications and so on. The functions are implemented from Systemwalker/Centric MGR as described below. Message Notification Event Monitoring Display of Detailed Messages Help Desk Knowhow Form Execution of Start and Stop Commands Remote Command For more details on each function, refer to the Systemwalker/Centric MGR manual Message (Event) Monitoring By making settings so that messages output by monitored CollaborationRing PM servers are sent to the operation management server using Systemwalker CentricMGR, you can monitor the operations of servers, including those of linked systems, from the console on the operation management server. [Systemwalker Linkage Message Notification] With Systemwalker/Centric MGR, a variety of information can be monitored. Information on problems that occur when linking to CollaborationRing PM is output in the form of the following error messages to the event log of the CollaborationRing PM server that is being monitored. Error messages output to syslog Display of Detailed Messages (Events) CollaborationRing PM error messages gathered by event monitoring in Systemwalker/Centric MGR are managed by transforming them into a database using the Systemwalker/Centric MGR Help Desk function. You can quickly restore 37

42 the system after an error by referring to the detailed information in the appropriate message Execution of Start and Stop Commands You can start and stop CollaborationRing PM functions remotely from the Systemwalker operation management server console. 5.2 Displaying and Modifying the Status of Business Proc esses CollaborationRing PM provides the following tools for displaying and modifying the status of business processes: Management Tool A tool for general business processes (mainly private processes). TPM Management Tool A tool specialized for BtoB trading processes (public processes) Management Tool Using the Management Tool, you can display and modify the status of business processes. You can also display and modify registered user information. [Management Tool] The tasks that you can perform with the Management Tool are described below. +++ Control server working environment modification You can change the working environment of the control server. Changes are made valid only after the control server is restarted. The items that you can modify are as follows: Linkage user name password Web server URI Control server administrator information (such as administrator ID and Management Tool port) Control server database environment 38

43 Mail linkage function environment Trace acquisition information (such as the trace acquisition level and trace file location) +++ User management You can view, update, add, delete, import, and export users registered in the control server. You can also view, grant, and revoke rights, and save lists to file. The information to which you can refer is as follows: User name Login name address User information Group +++ Group management You can view, update, add, and delete group information registered in the control server, and save lists to file. The information to which you can refer is as follows: Group name Group information User names in the group +++ Process management With processes that exist in the control server, you can: - display the list of processes - refer to processes - suspend, delete, and update processes - display process status - refer to variables - replace, add, and delete names of users registered in processes - save lists to file. The information to which you can refer is as follows: Process ID Globalkey (a unique ID number generated by CollaborationRing PM for a business document) Process subject Process description Priority Creator Status Process creation and end times User variables and set values Process definition title, version, and size of process used to draft a form Process history Process attachment information +++ Locked process management You can view, unlock and save to file locked processes registered in the control server. The information to which you can refer is as follows: Process ID Name of user who locked the process Lock key Lock reception time +++ Process definition management You can download, delete, change the title of, and replace, add and delete the operator name of process definitions registered in the control server. You can also view variables, save lists to file, and register process definitions created on a PC local machine in the control server. The information to which you can refer is as follows: Title Explanation Version 39

44 Owner name URL +++ Event management With events queued in the control server, you can: - display the list of events - display the list of detected error events - display the list of execution events in the control server (events currently being executed or for which execution is complete) - refer to error events - retry and delete events - save lists to file. The information to which you can refer is as follows: Event message ID Event issue time, event start time, event end time Event name Process ID Name of activity that caused the error Error message, error code, minor code, globalkey +++ Linkage approver management You can view, update, add and delete linkage approver information registered in the control server and save lists to file. The information to which you can refer is as follows: User name Login name address User information +++ History Send Agent database management You can delete process information on the History Send Agent database and save lists to file. The information to which you can refer is as follows: Process ID Recipient URL +++ Collection database management You can delete process information on the collection database and save lists to file. The information to which you can refer is as follows: Process ID Globalkey Process end time TPM Management Tool TPM Management Tool is a tool for managing BtoB trading processes. Using TPM Management Tool, you can refer to processes and carry out more efficiently the daily tasks listed below. Displaying the list of processes and detailed information Deleting processes Displaying process history Displaying graphically process progress (tracking information) Displaying the list of scenario definitions and detailed information Deleting scenario definitions and deleting all versions Displaying the list of error events and detailed information Retrying and deleting error events Displaying the list of unknown processes and detailed information Deleting unknown processes 5.3 Log Acquisition In order to facilitate troubleshooting and problem solving, CollaborationRing PM provides a variety of logs. By viewing 40

45 log information in a Web browser and processing it in applications, you can check detailed status and progress conditions. The main logs are as follows: Process flow manager log The process flow manager log records changes according to the progress of processes and records the behavior of business applications specified in activities. EAP log The EAP log records details, including process results and error information, for the following tasks performed by EAP: - data receipt from leading task - data extraction - data sorting - data aggregation - data splitting - data format conversion - data transfer to following tasks You can notify business applications that are carrying out procedures of log information as it is acquired. By referring to logs, you can confirm the processing history of data received from leading tasks. BtoB trading log The BtoB trading log records trading details. 5.4 Running a High Reliability System CollaborationRing PM provides a HA (High-Availability) function. For this function, CollaborationRing PM is loaded on two server machines. One machine operates as a virtual server machine to provide the high availability (high reliability) of the system. The two server machines comprise a cluster system, with one machine operational while the other is on standby. If a fault is detected in the active machine, the system and applications are passed to the standby machine so that the fault in the originally active machine can be fixed while operations continue uninterrupted Cluster System Supported by CollaborationRing PM If multiple servers are grouped together and used as one system, this is referred to as a cluster system. As far as the client computers are concerned, the multiple servers are a single server. In a server system using this cluster format, the server machine that provides business services during normal operation is called the active node. The server machine that provides business services instead of the active node when an error occurs in the active node is called the standby node. If only a single server machine is used for operations, human intervention is required to restart operations if the server machine stops or if server applications running on the server machine stop. In many cases, when an error is detected, work stops for several hours while the error is dealt with. However, in a cluster system, the nodes comprising the system are always monitored and, if an error occurs in the active node, the systems and applications running on that machine are restarted on the standby node. Thus, jobs can be restarted in a matter of minutes and the working time of services is maximized. This is referred to as HA by a cluster system. The CollaborationRing PM HA function uses this function to build highly reliable systems. 41

46 [Cluster System provides High Availability] Resource Registration and Dependency Relationships between Resource s When the CollaborationRing PM HA function is used, resources are registered in the cluster system. The resources to be registered are the Interstage Application Server, DBMS and CollaborationRing PM server functions, user applications, and other resources. In some cluster systems, these resources are also grouped and registered as job groups Process Flow when Active Node Stops The following figure shows the flow of the business service recovery processing when an error occurs in a CollaborationRing PM system (active node) that is using the HA function. [Flow of Business Service Recovery following Error Occurrence] 1. Error occurrence at active node The active node may stop due to a hardware or software error or due to an operator mistake. Alternatively, the active node may be stopped intentionally for maintenance. 2. Active node stop detected A private network is built between the active node and standby node in a cluster system. The standby node continually monitors the active node via this network to check that it is working. When the active node stops, the standby node no longer detects the signal coming from the active node via this private network, and therefore determines that the active node has stopped. 3. Services and applications started at standby node When active node stop is detected, the IP addresses are passed from the active node to the standby node, and the following are started in the sequence set in the cluster system: DBMS, Interstage Application Server, automatic execution applications, the CollaborationRing PM server functions, and user applications. When all the resources that were operating at the active node are started at the standby node, and business re-opens, this is referred to as "fail over". 4. Recovery processing after re-opening When the HA function is used, fail over enables business to re-open quickly. Even so, as with system failures in systems not using the HA function, the jobs that were running at the point when fail over occurred, depending on the job, must be considered when the job re-opens. To avoid subsequent problems, files and databases that were only partially updated may need to be fixed, and jobs that were being executed at the time may need to be re-opened manually. 5.5 Communication Security SSL (Secure Socket Layer) can be used to strengthen the security provided by the standard protocol SWAP when CollaborationRing PM is used for external transactions. SSL is an encryption technology method proposed by Netscape Communications Corporation for enabling safe electronic commercial transactions on the Internet. SSL can be used between client machines that use the client-type API and between control servers, and can also be used for client authentication. 42