Embed Size (px)
Citation preview
B1WD-2321-01ENZ0(00)August 2008
Business Process Manager Analytics 10.1
User's Guide
Preface
Purpose of this Document
This document provides an overview of Interstage Business Process Manager Analytics(hereafter abbreviated as "Analytics"). It describeshow to operate and use Analytics.
Who Should Read this Document?
This document is intended for users who need to install, operate, or use Analytics.
This guide assumes knowledge of the following:
･ Business systems
･ Application servers
･ Relational databases
･ The database system you are using (Oracle, SQL Server, or Symfoware)
･ Internet basics
･ Interstage Service Integrator
･ Interstage Business Process Manager (Interstage BPM Flow)
･ Interstage Job Workload Server
･ Interstage Interaction Manager
･ Interstage Studio
Organization of this DocumentThis document comprises the following chapters:
Chapter 1 Overview of Analytics
This chapter provides an overview of Analytics.
Chapter 2 Functions
This chapter describes the Analytics functions.
Reading this Document
The following table indicates which parts of this document to read for various purposes.
Purpose Chapter
To gain an overview of Analytics 1
To learn about Analytics functions 2
Notation Used in this Document
Abbreviations
The following abbreviations are used in this document.
- i -
Formal name Abbreviation
Microsoft(R) Windows Server(TM) 2003, Standard EditionMicrosoft(R) Windows Server(TM) 2003, Enterprise EditionMicrosoft(R) Windows Server(TM) 2003 R2, Standard EditionMicrosoft(R) Windows Server(TM) 2003 R2, Enterprise Edition
Windows Server 2003, or Windows
Microsoft(R) Windows Server(TM) 2003, Standard x64 EditionMicrosoft(R) Windows Server(TM) 2003, Enterprise x64 EditionMicrosoft(R) Windows Server(TM) 2003 R2, Standard x64 EditionMicrosoft(R) Windows Server(TM) 2003 R2, Enterprise x64 Edition
Windows Server 2003 x64,Windows Server 2003, orWindows
Microsoft(R) Windows Server(R) 2008, Standard EditionMicrosoft(R) Windows Server(R) 2008, Enterprise Edition
Windows Server 2008 or Windows
Microsoft(R) Windows(R) XP Professional operating systemMicrosoft(R) Windows(R) XP Home Edition operating system
Windows XP, or Windows
Microsoft(R) Windows Vista(R) Business
Microsoft(R) Windows Vista(R) Enterprise
Microsoft(R) Windows Vista(R) Ultimate
Windows Vista or Windows
Microsoft(R) Internet Information ServerMicrosoft(R) Internet Information Services
IIS
Microsoft(R) Internet Explorer 6.0Microsoft(R) Internet Explorer 7.0
Internet Explorer
Microsoft(R) Office Visio(R) Professional Visio(R)
Microsoft(R) Excel Excel
Solaris(TM) 9 operating system Solaris 9, or Solaris
Solaris(TM) 10 operating system Solaris 10, or Solaris
Red Hat Enterprise Linux ASRed Hat Enterprise Linux ES
Linux
Interstage Application Server Enterprise EditionInterstage Application Server Standard-J Edition
Interstage Application Server
Interstage Studio Enterprise EditionInterstage Studio Standard-J Edition
Interstage Studio, or Studio
Interstage Service Integrator ISI
Interstage Business Process Manager(Interstage BPM Flow)
Interstage BPM or BPM Flow
Interstage Job Workload Server IJOB
Interstage Interaction Manager Interaction Manager
Oracle9i Database Standard Edition R9.2.0Oracle9i Database Enterprise Edition R9.2.0Oracle 9i Database Standard Edition One R9.2.0
Oracle9i, or Oracle
Oracle Database 10g Enterprise Edition R10.1.0/R10.2.0Oracle Database 10g Standard Edition R10.1.0/R10.2.0Oracle Database 10g Standard Edition One R10.1.0/R10.2.0
Oracle10g, or Oracle
Microsoft SQL Server 2005 Standard EditionMicrosoft SQL Server 2005 Enterprise Edition
SQL Server 2005, or SQL Server
Notation
This document uses the following notation.
- ii -
Notation Description
[ ] Words displayed in screens, dialog boxes, and keyboard keys are enclosed in square brackets,for example:
[Settings] dialog box
[File] menu
[Item name]
[OK] button
[Enter] key
[ ]-[ ] Indicates screen menus and menu commands.
For example, for the [Settings] command under the [Tools] menu:
[Tools]-[Settings]
-> Indicates the results of an operation.
---
Indicates that some information is omitted, for example: <TABLE>---</TABLE>
Important information which must be read and carefully noted.
Helpful information.
Hints to facilitate understanding.
Reference information.
A reference location with further details.
Platform-specific explanation.
: Windows
: Solaris
: Linux
Export regulations
Fujitsu documents may include special technology regulated by foreign exchange and foreign trade regulation laws. If special technologyis included, permission must be obtained under these laws before exporting a document or providing it to a non-resident.
Trademarks
･ Microsoft, Windows, and Windows Server are trademarks or registered trademarks of Microsoft Corporation in the United States andother countries.
- iii -
･ Sun, Sun Microsystems, the Sun Logo, Solaris and all Solaris based marks and logos are trademarks or registered trademarks of SunMicrosystems, Inc. in the United States and other countries, and are used under license.
･ Linux is a registered trademark or trademark of Linus Torvalds in the United States and other countries.
･ Red Hat is a trademark or registered trademark of Red Hat Inc. in the United States and other countries.
･ Java and all Java-related trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United Statesand other countries.
･ Oracle is a registered trademark of Oracle Corporation (USA).
･ SQL Server is a Microsoft Corporation (USA) product.
･ "BEA WebLogic Server" is a registered trademark of BEA Systems, Inc.
･ "DB2" is a registered trademark of IBM Corporation (USA).
･ Pentium(R) is a registered trademark of Intel Corporation (USA).
･ All other company and product names referred to in this document are general trademarks or registered trademarks of their respectiveowners.
･ Screenshots are used in accordance with Microsoft Corporation guidelines.
Requests
･ This document may be revised without notice.
･ Do not pass on this document to other parties without permission.
･ Fujitsu bears no responsibility for third-party infringements of patent or other rights arising out of use of the data contained in thisdocument.
August 2008 First Edition
- iv -
ContentsChapter 1 Overview of Analytics..............................................................................................................................................1
1.1 Product Description.............................................................................................................................................................................11.2 Analytics Features................................................................................................................................................................................21.3 System Configuration..........................................................................................................................................................................5
1.3.1 Overview of System......................................................................................................................................................................51.3.2 System Configuration Details.......................................................................................................................................................61.3.3 Management Database..................................................................................................................................................................71.3.4 Related Software...........................................................................................................................................................................9
Chapter 2 Functions...............................................................................................................................................................102.1 Function List......................................................................................................................................................................................102.2 Detailed Functionality Description....................................................................................................................................................10
2.2.1 Event Collection.........................................................................................................................................................................102.2.2 Event Processing.........................................................................................................................................................................112.2.3 Visualisation and Action.............................................................................................................................................................112.2.4 Management Client.....................................................................................................................................................................13
2.2.4.1 Analytics Designer...............................................................................................................................................................142.2.4.2 Management Console..........................................................................................................................................................152.2.4.3 Management Commands.....................................................................................................................................................15
2.2.5 Linking Data with External Tools..............................................................................................................................................152.2.5.1 CSV Output Command........................................................................................................................................................15
- v -
Chapter 1 Overview of AnalyticsThis chapter provides an overview of Analytics.
1.1 Product DescriptionAnalytics monitors and displays the state of business activity and business flow. This helps improve efficiency and response times in areaslike customer service, thereby increasing corporate competitiveness.
In practical terms, Analytics displays the state of business activity in real-time charts, and notifies site users by email when problemsoccur. This allows users to track the state of the business in real time and to take appropriate action if a new corporate vision requiresgreater efficiency and faster responses.
Analytics also enables users to track the state of each process associated with the flow of business, and to monitor violations based onmanagement indices. Thus, useful judgments can be made about the site activity.
Analytics includes functions for Business Process Management (BPM) and for Business Activity Monitoring (BAM).
What is Business Process Management (BPM)?
BPM handles business processes as models. This initiative is designed to identify the problem points in a business flow in order to makecontinuous improvements.BPM uses the business process management cycle shown below, assisting users to continually make improvements and construct moreefficient business processes.
- 1 -
What is Business Activity Monitoring (BAM)?
BAM is one of the approaches recommended for BPM, and involves monitoring the state of business implementation and performanceresults. Having an understanding of conditions in real time enables site optimization.
1.2 Analytics FeaturesAnalytics offers the following features.
Tracking the status of business activities in real time
Analytics monitors business data and can display the business activity state as a graph or a table on a screen known as the dashboard.
If, for example, threshold values (rules) are set in advance for items such as sales quantities and numbers of orders processed, Analyticscan periodically check business data and display an alert if there is a problem.
- 2 -
Alert notification enables prompt responses
Analytics can detect abnormalities, such as delivery delays and sudden changes in sales quantities, and post an alert using either thedashboard or email. It can also call the service bus, flow engine, or on-demand batch execution engine. Users are made aware of anybusiness problems extremely quickly, which improves the speed and efficiency of responses.
Business process visibility provides an awareness of business progress
Business processes are displayed as a flow chart, and colors are used to display the state of business progression. Errors are displayed inred, warnings in yellow, normal termination in green, and business that is in progress is in blue.
In addition, if threshold values have been set for business data, items that exceed the threshold values are displayed in red (errors) or yellow(warnings).
Analyzing the performance of business processes supports efficiency improvements
Key performance indicators (KPI) needed for making business processes more efficient (such as lead times and on-time completion ratesfor business processes) can be tracked using the dashboard.
- 3 -
Support for installing add-ons to existing systems
Analytics can be installed as add-ons using standard adapters, without affecting existing systems. Check conditions can also be controlledexternally without having to amend the existing business logic.
Use in conjunction with work flow (Interstage BPM)
If the business system is to operate under Interstage BPM, these can be installed quickly. The process definition information managed byInterstage BPM can be imported as business process models. Since event data(*1) is collected automatically, the installation process is easilyperformed.*1: Event data is the data that indicates when events in the business system have occurred.
Event collection from service bus (Interstage Service Integrator)
Interstage Service Integrator (ISI) is a service bus product that can combine, as services, applications and packages that operate inenvironments other than J2EE and mainframe environments. Via ISI, Analytics can handle the processing status of interactive servicesand actual data as events.
Business data event collection (database)
The values of specific items in databases (for example, product inventory databases) used during business system operation can be collectedat regular intervals as events. Collection from Oracle, SQL Server, and Symfoware database systems is supported.
･ Symfoware Server V8.0
･ Symfoware Server V9.0
･ Oracle 9i Database
･ Oracle Database 10g
･ Microsoft SQL Server 2005
･ DB2
- 4 -
Collection of events from Text files
The values of specific data items (for example, business application execution logs) that are output to text files during business systemoperation can be collected at regular intervals as events. Collection from text files is supported for the following formats:
･ CSV format
･ FLAT format(*1)
･ Other delimited formats (comma delimited, tab delimited, etc.)
*1: The FLAT format is a fixed-length format that has multiple items in each record. The length and data type are determined separatelyfor each item, and items must be arranged in sequence without any changes of position.
Changing Settings using the GUI
Definitions can be customized via the GUI, in response to changes to business styles or monitoring requirements.
1.3 System ConfigurationThis section describes the system configuration that is used by Analytics for business monitoring.
1.3.1 Overview of SystemAnalytics provides server and client functions, as shown in the figure below.
The server functions perform business monitoring, and consist of three components ((1) to (3)). The client functions provide setup andother operation management.
In order to implement monitoring, several related products in addition to Analytics are required.
- 5 -
The overall operation of Analytics is as follows:
1. Analytics collects events from the business system being monitored, and manages the collected events in an event database.
2. Analytics periodically monitors the event database, assesses alerts, and performs statistical processes.
3. Analytics displays the contents of alerts and statistical results on the dashboard and distributes this information via email. When analert is issued, Analytics can also call the service bus (Interstage Service Integrator), the work flow engine (Interstage BPM), andthe on-demand batch execution engine (Interstage Job Workload Server).
An overview of related products is as follows:
1. Interaction Manager
This is the software used to display the contents of alerts and statistical results. It provides user management functions which allowusers to control the information displayed and the layout of the screen.
2. Event database
This is an RDB, and is required for storing business events, statistical processes, and so on. Oracle, SQL Server, and Symfowarecan be used.
3. Linking data to external tools
The monitoring results in the event database can be output to CSV files so that the data can be linked to other systems or analyzedusing tools such as Excel.
In addition to the above, in order to use Analytics, Interstage Application Server is required as the Java execution environment and InterstageStudio is required at the client as the execution environment for implementing operation definitions.
1.3.2 System Configuration DetailsThe following figure shows the elements in the system configuration.
Event collection (sensor)
Events are collected from the following systems. Sensors can be placed on either business systems or the monitoring server.
･ RDBMS
･ Service bus (Interstage Service Integrator)
- 6 -
･ Text files
･ Workflow (Interstage BPM)
Monitoring Server
The event monitor creates statistics from the events stored in the event database, and performs assessments based on threshold values andother monitored conditions. Statistical results and alert information are posted via the dashboard.
Monitoring Server sets monitored conditions, statistics conditions, and statistics execution schedules, and it also monitors events.
･ Monitored conditionsMonitored conditions such as, for example, "have sales totals fallen below the threshold value?" can be set.
･ Statistics conditionsStatistics conditions such as, for example, the "Average value of sales revenue per day" can be set. Statistics results are stored in thedatabase managed by Analytics.
･ Statistics execution schedulesStatistics execution schedules such as, for example, "Every Monday at 9:00" can be set.
The following management databases are held internally on the monitoring server.
･ Event databaseThe event database stores events collected by event collection (sensors), and also stores alert information.
･ Archive databaseThe archive database is for backing up the event data stored in the event database.
Management Client
The Management Client is used to manage monitoring behavior.
･ Monitoring DesignerThe Monitoring Designer is a tool for setting up the definitions required for monitoring. This tool runs as a plug-in for InterstageStudio Management Console
･ Management ConsoleThe Management Console is a tool for controlling Monitoring Server and setting up the environment.
End User Client
The end user client is a client for displaying the dashboard window using a Web browser.
1.3.3 Management DatabaseInterstage BPM Analytics uses databases to store events.
･ Event DBStore Interstage BPM Analytics events.
･ Archive DB Move event data out of the Event DB to reduce the amount of data stored in it.
Another database, called the Archive DB, is used to move event data out of the Event DB to reduce the amount of data stored in it.
- 7 -
The event data contained in the Event DB and the Archive DB can be output as CSV files using the CSV Output Command. Refer to theInterstage BPM Analytics Management Reference for details on the CSV Output Command.
Event DB
The Event DB is used to store events that have been collected from a monitored system.
The following types of data are stored in this database:
･ General events
･ Event calculation results
･ Alert notification history
Archive DB
The Archive DB is used to store event data after a specified period, in order to reduce the amount of data in the Event DB.
Conditions for moving event data from the Event DB to the Archive DB can be specified for each business. The following conditions canbe specified:
･ Events that are subject to transfer
･ Period of data storage that is subject to transfer
Refer to the Interstage BPM Analytics Operator’s Guide for details.
The Archive DB is not a mandatory component. It should be created in the following cases:
･ To store old monitoring results for analysis by BI tools, when no database is used for monitoring by the Dashboard
･ To prevent access to the Event DB of an active node when extracting and analyzing data with BI tools
The following database systems can be used:
･ Oracle 9i/10g
･ SQL Server 2005
- 8 -
･ DB2 UDB 8.2
Refer to the relevant database manuals for installation instructions.
1.3.4 Related Software･ Mandatory software :
- Interstage Application Server or WebLogic or JBoss
- Interstage Studio
- RDBMS
･ Related software :
- RDBMS
- Interstage BPM
- Interstage Service Integrator
- Interstage Job Workload Server
- Interstage Interaction Manager
- 9 -
Chapter 2 FunctionsThis chapter describes the Analytics functions.
2.1 Function ListThe following table lists the functions provided by Analytics.
Function Overview Detail function
Event collection (sensor)
This function collects events from monitoredsystems and stores them in the event database.
･ Workflow sensors
･ ESB sensors
･ RDB sensors
･ Text file sensors
Event processing This function uses the events that have beencollected to perform statistics processing and tomake alert assessments.
･ Event statistics calculation
･ Alert assessment
Visualisation and action This function displays alert messages and KPIcharts in the dashboard, and sends alert messageemails.
･ Dashboard
- Alert View
- KPI Chart View
- Process Performance View
- Tracking View
･ Reporting
･ Escalation function
- Mail notification
- Calling other systems
Management Client This function sets up definitions and managesmonitoring behavior.
･ Analytics Designer
･ Management Console
･ Management commands
2.2 Detailed Functionality DescriptionThis section describes Analytics functions.
2.2.1 Event CollectionThe event collection function collects events from the system being monitored and stores the events in the event database. Analytics canmonitor the following types of systems:
･ Workflow (Interstage BPM)Interstage BPM monitoring can collect as events a variety of historical information such as process start, activity start and completion,and user information.
･ Service bus (ISI)The following types of information can be collected as events during ISI monitoring:
- State of service processes (service processing time and service execution logs)
- Customer data (ISI shared messages)
- 10 -
- ISI operating status (sequence processing time and error logs)
For example, events such as "Did the service processing time exceed a fixed interval?" and "Error count statistics" can be monitored.
･ RDBRDB monitoring collects at regular intervals data items stored in a business database, and stores them in the management databases.For example, events such as "Hourly monitoring of the latest stock price for company name 'Company A' in the stock price informationtable" can be monitored.
･ Text filesData that has been output to text files during business system operations can be collected as events. Text file monitoring can periodicallybrowse within files and collect as events the parts that have been added. In addition, collection conditions can be set such that onlyinformation that matches those conditions is collected. For example, events such as "Monitoring at 30 minute intervals of informationon travel expense applications that exceed a total of $US100" can be monitored.
There are two types of text file sensors: text file sensors that operate as Web applications, and text file sensors that operate as Windowsservices (Windows service edition text file sensor). The Windows service edition text file sensor can be used to collect monitoring datafrom machines in which Interstage Application Server is not installed.
Schedules and rules for event collection can be set.
･ Setting event collection schedules Users can select from schedule types such as: at specific time intervals, every week, and at the end of each month.
･ Setting event collection methods Event collection methods can be set to suit the system that performs the monitoring.
These settings are entered using the Analytics designer.
2.2.2 Event ProcessingThe event processing function performs statistics processing and make alert assessments to events collected by the event collection.
･ AlertingAssesses alerts to the collected events by setting conditions using threshold values. You can assess alerts to the events of statisticalresults.
- Checking the event by parameter valuesExample: When the sales is five million yen or less
- Checking the progress of a processExample: When a process is not completed three days before the due.
･ Statistical CalculationCalculates a sum or average of the collected events. The statistical results are managed as statistical events in the Event DB.
These settings are entered using the Analytics designer.
2.2.3 Visualisation and ActionThis function displays alert messages and KPI charts in the dashboard, and sends alert message emails.
･ DashboardThe status of business activities can be displayed using graphs or tables, and the status of alerts can be displayed in real time. Thismakes it possible to respond to the various events that arise during business operations (such as errors) more quickly and efficiently.
- Alert ViewThe Alert View is a Web-based monitor window that displays a list of the alerts that have occurred during business process
- 11 -
operations.
- KPI Chart ViewThe KPI Chart View is a monitor window that graphically displays various KPIs for business processes.
- Process Performance ViewThe Process Performance View is a monitor window for analyzing trends in KPIs and the overall performance of business
- 12 -
processes.
- Tracking ViewThe Tracking View is a window for searching for form instances in business processes. This view can be used to track progressand to check for problems such as delays in delivery.
･ ReportingThis function regularly generates report files of monitored results. It stores charts and alert records. You can also output report filesdirectly from the Dashboard.
･ EscalationWhen an alert is generated, the alert contents can be posted to site users via email, and the service bus and workflow system, batchexecution engine can be called.
Use the Analytics designer to enter these settings.
2.2.4 Management ClientThe Management Client is used to set up definitions for monitoring and to manage monitoring behavior.
･ Analytics designer
･ Management Console
･ Management commands
- 13 -
2.2.4.1 Analytics DesignerAnalytics Designer is a tool for defining the information required for monitoring operations. This tool operates as an Interstage Studioplug-in.
Use the Analytics Designer to set event collection settings and visualization methods.
Setting event collection
Set the following in the event collection settings:
･ Sensor (information for connecting to the systems being monitored, etc.)
･ Collection tasks (data to be collected, dealing with events to be stored in the event database, etc.)
･ Sensor operation schedule
Setting event processing
Set the following in the event processing settings:
･ Events (attributes of events to be stored in the event database, etc.)
･ Simple statistical rules (event statistics rules, format of statistical events that store statistical results, etc.)
･ Alert assessment (assessment conditions, messages to be output, etc.)
･ Statistical schedule
Setting visualization and actions
Set the following in the visualization and action settings:
･ Dashboard
- 14 -
･ Reporting
･ Access control for users
･ Escalation (message template format and distribution addresses, and connection destination)
2.2.4.2 Management ConsoleThe Management Console is a Web tool for making environment settings and managing monitoring behavior.
The Management Console has the following functions.
･ Monitoring Server Management
- Starting and stopping the monitoring server, making log file settings
･ Sensor Management
- Starting and stopping sensors
･ System Setting
- Setting up connection information for the event database and the mail server environment
2.2.4.3 Management CommandsManagement commands are used for operations such as start and stop the monitoring server.
･ Start the monitoring server
･ Stop the monitoring server
･ Display the status of the monitoring server
･ Change the connection destination monitoring server
･ Reregister event information
･ Re-execute escalation
2.2.5 Linking Data with External ToolsThe monitoring results in the event database can be output to CSV files so that this data can be linked to other systems or analyzed usingtools such as Excel. Use a management command to output data to CSV files.
2.2.5.1 CSV Output CommandThe events stored in event database can be searched using search conditions and can then be output as CSV files.
- 15 -
Search conditions are defined in files known as "search definition files". For example, conditions such as "Sales slips for which eventswere issued between 10/01/2006 and 10/31/2006 for order delivery tasks" can be specified.
- 16 -
