Index Changes

At line 11 added 2 lines.
[{Image src='attach/ESBConsoleGlassfishESBEventManagementUserGuideConfiguringAlertPersistence/AlertPersistence.png' alt='Alert Persistence'}]
At line 36 added 29 lines.
!!To Configure the Alert Table Name (Databases Other Than Derby)
# Open the eventmanagement.properties file in the JavaCAPS-install-dir/appserver/domains/domain-name/jbi/config directory.
# If necessary, change the default value of the AlertTableName property and save the file.
You might need to change the default value to match your organization's naming conventions, or to comply with the database server's character limit for table names.
!!To Set Up Database Access (Databases Other Than Derby)
# Log in to the Sun Java System Application Server Admin Console.
# Integrate the JDBC driver. You can make the driver accessible to the common class loader or the system class loader. For detailed information about how to integrate a JDBC driver, click Help in the Admin Console.
# In the left pane, expand the Resources node and the JDBC node, and select the Connection Pools node.
# Click New.
# Create the JDBC connection pool. For detailed information about how to create a JDBC connection pool, click Help in the Admin Console.
# In the left pane, select the JDBC Resources node.
# Click New.
# Create the JDBC resource. You will enter the JNDI name of the JDBC resource in a later procedure. Set the pool name to the JDBC connection pool that you just created. For detailed information about how to create a JDBC resource, click Help in the Admin Console.
!!To Run the Database Scripts (Databases Other Than Derby)
# Open the jbi_rt.jar file in the GlassfishESB-install-dir/glassfish/jbi/lib directory.
# Extract the SQL scripts for your database type.
# If you are using Oracle, then create the tablespace and user that will be used to persist alerts.
## Open the create_event_store_user.sql script and make any changes needed to match your database configuration.
## Run the create_event_store_user.sql script.
# Create the table that will be used to persist alerts.
## Open the create_event_store_schema.sql script and make any changes needed to match your database configuration. Ensure that the table name matches the value in the eventmanagement.properties file.
## Run the create_event_store_schema.sql script.
!! Using the Alert Configuration Service API to configure the Event Management Framework
The Event Management Framework can be configured by writing code using the Common Management and Monitoring API. For more information, see [How do I use the Alert Framework Configuration Service API|ESBConsoleAlertConfigurationAPIUsage]
At line 67 added 4 lines.
----
* Back to [Glassfish ESB Event Management User Guide|ESBConsoleGlassfishESBEventManagementUserGuide]

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-9) was last changed on 03-Dec-09 09:28 AM, -0800 by Gopalan Suresh Raj