CentraSite Documentation : CentraSite Developer’s Guide : Application Framework : Mapping Beans to Registry Objects with Annotations : Generating Beans with the Command Line
Generating Beans with the Command Line
You can generate CSAF registry beans using the command line tool CentraSiteCommand.cmd (Windows) or CentraSiteCommand.sh (UNIX). The command line tool is located in <SuiteInstallDir>/CentraSite/utilities.
If you start the command line tool with no parameters, you receive a help text summarizing the required input parameters.
The parameters of the command are case-sensitive, so for example the parameter -url must be specified as shown and not as -URL.
If you omit the passwords from the command, you will be prompted to provide them.
To generate registry beans, use a command GenerateCSAFBeans of the following format:
On Windows
GenerateCSAFBeans.cmd -user <USERNAME> -pass <PASSWORD>
-url <CENTRASITE-URL> -typename <TYPENAME> -interfacepackage <INTERFACEPACKAGE>
-implpackage <IMPLPACKAGE> -destination <DESTINATION>
On UNIX
GenerateCSAFBeans.sh -user USERNAME -pass PASSWORD -url CENTRASITE-URL
-typename TYPENAME -interfacepackage INTERFACEPACKAGE -implpackage IMPLPACKAGE
-destination DESTINATION
Input Parameters
The following table describes the complete set of input parameters that you can use with the GenerateCSAFBeans utility:
Parameter
Description
USERNAME
Required. Your CentraSite user ID.
PASSWORD
Required. The password for your CentraSite user account.
CENTRASITE-URL
Required. The fully qualified URL for the CentraSite registry/repository.
If you omit this parameter, the importer assumes that the registry/repository resides at http://localhost:53307/CentraSite/CentraSite.
Note:  
If the registry/repository is running on a different machine and port number, you can use this parameter to specify its location instead of using the individual -h and -p parameters. (If you specify the -dburl parameter with the -h and/or -p parameters, the -h and -p parameters will be ignored.)
TYPENAME
Required. The namespace and name of the type to be generated (mandatory). Example: {http://test}TestService. Or, the name of the virtual type to be generated. Example: "Virtual service" Note: The quotation marks are necessary, in order that "Virtual service" is parsed as a single token.
INTERFACEPACKAGE
Required. The name of the package in which the interfaces should be generated. For example: com.sag.generated
IMPLPACKAGE
Required. The name of the package in which the implementation should be generated. For example: com.sag.generated.impl
DESTINATION
Required. The location where the generated bean will be stored.
Copyright © Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback