This section provides answers to a number of frequently asked questions about Entire Net-Work 7.2 (and later releases) and the migration from Entire Net-Work 2 to Entire Net-Work 7.2 (and later releases).
Must there be an Adabas database running on every system with an Entire Net-Work 7 Kernel running?
Must there be an Entire Net-Work 7 Kernel running on every system running an Adabas database?
How do I select the systems on which I should install Kernels?
How do I change configuration information for an Entire Net-Work 7 Kernel?
How do I change configuration information for a Directory Server?
How do I change configuration information for the Adabas Manager (AMN)?
When should I uninstall my existing classic Entire Net-Work 2 Kernels and clients?
Can I run both e-business and classic Entire Net-Work Kernels concurrently on the same machine?
Can Entire Net-Work 7 be installed from a central network disk server?
Does Entire Net-Work 7 run as a Windows service or as an application?
How can I run Production and Test environments on a single UNIX system with separate databases?
What is the advantage of running Entire Net-Work 7 as a Windows service?
How can I run Production and Test environments on a single UNIX system with separate databases?
I have a database on my mainframe with an ID above 255. Are there extra precautions I should take?
Should the Directory Server and Adabas Manager be installed on the same system?
With Entire Net-Work 2, I needed to allocate a unique node ID for each node. Where do I do that now?
With Entire Net-Work 2 there was a limit of 255 remote nodes per Kernel. Has that limit changed?
Must the Web browser run on the same system as Adabas Manager?
Can I install an Entire Net-Work 7 Kernel and client on the same system?
After I install an Entire Net-Work 7 Kernel, how do I configure it to access local databases?
Why do I need to reboot my Windows PC after installing Entire Net-Work 7?
How can I make Entire Net-Work 7 use Secure Sockets Layer (SSL)?
An e-business Adabas is a database that can communicate with an Entire Net-Work 7 client without the use of an intermediate Entire Net-Work 7 Kernel. Instead, it communicates via the ADATCP component or with the Simple Connection Line Driver (TCPX line driver) component provided with Entire Net-Work 6 (or later).
The e-business model refers to the new Entire Net-Work 7 model which does not require that an Entire Net-Work Kernel be installed on the client system, uses Directory Server entries to locate Adabas databases, and uses the new e-business transport protocol.
An e-business client is any Adabas client application that uses the Entire Net-Work 7 e-business model and its associated message protocol and Directory Server entries to access Adabas databases. Hence, all of the following applications are or can be e-business clients:
Jadabas client applications
Natural applications
Tamino applications
Adabas SQL Gateway applications
Any 3-GL user-written application that makes the Adabas() call.
The new e-business message protocol is a new message protocol (referred to internally as the A1 protocol). This protocol minimizes overhead and reduces the system processing load, thus increasing the speed of message transmission. It is one-third the size of the classic Remote Database Architecture (RDA) protocol used in classic Entire Net-Work 2 installations.
No. The Kernel can be installed on other systems and used to access databases on connected classic Entire Net-Work nodes (using the classic message protocol) and e-business Adabas databases.
Yes, if you want your users to be able to access the database remotely.
An Entire Net-Work 7 Kernel must be installed on every open system on which a local Adabas database resides. In addition, you can install Entire Net-Work 7 Kernels on other open systems if you want the Kernel to be used to access databases on connected classic Entire Net-Work nodes (using the classic message protocol) and e-business Adabas databases.
You can change configuration information for a Kernel using the System Management Hub. For more information, read Entire Net-Work Server Administration.
Configuration information for classic Entire Net-Work 2 Kernels must be changed as before.
You can change configuration information for a Directory Server using the System Management Hub. For more information, read Performing Directory Server Administration in the Software AG Directory Server Installation and Administration Guide.
Read the documentation provided with your Adabas Manager installation.
Yes, but we do not recommend it. In general, installing the two versions on the same system will not cause any problems, but running them at the same time might.
We recommend that you avoid this scenario. When you are ready to migrate a system to Entire Net-Work 7, stop the classic Entire Net-Work Kernel and install the Entire Net-Work 7 Kernel. The migration will happen smoothly, without complications, and you can use Entire Net-Work 7 to access the same databases you accessed using classic Entire Net-Work.
While it is possible to install and run an Entire Net-Work 7 Kernel on a system where an Entire Net-Work 2 Kernel is installed and running, choosing to do so is an advanced option. We recommend that you contact your Software AG technical support representative for assistance in doing this.
No. This is not recommended.
We recommend that you install Entire Net-Work 7 Kernels and clients in a test environment prior to applying it to your entire network.
Once you are satisfied that the test system is running smoothly, install Entire Net-Work 7 Kernels and clients on the rest of your network systems, as necessary.
Note:
If you are migrating from a classic Entire Net-Work installation
(Version 2) to Entire Net-Work 7.5, use the Configuration Utility provided with
Entire Net-Work 7.2 to migrate to 7.2 and then use the Directory Server entries
created for 7.2 as a basis for your manual configuration to Entire Net-Work 7.5;
migration to Entire Net-Work 7.5 must be performed manually.
Once you are satisfied that the Entire Net-Work 7 Kernels and clients are running satisfactorily, you can safely remove your existing Entire Net-Work 2 Kernels and clients. The installation of this product requires that you uninstall any Entire Net-Work version 2 products, once your testing and migration to Entire Net-Work 7 is complete and before you attempt to use Entire Net-Work 7 in your licensed production environments.
When you have installed comparable Entire Net-Work 7 Kernels and clients and you are satisfied with their operation.
Yes, but we do not recommend it.
We recommend that you avoid this scenario. When you are ready to migrate a system to Entire Net-Work 7, stop the classic Entire Net-Work Kernel and install the Entire Net-Work 7 Kernel. The migration will happen smoothly, without complications, and you can use Entire Net-Work 7 to access the same databases you accessed using classic Entire Net-Work.
While it is possible to install and run an Entire Net-Work 7 Kernel on a system where an Entire Net-Work 2 Kernel is installed and running, choosing to do so is an advanced option. We recommend that you contact your Software AG technical support representative for assistance in doing this.
Yes. You must have a unique license key for each Entire Net-Work 7 Kernel you install. Entire Net-Work 7 is the first Entire Net-Work version to require this.
Yes, but a unique license key is still required for each Entire Net-Work 7 Kernel you install.
Either. When you install an Entire Net-Work 7 Kernel, you are prompted to indicate whether or not you want it running as a Windows service.
Use the partitioning feature introduced with Entire Net-Work 7. For more information, read Partitioning.
When you run Entire Net-Work 7 as a Windows service, it will automatically start up when your system is started.
Use the partitioning feature introduced with Entire Net-Work 7. For more information, read Partitioning.
No. The NET_WORK_ID environment variable is not used by Entire Net-Work 7. Instead, use the partitioning feature introduced with Entire Net-Work 7. For more information, read Partitioning.
No. "Domaining" is not used by Entire Net-Work 7.2 and is not migrated during Configuration Utility processing. Instead, use the partitioning feature introduced with Entire Net-Work 7. For more information, read Partitioning.
No. All that manual configuration has been eliminated. Once you have established an Entire Net-Work 7 Kernel on each system with a database, client access is automatic (unless partitioning is used).
Yes. It is better to plan ahead for a database ID greater than 255 than to fix problems later. If you use the ADATCP features or the TCPX line driver of Entire Net-Work 6 (or later) on your mainframe, your Entire Net-Work 7 clients will be able to access that database directly. If you have clients accessing the database via Entire Net-Work 2 on Open Systems, you will need to retain those Entire Net-Work 2 systems until your migration to Entire Net-Work 7 is fully tested and complete.
Entire Net-Work 7 can handle this in two ways.
You can set up separate Directory Servers; one for each database with the same database ID. While this may seem a simple solution, it requires that you manage and administer multiple Directory Server configurations. In addition, your DNS and system settings must be set carefully to ensure that the correct clients are using the correct databases.
The more elegant solution is to use partitions, one partition for each database with the same database ID. Partitioning allows you to subdivide a single physical Directory Server into a series of logical partitions that do not interfere with each other. Using this solution, you have only one Directory Server to manage.
In addition, only your DNS settings need to be defined; defining system settings on client machines is no longer necessary. Instead, Clients can be defined as part of the partition to which the database they should access belongs.
For more information, read Partitioning.
You can set up separate Directory Servers; one for each database with the same database ID.
For example, multiple Directory Servers might be appropriate if your enterprise has multiple databases with the same database ID. However, in this case, you could also partitioning to direct specific Kernels and clients to those databases.
Yes. While Software AG recommends that you use only one Directory Server in your enterprise, you can set up as many Directory Servers as you wish, but remember:
You will have to manage and administer multiple Directory Server configurations.
The more Directory Servers you use, the more physical resources on your system will be consumed.
You will need to be very careful about which Directory Server you select to use in your installation of Entire Net-Work -- especially if other Directory Servers have been installed by other Software AG products.
As you are restricted to a single pointer to a Directory Server in your DNS (via its SAGXTSDSHOST and SAGXTSDSPORT entries), all systems required to use a different Directory Server must be redirected using local, manual, administration. For more information on this manual administration, contact your Software AG technical support representative.
Note:
You can also use partitioning to subdivide a single physical
Directory Server into a series of logical partitions that do not interfere with each
other. For more information, read
Partitioning.
The Directory Server and Adabas Manager can be installed on the same system, but it is not required.
Adabas Manager requires user authentication.
You do not need to use a node ID in Entire Net-Work 7 unless you are communicating with Entire Net-Work 5 on the mainframe using the RDA protocol. In Entire Net-Work 7.2 installations, the Kernel Configuration Utility will automatically migrate your old configuration file to URLs in the Directory Server, so there is no need for any manual configuration.
Note:
If you are migrating from a classic Entire Net-Work installation
(Version 2) to Entire Net-Work 7.5, use the Configuration Utility provided with
Entire Net-Work 7.2 to migrate to 7.2 and then use the Directory Server entries
created for 7.2 as a basis for your manual configuration to Entire Net-Work 7.5;
migration to Entire Net-Work 7.5 must be performed manually.
The node ID will become totally obsolete as classic Entire Net-Work 2 products are removed from your enterprise.
Yes. With Entire Net-Work 7, the only limit on the number of connections to a Kernel is imposed by the operating system. All previousEntire Net-Work limits on node connections have been removed. During internal tests of Entire Net-Work 7, Software AG has exceeded 1000 connections to a single Kernel.
Note:
Some mainframe databases do have limits on the number of
connections they can support. So the number of connections you can make from
Entire Net-Work 7 to these databases may be limited.
Yes. You may use any browser you wish. However, Software AG only tests with and warrants the use of Internet Explorer.
No. The Adabas Manager is a standard Web server application. It can be accessed by any Web browser in your enterprise. However you will need valid login credentials to the system running Adabas Manager.
You need only be concerned with node names when connecting back to the classic Entire Net-Work products. In the e-business world, system names are not used for identification. Each Entire Net-Work 7 Kernel determines the name of the local system and constructs an eight-character restricted name to use for the system in classic connections. So, yes, you do need to ensure that systems running Kernels have names that are unique in the first 8 characters as long as you are making classic connections.
Yes. This is unusual on a Windows machine, but it can be done without affecting applications. Remember that after the client installation, the ADALNK module (the Adabas linkage module for communication) becomes the e-business version so all remote databases will need to use the e-business message protocol. Installing both components on the same system will not affect local communication.
On Windows systems, there is a problem with compatibility between Adabas Version 3.2.2 databases and Entire Net-Work 7 clients installed on the same system. We recommend that you upgrade your databases to Adabas Version 3.3.1 or higher before installing an Entire Net-Work 7 client on the same system.
On UNIX systems, there are no restrictions or compatibility issues.
You don't. There are no manual steps required for local database access. You can start either the Kernel or the database first; the Kernel automatically detects the presence of a database and broadcasts or creates Directory Server entries for the database, as appropriate. It also detects when a database shuts down and removes the Directory Server entry for that database accordingly.
There may be a slight delay of a few seconds before the Directory Server entries match the current state of the database during transitions.
Entire Net-Work 7 does not use the same IPC mechanism used in classic Entire Net-Work systems. Consequently, the showipc utility and manual IPC cleanup are no longer required. However, the showipc utility is still delivered with Adabas.
By default, Adabas on open systems will create a demo database with an ID of "12". This has always been a problem if multiple databases with the same ID participate in networking connections. With Entire Net-Work 7 the chance of duplicate database IDs causing conflicts has been reduced because there are far fewer Kernels exchanging broadcast data.
The principle employed by an Entire Net-Work 7 Kernel when detecting a duplicate database ID broadcast, is to ignore it. Consequently, the first database detected with the ID will be used for all network traffic, even though the database may not be on the most efficient route.
Note:
With Entire Net-Work 7, you can also use partitioning to separate and
isolate databases with the same database ID. For more information, read
Partitioning.
No. With Entire Net-Work 7, there are far fewer Kernels and most client to database access is direct, without going through intermediate Kernels. So, routes between Kernels are not weighted, but are considered equal.
None. These are different terms used to describe the same technique: sending one or more messages from one Entire Net-Work component to another to test the communications path.
Both Software AG and its customers use ping and probe functionality as a performance measurement tool. Classic Entire Net-Work has a special probe message format for this test; e-business Entire Net-Work uses a simple database command (the CL command) to confirm database communication. Sometimes, this is called a ping. In Entire Net-Work 7, the term ping has become predominant.
Software AG works hard to keep the situations where a reboot is necessary after installation to a minimum. However, there are some instances where a reboot is necessary to start the Windows services associated with these components. You may need to schedule these installations for a time when such a reboot is non-disruptive.
Entire Net-Work 7 supports communications using Secure Sockets Layer (SSL). This support is provided using SSL protocol target entries in the Adabas Directory Server. For more information about target entries in the Directory Server, read Directory Server Target Entries in the Software AG Directory Server Installation and Administration Guide.
In addition, Software AG has an SSL Toolkit you can use, for testing purposes, to set up a certificate authority. You can then use the certificate authority to create security certificates for test purposes only. For more information about the SSL Toolkit, read Using the SSL Toolkit in the Encryption for Entire Net-Work User Guide, available from your Software AG support representative.
Note:
Due to export restrictions, the SSL Toolkit is not included on
the installation CD. If you plan to use SSL in your enterprise and want to use
the SSL Toolkit, please contact your Software AG support representative.