Message Modeling

You can integrate message customizations with the database schema and Publisher API code to aid production deployment of feed handlers. You can start by modeling the message or start with the database model.

If you start by modeling the message:

Model a RAP message in PowerDesigner.
Generate a RAP message template.
Generate a Publisher API stub.
Generate a physical RAPCache and RAPStore model.

If you start with the database model:

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).

In both scenarios you can validate a model using custom checks for RAP messages, in addition to standard PowerDesigner checks for all models.

Both scenarios require the PowerDesigner extensions for RAP.

This document summarizes tasks for these scenarios. For details, see Data Model and Queries.

Modeling a RAP Message in a PowerDesigner Logical Data Model
Create or modify messages in the RAP Messages model.
Developing a RAP Message Template from the RAP Messages Model
Export message definitions to a RAP template file.
Converting a RAP Messages Model to a RAPCache or RAPStore Model
For RAPCache, generate a Sybase Adaptive Server Enterprise model. For RAPStore, generate a Sybase IQ model.
Converting a RAPCache or RAPStore Model to a RAP Messages Model
Generate the RAP Messages logical model from either the RAPCache or RAPStore physical data model.
Impact and Lineage Analysis
With impact and lineage analysis, you can determine the full impact of changes to any object in the integrated model.

Parent topic: Customizing the RAP Messages and Schema