Administration

6.4.7 Object Migration

Objects refer to the various definitions defined in the Infrastructure and Financial Services applications. Object Migration framework within the Infrastructure facilitates you to define a set of objects to migrate across Information Domains within the same setup or across different setup. You can select one or more objects within an object type or within multiple object types and migrate same along with the dependencies of the selected object automatically. For example, if you explicitly select a Group Filter, the migration will automatically happen for the Data Element Filters which are the dependents referenced within that Group Filter. The following object types are available: Infrastructure UMM Objects such as Alias, Business Processor, Essbase Cube, Datasets, Business Measures, Business Hierarchy, and Business Dimension. Financial Services Applications infrastructure objects such as Dimension, Hierarchy, Filter, Expression Rule, and SQL Rule. You can also migrate objects which are specific to applications such as Asset Liability Management, Funds Transfer Pricing, or Profitability Management, if you have installed those applications. Following are the pre-requisites while working with Object Migration: Both the Source and Target should have the same OFSAA version number (v7.3 or later). Folders (Segments) that are present in the Source should also be present in the Target. The Source and Target environment should have the same installed locales for migration. Users in Source should be the same in Target. (At least for users associated with objects migrated). Users should have access to Folders in Target similar to the access in Source. Tables accessible to users in Source should also exist in Target. For example, if you want to migrate a Data Element Filter based on "Table A" and "Table B" in the Source, those two tables should exist in the Target. The key processing Dimensions should be the same in both the Source and Target environments. For member migration, the dimension type should have the same Attributes in both Source and Target environments. Migration of Infrastructure UMM Objects happens over a secure Java Socket based communication channel. To facilitate effective communication between the Source and Target systems and also to display the UMM objects from the source, you need to import the SSL certificate of Source in to the Target. Oracle Financial Services Software Confidential - Restricted 443

Administration

For Object migration across setups, migration process should always be triggered from the target setup. You need to login to the target setup and select the required information domain. Object Migration works more like an IMPORT into the Target. Thus, in case of migrating objects within the same setup across Information Domains, you need to have logged into the Target Information Domain in order to migrate the objects. The following object types will not be migrated with their parent objects even though they are registered as dependencies: Currencies registered as dependents of Interest Rate Codes (IRCs). Dimension Members registered as dependents. Ensure that these dependencies exist in the target environment prior to the migration of parent object. You (AAI System Administrator) need to have FU_MIG_HP function role mapped to access the Object Migration framework within Infrastructure. You can access Object Migration in the Utilities section of Administration module within the tree structure of LHS menu. Ensure that you have logged in to the Target setup and have selected the required Information Domain from the Connected to drop down list to which you need to migrate the objects from Source setup. Select Administration > Utilities > Object Migration. The Object Migration Summary screen is displayed as shown below.

The Object Migration Summary screen displays the list of pre-defined Object Migration rules with the other details such as Name, Folder, Source Infodom, Access Type, Modification Date, Last Execution Date, Modified By, and Status. You can use the Search option to search for a required Object Migration rule based on the Name or Folder in which it exists. The pagination option helps you to view the list of existing Object Migration rules within the system. For more information, refer Pagination section. In the Object Migration Summary screen you can do the following: Define Source Configuration Create Object Migration Definition

Oracle Financial Services Software Confidential - Restricted 444

Administration

View Object Migration Definition Modify Object Migration Definition Copy Migration Rules Migrate Stored Object Rules View Migration Execution Log 6.4.7.1 Define Source Configuration You can define a source configuration by specifying the database connection details and user credentials to access the database. You can also edit a pre-defined Source configuration. To define a Source Configuration in the Object Migration Summary screen: 1. Click button from the Object Migration tool bar. The Source Configuration screen is displayed with the pre-configured database details. You can also click button to view the pre-configured database details.

2. Click button adjacent to the Name field. The screen is refreshed and enables you to enter the required details. 3. Enter a Name for the source connection and add a brief Description. 4. Enter the Source Database details as tabulated: Oracle Financial Services Software Confidential - Restricted 445

Administration

Field

Description

Fields marked in red asterisk (*) are mandatory. Enter the JDBC (Java Database Connectivity) URL configured by the JDBC Driver Name administrator to connect to the database. For example, oracle.jdbc.driver.OracleDriver Enter the connection string in the following format. JDBC Connection String jdbc:oracle:thin:@<hostname:port>:<servicename> User ID Password Web Server URL Source Infodom Enter the user ID required to access the database. Enter the password required for authentication. Enter the web server URL in the format https://<hostname>:<port>/<domain> Enter the source Information Domain on which the database exists.

5. Click Validate to validate the specified configuration details. 6. Click Save to save the Source Definition details. The Audit Trail section at the bottom of Source Configuration screen displays the metadata information about the source definition created. You can also edit a pre-defined Source Definition by selecting the required source definition from Name drop down list. Edit the details, and click Save. 6.4.7.2 Create Object Migration Definition You can create an Object Migration definition in the target setup and launch the migration from the definition, or save the definition details and execute the migration process at a later point. If source objects exist in the target setup, the objects are migrated only on selection of Overwrite Object option in Object Migration definition screen. If source objects do not exist in the target setup, then the objects are created in the target setup. The dependent objects are migrated first and then the parent objects. To create an Object Migration definition: 1. Click button from the Object Migration tool bar. The New - Object Migration screen is displayed.

Oracle Financial Services Software Confidential - Restricted 446

Administration

2. Enter the Object Migration details as tabulated:

Field Description

Fields marked in red asterisk (*) are mandatory. Select the required folder from the drop down list. This folder refers to the folder associated with the Object Migration rule. Select one of the following options: Read-Only: Select this option to give other users access to only view the Access Type Object Migration definitions. Read/Write: Select this option to give other users access to view and modify the Object Migration definitions. Enter a name for the Object Migration definition. Ensure that there are no special characters or extra spaces in the name specified. Enter a brief description about the definition. Select the required source configuration from the drop down list. The list displays

Folder

Name

Description Source

Oracle Financial Services Software Confidential - Restricted 447

Administration

Field

Description
the available source configurations that are created from the Configuration screen. Select this checkbox to overwrite the target data, if source objects exist in the target setup.

Overwrite Object

Object Selection and Placement After you select an object type from the Migration rules LHS menu, the Object Selection and Placement section will display the following options related to that object type: This field is displayed if you have selected a segment /folder-based object type. Select the required source segment/folder from the drop-down list. Source Segment/Folder All the registered objects for the selected source segment/folder are displayed in the Source Infodom table. Note: If you leave Source Folder blank, the Source Infodom table displays all objects in all the folders to which you have access in the source environment. Object-type specific selections, such as Filter Type For some object types, there are additional selections. For example, if you select the object type as Filters, you can select the required Filter Type from the dropdown list. The Source Infodom table displays all objects belonging to the selected Filter Type. If you leave Filter Type blank, all filters will be displayed. This field is displayed if you have selected a segment /folder-based object type. Target folder is the folder to which the selected objects are migrated. Select Same as Source option to migrate the objects to the same folder as source folder. By default, Same as Source is selected. Select the required folder from the drop-down list if you want a folder other than source folder. Consider the following scenarios to know how the Parent and Dependent objects are migrated to the selected Target Folder. Dependent objects are migrated either implicitly or explicitly. Target Folder Implicit Migration: This occurs when the dependents are not explicitly selected. The dependent will be migrated automatically if its parent is selected (this occurs regardless of whether it is folder-based). For folderbased objects, the dependent migration uses Same as Source logic: It uses a Target Folder matching the dependents Source Folder. Explicit Migration: When you need to migrate the dependent objects to a specific folder (different than the dependents Source Folder), explicitly select the dependent object and the desired Target Folder for it. Note: Explicit selection takes precedence over implicit migration for a dependent.

Oracle Financial Services Software Confidential - Restricted 448

Administration

Field

Description
For folder-based objects: A dependent object will not inherit the parents Target Folder. This logic avoids the potential for unintended duplicates; that is, an object could be a dependent of multiple parent objects, and those parents each could be targeted for a different folder. From OFSAAI v7.3.3.0.0, an auto validation is done to check if the Target Folder exists. If it does not exist, The object will not be migrated. Objects parents (if any) will not be migrated, regardless of whether the child is implicitly or explicitly selected for migration. If the object has children whose migration could be valid (i.e. a valid Target Folder and valid dependents, if any) then migration is done by migrating a child prior to its parent to ensure integrity of parent. All available objects are displayed based on your selection of object type and (if applicable) source segment/folder. Select the checkbox corresponding to the required object and click to

migrate the object to the target folder. You can also double click to select the required object. Source Infodom Table Click to select all the listed objects for migration.

(Optional) You can use the Search and pagination options to find the required object. Click the Search button and enter the name or Reset button to clear the search

description in the Search screen. Use criteria. Use the

Find button to find an object displayed on the current page.

All objects which you have selected for migration are displayed. Select the checkbox corresponding to the required object and click Target Infodom Table to

remove the object from migration. You can also double click to remove the required object. Click to remove all the selected objects from migration.

3. The Selected Objects grid shows all objects you have explicitly selected, for all object types. (Optional) Click button from the Selected Objects tool bar to populate the complete

object details such as Target Modification Date (if object exists in target Infodom) and Operation (Add/Update) that can be performed during migration. 4. The Dependent Objects grid shows all objects which are automatically migrated due to a dependency in a parent object. Oracle Financial Services Software Confidential - Restricted 449

Administration

(Optional) Click button from the Dependent Objects tool bar to display the dependencies of the selected objects. To view the dependencies of a specific object, click on the object Name in either the Selected Objects grid or the Dependent Objects grid. The parent / child dependencies are displayed in the Parent / Child Dependency Information screen.

You can also toggle the view of Parent / Child dependency information by selecting Parent or Child in the Dependency Information grid. 5. The Audit Trail section will display details about Object Migration Rule creation and modification, after it is saved. You can add comments from the User Comments tab. 6. Click Migrate to save and migrate the selected source objects to target setup or click Save to save the Object Migration definition for future migration. You can later run the saved object migration rule. For more information, refer to Migrate Stored Object Definition section. Once the migration starts, the source objects are migrated to target setup and the Migration details such as status, start and end time are recorded. You can click View Log in the Object Migration Summary screen to view the details. NOTE: In case of an error during migration of any dependent objects, the specific parent object is excluded from migration. You can view the Migration Execution Log for details. 6.4.7.3 View Object Migration Definition You can view individual Object details at any given point. To view the existing Object Migration definition details: 1. Select the checkbox adjacent to the Object Migration Definition Name. 2. Click displayed. button in the Object Migration tool bar. The View - Object Migration screen is

Oracle Financial Services Software Confidential - Restricted 450

Administration

3. Click

button from the Selected Objects tool bar to populate the complete object

details such as Target Modification Date (if object exists in target Infodom) and Operation (Add/Update) that can be performed during migration. 4. Click button from the Dependent Objects tool bar to display the dependencies of the selected Object. 5. The Audit Trail section displays the details about Object Migration Rule creation and modification. You can add comments from the User Comments tab. 6.4.7.4 Modify Object Migration Definition To update the existing Object migration definition details: 1. Select the checkbox adjacent to the Object Migration Definition Name. 2. Click displayed. 3. Edit the required details. For more information, refer Create Object Migration Definition. NOTE: You cannot edit the Source details. button in the Object Migration tool bar. The Edit - Object Migration screen is

4. Click Save and save the changes. In the Object Migration Summary screen, you can also click Object Migration Definition details. 6.4.7.5 Copy Migration Rules The Copy Migration Rules facilitates you to quickly create a new Migration Rule Definition based on the existing Source-Target Object mappings or by updating the required mapping details. To copy an existing Migration Definition: 1. Select the checkbox adjacent to the Rule Name whose details are to be duplicated. 2. Click button in the Object Migration tool bar. Copy button is disabled if you have selected multiple migration rules. 3. Edit the Migration Rule Definition as required. You can modify the details such as Folder, Name, Description, Access Type, Overwrite option, and also view the dependencies of the selected objects. For more information, refer Create Object Migration Definition. NOTE: You cannot edit the Source details. button to delete the

4. Click Migrate to migrate the selected source objects to the target setup or click Save to save the Object Migration definition for future migration. Oracle Financial Services Software Confidential - Restricted 451

Administration

6.4.7.6

Migrate Stored Object Definition You can execute a stored Object Migration Definition and migrate the mapped objects to the target setup. You can also interrupt the ongoing migration process at any given point. To execute migration from a Stored Object Rules: 1. Select the checkbox adjacent to the Object Migration Definition Name. 2. Click button in the Object Migration tool bar.

The migration process is triggered and the source objects are migrated to target setup. The details can be viewed by clicking View Log in the Object Migration Summary screen. You can also interrupt the ongoing migration process by selecting the object rule definition and clicking 6.4.7.7 View Migration Execution Log You can view the status of an executed migration rule definition with the log details of each migrated object (parent) with the dependencies (child objects) indicated as components, along with its sequence and severity. To view the log details of an executed migration rule definition: 1. Click View Log in the Status column corresponding to the required Object Migration Definition. The View Log screen is displayed with the list of all the executed Object Migration Rule definitions. 2. Click on the Task ID of the required Object Migration Rule and view the migration status such as Task ID, Sequence, Severity, Message Description as Successful, Started, or Failed, Message Date, and Message Time. button.

6.4.8 Patch Information

This feature is available from OFSAAI 7.3.2.1.0 ML and subsequent versions.

Oracle Financial Services Software Confidential - Restricted 452