Interstage Business Process Manager Analytics V11.0. Administration Guide. Windows/Solaris/Linux

Transcription

1 Interstage Business Process Manager Analytics V11.0 Administration Guide Windows/Solaris/Linux J2U (00) December 2009

2 About this Manual This document describes the maintenance issues and techniques for the Analytics Server. Intended Audience This manual is intended for use by the system administrator. It assumes that the reader has a working knowledge of the following topics: Operating system administration Application server administration Database administration This Manual Contains: Chapter Title 1 Maintaining General maintanance for the Interstage BPM Analytics Server and Events database. 2 Messages Overview Overview of the messages that may be generated during Interstage BPM Analytics operations. 3 Troubleshooting How to deal with commonly encountered problems when they occur. A Application Log Messages Log messages that are output to application logs. B Analytics Server Messages Log messages that are output by the Analytics Server. Typographical Conventions The following conventions are used throughout this manual: command screen text Reference Parameter Example Meaning Text, which you are required to type at a command line, is identified by Courier font. Text, which is visible in the user interface, is bold. Reference material is in italics. A command parameter is identified by Courier font. Reference Materials The following reference materials for Interstage BPM Analytics are also available: Release Notes Contains an overview of Interstage BPM Analytics, and late-breaking information that could not make it into the manuals. Overview Describes the Interstage BPM Analytics Architecture and features. Installation Guide Explains how to install Interstage BPM Analytics. Dashboard / Output Guide Explains how to use the Dashboard to display Analytical data. Analytics Studio Guide Explains how to use the Analytics Studio to configure the parameters to enable Interstage BPM Analytics' features. - i -

3 Management Console Guide Explains how to use the Management Console and the Management Commands to configure the core parameters, how to start/stop the Interstage BPM Analytics service and how to display the Interstage BPM Analytics status. Abbreviations The following references for BPM Analytics are also available: Formal name Microsoft(R) Windows Server(TM) 2003, Standard Edition Microsoft(R) Windows Server(TM) 2003, Enterprise Edition Microsoft(R) Windows Server(TM) 2003 R2, Standard Edition Microsoft(R) Windows Server(TM) 2003 R2, Enterprise Edition Microsoft(R) Windows Server(TM) 2003, Standard x64 Edition Microsoft(R) Windows Server(TM) 2003, Enterprise x64 Edition Microsoft(R) Windows Server(TM) 2003 R2, Standard x64 Edition Microsoft(R) Windows Server(TM) 2003 R2, Enterprise x64 Edition Microsoft(R) Windows Server(R) 2008, Standard Edition Microsoft(R) Windows Server(R) 2008, Enterprise Edition Microsoft(R) Windows Server(R) 2008 R2 Standard Microsoft(R) Windows Server(R) 2008 R2 Enterprise Microsoft(R) Windows(R) XP Professional operating system Microsoft(R) Windows(R) XP Home Edition operating system Microsoft(R) Windows Vista(R) Business Microsoft(R) Windows Vista(R) Enterprise Microsoft(R) Windows Vista(R) Ultimate Microsoft(R) Windows(R) 7 Home Premium Microsoft(R) Windows(R) 7 Professional Microsoft(R) Windows(R) 7 Ultimate Microsoft(R) Internet Information Server Microsoft(R) Internet Information Services Microsoft(R) Internet Explorer 6.0 Microsoft(R) Internet Explorer 7.0 Microsoft(R) Internet Explorer 8.0 Microsoft(R) Excel Solaris(TM) 10 operating system Red Hat Enterprise Linux AS Red Hat Enterprise Linux ES Red Hat Enterprise Linux 5 Interstage Application Server Enterprise Edition Interstage Application Server Standard-J Edition Interstage Studio Enterprise Edition Interstage Studio Standard-J Edition Interstage Business Process Manager Oracle Database 10g Enterprise Edition R10.1.0/R Oracle Database 10g Standard Edition R10.1.0/R Oracle Database 10g Standard Edition One R10.1.0/R Oracle Database 11g Enterprise Edition Oracle Database 11g Standard Edition Oracle Database 11g Standard Edition One Windows Server Abbreviation Windows Server 2003( x64), or Windows Server 2003 Windows Server Windows XP, or Windows Windows Vista, or Windows Windows 7, or Windows IIS Internet Explorer Excel Solaris 10, or Solaris Linux Interstage Application Server Interstage Studio, or Studio IBPM Oracle10g, or Oracle Oracle11g, or Oracle - ii -

4 Formal name Oracle Database 11g R2 Enterprise Edition Oracle Database 11g R2 Standard Edition Oracle Database 11g R2 Standard Edition One Microsoft SQL Server 2005 Standard Edition Microsoft SQL Server 2005 Enterprise Edition Microsoft SQL Server 2008 Standard Edition Microsoft SQL Server 2008 Enterprise Edition Abbreviation SQL Server 2005, or SQL Server SQL Server 2008, or SQL Server Export regulations Fujitsu documents may include special technology regulated by foreign exchange and foreign trade regulation laws. If special technology is 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 and other countries. Sun, Sun Microsystems, the Sun Logo, Solaris and all Solaris based marks and logos are trademarks or registered trademarks of Sun Microsystems, 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 States and other countries. Oracle is a registered trademark of Oracle Corporation (USA). SQL Server is a Microsoft Corporation (USA) product. "DB2" is a registered trademark of IBM Corporation (USA). All other company and product names referred to in this document are general trademarks or registered trademarks of their respective owners. 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 this document. Copyright Copyright 2009 FUJITSU LIMITED December 2009 First Edition - iii -

5 Contents Chapter 1 Maintaining Backing Up the Interstage BPM Analytics Server environment Stopping Related Systems Backing up the Environment Backing up the Events Database Example Using the Oracle Export Utility Restart Related Systems Restoring the Interstage BPM Analytics Server Environment Installing the Interstage BPM Analytics, Sensors and Related Products Stopping Related Systems Restoring the Environment Restoring the Events Databases Example Using the Oracle Import Utility Restarting Related Systems Updating the Settings Migrating the Events database Procedure for Migrating the Events Database Procedure for Migrating the Archive database...12 Chapter 2 Messages Overview Message Output Format Message Output Destinations Message Format...15 Chapter 3 Troubleshooting Installation Problems Problems with the Analytics Server Problems with Sensors Problems with IBPM Analytics Studio Event Collection Problems Problems with the Management Console Problems Calculating Statistical data Problems with Dashboard Problems Displaying Alerts Chart Display Problems...22 Appendix A Application Log Messages...24 A.1 Application Log Messages (BOPExxxx)...24 A.2 Dashboard Messages (BDSHxxxx, BDAVxxxx)...28 A.3 Management Command Messages (BADCxxxx, BALTxxxx, and BMSGxxxx)...31 A.4 Management Console Messages (BADMxxxx)...43 Appendix B Analytics Server Messages...62 B.1 Analytics Server Messages (BEFAxxxx, BPSHxxxx, BEGNxxxx, BTSKxxxx, BSRCxxxx, BECSxxxx, BWIFxxxx, BDBAxxxx, BLTCxxxx, BESTxxxx, BDMSxxxx, BADCxxxx, BALTxxxx)...62 B.2 Sensor Messages (BFLSxxxx, BISSxxxx, BRDBxxxx, BSDKxxxx, and BTXSxxxx) iv -

6 Chapter 1 Maintaining This chapter provides information on how to maintain the Interstage BPM Analytics Server and Events database. 1.1 Backing Up the Interstage BPM Analytics Server environment As there is always the possibility of faults occurring with the system or the hardware, it is recommended that periodic backups be performed. It is also recommended that backups be performed before modifications are made to the Analytics environment, in case problems occur during the modification process. Interstage BPM Analytics environments that have been backed-up can only be restored to environments with the same system configuration as the original environment, including the same database product for the Event database and the same Remote sensor arrangement. The following resources are backed up: At the Analytics Server - Analytics Server configuration files - Events database - Archive database (if available) - Working directory At the Remote Sensor - Configuration files - Working directory Note If resources are backed-up individually (that is, only Server resources, only Remote Sensor resources or only Events database), then the data may become inconsistent when the resources are restored, preventing the recovered system from operating normally. Be sure to back up all resources while all Remote Sensors and the Server are stopped. It is recommended that the backup data be stored on a separate data storage medium in case hardware problems occur. In addition, it is recommended to maintain a series of previously backed-up data collections. The following procedure is describes the steps to back up each resource: Procedure for Backing up Analytics Server Resources The procedure for backing up Analytics Server resources is as follows. 1. Stop any related systems. 2. Back up the environment. a. Create backup directories. b. Back up the Analytics Server configuration files. c. Back up the working directory. 3. Back up Events database. 4. Restart the related systems

7 Procedure for Backing up Remote Sensor Resources Remote Sensors also have configuration files on the machines that they run on. The procedure for backing up Remote Sensor resources is as follows: 1. Stop any related systems. 2. Back up the environment. a. Create backup directories. b. Back up the Remote Sensor configuration files. c. Back up the working directory. 3. Restart the related systems. Procedure for Backing up Text Sensor Resources which on the Remote system Text Sensors which are running on remote systems as Windows Service program have other configuration files. The procedure for backing up resources is as follows: 1. Stop related systems. 2. Back up the environment. a. Create backup directories. b. Back up the Text sensor configuration files. c. Back up the working directory. 3. Restart related systems Stopping Related Systems Analytics Server Execute the following procedures on the host machine of the Analytics Server: [for Interstage] Stop the IBPMMServer Work Unit from the Interstage Management Console. [for Weblogic] Run the shutdown script located in <BEA Home>/user_projects/domains/<Domain Name>/bin: - On Windows Administration Server: stopweblogic.cmd Managed Server: stopmanagedweblogic.cmd <Server Name> - On Solaris/Linux Administration Server: stopweblogic.sh Managed Server: stopmanagedweblogic.sh <Server Name> [for WebSphere] Run the shutdown script located in <WebSphere Installation Directory>/AppServer/bin: - On Windows stopserver.bat <Server Name> - On Solaris/Linux stopserver.sh <Server Name> - 2 -

8 [for JBoss] Run the shutdown script located in <JBoss Home>/bin: - On Windows: shutdown.bat -S - On Solaris/Linux shutdown.sh -S Background Service program Execute the following procedures on the host machine of the Analytics Server: [On Windows] Stop the "Interstage BPM Analytics erule Engine" service using the Services window. [On Solaris/Linux] Execute the following command: /opt/fjsvibpma/etc/fjsvibpma.server stop Remote Sensor Execute the following procedures on the host machine which runs the Remote Sensor: 1. Stopping Work Units Stop the IBPMMServer Work Unit from the Interstage Management Console. 2. Stopping Services Stop the Interstage BPM Analytics Text File Sensor service using the Services window Backing up the Environment Create Backup Directories Create a separate directory for backing up the following files: Files to be backed up Analytics Server configuration files Remote Sensor configuration files Text Sensor configuration files Working files Examples of how to create these directories mkdir C:/BPMBackup mkdir C:/BPMBackup/conf mkdir C:/BPMBackup/agent mkdir C:/BPMSBackup mkdir C:/BPMSBackup/conf mkdir C:/BPMSBackup/agent mkdir C:/BPMTBackup mkdir C:/BPMTBackup/conf mkdir C:/BPMTBackup/agent mkdir C:/BPMBackup/ibpmm_data Backing up the IBPM Analytics Server configuration files Use commands or Windows Explorer to copy the settings files. Copy source All of the files and directories under the following directories: - [Web application deployment directory]/ibpmm.war/conf - 3 -

9 - [Web application deployment directory]/ibpmm.war/agent - E.g. Interstage for Windows C:/Interstage/J2EE/var/deployment/ijserver/IBPMMServer/apps/ibpmm.war/ - E.g. WebLogic for Solaris no stage mode: /var/opt/fjsvibpma/ibpmm/ stage mode: <WebLogic domain dir>/servers/<server_name>/stage/ibpmm/ibpmm/ - E.g. WebShpere for Linux <WebSphere_Installation_Directory>/AppServer/profiles/<profile_name>/installedApps/<WebShpere_Cell_Name>/ ibpmm_war.ear/ibpmm.war/ - E.g. JBoss for Linux <JBoss_Home>/server/default/ibpmm.war/ Copy destination The directory for backing up the working directory that was created in Create Backup Directories. The following example uses the copy command: xcopy %IS_J2EEAPF%/ijserver/IBPMMServer/apps/ibpmm.war/conf C:/BPMBackup/conf / E /K /O /X xcopy %IS_J2EEAPF%/ijserver/IBPMMServer/apps/ibpmm.war/agent C:/BPMBackup/ agent /E /K /O /X Backing up the Remote Sensor configuration files Use commands or Windows Explorer to copy the settings files. Copy source All of the files and directories under the following directories: - [Web application deployment directory]/ibpms.war/conf - [Web application deployment directory]/ibpms.war/agent - E.g. Interstage for Windows C:/Interstage/J2EE/var/deployment/ijserver/IBPMMSensor/apps/ibpms.war/ Copy destination The directory for backing up the working directory that was created in Create Backup Directories. The following example uses the copy command: xcopy %IS_J2EEAPF%/ijserver/IBPMMSensor/apps/ibpms.war/conf C:/BPMSBackup/conf / E /K /O /X xcopy %IS_J2EEAPF%/ijserver/IBPMMSensor/apps/ibpms.war/agent C:/BPMSBackup/ agent /E /K /O /X Backing up Text Sensor Configuration Back up the settings for Windows Service version text file sensors. Use commands or Windows Explorer to copy settings files and business models. Copy source: All of the files and directories under the following directories - [text file sensor installation directory]/bpmm/conf - [text file sensor installation directory]/bpmm/agent - 4 -

10 Copy destination: The directory for backing up the working directory that was created in Create Backup Directories The following example uses the copy command. xcopy [text file sensor installation directory]/bpmm/conf C:/BPMTBackup/bpmm/ conf /E /K /O /X xcopy [text file sensor installation directory]/bpmm/agent C:/BPMTBackup/bpmm/ agent /E /K /O /X Backing up the Working Directory Use a command or Windows Explorer to copy the working directory. Copy source All of the files and directories in the working directory (The working directory that was specified when Interstage BPM Analytics was installed) - e.g. for Windows C:/ibpmm_data - e.g. for Solaris/Linux /var/opt/fjsvibpma/data /var/opt/fjsvibpma/efs /var/opt/fjsvibpma/event Copy destination The directory for backing up settings files that was created in Create Backup Directories (C:/BPMBackup/ibpmm_data) The following example uses the copy command: xcopy C:/ibpmm_data C:/BPMBackup/ibpmm_data /E /K /O /X Backing up the Events Database These operations are required only for the Analytics Server. The following databases are backed up: Events database Archive database (if it is being used) This section explains how to back up these databases, using Oracle as an example. To back up other types of database, back up the target resources by referring to the manuals for the type of database management system being used. There are three ways of backing up Oracle data: Use the Oracle Export utility Use the Oracle Recovery Manager Use the operating system's utilities Refer to the Oracle manuals for details on each of these backup methods Example Using the Oracle Export Utility This example explains how to back up databases using the Oracle Export utility, which is often used for migrating data. There is more than one way of backing up databases using the Oracle Export utility, such as backing up entire tablespaces (using the tablespace specification method) or backing up individual tables (using the table specification method). Use the method most appropriate - 5 -

11 to the environment. For example, if a tablespace contains data that is not related to the Interstage BPM Analytics, use the table specification method. To use the Oracle Export utility, execute the EXP command as a user with database administrator privileges. Example Format of the Database Backup Command (Tablespace Specification Method) For the underlined sections, enter the items appropriate to the environment being backed up: exp user name/password@database name BUFFER=data buffer size TABLESPACES=(tablespace to be backed up) GRANTS=y (*1) FILE=path to the backup file LOG=path to the log file *1: Specifying GRANTS=y backs up the access permissions to the database. Example for the Database Backup Command (Tablespace Specification Method) This example assumes that the event DB and the Archive DB are stored in different tablespaces. exp 'esuser/password@dbname' BUFFER=4096 TABLESPACES=(EVENTSTORESPACE) GRANTS=y FILE=C:/BPMBackup/es_backup.dmp LOG=C:/BPMBackup/es_backup_exp.log exp 'asuser/password@dbname' BUFFER=4096 TABLESPACES=(ANALYSISSPACE) GRANTS=y FILE=C:/BPMBackup/as_backup.dmp LOG=C:/BPMBackup/as_backup_exp.log Restart Related Systems Remote Sensor Execute the following procedures on the Server which runs the Remote Sensor: 1. Starting Work Units Start the "IBPMMSensor Work Unit" from the Interstage Management Console. 2. Starting Services Start the "Interstage BPM Analytics Text File Sensor" service using the Services window. Background Service program Execute the following procedures on the Analytics Server: [Windows] Stop the Interstage BPM Analytics erule Engine service using the Services window. [Solaris/Linux] Execute the below command. /opt/fjsvibpma/etc/fjsvibpma.server start The Interstage BPM Analytics Server Execute the following procedures on the Analytics Server: [Interstage] Start the "IBPMMServer Work Unit" from the Interstage Management Console. [WebLogic] Run the startup script located in <BEA Home>/user_projects/domains/<Domain Name>/bin: - 6 -

12 - Windows Administration Server: startweblogic.cmd Managed Server: startmanagedweblogic.cmd <Server Name> - Solaris/Linux Administration Server: startweblogic.sh Managed Server: startmanagedweblogic.sh <Server Name> [WebSphere] Run the startup script located in <WebSphere Installation Directory>/AppServer/bin: - Windows startserver.bat <Server Name> - Solaris/Linux startserver.sh <Server Name> [JBoss] Run the startup script located in <JBoss Home>/bin: - Windows run.bat - Solaris/Linux run.sh 1.2 Restoring the Interstage BPM Analytics Server Environment This section provides details of how to restore the Interstage BPM Analytics Server environment using the files that have been backed up. Note Analytics environments that have been backed up can only be restored to environments with the same system configuration as the original environment, including the same database product for the event DB and the same sensor arrangement. After completing the restore procedures, check the access authority for the files and the folders. The access authority may have changed during the file copy process. Procedure for Restoring Server Resources The procedure for restoring Analytics Server resources is as follows: 1. Install IBPM Analytics Server and related products. 2. Stop any related systems. 3. Restore the environment. Restore the Server configuration settings. Restore the working directory. 4. Restore the Events database. 5. Restart the related systems. 6. Update the settings. Update the information for connecting to the Analytics Server

13 Update the information for connecting to the Events database. Note Please stop and restart related systems again if the Analytics Server fails to start first time after restoring. To do so, the Analytics Server will reconfigure itself. Procedure for Restoring Sensor Resources The procedure for restoring Analytics Sensor resources is as follows: 1. Install the sensors and related products. 2. Stop any related systems. 3. Restore the environment. Restore Remote Sensor configuration settings. Restore the working directory. 4. Restart the related systems. 5. Update the settings. Update the Sensor connection information. Note Please stop and restart related systems again if the Remote Sensor fails to start first time after restoring. To do so, the Remote Sensor will reconfigure itself Installing the Interstage BPM Analytics, Sensors and Related Products This operation is not required when simply restoring resources to a pre-existing Interstage BPM Analytics environment. Refer to the "Interstage BPM Analytics Installation Guide" for details on installation. Refer to the manuals for each product for details of installing the related products Stopping Related Systems Temporarily stop the Interstage BPM Analytics Server, background service program and remote sensors in order to restore environment data. Execute it according to the procedure similar to backup Restoring the Environment Restoring the configuration files Replace the target directory on the machine to which resources are being restored with the settings file that was saved in "Backing up the IBPM Analytics Server configuration files". Restoring the Work Directory Replace the target directory on the machine to which resources are being restored with the settings file (C:/BPMBackup/ibpmm_data) that was saved in Backing up the Working Directory Restoring the Events Databases Restore the following databases: - 8 -

14 Event Database Archive Database (if available) These operations are not required for sensors. This section explains how to restore these databases using Oracle as an example. For other types of database, restore the target resources by referring to the manuals for the type of database management system being used. To restore Oracle databases, use the restoration method for the tool that was used to back up the database in the first place. Refer to the Oracle manuals for details of each of these restoration methods Example Using the Oracle Import Utility This example explains how to restore databases using the Oracle Import utility, which corresponds to the Oracle Export utility. Perform the following operations as a user with database administrator privileges. Create Tablespaces Create tablespaces for restoring the data to the database. Sample Format for Creating Tablespaces Using SQL For the underlined sections, enter the items appropriate to the environment being restored: CREATE TABLESPACE "tablespace name" LOGGING DATAFILE 'path to the data file' SIZE tablespace size EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; Sample SQL Statements for Creating Tablespaces This example assumes that the Events Database and the Archive Database are stored in different tablespaces: CREATE TABLESPACE "EVENTSTORESPACE" LOGGING DATAFILE 'C:\ORACLE\ORADATA\BPM\EVENTSTORESPACE.ora' SIZE 100M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; CREATE TABLESPACE "ANALYSISSPACE" LOGGING DATAFILE 'C:\ORACLE\ORADATA\BPM\ANALYSISSPACE.ora' SIZE 100M EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO; Note that tablespaces can also be created from the Oracle Enterprise Manager Console. Create a User Create a user that connects to the database from the Interstage BPM Analytics. Sample Format for Creating Users using SQL For the underlined sections, enter the items appropriate to the environment being restored: CREATE USER "user name" PROFILE "DEFAULT" IDENTIFIED BY "password" DEFAULT TABLESPACE "created tablespace " ACCOUNT UNLOCK; GRANT "CONNECT" TO "user name"; - 9 -

15 Sample SQL Statements for Creating Users CREATE USER "ESBPM" PROFILE "DEFAULT" IDENTIFIED BY "password" DEFAULT TABLESPACE "EVENTSTORESPACE" ACCOUNT UNLOCK; GRANT "CONNECT" TO "ESBPM"; CREATE USER "ASBPM" PROFILE "DEFAULT" IDENTIFIED BY "password" DEFAULT TABLESPACE "ANALYSISSPACE" ACCOUNT UNLOCK; GRANT "CONNECT" TO "ASBPM"; Note that users can also be created from the Oracle Enterprise Manager Console. Restoring Data The Oracle data that was backed up in Section Backing up the Events Database can be restored by executing the following command. Sample Format for the Database Restoration Command For the underlined sections, enter the items appropriate to the environment being restored: imp user name BUFFER=data buffer size FROMUSER=owner of the table that was backed up TOUSER=owner of the table being restored DESTROY=y (*1) FILE=file that was backed up LOG=path to the log file *1: Specifying DESTROY=y overwrites the existing data file. Example of How to Execute the Database Restoration Command This example assumes that the event DB and the Archive DB are stored in different tablespaces. imp BUFFER=30720 FROMUSER=ESUSER TOUSER=ESBPM DESTROY=y FILE=C:/BPMBackup/es_backup.dmp LOG=C:/BPMBackup/es_backup_imp.log imp BUFFER=30720 FROMUSER=ASUSER TOUSER=ASBPM DESTROY=y FILE=C:/BPMBackup/as_backup.dmp LOG=C:/BPMBackup/as_backup_imp.log Note Do not create tables if the table specification method was used to back up the database. These tables will be created automatically when the database is restored Restarting Related Systems Background Service program Start services according to a similar procedure. Interstage BPM Analytics Server Start the Interstage BPM Analytics Server according to a similar procedure

16 1.2.6 Updating the Settings Updating the Information for Connecting to the Analytics Server If the information for connecting to the Interstage BPM Analytics Server has been changed (due to reinstallation, for example), use the Management Console to update the Connection Information for connecting to the Analytics server to match the post-restoration environment. After updating the connection information, restart the Interstage BPM Analytics Server. These operations are not required for sensors. Updating the Information for Connecting to the Database If the information for connecting to databases has been changed (due to reinstallation, for example), use the Management Console to update the Connection Information for Events DB and Connection Information for Archive DB settings to match the post-restoration environment. After updating the database connection information, restart the Interstage BPM Analytics Server. These operations are not required for sensors. Updating the Sensor Connection Information If the information for connecting to sensors has been changed (due to reinstallation, for example), use the Analytics Management Console to update the Sensor URL in the Connection Status to match the post-restoration environment. 1.3 Migrating the Events database When changes to the hardware environment or to the system environment occur, it is sometimes necessary to change the storage location for the Events Database or the Archive Database. This section explains the procedure to migrate the Events Database and the Archive Database. The storage location for the Events database and the Archive database can be changed if the following conditions are met: The old and new storage locations have the same DBMS type, and The new storage size is bigger than old one Procedure for Migrating the Events Database The procedure to migrate the Events database is as follows: Migration Procedure 1. Stop related systems 2. Back up the Events Database from its current storage location Back up the current Events Database. Refer to Section, Backing up the Events Database for details of how to back up databases. 3. Restore the Events Database to the new storage location Restore the data backed-up in step 2 to the new Events database. Refer to Section, Restoring the Events Databases for details of how to restore databases. 4. Start related systems 5. Update the Events Database connection information Update the information for connecting to the Events Database to the information for the new Events Database. Refer to the "Interstage Business Process Manager Analytics Management Console Guide" for details of how to change the information for connecting to the Events database

17 6. Delete the old Events Database Delete the Events Database at the old storage location if it is no longer required. Refer to the "Interstage Business Process Manager Analytics Installation Guide" for details of how to delete the Events Database. Note Check the procedure or sample script used to delete the old Events Database, in order to ensure that the new Events Database will not be deleted by mistake Procedure for Migrating the Archive database The procedure to migrate the Archive Database is as follows: Migration Procedure 1. Stop related systems 2. Back up the Archive Database from its current storage location Back up the current Archive Database. Refer to Section, Backing up the Events Database for details of how to back up databases. 3. Restore the Archive database to the new storage location Restore the data backed-up in step 2 to the new Archive Database. Refer to Section, Restoring the Events Databases for details of how to restore databases. 4. Start related systems 5. Update the Archive Database connection information Update the information for connecting to the Archive Database to the information for the new Archive database. Refer to the "Interstage Business Process Manager Analytics Management Console Guide" for details of how to change the information for connecting to the Archive Database. 6. Delete the old Archive Database Delete the Archive Database at the old storage location if it is no longer required. Refer to "Interstage Business Process Manager Analytics Installation Guide" for details of how to delete the Archive Database. Note Check the procedure or sample script used to delete the old Archive Database, in order to ensure that the new Archive Database will not be deleted by mistake

18 Chapter 2 Messages Overview This chapter provides an overview of the messages that may occur during Interstage BPM Analytics operations. 2.1 Message Output Format A sample message output is shown in the following table. Message identifier BADM2104 Message content Authentication failed. The password is incorrect. Message identifier The number identifying each message. Message content The message text which is output. This manual does not cover the following messages: Messages that do not require any action. These include information-level messages such as "The operation was successful." Messages that do not require a detailed explanation. These include simple messages, for example a message indicating that a password was entered incorrectly. Messages reporting problems that the user cannot resolve. These include messages reporting a corrupt system environment or corrupt definitions. Contact Fujitsu technical staff in such cases. 2.2 Message Output Destinations Output to GUI The following functions output messages to these corresponding destinations: Analytics Studio Management Console Dashboard Function Management command Other messages Output destination Analytics Designer GUI Web browser Command line Log file Windows Application logs Application logs relating to general Interstage BPM Analytics operations can be viewed using the Event Viewer provided with Windows. Server logs Interstage BPM Analytics Server, Dashboard and Sensor logs are output to the following folder: Interstage Application Server: [Interstage installation directory] /J2EE/var/deployment/ijserver/IBPMMServer/apps/ibpmm.war/log

19 WebLogic Server: - no-stage mode: On Windows: C:\ibpmm\bpmm\ibpmm\log On Solaris/Linux: /var/opt/fjsvibpma/ibpmm/log - stage mode: <WebLogic domain dir>/servers/<server_name>/stage/ibpmm/ibpmm/log WebSphere Server: - <WebSphere_Installation_Directory>/AppServer/profiles/<profile_name>/installedApps/<WebSphere_Cell_Name>/ ibpmm_war.ear/ibpmm.war/log JBoss Server: - Default context: <JBoss Home>/server/default/ibpmm.war/log - IBPMServer context: <JBoss Home>/server/IBPMServer/ibpmm.war/log These functions have the following log files: Type Analytics Server Dashboard Sensor Log files server.log access.log bpmeventcollectorerror.log activitymonitor.log activitymonitoralert.log activitymonitorweb.log (log/agent/) sdk.log sdk_access.log sdk_event.log agent_isi.log agent_eis_rdbms.log agent_text.log Note The logging level and the log file size can be changed from the Management Console. The server.log and access.log can be seen in View Log window in the Management Console, and can be downloaded. Remote Sensor logs Remote Sensor logs are output to the following folders: Interstage Application Server: [Interstage installation directory]/j2ee/var/deployment/ijserver/ibpmmsensor/apps/ibpms.war/log/agent Sensor as Windows service: [Sensor installation directory]/log/agent Interstage BPM Analytics Studio logs Interstage BPM Analytics Studio logs are output to the following file: [eclipse workspace]\.metadata\.log

20 Interstage BPM Analytics Studio logs can be viewed from the [ Log] view of Interstage Studio (or Eclipce). Display the [ Log] view: [Window] - [Display Views] - [Other] - [PDE Runtimes] - [ Log] plug-in name: "com.fujitsu.bpm.designer" 2.3 Message Format The format of messages listed in this manual are as follows: Message This section shows a message output by the product. It consists of a message identifier and message content, and can also include parameter information. This section shows one of the following three message types: Warning Information This section shows the meanings of parameters that are embedded within a message. This section shows the meaning of the message. This section outlines the action to be taken in response to a message. Refer to the manual for details. Note that messages of the type "Information" do not require any action

21 Chapter 3 Troubleshooting 3.1 Installation Problems Installation Failed on Interstage Application Server (Windows) Cause A required Interstage Application Server service program may not be available. Start the following service programs if they are not currently running: - Interstage Operation Tool - INTERSTAGE displayed in event log after installation Problem The error The Analytics Server failed to start. was displayed in the event log after installation. Cause This message is generated when the set up is not completed immediately after the installation. No action required. 3.2 Problems with the Analytics Server Analytics Server Failed to Start when SQL Server is used for the Events Database Cause The Analytics Server may have failed to access the Events Database. SQL Server does not support Windows authentication when connections are established using JDBC drivers. Change the authentication method for users connecting to the Events Database to mixed mode (rather than Windows authentication mode). IBPM Analytics Server Failed to Start Cause The cause may be any of the following: - The [Interstage BPM Analytics erule Engine] service is not running. - An error in the settings for connecting to the Events Database. - The Events Database (RDBMS) may not be running. Check the causes listed above, and take any necessary action

22 3.3 Problems with Sensors Sensor not Running after Installation Cause 1 A sensor may fail to start because the IBPM Analytics Server may not be running. 1 Check operational status using the Management Console. Log in to the Management Console, start the IBPM Analytics Server, and then try starting the sensor again. Cause 2 The host name or port number specified at installation for the IBPM Analytics Server may not be correct. 2 Check the host name and port number using bpmupdatesensorconf command at the Sensor site. If it is not correct, make new settings using the bpmupdatesensorconf command in the update mode and then try starting the Sensor again. 3.4 Problems with IBPM Analytics Studio Failed to connect to IBPM Analytics Server Cause The host name or port number specified in the Analytics Studio s configuration for the IBPM Analytics Server may not be correct. The following problems may result from this error: - Cannot download definitions from the IBPM Analytics Server - Cannot upload updated definitions to the IBPM Analytics Server - Cannot change Analytics Studio s edit mode Specify the correct host name or port number of the IBPM Analytics Server. Sensor which can control several connections is not listed in the Connection Wizard Cause 1 The Sensors will be displayed in the Sensor list using latest downloaded definitions. If you install a Sensor after the download operation, it will be not displayed. 1 Download definitions from the Analytics Server after the Container (Sensor) is installed. Cause 2 The Sensor which is installed on the remote system cannot connect to the IBPM Analytics Server. 2 Check the Sensor connection, IBPM Analytics Server address or Network environment. Edit mode cannot change to Single Cause 1 Another user has been editing definitions in the Single user mode. 1 Check whether another user is using the IBPM Analytics Studio, and ask that user to switch to the Multi-user mode

23 Java VM Message Cause 1 The error message "The heap size of Java VM is insufficient" is displayed. In this case too many plug-ins are running on Eclipse concurrently. 1 Tune the memory size of the software on which the IBPM Analytics Studio is installed. The recommended value is 512MB or more. (-Xmx512m) For Interstage Studio C:/Interstage/IDE/eclipse/isstudio.ini For BPM Studio C:/Fujitsu/InterstageBPM_studio/bin/IBPMStudio.ini For Eclipse C:/eclipse/eclipse.ini 3.5 Event Collection Problems Events cannot be Collected Cause The cause may be any of the following: - The defined Connection may not have been enabled. - Sensors were not restarted after uploading a new Sensor configuration. Check the causes listed above, and take any necessary action. Text Sensor Events not Collected Cause There may be an incorrect file name or directory path. Specify the file name or directory path again, using the correct values. Deletion and Movement Processing Failed during Text File Collection Cause A text sensor may have been accessing the file (in order to collect events) at the moment when the business system executed deletion or movement processing on the file in question. Files cannot be deleted while they are being read by text file sensors. If the business system includes processing that deletes or temporarily moves the file, then the timing of when the sensor reads the file will need to be adjusted

24 Text File Sensor Collection Failed Cause 1 The access privileges that have been set up for the file may not allow the file to be accessed using the "Administrator" privileges held by the text sensor. 1 Enable the file to be accessed, for example, by adding "Administrator" privileges to the access rights for the file. Cause 2 An error with the format specification in the task settings for the Analytics Studio when date/time type elements are acquired. 2 Correct the acquisition format specifications in the task settings to match the format of the text file being monitored. The default format specification assumes that the data will be accurate to the millisecond. If the text file does not include digits for milliseconds, remove the digits for milliseconds from the format specification as well. Cause 3 The size of installation folder path is too long on the Windows Service Edition Text File Sensor. 3 Re-install using a shorter sized path. Cause 4 When the binary data is included in the file, it fails. 4 Check the target file. Date and Time Information Incorrectly Extracted from a Text File Cause The format specification for date/time elements (such as yyyy/mm/dd HH:mm:ss) may be incorrect. Check that the format specification is correct. 3.6 Problems with the Management Console "Internal Server " Encountered Cause The "IBPMMServer" Interstage Application Server Work Unit may not be running. Start the "IBPMMServer" Interstage Application Server Work Unit. Connections Defined in Analytics Studio not Displayed in the Management Console Cause 1 The Upload to Server operation in the IBPM Analytics Studio was not performed. 1 Execute an Upload to Server operation. Cause 2 The latest information may not be displayed in the Management Console

25 2 Click the [Refresh] button in the Management Console. Data Migration Problems Cause The Archive Database Connection Information setting may be not correct. Check the settings on the Management Console. Cannot create Database table Cause The setting of the Management database might be wrong. Investigate the following items: - Has an appropriate JDBC driver been deployed? - Is the JDBC connection parameter correct? - Is the User ID/Password valid? - Does the user have proper access rights? 3.7 Problems Calculating Statistical data Expected statistical data not generated Cause Some events may fall outside the range of the operating specification for calculation processing, such as: - General events that occurred before the [Start Time of Calculation] may not have been calculated. - General events that occurred more than [Number of calculation units] x [unit of calculation] ago may not have been calculated. Check the calculation rule settings, taking the above specifications into account. Unexpected Results Cause There may be a mistake with the way the calculation processing functions are being used. Consider the following factors: - Attributes specified with group attributes may have been calculated as independent events. - For calculations that require the total number of events, "Count" must be specified as the calculation method - not "Total". If "Total" is specified, the result will be the total of the data values for the target attributes. Review the settings for the calculation rule, taking the above factors into account. Measurement and judgment of Lead Time results not correct Cause The Calendar setting of the work flow environment (time zone and business hours, etc.) might be wrong

26 Confirm the Calendar setting of the work flow environment. The calendar setting also exists in IBPM Studio. 3.8 Problems with Dashboard "Internal Server " Displayed Cause The "IBPMServer" Interstage Application Server Work Unit may not be running. Start the "IBPMServer" Interstage Application Server Work Unit. Dashboard not Displayed Correctly Cause1 The security settings for the Web browser may be too high, blocking the execution of some of the IBPM Analytics screen. 1 Lower the security level for the Web browser, for example, by removing the blocks on JavaScript and ActiveX. As a general rule, the browser should run at "Medium" security level. Cause2 - Select Enable of Allow META REFRESH on Miscellaneous category. - Select Enable of Active scripting on Scripting category. Required software such as Adobe Flash Player is not available on your PC. 2 Install required software to your PC. Extremely Slow Screen Display Response Times Cause 1 Event statistics calculation processing may be placing a high load on the IBPM AnalyticsServer. 1 Either decrease the frequency with which calculation processing is executed (by adjusting the schedule) or reduce the precision of the calculation processing (by adjusting the settings for calculation units). Cause 2 The Events Database may require performance tuning. 2 Tune the database by referring to the manuals for the database. Even if optimized information has been set up, consider updating the optimized information if the amount of data has changed. Process diagram not displayed for Business Performance analytics Cause The cause may be any of the following: - The Interstage BPM Console program is not installed on the IBPM Analytics server. - The Console configuration for the IBPM Analytics Server has not been completed

27 - The specified Interstage BPM Server address in the Console is not correct. Check the causes listed above, and take any necessary action. 3.9 Problems Displaying Alerts No Alerts Displayed in the Alert List Cause The cause may be any of the following: - Events may not been collected. - The alert rules may not have been enabled. - The alert rules may not have been enabled if the IBPM Analytics Server was restarted after the rules were set up. Check the causes listed above, and take any necessary action. Intended Alerts not Displayed in Alert List Cause The alerts may not have been specified in [Filter by alert rule name] in the [Alert Monitor Pattern] settings in the IBPM Analytics Studio. Either cancel the [Use] checkbox for [Filter by alert rule name] in the [Alert Monitor Pattern] settings in the IBPM Analytics Studio, or add the required alert rule to the list of alert rule names. Unknown strings ${any words} in Alert message Cause1 The Input Parameter which is used to generate the error message for the Alert, is not correct. 1 Update this parameter to correct using IBPM Analytics Studio. Cause2 Analytics server can convert them to the instance values only when the target event has the values. 2 Delete the unconverted parameter from Alert message using IBPM Analytics Studio Chart Display Problems IBPM Analytics Studio Chart Settings Changes not Applied Cause The new definitions may not have been uploaded since the changes were made using the IBPM Analytics Studio. Upload the definitions

28 Extremely Slow Screen Display Response Times Cause1 The screen may be taking a long time to refresh because of an extremely large number of events in the display range for the chart. 1 Reduce the number of data elements to be plotted on the graph by adjusting the [Data acquisition range] in the chart settings. Cause2 There are too many charts in the Chart layout. 2 Reduce number of charts to display. "No data" Displayed, No Data Plotted Cause The cause may be any of the following: - No events data exists for the period specified by the display range settings for the chart. - Intended chart settings were not applied because the commit (upload to the server) function was not performed after changes to the definitions were made in the IBPM Analytics Studio. - Intended calculations were not executed because a calculation rule was not enabled. Check the causes listed above, and take any necessary action. Statistics Events Charts not Displayed Clearly Cause The target data displayed in the chart may be incomplete as a result of a time lag between the time when all of the target general events for the calculation were ready and the time when the calculation was executed. Make the following two settings to adjust statistics events that are displayed in the chart: - Increase the precision of the calculation results. - To do so, increase the value of the [Number of Calculation Units] in the [Setting for Calculation Period] for the statistics events step by step. - Adjust the right-hand edge of the graph in the [Period] settings for the chart by an amount equal to the time lag above. "An unexpected error has occurred" is Displayed Cause This error message is sometimes displayed in the chart view if chart settings are changed using the IBPM Analytics Studio while a chart is still displayed in the Web browser. Close the Web browser and then open the chart view again

29 Appendix A Application Log Messages A.1 Application Log Messages (BOPExxxx) This chapter explains the operation log messages that are output to application logs. They mainly consist of logs relating to the startup and shutdown of basic services and major problems that occur during the execution of monitoring functions. BOPE1001 The number of pooling event in sensor is over the maximum count [{0}]. Warning {0}= The maximum number of pooling events The number of pooling events has exceeded the monitored value. Reduce the interval used to report events from the sensor. If the problem persists even after the notification event is shortened, ask the administrator to check the operational status of the Analytics Server. BOPE2001 Failed to start the Analytics Server. ( Caused: {0} ) {0}= Cause message An error occurred while the Analytics Server was starting up. Refer to the error message and take whatever action is appropriate. If the problem persists, contact a Fujitsu SE. BOPE2011 Failed to execute the event calculation process. ( Rule name:{0}, Caused: {1} ) {0}= Event statistics calculation rule name {1}= Cause message An error occurred during an event statistics calculation process