Installation of LINK2i


IBM i Side

There are a few steps to perform on the IBM i side in order for LINK2i to operate.

WARNING: In any case, please keep a backup security officer account outside of LINK2i's scope. Failing more than 3 times at the authentication on the IBM i system automatically locks the account and a security officer (SECOFR) role is required to unlock accounts.
LINK2i uses standard IBM i authentication, it is prone to unintentional account lock in case of a programming error.

Prerequisites

To run LINK2i, the minimum configuration on the IBM i side must be:

  • Release: From V4R4M0 with limited support / From V5R4M0 with full support
  • One available ethernet port
  • An account with security officer role
  • A working full installation of IBM Client Access or IBM Access Client Solution (ACS) between the targeted IBM i partition and the Windows-OS server
Remark: LINK2i allows the user to perform tasks that are meant to be performed by the targeted IBM i. In other words, some functionalities of LINK2i won't work at their full potential with older IBM i releases (from V4R4M0 to V5R3M0).

Installation

The installation on the IBM i side consists in creating libraries/databases inside the targeted IBM i partition.
Default installation can be performed by running the instructions below. Default names must be kept

CL Commands to execute on the IBM i partition:
CRTLIB LIB(QLINK2I) TEXT('Link2i License')
CRTLIB LIB(QLINK2T) TEXT('Link2i Tokens')

SQL queries to run on the IBM i partition using STRSQL:
CREATE TABLE qlink2i/liclink (link2i varchar(512))
INSERT INTO qlink2i/liclink VALUES ('IBMi-Key') 

The value of IBMi-Key is obtained by ordering a license at the LINK2i License Center

License Key Renewal

LINK2i license keys' validity durations are limited to one year. After the renewal had been completed at the LINK2i License Center, a new IBMi-Key is generated.
The IBMi-Key value update can be performed by following the instructions below (these commands are valid for the default installation and have to match actual libraries names)

CL Command to execute on the IBM i partition:
CLRPFM FILE(qlink2i/liclink)

SQL queries to run on the IBM i partition using STRSQL:
INSERT INTO qlink2i/liclink VALUES ('IBMi-Key') 

The value of IBMi-Key is obtained by ordering a license at the LINK2i License Center

Uninstallation

Uninstalling LINK2i from the IBM i partition only consists in deleting libraries that had been created at the installation.
Uninstallation can be performed by running following CL command lines. These commands are valid for the Default installation and have to match actual libraries names.

DLTLIB LIB(QLINK2I)
DLTLIB LIB(QLINK2T)
Remark: Once LINK2i libraries have been deleted, there is no remaining footprint of LINK2i on the IBM i system

.NET Side

Prerequisites

To run LINK2i, the minimum configuration on .NET side must be:

  • A windows environment (Windows 10 professional/ Windows Server ...)
  • Visual Studio 2017
  • A working full installation of IBM Client Access or IBM Access Client Solution (ACS) between the targeted IBM i partition and the Windows-OS server
  • Microsoft Office 2007 or newer (recommended)
Remark: We recommand using a dedicated windows server to run LINK2i, learn more about LINK2i architectures

Installation

LINK2i is available on nuget.org as a NuGet package and can be installed in different ways:

Via Visual Studio NuGet package manager (requires intenet)
In a .NET project in Visual Studio, open the NuGet package manager (Project > Manage NuGet packages...)
Then in Browse tab, search for LINK2i. Select LINK2i by AUMERIAL, click on install button and follow the steps to finalize the installation.

LINK2i is then installed in your environment

Remark: For more details about NuGet and NuGet packages, read Microsoft documentation about NuGet.

License Activation

To activate LINK2i on server side (windows environment), open a windows Command Prompt as administrator. Then run the following command lines:

cd %WINDIR%
cd. > LicenseLink2i.txt
LicenseLink2i.txt

An empty text file opens. In this file, paste the DOTNET-Key of each LINK2i license you ordered (1 line per DOTNET-Key) The format of a DOTNET-Key is:

DOTNET-Key --- Caption

The DOTNET-Key file looks like this:

DOTNET-KeyEXAMPLE1XXXXX1234567890 --- IBM i S/N: 00000001   Partition Name: MYPART01  Validity: 31/12/2021 plus 30 days delay
DOTNET-KeyEXAMPLE2XXXXX1234567890 --- IBM i S/N: 00000001   Partition Name: MYPART02  Validity: 31/12/2021 plus 30 days delay

Renew, add or delete license keys

To edit LINK2i license keys on a Windows system, open a Windows Command Prompt as administrator. Then run the following command lines:

cd %WINDIR%
LicenseLink2i.txt

The license keys file opens.
In this file each line represents a single DOTNET-Key (activation key) formatted like so:

Activation key --- Caption

To renew a license key, replace the corresponding line by its new DOTNET-Key.
To add a license key, add a DOTNET-Key as a new line.
To delete a license key, delete the corresponding line.

Uninstallation

To uninstall LINK2i from a Windows environment, run the following command lines in a Windows Comand Prompt opened as administrator:

cd %WINDIR%
del /f LicenseLink2i.txt

At this point LINK2i is disabled but you may still have LINK2i packages included in your .NET projects. To uninstall LINK2i NuGet package from a project, follow this tutorial from Microsoft on how to uninstall NuGet packages.


See also: