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
Logs are rotated automatically based on settings in the logging.properties file. You can change these settings by using the Administration Console.
You can rotate the server log file manually by using the rotate-log subcommand in remote mode. The server log in the default location is immediately moved to a time-stamped file and a new server log is created.
Because log rotation is a dynamic operation, you do not need to restart Enterprise Server for changes to take effect.
Ensure that the server is running.
Remote subcommands require a running server.
Rotate a log by using the
rotate-log(1) subcommand.
This example moves the server.log file to yyyy-mm-dd_server.log and creates a new server.log file in the default location.
asadmin> rotate-log Command rotate-log executed successfuly.
You can also view the full syntax and options of the subcommand by typing asadmin help rotate-log at the command line.