1. Introduction to the Development Environment for Enterprise Server Add-On Components
3. Extending the Administration Console
4. Extending the asadmin Utility
About the Administrative Command Infrastructure of Enterprise Server
Representing an asadmin Command as a Java Class
Specifying the Name of an asadmin Command
Ensuring That an AdminCommand Implementation Is Stateless
Example of Adding an asadmin Command
Adding Parameters to an asadmin Command
Representing a Parameter of an asadmin Command
Identifying a Parameter of an asadmin Command
Specifying Whether a Parameter Is an Option or an Operand
Specifying the Name of an Option
Specifying the Long Form of an Option Name
Specifying the Short Form of an Option Name
Specifying the Acceptable Values of a Parameter
Specifying the Default Value of a Parameter
Specifying Whether a Parameter Is Required or Optional
Example of Adding Parameters to an asadmin Command
Adding Message Text Strings to an asadmin Command
Enabling an asadmin Command to Run
Setting the Context of an asadmin Command
Examples of Extending the asadmin Utility
5. Adding Container Capabilities
6. Packaging, Integrating, and Delivering an Add-On Component
The brand in the Enterprise Server command-line interface (CLI) consists of the product name and release information that are displayed in the following locations:
In the string that the version(1) command displays
In each entry in the server.log file
If you are incorporating Enterprise Server into a new product with an external vendor's own brand name, change the brand in the Enterprise Server CLI.
To change the brand in the Enterprise Server CLI, create an OSGi fragment bundle that contains a plain text file that is named src/main/resources/BrandingVersion.properties.
In the BrandingVersion.properties file, define the following keyword-value pairs:
product_name=product-name abbrev_product_name=abbrev-product-name major_version=major-version minor_version=minor-version build_id=build-id version_prefix=version-prefix version_suffix=version-suffix
Define each keyword-value pair on a separate line of the file. Each value is a text string without quotes.
The meaning of each keyword-value pair is as follows:
Specifies the full product name without any release information, for example, Sun GlassFish Enterprise Server.
Specifies an abbreviated form of the product name without any release information, for example, Sun GlassFish.
Returns the product major version, for example, 3
Specifies the product minor version, for example, 0.
Specifies the build version, for example, build 17.
Specifies a prefix for the product version, for example, v.
Specifies a suffix for the product version, for example, Prelude.
This example shows the content of the BrandingVersion.properties for defining the product name and release information of Sun GlassFish Enterprise Server v3.0 Prelude, build 17. The abbreviated product name is sun-glassfish.
product_name=Sun GlassFish Enterprise Server abbrev_product_name=sun-glassfish major_version=3 minor_version=0 build_id=build 17 version_prefix=v version_suffix=Prelude