Before you install Encryption for Entire Net-Work, be sure you have met the requirements described in Prerequisites.
This document covers the following topics:
On mainframe systems, the installation of Encryption for Entire Net-Work involves installing the software for the SSL/SSLI line driver's. This runs with the Entire Net-Work WCP V6.3.2 library. This section describes the steps required for this installation on z/OS platforms.
The following table describes the libraries included on the release tape when you purchase Encryption for Entire Net-Work. Once you have unloaded the libraries from the tape, you can change these names as required by your site.
| Library Name | Description |
|---|---|
| APSvrs.LDnn | One or more Software AG internal libraries. The vrs in the library name represents the version of the internal library code, which is not necessarily the same as the version of Entire Net-Work |
| WSLvrs.LOAD | The z/OS load library for Encryption for Entire Net-Work. The vrs in the library name represents the version of Encryption for Entire Net-Work, which is not necessarily the same as the version of Entire Net-Work. |
If not already performed, install the Entire Net-Work mainframe and Entire Net-Work TCP/IP Option libraries, using the procedure for your operating system environment. Then unload the SSL/SSLI line driver components from the installation tape as follows:
| Platform | Installation Procedure |
|---|---|
| z/OS | IEBCOPY to restore the required data sets. Refer to the Report of Tape Creation for the correct data set sequence numbers and names. |
Make the following changes to the Entire Net-Work startup JCL.
| Platform | Startup Job Change |
|---|---|
| z/OS | A sample startup JCL member called JCLNET is provided in the WCP source libraries. Add the SSL/SSLI line driver load library to the STEPLIB concatenation. |
Use the existing Entire Net-Work configuration to create the necessary SSL/SSLI DRIVER and LINK statements for your environment in the Entire Net-Work DDKARTE input file.
Note:
If you are installing the SSL line driver the value of the
SSL or SSLI DRIVER's API parameter must be "OES". The SSL format
is as the TCPX Driver, the SSLI as the TCPI Driver in the WCP example jobs.
For an LUW client to correctly send the database request to the Entire Net-Work node where the database is located, Adabas Directory Server entries must be added for each database. These entries tell the client application where the server (Entire Net-Work) is located and which databases it serves. A Directory Server access entry must be added for each database that the client will call via the security option of the SSL line driver.
For more information, read Access and Connection Definition Setup.
Because of the many possible variations of the Entire Net-Work, Adabas, and applications topology, Software AG does not provide standard installation verification procedures. However, the following procedure is suggested for verifying the SSL/SSLI line driver installations:
Start the Entire Net-Work system and make connections to each link defined to the system.
Test the connections and verify that the links can be established from either side by connecting and disconnecting the links several times from each node. While the links are connected, issue the Entire Net-Work operator command DISPLAY TARGET to display the targets and the nodes on which they are located.
Test your applications running across Entire Net-Work. At first, run one application at a time, and then verify the results.
For the final verification test, run a load test through the network (that is, multiple users on each node accessing data on the partner node).
On LUW systems, the installation of Encryption for Entire Net-Work provides the required SSL libraries used in encryption. It also provides the open source SSL Toolkit that you can use to create certificates. Although delivered on all supported LUW platforms, the SSL Toolkit only runs on Windows. This section describes general information you should understand prior to completing the installation as well as providing installation and uninstallation steps for Windows environments.
Installation of Encryption for Entire Net-Work is accomplished by the following steps:
Contact Software AG Support to obtain the delivery for the operating system(s) where you want to install Encryption for Entire Net-Work. The delivery is available as an archive (.zip for Windows, .tgz for all others) and will have the following format:
WSLv1.3_SP1<platform>.zip/.tgz
…where <platform> corresponds to the operating system you are installing on.
Extract the contents of the archive to a temporary folder on all machines where you already have either Entire Net-Work Server v7.6_SP1 or Entire Net-Work Client v1.3_SP1 already installed and you want to take advantage of SSL communication.
Inside this folder, navigate to the WSL directory.
Inside this directory, you will see a script called install.bat (Windows) or install.sh. Run this script and follow the prompts to install Encryption for Entire Net-Work on your system.
Note that on Windows systems, install.bat requires a command line argument of either "all" or "toolkit". The argument "toolkit" will install only the SSL Toolkit that can be used to generate test certificates. The argument "all" will first install the required SSL libraries in your Adabas Client environment, then will prompt the user whether the SSL Toolkit should be installed as well.
When the script completes, Encryption for Entire Net-Work is now installed. See Activating Encryption for Entire Net-Work for details on configuring your Entire Net-Work Server and Clients for SSL usage.
The SSL Toolkit is uninstalled simply by deleting the files installed by the installation script. These files can be found under the AdabasClient directory in your environment as follows:
Windows: AdabasClient\bin\sagossl5.dll and
AdabasClient\bin32\sagossl5.dll
UNIX/LINUX: AdabasClient/lib/libsagossl5.so and
AdabasClient/lib_32/libsagossl5.so.
On Windows systems, if you have installed the SSL Toolkit, delete the entire SSLToolkit folder.