Configuring the environment using the configuration wizard

You can configure the required IBM® Business Monitor environment using the configuration wizard in the administrative console.

1. In the navigation panel, click Servers > IBM Business Monitor configuration. A list of required and optional components is displayed. Review the status of each component. If you have an ND environment and have not configured a deployment environment, none of the components will be installed or configured, and you must complete the remaining steps to install and configure the components.
2. Configure the outbound CEI event service by completing the following steps. The outbound CEI event service is used to send events from IBM Business Monitor, including alerts. You must configure an event emitter factory to point to the outbound CEI event service.
   Important: Before configuring the event emitter factory, you must have a local CEI service that IBM Business Monitor can use to send events. If you need to create a local CEI service, see Configuring CEI event services for instructions.
   1. In the list of components, click Outbound CEI event service. The status for the outbound CEI event service and event emitter factory is displayed. If you have an existing MonitorEmitterFactory, the name of the CEI event service that the emitter factory is configured to use is listed in the status box. If you have not already configured the emitter factory, you will see the message "Local CEI event service exists, but event emitter factory does not exist." In that case, you must create and configure the emitter factory.
   2. Under Configure an event emitter factory, select the server or cluster for the event emitter factory. All available servers and clusters are listed. You can select only servers that have a CEI event service configured. (The available servers and clusters are shown with asterisks (*)). If you have more than one server with the same name, be sure to choose the server on the correct node.
   3. To launch the configuration wizard, click Configure the Event Emitter Factory. An outbound event emitter factory named MonitorEmitterFactory is created for the cell. The status box for the outbound CEI event service is updated to indicate the CEI event service that the MonitorEmitterFactory is configured to use.
   4. Return to the configuration page by clicking IBM Business Monitor configuration in the breadcrumb listing.
3. Create the service integration bus and configure the messaging engine by completing the following steps. IBM Business Monitor requires its own bus and messaging engine before it can monitor events.

   If you do not have an existing bus, one is created for you when you configure the messaging engine. The bus is named MONITOR.<cell_name>.Bus and the name cannot be changed.

   1. In the list of components, click Messaging engine. The status for the service integration bus and the messaging engine is displayed.
   2. To launch the configuration wizard, click Configure the Messaging Engine.
   3. On the Select a bus member panel, choose one of the following options to select the location where the messaging engine will be created, and click Next:
      • Cluster: Choose this option to create the messaging engine on an existing cluster. You must select the cluster name from the list.
      • Server: Choose this option to create the messaging engine on a server. You must select the server from the list. If you have more than one server with the same name, be sure to choose the server on the correct node.
   4. On the Select the type of message store panel, choose one of the following options, and click Next:
      • Data store: A data store is a message store that contains a set of tables that are accessible to all members of the cluster that hosts the messaging engine.
      • File store: A file store is a message store that uses files in a file system through the operating system. This option is not available if you chose Cluster on the Select a bus member panel.
   5. If you are using a data store, choose one of the following options on the Provide the message store properties panel:
      • Create a default data source with generated JNDI name: By default, the data store uses Derby. This option is not available if you selected Cluster on the Select a bus member panel.
      • Use an existing data source: If you select this option, complete the following fields:
        • Data source JNDI name: Select the JNDI name that corresponds to the database that you are planning to use. For example, jdbc/wbm/MonitorMEDatabase.
        • Schema name: Enter the schema name. For example, MONME00.
        • Authentication alias: Select the authentication alias that you are planning to use. You must select the authentication alias if you want the tables to be created. For example, Monitor_JDBC_Alias.
        • Create tables: Select this option to create the tables in the database. If you do not select this option, the database administrator must create the tables.
   6. On the Confirm panel, review the information and click Finish to complete the configuration. The bus and messaging engine status boxes are updated with the new configuration information.
      Note: You might have to wait a few moments for the messaging engine to start successfully.
   7. Return to the configuration page by clicking IBM Business Monitor configuration in the breadcrumb listing.
4. Verify that the bus and messaging engine have the correct user ID for your environment:
   1. In the navigation panel, click Security > Bus Security.
   2. Click the bus for the IBM Business Monitor server. The Buses configuration properties page is displayed.
   3. Under Additional Properties, click Security. Another properties page is displayed.
   4. Under Authorization Policy, click Users and groups in the bus connector role.
   5. Verify that your user ID exists. If it does not exist, complete these steps to add it:
      1. Click New.
      2. Select Users, and a enter a filter that will find your user ID. Click Next.
      3. Select your ID from the list and click Next.
      4. Review the changes and click Finish.
   6. Return to the configuration page by clicking IBM Business Monitor configuration in the breadcrumb listing.
5. Install the IBM Business Monitor action services application by completing the following steps. The action services application invokes actions, such as sending dashboard alerts or email notifications, when it receives defined situation events emitted by and other applications. Situation events typically indicate business situations that need attention, such as a printer running out of paper or a metric exceeding a certain value.
   1. In the list of components, click Action services. The status for the application is displayed. If the application is properly installed, the location of the installed application is listed in the status box.
   2. Under Deploy action services, select the server or cluster for the action services application from the list. All available servers and clusters are listed. You must select a server where IBM Business Monitor has been installed. If you have more than one server with the same name, be sure to choose the server on the correct node.
   3. To install the application, click Deploy Action Services. The application is installed and the Monitor action services group profile is created. The application status box is updated with the location of the installed application, named IBM_WBM_ACTIONSERVICES. If this application has been installed to a cluster, the application will appear unavailable until all nodes in the cluster have been synchronized.
   4. Return to the configuration page by clicking IBM Business Monitor configuration in the breadcrumb listing.
6. Install the Monitor scheduled services application by completing the following steps. You must install this application to schedule recurring services, such as the data movement service and the key performance indicator (KPI) history for monitor models.
   1. In the list of components, click Monitor scheduled services. The status for the application is displayed. If the application is properly installed, the location of the installed application is listed in the status box.
   2. Under Deploy Monitor Scheduled Services, select the server or cluster for the Monitor scheduled services application from the list. All available servers and clusters are listed. You must select a server where IBM Business Monitor has been installed. If you have more than one server with the same name, be sure to choose the server on the correct node.
   3. To install the application, click Deploy Monitor Scheduled Services. The application status box is updated with the location of the installed application, named IBM_WBM_DATA_SERVICES. If this application has been installed to a cluster, the application will appear unavailable until all nodes in the cluster have been synchronized.
   4. Return to the configuration page by clicking IBM Business Monitor configuration in the breadcrumb listing.
   You can view the scheduled services for each installed monitor model by clicking Applications > Monitor services > Monitor scheduled services
7. Optional: If you plan to use the IBM Cognos® Business Intelligence service to conduct multidimensional analysis on your dashboards, in the list of optional components, click Cognos. The status for the service is displayed. If the service is properly installed, the location of the installed service is listed in the status box. (If you installed IBM Cognos BI with IBM Business Monitor and created a stand-alone profile, the IBM Cognos BI service is already deployed.)
   1. To deploy a new IBM Cognos BI service, select the server or cluster for the IBM Cognos BI service from the list. All available servers and clusters are listed. (The available servers and clusters are shown with asterisks (*)). If you have more than one server with the same name, be sure to choose the server on the correct node.

      Provide a database name to be used for the content store. On DB2® and Microsoft SQL Server, the database name must be different from the MONITOR database name. Provide a database user name and password. If you use the same user name for the content store as for the MONITOR database, you must use the same password. Because the database user provided for accessing the content store database must have privilege to create tables in the database, it is recommended that you create a new database user for the content store database only.

      Note: The user name and password for the IBM Cognos BI content store database are kept in the Cognos_JDBC_Alias, which allows all database credentials to be maintained in one place. Whenever you start the IBM Business Monitor IBM Cognos BI server, the current values are passed to the IBM Cognos BI configuration to allow IBM Cognos BI access to the content store. Because of this integration, you cannot change the content store user name and password using the IBM Cognos BI Configuration application.
      If administrative security is enabled, you must also provide the IBM Cognos BI administrator user name and password.

      Click Create a New Cognos Service. The status box is updated with the location of the installed service. If this service has been installed to a cluster, the service will appear unavailable until all nodes in the cluster have been synchronized and restarted. If the deployment takes more time than is provided by the administrative console response timeout, you might see a timeout message. Wait a few more minutes before attempting to restart the servers.

   2. If you already have an existing version of IBM Cognos BI installed, under Use an existing Cognos service, provide the external dispatcher URI of the IBM Cognos BI server. You can find this URI in the IBM Cognos BI configuration client in Local Configuration > Environment > Dispatcher Settings (for example, http://my_host:my_port/p2pd/servlet/dispatch/ext). If administrative security is enabled on the IBM Cognos BI server, you must also provide the IBM Cognos BI administrator user name and password.

      Click Use an Existing Cognos Service. The status box is updated with the location of the installed service.

   3. Return to the configuration page by clicking IBM Business Monitor configuration in the breadcrumb listing.
8. Optional: If you plan to use the IBM Business Monitor dashboards on mobile devices, you must install the application by completing the following steps. If you do not plan to use the dashboards on mobile devices, you are not required to complete these steps.
   1. In the list of optional components, click Dashboards for mobile devices. The status for the application is displayed. If the application is properly installed, the location of the installed application is listed in the status box.
   2. Under Deploy Dashboards for mobile devices, select the server or cluster for the dashboards on mobile devices application from the list. All available servers and clusters are listed. You must select a server where IBM Business Monitor has been installed. If you have more than one server with the same name, be sure to choose the server on the correct node.
   3. To install the application, click Deploy the Dashboards for Mobile Devices. The application status box is updated with the location of the installed application, named IBM_WBM_MOBILE_DASHBOARD. If this application has been installed to a cluster, the application will appear unavailable until all nodes in the cluster have been synchronized.
   4. Return to the configuration page by clicking IBM Business Monitor configuration in the breadcrumb listing.
9. Optional: If you plan to use the Java Messaging Service (JMS) and Representational State Transfer (REST) event emitter services, you must install the API service applications by completing the following steps. Rather than coding or generating Common Base Events directly, you can then use these event emitter services. You provide the event XML, and the event emitter services receive the event XML and wrap it in a Common Base Event so that IBM Business Monitor can process it.
   1. In the list of optional components, click Inbound event emitter services (JMS and REST). The status for the applications is displayed. If the application are properly installed, the locations of the installed applications are listed in the status box.
   2. Under Deploy event emitter services, select the server or cluster for the applications from the list. All available servers and clusters are listed. You must select a server where IBM Business Monitor has been installed. If you have more than one server with the same name, be sure to choose the server on the correct node.
   3. To install the applications, click Deploy Event Emitter Services. The application status box is updated with the locations of the installed applications. If the applications have been installed to a cluster, the applications will appear unavailable until all nodes in the cluster have been synchronized.
   4. Return to the configuration page by clicking IBM Business Monitor configuration in the breadcrumb listing.
10. Optional: To configure the Representational State Transfer (REST) Services Gateway for widgets for Business Space, complete the following steps.
    Note: Because the REST Services Gateway is a shared component, you cannot configure it using the configuration wizard. If you create clusters using the deployment environment configuration wizard, or create a stand-alone profile, the REST Services Gateway is configured for you. The REST Services Gateway must be deployed and registered with Business Space before your team can use the widgets in Business Space.
    1. In the administrative console, click Servers > Server Types > WebSphere application servers or Servers > Clusters > WebSphere application server clusters.
    2. Click the name of your server or cluster.
    3. On the Configuration page, under Business Integration, click Rest Services.
11. Optional: To configure Business Space, complete the following steps.
    Note: Because Business Space is a shared component, you cannot configure it using the configuration wizard. If you create clusters using the deployment environment configuration wizard, or create a stand-alone profile, Business Space is configured for you.
    1. In the administrative console, click Servers > Server Types > WebSphere application servers or Servers > Clusters > WebSphere application server clusters.
    2. Click the name of your server or cluster.
    3. On the Configuration page, under Business Integration, click Business Space Configuration.
12. After you have finished configuring components, synchronize the nodes. In the administrative console, click System administration > Nodes, select all of the nodes, and click Full Resynchronize. Then stop and restart all of the clusters and servers.