This article assumes assumes that cloning to target system from source system has been completed and integration of cloned target instance with OID (Oracle Internet Directory) has already been performed.
High Level Steps:
- Delink all Oracle E-Business Suite users that were linked to the original Oracle Internet Directory users
- On the target system, start only the Admin Server
- Deregister the cloned Oracle E-Business Suite from Oracle Access Manager
- Remove Oracle E-Business Suite AccessGate from the cloned Oracle E-Business Suite instance.
- Integrate EBS 12.2 again with Oracle Access Manager using note 1576425.1
Detailed steps:
Delink all Oracle E-Business Suite users that were linked to the original Oracle Internet Directory users
The SQL script $FND_TOP/patch/115/sql/fndssouu.sql can be used by system administrators to unlink the user’s GUID information from an FND_USER account. This script removes the link between the Oracle E-Business Suite and Oracle Internet Directory.
As the APPS user, run the script to unlink all Oracle E-Business Suite users:
SQL>@$FND_TOP/patch/115/sql/fndssouu.sql %
Deregister the cloned Oracle E-Business Suite from Oracle Access Manager
Execute the following command to deregister Oracle E-Business Suite from Oracle Access Manager.
$ txkrun.pl -script=SetOAMReg -deregisteroam=yes
The script will now perform the following main tasks automatically:
- Deregister Oracle E-Business Suite AccessGate with Oracle Access Manager.
- Disable WebGate in your Oracle E-Business Suite webtier.
- Clear Oracle E-Business Suite profile options Application Authenticate Agent (APPS_AUTH_AGENT) and Applications SSO Type (APPS_SSO) to switch back to local login. If you registered the instance with -ebsProfileLevel=Site (default), deregistration will clear the profiles at SITE level. If you registered the instance with -ebsProfileLevel=Server, deregistration will clear the profiles at SERVER level
The script must complete successfully. Review the log files for any error messages.
The script will not automatically delete the following entries, as you may have also used these for other partner applications:
- Authentication Scheme (by default named EBSAuthScheme)
- Authentication Module (by default named LDAP_EBS)
- Identity Store (by default named OIDIdentityStore)
Remove Oracle E-Business Suite AccessGate from the cloned Oracle E-Business Suite instance.
1)
Delete your Oracle E-Business Suite AccessGate using your WebLogic Administration Console
Delete Oracle E-Business Suite AccessGate deployment using your WebLogic Administration Console
http://ebshost.example.com:7001/console
In the WebLogic Administration Console, navigate to EBS_domain_sid > Deployments, stop then delete the Oracle E-Business Suite AccessGate application named “accessgate”. Ensure that you click ‘Activate Changes’ in the ‘Change Center’ pane, for the changes to take effect.
2)
Delete the datasource “OAEADatasource”
Navigate to EBS_domain_sid > Services > Data Sources, and delete data source “OAEADatasource”. Ensure that you click ‘Activate Changes’ in the ‘Change Center’ pane, for the changes to take effect.
3)
Delete the managed server on which accessgate was deployed
- If the managed server oaea_server1 is currently running, shut it down as follows:
$ sh $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh stop oaea_server1
The script will prompt for the following passwords:
- Enter the WebLogic Admin password.
Enter the required information when prompted.
- Run the command below on the application tier node where the oaea_server1 managed server resides. This will delete the managed server, and also update the respective context variables that contain references to the deleted managed server:
$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl \
ebs-delete-managedserver \
-contextfile=$CONTEXT_FILE -managedsrvname=oaea_server1
4)
Remove the managed server and port from the mod_wl_ohs.conf configuration:
$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl \
-contextfile=$CONTEXT_FILE \
-configoption=removeMS \
-accessgate=<host>.<domain>:<port>
To determine the value of the Port that was used for the oaea_server1 managed server, search for ‘s_wls_oaeaport’ in $CONTEXT_FILE.