Single-stream agent releases

Content

Previously, each Guardium 12.x release (12.0, 12.1, and 12.2) had its own separate agent installers and patch packages. With the move to single-stream packaging, the agent binaries are unified into one continuous release line, so the same installation and upgrade package applies across multiple Guardium 12.x versions. This simplifies maintenance, reduces version divergence, and ensures consistent feature and fix availability across all supported 12.x environments. 

With this change, customers no longer need to locate minor version-specific agent packages for each 12.x release in IBM Support Fix Central. File names starting with “12.x” are now applicable to all current (12.0, 12.1, and 12.2) and future minor version releases within the Guardium 12.x family. The new naming convention follows a sequence, such as 12.xp100, 12.xp101, and so on. 

The single-stream 12.x package updates for Linux-UNIX and Windows Agents are cumulative; they contain all previous patches for that major version. The agents are tested on supported Guardium appliance versions, which are currently 12.0, 12.1, and 12.2.x. Installing the latest 12.x agent package is supported across all 12.x collector and aggregator versions that meet the documented compatibility requirements. 

The single-stream packaging currently applies to the following agents:

• Guardium Configuration Auditing System (CAS)

• Guardium File Activity Monitor (FAM) for Windows

• Guardium Installation Manager (GIM)

• Guardium Software TAP (S-TAP)

Note: The single-stream packaging does not currently apply to External S-TAP agents. 

Required steps for GIM-managed agent environments 

To accommodate the single-stream packaging change, updates are required to the Guardium Installation Manager (GIM) server. Ad-hoc appliance patches are required for any GIM-managed Linux-UNIX or Windows Agents customer environment before upgrading to the new single-stream agent release packages, such as Linux-UNIX Agents 12.xp101 or later, and Windows Agents 12.x.p100 or later. 
 
Note: Customers who already upgraded to Guardium 12.0p230 (see release note) or do not use GIM to install and manage agents do not need to apply these ad-hoc patches to use the new single-stream agent release packages.
 
The following ad-hoc patches align with specific Guardium appliance versions. Identify your current appliance patch level and apply the corresponding ad-hoc patch before deploying single-stream agent release packages. 

• Upgrade 12.0.p45 to 12.0.p47 (see release note)
• Upgrade 12.0.p50 to 12.0.p51 (see release note)
• Upgrade 12.0.p55 to 12.0.p57 (see release note)
• Upgrade 12.0.p140 to 12.0.p144 (see release note)
• Upgrade 12.0.p7135 to 12.0.p1046 (see release note)
• Upgrade 12.0.p125 to 12.0.p1047 (see release note)
• Upgrade 12.0p220 to 12.0p229 (see release note) 
  Note: Customers on Guardium versions 12.0p200 or 12.0p210 must first upgrade to version 12.0p220 before applying patch 12.0p229. (Or upgrade to version 12.0p230 and not need to install patch 12.0p229.)

Use the following sequence to upgrade to the single-stream agent releases:

1. Apply the correct ad-hoc patch to the corresponding Guardium appliance version to update the GIM server, making it ready to accept and distribute the single-stream agent releases.
2. Upload Linux-UNIX Agents 12.xp101 or later, or Windows Agents 12.x.p100 or later, and deploy them by means of the GIM. 

Important: Do not upload Linux-UNIX Agents 12.xp101 or later, or Windows Agents 12.x.p100 or later to a GIM server that does not yet have this appliance patch installed because the bundle will not process correctly.