1. Overview of Enterprise Server Administration
Default Settings and Locations
Instructions for Administering Enterprise Server
4. Administering the Virtual Machine for the Java Platform
6. Administering Web Applications
7. Administering the Logging Service
8. Administering the Monitoring Service
9. Administering Life Cycle Modules
10. Extending Enterprise Server
Part II Security Administration
11. Administering System Security
12. Administering User Security
13. Administering Message Security
Part III Resources and Services Administration
14. Administering Database Connectivity
15. Administering EIS Connectivity
16. Administering Internet Connectivity
17. Administering the Object Request Broker (ORB)
18. Administering the JavaMail Service
19. Administering the Java Message Service (JMS)
20. Administering the Java Naming and Directory Interface (JNDI) Service
21. Administering Transactions
A profiler generates information used to analyze server performance. The following topics are addressed here:
A server instance is tied to a particular profiler by the profiler element in the Java configuration. If JVM options are created for a profiler, the options are used to record the settings needed to activate a particular profiler. Use the create-profiler subcommand in remote mode to create the profiler element in the Java configuration.
Only one profiler can exist. If a profiler already exists, you receive an error message that directs you to delete the existing profiler before creating a new one.
Ensure that the server is running.
Remote subcommands require a running server.
Create a profiler by using the create-profiler(1) subcommand.
Information about properties for the subcommand is included in this help page.
To apply your changes, restart Enterprise Server.
See To Restart a Domain.
This example creates a profiler named sample_profiler.
asadmin> create-profiler --classpath=/home/appserver/ --nativelibrarypath=/u/home/lib --enabled=false --property=defaultuser=admin:password=adminadmin sample_profiler Command create-profiler executed successfully.
You can also view the full syntax and options of the subcommand by typing asadmin help create-profiler at the command line.
Use the delete-profiler subcommand in remote mode to delete the profiler element from the Java configuration. You can then create a new profiler.
Ensure that the server is running.
Remote subcommands require a running server.
Delete the profiler by using the delete-profiler(1) subcommand.
To apply your changes, restart Enterprise Server.
See To Restart a Domain.
This example deletes the profiler named sample_profiler.
asadmin> delete-profiler sample_profiler Command delete-profiler executed successfully.
You can also view the full syntax and options of the subcommand by typing asadmin help delete-profiler at the command line.