JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Basic Administration     Oracle Solaris 10 8/11 Information Library
search filter icon
search icon

Document Information

About This Book

1.  Oracle Solaris Management Tools (Road Map)

2.  Working With the Solaris Management Console (Tasks)

3.  Working With the Oracle Java Web Console (Tasks)

What's New in Administering the Oracle Java Web Console?

Oracle Java Web Console Server Management

Applications That Are Available to the Oracle Java Web Console

Oracle Java Web Console (Overview)

What Is the Oracle Java Web Console?

Oracle Java Web Console Management Commands

Supported Web Browsers

Getting Started With the Oracle Java Web Console (Task Map)

Getting Started With the Oracle Java Web Console

How to Start Applications From the Oracle Java Web Console's Launch Page

Managing the Console Service

How to Start the Console Service

How to Enable the Console Service to Run at System Start

How to Stop the Console Service

How to Disable the Console Service

Configuring the Oracle Java Web Console

How to Change Oracle Java Web Console Properties

Oracle Java Web Console User Identity

Using the Console Debug Trace Log

Troubleshooting the Oracle Java Web Console Software (Task Map)

Troubleshooting the Oracle Java Web Console Software

Checking Console Status and Properties

How to Check if the Console is Running and Enabled

How to List Console Resources and Properties

Problems Accessing the Console

Problems with Application Registration

How to Determine if an Application is a Legacy Application

How to List Deployed Applications

How to Register a Legacy Application With the Oracle Java Web Console

How to Unregister a Legacy Application From the Oracle Java Web Console

How to Register a Current Application With the Oracle Java Web Console

How to Unregister a Current Application from the Oracle Java Web Console

Oracle Java Web Console Reference Information

Oracle Java Web Console Security Considerations

Access to the Oracle Java Web Console

Access to Applications in the Oracle Java Web Console

Application Privileges

Application Access to Remote Systems

Internal Passwords That Are Used in the Console

Specifying Authorizations With the authTypes Tag

Enabling Remote Access to the Oracle Java Web Console

How to Enable Remote Access to the Oracle Java Web Console

Disabling Remote Access to the Oracle Java Web Console

How to Disable Remote Access to the Oracle Java Web Console

Changing Internal Passwords for Oracle Java Web Console

How to Change the Console's Internal Passwords

4.  Managing User Accounts and Groups (Overview)

5.  Managing User Accounts and Groups (Tasks)

6.  Managing Client-Server Support (Overview)

7.  Managing Diskless Clients (Tasks)

8.  Introduction to Shutting Down and Booting a System

9.  Shutting Down and Booting a System (Overview)

10.  Shutting Down a System (Tasks)

11.  Modifying Oracle Solaris Boot Behavior (Tasks)

12.  Booting an Oracle Solaris System (Tasks)

13.  Managing the Oracle Solaris Boot Archives (Tasks)

14.  Troubleshooting Booting an Oracle Solaris System (Tasks)

15.  x86: GRUB Based Booting (Reference)

16.  x86: Booting a System That Does Not Implement GRUB (Tasks)

17.  Working With the Oracle Solaris Auto Registration regadm Command (Tasks)

18.  Managing Services (Overview)

19.  Managing Services (Tasks)

20.  Managing Software (Overview)

21.  Managing Software With Oracle Solaris System Administration Tools (Tasks)

22.  Managing Software by Using Oracle Solaris Package Commands (Tasks)

23.  Managing Patches

A.  SMF Services

Index

Configuring the Oracle Java Web Console

The Oracle Java Web Console is preconfigured to run without administrator intervention. However, you might choose to change some of the web console's default behavior by overriding the console's configuration properties.


Note - Starting with the Solaris 10 11/06 OS, you must use the wcadmin command to change these properties. Previously, the smreg command was used. For more information about the wcadmin command, see the wcadmin(1M) man page.


Properties in the console's configuration files control the behavior of the console. To change the behavior, you define new values for properties to override the default values. The default values of most properties should not be overridden unless there is a specific need that the default values do not provide, such as specifying your own login service.

In general, the property values that you might consider changing are the following:

See Example 3-5 for an example of specifying the auditing implementation.

How to Change Oracle Java Web Console Properties

  1. Become superuser or assume an equivalent role.

    Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

  2. Depending on which Oracle Solaris release you are running, change the selected property value as follows:
    • If you are running at least the Solaris 10 11/06 release, use this command:
      # wcadmin add -p -a console name=value
      -p

      Specifies that the object type is a property.

      -a console

      Specifies that the property changes are for the application named console. The -a console option must always be used when you are changing console properties.

      name=value

      Specifies the property name and the new value for that property.

    • For the Oracle Solaris 10, Solaris 10 1/06, and the Solaris 10 6/06 releases, use this command:
      # smreg add -p -c name
  3. (Optional) Reset a console property to its default value.
    • If you are running at least the Solaris 10 11/06 release, use this command:
      # wcadmin remove -p -a console name=value
    • For the Oracle Solaris 10, Solaris 10 1/06, and the Solaris 10 6/06 releases, use this command:
      # smreg remove -p -c name
      -p

      Specifies that the object type is a property.

      -c

      Specifies that the property changes are for the console application. The -c option must always be used when you are changing console properties.

      name

      Specifies the property name and the new value for that property.

Example 3-1 Changing the Oracle Java Web Console's Session Timeout Property

This example shows how to set the session time out value to 5 minutes.

# wcadmin add -p -a console session.timeout.value=5

Example 3-2 Configuring the Oracle Java Web Console Logging Level

This example shows you how to set the logging level to all.

# wcadmin add -p -a console logging.default.level=all

Example 3-3 Resetting the Oracle Java Web Console Logging Level to the Default Value

This example shows how to reset the logging level to the default.

# wcadmin remove -p -a console logging.default.level

Example 3-4 Specifying a Java Version for the Oracle Java Web Console

This example shows how to set the Java version for the console.

# wcadmin add -p -a console java.home=/usr/java

Example 3-5 Choosing an Auditing Implementation for the Oracle Java Web Console

This example shows you how to set the auditing implementation to None.

# wcadmin add -p -a console audit.default.type=None

The valid auditing types are:

None

No auditing

Log

Audit messages to syslog

Solaris

Audit messages to BSM

Oracle Java Web Console User Identity

By default, the web console runs under the user identity, noaccess. However, some system configurations disable the noaccess user, or set the login shell for the noaccess user to an invalid entry to make this user identity unusable.

When the noaccess user is not usable, the web console server cannot be started or configured, so an alternative user identity must be specified. Ideally, the user identity should be changed only once, before the console server is configured at initial startup.

You can configure the web console to run under an alternative non-root user identity by using either of the following commands before the console starts:

# smcwebserver start -u username

This command starts the web console server under the specified user identity. The web console server runs under this identity each time the server is subsequently started if the command is issued before the first console start.

If you are running at least the Solaris 10 11/06 release, you can also use this command:

# wcadmin add -p -a console com.sun.web.console.user= username

Note - Starting with the Solaris 10 11/06 release, when the system initially starts, the console also starts and is automatically configured to run under noaccess. Consequently, the user identity is set to noaccess before you are able to change the user identity. Use the following commands to reset the console to its initial unconfigured state. Then, specify a different user identity when you restart the console.

# smcwebserver stop
# /usr/share/webconsole/private/bin/wcremove -i console
# smcwebserver start -u new_user_identity

For the Oracle Solaris 10, Solaris 10 1/06, Solaris 10 6/06 releases, use this command:

# smreg add -p -c com.sun.web.console.user=username

This command causes the web console server to run under the specified user identity the next time the server starts, and each time the server is started.

Using the Console Debug Trace Log

By default, the console does not log debug messages. You can turn on debug logging to help troubleshoot console service problems.

Use the debug.trace.level property to turn on debug logging by setting the property to a value other than 0.

Available choices include the following:

By default, the debug trace log is created in the /var/log/webconsole directory for the Oracle Solaris 10, Solaris 10 1/06, and the Solaris 10 6/06 releases. Starting with the Solaris 10 11/06 release, the log is created in the /var/log/webconsole/console directory. The log file is named console_debug_log. Historical logs, such as console_debug_log.1 and console_debug_log.2 might also exist in this directory. There can be up to five (default setting) historical logs stored in this directory before the earliest log is deleted and a new log is created.

Example 3-6 Setting the Console Debug Trace Log Level

Use the following command to set the debug trace log level to 3.

For the Solaris 10 11/06 release, use this command:

# wcadmin add -p -a console debug.trace.level=3

For the Oracle Solaris 10, Solaris 10 1/06, and the Solaris 10 6/06 releases, use this command:

# smreg add -p -c debug.trace.level=3

Example 3-7 Checking the Status of the debug.trace.level Property

To check the status of the debug.trace.level property, use the wcadmin list or smreg list command.

Solaris 10 11/06:

# wcadmin list -p | grep "debug.trace.level"

For the Oracle Solaris 10, Solaris 10 1/06, and Solaris 10 6/06 releases, use this command:

# smreg list -p | grep "debug.trace.level"