- creates the profiler element
create-profiler [--help] [--target target_name] [--classpath classpath] [--nativelibpath native_library_path] [--enabled=true] [--property(name=value)[:name=value]*] profiler_name
The create-profiler subcommand creates the profiler element. A server instance is tied to the profiler by the profiler element in the Java configuration. Only one profiler exists at a time. If you attempt to create a profiler while one already exists, an error message is displayed.
For changes to take effect, the server must restarted.
This subcommand is supported in remote mode only.
Displays the help text for the subcommand.
This option specifies the target on which you are creating a profiler. Valid values are
Creates the profiler for the default server instance. This is the default value.
Creates the profiler for the named configuration
Creates the profiler for every server instance in the cluster
Creates the profiler for a particular server instance
Java classpath string that specifies the classes needed by the profiler.
This path is automatically constructed to be a concatenation of the GlassFish Server installation relative path for its native shared libraries, standard JRE native library path, the shell environment setting (LD_LIBRARY_PATH on UNIX) and any path that may be specified in the profile element.
Profiler is enabled by default.
Name/value pairs of provider-specific attributes.
Name of the profiler.
Example 1 Creating a Profiler
This example creates a profiler named sample_profiler.
asadmin> create-profiler --classpath /home/appserver/ --nativelibpath /u/home/lib --enabled=false --property defaultuser=admin:password=adminadmin sample_profiler Created Profiler with id = sample_profiler
subcommand executed successfully
error in executing the subcommand