| Oracle® Access Manager Configuration Manager Installation and Administration Guide 10g (10.1.4.0.1) Part Number B32392-01 |
|
|
View PDF |
| Oracle® Access Manager Configuration Manager Installation and Administration Guide 10g (10.1.4.0.1) Part Number B32392-01 |
|
|
View PDF |
This chapter suggests how to validate the success of a data migration performed using the Oracle Access Manager Configuration Manager. Topics in this chapter include:
As discussed in Chapter 1, Oracle recommends that you develop specific tests to help you quickly evaluate the configuration data changes in the source deployment before you began migrating data. After migration, you can use these same tests in the target deployment to ensure that everything is working as expected.
Caution:
Oracle strongly recommends that you "true up" any dependencies in the target deployment. For example if you migrated workflow data, ensure that all workflow participants mentioned in the source directory are included in the target. Otherwise, the workflow in the target deployment may not work properly.Confirm that the prerequisite tasks outlined in Table 4-1 have been performed before starting tasks in this chapter.
Table 4-1 Validation Prerequisites
| Confirm | Prerequisite Task | Look In |
|---|---|---|
|
Develop tests in the source deployment that validate the success of configuration data changes to be migrated |
Data Migration Planning and Deliverables |
|
|
Migrate data |
|
|
|
Restart all Identity and Access Servers in the target deployment |
Restarting Servers After Migration |
|
|
Ensure that all dependencies in the source are also in the target environment |
For more information you can use to ensure that the migrated data operates properly, see the following topics:
Note:
The procedures you complete to validate the success of the migration in a live target deployment are essentially the same regardless of your product release (10g (10.1.4.0.1) or release 7.0.4). Only certain product terms differ.Oracle recommends that you use the migrated data in your Oracle Access Manager 10g (10.1.4.0.1) deployment to ensure that the changes were properly migrated and everything is working as expected.
Refer to following discussions for details about validating migrated data within your target Oracle Access Manager 10g (10.1.4.0.1) deployment:
To validate data migration, you will perform tasks in the Oracle Access Manager 10g (10.1.4.0.1) Identity System Console and applications that rely on the target directory and migrated data.
The following procedure provides steps and an outline of activities you might perform to validate migrated data. Step 5 includes several suggestions about activities you might want to perform. However, the actual tasks you perform will depend on the data you have migrated.
To validate 10g (10.1.4.0.1) Identity System data migration
Identify the Identity System applications and functions that are impacted by the migrated data and develop a plan to test these in the target Identity System and applications.
In the target installation, ensure that all Identity Server services and WebPass Web server instances are running.
Go to the Identity System Console from your browser by specifying the appropriate URL. For example:
http://hostname:port/identity/oblix
where hostname refers to computer that hosts the Web server; port refers to the HTTP port number of the WebPass Web server instance; /identity/oblix connects to the Identity System Console.
The Oracle Access Manager landing page appears.
Perform any of the following tasks, or others, to prove that the migrated data is operating properly. For example:
Review panels in the User Manager, Group Manager, or Organization Manager.
Verify audit policies for the User Manager, Group Manager, Organization Manager, if these are impacted.
Review attribute access control policies in the User Manager, Group Manager, or Organization Manager
Review the Master Auditing Policy and the Global Auditing Policy, if appropriate.
Verify Password and Lost Password policies, if such data changes were migrated.
Validate any migrated workflow configuration details, when data changes were migrated.
Review object class definitions, if appropriate after migration.
Verify Identity Server and WebPass definitions; server settings; administrator information; and directory options.
Log out, as usual.
For information about performing specific tasks, see the Oracle Access Manager Identity and Common Administration Guide.
To validate data migration in the Access System, you will perform tasks in the Oracle Access Manager 10g (10.1.4.0.1) Access System Console and applications that rely on the target directory and migrated data.
The following procedure provides steps and an outline of activities you might perform to validate migrated data. Step 5 includes several suggestions about activities you might want to perform. However, the actual tasks you perform will depend on the data you have migrated.
To verify a successful 10g (10.1.4.0.1) Access System data migration
Identify the Access System applications and functions that are impacted by your migrated data and develop a plan to test these.
Make sure all Policy Manager Web server and WebPass Web server instances are running.
Go to the Access System Console from your browser by specifying the appropriate URL. For example:
http://hostname:port/access/oblix
where hostname refers to computer that hosts the Web server; port refers to the HTTP port number of the WebPass Web server instance; /access/oblix connects to the Access System Console.
The Oracle Access Manager landing page appears.
Log in as a Master Administrator.
Perform one or more of the following tasks, or others, to validate migrated data. For example:
Log out, as usual.
For more information about performing specific tasks, see Oracle Access Manager Access Administration Guide.
Oracle recommends that you use the migrated data in your Oracle COREid Release 7.0.4 deployment to ensure that the changes were properly migrated and everything is working as expected.
The following procedures describe how to validate successful data migrations in Oracle COREid Release 7.0.4:
Validating Identity System Data Migration in Oracle COREid Release 7.0.4
Validating Access System Data Migration in Oracle COREid Release 7.0.4
Note:
The procedures you complete to validate the success of the migration in a live target deployment are essentially the same regardless of your product release (10g (10.1.4.0.1) versus release 7.0.4). Only certain product terms differ.To validate data migration Identity System, you will perform tasks in the Oracle COREid Release 7.0.4 System Console and applications that rely on the target directory and migrated data.
The following procedure provides steps and an outline of activities you might perform to validate migrated data. Step 5 includes several suggestions about activities you might want to perform. However, the actual tasks you perform will depend on the data you have migrated.
To validate Identity System data migration in release 7.0.4
Identify the Identity System applications and functions that are impacted by your migrated data and develop a plan to test these.
Make sure all Identity Server services and WebPass Web server instances are running.
Go to the COREid System Console from your browser by specifying the appropriate URL. For example:
http://hostname:port/identity/oblix
where hostname refers to computer that hosts the Web server; port refers to the HTTP port number of the WebPass Web server instance; /identity/oblix connects to the COREid System Console.
The COREid landing page appears.
Log in as a Master Administrator.
Using the COREid System Console or applications, perform the following tasks, or others, to validate data that may be impacted by the migration. For example:
Review panels in the User Manager, Group Manager, or Organization Manager.
Verify audit policies for the User Manager, Group Manager, Organization Manager, if these are impacted.
Review attribute access control policies in the User Manager, Group Manager, or Organization Manager
Review the Master Auditing Policy and the Global Auditing Policy, if appropriate.
Verify Password and Lost Password policies, if such data changes were migrated.
Validate any migrated workflow configuration details, when data changes were migrated.
Review object class definitions, if appropriate after migration.
Verify Identity Server and WebPass definitions; server settings; administrator information; and directory options.
Log out, as usual.
For more information about performing specific tasks, see the Oracle COREid Access and Identity Administration Guide Volume 1.
To validate data migration Access System, you will perform tasks in the Oracle COREid Release 7.0.4 Access System Console and applications that rely on the target directory and migrated data.
The following procedure provides steps and an outline of activities you might perform to validate migrated data. Step 5 includes several suggestions about activities you might want to perform. However, the actual tasks you perform will depend on the data you have migrated.
To verify a successful Access System data migration in release 7.0.4
Identify the Access System applications and functions that are impacted by your migrated data and develop a plan to test these.
Make sure your Access Manager Web server and WebPass Web server instances are running.
Go to the Access Manager/Access System Console from your browser by specifying the appropriate URL. For example:
http://hostname:port/access/oblix
where hostname refers to computer that hosts the Web server; port refers to the HTTP port number of the WebPass Web server instance; /access/oblix connects to the Access System Console.
The Access System landing page appears.
Log in to the Access Manager/Access System Console as a Master Administrator.
Perform any of the following tasks, or others, to validate the migrated data. For example:
Log out, as usual.
For more information about specific tasks, see Oracle COREid Access and Identity Administration Guide Volume 2.
