Installing a Ketura Server

The Ketura server should only be installed on a machine that meets the minimum system requirements to run the Ketura server. Installing Ketura on a machine that does not meet these requirements is likely to result in unsatisfactory performance.

In a corporate network environment, Ketura might typically be installed on a server machine that is accessible from the local network. However, Ketura may also be installed on a personal machine, such as a laptop or a desktop, provided that the machine meets the minimum system requirements. This capability is particularly helpful for people evaluating Ketura.

A Ketura server can coexist with other applications (including server applications) that might be running on a machine, but you should ensure that the machine has sufficient memory available to Ketura, and that enough CPU time is available to Ketura for it to perform adequately.

Because sensitive information might be stored in your Ketura system, please ensure that you have read and understood the Security Considerations topic.

If you are upgrading from an earlier version of Ketura, please read Upgrading to a Newer Version of Ketura before proceeding. Do not skip the backup step discussed in that article.

1. Download the latest version of the Ketura installer disk image (.dmg file) for Mac OS X from the Ketura download page on the Araxis website. This will have a name such as Ketura_2007.bbbb.dmg, where bbbb is the build number of Ketura.

   Ketura comes with a licence to evaluate Ketura for a limited period of time, after which a licence can be purchased if you wish to continue to use Ketura. If you already have a licence to use Ketura, you can install it once the system has been installed.

2. If the disk image doesn’t open and mount automatically, double-click it to mount it.
3. Double-click the Araxis Ketura 2007.bbbb.pkg item within the disk image to launch the installer package. Complete the installation.

4. Open the Araxis Ketura Manager application in the system Applications folder. As this is the first time you are running the Ketura Manager, you will be prompted to provide a password for the System Administrator account, which by default has the log on user id admin. You will need this to log on to Ketura.

   Do not reuse a password that you have used for something else, as this is a security risk.

5. The Ketura Manager will then prepare Ketura for use. Please wait a minute or two, until this has been completed.
6. Ketura should now be ready for use. Please see the Logging on to Ketura Using a Web Browser topic for information about logging on.

Ketura automatically adds an entry to the Firewall tab of the Sharing item (on Mac OS X v10.4 ‘Tiger’) or Security item (on Mac OS X v10.5 ‘Leopard’) in System Preferences. This entry is checked by default, so that other users on your local network can access Ketura. You may uncheck this entry if you don’t wish other users to be able to access your Ketura installation.

Uninstallation: Please see Uninstalling Ketura should you wish to uninstall Ketura.

Ketura and the Mac firewall

Mac OS X has a built-in firewall to protect the system’s security. It can be configured to allow (or disallow) other machines on the same network to access Ketura.

Mac OS X v10.4 ‘Tiger’

When the Araxis Ketura Manager application is run for the first time after installation, the built-in firewall is configured so that Ketura can be accessed by other machines on the same network.

Mac OS X v10.5 ‘Leopard’

The built-in firewall in Leopard has three different modes of operation. These modes can be selected from the Mac OS X System Preferences window, in the Firewall tab of the Security section. The three options are:

• Allow all incoming connections – When selected, users on the same network will have access to Ketura.
• Allow only essential services – When selected, users on the same network will not have access to Ketura.
• Set access for specific services and application – When Ketura is started for the first time after this firewall option has been selected, a message box will appear asking Do you want the application “java” to accept incoming network connections?. Clicking Allow will enable other users on the same network access to Ketura. Clicking Deny will prohibit other users from accessing Ketura.

Please note that the installation (and uninstallation) of Ketura must be performed using an account with administrative privileges. If in doubt, please see your network or system administrator.

1. Download the latest version of the Ketura setup program for Windows from the Ketura download page on the Araxis website. This will have a name such as Ketura_2007.bbbb.exe, where bbbb is the build number of Ketura.

   Ketura comes with a licence to evaluate Ketura for a limited period of time, after which a licence can be purchased if you wish to continue to use Ketura. If you already have a licence to use Ketura, you can install it once the system has been installed.

2. Double-click the setup program that you have downloaded. This works like many other Windows installers, so should be straight-forward to work through. The notes below might be helpful

   Installing a newer version of Ketura into a directory where an older version of Ketura is already installed

   If you try to install a newer version of Ketura into a folder where an older version is already installed, the Setup program will ask you whether you wish it to uninstall the older version (which it can do for you automatically).

   Any existing database is left intact when an older version of Ketura in uninstalled. Provided it is compatible with the version of Ketura you are installing, you can therefore elect to re-use it in Step 5, below.

   Installing an older version of Ketura into a folder where a newer version of Ketura is already installed

   If a you try to install an older version of Ketura into a folder where a newer version of Ketura is already installed, the Setup program will warn you that this is not possible, and ask you whether you want to change the installation folder or quit the installation. If you wish to install in the same location as an existing, newer, version of Ketura, you will need to quit the installation, uninstall the previous installation and re-run Setup.

   Deciding whether to reuse an existing database

   If no normal or example databases exist from a previous installation, Ketura will automatically create them as required. However, if a normal and/or example database from a previous installation exists in your chosen installation location, Setup will check to see whether they can be reused. If they can, Setup will ask you whether you wish to reuse them or create new databases. If the existing databases cannot be reused, Setup will ask you whether you wish to install new databases or exit Setup.

   If you choose to create a new database, Setup endeavours to rename any old database it finds, rather than deleting it. The renamed old database will be left in the Database/Mckoi subfolder of the Ketura installation folder, and will be called something such as Database_Normal_dd_mm_yyyy_hhmmss or Database_Example_dd_mm_yyyy_hhmmss, where dd_mm_yyyy and hhmmss represent the date and time when the database was renamed. Once you are sure that you no longer need the old renamed databases, you may simply delete them. Alternatively, if for some reason you wish to revert to an old database, and you did not make a backup immediately prior to upgrading Ketura as recommended, it might be possible to recover your data using the old renamed database. Please contact Araxis for assistance in this scenario.

   If you exit the Setup program at this stage, any previous installation of Ketura will not be re-installed automatically. If you wish to continue using the existing database, you will need to re-install a version of Ketura compatible with it.

   Providing a password for the System Administrator account

   If a new database is being installed, the Setup program will now request a password for the System Administrator account, which by default has the log on user id admin.

   Do not reuse a password that you have used for something else, as this is a security risk.

   Due to limitations in the installation technology used to create the Ketura Setup program, the password that you enter can contain only the English letters A-Z, a-z, the digits 0-9, and the following symbols and punctuation characters: !#$%&()*+,-./ :;<=>@{|}~[\]^_. Once Ketura has been installed, you may, if you wish, log in and change the password to something that contains characters from other languages.

   Responding to a possible security alert message

   If the machine upon which Ketura is being installed is running a third-party firewall or security product, it is possible that a security alert message will now appear. This will ask if the program Java(TM) 2 Platform Standard Edition binary should be blocked or unblocked. Allow it to be unblocked to ensure that Ketura installs correctly. Once Ketura has been installed, it is recommended that you adjust your security product to re-block this program.

3. Ketura should now be ready for use. Please see the Logging on to Ketura Using a Web Browser topic for information about logging on.

Ketura and the Windows firewall (Windows XP Service Pack 2 and Windows Vista)

By default, the Setup program configures the Windows firewall so that Ketura can be accessed by other machines on the same local network (subnet) as the Ketura server. This is the only setting required for most installations.

To change the Windows firewall configuration:

• If your organization has a network or system administrator, check with him or her before making changes to your firewall settings.
• Launch the Windows Firewall administration utility. This is the Windows Firewall item in the Windows Control Panel.
• Select the Exceptions tab.
• In the list of exceptions, select the item named ‘Araxis Ketura’. This is the exception that permits access to Ketura from the local subnet.
• Click the Edit button to make changes to the exception. On the dialog that appears it is possible to change the scope to allow or deny access to Ketura from other network locations.
• When you are finished making the changes you require, click the OK button (in the dialog captioned Edit a Program).

The ‘Araxis Ketura’ exception in the list of exceptions can be temporarily disabled by un-checking the checkbox next to it. This is useful when you want to temporarily restrict access to Ketura when, for example, you want to perform an upgrade to Ketura and therefore prevent users from connecting to the system. The exception must be reinstated by checking the checkbox to enable access to Ketura from other machines on your network.

Other firewalls

Although Ketura should now be accessible from the machine upon which it has been installed, your computer might have a firewall installed to protect against unauthorized network access. If other users on your organization’s network are to be able to access Ketura, any such firewall must be configured appropriately.

If you are running an Internet security product, such as ZoneAlarm Pro, you will also need to configure that product to allow access to the Ketura server on your local machine, and to allow cookies, JavaScript and so on for that server. For ZoneAlarm Pro, this will involve adding an entry in the sites section for the local machine.