|
|
|
|
|
|
[-b bucketcount]
[-c]
[-d]
[-f filename]
[-M maxiterators]
[-p [persiststoragefilename] ]"The server process for the CORBA Name Service provides a CORBA CosNaming compliant name service. You need to define the server process for the CORBA Name Service and its options in the UBBCONFIG file for your Oracle Tuxedo application as you do any other server process used by your Oracle Tuxedo application. Enter the cns command-line options after the double dash (--) in the CLOPT parameter of the UBBCONFIG file. The command-line options are as follows:-b bucketcountCompresses the persistent storage file when the server process for the CORBA Name Service starts. Over time the persistent storage file can grow in size as naming context and application objects are added and removed from the namespace. Compression reduces the size of the persistent storage file to a minimum. Dangling bindings are removed during compression. Dangling bindings are left in the namespace after the object the binding is associated with is deleted from the namespace. The -p command-line option must be specified when specifying the -c command-line option.Directs the server process for the CORBA Name Service to delete orphan contexts when the server process starts. An orphan context is a context that is not bound to any other context. It may never have been bound or it may have been bound to a context and the binding was destroyed either explicitly or as a side-effect of a rebind. The -p command-line option must be specified when specifying the -d command-line option.-f filename-M maxiteratorsBinding iterators are created when a client application uses the CosNaming::NamingContext::list()method. The client application should use the CosNaming::BindingIterator::destroy()method to delete a binding iterator when the client application is done using the binding iterator.If a client application does not specifically delete binding iterators, the server process for the CORBA Name Service deletes the binding iterators when the number reaches the value specified in the -M command-line option. Once the maximum number of binding iterators is reached, any attempt to create a new binding iterator causes the server process for the CORBA Name Service to destroy a binding iterator currently in use by the client application.Binding iterators are deleted using a least-recently-used algorithm. The default value is 20. A value of 0 indicates that there is no maximum number of binding iterators (meaning binding interators are never destroyed by the server process for the CORBA Name Service and the associated memory is not released). If a value of 0 is specified, the client application must explicitly use the CosNaming::BindingIterator::destroy() method to delete outstanding binding iterators.Directs the server process for the CORBA Name Service to save a copy of the current namespace to persistent storage using the specified file. If a filename is not specified, the value of the CNS_PERSIST_FILE environment variable is used. If the CNS_PERSIST_FILE environment variable is not set, the following files are used:
CosNaming::NamingContext::unbind() method.A list of returned bindings where each element is a binding containing a Name representing a single NameComponent object. Each Name is a simple name, that is, a name sequence of length 1. The number of bindings in the list does not exceed the value of how_many.A reference to a BindingIterator object for use in traversing the rest of the bindings.The specified Name has zero name components or one of the first name components did not resolve to a naming context.The Name or one of its components could not be found.This method returns a sequence of name bindings. If more name bindings exist than can fit in the bl list, a BindingIterator object is returned. The BindingIterator object can be used to get the next set of bindings. The BindingList (C++) object can return less than the requested number of bindings if it is at the end of the list. If bi returns a NULL reference, then bl contains all of the bindings.This method is similar to the bind() method. The difference is that the rebind method does not raise the AlreadyBound exception. If the specified Name has already been bound to another object, that binding is replaced by the new binding.A Name data structure, initialized with the desired name for the object.The specified Name data structure has zero name components or one of the first name components did not resolve to a naming context.The Name or one of its components, could not be found. If this exception is raised because the binding already exists or the binding is of the wrong type, the rest_of_name member of the exception has a length of 1.Naming contexts bound with the rebind()method do not participate in name resolution when compound names are passed to be resolved.This method is similar to the bind_context() method. The difference is that the rebind_context method does not raise the AlreadyBound exception. If the specified Name has already been bound to another object, that binding is replaced by the new binding.A Name data structure, initialized with the desired name for the object.The NamingContext object to be rebound.The specified Name data structure has zero name components or one of the first name components did not resolve to a naming context.The component of a name does not identify a binding or the type of binding is incorrect for the operation being performed. If this exception is raised because a binding already exists or it is of the wrong type, the rest_of_name member of the exception has a length of 1.Naming contexts bound with the rebind_context method do not participate in name resolution when compound names are passed to be resolved.A Name data structure, initialized with the desired name for the object.The specified Name data structure has zero name components or one of the first name components did not resolve to a naming context.The specified Name must exactly match the name used to bind the object. The CORBA Name Service does not return the type of the object. Client applications are responsible for narrowing the object to the appropriate type.Performs the inverse operation of the bind() method, removing the binding associated with the specified Name.A Name data structure, initialized with the desired name for the object.The specified Name data structure has zero name components or one of the first name components did not resolve to a naming context.This method removes the binding between a name and an object. It does not delete the object. Use the CosNaming::NamingContext::unbind() method and then the CosNaming::NamingContext::destroy() method to delete the object.The NamingContextExt object provides methods to use URLs and stringified names in the CORBA Name Service. The NamingContextExt object is derived from the NamingContext object. Note that the root of the CORBA Name Service is a NamingContextExt object (which means the root is also a NamingContext object). No special operation is needed to obtain a reference to a NamingContextExt object. Listing 2‑2 shows the OMG IDL for the NamingContextExt object.Listing 2‑2 OMG IDL for the NamingContextExt ObjectTakes a stringified name, converts it to a Name, and resolves it.This is a convenience method that performs a resolve in the same manner as the
CosNaming:NamingContext::resolve() method. The method accepts a stringified name as an argument instead of a Name object. The method returns errors if the stringified name is invalid or if the method cannot bind it.Takes a stringified name and returns a Name object.The stringified name to be resolved to a Name object.This method accepts a stringified name and returns a Name object. The method returns errors if the name is invalid.Returns a Name object.Accepts a Name object and returns a stringified name.The Name object to be converted to stringified nameThis method accepts a Name object and returns a stringified name. It returns errors if the name is invalid.The BindingIterator object allows a client application to walk through the unbounded collection of bindings returned by the list method of a
NamingContext object. Using the BindingIterator object, a client application can control the number of bindings obtained with each call. If a naming context is modified between calls to the methods of a BindingIterator object, the behavior of further calls to the next_one() method or the next_n() method is implementation specific.If a client application creates BindingIterator objects but never calls the destroy method, the client application can run out of resources. The CORBA Name Service is free to destroy binding iterators at any time and without warning to the client application. Client applications should be written to expect the OBJECT_NOT_EXIST exception from calls to a BindingIterator object and to handle this exception gracefully.Listing 2‑3 shows the OMG IDL for the BindingIterator object.Listing 2‑3 OMG IDL for BindingIterator ObjectDestroys the BindingIterator object and releases the memory associated with the object. Failure to call this method results in increased memory usage.If a client application invokes any operation on a BindingIterator object after calling the destroy method, the operation raises an OBJECT_NOT_EXIST exception.Returns a BindingList data structure containing the number of requested bindings from the list. The number of bindings returned may be less than the requested amount if the list is exhausted.A BindingList data structure containing no more than the requested number of bindings.Raised if the how_many parameter has a value of zero.CORBA::FALSE is returned when the list has been exhausted. Otherwise, CORBA::TRUE is returned.Returns the next Binding object in the list.The next Binding object from the list.CORBA::FALSE is returned when the list has been exhausted. Otherwise, CORBA::TRUE is returned.NamingContext cxtName rest_of_nameThis exception is raised if a Name is invalid. A name length of zero is invalid.This exception is raised when the destroy()method is used on a NamingContext object that contains bindings. A NamingContext object must be empty before it is destroyed.This exception is raised when a component of the name does not identify a binding, or if the type of binding is incorrect for the operation being performed. The why parameter explains the reason for the error. The rest_of_name parameter identifies the cause of the error. The following causes can appear: