Migrating RAP - The Trading Edition

A migration installation allows migration from the previous RAP installation to the new RAP installation. Run a migration installation on each machine that has a RAP component on it. Run the migration installation for the RAPCache Database Server separately and install it in the existing installation directory. Install all other components into a new RAP R3 installation directory.

Upgrade installer actions

During the migration, the installer:

Assigns default port values in the 3000 – 4000 range to all publisher components. Port values are validated during installation, and if a defined port is already in use, the installer displays two popup messages. The first message tells you that the port number is already in use and an alternative port will be selected. The second message provides the new port assignment. If your Network Administrator chooses a different set of port values, record these items on your worksheet, and replace the default value with these items.

Lets you install the RAPCache Database Server and RAPCache Subscriber separately. Running the installations separately installs the RAPCache Database Server on the target machine with ASE 15.0.3 ESD #1 defaults, and sets the host name to the install machine.

Lets you install the RAPStore Database Server and RAPStore Subscriber separately. Running the installations separately installs the RAPStore Database Server on the target machine with Sybase IQ 15.1 defaults, and sets the host name to the install machine. If you install the RAPStore Subscriber at the same time, this component inherits all appropriate server connection settings, but prompts you for the appropriate data channels and publisher configuration as well as the location of the RAPStore Database Server.

Assigns all appropriate port values for Operations Console. If you install Operations Console at the same time you install RAPCache and RAPStore, the installer populates the appropriate Host and port values for these items. If not, the Host fields are left empty and the port is the appropriate default for the database (5000 for RAPCache and 2638 for RAPStore).

Premigration Tasks
Premigration involves performing specific tasks and collecting specific information before migrating RAP.
Running the Migration Installer from the Command Line
Run the migration installation using the specified command line. Using the standard command launches the full installer instead of the migration installer.
Migrating the RAPCache Database Server
The RAPCache Database Server is one of the two options that are part of the RAPCache System.
Migrating the Demo Feed Handler
Demo Feed Handler is a Sybase feed handler that reads comma-delimited market data from a demo file (STOCK_QUOTE.csv). This component is intended to demonstrate network message flow and to help developers become familiar with the Publisher API.
Migrating the FAST Feed Handler
The FAST Feed Handler connects directly to market data feeds, receives FAST-encoded messages, decodes the data, and makes the decoded data available to the message handler plug-in.
Migrating the Publisher API
The Publisher API formats incoming market data messages and forwards those messages to a subscriber. This API is used by feed handlers (Demo Feed Handler and FAST Feed Handler), and developers who want to map proprietary market data into RAP.
Migrating the RAPCache Subscriber
The RAPCache Subscriber is one of the two options that are part of the RAPCache System.
Migrating the RAPStore System
The RAPStore System includes two options: RAPStore Database Server and RAPStore Subscriber.
Migrating the Demo Subscriber
Demo Subscriber processes message packets that arrive over data streams from a publisher. The purpose of the Demo Subscriber is to demonstrate, in conjunction with the Demo Feed Handler, message flow through RAP.
Migrating the Operations Console
Operations Console is a web-based interface that provides administration and monitoring functions.
Postmigration Tasks
After you migrate RAP, copy the specified configuration files into the new installation directory, update the IQ plug-in, update the RAPStore database, and verify the successful migration of the RAP components.