nameclt(1) [debian man page]
nameclt(1) General Commands Manual nameclt(1) NAME
nameclt - Naming Service client SYNOPSIS
nameclt [-ior <object-reference>] [-advanced] <operation> DESCRIPTION
The nameclt command invokes operations on the Naming Service. The allowed operations are: list <context-name> lists contexts and objects bound in the context with the specified name. bind_new_context <context-name> binds name to a new context, and returns the stringified context IOR. remove_context <context-name> unbinds and destroys the named context, as long as it is empty. bind <object-name> <stringified-IOR> binds name to object. unbind <object-name> unbinds name and object. resolve <object-name> returns stringified IOR bound to specified name. OPTIONS
-ior NameService-object-reference Use the given stringified IOR as the "root" context of the naming service. By default, nameclt uses the object reference returned by calling CORBA::ORB::resolve_initial_references("NameService"). -advanced Allow advanced operations. These are operations which should not normally need to be used. They may however be useful for testing the naming service and also for cleaning up in the event of a client messing up the namespace. The operations are: bind_context <context-name> <stringified-IOR> binds name to context. rebind <object-name> <stringified-IOR> binds name to object even if binding already exists. rebind_context <context-name> <stringified-IOR> binds name to context even if binding already exists. new_context returns stringified IOR for a new context. destroy destroys the naming context given with -ior flag. SEE ALSO
omniNames(1) AUTHOR
Tristan Richardson, ORL (Olivetti & Oracle Research Laboratory) ORL
7 May 97 nameclt(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)