This chapter describes how to install SilverStream on UNIX.
See the SilverStream Application Server release notes for the latest information on the following:
NOTE For any updated information about installing SilverStream, see the release notes.
This section describes how to install the SilverStream Server. It is divided into the following sections:
You must have Read or Execute status to the install directories, otherwise you receive an error message.
On UNIX, the SilverStream Server listens on port number 8080 by default. If another process is occupying that port, the installation procedure lets you specify a different port. If you want to set the port numbers to values lower than 1024 (normally reserved for root on UNIX systems), you have to be identified as user root.
After installing SilverStream, you can change the user name and port used by the SilverStream Server.
For more information, see
Changing the user account and port.
HP-UX note
Java programs can heavily use threads and sockets. HP-UX's default setting for the max_thread_proc kernal parameter is too low for Java applications. You need to increase its value to at least 2048. If you don't, the VM might silently crash. For more information, see this page on the HP Web site: http://unixsolutions.hp.com/products/java/2_60_hpux_4java.html.
To install SilverStream you must first mount the CD-ROM drive, then run the install script.
$ mkdir /cdrom
$ nohup /usr/sbin/pfs_mountd &
$ nohup /usr/sbin/pfsd &
$ /usr/sbin/pfs_mount -x unix -t rrip /dev/dsk/c1t2d0 /cdrom
where c1t2d0 is the CD-ROM device.
$ cd /cdrom
The Solaris Volume Management software automatically mounts the CD-ROM to the /cdrom mount point.
Once the CD-ROM drive is mounted, you can install SilverStream. You do not need to run the Installation program with root privileges; you can install as any user.
cd /cdrom
./install.sh
The installation script begins. It checks to see whether you have all required patches installed. If so, it continues; if not, it tells you what you need to do.
The information you now need to provide depends on the database type you chose.
NOTE You can check the connection to the database from the machine you are running the installation on using sqlplus, for example, | |
Select Yes to upgrade your previous SilverMaster and any databases you have added to the SilverMaster to Version 3.
The SilverStream Application Server defaults to port 8080 on UNIX. You need to specify the port number when you connect to the server from the SilverStream Designer or when you specify URLs on that server. For example, from the SilverStream Designer, select the Choose Server icon and enter the name as hostname:portnumber. For example:
myserver:8080
For application URLs on the server, you need to tell the browser what port number the server is using (for example, http://myserver:8080/SilverStream/Pages/myPage.html).
Enter the name service port number or press Enter to accept the default.
The installation program displays a screen that contains information about the changes the program will make, information about the SilverMaster and SilverStream Server settings, and the license string.
The program creates or edits your httpd.props file and sets environment variables in .agprofile. A list of the install directories appears, along with the message that SilverStream is creating resources. This portion of the installation, which runs SilverMasterInit, may take some time.
When the installation completes, you are asked if you want to start the SilverServer now.
If you choose N, you can start the SilverStream Server manually. See Testing the install.
If you want the server to start automatically when the machine boots, use the sample startup scripts that are installed on your system. The text preceding the final installation prompt tells you where to find the sample startup scripts.
For more information about using the startup scripts, see
Setting the SilverStream Server and cluster components to run as daemons.
$ /usr/sbin/pfs_umount /cdrom
The Installation program installs sample startup scripts that your system can run to automatically start the SilverStream Server or cluster components as daemons at boot time.
The paths to the server and cluster component startup scripts for each supported UNIX platform are listed in the following tables. See step 4 of the following procedure for sample commands that install the server component for each platform.
NOTE As shown in the preceding table, the HP-UX server and cluster component scripts use link files.
A system administrator with root privileges must copy the sample server and cluster scripts from the install directory into your operating system's boot directory.
For more information, see
Setting up the SilverStream Server to run as a daemon next and
Setting up the SilverStream cluster to run as a daemon.
To have the server startup script run the next time your system reboots, a system administrator with root privileges must copy the script from the install directory into your operating system's boot directory as shown in step 4 of the following procedure.
To set up the SilverStream Server to run as a UNIX daemon:
The following procedure assumes that you have already run the Installation program and created and configured a database to be used as your SilverMaster database.
For example, to copy the sample server script for Solaris from an install directory called $Silverstream_root/etc/rc3.d to a boot directory called /etc/rc3.d you would type the following:
#cp $Silverstream_root/etc/rc3.d/S90silverserver /etc/rc3.d
The following table shows platform-specific sample commands.
#cp $Silverstream_root/etc/rc.silverserver /etc/ | |
#cp $Silverstream_root/sbin/init.d/silverserver /sbin/init.d | |
#cp $Silverstream_root/etc/rc3.d/S90silverserver /etc/rc3.d | |
NOTE The HP-UX sample scripts use links that are similar to those used by HP-UX for their startup script environment. In the second line of the command in the preceding table, /sbin/rc3.d/s300silverserver is a link that points to /sbin/init.d/silverserver.
For more information, see the
Server and cluster sample startup scripts.
For more information, see the Administrator's Guide.
You should change privileges from root to a different effective user ID. Once a root process changes its ownership to become a non-root process, it can't recover its former access privileges.
You can use the sample scripts to start a cluster component as a daemon. By default, the scripts run with root privileges. If you want the cluster to start as a user other than root, see your system administrator who can apply the setuid permission to the cluster component script files.
For a list of startup scripts, see the table in
Using the server sample startup scripts.
After installing SilverStream, you can change the user account that the server runs under. You can also change the port used by the server. For example, you might want to use port 80, which is the default port number for SilverStream on NT. That requires root access, but maybe you want the server to run under a different user account. You could perform the following procedure.
To change the user account and port:
For more information about the SMC, see the Administrator's Guide.
Using a port less than 1024
If you specified a port less than 1024 (such as 80) but a user name other than root, you need to do the following:
The server opens the specified port and switches the process UID to the user name you specified.
Tablespaces for Oracle databases
The installation will use the default tablespace of the username/password specified for your SilverMaster database. You can usually set the default tablespace with the following SQL statement:
ALTER USER username DEFAULT TABLESPACE mytablespace ;
Using different database types with the same SilverStream Server
If you install with a Sybase or Informix SilverMaster, and wish to add an Oracle database, you need to have $ORACLE_HOME set and have $ORACLE_HOME/LIB in your SHLIB_PATH (for HP-UX) or LD_LIBRARY_PATH (for Solaris).
If you installed with an Oracle SilverMaster and would like to add a Sybase or an Informix database, you need to add the jConnect classes or Informix JAR file to your AGCLASSPATH.
Alternatively, you can modify the AGCLASSPATH in the environment file silverstream/.agprofile. Note that SilverServer sources .agprofile automatically; you do not need to source it manually.
You must perform all of these steps before starting the server.
To test your installation, start the SilverStream Server.
For complete information about starting and stopping the SilverStream Server, see the chapter on running the server in the Administrator's Guide.
To start the SilverStream Server:
#./SilverServer &
# SilverStream Server loading properties from: /usr/silverstream/Resources/httpd.props
SilverStream Server ... serving at: http://host_name:port
You must have Read or Execute permissions to the install directories, otherwise you will receive an error message.
NOTE It is also good idea to verify that any services that the SilverStream Server depends on are running and set to start automatically when the system reboots.
If you encounter a problem, see
Troubleshooting.
You can access the SilverStream Server running on UNIX from the SilverStream Designer running on NT.
To access a UNIX SilverStream Server from the Designer:
A dialog box appears, prompting you to enter the name of the server.
A new server icon appears in the left pane of the main window. This icon displays the name of the server you specified.
SilverStream creates the environment file .agprofile in the SilverStream installation directory during installation (since it is a "dot" file, you need to issue the ls -a command to see it).
The .agprofile file sets up a proper environment to launch the SilverStream Server. It sets environment variables for the following:
Normally this file is only edited by SilverStream during installation. However, you might want to alter this file for the following reasons:
You must restart the server after changing the AGCLASSPATH and before adding the database.
This section describes known problems and their workarounds.
***Warning: License improperly installed: SilverStream Software;
<licensenumber>
***Warning: No valid Licenses found defaulting to Single User
License.
SilverStream Server [Build Number: Number] serving at: http://servername: portnumber
This may occur if you run SilverMasterInit outside of the installation.
You must reapply your license to the SilverMaster database. Go to your /cdrom/silverstream directory and run the following command:
./upldlic.sh your license number
Xlib: connection to "sunny:0.0" refused by server
Xlib: Client is not authorized to connect to Server
Messages like these can occur if you are installing on a remote machine. The following command or a suitable variation should be run from a remote machine:
xhost +
xhost + machinename_of_installation
If after executing the xhost command, you get the following error
/usr/openwin/bin/xhost: must be on local machine to add or remove hosts.
You must execute the command at the server console and not remotely.
The following message may be caused by an incorrect DISPLAY variable.
Java exception occurred java.lang.InternalError: Can't connect
to X11 window server using '222.111.99.333:0.0' as the value
of the DISPLAY variable.
Try changing the value of the DISPLAY environment variable to one of the following:
DISPLAY=:0.0
export DISPLAY
DISPLAY=machinename:0.0
export DISPLAY
***Fatal Error, aborting com.sssw.srv.http.httpd: An unexpected exception occurred com.sssw.srv.daemon.ServerHandlerInitException: Unable to create server socket on port 80, details: Permission denied at com.sssw.srv.http.httpd.initializeServerSocket (httpd.java:1105) at com.sssw.srv.http.httpd.initialize (httpd.java:2344) at com.sssw.srv.http.httpd.mainBODY = (httpd.java:2437) at com.sssw.srv.http.httpd.main(httpd.java:2446)
You tried to start SilverServer on port 80 without root privileges.
Usually only the root user can start a server on port 80. Try logging on as root and starting SilverServer, or follow the procedure in Changing the user account and port.
# SilverStream Server loading properties from:
/opt/silverstream/Resources/httpd.props
*** Fatal Error, aborting
com.sssw.srv.http.httpd: An unexpected exception occurred
com.sssw.srv.daemon.ServerHandlerInitException: An exception
occurred while attempting to initialize the connection to
'SilverMaster':
Unable to find schema for database SilverMaster in AgInfo
table.
at com.sssw.srv.http.httpd.initializeProperties
(httpd.java:1356)
at com.sssw.srv.http.httpd.initialize(httpd.java:2287)
at com.sssw.srv.http.httpd.mainBODY(httpd.java:2437)
at com.sssw.srv.http.httpd.main(httpd.java:2446)
++++
-----------------------------------------------------
Java exception occurred java.lang.RuntimeException:
An unexpected exception occurred
-----------------------------------------------------
If after running SilverServer you see this error, the SilverMaster database has been corrupted and SilverMasterInit should be rerun. When running SilverMasterInit, all data in Ag* tables will be lost.
If you would like to start SilverServer without checking the SilverMaster resources, you can start the server using the -nodbcheck startup option:
./SilverServer -nodbcheck
Unable to save a table with a field that is marked "Full Text Searchable".
Full-text search will fail if the directory in which SilverStream resides contains a hyphen (-) or a period (.).
Reinstall SilverStream into a directory which does not contain a hyphen or a period. Renaming the SilverStream directory will not be sufficient since environment variables are set during the installation.