This section describes how to install Entire Access on a Windows server. It covers the following topics:
Supported Windows servers are:
Windows 2008 R2 Server
Windows 2012 Server
Windows 2016 Server
Windows 2019 Server
Except where indicated, the installation described in this section applies to all the above servers.
Please read the following information, before you proceed with the installation:
See Client and Server Versions in the section Installing a Server under UNIX.
The following are the minimum hardware and operating-system requirements for Entire Access servers:
512 MB of RAM,
about 10 MB of available hard-disk space (if all options are installed).
Natural Version 8.4 or above is required for Natural clients.
TCP/IP is required on both client and server machines for remote access.
For information about the use of third-party network products, see the section Remote Data Access Using Third-Party Network Products.
Entire Access supports the data sources listed below. Except where noted, access can be either local or remote.
The following database server versions are supported on Windows servers:
Adabas D 15
DB2 10 and 11
Informix 11 and 12
Oracle 12c, 18c and 19c
Sybase 15, 16 CTLIB and DBLIB
Microsoft SQL Server 2012, 2014, 2016, 2017 and 2019
ODBC-compliant servers (local access)
There is one Adabas D DLL driver for Windows platforms:
AAD15.DLL for Adabas D 15
There is one DB2 DLL driver for Windows platforms:
DB2.DLL for all supported DB2 versions
There is one Informix DLL driver for Windows platforms:
INF.DLL for all supported Informix versions
Use the Informix utility SETNET32.EXE to set the following
Informix variables for Entire Access:
If a conflict occurs with Natural shared memory, adjust the
SHMBASE by changing the
SHMBASE 0XC000000L to
There is one Oracle DLL driver for Windows platforms:
ORA.DLL for all supported Oracle versions
If the environment variable
is set, this value is used as the name of the Sybase server. If
DSQUERY is not set, the default SYBASE is used.
Consult your Sybase documentation for information about this variable.
Unless you use the default server name SYBASE, you must either define the server name in the INTERFACES file or pass the name in the connect string.
There are two Sybase DLL drivers for Windows platforms:
SYBCT.DLL for all supported Sybase CTLIB
SYBDB.DLL for all supported Sybase DBLIB
Software AG recommends that new customers use Sybase CTLIB, not Sybase DBLIB, as their default driver.
There are two Microsoft SQL Server DLL drivers for Windows platforms:
MSSQLODBC.DLL for MS SQL Server 2012, 2014,
2016, 2017 and 2019 using SQL Server's ODBC interface.
The SQL Server database to be accessed has to be defined as a data source using the Microsoft ODBC Administrator. Natural 8.4 or above is a prerequisite for using the MSSQLODBC interface.
MSSQLODBCN.DLL for MS SQL Server 2012, 2014,
2016, 2017 and 2019 using SQL Server's ODBC native client interface.
The SQL Server database to be accessed has to be defined as a data source for the SQL Server native client interface using the Microsoft ODBC Administrator. Natural 8.4 or above is a prerequisite for using the MSSQLODBCN interface.
There are two ODBC (Open Database Connectivity) DLL drivers for Windows platforms:
VTX11.DLL for local ODBC access
ODBCNET.DLL for remote ODBC access
This implies that the actual ODBC driver from the vendor (for example, DataDirect) will be installed and that the data source will be defined using the Microsoft ODBC Administrator.
The Entire Access installation package contains two CDs:
The server CD contains the Windows server components.
The client CD contains the Windows client components only.
Perform the following steps to install Entire Access on a Windows server.
Insert the server CD into a CD drive.
To start the installation program, invoke the CD autorun.inf file. It begins the installation program automatically when the CD drive is closed. Or, to start the installation program manually, issue the following command at the command prompt, where x is the selected CD drive:
The InstallShield Wizard is invoked to perform the installation tasks. The Entire Access Welcome message appears when the load is complete.
Follow the directions concerning the License Agreement.
Enter your customer information, including your selection regarding Administrator rights. Be sure to read the statement regarding Administrator privileges.
Select the appropriate Destination Folder designations.
Chooseto proceed with the installation (or to terminate the setup program).
Review the settings before copying the files.
Review the README file as necessary.
Decide whether you will restart your computer now or later. Restarting now is recommended.
Entire Access depends on Environment Variable updates that get established after restart.
After your computer is restarted, the InstallShield Wizard continues. Although an InstallShield window appears, it does not take long to complete, depending on your processor speed and whether other applications are also being restart.
Your Entire Access installation is now ready to function as:
a local RDBMS server for a remote Natural application,
a local RDBMS server for a local Natural application,
a host for a local client application that will connect to a remote RDBMS elsewhere in the network.
%INFORMIXSERVER% variable is
not set for your environment, error -25560 will be issued when you attempt to
connect to the database server.
To set the
Launch Setnet32 from the %INFORMIXDIR%\bin directory and select the Environment tab.
INFORMIXSERVER in the list
of variables and select it. Type the server name into the entry box and then
click the Set button.
SHMBASE problems that are
related to other products can often be resolved by adjusting the
SHMBASE for Informix, as follows:
Assume that your Informix server name as defined in the
INFORMIXSERVER variable is
Copy and then edit the
%INFORMIXDIR%\etc\ONCONFIG.inf92 and change the
SHMBASE 0xC000000L # Shared memory base address
SHMBASE 0x2000000L # Shared memory base address