Command Line Tools (Preview/Unstable) - Not recommanded to use in production environment
The following commands are located under "dist" subdirectory.
PSDL Compiler
Command Name : psdlc
Usage Generate Corba stub files based on the input PSDL definition. The PSDL compiler is based on the IDL compiler, so the command options for IDL compiler are also available in psdlc command.
Command options Description
-release Show version number.
-database Select database persistence, default is memory persistence.
-file Select file persistence.
-noapi Don't generate the standard API from PSDL.
-nowrapper Don't generate wrapper from PSDL.
-wrapper [wrapper_name] Set a external wrapper for file generation.
e.g.
# generate C# files

command prompt>psdlc -I ../../../PSS_Idl -lang CS ../../../Psdl/offer.psdl

Note : psdlc requires to import other Corba IDL definition for IDL interpretation.
Remember to specify the location of the IDLs come from OMG by using -I command option.
Interface Repository Service
Command Name : irsvc
Usage
e.g.
IR Loader
Command Name : irloader
Usage
Command options Description
-I[include file directory] Define include directories
-D Specify a symbol equivalent to #define
-verbose Activate the vorbose mode
e.g.
Notification Service
Command Name : notifysvc
Usage
Command options Description
-naming Bind into naming service.
-help Print the help message.
-printior Print IOR to stderr.
-usedefault Run on default port.
e.g.
Trader Service
Command Name : tradesvc
Usage
Command options Description
-ir Use Interface Repository for type checking.
-ior Generate a IOR for the lookup interface into a file name 'looking.ior'. If the service type repository is embedded, it is bound with the following name : ServiceTypeRepository.
-naming Bind the Lookup interface to the naming service with following name : TradingService

If the service type repository is embedded, it is bound with the following name : ServiceTypeRepository

-tradername [name] Specify the trader name from command line.
e.g. -tradername foo
-url Specify the service type repository url : -url corbaname::#bar
-persistence USe this option to start the trader under a persistent mode.
-namingpath [name] Name the naming service to bind the lookup interface:

-namepath MyPath implies the lookup interface to be bound with the MyPath/Lookup

e.g.
Trader Repository
Command Name : traderepos
Usage
Command options Description
-ir Use Interface Repository for checking.
-ior Generate a IOR for the lookup interface into a file named 'lookup.ior'. If the service type repository is embedded, another file is generated 'strep.ior' for it.
-naming Bind the Lookup Interface to the naming service with the name : TradingService.

If the service repository is embedded, it is bound with the name : ServiceTypeRepository.

-tradername Specify the trader name from the command line :
e.g. -tradername foo
-url Specify the service type repository URL.
e.g. -url corbaname::#bar
-persistence Use this option to start the trader under a persistent mode.
-namingpath Name for the naming service to bind the lookup interface:

-namingPath MyPath implies the Lookup Interface to be bound with the MyPath/Lookup

e.g.
Trader STDL Compiler
Command Name : stdlc
Usage
Command options Description
-release Show version number.
-export Generate a class file for a Service Type that exports an offer.
e.g.
IDL3 Compiler
Command Name : idl3c
Usage
Command options Description
-release Show version number.
-equivalent [idl_file_name] Select a target language for code generation
-nojava Don't generate implemenation files. This option will be renamed to -noimpl in future.
e.g.
CIDL Compiler
Command Name : cidlc
Usage
Command options Description
e.g.
/pre>
CCM Service
Command Name : ccmsvc
Usage
e.g.
Home Finder
Command Name : homefinder
e.g.
CCM Deloyer
Command Name : deploy [CCMProjectFile.xml] [-packging | -deployement | -clean ]
Usage
Command options Description
-packaging components and containers described in the project file will be packaged in archives.
-deployment components and containers described in the project file will be deployed in servers.
-clean components and containers described in the project file will be deleted after deployment.
e.g.