Check to determine if the console is running and enabled.

Use the smcwebserver, wcadmin, and svcs commands to check if the console is running and enabled. This information is useful for troubleshooting problems.

List console resources and properties.

You might need to gather information about the console resources and properties for troubleshooting purposes.

Determine if an application is a legacy application.

Current applications are registered and deployed with a single command while the console server is running. Legacy applications require the console server to be stopped during registration. If you need to register or unregister an application, you must first determine if the application is a legacy application.

List all registered applications.

You can list all applications that are registered with the Oracle Java Web Console. Listing all registered applications provides you with information that can be helpful in troubleshooting situations.

Register a legacy application with the Oracle Java Web Console.

If you need to use a legacy application, you must first register the application with the Oracle Java Web Console.

Unregister a legacy application from the Oracle Java Web Console.

If you do not want a legacy application registered with the Oracle Java Web Console, follow the procedure to unregister the legacy application.

Register a current application with the Oracle Java Web Console.

Before using a new application, you need to register the application with the Oracle Java Web Console.

Unregister a current application from the Oracle Java Web Console.

In some situations, you might need to unregister a current application from the Oracle Java Web Console.

Enable remote Access to the Oracle Java Web Console.

You can enable remote access only to the console, while leaving the other access restrictions in place.

Change the console's internal passwords.

The Oracle Java Web Console uses internal passwords. To reduce the possibility of a security breach, you can change these passwords.