System Configuration Overview

After installing the Large Database connector, you must perform the following general configuration steps, which are explained in subsequent sections:

  1. Configure the jms.properties file to "fetch" your data sources - The Large Database connector needs configured to get data from a CDC Event Server via the JMS service provider. If the JMS service provider is WebSphere MQ, you only need to set the host, port, queue name of the JMS service provider. However, if you are using a non-WebSphere MQ JMS provider service, you will need to configure the file spring-jms-context.xml to work with your JMS third party provider.
  2. Configure the application.conf file to "push" data - After configuring the Large Database connector to "fetch" data, the connector needs to know where to send that data. This requires setting the configuration for the location of ZooKeeper, which in turn informs the connector about the location of one or more Watson™ Explorer Engine collections. It is assumed that ZooKeeper and your Watson Explorer Engine collections are configured to receive this information. See System Requirements for details on these settings.
  3. Configure the application.conf file to map fields from the CDC Event Server to fields in the Application Builder entity model - Application Builder enables searching across multiple Watson Explorer Engine search collections. You will need to configure field mapping settings in the Large Database connector application.conf file. These settings link the fields in your CDC Event Sever with the equivalent fields in the Application Builder entity model. The Large Database connector essentially maps the database schema to the Application Builder entity model schema.
    Note: The entity model in Application Builder must already have been created. Consult your Watson Explorer Application Builder resources if you need assistance with creating and configuring an Application Builder entity model.

The Large Database connector is now installed. Next, you will need to configure the Large Database connector.