BPI consists of a number of individual components, each of which has its own configuration, or property file that define the parameters that can be used to control how the component behaves. Examples of parameter values that can be configured are:
➤ Retry delays
➤ Port numbers
➤ Logging levels
Many of the parameters in these property files do not need to be changed.
Therefore, in order to simplify the management of the BPI system, only those parameters that might need to be modified have been made available through the BPI Server Administration Console.
Caution: If you do make changes directly to the properties in the property files, you need to reapply the changes each time you reinstall BPI, or add the same changes within the Administration Console, where they are preserved.
This is because the files and the property values in these files are overwritten when the BPI Server is installed.
Specifically, the Administration Console provides access to the following BPI Server component areas:
➤ Server component status, which:
➤ Shows whether the BPI Server components are running.
➤ Enables you to start and stop components.
➤ Enables you to view the content of the current log file.
See "Status" on page 135 for details of the Status option.
➤ Notification Server parameters; see "Component Configuration - Notification Server" on page 141.
➤ Business Impact Engine parameters; see "Component Configuration - Business Impact Engine (BIE)" on page 145.
➤ Monitor Engine parameters; see "Component Configuration - Monitor Engine" on page 161.
➤ HP Business Service Management parameters; see "Component
Configuration - HP Business Service Management Settings" on page 175.
➤ Process Repository parameters; see "Component Configuration - Process Repository" on page 184.
➤ Business Event Handler parameters; see "Component Configuration - Business Event Handler" on page 188.
➤ JMS Business Event Handler parameters; see "Component Configuration - JMS Business Event Handler" on page 190.
➤ Servlet Engine parameters; see "Component Configuration - Servlet Engine" on page 197.
➤ Microsoft SQL Server access.
This option is available when you have configured Microsoft SQL Server as the database for the BPI Server; see "Component Configuration - MS
➤ Port number settings; see "Component Configuration - Port Numbers" on page 209.
➤ Logging parameter settings; see "Component Configuration - Logging" on page 212.
The configuration parameters that you can modify for these component areas are described in the remaining sections of this chapter.
Note: The Modeler is not a BPI Server component. For details on configuring the Modeler, see the “Modeler” chapter in the Using Business Process Instance Guide.
Status
Use this option to start and stop the BPI Server components and also to view the component log files of these components.
The Status pane lists the BPI Server components that you can start and stop, and includes buttons labeled, Start, Stop and View Log. The components included on the Status pane, following a full installation on Windows, are:
➤ Business Impact Engine (BIE)
The component responsible for managing the progress of process instances, based on the business and operational events received from external sources. The BIE also generates impact notifications.
➤ Monitor Engine
The component that analyzes and provides the statistical results from Business Process Monitor, monitor instances and performance indicators.
The Business Process monitors are created using the Business Process Monitors Definer.
➤ Business Event Handler
Receives business events from sources external to BPI and forwards them on to the Business Impact Engine in a standard format.
➤ JMS Business Event Handler
Received JMS-sourced business events from JMS-based business
application sources external to BPI and forwards them on to the Business Impact Engine in a standard format. TransactionVision is an example of a JMS-based application.
➤ Process Repository
The design-time repository where the BPI Modeler stores its definitions.
The Process Repository uses the information in the Process Repository schema when deploying the Business Processes.
➤ Data Samples Provider
The BPI component that is responsible for sending data samples to the BSM system.
➤ Web Services Provider
The BPI interface that exposes BPI Web Services to an external consumer.
➤ CI Status Poller
This is the service adapter that is used to manage the communication between the Business Impact Engine and the Gateway Server that BPI connects to for CI statuses.
➤ Servlet Engine
This is the Web Server component (Tomcat) that is installed as part of BPI.
This component manages the server-side of all the BPI Web-based interfaces, for example: the Notification page and Process Intervention page. It also manages the process instance and violation pages that are presented through the BPI Application pages.
➤ Notification Server
The component used to send email notifications of business events to configured recipients.
You also access the log files for the BPI Server components from the Status pane. This enables you to identify status and error information for that component. The level of detail shown in the log files is controlled by the logging levels that you set. Setting log levels is described in section
"Component Configuration - Logging" on page 212.
If the log files are not displaying correctly on your system, you can change the viewer used to display the log files as described in section "Log File Locations and Changing the Log Viewer" on page 139.