| Oracle® Enterprise Manager Getting Started with Management Pack Plus for SOA 10g Release 5 (10.2.0.5.0) Part Number E14396-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Getting Started with Management Pack Plus for SOA 10g Release 5 (10.2.0.5.0) Part Number E14396-04 |
|
|
PDF · Mobi · ePub |
Besides discovery and monitoring capabilities, Enterprise Manager Grid Control also offers provisioning capabilities using deployment procedures that help you deploy Oracle Service Bus (OSB) resources from a source OSB domain or Oracle Software Library (Software Library) to a target OSB domain.
The resources of OSB can be organized into individual projects. Projects are non-hierarchical, disjointed, top-level grouping constructs. All resources (such as business services, proxy services, WS-Policies, WSDLs, schemas, XQuery transformations, JARs, and so on) reside in exactly one non-overlapping project. Resources can be created directly under a project or be further organized into folders. Folders may be created inside projects or inside other folders, and the folders are similar to directories in a file system, with the project level being the root directory.
And as described in the previous chapter, a deployment procedure is a procedure that contains a hierarchal sequence of provisioning or patching steps, where each step may contain a sequence of other steps. In other words, the workflow of all tasks that need to be performed for a particular lifecycle management activity is encapsulated in a deployment procedure.
The deployment procedure used for provisioning OSB resources is Oracle Service Bus Resource Provisioning. Using this deployment procedure, you can provision the resources for Oracle Service Bus 2.6, 2.6.1, 3.0, and 10gR3 (3.1).
This chapter describes how you can use this deployment procedure to provision OSB resources. In particular, this chapter covers the following:
Provisioning Oracle Service Bus Resources from Oracle Service Bus Domain
Provisioning Oracle Service Bus Resources from Oracle Software Library
This section describes how you can provision OSB resources directly from a source OSB domain.
In particular, this section covers the following:
Before running the deployment procedure to provision OSB resources from a source OSB domain, meet the following prerequisites:
Ensure that the source host and target host are discovered and monitored in Enterprise Manager Grid Control.
Ensure that Oracle Management Agent 10g Release 5 (or higher) is installed on the source domain host as well as on the target domain host.
Ensure that the source OSB (from where you want to export the resources) is already discovered and monitored in Enterprise Manager Grid Control.
Register the credentials of the target host as preferred credentials in Enterprise Manager Grid Control.
Ensure that Software Library is set up. For instructions to set up the Software Library, see Setting Up Oracle Software Library. For more information, refer to the Enterprise Manager Advanced Configuration Guide available at the following URL:
If you want to use a customization file to customize the environment variables in the changed (target) environment, then you must ensure that the customization file is available as a generic component in Oracle Software Library. For instructions to create generic components, refer to the Enterprise Manager Advanced Configuration Guide available at the following URL:
To provision OSB resources from a source OSB domain, follow these steps:
In Grid Control, click Deployments. Enterprise Manager Grid Control displays the Deployments page.
On the Deployments page, in the Deployment Procedure Manager, click Deployment Procedures. Enterprise Manager Grid Control displays the Deployment Procedure Manager page.
On the Deployment Procedure Manager page, in the Procedures tab, from the table, select Oracle Service Bus Resource Provisioning. Then click Schedule Deployment. Enterprise Manager Grid Control displays the Select Source page.
On the Select Source page, in the Source section, select Oracle Service Bus Domain.
For Domain, click the torch icon and select the OSB domain from where the resources can be exported and deployed to a target OSB domain. In the following page of the wizard, you will be allowed to select the domain's projects that you want to export.
For BEA Home Directory, specify the full path to the BEA home directory where all BEA product-related files are stored. For example, /home/mark/bea.
Click Next. Enterprise Manager Grid Control displays Select Projects page.
On the Select Projects page, do the following:
In the Resource Summary section, select the projects you want to export and deploy to the target OSB domain. The selected projects are exported to a JAR file, and the JAR file is moved to the host where the target OSB domain is running.
Note that the resources of the selected projects that exist in the target OSB domain but not in the exported JAR file will be deleted.
In the Export Mode section, do one of the following:
Select Export Projects if you want to export the resources at project level. While deploying the exported JAR file to the target host, the entire project is deployed. This may add, overwrite, or delete resources depending on the availability of resources on the target host.
Select Export Resources if you want to export the resources at resource level. While deploying the exported JAR file to the target host, only the resources are deployed. This may add or overwrite resources depending on the availability of resources on the target host.
To understand these options better, read the use cases described in Understanding Export Modes.
(Optional) In the Security Options section, if the projects you want to export contain any resources with sensitive data, then specify a pass-phrase to protect them. The same pass-phrase will be used to import the proctected resourced during deployment.
(Optional) In the Save Projects to Software Library section, select Save Projects to Software Library and specify a component name and location if you want to save the exported project JAR file as a generic component in the Software Library.
By default, the projects you select here are exported to a JAR file and moved to the host where the Administration server of the target OSB domain is running. However, the JAR files are not saved in the Software Library for future use. Using this option, you can save them as a component in the Software Library.
On the Select Target page, do the following:
In the Target section, specify the following:
For Domain, click the torch icon and select the OSB domain where you want to deploy the selected resources.
For BEA Home Directory, specify the full path to the BEA home directory where all BEA product-related files are stored.
(Optional) In the Advanced Options section, select the settings you want to retain if you have done some customization to the resources selected for deployment, and if you want to preserve those changes in the target OSB domain.
Note that for Oracle Service Bus 2.6.x, Security and Policy Configuration, Credentials, and Access Control Policies cannot be preserved.
In the Customization section, provide details about the customization file that can be used to modify the environment settings in the target OSB domain.
If you do not want to use a customization file, select None.
If you are using a customization file and if it is available on the host where the target OSB domain is running, then select Use the Customization file on the target host and specify the full path to the location where the file is present.
If the customization file is stored as a generic component in Oracle Software Library, then select Select the customization file from the Software Library and specify the full path to the location in Oracle Software Library where the generic component is stored.
Click Next. Enterprise Manager Grid Control displays the Set Credentials page.
On the Set Credentials page, specify the following and click Next.
Specify the login credentials of the source and target Oracle Sevice Bus (OSB) domains.
Specify the credentials of the hosts where the Management Agents, which are monitoring the administration servers of the OSB domains, are running
On the Schedule page, schedule the deployment procedure to run immediately or later, and specify a unique name for the deployment procedure so that it can be tracked. Click Next. Enterprise Manager Grid Control displays the Review page.
On the Review page, review the details you have provided for provisioning OSB resources, and click Submit.
The following describes the different use cases and explains how the export modes will work for those circumstances.
While the first column shows the project selected from the source domain and the resources contained in that selected project, the second column shows the availability of that project in the target domain. And, while the third column shows how Export at Project Level work, the fourth column shows how Export at Resource Level works.
Table 5-1 Understanding Export Modes
| Source Domain | Target Domain | Export at Project Level | Export at Resource Level |
|---|---|---|---|
|
You have selected Project_1 from the source domain, and this project has Resource_1, Resource_2, and Resource_3. |
The target domain has no projects at all. |
The entire Project_1 will be deployed to the target domain. |
The entire Project_1 will be deployed to the target domain. |
|
You have selected Project_1 from the source domain, and this project has Resource_1, Resource_2, and Resource_3. |
The target domain has Project_1, and this project has Resource_1. |
The entire Project_1 will be deployed to the target domain, wherein, Resource_1 will be overwritten because it is already available in the target domain, and Resource_2 and Resource_3 will be ADDED. |
Only the resources of Project_1 will be deployed to the target domain, wherein, Resource_1 will be overwritten because it is already available in the target domain, and Resource_2 and Resource_3 will be ADDED. |
|
You have selected Project_1 from the source domain, and this project has Resource_1. |
The target domain has Project_1, and this project has Resource_1, Resource_2, and Resource_3. |
The entire Project_1 will be deployed to the target domain, wherein, Resource_1 will be overwritten because it is already available in the target domain, and Resource_2 and Resource_3 will be DELETED. |
Only the resources of Project_1 will be deployed to the target domain, wherein, only Resource_1 will be overwritten because it is already available in the target domain. The other two resources already available in the target domain, that is, Resource_2 and Resource_3 will NOT be affected. |
This section describes how you can provision OSB resources from the Software Library.
In particular, this section covers the following:
Before running the Deployment Procedure to provision OSB resources from the Software Library, meet the following prerequisites:
Ensure that the target host is discovered and monitored in Enterprise Manager Grid Control.
Ensure that Oracle Management Agent 10g Release 5 (or higher) is installed on the the target host.
Register the credentials of the target host as preferred credentials in Enterprise Manager Grid Control.
Ensure that the Software Library is set up. For instructions to set up the Software Library, see Setting Up Oracle Software Library. For more information, refer to the Enterprise Manager Advanced Configuration Guide available at the following URL:
Export the resources of an OSB domain as a JAR file. Use OSB console for this.
Ensure that the JAR file is available as a generic component in Oracle Software Library. For instructions to create generic components, refer to the Enterprise Manager Advanced Configuration Guide available at the following URL:
If you want to use a customization file to customize the environment variables in the changed (target) environment, then you must ensure that the customization file is available as a generic component in Oracle Software Library. For instructions to create generic components, refer to the Enterprise Manager Advanced Configuration Guide available at the following URL:
To provision OSB resources from a source OSB domain, follow these steps:
In Grid Control, click Deployments. Enterprise Manager Grid Control displays the Deployments page.
On the Deployments page, in the Deployment Procedure Manager, click Deployment Procedures. Enterprise Manager Grid Control displays the Deployment Procedure Manager page.
On the Deployment Procedure Manager page, in the Procedures tab, from the table, select Oracle Service Bus Resource Provisioning. Then click Schedule Deployment. Enterprise Manager Grid Control displays the Select Source page.
On the Select Source page, in the Source section, select Oracle Software Library.
For Component, click the torch icon and select the generic component that contains the resources to be deployed to a target OSB domain.
(Optional) For Pass Phrase, specify a pass-phrase if any of the resources in the JAR file contain sensitive data and are protected. The same pass-phrase is used while importing these resources to the target domain.
Click Next. Enterprise Manager Grid Control displays Select Target page.
On the Select Target page, do the following:
In the Target section, specify the following:
For Domain, click the torch icon and select the OSB domain where you want to deploy the selected resources.
For BEA Home Directory, specify the full path to the BEA home directory where all BEA product-related files are stored.
(Optional) In the Advanced Options section, select the settings you want to retain if you have done some customization to the resources selected for deployment, and if you want to preserve those changes in the target OSB domain.
Note that for Oracle Service Bus 2.6.x, Security and Policy Configuration, Credentials, and Access Control Policies cannot be preserved.
In the Customization section, provide details about the customization file that can be used to modify the environment settings in the target OSB domain.
If you do not want to use a customization file, select None.
If you are using a customization file and if it is available on the host where the target OSB domain is running, then select Use the Customization file on the target host and specify the full path to the location where the file is present.
If the customization file is stored as a generic component in Oracle Software Library, then select Select the customization file from the Software Library and specify the full path to the location in Oracle Software Library where the generic component is stored.
Click Next. Enterprise Manager Grid Control displays the Set Credentials page.
On the Set Credentials page, specify the following and click Next.
Specify the login credentials of the source and target Oracle Sevice Bus (OSB) domains.
Specify the credentials of the hosts where the Management Agents, which are monitoring the administration servers of the OSB domains, are running
On the Schedule page, schedule the deployment procedure to run immediately or later, and specify a unique name for the deployment procedure so that it can be tracked. Click Next. Enterprise Manager Grid Control displays the Review page.
On the Review page, review the details you have provided for provisioning OSB resources, and click Submit.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
