Entire Net-Work is the backbone of Software AG's distributed computing technology. It is middleware that provides a common communication service for database applications, query tools, cooperative processing applications, application development tools, and other software. Its primary function is to transmit Adabas calls from a client application to a remote Adabas database. However, it is also used by clients to access other Software AG product servers (such as those for EntireX Communicator, Tamino, or Adabas SQL Gateway).
Entire Net-Work key performance indicator (KPI) statistics are provided to webMethods Optimize for Infrastructure. Using the Optimize component of webMethods Optimize for Infrastructure, you can monitor the status of these statistics as well as the overall status of your system. This support is available in version 8.2 (and later versions) of webMethods Optimize for Infrastructure.
In addition to Entire Net-Work for open system platforms (Windows and UNIX), other versions of Entire Net-Work run on a range of hardware and software platforms including IBM mainframes. Using Entire Net-Work, organizations can implement applications distributed across multiple heterogeneous platforms.
Entire Net-Work 7, also referred to as the e-business model, is the next generation of Entire Net-Work for open systems (previously at Version 2), which is now referred to as the classic model. If you intend to migrate from Entire Net-Work 2 to Entire Net-Work 7 on your open system platforms, we recommend that you read Planning for Entire Net-Work 7 for a complete description of the differences between these Entire Net-Work releases and the steps you should take to perform the migration.
Once you have installed the Entire Net-Work Client components, you must manually make updates in the System Management Hub (SMH) if you need to support the Simple Connection Line Driver. For more information, read Required Post-Installation Updates for Simple Connection Line Driver Support.
Note:
If you attempt to install and use Entire Net-Work in a system with a
firewall in place, be sure that your system administrator has set up the
firewall so that the Entire Net-Work component applications can access the ports they
need (including the Adabas Directory Server port and those Entire Net-Work dynamically assigns
during its own processing). For more information about Entire Net-Work ports, read
Port Number
Reference. For information about
configuring Entire Net-Work components for Windows personal firewall, read
Configuring Product
Components for Windows Personal Firewall, in the
Entire Net-Work Server LUW Installation and Administration Guide.
This document provides an overview of Entire Net-Work 7 for open system platforms. It covers the following topics:
| Architecture |
| Components |
| Understanding Partitioning |
| Understanding Filtering |
| Getting Started |