Morningstar Quotes Feed Input Adapter

Name: Use this required field to specify or change the name of this instance of this component, which must be unique in the current EventFlow module. The name must contain only alphabetic characters, numbers, and underscores, and no hyphens or other special characters. The first character must be alphabetic or an underscore.

Adapter: A read-only field that shows the formal name of the adapter.

Class name: Shows the fully qualified class name that implements the functionality of this adapter. If you need to reference this class name elsewhere in your application, you can right-click this field and select Copy from the context menu to place the full class name in the system clipboard.

Start options: This field provides a link to the Cluster Aware tab, where you configure the conditions under which this adapter starts.

Enable Error Output Port: Select this check box to add an Error Port to this component. In the EventFlow canvas, the Error Port shows as a red output port, always the last port for the component. See Using Error Ports to learn about Error Ports.

Description: Optionally enter text to briefly describe the component's purpose and function. In the EventFlow Editor canvas, you can see the description by pressing Ctrl while the component's tooltip is displayed.

This section describes the properties on the Adapter Properties tab in the Properties view for the Morningstar Quotes Feed adapter.

This section describes the properties on the Adapter Properties tab in the Properties view for the Morningstar Quotes Feed adapter.

Use the Edit Schemas tab to specify the schema for message types selected on the Adapters Properties tab. See Using the Adapter section below for information on field names to use.

For general instructions on using the Edit Schemas tab, see Defining Input Streams.

Use the settings in this tab to allow this operator or adapter to start and stop based on conditions that occur at runtime in a cluster with more than one node. During initial development of the fragment that contains this operator or adapter, and for maximum compatibility with TIBCO Streaming releases before 10.5.0, leave the Cluster start policy control in its default setting, Start with module.

Cluster awareness is an advanced topic that requires an understanding of StreamBase Runtime architecture features, including clusters, quorums, availability zones, and partitions. See Cluster Awareness Tab Settings on the Using Cluster Awareness page for instructions on configuring this tab.

Use the Concurrency tab to specify parallel regions for this instance of this component, or multiplicity options, or both. The Concurrency tab settings are described in Concurrency Options, and dispatch styles are described in Dispatch Styles.

All Morningstar data messages are composed of a small header and a variable number of field ID-data type-value triplets. A Field Dictionary is used to map a Morningstar Field ID to a StreamBase field name.

A Morningstar data message header has four fields that are common across all data messages. These fields are:

Unlike all other Morningstar fields, these field names are not configurable via the field dictionary.

For message types that are selected, Morningstar field IDs that appear in Morningstar messages and do not have a corresponding StreamBase field name defined cause a warning to be emitted by StreamBase Server. This warning can be disabled by selecting the Skip Missing Fields option.

Field names defined in a StreamBase message type schema that do not appear in a Morningstar message are set to null. Since individual Morningstar messages within a single message type can have a varying number of fields, it is not uncommon to have StreamBase tuples with a varying number of null fields.

All Morningstar data messages are composed of a variable number of field ID-data type-value triplets. Morningstar field IDs are integer values. An optionally configurable field dictionary is used to map a Morningstar field ID integer to a StreamBase field name. A default field dictionary is included with the StreamBase adapter and is used if a custom dictionary is not specified. The default Morningstar field ID to StreamBase field name mapping can be seen in the file MSFieldDictionary.csv delivered as part of the Morningstar sample application.

Some field IDs are common across many message types, while other field IDs are unique to individual message types, security types, and so on. You must consult Morningstar documentation to determine the field IDs provided by various message types, and what fields are of particular interest.

An individual field ID always corresponds to a particular StreamBase field name. As Morningstar messages are parsed, their field IDs are looked up in the field ID dictionary to yield a StreamBase field name. The resulting StreamBase field name is used to set the field in the output tuple with the value parsed out of the Morningstar Field ID-value pair.

Morningstar value data types are represented by one of four StreamBase data types:

Trying to set a Morningstar data type to an incompatible StreamBase data type results in a warning message at runtime.

The Morningstar Quote Feed adapter has one command input port. The schema for this port has the following fields:

The StreamBase Morningstar Quotes Feed adapter has one output status port, plus a configurable number of data message ports.

The Morningstar Quotes Feed adapter has an optional Admin output port plus one or more data message output ports. The schema for these ports are defined in the Edit Schemas tab in the adapter's Properties view. The field names you specify must be present in the field dictionary currently being used.

The seven data message ports have four fields derived from the data header, and have fixed field names. These are: Symbol, SecurityType, ExchangeId, MarketCenter.

The status output port will output tuples giving relevant information.

The schema for the status output port is:

The following is a list of status outputs and the associated objects:

Add an instance of the adapter to a new StreamBase EventFlow application as follows: