Steps for Configuring Optimize for B2B

1. Configure the JMS Message Server. If you want to use a Message Server other than the default Integration Server Message Server instance, you must configure it appropriately. See Configuring the Java Message Service (JMS) Server for details.

3. Configure a TN document type by selecting the document attributes you want to monitor. The values of only those document attributes that you select are extracted for monitoring. You can monitor both system attributes and custom attributes. See Configuring TN Document Types and Attributes for BAM for details.

For each document attribute you selected for monitoring, you must indicate whether the document attribute is a measure, a dimension, or a transaction. This is known as map.

A KPI is a monitor item that analyzes the measures using the dimensions. A Dimension Hierarchy illustrates the relationships between KPIs. You map each KPI with a Dimension Hierarchy. Based on these KPIs, Optimize for B2B analyzes the data and saves that data to the Optimize database.

Note:

For most systems, the default Optimize event processing configuration provides an appropriate mix of performance and event integrity and, under normal operation, users should not encounter any event related problems. For some users that require maximum event integrity in the face of system or software failures, however, Optimize supports a guaranteed event storage configuration that uses a custom Monitor API (MAPI) configuration and batching techniques to provide enhanced event delivery and notification of event delivery problems. Note that this configuration sacrifices system performance for maximum event integrity, and it is not appropriate for most typical system configurations. For more information about implementing Guaranteed Event Storage, see the "Configuring Optimize" chapter of the Administering webMethods Optimize guide.