R12 d49656 gc10-apps dba 03

Editor's Notes

• #2: ILT Schedule: Timing Topic 30 minutes Lecture 30 minutes Practice 60 minutes Total
• #3: <Course name> <Lesson number> - Objectives Just as the preliminary installation steps were crucial in having a successful installation, the post-installation steps are important in providing a fully configured Oracle Applications system for your users.
• #4: <Course name> <Lesson number> - Overview Once Rapid Install completes the installation of Oracle Applications, there are a number of post-installation tasks to complete. Some of these tasks are necessary to finish a new installation, an upgrade, or a technology stack installation for Oracle Applications Release 12. Other tasks may be required only for systems with specific functionality. This module discusses the required and conditional tasks.
• #5: Required Post-install Steps These tasks are required for all Oracle Applications installations.
• #6: Log In to Oracle Applications You log in to Oracle Applications using a web browser from the Applications Login page URL, at: http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLogin For example: http://apps1.company.com:8000/OA_HTML/AppsLogin Once the connection has been made, the Applications Login page appears. as shown on the slide. Enter your username and password. Instructor Note: The Rapid Install Portal is obsolete. In Release 12, its features are available via other routes. For example, you can access Oracle Applications Manager by selecting the System Administrator responsibility.
• #7: E-Business Suite Home Page After your credentials have been validated on the Login page, the E-Business Suite Home Page appears. You can use this page to access responsibilities for any of the individual Oracle Applications products that your organization has licensed. The E-Business Suite Home Page provides a single point of access to HTML-based applications, Forms-based applications, and Business Intelligence applications. The system administrator should log in the first time using the System Administrator login account that is pre-configured in the Applications installation. Use the System Administrator responsibility to launch an Applications Forms session where the system administrator can complete the implementation steps.
• #8: Change Passwords The default passwords for the SYSTEM and SYS Oracle Applications database accounts are manager and change_on_install , respectively. To maintain database security and restrict access to these accounts, you should change these passwords without delay, ensuring that your choices meet your organization's security requirements. The password for both SYS and SYSTEM in the Vision Demo is manager . You should also change the default passwords for the Applications product accounts of the production and test databases Instructor Note: Further details can be found in Applications DBA Duties in Oracle System Administrator’s Guide – Configuration .
• #9: Configure Database Initialization Parameters The current init.ora settings allow for a total of 100 connections. However, after the standard setup is complete, only a few users can be connected because of the connections used by the concurrent managers, AQ workers, and job queues. Instructor Note: The relevant database initialization parameters are listed in Oracle MetaLink Note 396009.1, Database Initialization Parameters for Oracle Applications Release 12 .
• #10: Review Security Practices Review the recommended security processes documented in Oracle MetaLink Note 403537.1, Best Practices for Securing Oracle E-Business Suite Release 12 . In particular, if you have any computers that require direct access to the Applications database, but are not registered nodes in AutoConfig (such as OAM clients), you must explicitly grant access as described in the Oracle TNS Listener Security chapter of that document.
• #11: Update PL/SQL Log and Out Directory The temporary directory on your database server for log and output files from PL/SQL concurrent programs is set to /usr/tmp (UNIX) or C:\\TEMP (Windows) by default. This value is specified in the utl_file_dir parameter of the database initialization file, and assigned to the APPLPTMP environment variable. As the temporary files placed in this directory may contain sensitive information, it should have suitably restricted access, such as read and write access for the account that owns the database. This can be achieved by proceeding as follows: Enter your choice of directory as the new value for utl_file_dir in the database initialization parameter file. Use the edit AutoConfig parameters feature of Oracle Applications Manager to update the APPLPTMP variable in the Applications context file with the new utl_file_dir directory location. Run AutoConfig to recreate the environment files.
• #12: Implement Product and Country-specific Functionality Depending on which products or country-specific functionality you plan to use in your installation, you may need to perform additional tasks or apply additional patches. Refer to the individual product or country-specific implementation manuals, user's guides, or Oracle MetaLink for details..
• #13: Configure Client Software The connection between the client and the E-Business Suite forms is provided through an applet in the client Web browser. Instead of using the browser's own JVM, Oracle Applications Release 12 uses the Sun J2SE Native Plug-in , which is invoked when a user chooses to access functions that require it, such as running a form. If the J2SE Plug-in has not been installed, the browser prompts the user to download the required installation executable. Instructor Note: Oracle JInitiator (used in Release 11i) is not used in Release 12.
• #14: Tasks Specific to Your Installation These tasks are conditionally required, depending on the configuration of your Oracle Applications system.
• #16: Set Up Printers For details about setting up printers in your Oracle Applications installation, refer to the Oracle Applications System Administrator’s Guide .
• #17: Set Up Printers - Windows The concurrent manager starts by default under the internal SYSTEM account. This account does not have access to network printing devices. To run reports using the concurrent manager, complete the steps in the slide.
• #18: Resize Your Database You will need to increase the size of your database to meet the specific requirements of your system. The increase will in part depend on the products you have licensed and the additional features (such as multiple languages or multiple organizations) you configure in your installation..
• #19: Set Up National Language Support (NLS) Although the base product files are provided in American English, Oracle Applications is available in many different languages. Running Oracle Applications in languages other than American English is referred to as National Language Support or NLS. You can also run Oracle Applications in multiple languages simultaneously, and this is referred to as Multilingual Support or MLS. If you are performing an NLS installation, Rapid Install installed the translated files for all active languages during the installation. To finish the installation for NLS, follow the instructions in the Oracle Applications NLS Release Notes (available on Oracle MetaLink ).
• #20: Set Up UTF8 Character Set Regardless of the languages installed, you may need to complete additional steps if you use a Unicode character set, such as UTF8, in the database tier. With Release 12, UTF8 and AL32UTF8 are both supported Unicode character sets in the database. However, supplementary characters are not supported. If you customize seed data, your changes may be overwritten during an upgrade. This also applies to any changes to translations of seed data made using the globe icon. Instructor Note: See Oracle Applications System Administrator’s Guide – Configuration for language setup details, and Oracle MetaLink Note 393861.1, Oracle Applications Globalization Support Guide (Release 12) for further details of languages and character sets.
• #21: Complete Oracle Workflow Notification Mailer Configuration 1. From the Applications Dashboard of Oracle Applications Manager, select Workflow Manager from the "Navigate to" pull-down menu, and click on the Go button. 2. In the Workflow System region, click the Notification Mailers status icon to navigate to the Service Components page for notification mailers. At this point, the Notification Mailers status icon should be showing the status Down . 3. In the Service Components page, select the Workflow Notification Mailer service component and click the Edit button to navigate to the Notification Mailer configuration wizard. 4. In the Outbound Email Account (SMTP) region, enter the name of the outbound SMTP mail server. 5. If you want to enable inbound email processing, select the Inbound Processing parameter in the Inbound Email Account (IMAP) region, and enter the name of the inbound IMAP mail server, the username and password of the email account that the Notification Mailer uses to receive email messages, and the reply-to address of the email account that receives incoming messages, to which notification responses should be sent. 6. Click Apply , then r eturn to the Service Components page and verify that the status of the Workflow Notification Mailer service component is now Running .
• #22: Set Up and Implement Oracle Embedded Data Warehouse (EDW) The Embedded Data Warehouse (EDW) is a foundation technology for Oracle Business Intelligence applications. This end-to-end solution provides an open schema and extensible data warehousing architecture, powered by robust data warehousing tools. EDW includes fact tables from seven intelligence areas: Financials, Projects, Purchasing, Manufacturing, Marketing, Human Resources, and Supply Chain. If you licensed Oracle Embedded Data Warehouse (EDW), you must complete additional setup and implementation steps before using this product.
• #23: Set Up and Implement Discoverer End User Layer (EUL) To use Discoverer, you need a database account that enables you to connect to Discoverer. You store database account details in a Discoverer connection, along with EUL and language settings. To set up and implement the End User Layer, follow the instructions documented in Oracle MetaLink Note 373634.1, Using Discoverer 10.1.2 with Oracle E-Business Suite Release 12.
• #24: Set Up Demand Planning To set up and begin using Demand Planning, you must perform the implementation tasks outlined in the Oracle Demand Planning Installation and Configuration Guide .
• #25: Convert to a Public Sector, Education, or Not-for-Profit System Rapid Install sets up products for commercial or for-profit use. To convert your system to use public sector, education, or not-for-profit products after the installation is complete, use License Manager to register public sector or not-for-profit products. See Oracle Applications Maintenance Utilities for information on registering products.
• #26: Implement Multiple Organizations The Oracle Applications Multiple Organizations Architecture provides support for multiple organizations in a single installation of Oracle E-Business Suite, with relationships you define. Multiple Organizations specifies how the different organizations interact, and how transactions flow between them. These organizations can be ledgers, business groups, legal entities, operating units, or inventory organizations. When you install a production E-Business Suite system, the data model is identical whether you implement Multiple Organizations or not. The Multiple Organizations views used to partition data are incorporated into the normal install, and use predefined text. When you convert to Multiple Organizations, tables are renamed to use the "_ALL" suffix to denote that they now contain Multiple Organizations partitioned data. In Release 12, the AD Administration utility is used for the initial conversion of seed data and transaction data to Multiple Organizations format. Note that the underlying data model is not changed. When you create a new operating unit, a concurrent program adds the appropriate seed data. Instructor Note: For further details, see AD Administration in Oracle Applications Maintenance Utilities .
• #27: Back Up Oracle Applications After installation is complete, your operating system administrator should back up the Oracle Applications product files, including the Application Server technology stack components. Your database administrator should back up the Oracle Applications database components. Subsequently, you should establish a backup policy that meets your organization's needs, balancing the overhead of carrying out the chosen backup type and frequency against the need to be able to recover from a variety of types of system failure. The backup procedures should be tested periodically.
• #28: Understand System Administration Tasks You should be familiar with the information in the three-volume Oracle Applications System Administrator’s Guide . It contains important information about Oracle Applications. Understand Oracle Applications Maintenance Tasks You should be completely familiar with the information in both volumes of the Maintaining Oracle Applications Documentation Set ( Oracle Applications Maintenance Utilities and Oracle Applications Maintenance Procedures ). Both books contain important details about maintenance utilities and tasks.
• #29: <Course name> <Lesson number> -
• #30: <Course name> <Lesson number> -
• #31: <Course name> <Lesson number> - Refer to Practice - Accessing Oracle Applications and Configuring the Java Client Software [LAB41F0Y]