Console applications typically are registered as part of their installation process, so you should not normally need to register an application yourself. However, if a user cannot access an application, the application might need to be registered.
Two different command-line tools are used to register applications:
smreg – used to register legacy applications, which were developed for earlier versions of the console. You need to restart the console server to allow the registration to complete.
wcadmin – used to register current applications while the console is running.
The commands are located in /usr/sbin on UNIX® operating systems. On Windows operating systems, the commands are in C:\Sun\WebConsole\bin or C:\Program Files\Sun\JavaES5\share\WebConsole\bin. Each command has a man page and a -h option for a help message.
To determine whether an application is a legacy application, examine the registrationInfo tag in the app.xml file in the application's WEB-INF directory. This directory is located in a subdirectory of the webconsole directory.
For a legacy application, the registrationInfo tag indicates a version 2, such as registrationInfo version="2.2.4".
For a current application, the registrationInfo tag indicates at least version 3, such as registrationInfo version="3.0".
To register an application:
Become superuser or assume an equivalent role or administrator login.
Register the application with one of the following commands:
For legacy applications:
smreg add -a /path/to/appname/files
For current applications:
wcadmin deploy -a app_name -x app_context_name /path/to/appname
For example, if the application, foo, is in the /holdapp/ directory, then use one of the following commands:
smreg add –a /holdapp/foo
wcadmin deploy -a foo -x foo_1.0 /holdapp/foo
If you are registering a legacy application with the smreg command, restart the console web server.
smcwebserver restart
The wcadmin command can register and deploy applications while the console server is running, so a restart is not necessary.