15 Complete Mandatory Common Post-Installation Tasks

This section describes the mandatory post-installation tasks to complete before starting working with Oracle Fusion Applications.

This section contains the following topics:

15.1 Introduction to Completing Mandatory Post-Installation Tasks

After successfully completing the installation phases on all the hosts in the environment, perform the following required manual steps described in this section.

Some components in the Oracle Fusion Applications environment are dependent on one another. Therefore, it is important to start and stop components in the proper order. In the course of normal IT operations, common operations include shutting down computers and starting them back up. Therefore, it is crucial to start and stop Oracle Fusion Applications in a sequential manner. See Start and Stop an Oracle Fusion Applications Environment in the Oracle Fusion Applications Administrator's Guide.

15.2 Apply Patches to the New Environment

Refer to Oracle Fusion Applications release notes for mandatory post-installation steps, including the application of all mandatory patches. For general information about applying patches to an applications environment, see Introduction to Patching Oracle Fusion Applications in the Oracle Fusion Applications Patching Guide.

15.3 Update the MDS Schema Database Statistics

After Oracle Fusion Applications is deployed and provisioned, ensure optimized query plans for Oracle Metadata Services (MDS) queries are generated so that performance does not decline until the next automatic statistics collection window. For each MDS schema, execute the following statements in SQL*Plus as a privileged database user, for example SYS.

  1. Execute the following command to regather the statistics:

    execute dbms_stats.gather_schema_stats(

    ownname =>'schemaOwner',

    estimate_percent =>dbms_stats.auto_sample_size,

    method_opt =>'for all columns size auto',

    cascade => true);

    Replace schemaOwner with the name of the schema, for example FUSION_MDS. Also, place the entire command in a single line at the time of execution.

  2. If there is no performance improvement after collecting statistics, then flush the shared pool to clear the execution plan for the database and generate a new query plan, using the following command:

    alter system flush shared_pool;

    alter system flush buffer_cache;

    Perform this action only when the system is not being actively used as it may affect the performance of production systems.

15.4 Set Up Notifications

Oracle User Messaging Service is a component of Oracle SOA Suite, which enables to receive notifications sent from SOA applications.

Applications in the following product families receive approval notifications and complete approvals and rejections of requests through e-mail:

  • Oracle Fusion Customer Relationship Management

  • Oracle Fusion Financials

  • Oracle Fusion Human Capital Management

  • Oracle Fusion Supply Chain Management

  • Oracle Fusion Procurement

  • Oracle Fusion Project Portfolio Management

Before proceeding, ensure that an e-mail server exists. If the bulk e-mail feature of Oracle Fusion Customer Relationship Management is intended to be used, set up the e-mail to handle bulk e-mail. To configure an e-mail server, see Adding an E-Mail Server in the Oracle Fusion Middleware Administrator's and Developer's Guide for Oracle Business Intelligence Publisher.

15.4.1 Configure E-Mail Notification Using Oracle SOA Suite

Configure Oracle SOA Suite as follows to enable e-mail notifications:

  1. For existing users, associate the users with their e-mail addresses in the domain.

  2. For new users, do the following:

    1. Add user profile in the domain.

    2. Create e-mail account in the e-mail server for the added user.

    3. Associate the user profile with the respective e-mail address.

  3. Configure e-mail driver properties.

    To enable the workflow participants to receive and forward notifications, configure Oracle User Messaging Service by setting the appropriate driver instances with Oracle Enterprise Manager Fusion Applications Control.

    1. In the navigation pane, expand farm - User Messaging Service - usermessagingdriver-email.

    2. Go to User Messaging Email Driver - Email Driver Properties. The Email Driver Properties page displays.

    3. In the Driver-Specific Configuration, modify the Outgoing and Incoming properties with the following:

      Modify OutgoingMailServer, OutgoingMailServerPort, OutgoingDefaultFromAddr, OutgoingUsername, and OutgoingPassword.

      Modify IncomingMailServer, IncomingMailServerPort, IncomingMailIDs, IncomingUserIDs, IncomingUserPasswords, and receivefolder.

    4. Select the ImapAuthPlainDisable checkbox.

    5. Click Apply to save the changes.

    To configure e-mail driver properties for other usermessagingdriver-email services under farm - User Messaging Service, repeat Steps a to e.

  4. Configure notification properties to enable workflow e-mail notifications using Oracle Enterprise Manager Fusion Applications Control:

    1. In the navigation pane, expand farm - SOA.

    2. Go to SOA Infrastructure - SOA Administration - Workflow Notification Properties. The Workflow Notification Properties page displays.

    3. From the Notification Mode list, choose All.

    4. In the Notification Service section, specify the notification channel values. These properties are used to notify the users of any changes to the state of a task. Workflow notifications can use three types of addresses:

      From Address: For sending notifications.

      Actionable Address: For receiving actionable responses. The Actionable Address is the account in which task action-related e-mails are received and processed by human workflow.

      Reply To Address: For receiving reply notifications.

    5. Click Apply to save the changes.

    To configure workflow notification properties for other Oracle SOA Suite servers, repeat Steps 3a to 3e.

  6. Specify the actionable e-mail account name using Oracle Enterprise Manager Fusion Applications Control:

    1. In the navigation pane, expand farm - SOA.

    2. Go to SOA Infrastructure - SOA Administration - Workflow Task Service Properties. The Workflow Task Service Properties page displays.

    3. In the Actionable Email Account field, specify the incoming actionable e-mail account to use. The default account name is Default, which is the account configured in Step 3. If a different account name is specified in the Actionable Email Account field, then create and configure that account.

    For more information on configuring human workflow notification properties, see Configuring Human Workflow Notification Properties in the Oracle Fusion Middleware Administering Oracle SOA Suite and Oracle Business Process Management Suite guide.

    Repeat Steps 2 to 4 to configure e-mail notification separately for each product family such as Oracle Fusion CRM, Oracle Fusion HCM, and so on.

  7. Restart the Oracle WebLogic Server Managed Servers for the domains in the product families:

    1. Stop the Managed Servers by using one of the following scripts from the Oracle Fusion Applications Middleware home directory. In these scripts, managed_server_name specifies the name of the Managed Server and admin_url specifies the listen address and port number of the domain's administration server. The listen address is the host name, IP address, or domain name server (DNS) name. When prompted, enter the user name and password.

      Platform Script

      UNIX

      FA_MW_HOME/user_projects/domains/domain_name/bin/stopManagedWebLogic.sh managed_server_name admin_url

    2. Start the Oracle WebLogic Server Managed Servers for the product families using one of the following scripts from the fusionapps Middleware directory. In these scripts, managed_server_name specifies the name of the Managed Server and admin_url specifies the listen address (host name, IP address, or DNS name) and port number of the domain's administration server. When prompted, enter the user name and password.

      Platform Script

      UNIX

      FA_MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh managed_server_name admin_url

    For more information about performing administrative activities, see Perform Basic Administrative Tasks in the Oracle Fusion Applications Administrator's Guide.

  8. Add the host name and address of the e-mail server to the /etc/hosts file on the server hosting the SOA managed servers where the drivers are running.

15.5 Create a Custom Index for SYSAUX Segments

Because the database audit trail feature is activated, it is recommended to create a custom index for audit segments on SYSAUX tables to improve the performance of any audit reporting that may occur. Skip this task if the Fusion Applications database is created using the Provisioning Wizard. If the Provisioning Wizard is not used to create the Fusion Applications database, perform this task.
Before creating a custom index, complete the task described in Moving an AUDIT segment from the SYSTEM to the SYSAUX Tablespace.
  1. Login as a SYS user
  2. Execute the following SQL statement:
    create index sys.i_aud3 on sys.aud$(ntimestamp#) tablespace SYSAUX;
Depending on the audit reporting needs regarding the SYSAUX tables, it is recommended to review and adjust the custom index as meeded.

15.6 Next Steps

Review and complete the conditional common post-installation tasks to perform before proceeding to the product specific post-installation tasks. Go to Complete Conditional Common Post-Installation Tasks to get started.