![]() ![]() ![]() ![]() ![]() ![]() |
This section includes the following topics:
Finding and Replacing Environment Values
Use the Find and Replace page to search for environment values that differ between domains. Environment values are certain predefined fields in the configuration data whose values are very likely to change when you move your configuration from one domain to another (for example, from test to production). Environment values represent entities such as URLs, URIs, file and directory names, server names, e-mails, and such. Also, environment values can be found in alert destinations, proxy services, business services, SMTP Server and JNDI Provider resources, and UDDI Registry entries.
This page behaves differently based on whether or not you are in a session. If you are in a session, you can find and replace environment values. However, if you are outside a session, you can find environment values only; Replace All is disabled.
A list of relevant values is displayed, which includes the Owner, Type, and the Environment Value columns.
All occurrences of the environment value you entered in the Find Value field are replaced with the environment value you entered in the Replace with field in the current session.
Note: | Certain environment values are complex XML objects that cannot be found and replaced using the console. However, you can still set these environment values directly by using the
ALSBConfigurationMBean from a script. For detailed information about
ALSBConfigurationMBean , see the
Javadoc for Oracle Service Bus Classes. In addition to setting them through the API, you can set complex type environment values using customization files. See Executing Customization Files. |
For detailed information about
EnvValueTypes
, see the
Javadoc for Oracle Service Bus Classes. The Java types and location values of these environment values are specified in the javadoc.
The Create Customization File page provides a convenient way to generate a customization file for a set of resources or projects that you select. You can then use this file as a starting point for making your desired modifications by specifying the actual values for an environment.
You can use customization files to make changes to environment values as well as to change references within resources. Customization files can include customizations for all the environment values found in the resources you selected, including complex environment values types defined inside the EnvValueTypes
class. In addition, it includes a reference customization type for changing resource references inside resources with dependencies.
The customization schema (Customization.xsd
) which describes the customization types is available at the following location in your Oracle Service Bus installation:
BEA_HOME
\modules\com.bea.common.configfwk_[version].jar
, where BEA_HOME
represents the directory in which you installed Oracle Service Bus.
The Create Customization File page displays the list of objects in your configuration. The name and type of each object is displayed.
Use this page to execute a customization XML file that has been previously saved on your system. Customization files provide a convenient way to modify your environment during deployment, from development to staging, from staging to production, or during design time.
You must be in a session to execute a customization file.
If you limit customizations to only resources modified in the current session, the Apply To column gets updated with the resources modified in current session. If you limit customizations of a project or folder, then the resources modified in current session within that project or folder are displayed in Apply To column.
To view customization details, within the session, select View Changes under Change Center, and click the Customization task. See Viewing Configuration Changes.
![]() ![]() ![]() |