|
Generic notes
Windows
Linux / Unix
Unlike the Windows installer the "Linux / Unix"-installer does not
install any real database; you must install the database
yourself. Most Linux distributions have some database
installed by default but if you don't have any database, we recommend using either MySQL or PostgreSQL.
Installation instructions for the databases can be found
from here. It is also
possible to use the Hypersonic database which comes bundled
with the installer but that database is very simple,
inefficient and does not support database updates so you
will not be able to install (part of) Sirid updates.
Note: After you have installed the database you
must also create a new view for Sirid and create appropriate
tables. See the database installation
instructions for more information.
Before you can run the installation you must have Java Runtime
Environment (JRE) 1.4 or newer installed. JRE 1.4.2 can be obtained from here.
After you have installed JRE you can start the installation
by first opening a new shell window (command prompt). It is
highly recommended to run the installation using the root
account (su). Then
go to the directory where you downloaded siridtux.jar (cd
<directory>) and type
java -classpath siridtux.jar Install
Be careful with capitals; they must be exactly as
above. This will start the installation which has the
following steps:
Installation directory: This setting specifies the directory where
to install Sirid.
Database: This setting specifies the database to use. See
above for information on installing a database.
Database JDBC URL: This value is required in order to
connect to the database. If you chose PostgreSQL,
MySQL or Hypersonic and you have not made any uncommon
changes to the database, the default value is correct (just hit enter to
accept it).
Database user name: This setting specifies the name to use
when connecting to the database. See the database installation
instructions for more information. This setting is not required for
Hypersonic.
Database user password: This setting specifies the password
to use when connecting to the database with the given user. This
setting is not required for Hypersonic.
JDBC driver: This setting specifies the class name of the JDBC
driver to use (e.g. org.gjt.mm.mysql.Driver). This setting
is not shown if you selected MySQL, PostgreSQL or Hypersonic.
JDBC driver file name: This setting specifies the
driver file of the JDBC driver for the selected database. This setting is not
shown if you selected MySQL, PostgreSQL or Hypersonic (the
installation contains the driver for those databases).
Email information: The email server and email address
are required in order for Sirid to be able to send the
various notification messages. The mail server is typically
mail.yourcompany.com or smpt.yourcompany.com, or
mail.yourisp.com or smpt.yourisp.com. The email address has
no practical effect from the systems point of view. You may,
however, want to create a new email address for this use
(e.g. sirid@yourcompany.com).
HTTP port: This setting specifies the HTTP port which Sirid
uses. If you select any other port than 80 you must
explicitly specify the port when connecting to the Sirid
server using HTTP protocol (for example http://ipaddr:1234).
HTTPS port: This setting specifies the HTTPS (secure HTTP) port which
Sirid uses. If you select any other port than 443 you must
explicitly specify the port when connecting to the Sirid
server using secure HTTP protocol (for example
https://iparrds:1235).
Context root: This setting specifies the directory
of Sirid on the web server. That is, if you set the value
of this setting to /sirid, you must type
https://theIpAddr/sirid to the location bar of your internet
browser in order to access Sirid. Default value is / which
means that Sirid will be accessible in the server root
(https://theIpAddr).
After entering the context root the actual installation process will
begin. Once the installation finishes successfully you must
explicitly start the server. The installation tells you
which shell script you should run in order to start the server.
Custom
Troubleshooting
|
