These policies are also attached to Web services and clients.įor SSL, configured self-signed certificates. Oracle Platform Security is useful for applications such as ADF, WebCenter, and SOA Composite applications.įor Oracle Web Services Manager, created Oracle Web Services Manager policies. The Oracle Access Manager configuration data resides in a file and the policy and configuration data resides in a database, as described in the Oracle Fusion Middleware Administrator's Guide for Oracle Access Manager.įor Oracle Platform Security, created security policies and stored credentials in the Credential Store Framework (CSF). These profiles are in the form of LDAP entries residing in Oracle Internet Directory.įor Oracle Identity Federation, configured various trusted identity providers and service providers.įor Oracle Access Manager 11 g, set up authentication with corresponding WebGates configured in the Web tier of the protected applications. In addition, you may have made other configuration changes such as adding ACLs, changing schemas, the Listener configuration, server configuration, plug-ins, mappings, auditing, logging, and keystores.įor Oracle Directory Integration Platform, created synchronization profiles to various targets. Oracle Access Manager 11 g or Oracle Access Manager 10 gįor Oracle Internet Directory, created the desired LDAP trees and entries, in particular, users and groups.įor Oracle Virtual Directory, created adapters to various data sources, such as LDAP and databases, and you may have configured a Local Store Adapter (LSA) to create local LDAP data, which resides in the local file system. Installed and configured Identity Management, including the following components: Installed a database to be used for Identity Management components such as Oracle Internet Directory, Oracle Directory Integration Platform (which depends on Oracle Internet Directory,) and Oracle Identity Federation. In both scenarios, you have performed the following in the test environment: Moving Identity Management to an Existing Production Environment Moving Identity Management to a New Production Environment
#HOW T OPEN THE ANT MIGRATION TOOL IN WELKIN SUITE HOW TO#
The following topics describe how to move Identity Management from a test environment to a production environment: Modify any information that is specific to the new environment such as host name or ports.Ģ1.2 Moving Identity Management Components to a Production Environment Move other data, such as UMS user messaging preferences, data for Oracle WebCenter applications, or Oracle Web Cache configuration files. (The default security information is moved when you move the configuration of components.) If an external LDAP was used in the test environment, move security information, such as users and groups, the identity and policy stores, and credentials. For application-level data sources, you must deploy the ADF application configured with the application-level data sources to a server in the target domain, and manually configure the data sources on the target domain. When you move the configuration of components, the script cop圜onfig handles only global data sources defined in each Oracle WebLogic Server domain. (You specify the hosts for each Managed Server in the move plan.) For example, if the source domain contains Managed Servers server_1 and server_2 on Host A and Managed Servers server_3 and server_4 on Host B, you must specify a similar relationship between Managed Servers and hosts at the target. When you move the configuration of a component, the scripts replicate the topology of the source. Moving Oracle Data Integrator to a Production EnvironmentĬonsiderations in Moving to and from an Oracle RAC Environment Moving Oracle Enterprise Content Management to a Production System Moving Oracle Real-Time Decisions to a Production System Moving Oracle Business Intelligence Components to a Production System Moving Oracle Portal, Oracle Forms Services, Oracle Reports, and Oracle BI Discoverer Components to a Production Environment Moving the Web Tier to a Production Environment Moving Oracle WebCenter to a Production Environment
Moving Oracle SOA Suite to a Production Environment Moving Identity Management Components to a Production Environment Overview of Procedures for Moving from a Test to a Production Environment This chapter includes the following topics: You can also use this approach for testing and rolling out upgrades. You can develop and test applications in a test environment, and then eventually roll out the test applications and, optionally, test data to your production environment. This chapter describes how to move Oracle Fusion Middleware from a test environment to a production environment. 35/46 21 Moving from a Test to a Production Environment