Articles in this section

Installing the vLink (Connector) Using BSX Package

Overview

This article provides step-by-step instructions for installing the JetPatch vLink using BSX packages on various Unix-like operating systems, including Linux distributions, AIX, and Solaris. 

The connector enables endpoints to communicate with the JetPatch server for patch management operations.

Deploying the vLink (Connector) on the Endpoint Itself

See article

Linux Installation

  1. Verify pre-reqs (very important)
  2. Download the latest Linux connector 
    • Alternatively, copy the latest Linux BSX from JetPatch Server (/usr/share/intigua/bin/) 
  3. Once copied to the endpoint, you need to change the permission of the file to run it (via chmod +x)
  4. The JetPatch Connector installation files install to /usr/local by default.
  5. Lastly, run the following command (make sure you modify the command to point to your JetPatch server)

For Enterprise Linux (incl. RHEL, OL, etc) and SLES

For versions before 5.0:

./vlink_installer_linux_x64_Release*.bsx -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname/vmanage-server/"

Post 5.0 (assuming default port 8443):

./vlink_installer_linux_x64_Release*.bsx -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443"

For Debian Linux (incl. Debian and Ubuntu)

./vlink_installer_linux_x64_Release*.bsx --out=install_state.log --coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname/vmanage-server/"
./vlink_installer_linux_x64_Release*.bsx --out=install_state.log --coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443"
Note: Typically, connector installs in /usr/local. If you want a different location, add the following parameter to the command:

For Enterprise Linux (incl. RHEL, OL, etc) and SLES:

-locations=/usr/bla/
--locations=/usr/bla/

AIX Installation

Required Dependencies:

Before installing the vLink Connector (4.2.8.210+) on AIX 7.2 or 7.3, ensure the following prerequisite packages are installed from the IBM AIX Toolbox for Open Source:

  • gettext (provides /opt/freeware/lib/libintl.a)

The connector's Kerberos library (libkrb5support.so) has a hardcoded dependency on /opt/freeware/lib/libintl.a(libintl.so.8). This path is embedded in the binary's loader section and cannot be overridden using LIBPATH. If this library is not present, the connector will fail to start.

To install:

dnf install gettext

Or install the RPM manually from the IBM AIX Toolbox: https://www.ibm.com/support/pages/aix-toolbox-open-source-software-downloads-alpha

To verify after installation:

ls -la /opt/freeware/lib/libintl.a
dump -H /opt/freeware/lib/libintl.a

Confirm that the libintl.so.8 member is present in the archive.

Note: Do not substitute the Intigua-bundled copy (/usr/local/intigua/lib/libintl.a) into /opt/freeware/lib/, as the two builds have different dependency chains (the Intigua version requires libiconv.a, which may break other freeware consumers).

Deploying the vLink:

  1. Verify that the endpoint has Unzip installed
  2. Download the AIX connector
  3. Alternatively, copy the latest AIX BSX from JetPatch Server (/usr/share/intigua/bin/) or configure NGINX to point to the connector folder to download from UI
  4. Lastly, run the following command (make sure you modify the command to point to your JetPatch server)
./vlink_installer_AIX_power_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname/vmanage-server/"
./vlink_installer_AIX_power_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443"

Known Issues:

AIX — Connector fails to start with missing library error

Symptom: Connector fails to start on AIX 7.2/7.3. Logs may show errors related to libintl or unresolved symbols.

Cause: The gettext package from the AIX Toolbox for Open Source is not installed. The connector requires /opt/freeware/lib/libintl.a(libintl.so.8).

Resolution: Install the gettext package as described in the prerequisites section above.

 

Solaris Installation

Solaris 10

  1. Download the latest Solaris 10 connector
  2. Alternatively, copy the latest Solaris 10 BSX from JetPatch Server (/usr/share/intigua/bin/) or configure NGINX to point to the connector folder to download from UI
  3. Lastly, run the following command (make sure you modify the command to point to your JetPatch server)
./vlink_installer_solaris11_sparc64_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname/vmanage-server/"
./vlink_installer_solaris11_sparc64_Release*.bsx -no-kill-session /tmp -out=install_state.log -coreserverurl="https://Your_JetPatch_Server_IP_or_Hostname:8443/"

Solaris 11

  1. Download the Solaris 11 connector
  2. Alternatively, copy the latest Solaris 11 BSX from JetPatch Server (/usr/share/intigua/bin/) or configure NGINX to point to the connector folder to download from UI

Verification and Troubleshooting

 Now connect to your JetPatch Console and check that you can see the machine on the "Servers" tab.

mceclip0.png

1. To verify that the connector has been properly installed, check if the service is running:

/etc/init.d/intigua status

2. If the coreserverurl needs to be modified, see this article.

If there are still issues, generate connector logs from the endpoint and contact the Support Team.

 

Related articles

Comments

0 comments

Article is closed for comments.