Oracle enterprise library software

However, if you have configured the OMS Shared Storage Location on a local file system, then perform the steps listed in the Section To access the administration console, log in to Enterprise Manager Cloud Control with Administration access, and follow these steps:.

On the Software Library home page, from Actions menu, select Administration. The Software Library Administration Page is a GUI based screen that enables you to create one or more storage locations to store or refer to files that are associated with an entity. To view the entities present in the storage location, click show on the Administration page. With Enterprise Manager 12 c , a new feature called Referenced File Location has been introduced, wherein Software Library entities can refer to files that are stored on another host.

These locations are however read-only for Software Library, and will not be used for uploading files. The space requirements for configuring Software Library depends on the amount of space required for storing the software binaries, and its associated scripts. Understandably, this space requirement increases over a period of time as you create more entities.

Depending on the features or software required for provisioning and patching, you must decide and configure the Software Library storage space.

Once the storage location starts running out of space, it is important to deactivate the configured storage location so that no new uploads can happen to this location. For more information about removing a storage location, see Section Upload File Locations are locations configured for storing files uploaded by Software Library as part of creating or updating an entity. For Software Library to become usable, at least one upload file location must be configured. On adding the first upload file location, a job is submitted to import the Software Library metadata from the Oracle home of each of the installed Enterprise Manager plug-in.

Ensure that you wait for this job to complete successfully, before performing other patching or provisioning operations. When OMS instances are added, it is necessary to ensure that the configured locations are accessible from the designated host where the new OMS will be provisioned. For an OMS that will be provisioned using the Add Management Service functionality, the shared location configured as upload location should be mounted on the designated host, and verified manually.

This option is ideal for UNIX systems. However, in future, if you plan to expand the single OMS setup to a multiple OMS setup, then local file system path is not recommended. If you are implementing multiple management servers for high availability you should also make the Software Library file system highly available.

Besides accessibility and availability, it is important to ensure that there is enough space more than GB for production deployment of Enterprise Manager available for the storage of software binaries, and associated scripts for the entities that you want to create and store.

Click Change Credential to change the associated credential to be used to access this location. Referenced File Locations are locations that allow you to leverage the organization's existing IT infrastructure like file servers, web servers, or storage systems for sourcing software binaries and scripts. Such locations allow entities to refer to files without having to upload them explicitly to a Software Library storage.

The server need not be an Enterprise Manager host target. The Agent can be configured to serve the files located on that host. These locations require a named credential to be associated which will be used to access the files from the base location on the host through the Enterprise Manager Agent.

Cache Nodes is a feature in Enterprise Manager that enhances the file transfer experience to distant servers and data centers by reducing the load on the OMS. Cache nodes work on a set of predefined targets that function as one unit called the Group, and each cache node is an intermediate storage location on a host that serves a particular group of targets that it is associated with.

For more information about Cache Nodes, see Section To administer the different storage types, and to configure software library, keep the following points in mind:.

The storage needs change based on the usage pattern. Each OMS host must have a preferred normal host credential set before configuring the location. You the user configuring the Software Library must have view privilege on all the OMS, and the agent targets running on the host machine.

As per the accessibility verification, you must be able to view, and edit these newly configured locations. To add an OMS Agent storage location, ensure that you have view privileges on the target OMS host, and the agents running on that target host. System Administrators are responsible for configuring a storage location. Only after the storage location is configured, you can start uploading the entity files.

Ensure that the configured storage location is a shared location that is accessible by all the OMS instances. When you configure an upload location for the first time, a metadata registration job is submitted which imports all the metadata information of all the installed plug-ins from the Oracle home of the OMS. To track the progress of the job, click Show Detailed Results. If the Import job fails, see Section In addition to this, you can click Associated Entities to view or search the entities present in the selected upload location.

In the Host field, click the magnifier icon. In the Location field, click the magnifier icon. The selected credential is saved along with the host and selected file system path. The saved credential is used to upload files and stage the uploaded files to a host target as part of some provisioning or patching activity. This will appear as the original credential name during Edit Credential flow. To configure storage location that can be used for referring to files from the Software Library entities, perform the following steps:.

A new entry for the storage location is created, with details like Name , Location , and Status. In the Location field, provide the shared location or directory path on the NFS server to define a storage location, then click OK. A new entry for the storage location is created in the table, with details like Name , Location , and Status. In the Host field, click the magnifier icon to select a target from the list available. In the Location field, click Login As to select the credentials and browse the previously selected host.

The credential selected, either Preferred, Named or New, is saved along with the host and selected file system path. The saved credential is used for staging the files to a host target as part of some provisioning or patching activity. Note: The administrator configuring the Software Library must grant view privilege at least on the credential chosen to all designers uploading or staging the files to or from this location.

Note: When you create a new entity, these newly configured Referenced File Locations are available as storage options. Doing this will ensure that this newly configured location remains accessible from any OMS host as and when they are added.

All upload and stage requests for the files will happen through the Management Agent monitoring the OMS host. If however, you have configured the OMS Shared storage location to use a local file system path, then you must migrate it to another OMS Shared Storage Location that uses a shared or mounted path. To do so, follow these steps:. On successful completion, select the location you want to migrate, For example: OldNonShared , and click Migrate and Remove.

Click Remove to submit a job, which on successful completion deletes the storage location entry from the table. The Oracle Enterprise Manger Cloud Control 13c R1 introduces support for configuring one or more cache nodes in close proximity to a group of targets.

Once configured, the Software Library File Transfer job ensures that entity files are picked from the appropriate cache node, caching the entity files as needed, thereby reducing the time taken for transferring files to targets distant from the Oracle Management Service. Typically, creating a group with targets that belong to the same geographical location is beneficial. Proximity of these targets ensures efficient file transfers.

Having a cache node is also hugely beneficial to reduce the load on the OMS. For example, patching targets at the same time is a huge load on the OMS, as the OMS will have to orchestrate file transfers with each of the targets individually. However, you can counter this by using cache nodes in a way that the OMS just needs to transfer the files to the cache node once, and the cache node in turn processes the file transfer to the individual targets in the group that it is serving.

Note that a given group of targets can be linked to more than one cache node. This approach is employed to ensure that the load is equally balanced across the nodes, which in turn helps in maximizing the performance of the individual cache node of the associated group.

Before your begin adding cache nodes, you must ensure that you have created a group of targets to associate with the relevant cache nodes. For information on creating groups, see Groups page. Add a short description for the cache node for your reference. For example, these are the targets on different hosts restricted to Austin, U. Provide the host target machine that will be used as the cache node.

For example, slc Provide a location on the host to store the files that are transferred from the OMS. Note that the directory must already exist and must be empty. Click OK to create a cache node that serves the targets added to the group specified. A summary of the available disk space, the file transfer history, and the information about the cache node is displayed once the node is successfully created.

Once the cache node is successfully created, you can click show to view all the entities associated with the targets in the group. Additionally, you can view the group details by clicking the group name. On the Cache Node tab select the cache node that you want to update, and click Edit.

This is particularly useful when you want to change the group associated with the cache or update the quota details. On the Cache Node tab select one or more cache nodes, and click Delete. If you want to temporarily suspend the functioning of a particular cache node, click Deactivate. Typically, when the quota is full or when you have to carry out some maintenance tasks on the cache nodes, this option becomes useful.

If you want to remove all the files associated with a cache node in order to free up the quota, click Clear. These compressed files can be transported to a cache node host and imported into the cache node.

If Software Library entities are staged to one or more targets in the group served by the cache node, then the files will be served directly from the cache node in place of the OMS. Create a file with one Software Library entity internal ID per line.

Once the file cachefiles. The table on this page shows all file transfer activities that have been performed recently. The Job Name column displays the job for which the file transfer activity was performed, and the Procedure Run Name column displays the Deployment Procedure run name if it is run within a Deployment Procedure. Both these columns together can be used to identify the file transfer activity. Software Library is a repository that stores certified software binaries such as software patches, virtual appliance images, reference gold images, application software and their associated directive scripts, generally referred to as Entities.

Accesses and privileges on these entities are decided by the Super Administrators or the owner of the entity. A number of lifecycle management tasks such as patching and provisioning deployment procedures make use of the entities available in Software Library to accomplish the desired goal. Here is a pictorial representation of how a Provisioning Deployment Procedure and a Patching Deployment Procedure makes use of the entities available in the Software Library:.

The custom folder can contain User-owned folders, entities, and customized entities created by using the Create Like option. In the Create Folder dialog box, enter a unique name for the folder. Also, select the parent folder in which you want to create this new custom folder and click Save. Note: Only the owner of the folder or the Super Administrator has the privilege to delete the folder, nobody else can.

Note: You cannot create a generic component in an Oracle Owned Folder. To create a custom folder, see Section From the Actions menu, select Create Entity and click Component. Alternately, right click the custom folder, and from the menu, select Create Entity and click Component.

Note: The component name must be unique to the parent folder that it resides in. Sometime even when you enter a unique name, it may report a conflict, this is because there could be an entity with the same name in the folder that is not visible to you, as you do not have view privilege on it. Ensure that the file size is less than 2 MB. In the Notes field, include information related to the entity like changes being made to the entity or modification history that you want to track. On the Configure page, you can customize the generic component that you are creating by adding some new properties or updating the existing properties of the component.

Note: Select Shared Type to reuse the component property. Shared Type can be stored as a template, which can be used for creating different and more complicated top level types. Enter a unique name for the property. Depending on the property type selected, enter an initial or default value for the property. To add a constraint, specify the Minimum or Maximum value for the selected property type, and click Add Constraint.

The Configured Constraints table lists all the constraints added. To remove a particular constraint from the property, select the property and click Remove. On the Select Files page, you can select one or more files to be associated with the entity.

Select one of the following options:. Upload Files: If you want to upload some entity files from the local file system or the agent machine to the selected destination location. To select the destination location, in the Specify Destination section, in the Upload Location field, click the magnifier icon to select one of the following options:. If you select OMS Agent File system location, then ensure that you have the necessary privileges to access the location.

In the Specify Source section, enter the location from where the files are being sourced, these locations can either be local file system or a remote file system monitored by the Management Agent. Select one of the following options for File Source:,:. Click Browse to select the entity file from the source location, and give a unique name, and click OK.

If you select Agent Machine , select the name of the host machine from where you want to pick up the entity files. For more information about the different credential types and their setup, see Oracle Enterprise Manager Lifecycle Management Guide. Once you log in to the host machine, browse to the location where the files to be uploaded are present. Refer Files: If you select the Refer Files option, you only need to enter the source location details, since you are not technically uploading anything to the Software Library.

The corresponding Storage Type and Location Path of the selected location is populated. Click Stage As to organize the file in a temporary stage location with a unique name. On the Set Directives page, click Choose Directives to associate a component with one or more directives. Click Next. On the Review page, review all the details, and click Finish to create the component and upload it on the Software Library.

Directives are entities in the Software Library that represent a set of instructions to be performed. These are constructs used to associate scripts with software components and images.

These scripts contain directions on how to interpret and process the contents of a particular component or an image.

From Actions menu, select Create Entity and click Directive. In case you enter a unique name and it reports a conflict, it may be due to an entity with the same name in the folder that is not visible to you, as you do not have view privilege on it. On the Configure page, specify the command line arguments that must be passed to the directive to configure it.

This command provides the parameters required to execute the directive. The Argument Prefix eliminates the error-prone task of manually specifying the order of the parameter executions in a given directive. This is specially useful when a directive is made of multiple parameters. Property Name, is the name of the property, that must be a string value. Argument Suffix, is the text that must follow the command line property. Though the suffix is rarely used, it determines how the parameters must be executed, based on the suffix value.

All the parameters added appear in the order of addition against the Command Line field. To change the order of the parameter or edit any property of an existing parameter, click Edit. In the Configuration Properties section, select either Bash or Perl as defined in the script. Coordinates requests among multiple TapePlexes. These requests can consist of mounts, dismounts, and swaps, and queries configuration, volume lookup.

Separating a customer-defined portion of existing ACS hardware and tape volume pools for the period of the disaster recovery test to allow concurrent use of ACS hardware. Allows for easily combining separated hardware back into production use at the termination of the disaster recovery test without interruption of normal production processing.

The script is located at the following location:. Once a Software Library entry is deleted, it becomes inaccessible. If the location is not accessible from all Oracle Management Servers, user can experience problems during deployment of such entities later. If multiple locations for the Software Library are configured, when you deconfigure the Software Library, you can remove all except one Software Library location.

It is recommended that the system administrator periodically performs the following administrative tasks to ensure that the Software Library is functioning properly:. Check accessibility of the configured Software Library locations to ensure that they are accessible by all Oracle Management Servers. Component creation sometimes fails with "Cannot create under the software library, please contact your administrator. This may happen if the Software Library is not configured with Enterprise Manager.

Configure the Software Library as explained in Section Create the components once the Software Library is configured. Restoring the file system should be fine but you will lose the entities that were created since the last backup. These entities will still show up in the Provisioning UI but errors will be encountered while accessing them or attempting to deploy them. Skip Headers. Software Library can store the following types of entities: Components: These entities represent the primary building blocks of the provisioning framework.

Note: When you add a Software Library location for the first time, the configuration will take some time. Subsequently, adding other Software Library locations will be quicker. This is a required parameter. PAR Filename The file name must end with a.

The name of file can be viewed in the Job output page. Oracle Wallet Password This is used to securely store all secret property values in an encrypted Oracle Wallet. However, the password is used only if any exported entity has a secret property. Exclude File Select this option to exclude file, binary, or script associated with an entity to be exported. Export You can choose to either export all entities or export a selected entity. This location must be accessible by the Oracle Management Server.

Oracle Wallet Password This is an optional field. The password is required if the PAR file contains an Oracle Wallet that stores secret property values. Hence, if you are importing an Oracle provided PAR file, then password need not be provided. Force New Revision If an entity being imported is already present in the Software Library, then this option allows the user to force a newer revision of the entity to be created during import.

If the option is not selected and the PAR file contains an entity in a directory that already exists in the repository, then the import process will fail.

Purge deleted entities to conserve disk space. For information about these features, see Using the Software Library. All rights reserved. Book List. Contact Us.