Overview Oracle Fusion Middleware Online Documentation Library

6-6 Oracle Fusion Middleware Application Security Guide ■ Section Deploy an Application Using Fusion Middleware Control in the Oracle Fusion Middleware Control online help system. ■ Section 8.4, Deploying and Undeploying Oracle ADF Applications, in Oracle Fusion Middleware Administrators Guide. This section is divided into the following topics: ■ Deploying to a Test Environment ■ Migrating from a Test to a Production Environment

6.3.1 Deploying to a Test Environment

The security options available at deployment are explained in Deploying Java EE and Oracle ADF Applications with Fusion Middleware Control . When deploying an Oracle ADF application to a test environment with Fusion Middleware Control, the following operations take place: Policy Management ■ Application-specific policies packed with the application are automatically migrated to the policy store when the application is deployed. Oracle JDeveloper automatically writes the necessary configuration for this migration to occur. Credential Management ■ Application-specific credentials packed with the application are automatically migrated to the credential store when the application is deployed. Oracle JDeveloper automatically writes the necessary configuration for this migration to occur. ■ The bootstrap credentials necessary to access LDAP repositories during migration are automatically produced by Fusion Middleware Control. For details about a manual setup, see Section 21.4.7, Specifying Bootstrap Credentials Manually. Identity Management Identities packed with the application are not migrated. The domain administrator must configure the domain authenticator with the Administration Console, update identities enterprise users and groups in the environment, as appropriate, and map application roles to enterprise users and groups with Fusion Middleware Control. Other Considerations ■ When deploying to a domain with LDAP-based security stores and to preserve application data integrity, it is recommended that the application be deployed at the cluster level or, otherwise, to just one managed server. Note: Before migrating a file-based policy store that is, the file jazn-data.xml to a production environment, verify that any grant contains no duplicate permissions. If a duplicate permission one that has the same name and class appears in a grant, the migration runs into an error and it is halted. In this case, manually edit the jazn-data.xml file to remove any duplicate permissions from a grant definition, and invoke the migration again.