Hi Bruce!
Naturally you can configure your applications however you see fit.
In the example
demo/IceStorm/clock, we use the file
config_service for IceBox, and the file
config for IceStorm, the publisher and the subscriber. If you look closely at
config_service, you'll notice that the IceStorm service is configured with the argument
--Ice.Config=config, which causes it to load the properties in
config.
To be more specific, IceBox requires the following properties in order to load IceStorm:
Code:
IceBox.ServiceManager.Endpoints=<sm-endpoints>
IceBox.Service.IceStorm=IceStormService,12:create
IceBox.DBEnvName.IceStorm=<dbdir>
IceStorm requires the following properties:
Code:
IceStorm.TopicManager.Endpoints=<icestorm-endpoints>
IceStorm.Publish.Endpoints=default
Publishers and subscribers need a proxy for the TopicManager. In this example they use the following property:
Code:
IceStorm.TopicManager.Proxy=IceStorm/TopicManager:<icestorm-endpoints>
Hope that helps,
- Mark