After you install an OES 2 server, anyone with browser access to the server can access its Welcome Web site, which is a collection of dynamic Web pages that provides the features illustrated and explained in Figure 11-2.
Figure 11-2 The Default OES Welcome Page
This section explains OES Welcome Web Site features, and discusses:
Browsers accessing the Welcome site must have JavaScript* enabled to function correctly.
Additionally, it is possible to install OES 2 on either supported platform without including the Apache Web Server or the Tomcat Servlet Container. For example, if you install OES 2 NetWare® by using the
option, neither of these components is selected by default. For OES 2 Linux, the Apache server and Tomcat container are included with many of the server patterns, but not all of them.If you are unable to access the Welcome Web site, your server is probably missing one or both of these required components. To make the site available, you need to add the components to the OES 2 server.
Anyone with browser access to an OES 2 server can access the Welcome site by doing the following:
Open a supported Web browser that has a TCP connection to the network where the OES 2 server is installed.
Enter the URL to the server, using HTTP.
For example:
http://server.example.com/welcome
or
http://192.168.1.206/welcome
IMPORTANT:By default, the Welcome site is accessible by entering only the DNS name or IP address without the path to /welcome as the URL. However, this behavior changes as follows:
On NetWare, the sys:/apache2/htdocs/index.html file redirects requests to the Welcome site page. If the file is changed, then the behavior reflects the changes made.
On Linux, the Welcome site displays only when there is no index.html file in /srv/www/htdocs. For example, installing the Web and LAMP Server pattern installs a page that says It Works!
and the Welcome site is not displayed.
In these cases the complete path is required (including /welcome) to access the Welcome site.
Although the Welcome Web site is designed primarily for administrators, it can also be accessed and used by end users. For example, if iPrint is installed on the server, users can install the iPrint Client by clicking the
link and selecting the appropriate client.Administrators can access any of the administrative tools installed on the server by clicking the Management Services link, selecting the tool they want to use, and entering the required authentication information.