Integrating Oracle E-Business Suite Release 12 with Oracle Access Manager 11gR1 PS2 (11.1.1.7.0)

Integrating Oracle E-Business Suite Release 12 with Oracle Access Manager 11gR1 PS2 (11.1.1.7.0) using Oracle E-Business Suite AccessGate (Doc ID 1543803.1)

Integration of Oracle E-Business Suite 12.2 with Other Products

Oracle E-Business Suite Setup Guide Release 12.2 Part Number E22953-09 Integration of Oracle E-Business Suite with Other Products Oracle E-Business Suite can be integrated with other Oracle products. This chapter highlights some of the key integration points. Linking to Application Development Framework Applications You can link to an Application Development Framework (ADF) application from the Oracle E-Business Suite home page, regardless of how or if the ADF application integrates with Oracle E-Business Suite data on the back end. For more information on using ADF applications with Oracle E-Business Suite, see E-Business Suite Application Development using Oracle Application Framework (OAF) and Application Development Framework (ADF), My Oracle Support Knowledge Document 563047.1. Integrating Oracle E-Business Suite with Oracle Access Manager using Oracle E-Business Suite AccessGate Oracle E-Business Suite supports authentication of application users using Oracle Access Manager through the Oracle E-Business Suite AccessGate application. Oracle E-Business Suite AccessGate is a Java EE application that is deployed to a WebLogic Server instance, and works in conjunction with Oracle Access Manager and Oracle Internet Directory (OID) to enable single sign-on capabilities for your entire enterprise. This application is currently targeted primarily at customers who have already deployed Oracle Access Manager in other organizations within the company, and who wish to extend the authentication capabilities of Oracle Access Manager to Oracle E-Business Suite instances. More information can be found in Integrating Oracle E-Business Suite Release 12.2 with Oracle Access Manager 11g using Oracle E-Business Suite AccessGate, My Oracle Support Knowledge Document 1368292.1. Using AppsDataSource, Java Authentication and Authorization Service, and Utilities for Oracle E-Business Suite Oracle Application Object Library added new standard Java datasource and Java Authentication and Authorization Service (JAAS) features, plus extended error logging routines, to Oracle E-Business Suite in Patch 8571001. These features are meant for use with Java EE programs deployed in application servers on external nodes; that is, nodes other than those where Oracle E-Business Suite middle tier is installed. These are lightweight implementations that can be used on an external application server without needing to install an entire Oracle E-Business Suite instance on the application server machine. For more information, see: Oracle E-Business Suite Software Development Kit for Java (includes AppsDataSource, Java Authentication and Authorization Service, session management) Readme - Patch 13882058, My Oracle Support Knowledge Document 974949.1. Using Oracle GoldenGate with Oracle E-Business Suite for Operational Reporting You can use Oracle GoldenGate with Oracle E-Business Suite for operational reporting, in which selected tables are replicated from the primary Oracle E-Business Suite database to a secondary (duplicate) instance. This enables read-intensive, custom reports to be run without using resources on the primary Oracle E-Business Suite database. For more information, see: Deploying Oracle GoldenGate to Achieve Operational Reporting for Oracle E-Business Suite, My Oracle Support Knowledge Document 1112325.1. Autovue Document Print Service with File-Type Attachments Attachments are fully integrated with Oracle's AutoVue Document Print Service, allowing users to print their file-type attachments. This integration also allows an enterprise to support the printing of attachments of different file types from a server where the Auto Document Print Service is configured, without having to install or configure additional software to view and print files in client/server machines. Note: Oracle E-Business Suite Release 12.2 integration with AutoVue Document Print Service is certified with Oracle AutoVue Release 20.1.1. In the Attachments feature user interface, a Print icon is available in the Attachments list for file-type attachments. Users can select the Print icon to print the file. Users can use this feature only when the file-type attachment is committed to the database. If the Automatic Save property of an attachment region item is set to False, a user must explicitly commit the transaction of any newly-added file attachment first. This feature is enabled through the profile option FND Attachment AutoVue Server. For more information, see the Oracle Application Framework Developer's Guide available from My Oracle Support Document 1315485.1.

Integrating Oracle E-Business Suite Release 12.2 with Oracle Access Manager 11gR1 (11.1.1.5.0) using Oracle E-Business Suite AccessGate (Doc ID 1368292.1)

Integrating Oracle E-Business Suite Release 12.2 with Oracle Access Manager 11gR1 (11.1.1.5.0) using Oracle E-Business Suite AccessGate (Doc ID 1368292.1)

Oracle E-Business Suite 12.2 Architecture

Oracle E-Business Suite 12.2 Architecture There are lots of updates coming in this release, but from a technology stack perspective, EBS 12.2 will be notable for two things: 1.Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g 2.Online Patching support via 11gR2 Edition-Based Redefinition Oracle E-Business Suite 12.2 Technology Highlights: 1. Latest middleware: Fusion Middleware 11g. 2. WebLogic Server to replace Fusion Middleware 10g Oracle Containers for Java (OC4J) Latest database: Oracle 11gR2 11.2 Database Online patching via Edition-Based Redefinition Improved performance via database result caching. Functionality uses native 11gR2 Features that allow online application Upgrade with uninterrupted Availability of the application • Patches can be applied while theproduction system is fully operational • Only a short downtime is required tocomplete patching process The amount of downtime required by Any patch will be more predictable Oracle E-Business Suite 12.2 Technology Highlights Enhanced user interface: Home page improvements New slide-out navigator Personalization improvements AutoVue print services for attachments Performance enhancements: Workflow RAC Affinity Result set caching for profiles

Weblogic 11g Change to Production mode from Development mode

Change to production mode All servers in a domain run either in development mode or production mode. In general, production mode requires you to configure additional security features. For information on the differences between the two modes, refer to "Creating a WebLogic Domain" in Creating WebLogic Domains Using the Configuration Wizard. To configure all servers in a domain to run in production mode: 1.If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center). 2.In the left pane of the Console, under Domain Structure, select the domain name. 3.Select Configuration > General and select the Production Mode check box. 4.Click Save, and then, to activate these changes, in the Change Center, click Activate Changes. 5.Shut down any servers that are currently running. See Start and stop servers. 6.Invoke the domain's startWebLogic script. See Starting an Administration Server with a Startup Script. The Administration Server starts in the new mode. 7.If the domain contains Managed Servers, start the Managed Servers. Result As each Managed Server starts, it refers to the mode of the Administration Server to determine its runtime mode. Note: Once you have changed to production mode, whether by using a start command argument, the Console, or WLST, you cannot change back to development mode without restarting the server.

Weblogic Server 11g Development Mode Vs Production Mode

Weblogic Server Development Mode Vs Production Mode While configuring any Weblogic domain the there are two modes the domain can be configured with. - Development Mode - Production Mode The question is how to decide which mode to use: Let’s say you are developing your applications. The process will involve multiple redeployments to the server. In this case you would wish for a relaxed security configuration on the server. Also you would wish for features like auto deployment of your code. In such scenarios use the Development Mode. Now consider you got your application working right, ready to go live. In this mode you would definitely wish for a full fledged security. Consider using the Production Mode here. The differences between the two modes are stated below: 1. SSL In development mode you can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL where as in Production Mode you should not use the demonstration digital certificates and the demonstration keystores. If you do so, a warning message is displayed. 2. Application DeploymentIn Development Mode WebLogic Server instances can automatically deploy and update applications that reside in the domain_name/autodeploy directory (where domain_name is the name of a domain) where as in Production Mode the auto-deployment feature is disabled, so you must use the WebLogic Server Administration Console, the weblogic.Deployer tool, or the WebLogic Scripting Tool (WLST).3. Lock And Edit Feature In Development Mode any configuration change being done by a user doesn’t need him to take a Lock and Edit session, where as in Production Mode the user needs to procure a Lock and Edit session before trying to make any configurational changes. Important Considerations: ü It is recommended that this method be used only in a single-server development environment.ü You can always switch the domain startup mode from Development to Production and Vice Versaü Oracle recommends usage of JRockit instead of Sun JDK in Production Mode. This recommendation depends on platform on which your domain runs. For platforms like Solaris SunJDK is recommended even in Production Mode. JRockit works well on OEL/Red hat Linux platforms. 

OBIEE 11g Configuration Files

OBIEE Logs and Configuration files bi_server1.log & bi_server1-diagnostic.log (bi_server1.out & access.log are also captured in this directory) [$FMW_HOME]/user_projects/domains/bifoundation_domain/servers/bi_server1/logs nqserver.log & nqquery.log [$FMW_HOME]/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplication_obis1 sawlog.log [$FMW_HOME]/instances/instance1/diagnostics/logs/OracleBIPresentationServicesComponent/coreapplication_obips1 NQSConfig.INI & DBFeatures.INI [$FMW_HOME]/instances/instance1/config/OracleBIServerComponent/coreapplication_obis1 instanceconfig.xml & credentialstore.xml [$FMW_HOME]/instances/instance1/config/OracleBIPresentationServicesComponent/coreapplication_obips1 config.xml [$FMW_HOME]/user_projects/domains/bifoundation_domain/config system-jazn-data.xml [$FMW_HOME]/user_projects/domains/bifoundation_domain/config/fmwconfig