StreamBase Path Notation

The name of the StreamBase container hosting the application. Container names are either system, default, or a name you assign when creating a container. The following examples address two operators with the same name in separate containers:

container1.ReadOrders
default.ReadOrders

When containerName is omitted, the StreamBase container named default is assumed. Every EventFlow fragment has a default container named default, which contains the application's top-level module unless you explicitly create a non-default container. This means you can often omit the containerName portion of the address. For example, the following commands are equivalent when the server is running the Best Bids and Asks sample in the default StreamBase container:

epadmin --ad=adminport enqueue stream --path default.NYSE_Feed
epadmin --ad=adminport enqueue stream --path NYSE_Feed
sbc -p sbport enqueue default.NYSE_Feed
sbc -p sbport enqueue NYSE_Feed

Use the containerName portion of the address when you are addressing a non-default container, or when a name conflict would otherwise occur.

The name of a module that is either referenced explicitly in the fragment, or referenced implicitly by StreamBase. Implicit references occur when a component runs in separate or multiple parallel regions; in this case, StreamBase automatically creates a module for each running instance. There can be multiple moduleRefName levels in the address syntax.

The following line addresses an operator named SumOrders within a module reference named MWindowModuleRef1:

MWindowModuleRef1.SumOrders

The next example addresses a group of entities associated with an operator that you have configured, using the Concurrency tab of the operator's Properties view, to run in a parallel region. In each entity, the prefix references the module that StreamBase creates for the operator's parallel region.

MyOperator.InputStream1              (input stream)
MyOperator.out:MyOperator_1          (output stream)
MyOperator.schema:RetrieveLastOrders (schema)
MyOperator.MyOperator                (operator)

Finally, If you set a component to run in multiple parallel regions, you can address each region separately. The following example addresses two instances for the same operator, each running in its own parallel region.

default.Filter:0.Filter
default.Filter:1.Filter

The name of an individual stream, operator, schema, or queue.

In StreamBase Manager, you might also see a parallel region instance number appended to the entityName in the form entityName[:instanceNumber], using zero-based instance numbers. For example: Update_Bids_and_Asks:0, Update_Bids_and_Asks:1, and so on.