When migrating security, there are really two scenarios proposed to artifacts on your target environment: clean or dirty. If you have already done a clean migration (that is, the first time) to your target once, then the environment is now dirty. So, subsequent migrations must take into consideration the possibility of overwriting or replacing existing items. Regarding Security Realm migration, the WLS Security Realm migration utility handles all of this for you. For example, if you export a Security Realm from Development and it contains a group named BIAdministrators that also exists in the Production environment, the import into Production will not overwrite the BIAdministrators group already existing there.
To understand how to migrate the default Security Realm from one environment to another, follow these steps:
C:TempMyExport
, in the Export Directory on Server field. The file path you enter must already exist:
C:TempMyImport
.Following the preceding steps, you have successfully migrated a single Security Realm from one environment to another. Unless you checked the Overwrite checkbox when you exported the Security Realm, WLS will automatically use a difference algorithm to ensure that no users, groups, and so on are overwritten in the target environment.
3.139.239.17