This section describes how to integrate Oracle Entitlements Server with Oracle Enterprise Repository. It includes the following topics:
You can use Oracle Enterprise Repository to manage OES policy data as OER assets. By integrating OER with OES, you can:
|Note:||While the OER console allows direct modification of data in an OES policy asset, it is recommended that policy changes first be made in OES and then imported to OER. See Importing/Exporting Policy Asset Data.|
To manage OES policies with OER:
Follow these steps to set the required import/export properties in OER:
The OES Policy asset type must be imported in OER. This asset type defines OES metadata, such as privileges, policy, resources, and resource attributes. Follow these steps:
ales32-admin/data/alerand select the appropriate Policy Asset Type zip file. Then click Next twice.
ALES Policy Asset Typeappears in the Type Manager.
The Asset Editor displays OES Policy Assets in the following tabs:
OER maintains version information for its assets. OES Policy Assets use version numbers in the format N.N (1.0, for example). When importing Policy Assets into OER for the first time, the version number is set to 1.0. When you subsequently import the same assets, the version number increments by 1. You can also modify the version number of an asset within OER.
The policyIX utility can perform imports/exports of policy asset data between OES and OER.
PolicyIX makes use of configuration files for imports/exports with OER. For details, see Import/Export Configuration Files.
For more information about policyIX itself, seein the Administration Reference
To export policy assets directly to OER, run policyIX with the
policyIX -exportToALER <config_file>
To export the data to OER using a policy data file:
policyIX -exportToALER <config_file> <file_name>
The structure of policy data files has changed in this release. If <
file_name> was generated by an earlier version of policyIX, perform the following steps to add the necessary information to the file before exporting the data to OER:
To import directly into OES, use the
policyIX -importFromALER <config_file>
To import using a file:
This section describes the configuration file used for imports/exports between OER and OES. This file uses XML to specify required OER information.
|Note:||Further information about the configuration file used with policyIX, seein the Administration Reference guide.|
<aler_property name="<property_name>" value=”<value>”/>
server_version—(Required) Server version (2.6 or 3.0)
server_url—(Required) connection URL
username—(Required) user name for connecting to OER
userPassword—(Required) user password
assetName—(Required) name of the asset
assetDescription—(Optional) Description of the asset
importAssetVersion—(Required) Asset version to import; valid only if the
-importFromALER option is used in the policyIX command.
Listing 7-1 provides an example of the OER-related elements in the configuration file:
<aler_property name="server_version" value=”3.0”/>
<aler_property name="userName" value="admin"/>
<aler_property name="userPassword" value="tan66kds9"/>
<aler_property name="assetName" value="MyALESPolicy"/>
<aler_property name="assetDescription" value="An
ALES Policy asset"/>
<aler_property name="importAssetVersion" value="2"/>