Backing Up the Application Tier Configuration Create a Protected Resource for Oracle Identity Navigator

11-22 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

11.12 Backing Up the Application Tier Configuration

It is an Oracle best practices recommendation to create a backup after successfully completing the installation and configuration of each tier, or at another logical point. Create a backup after verifying that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps. The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process. For more details, see the Oracle Fusion Middleware Administrators Guide. For information on database backups, refer to the Oracle Database Backup and Recovery Users Guide. To back up the installation to this point, follow these steps: 1. Back up the web tier as described in Section 5.5, Backing up the Web Tier Configuration. 2. Back up the Oracle Access Manager database. This is a full database backup, either hot or cold. The recommended tool is Oracle Recovery Manager. 3. Back up the Administration Server domain directory as described in Section 6.15, Backing Up the WebLogic Domain. 4. Back up the Oracle Internet Directory as described in Section 7.7, Backing up the Oracle Internet Directory Configuration. 5. Back up the Oracle Virtual Directory as described in Section 9.10, Backing Up the Oracle Virtual Directory Configuration. For information about backing up the application tier configuration, see Section 20.4, Performing Backups and Recoveries.

11.13 Create a Protected Resource for Oracle Identity Navigator

To create a protected resource for Oracle Identity Navigator, log in to the Oracle Access Manager console at http:admin.mycompany.comoamconsole using the oamadmin account. Then proceed as follows:

1. From the Navigation window expand: Application Domains

IDMDomainAgent .

2. Click Resources.

3. Click Create on the tool bar below the Browse tab.

Enter the following information: ■ Type : http Note: The files ssoKeystore.jks and oamclient-truststore.jks are required when you integrate Oracle Access Manager running in Simple mode with Oracle Identity Management or Oracle Access Manager. When you integrate these components, you are asked to copy these files to the DOMAIN_ HOME configfmwconfig directory. If you subsequently extend the domain on machines where these files have been placed using packunpack, you must recopy ssoKeystore.jks and oamclient-truststore.jks after unpacking. Extending the Domain with Oracle Access Manager 11g 11-23 ■ Host Identifier : IDMDomain ■ Resource URL : oinav

4. Click Apply.

5. From the Navigation window expand: Application Domains

IDMDomainAgent Authentication Policies.

6. Click Protected HigherLevel Policy.

7. Click Edit on the tool bar below the Browse tab.

8. In the Resources box, click +.

9. From the list, select the resource oinav.

10. Click Apply.

11. From the Navigation window expand: Application Domains

IDMDomainAgent Authorization Policies.

12. Click Protected Resource Policy.

13. Click Edit on the tool bar below the Browse tab.

14. In the Resources box, click +.

15. From the list, select the resource oinav

16. Click Apply.

11-24 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 12 Extending the Domain with Oracle Adaptive Access Manager 12-1 12 Extending the Domain with Oracle Adaptive Access Manager Oracle Adaptive Access Manager OAAM is built on a Java EE-based, multi-tiers deployment architecture that separates the platforms presentation, business logic, and data tiers. Because of this separation of tiers, OAAM can rapidly scale with the performance needs of the customer. The architecture can leverage the most flexible and supported cross-platform Java EE services available: a combination of Java, XML and object technologies. This architecture makes OAAM a scalable, fault-tolerant solution. OAAM Apps is divided into following two components. ■ OAAM Administration Applications ■ OAAM Server Applications This chapter describes the procedure to extend an existing IDM domain to include Oracle Adaptive Access Manager. This chapter contains the following topics: ■ Section 12.1, Prerequisites