Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

eventc(1) [debian man page]

EVENTC(1)																 EVENTC(1)

NAME

       eventc - create a CORBA EventChannel and register it in the naming service

SYNOPSIS

       eventc [-n channel-name] [-N factory-name] [-c nanoseconds] [-i id] [-p num] [-q num] [-R milliseconds] [-t repository-id] [-vh]
	      [-ORBparameter value] [factory-uri]

DESCRIPTION

       eventc contacts the omniEvents server to request an Event Channel. The Event Channel is created within the the omniEvents  process.  eventc
       then registers the created Event Channel with the Naming Service, and exits.

       factory-uri: The factory may be specified as a URI. This may be an IOR, or a corbaloc::: or corbaname::: URI.

       Example: eventc corbaloc::localhost:11169/omniEvents

       If the factory-uri argument is not supplied, then the -N factory-name option is used to look up the server in the CORBA Name Service.

OPTIONS

       -n channel-name
	      Sets the CORBA Name Service name for the new EventChannel CORBA object.

	      Format for channel-name: [CONTEXT-ID[.CONTEXT-KIND]/]*OBJECT-ID[.OBJECT-KIND]

	      Examples: foo, foo.bar, foo.bar/baz/qux, foo/bar/baz.qux.

	      The default is EventChannel

       -N factory-name
	      The  CORBA  Name Service name for the EventChannelFactory CORBA object. The default value is EventChannelFactory. This value is only
	      used when the factory-uri argument is not supplied.

       -c nanoseconds
	      Sets the CyclePeriod_ns parameter of the new event channel.

       -i id  Set the InsName of new event channel, to enable access via corbaloc.

       -p num Sets the MaxNumProxies parameter of the new event channel.

       -q num Sets the MaxQueueLength parameter of the new event channel.

       -R milliseconds
	      Sets the PullRetryPeriod_ms parameter of the new event channel.

       -t repository-id
	      Sets the FilterId parameter of the new event channel.

       -v     Output the CORBA IOR of the new EventChannel CORBA object.

       -h     Display a short summary of command-line options.

       -ORBparameter value
	      Standard omniORB options. see omniORB documentation for details. This option is commonly used to set the omniORB traceLevel, in  or-
	      der to get more detailed output.

	      Example: -ORBtraceLevel 5

ENVIRONMENT VARIABLES

       OMNIORB_CONFIG
	      The location of the omniORB configuration file.

COPYRIGHT

       Copyright (C) 2003-2005 Alex Tingle, 1999 Paul Nader.

       This  is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
       LAR PURPOSE.

																	 EVENTC(1)

Check Out this Related Man Page

OMNIMAPPER(8)						      System Manager's Manual						     OMNIMAPPER(8)

NAME

       omniMapper - Simple proxy for CORBA naming service from omniORB

SYNOPSIS

       omniMapper [options]

DESCRIPTION

       This manual page documents briefly the omniMapper command.

       omniMapper is a simple daemon which listens on port 2809 (or any other port) and redirects IIOP requets for configured object keys to asso-
       ciated persistent IORs.	It can be used to make a naming service (even an old non-INS aware version of omniNames or other ORB's naming ser-
       vice)  appear on port 2809 with the object key NameService.  The same goes for any other service you may wish to specify, such as an inter-
       ace repository.

OPTIONS

       A summary of options is included below.	For a complete description, see the HTML pages included in the omniorb4-doc package.

       -port port
	      This allows you to choose a port other than 2809 to listen on.

       -config config_file
	      This specifies a location for the configuration file.  The default name is /etc/omniMapper.cfg.

       -v     omniMapper does not normally print anything; this option makes it verbose so it prints configuration information and a record of the
	      redirections it makes to standard output.

CONFIGURATION FILE

       The  configuration file is very simple.	Each line contains a string to be used as an object key, some white space and an IOR (or any valid
       URI) that it will redirect that object key to.  Comments should be prefixed with a # character.	For example:
	   # Example omniMapper.cfg
	   NameService	       IOR:000f...
	   InterfaceRepository IOR:0100...

SEE ALSO

       omniNames(8).
       The programs are documented fully by the HTML documentation in the omniorb4-doc package.

AUTHOR

       omniMapper was written by Duncan Grisby <duncan@grisby.org>

       This manual page was written by Floris Bruynooghe <floris.bruynooghe@gmail.com>, for the Debian project (but may be used by others).

								    30 Apr 2007 						     OMNIMAPPER(8)
Man Page