Extending the Oracle linux Download Plug-in

You can configure the OEL Download Plug-in to download and cache packages from repositories that are not officially supported by BigFix. The OEL Plug-in can resolve package dependency for unsupported OEL repositories, allowing the installation of unsupported dependent packages. This extended solution allows you to use BigFix to deploy packages from repositories that are not shipped out of the box.

Before you begin, you must complete the following tasks:

Ensure that appropriate licenses are registered and that your OEL subscription is active.
Review the BigFix Patch for OEL support information and verify the list of supported repositories:
- Supported architecture, erratas, and repositories

To extend the plug-in to use repositories that are not officially supported by BigFix, you must carefully follow these steps:

Create an extended repository list file.
Update the OEL download plug-in R2 configuration file.
Verify the extended repository setup.

Step 1: Creating an extended repository list file

The OEL Plug-in can use an extended repository list file, which contains additional repositories for both base and extension products that are included in your subscription.

The extended repository list file must meet the following criteria:

It must be a valid .json file.
It must be accessible to the OEL Plug-in. Ensure that the Administrator or root user can read the file.

It must contain the following format:

{OEL Plug-in
   "<OS_key>":[     
     {"name": "<name>", "baseurl": "<base_url>"},
     {"name": "<name>", "baseurl": "<base_url>"}
   ], 
   "<OS_key_1>'': [
     {"name": "<name>", "baseurl": "<base_url>"}
   ]
}

Note: It uses the same format as the DLOELRepoList.json file, which is set for repoListFile in the plugin.ini file.

You must replace the placeholders, which are enclosed in angle brackets <>, with the actual values.

OS_key

To use the unsupported repository with the BigFix OEL Patching content, use the following OS key as listed in the DLOELRepoList.json file:

oel-9-x64

This might not be the full list as later versions of the download plug-in are released. To get the latest and complete copy of the repository list, complete the following actions:

Check whether your endpoints are registered to the latest download plug-in. The Manage Download Plug-ins dashboard indicates when the plug-in is up-to-date or when a new version is available.
View the DLOELRepoList.json file from the following locations:

On Windows Systems

%PROGRAM FILES%\BigFix Enterprise\BES Server\GatherDBData\gather\Patching Support\CurrentSiteData

On Linux Systems

/var/opt/BESServer/gatherDBData/gather/Patching Support/CurrentSiteData

Important: Use the correct OS key for each repository to avoid download and dependency resolution issues.

base_url

The base URL is formed from the OEL repository lists:

https://yum.oracle.com/repo/OracleLinux/<OracleOS_version>/<repo_name>/latest/<architecture>

https://yum.oracle.com/repo/OracleLinux/<OracleOS_version>/<repo_name>/<architecture>

Here is an example .json file with the prescribed format:

{
	"oel-9-x64": [
		{"name": "EPEL 7", "baseurl": "https://dl.fedoraproject.org/pub/epel/7/x86_64"}
	]
}

We will name this file as epel_repos.json and use it in the examples throughout this section.

Step 2: Updating the OEL download plug-in configuration file

Configure the OEL Plug-in to use an extended repository list file. The plugin.ini configuration file is overwritten when the OEL Plug-in is unregistered or configured from the Manage Download Plug-in dashboard. Any change that you make in the configuration file is lost, therefore take note of the previous changes.

Use a text editor to open the plugin.ini file from the following locations:

On Windows systems

%PROGRAM FILES%\BigFix Enterprise\BES Server\DownloadPlugins\OEL Protocol

On Linux systems

/var/opt/BESServer/DownloadPlugins/OEL Protocol
In the extendedRepoListFile field, enter the absolute path or relative path to the extended repository list file. If it is set to a relative path, the path must be relative to the location of the OEL Plug-in executable.
For example:
```
extendedRepoListFile  = ./epel_repos.json
```
This example indicates that the epel_repos.json file is located in the same directory as the download plug-in binary.
If you want set the OEL Plug-in to only use the extended repository list, set the onlyUseExtendedRepoListFile field to yes.
For example:
```
onlyUseExtendedRepoListFile= yes
```
If you want to set OEL Plug-in to use both repository list files, configure the setting to no. In cases where the same OS key is used in both files, the repositories will be combined.
Save the file.

Step 3: Verifying the extended repository setup

Use the OEL Download Cacher to verify whether the extended repository has been set up correctly and that you can it. For details about the cacher, see Oracle linux Download Cacher usage information.

To do this, run the OELDownloadCacher.exe --check-allrepos command.

The expected output for a successful setup is as follows:


3488     : 2018-02-28 17:23:36 : INFO     :  Testing access to: oel-6-x64
3488     : 2018-02-28 17:23:36 : INFO     :  EPEL_6
3488     : 2018-02-28 17:23:36 : INFO     :  Success!
3488     : 2018-02-28 17:23:36 : INFO     :  OEL_-_OS
3488     : 2018-02-28 17:23:36 : INFO     :  Success!

3488     : 2018-02-28 17:23:36 : INFO     :  Testing access to: oel-9-x64
3488     : 2018-02-28 17:23:36 : INFO     :  EPEL_7
3488     : 2018-02-28 17:23:36 : INFO     :  Success!
3488     : 2018-02-28 17:23:36 : INFO     :  OEL_-_OS
3488     : 2018-02-28 17:23:36 : INFO     :  Success!