Glossary

association

A term used to describe a designated source directory and target directory pair. Each directory association includes a designated source directory from which logical objects are selected for migration to a designated target directory. All the history related to the migration of logical objects between the designated source and target directory pair belongs to the association.

attribute

One or more characteristics or traits related to logical (and physical) objects. For example, the logical object "Workflow Definition" includes a name attribute and a description attribute in addition to other attributes.

configuration data

Oracle Access Manager, or Oracle COREid, product-specific configuration data and access policy data stored in a Lightweight Directory Access Protocol (LDAP) directory. This data includes workflow and configuration information that governs the appearance and functionality of the Identity System and Access System. Configuration data is managed by the Identity System.

configuration management

Life-cycle management of specific Oracle Access Manager (or Oracle COREid) configuration data. Oracle Access Manager Configuration Manager enables you to push changes from one deployment to another deployment within the same release. See also environment.

configuration dn

The bind DN for Oracle Access Manager (or Oracle COREid) configuration data. See also COREid

COREid

The product formerly known as "Oblix NetPoint" or "Oblix COREid" has been renamed "Oracle COREid". Oracle COREid Release 7.0.4 was made available as part of Oracle Application Server 10g Release 2 (10.1.2). See also Oracle Access Manager.

delta

The difference between the logical objects of the source directory and the logical objects of the target directory in an associated pair (prior to migration). See also logical object

deployment

Each individual installation of Oracle Access Manager 10g (10.1.4.0.1), or Oracle COREid Release 7.0.4, is known as a deployment. Your enterprise can include one or more deployment types, for example a development or QA or production or preproduction deployment. You can have multiple deployments of the same type.

directory

An LDAP directory that is installed and configured for Oracle Access Manager 10g (10.1.4.0.1) or Oracle COREid Release 7.0.4. Each directory that you add to Oracle Access Manager Configuration Manager can be designated as either the source or target in an association pair. See also environment.

environment

A supported LDAP directory server that is installed and configured to work with Oracle Access Manager 10g (10.1.4.0.1), or Oracle COREid Release 7.0.4, within various deployments (development, or QA, or production) within your enterprise. Such directories include either , or Oracle COREid, configuration data stored as physical entities, which correspond to logical objects. See also logical object.

export

In the context of Oracle Access Manager Configuration Manager, the term export refers to writing configuration data that you select to an LDIF file, which you can use with an external tool to import data to an LDAP directory. See also import andLDIF file.

horizontal data migration

The process of copying configuration data changes from one Oracle Access Manager 10g (10.1.4.0.1), or Oracle COREid Release 7.0.4, deployment to another. You cannot migrate 10g (10.1.4.0.1) data to a release 7.0.4 deployment, nor vice versa. See also environment.

import

In the context of Oracle Access Manager Configuration Manager, the term import refers to opening a file and extracting information in a usable format. For example, after exporting configuration data to an LDIF file using Oracle Access Manager Configuration Manager, you can import data from the LDIF file into an LDAP directory using an external tool. See also LDIF file.

LDAP

A Lightweight Directory Access Protocol (LDAP) directory. Data stored in this type of directory is referred to as LDAP data.

LDIF file

Lightweight Directory Interchange Format (LDIF) file. LDIF files are ASCII format files that you can use to exchange and synchronize data between Lightweight Directory Access Protocol (LDAP) servers using an external tool.

logical object

For most applications you can have a repository (a database or directory server) that stores the data as physical entities (tables in a database or LDAP entries in a directory server). Many times, a group of physical entities are logically related so tightly that an individual physical entity cannot make much sense with respect to the application. These physical entities can be grouped together under the name of one object (called a logical object). A logical object can also be a one-to-one mapping with a physical entity. A logical object can have dependencies on other logical objects. For example in Oracle Access Manager 10g (10.1.4.0.1) and Oracle COREid Release 7.0.4, Workflow Definition is configuration information that can be considered as a logical object with dependencies on workflow steps which in turn have dependencies on workflow participants.

Oracle Access Manager Configuration Manager migrates (copies) logical objects from one installed deployment to another. For example, from an Oracle Access Manager 10g (10.1.4.0.1) Development directory to another Oracle Access Manager 10g (10.1.4.0.1) Development directory or to an Oracle Access Manager 10g (10.1.4.0.1) Production directory. Migration of each logical object is atomic (the logical object and all its dependents are copied to the target). See also LogicalObject.

LogicalObject

The inmemory structure of the logical object and its attribute-values and the dependent logical objects. This represents the actual logical object that exists in the particular environment (directory). LogicalObject defines the mapping of a logical object type to one or more physical entities. It also defines the dependencies among the logical objects of a directory in an association pair. Migration of one logical object is atomic (the logical object and all its dependents are copied to the target). See also logical object.

migration

The process of pushing (copying) selected logical objects (and related physical entities) from the designated source to the designated target directory of an associated pair. For example, if you have defined and tested a new password policy in your QA deployment you can propagate the policy to a Production system using Oracle Access Manager Configuration Manager. When you migrate data, all selected entries in the configuration tree are copied from the source directory server to the target directory server in the associated pair.

oblix tree

The directory tree in which Oracle Access Manager, or Oracle COREid Release 7.0.4, configuration and access policy data are stored.

Oracle Access Manager

Starting with release 10g (10.1.4.0.1), the product formerly known as Oracle COREid is now named Oracle Access Manager. See also COREid.

repository

The datastore that you install for use with Oracle Access Manager Configuration Manager. The repository is where migration information is stored, including migration transaction data, snapshots, LDIF files to import, and audit details. Configuration Manager log files are not stored in the repository.

restore

Restore a directory snapshot to revert changes made to the logical objects since the snapshot.

roll back

Revert changes made during a specific migration transaction and return the logical objects in the target directory to their state before the specific migration. See also transaction.

source

The directory in an associated pair in Oracle Access Manager Configuration Manager that is designated to send a copy of the configuration data changes to the target. See also target.

snapshot

A backup copy of the configuration data for all logical objects in the designated directory made at a given point in time using Oracle Access Manager Configuration Manager. A snapshot will include only the logical objects (workflow definitions, for example, but not the workflow instances). A snapshot can be used to restore (return) the directory to the state it was in at the time the snapshot was made.

system configuration

A tab in Oracle Access Manager Configuration Manager that enables individuals with the HMAdmin privilege to enter and edit Oracle Access Manager Configuration Manager repository information. See also repository.

target

The recipient environment in an Oracle Access Manager Configuration Manager associated pair (the directory designated to receive a copy of the configuration data changes from the source). See also environment and source.

transaction

Every configuration data migration that is performed using Oracle Access Manager Configuration Manager is referrred to as a transaction. A transaction ID is assigned automatically just before the migration occurs. You can provide an optional transaction description. See also transaction record.

transaction record

A record is created each time you migrate configuration data using Oracle Access Manager Configuration Manager. Each transaction record includes the entire group of logical objects (and their dependencies) that were migrated from the source to the target of the associated pair. A list of all transaction records is available. You can choose a particular record and view the changes made during that transaction. You can select a transaction and rollback the changes to restore the target to the state it was in before that migration. See also transaction.

transformation rule

A rule you can define for a directory association. A transformation rule enables you to change the value of selected logical object attributes automatically during migration. See also migration.