Java RFC Orbix Server Installation Processing (SAP-Bibliothek

Java RFC Orbix Server Installation Processing

Purpose

This document describes the processing performed by the JRFC.EXE installation utility. In all examples, assume that you install the Orbix server component onto a directory called TARGETDIR.

Process Flow

The Orbix installation procedure:

Checks for existing Orbix versions:

If Orbix is not installed on your Orbix server computer, the Java RFC installation installs the necessary components of the Orbix service.
If you have an Orbix service of a version earlier than 2.3C installed, you have to overwrite it to continue with the Java RFC installation.

In both of the above cases, the Java RFC installation copies the Orbix Library/Utilities (IONA's Orbix 2.3C runtime components, OrbixWeb, and the Orbix configuration files) to the Orbix server computer.

If you have version 2.3C of Orbix installed, then the Java RFC installation checks for certain Orbix components. It may install some missing tools or additional helper files in the target directory you specify.

Copies the Java RFC Orbix server executable (jrfcserver.exe) and the RFC Dynamic Link Library (librfc32.dll) to your server computer.
Self-registers the JRFC Orbix server with the Orbix daemon.

In addition, if you are installing the Orbix utilities FOR THE FIRST TIME, the JRFC.EXE installation program:

Changes the IT_CONFIG_PATH environment variable to point to the TARGETDIR\cfg subdirectory.

Sets the IT_CONFIG_PATH entry under HKEY_LOCAL_MACHINE in the Windows Registry to TARGETDIR\cfg.

If you specify that the Orbix daemon is to be installed as an NT service, then the Java RFC Orbix server installation also sets the SYSTEM\CurrentControlSet\Services\Orbix daemon\Start Windows Registry entry under HKEY_LOCAL_MACHINE to 0x2. This means that the Orbix Daemon service will automatically start at system startup time.

If you do not want to have the service start automatically, you may change the setting from the Control Panel, or modify this registry entry to 0x3.

Sets the following lines in the Orbix configuration file (Orbix.cfg) in TARGETDIR\cfg:

IT_DAEMON_PORT is set to 1571

This is required by the Orbix client, which looks for the Orbix daemon on the Orbix server host only at this port number. This is different from the default Orbix port number 1570. If you have an existing version of Orbix, the Java RFC installation does not change this entry.

Since the Java RFC setup assumes the use of Port number 1571, if you have an existing Orbix installation that uses another port number, you must set the port number used by the client side to the one defined in your Orbix configuration. You do this by using the MiddlewareInfo object. See the get/setOrbDaemonPort methods of MiddlewareInfo in the Java RFC HTML Reference document.

IT_LOCAL_DOMAIN is set to empty

This field can be overwritten from the Java RFC client, using the MiddlewareInfo object. See the get/setLocalDomainName methods of MiddlewareInfo in the Java RFC HTML Reference document.

If you have an existing version of Orbix, the Java RFC installation also does not modify this value.

Adds the SAP Java RFC program group to the Windows Start menu.