This document covers the following topics:
See EntireX Platform Coverage for a complete list of which EntireX components are available under which Windows platform.
Please note the following before you start the EntireX installation:
You need administrator's access rights during the Windows Installation.
Before you start installing, backup your current product version, including your attribute files.
If a previous EntireX version is installed, it will be upgraded to 7.3 automatically. EntireX versions older than 611 must be uninstalled before EntireX 7.3 can be installed.
If you are upgrading from EntireX version 611 or later, select the option to install the product. Be sure to specify the same directory as the current product. Select the type of installation that matches the current product - Typical, Runtime or Custom. Note that the installation will automatically update each broker attribute file to the new format. The previous attribute files will be renamed to ETBxxx.ATR.bak and will be saved in the same directory as the corresponding new attribute files.
During the installation you need a valid License (Typical, Custom).
Note:
Under Windows 2000 Professional and Windows XP Professional, no
license file is required for the EntireX Runtime component. On all other
Windows platforms, a license file is required for all components.
The runtime DLLs are always installed in the Windows directory: Program Files\Common Files\Software AG.
This cannot be changed.
If you intend to use a Lightweight Directory Access Protocol (LDAP) for Location Transparency, the installation procedure will prompt you for the values to be used to access the directory. Be sure to get the host name, port number, Distinguished Name (DN) and authorization DN and password (if security is enabled) from your Directory Administrator before starting. See Configuration of LDAP Server for more information.
There are three types of installation, typical, and custom.
Specify typical installation to install the following components:
EntireX Runtime
EntireX Broker
EntireX Developer's Kit
EntireX Management Tools
Runtime installation will install the following component:
EntireX Runtime
Use Custom installation to optionally specify the following components:
EntireX Runtime
EntireX Broker
EntireX Developer's Kit
EntireX MS Visual Studio Plug-ins
EntireX Management Tools
EntireX Security (not installed by default)
EntireX DCOM
3rd Party Products
A silent installation, once it has been started, requires no additional user interaction.
To perform a silent installation with Eclipse Plug-ins
Enter
"\\<server>\Windows\EXX\Setup.exe" /V"PATHTOFILE=\\<server>\<License file> ECLIPSE_INSTALL="Yes" /Leoi %temp%\EXX73inst.log /qr"
To perform a selective silent installation
Use the property ADDLOCAL="feature1,feature2,..."
for example
"c:\temp\Windows\EXX\Setup.exe" /V"ADDLOCAL="RuntimeFiles,DeveloperTools" PATHTOFILE=a:\Exx73.xml /Leoi c:\temp\EXX73inst.log /qr"
Valid Windows Features are:
RuntimeFiles
SMH_Agents needed for DeveloperTools, BrokerKernel
DeveloperTools
ExxVSStudioPlugins
Examples
BrokerKernel
Security
DCOM
Exx3rdParty
To perform a silent installation with location transparency
settings
Enter, for example
"c:\temp\windows\exx\setup.exe" /V"ADDLOCAL=RuntimeFiles,DeveloperTools PATHTOFILE=A:\ USELDAP=1 LDAPHOST=<LdapServer> LDAPPORT=389 LDAPBASEDN="CN=test,CN=users,DC=LdapServer,DC=com" /Leoi "%temp%\exx73inst.log" /qr"
The EntireX Mini Runtime is a set of components that may be used for the deployment of applications using the Broker ACI, the Broker RPC, and - under Windows only - DCOM Wrapper objects and the Broker ActiveX Control. Unlike the full EntireX Runtime, the Mini Runtime does not include Java capabilities.
The EntireX Mini Runtime is delivered as install kit entirexminiruntime.exe located in the <EntireX Home>\etc directory. This install kit installs the Broker stubs, the 3GL RPC runtime and the Broker ActiveX Control.
To start the default silent installation
Enter the command:
entirexminiruntime.exe /V"/Leoi %temp%\entirexminiruntime.log /qr"
To start the silent installation with security (secuexit.dll)
Enter the command:
entirexminiruntime.exe /V"ADDLOCAL=CommonFiles,BrokerActivex,Security /Leoi %temp%\entirexminiruntime.log /qr"
To start the silent installation with security and encryption
Enter the command:
entirexminiruntime.exe /V"ADDLOCAL=CommonFiles,BrokerActivex,Security,Encryption
/Leoi %temp%\entirexminiruntime.log /qr"
Notes:
"ALLUSERS=2".
The installation procedure automatically creates a Broker instance ETB001 in subdirectory EntireX\Broker\ETB001. If an instance already exists in that directory, the attribute file is renamed toETB001.ATR.BAK, and an additional backup is created in directory %Temp%. A default attribute file named ETB001.ATR will be created. This Broker instance is ready to be started, but additional services may have to be defined in the attribute file.
Note:
All Broker instances reside in subdirectories of the
EntireX\Broker directory. The directory name is identical
to the Broker ID. The Broker attribute file and the Broker log files can be
found in that subdirectory.
The EntireX Broker Service etbsrv.exe must be active on every machine where a Broker instance is running. The installation procedure installs it with startup type "automatic" and with status type "started". etbsrv.exe is in the Bin subdirectory of the EntireX installation directory.
 |
Warning: User account SAGUSER added during installation of System Management Hub |
During installation of System Management Hub, a user account SAGUSER is added to the Administrators group of your local machine. SAGUSER is not an interactive account; login to the Windows desktop is not possible, and no other resources can be used. SAGUSER is required by several Software AG services to operate correctly, and therefore must not be deleted or modified. For more information please see the Sytem Management Hub Installation documentation.
Eclipse is an optional component of EntireX Communicator. For EntireX Workbench, it is required. If you have not already installed Eclipse at your site, you can install Eclipse and the EntireX Workbench from the installation medium. If you wish to install the EntireX Workbench into an existing Eclipse environment, use the Eclipse update mechanism to deploy the EntireX Communicator feature.
Under Windows, JDK is installed automatically with all installation options (typical, runtime and custom).
During installation you are prompted for a CentraSite URL. If CentraSite is installed in your network, enter the URL under which CentraSite is accessible. The installation verifies the connection and stores the connection data for use by the Eclipse Preferences. See CentraSite Configuration.
To remove files and registry entries created during the installation
of EntireX
From the Control Panel, choose Add or Remove Programs.
Select the instance of EntireX you wish to uninstall.
Choose Change/Remove and confirm.
Environment variables such as ETB_TRANSPORT, for example, must be removed manually.
If an update kit for EntireX is available, we strongly recommend you install this kit after installing EntireX as described above. The update kit represents updates or corrections to features that are installed during the main EntireX installation.
To install the update kit, execute the file EX nnnnn.exe on <CD-Root>\windows.
We also recommend you regularly check ServLine24 at http://servline24.softwareag.com/public/default.htm for update kits of EntireX. Alternatively you can subscribe to a variety of services under http://servline24.softwareag.com/SecuredServices/. Choose to be notified of any updates by e-mail.
To verify successful installation, you can use the
etbinfo utility. It queries the Broker for information
as described below.
If you have not already created a default Broker, create one using SMH. See Adding a Local Broker
Start the Broker using SMH.
Run etbinfo to get back a response from the
broker. Start a Command Prompt session, change your directory to
Etbinfo, e.g. C:\Program Files\Software
AG\EntireX\Broker\Etbinfo and use the following command:
etbinfo -blocalhost -dBROKER -pbroker.pro
This assumes that you use the default port 1971. Otherwise use the command:
etbinfo -blocalhost:port -dBROKER -pbroker.pro
where port is the port number of your broker.
This should display a simple formatted report with information about the broker.
