Skip Headers

Oracle E-Business Suite Installation Guide: Using Rapid Install
Release 12.2 (12.2.0)
Part Number E22950-16
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Performing an Installation

Rapid Install offers two options for a new installation: a standard installation, which involves creating a new system using system-specific configuration parameters, and an Express installation, where Rapid Install supplies default values for many parameters, requiring only a few to be supplied by the user carrying out the install.

This chapter covers the following topics:

Standard Installation

This section describes the setup steps for a standard installation, where the user supplies various system-specific parameters. An Express installation is described in Setting Up an Express Installation.

Follow the instructions in the section Before You Begin in Getting Started. Then complete the following tasks, which are grouped into logical sections.

Important: You need to carry out the relevant steps on every node that will be part of your Oracle E-Business Suite system: for example, a database node and two Applications nodes. Where applicable, operations should always be carried out on the database node first.

For important additional requirements and restrictions on order of deployment, refer to Step 11 later in this chapter on configuring Applications nodes.

Describe System Configuration

  1. Start the Rapid Install wizard

    Start the wizard from the command line by entering rapidwiz at the prompt. The Welcome screen lists the database and the technology stack components that are installed with Oracle E-Business Suite.

    Welcome Screen

    the picture is described in the document text

    This screen lists the components that are included in, or supported by, this release of Oracle E-Business Suite. You can expand the component lists, using the scroll bar to bring all the components into view.

    A new installation includes a fresh Oracle 11g Release 2 (11gR2) database. In an upgrade, Rapid Install can optionally create an Oracle 11gR2 database Oracle Home without a database. You can use this Oracle Home to upgrade or migrate your existing database to Oracle 11gR2. Alternatively, you can choose to use a suitable existing Oracle Home.

    Note: See Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2.0.

    This screen is for information only. No decisions need to be made. When you have reviewed the information, click Next to continue.

  2. Create stage area (conditional and optional)

    The next screen will appear if the stage area has not already been created by manual running of the script startCD/Disk1/rapidwiz/bin/buildStage.sh.

    the picture is described in the document text

    In most situations, creating the stage area will be the correct action, in which case click on Browse and specify the location. Otherwise, click on Next to proceed without creating the stage area.

    Note: You will not need to create the stage area if you are running Rapid Install simply to create a configuration file for later use.

    If you specify that you do want to create the stage area, a popup window like this will show the progress of the operation:

    the picture is described in the document text

    When the stage area is built, you can proceed with the installation.

  3. Select a wizard operation

    Use the Select Wizard Operation screen to indicate the action you want Rapid Install to perform. You begin both new installations and upgrades from this screen. Based on the action you choose, the Rapid Install wizard continues with the appropriate screen flow.

    Select Wizard Operation - Install Oracle E-Business Suite Release 12.2.0

    the picture is described in the document text

    The available actions are as follows:

    Using the following steps, you will set up a new installation. Choose Install Oracle E-Business Suite Release 12.2.0 and then click Next to continue.

  4. Supply email details for security updates

    Data collected is sent via HTTPS (secure HTTP) to Oracle Support, facilitating pro-active problem avoidance and helping to reduce the time needed for resolution of support issues.

    Supply Email Details for Security Updates

    the picture is described in the document text

    If submission of your details fails because no connection can be made, you are presented with a pop-up screen prompting for proxy server information:

    Specify Proxy Server [Shown After Failed Connection Attempt]

    the picture is described in the document text

    If this screen appears, respond appropriately and then click OK.

  5. Identify configuration file

    On the Configuration Choice screen, you indicate whether you will be using previously saved configuration details.

    Configuration Choice

    the picture is described in the document text

    If you choose Create a new configuration , Rapid Install saves the configuration parameters you enter on the wizard screens in the Oracle E-Business Suite database, and in a configuration file (conf_<SID>.txt), which is stored in your system temporary directory until the installation is completed.

    If you choose Load the following saved configuration, the database connect string field becomes active. For a configuration stored in the database, this field is made up of <hostname>:<SID>:<database port>, for example server1.example.com:VIS:1521.

    Important: The host name must include the domain.

    Enter the appropriate database connect string (or conf_<SID>.txt file location, if applicable) to point Rapid Install to a stored configuration whose parameters you wish to use. Typically, you would choose this option when performing a multi-node install..

    Note: If Rapid Install is being run on the database tier using the Load the following saved configuration option, you must enter the default password for the APPS database user.

    After completing this step, click Next to continue.

  6. Specify Global System Settings

    On the Global System Settings screen, you indicate whether you want to accept the default port values. You can specify a Port Pool setting to enable multiple Oracle E-Business Suite environments to co-exist on the same machine.

    For example, if you select an increment of 3 from the Port Pool list, the values in the Derived Port Settings will reflect this choice. Use the scroll bar or click Advanced Edit to see the Port Values screen.

    Global System Settings

    the picture is described in the document text

    The default value of the Port Pool set is zero, but you can customize it by selecting another value from the drop-down list in the Port Pool field. There are 100 port pool selections: if you select an increment of 3, the default values are increased by that value. The Database Port (1521) becomes 1524, the RPC Port (1626) becomes 1629, and so on.

    At this point, you can simply accept the values for the chosen Port Pool (and therefore individual ports) by clicking Next. This will suffice for many installations.

    Otherwise, you can add an extra level of sophistication by specifying individual port values to meet particular site-specific requirements, over and above the basic use of the Port Pool mechanism described above. For example, you might wish to avoid using a particular port for some reason, perhaps because it will be needed by some other software. Clicking on the Edit Ports button will open a screen that allows you to specify the values of any ports you wish.

    Port Values

    the picture is described in the document text

    When finished on this screen, click OK to return to the Global System Settings screen, and click Next on that screen.

  7. Define Database Node Configuration

    On the Database Node Configuration screen, indicate the kind of database you want to install in the new system, the name you will use to identify it, the machine on which it will run, and that machine's domain name. You then need to confirm the operating system shown on the drop-down list is correct, specify the Oracle user's operating system account name and group, and finally specify the base directory under which the installation is to take place.

    Database Node Configuration

    the picture is described in the document text

    You can install either a fresh database or a Vision Demo database.

    In this example, use the Database Type drop-down list to select a fresh database. Accept the default database name or type in another name (alphanumeric, not to exceed 8 characters in length, with no spaces) for the local instance. This name is often referred to as the database SID.

    The Database Install Information screen prompts you for information Rapid Install needs to set up and install the database.

    The Base directory field defaults to a sample directory name, using the operating system syntax for the machine where you started the Rapid Install wizard. This directory is the top-level directory that Rapid Install uses to derive the mount points associated with the RDBMS.

    The Database OS User is the account that will own the database technology stack and file system. Enter the name of the Database OS Group. The Database OS User may belong to other groups, but it must belong to this group.

    If you wish to browse the file system for suitable base directories, click the applicable Browse button to open a navigation window.

    Choose Directory

    the picture is described in the document text

    On this screen, click on a suitable folder, or type a path in the Directory field. Click OK to confirm your choice and return to the Database Node Configuration screen, or click Cancel to return without making a selection.

    As well as letting you specify the type of storage where the database files will reside, the Database Node Configuration screen enables you to specify whether this database node will be part of an Oracle Real Application Clusters (Oracle RAC) system.

    Important: Before you can perform an Oracle E-Business Suite installation on Oracle RAC, you must have the necessary Oracle Grid infrastructure in place. For more information on this, refer to the appropriate documents for your platform.

    If you wish to install Oracle E-Business Suite on Oracle RAC out of the box, you must tick (check) the RAC checkbox. You can then select the desired nodes in the popup window that appears when you click the RAC Nodes button.

    Important: The setting of the compatible database initialization parameter must be the same for both the Oracle E-Business Suite database.and the ASM instance and ASM disk groups. The Oracle E-Business Suite database parameter is set to 11.2.0 for all platforms except Exadata, where it is set to 11.2.0.2.

    Oracle RAC installation on more than one server can be acomplished either by having an Oracle Home on each of the individual servers, or by using a shared Oracle Home. When you select the RAC checkbox, the Shared Oracle Home checkbox will become available for ticking. Do so if you want the Oracle RAC installation to use shared Oracle Homes. Leave it unticked if you want to use individual Oracle Homes.

    After completing this screen, click Next to continue.

  8. Select product license type (Fresh Database installation only)

    When installing a fresh database (not a Vision demo database), the wizard prompts you to indicate the type of licensing agreement you have purchased from Oracle. It then presents the appropriate licensing screen.

    Completing a licensing screen does not constitute a license agreement. It simply registers your products as active. The only way to set up a license agreement is to purchase Oracle E-Business Suite products through the Oracle Store or an Oracle sales representative. You should have complete information about your product license before you complete the licensing screens.

    Select Licensing Type

    the picture is described in the document text

    Rapid Install installs all products regardless of their licensed status. However, you must register products you have licensed so that they are flagged in the system as active. An active flag marks products for inclusion in patching and other tasks that you will perform to update and maintain your system after the initial installation.

    Note: Rapid Install automatically installs and registers shared and dependent products for you.

    You can register products using either the Suite license model or the Component license model. Complete only one of these licensing screens, to match your licensing agreement.

    If you clicked the Suite licensing option on the Suite Selection screen, the Licensing Page for that option appears.

    License Additional Products

    the picture is described in the document text

    This licensing model allows wide access to Oracle E-Business Suite functionality. By choosing it, you tell Rapid Install to automatically register all products included in the Oracle E-Business Suite price bundle. The products that are checked and grayed are licensed automatically as a part of the suite. The ones that are not must be registered separately as additional products — they are not part of the E-Business Suite price bundle. Place a check mark next to any additional products you have licensed and want to register.

    If you clicked the Component licensing option on the Suite Selection screen, the Licensing Page for that option appears.

    License Products

    the picture is described in the document text

    Choose this option if your licensing agreement is for individual Oracle E-Business Suite component products. These products are licensed based on the number of authorized users or on the number of business transactions processed. All individual products are listed on this screen. Products that are grayed out cannot be selected unless the "parent" component is selected.

    Note: To register additional products after the initial installation, use the License Manager component of Oracle Applications Manager. For more details, see License Manager in Oracle E-Business Suite Maintenance Guide.

    Complete the appropriate licensing screen and click Next to continue.

  9. Select Country-Specific Functionality (Fresh Database installation only)

    Some systems require the country-specific functionality of a localized Oracle E-Business Suite product. For example, if your company is based in the United States but also operates in another country, products such as Human Resources require additional features to accommodate the labor laws and codes that differ from those in the United States. You register the name of the region associated with the localized product on the Select Country-specific Functionalities screen.

    If your company operates only in the United States, you can bypass this screen. If you begin doing business in another country at a later date, you can use License Manager to register the associated region at any time after the original installation or upgrade.

    Select Country-Specific Functionalities - Initial Screen

    the picture is described in the document text

    All the country-specific functionalities that Oracle supports are listed on this screen, arranged alphabetically. Double-click a region in the Available Regions box to move it into the Selected Regions box or highlight it and click the right arrow (>). To deselect a region, highlight it and double-click or click the left arrow (<) to remove it from the Selected Regions box.

    For example, if you select Canada, the screen would look like this.

    Select Country-Specific Functionalities - Subsequent Screen

    the picture is described in the document text

    To select or deselect all the regions and move them between boxes in a single action, use the relevant double arrows, >> or <<.

    After making your selection, click Next to continue.

  10. Select Internationalization Settings (Fresh Database installation only)

    American English is the only language installed in your system by default. However, Oracle E-Business Suite supports numerous other languages. These can be activated using License Manager (part of Oracle Applications Manager), and installed after the initial Release 12.2.0 installation is complete.

    Note: For further details, refer to Oracle E-Business Suite Maintenance Guide.

    Select Internationalization Settings

    the picture is described in the document text

    The languages you select help determine the available options for the other NLS-related configuration parameters (such as territory and character set) that your system requires and can support.

    Note: See Globalization Support in Oracle E-Business Suite Concepts.

    Double-click a language in the Available Languages box to move it into the Selected Languages box or highlight it and click the right arrow (>). Highlight a language in the Selected Languages box and click the left arrow (<) to remove it. To select or deselect all languages in a single action, use the double arrows, >> or <<.

    Note: You cannot remove American English from the Selected Languages box.

    Languages are no longer licensed using Rapid Install; instead, use License Manager (part of Oracle Applications Manager) to license languages. To install new languages after Rapid Install is complete, refer to Oracle E-Business Suite Maintenance Guide.

    Click Next to continue.

    The NLS language and territory settings are stored as profile options in the database. They are configured at the site level when you run Rapid Install. The base language is used for the default language setting and the default territory is used for the territory profile option. Users inherit these values the first time they log in via the Oracle E-Business Suite Home Page.

    The base language defaults to American English. If you choose additional languages on the Select Additional Languages screen, they appear in the Selected Languages box.

    Rapid Install does not set RDBMS date and numeric formats during installation. It uses default formats based on the territory profile setting (as derived from NLS_LANG). The Default Territory is AMERICA at the site level. Enter a new value, as needed, based on your user requirements.

    The "Database character set" and the "APPL_TOP character set" drop-down menus initially show US7ASCII as the default character set. Other compatible character sets are listed as well.

    Note: AL32UTF8 is the default character set for the Vision Demo database and the APPL_TOP. You cannot convert either of these character sets. Additional setup steps may be required for systems with fresh install databases that will use AL32UTF8. See Set Up Unicode Character Sets in Finishing Tasks for details.

    If you selected an additional language, the character set choices will change to include only those that are compatible with both American English and the additional languages selected.

    If you want to change the character set in either the database or the APPL_TOP, select a new value from the drop-down list.

    Caution: Any languages you plan to install after Rapid Install is complete must be compatible with the character set of your Oracle E-Business Suite system.

    The IANA (Internet Assigned Numbers Authority) character set is the Internet-assigned standard character set name used by the Web server. See http://www.iana.org/assignments/character-sets for more information.

    You can change this value, as needed. Complete the appropriate fields on this screen, and click Next to continue.

  11. Enter Primary Applications Node Information

    You have already specified the top-level directory for the RDBMS. Now you must specify top-level directory and subdirectories associated with the Applications nodes.

    Special Considerations for Multi-Node Installs

    When performing a multi-node install (using the conf_<SID>.txt file), the first application tier node to be specified (primary Applications node) must be installed first, because Oracle WebLogic Administration Server must be running on this node before installation can be performed on any secondary nodes. The primary node will also be the node where the Web Entry services run (these services cannot be disabled).

    Note: The same platform must be used for all Applications nodes.

    During the initial installation process,Web Entry Point Services and Web Application Services cannot run on secondary Applications nodes. After the installation has been completed, Web Entry Point Services can be enabled on secondary Application nodes if desired.

    Note: The following additional step is required on Windows only.

    After all secondary Applications nodes are installed, you must go back to the primary node and run the following command:

    $ perl %AD_TOP%\bin\adRegisterWLSListeners.pl -contextfile=<context file>
    

    This only needs to be done on File System 1 (fs1). There is no need to restart any services after running this command.

    Primary Applications Node Configuration - UNIX

    the picture is described in the document text

    The default sample directories use the syntax of the operating system where you started Rapid Install. In addition, some of the fields are operating system-specific.

    The above example shows this screen for a Linux system, where you need to complete the information for Apps OS User (the account that owns the Applications tier file system and technology stack) and Apps OS Group (the group to which the Apps OS User belongs). Accept the defaults, or enter new values.

    On all these Primary Applications Node Configuration screens, the Base Directory is the top-level directory that Rapid Install will use to derive the mount points for the Applications nodes. You can accept the defaults or enter new values.

    Important: You must accept the system-supplied defaults for the derived mount points.

    The Apps CSF field enables you to specify the directory where the concurrent processing log files will reside.

    Clicking the Edit Services button enables you to choose which services are enabled on this Applications node. Categories are: Root Service, Web Administration, Web Entry Point Services, Web Application Services, Batch Processing Services, and Other Services.

    Specify Services to be Enabled

    the picture is described in the document text

    A particular Applications node's role is defined not by the files installed: all the APPL_TOPs on a multi-node system contain the same files. Instead, the role is determined by the services that you set as enabled. These services specify the set of processes that will be started on each Applications node, and consequently the functions the node will perform. In other words, there is no concept of a "Forms node", "Web node", and so on, as there is no direct association between installed files and the services that can be run on that machine. This model enforces the three-tier architecture and simplifies tasks such as patching and upgrading.

    However, the Web Administration service group is an important exception, which can only be enabled on a single application tier node (and must be enabled on one node). This Web Administration node is where the WLS Admin Server will reside.

    If you specify Web Administration Services as being enabled on more than one node, clicking Next on the review Node Information screen (shown at the beginning of the next step) will result in an error message such as this being displayed:

    the picture is described in the document text

    If, on the other hand, you do not specify Web Administration Services as being enabled on any node, clicking Next on the review Node Information screen will result in a different error message being displayed:

    the picture is described in the document text

    The services provide the following functionality:

    Applications Node Services Summary
    This Service Group: Supports:
    Root Service
    • Node Manager

    Web Administration
    • WebLogic Admin Server

    Web Entry Point Services
    • Oracle HTTP Server

    • Oracle Process Manager

    Web Application Services
    • OACORE WLS

    • OAFM WLS

    • Forms WLS

    • Forms-C4WS

    Batch Processing Services
    • Oracle TNS Listener

    • Concurrent Managers

    • Fulfillment Server

    • Oracle ICSM

    Other Services
    • Oracle Forms Services

    • Oracle MWA Service

    Important: Currently, the following additional instructions apply to installing and activating application tier services:

    1. Perform the installation on the node that has been chosen to have the Web Administration (WLS Server Administration) and Web Entry (Oracle HTTP Server) service groups enabled, and then run AutoConfig on this node.

    2. Be aware that when subsequently installing on the secondary (managed) nodes, Rapid Install will not run adstrtall.sh, so services will not be running and the installer will display a message to this effect at the end of the install. This failure of the post-install checks is expected.

    3. Run $INST_TOP/admin/scripts/adstrtall.sh on all the other nodes to start the services.

    Applications nodes should have services enabled according to the following criteria:

    When installing, be aware of the following important service dependency:

    Note: For further details and any updates, see My Oracle Support Knowledge Document 406558.1, Understanding Applications Node Services in Oracle E-Business Suite Release 12.

    Example: Adding a Concurrent Processing Node that Resides on the Same Node as the Database Tier

    Tip: This example shows the concurrent managers being installed on the same machine as the database. However, with much faster local networks now being common, and the typical co-location of database and application tier machines, it is often preferable to run them on a separate machine. This is completely supported, and greatly facilitates ease of management and maintenance.

    Consider an installation deployed as follows:

    Note: The primary node is always the WLS Admin node, and the information for this node should be entered first even if the WLS Admin node will reside on a different system that will be installed later in the installation flow.

    1. Run Rapid Install on Server 1.

    2. Enter the information for the database tier using Server 1.

    3. Enter the information for the primary node using Server 2. This node will be the WLS Admin node.

    4. On the primary node, Server 2, enable all services except for Batch Processing Services.

      Note: In the next screen, the WLS Admin and Apps OS User passwords will be grayed out. You will enter this information later when installing the primary node (the WLS Admin node).

    5. Add a secondary application tier node to serve as the Concurrent Processing node using Server 1. On this node, enable only Batch Processing Services.

    6. Complete the installation on Server 1. At the end of the installation, only Batch Processing Services will be enabled on the application tier.

    7. Run Rapid Install on Server 2 to install the WLS Admin node. At the end of the installation, the following services will be enabled: Root Service, Web Administration, and Web Entry Point Services.

      Note: Rapid Install will prompt you to enter the WLS Admin and Apps OS User passwords. If you run Rapid Install in silent mode, the WLS Admin password will be set to the default.

    Important: Because the database and the secondary application tier node will be installed first on Server 1, you must manually perform the Secure Shell (SSH) setup for adop remote invocation after the install completes on Server 2. See: Set Up Secure Shell on Application Tier Nodes, Oracle E-Business Suite Maintenance Guide.

    Specifying Web Entry Points (Conditional)

    In some specialized configurations, detailed below, you may need to set certain context variables according to your node deployment.

    Note: Only customers with configurations of the types listed below will need to perform these steps.

    With the unified file system supported in Oracle E-Business Suite Release 12.2, some scripts should only be run on nodes that update URL parameters. For example, in a two-node install, with the database and concurrent processing server running on Node A and Web and Forms services running on Node B, AutoConfig should not update the URL-related parameters when run on Node A, because Node B is the web entry point.

    For example, installations that have multiple concurrent processing nodes or simply multiple web entry points may need to have the web entry point variables set to different values. Similarly, when adding a new node to a group of existing nodes, the new node may need to use the existing web entry point or a new web entry point (for example, in a DMZ configuration, when using load balancing; or when using a reverse proxy). In such cases, the web entry point variables must be set in each application context file to point to the correct web entry point, which will typically be the URL used to access the application.

    In such circumstances, the following context variables need to be set on the applicable nodes, and AutoConfig run to update the relevant configuration files:

    Web-Related Context Variables
    This variable: Specifies the:
    s_webentryurlprotocol Web Entry URL Protocol
    s_webentryhost Web Entry Host
    s_webentrydomain Web Entry Domain
    s_active_webport Active Web Port

    Another situation where you currently need to update the value of s_webentryhost is if you are using a load balancer to distribute processing across all the Applications tier nodes. In such a case, each of those nodes should have the value of the s_webentryhost variable to be that of the load balancer's hostname.

    Note: For further details of specifying context variables, see Chapter 3, Technical Configuration, in Oracle E-Business Suite Setup Guide.

  12. Supply Application User Information

    Supply Application User Information

    the picture is described in the document text

    The Apps OS User password is needed for setting up Secure Shell (ssh) on the application tier nodes, and must be the same on all these nodes.

    The checkbox to change the default passwords is automatically ticked when this screen appears. We strongly recommend accepting this, and changing the passwords accordingly. If you wish to retain the standard passwords, untick the box.

    Important: If you wish to run Rapid Install in silent mode, for example to avoid having to provide user responses during an upgrade, you must retain the default passwords (including the WLS Admin password). This is because passwords can no longer be passed on the command line in silent mode.

  13. Review Database and Applications Node Information

    Review Node Information

    the picture is described in the document text

    At this stage, you have specified details for the database node and the primary Applications node. For simple environments, you may only want a single Applications node, in which case you simply click Next to bypass the following step.

    If you do want to specify details for additional Applications nodes, proceed to the next step.

  14. Provide Details of Additional Applications Nodes

    If additional Applications nodes are required, as is typically the case, click the Add Server button. This opens a window that allows details to be specified.

    Specify Additional Applications Node

    the picture is described in the document text

    Here, you specify details of additional Applications nodes.

    The buttons on this screen fulfill the same roles as their counterparts on the Primary Applications Node screen. The Browse button allows you to search the file system for a suitable location to use as the Base directory. The Edit Paths button opens a window where you can specify a new value for one or more of the Applications node paths. Clicking the Edit Services button enables you to choose which services are enabled on this Applications node.

    When you have finished providing details for the first additional Applications node, click OK to return to the Primary Applications Node screen. If you want to add further Applications nodes, click on Add Server again and repeat the process.

    The following screen shows the result of adding a total of two additional Applications nodes, over and above the Primary Applications node.

    Review Node Information - With Additional Nodes

    the picture is described in the document text

    You will see that two additional actions are available for the new Applications nodes: the icons to their left enable you to edit their details and delete them, respectively.

    If you click on the wastebasket icon to delete a node, a popup window appears to request confirmation. You cannot delete either the Database Node or the Primary Applications node.

    Important: If you click the Back button at this stage, details of any additional Applications nodes will automatically be removed. This is because some information for additional nodes is derived from what was entered previously, so could be out of date if you made changes after going back to a previous screen.

  15. Review Pre-Install Checks

    Rapid Install performs a series of system tests to validate the configuration specified. The System Check Status screen checks port availability.

    The Validate System Configuration screen appears, to indicate whether various pre-install requirements for the installation have been met. The pre-install check screen then appears:

    Pre-Install Checks

    the picture is described in the document text

    The parameters that Rapid Install validates and reports on this screen include:

    Pre-Install Tests and Parameters
    This test: Checks:
    Port Availability The ports you selected are available for use.
    Database Pre-install Checks The Oracle E-Business Suite Database meets the necessary requirements.
    Port Uniqueness There are no duplicate defined ports for server processes.
    File Space The specified file systems have sufficient space.
    Stage Area Check The stage area is valid.
    Web Server Install Prerequisites Oracle HTTP (Web) Server requirements have been met.
    Mid Tiers Connectivity Application tier connectivity is working.
    OS User and Group Check The OS user account and group exist, and the user account is a member of the group.
    File Systems The specified file systems exist and have correct privileges.
    Host/Domain The host and domain names are valid.
    System Utilities The required system utilities are available.

    The results of each test are labeled with icons. There are three result types:

    When you have resolved any issues, click Next on the Validate System Configuration screen to continue with the installation.

  16. Begin the Installation

    On the Component Installation Review screen, Rapid Install lists the components it will install, based on the system parameters you entered in the wizard.

    Review Components

    the picture is described in the document text

    Click Next. Rapid Install now displays another alert screen asking you to verify that you are ready to begin the installation. Click Yes.

    Begin Installation

    the picture is described in the document text

Monitor Installation Progress

  1. Check progress bars

    During an installation, Rapid Install displays a main progress bar and an individual progress bar. The main progress bar reports on the completion percentage of the installation as a whole. The individual progress bar reports on the progress of each individual step.

    Warning: The installation is not complete until all the progress bars disappear from your screen.

    Installation Progress

    the picture is described in the document text

Post-Install Review

After the installation is complete, Rapid Install automatically validates the installed Oracle E-Business Suite environment. Tests include database availability, correctly-configured environment files, and functioning listeners.

Post-Install Checks

the picture is described in the document text

Post-installation tests include:

Post-Install Tests and Parameters
This test: Checks:
Database Availability Database is running and allows users to log on.
Environment File Environment file has been delivered.
HTTP HTTP listener is working.
Virtual Directory Validity of Web Virtual directories, such as OA_MEDIA, OA_JAVA, and OA_CGI, which are used for functionalities such as FNDWRR.
JSP JavaServer pages are working.
Configuration Upload Uploading of the configuration file (conf<SID>.txt) to the database (FND_OAM_CONTEXT_FILES table).
DBC File DBC file has been created.
Help Page Validity of Help pages (from clicking on "?" symbol), which are run from OA_HTML/help.
WLS Domain Validation The Oracle WebLogic Server domain is valid.
Login Page Login Page is working.
  1. Review the information from the tests Rapid Install has completed

    If there is an ! or x icon, click it to see the details. If any of the checks fail, refer to the Rapid Install log files to determine the reason, and resolve each problem before continuing. When the errors are fixed, click Retry to perform the post-install validation again.

  2. Click Next if there are no errors.

    Rapid Install informs you of the components that it installed on the Finish screen.

    If you wish to review the Post-install Checks screen, click Back. If you want to log on to Oracle E-Business Suite now, click Connect to Oracle Applications Release 12.2.0 to access the Oracle E-Business Suite Login page. Otherwise, click Finish to complete the Rapid Install session.

    Note: See Log On to Oracle E-Business Suite in Finishing Tasks for more information.

Express Installation

An Express installation sets up a fully configured single-user/single-machine system with either a fresh database or Vision Demo database. You specify basic configuration parameters, such as database type and name, top-level installation directory, and port increments. The remaining directories and mount points are supplied by Rapid Install using default values.

This type of installation contains (by default) a set of core Oracle E-Business Suite products. It also contains the US7ASCII character set (for a fresh install) and the AL32UTF8 character set (for a Vision Demo install), in both the database and the APPL_TOP. You can easily register additional products (according to your Oracle licensing agreement) after the installation is complete, by using License Manager. However, converting the character set may be time-consuming, and is best avoided if possible.

Note: For more details, see License Manager in Oracle E-Business Suite Maintenance Guide.

  1. Start Rapid Install

    On the Select Wizard Operation screen, select Install Oracle E-Business Suite Release 12.2.0 and then check Use Express Configuration.

    Select Wizard Operation - Install Oracle E-Business Suite Release 12.2.0, Use Express Install

    the picture is described in the document text

    Click Next to continue.

  2. Supply email details for security updates

    Data collected is sent via HTTPS (secure HTTP) to Oracle Support, facilitating pro-active problem avoidance and helping to reduce the time needed for resolution of support issues.

    Supply Email Details for Security Updates

    the picture is described in the document text

    If submission of your details fails because no connection can be made, you are presented with a pop-up screen prompting for proxy server information:

    Specify Proxy Server [Shown After Failed Connection Attempt]

    the picture is described in the document text

    If this screen appears, respond appropriately and then click OK.

  3. Enter Configuration Values

    The Express Configuration Information screen prompts for minimal configuration values. Default values are provided for all fields except Domain.

    This example screen is for UNIX:

    Express Configuration Information

    the picture is described in the document text

    In the Database Type field, use the drop-down list to choose either a Vision Demo database or a fresh database, and then either accept VIS or enter another name in the Database SID field. On Windows (as shown in the example above), enter the path to the UNIX Toolkit directory and Visual Studio directory, or click Browse and navigate to the desired path for each of these. On UNIX systems, the DISPLAY environment variable must be set to an active and authorized display.

    In the Domain field, enter a value that produces a fully qualified domain name (FQDN) when combined with a host (machine) name. For example, a host name of apps1 and domain name of company.com make up an FQDN of apps1.company.com.

    In the Base Directory field, enter the top-level directory path you want Rapid Install to use to create the derived mount points for the database node and all Applications nodes. Alternatively, click Browse and navigate to the desired path.

    The default value of the Port Pool set is zero, but you can customize it by selecting another value from the drop-down list in the Port Pool field. There are 100 port pool selections: if you select an increment of 3, the default values are increased by that value. The Database Port (1521) becomes 1524, the RPC Port (1626) becomes 1629, and so on.

    Note: The fields on this screen are fully described in Node-specific Configuration Information in Configuration Details.

    Click Next to continue.

  4. Start Installation Process

    Rapid Install displays the pre-install tests as it performs them. When it is complete, the Pre-install Checks screen appears.

    Pre-Install Checks

    the picture is described in the document text

    If there is an exclamation mark (!) or x icon shown, click on it to see the details stored during the check process. For example, if you see an exclamation mark beside File Space Check, clicking on it may display a screen such as this:

    Error Example - Insufficient File System Free Space

    the picture is described in the document text

    Resolve any issues you need to fix, and then click OK to return to the Pre-install Checks screen.

    If you decide to continue the installation without fixing the flagged issues, Rapid Install displays the following warning when you click Next.

    Configuration Alert

    the picture is described in the document text

    Click Yes to continue or No to stop the installation. If you click No, you must go back to the appropriate screen and re-enter the incorrect or incompatible parameter. Click Back to return to a previous screen.

  5. Continue Installation

    The remaining screens in the Rapid Install flow for an Express installation are the same as for a standard installation.

What To Do Next

After completing the appropriate steps in this chapter, you must follow the applicable steps in the Enabling Online Patching section of the Oracle E-Business Suite Online Patching chapter of Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.2 or Oracle E-Business Suite Upgrade Guide: Release 12.0 and 12.1 to Release 12.2.

Note that Step 2 of Enabling Online Patching requires you to go to My Oracle Support Knowledge Document 1349240.1, Database Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade. Follow the steps in "Path A" of this document to obtain any Oracle Database 11.2 one-off patches that may not have included with Rapid Install.

Release 12.2.2 is the minimum supported 12.2.x release level for production use. Consequently you must also apply Oracle E-Business Suite Release 12.2.2 or a higher Release 12.2.x release update pack before you begin using your Oracle E-Business Suite Release 12.2 instance. For instructions, see the readme for the release update pack you want to apply, such as Oracle E-Business Suite Release 12.2.2 Readme, My Oracle Support Document 1506669.1, or Oracle E-Business Suite Release 12.2.3 Readme, My Oracle Support Document 1586214.1.

Once the main installation is complete, some additional finishing steps are required for all users, and some others are required for specific types of installations. For example, all users must configure the client software, but some users may also need to set up NLS support.

Go to Finishing Tasks, and perform the tasks that apply to your system.