Entire Net-Work 7 components include: Entire Net-Work Server and Entire Net-Work Client. In addition, Entire Net-Work 7's e-business model makes use of a number of other Software AG products to achieve its goals:
Adabas Directory Server
Adabas Manager
This document covers the following topics:
An Entire Net-Work Client uses the Entire Net-Work 7 e-business message protocol to access Adabas databases. A Kernel does not need to be installed on the same system as a client.
Simply install an Entire Net-Work Client on any machine from which you wish to access Adabas databases. Only one Entire Net-Work Client installation is needed on the machine. Assuming the appropriate Kernels have been defined in your enterprise and the Adabas Directory Server entries have been migrated for Entire Net-Work, your client should be immediately able to access the Adabas databases it needs.
When you install Entire Net-Work Client, its Windows service or Linux daemon is installed. Using the Adabas Manager (AMN), you can define multiple client configurations within Entire Net-Work Client. Multiple client configurations allow you to control how 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 information about using partitioning and filtering, read Understanding Partitioning and Understanding Filtering.
When you receive your Entire Net-Work Client package, it includes installation code for a default client configuration.
Note:
If you attempt to install and use Entire Net-Work Client 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 Client 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.
An Entire Net-Work Server uses the Entire Net-Work 7 e-business message protocol to access Adabas databases. Using Entire Net-Work Server, you can set up multiple Kernels that can be used to access Adabas databases. A server does not need to be installed on the same system as an Entire Net-Work Client.
Simply install an Entire Net-Work Server on any machine where you wish to define Kernels. Only one Entire Net-Work Server can be installed on a machine. Kernel definitions are required on every machine on which an Adabas open system database resides, if you want your Entire Net-Work Clients to be able to access the open system database.
When you install Entire Net-Work Server, its Windows service or Linux daemon is installed. Using the Adabas Manager (AMN), you can define multiple Kernels within Entire Net-Work Server. Multiple Kernels allow you to control how your network is used. Each Kernel can have its own partition, filter, database, trace, user exit, and Directory Server settings. In other words, by specifying database access definitions for particular Kernels, you can control which databases are accessible and what trace and user exit settings are used for the client requests to those databases.
For more information about Entire Net-Work Server and Kernel parameters, read Managing Servers and Managing Kernels. For information about using partitioning and filtering, read Understanding Partitioning and Understanding Filtering.
When you receive your Entire Net-Work Server package, it includes installation code forEntire Net-Work Server. This includes code necessary to define and maintain Entire Net-Work Kernels.
Note:
If you attempt to install and use Entire Net-Work Server 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 Server 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.
The Entire Net-Work 7 Kernel provides access to local and e-business Adabas databases. It requires a set of standard URLs (maintained using the Directory Server) to control its activities. A Kernel must be installed on each machine on which a database resides if you want Entire Net-Work clients to reach it.
In addition, if your Entire Net-Work Clients need to communicate with databases on the mainframe or with databases managed by a classic Entire Net-Work 2 Kernel, a single Entire Net-Work 7 Kernel must be used as a bridge to provide this access. In this case, the Kernel used can be one already defined on a system with a local database. It can also be a Kernel that is defined standalone on a machine without a local database. You will need to evaluate your network traffic to determine which configuration works best for your site.
The Entire Net-Work 7 Kernel is the most complex component in the product because it provides various migration bridge technologies to assist you.
A Kernel provides access to local Adabas databases. It manages Directory Server URLs so that all e-business clients can use the new e-business message protocol to access the database via the Kernel. In addition, it broadcasts local database availability to all connected classic nodes so that clients on those nodes can also access the database via the older protocol.
The Kernel finds local databases by examining the ADABAS.INI file on the local system, which is maintained by the Adabas DBA Workbench. If you use Adabas command line tools to define your databases, instead of the DBA Workbench, the database definitions are not added to ADABAS.INI and must be added manually if you want the Entire Net-Work Kernel to provide access to all of your local databases. Software AG does not recommend that you mix the usage of the DBA Workbench and command line tools to define your databases. In this case, only the databases listed in ADABAS.INI will be processed.
If no ADABAS.INI file is found or if it exists but contains no DBID entries (under DB_LIST), the Entire Net-Work Kernel will poll the local system for all 255 potential database IDs and register those it finds.
A Kernel provides access from e-business clients to databases on connected classic nodes using the older Entire Net-Work protocols. When a classic node connects or is connected to, the Kernel detects available remote databases and manages Directory Server URLs accordingly. Consequently, e-business clients can send Adabas calls to the Kernel where they will be converted to the older Entire Net-Work protocol and relayed to the classic node. Each reply is reconverted to the newer, e-business protocol and returned to the client. The Kernel also keeps track of database transitions (starts, stops, crashes), connections, and disconnections for databases on connected classic nodes.
A Kernel provides access from classic Entire Net-Work to e-business Adabas databases. When an e-business database is connected to a Kernel, the database availability is broadcast to all connected classic nodes using the older Entire Net-Work protocol. Classic Entire Net-Work can then send Adabas calls to the Kernel where they will be converted into the e-business protocol and sent to the database. Replies are reconverted to the classic message protocol and relayed back to the client.
Note:
Currently mainframe e-business Adabas database access is only
supported if Entire Net-Work 6 (or later) ADATCP or Simple Connection Line Driver
(TCPX line driver) are installed on the mainframe host.
In summary, once all classic connection definitions have been converted, the Entire Net-Work 7 Kernel, using the Directory Server entries, becomes the bridge between classic Entire Net-Work installations and new e-business Entire Net-Work 7 installations.
You can set up partitioning of Kernel entries to direct Kernel requests to specific databases. This partition information can be specified during installation or later using the Adabas Manager (AMN). Partition information is stored in the Directory Server. For more information, read Understanding Partitioning.
Entire Net-Work uses information stored in a Directory Server to send and receive messages from the client to the database and back. The Directory Server contains an entry for each Kernel and database in the network.
 |
Warning: The Directory Server is critical to the functions of Entire Net-Work 7. It should be on a dedicated system that is operational 24 hours a day, with a UPS. The location of the Directory Server must be specified to the Kernel and clients when they are installed. In addition, the location of the default Directory Server may be defined in the SAGXTSDSHOST entry in the DNS. You may need to consult with your Information Technology department to make updates to the DNS. If no Directory Server can be found for your enterprise, Entire Net-Work cannot function. |
All Directory Server data is stored in the form of a Universal Resource Locator (URL) that is familiar to any Internet user. The Directory Server allows complex URLs to contain management data for Entire Net-Work using this standard industry-wide syntax. More importantly, an Entire Net-Work Kernel can dynamically add, modify, or delete client access URLs in the Directory Server.
Entire Net-Work 7 also supports communications using Secure Sockets Layer (SSL) target entries in the Adabas Directory Server. For more information about target entries in the Directory Server, read Directory Server Target Entries in the Concepts chapter of the Software AG Directory Server Installation and Administration Guide. In addition, an SSL Toolkit is provided that allows you to set up a certificate authority that you can use 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.
An Entire Net-Work Client only needs to be able to extract the location of the Adabas database it is trying to access from the Directory Server. Consequently, a single Directory Server URL is required for each database in the enterprise in order for all e-business clients to access that database. If Entire Net-Work partitioning is used, more than one Directory Server entry may exist for a given database. For more information, read Understanding Partitioning.
When operational changes occur for a database (startups, shutdowns, and movement between machines), the Entire Net-Work Kernel automatically maintains the URLs in the Directory Server: it adds a URL to the Directory Server when it discovers a database (and can accept Adabas calls intended for that database); likewise it can remove the same URL when a database becomes unavailable.
At least one Adabas Directory Server should be installed in your enterprise; we recommend that you install only one Directory Server to ensure centralized administration. However, your enterprise network configuration may require more than one. For example, you may want to install more than one Directory Server to fully direct requests to specific databases. While partitioning can also be used to restrict database access, all entries (in all partitions) of a Directory Server can be maintained via the Adabas Manager, so restriction is not complete. If, however, you use multiple Adabas Managers, you can limit what entries are available for viewing in the Directory Server portion of the Adabas Manager.
Directory Server administration is performed using the Adabas Manager. The Directory Server administration function allows you to populate this directory with entries that identify the address of each target in your network.
Note:
If you attempt to install Entire Net-Work in a system with a firewall in
place, be sure that your system administrator has opened the firewall for the
Adabas Directory Server port or the installation may not complete successfully.
The port number used by the Directory Server can be changed, but must be changed with care. For complete information on changing the Directory Server port used by Entire Net-Work 7 components, read Changing the Adabas Directory Server Port Number.
Adabas Manager performs Entire Net-Work, Entire Net-Work Client, and Adabas Directory Server management tasks.
Adabas Manager (AMN), provides centralized management of all Software AG products installed in the enterprise, using a Web-based graphical user interface. Use of Adabas Manager eliminates the need for a system administrator to visit individual machines or maintain multiple product windows on the desktop.
Adabas Manager can be used to manipulate configuration information. Using Adabas Manager, you can easily change the URLs stored in the Directory Server without fully understanding the syntax. In addition, the Entire Net-Work Servers and Entire Net-Work Clients can be examined and controlled via Adabas Manager. The status of classic nodes and databases for which connections have been defined can be determined. Statistics can be examined and various control functions, such as node disconnection, Kernel shutdown, and trace settings can be performed.
|
Warning: Adabas Manager should be on a dedicated system that is operational 24 hours a day. If Adabas Manager is not available, you cannot maintain and control Entire Net-Work, Entire Net-Work Client, or Adabas Directory Server. |
If Adabas Manager is already installed in your enterprise, it should not be installed again. Only one Adabas Manager is required to manage all Software AG products that require it.
For more information about the management tasks that can be performed using Adabas Manager, refer to Using Adabas Manager.
Entire Net-Work 7 also 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 Concepts chapter of 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.