Creating an Application Data Model

The following procedure enables you to:

  • Initiate creation of an Application Data Model (ADM)

  • View and edit application tables

  • View referential relationships

  • Manually add a referential relationship

  • Discover sensitive columns

  • Set the type for sensitive columns

Before proceeding, ensure that you have the following privileges:

  • EM_ALL_OPERATOR for Enterprise Manager Cloud Control users

  • SELECT_CATALOG_ROLE for database users

  • Select Any Dictionary privilege for database users

Note:

When you create an ADM, the PL/SQL metadata collection packages are automatically deployed on the target database. The Database user must have DBA privileges to auto-deploy the packages.

To create an Application Data Model:

  1. From the Application Data Models page, view the diagram that shows how you can create a database for a test environment.

    As the diagram shows, the first step is to create an ADM.

  2. Create an ADM:

    1. Click Create.

      A pop-up window requesting general properties information appears.

    2. Provide the required Name and Source Database.

      The Source Database is the source from which the metadata is to be extracted.

    3. Select an Application Suite:

      If you select Custom Application Suite:

      • By default, metadata collection is enabled for the ADM creation process.

      • If you uncheck "Create One Application For Each Schema," you create a shell ADM and will need to edit the ADM later to add applications and tables. Also, no metadata collection job is submitted, unlike the default choice.

      If you select Oracle Application Suite:

      • Oracle E-Business Suite–You provide database credentials for APPS user (or equivalent) and submit a job to create the ADM.

      • Oracle Fusion Applications–You provide database credentials for FUSION user (or equivalent) and submit a job to create the ADM.

      Note the following points about metadata collections:

      • The metadata collection for the selected application suite populates the ADM with the applications and tables in the suite.

      • The ADM can collect metadata for one or more schemas. An ADM application typically represents a schema. Each schema you select becomes an ADM application, and the ADM becomes populated with the tables in the schema, particularly in the case of custom applications. Note, however, that multiple applications can also map to a single schema, as in the case of Fusion Applications. The actual mapping depends on the application metadata discovered by the metadata collection job.

    4. Click Continue.

      Assuming that you selected Custom Application Suite, a Schemas pop-up appears in which you select schemas to include from the Available list.

    5. Click Continue, provide the schedule parameters, then click Submit to submit the metadata collection job.

      The ADM you created appears in the Application Data Models page. The Most Recent Job Status table column indicates that the metadata collection job is running. The model is locked, and you cannot edit it during this period until the status indicates that the job is complete.

  3. View and edit application tables:

    1. Select the model you created, then select Edit.

      The Applications and Tables subpage appears, displaying the applications found during metadata collection.

      To see the tables for an application, click the expand ( > ) icon.

    2. To edit an application, select the application, open the Actions menu, then select Add Table to Application.

      The Add Table to Application pop-up window appears.

    3. Click the Table search icon.

      The Search and Select pop-up appears, showing all of the tables from the selected schema that are not assigned to an application.

    4. Select an unassigned table, then click OK.

      The table name now appears in the Add Table to Application pop-up.

    5. After selecting a Table Type, click OK.

      The table now appears in the Applications and Tables view.

  4. View referential relationships:

    1. Click the Referential Relationships tab.

      There are three types of referential relationships:

      • Dictionary-defined

        Upon opening this tab, this view shows the referential relationships that the metadata collection extracted, resulting from primary key and foreign key relationships. You can remove relationships from the ADM if desired.

      • Imported from template

        If there are application templates available from the vendor of the enterprise application, for example, Oracle Fusion Applications or Oracle E-Business Suite, then the ADM can be created from the application vendor-supplied template by using the Import action on the ADM home page.

      • User-defined

        See the step below about manually adding a referential relationship for more information.

    2. Open an application view by selecting it, then using the chevron icon (>) to reveal parent and dependent key relationships, or by selecting Expand All from the View menu to view all relationships.

  5. Manually add a referential relationship:

    1. From the Referential Relationships tab, open the Actions menu, then select Add Referential Relationship.

      The Add Referential Relationship pop-up window appears.

    2. Select the requisite Parent Key and Dependent Key information.

    3. In the Columns Name list, select a dependent key column to associate with a parent key column.

    4. Click OK to add the referential relationship to the ADM.

      The new dependent column now appears in the referential relationships list.

  6. Discover sensitive columns automatically or add them manually:

    To automatically discover sensitive columns:

    1. From the Sensitive Columns tab, open the Actions menu, then select Create Sensitive Column Discovery Job.

      The Parameters pop-up appears.

    2. Select one or more applications and one or more sensitive column types.

      Each type you select is processed for each application to search for columns that match the type.

    3. Click Continue.

      The schedule pop-up window appears.

    4. Provide the required information, schedule the job, then click Submit when you have finished.

      The Sensitive Columns subpage reappears.

    5. Click Save and Return to return to the Application Data Models home page.

    6. When the Most Recent Job Status column indicates that the job is Successful, select the ADM, then click Edit.

    7. Select the Sensitive Columns tab, then click Discovery Results to view the job results.

    8. To set the sensitive status of any column, select the row for the column you want to define, open the Set Status menu, then select either Sensitive or Not Sensitive.

    9. Click OK to save and return to the Sensitive Columns tab.

      The sensitive columns you defined in the previous step now appear in the list.

    10. Click Save and Return to return to the Application Data Models page.

    To manually add sensitive columns:

    1. From the Application Data Models page, select an ADM, then click Edit.

    2. Select the Sensitive Columns tab, then click Add.

      The Add Sensitive Column pop-up appears.

    3. Provide the required information and an optional Sensitive Column Type, then click OK.

      The sensitive column now appears in the table for the Sensitive Columns tab.

  7. Change the type for sensitive columns:

    1. Click the Sensitive Columns tab.

      This view shows the sensitive columns that have already been identified.

    2. Select the sensitive column for which you want to change the type.

    3. Open the Actions menu, then select Set Sensitive Column Type.

      The Set Sensitive Column Type pop-up window appears.

    4. Select the new type and click OK.