Database Reference
In-Depth Information
Using the Software Library yields a lot of advantages for administrators, including the following:
•
Facilitates patching and provisioning tasks in both modes, online and offline
•
Supports referenced file locations, allowing administrators to leverage existing IT
infrastructures (file servers, web servers, and storage systems) to store and stage software
entities for patching and provisioning activities
•
Allows for organization of software entities into logical folders for efficient management
As mentioned earlier, the Software Library is the core repository for everything within EM12c, when it comes to
patching and provisioning. We have briefly discussed how to get to the Software Library console, the types of folders
that can be configured within the library, and its advantages. What we haven't discussed yet is how to configure the
Software Library so it can be used. Let's take a look at that now.
Configuring the Software Library
Before you can start using the Software Library, you must set it up through the Software Library Administration
console. A Software Library must consist of at least one upload file location on the host where the Oracle Management
Server (OMS) is running. A storage location in the Software Library represents a directory that is either uploaded to
the library or generated and saved by some user-owned processes.
There are three options for upload file locations when configuring the Software Library: an OMS Shared
Filesystem, OMS Agent Filesystem, or Referenced File Location. These are the only supported storage options for
setting up the Software Library. Let's take a quick look at these options:
OMS Shared Filesystem
: This location is required to be shared (or mounted) across all the
OMS hosts.
OMS Agent Filesystem
: Using this option, ensure that you have a preferred or name
credential for the OMS host set.
Referenced File Location
: This option allows you to leverage the organization's existing
IT infrastructure for sourcing software binaries and scripts. Referenced File Locations
support three storage options:
•
HTTP
: An HTTP storage location represents a base URL that acts as the source of files that
can be referenced.
•
NFS
: An NFS storage location represents an exported filesystem directory on a server.
The server does not need to be the OEM host target.
•
Agent
: An agent storage location is similar to the OMS Agent Filesystem option, but an
OEM agent can monitor any host. The agent can be configured to serve the files located
on that host.
To configure the Software Library, you need to decide on the upload file location. In many of the configurations
I have done, I use the OMS Shared Filesystem for the Software Library, because it is simple to set up and is local to the
OMS. Let's take a look at how to set up this type of share for the Software Library.
■
when setting up the Software Library, no matter the type of location you use, the question of size comes to
mind. how large is the Software Library supposed to be? what do i need to preallocate for the Software Library? you
should allocate as much space as you think is going to be used. i've always recommended a starting size between 5gb
and 50gb. this is due to the agent software needing to be downloaded into the Software Library before deployment.
Note
