!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! Name: opus_corba_objs_template
!
! Purpose:   Default OPUS CORBA object name-to-type mapping and server
!            configuration file template.
!
! Modification History:
!
!   Date       OPR         Who       Reason
! --------   -------   ------------  -----------------------------------------
! 11/28/00    42874    WMiller       Initial version
! 03/26/01    43520    WMiller       Place usable nodes in template
! 12/04/01    44741    WMiller       Add FILE BB server
! 04/24/03    47450    Sontag        Use OPUS_REMOTE_SHELL, and shift -n arg
! 10/21/03    49601    Sontag        Shift args for identification ease in 'ps'
! 05/25/04    50605    Sontag        Provide the default config as non-cluster
! 01/06/06    54853    WMiller       Document/default to new event server switch
! 03/26/10    64273    MSwam         Add svc.conf file (so far,needed for Linux)
! 06/16/10    64273    MSwam         back OUT the svc.conf (no longer needed)
! 09/28/10    65360    MSwam         REALLY back out svc.conf, completely
! 09/29/10    65360    MSwam         Sigh. OK, leave a placeholder for svc.conf
!                                      so that Solaris works as is, and Linux
!                                      can have the build_opuslogin tool fill
!                                      out the placeholder with a working value
!                                      for each user.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! The command used to start each server type (CONTEXT, EVENT, OSF, PSTAT, and 
! FILE) must be configured by the user in the file 
! OPUS_DEFINITIONS_DIR:opus_corba_objs. The server types map to executables
! in the following way:
!
! CONTEXT -> opus_env_server
! EVENT   -> opus_event_service
! PSTAT   -> opus_bb_server (with -t PSTAT)
! OSF     -> opus_bb_server (with -t OSF)
! FILE    -> opus_bb_server (with -t FILE)
!
!
! The command-line options for each server are listed below. Note, however,
! that the token ^F can be used in place of arguments that indicate the string
! object name. At startup, this token is replaced with the requested string 
! object name.
!
!
! opus_env_server [[-d OPUS_DEBUG_LEVEL] [-t thread_pool_size]
!                 [[ORB_arg0] ... [ORB_argN]] ]
! 
! where
!
!    OPUS_DEBUG_LEVEL = One of the enumerated message report levels of the 
!                       OAPI Msg class (e.g., ALL, INFO, ...) {default: INFO}
!    thread_pool_size = The number of threads to create for servicing clients
!                       of the bootstrap server {default: 3}
!    ORB_argN         = An ACE/TAO ORB option {default: ACE/TAO default ORB}
!
! opus_bb_server -t blackboard_type -i blackboard_ID [[-d OPUS_DEBUG_LEVEL] 
!                [-r polling_interval] [[ORB_arg0] ... [ORB_argN]] ]
! 
! where
!
!    blackboard_ID    = The string name of the blackboard
!    blackboard_type  = PSTAT, OSF, or FILE
!    OPUS_DEBUG_LEVEL = One of the enumerated message report levels of the 
!                       OAPI Msg class (e.g., ALL, INFO, ...) {default: INFO}
!    polling_interval = When BB_TYPE = FILE, the number of seconds in between
!                       polling attempts {default: 5}
!    ORB_argN         = An ACE/TAO ORB option {default: ACE/TAO default ORB}
!
! opus_event_service -i event_channel_ID [[-d OPUS_DEBUG_LEVEL] 
!                    [-c] [[ORB_arg0] ... [ORB_argN]] ]
! 
! where
!
!    event_channel_ID = The string name of the event channel.
!    OPUS_DEBUG_LEVEL = One of the enumerated message report levels of the 
!                       OAPI Msg class (e.g., ALL, INFO, ...) {default: INFO}
!    -c               = Use reactive consumer control to prevent event push
!                       delays in case of dead push consumers
!    ORB_argN         = An ACE/TAO ORB option {default: ACE/TAO default ORB}
!
!
! For example, a simple configuration which starts each server type is shown:
!
CONTEXT =  opus_env_server -ORBSvcConf -ORBStdProfileComponents 0 &
EVENT   =  opus_event_service -i ^F -c -ORBSvcConf -ORBStdProfileComponents 0 &
OSF     =  opus_bb_server -t OSF -i ^F -ORBSvcConf -ORBStdProfileComponents 0 &
PSTAT   =  opus_bb_server -t PSTAT -i ^F -ORBSvcConf -ORBStdProfileComponents 0 &
FILE    =  opus_bb_server -t FILE -i ^F -ORBSvcConf -ORBStdProfileComponents 0 &
!
! In a cluster environment, you may wish to use rsh (or $OPUS_REMOTE_SHELL)
! to start each server type on a designated node (e.g $HOST) as shown:
! 
! OSF = SUB[OPUS_REMOTE_SHELL] SUB[HOST] -n opus_bb_server -t OSF -i ^F -ORBStdProfileComponents 0 &
!
! *** NOTE: the file opus_corba_objs is accessed by the system through the
!           resource blackboard. This blackboard discards any comments in
!           the resource file.