Certain tasks are necessary to finish all installations for Oracle E-Business Suite. There are also other tasks that are required only for systems with specific functionality. You must complete all tasks marked as required. You should also complete any tasks marked as conditional that apply for your instance, or that are necessary to meet your site or product-specific requirements.
This chapter covers the following topics:
Immediately after the successful installation of the 12.2.0 file system using the latest StartCD, you must apply the latest application tier technology patches to the run file system. After the release of the startCD, new required patches may have been discovered, so it is important to perform this step.
Required Action: Follow the instructions in Section 1.5, Apply latest application tier technology patches to run file system, Oracle E-Business Suite Release Notes, Release 12. (Doc ID: 1320300.1).
Required Action: Follow the instructions in the Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID: 1594274.1) to do the following:
Check for missing database patches by executing the Oracle E-Business Suite Technology Codelevel Checker (ETCC) checkDBPatch.sh script.
Apply the latest database patches identified in the report as missing.
Confirm successful application of the required database patches by re-executing the Oracle E-Business Suite Technology Codelevel Checker (ETCC) checkDBPatch.sh script.
Required Action: Follow the instructions in Section 2.2, Apply Consolidated Seed Table Upgrade Patch, Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID: 1320300.1).
Important: None of the application tier services should be up until you upgrade to the latest Oracle E-Business Suite Release Update Pack for Release 12.2 as described in the following section. Only the WebLogic AdminServer services can be brought up as part of applying the latest AD and TXK Release Update Packs, as mentioned in their readme documents. The AdminServer in turn brings up NodeManager.
Required Action: Follow the instructions in Oracle E-Business Suite Release 12.2: Suite-Wide Release Update Pack and AD/TXK Delta Information (Doc ID: 1583092.1) to apply the latest AD and TXK patchsets.
The 12.2 Release Update Pack (RUP) is a thoroughly tested release pack that combines patches created across the Oracle E-Business Suite after the initial release of Oracle E-Business Suite Release 12.2.
Required Action: You must apply the latest Oracle E-Business Suite Release Update Pack. Follow the instructions in E-Business Suite RUP, AD and TXK RUP Information, Release 12.2 (Doc ID: 1583092.1).
Ensure that you complete the post-upgrade steps described in the Oracle E-Business Suite Release Update Pack Readme specific to the Oracle E-Business Suite Release Update Pack (RUP) that you applied.
Required Action: For example, if you upgrade to Oracle E-Business Suite Release 12.2.7, then you must complete all post-upgrade steps described in Oracle E-Business Suite Release 12.2.7 Readme (Doc ID: 2230783.1).
Oracle highly recommends that you apply the latest critical patch update to your Oracle E-Business Suite environment.
Required Action: Go to the Critical Patch Updates, Security Alerts and Third Party Bulletin web page located at: https://www.oracle.com/technetwork/topics/security/alerts-086861.html
From this page, go to the latest Critical Patch Update page and select the link to Oracle E-Business Suite. From this page, select the link to the Oracle E-Business Suite MOS Note for the current CPU. Review and apply the CPU patches according to the referenced MOS note.
Oracle highly recommends that you enable TLS. You must apply the prerequisite patch requirements to enable TLS.
Required Action: Review the prerequisite patch requirements in Enabling TLS in Oracle E-Business Suite Release 12.2 (Doc ID: 1367293.1), Section 5.1 for TLS 1.2 with Backward Compatibility, and Section 6.1 for TLS 1.2 Only. Apply all required patches and prerequisites to enable TLS.
Note: You will perform the TLS configuration in the Performing Secure Configuration section later in this chapter.
Suggested Reading: Additional information regarding the use of Patch Wizard is available in Oracle E-Business Suite Releases 11i and 12.x: Required Updates for Patch Wizard (Doc ID: 1267768.1)
From the Oracle E-Business Suite Login page, you can access the Oracle E-Business Suite Home Page, which provides a single point of access to HTML-based applications, forms-based applications, and Business Intelligence applications. You access the Oracle E-Business Suite Login page from the following URL:
http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLogin
Once the connection has been made, the Oracle E-Business Suite Login page appears. Enter a suitable username and password. For example, SYSADMIN is a privileged account that has System Administrator responsibility. You were required to specify your choice of password for this account on the Application User Information screen in Rapid Install.
After entering the account name and password, click Login.
Oracle E-Business Suite Login Page
After your credentials have been validated, the Oracle E-Business Suite Home Page Oracle appears. From this page you can access responsibilities for any of the individual Oracle E-Business Suite products your organization has licensed.
Oracle E-Business Suite Home Page
The system administrator should log in using the SYSADMIN account mentioned above, and use the System Administrator responsibility to launch an Applications Forms session and perform further implementation steps.
Additional Information: See Oracle E-Business Suite Security Guide for details.
Oracle recommends changing the default passwords for the accounts shown on the Application User Information screen. If you did not do so during the installation, you can still change the passwords once installation is complete.
The default passwords for the SYSTEM and SYS accounts for the Oracle E-Business Suite database are manager and change_on_install, respectively. To maintain database security and restrict access to these accounts, you should change these passwords, ensuring that your choices meet your organization's security requirements. The password for both SYS and SYSTEM in the Vision Demo is manager.
You should also change the default passwords for the Oracle E-Business Suite product accounts in your production and test databases.
Additional Information: See Applications DBA Duties, Oracle E-Business Suite Maintenance Guide.
Logged in as the SYSADMIN user, you should change the passwords for the following application user accounts:
The GUEST user will still have the default password, which can be changed if needed.
When configuring an Oracle E-Business Suite domain in Oracle WebLogic Server, you may after some minutes encounter a timeout when the
txkEBSDomainConfig.pl deployment script is being run either automatically by Rapid Install or manually by a user:
NMProcess: INFO: Plain socket listener started on port 5556, host myhost.example.com ERROR: Unable to startup the Admin Server. Cannot proceed with the deployment of EBS. Creation and deployment of E-Business Suite domain completed. EBS deployment failed! Error code=1.
If such a timeout occurs, you can resolve it by changing the value of the
s_adminservertimeout context variable as described in the steps listed below. This variable has a default value of 1000 seconds. The new value needed will depend on the performance of the machine where the script is being executed.
Check for available memory and clear the cached memory.
Using Oracle Applications Manager, change the value of
s_adminservertimeout from 1000 to 3000.
Note: Do not run AutoConfig.
Stop all application tier services.
Delete the WLS domain that was not successfully created.
Run the deployment scripts again.
If the error recurs, repeat steps 2-5, this time specifying a value of 6000 for
In the database tier context file, check that the values of the context variables
s_archive_dest are each set to the appropriate directory where the database files are located. Also, check that the context variable
s_base is set to the appropriate location. If necessary, update the database tier context file to set these variables correctly.
AutoConfig is a tool that simplifies and standardizes configuration management tasks in an Oracle E-Business Suite environment. A fresh install of Release 12.2 includes AutoConfig as a standard and required configuration management tool.
Refer to the Technical Configuration chapter of Oracle E-Business Suite Setup Guide for more information about running AutoConfig.
Multiple signatures in JAR files may result in security warnings, for example when launching forms. If you are performing a new installation, you must create your own signature, and then use the adadmin utility to force regeneration of all JAR files.
The current init<SID>.ora default settings allow for a maximum of 100 connections. However, after the standard setup is complete, only a few users can be connected because of the connections used by the concurrent managers, AQ workers, and job queues.
The relevant database initialization parameters are listed in My Oracle Support Knowledge Document Note 396009.1, Database Initialization Parameters for Oracle Applications Release 12. Refer to this document when planning to update parameter settings to meet the specific requirements of your system.
The temporary directory on your database server for log and output files from PL/SQL concurrent programs is set to /usr/tmp (UNIX) or C:\TEMP (Windows) by default. This value is defined as a database directory for PL/SQL file I/O, and assigned to the APPLPTMP environment variable. As the temporary files placed in this directory may contain sensitive information, it should have suitably restricted access, such as read and write access for the account that owns the database.
Define the directory you want to use as a database directory for PL/SQL file I/O. See My Oracle Support Knowledge Document 2525754.1, Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2.
Then use the edit AutoConfig parameters feature of Oracle Applications Manager to update the APPLPTMP variable in the Applications context file with the database directory location. Finally, run AutoConfig to recreate the environment files.
Depending on which products or country-specific functionality you plan to use in your installation, you may need to perform additional tasks or apply additional patches. Refer to the individual product or country-specific implementation manuals or user's guides for details.
Additional Information: For a list of Web browsers supported for use with Oracle E-Business Suite Release 12, see My Oracle Support Knowledge Document 389422.1, Recommended Browsers for Oracle Applications 12.
Instead of using the browser's own JVM, Oracle E-Business Suite Release 12 uses the Sun Java Runtime Engine (JRE). This component is invoked when a user accesses a function that requires it, such as running a form. If the JRE Plug-in has not already been installed, the browser prompts the user to download the required installation executable. JRE replaces Oracle JInitiator, which was used in Release 11i.
Additional Information: For further details of using JRE with Oracle E-Business Suite, see My Oracle Support Knowledge Document 393931.1, Upgrading JRE Plugin with Oracle Applications R12.
At the command prompt, enter:
$ lpstat -p
Click on Printers and Faxes in the Start menu.
The concurrent manager starts by default under the internal SYSTEM account. This account does not have access to network printing devices. To run reports using the concurrent manager, complete the following steps:
Log in to a user account that has administrative privileges.
From the Services menu, highlight the Oracle Concurrent Manager service (OracleConcMgr<SID>, where <SID> is the database SID), and click Startup. In the Log in As section, select This Account, and enter the username and password used to start the concurrent manager. Then click OK.
Repeat the actions in Step 2 for the Oracle TNS Listener service.
Using the Add Printer option, define a printer for the account that was used in Steps 2 and 3.
Reboot the system to allow the changes to take effect.
Additional Information: For more information about setting up printers, see Chapter 6, Setting Up Printers, in Oracle E-Business Suite Setup Guide.
Refer to the Oracle E-Business Suite Setup Guide and Oracle E-Business Suite Maintenance Guide for information about system administration and maintenance tasks, as well as the associated tools and utilities.
Required Action: Deploy your customizations following the instructions in Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID: 1577661.1), Section 1.5, Deploying Custom Application Tier Objects.
Installing Oracle E-Business Suite Release 12.2 is performed with a single application tier node and a single database node even if you are using Oracle RAC. Scaling the environment is a post-install task. Now that the installation is complete, you can scale your environment according to production-level requirements by adding managed servers within an application tier node, adding application tier nodes, and adding database Oracle RAC nodes.
By default, every application tier node contains only a single instance of the oacore, oafm, forms and forms-c4ws services. If more instances of a particular service are required on an application tier node, you can create new managed servers.
Conditional Action: If you need to add additional managed servers in an application tier node, follow the instructions in section 4.4.1, Adding a new managed server, in Managing Configuration of Oracle HTTP Server and Web Application Services in Oracle E-Business Suite Release 12.2 (Doc ID: 1905593.1).
Conditional Action: If you need to add additional application tier nodes, then configure load balancing as described in Using Load-Balancers with Oracle E-Business Suite Release 12.2 (Doc ID: 1375686.1).
When deploying multiple application tier nodes for an Oracle E-Business Suite environment, you can use a shared application tier file system or replicate the file system on every node in the environment.
Tip: Oracle highly recommends that you use a shared application tier file system.
When directed in Using Load-Balancers with Oracle E-Business Suite Release 12.2 (Doc ID: 1375686.1), follow the steps in one of the following notes to create a new application tier node:
To create the shared application tier file system and add new application tier nodes, follow the steps in Sharing The Application Tier File System in Oracle E-Business Suite Release 12.2 (Doc ID: 1375769.1).
If you are using a distributed file system, then follow the steps in Cloning Oracle E-Business Suite Release 12.2 with Rapid Clone (Doc ID: 1375769.1) to add new application tier nodes.
Conditional Action: If you are adding additional database tier nodes to Oracle Real Application Clusters (RAC) to meet scalability or high availability requirements, then follow the steps in Oracle E-Business Suite Release 12.2: Adding or Deleting 11gR2 Oracle RAC Nodes (Doc ID: 1570554.1).
Conditional Action: If you need to configure Oracle E-Business Suite Release 12.2 for access from the internet, then review and follow the steps in Oracle E-Business Suite Release 12.2 Configuration in a DMZ (Doc ID: 1375670.1).
Conditional Action: If you need to create a disaster recovery site, then review and follow the steps in the appropriate document for your system:
Business Continuity for Oracle E-Business Suite Release 12.2 Using Oracle 12c (220.127.116.11) Physical Standby Database (Doc ID: 1963472.1)
Business Continuity for Oracle E-Business Suite Release 12.2 Using Logical Host Names with an Oracle 12c Physical Standby Database (Doc ID: 2246690.1)
Business Continuity for Oracle E-Business Suite Release 12.2 Using Oracle 11g (11gr2) Physical Standby Database (Doc ID: 1491855.1)
Conditional Action: If you need to create a reporting environment, then review and follow the steps in Using Active Data Guard Reporting with Oracle E-Business Suite Release 12.2 and an Oracle 11g or 12c Database (Doc ID: 1944539.1).
The database and file system architecture of Oracle E-Business Suite Release 12.2 are designed to support Online Patching. Integrations with Oracle E-Business Suite must comply with Oracle E-Business Suite deployment and development standards in order to work correctly with Oracle E-Business Suite Release 12.2. Examples include custom and third-party integrations, as well as integrations with other Oracle products such as Oracle Application Express.
Additional Information: Refer to Guidance for Integrating Custom and Third-Party Products With Oracle E-Business Suite Release 12.2 (Doc ID: 1916149.1).
If you plan to use external integrations that require updates to meet certification requirements with Oracle E-Business Suite Release 12.2 or require additional steps to deploy, then perform those actions now. Validate all external integrations once the necessary steps have been performed.
You will need to increase the size of your database to meet the specific requirements of your system. The increase will in part depend on the products you have licensed and the additional features (such as multiple languages or multiple organizations) you configure in your installation.
Conditional Action: If you chose to enable load balancing for concurrent processing servers during the Rapid Install process, you must complete additional setup steps. See Managing Parallel Concurrent Processing. Oracle E-Business Suite Setup Guide.
By default, Oracle E-Business Suite Release 12.2.0 supports Oracle Forms 10g in servlet mode, which facilitates use of firewalls, load balancing, proxies, and other networking options. The use of socket mode is also supported, however, and can be enabled by following the instructions in My Oracle Support Knowledge Document 384241.1, Using Forms Socket Mode with Oracle E-Business Suite Release 12.
Conditional Action: If you plan to use languages other than American English, you must first complete the applicable steps for installing the translated software for National Language Support (NLS) as listed in My Oracle Support Knowledge Document 1314621.1, Oracle E-Business Suite NLS Release Notes, Release 12.2.
To use additional languages, you must first activate the additional languages via the License Manager utility, and then change the base language if required.
After this, the multilingual tables must be updated for the activated languages. Go to the AD Administration main menu, choose the 'Maintain Applications Database Entities' submenu, and run the 'Maintain Multi-lingual Tables' task.
Additional Information: For more information about using License Manager, see License Manager, Oracle E-Business Suite Maintenance Guide. For more information about the AD Administration utility, see Applications DBA System Maintenance Tasks and Tools, Oracle E-Business Suite Maintenance Guide.
You now need to install the relevant NLS software for all the active languages, to lay down the NLS translated files into the APPL_TOP.
After this, you should use the Translation Synchronization Patch Utility to synchronize the languages with the American English patch level. This step is needed in case any American English patches were applied after Rapid Install was run.
Regardless of the languages installed, you may need to complete additional steps if you use a supported Unicode character set, such as AL32UTF8, in the database tier. In addition, be aware that supplementary characters are not supported.
If you customize seed data, your changes may be overwritten during an upgrade. This also applies to any changes to translations of seed data made using the globe icon.
Additional Information: See Oracle E-Business Suite Setup Guide for language setup details, and My Oracle Support Knowledge Document 393861.1, Oracle Applications Globalization Support Guide (Release 12), for further details of languages and character sets.
Before you can send Oracle Workflow email notifications and Oracle Alert email alerts, you must complete the Workflow Notification Mailer configuration, using the Notification Mailer configuration wizard in Oracle Applications Manager.
From the Applications Dashboard of Oracle Applications Manager, select Workflow Manager from the "Navigate to" pull-down menu, and click on the Go button.
In the Workflow System region, click the Notification Mailers status icon to navigate to the Service Components page for notification mailers. At this point, the Notification Mailers status icon should be showing the status Down.
In the Service Components page, select the Workflow Notification Mailer service component and click the Edit button to navigate to the Notification Mailer configuration wizard.
In the Outbound Email Account (SMTP) region, enter the name of the outbound SMTP mail server.
If you want to enable inbound email processing, select the Inbound Processing parameter in the Inbound Email Account (IMAP) region, and enter the name of the inbound IMAP mail server, the username and password of the email account that the Notification Mailer uses to receive email messages, and the reply-to address of the email account that receives incoming messages, to which notification responses should be sent.
Return to the Service Components page, and verify that the status of the Workflow Notification Mailer service component is now Running.
Additional Information: For more information, see Notification Mailers, Oracle Workflow Administrator's Guide.
To set up and implement the Discoverer End User Layer (EUL), follow the instructions documented in My Oracle Support Knowledge Document 1380591.1, Using Discoverer 11.1.1 with Oracle E-Business Suite Release 12.2.
Additional Information: See also Oracle E-Business Suite Support Implications for Discoverer 11gR1, My Oracle Support Knowledge Document 2277369.1.
Optional Action: To convert your system to use public sector, education, or not-for-profit products after the installation is complete, use License Manager to register public sector or not-for-profit products. See License Manager, Oracle E-Business Suite Maintenance Guide.
Optional Action: If you want to use the Multiple Organizations architecture in a production or test environment, follow the instructions in the Oracle E-Business Suite Multiple Organizations Implementation Guide.
Additional Information: For more information, see Multiple Organization Architecture, Oracle E-Business Suite Concepts.
Conditional Action: See Achieving Optimal Performance with Oracle E-Business Suite, My Oracle Support Knowledge Document 2125596.1.
After installation is complete, your operating system administrator should back up the Oracle E-Business Suite application tier product files, including the technology stack components. Your database administrator should back up the Oracle E-Business Suite database components.
Subsequently, you should establish a backup policy that meets your organization's needs, balancing the overhead of carrying out the chosen backup type and frequency against the need to be able to recover from a variety of types of system failure. The resulting backup and recovery procedures should be verified, then periodically tested to ensure continued applicability.
Review and Deploy Security Guidelines (recommended for all Oracle E-Business Suite releases)
Follow the Secure Configuration Guidelines
Tip: You must follow all recommended secure configuration guidelines as documented in the Oracle E-Business Suite Security Guide. At a minimum, Oracle recommends that you configure the following:
Allowed JSPs feature
TLS for inbound, outbound, and loopback connections
Action: Review and deploy the recommended security guidelines documented in Oracle E-Business Suite Security Guide, Release 12.2, Part 2: Secure Configuration.
Action: Follow the instructions in Enabling TLS in Oracle E-Business Suite Release 12.2 (Doc ID: 1367293.1) to encrypt inbound, outbound, and loopback connections.
Tip: If you have any computers requiring direct access to the database that are not registered nodes in AutoConfig, such as OAM clients, then you must explicitly grant access.
Execute the Security Check Scripts
Action: Regularly run the Security Check Scripts on your production instance to ensure that it is and continues to be in compliance with the recommendations in this document. For information on how to run the Security Check Scripts, see Security Configuration and Auditing Scripts for Oracle E-Business Suite (Doc ID: 2069190.1).
Tip: If you upgraded to Oracle E-Business Suite Release 12.2.6 or higher, then you can use the Secure Configuration Console on an ongoing basis to perform necessary checks on your environment.
Perform the following if you have upgraded to Release Update Pack 12.2.6 or higher (conditional):
Tip: After you apply Patch 24744399:R12.FND.C (a mandatory post requisite for R12.ATG_PF.C.Delta.6) or upgrade to Oracle E-Business Suite Release 12.2.7 Release Update Pack (which includes patch 24744399:R12.FND.C), your system will be locked down until a local system administrator resolves or acknowledges the recommended security configurations in the Secure Configuration Console.
Log in to Oracle E-Business Suite
Upon initial login as a local system administrator with the Functional Administrator responsibility, you are automatically directed to the Secure Configuration Console.
Resolve or acknowledge security configurations
You must now either resolve or acknowledge the recommended security configurations in the Secure Configuration Console.
Suggested Reading: Secure Configuration Console, Oracle E-Business Suite Security Guide, Release 12.2.
Manually add custom redirects and resources to configuration files (conditional)
The Allowed Redirects and Allowed Resources features are enabled by default after your upgrade to Oracle E-Business Suite Release Update Pack 12.2.6 or higher. Consequently, if you use custom redirects and resources, such as JSPs and servlets, in your environment, then you must manually add these to your configuration files for allowed redirects and allowed resources, respectively.
Additional Information: For more information, see Allowed Redirects, Oracle E-Business Suite Security Guide, and Allowed Resources, Oracle E-Business Suite Security Guide.