Creating a Custom Configuration File for the Feed Handler

Define a file to store additional configuration settings for your custom feed handler.

Prerequisites

Review publisher.xml to see what XML elements are there. Calling pub_initialize() reads in and uses the settings in publisher.xml for all feed handlers. Your custom file only needs to initialize custom code, if necessary, or to override settings in publisher.xml.

While you can modify a custom configuration file at any time, it is a good practice is to create it and establish initial settings as you develop your feed handler. Manage your code to read the RAP configuration files, and add your own configuration files if needed.

Define an XML file, properties file, or other source to contain configuration settings for your feed handler.
Defining configuration settings in a separate file means that you do not need to recompile code if settings change.

For custom feed handler configuration settings, you do not need to use a file that references XML elements as in publisher.xml.
Set XML elements or properties as needed for your publisher and environment.
Your file should specify sources for feeds, log files, and other information needed to associate your publisher with the rest of the data flow in the system. It does not mirror publisher.xml

For examples, see the additional configuration settings for the FAST feed handler in fastfeedhandler.xml.
Initialize the configuration file in a method you define in your publisher and ensure that your code parses the settings in your configuration file.

Next

To manage your feed handler from the OpsConsole, configure agent-plugin.xml, register the agent, and set required environment variables. You need to configure values for the publisher host name and administration port, start command, component display names, and log file.