User Guide > Push-Based Incremental Caching > Configuring Oracle Data Sources for Change Notification
 
Configuring Oracle Data Sources for Change Notification
Data sources must have a change notification connector and a topic name specified.
Derived views must be available to be subscribed to, or have cached views that are incrementally maintained. The topic name must be specified on the Change Notification tab of the data source; otherwise, the data source will not receive data source change messages from the Oracle GoldenGate process.
Note: The Change Notification tab for the data source only appears after the Central Event Server has been configured.
The data source Change Notification tab defines the Topic Name to which Oracle GoldenGate is configured to send change notification messages.
Each watched data source must specify a topic on which to receive change notification messaging from the Oracle GoldenGate utility. The topic can use the Input EMS Default Connector or a different JMS Connector specific for that data source.
If a single instance of Oracle GoldenGate has been sending nonconforming messages, it is possible that only the topics affected by that Oracle GoldenGate instance need to be purged rather than all of the data sources topics.
To configure an Oracle data source for change notification
1. Create the Oracle data source.
2. Open the Oracle data source.
3. Select the Change Notification tab.
4. (Optional) Type a JMS Connector Name. This value overrides any JMS connection that is defined in the TDV configuration parameters. If no value is specified, the value of the Default Connector TDV configuration parameter is used as the JMS connector.
5. Type a Topic Name. The topic name must be the one you created during JMS configuration. (See Defining Connectors.)
6. Save the information.