Installing and Uninstalling Entire Net-Work Client

#### Search Results

Search

# Installing and Uninstalling Entire Net-Work Client

Entire Net-Work Client is installed using the Software AG Installer. It does not require a license key.

This document provides product-specific instructions for installing Entire Net-Work Client. It is intended for use with Using the Software AG Installer, which explains how to prepare your machine to use the Software AG Installer and how to use the Software AG Installer and Software AG Uninstaller to install and uninstall your products. The most up-to-date version of Using the Software AG Installer is always available in the webMethods product documentation located on the Empower website (https://empower.softwareag.com/).

You can create a silent installation of Entire Net-Work Client using Software AG Installer scripts. For complete information, read Using the Software AG Installer.

This document covers the following topics:

- Installation Overview

- System Requirements

- Configuration Considerations

- Before You Begin

- Installation Steps

- Required Post-Installation Updates for Simple Connection Line Driver Support

- Configure the Adabas Client Environment

- Configuring Product Components for Windows Personal Firewall

- Uninstallation Steps

- Installing Fixes Using Software AG Update Manager

- Uninstalling Fixes Using Software AG Update Manager

## Installation Overview

This product is installed using the Software AG Installer, which you can download from the Empower website at https://empower.softwareag.com/.

Installation of Entire Net-Work requires the presence of an Adabas Directory Server in your enterprise.

If you have a Directory Server already installed at your site from an earlier release of Software GmbH products, you do not need to install it again; your new products can use the existing installation instead.

The Directory Server must be installed on a machine in your network that can be accessed by all machines where Entire Net-Work will be installed (both Entire Net-Work Server and Entire Net-Work Client). It should be installed on a dedicated system that is operational 24 hours a day, with a UPS.

We recommend that you install one Directory Server for use with all the Software GmbH products that require it.

## System Requirements

This section describes the system requirements of Entire Net-Work Client.

- Supported Operating System Platforms

- Supported Hardware

- Supported Browsers

- Space Requirements

- Firewall Requirements

### Supported Operating System Platforms

Software GmbH generally provides support for the operating system platform versions supported by their respective manufacturers; when an operating system platform provider stops supporting a version of an operating system, Software GmbH will stop supporting that version.

For information regarding Software GmbH product compatibility with IBM platforms and any IBM requirements for Software GmbH products, please review the Product Compatibility for IBM Platforms web page.

Before attempting to install this product, ensure that your host operating system is at the minimum required level. For information on the operating system platform versions supported by Software GmbH products, complete the following steps.

1. Access Software GmbH's Empower web site at https://empower.softwareag.com.

2. Log in to Empower. Once you have logged in, expand Products & Documentation in the left menu of the web page and select Product Version Availability to access the Product Version Availability screen.

3. Use the fields on the top of this screen to filter its results for your Software GmbH product. When you click the Search button, the supported Software GmbH products that meet the filter criteria are listed in the table below the filter criteria.

   This list provides the following information for the supported operating systems:

   - the general availability (GA) date of the product;

   - the date the operating system platform is scheduled for retirement (OS Retirement);

   - the end-of-maintenance (EOM) date for the product; and

   - the end-of-sustained-support (EOSS) date for the product.

Note
Although it may be technically possible to run a new version of your Software GmbH product on an older operating system, Software GmbH cannot continue to support operating system versions that are no longer supported by the system’s provider. If you have questions about support, or if you plan to install this product on a release, version, or type of operating system other than one listed on the Product Version Availability screen described above, consult technical support to determine whether support is possible, and under what circumstances.

### Supported Hardware

For general information regarding Software GmbH product compatibility with other platforms and their requirements for Software GmbH products, visit Software AG's Hardware Supported web page.

### Supported Browsers

The Adabas Manager requires an Internet browser. For information on supported browsers, see the webMethods System Requirements documentation on the Empower web site.

### Space Requirements

The following table displays the minimum disk space requirements on Windows and Linux systems for various Adabas LUW and Entire Net-Work LUW products, including the Adabas Directory Server:

Product | Space Requirement
--- | ---
Entire Net-Work Client | 25 MB
Entire Net-Work Server | 30 MB
Adabas Directory Server | 20 MB

### Firewall Requirements

If you attempt to install and use this software in a system with a firewall in place, be sure that your system administrator has set up the firewall so that the component applications can access the ports they need (including the Adabas Directory Server port and any ports Entire Net-Work dynamically assigns during its own processing). For more information about port usage, read the Port Number Reference found elsewhere in this documentation.

## Configuration Considerations

Before you install this product, you must decide how you are going to configure it. To assist you in these decisions, the following table provides some questions you should answer for the installation of this product in your enterprise. Corresponding considerations for the questions are also provided.

Category | Question | Considerations
--- | --- | ---
Adabas Directory Server and this product | Do you want to direct specific clients or Kernels to specific databases by department or other organizational grouping? | You can create multiple Kernels and use Directory Server partitioning and client and Kernel filtering in SMH to control which clients and Kernels have access to which databases.
Partitioning | Do you want to implement partitioning? | Partitioning allows you to direct specific clients or Kernels to specific databases. Partitions are defined for the clients and Kernels in the Adabas Manager. For more information, read Understanding Partitioning.
Entire Net-Work Servers | On which machines must an Entire Net-Work Server be installed? | One Entire Net-Work Server must be installed on each machine where you wish to define Kernels. Only one server can be installed on a machine.
Kernels | On which machines do your open system databases reside? | At least one Kernel must be defined on each of these machines if you want your clients to be able to access the open system databases.
Will your Entire Net-Work Clients need to communicate with databases on the mainframe or with databases managed by classic Entire Net-Work 2 Kernels? | One Entire Net-Work Kernel must be used as a bridge to access these databases. This Kernel will translate and direct requests as appropriate. The Entire Net-Work Kernel used can be one already defined on a system with a local database. It can also be a Kernel that is defined standalone on a machine without a local database. You will need to evaluate your network traffic to determine which configuration works best for your site.
Will you want to install and run an Entire Net-Work 7 Kernel and an Entire Net-Work 2 Kernel on the same machine? | we recommend that you install either the Entire Net-Work 7 or the Entire Net-Work 2 Kernel on a machine -- but not both. Instead, when you are ready to migrate a system to Entire Net-Work 7, stop the classic Entire Net-Work 2 Kernel and install the Entire Net-Work 7 Kernel. The migration will happen smoothly, without complications, and you can use Entire Net-Work 7 to access the same databases you accessed using classic Entire Net-Work. While it is possible to install and run an Entire Net-Work 7 Kernel on a system where an Entire Net-Work 2 Kernel is installed and running, choosing to do so is an advanced option. We recommend that you contact your technical support representative for assistance in doing this.
If you are implementing partitioning, which Kernels will be part of which partition? | Partitioning allows you to direct specific Kernels to specific databases. For more information, read Understanding Partitioning.
Are you implementing filtering? | Filtering allows you to direct specific Kernels to specific databases. For more information, read Understanding Filtering.
Entire Net-Work Clients | How many Entire Net-Work Clients will you need and on which machines will they be needed? | One Entire Net-Work Client must be installed on each machine that needs to communicate with an Adabas database or that needs to access other Software GmbH product servers (such as those for EntireX Communicator, Tamino, or Adabas SQL Gateway).
If you are implementing partitioning, which clients will be part of which partition? | Partitioning allows you to direct specific clients to specific databases. For more information, read Understanding Partitioning.
Are you implementing filtering? | Filtering allows you to direct specific clients to specific databases. For more information, read Understanding Filtering.
Will any of the machines be used to run both databases and Entire Net-Work Clients? | At least one Entire Net-Work 7 Kernel must be defined and one Entire Net-Work 7 client must be installed on any machine on which a local database is installed and from which access to other databases is required.

## Before You Begin

Before you begin installing this product, ensure that the following prerequisites have been met:

1. we strongly recommend that you create an installation image of your existing Software products and store the image on your internal network. You should create an image for each operating system on which you plan to run the installation (for example, 32-bit, 64-bit, or both). This will help you reduce WAN traffic and speed up installation and will ensure consistency across installations over time, since the Software AG Installer provides only the latest release of each product.

2. Close (stop) all open applications, especially those applications interacting with or depending on your Adabas databases. This includes Natural, Adabas Manager, the Adabas DBA Workbench, and prior releases of any other Adabas products. To be on the safe side, also shut down all Software AG services.

   Important
   For some Software GmbH products, the Software AG Uninstaller will not be able to remove key files that are locked by the operating system if the associated Software GmbH products are not shut down.

3. Disable any antivirus software.

4. Ensure the target computer is connected to the network.

5. If this product requires a license key file, verify the license key file is copied somewhere in your environment . Products requiring license key files will not run without valid license keys. For more information, read The License Key, elsewhere in this section.

6. Verify your environment supports the system requirements for this product, as described in System Requirements, elsewhere in this section.

## Installation Steps

Entire Net-Work Client is installed using the Software AG Installer. It does not require a license key.

You can download the Software AG Installer from the Software AG Empower website at https://empower.softwareag.com/.

This installation documentation provides a brief description on how to install the Entire Net-Work Client directly on the target machine using the installer wizard. For detailed information on the installer wizard, read Using the Software AG Installer.

Note
Read Using the Software AG Installer also if you want to use console mode, or if you want to install using an installation script or installation image.

To install Entire Net-Work Client, complete the following steps:

1. Start the Software AG Installer as described in Using the Software AG Installer.

2. When the first page of the Software AG Installer wizard (the Welcome panel) appears, choose the Next button repeatedly, specifying all required information on the displayed panels, until the panel containing the product selection tree appears.

   All Adabas-related products (including Adabas Directory Server) can be selected for installation within the Adabas Family product selection tree.

   Note
   The Infrastructure tree and required components therein is automatically selected for all Software GmbH product installations.

3. To install Entire Net-Work Client, select (check) the Entire Net-Work Client entry from the Adabas Family product selection tree.

   Note
   You can opt to install other Software GmbH products from this list at the same time. This section just describes the installation of Entire Net-Work Client.

4. On the License panel, read the license agreement and select the check box to agree to the terms of the license agreement and then click Next to continue. If you do not accept the license agreement, the installation will stop.

5. When the Configure panel appears, specify the URL and port number for the Directory Server that should be used for this installation. The default is tcpip://localhost:4952. For complete information on the port used by the Directory Server, read Port Number Reference.

   In addition, on Linux systems, select the radio button indicating whether Entire Net-Work Client should be installed as an application or a Daemon. You can only select one. By default, it is installed as a Daemon.

   Click Next to continue.

6. On the last panel, review the items you have selected for installation. If the list is correct, choose the Next button to start the installation process.

After Entire Net-Work Client has been installed, it will start automatically on Windows, and on Linux only, if it has been installed as a Daemon.

## Required Post-Installation Updates for Simple Connection Line Driver Support

Note
The most recent deliveries of Entire Net-Work and Adabas with ADATCP on the mainframe are compatible with a Directory server. If these products are configured to register their targets with the Directory Server, the steps outlined below are notnot necessary. These steps only apply if you need to manually configure connections to your mainframe Adabas targets.

Once you have installed the Entire Net-Work Client components, you must add target entries in the Adabas Manager (AMN) to support the Simple Connection Line Driver.

You can do this in one of two ways:

- You can add them on your local machine by adding an Adabas access definition to a client configuration in Adabas Manager. Specifically, one Adabas access definition must be added for each open systems Adabas database you want to access using the Simple Connection Line Driver. For more information, read Adding Adabas Access Definitions .

- You can manually set up Directory Server target entries for the Adabas open systems databases in the Directory Server that the client uses. Specifically, one XTSaccess (access) target entry must be created in the Directory Server for each open systems Adabas database you want to access using the Simple Connection Line Driver. You can add these target entries using Adabas Manager.

  For example, if you needed to access database 5 on the host machine named BHOST at port 2504, your access entry might look like this:

      XTSaccess.5[0]=tcpip://bhost:2504

  For complete instructions on creating target entries in the Directory Server, read Maintaining Targets in the Adabas Server Installation and Administration Guide. For general information about target entries, read Directory Server Target Entries.

## Configure the Adabas Client Environment

To ensure that the Adabas Client environment is set correctly for use with Entire Net-Work Client, it must be configured.

The Adabas Client environment is only required by applications and services that access an Adabas database or use the database communication facilities. An Adabas Client environment is not automatically configured during installation. An Adabas Client environment enables you to configure the environment to fit the needs of your application or service.

The Adabas Client environment can either be set system-wide (global setting) or locally to the application (local setting). A global Adabas Client environment is required, when one or more of the following conditions apply:

- When the remote administration of the database is required;

- When the database is to be accessed via Entire Net-Work;

- When a service application requires access to the database;

- When multiple database versions are accessed concurrently.

Setting a global Adabas Client environment implies that only one Adabas Client version can be used. In such cases, the newest Adabas Client version installed on your machine should always be used.

Setting a local Adabas Client environment enables custom configuration of applications. This can be achieved in one of two ways:

1. By executing the application at a Local Client Environment command prompt; or

2. By executing the application with a local Adabas Client environment.

This section covers the following topics:

- Creating a Local Adabas Client Environment

- Setting up the Global Adabas Client Environment

- Modifying an Existing Global Adabas Client Environment

### Creating a Local Adabas Client Environment

There are two ways to create a local Adabas Client environment:

1. Execute the application from a local Adabas Client command prompt via the Start menu: All Programs > Software AG > Administration > Adabas Client v.r > Start Local Environment.

2. Initialize the Adabas Client environment prior to executing the application by calling the script aclenv.bat located in the directory <install_dir>\AdabasClient\INSTALL\.

### Setting up the Global Adabas Client Environment

There are two ways to set up a global Adabas Client environment:

1. Execute the application from a local Adabas Client command prompt via the Start menu: All Programs > Software AG > Administration > Adabas Client v.r > Configure Global Environment.

2. As a system administrator, open a command prompt and run the script aclenvvar.bat located in the directory <install_dir>\AdabasClient\INSTALL\.

### Modifying an Existing Global Adabas Client Environment

When upgrading from a previous Adabas Client version, use one of the methods described in Setting up the Global Adabas Client Environment to set the global environment.

## Configuring Product Components for Windows Personal Firewall

If you have the default Microsoft Windows personal firewall enabled on a PC and you would like to install and run Adabas and Entire Net-Work components on that PC, you will need to allow communications through the firewall on certain ports. You can do this in one of two ways: you can allow ports for a specific executable program or you can open specific ports. This section covers the following topics:

- Allow Ports for a Specific Executable Program

- Open a Specific Port

Note
If you attempt to install Adabas or Entire Net-Work in a system with a firewall in place, be sure that your system administrator has opened the firewall for the Adabas Directory Server port or the installation may not complete successfully.

### Allow Ports for a Specific Executable Program

You can allow a specific executable program to open a port. To do so, issue the following command:

    C:\>netsh firewall add allowedprogram program="<path and file name>"
    name="<component-name>" profile=ALL

where <path and file name> is the path and file name of the file you want to allow and <component-name> is a user-specified name to identify the file you are allowing. The following table lists the common Adabas and Entire Net-Work component files that might need to be allowed if Windows personal firewall is enabled:

Component Name | Path and File Name
--- | ---
Entire Net-Work Client Service | <your-installation-location>\EntireNetWorkClient\bin\wclservice.exe
Entire Net-Work Kernel program | <your-installation-location>\EntireNetWorkServer\bin\wcpkernel.exe
Entire Net-Work Server Service | <your-installation-location>\EntireNetWorkServer\bin\wcpservice.exe
Adabas Directory Server Service | <your-installation-location>\SoftwareAG\SoftwareAgDirectoryServer\bin\xtsdssvcadi.exe

To remove the Adabas or Entire Net-Work component as an allowed program, issue the following command:

    C:\>netsh firewall delete allowedprogram program="<path and file name>"
    profile=ALL

where <path and file name> is the path and file name of the file you want to disallow.

### Open a Specific Port

To open a specific port for use by an Adabas or Entire Net-Work component in the firewall, issue the following command:

    C:\>netsh firewall add portopening protocol=TCP port=nnnn
    name="<component-name>" profile=ALL

where nnnn is the port number you want to open and <component-name> is a user-specified name to identify the port you are allowing.

To avoid port number conflicts, read Port Number Reference for a general list of the ports used by Software GmbH products.

To close a specific port in the firewall, issue the following command:

    C:\>netsh firewall delete portopening protocol=TCP port=nnnn profile=ALL

where nnnn is the port number you want to close.

## Uninstallation Steps

You uninstall this product using the Software AG Uninstaller. For information on how to use the uninstaller, read the Using the Software AG Installer guide.

## Installing Fixes Using Software AG Update Manager

Entire Net-Work Client is updated using the Software AG Update Manager (SUM).

You can download the Software AG Update Manager from the Software AG Empower website at https://empower.softwareag.com/.

This SUM installation documentation on Empower provides a brief description on how to update Software GmbH products directly on the target machine using the Update Manager wizard. The SUM documentation also includes instructions on how to apply updates in console mode or using scripts.

To update Entire Net-Work Client, complete the following steps:

1. Download and install Software AG Update Manager for your platform from Empower.

2. Shut down any running instances of the product. Updates cannot successfully apply if the application is active.

3. From a console prompt in the SUM /bin directory, enter `UpdateManagerGUI.bat` (`UpdateManagerGUI.sh` on Linux).

4. On the opening page of the SUM tool, select Install Fixes from Empower, enter your SAG product directory root location and provide your Empower User ID and password. Click Next.

5. Expand through the Adabas Family product selection tree to find the entry for this product.

   Tip
   If the product is not shown in the tree, there is either no update available or the product is not installed in the location you specified.

6. Select (check) the Entire Net-Work Client entry in the product selection tree. Click Next.

   Tip
   You can select more than one product to update before proceeding.

7. The next screen presents a summary of products that are about to be updated. If any of them require manual pre-installation steps, they will be highlighted in red and you will be directed to read the update readme file for that product before proceeding.

   Complete any pre-installation steps outlined in the readme file and check the box next to Pre-installation steps have been completed. Click Next.

   Note
   If any pre-installation steps are required, the Next button will be unavailable until you confirm these steps have been completed.

8. The tool will apply updates to all selected products and present you with a final screen confirming updates have been applied. Click Close to exit SUM or Home to return to the tool's starting panel.

## Uninstalling Fixes Using Software AG Update Manager

To remove an installed update, complete the following steps:

1. Shut down any running instances of the product.

2. Start Software AG Update Manager.

3. On the opening page, select Uninstall Fixes from the selection panel. Click Next.

4. If any product selected for uninstall requires manual steps, you will be directed to review the update readme and confirm you have performed any pre-uninstallation steps. Click Next.

5. The fix(es) you selected for uninstall will be removed and the product(s) returned to their previous state. Click Close to exit SUM or Home to return to the tool's starting panel.

### On this page

- Installation Overview
- System Requirements
- Configuration Considerations
- Before You Begin
- Installation Steps
- Required Post-Installation Updates for Simple Connection Line Driver Support
- Configure the Adabas Client Environment
- Configuring Product Components for Windows Personal Firewall
- Uninstallation Steps
- Installing Fixes Using Software AG Update Manager
- Uninstalling Fixes Using Software AG Update Manager