WebSphere

Configuring the Common Event Infrastructure using the Administrative Console

ConfigureCommon Event Infrastructure by using the server administrative console.

About this task

Open the Common Event Infrastructure Server panel of administrative console:
Procedure
  1. Enable the deployment of the Common Event Infrastructure enterprise application by selecting the check box labeled Enable the event infrastructure server. If the server has already been configured, then you can enable or disable it by selecting or clearing the check box. If the enable check box is cleared then Common Event Infrastructure has not been configured, or has had a previous configuration disabled but the server has not been restarted. An information message shows you whether this deployment target has Common Event Infrastructure configured. If the server has already been configured, you may change the data source settings for the event database and/or the message store.

    Note: If you select the check box to enable the Common Event Infrastructure server and the server has not yet been configured, then the parameters shown will be used to configure it unless you change them.
    • If this is the first time you have performed the configuration, then the event data source tables are created on the common database. If there is already a Common Event Infrastructure server configuration, then you need to create a new database.
    • The messaging service is created under a unique schema under the common database.

    When the server/cluster on which Common Event Infrastructure has been configured is restarted, then the new changes take effect.

  2. Configure (or change the current settings for an existing configuration of) the event database by using one of the following methods to populate the fields with the appropriate settings.
    • Click Edit for a database configuration panel with a more extensive list of options than those listed on the panel.
    • Use the fields on the panel to enter the information, as outlined below:
    1. Database Instance – the name of the database you will use to store events.
    2. Create Tables – select this check box if you want to create the database tables on the event database.
      Note: If you are configuring Common Event Infrastructure to use a database on another server, then you will not be able to create the tables using this control. Instead, you will have to use the database scripts that will be generated after you complete the rest of this configuration. In this case, you can click Edit to show the data source detail panel, which will tell you the location of the database creation scripts.
    3. Username and Password – for authenticating into the event database.
    4. Server – name of the server where the event database is located.
    5. Provider – choose a provider for your database from the menu.
    Note: The Schema field is activated only if the database is created using DB2® on an iSeries® or z/OS® platform. In all other cases, the schema field will be disabled.
    Important: If the tables already exist on the target database, then the configuration may fail.
  3. Select whether the Common Event Infrastructure bus will be Local on the server, or Remote and reside on another server. If you choose remote, then select the remote location from the menu or click New to create a new remote bus.
  4. Configure Common Event Infrastructure support for messaging.
    • Click Edit for a database configuration panel with a more extensive list of options than those listed on the panel.
    • Use the fields on the panel to enter the information, as outlined below:
    1. Database Instance – enter the name of the database you will use to store messages.
    2. Schema – enter a name for the schema, or accept the default name given.
    3. Username and Password – for authenticating into the messaging database.
    4. Server – name of the server where the messaging database is located.
    5. Provider – choose a provider for your database from the menu.
  5. Click OK or Apply.
  6. Restart your server or cluster.

Results

All of the major parts of Common Event Infrastructure will now be configured and running on your server or cluster. These include the event data store, the messaging engine, and the event application. This single panel can be used in place of many commands and steps you would otherwise use to configure Common Event Infrastructure.

What to do next

After you have restarted your server or cluster, you will be able to store service component events that are emitted from your applications. You can now change the runtime properties of the Common Event Infrastructure server by selecting the Common Event Infrastructure Destination panel. You can choose whether to start the Common Event Infrastructure server at startup, and specify the emitter factory JNDI name where the events will be sent.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 22 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.websphere.cei.z.620.doc/doc/tcei_configceiconsole.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).