Getting started with Oracle SOA Cloud Service Part 2: Configure Oracle Database Cloud Service Instance

In this Post we cover the steps to setup the Oracle Database cloud service instance.

The Oracle Database Cloud Service instance is like any normal Oracle Database instance that is accessible and managed over a cloud.

Note: For Oracle SOA cloud service we need to create an Oracle Database Cloud Service with both Cloud Storage and Local Storage backup configuration

 Follow the below steps to Configure Oracle Database Cloud Service Instance:

1. Log in to your Trial My Services Account
2. From Menu on Left Side, click on Oracle Database Cloud Service
3. Click on Create Service Button








4. It will ask to either upload the SSH key or generate the new Key. Make sure you save the SSH key as it is needed to connect later.









5. Next, enter the service name, select the Software Release Version and click Next










6. Next, Select the Compute Shape i.e. how many CPU's and RAM is needed.
Since this is a trial I selected 2 CPU with 15GB RAM, which I feel is more than enough.

Make you select "Both Cloud Storage and Local Storage" Option.

Here in the container details, we need to provide the container service URL, user/password, which we covered in PART 1.

If the container does not exist, you can check Create Cloud Storage Container Check Box










7. Review the configuration details, if everything is OK, click on Create Button.











8. It take about 15- 20 mins to create the Database Instance. Till then you will see the status as In progress.






Once the Service is created, you will see the status as completed. Also the action button is enable for the instance.







Next, we will see how to connect to this Oracle Database Cloud Instance over a public network:

 In Order to access the Database Instance over a public network we need to enable the Access Rule.

1. Identify the Public IP address for our Oracle Database Cloud Instance. To do this, just click on the instance and IP will be visible in Details Section

2. Click on Action Button, and Click on Access Rules









3. Enable the ora_p2_dblistener access rule










4. As the access rule is now enabled, lets connect to the Cloud Database from Local JDeveloper.
    Open the JDeveloper, Click on Add Connections under database window

Provide the required details i.e. User/Password that was enter while creating the Database Instance.
Public IP as a Hostname
SID/Port

















5. If everything is proper, you will see the success message.

Now you can query the database like any other private database in the network.





















The Action button provide options to access EM console/DBaas monitor etc, which can be used by the DBA to maintain and manage the DB instances.













Overall, I am pretty impressed with the Oracle Cloud Offering, if you see in this post, I as non-DBA, was able to set up the Database Instance in less than 1 hour with just clicks.

Next in Part 3, We will explore the steps to Configure Oracle SOA Cloud Service Instance using this DB Instance.

Ref:
http://docs.oracle.com/en/database/

Popular posts from this blog

JAVA embedding in Oracle SOA 12c

Image
In this post we will explore how to EMBED Java or call Java API from Oracle SOA BPEL process. In order to demonstrated this, I have created a simple JAVA project with 3 classes. 1.        Account.java -> This class represent Account DTO       2.       Party.java -> This class represent a party (customer) DTO       3.       GetNumber.java -> This class contains the method that takes Party DTO as input and apply some business logic and return party’s AccountDTO in response. public Account getNumber(Party party) The above classes are created to simulate the calling of actual business logic API’s. Account.java Party.java GetNumber.java public class Account {     public Account() {         super();     }     String account;     public void setAccount(String account) {         this.account = account;     }     public String getAccount() {         return account;     } } public class Party {     public Part
Read more

Passing/Receiving HTTP header in SOA BPEL

Image
In this example we will explore how to pass or receive the parameters from HTTP header. We will explore below two scenarios, To receive the HTTP header from SOAP request. To pass the HTTP header while calling soap service. SOA version used: 12.1.3c To receive the HTTP header from SOAP request: First we need to add the property “oracle.webservices.http.headers” under binding.ws in Service element in composite.xml. This property contains the comma separated parameters that we are expecting in request. Example,  ENV,VERSION. <binding.ws port="http://xmlns.oracle.com/SOA_Learning/HTTPHeader/HTTPHeaderTest#wsdl.endpoint(httpheadertest_client_ep/HTTPHeaderTest_pt)">          <property name="oracle.webservices.http.headers">ENV,VERSION</property> </binding.ws> Now in BPEL source under receive activity, we need add <fromProperties> element which will copy the parameters from HTTP header to BPEL variable.
Read more

Integrating Weblogic with IBM MQ over JMS

Image
We can integrate weblogic with IBM MQ over JMS by creating Foreign JMS server with Links in weblogic server. We need to create .binding file which will acts as file based JNDI provider to create JMS binding to MQ resources. Will first explain how to create .binding file and then will configure weblogic to use the same. Steps to create .binding file: Firstly we need to add below jar’s in CLASSPATH jms.jar com.ibm.mq.jar com.ibm.mqjms.jar jta.jar connector.jar jndi.jar providerutil.jar fscontext.jar Create JMSProperties.config file with below properties INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory PROVIDER_URL=file:/tmp/mqm/jndi SECURITY_AUTHENTICATION=none Run below command ./JMSAdmin -v JMSProperties . config InitCtx> def qcf(ForeignCF) TRANSPORT(CLIENT) HOST(localhost) PORT(1414) CHANNEL(MQCHANNEL) QMGR(MQMRG) def q(MQ1) qmgr(MQMRG) queue(MQ1) def q(MQR1) qmgr(MQMRG) queue(MQR1) display ctx
Read more