Adabas Administration Services (AAS) provides remote administration and system service support for Software AG products. Specifically, Adabas Administration Services allows you to perform the following remote administration tasks for Software AG products with which it is supported:
You can start and stop the product remotely.
You can obtain product log files remotely.
You can read and write product files remotely.
You can read directories remotely.
In addition, Adabas Administration Services allows you to operate the Software AG product as a system service.
Ordinarily, Adabas Administration Services starts up automatically after it is installed or whenever the machine on which it is installed is started. In UNIX environments, however, you may occasionally need to start it manually.
Adabas Administration Services allows remote administration of Adabas databases through Adabas Manager. Once activated, Adabas Administration Services queries the local environment to determine which databases are active in that environment. It then makes target access entries in a Software AG Directory Server repository. These entries are then used by Adabas Manager as a communication path to the database for local or remote administration.
This document also covers the following topics:
Adabas Administration Services supports partitioning of Adabas Directory Server entries. Partitioning enhances your ability to use one Directory Server for your whole enterprise, rather than separate Directory Servers for different departments within your enterprise. The partitions need to be managed separately, but only one Directory Server needs to be installed.
Once you have defined a service, you can assign it to a specific partition. If you specify one for a service, the Directory Server entries created for that service are stored in a partition by that name in the Directory Server configuration or in the service configuration file (depending on where the partition is defined); the entries in the partition are maintained separately from the other entries in the appropriate configuration. The service is only able to direct requests to databases, clients, and client hosts that have entries in this partition.
Here are some of the advantages of partitioning:
You can use partitioning to direct Adabas Administration Services support to specific databases.
If you have created Adabas databases with identical database IDs, you can use partitioning to correctly identify which client calls get directed to which Adabas database.
You can use partitioning to group client calls to an Adabas database, thus reducing the number of actual connections required for that database. This provides you with some level of client control: if you want to remove access to a specific database for clients in a given partition, simply remove the access URL entry for that database (using the System Management Hub) or stop the service in that partition.
Using SSL, you can use impose real security requirements on calls made by clients in specific partitions.
For complete information about partitioning, including an example, read Partitioning a Directory Server in the Software AG Directory Server Installation and Administration Guide.
Adabas Administration Services supports filtering of databases, client hosts, Entire Net-Work Client configurations, and Entire Net-Work Kernel definitions by Adabas database ID. Filtering is set up in the System Management Hub (SMH) using parameters on the Service Filters panel. For more information about this panel, read Maintaining Adabas Administration Services Filters.
You can filter services by requests:
made to specific Adabas database IDs;
submitted from Kernels, by Kernel name;
submitted to and from specific machines, by machine name; and
submitted from clients, by client name.
This section covers the following topics:
Using the Service Filters panel in SMH, you can identify databases for which requests should be processed by the service. If no databases are listed in the ACCEPTED_DBIDS field, the service 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 service will process all requests to all databases defined in the Adabas Directory Server, unless a specific list is provided in the ACCEPTED_DBIDS field.
Using the Service Filters panel in SMH, you can identify Kernels for which requests should be processed by the service. If no Kernels are listed in the ACCEPTED_KERNELS field, the service will process all requests to all Kernels, except those listed in the REJECTED_KERNELS field. Likewise, if no Kernels are listed in the REJECTED_KERNELS field, the service will process all requests to all Kernels, unless a specific list is provided in the ACCEPTED_KERNELS field.
Using the Service Filters panel in SMH, you can identify host machines for which requests should be processed by the service. If no host machines are listed in the ACCEPTED_HOSTS field, the service will process all requests to all host machines, except those listed in the REJECTED_HOSTS field. Likewise, if no host machines are listed in the REJECTED_HOSTS field, the service will process all requests to all host machines, unless a specific list is provided in the ACCEPTED_HOSTS field.
Using the Service Filters panel in SMH, you can identify clients for which requests should be processed by the service. If no clients are listed in the ACCEPTED_CLIENTS field, the service will process all requests to all clients, except those listed in the REJECTED_CLIENTS field. Likewise, if no clients are listed in the REJECTED_CLIENTS field, the service will process all requests to all clients, unless a specific list is provided in the ACCEPTED_CLIENTS field.