Документ взят из кэша поисковой машины. Адрес оригинального документа : http://rtm-cs.sinp.msu.ru/manual/mico/doc/node26.html
Дата изменения: Mon Jun 7 21:54:58 1999
Дата индексирования: Mon Oct 1 21:21:37 2012
Кодировка:

BOA Daemon

 

The BOA daemon (micod) is the part of the basic object adapter that activates object implementations when their service is requested. Moreover micod contains the implementation repository. To make all MICO applications use a single implementation repository you have to take similar actions as for the interface repository as described in section 4.2. That is you have to tell micod an address to bind to using the -ORBIIOPAddr option and tell all MICO applications this address by using the -ORBImplRepoAddr option. For example:

  micod -ORBIIOPAddr inet:<micod-host-name>:9999

Now you can run all MICO applications like this:

  some_mico_application -ORBImplRepoAddr inet:<micod-host-name>:9999

or you can put the option into .micorc and run some_mico_application without arguments.

micod understands the following command line arguments:

-help

 
Show a list of all supported command line arguments and exit.

-forward

 
This option instructs micod to make use of GIOP location forwarding, which results in much better performance (there is nearly no overhead compared to not using micod at all). Unfortunately this requires some client side GIOP features that some ORBs do not support properly although prescribed in the CORBA specification. Therefore you may encounter problems when using clients implemented using such broken ORBs. That is why this feature is off by default.

-db <database file>

 
Specifies the file name where micod should save the contents of the implementation repository when exiting. When micod is restarted afterwards it will read the file given by the --db option to restore the contents of the implementation repository.