Configure 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).
  1. Click Create.

Log 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.

Review Your Oracle E-Business Suite Virtual Machine Configuration

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.

The 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:

An example of your instance-specific configuration details might look like this:

  • Operating System Version: Oracle Linux 6
  • Oracle E-Business Suite Database Configuration
  • Oracle E-Business Suite Application Tier Configuration

Change Oracle E-Business Suite Account Passwords

You must now change your Oracle WebLogic Server and Oracle E-Business Suite account passwords. 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.

Configure Instance for HTTP Access

Your instance is now 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 “Create a Security Rule” to enable access to instances using other protocols and ports, or if you want to specify a different source or destination.

Configure 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.

Note: You can find the public IP address by navigating to the Instances tab on the Oracle Compute Cloud Service console and reviewing the details page for your instance.

2. 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.

3. 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:

4. Run the following script to configure the web entry point:

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:

a. Enter the Web Entry Protocol (e.g. https/http): http

b. Enter the Web Entry Host Name (e.g. public): oc-129-144-28-2

c. Enter the Web Entry Domain Name (e.g. domain.com): compute.oraclecloud.com

d. Enter the Web Entry Port (e.g. 443/80): 8000

e. Enter the base installation directory (e.g. /u01/install/APPS): /u01/install/APPS

5. Review the parameters. If any value entered is incorrect, abort by pressing Ctrl-C.

6. Press Enter. The web entry configuration is now complete.

7. Log in as oracle and execute the /u01/install/APPS/scripts/stopapps.sh script to stop any application tier processes that are running.

8. Log in as oracle and execute the /u01/install/APPS/scripts/startapps.sh script to start the application tier processes.

9. Access the Oracle E-Business Suite Login page. For example:
http://oc-129-144-28-2.compute.oraclecloud.com:8000/OA_HTML/AppsLogin

 

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 Oracle Compute Cloud Service 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 Oracle Compute Cloud Service 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 dropdown 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.

Related Posts

Let us fetch you the latest from Oracle!





Not a robot?
Enter the sum of 8 + 9 below:

* Indicates required field.

Success! Thank you!