Oracle Applications System Administrator's Guide

Oracle® Applications System Administrator's Guide - Configuration Release 12 Part No. B31453-04

December 2007

Oracle Applications System Administrator's Guide - Configuration, Release 12 Part No. B31453-04 Copyright © 1994, 2007, Oracle. All rights reserved. Primary Author: Mildred Wang, Robert Farrington Contributing Author: Ahmed Alomari, George Buzsaki, Anne Carlson, Steve Carter, Steven Chan, Siu Chang, Jennifer Collins, Ivo Dujmovic, Elanchelvan Elango, Osama Elkady, Mark Fisher, Clara Jaeckel, Ramkarthik Kalyanasundaram, Takafumi Kamiya, Senthil Madhappan. Teresa Mak, Revathy Narasimhan, Sarita Nori, Mladena Novakovic, Muhannad Obeidat, Gursat Olgun, Richard Ou, Lisa Parekh, Jan Smith, Dana Spradley, Seth Stafford, Susan Stratton, Leslie Studdard, Suchithra Upadhyayula, Venkat Vengala, Mark Warren, Aaron Weisberg, Sara Woodhull The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Contents

Send Us Your Comments Preface 1

Introduction Introduction to This Manual..................................................................................................... 1-1 Other Volumes for System Administrators.............................................................................. 1-4

2

Basic Configuration Tasks Oracle Applications Setup Steps.............................................................................................. 2-1 Configuring the Login Page for Oracle Applications.............................................................. 2-1 Personalizing the Oracle E-Business Suite Home Page........................................................... 2-5 Administering Oracle HTTP Server......................................................................................... 2-6 AdminAppServer Utility.........................................................................................................2-11 Administering Server Security............................................................................................... 2-15 Restricting Access to Responsibilities Based on User's Web Server..................................... 2-19 Application Object Library AOL/J Setup Test Suite.............................................................. 2-20 Using Oracle Application Framework.................................................................................... 2-22 AutoConfig and Oracle Applications Manager...................................................................... 2-22

3

Oracle Applications Tablespace Model and Migration Utility Introduction to Oracle Applications Tablespace Model.......................................................... 3-1 Advantages of Migrating to OATM.......................................................................................... 3-1 OATM Tablespaces................................................................................................................... 3-5 Customizations and Extensions................................................................................................ 3-8 Introduction to the Oracle Applications Tablespace Migration Utility.................................. 3-9

iii

Planning for Migration............................................................................................................. 3-9 Setting Up the Tablespace Migration Utility......................................................................... 3-10 Phase 1: Preparatory Steps...................................................................................................... 3-13 Phase 2: Migration Steps......................................................................................................... 3-18 Phase 3: Post Migration Steps................................................................................................. 3-21

4

System Administration Setup Tasks Setting Up Oracle Applications System Administrator........................................................... 4-1 Setup Checklist ................................................................................................................... 4-1 Setup Steps .......................................................................................................................... 4-2

5

Introduction to Oracle Applications Manager Introduction to Oracle Applications Manager......................................................................... 5-1 Oracle Applications Manager Setup......................................................................................... 5-2 The Site Map............................................................................................................................. 5-4 Configuration Overview........................................................................................................... 5-8

6

Defining Concurrent Programs and Requests Overview of Concurrent Programs and Requests.................................................................... 6-1 Controlling Access to Concurrent Programs............................................................................ 6-2 Organizing Programs into Request Sets .................................................................................. 6-5 Defining Request Sets.......................................................................................................... 6-6 Request Sets and Owners................................................................................................... 6-17 System Administrator Request Set Privileges ................................................................... 6-18 Request Set Incompatibilities............................................................................................. 6-19 Sharing Parameters in a Request Set.................................................................................. 6-20 Request Sets Report ................................................................................................................ 6-21 Report Parameters............................................................................................................. 6-21 Report Headings ............................................................................................................... 6-22 Organizing Programs into Request Groups .......................................................................... 6-22 Request Security Groups ................................................................................................... 6-23 Using Codes with Request Groups ................................................................................... 6-23 Customizing the Submit Requests Window...................................................................... 6-24 Customizing the Submit Requests Window using Codes ................................................. 6-26 Report Group Responsibilities Report .................................................................................. 6-27 Report Parameters............................................................................................................. 6-27 Defining Program Incompatibility Rules .............................................................................. 6-27 Incompatible and Run Alone Programs............................................................................. 6-27 Concurrent Conflict Domains............................................................................................ 6-29 Enforcing Incompatibility Rules........................................................................................ 6-30

iv

Custom Concurrent Programs................................................................................................. 6-32 Log and Output Filenames................................................................................................ 6-32 Oracle Tool Concurrent Programs..................................................................................... 6-33 Pro*C Concurrent Programs.............................................................................................. 6-34 Host Language Concurrent Programs............................................................................... 6-37 Submitting Concurrent Requests (CONCSUB).................................................................. 6-38 Copying and Modifying Program Definitions ...................................................................... 6-43 Copying and Renaming a concurrent program ................................................................ 6-44 Alter Program Priority....................................................................................................... 6-45 Modifying an Incompatible Programs List ....................................................................... 6-46 Concurrent Program Parameters ...................................................................................... 6-46 Control the Behavior of Request Parameters..................................................................... 6-47 Example of modifying a program's parameters................................................................. 6-53 Conflict Domains.................................................................................................................... 6-54 Defining Logical Databases ................................................................................................... 6-55 Concurrent Program Details Report....................................................................................... 6-56 Report Parameters............................................................................................................. 6-56 Report Headings ............................................................................................................... 6-56 Concurrent Programs Report.................................................................................................. 6-56 Report Parameters............................................................................................................. 6-57 Report Headings ............................................................................................................... 6-57 Request Groups Window........................................................................................................ 6-58 Request Groups Block........................................................................................................ 6-59 Requests Block................................................................................................................... 6-59 Concurrent Program Executable Window.............................................................................. 6-60 Concurrent Program Executable Block.............................................................................. 6-60 Stage Function Parameters Window.................................................................................. 6-62 Concurrent Programs Window............................................................................................... 6-63 Concurrent Programs Block............................................................................................... 6-63 Copy to Window................................................................................................................ 6-69 Session Control Window................................................................................................... 6-70 Incompatible Programs Window....................................................................................... 6-71 Concurrent Program Parameters Window........................................................................ 6-73 Data Groups Window............................................................................................................. 6-77 Data Groups Block............................................................................................................. 6-78 Application-ORACLE ID Pairs Block.................................................................................6-78 Concurrent Conflicts Domains Window ............................................................................... 6-79 Concurrent Programs HTML UI............................................................................................. 6-80 Search for Concurrent Programs ....................................................................................... 6-80 Create Concurrent Program .............................................................................................. 6-80 Concurrent Program - Add Parameter...............................................................................6-87

v

7

Defining Concurrent Managers Defining Managers and their Work Shifts in the Oracle Forms UI.........................................7-1 Work Shift Definitions......................................................................................................... 7-3 Using Work Shifts to Balance Processing Workload............................................................ 7-5 Using Time-Based Queues................................................................................................... 7-7 Creating Services within Oracle Applications Manager.......................................................... 7-8 Completed Concurrent Requests Report................................................................................ 7-15 Report Parameters............................................................................................................. 7-15 Report Headings ............................................................................................................... 7-15 Work Shift by Manager Report............................................................................................... 7-16 Report Parameters............................................................................................................. 7-16 Report Headings ............................................................................................................... 7-16 Work Shifts Report.................................................................................................................. 7-16 Report Parameters............................................................................................................. 7-16 Report Headings ............................................................................................................... 7-16 Specializing Managers to Run Only Certain Programs ........................................................ 7-17 Introduction to Specialization Rules.................................................................................. 7-17 Defining Specialization Rules............................................................................................ 7-17 Examples - Using Specialization Rules.............................................................................. 7-22 Defining Combined Specialization Rules........................................................................... 7-27 Using Combined Rules...................................................................................................... 7-29 Differences Between Specialization and Combined Rules ................................................ 7-32 Grouping Programs by Request Type ................................................................................... 7-33 Controlling Concurrent Managers ......................................................................................... 7-35 Manager States .................................................................................................................. 7-35 Controlling Managers from the Administer Managers form ............................................ 7-36 Controlling the Internal Concurrent Manager from the Operating System ...................... 7-38 Overview of Parallel Concurrent Processing ......................................................................... 7-42 What is Parallel Concurrent Processing?........................................................................... 7-42 Parallel Concurrent Processing Environments...................................................................7-43 How Parallel Concurrent Processing Works...................................................................... 7-44 Managing Parallel Concurrent Processing............................................................................. 7-45 Defining Concurrent Managers......................................................................................... 7-46 Administering Concurrent Managers................................................................................ 7-47 Administer Concurrent Managers Window........................................................................... 7-49 Administer Concurrent Managers Block........................................................................... 7-49 The actions you can choose for controlling a manager are:......................................... 7-50 Reviewing a Specific Manager.....................................................................................7-52 Concurrent Processes Window............................................................................................... 7-53

vi

Viewing Log Files.............................................................................................................. 7-55 Concurrent Requests Window................................................................................................ 7-56 Request Diagnostics Window............................................................................................ 7-57 Concurrent Managers Window............................................................................................... 7-58 Concurrent Managers Block...............................................................................................7-58 Work Shifts Window..........................................................................................................7-61 Specialization Rules Window............................................................................................ 7-63 Work Shifts Window............................................................................................................... 7-65 Combined Specialization Rules Window...............................................................................7-67 Combined Specialization Rules Block................................................................................ 7-68 Specialization Rules Block................................................................................................. 7-68 Concurrent Request Types Window....................................................................................... 7-70 Concurrent Request Types Block....................................................................................... 7-70 Viewer Options Window........................................................................................................ 7-71 Viewer Options Block........................................................................................................ 7-72 Nodes Window........................................................................................................................ 7-73 Nodes Block....................................................................................................................... 7-73

8

Setting Up and Starting Concurrent Managers Concurrent Managers................................................................................................................ 8-1 Setting Up Concurrent Managers........................................................................................ 8-1 Starting the Concurrent Managers....................................................................................... 8-4 Restarting the Concurrent Managers................................................................................... 8-6 Shutting Down the Concurrent Manager Service (Windows)..............................................8-7 Removing the Concurrent Manager Service (Windows)..................................................... 8-7 File Conventions.................................................................................................................. 8-8 Directory Privileges............................................................................................................. 8-9 Printing.............................................................................................................................. 8-11

9

Printers Printers and Printing ................................................................................................................ 9-1 Overview............................................................................................................................. 9-1 Printer Types, Print Styles, and Printer Drivers................................................................... 9-2 Sequence of Printing Events ................................................................................................ 9-4 Setting Character-Mode vs. Bitmap Printing ...................................................................... 9-5 Setting Up Your Printers........................................................................................................... 9-8 Printing Setup Interrelationships......................................................................................... 9-9 Printer Setup Information Is Cached On Demand............................................................... 9-9 Printer Setup with Pasta.......................................................................................................... 9-10 Overview........................................................................................................................... 9-10

vii

Setup for Basic Printing with Pasta.................................................................................... 9-10 Defining Configuration Files for Specific Printers............................................................. 9-11 Using a Different Configuration File as the Default...........................................................9-11 Modify an Existing Printer Type to Use Pasta................................................................... 9-12 Add a New Printer Type to Use Pasta............................................................................... 9-13 Setting Margins.................................................................................................................. 9-13 Printing a Report Generated Using the noprint Option..................................................... 9-14 Generating Other Formats Using the Preprocessing Option............................................. 9-15 Font Source........................................................................................................................ 9-16 Language-Specific Font Support........................................................................................ 9-17 Configuration File Options................................................................................................ 9-18 Command Line Parameters............................................................................................... 9-24 Using PrintForms..................................................................................................................... 9-25 Create the PrintForm......................................................................................................... 9-26 Common UNIX Printing System (CUPS) Integration............................................................ 9-28 Customizing Printing Support in Oracle Applications .........................................................9-31 Hierarchy of Printer and Print Style Assignments ................................................................ 9-39 Hierarchy of Printer Assignments..................................................................................... 9-40 Hierarchy of Print Style Assignments................................................................................ 9-41 System Administrator Printer and Print Style Settings...................................................... 9-42 End User Printer and Print Style Settings.......................................................................... 9-43 Postscript Printing in UNIX ................................................................................................... 9-43 Printer Types Window............................................................................................................ 9-47 Printer Types Block............................................................................................................ 9-48 Printer Drivers Block..........................................................................................................9-48 Printers Window...................................................................................................................... 9-49 Printers Block..................................................................................................................... 9-49 Print Styles Window............................................................................................................... 9-50 Print Styles Block............................................................................................................... 9-51 Layout Block...................................................................................................................... 9-52 Printer Drivers Window.......................................................................................................... 9-53 Printer Drivers Window Fields.......................................................................................... 9-54 Driver Method Region................................................................................................. 9-54 Driver Method Parameters Region.............................................................................. 9-55

10

Oracle Applications Help Setting Oracle Applications Help Profile Options.................................................................10-1 Customizing Oracle Applications Help ................................................................................. 10-1 Downloading and Uploading Help Files .......................................................................... 10-2 Linking Help Files.............................................................................................................. 10-5

viii

Updating the Search Index.................................................................................................10-8 Customizing Help Navigation Trees .................................................................................10-8 The Help Builder User Interface.................................................................................. 10-9 Customizing Help in a Global Environment....................................................................10-16 Using Oracle Tutor................................................................................................................ 10-17

11

Applications DBA Duties Overview of Applications DBA Duties.................................................................................. 11-1 ORACLE Schemas............................................................................................................. 11-1 Registering an ORACLE Schema....................................................................................... 11-2 Initialization Code............................................................................................................. 11-3 Resource Consumer Groups in Oracle Applications............................................................. 11-3 Assigning Resource Consumer Groups............................................................................. 11-4 Hierarchy of Resource Consumer Group Assignments..................................................... 11-4 Oracle Applications Schema Password Change Utility (FNDCPASS).................................. 11-5 FNDCPASS Command and Arguments............................................................................ 11-5 Using the FNDCPASS Utility............................................................................................. 11-7 ORACLE Users Window......................................................................................................... 11-8 ORACLE Users Block....................................................................................................... 11-10 Applications Window........................................................................................................... 11-12 Prerequisites.................................................................................................................... 11-12 Applications Block........................................................................................................... 11-13 Network Test Window.......................................................................................................... 11-15 Administering Folders.......................................................................................................... 11-17

12

Query Optimization in Oracle Applications Oracle Applications and Query Optimization....................................................................... 12-1 Gathering Statistics for the CBO............................................................................................ 12-2 Gather Table Statistics............................................................................................................ 12-2 Backup Table Statistics........................................................................................................... 12-3 Restore Table Statistics........................................................................................................... 12-4 Gather Schema Statistics......................................................................................................... 12-4 Gather Column Statistics........................................................................................................ 12-6 Gather All Column Statistics.................................................................................................. 12-7 Purge FND_STATS History Records...................................................................................... 12-7 FND_STATS Package.............................................................................................................. 12-8 CREATE_STAT_TABLE Procedure................................................................................... 12-8 BACKUP_TABLE_STATS.................................................................................................. 12-8 BACKUP_SCHEMA_STATS Procedure............................................................................ 12-9 RESTORE_SCHEMA_STATS Procedure......................................................................... 12-10

ix

RESTORE_TABLE_STATS Procedure..............................................................................12-10 RESTORE_COLUMN_STATS Procedure........................................................................ 12-11 ENABLE_SCHEMA_MONITORING Procedure............................................................. 12-11 DISABLE_SCHEMA_MONITORING Procedure............................................................ 12-12 GATHER_SCHEMA_STATS Procedure.......................................................................... 12-12 GATHER_INDEX_STATS Procedure.............................................................................. 12-15 GATHER_TABLE_STATS Procedure.............................................................................. 12-16 GATHER_COLUMN_STATS Procedure......................................................................... 12-18 GATHER_ALL_COLUMN_STATS Procedure................................................................ 12-19 ANALYZE_ALL_COLUMNS Procedure.........................................................................12-20 LOAD_XCLUD_STATS Procedure.................................................................................. 12-21 PURGE_STAT_HISTORY Procedure............................................................................... 12-21 CHECK_HISTOGRAM_COLS Procedure....................................................................... 12-21 VERIFY_STATS Procedure.............................................................................................. 12-22

13

Oracle Applications and Oracle Real Application Clusters Introduction to Oracle Real Application Clusters.................................................................. 13-1 Prerequisites............................................................................................................................ 13-1 Migrating to Oracle RAC........................................................................................................ 13-1 Establishing the Oracle E-Business Suite Environment for Oracle RAC.............................. 13-2 Configuring Parallel Concurrent Processing with Oracle RAC.............................................13-2

14

Document Sequences What is a Document Sequence?.............................................................................................. 14-1 Defining a Document Sequence......................................................................................... 14-1 Defining Document Categories.......................................................................................... 14-4 Assigning a Document Sequence....................................................................................... 14-5 Document Numbering vs. Document Entry...................................................................... 14-7 Document Sequences Window............................................................................................... 14-7 Document Sequences Block............................................................................................... 14-8 Document Categories Window............................................................................................. 14-10 Document Categories Block............................................................................................. 14-10 Sequence Assignments Window.......................................................................................... 14-12 Sequence Assignments Block........................................................................................... 14-12 Assignment Region................................................................................................... 14-13 Document Flexfield................................................................................................... 14-14

15

Developer Tools Developer Tools...................................................................................................................... 15-1 Forms Personalization............................................................................................................. 15-1

x

Work Directory........................................................................................................................ 15-2 Web Enabled PL/SQL Window............................................................................................... 15-3 PL/SQL Object Block.......................................................................................................... 15-3

16

Administering Process Navigation Overview of Process Navigation............................................................................................. 16-1 What is Oracle Workflow?................................................................................................. 16-1 What are Seeded Processes?............................................................................................... 16-1 Modifying Your Menu............................................................................................................ 16-1 Creating Process Navigator Processes.....................................................................................16-2 Creating Process Navigator Processes............................................................................... 16-2

17

Administering Globalization Overview of Globalization Support....................................................................................... 17-1 Language Values for User Sessions........................................................................................ 17-1 Language Values for User Sessions using AppsLocalLogin.jsp......................................... 17-1 Language Value from Login External to Oracle Applications........................................... 17-3 Language Values for Oracle Workflow Notifications........................................................ 17-3 Date Formats in NLS Implementations.................................................................................. 17-4 Multilingual External Documents.......................................................................................... 17-4 Translations Window.............................................................................................................. 17-6 Currencies Window................................................................................................................. 17-6 Languages Window................................................................................................................. 17-7 Languages Record.............................................................................................................. 17-7 Natural Languages Window................................................................................................... 17-8 Natural Languages Record................................................................................................ 17-8 Territories Window................................................................................................................. 17-9 Territories Block................................................................................................................. 17-9

A

Oracle Application Server with Oracle E-Business Suite Introduction.............................................................................................................................. A-1 Using Oracle Application Server 10g with Oracle E-Business Suite.......................................A-1

B

Loaders Generic Loader.......................................................................................................................... B-1 Overview............................................................................................................................. B-1 FNDLOAD Executable........................................................................................................ B-3 Configuration File................................................................................................................B-4 Data File.............................................................................................................................. B-7

xi

Oracle Application Object Library Configuration Files.......................................................... B-8 Attachments Setup Data Configuration File............................................................................ B-9 Concurrent Program Configuration File ............................................................................... B-11 Flexfields Setup Data Configuration File.............................................................................. B-14 Flexfield Value Sets ........................................................................................................... B-14 Descriptive Flexfields........................................................................................................ B-14 Key Flexfields ................................................................................................................... B-15 Folders Configuration File ..................................................................................................... B-15 Lookups Configuration File................................................................................................... B-18 Messages Configuration File.................................................................................................. B-19 Profile Options and Profile Values Configuration File......................................................... B-19 Request Groups Configuration File....................................................................................... B-20 Security Information Configuration File............................................................................... B-21 Message Dictionary Generator............................................................................................... B-22 Message Repositories........................................................................................................ B-22 Usage................................................................................................................................. B-23 Generic File Manager Access Utility (FNDGFU)................................................................... B-24 Usage................................................................................................................................. B-24 Example of FNDGFU Upload............................................................................................ B-25 Purging Generic File Manager Data ................................................................................. B-27 Purge Obsolete Generic File Manager Data........................................................................... B-27 Program Parameters.......................................................................................................... B-27

C

Functional Administrator and Functional Developer Tasks Overview of Functional Administrator and Functional Developer Responsibilities............ C-1

D

Oracle Self-Service Web Applications Overview of Oracle Self-Service Web Applications (HTML-based Applications)................ D-1 Oracle Self-Service Web Applications Architecture................................................................ D-1 Web Applications Dictionary Overview.................................................................................. D-5 Setting the Folder Mode...................................................................................................... D-6 Web Applications Dictionary Tasks........................................................................................ D-7 Defining Objects.................................................................................................................. D-7 Assigning Attributes to Objects .......................................................................................... D-8 Defining Attributes............................................................................................................. D-9 Defining Unique Keys....................................................................................................... D-10 Defining Foreign Keys....................................................................................................... D-10 Defining Regions............................................................................................................... D-11 Creating Region Items....................................................................................................... D-12

xii

E

Timezone Support User-Preferred Timezones........................................................................................................ E-1 Time Zone Concepts............................................................................................................ E-1 Upgrade Considerations...................................................................................................... E-2 Implementation Details....................................................................................................... E-3

Index

xiii

Send Us Your Comments Oracle Applications System Administrator's Guide - Configuration, Release 12 Part No. B31453-04

Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document. Your feedback is important, and helps us to best meet your needs as a user of our products. For example: • • • • • •

Are the implementation steps correct and complete? Did you understand the context of the procedures? Did you find any errors in the information? Does the structure of the information help you with your tasks? Do you need different information or graphics? If so, where, and in what format? Are the examples correct? Do you need more examples?

If you find any errors or have any other suggestions for improvement, then please tell us your name, the name of the company who has licensed our products, the title and part number of the documentation and the chapter, section, and page number (if available). Note: Before sending us your comments, you might like to check that you have the latest version of the document and if any concerns are already addressed. To do this, access the new Applications Release Online Documentation CD available on Oracle MetaLink and www.oracle.com. It contains the most current Documentation Library plus all documents revised or released recently. Send your comments to us using the electronic mail address: [email protected] Please give your name, address, electronic mail address, and telephone number (optional). If you need assistance with Oracle software, then please contact your support representative or Oracle Support Services. If you require training or instruction in using Oracle software, then please contact your Oracle local office and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at www.oracle.com.

xv

Preface

Intended Audience Welcome to Release 12 of the Oracle Applications System Administrator's Guide Configuration. This guide assumes you have a working knowledge of the following: •

The principles and customary practices of your business area.

•

Computer desktop application usage and terminology.

If you have never used Oracle Applications, we suggest you attend one or more of the Oracle Applications training classes available through Oracle University. See Related Information Sources on page xviii for more Oracle Applications product information.

TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.

Documentation Accessibility Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all

xvii

of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/ .

Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Structure 1 Introduction 2 Basic Configuration Tasks 3 Oracle Applications Tablespace Model and Migration Utility 4 System Administration Setup Tasks 5 Introduction to Oracle Applications Manager 6 Defining Concurrent Programs and Requests 7 Defining Concurrent Managers 8 Setting Up and Starting Concurrent Managers 9 Printers 10 Oracle Applications Help 11 Applications DBA Duties 12 Query Optimization in Oracle Applications 13 Oracle Applications and Oracle Real Application Clusters 14 Document Sequences 15 Developer Tools 16 Administering Process Navigation 17 Administering Globalization A Oracle Application Server with Oracle E-Business Suite B Loaders C Functional Administrator and Functional Developer Tasks D Oracle Self-Service Web Applications E Timezone Support

Related Information Sources This book is included on the Oracle Applications Documentation Library, which is supplied in the Release 12 Media Pack. You can download soft-copy documentation as PDF files from the Oracle Technology Network at http://otn.oracle.com/documentation, or you can purchase hard-copy documentation from the Oracle Store at

xviii

http://oraclestore.oracle.com. The Oracle Applications Documentation Library Release 12 contains the latest information, including any documents that have changed significantly between releases. If substantial changes to this book are necessary, a revised version will be made available on the "virtual" documentation library on Oracle MetaLink. For a full list of documentation resources for Oracle Applications Release 12, see Oracle Applications Documentation Resources, Release 12, OracleMetaLink Document 394692.1. If this guide refers you to other Oracle Applications documentation, use only the Release 12 versions of those guides. Online Documentation All Oracle Applications documentation is available online (HTML or PDF). •

Online Help - Online help patches (HTML) are available on OracleMetaLink.

•

PDF Documentation - See the Oracle Applications Documentation Library for current PDF documentation for your product with each release. The Oracle Applications Documentation Library is also available on OracleMetaLink and is updated frequently.

•

Oracle Electronic Technical Reference Manual - The Oracle Electronic Technical Reference Manual (eTRM) contains database diagrams and a detailed description of database tables, forms, reports, and programs for each Oracle Applications product. This information helps you convert data from your existing applications and integrate Oracle Applications data with non-Oracle applications, and write custom reports for Oracle Applications products. The Oracle eTRM is available on Oracle MetaLink.

Related Guides You should have the following related books on hand. Depending on the requirements of your particular installation, you may also need additional manuals or guides. Oracle Alert User's Guide This guide explains how to define periodic and event alerts to monitor the status of your Oracle Applications data. Oracle Applications Concepts This book is intended for all those planning to deploy Oracle E-Business Suite Release 12, or contemplating significant changes to a configuration. After describing the Oracle Applications architecture and technology stack, it focuses on strategic topics, giving a broad outline of the actions needed to achieve a particular goal, plus the installation and configuration choices that may be available. Oracle Applications CRM System Administrator's Guide This manual describes how to implement the CRM Technology Foundation (JTT) and use its System Administrator Console.

xix

Oracle Applications Developer's Guide This guide contains the coding standards followed by the Oracle Applications development staff. It describes the Oracle Application Object Library components needed to implement the Oracle Applications user interface described in the Oracle Applications User Interface Standards for Forms-Based Products. It also provides information to help you build your custom Oracle Forms Developer forms so that they integrate with Oracle Applications. Oracle Applications Flexfields Guide This guide provides flexfields planning, setup, and reference information for the Oracle Applications implementation team, as well as for users responsible for the ongoing maintenance of Oracle Applications product data. This guide also provides information on creating custom reports on flexfields data. Oracle Application Framework Personalization Guide This guide covers the design-time and run-time aspects of personalizing applications built with Oracle Application Framework. Oracle Applications Installation Guide: Using Rapid Install This book is intended for use by anyone who is responsible for installing or upgrading Oracle Applications. It provides instructions for running Rapid Install either to carry out a fresh installation of Oracle Applications Release 12, or as part of an upgrade from Release 11i to Release 12. The book also describes the steps needed to install the technology stack components only, for the special situations where this is applicable. Oracle Applications Supportability Guide This manual contains information on Oracle Diagnostics and the Logging Framework for system administrators and custom developers. Oracle Applications System Administrator's Guide Documentation Set This documentation set provides planning and reference information for the Oracle Applications System Administrator. Oracle Applications System Administrator's Guide Configuration contains information on system configuration steps, including defining concurrent programs and managers, enabling Oracle Applications Manager features, and setting up printers and online help. Oracle Applications System Administrator's Guide - Maintenance provides information for frequent tasks such as monitoring your system with Oracle Applications Manager, managing concurrent managers and reports, using diagnostic utilities, managing profile options, and using alerts. Oracle Applications System Administrator's Guide - Security describes User Management, data security, function security, auditing, and security configurations. Oracle Applications User's Guide This guide explains how to navigate, enter data, query, and run reports using the user interface (UI) of Oracle Applications. This guide also includes information on setting user profiles, as well as running and reviewing concurrent requests. Oracle Integration Repository User's Guide

xx

This guide covers the employment of Oracle Integration Repository in researching and deploying business interfaces to produce integrations between applications. Oracle iSetup User Guide This guide describes how to use Oracle iSetup to migrate data between different instances of the Oracle E-Business Suite and generate reports. It also includes configuration information, instance mapping, and seeded templates used for data migration. Oracle Workflow Administrator's Guide This guide explains how to complete the setup steps necessary for any product that includes workflow-enabled processes. It also describes how to manage workflow processes and business events using Oracle Applications Manager, how to monitor the progress of runtime workflow processes, and how to administer notifications sent to workflow users. Oracle Workflow Developer's Guide This guide explains how to define new workflow business processes and customize existing Oracle Applications-embedded workflow processes. It also describes how to define and customize business events and event subscriptions. Oracle Workflow User's Guide This guide describes how users can view and respond to workflow notifications and monitor the progress of their workflow processes. Oracle Workflow API Reference This guide describes the APIs provided for developers and administrators to access Oracle Workflow. Oracle XML Publisher Administration and Developer's Guide Oracle XML Publisher is a template-based reporting solution that merges XML data with templates in RTF or PDF format to produce a variety of outputs to meet a variety of business needs. Outputs include: PDF, HTML, Excel, RTF, and eText (for EDI and EFT transactions). Oracle XML Publisher can be used to generate reports based on existing E-Business Suite report data, or you can use Oracle XML Publisher's data extraction engine to build your own queries. Oracle XML Publisher also provides a robust set of APIs to manage delivery of your reports via e-mail, fax, secure FTP, printer, WebDav, and more. This guide describes how to set up and administer Oracle XML Publisher as well as how to use the Application Programming Interface to build custom solutions.

Integration Repository The Oracle Integration Repository is a compilation of information about the service endpoints exposed by the Oracle E-Business Suite of applications. It provides a complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets users easily discover and deploy the appropriate business service interface for

xxi

integration with any system, application, or business partner. The Oracle Integration Repository is shipped as part of the E-Business Suite. As your instance is patched, the repository is automatically updated with content appropriate for the precise revisions of interfaces in your environment.

Do Not Use Database Tools to Modify Oracle Applications Data Oracle STRONGLY RECOMMENDS that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle Applications data unless otherwise instructed. Oracle provides powerful tools you can use to create, store, change, retrieve, and maintain information in an Oracle database. But if you use Oracle tools such as SQL*Plus to modify Oracle Applications data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data. Because Oracle Applications tables are interrelated, any change you make using an Oracle Applications form can update many tables at once. But when you modify Oracle Applications data using anything other than Oracle Applications, you may change a row in one table without making corresponding changes in related tables. If your tables get out of synchronization with each other, you risk retrieving erroneous information and you risk unpredictable results throughout Oracle Applications. When you use Oracle Applications to modify your data, Oracle Applications automatically checks that your changes are valid. Oracle Applications also keeps track of who changes information. If you enter information into database tables using database tools, you may store invalid information. You also lose the ability to track who has changed your information because SQL*Plus and other database tools do not keep a record of changes.

xxii

1 Introduction

Introduction to This Manual A system administrator is involved in setting up an Oracle Applications installation, controlling access, and ensuring smooth ongoing operation. The tasks involved in these functions are described in the Oracle Applications System Administrator's Documentation Set, in these three volumes. •

Configuration

•

Security

•

Maintenance

This Oracle Applications System Administrator's Guide - Configuration volume describes the tasks involved in setting up and configuring Oracle Applications. These tasks may be done once upon installation, or may also be done as needed, such as setting up a printer or customizing online help files.

Basic Configuration Tasks This chapter describes some of the recommended manual setup steps for Oracle Application Object Library. This chapter can also be used as reference for maintaining an Oracle Applications installation. For complete instructions on setting up a new installation, see Installing Oracle Applications.

Oracle Applications Tablespace Model and the Tablespace Migration Utility The new Oracle Applications Tablespace Model (OATM) has fewer, consolidated tablespaces (twelve, including three system tablespaces: temporary, system and undo segments). Locally managed tablespaces are also supported. The Tablespace Migration Utility is a menu-based Perl program that enables you to estimate future space requirements for the tablespaces and to migrate the Applications

Introduction 1-1

database to OATM.

System Administrator Setup Tasks This chapter describes some common system administrator setup tasks, typically done through the Oracle Applications user interface.

Introduction to Oracle Applications Manager This chapter introduces the Oracle Applications Manager framework. Oracle Applications Manager provides a powerful set of features for managing all aspects of an Oracle Applications system. It provides a comprehensive summary of the system including configuration changes, infrastructure usage, performance, required maintenance activities, potential security issues, and diagnostic test results. It also includes utilities to help you manage Oracle Workflow, patching, configuration utilities, and concurrent processing.

Defining Concurrent Programs and Reports This chapter explains how to define concurrent programs and organize those programs into groups and sets. This chapter also explains how to modify concurrent program definitions, modify the behavior of parameters the programs refer to, and define incompatibility rules among different programs.

Setting Up Concurrent Processing and Concurrent Managers Concurrent managers run processes in the background (concurrent processes) on a server machine. You must set up and start concurrent managers for each product group before you can use the Oracle Applications products.

Setting Up Printers This chapter describes how to set up printers and printing in Oracle Applications.

Oracle Applications Online Help The Oracle Applications online help files can be customized, as explained in this chapter.

Oracle Applications DBA Duties This chapter explains Oracle Applications tasks that require a database administrator to perform explicitly, or assist in by performing prerequisite tasks.

1-2 Oracle Applications System Administrator's Guide - Configuration

Query Optimization in Oracle Applications Oracle Applications uses the cost–based optimizer (CBO) in order to choose the most efficient execution plan for SQL statements. Using this approach, the optimizer determines the most optimal execution plan by costing available access paths and factoring information based on statistics for the schema objects accessed by the SQL statement.

Oracle Applications and Oracle Real Application Clusters This chapter describes the steps required to install Oracle Applications in an environment that uses Oracle Real Application Clusters (Oracle RAC).

Document Sequences This chapter explains how to assign unique numbers to documents created in Oracle Applications.

Administering Process Navigation The Process Navigator provides users with diagrams of business processes as a whole as well as the individual steps in each process. The Process Navigator also provides direct access to the form associated with each step in a process.

Administering Globalization This chapter describes some of the features of internationalization support in Oracle Applications, including language values for user sessions and multilingual external documents.

Developer Tools This chapter provides information on the Forms Personalization and Work Directory features, which can help system administrators and developers create and debug custom forms.

Loaders Oracle Applications provides loader programs to help you move Oracle Applications data between database and text file representations.

Functional Administrator and Functional Developer Tasks Specific system administrator and application developer tasks using HTML-based pages are grouped under the Functional Administrator and Functional Developer

Introduction 1-3

responsibilities.

Oracle Self-Service Web Applications Some features of Oracle Self-Service Web Applications (OSSWA) are supported for backward compatibility and described in an appendix.

Oracle Application Server with Oracle Applications Oracle Application Server offers the industry's fastest, most complete, and integrated J2EE-certified application server. Refer to this section to learn about configuring Oracle Applications with Oracle Application Server.

Other Volumes for System Administrators Listed below are other volumes in the Oracle Applications System Administrator's Documentation Set. Please refer to the Preface for additional related guides. Oracle Applications System Administrator's Guide - Security describes security concepts, setup tasks, and maintenance tasks done in the following areas: •

Oracle User Management

•

Function Security in Oracle Application Object Library

•

Data Security in Oracle Application Object Library

•

User and Data Auditing

•

Oracle Single Sign-On Integration (optional)

Oracle Applications System Administrator's Guide - Maintenance describes tasks you might perform on frequent basis, such as monitoring your system, reviewing concurrent requests, and setting profile options. The following areas are covered in this manual: •

Managing Concurrent Processing and Concurrent Programs

•

Oracle Workflow Manager

•

Monitoring Oracle Applications

•

Diagnostics and Repair

•

Patching and Maintenance

•

User Profiles and Profile Options in Oracle Applications Object Library

•

Using Predefined Alerts


2 Basic Configuration Tasks

Oracle Applications Setup Steps Proper setup is required before a number of Applications features will operate correctly. The following steps are carried out automatically during or after installation: 1.

Run Rapid Install

2.

Test Web listener virtual directories

3.

Test Oracle HTTP Server configuration

4.

Create DBC files

5.

Test Java Servlet setup

6.

Set Web Server profile options

The above is not an inclusive list of the installation and post-installation tasks that may be needed on a particular system. Rapid Install is the installation program. Refer to Installing Oracle Applications: Using Rapid Install for detailed information on running Rapid Install.

Configuring the Login Page for Oracle Applications Oracle Applications uses a configurable login page, which can be tailored to suit the needs of different organizations.

Oracle Applications Login page Users log in to Oracle Applications using a client web browser. From the Oracle Applications Login page, users access the E-Business Suite Home Page, which provides a single point of access to HTML-based applications, forms-based applications, and

Basic Configuration Tasks 2-1

Business Intelligence applications. Users access the Oracle Applications Login page from the following URL: http:///OA_HTML/AppsLogin

For example, http://oraapps1.oracle.com:8000/OA_HTML/AppsLogin

From this URL, you will be redirected to the central login page, "AppsLocalLogin.jsp". Central Login Page

The following features are displayed in the default login page: Username field, Password field, Login button, and the Language Picker (if more than one language is installed). The following user interface features can be turned on or off through the Local Login Mask profile option: •

Hints for username/password

•

* Register URL - this link allows the user to perform self-service registration in User Management

•

* Forgot Password URL - allows the user to have a password reset

•

Language Picker

•

Corporate Policy message

* Oracle User Management must be installed for "Register URL" and "Forgot Password URL" to be enabled. The ICX login page (http://server:port/OA_HTML/US/ICXINDEX.htm) redirects the user to the central login page, "AppsLocalLogin.jsp". If, in a previous release, you


customized the ICX login page previously with a custom logo, you should make a copy of the new ICX login page and replace the existing image with your custom image in the copied file. The location for the company logo is $OA_MEDIA/FNDSSOCORP.gif. Ensure that the image is appropriately size. Also, you should change the text of the message 'FND_ORACLE_LOGO' in Message Dictionary to the appropriate text. The following login URL is supported, but no new features are being added to it: http://server:port/OA_HTML/jtflogin.jsp

If the Oracle Applications instance is Single Sign-On enabled, the servlet directs the user to the Single Sign-On login page. Passwords Note that in previous releases of Oracle Applications, user passwords were treated as case insensitive. Now, Oracle Applications user passwords can optionally be treated as case sensitive, depending on the mode you choose. Case-sensitivity in passwords is controlled by the profile option Password Case Option. Language The current browser language, if it exists in the applications database also, is used for the login page. The user can choose a different language on the login page (if the Language Picker is enabled) and refresh the page to have it appear in that language. If the current browser language does not exist in the Oracle Applications installation, the language set in the site-level setting of the ICX_LANGUAGE profile option is used to render the login page. A user can override the value of the ICX_LANGUAGE profile option for a given session only. Oracle Applications Manager Oracle Applications Manager uses this central login page as well to authenticate users.


Customizing the Oracle Applications Login page Customized Login Page

User interface features can be turned on or off using the profile option Local Login Mask (FND_SSO_LOCAL_LOGIN_MASK): For the Login page to show one of more of these optional attributes, just add the numeric values of all desired attributes and set the value of the profile option to that value. •

Username Hint = 01

•

Password Hint = 02

•

Cancel Button = 04

•

Forgot Password URL = 08

•

Register URL = 16

•

Language Picker = 32

•

Corporate Policy Message = 64

For example to show the Password Hint and the Forgot Password URL only, set the Local Login Mask profile option to 10 (02+08). To show just the Language Picker, set the


value to 32, which is also the default value for the profile option. The values for the Username Hint, Password Hint, Forgot Password URL text, Register URL text, and the Corporate Policy Message, as well as the Copyright text, are stored in Message Dictionary. You can update these messages using the Messages form or HTML page. The table below lists the message names and their default values. Login Page Message Names and Default Values Message Name

Default value

FND_SSO_HINT_USERNAME

(example: michael.james.smith)

FND_SSO_HINT_PASSWORD

(example: 4u99v23)

FND_SSO_FORGOT_PASSWORD

Forgot your password?

FND_SSO_REGISTER_HERE

Register here

FND_SSO_SARBANES_OXLEY_TEXT

Corporate Policy Message

FND_SSO_COPYRIGHT_TEXT

Copyright (c) 2006, Oracle. All rights reserved.

Personalizing the Oracle E-Business Suite Home Page The Oracle E-Business Home Page can be personalized to display the Worklist and to display the Applications Navigator in "Tree" or "Flat" mode. By default, the Applications Navigator is shown in Flat mode. Refer to the Oracle Application Framework Personalization Guide for more information on personalizing Oracle Application Framework pages. Ensure that you have the relevant profile options set appropriately. Follow these steps to use the Tree mode: 1.

Log in to Oracle Applications with the system administrator responsibility.

2.

From the Oracle E-Business Suite Home page, select Personalize Page.

3.

Select Apply in the "Choose Personalization Context" page.

4.

Under "Personalization Structure", expand the following nodes: 'Table Layout: (topTableLayoutContainer)' > 'Row Layout: (tableLayoutRow)' > 'Cell Format: (worklistResponsibilityLeftCell)' > 'Table Layout: Home Contenttable'.


5.

Under the node 'Table Layout: Home Contenttable' > Row Layout: (responsibilityRow), click the Personalize icon.

6.

Change the value for the 'Rendered' property for the column 'Function: Applications Home Page' to 'false'. Select Apply.

7.

Click on the Personalize icon for 'Table Layout: Home Contenttable' > 'Row Layout: (appsNavTreeRow)'.

8.

Change the value for the 'Rendered' property for the column 'Function: Applications Home Page' to 'true'. Select Apply.

9.

Select Return to Application.

Administering Oracle HTTP Server Oracle HTTP Server Powered by Apache provides the communication services within Oracle Application Server. This facilitates deployment of HTML-based applications within a multi-tiered computing environment.

Oracle HTTP Server All incoming client requests to Oracle Internet Application Server (AS) are handled by the Communication Services component of AS. The Oracle HTTP Server, powered by Apache Web Server technology accepts and processes these requests. The Apache technology adopted by Oracle HTTP Server provides an extremely stable, scalable, and extensible platform on which to deploy web-based applications. The modular design of the Apache server allows for extension of the capabilities of the Oracle HTTP Server. In addition to the standard Apache modules (often referred to as modules, or simply mods), a number of Oracle specific modules are provided along with an extension to the functionality of several standard modules. These modules include: •

mod_ssl - This module provides secure listener communications using an Oracle provided encryption mechanism using 128-bit Secure Sockets Layer (SSL). The mod_ossl module replaces mod_ssl. In contrast to the OpenSSL module, mod_ossl is based on the Oracle implementation of SSL, which supports SSL version 3 and uses the Oracle Wallet Manager for Certificate Management. The Apache HTTP Server SSL configuration file, ssl.conf, is located in $INST_TOP/ora/10.1.3/Apache/Apache/conf directory.

•

mod_oc4j - This module routes all servlet requests to the Apache OC4J servlet engine embedded within Oracle HTTP Server. Servlets can be shared across multiple zones.


•

mod_perl - This module forwards Perl requests to the Perl Interpreter. The Perl Interpreter is embedded within the Oracle HTTP Server, removing the necessity to spawn an external interpreter as well as providing a caching mechanism such that modules and scripts need only be loaded or compiled once. Oracle Applications does not currently utilize mod_perl. The Oracle HTTP Server is powered by a standard version of Apache. A number of books have been published describing the operation of the Apache server. To further add to your knowledge of the Apache server, you may wish to consult one of these. Note: Refer to the Oracle HTTP Server documentation for a more

detailed description of the operation and configuration of the Oracle HTTP Server. The information in this section is supplementary to that provided in the Oracle HTTP Server books.

Oracle Applications Installation Guide: Using Rapid Install should be consulted for additional information on directory structures and file locations referred to in this guide.

Apache Configuration Files Apache is configured through directives contained in one or more configuration files. The directives necessary for operating Apache within the Oracle environment will be entered into the configuration files during the install process. It should not be necessary to modify these files unless the system is being reconfigured. Warning: An invalid directive entered into a configuration file will

prevent Apache from starting. An incorrect definition provided to a directive may cause Apache to behave in an unintended fashion.

Location The Apache configuration files are installed as part of the Oracle Applications Rapid Install process. On UNIX, for example, the files will be placed in $INST_TOP/ora/10.1.3/Apache/Apache/conf.

Secure Sockets Layer Configuration Secure Sockets Layer (SSL) allows the Apache listener to encrypt HTML pages and transmit them on the network using the HTTPS protocol for secure transmissions. SSL uses an encrypting method called public key cryptography, where the server provides the client with a public key for encrypting information. The server's private key is required to decrypt this information. The client uses the public key to encrypt and send information to the server, including its own key which identifies it to the


server. In order for the Oracle HTTP Server, powered by Apache, to function in secure mode it is also necessary to utilize certificates which validate the server's identity. These certificates are used to ensure that the owner of a public key is who they say they are. Typically you will want to use a private key with an officially signed certificate, validated by a Certificate Authority (CA). The CA validates the company details, sets expiration dates on the certificates and may place policies on what information is contained within the certificate. A number of CAs exist, and include such authorities as Verisign, RSA, and GTE CyberTrust. To obtain a CA approved certificate it is necessary to generate a certificate request, which includes details of the organization applying as well as the public key to be distributed, this is then sent to the CA, validated and returned. Authorities may also require proof of ownership of the company applying for the certificate, as well as proof of ownership of the domain name specified in the certificate request. It is possible to generate a self-signed certificate that can be used to test SSL operation. Most browsers are configured to accept certificates from a number of recognized authorities. Receiving a certificate from an organization other than one of these will generate a warning, and the user will be prompted to accept or reject this certificate. A self-signed certificate will generate this warning.

Creating a self-signed certificate The SSL module provides two utilities - Oracle Wallet Manager, and the Oracle Wallet Manager Command Line Interface (orapki) - that can be used to create a self-signed certificate for testing purposes. Warning: Self-signed certificates are inherently insecure, and should

not be used in a environment where security is required.

In order to generate a self-signed certificate, perform the steps below using the Oracle Wallet Manager Command Line Interface:

Temporary SSL Environment Setup Follow these steps for the temporary SSL environment setup. 1.

Source your environment 1.

Log on to the application (middle) tier, as the OS user who owns the application tier files.

2.

Source your /.env file to set your APPL_TOP variables.

3.

Navigate to the $INST_TOP/ora/10.1.3 and source the .env file


to set your 10.1.3 ORACLE_HOME variables. When working with wallets and certificates, you must use the 10.1.3 executables. 2.

Create a Wallet 1.

Verify the location of the Web SSL directory: grep s_web_ssl_directory $CONTEXT_FILE

2.

Navigate to this directory, which will have Apache and opmn subdirectories

3.

Change to the Apache subdirectory

4.

Backup any existing wallets (demo certificates are included in Release 12)

5.

Create your new wallet: orapki wallet create -wallet . -auto_login -pwd

"-wallet ." (note the ".") tells orapki that you want to create the wallet in the current directory. You can also specify the full path to any directory where you wish to create a wallet. " -auto_login" tells orapki that you want to create cwallet.sso which is an obfuscated copy of ewallet.p12. With auto login enabled, processes submitted by the OS user who created the wallet will not need to supply the password to access the wallet. 6.

3.

You should now see two wallet files in your directory: cwallet.sso and ewallet.p12.

Add your self-signed certificate to the wallet. 1.

Enter the following command all on one line, substituting the appropriate parameters for your instance: orapki wallet add -wallet . -dn "CN=server.us.oracle.com,OU=Unit,O=Org,L=Orlando,ST=Florida,C=US" -keysize 1024 -self_signed -validity 3650 -pwd welcome1

2.

Your wallet is now ready for use in environments where security is not required (as mentioned in the warning note above, self-certification is by definition not secure).

Configure Apache for SSL Connections using AutoConfig Ensure that the following parameters are correctly set in your Applications context file:


Variable

Non-SSL Value

SSL Value

s_url_protocol

http

https

s_local_url_protocol

http

https

s_webentryurlprotocol

http

https

s_active_webport

Same as s_webport

Same as s_webssl_port

s_help_web_agent

URL constructed with http protocol and s_webport

URL constructed with http protocol and s_webport (same as non-SSL)

s_login_page

URL constructed with http protocol and s_webport

URL constructed with https protocol and s_webssl_port

Run AutoConfig, either through the Oracle Applications Manager interface, or by using the adautocfg.sh script in the application tier $ADMIN_SCRIPTS_HOME directory. Note: For more details, see OracleMetaLink Note 387859.1, Using

AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12.

Test Startup of Apache and Oracle Applications Sign-On Restart the application tier Apache services using the adapcctl.sh script in the $ADMIN_SCRIPTS_HOME directory. Ensure that Apache can startup successfully, and that you successfully get an SSL connection to the default Apache banner screen using https:/:, where is the fully qualified name of the machine running Apache, and is the SSL port number defined in ssl.conf. Once you have signed on to Oracle Applications, select a responsibility and process that will launch a Forms-based application. For example, System Administrator responsibility and the Define User process. Note: For further details of using SSL, see OracleMetaLink Note

376700.1, Enabling SSL with Oracle Application Server 10g and E-Business Suite Release 12, and Note 376694.1, Using the Oracle Wallet Manager Command Line Interface with Oracle E-Business Suite Release 12.


AdminAppServer Utility Important: The following details are provided for reference only. You

should not need to carry out manual maintenance on dbc files, as they are managed by AutoConfig, which runs AdminAppServer automatically. See "Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12", Note 387859.1, on OracleMetaLink.

Because Release 12 is deployed in a multi-tier configuration, the security model includes authentication of application servers to the database servers they access. When this layer of security is activated, the application server passes server IDs (similar to passwords) to the database server. If the database server recognizes the server ID, it grants access to the database. The server IDs are created using a Java script called AdminAppServer. The application server security system is by default not activated; if it you must activate it after installation, if required. The application servers are not assigned server IDs and the database servers do not check for server IDs.

Using the AdminAppServer Utility The Java script AdminAppServer is used to create .dbc files and to enable or disable application server security. Prior to running AdminAppServer you must ensure that: •

JDBC classes are in the CLASSPATH and LD_LIBRARY_PATH

•

$JAVA_TOP is in the classpath

For UNIX platforms, the script is run as: java oracle.apps.fnd.security.AdminAppServer [parameters]

For Windows platforms, the script is run as: jre -classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer [parameters]

The first parameter must be the connection string followed by the command string, for example: apps/apps@dbname ADD

The following commands are supported: •

ADD - create a new .dbc file

•

UPDATE - update an existing .dbc file


•

DELETE - delete an existing .dbc file

•

STATUS - check the serverID status for a database

•

AUTHENTICATION - toggle authentication mode

Additional parameters depend on the operation. These include: •

DBC - The .dbc file to modified, or used to connect to the database. Used with UPDATE, DELETE, STATUS, AND AUTHENTICATION.

•

SECURE_PATH - Used with ADD. This parameter specifies in which directory the .dbc file should be created, and defaults to the current directory if not provided. This parameter should always point to $FND_TOP/secure.

•

DB_HOST - Required. The host machine of database.

•

DB_PORT - Required. The port of database. The default is 1521.

•

DB_NAME - For thin drivers. The database SID.

•

APPS_JDBC_DRIVER_TYPE - THICK or THIN. This parameter must be set to THIN.

•

GUEST_USER_PWD - Any valid applications user. This parameter defaults to the value of GUEST_USER_PWD profile if not provided. If passed with no arguments to an UPDATE call, it will refresh with the value from database.

•

GWYUID - For thick drivers.

•

FNDNAM - For thick drivers.

•

TWO_TASK - For thick drivers. Name of database.

•

WALLET_PWD - Used with the TCF Socket Server in SSL mode.

•

SERVER_ADDRESS - Used with authentication.

•

SERVER_DESCRIPTION - Used with authentication.

•

FND_MAX_JDBC_CONNECTIONS - The maximum number of open connections in the JDBC connection cache. This number is dependent on the amount of memory available, number of processes specified in the init.ora file of the database and the per-processor file descriptor limit.

•

FND_IN_USE_CONNECTION_TIMEOUT - The maximum number of seconds a connection can be in use. In order to avoid connections being locked up for too long, the connection cache uses this parameter to forcibly close connections that


have been locked for longer than this specified limit. If this parameter is unspecified, connections in use will not be cleaned up. This should be set to a number larger than the time taken to complete the largest transaction. •

FND_UNUSED_CONNECTION_TIMEOUT - The maximum number of seconds an unused connection can remain in the cache. The connection cache will close and remove from the cache any connection that has been idle for longer than this specified limit. Important: The following parameters are required:

APPS_JDBC_DRIVER_TYPE (must be set to THIN), DB_HOST, and DB_PORT.

Administering .dbc Files The .dbc file is contained on the web/applications server and holds information used by the database for authentication. The web/application server passes the information from the .dbc file, as well as login information, to the database server to authenticate the user. The authentication process is handled by the standard applications security feature. The .dbc files required by the application server security system are not part of the delivered product and must be created after installation. The Java utility AdminAppServer is used to create the .dbc files. Prior to running AdminAppServer you must ensure that: •

JDBC classes are in the CLASSPATH and LD_LIBRARY_PATH

•

$JAVA_TOP is in the classpath

Creating a .dbc file Use the AdminAppServer utility to create a .dbc file for the application server to access the database server. In addition to creating the .dbc file this utility registers the application server with the database for the Applications Server Security feature. To access additional database servers from the same application server, you must rerun the AdminAppServer utility for each additional database. You must run the AdminAppServer utility each time you create a .dbc file, and each .dbc file only allows access to one database. To create a .dbc file for an application server: 1.

You must set the username/password value for the GUEST_USER_PWD parameter. Create a valid username ("guest" for example) in Oracle Applications. Then use the username/password combination as the value for GUEST_USER_PWD. The syntax is illustrated in the following example:


GUEST_USER_PWD=guest/guest

Oracle recommends that you do not assign any responsibilities for this user. 2.

From the command line, enter the appropriate command for your platform: For UNIX platforms: java oracle.apps.fnd.security.AdminAppServer apps/apps@dbname \ ADD DB_HOST=database_host_name DB_PORT=database_port \ DB_NAME=database_sid \ [env_name=env_value] SECURE_PATH=$FND_TOP/secure

For Windows platforms: jre -classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps@dbname \ ADD DB_HOST=database_host_name DB_PORT=database_port \ DB_NAME=database_sid \ [env_name=env_value] SECURE_PATH=$FND_TOP/secure

GWYUID, FNDNAM, and GUEST_USER_PWD will be defaulted if not provided explicitly. dbc files should be located in $FND_TOP/secure, so SECURE_PATH should always be set to that, or this should be run directly out of of the $FND_TOP/secure area.

Updating a .dbc file (or Server ID) When updating the .dbc file you can change as many parameters as you want, including the server ID, but you must enter at least one. Settings that you do not update retain their value.

To update a .dbc file or server ID: Enter from the command line: UNIX java oracle.apps.fnd.security.AdminAppServer apps/apps@dbname \ UPDATE DBC=$FND_TOP/secure/file.dbc APPL_SERVER_ID \ [env_name=env_value] Windows jre -classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps@dbname \ UPDATE DBC=$FND_TOP/secure/file.dbc APPL_SERVER_ID \ [env_name=env_value] If APPL_SERVER_ID is not passed, AdminAppServer will attempt to synchronize the current server ID value in the .dbc file and the database, generating a new one if neither contains a value at all. Passing in APPL_SERVER_ID by itself will force a brand new application server ID to be created always, overwriting any existing one.

Deleting a .dbc file To delete a .dbc file, enter on the command line: UNIX java oracle.apps.fnd.security.AdminAppServer apps/apps@dbname \ DELETE


DBC=$FND_TOP/secure/file.dbc Windows jre -classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps@dbname \ DELETE DBC=$FND_TOP/secure/file.dbc This deletes the .dbc file and disallows access to the indicated database if Server Security is active.

Troubleshooting The following are possible problems you may encounter and suggested solutions. •

Database connection failed. Check to see if your JDBC environment is correct. See: AdminAppServer Utility, page 2-11.

•

File I/O error while adding the server. Check to see if the path you supplied as SECURE_PATH exists and that you have write permissions on it.

•

Unable to read environment file. A value for SECURE_PATH may not have been specified. If a value is not specified, the AdminAppServer utility assumes you are running from JAVA_TOP and looks for the file $JAVA_TOP/oracle/apps/env.html to find the value of FND_TOP. Retry the command specifying the value of SECURE_PATH.

•

Database error: Unique constraint violated. There can be only one entry for each application server per database. If you do not specify the value for SERVER_ADDRESS, the AdminAppServer utility will default the IP address of the machine from which you are running the command. To resolve this issue, run the STATUS command of AdminAppServer to ensure you are not trying to create a duplicate entry. Delete the old entry if you want to replace it. Retry, supplying the correct value for SERVER_ADDRESS.

Administering Server Security Oracle Applications is deployed in a multi-tier configuration with one database server and many possible middle-tier application servers. The application servers include Apache JSP/Servlet, Forms, Discoverer and also some client programs such as Application Desktop Integrator. Any program which makes a SQL*Net connection to the Oracle Applications database needs to be trusted at some level. Oracle Applications uses the Server Security feature to ensure that such SQL*Net connections are coming from trusted machines and/or trusted programs. The Server Security feature of Application Object Library supports authentication of


application server machines and code modules in order to access the database. When Server Security is activated, application servers are required to supply server IDs (like passwords) and/or code IDs to access a database server. Server IDs identify the machine from which the connection is originating. Code IDs identify the module and patch level from which the connection is originating. Code IDs are included in applications code by development. The database server can be set to allow access only from specific machines and/or by code at a desired patch level. The application server security feature is not initially activated. You should activate it by using the commands described in this section. Application Server Security can be in one of three states: •

OFF - Server security is not checked. Any application server machine can access the database. Code IDs are also not checked. Use this option on test systems or if you have full control over the software on all machines which can physically access your database.

•

ON - Some level of trust is required to access the database. Either the application server must be registered with the database or the code must pass a module and version ID known to be trusted. Use this option only if you wish to maintain compatibility with application servers that you cannot yet patch to the code level required for best security.

•

SECURE - Full trust is required for access to the database. Only registered application server machines may connect to the database, and only trusted code modules may connect to the database. This is the default setting for Release 12.

Server Security Status You can check the Server Security status for a particular database using the STATUS command in the AdminAppServer utility, and providing the dbc file corresponding to that database. The STATUS command will display whether server security is turned on and whether the server ID in the dbc file is currently valid. To check the Server Security status for a database: On UNIX: java oracle.apps.fnd.security.AdminAppServer apps/apps \ STATUS DBC=

On Windows: jre –classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps \ STATUS DBC=

Important: Check the Server Security status of your databases before

you activate server security and ensure that all desired application servers have been registered.


Adding, Updating, or Deleting Server IDs Application servers can be registered as trusted machines with a database server. This works by generating a large random ID number and storing that in both the application server and the database. When the application server attempts to connect to the database it will supply its server ID and the database will verify that it matches a trusted machine. The server ID is stored as a parameter in the DBC file for each application server. It can also be defined as an environment variable. The AdminAppServer utility is used to generate server IDs and then register them with a database server.

To add a server ID Server ID values are generated by the AdminAppServer utility, and therefore cannot be supplied on the command line. They will be added to the database automatically when the AdminAppServer is used to create a dbc file. On UNIX: java oracle.apps.fnd.security.AdminAppServer apps/apps \ ADD [SECURE_PATH=$FND_TOP/secure] \ DB_HOST= \ DB_PORT= \ DB_NAME=

On Windows: jre –classpath %CLASSPATH \ oracle.apps.fnd.security.AdminAppServer apps/apps \ ADD [SECURE_PATH=$FND_TOP/secure] \ DB_HOST= \ DB_PORT= \ DB_NAME=

To update a server ID You can update an application server's server ID at any time. From the command line enter: On UNIX: java oracle.apps.fnd.security.AdminAppServer apps/apps \ UPDATE DBC= APPL_SERVER_ID

On Windows: jre –classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps \ UPDATE DBC=

By providing the APPL_SERVER_ID argument, you will force a new server ID to be generated and added to your DBC file. If the APPL_SERVER_ID argument is not provided, AdminAppServer will take care of syncing up the server ID's of your dbc file and your database automatically, if required.


To delete a server ID Server IDs can be deleted. This must be done using the AdminAppServer utility as follows: On UNIX: java oracle.apps.fnd.security.AdminAppServer apps/apps \ DELETE DBC= APPL_SERVER_ID

On Windows: jre –classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps \ DELETE DBC=

Activating Server Security You can turn the server security feature to OFF, ON, or SECURE mode using the AdminAppServer utility. When you turn off server security, you will not change or delete your server IDs. You can re-enable server security without having to recreate server IDs for existing registered application servers.

On UNIX: To activate basic server security on UNIX, enter on the command line: java oracle.apps.fnd.security.AdminAppServer apps/apps \ AUTHENTICATION ON DBC=

To activate full server security (SECURE mode) on UNIX, enter: java oracle.apps.fnd.security.AdminAppServer apps/apps \ AUTHENTICATION SECURE DBC=

To deactivate server security on UNIX, enter: java oracle.apps.fnd.security.AdminAppServer apps/apps \ AUTHENTICATION OFF DBC=

On Windows: jre -classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps \ AUTHENTICATION ON DBC=

To activate full server security (SECURE mode), from the command line, enter: jre -classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps \ AUTHENTICATION SECURE DBC=

To deactivate server security, from the command line, enter: jre -classpath %CLASSPATH% \ oracle.apps.fnd.security.AdminAppServer apps/apps \ AUTHENTICATION OFF DBC=


Restricting Access to Responsibilities Based on User's Web Server Oracle Applications has the capability to restrict access to a responsibility based upon the Web server from which the user logs in. This capability is provided by tagging Web servers with a "server trust level." The server trust level indicates the level of trust associated with the Web server. Currently, three trust levels are supported: 1) administrative, 2) normal, and 3) external. Web servers marked as "administrative" are typically those used exclusively by system administrators. These servers are considered secure and may contain highly sensitive information. Servers marked as "normal" are those used by employees within a company's firewall. Users logging in from normal servers have access to only a limited set of responsibilities. Lastly, servers marked as "external" are those used by customers or employees outside of a company's firewall. These servers have access to an even smaller set of responsibilities.

Setting the Server Trust Level for a Server To assign a trust level to a Web server, set the Node Trust Level profile option. The Node Trust Level profile option uses the Server profile hierarchy type, meaning that the value of the profile depends on the particular middle-tier server accessing the profile. This profile option can be set to either 1, 2, or 3, with the following meanings. •

1 - Administrative

•

2 - Normal

•

3 - External

To avoid having to set the Node Trust Level profile option for every Web server, you may wish to set it to a default level of trust at the site level, such as level 1. If no value is set for the Node Trust Level profile option for a Web server, the Web server is assumed to have a trust level of 1 (Administrative).

Restricting Access to a Responsibility To restrict access to a responsibility, set the security-based Responsibility Trust Level (internal name APPL_SERVER_TRUST_LEVEL) profile option value for that responsibility to be the number 1, 2, or 3. Setting this profile value ensures that only Web servers with the same or greater privileged trust level may access that responsibility. Like the Node Trust Level profile option, the default value for the Responsibility Trust Level is 1. When fetching the list of valid responsibilities for a user, Oracle Applications checks to find only responsibilities with a Responsibility Trust Level value greater than or equal to the Web server's Node Trust Level. In this way, a responsibility with Responsibility


Trust Level set to 1 would only be available if the Web server has the Node Trust Level set to 1 as well. A responsibility with Responsibility Trust Level set to 2 would only be available if the Web server has Node Trust Level set to either 1 or 2.

Application Object Library AOL/J Setup Test Suite The AOL/J Setup Test suite consists of Java Server Pages (JSPs) and can be used to diagnose AOL/J setup issues. These JSPs exercise various features of AOL/J and provide feedback on the results. The test suite is accessed from the URL: http://:/OA_HTML/jsp/fnd/aoljtest.jsp

where host_name and port_number correspond to the host name and port number of your instance's Apache listener. The host name and port number values are normally found in the APPS_SERVLET_AGENT profile option. When you access the test suite, you will be asked to provide login information for your instance: •

Applications Schema Name

•

Applications Schema Password

•

TWO_TASK

•

Host Name

•

Port Number

The following is a list of functions and tests you can run with your instance. •

Connection Test •

Locate DBC File

•

Verify DBC Settings

•

AOL/J Connection Test

•

Virtual Directory settings

•

APPS_WEB_AGENT •

Virtual Directory Settings

•

FND_WEB.PING

•

Custom Authentication

•

GFM (Generic File Manager)


•

•

APPS_SERVLET_AGENT •


•

Servlet Ping

•

Jsp Ping

APPS_FRAMEWORK_AGENT •


•

Servlet Ping

•

Jsp Ping

•

Cabo Setup Tests

•

X Server Accessibility

•

OA Framework System Info

•

Versions for Loaded Classes

•

HELP_WEB_AGENT

•

TCF •

•

•

Test Connection

Tool Launcher Profile Settings •

ICX_FORMS_LAUNCHER

•

ICX_REPORT_LAUNCHER

•

ICX_DISCOVERER_LAUNCHER

Application Login •

Login Page

•

Show Responsibilities

•

Show Session Properties


Using Oracle Application Framework Oracle Application Framework is the Oracle Applications development and deployment platform. It is a 100% Java and XML, middle-tier application framework and services for the rapid development and deployment of HTML based applications. For information on Oracle Application Framework, see "Oracle Application Framework Documentation Resources, Release 12", Note 391554.1 on OracleMetaLink.

AutoConfig and Oracle Applications Manager Oracle Applications Manager (OAM) provides access to the AutoConfig configuration management tool via the AutoConfig tab in the Site Manager screen. Previous configuration settings can easily be compared with the current settings, allowing changed settings to be identified and rolled back as necessary. The configuration editor also helps you add custom variables to the context files, to allow AutoConfig and AutoPatch to preserve your system configuration customizations. For more information on AutoConfig, see: "Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12", Note 387859.1, on Oracle MetaLink. For more information on Oracle Applications Manager, see: Introduction to Oracle Applications Manager, page 5-1. From the Oracle Applications Manager Site Map, AutoConfig is on the Administration tab under the System Configuration heading. Click on the AutoConfig link to go to the tool's home page. From the AutoConfig home page, you can view details of a context file by clicking Show. For example, you can see Version, Path, Creation Date. Last Updated By, Status (for example, Write succeeded), and Comments. You can select a context file and choose Edit Parameters. This is the only supported way to modify parameters that AutoConfig maintains: if you edit any context files manually, they will be overwritten the next time AutoConfig is run. Under Edit Parameters, choosing the Local tab will open a screen that shows environment-related details, including local host machine name, virtual hostname (used to connect), local domain name, and platform type. You can select a context file and click on Show History, to see details of any previous configurations. The Custom tab under Edit Parameters allows you to add a new context variable (not maintained by AutoConfig) to the context file. This is the only supported way to add customizations.


Related Topics Configuration Overview, page 5-8


3 Oracle Applications Tablespace Model and Migration Utility

Introduction to Oracle Applications Tablespace Model The Oracle Applications Tablespace Model (OATM) uses twelve consolidated tablespaces (including three system tablespaces: temporary, system and undo segments) and provides support for locally managed tablespaces. OATM was introduced in Release 11i.10. In prior 11i releases of the E-Business Suite, each product was allocated two tablespaces, one for data and one for indexes. The Migration Utility is a menu-based PERL program and a series of sizing estimate reports that enables conversion of E-Business Suite applications schemas either in a single comprehensive migration or a phased, schema-by-schema migration. In general Oracle recommends performing a single comprehensive migration, however this requires a sufficient amount of down time and disk space. Oracle does not support partial migration of tablespaces. You must still migrate all schemas when performing a phased schema-by-schema migration. With OATM, each database object is mapped to a tablespace based on its Input/Output characteristics, which include object size, life span, access methods and locking granularity. This model allows for easier maintenance, and reduced space usage for the E-Business Suite. Another configuration supported with Locally Managed Tablespaces, User Extent Management, is only relevant when Dictionary Tablespaces have been migrated to Locally Managed Tablespaces. Because migration to OATM is performed at the object level and not at the tablespace level, User Extent Management is not relevant. The default recommended configuration in OATM is Uniform Extent Management.

Advantages of Migrating to OATM Migrating database objects to OATM provides the following benefits:

Oracle Applications Tablespace Model and Migration Utility 3-1

•

Fewer and more consolidated tablespaces

•

Locally Managed Tablespaces

•

Accounts for the I/O characteristics of an object

•

Reclaims space after migration

•

Real Application Cluster (RAC) Support

Fewer and More Consolidated Tablespaces OATM contains twelve locally managed tablespaces for all products, including temporary tablespace, system tablespace, and undo segments. The previous tablespace model contained two tablespaces for each Oracle product resulting in hundreds of tablespaces.

Locally Managed Tablespaces This model provides support for either Uniform or Auto-allocate extent management, available with Locally Managed Tablespaces. Locally Managed Tablespaces have benefits over Dictionary Tablespaces in the previous model and allow for the sizes of extents to be determined automatically by the system (Auto-allocate). Alternatively, all extents can have the same size (Uniform) in and override object storage options. OATM implements Automatic segment-space management, a simpler and more efficient way of managing space within a segment. It completely eliminates any need to specify and tune the PCTUSED, FREELISTS, and FREELISTS GROUPS storage parameters for schema objects created in the tablespace. Automatic segment-space management delivers better space utilization than manual segment-space management, and is self tuning because it scales by increasing the number of users, as well as instances. For a Real Application Clusters environment, automatic segment-space management enables dynamic affinity of space to instances, which avoids the hard partitioning of space inherent with using free list groups.

Uniform Extent Size The value for uniform extent size should be carefully selected based on system requirements. For production environments and large tablespaces like transaction tables, transaction indexes, interfaces, summaries, archives, and media, a uniform extent size of 1MB or 10MB (with caution) should be considered. Choosing an extent size that is too small can result in frequent extensions and performance degradation of the system. The Release 12 Rapid Install production database is delivered out-of-the-box with locally managed tablespaces with uniform extent sizes of 128Kb. If this size is not the best match for the characteristics of your system, you can follow subsequent


re-migration steps to create new tablespaces with the desired uniform extent size and migrate objects to those new tablespaces. The OATM Migration Utility supports all possible configurations of locally managed tablespaces. You have the flexibility to override the default recommendation of uniform extent size with Auto-Allocate extent management as per your requirements. Uniform extent size is also configurable. Note: The Oracle database server does not as yet support altering the

extent management type or uniform extent size after the locally managed tablespaces have been created. Therefore, if the originally used extent management type or uniform extent size needs to be modified, re-creation of the tablespaces and re-migration of objects is the only available option.

Re-migration steps Use the customization option to change names of existing OATM tablespaces as listed in the following table: Tablespace Type

Old Tablespace Name

New Tablespace Name

Transaction Tables

APPS_TS_TX_DATA

APPS_TS_TX_DATA_1MB

Transaction Indexes

APPS_TS_TX_IDX

APPS_TS_TX_IDX_1MB

Reference

APPS_TS_SEED

Interface

APPS_TS_INTERFACE

APPS_TS_INTERFACE_1MB

Summary

APPS_TS_SUMMARY

APPS_TS_SUMMARY_1MB

Nologging

APPS_TS_NOLOGGING

Advanced Queuing/AQ

APPS_TS_QUEUES

Media

APPS_TS_MEDIA

APPS_TS_MEDIA_1MB

Archive

APPS_TS_ARCHIVE

APPS_TS_ARCHIVE_1MB

Please note that for the types of tablespaces for which you do not wish to modify the uniform extent size, you should not change the tablespace name and objects will remain in the respective tablespace with the originally selected extent size and no attempt will be made to migrate them. Sizes of those tablespaces should be ignored in the sizing report and 'alter tablespace' statements removed from the 'create tablespace' script


before the script is run. From the main menu, select option 7. Run Customization Steps: Customization 1.

Register new tablespace - tablespace type

2.

Change name of the existing tablespace

3.

Register object classification

4.

Change object classification

Please select "2. Change name of existing tablespace". Enter tablespace type: TRANSACTION_TABLES Enter new tablespace name: APPS_TS_TX_DATA_1MB Tablespace name for TRANSACTION_TABLES changed to APPS_TS_TX_DATA_1MB. Do you want to continue changing tablespace names?[Y]: Enter tablespace type: TRANSACTION_INDEXES Enter new tablespace name: APPS_TS_TX_IDX_1MB ...

The same steps should be performed for all tablespace types for which you want to change the uniform extent size. When the customizations are complete, please run the following steps as described in the chapter Oracle Applications Tablespace Migration Utility, page 3-9. •

Run the sizing process and create new tablespaces.

•

Run migration command generation.

•

Complete post-migration steps and drop old tablespaces that have no remaining segments.

I/O Characteristics of an Object OATM takes into account the following object I/O characteristics of an object: •

size

•

life span

•

access methods

•

locking granularity


Automatic Segment-space Management Automatic segment-space management is a simpler and more efficient way of managing space within a segment. It completely eliminates any need to specify and tune the PCTUSED, FREELISTS, and FREELISTS GROUPS storage parameters for schema objects created in the tablespace. Automatic segment-space management delivers better space utilization than manual segment-space management, and is self tuning because it scales with the increasing number of users and instances. For a Real Application Cluster (RAC) environment, automatic segment-space management enables dynamic affinity of space to instances, which avoids the hard partitioning of space inherent with using free list groups.

Reclaims Space After Migration The tablespace migration utility migrates objects from the existing dictionary-managed tablespaces to locally managed tablespaces with automatic segment management and either uniform or Auto-allocate extent management. As a result, space is better utilized and less wasted. Migration of table and index segments from one tablespace to another also reclaims unused space, especially for indexes that are fragmented when the index columns are inserted, updated or deleted frequently.

Real Application Cluster (RAC) Support OATM facilitates Real Application Cluster (RAC) support because of its reduced number of tablespaces. RAC is an Oracle database feature that harnesses the processing power of multiple interconnected computers where all active instances can concurrently execute transactions against a shared database disk system. The new tablespace model is critical when implementing RAC on Linux, where currently there is a limitation of 255 raw devices.

Additional Benefits OATM provides the following additional benefits: •

Facilitates administration and configuration ease

•

Increases block-packing to reduce the overall number of buffer gets.

OATM Tablespaces The advantages of OATM's product tablespaces are best understood in terms of the tablespace model that preceded it. This model contained two tablespaces for each Oracle Applications product. One tablespace was allocated for tables and one for indexes. In this model, the standard naming convention for tablespaces contained the product's Oracle schema name with a suffix of either "D" for "Data" tablespaces or "X"


for "Index" tablespaces. For example, the tablespaces APD and APX were the default tablespaces for Oracle Payables tables and indexes, respectively. In contrast to the previous tablespace model, OATM contains nine default tablespaces for applications objects in addition to Undo, Temp and System database tablespaces. Indexes on transaction tables are held in a separate tablespace dedicated for transaction table indexes whereas all other indexes are held in the same tablespace as the parent/base table. All Oracle Applications product schemas now have a default tablespace set to point to the TRANSACTION_TABLES tablespace type for data objects and the TRANSACTION_INDEXES tablespace type for index objects. The Oracle Applications Tablespace Model uses Locally Managed Tablespaces and supports either Uniform or Autoallocate extent management. Another configuration supported with Locally Managed Tablespaces - User Extent Management, is of relevance only in case of Dictionary Tablespaces that have been migrated over to Locally Managed Tablespaces. Because migration to OATM is performed at the object level and not at the tablespace level, User Extent Management is not relevant. The default recommended configuration in OATM is Uniform Extent Management. The migration utility recommends the default of 128k uniform extents which can be changed to suit the customer database. Tablespace types are listed in the following table: Tablespace Types Tablespace Type

Tablespace Name

Content

Transaction Tables

APPS_TS_TX_DATA

Tables that contain transactional data.

Transaction Indexes

APPS_TS_TX_IDX

Indexes on transaction tables.

Reference

APPS_TS_SEED

Reference and setup data and indexes.

Interface

APPS_TS_INTERFACE

Interface and temporary data and indexes.

Summary

APPS_TS_SUMMARY

Summary management objects, such as materialized views, fact tables, and other objects that record summary information.

Nologging

APPS_TS_NOLOGGING

Materialized views not used for summary management and temporary objects.


Tablespace Type

Tablespace Name

Content

Advanced Queuing/AQ

APPS_TS_QUEUES

Advanced Queuing and dependent tables and indexes.

Media

APPS_TS_MEDIA

Multimedia objects, such as text, video, sound, graphics, and spatial data.

Archive

APPS_TS_ARCHIVE

Tables that contain archived purge-related data.

Undo

UNDO

Automatic Undo Management (AUM) tablespace. UNDO segments are identical to ROLLBACK segments when AUM is enabled.

Temp

TEMP

Temporary tablespace for global temporary table, sorts, and hash joins.

System

SYSTEM

System tablespace used by the Oracle Database

Tablespace Classification OATM relies on specific explicit and implicit classification rules that are determined based on storage considerations for the object type in question. The Oracle Tablespace Migration Utility migrates objects based on these rules. The following table contains rules for implicit classifications that are applied in OATM, based on object types. Objects that do not have an implicit classification rule or an explicit object classification are migrated to the default tablespaces of the schema in which they reside. Explicit Classification Rules Explicit object classifications are seeded by Oracle based on the I/O characteristics of the object. Implicit Classification Rules The following table contains implicit classification rules for the Oracle Applications Tablespace Migration Utility.


Implicit Classification Rules Object Type

Tablespace_Type

AQ Tables

AQ

IOTs (Index Organized Tables)

Transaction_Tables

Materialized Views

Summary

Materialized View Logs

Summary

All other Indexes

Same Tablespace type as the table

Domain Indexes

Transaction_Indexes

Indexes on Transaction Tables

Transaction_Indexes

Customizations and Extensions The Oracle Applications Tablespace Migration Utility is primarily designed to migrate tables, indexes, materialized views, materialized view logs and other database objects that are owned by standard Oracle Applications schemas from their existing tablespace model to OATM. Custom or third party schemas can also be migrated using the Oracle Tablespace Migration Utility, customer preferred methods, or a database management tool such as the Oracle Enterprise Manager (OEM). Custom objects in standard Oracle application product schemas are migrated by default. The Oracle Tablespace Migration Utility enables the following customizations: •

Changing tablespace names

•

Registering custom tablespace types

•

Registering custom object-tablespace classifications

•

Changing existing object classifications.

Migrating Custom or Third Party schemas Login to the Forms-based version of Oracle Applications with the System Administrator Responsibility. Navigate to Security -> ORACLE -> Register and register the external schema(s) if they are not already registered. Set Privilege to "Enabled".


Preventing Migration of Specific Schemas In some cases, you may not want to migrate some of your schemas such as non-Oracle schemas that are registered with Oracle Applications. To accomplish this, you must disable those schemas by accessing System Administrator responsibility -> Security -> ORACLE -> Register and then selecting either "External" or "Disabled" for the schema in question. Conversely, if you want to flag specific schemas for migration, you can enable them by accessing System Administrator responsibility -> Security -> ORACLE -> Register and then selecting "Enabled".

Introduction to the Oracle Applications Tablespace Migration Utility The Tablespace Migration Utility is a menu-based PERL program that enables you to estimate future space requirement for the tablespaces and to migrate the Applications database to OATM. Log files are available for user viewing and are created in the working directory from which your run the PERL program. The Log file name and location are displayed once you choose the required option. The Tablespace Migration Utility enables you to perform either a single, comprehensive migration of all schemas or a phased, schema-by-schema migration. To minimize downtime, Oracle recommends that you perform the single comprehensive migration of all schemas, however this requires a sufficient amount of down time and available disk space. If , you do not have sufficient down time or disk space to accomplish this, then you can run the phased schema-by-schema migration. Once you migrate an object from its existing tablespace to OATM, this process cannot be reversed. Oracle does not support the rollback of schemas migrated to OATM in a phased schema-by-schema migration. The only method for achieving this result is to recover the migrated schemas from a backup. Note: Once you initiate migration of one or more schemas to OATM it

is not possible to perform additional migrations from a different PERL menu. You must wait until one migration is completed before beginning another.

Planning for Migration Sizing Requirements Whenever possible, Oracle recommends the following: •

perform a single comprehensive migration of all schemas instead of performing a phased schema-by-schema migration.

•

perform test runs to determine the amount of down time required to perform a


comprehensive migration of all schemas •

secure twice as much disk space as your existing space to perform the a single comprehensive migration of all schemas, and to be operational using the new model.

Setting Up the Tablespace Migration Utility Setting up the Tablespace Migration Utility When you first install the Tablespace Migration Utility, it does the following: •

Copies the PERL menu script, fndtsmig.pl, to the FND_TOP/bin directory.

•

Copies the SQL scripts for the Tablespace Migration utility to FND_TOP/patch/120/sql directory.

•

Copies the PLS files for the Tablespace Migration utility to the FND_TOP/patch/120/sql directory and creates packages in the database.

•

Compiles the Java files into the packages oracle.apps.fnd.tsmig, in FND_TOP/java/apps.zip file.

•

Creates and seeds the following tables: •

FND_TABLESPACES

•

FND_OBJECT_TABLESPACES

•

FND_TS_SIZING

•

FND_TS_MIG_CMDS

•

FND_TS_MIG_RULES

•

FND_TS_PROD_INSTS

Invoking the Tablespace Migration Utility Main Menu Invoke the Tablespace Migration Utility main menu by performing the following: 1.

Run the fndtsmig.pl PERL script: perl $FND_TOP/bin/fndtsmig.pl.

2.

Provide the following information when prompted to access the Tablespace Migration Utility main menu:


•

OATM configuration file

•

APPL_TOP[]

•

FND_TOP[/fnddev/fnd/12.0]

•

Database Connect String [dummy]: atgtsqa

•

Password for your 'SYSTEM' ORACLE Schema

•

Password for your 'SYS' ORACLE Schema

•

Oracle Application Object Library Schema name [APPS]

•

Password for APPS

•

APPLSYS Schema Name [APPLSYS]

Information can be provided in an interactive manner or by providing an OATM configuration file with all information already specified. An OATM configuration file has the following format with the following valid tags: APPL_TOP FND_TOP APPS_SCHEMA APPLSYS_SCHEMA ALLOC_TYPE UES DBF_DIR INDIVIDUAL_DATAFILE_SIZE NUM_WORKER MIGRATION_SCHEMA CONNECT_STRING AUTO_START_MIGRATION after

-

valid APPL_TOP value or $ENV$ valid FND_TOP value or $ENV$ valid apps schema name valid applsys schema name UNIFORM/AUTOALLOCATE - valid integer (uniform extent size) - valid directory for generated database file - maximum datafile size - integer (number of concurrent workers.) - % or comma separated list of schemas - database connect string - should migration be started automatically preparatory steps are completed

Y(default)/N

$ENV$ is a reserved word for the OATM configuration file. If $ENV$ is used as a value for a specific token, then that token's real value will be derived from the customer's environment dynamically during the runtime.


Example

Oracle Applications System Administrator's Guide

Oracle Applications System Administrator's Guide

Suggest Documents

Oracle Applications System Administrator's Guide

Oracle Applications Flexfields Guide

Oracle Applications System Administrator's Guide - Maintenance

Oracle® Applications - Oracle Documentation

Oracle Lifetime Support Policy for Oracle Applications Guide [PDF]

Oracle Lifetime Support Policy for Oracle Applications Guide

Oracle Lifetime Support Policy for Oracle Applications Guide

Oracle Business Intelligence Applications Configuration Guide for ...

Oracle Business Intelligence Applications Installation Guide for ...

PeopleTools 8.52: PeopleSoft Applications User's Guide - Oracle ...

Oracle Business Intelligence Applications Configuration Guide for ...

Oracle Business Intelligence Applications Security Guide

Oracle Business Intelligence Applications Security Guide

Siebel Applications Administration Guide - Oracle Documentation

Security Guide for Siebel eBusiness Applications - Oracle ...

Oracle® Applications

Oracle® Applications

Oracle® Applications

Oracle AppAdvantage, Oracle Applications Customers Using Oracle ...

Oracle AppAdvantage, Oracle Applications Customers Using Oracle ...

Oracle Fusion Middleware System Administrator's Guide for Oracle ...

System Administration Guide, Volume 1 - Oracle Documentation

Oracle Business Intelligence System Troubleshooting Guide

System Administration Guide Oracle Solaris 9 Containers