Installing Borland AppServer on Suse Linux

This document describes procedures for installing Borland AppServer on Suse Linux x86 32-bit operating system.

Notes:

• We recommend uninstalling any previous versions of Borland AppServer, or installing the new version to a different location; on a different install path.
• If you have already installed an evaluation version and have since purchased a license to use Borland AppServer on a permanent basis, you do not need to reinstall the version of the software you evaluated. You can use the License Manager (launched from the Tools menu in the Management Console) to remove your evaluation license, then add and activate your new, permanent license. For information on activating your new license, see Licensing and Registration.

Preparing for installation

Before installing on Suse Linux you should:

• check platform and system requirements
• check JDK requirements

Platform and system requirements

Before installing Borland AppServer on Suse Linux check the platform, system, and JDK requirements.

JDK requirements

The installation package on CD includes a bundled version of the Java Development Kit (JDK). However, if you are downloading Borland AppServer from the web, you need an existing JRE 1.4.2 and above in your environment in order to run the installer.

Important: Before installing on Suse Linux, you must have an existing JDK (1.4.2 is supported) installed. Make sure to put the JDK bin directory into the path variable.

For information about changing a Partition's JDK after you have completed the product installation, go to “Changing the JDK” in the “Using Partitions” section of the Management Console User's Guide.

To check the location of your JDK and the version, use the following syntax:

$which java

/opt/local/bin/java

$java -version

java version "1.4.2"

Mounting the Borland AppServer CD on Suse Linux

The Borland AppServer CD includes installation software for the Suse Linux operating systems. This section describes how to prepare to install Borland AppServer on Suse Linux from CD.

1. Log in as a user with root authority.
2. Insert the CD-ROM in the drive and enter the following command:

    # mount -t iso9660 -o ro /dev/cdrom /cdrom 

   where /cdrom represents the mount point of the CD-ROM.

If you are using auto-mounting software, the CD-ROM is mounted automatically to the directory specified in your auto-mount configuration when you insert it into the CD-ROM drive. You can proceed with instructions given in Installing Borland AppServer.

To check if you have auto-mounting software, use the following command:

$ ps aux | grep automount

root 628 0.0 0.2 1148 588 ? S 17:32 0:00 /usr/sbin/automount

Go to root and enter the following command:

umount /cdrom (if you have manually mounted the CD-ROM)

eject cdrom (if you have used auto-mounting software to mount the CD-ROM)

Installing Borland AppServer on Suse Linux

You can install Borland AppServer from the CD or download the software from the Borland web site: http://www.borland.com/downloads/download_appserver.html

Before you install Borland AppServer, select the installation method:

• If you want to download a version of the product from the Borland web site, go to the web site mentioned above.
• If you are installing from CD, mount CD before starting the installation.
• If you want to perform a silent installation using definitions from a properties file, see Invoking silent installation.

1. To install Borland AppServer from a CD:

   1. Mount the CD-ROM.
   2. Enter the following command to launch the installer:

       $ /cdrom/install_linux

      where /cdrom is the directory where CD-ROM is mounted.

      Important: Make sure the Mozilla (located at /usr/bin) is in your path in order to use the default browser.

   3. The CD splash screen appears after a few moments. The installation wizard launches a separate window.

      Note: To view Readme and installation documentation on the CD, or to browse the contents of the CD, click the appropriate entries on the splash screen.

   4. Select the product you want to install.

      For most options, defaults offered by the installation wizard are acceptable. You can use the Previous button to return to earlier screens and change any information that is incorrect.

   If installing from the web download:

   1. Go to the directory where you downloaded the installer and change permissions to all for the appropriate .jar file using chmod command.
   2. Invoke the appropriate command to launch the installer.

      java -cp <product name>-<release number>-linux-suse-x86.jar install

      For most options, defaults offered by the installation wizard are acceptable. You can use the Previous button to return to earlier screens and change any information that is incorrect.

2. Select the Borland Deployment Platform product you want to install:

   Borland AppServer with Tibco: Installs the entire Borland Enterprise Server, which includes support for integrated management of Java Messaging Services (JMS) through Tibco.

   Borland AppServer with OpenJMS: Installs the Borland AppServer, which includes support for integrated management of JMS through OpenJMS.

3. License agreement: Installation and use of Borland AppServer requires acceptance of the license agreement.
4. Choose Install Folder:

   This creates a new installation of Borland Appserver in the folder you specified.

   Important: You cannot install this version of Borland AppServer on top of previous releases.

5. Choose Product Components:

   Management Console: GUI and tools for managing services and Partitions. For information about installing only the Management Console, go to Installing a standalone Borland Management Console.

   Server: All server components, such as the Partition, Apache Web server, JDataStore, and VisiBroker.

   Client: Components for client applications (EJB client).

   Documentation: Suite of online documentation.

   Examples: Example applications for Borland Appserver.

6. Choose Install Type: Typical/Custom panel:
   1. Typical: This is express install and it uses default settings. The installer generates the BAS example configuration, which is comprised of different example Partitions, and their supporting services.

      In addition, the typical installation includes the following defaults:

      • Smart Agent port: Also known as the osagent port. This port is used by the ORB to communicate with the server. You can use the Management Console to change the Smart Agent port after installation is completed. The default is 14000.
      • Management port: The port Borland AppServer listens to for management functionality in the Management Console. You can use the Management Console to change the Management Agent port (sometimes referred to as the "user port") after installation is completed. The default is 42424.
      • Agent name: The name of the management agent which will run on your server. Every management agent using the same Management port should have a unique name. The default is the host name.

        Note: The value(s) you enter for the port(s) must be valid for the installation to proceed.

      • Adding the BAS bin directory to your PATH variable. The typical installation does not add the BAS bin folder to your PATH. To add it, choose the Custom install type.

      Note: If you select the default, you may have to manually add certain components to your environment path.

      • Adding the VisiBroker environment variables:

      The typical installation does not add the VisiBroker environment variables to your system environment. If you choose the Custom install type to add the VisiBroker environment variables, the installation sets the BAS_LIC_DIR to /var and BAS_LIC_DEFAULT_DIR to /license.

   2. Custom: This option allows you to set various installation options, such as:
      • Specifying Smart Agent port/ Management port/ Agent name to value other than the default value (see Choose Install Type for the default values).
      • Example management configuration setup. To install Borland AppServer sample management configurations, choose "Yes" (default).
      • Include bin directory in PATH. The default is “No”. To add the directory to your PATH, choose “Yes”.
      • Include VisiBroker environment variables: The default is "No". To add the VisiBroker environment variables to your system environment, choose "Yes". The installation sets the BES_LIC_DIR to <install_dir>/var and BES_LIC_DEFAULT_DIR to <install_dir>/license.
7. Pre-Installation Summary: Review the displayed information before proceeding with the installation. You can click the Previous button to revisit and change any selections you made except your choice for which product to install.
8. To approve your choices and start installing, click the Install button.
9. Registration.
   • To launch the Borland Product Registration Wizard before exiting the installer, choose "Yes" (default) and click Next. The Registration Wizard launches in a separate window. After you dismiss the Registration Wizard, the installer completion panel displays.
   • If you are installing an evaluation or free version of Borland AppServer, you are not prompted to launch the Registration Wizard. Before using Borland AppServer, copy the license activation key file you receive by email from Borland to the <install_dir>/license directory. If you did not receive a license activation key file, or if you are reinstalling the software, go to http://www.borland.com/downloads/download_appserver and download a new license key.

   Important: You must register and activate your license in order to use the product. If you have a valid, node-locked license for the previous version of the Borland AppServer on the same machine where you installed the latest Borland AppServer, use the lmadm command-line tool to migrate your older license for use with the newly-installed Borland AppServer software.

   Note: If you want to register and activate your license later, either by running the lmadm executable found in the <install_dir>/bin directory or by launching the wizard from the Tools menu in the Management Console (see the Management Console User's Guide), choose "No" and click Next.

10. When the installation completes, to dismiss the installer, click Done.

Install log

The installer generates an install log that is written to the root of the installation directory if you installed Borland AppServer from CD, or to the folder where the installer file resides if you used a downloaded file to install Borland AppServer.

<install_dir>/Borland_AppServer_InstallLog.xml

The file is an XML formatted log with installation-specific information, such as errors.

Installing a standalone Borland Management Console

Borland AppServer includes a graphical user interface, called the Management Console, which acts as the focal point for managing Agents and applications on your network.

The server typically runs on a large shared UNIX or Windows machine, while the Management Console runs on any machine from which users want to view or modify the distributed system. Once the Management Console is installed, you can deploy to any server on your network.

To install a standalone Management Console:

1. On the Choose Product Components panel, select only the Management Console.
2. On the Choose Install Type panel, choose Custom.
3. When the Configuration Settings screen appears, specify the same Management Agent port as those specified for the server(s) you want the Management Console to support.
4. Complete the installation as described in Installing Borland Appserver on Suse Linux.

Installing more than one BAS instance

If you install more than one instance of BAS on the same machine:

• Each instance must have completely different install paths; the install directories at the top level must be different.
• You must modify management ports with unique port ID numbers to make sure container services are included with each instance.
• Keep the defaults on one instance, but change the defaults for all other instances so that they have unique port ID numbers.

  Note: We recommend you use the management console to change port ID numbers.

To change Management port numbers:

1. Open the Borland Management Console.
2. Right-click on the Agent whose ports you want to change and select Properties.
3. Enter port numbers as needed.

To change Web container port IDs:

1. Open the Borland Management Console.
2. In the navigation tree, expand the Partition whose web container you want to change.
3. Right-click the web container node and select Properties. The Properties tab Service: HTTP/ node displays the connector attributes.
4. To edit port ID properties, enter the values into the table.

   For information about updating the Borland web container server.xml, go to "Web component" section in the BAS Developer's Guide.

1. Install BAS.
2. Copy the base directory from /var/domains/base and rename it, for example you can call it base2 (/var/domains/base2)
3. Change the agent.name property in the file /var/domains/base2/adm/ properties/agent.properties to a unique name of your choice. (This is the name assigned to the management agent).
4. Change the vbroker.agent.port property in the file /var/domains/base2/ adm/properties/management_vbroker.properties to a unique management port. (This is the management port for the agent)
5. To start scu with the settings in base use the command:

   
   scu -domain base

   Similarly to start with the settings as specified in base2 use

   
   scu -domain base2.

Running the installer without a GUI

The installer is capable of running in a text only mode for UNIX systems. You can invoke the installer with a parameter which specifies the UI mode.

To run the installer in text-only mode:

1. Change directories to the folder where the installation executable file is and enter the following command:

   java -cp <install_file>.jar install -i console 

2. When the installer launches, follow the onscreen installation panels.

   The installer will write to stdout and read from stdin. This allows you to telnet from one system to another and run the installer remotely.

Configuring VisiTransact license variables

Before running VisiTransact, you need to set two license environment variables (BES_LIC_DIR and BES_LIC_DEFAULT_DIR). During installation, a shell script is created for you to use for setting these environment variables.

To set the variables:

1. Open a command window.
2. Change directory to <install_dir>/bin.
3. Determine the appropriate script for your shell.

   If you are using the Korn or Bourne shell, use the following script to set environment variables:

   vbroker.sh

   If you are using the C shell, use the following script to set environment variables:

   vbroker.csh

4. To run the script automatically when you log in, add a command to your .profile, .cshrc, or .login file.

Using the setuser tool to manage ownership

Note: The setuser tool replaces the functionality provided by the iaschangeowner script included in previous releases.

The setuser tool manages ownership of Borland AppServer components installed on UNIX hosts. The tool manages all aspects of ownership for these components, which includes:

• Changing the owner ID of installed Borland AppServer Agent and other components.

  For example, if you install the software as usernameA but usernameB is the intended user, you can use setuser with the +o option to change ownership of the appropriate components so usernameB can start the SCU process (Agent) as intended.

• Configuring Borland AppServer to execute in multi-user mode (MUM) so that different users can own multiple Managed Objects (MOs) managed by the same Agent without granting access to other MOs or Borland AppServer components they do not own.

  For example, if you have Payroll, Legal, and Human Resources departmental applications configured as separate MOs under the same Agent, you can use setuser with the +m option to grant execution permissions for each application to mutually exclusive owners without exposing other Borland AppServer privileges to either owner. While Borland AppServer is running in MUM, each user has access to only the MOs they have permission to use.

  The setuser tool implements defense mechanisms to secure these components by configuring the file system with appropriately restrictive ownership and access permissions.

Usage

Important: This tool must be run by a superuser, and all Borland AppServer processes must be stopped before running the tool. The superuser's current GID should be configured to be the same as the GID that was initially used to configure the MUM. The SCU process will fail to start if you invoke it as root but with a GID that is different than the one used to configure the MUM.

The setuser tool is in your Borland AppServer installation's /etc/utils/ directory. Its usage is as follows:

setuser [-r <install-dir>] [-u <new-user>] [-g <new-group>] [+o|+m] [-h]

where

• <install-dir> is the root directory of the installation where the ownership changes are made. If not specified, the setuser tool's own installation location is used.
• <new-user> is the new username for the installation (and, if enabling MUM, the default username that MOs started by the Agent run under).
• <new-group> is the new groupname for the installation (and, if enabling MUM, the default group name that MOs started by the Agent run under).
• +o changes the owner ID of the Agent and other Borland AppServer components to <new-user> and <new-group>.
• +m changes the owner ID of the Agent and other Borland AppServer components to <new-user> and <new-group> while simultaneously enabling the application to run in MUM, allowing each MO started by the Agent to retain its configured ownership.
• -h displays usage information for the setuser tool.

The +o and +m options are mutually exclusive: either use +o to configure the installation to simply execute Borland AppServer components under a different owner, or use +m to enable MUM.

The -u and -g options are optional.

Examples:

• Changing ownership of the Borland AppServer installation found in /Borland/appserver to usernameB:

  
  setuser -r /Borland/Appserver -u usernameB -g admins +o
  
  

• Enabling Borland AppServer to run in MUM without changing Borland AppServer ownership:

  
  setuser +m
  
  

• Disabling MUM without changing Borland AppServer ownership:

  
  setuser +o
  
  

Changing the ownership of an installation and supporting files

Note: Subsequently running setuser with the +o option to change ownership after using the +m option disables MUM. To enable MUM and change ownership of the installation at the same time, use the +m option only (see Enabling multi-user mode).

When you need to change the ID an installation's Agent runs under, use the setuser tool with the +o option. The tool changes the owner ID and reconfigures the necessary file ownerships (log files, property files, configuration files, and so forth). For example:

setuser -r /borland/myBAS/ -u usernameC -g admins +o

To change ownership of the installation and its supporting files:

1. Stop all running Configurations.
2. Stop all running Borland AppServer processes.
3. Open a command shell and become root.
4. Run the setuser tool with the +o option, specifying the username and groupname of a new owner. For example:

   
   setuser -r /borland/myBAS/ -u usernameC -g admins +o
   
   

5. Restart the SCU process.
6. Restart Configurations as required.

Enabling multi-user mode (MUM)

Important: If you are configuring a remote script or application to run under MUM, the MO user you specify in the Configuration must have appropriate permissions on the remote filesystem to load and execute the script or application. For security, other users should not have access to the remote script or application's filesystem.

Note: If you add or modify configurations under an Agent that is already running in MUM, you need to rerun setuser with the +m option to enable the new or modified Configurations to run in MUM.

Multi-user mode configures Borland AppServer to securely support running MOs under multiple, differing user IDs. Enabling MUM is in many ways a special case of changing the user ID under which the Agent executes.

When MUM is enabled for an Agent, the SCU process for the Agent must be started by root. After the SCU process starts, the running process is owned by the specified Agent owner, while the processes for each MO are owned by the configured user for the MOs or applications. If a Configuration does not specify values for Start As User or Start As Group, the MO's processes are owned by the Agent's owner.

To enable MUM:

1. Launch the Borland Management Console.
2. Stop all running Configurations.
3. To edit an MO's properties, right-click the applicable MO and select Properties to launch the Properties editor.
4. To change the owner and group allowed to start the MO:
   • In the Properties editor, choose the Settings tab, then click More Settings.
   • Choose the Platform Specific Settings tab.
   • Change the values for Start As Group and Start As User.
   • Click OK to save the changes and dismiss the Properties editor panels.
5. For each MO that will be executed by a different owner, repeat steps 3 and 4.
6. Stop all running Borland AppServer processes.
7. To enable MUM:
   1. Open a command shell and become root.
   2. Run setuser with the +m option, specifying the new owner ID (or omit the -u and -g flags to keep the existing owner ID). For example:

      
      setuser -r /borland/myBAS/ -u usernameC -g admins +m
      
      

8. If needed, to allow MOs to be started as root, modify agent.config (see Enabling Managed Objects to start as root).
9. If needed, to allow JavaScripts contained in an MO to execute when the MO is started by root, modify agent.config (see Enabling JavaScript support when starting Managed Objects as root).
10. Become root and restart the SCU process.

    The SCU process starts under root ownership but after starting, the process is owned by the existing owner of the Borland AppServer installation, or by the new owner ID specified by the -u and -g options. Each MO's processes are owned by the owners specified in their Configurations. If a Configuration does not specify values for Start As User or Start As Group, the MO's processes are owned by the Agent's owner.

11. Restart Configurations as needed.

Enabling Managed Objects to start as root while running in MUM

Important: Enabling an MO to start as root might expose elevated privileges to unintended users, and should only be implemented for MOs that must be started as root to provide required functionality (for example, enabling Apache to allow privileged port access). To prevent accidental or malicious deployment of a root-started MO that might compromise system security, before enabling an MO to start as root, perform a security audit on the MO's executables and secure access to the system where the MO resides.

Tip: To isolate potential security exposures and simplify administration efforts, put all root-started MOs under one Agent and update its agent.config file to allow the MOs to start as root. Place all other MOs under a different Agent and leave its agent.config file unchanged to retain the default Borland AppServer behavior to disallow starting MOs as root.

Typically, to protect against unauthorized access to MOs, the Agent is prevented from starting an MO as root user. In rare cases, an MO might need to be started by root to function as intended. To override builtin protection against root-started MOs after enabling Borland AppServer to run in MUM, you need to modify agent.config to allow MOs to be started by root. After the MO starts under root ownership, its process ownership is defined and configured by the MO or application (for example, the Apache owner specified in the httpd.conf file), not by Borland AppServer.

To enable MOs to be started by a root user:

1. Stop the SCU (Agent) process.
2. Edit the agent.mum.enable.root.mo property in agent.config (found in <install_dir>/var/domains/base/adm/properties) as follows:

   
   agent.mum.enable.root.mo=true
   
   

3. Become root and restart the SCU (Agent) process.
4. Reconfigure and restart Configurations, as needed.

Enabling JavaScript support when starting Managed Objects while in MUM

Important: Enabling JavaScript execution for an MO started by an Agent configured for MUM might expose your system to malicious code that can run with elevated privileges. When enabling JavaScript execution for such an MO, ensure that the JavaScript has been security audited and is protected from unauthorized user access.

JavaScript execution is typically not allowed when an MO is started by an Agent configured for MUM. If any of the MOs that will run in MUM contain JavaScripts, you need to modify agent.config to allow those JavaScripts to run.

To enable JavaScript execution when MUM is enabled:

1. Stop the SCU (Agent) process.
2. Edit the agent.mum.enable.jscript property in agent.config (found in <install_dir>/var/domains/base/adm/properties) as follows:

   
   agent.mum.enable.jscript=true
   
   

3. Become root and restart the SCU (Agent) process.
4. Restart Configurations, as needed.

Disabling multi-user mode

To disable MUM:

1. Stop all running Configurations.
2. Stop all running Borland AppServer processes.
3. To disable MUM:
   1. Open a command shell and become root.
   2. Run setuser with the +o option. For example:

      
      setuser -r /borland/myBAS/ +o
      
      

4. If needed, to disable starting MOs as root, set the agent.mum.enable.root.mo property in agent.config to false.
(see Enabling Managed Objects to start as root while running in MUM.
5. If needed, to disallow JavaScripts contained in an MO to execute when the Agent is running in MUM, set the agent.mum.enable.jscript property in agent.config to false (see Enabling JavaScript support when starting Managed Objects while in MUM).
6. Restart the SCU (Agent) process.
7. Restart Configurations, as needed.

The SCU process will start and run as the existing Borland AppServer owner ID (or the new owner ID specified by the -u and -g options). Any unique user ID information configured for individual MOs will be ignored, and the MOs are run under the Agent's owner ID.

What is Silent Installation

Important: Using silent installation implies your consent to the BAS License Agreement.

Preparing for Silent Installation

Before using silent installation you should:

• Check disk space requirements. You must have a minimum disk space of 1 GB.
• Verify the installation root directory has no existing BAS installation.

JDK

For Suse Linux, only JDK 1.5.0 is installed. For information on Java products for Suse Linux, go to Sun or IBM's website

Important: Before installing on Suse Linux, you must have an existing JDK (1.4.2 and 1.5.0 is supported) installed. Make sure to put the JDK bin directory into the path variable. To ensure that you have the right JDK version installed, you can run the jdkpatchcheck tool from the prompt. Navigate to the /etc/util directory and run the following command:

/jdkpatchcheck

The optional JDK property (JVM_JDK_HOME) sets the JDK path for BAS components that host user application code, such as new Partitions (including the Standard Partition), and the application client container, “VisiClient Container”. By default, the JDK used will be JDK 1.5.0 which was packaged with the product, or in the case of Suse Linux, the first JDK found in the PATH at the time that the installer is run.

For silent installation, the optional JVM_JDK_HOME property is only used when you need to set the JDK path to a JDK other than the default version. Using a JDK other than the one installed with BAS may have unpredictable results. We highly recommend you use the JDK included with the installer.

Important: Do not remove the JDK installation that JVM_JDK_HOME points to before uninstalling BAS. If you remove the installed JDK, the Uninstaller will not work, since the Uninstaller is configured to use the JDK pointed to by the JVM_JDK_HOME property.

Using silent installation

Before invoking the silent installation process, you must first create a text file that contains the properties for configuration settings, such as install directory, server name and JDK home. Each property must be listed on its own line, terminated by a carriage return, with no blank spaces at the end of each line and no blank lines at the end of the file. See the Properties file for silent installation section for more information.

After creating the text properties file, save it as <propertiesfile>.txt, where <propertiesfile> is the filename prefix for your properties file. Now you can invoke the silent installation process using the values specified in the properties file(s).

Note: All properties and values are case-sensitive. When specifying directory and file paths, always use a forward slash.

Properties file for silent installation

The properties file is a plain text file, with each property listed on its own line, terminated by a carriage return, with no blank spaces at the end of each line and no blank lines at the end of the file. The properties can appear in any order in the file.

Properties File Contents for Silent Installation

Sample silent installation properties for BAS

This example installs Borland Appserver on non-default management agent ports.

 INSTALLER_UI=silent

 USER_INSTALL_DIR=/opt/Borland/appserver

 INSTALL_TYPE=appserver

 JMS_TYPE=TIBCO

 USER_SHORTCUTS=/dev/null

 OSAGENT_PORT=14925

 MANAGEMENT PORT=42925

 CONFIGURATION_SETUP=NO

Invoking silent installation

To invoke the silent installation process using the values specified in the properties file:

1. Open a command-line shell.
2. Go to http://www.borland.com/downloads/download_appserver.html and download Borland AppServer for Suse Linux.
3. Extract the installer executable file.
4. Go to the directory where you downloaded the installer and obtain all permissions, or chmod all, where 777 indicates all, to run the installer.
5. Invoke the silent installation process by entering the following command. Make sure to specify the full path name of the <propertiesfile> file:

   
   java -cp <installer file>.jar install -f <path to properties file>

   where <path to properties file> is the full path of the propertiesfile file.

Note: After silent installation is completed, you need to register and activate the license you received for your product. The license may be in the form of an email from Borland listing one or more serial numbers and license keys, or it may be a license key file sent to you in an email from Borland. If you want to register and activate your license by running the lmadm executable found in the <install_dir>/bin directory or by launching the wizard from the Tools menu in the Management Console (see the Management Console User's Guide).

Licensing and Registration

Before using Borland AppServer, you need to register and activate the license you received for your product. The license may be in the form of an email from Borland listing one or more serial numbers and license keys, or it may be a license key file sent to you in an email from Borland.

If you have a valid, node-locked license for previous version of Borland AppServer installed on the same machine as the newly-installed Borland AppServer, use the lmadm command-line tool to migrate your previous license for use with the newly-installed Borland AppServer 6.6 software

If you have already received a key file in an email from Borland for a product you purchased online or downloaded for evaluation, or if you downloaded a free version of the product, you can use the registration wizard to apply the key file, or you can copy it to the <install_dir>/license directory and it will be applied automatically when you restart your product.

If you have a serial number and key, you can register and activate your Borland AppServer product using one of the following registration methods:

• Direct: If your system is connected to the Internet, this is the simplest method. The product registration wizard guides you through all required steps and automatically activates your license for you. For more information, see the Direct registration section.
• Email: You send your registration request via your own email account (from any system), and will receive an activation file via email that you can apply to your installation. For more information, see the Email registration section.
• Web page: Similar to email, except you register by visiting the Borland web site. For more information, see the Web page registration section.
• Telephone: You provide information to a Borland representative, who will send you an activation file by email or mail. For more information, see the Telephone registration section.

Depending on which method you choose, you may be asked to indicate whether you have a Borland Developer Network (BDN) account. If you do not have an account, you will be prompted to create one in the product registration wizard.

If you do not choose the Direct registration method, you will receive an activation file. Copy this file into the <install_dir>/license directory and it will be applied automatically when you start your product.

Direct registration

To use the Borland product registration wizard for Direct registration:

1. Select the Direct registration method in the first wizard screen, and click Next.
2. Indicate whether you have a BDN account, and click Next. If you do not have an account you are prompted to create one in this wizard.
3. If applicable, enter proxy settings for your internet connection.
4. Review the summarized information before clicking Next. The wizard monitors and displays the progress of your registration.
5. When registration is successfully completed, click Next. Then click Finish to close the Wizard.

Email registration

To use the Borland product registration wizard for Email registration:

1. In the first wizard screen, select the Email registration method and click Next.
2. Indicate whether you have a BDN account, and click Next. If you do not have an account you are prompted to create one in this wizard.
3. Review the summarized information before clicking Next.
4. Copy the content of the Email Registration content pane into an email message addressed to reg@borland.com, and click Next.
5. To close the Wizard, click Finish. You will receive a product activation file by email.
6. Copy the activation file into the <install_dir>/license directory, and it will be applied automatically when you start your product.

Web page registration

To use the Borland product registration wizard for Web page registration:

1. In the first wizard screen, select the Web page registration method and click Next.
2. Copy the registration key from the Web Registration step of the wizard, then click Finish to close the Wizard.
3. Start a web browser and open the http://reg.borland.com.
4. In the registration web page, enter your BDN account information and click Login. If you do not have an account, click the Create account link (http://reg.borland.com/srs5/new_user.jsp).
5. In the Product Registration web page, enter the Serial Number and the Registration Key (from the registration wizard) and click Continue.
6. Verify the email address to which the activation file will be sent, and click Register. You will receive a product activation file by email.
7. Copy the activation file into the <install_dir>/license directory, and it will be applied automatically when you start your product.

Telephone registration

To use the Borland product registration wizard for Telephone registration:

1. In the first wizard screen, select the Telephone registration method and click Next.
2. From the drop-down list, select the location that is nearest you.
3. Click Next, then click Finish to close the Wizard.
4. Dial the number for assistance by telephone and keep the information in the Phone Registration wizard screen on hand.
5. When you receive your activation file, copy it into the <install_dir>/license directory, and it will be applied automatically when you start your product.

Uninstalling Borland AppServer

To uninstall Borland AppServer:

1. Make sure there are no background processes (such as osagent) running during the uninstall.
2. Change directories to <install_root>/UninstallerData directory.
3. Enter the uninstall command:

   java -cp uninstaller.jar uninstall

   [ -i console] # for console mode.

   Note: This does not remove files and folders that were created after the installation.

4. After you run the uninstall command, check the installation directory and remove any unnecessary files and subdirectories.

Note: By default, the uninstallation happens in the same mode by which you have installed