Business Process Manager Analytics 10software.fujitsu.com/jp/manual/manualfiles/M080185/... · Related software Interstage Business Process Manager 10 Interstage Interaction Manager

B1WD-2331-01ENZ0(00)August 2008

Business Process Manager Analytics 10.1

Installation Guide

Preface

Purpose of this Document

This document describes how to install Interstage Business Process Manager Analytics (hereafter abbreviated as "Analytics").

Who Should Read this Document?

This document is intended for system administrators who will be performing the Analytics installation tasks. It covers all aspects ofinstalling and uninstalling 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 Preparing for Installation

This chapter describes the preparation required before installation.

Chapter 2 Installing

This chapter describes how to install Analytics.

Chapter 3 Uninstalling Analytics

This chapter describes how to uninstall Analytics.

Appendix A Required Resources

This chapter describes the resources required.

Appendix B Requried disk size for database

This chapter describes how to estimate the database resources required.

Reading this Document

The following table indicates which parts of this document to read for various purposes.

- i -

Purpose Chapter

To learn about the preparation required before installation of Analytics 1

To install Analytics 2

To uninstall Analytics 3

To identify the resources required for Interstage Business Process ManagerAnalytics

Appendix A

To estimate the database resources used for Interstage Business ProcessManager Analytics

Appendix B

Notation Used in this Document

Abbreviations

The following abbreviations are used in this document.

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

- ii -

Formal name Abbreviation

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.

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.

- iii -

Notation Description

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.

･ 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 Preparing for Installation..........................................................................................................................................1

1.1 Installed functions................................................................................................................................................................................11.2 Operating Environment........................................................................................................................................................................21.3 Installation Flow..................................................................................................................................................................................51.4 Notes on Security.................................................................................................................................................................................5

Chapter 2 Installing...................................................................................................................................................................62.1 Tasks Required Before Installation......................................................................................................................................................62.2 Installation...........................................................................................................................................................................................7

2.2.1 Analytics Server Installation ( for Windows )..............................................................................................................................72.2.2 Analytics Server Installation ( for Linux )..................................................................................................................................102.2.3 Analytics Server Installation ( for Solaris )................................................................................................................................112.2.4 Client Installation........................................................................................................................................................................122.2.5 Sensor Installation.......................................................................................................................................................................15

2.3 Post-Installation Tasks.......................................................................................................................................................................202.3.1 Security Provided by Folder Access Restrictions.......................................................................................................................202.3.2 Changing the Management Console Password...........................................................................................................................21

2.4 Adding and Deleting Functions.........................................................................................................................................................21

Chapter 3 Uninstalling Analytics.............................................................................................................................................243.1 Tasks Required Before Uninstalling..................................................................................................................................................243.2 Uninstalling........................................................................................................................................................................................243.3 Tasks Required after Uninstalling.....................................................................................................................................................25

3.3.1 Deleting the Analytics Server Databases....................................................................................................................................253.3.2 Stopping and Deleting the WorkUnit for the IJob Execution Servlet........................................................................................26

Appendix A Required Resources........................................................................................................................................... 27A.1 Disk Space Required at Installation..................................................................................................................................................27A.2 Save Area for Monitoring Settings Data...........................................................................................................................................27A.3 Work Areas.......................................................................................................................................................................................27

A.3.1 Overview of Work Areas...........................................................................................................................................................27A.3.2 Estimating the Sensor Work Area..............................................................................................................................................28A.3.3 Estimating the Server Work Area..............................................................................................................................................31

Appendix B Requried disk size for database..........................................................................................................................32B.1 sammry of disk size (It is common in all data bases).......................................................................................................................32B.2 Database size necessary for each operation pattern.( It is common in all data bases)......................................................................32

B.2.1 pattern1 : monitoring of the small scale database......................................................................................................................32B.2.2 attern2 : monitoring of the large scale database.........................................................................................................................32B.2.3 attern3 : monitoring of the small scale workflow system..........................................................................................................33B.2.4 attern3 : monitoring of the large scale workflow system...........................................................................................................33

- v -

Chapter 1 Preparing for InstallationThis chapter describes the preparation required before installation.

1.1 Installed functionsThis section describes the installed functions.

･ Analytics Server (server function)This is main server function for Monitoring. Because Analytics Server has sensor function, Analytics Server can not be installed onthe environment where the sensor is already installed.

･ Sensor (senser function)The sensor is the component that collects events. Install a sensor on a separate machine if you want the sensor to run on a separatemachine from the Analytics Server.A sensor can be installed on the business system that is to be monitored, or on a separate system. Installation on a system other thanthe Analytics Server is recommended if you wish to give priority to Analytics Server operation performance.

- text file sensors:

- There are two types of text file sensors: a text file sensor that runs as a Web application, and a text file sensor that runs as aWindows service (the Windows service edition text file sensor). The Windows service edition text file sensor can be used tocollect monitoring data from machines where Interstage Application Server is not installed.

- Text file sensors collect events by accessing local files. Therefore, install the sensor on the system that has the targeted files.

･ Analytics Designer (client function)Analytics Designer is a setup tool as eclipse plug-in. It can be installed on any of the machines.

- 1 -

1.2 Operating EnvironmentThis section describes the operating environment.

Analytics Server

Hardware The hardware on which the Interstage Application Server 9 can run.

OS Windows Server 2003, Standard EditionWindows Server 2003, Enterprise EditionWindows Server 2003 R2, Standard EditionWindows Server 2003 R2, Enterprise EditionWindows Server 2003, Standard x64 Edition

- 2 -

Windows Server 2003, Enterprise x64 EditionWindows Server 2003 R2, x64 Standard EditionWindows Server 2003 R2, x64 Enterprise EditionSolaris 10RHEL5

Mandatory software Interstage Application Server 9 (JDK5.0) (for Windows)orWebLogic Server 9.2 (for Solaris)orJBoss Application Server 4.0.5 (for Linux)

Related software Interstage Business Process Manager 10Interstage Interaction Manager 9or other portal product(*1)

*1) Required if Dashboard is used on portal. Construction must be on the same system as the Analytics Server. Web servers that use portalproducts must use Interstage Application Server Apache2.0.

Sensor (if a stand-alone sensor is configured separately from a Analytics Server)

Hardware The hardware on which the Interstage Application Server 9 can run.

OS Windows Server 2003, Standard EditionWindows Server 2003, Enterprise EditionWindows Server 2003 R2, Standard EditionWindows Server 2003 R2, Enterprise EditionWindows Server 2003, Standard x64 EditionWindows Server 2003, Enterprise x64 EditionWindows Server 2003 R2, x64 Standard EditionWindows Server 2003 R2, x64 Enterprise Edition

Mandatory software Interstage Application Server 9(JDK5.0)

Sensor (Windows service edition text file sensor)

Hardware The hardware on which a Windows can run.

OS Windows XP professional SP2 or laterWindows Server 2003Windows Server 2003 R2

JDK JDK1.4.2(JRE1.4) or JDK5.0(JRE5.0) (*1)

*1) JDK1.4.2 (JRE1.4) and JDK5.0 (JRE5.0) can be obtained from: http://java.sun.com/

Management Console

Hardware The hardware on which a web browser can run.

OS Windows(R) XP, or Windows Vista Business/Enterprise/Ultimate

Web browser Microsoft(R) Internet Explorer 6.0 or later

Dashboard

Hardware The hardware on which a web browser can run.

- 3 -

OS Windows(R) XP, or Windows Vista Business/Enterprise/Ultimate

Web browser Microsoft(R) Internet Explorer 6.0 or later

Event Database Server /Archive Database Server

Hardware The hardware on which the DBMSs can run.

OS The operating system on which the DBMSs can run.

DBMS ･ Oracle9i R2/Oracle10g R1/R2

･ SQL Server 2005

･ IBM DB2 UDB 8.2

Analytics Designer

Hardware The hardware on which the Interstage Studio 9 can run.Note that the display resolution must be at least XGA (1024*768).

OS Windows(R) XP, or Windows Vista Business/Ultimate

Other mandatory software Interstage Studio 9orEclipse 3.2.2 and GEF3.2.2(Eclipse plugin)orEclipse 3.2.1 and GEF3.2.2(Eclipse plugin)

Other related software Interstage BPM Studio 10 (for Workflow sensor)Interstage Service Integrator 9 ISI Studio (for ESB sensor)

JDBC drivers

For Oracle The following Oracle JDBC drivers can be used:

･ 9.2.0.4.0

･ 9.2.0.5.0

･ 10.1.0.1.0

･ 10.2.0.1.0

For SQL Server The following SQL Server JDBC drivers can be used:

･ For SQL Server 2005:Microsoft SQL Server 2005 JDBC Driver

･ JDBC drivers can be downloaded from the Microsoft(R)website.

For DB2 The following DB2 JDBC drivers can be used:

･ UDB 8.2

- 4 -

1.3 Installation FlowThe following figure shows the installation task flow.

1. Install the mandatory software.

2. Install the Server function.

3. Install the Sensor function. (If use separated sensor from server)

4. Install the Client function.

Refer to Section "1.1 Installed functions", for details of mandatory products.

Refer to "Chapter 2 Installing", for installation details.

･ Since the sensor is installed at the same time as the Analytics Server, the following installation is not possible:

- Sensor installation to an environment where the Analytics Server is already installed

- Analytics Server installation to an environment where the sensor is already installed

･ Administrator permission is required to perform the installation.

･ The "Admin server functions (multi-server management functions)" cannot operate in an Interstage Application Server environmentthat runs Analytics.

1.4 Notes on SecurityThis product is not designed or manufactured for the purpose of being used to provide services to the Internet. If it is used in environmentsthat do not connect to the Internet (within an intranet), or if it is used by connecting to the Internet, implement appropriate security measuresat the operating environment to prevent security breaches.

The following points must be noted in order to use monitoring safely:

To guarantee the safety of monitoring operations and the content of monitoring settings:

･ This product presumes in-house use. Therefore, positioning the Analytics Server on the Internet or in the DMZ is not recommended.

･ Network administrators must ensure that information is secure and not accessible outside the network where the Analytics Server ispositioned.

- 5 -

Chapter 2 InstallingThis chapter provides information on how to install.

2.1 Tasks Required Before InstallationThis section describes the tasks required before installation.

･ If the terminal service at Windows Server is in application server mode, it must be changed to install mode.

･ The "Admin server functions (multi-server management functions)" cannot be used in an Interstage Application Server environmentthat runs Analytics.

･ Allocation of the Analytics Server and the event database on separate systems has the advantage of enabling server load balancing,but the following points must be noted:

- The Analytics Server does not operate correctly if the database system fails or if the network is disconnected.

- The synchronization of operations between the two systems needs to be considered.

Analytics Server (server function)

Installation and setup of the following products and components must have already been completed:

･ Application Server

- Interstage Application Server

- WebLogic

- JBoss

･ DBMS ( Oracle, SQL Server, or DB2 )

･ JDBC drivers

The Analytics Server uses JDBC connections to the event database and to the target databases.

In order to connect to these databases, JDBC drivers that enable connection to these databases must be installed on the same machineas the Analytics Server. Refer to the manuals of the applicable databases for JDBC driver installation details.

Sensor (sensor function)

Installation and setup of the following products and components must already be completed:

･ Interstage Application Server

･ JDBC drivers

The sensor uses JDBC connections to the event database.

JDBC drivers that enable connection to this database must be installed on the same machine as the sensor. Refer to the manual of theapplicable database for JDBC driver installation details.

Sensor (sensor function: Windows service edition text file sensor)

Installation and setup of the following components must already be completed:

･ JDK 1.4.2

･ JRE 1.4.2

･ JDK 5.0

- 6 -

･ JRE 5.0

JDK or JRE provided by Sun Microsystems must already be installed. Refer to the following website for information concerningobtaining these modules:http://java.sun.com/

Analytics Designer (client function)

Installation and setup of the following products must already be completed:

･ Interstage Studio

･ Interstage BPM Studio (for Workflow events)

Installation and setup of Interstage Studio is required before the Analytics Designer is installed.

･ Interstage Service Integrator - ISI Studio (for ISI events)

2.2 Installation

2.2.1 Analytics Server Installation ( for Windows )

This section describes the procedures for installing the Analytics Server in Windows system.

･ The following services must be running when the Analytics Server is installed:

- Interstage Operation Tool

- INTERSTAGE

Installation parameters

parameters Default Example

Program install directory C:¥ibpmm C:¥ibpmm

Data directory C:¥ibpmm_data C:¥ibpmm_data

Procedures of Installation

1. Login, with administrator authority, to the server where the Analytics Server is to be installed.

2. Insert the "Interstage BPM Analytics 10.0" CD-ROM in the CD-ROM drive.

- 7 -

3. Click [Install] on the following screen, which is automatically displayed.

4. On the [Select installation type] screen, select "Install Server components", then click the [Next] button.

->If "Server comp" is selected on the [Select of server components] screen, the FJapache service start or restart confirmation screen

- 8 -

is displayed. If you want to continue, click the [Yes] button.

5. In the [Choose destination Location] screen, specify the folder where Analytics is to be installed, then click the [Next] button.

6. If "Server comp" is selected on the [Select on server components] screen, the [Specify Workspace directory] screen is displayed.Enter the "Workspace directory path", then click the [Next] button. The workspace directory is the directory used for temporarystorage of events collected by the sensor and for storage of settings information. It is not a database.

- 9 -

The specified directory is newly created. An existing directory cannot be specified.

7. Check the settings displayed on the [Start Copying Files] screen and, if these settings are correct, click the [Install] button.

8. The installation will be completed.

2.2.2 Analytics Server Installation ( for Linux )

This section describes the procedures for installing the Analytics Server in Linux system.

- 10 -



Server FQDN or IP address (host name) Host1

JBoss AJP port 8009 8009

Analytics server port 40330 40330

JBoss installation directory /opt/jboss /opt/jboss


1. Login the system as root.

2. Set CD-ROM on the system.

3. Move to following directory.# cd /media/IBPM_ANALYTICS/

4. Execute installation script.# /bin/sh install.sh

5. According to the parameter confirmation messages, execute installation.

2.2.3 Analytics Server Installation ( for Solaris )

This section describes the procedures for installing the Analytics Server in Solaris system.



Program install directory /opt /opt

Data directory /var/opt /var/opt

Server FQDN or IP address (host name) Host1

WebLogic server port 7001 7001

Analytics server port 40330 40330


1. Login Solaris system as root.

2. Set CD-ROM on Solaris system.

3. Move to following directory.# cd /cdrom/ibpm_analytics

4. Execute installation script.# install.sh

5. According to the parameter confirmation messages, execute installation.

Procedures of Deployment to WebLogic

1. Start WebLogic server.

2. Start Server Instance on which Analytics Server will be deployed.

3. Deploy “ibpmm Web Application” to WebLogic Server Instance.

- 11 -

1. Login to “WebLogic Admin Server Console”. http://host1:7001/console/

2. Select “Deployments” from “WebLogic Admin Server Console”.

3. Select “lock & Edit”and push “Install” from “Deployments”.

4. Select Location “/var/opt/FJSVibpma/ibpmm.war” and go Next.

5. Select “Install this deployment as an application” and go Next.

6. Check that the Name is “ibpmm” and push “finish”

7. Push “Activate Changes”.

8. Check on “ibpmm” from “Deployments”, and Select “Serving all requests” from “start”.

4. ”BPM Analytics Servlet” will be started.

Don’t change servlet context name “ibpmm”.

2.2.4 Client InstallationThis section describes the client installation procedures.

･ To link up with Interstage BPM, please install Analytics Designer on Interstage BPM Studio.




Plug-in directory C:¥Interstage¥APW¥eclipce C:¥Interstage¥APW¥eclipce


1. Login, with administrator authority, to the server where the Analytics Designer is to be installed.


- 12 -


4. On the [Select installation type] screen, select "Install Client components", then click the [Next] button.

- 13 -

5. On the [Choose Destination Location] screen, specify the install folder, then click the [Next] button.

6. If "Client component" is selected on the [Select of client components] screen, the [Specify Analytics Designer Plug-in Location]screen is displayed. Specify the "Studio plug-in directory path", then click the [Next] button.

To link up with Interstage BPM, please input the folder of Interstage BPM Studio.Exp) C:¥Fujitsu¥InterstageBPM_studio¥bin

- 14 -

7. Check the settings displayed on the [Start Maintenance] screen and, if the settings are correct, click the [Continue] button.


2.2.5 Sensor InstallationThis section describes the sensor installation procedures. Install the sensor if you want the sensor to operate on a separate machine fromthe Analytics Server.

･ Before starting sensor installation, check that installation of the Analytics Server has been completed. The sensor communicates withthe Analytics Server to collect information. Therefore, installation of the Analytics Server must be completed before the sensor isinstalled, and the Analytics Server must already be started.

･ The following services must already be started when the sensor is installed:

- Interstage Operation Tool

- INTERSTAGE

There are two types of text file sensors: a text file sensor that runs as a Web application, and a text file sensor that runs as a Windowsservice (the Windows service edition text file sensor). The Windows service edition text file sensor can be used to collect monitoring datafrom machines where Interstage Application Server is not installed. If Interstage Application Server is not installed, the screen switchesto the install screen for the Windows service edition text file sensor.




- 15 -


Data directory C:¥ibpmm_data C:¥ibpmm_data

Monitoring Server address (host name) Host1

Monitoring Server port(Web server)

80 80


1. Login, with Administrator authority, to the server on which the sensor is to be installed.



If the screen is not displayed, double-click the autorun.exe icon in the CD-ROM folder.

- 16 -

4. On the [Select installation type] screen, select "Install Sensor components", then click the [Next] button.

->If Interstage Application Server is not installed on the machine, a confirmation screen that asks if you want to install the Windowsservice edition text file sensor is displayed. To continue, click [Yes].

->The confirmation screen for installing the sensor component is displayed. To continue, click [Yes].

5. On the [Choose Destination Location] screen, specify the installation folder, then click the [Next] button. Under the standard settings,the sensor is installed in the following folder:

- 17 -

[operating system install drive]¥ibpmm

6. Enter the "Workspace directory path". The workspace directory is the directory used for temporary storage of events collected bythe sensor and for storage of settings information. It is not a database.The specified directory is newly created. An existing directory cannot be specified.

- 18 -

7. On the "Analytics Server setting" screen, enter the "Analytics Server hostname or IP address" and the "Web server port No. of theAnalytics Server", then click the [Next] button.

8. Check the settings displayed on the [Start Copying Files] screen and, if the settings are correct, click the [Install] button.


- 19 -

If the Analytics Server hostname or IP address of an incorrect connection destination, or an incorrect Web server port number, wasaccidentally specified and installation has been completed, the bpmupdatesensorconf command can be used to change the setting. Referto the Command Reference manual for details of how to use the bpmupdatesensorconf command.

2.3 Post-Installation TasksThis section describes the tasks to be performed after installation.

2.3.1 Security Provided by Folder Access RestrictionsFor security purposes, take the following measures at the Interstage Application Server install folder and the product install folder.

Security Measures at the Interstage Application Server Install Folder

It is recommended that the access permission be changed such that unauthorized users are not permitted to access the folders and filesunder the Interstage Application Server install folder.

Refer to "Common Measures" in the "Interstage Application Server Security System Operator's Guide" for details.

The Interstage Application Server issetfoldersecurity command can be used to change the access permission. Refer to "issetfoldersecurity"in the "Interstage Application Server Reference Manual (Commands)" for details of this command.

Security Measures at the Install Folder

If the access permission needs to be changed for the folders and files under the install folder, it is recommended that permission is changedby using Windows functions.

The following screen shows the security status of the install folder when referenced from Properties under Windows Explorer. Takemeasures such as deleting "Everyone" and assigning access permission to only specified users.

- 20 -

2.3.2 Changing the Management Console PasswordFor security purposes, it is recommended that you change the management console password from its initial value. Refer to the "Management Reference" for information on how to change the password.

2.4 Adding and Deleting FunctionsThis section describes how to add and delete functions.

1. Log in, with administrator authority, to the machine to which functions are to be added or deleted.

2. If functions are to be added, insert the "Interstage BPM Analytics 10.0" CD-ROM in the CD-ROM drive.

3. In the Control Panel, double-click "Add or Remove Programs".

4. From the list of currently installed software, select the program shown below, then click the [Change] button:

- Interstage BPM Analytics

When the [Change] button is clicked, functions can be added and deleted.To delete the product itself, click the [Remove] button.

1. Select the checkboxes of the functions you want to add and deselect the checkboxes of the functions you want to delete, then clickthe [Next] button.

･ Since the sensor is included in the Analytics Server, the two components cannot be installed on the same machine. Thus, if the AnalyticsServer is installed, the sensor is not displayed, and if the sensor is installed, the Analytics Server is not displayed.

･ If no changes are made on the function addition and deletion screen, the [Next] button is disabled.

- 21 -

->If a function is to be installed, the input screens and dialog screens that are required for installation are displayed. Refer toSection "2.2.1 Analytics Server Installation ( for Windows )", Section "2.2.4 Client Installation", Section "2.2.5 SensorInstallation" for details of the input screens and confirmation dialogs required for each function.

->If the Analytics Server is being uninstalled and the FJapache service is currently in the "started" state, the following screen isdisplayed.

1. If you want to continue, click the [Yes] button.

2. Check the settings displayed on the [Start Maintenance] screen and, if the settings are correct, click the [Continue] button.

->If a function is being uninstalled, a confirmation dialog is displayed.

->If the Analytics Server or a sensor is being uninstalled, the following screen is displayed.

- 22 -

If you want to continue, click the [Yes] button on these screens.

3. This completes the function addition and deletion.

- 23 -

Chapter 3 Uninstalling AnalyticsThis chapter describes how to uninstall Analytics.

3.1 Tasks Required Before UninstallingThis section describes the tasks to be performed before Analytics is uninstalled.

To retain existing monitoring environment resources, refer to the applicable "Operator's Guide" and execute backup tasks beforeuninstalling Analytics.

Do not uninstall Interstage Application Server before Interstage BPM Analytics is uninstalled. The following services must be in the startedstate.

･ Interstage Operation Tool

･ INTERSTAGE

3.2 UninstallingUse the following procedures to uninstall Interstage BPM Analytics:

( for Windows )

1. Login with administrator authority to the machine where you will be performing the uninstall.

2. In the Control Panel, double-click [Add or remove programs].

3. From the list of currently installed software, select the following program, then click the [Remove] button.

- Interstage BPM Analytics

4. According to the confirmation dialog screen, execute uninstallation.

( for Linux )



3. Move to following directory.# cd /media/IBPM_ANALYTICS/

4. Execute uninstallation script.# bin/sh uninstall.sh

5. According to the confirmation messages, execute uninstallation.

( for Solaris )

1. Delete “ibpmm Web Application” on WebLogic server.

1. Login to “WebLogic Admin Server Console”. http://host1:7001/console/

2. Select “Deployments” from “WebLogic Admin Server Console”.

3. Check on “ibpmm” from “Deployments”, and Select “When work completes” from “stop”. ->”BPM Analytics Servlet” will be stopped as “Prepared”.

4. Select “lock & Edit”and Check on “ibpmm” from “Deployments”. And push “Delete”.

- 24 -

5. Select “yes”on “Delete Application Assistant”.

6. Push “Activate Changes” for completion.



4. Move to following directory.# cd /cdrom/ibpm_analytics

5. Execute uninstallation script.# uninstall.sh

6. According to the confirmation messages, execute uninstallation.

To delete only the sensor:

If you want uninstall a sensor that is installed on a different machine to the Analytics Server, perform the above uninstall procedures, thenuse the Analytics Designer to delete the applicable sensor controller. Note that it is not possible to delete only the sensor if the sensor isinstalled on the same machine as the Analytics Server.

3.3 Tasks Required after UninstallingThis section describes the tasks required after Analytics is uninstalled.

3.3.1 Deleting the Analytics Server DatabasesDelete the following databases after the Analytics Server has been uninstalled:

･ Event database

･ Analysis database

Deleting the Event Database

Delete each of the areas prepared when the event database was constructed. Perform the deletion task procedures described in the applicabledatabase manual.

Database product Special-purpose areas prepared

Oracle Table space (table area)

SQL Server Database

DB2 Table space

･ Under Oracle, check whether or not the table space used is also used by other users as the default table area. If a table space that isused as a default table area by another user is deleted, an error will occur when that user creates a table.

･ If the event database was not created in a special-purpose area when it was constructed, the above areas cannot be deleted. In this case,if you want to delete data, each of the tables generated by operations must be deleted individually.

Deleting the Analysis Database

Delete the areas prepared as special-purpose areas in the same way as for deletion of the event database .

- 25 -

If the analysis database was not created in a special-purpose area when it was constructed, the above areas cannot be deleted. If required,delete each of the tables generated by operations individually.

3.3.2 Stopping and Deleting the WorkUnit for the IJob Execution ServletIf escalation was being used for the Analytics Server , from the server where IJob is operating delete the WorkUnit operated by the servlet.Perform the deletion using the following war filename:

･ BPMIJobExecuteServlet

Refer to the Application Server Operator's Guide for information on how to stop and delete WorkUnits.

- 26 -

Appendix A Required ResourcesThis appendix describes the resources required and how to estimate these resources.

A.1 Disk Space Required at InstallationThe following table shows the free space required at the time of installation.

Functions being installed Free space required for installation

Server function 105MB

Client function 45MB

Sensor function 15MB

Windows service edition text file sensor 10MB

A.2 Save Area for Monitoring Settings DataThe following table shows the amount of free space required as a save area for the monitoring settings data managed by the AnalyticsServer.

Save area for monitoring settings data Required free space

On the Analytics Server 10MB

A.3 Work AreasThis section describes how to estimate the work areas specified during installation of the Analytics Server and the sensor.

A.3.1 Overview of Work AreasThe work areas are for the temporary storage of events collected by the sensor and for holding settings information. They are not databases.

When the sensor transfers events to the Analytics Server, it transfers multiple events together. This reduces processing costs between thesensor and the Analytics Server, thereby improving performance. To achieve this, the sensor collects events, and transfers them at fixedintervals. This interval is called the "Event transfer interval", and is set from the monitor designer.

The server side receives event notifications from the sensor and stores them in the event database. Event database storage is asynchronousto reception of the event notification from the sensor. Therefore, after the notification, events are written to the work area as pooled eventsuntil they are able to be stored in the event database. When the processing to store the events in the event database is attempted, the eventsare then deleted. If the processing to store the pooled events in the event database fails, the events may be output to the work area as error files, where theyremain until they are successfully reregistered manually.

- 27 -

Work area sizes

The sections below explain the work area sizes.

･ If the Analytics Server and the sensor run on the same machine:

Allocate the work area size to be the total size of the estimates for the "sensor work area" and the "server work area" .

･ If the Analytics Server and the sensor run on separate machines:

Allocate the "sensor work area" estimated size as the work area on the machine where the sensor is installed. Allocate the "server work area" estimated size as the work area on the machine where the Analytics Server is installed.

A.3.2 Estimating the Sensor Work AreaUse the following formula to calculate the size of the work area.

Required area size = Total of the work area sizes required for one event transfer interval from each sensor

Work area size required for one event transfer interval

Use the following formula to calculate the work area size required for one event transfer interval.

Work area size required for one event transfer interval =average number of events * event transfer interval * average event size * 1.5

1.5: Safety coefficient (since collection is also performed during transfer, a value with a margin for error must be estimated.)

Average number of events

This is the average number of events collected by the sensor in one minute. This value is used as the "average number of events collectedfor the task per minute".Use the following formula to calculate the average number of events collected for the task per minute.

Average number of events collected for the task per minute = number of events collected from one execution /execution interval (minutes)

Event transfer interval

This is the interval at which pooled events are transferred from the sensor to the Analytics Server. The event transfer interval is set separatelyfor each sensor from the Analytics Designer. The unit is "minutes".

- 28 -

Average event size

This is the area used by one pooled event.The data type of attributes must be taken into account when calculating the average event size.

The following table shows the attribute length for each data type.

Data type Attribute length (bytes) (data length + appended information)

Character string Length of character string data in UTF-8 encoding + 50

Integer Depends on the number of digits in the value + 50

Real number Depends on the value + 50

Boolean 50

Date and time 80

Date 60

Time 60

Example of calculating the required area size

An example of calculating the required area size is shown below.

Average event size

Use the following formula to calculate the average event size

Average event size = Task name (*1) + event name (*1) + total of average attribute length of each attribute + 270 (bytes)

*1：Length in UTF-8 encoding

This example assumes the following attributes:

Attribute Length

Task name 36 bytes

Event name 36 bytes

Average attribute length of character string typeattribute A

150 bytes

Average attribute length of character string typeattribute B

200 bytes

Average attribute length of character string typeattribute C

250 bytes

Average attribute length of integer type attribute D 60 bytes

Average attribute length of integer type attribute E 60 bytes

Average attribute length of date and time type attributeF

60 bytes

Attribute name length Uniformly 30 bytes

The formula is as follows:

Average event size = Task name (36) ＋ event name (36) ＋ total of each attribute length (attribute name length (30) * 6 + 780) + 270= 1302 bytes ≒ 1.31 Kbyte

- 29 -

Average number of events

The average number of events that the sensor collects each minute is the total of the average number of events collected for the task eachminute. In this example, the following tasks are set for Sensor A:

Task Execution schedule Average number ofitems collected

Average number ofevents collected per

minute

Task A Collected at 2 minuteintervals

Average of 100 itemscollected each time

50 events

Task B Collected at 5 minuteintervals


10 events

Task C Collected at 4 minuteintervals


30 events

The average number of events that the sensor collects each minute is as follows:

Average number of events = 50 + 10 + 30= 90 (events)

Work area size required for one event transfer interval

The following table shows the requirements for various transfer intervals.

Event transferinterval

Formula Required work areasize

2 minutes Average number of events (90) * transfer interval (2) * average size(1.31) * safety coefficient (1.5) = 353.7

About 354 (Kbytes)

5 minutes Average number of events (90) * transfer interval (5) * average size(1.31) * safety coefficient (1.5) = 884.35

About 885 (Kbytes)

60 minutes Average number of events (90) * transfer interval (60) * average size(1.31) * safety coefficient (1.5) = 10611

About 10.4 (Mbytes)

8 hours Average number of events (90) * transfer interval (860) * average size(1.31) * safety coefficient (1.5) = 84888

About 82.9 (Mbytes)

24 hours Average number of events (90) * transfer interval (24 * 60) * averagesize (1.31) * safety coefficient (1.5) = 254664

About 248.7 (M bytes)

Example of calculation assuming operation when communication with the server is not possible

In the above example, it is assumed that server operations are stopped for one hour for maintenance, from 2 am to 3 amIn this case, the area used by sensor A (event transfer interval: 2 minutes) for pooled events at night is as follows:

Size of required work area (354 Kbyte) * server stopped duration (1 * 60)= 21240 (Kbyte) = approx 2.1 (Mbyte)

If the Analytics Server is stopped for a long time, also stop the sensor. If only the sensor is running, events are pooled in the work areadirectory and an area shortage may occur.

- 30 -

A.3.3 Estimating the Server Work AreaEvent notifications from the sensor are implemented in accordance with the event transfer interval of each sensor. Therefore, use thefollowing formula to calculate the size for the work area.

Required area size = sum of maximum event capacity * safety coefficient

Maximum event capacity

The maximum event capacity indicates the maximum case of "number of events notified * average event size". This value can be calculatedby adding together the value for each sensor.

Safety coefficient

The safety coefficient takes into account the possibility of subsequent events being notified before all the previously notified events arestored. Therefore, a safety coefficient value of 2 or more is recommended

Example of calculating the required area size

The required work area size can be calculated by multiplying the total amount of space used for events at each of the sensors by the safetycoefficient. Refer to Section A.3.2, "A.3.2 Estimating the Sensor Work Area", for the formula to calculate the amount of space used forevents at the sensor.

If the maximum event capacity of each sensor is 2.1 Mbyte, during the assumed night stopped time, and if there are 4 sensors, the requiredarea size is as follows:

Required area size = Total of maximum event capacity for events notified by each sensor (2.1 Mbyte * 4) * safety coefficient (2)= 16.8 (Mbyte) = approx17 (Mbyte)

Example of calculating an estimate if an error is assumed

An example of calculating an estimate when the following types of error are assumed is described below:

･ Data value error (for example, the maximum length of a character string in a database column is exceeded, or similar)

･ Event definition does not exist (was deleted, different event name was notified, etc.)

Normally, these cases do not occur, but if an "Event definition does not exist" error does occur, pooled events continue to accumulate untilthe task is ended in order to resolve the error. It is recommended that you prepare an amount of free space that takes into account theamount of time until the task is ended to resolve the error.

If the definition was accidentally deleted for an event collected by a sensor, and if the error continues for one day, the following area isrequired:

Required area size = Work area size required for one event transfer interval (354 Kbyte) * duration of error (24 * 60)/event transfer interval (2)＝ 254880 (Kbyte) = approx 249 (Mbyte)

- 31 -

Appendix B Requried disk size for databaseAppendixA explains the disk size which is required to manage the database of Interstage BPM Analytics.

When you want to know a required size for database raoghly, refer 'B.1'. And you want to clarify the required size of database, refer 'B.2'.

B.1 sammry of disk size (It is common in all data bases)This paragraph indicates required size for database in the case of the following business environment.

example

Target systems Database(2 tables) + Workflow(10 flows)

Alert rules 10 rules

Statistic rules 10 rules

Data incidence 100 events a day

Data maintenanceperiod

3 years

Required disk size : 10 - 50GB

B.2 Database size necessary for each operation pattern.( It iscommon in all data bases)

This paragraph indicates size necessary for each operation pattern.

B.2.1 pattern1 : monitoring of the small scale database

Target systems Database ( 1 table )

Data incidence 1000 events a day

Data maintenance period 1 year


Statistic rules 1 rule

Frequency of execution a statistic rule one time a day

Number of sections 3

Number of commodities 100

Average number of attributes 5

[monitoring policy]

Delete from analyze database when one year passes.

Data maintenance period of statistics event is one year.

Required disk size : 5 - 6GB (If the data maintenance period is 3 year ｓ: 5 - 8GB)

B.2.2 attern2 : monitoring of the large scale database

Target systems Target systems

Data incidence Data incidence

- 32 -

Data maintenance period Data maintenance period

Alert rules Alert rules

Statistic rules Statistic rules

Frequency of execution a statistic rule Frequency of execution a statisticrule

Number of sections Number of sections

Number of commodity division * Number of commodity division *

Average number of attributes Average number of attributes

[monitoring policy]

Delete from analyze database when half a year passes.

Data maintenance period of statistics event is 3 years.


Required disk size(when * is 1000) : 40 - 50GB

Required disk size(when * is 10000) : 150 - 200GB

B.2.3 attern3 : monitoring of the small scale workflow system

Target systems workflow ( 2 flows )

Number of process 100 a day


1 year


Number of activitys 10

Average number ofattributes

5

[monitoring policy]

Data maintenance period of statistics event is one year.

Required disk size : 5 - 6GB (If the data maintenance period is 3 year ｓ : 5 - 8GB)

B.2.4 attern3 : monitoring of the large scale workflow system

Target systems workflow ( 10 flows )

Number of process 10,000 a day


3 year


Number of activitys 20

Number ofapplications

2

Average number ofattributes

20

[monitoring policy]

Data maintenance period of statistics event is 3 year.

- 33 -


- 34 -

Documents

Business Process Manager Analytics 10software.fujitsu.com/jp/manual/manualfiles/M080185/... · Related software Interstage Business Process Manager 10 Interstage Interaction Manager