System Administration Guide: Basic Administration

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

Note –

This procedure applies to all console applications in the Oracle Solaris 10, Solaris 10 1/06, and Solaris 10 6/06 releases. Starting with Solaris 10 11/06 release, this procedure also applies only to those applications that are identified as legacy applications. See How to Register a Current Application With the Oracle Java Web Console for the registration procedure for current applications. See also How to Determine if an Application is a Legacy Application.

  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. Stop the web server.

    # smcwebserver stop
  3. Register the application.

    # smreg add -a /directory/containing/application-files

    The smreg command manages the information in the Oracle Java Web Console's registration table. This script also performs some additional work to deploy the application. For additional options to this command, see the smreg(1M) man page.

  4. Restart the web server.

    # smcwebserver start

Example 3–8 Registering a Legacy Application

This example shows how to register a legacy application whose files are located in the /usr/share/webconsole/example directory. Notice that for legacy applications, the console server must be stopped before the application is registered, and started after the application is registered. A warning given by smreg can be ignored because this application is a legacy console application.

# smcwebserver stop
# smreg add -a /usr/share/webconsole/example

    Warning: smreg is obsolete and is preserved only for
    compatibility with legacy console applications. Use wcadmin instead.

    Type "man wcadmin" or "wcadmin --help" for more information.

Registering com.sun.web.admin.example_version.

# smcwebserver start