2 Before You Begin with Oracle Forms for Oracle Cloud Infrastructure

Before you use this Oracle Cloud Marketplace image, review these permission and database considerations carefully.

Required Permissions

Ensure you have the necessary permissions to:

• Create new Compute instances.
• Create new Virtual Cloud Networks or select an existing one.
• Create a Database Cloud Service instance or connect to an existing instance as the SYS user (only required if planning to use DBCS with this Forms instance).
• Create an Autonomous Database instance or connect to an existing instance as the admin user (only required if planning to use ADB with this Forms instance).
• Create an Identity Dynamic Group and Policy or modify existing ones (only required if planning to use ADB with this Forms instance)

Database Options

The database you choose at provisioning is configured for both the Oracle Fusion Middleware repository and application data.

You can easily change your configuration to use a different database for application data, but attempting to change the database used for the FMW Repository is not recommended.

• Local database: If you elected to configure this instance using the locally installed database, it will be configured and running upon completion of the provisioning.
• Database Cloud Service: If you elected to configure this instance using DB Cloud Service, you must ensure it has been configured, is running, and you have SYS credentials to access it. You will also need the Easy Connect String and the Long Connect String in order to complete the provisioning. This information can be found on the DB Cloud Service dashboard for that instance.
• Autonomous Database: If you elected to configure this instance using Autonomous Database, in addition to having the instance created and accessible, you will also need the "admin" user password and complete the following pre-setup steps:

Set Up Oracle Forms to Use Autonomous Database

1. Create an Identity Dynamic Group:
   1. From the Cloud navigation pane, click Identity and then Dynamic Groups.
   2. Click Create Dynamic Group.
   3. Type a name for your group, such as "Forms_ADB_Access".
   4. Click the Rule Builder link to the right of the Rule 1 box.
   5. Select Compartment OCID from the Match instances with list.
   6. Enter your Compartment OCID in the Value field.

      Note:

      You can match by Compute Instance OCID if the instance has not yet been accessed the first time.
   7. Click Add Rule and then Create.
2. Create an Identity Policy:
   1. From the Cloud navigation pane, click Identity and then Policies.
   2. Click Create Policy.
   3. Enter a name for your policy, such as "Forms_ADB_Policy".
   4. Click Policy Builder Show manual editor.
   5. Enter the policy as shown below. Use the Policy and Compartment name used for Step 1c above.

      allow dynamic-group <YOUR DYNAMIC GROUP NAME> to use autonomous-database-family 
      in compartment <YOUR COMPARTMENT NAME> 

      The above policy should be enter on a single line.

   6. Click Create.
3. Access the new Compute instance using SSH to begin the provisioning process.