There are two implementations of Adabas Directory Server delivered with the installation. When Adabas Directory Server is installed, the classic C implementation is installed, configured and started. Should the user prefer to use the Java implementation, there is a script in the product home directory called swapadi.bat/sh that can be called.
There is no functional difference between the two implementations. The Java implementation is provided for those who may be using the new Java implementation of the Directory Server on the mainframe and want to use an instance of the Java implementation on Linux, UNIX and Windows (LUW) as well, either for testing or in production. LUW and mainframe Directory Server clients are able to communicate with either implementation running on either platform.
To switch to the Java implementation of the Directory Server, perform the following steps:
Shut down the running Directory Server Windows service or Linux daemon instance that will be affected by this change.
On Windows, use the Windows Control Panel applet to shut down the running service called Software AG Adabas Directory Server Service 5.9 or use the script stopService.bat found in the SoftwareAgDirectoryServer\sh directory.
On Linux systems, it is best to use the
systemctl
command to shut down the daemon as
follows:
sudo systemctl stop sag<instance>adi590
Where
<instance>
corresponds to the
Software AG products installation root. In most cases this will be
"1". However, if you have multiple Software AG
installation locations, it may be different. The name of the service
corresponds to the name of the daemon script found in the product´s
/INSTALL directory.
On UNIX systems, use the script adistop.sh in the /INSTALL directory.
Back up the contents of the SoftwareAgDirectoryServer directory.
Ensure you have no file open under the product installation directory.
Run the provided script swapdi.bat (swapadi.sh on Linux).
The script will:
make a backup copy of the Directory Server’s file repository;
uninstall the current service or daemon;
copy the current contents of the SoftwareAgDirectoryServer directory to a new adic directory as backup;
move the Java implementation files to the active location; and
register and start the new service or daemon.
If you need to switch back to the C implementation, follow the above instructions again. The swapdi script can be run multiple times to toggle back and forth between the two implementations.
Important:
When applying updates to the Adabas Directory Server, the
Software Update Manager expects the C implementation of ADI to be the active
one. If you have swapped the implementation to Java, you MUST swap
back to the C ADI before attempting to apply the update.