After installation, the man pages for the Java ES components are located in default directories. You need to add this location to your MANPATH environment variable.
The following table indicates the default locations for the man pages of the Java ES components. If a component is not listed, the component does not have man pages.
Table 6–1 Man Pages Default Locations
Component |
Location of Man Pages |
---|---|
For Solaris OS: /opt/SUNWasvmn/man For Linux: /opt/sun/man |
|
For Solaris OS: /opt/SUNWappserver/share/man For Linux: /opt/sun/appserver/share/man |
|
For Solaris OS: /opt/SUNWcacao/man For Linux: /opt/sun/man |
|
For Solaris OS: /opt/SUNWdsvmn/man For Linux: /opt/sun/man |
|
For Solaris OS: /usr/cluster/man/ |
The following example procedure shows how to ensure that the Application Server man pages are available using the C shell.
Add the location of your Java ES component man pages to your MANPATH environment variable.
On Solaris OS, the following example command sets your MANPATH environment variable for the session:
setenv MANPATH {$MANPATH}:/usr/dt/man:/usr/man:/opt/SUNWappserver/share/man |
To configure this environment variable to apply each time you log in, add the setenv command contents to your .login or .cshrc file.
On Linux, update the /etc/man.config file with the required MANPATH. For example, add this line to the /etc/man.config file:
MANPATH /opt/sun/man |
The new man pages will be fully accessible, regardless of path.
For Linux, if users have MANPATH settings in their own shells, the procedure for Solaris OS should be used. This allows their personal settings to override the /etc/man.config file.
Verify that the man pages are accessible.
For example, the following command should display the asadmin man page for Application Server:
man asadmin |