Development Scenarios

Choose the degree of customization your application requires.

When choosing a development scenario, note that they are all related. If you are developing a custom feed handler, you need to customize the messages and schema. Likewise, if you customize messages and schema, you need to modify the feed handler.

RAP Development Scenarios
Scenario	Description
Customize the RAP messages and schema	Add a new table or column to the RAPCache and RAPStore.
Develop a custom feed handler from a RAP Messages model	Follow either scenario for message modeling: Model a RAP message in PowerDesigner. Generate a RAP message template. Generate a Publisher API stub. Generate a physical RAPCache and RAPStore model. Or: Model the database tables in the RAPCache or RAPStore model. Generate the RAP Messages model from the RAPCache or RAPStore physical model. Generate message templates and Publisher API stubs. Generate the other physical data model (RAPCache or RAPStore, whichever you did not create or update in the first step).
Develop a custom feed handler	Use the Publisher API, the logging API, and configuration files to develop and deploy a custom feed handler. (Optional) Accelerate feed handler development using Publisher API stubs.
Customize the FAST feed handler	Customize the FAST feed handler by writing a message handler plug-in. Follow this process when the incoming data stream is encoded in the FAST protocol. You can implement a subset of the Sybase FAST feed handler, process message types other than those defined in the Sybase FAST templates library, or perform different initialization, processing, or logging.