This section provides and overview of the procedure for Data Archiving for Adabas installation:
Data Archiving for Adabas requires both Adabas System Coordinator and System Management Hub in order to function. There are three basic areas of the archiving installation:
The runtime logic.
The browser UI (user interface).
The configuration file.
In a production environment it is quite normal for the runtime to be installed on many computers without the UI. The UI is usually installed on a workstation; one session with the UI can manage, monitor and operate all the runtimes on all the computers in your network, providing your firewall allows of course!
The whole aim of the runtime logic is that it runs unattended. The runtime is made up of the following components:
Launch controller.
The launch controller is a very small part of the logic that is recommended to start up when the operating system starts up. The launch controller does what its name suggests, it launches the other components automatically according to the rules you define in the configuration file.
The Archive management service.
This is the “control center” for all archive operations. The archive service makes sure all the archive operations that you define (in the configuration file) are carried out. In doing so it will itself launch extractors, accumulators, recalls, etc as appropriate. No need for submitting jobs or typing command-line inputs; everything happens automatically.
Extractors, accumulators, recalls, etc.
As stated above, these are launched by the archive service. As they run they will confide status information back to the archive service.
Where you only install the runtime without the UI (this is normal for most servers where Adabas runs) then the embedded System Management Hub install is also skipped.
The UI is a plug-in to the System Management Hub. All archiving administration, configuration, operation and monitoring is performed through the UI. No need to get into every computer where the runtime is installed, you can manage everything from the outside in the UI. So where the runtime is installed on the many differing types of operating system that you have you only need get into the UI in one place in order to manage archiving across your whole network.
The configuration file has already been discussed in the planning section above. The planning section describes how to use the recommended in-built mechanism for sharing the configuration file. However, depending upon the products installed and the platform being installed upon it is possible for other sharing mechanisms to be used, in whole or in part:
Use Adabas Cluster Services as the home of the file. This is appropriate for all instances of the runtime that are to run in connected z/OS computer running as a SYSPLEX.
Use Net-Work.
