Entire Net-Work supports filtering of Entire Net-Work Client configurations and Entire Net-Work Kernel definitions by Adabas database ID. In this way, individual Entire Net-Work Client configuration definitions and Entire Net-Work Kernel definitions can apply to only specific databases.
Filtering is set up in the Adabas Manager for both client configurations and for Kernels. This document covers the following topics:
For Entire Net-Work Client configurations, database filtering is specified on the Client Parameters panel and allows you to identify databases that can be accessed by the client. If no databases are listed in the ACCEPTED_DBIDS field, all databases defined in the Adabas Directory Server can be accessed except those listed in the REJECTED_DBIDS field. Likewise, if no databases are listed in the REJECTED_DBIDS field, all databases in the Directory Server can be accessed, unless a specific list is provided in the ACCEPTED_DBIDS field.
For more information on setting these Entire Net-Work Client configuration parameters, read Maintaining Client Configuration Parameters.
You can filter Kernels by requests:
made to specific Adabas database IDs;
relayed to other Kernels;
submitted from other Kernels, by Kernel name;
submitted to and from specific machines, by machine name; and
submitted from other clients, by client name
This section covers the following topics:
For Entire Net-Work Kernel definitions, database filtering is specified on the Kernel Filters panel and allows you to identify databases for which service requests should be processed by the Kernel. If no databases are listed in the ACCEPTED_DBIDS field, the Kernel will process all requests to all databases defined in the Adabas Directory Server, except those listed in the REJECTED_DBIDS field. Likewise, if no databases are listed in the REJECTED_DBIDS field, the Kernel will process all requests to all databases defined in the Adabas Directory Server, unless a specific list is provided in the ACCEPTED_DBIDS field.
For more information on setting these Kernel parameters, read Maintaining Kernel Filters, in your Entire Net-Work Server documentation.
In the basic Kernel parameters, you can use the RELAY_TRAFFIC parameter to restrict whether or not requests to other Kernels in the network should be relayed by the Kernel. If the value of the RELAY_TRAFFIC field is "YES", requests are relayed to other Kernels; if the value is "NO", they are not.
For more information on setting these Kernel parameters, read Maintaining Kernel Filters, in your Entire Net-Work Server documentation.
A combination of Kernel parameters can be used to filter requests to the Kernel:
In the advanced Kernel parameters, you can use the UNSOLICITED parameter to indicate whether or not the Kernel will process service requests from other Kernels it has not included in its Kernel filter list. If "YES" is specified, Kernel filtering is ignored and any Kernel can submit service requests to the Kernel. If "NO" is specified, only Kernels included on the Kernel filter list can submit requests to the Kernel; all other unsolicited requests are ignored. The Kernel filter list parameters are governed by the ACCEPTED_KERNELS and REJECTED_KERNELS parameters.
If the UNSOLICITED advanced Kernel parameter is set to "YES", any Kernel can submit service requests to this Kernel, except Kernels listed in the REJECTED_KERNELS filter parameter on the Kernel filter list. If the UNSOLICITED advanced Kernel parameter is set to "NO", all unsolicited Kernel service requests are ignored, except for the Kernels listed in the ACCEPTED_KERNELS filter parameter on the Kernel filter list.
For more information on setting the UNSOLICITED parameter, read Maintaining Kernel Filters, in your Entire Net-Work Server documentation.
You can create a Kernel filter list to identify the Kernels from which service requests to the Kernel will be processed. The Kernel filter list is specified using the ACCEPTED_KERNELS and REJECTED_KERNELS parameters. Using these parameters, you can list Kernel names that should be accepted (service requests from these Kernels will be processed) or rejected (services requests from these Kernels will be rejected).
For complete information on the Kernel filter list and maintaining its parameters, read Maintaining Kernel Filters, in your Entire Net-Work Server documentation.
You can create a host machine filter list to identify the host machines from which service requests to the Kernel will be processed and to which the Kernel can send service requests. The host machine filter list is specified using the ACCEPTED_HOSTS and REJECTED_HOSTS parameters. Using these parameters, you can list machines names that should be accepted (service requests from and to these machines will be processed) or rejected (services requests from and to these machines will be rejected).
For complete information on the host machine filter list and maintaining its parameters, read Maintaining Kernel Filters, in your Entire Net-Work Server documentation.
You can create a client filter list to identify the Entire Net-Work Clients from which service requests to the Kernel will be processed. The client filter list is specified using the ACCEPTED_CLIENTS and REJECTED_CLIENTS parameters. Using these parameters, you can list Entire Net-Work Client names that should be accepted (service requests from these clients will be processed) or rejected (services requests from these clients will be rejected).
For complete information on the client filter list and maintaining its parameters, read Maintaining Kernel Filters, in your Entire Net-Work Server documentation.