seedispatch: start a dispatcher


seedispatch parameter parameter . . 

Starts a self-hosted dispatcher and optional start listener, SEP, and console viewer processes. An event monitor starts if one is not already started.


Automatically start self-hosted SEP process.
Automatically start a listener process.
A self-hosted SEP process must be started manually. This is the default.
Do not display utility welcome and copyright messages.
Do not start a console viewer process. If this parameter is omitted, a console viewer process starts automatically.
Starts the console viewer in a separate console window.
Do not wait for key press before existing. Used in conjunction with -was.
Name of the region to associate with a started listener and console viewer. The default is ESDEMO.

Passed to the started console viewer process, or ignored if -nocv is specified. Prefixes each console message with the date and time it was created.

You can also enter a numeric value to specify the width of the console window. If the value for <number-of-columns> is greater than the maximum width supported for a Windows Console, the value is set to the maximum width.

Name of the database server instance that hosts the region database. For example:
Default database server on the local machine: -usedb
Default database server on the local machine, identical to -usedb: -usedb:(local)
Specific database server on the local machine: -usedb:(local)\SQLEXPRESS
Default database server instance on a specific machine (SC1 used in example) -usedb:SC1
Specific database server instance on a specific machine (SC1, SQLEXPRESS used in example for machine name, database server name) -usedb:SC1\SQLEXPRESS
Note: Parameter values are not case sensitive.
The command output displays all of the messages that the command generates.
Use a WAS-hosted dispatcher instead of self-hosting. With this parameter, seedispatch starts the console viewer and/or listener, depending on other command-line parameters. A WAS process running under IIS handles dispatching.
Use a WAS-hosted SEP. This parameter is only required if -was is not specified. A WAS-hosted dispatcher always uses a WAS-hosted SEP.

Using a configuration file with seedispatch

You can use a seedispatch.config configuration file to configure the behavior of seedispatch. In the current release, the maximum TCP and named pipe connections supported by the exposed WCF services, the default port for the WCF services, and CTF tracing can be configured.

The following statements show how to use a configuration file to specify a maximum of 20 connections for each protocol.
  <sectionGroup name="MicroFocus.SEE.Dispatch">
    <section name="services" type="System.Configuration.NameValueSectionHandler" />
    <add key="NetNamedPipe.maxConnections" value="20" />
    <add key="NetTcp.maxConnections" value="20" />

Example: Starting a self-hosted dispatcher

The following command:
  • Starts a self-hosted dispatcher
  • Automatically starts a self-hosted SEP
  • Automatically starts a listener and console viewer for the ESDEMO region
seedispatch -region:ESDEMO -usedb:(local)\SQLEXPRESS -automatic

Example: configuring a WAS-hosted dispatcher and SEP

The following command configures a WAS-hosted Dispatcher and SEP. This example starts a listener and console viewer for the ESDEMO region. The console viewer starts with a 132-column wide window and the date and time of creation prefixes each message output.

Note: The -nowait parameter terminates the seedispatch process once the other processes start.
seedispatch -was -nowait -region:ESDEMO -usedb:(local)\SQLEXPRESS 
-automatic -listener -showtime:132