Borland Enterprise Server installation FAQ

From Support
Jump to: navigation, search

Borland Enterprise Server Installation

Frequently Asked Questions




Is it a requirement to use J2SE 1.3.1?

Yes.

See the latest information about certification on the Product Platforms Page. Information on obtaining J2SE can be found here.

The Borland Enterprise Server has not been tested or certified with any unsupported J2SE release; customers using an unsupported J2SE release with Borland Enterprise Server will have limited support available to them from Borland.

Note: You need the full JDK installed, not just the Java Runtime Environment (JRE).

Compatibility with J2SE 1.4

Borland Enterprise Server does not work with the J2SE 1.4 pre-releases.

Compatibility with J2SE 1.3

Some Borland Enterprise Server customers may find that unsupported J2SE 1.3.x releases work within the boundaries of their application usage. However, there are known issues with these unsupported J2SE 1.3.x versions which have been corrected in the supported release. You should use a supported J2SE release.

Compatibility with JDK 1.0.2, 1.1.x and 1.2.x

Borland Enterprise Server does not work with JDKs older than 1.3

Compatibility with 64-bit versions of Java

Borland Enterprise Server is only certified to work with 32-bit versions of the Java Runtime Environment, even on 64-bit hardware platforms. If a vendor provides separate 64-bit and 32-bit J2SE products you should use the 32-bit version.

back 

Where can I find J2SE 1.3.1?

On Solaris, Windows, and Linux, the Borland Enterprise Server will install a compatible J2SE version for you in the /jdk directory. On all other platforms you must obtain J2SE from the operating system vendor and install it before installing Borland Enterprise Server. These can be found at:

See also the FAQ on [[../general/whatplatforms.html#_jvm_crashes|Why am I seeing odd Java VM crashes?]]

back 

Do I need to install any Operating System patches?

On Solaris, HP-UX, and AIX there are critical Operating System patch requirements in order to run Java reliably. See the FAQ on [[../general/whatplatforms.html#_jvm_crashes|Why am I seeing odd Java VM crashes?]] for details.

In addition, on HP-UX, the following patches are required in order to run Borland Enterprise Server:

  • HP-UX 11.11 - PHSS_24304
  • HP-UX 11.00 - PHSS_24303

back 

Which user should I install Borland Enterprise Server as?

Windows NT 4.0 and Windows 2000

The installer modifies some registry entries. This means you must run Setup while logged in as a user with administrator permissions.

Solaris, HP-UX and Linux

You can run setup on Unix as any user. This user becomes the "owner" of this Borland AppServer installation. You must always start Borland AppServer (i.e. run the "ias" command) from the installation owner account.

If you later want to start Borland AppServer from a different user account you must first change the ownership of the installation. You can do this by running the "iaschangeowner" command (you must be root to run iaschangeowner). After running iaschangeowner you must then always start Borland Enterprise Server from the new owner of the installation, not the previous owner.

AIX

You must install Borland Enterprise Server as root. This user becomes the "owner" of this Borland AppServer installation. It is highly unlikely that you want to run Borland Enterprise Server as root. You should therefore run the iaschangeowner command immediately after completely the installation of Borland Enterprise Server on AIX. After running iaschangeowner you must then always start Borland Enterprise Server from the new owner of the installation, not the previous owner.

Back 

Do I need to install as root to enable http on port 80?

No.

It is unlikely that you will need to install, or run, Borland Enterprise Server as root. In general, running processes as root is to be avoided to reduce the security vulnerabilities that doing so brings.

However, on UNIX system, in order to open a privileged port (<1024), the process must run as root. This means that any web server wishing to serve on the default http port 80 must be started as root.

You should use the iaschangeowner script with the -a flag to configure Borland Enterprise Server to start Apache as root if you're running http on a port <1024. Then run Borland Enterprise Server is the none root user you installed it as.

Back

Can I run the installer without a GUI?

Yes, on a UNIX system.

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:

installer.bin -i console

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

Back

Can I run the installer with no user input?

This can be done on all platforms, but is currently not officially supported.

The body of text below is a sample installer.properties file. To pass this to the installer at runtime, specify

installer -f installer.properties

There is currently no support for licensing an installation using the silent installation mode. To license an silent installation, you may use the console either locally or remotely to apply the license to the server.

You must be careful about trailing whitespace when specifying a property value. See the notes in the sample file below.

# # Sample properties file for installation in silent mode # The following are a list of variables that must be filled out for # installation to be successful. The omission of any variable, i.e. leaving # them blank, will cause the installation to fail # # KNOWN ISSUES: # trailing whitespace following the definition of USER_INSTALL_DIR # will cause the installation to fail. # ############################ ########################## # # Installation mode. INSTALLER_UI=silent # # Installation folder # This is the folder that BES will be installed into # Example: USER_INSTALL_DIR=C:Program FilesBES USER_INSTALL_DIR= # # User short cut. # This is the location on Windows Start menu # Example: USER_SHORTCUTS=C:Documents and SettingshnguyenStart MenuProgramsBES # On UNIX this should always be USER_SHORTCUTS=/dev/null USER_SHORTCUTS= # # OS Agent port # Default to 14000 OSAGENT_PORT=14000 # # Server name # Example: SERVER_NAME=theserver SERVER_NAME=theserver # # JDK Home path # This path can be path to any existing jdk that you have installed # in your system. If you want the installer to install a jdk along with # BES, this variable must be in the following format # JVM_JDK_HOME=/jdk # JVM_JRE_HOME=/jdk/jre # Example: JVM_JDK_HOME=C:Program FilesBESjdk # JVM_JRE_HOME=C:Program FilesBESjdkjre # # JVM_JRE_HOME_NORMAL must use unix style file separators. # it must also contain the same value as JVM_JRE_HOME. for # unix installations, JVM_JRE_HOME and JVM_JRE_HOME_NORMAL will # be identical. for a windows install, the difference will # between the values will be the file separator. # windows, e.g.: JVM_JRE_HOME=C:homesomewhereBESjdkjre # JVM_JRE_HOME_NORMAL=C:/home/somewhere/BES/jdk/jre # unix, e.g.: JVM_JRE_HOME=/home/somewhere/BES/jdk/jre # JVM_JRE_HOME_NORMAL=/home/somewhere/BES/jdk/jre # JVM_JDK_HOME= JVM_JRE_HOME= JVM_JRE_HOME_NORMAL= #

back



Article originally contributed by Sam Patterson


Tags: AppServer Enterprise Borland BES Server
Retrieved from "https://docwiki.embarcadero.com/Support/e/index.php?title=Borland_Enterprise_Server_installation_FAQ&oldid=996"