P. 1
EBS Single Sign

EBS Single Sign

|Views: 86|Likes:
Published by Shiraz Mustafa
EBS Single Sign Document helpful for ERP customers
EBS Single Sign Document helpful for ERP customers

More info:

Published by: Shiraz Mustafa on Apr 17, 2013
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

10/30/2013

pdf

text

original

Oracle E-Business Suite Standards

Schedule to the On Demand Services Ordering Document
Version 1.3, 4/1/2011 This is the Oracle E-Business Suite Standards Schedule to the On Demand Services Ordering Document. This Schedule describes Oracle‟s On Demand standards for the Oracle E-Business Suite Programs listed in the Ordering Document and that reside in Customer ‟s Environment. The standards described herein are part of the On Demand Services provided under the terms of the Ordering Document. Capitalized terms not otherwise defined herein shall have the meaning ascribed to them in the Definitions Schedule. This Schedule addresses the following topics: Section 1: Section 2: 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 Standards Scope .............................................................................................................. 2 Oracle On Demand Infrastructure .................................................................................... 2

Certified Configurations ............................................................................................................... 2 Oracle E-Business Suite Certified Configuration ........................................................................... 2 Environments .............................................................................................................................. 3 Vision Database .......................................................................................................................... 4 Wireless Networks....................................................................................................................... 4 Multi-Phase Implementations ....................................................................................................... 4 Setup and Maintenance Releases ................................................................................................ 4 Language Support ....................................................................................................................... 4 Localizations ............................................................................................................................... 4 Third Party Software .................................................................................................................... 4 Hardware .................................................................................................................................... 6 Operating System........................................................................................................................ 6 Oracle On Demand Automation Platform...................................................................................... 6 Server Load Balancing (BIG-IP) ................................................................................................... 6 Oracle On Demand Network Architecture and Internet Connectivity .............................................. 6 Using Database Links for the @Oracle Model .............................................................................. 7 Storage Architecture .................................................................................................................... 8 Oracle On Demand Standards and Requirements ........................................................... 8

Section 3: 3.1 3.2 3.3

Software, Operating System, and Third Party Software Standards and Requirements ................... 8 Oracle On Demand Development CEMLI Standards and Requirements ........................................ 9 File Transfers ............................................................................................................................ 14 Oracle On Demand Environment Naming Conventions and Access Controls ............. 14

Section 4: 4.1 4.2

Oracle On Demand Naming Conventions ................................................................................... 14 Access Controls ........................................................................................................................ 15 Printing ........................................................................................................................... 19

Section 5: 5.1 5.2 5.3

Oracle On Demand and Print Servers ........................................................................................ 19 Oracle On Demand and Operating System Printer Standards ..................................................... 19 Operating System Printer Queue Setup...................................................................................... 19

1

Oracle provides Certified Configurations.2 Oracle E-Business Suite Certified Configuration Oracle E-Business Suite is a consolidated suite of Enterprise Resource Planning (ERP) applications. 2. 2. It is installed with the required Oracle E-Business Suite software configured in accordance with the Standards. implementation and management of Customer‟s Environment for the Oracle E-Business Suite Programs listed in the Ordering Document and that reside in Customer‟s Environment (“Oracle Programs” or “Oracle E-Business Suite Programs”). The Figure below illustrates the Oracle E-Business Suite R11i Certified Configuration core architecture. Section 2: Oracle On Demand Infrastructure This Section 2 describes the Infrastructure Standards for Oracle E-Business Suite Programs. Customer is solely responsible for system hardware. For @Customer deployments. storage and any types of load balancing required for the On Demand Services. Oracle requires that all implementations of Oracle E-Business Suite Programs begin with the Certified Configuration software. including the Certified Configuration and Oracle On Demand Automation (OAP). and the Oracle Program software stack. operating systems. 2 .Section 1: Standards Scope This Schedule describes standards (the “Standards”) specified by Oracle for the development.1 Certified Configurations Certified Configurations (CCs) combine the integration. which contain the software used to set up and initialize On Demand systems to be compliant with the Standards. Three separate Oracle E-Business Suite environments are provided on the Oracle E-Business Suite Certified Configuration:   The Production Environment (PROD) is designed to run Customer‟s production application system. The Production Support Environment (TEST) is used for problem diagnostics and resolution. and validation of hardware systems. The Oracle E-Business Suite Certified Configuration is designed to provide a “ready-to-implement” Environment for Oracle On Demand. configuration.

10 and above).1.2. and Oracle Application Server Portal) Oracle Forms 6.8.2 Since the Oracle E-Business Suite Certified Configuration can change over time.1.2   Oracle Express Server can only be licensed for Release 11 implementations Oracle Financial Analyzer (OFA) and Oracle Sales Analyzer (OSA) 11i Server  Customer must purchase On Demand Services for the following in order to use the financial and sales analyzer functionality:    Oracle Financials Analyzer Oracle Sales Analyzer Oracle Advanced Supply Chain Planning (ASCP)   Apache/1. In general. Oracle Discoverer.0. The Non-Production Environment (DEV) provides an isolated environment for development of configurations.3. the Non-Production (DEV) environment).0.3 Oracle Applications Server 10gR2 Forms 10.1.2 rollup 5) Release 12  E-Business Suite Release 12.0.2 Oracle Discoverer 10g Release 10.27.1.26 Web ADI 11i UTF8 database character set Oracle Express Server 6. including the following:         Oracle Database 10g Oracle9i Applications Server or Oracle Applications Server 10g (for example.2. 2.3.26 Oracle Database10gR2 10. modifications.2.3.5 CC Utility Pack Version 4. including:         JInitiator 1. Customer should refer to the Oracle E-Business Suite Certified Configuration Release Notes to identify the currently supported components. localization.2 Applications Release 12.0 Single Instance Oracle Applications Server 10gR3 J2EE 10. The Oracle E-Business Suite Certified Configuration consists of the following components for each Major Release:  Release 11i  Oracle E-Business Suite Release 11i (11. Oracle Developer. and integrations (CEMLI) and multiphase development when more than one phase is in progress.19(iAS 1. the Non-Production Environment serves as a test-bed for any development activities.3.5. Typical Oracle-Controlled Environments are the Production Environment and the Production Support Environment following Production Go-Live.1. extensions.3 Environments Customer-Controlled Environments are those environments in which Customer or its designees have authority to make changes (for example. 3 .0.0 Oracle Applications Manager 11i JInitiator 1.2 Java Development Kit (JDK) 1. OracleControlled Environments are those environments in which Oracle has sole access to make Changes.

based upon Customer‟s requirements. is created. WiFi). Customer or its designee typically control all environments. Other languages required and purchased by Customer are installed during initialization or thereafter. typically the DEV Environment. Accordingly.10 may be installed and maintained in the 4 .During the implementation phase of On Demand Services. 2. also known as localizations. 2. or any Non-Production Environments (collectively. including the provision and management of the network and carrier and ensuring the privacy and security of such access. 2.7 Setup and Maintenance Releases Customer is solely responsible for setup of the Oracle Programs and applying Maintenance Releases prior to Production Go-Live.10 Third Party Software On Demand has a strict policy about Third Party Software that may be installed on the Environment. developed by Oracle to support local requirements for On Demand Services are not installed or activated during On Demand initialization. Customer is solely responsible for all aspects of such access. Production Support Environment. There are two types of Vision Databases:   Shared Vision Databases can be accessed by all Oracle On Demand customers (“Shared Vision Database” A Vision instance dedicated solely to Customer (“Dedicated Vision Instance”) A Dedicated Vision Instance is counted as a Non-Production Environment against Customer‟s Entitled environments as indicated in the Applicable Entitlement Schedule. Access is granted for two to three months until Customer‟s first environment.6 Multi-Phase Implementations The implementation of an Oracle E-Business Suite Environment is sometimes comprised of multiple phases due to the number and complexity of modules. 2. A shared Vision database is not counted towards Customer‟s Entitlement. The Vision instance is intended only for demonstration purposes.4 Vision Database The Vision instance is a Demonstration Environment (DEMO) of the Oracle E-Business Suite installation. Oracle On Demand may make changes to the documentation for the Production Support Environment and Production Environment. If Customer allows their employees to access the Oracle Programs via wireless and mobile networks (for example. Oracle On Demand recommends that Customer order additional Non-Production Environments to enable multi-phase implementations. 2. Configuration changes made to the Production Environment. Customer is responsible for maintaining and updating the documentation for Customer-Controlled Non-Production Environments.8 Language Support Oracle E-Business Suite Certified Configurations use U. English. If Customer has purchased Computer and Administration Services.9 Localizations Any country-specific customizations.S. Customer will receive a Vision instance upon request. the “Environment”) must be documented. Additional fees will apply for the additional Non-Production Environments.5 Wireless Networks Oracle On Demand does not provide services to support wireless or mobile access. The applications listed in this Section 2. 2. 2. Oracle does not provide backup or recovery services for Vision instances.

and the Payroll Tax Law updates that are necessary for the Oracle E-Business Suite Programs. Ongoing 5 . management of print servers is Customer‟s responsibility. Oracle does not provide content services for any of the other listed applications. Additionally. Approved Third Party Software is listed in the following table. Oracle installs year-end legislative updates. and North American address validation data. IRS 1099 rules. 1 For @Oracle. The supportability and certification over Certified Configuration platforms and operating systems of Third Party Software The Environment is designed to allow Third Party Software approved by Oracle (“Approved Third Party Software”) to integrate with the Environment if such software adheres to the integrations standards outlined herein. all print servers are located on Customer‟s side of the network. Oracle will load monthly content updates for Vertex that consist of payroll tax data. sales tax data. Approved Third Party Software PRINTING SOFTWARE1 Optio Print Manager Evergreen Data Systems FormScape Loftware Connector Adobe Output Pack for Oracle E-Business Suite TAX SOFTWARE CertiTAX Vertex Taxware ONLINE PAYMENT SOFTWARE Verisign Pay Flo Pro Payment Tech BUSINESS INTELLIGENCE SOFTWARE Kbace KBX Noetix Views  Content Services Based on Customer‟s requirements. at year-end. The list of approved Third Party Software is subject to change. Customer is solely responsible for the following:     Configuring and managing all Third Party Software (excluding the @Oracle operating system and the VPN provided by Oracle) in accordance with Oracle specifications Testing and resolving issues related to Customer or Third Party Software (including working with Third Party Software Vendors) Sizing related to Third Party Software. Customer may not use any Third Party Software in connection with Computer and Administration Services without Oracle's prior written approval.Environment in accordance with Oracle practices.

@Customer hardware configurations are only available on x86-64 hardware (containing at least 2 processors and 16GB RAM). BIG-IP virtual server port 80 mapped to Apache service on mid-tier server port 10015) and offloads SSL processing from Apache mid-tiers to BIG-IP hardware SSL accelerator cards.15 Oracle On Demand Network Architecture and Internet Connectivity Oracle On Demand specifies network architectures from which Customer must choose for network connectivity with Oracle. a server load-balancing appliance.   2. Changes to the OAP Toolset are applied following the Change Management process. administration and management of the Oracle Programs.  Oracle On Demand Automation Platform Toolset The On Demand Automation Platform (OAP) Toolset is a subset of OAP that Oracle will install on Customer‟s Environment during initialization. OAP resides in a data center that provides telecommunications. mechanical. 2. User and Installation Guides During initialization. Oracle will assist Customer or Implementer as necessary during the installation when specific installations tasks require special privileges not granted to Customer or its Implementer. The tasks include initialization. and for assisting Oracle with such patching or Upgrades..13 Oracle On Demand Automation Platform The Oracle On Demand Automation (OAP) is a comprehensive set of software Tools and processes that enable Oracle On Demand to deliver operational tasks in a repetitive and automated fashion. 6 . This hardware is validated against Oracle requirements and Customer‟s application workload. electrical. and IBM platforms. Patching and Upgrades Customer is responsible for providing to Oracle detailed instructions for installation. Oracle On Demand Automation Platform Repositories and Processes In addition to the OAP Toolset. Oracle E-Business Suite On Demand @Customer deployments are supported on Oracle Enterprise Linux. Oracle E-Business Suite is standardized on the Enterprise Linux distribution from Oracle--the Oracle Enterprise Linux Release 5. patching and Upgrades for Third Party Software. Oracle reserves the right to change the operating system at its discretion. HP. For more information about networking.14 Server Load Balancing (BIG-IP) Oracle On Demand uses BIG-IP. OAP also contains information repositories and defined processes. 2. based on Customer‟s deployment configuration.12 Operating System For a @Oracle deployment. 2.g. It provides port translation services (e.11 Hardware Oracle E-Business Suite Certified Configurations for Computer and Administration Services are built on Intel or AMD 64-based architecture containing at least two processors and 8 GB of memory. deployed in a redundant configuration to cluster application servers for scalability and fault tolerance. and room specifications. Oracle provides Customer with appropriate user and installation guides (if applicable). The OAP repositories are proprietary in nature and are not available to Customer. 2. see the Network and Connectivity Standards Schedule. The OAP Toolset is subject to change without notice.0. The Certified Configuration contains the necessary patches for running the Oracle application software stack. Customer preferred platforms must be able to support the On Demand-supported operating system and Oracle software certifications. This system is referred to as the minimum standard architecture. Sun.

If Customer purchases a DMZ server. For example. Oracle Warehouse Builder. 7 . commonly known as the “OSA-10”. and any other deployments are not allowed for security reasons. Oracle examines database links intended for deployment in the Production Environment as part of the Production Assessment to determine whether or not usage conforms to Oracle‟s guidelines. Oracle approval is required to implement an internet-facing environment.  Implementation Customer may need to migrate data to the Environment. the WAN.  Stabilization During stabilization. Such an approval should be documented in the Customer Functional and Business Requirement Document. Oracle will design Customer's Environment to be available through the Internet through Secure Sockets Layer (SSL) connections. Oracle Portal.16 Using Database Links for the @Oracle Model An Oracle database link enables connections and transfer of data from one database to another. No other Internet-facing deployment is available. To accommodate this. 2. Oracle reserves the right to remove database links that do not conform to Oracle‟s guidelines. The Implementer must remove any database links that do not comply with these guidelines. and Oracle9iAS or Oracle Applications Server 10g InterConnect database connectors can be used. Oracle assumes Customer is aware of the risks of data loss and compromise inherent in Internetfacing deployments.Internet-Facing Deployment of Oracle E-Business Suite Applications Oracle On Demand Environments are deployed in an Internet-facing environment only if specifically requested by Customer as indicated in the Ordering Document and provided that Customer first pays additional fees associated with a DMZ server. architecture standards require database links to be used within the Oracle On Demand Infrastructure. Customer acknowledges and agrees that Oracle is not responsible for any loss or compromise of data arising from or related to the use of Internet-facing deployments. and expects Customer to seriously consider these risks before requesting such a deployment. If Customer chooses to use database links. Database links providing data exchange and integration over the Internet. Internet-facing Environments must have the latest patch level Release and Critical Patch Updates must be applied immediately after their release. database links are allowed during implementation to perform bulk data moves from a source database to the target database within Customer‟s Environment. provided they are located within Oracle‟s Data Center.

17 Storage Architecture The @Oracle base configuration includes the Entitled storage indicated in the Oracle E-Business Suite for @Oracle Entitlement Schedule. Information about the configuration and Release requirements for the operating system software is available in the corresponding Oracle E-Business Suite Certified Configuration installation guide. operating system. Timelines for temporary modifications must likewise be documented and approved in writing by Oracle. or Re-implement the integration to use bulk extract methods. 3. Operating System. Database links defined into or out of Oracle‟s Data Center are not allowed. archive files.  Oracle E-Business Suite Certified Configuration Oracle requires that implementations of @Oracle and @Customer deployments for Oracle EBusiness Suite Programs begin with the Certified Configuration. database files. 2. Contact Oracle On Demand for the most recent list of supported operating systems. Oracle E-Business Suite and HTML DB Support Oracle On Demand supports HTML-DB only if Customer purchases On Demand for Oracle Technology Programs. or later (some components might be available only on 32-bit platforms) All platforms in the preceding table are supported for an @Customer deployment. concurrent manager output.1 Software. Section 3: Oracle On Demand Standards and Requirements This section describes the Oracle On Demand standards and requirements. and Third Party Software. particularly where VPN and WAN are used. Any security changes required to perform these operations must be documented and approved in writing by Oracle. database code. Where defined database links are not allowed based on Oracle‟s guidelines. applications code. Production Database links with end-points that are located within Oracle‟s Data Center are allowed. Any requested exceptions will be examined by Oracle On Demand Global Information Security (GIS) and are subject to GIS approval and a documented risk assessment may be required.  8 . and support for enhanced backup and restoration processes). to move large volumes of data. Oracle Enterprise Linux is the only operating system available for @Oracle deployments. the Web-based version is deployed with the Oracle Programs. All disk storage supports a variety of applications and applications or business development lifecycle requirements (for example. Certified Configurations support Oracle EBusiness Suite Releases on the following platform and operating system combinations: Platform Linux x86 (32-bit and 64-bit) Operating System Version Oracle Enterprise Linux 5. and Third Party Software Standards and Requirements This section describes the standards and requirements for the Oracle E-Business Suite Programs. Either of these methods should provide better performance and scalability than database links. Additional Storage can be purchased for additional fees. for example SFTP. the following options are available:   Re-implement the integration to use the integration methodology described in this Schedule.  Oracle E-Business Suite Release and Oracle Operating System Requirements As of the publication date of this document.  Oracle Web-Based Application Deployment If Web-based Releases of the Oracle E-Business Suite client software applications are available.

modifications are not allowed within the Environment. Because it is very difficult to identify such changes to standard objects.2 identifies standards that are either unique to On Demand or require special emphasis. or separately contracting for support of. including the Oracle Application Developers Guide. and integrations. This Section 3. extensions. New Releases of Oracle Programs have minimal. also known as "customizations in place". and all integrations must follow the guidelines and standards required for creating extensions.  Configurations Configurations are defined as changes that are made to functionality of the Oracle Programs to meet customer-specific business requirements and are completed using the user interface provided with Oracle Programs. Thus. Integrations Integrations enable Customer to transfer data between Oracle E-Business Suite Programs and other Oracle programs or Third Party Software. @Oracle Minimum Deployment Architecture The minimum @Oracle deployment architecture for Oracle E-Business Suite Programs is a two-tier Production Environment physically or logically isolated from a two-tier Non-Production Environment. Provided that Oracle‟s guidelines and standards for creating these extensions are followed (including keeping these objects separate from standard Oracle E-Business Suite Program components). and the use of Change Management processes. This section does not supply all content required to effectively perform an On Demand implementation. recommendations.  Modifications Modifications. Localizations for a country are typically provided and supported by Oracle Consulting or other Oracle subsidiaries in that country through a separate written agreement with Customer. Oracle‟s support is limited to configurations and localizations. impact on extensions. Integrations must be developed by Customer.2 Oracle On Demand Development CEMLI Standards and Requirements Oracle publishes several documents that describe Oracle requirements. are changes made to standard Oracle Program objects or code.  Extensions Extensions are new components developed by Customer using the development features provided within the Oracle Programs. Oracle On Demand CEMLI Goal Oracle On Demand's CEMLI goal is to minimize complexity. unless otherwise specifically stated within this Schedule. extensions are generally relatively straightforward to identify and maintain. Customer is responsible for supporting. which are not part of the standard functionality of the Oracle Programs. Integrations should take advantage of several standard interface programs and APIs provided with the Oracle E-Business Suite Programs to facilitate data transfer. Although Oracle On Demand may host such CEMLIs. or no. Configurations do not change the existing code or add new code. Localizations Localizations are developments designed to address country-specific requirements. cost and risk to Customer through Customer's implementation of correct controls. such as statutory reporting and other business practices.    9 . Oracle On Demand requires that all CEMLIs deployed into the Environment comply with the requirements listed within the Oracle Developer’s Guide. there is significant risk that modifications may not be preserved when a new Release is applied. 3. modifications. and practices for the implementation of Oracle E-Business Suite programs. Oracle may agree to provide services for certain CEMLIs via written agreement with Customer. the use of Oracle development standards.

including a detailed customization review and risk assessment. Customer must:    Follow a structured process. and the security of data.  CEMLI Standards To minimize the risk associated with CEMLI customizations. CEMLIs may also affect or compromise system availability. Adhere to Oracle‟s Change Management procedures to control and manage the ongoing addition of customizations throughout the On Demand lifecycle. and accurate documentation regarding the implementation of the Oracle Programs and CEMLIs. and document customization requirements prior to beginning development. Upgrades may break existing CEMLIs. Upgrade and Maintenance Release Risk New Releases and  CEMLIs may impact the application of new Releases or Upgrades. of any CEMLIs. Upstream modifications may break downstream delivery and impact service.   Version Control Implementer or Customer must execute version control of CEMLI code. 10 . This exercise helps to assess the impact of the CEMLI on operations and to compare the risks versus costs of the CEMLI. concise. for the life of the CEMLI. communicate. batch process. or database levels. Risks of Using CEMLIs Customizations to the Oracle E-Business Suite Programs present three types of risk to Customer and Customer‟s Environment:   Support Risk: CEMLIs may result in more complex or less effective support to Customer Operations Risk: CEMLIs create the risk of adversely impacting performance and/or system operability at the on-line. and include the following types of documentation:       Business requirements and functional specifications System design and technical specifications Technical documentation User documentation The documentation must: Provide enough information to assist Customer or Implementer with the comparison process that must be performed when new Releases or Upgrades are reviewed Be submitted before Production Go-Live. Comply with Oracle‟s CEMLI standards and guidelines. The documentation should include the functional and technical design. system level integrity. and functionality. Roles and Responsibilities The parties‟ roles and responsibilities regarding CEMLIs are as follows:  Customer and Implementer  Establish. Oracle strongly recommends that Customer utilize the following guidelines in an effort to minimize performance risk and stability risk presented by CEMLIs:      Minimize the use of CEMLIs by using functional alternatives and workarounds Minimize risks by using pre-packaged customizations Minimize risks by employing Oracle On Demand development and testing standards and best practices Update documentation detailing the CEMLIs when changes are applied to customized code CEMLI Documentation and Version Control Customer or Customer‟s Implementer must maintain clear.

and fixes.      Maintain a copy of the customization documents identified above and provide updated copies to Oracle throughout the CEMLI‟s lifecycle. patches. All custom applications should be registered under the XBOL or custom directory beginning with the XX-prefix. menus. where SID is the system identifier. Perform any additional work on the customized objects such as Upgrades. The forms directory contains forms. Identify the impact on customizations of implementing new Releases. responsibilities. (Oracle allows multiple custom file system directories). Retrofit customized objects. and functions should be registered under XBOL or similar custom applications beginning with the XX-prefix as defined by Customer. and to discuss alternatives. The sql directory contains SQL scripts and SQL*Plus reports. Store all custom files under the $XBOL_TOP directory or any custom directory starting with the XX-prefix. concurrent programs. All CEMLIs that run as concurrent programs such as concurrent executables. Directory Structure for CEMLIs Note the following:      The bin directory contains UNIX shell scripts and SQL loader scripts. Customer and Implementer   Review and test customized code before it is deployed into the Production Environment On Demand Development Standards for File System and File System Objects Customer and its Implementer must follow the guidelines listed in this section when creating custom file systems or file system objects. risks and costs. reports. including Upgrades. The reports directory contains reports. 11 . Store all custom files under the SID/applmgr/CUSTOM directory. Discuss customizations and their operational and support impact to understand the requirements. The wf directory contains Oracle Workflow definitions. The discussion should focus on minimizing the use of customizations and related risks Oracle.     Do not change the standard Oracle file system architecture. request sets. Retain responsible for any impact that the implementation of new Releases has on any CEMLI.    CEMLI Directory Structure The following figure illustrates the directory structure for CEMLIs in the $XBOL_TOP or $XXprefix custom directory.

  The cstmsdx directories contain Customer code. including packages. Customer may have multiple custom schemas. Customer is solely responsible for testing and resolving issues related to. technical support. and that certain Change Management activities may overwrite modifications.   Custom schemas should be named BOLINF or should start with the „XX‟ prefix. Customer should contact its Oracle sales representative to learn more about Oracle Application Server 10g.  If Customer proceeds with modifications to the standard objects or tables. Customer acknowledges the following:   Identifying and debugging errors caused by triggers is difficult and is provided by Oracle on an “as-is” basis. 12 . Customer is responsible for purchasing all necessary Oracle licenses. Customer acknowledges that support of modifications is very difficult and is provided by Oracle on an “as-is” basis. Customer may not add to or change the database triggers for standard Oracle E-Business Suite Program tables. If Customer uses custom triggers. Customer may not use custom triggers to modify data in Oracle E-Business Suite Program tables. such custom database objects. including PL/SQL objects.2 when creating custom database objects. Custom objects.  On Demand Oracle Application Server 10g Integration Framework The Oracle Application Server 10g integration framework provides a framework and mechanisms designed to enable effective integration between the Oracle Programs and other applications. Register all custom objects. located in the database under the custom schema. to support the On Demand Oracle Application Server 10g integration solution. Customers may add additional sub-directories as required for their application. and any impact patching may have on. The following subsections describe those integration mechanisms.  Adding new database triggers or changing existing database triggers on standard application tables can cause a complete change in the functionality of the Oracle Programs and can lead to serious data integrity problems.       Customer must use APIs when Customer requires access to base application tables. Customer may not modify standard Oracle E-Business Suite Program objects or tables unless there is no alternative to such modification. and On Demand Services for Oracle Technology Programs. Customer should use custom triggers only when other methods of completing the required task do not meet Customer‟s business requirements.  Support personnel may overlook problems associated with triggers that are not documented. Oracle E-Business Suite database The Oracle E-Business Suite database contains the following:     Universal schema (APPS) Oracle application module schema (for example AR) Customization schema (BOLINF or XX-prefix) Read-only schema (RAC_ACCNT)  Standards for Oracle E-Business Suite Integration Oracle On Demand provides a variety of standard mechanisms to enable integration with Customer‟s Environment. may not be registered under APPS. such as packages. Development Standards for Database Schemas and Database Objects Customer and its Implementer must follow the standards listed in this Section 3.

Customer is responsible for purchasing all necessary Oracle licenses. and On Demand Services for Oracle Technology Programs. If Customer requires SSO/CIM solutions. The minimum requirements for an @Oracle deployment of the Oracle Programs and SSO/CIM follow. Customer may be required to purchase full-use licenses based on their application environment. The SSO server must be dedicated to SSO/CIM functionality and may not be multi-purposed for other Oracle Application Server 10g functionality such as Discoverer or Portal. technical support. technical support. Service/ Requirements SSO / OID Single sign on through VPN Production 1 (two-tier) x2 CPU each tier 1 Server x2 CPU Database 1 Server x2 CPU Oracle AS 1 (two-tier) x2 CPU each tier 1 Server x2 CPU Database 1 Server x2 CPU Oracle AS (DMZ Server) 2 (two-tier) x2 CPU each tier 1 Server x2 CPU Database SSO/OID/CIM/Portal 1 Server x2 CPU Oracle AS SSO/OID/CIM/Portal 2 (two-tier) x2 CPU each tier 1 Server x2 CPU Database SSO/OID/CIM/Portal 1 Server x2 CPU Oracle AS SSO/OID/CIM/Portal (DMZ Server) 2 (two-tier) x2 cpu Oracle Application Server Non-Production 1 (two-tier) x2 CPU each tier 1 Server x2CPU Database 1 Server x2CPU Oracle Application Server (AS) 1 (two-tier) x2 CPU each tier 1 Server x2 CPU Database 2 1 Server x2 CPU Oracle AS (DMZ Server) 2 (two-tier) x2 CPU each tier 1 Server x2 CPU Database SSO/OID/CIM/Portal 1 Server x2 CPU Oracle AS SSO/OID/CIM/Portal 2 (two-tier) x2 CPU each tier 1 Server x2 CPU Database SSO/OID/CIM/Portal 1 Server x2 CPU Oracle AS SSO/OID/CIM/Portal (DMZ Server) 2 (two-tier) x2 cpu Oracle Application Server SSO / OID through Internet SSO / CIM through VPN SSO / CIM through Internet SSO / CIM with Collaboration Suite 3 On Demand (CSO)  Oracle E-Business Suite and Integration with Portal Customer may choose to create a custom portal for the Oracle Programs. This minimum architecture does not take into account Customer‟s capacity or availability requirements. The minimum architectures do not take into account Customer‟s capacity or availability requirements. Oracle supports the integration of disparate directories to enable a CIM solution. and On Demand Services for Oracle Technology Programs for such a solution. The minimum requirements for an @Oracle deployment with a custom Oracle Application Server 10g Portal for the Oracle E-Business Suite Programs follows. Service/ Requirements Oracle Application Server 10g Portal Production 2 (two-tier)x2 cpu Oracle Application Server4 Non-Production 2 (two-tier)x2 cpu Oracle Application Server 2 3 4 Depending on Customer‟s requirements. Customer is responsible for purchasing all necessary Oracle licenses. 13 . Oracle E-Business Suite and Integration with Oracle Single Sign-On and Common Identity Management Solution Oracle provides Identity Management solutions that are designed to enable Customer to create Single-Sign On (SSO)/Common Identity Management (CIM) solutions for Oracle applications and Third Party Software. Customer may be required to purchase full-use database licenses for the database tier.

and On Demand Services for Beehive Programs.sum extension. such as program files and scripts.Customer is solely responsible for the implementation of portal services.  3.  Oracle E-Business Suite Integration with Oracle Beehive There are certain Oracle E-Business Suite modules that may be integrated with Oracle Beehive. The names are defined as follows:   The Oracle user name is made by concatenating or with the database SID. and user names. All inbound files. Customer is solely responsible for providing. The file contains the checksum value performed on the data file. This can be the Production Support Environment (TEST). support. Customer may send a checksum file along with a data file. The On Demand Change Management process must be followed for Production Environments. The name of the checksum file must match the name of the data file. However. The mount point for the environment is the same as the database SID. can be moved to the appropriate location on Customer's SFTP server using SSH File Transfer Protocol. This four-character code uniquely identifies Customer‟s Environment.     14 . except it has a *. and SQL scripts to the appropriate environment after Customer or Customer‟s Implementer uploads them to the SFTP server. All outbound files. User names. Mount point. Customer is solely responsible for the implementation of these integrations. File Transfers Oracle will provide SSH File Transfer Protocol (Secure FTP or SFTP) access to a dedicated SFTP server that will facilitate Customer customization or patching of Non-Production Environments. when Customer has Additional NonProduction Environments. such as Customer data file movement. maintaining and supporting any SFTP client and other software. or Additional Non-Production Environments. To leverage this integration. the SFTP server is the only server directly accessible from the Production Environment server. Customer has the option of verifying the checksum before using the data file. mount points. Each environment uses different port numbers. Customer will receive its own file transfer account. Database SID. It is combined with the first letter of the environment type to form the database system identifier (SID). reports.3 Oracle E-Business Suite Integration with Printers For information about configuring the Oracle Programs for printing. The mount point is always entered in lowercase. Environment type. 4. If Customer has purchased Computer and Administration Services. Customer must purchase Oracle the applicable licenses. Customer‟s short code. and the letter i.  Transfer Process With the exception of the Production Environment and the Production Support Environment. the FTP process automatically moves CEMLIs such as custom forms. the SID is created with the first three digits of the short code plus the environment number. This is usually made by concatenating the first letter of the environment type.1 Oracle On Demand Naming Conventions The naming conventions for Oracle E-Business Suite are as follows:  Customer short code. should be automated using a standard process set up by Oracle On Demand to transfer the data files from the NonProduction Environment to the SFTP server. Oracle will not provide SFTP clients or other software or any support for such software. the NonProduction Environment (DEV). Oracle will provide operational support for the SFTP infrastructure only. Section 4: Oracle On Demand Environment Naming Conventions and Access Controls This section describes Oracle On Demand naming conventions and access controls. refer to Section 5. The applmgr user name is made by concatenating ap with the database SID.

The BOL-SETUP user name is assigned the Applications Administrator responsibility for use in implementing the Oracle Programs.2. The implementation team is granted required and necessary access to Non-Production Environments to perform required application-related configuration. During initialization. There will be two standard SFTP accounts: one for the Production Environment.2 Access Controls Oracle On Demand implements an access control method that incorporates layers of access. and usage materials. initialization. The following table illustrates a Production Support Environment (TEST) example for both Release 11i and Release 12 where xxxx is the four character Customer code. E-Business Suite Release R11i Database Tier               /txxxxi/oracle /txxxxi/oradata /txxxxi/backup /txxxxi/oracle /txxxxi/arch /txxxxi/applcsf /txxxxi/oracle /txxxxi/oradata /txxxxi/backup /txxxxi/oracle /txxxxi/oratmp /txxxxi/log /txxxxi/arch /txxxxi/applcsf     Middle Tier /txxxxi/applcsf /txxxxi/applmgr /txxxxi/product /txxxxi/disco RAC  /oracm/oracle  /oracm/oradata R12       /txxxxi/applcsf /txxxxi/applmgr /txxxxi/product /txxxxi/mtlog /txxxxi/disco /txxxxi/inst  /oracrs/oracle  /oracrs/oradata 4.   The following table shows examples of user names (where xxxx is the four character Customer code): Environment Production Support (TEST) Development Database SID txxxxi User Names  oracle user: ortxxxxi  applmgr user: aptxxxxi  interface user: one for the Production Environment and one for the Non-Production Environment  oracle user: ordxxxxi  applmgr user: apdxxxxi  interface user: one for the Production Environment and one for the Non-Production Environment dxxxxi  Oracle On Demand Standard File Systems Oracle E-Business Suite is installed under and uses a standard file system structure. named accounts mapped to individual users. the Applications Administrator responsibility should be assigned to a named application user. Oracle provides Customer with the latest account specifications. An overview of the layers involved and the key characteristics of each layer are presented in this Section 4. Prior to Production Go-Live. For multi-tenant. there will be separate accounts for each Customer using the $CID in the account name. The user BOL-SETUP will be end dated at Production Go-Live. and one for the Non-Production Environment. and verification 15 . training. and mandatory password maintenance. development.

 Operating System Users Oracle E-Business Suite Programs are typically installed under two operating system users: oracle and applmgr. Named Linux or UNIX Accounts Named Linux or UNIX accounts are used to associate individuals to unique operating system user accounts.  Operating System and Database Access For @Oracle deployments. see the Oracle On Demand PowerBroker Access and Automated Password Management Manual.  PowerBroker Policies Symark PowerBroker is Third Party Software used to permit access beyond that granted to named accounts. Account or Responsibility Responsibility Application Responsibility: Custom responsibility provided to Customer’s technical lead Application Administrator Oracle On Demand provides this access to Customer‟s technical lead administrator. and are necessary to use the Password Manager utility to gain access to the database. refer to the Oracle On Demand PowerBroker Access and Automated Password Management Manual. The oracle user owns the Oracle Technology Stack and database.  Database or Oracle E-Business Suite Accounts After an individual has gone through the first three layers. Using these accounts and passwords.  Application and Database Access The following table provides information about the accounts in an environment for Oracle E-Business Suite programs and the applications-related responsibilities associated with them. an account is created for the Implementer and the interface account is created for file transfers. Anonymous or shared logins to the operating system are not permitted. PowerBroker policies associate the named accounts to more privileged operating system accounts. For more information on Symark Powerbroker policies and password management. only access to the operating system and database is available. These security measures are not used independently. For information about access to the operating system and database. certain well-known Oracle E-Business Suite Program accounts. Named Linux or UNIX accounts. for which they have been authorized. PowerBroker policies. and is a member of the oaa group. they have final access to the set of database accounts or Oracle E-Business Suite Program accounts. and if applicable. the individual is able to use the various accounts described in the following subsections. These named accounts are the lowest level of access with minimal privileges. Password Manager enables Oracle On Demand to manage passwords and provide controlledaccess to passwords for End Users with named operating system accounts and associated PowerBroker policies. or both. If Customer has purchased Administration Services. For @Oracle deployments. The responsibility is given in lieu of the System Administrator responsibility and should be assigned to the named application Users that will handle application administration at  16 . and is a member of the dba group. and the Password Manager utility provide interrelated layers of security.tasks. Customer is responsible for implementing an access control method for the operating system. The applmgr owns the Oracle E-Business Suite Technology Stack.  Password Manager The Oracle-proprietary Password Manager utility is used to display privileged database and Oracle E-Business Suite Program passwords to those who have named Linux accounts and associated PowerBroker policies.

Account or Responsibility Customer‟s site. This responsibility enables use of Examine Privileges on Non-Production Environments. there will be a separate account for each customer which will include the $CID in the account name. define value sets. For multi-tenant customers. and delete access to the standard interface or customized objects. define currencies. insert. define application messages. define request sets. administer responsibilities. It is granted to Customer‟s Implementer only for Non-Production Environments. printer types. perform network latency and bandwidth tests. System Administrator responsibility may be granted to this User to complete setup. define executables. query concurrent requests. This account is not available in Production Environments. print styles. Database User BOLINF This responsibility grants read-only access to standard applications schema and objects and provides access to create. Production Environment. define printers. and Non-Production Environments. and drivers. administer Users. query concurrent programs. and value set values. There will be 2 accounts for SFTP: one for the Production Environment and one for the Non-Production Environment. This is for the protection of Customer‟s data and systems within Oracle‟s Data Center. query functions. administer folders. SFTP Oracle On Demand maintains a list of authorized system Users so requests for assistance can be verified against the list. Application Responsibility: Application setup responsibility System Administrator This account is not granted to Implementers or Customer Application Responsibility: Used by Oracle for advanced application functions such as updating the Production Environment with custom forms This account is not granted to Implementers or Customer Application User: Granted Application Administrator responsibility Application Developer BOL-SETUP For a limited time. and set profile options to administer Customer‟s application End Users. Database User RAC_ACCNT This responsibility grants Read-only database schema for the Production Support Environment. define request security group. On Demand does not provide access or troubleshoot Problems for individuals not on the authorized list. query concurrent executables. 17 . update. define application menus.  Responsibility Administer document sequences and categories. define flex fields. query Concurrent Managers. manage workflow processes and notifications. define concurrent programs. Database User APPS This access is granted for the sole purpose of testing steps and procedures that On Demand will perform in the Production Environment and Production Support Environment.

see the Oracle On Demand PowerBroker Access and Automated Password Management Manual. Access Type Concurrent Manager monitoring and management Environment Accessible? Comments  DEV= Yes  Function performed by Oracle On  PRODUCTION SUPPORT= No Demand for the Production Environment only  PROD= No  Developed by Customer in the  DEV=Yes Development Environment  PRODUCTION SUPPORT= No  FNDLOAD script provided for the Production Support Environment  PROD= No and the Production Environment  DEV=Yes  PRODUCTION SUPPORT=No  PROD=No  Developed by Customer in the Development Environment  FNDLOAD script provided for the Production Support Environment and the Production Environment Forms Registration Reports Registration Printer Configuration Application Administrator  DEV=Yes  Function performed by Oracle On  PRODUCTION SUPPORT=Yes Demand for all environments. 18 .The implementation team project manager should communicate changes to the list of authorized Users to On Demand as soon as changes occur.  PROD=Yes  DEV=Yes  This responsibility is available in  PRODUCTION SUPPORT=Yes all environments  PROD=Yes  Oracle On Demand Server Access For information about Oracle On Demand server access. Oracle On Demand does not allow Customer to modify base application tables. used by Customer‟s Implementer to perform application setup and any CEMLI testing Following Production Go-Live. and user identification required to perform various functions. Environment Non-Production (DEV) Production    Production Support (TEST)     Guidelines Used by Customer‟s Implementer developers for the development and unit testing of CEMLIs Used after setups have been tested and approved by Customer through User Acceptance Testing Becomes Customer‟s live Production Environment Prior to Production Go-Live. The following table describes the general guidelines for each type of environment. At Production Go-Live. all system access for Customer‟s Implementer is removed from the list of Authorized Users. system access types. used exclusively by Oracle for Change Management activities following Not built to scale to match performance of the Production Environment Primarily used for Change Management tasks and to test functionality The following table describes the general applications.

and any other non-host based print software be installed on Customer‟s premises. Oracle provides a web-based interface that enables Customer to set up necessary printer queues. configure. Customer-selected printers are set up before Oracle E-Business Suite is available for implementation. Most On Demand customers with more than five printers use a print server. Printing from Oracle E-Business Suite programs requires a variety of configuration and setup activities across several layers of the stack. Customer may require additional printers to be set up at the system level at a later time. Oracle On Demand recommends a print server that is located on Customer‟s site. printservers. Customer must verify that TCP/IP print services are installed and started on the printer server.2 Oracle On Demand and Operating System Printer Standards For @Oracle deployments.3 Operating System Printer Queue Setup For @Customer deployments. 5. Oracle supports print drivers that are supported by the Oracle EBusiness Suite programs. If using a Windows 2000 printer server (such as Optio or Evergreen). Oracle enables Customer to set up the operating system print queues with a self-service product called Print-Pro. TCP/IP print services are not part of the default installation for Windows 2000 and must be added. Customer is responsible for setting up print queues. Oracle requires that all printers. Customer may purchase such services.Section 5: Printing There are several key configuration tasks that are required to enable effective printing. The second task is to set up the operating system printer queues. Although Oracle Programs and Oracle On Demand enable the installation of third party drivers and fonts. 19 . At the time of publication of this document. For @Oracle deployments. and application level. Oracle E-Business Suite was certified and supported Hewlett Packard model PCL4 and higher postscript-based print drivers.1 Oracle On Demand and Print Servers If Customer has several printers or complicated print activities. Customer is responsible for all printer configuration and maintenance at the network. and end-printer. The third task is to configure and manage the application itself and the appropriate print server. 5. operating system. If Customer requires Oracle to install. The first task is to establish network connectivity between the appropriate environment. Customer manages Oracle print jobs through the self-service application. 5. and maintain printer queues on the managed system that are not supported by the web-based management interface. Refer to the Application Management Services for Oracle E-Business Suite Schedule for details of the key tasks involved. Print servers give Customer greater control of individual print jobs and enable a more centralized print management process. Customer is responsible for supporting this software. If Customer purchased Computer and Administration Services. If Customer purchased Administration Services. print server (if used).

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->