1. Overview of Enterprise Server Administration
Default Settings and Locations
Instructions for Administering Enterprise Server
About Administering Domains (or Servers)
Creating, Logging In To, and Deleting a Domain
Starting and Stopping a Domain
Automatically Restarting a Domain
To Automatically Restart a Domain on Solaris 10
To Restart Automatically on Linux
To Prevent Service Shutdown When User Logs Out on Windows
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
The following topics are addressed here:
Use the uptime subcommand in remote mode to display the length of time that the domain administration server (DAS) has been running since it was last started.
Ensure that the server is running.
Remote subcommands require a running server.
Display uptime by using the uptime(1) subcommand.
This example displays the length of time that the DAS has been running.
asadmin> uptime Uptime: 1 Weeks, 4 days, 0 hours, 17 minutes, 14 seconds, Total milliseconds: 951434595 Command uptime executed successfully.
You can also view the full syntax and options of the subcommand by typing asadmin help uptime at the command line.
Enterprise Server v3 requires Version 6 Java SE platform as the underlying virtual machine for the Java platform (Java Virtual Machine or JVM machine).
Note - Do not downgrade to an earlier Java version after a domain has been created with a newer JVM machine. If you must downgrade your JVM machine, downgrade it only for individual domains.
If you have not already done so, download the desired Java SDK (not the JRE) and install it on your system.
The Java SDK can be downloaded from http://java.sun.com/j2se.
Start the domain for which you are changing the JDK.
Use the following format:
as-install/bin/asadmin start-domain domain-name
For a valid JVM installation, locations are checked in the following order:
domain.xml (java-home inside java-config)
asenv.conf (setting AS_JAVA="path to java home")
If a legal JDK is not found, a fatal error occurs and the problem is reported back to you.
If necessary, change the JVM machine attributes for the domain.
In particular, you might need to change the JAVA_HOME environment variable. For example, to change the JAVA_HOME variable, type:
as-install/bin/asadmin set "server.java-config.java-home=path-to-java-home"