The Fault and Alarm component Web service can
be configured to use the Common Event Infrastructure (CEI) service
that is included with WebSphere® Application Server and WebSphere Enterprise Service
Bus.
You must enable the service for the Access Gateway cluster
and for the cluster on which the Web service implementations are
deployed.
Before you begin
The instructions for this procedure assumes the database
server is not on the same server as the WebSphere Application Server.
You
must have:
- Installed the database client application on the WebSphere Application Server node.
- Stopped the deployment manager and nodes for the Access Gateway cluster
- Stopped the deployment manager and nodes for the Web services
cluster
About this task
By default the CEI service is enabled and configured to
use the database that is included with WebSphere Application Server.
For a production environment, configure the CEI service to use IBM® DB2® Enterprise
Server Edition or
Oracle.
To configure the CEI service database, you must run
a wsadmin command. The command is provided in the
instructions. The command is based on the following configuration.
If the configuration does not match your environment, consult the WebSphere Application Server Information
Center for details. Refer to the related reference link at the end
of the instructions.
This procedure assumes:
- A cluster network configuration
- The database server in not on the same server WebSphere Application Server
- The database server is running and configured
- The database client application is installed on the WebSphere Application Server node
The database that will store the CEI events
has been created
- On the Access Gateway deployment
manager, configure the CEI repository. Refer to the topic Configuring
the event database in theWebSphere ESB Information
Center for more information. (A link is provided at the end of these
instructions.) Select the appropriate database setup for your network.
- Stop the manager on the network deployment server for the
service implementations cluster.
Note: The user name and
password stopmanager.sh are required only when
the security is enabled.
Run
the following command:
was_profile_root/bin/stopManager.sh -username user_name -password password
was_profile_root/bin/stopManager.sh -username user_name -password password
was_profile_root/bin/stopManager.sh -username user_name -password password
Note: The user_name and password parameters
are required only when security is enabled.
Where:
- The was_profile_root path
contains the name of the deployment manager profile (for example,
Dmgr01).
- user_name represents your WebSphere Application Server administrator
user ID.
- password represents the password associated
with your user_name.
- Run the deployEventService command to
enable CEI.
- Change to the deployment manager profile directory. For example, if you are using the default path:
cd /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin
- Run the following command:
./wsadmin.sh -conntype none -c "\$AdminTask deployEventService { -clusterName cluster_name -enable true }"
Where: - cluster_name is the cluster where the Web service implementations are
deployed.
- Start the deployment manager and nodes. For
example, from the /bin directory of the deployment
manager profile:
./startManager.sh
- Click and enable both
administrative security and application security.
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Verify that the service was enabled:
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click the name of the application server.
- Under Container Settings, click Container
Services and then verify that Common Event
Infrastructure Service is visible.
- To enable the service on startup,
click Common Event Infrastructure Service.
- On the configuration page, click Enable service
at server startup option.
- Click Apply.
- Stop the manager before configuring the CEI service repository. Run
the following command:
was_profile_root/bin/stopManager.sh -username user_name -password password
was_profile_root/bin/stopManager.sh -username user_name -password password
was_profile_root/bin/stopManager.sh -username user_name -password password
Note: The user_name and password parameters
are required only when security is enabled.
Where:
- The was_profile_root path
contains the name of the deployment manager profile (for example,
Dmgr01).
- user_name represents your WebSphere Application Server administrator
user ID.
- password represents the password associated
with your user_name.
- Configure the CEI repository by running the appropriate
command for your database server:
Run the following command. Note that
this command is entered on a single line../wsadmin -conntype none -c "\$AdminTask configEventServiceDB2DB {-createDB
true -overrideDataSource true -clusterName cluster_name
-jdbcClassPath path_to_db_jar -dbHostName host_name
-dbUser db_user -dbPassword password -dbPort port}"
Where:- -createDB true indicates that the database has
not been created, but the database server is running. If the database
has been created, specify false and refer to the WebSphere Application Server Information
Center for more information.
- cluster_name is the cluster where WebSphere Telecom Web Services
Server will
be deployed and where the data source for the CEI service should be
created.
- path_to_db_jar is the path to the database
JAR file.
- host_name is the server on which the database
server is deployed.
- db_user is the database administrator ID,
for example db2inst1.
- password is the password for the database
administrator ID.
- port is the port used to communicate with
the database server. The default value is 50000.
Run the following command. Note that
this command is entered on a single line../wsadmin -conntype none -c "\$AdminTask configEventServiceOracleDB {-createDB
true -overrideDataSource true -clusterName cluster_name
-jdbcClassPath path_to_db_jar -oracleHome oracle_home
-dbUser db_user -dbPassword cei_password -dbName db_name
-dbHostName host_name -dbPort port -sysUser dba -sysPassword dba_password}"
Where:- -createDB true indicates that the database is
configured and running. If the database has not been created, specify false and
refer to the WebSphere Application Server Information
Center for more information.
- cluster_name is the cluster where WebSphere Telecom Web Services
Server will
be deployed and where the data source for the CEI service should be
created.
- path_to_db_jar is the path to the database
JAR file.
- oracle_home is the directory where Oracle is
installed.
- db_user is the Oracle schema
user ID that will own the CEI tables. The user ID will be created
during the database creation. The default value is ceiuser.
- cei_password is the password of the schema
user ID. The password will be created when the database is created.
This parameter is required.
- db_name is the Oracle System Identifier (SID).
The SID must already be created and available for the command to create
the tables and populate the tables with data.
- host_name is the server on which the database
server is deployed
- port is the port used to communicate with
the Oracle instance.
The default value is 1521.
- dba is the database administrator ID with
SYSDBA privileges. The default value is sys.
- dba_password is the password for the database
administrator ID.
- Start the manager. Run
the following command:
was_profile_root/bin/startManager.sh
was_profile_root/bin/startManager.sh
was_profile_root/bin/startManager.sh
Where:
- The was_profile_root path
contains the name of the deployment manager profile (for example,
Dmgr01).
- Log in to the Integrated Solutions Console:
- Open a browser and navigate to the following
URL: https://host_name:port/ibm/console.
Where:
- host_name is the fully qualified host name
of the server where the application or the network deployment manager
is deployed.
- port is the secured port used to access the
console. The default port is 9043.
Note: The default unsecured port is 9060.
If you use 9060, you must have "http" instead of "https" in the URL.
- Enter an administrator user ID and password. (Omit the password if security is
not enabled.)
- Click Log in.
- In the navigation pane, click .
- Click the JDBC provider for your database:
Event_DB2_JDBC_Provider
Oracle JDBC Driver
- Under Additional Properties, click Data sources.
- Verify that following names are listed in the JNDI name
column.
- jdbc/cei
- jdbc/event_catalog
For CEI to work on your DB2 server,
configure the following JNDI: jdbc/com.ibm.ws.sib/imsCluster-CommonEventInfrastructure_Bus.
- In the navigation pane, click .
- Click New and enter the following
information for the newly created DB2 Universal JDBC Driver Provider:
Populate :
- Enter the JNDI name as jdbc/com.ibm.ws.sib/imsCluster-CommonEventInfrastructure_Bus.
- Select a proper J2C for the Component-managed authentication
alias.
- Enter EVENT as the database name.
- Enter your database server name as the Server name.
- Enter the port number for the database server, for example
50000 or 1521.
- Save your updates.
- Optional: For DB2 systems,
check the results by running db2cc from the DB2 server,
or by performing the following steps from the database manager:
- On DB2,
connect to EVENT user db2inst1, using connect
to CEI EVENT database . The DB2 list
table displays.
- Verify that the display shows a list of tables whose
names start with CEI.