Adabas Manager Version 9.1 supports Adabas Auditing Administration. It provides you with the information of the currently running Adabas Auditing environment.
For more information on how to use Adabas Manager to perform the administration tasks necessary for Adabas Auditing operations, see Adabas Auditing.
It is necessary to authenticate with mainframe credentials before a user can view and/or modify the Adabas Auditing data, depending on the security setup on the mainframe. Please refer to section documentation on the security setup.
The SSL certificate used to connect to the Adabas Manager Runtime Server can be protected by a password. The self-signed SSL certificate generated during the installation with the Software AG Installer is not protected by a password. In addition, a user can define different locations to store the SSL certificate and private key files. Please refer to the Installation > Important Information documentation for more information.
Adabas Manager version 9.1 supports retrieving databases on mainframe registered on the SoftwareAG Directory Server (ADI), which is connected by the Adabas Manager Communicator (AMC).
From AMN900 onwards, this runtime service running at port 4990 takes over the role of the previous SoftwareAG Runtime Service (commonly on port: 8083) to render Adabas Manager web pages. The Adabas Manager Runtime Service also acts as a proxy server to issue API calls to various REST servers, for example, Adabas REST Administration Server, Adabas Manager Communicator (AMC) and Adabas Auditing. With this runtime service, users only need to open port 4990 of the firewall between Adabas Manager client and various remote REST servers.
Adabas Manager is by default running at HTTPS port.
The backgound:
In Adabas Manager 850 (in short AMN850), a user can have 2 configuration files (adaRest and netHost) for host connections to Adabas REST and AMC respectively. Since AMN860, 1 user will only have 1 configuration file by combining different host connections (Adabas REST, AMC and Adabas Audit Server) into 1 file.
From AMN850 to AMN860, the host configuration file consolidation is done behind the scenes for the users.
From AMN850 to AMN910, there is a script (migrate_host.bat or migrate_host.sh) located in the /AdabasManager/bin directory, that executes the migration of adaHost_<userid>.config and netHost_<userid>.config to the new file host_<userid>.config.
To migrate host configuration files from AMN850 to AMN910, copy or move the configuration files from AMN850 to the directory <AMN910_Installed_directory>/AdabasManager/config before executing the script (migrate_host.bat or migrate_host.sh).
Note:
We highly recommend to migrate the AMN850 configuration files to the AMN910 single
file format before logging on to AMN910 for the very first time. Otherwise, AMN910 will
create a default host configuration file (host_<userid>.config)
if the migrated file is not found.
From AMN910 onwards, it is possible to create a new encrypted database on Linux, and to view the encryption algorithm and target from the Database Properties page. Currently, it is not possible to create new encrypted database with the Adabas restore utility.