Provisioning a New Oracle E-Business Suite Installation on a Single Node on Oracle Cloud Infrastructure Classic


Options



Before You Begin

Purpose

In this tutorial, you'll use an image hosted on the Oracle Cloud Marketplace to provision a single virtual machine (VM) containing both the database tier and the application tier on Oracle Cloud Infrastructure Classic.

You can choose any combination of the following Oracle E-Business Suite releases and install types:

  • Release 12.2.7, 12.2.6, or 12.2.5
  • Vision (demo) or fresh install

Optionally, you can enable Oracle Distributed Yard Management or Oracle Distributed Warehouse Management as a post-install step.

Time to Complete

A minimum of 1 hour.

The first time you create an instance from an image, the image is downloaded from the Oracle Marketplace to your domain’s object storage and a bootable volume is created. These two processes can take several hours. Subsequent instance creation is relatively quick, since you do not need to download the image again.

Background

When you are following the procedures described in this tutorial, do not expose any ports to the internet directly and employ a secure protocol. We recommend that you:

  • Employ a suitable strategy to restrict access, either using a VPN or a security IP list (constrained by IP addresses). This includes access to the HTTP/HTTPS ports. In this tutorial, we will use a security IP list.
  • Use the HTTPS protocol for all deployments. The HTTP examples shown in this document are solely intended to demonstrate the principles of setting up a security list and are not a recommendation to use the HTTP protocol.

What Do You Need?

To perform the steps in this tutorial, you need:

  • An understanding of the relevant information in My Oracle Support Knowledge Document 2066260.1, Getting Started with Oracle E-Business Suite on Oracle Cloud.
  • A subscription to Oracle Cloud Infrastructure Compute Classic. (See Getting Started with Oracle Cloud Infrastructure Compute Classic.) You must be a user with the Compute_Operations (Service Administrator) role.
  • Cloud service resources that match or exceed the following minimum requirements:
  • Configuration Number of Virtual Machines (VM) OPCUs Memory Block Storage External IPs
    Single-node installation with a demo database or fresh installation database 1 1 15 GB 430 GB 1

Process Overview

To create and configure a Release 12.2.7, 12.2.6, or 12.2.5 single-node Oracle E-Business Suite instance in Oracle Cloud Infrastructure Compute Classic (which will be referred to as "Compute Classic" in this document), you must complete the following tasks:

  1. Generate an SSH key pair on your local system and upload the public key to Compute Classic.
  2. (Optional) Create a security IP list.
  3. Create your Oracle E-Business Suite instance.
  4. Configure the instance for SSH access.
  5. Log into your instance using SSH.
  6. Review your Oracle E-Business Suite virtual machine configuration.
  7. Change the default passwords for accounts.
  8. Configure your instance for HTTP access.
  9. Configure the web entry point.
  10. Acknowledge secure configuration recommendations.
  11. (Optional) Install Oracle Distributed Yard Management or Oracle Distributed Warehouse Management
  12. Perform conditional post-install steps

To supplement these tasks, also refer as needed to the following:

Generating an SSH Key Pair

Before you create your Compute Classic instance, you must:

  1. Generate an SSH key pair on your local system (UNIX or Windows).
  2. Upload the SSH public key to Compute Classic. This SSH public key is used for authentication when you log in to the instance.
    Note: Be sure to record the public and private key names, where you saved them, and your key passphrase.

Creating a Security IP List (Optional)

We recommend that you avoid exposing the VM to the public internet. To do so, first work with your network administrator to identify a restricted IP range (or ranges) to be used to access your Oracle E-Business Suite cloud instance. Then, create a security IP list with a name such as Allowed-External-Addresses that identifies these IP addresses. You will associate this security IP List with the instance that you create in the next section.

See "Creating a Security IP List" in Managing Security IP Lists for instructions.

Creating an Oracle E-Business Suite Instance

  1. Navigate to the Oracle Cloud Infrastructure Compute Classic console by following these steps:
    1. Sign in to the Oracle Cloud My Services application by navigating to https://cloud.oracle.com/sign-in.
    2. In the Cloud Account region, select the "Traditional Cloud Account" option in the account type drop-down list.
    3. Then, select your data center from the data center drop-down list.
    4. Click My Services.
    5. On the next screen, enter your identity domain. Click Go.
    6. Enter your sign in credentials. Click Sign In. This takes you to the Oracle Cloud My Services Dashboard.
    7. Click the menu button near the upper left corner of the Dashboard page to bring up the Navigation menu.
    8. Select Compute Classic to view the Compute Classic console.
  2. In this console, select the Instances tab and then click Create Instance.
  3. Here, from the QuickStarts page, click Customize.
  4. This will bring up the Image screen. On this screen:
    1. Select Marketplace in the side navigation menu.
    2. In the Search field to the right of the side navigation menu, enter your choice of either "EBS 12.2.7," "EBS 12.2.6," or "EBS 12.2.5" and then click on the magnifying glass or press <Return>.
    3. Choose the image you want to install:
      • For 12.2.7, click the Select button below either the EBS 12.2.7 Demo Install Image or EBS 12.2.7 Fresh Install Image.
      • For 12.2.6, click the Select button below either the EBS 12.2.6 Demo Install Image or EBS 12.2.6 Fresh Install Image.
      • For 12.2.5, click the Select button below either the EBS 12.2.5 Demo Install Image or EBS 12.2.5 Fresh Install Image.
    4. In the pop-up window that appears, accept the terms of use and click the Install button.
    5. When the image is available in your account, you will see the message "Marketplace image installed and ready to use".
    6. Proceed to the Shape screen by clicking the > button at the top right.
  5. On the Shape screen, select an appropriate shape for your instance. The shape specifies the number of CPUs and amount of memory your instance will have.
    1. For example, select oc1m (OCPUs: 1, Memory: 15 GB).
    2. Click the > button to proceed to the Instance screen.
  6. On the Instance screen, perform the following steps:
    1. Using the Persistent drop-down list, ensure that the default option "False" is selected.
    2. Using the Placement drop-down list, ensure that the default option "Auto" is selected.
    3. In the Name field, enter an appropriate name. If you don’t specify a name, the instance name will be generated automatically based on the date and time.
    4. In the Label field, enter a description to help identify the instance. If you provide a label, the label is used to list the instance on the Instances tab.
    5. In the SSH Keys field, if you have already uploaded your SSH Public Key you created earlier, select it from the drop-down list.
    6. Otherwise, click on Add SSH Public Key, then:
      1. In the Add SSH Public Key dialog box, enter a name and the value of the SSH public key you generated earlier.
      2. Click Add to add your SSH public key and associate it with the instance being created. Paste the key value exactly as it was generated. Do not append or insert any extra characters, line breaks, or spaces.
    7. Click the > button to proceed to the Network screen.
  7. On the Network screen, perform the following steps:
    1. In the DNS Hostname Prefix field, enter a string that will be used as a prefix in the domain host name for your instance. For EBS 12.2.7 images, this string must be apps.
    2. For Network Options, select Shared Network. Ensure that IP Network is not selected.
    3. Using the Public IP Address drop-down, choose Persistent Public IP Reservation.
    4. An IP Reservation drop-down list will appear. If you have reserved an IP address, choose it from the list.
    5. Otherwise, click Create IP Reservation, then:
      1. In the Create Public IP Reservation dialog box, enter the desired name of your IP reservation
      2. Click Create.
    6. In the Security Lists field, either specify an existing security list (substep 1 below) or create a new one (substep 2 below).
      1. If you created a security list previously, enter its name.
      2. If you did not create a security list earlier, click Create Security List. In the dialog box, supply the following and then click Create:
        • Name: Enter the desired name of your security list. For example, you could enter ebs-net.
        • Inbound Policy: Retain the default policy, Deny (Drop Packets, No Reply).
          Note: Never set Inbound Policy to Permit, as this setting will disable the firewall and will allow any traffic into the VM instance. For more information, refer to About Security Lists in Using Oracle Compute Cloud Service (for PaaS).
        • Outbound Policy: Retain the default policy, Permit (Allow packets).
        • Description: Enter a description.
    7. Click the > button to proceed to the Storage screen.
  8. On the Storage screen:
    1. Under the Name column, you will see one volume listed, called <instance_name>_storage. The value of <instance_name> is the name you previously entered (or accepted) on the Instance page. Do not make any changes to this name.
    2. Click the > button to proceed to the Review screen.
  9. On the Review screen, check your selections and make any necessary edits.
    1. When you are ready, click Create to start creation of your instance. You will see the message: "Starting orchestration <instance name>_master".
    2. Instance creation and configuration includes various phases, and can take up to two hours to complete. While this is proceeding, we suggest you carry out the steps in the next section, Configuring the Instance for SSH Access
      Note: You can monitor progress by selecting the Orchestrations tab.
    3. When the process is complete, you will be able to click on the Instances tab to view your running instance.

Configuring Instance for SSH Access

Perform the following steps to enable SSH access to your instance.
  1. Select the Network tab.
  2. Select Security Rules from the navigation menu on the left.
  3. Select Create Security Rule and then do the following:
    • Name: Enter a name for the rule. For example, allow_ssh
    • Status: Select Enabled.
    • Security Application: Select ssh
    • Source: Select the Security IP List radio button and specify a Security IP List:
      • If you created a Security IP List earlier (for example, Allowed-External-Addresses) select it from the drop-down list.
      • If you did not create a Security IP list, select public-internet from the drop-down list.
    • Destination: Select the Security List radio button. Then, from the Security List drop-down list, select the name of the security list that you created earlier. For example, ebs-net.
    • Description: Enter a description for the rule (for example, Allow SSH access to instance).
  4. Click Create.

Logging Into Your Instance Using SSH

After instance creation and configuration are complete and you have configured the instance for SSH access, you will log in to the instance using SSH to perform any subsequent operations.

For detailed instructions, refer to section "Connect to Your Oracle Cloud Instance Via SSH" in the Oracle by Example tutorial Common Tasks for Oracle E-Business Suite in Oracle Cloud.

Reviewing Your Oracle E-Business Suite Virtual Machine Configuration

The creation of a VM from the 12.2.7 image is very fast due to the use of a logical hostname, which allows for preconfiguration of the application tier and the database tier.

When using the EBS 12.2.6 and 12.2.5 images, the Oracle E-Business Suite database and application tier configuration is automatically performed at boot time during the create instance phase. The boot script first configures the database tier file system, then the application tier file system. This configuration may take an hour or more, depending on the shape of the virtual machine chosen during the create instance phase. Before you try to use the new Oracle E-Business Suite environment, you should confirm that virtual machine configuration is complete by looking for entries like these in the log file /var/log/oraclevm-template.log:

[INFO] Oct 06 11:32:48 configdhcp.sh: Cloning the DB Tier Completed Successfully
[INFO] Oct 06 12:45:03 configdhcp.sh: Cloning the Apps Tier Completed Successfully
Warning: If those entries are not present in the log file, the configuration is not yet complete and you must wait until it is complete to use the VM. Here is an example of an error you might see if you attempt to source the environment before the configuration is complete.
. /u01/install/APPS/EBSapps.env
Node info file
  /u01/install/APPS/fs2/FMW_Home/Oracle_EBS-app1/applications/oacore/APP-INF/node_info.txt is not found.
  EBSapps.env: exiting with status 1 (Fail)

Once complete, here is an example of what your instance-specific configuration details might look like:

  • Operating System Version: Oracle Linux 6.9
  • Oracle E-Business Suite Database Configuration
  • Oracle Home Location /u01/install/APPS/12.1.0
    Oracle Data Files /u01/install/APPS/data
    Oracle Database Version 12.1.0.2
    Oracle SID EBSDB
    SGA Size 2 GB
    Port Pool 0 (TNS Listener Port 1521)
  • Oracle E-Business Suite Application Tier Configuration
  • Application Tier File System Top /u01/install/APPS
    Location of the Run Edition File system /u01/install/APPS/fs1
    Location of the Patch Edition File system /u01/install/APPS/fs2
    Location of the Non-editioned File system /u01/install/APPS/fs_ne
    Port Pool 0 for the run edition and 1 for the patch edition
    Oracle E-Business Suite Application Tier Version 12.2.7
    Oracle WebLogic Server Version 10.3.6.0.171017 PSU
    Oracle WebTier Version 11.1.1.9
    Oracle Forms and Reports 10.1.2.3
    Critical Patch Update January 2018

Changing Oracle E-Business Suite Account Passwords

Oracle E-Business Suite is provisioned with default passwords for standard user accounts such as apps, system, sys, and weblogic. Information about these passwords can be found in Specify Application User Information in Chapter 2: Performing an Installation, Oracle E-Business Suite Installation Guide: Using Rapid Install, which is available in the Oracle E-Business Suite Documentation Web Library, Release 12.2.

You must now change these passwords. For instructions, refer to the "Change E-Business Suite Account Passwords" section in the Oracle by Example tutorial Common Tasks for Oracle E-Business Suite on Oracle Cloud Infrastructure Classic.

Configuring Instance for HTTP Access

Your instance is currently configured to allow public access over SSH only.

To enable access to the instance over other protocols, such as HTTP or HTTPS, you must open the required ports. In this tutorial, you'll create a security rule to enable HTTP access to your instance over port 8000.

Create a Security Application

A security application is a mapping between a port number and port type (TCP, UDP, or ICMP). To open port 8000, you must create a security application for that port.

Perform the following steps to create a security application for port 8000:

  1. Select the Network tab.
  2. Select Security Applications from the navigation menu on the left.
  3. Click Create Security Application.
  4. In the Create Security Application dialog box, do the following:
    • Name: Enter a name for the new security application (for example, http_8000). Make a note of the name, which you will use later in this tutorial.
    • Port Type: Select tcp.
    • Port Range Start and Port Range End: In both these fields, enter the port that you want to open (for example, 8000).
    • Description: Enter a description for the new security application (for example, HTTP traffic to port 8000).
  5. Click Create.

In the next section, you will create a security rule to allow HTTP traffic from the subset of the Internet that you specified in your Security IP List.

Create a Security Rule

You created a security list (for example, ebs-net) when you created the Oracle E-Business Suite instance. A security list is a set of instances that can communicate with each other across all protocols and ports.

When you create a security rule, specify this security list as a destination. This allows traffic from a specified source (such as your private network) to access all the instances that are part of the destination security list - and in this case, the Oracle E-Business Suite instance you just created - using a specified protocol and port.

  1. Select Security Rules from the navigation menu on the left.
  2. Select Create Security Rule and then do the following:
    • Name: Enter a name for the rule. For example, allow_ebs_http_8000.
    • Status: Select Enabled.
    • Security Application: Select the security application you created earlier. For example, http_8000.
    • Source: Select the Security IP List radio button and specify a Security IP List:
      • If you created a Security IP List earlier (for example, Allowed-External-Addresses) select it from the drop-down list.
      • If you did not create a Security IP list, select public-internet from the drop-down list.
    • Destination: Select the Security List radio button. Then, from the Security List drop-down list, select the Security List you created earlier. For example, ebs-net.
    • Description: Enter a description for the rule (for example, Allow TCP traffic to http server on port 8000).
  3. Click Create.

Port 8000 on the instances in the security list you created (for example, ebs-net) is now open to HTTP requests. You can temporarily suspend security rules at any time by disabling them. You can also delete security rules you no longer need.

Note: You will repeat the steps in sections "Create a Security Application" and "Creating a Security Rule" to enable access to instances using other protocols and ports, or if you want to specify a different source or destination.

Configuring the Web Entry Point

Your Oracle E-Business Suite instance on Oracle Cloud is installed with an internal DNS name and a private IP address, so is not accessible from the public Internet. To make the instance accessible from the public Internet, you need to set the web entry point parameters in the applications context file to point to the <publichostname>.<publicdomain> name.

Perform the following steps to configure the web entry point.

  1. Identify the public IP address of your Oracle E-Business Suite virtual machine.
  2. Note: You can find the public IP address by navigating to the Instances tab on the Compute Classic console and reviewing the details page for your instance.

  3. If, for example, the public IP address of the virtual machine is 129.144.28.2, the public hostname.public domain for the virtual machine will be oc-129-144-28-2.compute.oraclecloud.com.
  4. Check that the Oracle E-Business Suite database tier services (database and TNS listener) are running. If they are not, start them by performing the following steps, first setting the user account to 'oracle' and then running the startdb.sh script:
  5. $ echo $USER 
    opc 
    $ sudo su - oracle
    $ echo $USER 
    oracle 
    $ /u01/install/APPS/scripts/startdb.sh
  6. Run the following script to configure the web entry point:
  7. $ /u01/install/scripts/configwebentry.sh

    The script prompts for the following parameters. Enter the values as shown below. For example, to access the Oracle E-Business Suite instance with the URL http://oc-129-144-28-2.compute.oraclecloud.com:8000:

    1. Enter the Web Entry Protocol (e.g. https/http): http
    2. Enter the Web Entry Host Name (e.g. public): oc-129-144-28-2
    3. Enter the Web Entry Domain Name (e.g. domain.com): compute.oraclecloud.com
    4. Enter the Web Entry Port (e.g. 443/80): 8000
    5. Enter the base installation directory (e.g. /u01/install/APPS): /u01/install/APPS
  8. Review the parameters. If any value entered is incorrect, abort by pressing Ctrl-C.
  9. Press Enter. The web entry configuration is now complete.
  10. Log in as oracle and execute the /u01/install/APPS/scripts/stopapps.sh script to stop any application tier processes that are running.
  11. Log in as oracle and execute the /u01/install/APPS/scripts/startapps.sh script to start the application tier processes.
  12. Access the Oracle E-Business Suite Login page. For example:
    http://oc-129-144-28-2.compute.oraclecloud.com:8000/OA_HTML/AppsLogin

Acknowledging Secure Configuration

As of Oracle E-Business Suite Release 12.2.7, access to the environment will be restricted until the system administrator configures or acknowledges the secure configuration recommendations.

To access the Secure Configuration Console, a user must have a responsibility that includes the Applications System (OAM_APP_SYSTEM) function privilege, such as the seeded System Administration or System Administrator responsibilities, and must be registered as a local user with Oracle E-Business Suite. The administrator must log in to Oracle E-Business Suite using the local login page (http(s)://[host]:[port]/OA_HTML/AppsLocalLogin.jsp) to navigate to the console and unlock the system. If a user with local system administrator privileges is not available, you can access the Secure Configuration Console through a command line utility. For more information, see "Secure Configuration Console" in the Oracle E-Business Suite Security Guide.

Oracle E-Business Suite Secure Configuration Console

Note: Once the system is "Unlocked" for normal usage, the Secure Configuration Console is still available for administrators under the 'Functional Administrator' responsibility.

Installing Oracle Distributed Warehouse Management or Oracle Distributed Yard Management (Optional)

Once you have provisioned a Release 12.2.6 single-node fresh install environment, you have the option of installing additional components to enable use of Oracle Distributed Warehouse Management or Oracle Distributed Yard Management.

Follow the steps below for either of these two products:

  1. Connect to your new instance via SSH and switch from the opc user to the oracle user.
  2. $ sudo su - oracle
  3. Set the environment:
    $ . /u01/install/APPS/EBSapps.env run
  4. Navigate to the $WMS_TOP/admin directory:
    $ cd $WMS_TOP/admin
  5. Download the special patch required:
    $ wget https://storagesvc-a425918.storage.oraclecloud.com/v1/storagesvc-a425918/Patches/EBS/12.2/WMS/p25144072_122600_LINUX.zip
  6. Unzip the patch:
    $ unzip p25144072_122600_LINUX.zip
    Once the patch is unzipped, a folder called 25144072 is created. Copy the files in this folder to the $WMS_TOP/admin directory.

Then conduct the following steps for your chosen product:

  • For Oracle Distributed Warehouse Management, run the command:
    $ $WMS_TOP/admin/wmsopcmp.sh apps apps_pwd DWMS
    Note: apps_pwd is the password for the apps user.
  • For Oracle Distributed Yard Management, perform the following steps:
    1. Run the command:
      $WMS_TOP/admin/wmsopcmp.sh apps apps_pwd DYMS
      Note: apps_pwd is the password for the apps user.
    2. Perform additional steps as listed in My Oracle Support Knowledge Document 1672903.1, Oracle Yard Management, Deployment Steps For ADF Components.
You must then complete the setup process by activating the products and performing the functional implementation steps. Refer to the "Performing Conditional Post-Install Steps" section below.

Performing Post-Install Steps

If you have provisioned a fresh install of Oracle E-Business Suite, Oracle Distributed Warehouse Management, or Oracle Distributed Yard Management, before you can use the applications you will need to activate any required products and languages and perform the relevant functional setups.

In a Vision Demo installation, you can also activate languages other than the default of American English.

Refer to the instructions below for more information.

Activate Products and Languages

Activate your chosen products and languages by running the License Manager utility. For detailed instructions, refer to Chapter 16 "License Manager" in Oracle E-Business Suite Maintenance Guide, Part No. E22954, available in the Oracle E-Business Suite Documentation Web Library, Release 12.2.

Conduct Functional Implementations

After you have activated your products and languages, you may proceed with your functional implementation.

Appendix A - Managing Your Orchestrations and VM Instances

This section explains how orchestrations are related to instances, and what your options are if you want to reboot, delete or recreate a VM instance.

Understanding Orchestrations

Each instance you create has three corresponding orchestrations:

  • <instance_name>_master - The master orchestration that specifies the individual orchestrations for both the instance and any storage volumes that are created.
  • <instance_name>_instance - The orchestration that specifies the instance to be created. If storage volumes are created during instance creation, this orchestration waits for the storage volumes to be online before starting.
  • <instance_name>_storage - The orchestration that creates storage volumes.

Note:  Do not stop the master orchestration, as doing so will delete the instance and all the associated applications and data.  See section "Deleting a VM Instance".

Rebooting a VM Instance

To reboot your VM instance and all the associated applications and database processes, you can simply restart it from the Compute Classic console. When you do so, your instance retains all its configuration information, including its public IP address and any attached and mounted storage volumes:

  1. Sign in to the Compute Classic console.
  2. If your domain spans multiple sites, select the appropriate site. To change the site, click the Site menu near the top of the page.
  3. On the Instances screen, go to the instance you want to restart.
  4. From the drop-down menu at the right of the instance row, select Reboot.

Deleting a VM Instance

You can delete an instance you no longer need by stopping either the instance orchestration or the master orchestration:

  • Stopping the instance orchestration (<instance_name>_instance) deletes the instance but retains the data on the attached storage volumes. Any patches and customizations that were applied to the instance will be lost.
  • Stopping the master orchestration (<instance_name>_master) deletes the instance, and also deletes those IP addresses and storage volumes that were created when the instance was created.

Recreating a VM Instance

If you stop the instance orchestration, you can recreate the instance by restarting the orchestration. (Stopping the instance orchestration is not the same as stopping the master orchestration, which deletes the instance completely.)

Note: Recreating is equivalent to provisioning a new instance: any customizations that were associated with the old instance are lost.

Appendix B - Example Worksheet

You can use the example worksheet below to record the key information you will need to supply when you work through this tutorial.

    Applicable Section Item Name Item Value
    Generate an SSH Key Pair Private SSH key name  
    Public SSH key name  
    SSH key passphrase  
    SSH keys path  
    Create a Security IP List List of IP addresses  
    Security IP List name  
    Create an Oracle E-Business Suite Instance Full image name  
    Shape  
    Instance name  
    Instance label  
    DNS hostname prefix  
    IP reservation name  
    IP address of instance  
    Security list  
    Configure Instance for SSH Access Security rule to enable ssh  
    Change Default Passwords for Accounts WLS admin password  
    SYSADMIN user password  
    Vision demo users (1-30)  
    Configure Instance for HTTP Access Security application to enable HTTP  
    Security rule to enable HTTP  
    publichostname.publicdomain value  
    URL to EBS login page  

Want to Learn More?

See the following sections of Using Oracle Cloud Infrastructure Compute Classic:

Change Log

Date Description
2018-06-18
  • Updated "Purpose" to indicate a single VM contains both the database tier and the application tier.
  • Updated "Reviewing Your Oracle E-Business Suite Virtual Machine Configuration."
  • Updated "Changing Oracle E-Business Suite Account Passwords" to include Oracle E-Business Suite Installation Guide: Using Rapid Install reference.
2018-06-15
  • Added guidance in Step 7a regarding the DNS Hostname Prefix field in "Creating an Oracle E-Business Suite Instance."

2018-05-18

  • Updated "Purpose" and "Creating an Oracle E-Business Suite Instance" to include both demo and fresh install options for 12.2.7.
  • Made updates to section "Reviewing Your Oracle E-Business Suite Virtual Machine Configuration."

2018-03-23

  • Made changes to step 6 of "Creating an Oracle E-Business Suite Instance" to follow updated UI.

2018-01-22

  • Updated content in "Performing Post-Install Steps."
  • Added new section "Acknowledging Secure Configuration."

2017-11-08

  • Made various updates in document to reflect updates in product/service name changes as well as UI updates.

2017-10-02

  • Updated various content in document to add 12.2.7 demo support
  • Edited login instructions to match updated UI.

2017-06-12

  • Changed block storage requirement from 375 to 430 GB in table of "What Do You Need?" section.

2017-05-02

  • Updated steps in "Create an Oracle E-Business Suite Instance" to match changes in UI.
  • Updated to 03/28/17 OBE template.

2017-03-10

  • Changed title of OBE to "Provisioning a New Oracle E-Business Suite Installation on a Single Node on Oracle Cloud".

2017-03-03

  • Added step "You may use the seeded user DYMSADMIN which has all the required roles and grants." to DYMS subsection of section "Conduct Functional Implementations".

2017-02-28

  • Added supplementary install steps for Distributed Warehouse Management and Distributed Yard Management.
  • Modified Create Instance steps to reflect new Compute UI.
  • Moved some shared content to Oracle by Example tutorial "Common Tasks for Oracle E-Business Suite on Oracle Cloud".

2017-02-07

  • Added example to step for switching to oracle user in Change Password sections.

2017-01-30

  • Rewrote section "What Do You Need?"
  • Rewrote section "Generate an SSH Key Pair".
  • Added new Appendix A on managing instances and orchestrations.
  • Created Appendix B to store Example Worksheet.
  • Renamed OBE.

2016-12-14

  • Amended adstpall and adstrtal commands in Steps 3 and 5 respectively of "Change the Oracle WebLogic Server Administrator Password" subsection of "Change Default Passwords For Accounts" section.
  • Fixed a couple of typos.

2016-11-30

  • Added instructions for logging on to Oracle Compute Cloud Service console.
  • Fixed several small typos.

2016-11-04

  • Added section with Example Worksheet.

2016-10-14

  • Updated information on changing passwords.
  • Added Step 4e to section "Configure the Web Entry Point".
  • Made various changes throughout document.

2016-10-10

  • Added new section "Configure the Instance for SSH Access".
  • Replaced most of section "Generating an SSH Key Pair on Windows using the PuTTY Key Generator" with a reference to external doc.
  • Made various other small changes throughout document.
2016-09-30
  • Removed step for Get App as no longer needed.
  • Added new section "Create a Security IP List", plus a reference to it from "Create a Security Rule" section.
  • Made various changes throughout document.

2016-09-16

  • Added 12.2.6 information.
  • Updated section "Configure External IP Address/Internal Host Name on Client Machines".

2016-08-03

  • Amended title.

2016-07-08

  • Expanded "Time to Complete" description.

2016-06-21

  • Updated Step 5 of "Create an Oracle E-Business Suite Instance", consolidating the previous points a and b into a single new point a.

2016-06-09

  • Fixed a formatting issue with "Copy Required Image from Oracle Cloud Marketplace into Compute Account" section.

2016-06-03

  • Amended security list instructions in Step 4f of "Create an Oracle E-Business Suite Instance" section.

2016-05-27

  • Added "User Interface" section.

2016-05-26

  • Updated "Process Overview".
  • Removed "Uploading the SSH Public Key," "Reserving a Public IP Address," "Create a Security List," and "Add Your Instance to a Security List" sections - embedded information into other sections.
  • Updated "Creating an Oracle E-Business Suite Instance" section.

2016-05-12

  • Updated OBE title
  • Added minimum requirements for Oracle Compute Cloud resources needed to implement OBE flow in "What Do You Need" section

2016-04-25

  • In section "What do you need?", removed note mentioning obsolete requirement to use an oracle.com account.

2016-03-24

  • Made various refinements and updates to reflect latest offerings and features.

2016-02-05

  • Made changes throughout document to reflect modified Cloud Service UI.

2016-01-27

  • Updated information about creating storage volumes.
  • Made minor updates throughout document.

2015-12-21

  • Initial publication.