This document covers the following topics:
Entire Net-Work Client 1.2.2 is a complete replacement for any prior version of Entire Net-Work Client. Before you install Entire Net-Work Client 1.2.2, be sure to uninstall prior versions of the product. Multiple versions of Entire Net-Work Client cannot be installed on the same system at this time.
Last-minute information on problems that have been addressed by this release are described in the ReadMe file.
The following enhancements have been made to this release of Entire Net-Work Client:
Support for various UNIX platforms has been added. For a list of the UNIX environments supported by Entire Net-Work Client, read Supported Platforms.
This release includes Directory Server 5.2.1.1, which includes a change in the Directory Server port number behavior.
When Directory Server 5.2.1.0 was released (with products such as Entire Net-Work 7.3.1 and Entire Net-Work Client 1.2.1), Directory Server ports set to "0" defaulted to the new IANA port number, 4952. This caused some problems with existing applications that expected port 0 to default to 12731. As a result of these problems, in Software AG Directory Server 5.2.1.1 the default for port 0 has been changed back to 12731, shipment of Directory Server 5.2.1.0 has been discontinued, and new Directory Server installations can no longer use port 0. If you upgrade Software AG products that used Directory Server 5.2.1.0 (such as Entire Net-Work 7.3.1 and Entire Net-Work Client 1.2.1) to newer versions of their software, be aware that the upgrade (or reinstallation) to Directory Server 5.2.1.1 will inherit any port 0 settings from the prior release. In these cases, you will need to manually modify the Directory Server port number to a valid non-zero port number after the upgrade (or reinstallation), as described in Modifying a Directory Server Link Definition . For more information about port number usage in Entire Net-Work, read Port Number Reference.
Entire Net-Work Client 1.2.1.1 is a complete replacement for any prior version of Entire Net-Work Client. Before you install Entire Net-Work Client 1.2.1.1, be sure to uninstall prior versions of the product. Multiple versions of Entire Net-Work Client cannot be installed on the same system at this time.
Last-minute information on problems that have been addressed by this release are described in the ReadMe file.
The following enhancements have been made to this release of Entire Net-Work Client:
You can now specify the path to a location in which you want your Entire Net-Work Client configuration files stored. This path is specified when you add the client configuration. For more information, read Adding Client Configurations and About Client Configurations.
Entire Net-Work Client 1.2.1 is a complete replacement for any prior version of Entire Net-Work Client. Before you install Entire Net-Work Client 1.2.1, be sure to uninstall prior versions of the product. Multiple versions of Entire Net-Work Client cannot be installed on the same system at this time.
Last-minute information on problems that have been addressed by this release are described in the ReadMe file.
The following enhancements have been made to this release of Entire Net-Work Client:
A Windows service is now installed for each copy of Entire Net-Work Client you install. This service maintains an access entry for the Software AG Directory Server you elected to use during installation. The System Management Hub (SMH) agent installed with Entire Net-Work Client uses this Windows service to display the client entries defined in the Directory Server and allows you to maintain parameters and settings for them.
Only one Entire Net-Work Client service can be installed on a given machine. The Entire Net-Work Client service may need to be started manually, depending on the startup option that is selected when Entire Net-Work Client is installed.
For more information about the Entire Net-Work Client component of Entire Net-Work, read Entire Net-Work Client. For information about the installation and administration of Entire Net-Work Client, read Entire Net-Work Client Installation and Administration.
In past releases of Entire Net-Work Client, only a single client configuration was allowed with each Entire Net-Work Client installed. With this release, you can define multiple client configurations within an Entire Net-Work Client service. Multiple client configurations allow you to control how different clients use your network. Each client configuration can have its own partition, filter, database, trace, user exit, and Directory Server settings. In other words, by directing client requests to particular client configurations, you can control which databases are accessible and what trace and user exit settings are used for the client request. For more information about client configuration parameters, read Maintaining Client Configuration Parameters. For information about using partitioning and filtering, read Understanding Partitioning and Understanding Filtering.
To identify which client configuration should be used by your application, read Identifying the Client Configuration to Your Application.
Client configurations and all of their parameter settings can now be maintained remotely using the System Management Hub (SMH). For more information, read Entire Net-Work Client Administration.
This Entire Net-Work Client release supports all features of Entire Net-Work 7.3.
This release of Entire Net-Work Client supports networking between Adabas 6 (open systems) and Adabas 8 (mainframes) databases. For complete information about these Adabas products, refer to their documentation sets.
A new IANA port, 4952, has been assigned the Software AG Directory Server.
For more information about port number use in Entire Net-Work, read Port Number Reference.
Port numbers are now dynamically assigned by Entire Net-Work when the client is started, as follows:
Entire Net-Work searches for the first available port starting from port 49152 through 65535. (The starting search port number, 49152, is the IANA-recommended value from which to start.).
Once an available port number is found, it is assigned to the client in its Software AG Directory Server entry.
For more information about port number use in Entire Net-Work, read Port Number Reference.
In past releases of Entire Net-Work, access and connection definitions were stored in the Software AG Directory Server. However, with this version of Entire Net-Work, these definitions are stored in files in the local installation directories; they are no longer stored in the Directory Server. Thus, once the definitions are defined, your Entire Net-Work connection and access capabilities are not affected if the Directory Server becomes unavailable for some reason.
The user exit support provided in classic Entire Net-Work 2 is now supported in Entire Net-Work Client 1.2 with some enhancements. In classic Entire Net-Work 2, only one user exit could be specified for the whole network. In Entire Net-Work Client 1.2, however, a single user exit can be specified for each Entire Net-Work Client configuration you create.
The user exits you used in Entire Net-Work 2 are still valid and supported by Entire Net-Work Client 1.2. No user exit code changes are necessary, however, you must rebuild and recompile any existing Entire Net-Work 2 user exits into the Entire Net-Work Client 1.2 installation library so they will be recognized by Entire Net-Work Client 1.2.
For more information about the use of user exits in Entire Net-Work Client 1.2, read Understanding the User Exit Interface
If the Software AG Directory Server is installed and used by a prior version of Entire Net-Work Client, be sure to use the existing Software AG Directory Server port number setting for the Entire Net-Work Client 1.2 installation. You can change the port number after Entire Net-Work Client 1.2 is installed. For complete information on changing the Directory Server port number used, read Changing the Software AG Directory Server Port Number.
The documentation for this product has been updated for this release. When additional updated versions of the documentation are created, you can review them on the Software AG documentation web site: http://documentation.softwareag.com/. The documentation at this site will be updated as required. If you have a maintenance contract, past versions of documentation can be reviewed by linking to the following Software AG ServLine24 web site: http://servline24.softwareag.com/public/. If you do not have a ServLine24 user ID and password yet, you will find instructions for registering on this site (free for customers with maintenance contracts).
The Entire Net-Work Client documentation includes:
online HTML topics describing all aspects of the product;
Adobe Acrobat Reader Portable Document Format (PDF) files created from the HTML topics;
Adobe Acrobat Reader Portable Document Format (PDF) files of a book created from the HTML topics.
Documentation for the Software AG Directory Server can be found in Software AG Directory Server Documentation.
The System Management Hub documentation can be found in the System Management Hub installation. For example, if SMH is installed in Windows at C:\Program Files\Software AG\ System Management Hub, then the SMH documentation can be found in: C:\Program Files\Software AG\System Management Hub\help\doc\overview.htm. Likewise, in UNIX environments, if the SMH installation is located at $SAG/common/arg, then the SMH documentation can be found in $SAG/common/arg/help/doc/overview.htm.
No hard-copy documentation is provided, but you can print the PDF and HTML files on your local printer.
With Service Pack 2 (SP2) for Windows XP and Service Pack 1 (SP1) for Server 2003, Microsoft introduced a range of powerful new security features that restrict active content that runs locally on your computer. Active content includes ActiveX controls, Java applets, and JavaScript. Software AG's documentation web pages contain some JavaScript, and the SEARCH, INDEX and CONTENTS capabilities are implemented as Java applets. As a result, when viewing documentation web pages that reside on your PC using Internet Explorer and Mozilla Firefox under Windows XP SP2, note that active content is blocked. You must explicitly and repeatedly allow active content if you want to make use of the documentation's full navigation features. Note that this behavior is only observed when reading web pages installed locally on your PC, including those on CD in the PCs CD-ROM drive.
The active content for which Software AG is responsible, that is, the JavaScript code in our HTML documentation pages, will not harm your computers. The risk in using the navigation applets is negligible: Software AG has received no reports from users concerning any harm caused to a computer by the applets. We therefore suggest that when reading Software AG documentation in a local context, you should allow active content via the Security settings in the browser (with Internet Explorer, usually found under Tools > Internet Options > Advanced).
Full details of alternatives can be found on the home page of the suppliers of the navigation applets: http://www.phdcc.com/xpsp2.htm.
