Cloud Native, Big/Fast Data, Containers. AWS, Azure and GCP certified..
The 27th leap second will be officially applied December 31, 2016 at 23:59:60 UTC. For Oracle DB instances on RDS the following applies:
Oracle SOA Suite is certainly the most comprehensive and also the most complex product of the classical WLS / OSB / SOA Suite stack. There are plenty of tools and other products tightly interwoven with SOA Suite:
It all starts with the installation where a supported database is required for the meta data repository. The necessary schema are created with the separate repository creation utility (RCU). Testing processes is done from Oracle Enterprise Manager. Finally developing BPEL processes requires JDeveloper as an IDE.
That’s it to get started yet more complex projects often involve a Oracle Web Service Manager, and sometimes a repository and a registry.
The recipe below is part III of a series of introduction recipes covering Oracle Fusion Middleware. It’s reduced to the max and as buzzword free as it gets. It certainly doesn’t replace an in-depth training though.
For a better understanding make sure to read part I and II first:
Part I: Basic SOA Principles (not really related to OFM) and Oracle Fusion Middleware (OFM) Introduction
Part II: Oracle Service Bus (OSB) for the Busy IT Professional – an Introduction
Part III: this document
You can download the SOA Suite recipe as a PDF file from here. Enjoy!
This recipe is straight out of my book WebLogic Server 12c: Distinctive Recipes
this is more a note to myself, because I keep forgetting the details and then I get angry about myself when I am in a hurry 😉
If you quickly require a database with WebLogic 12.1.1 (or some other version 10.3.3 or later, because since then WLS comes with Derby) and some content (e.g. to try some monitoring tool or a WLST script or something), do the following:
– make sure you have the WebLogic samples and the sample DB installed.
– create a new domain.
– in the domain’s setDomainEnv.sh under DOMAIN_HOME/bin
change the DERBY_FLAG from false to true.
– start the Admin server which will start the Derby database as well.
– Create a data source using the following values:
DBName: medrec Host: localhost Port: 1527 Username: medrec Password: medrec
– Test the connection pool after creating it. It should work right away.
Done!
Amazon Web Services improved its Relational Database as a Service (RDS) for Oracle. It now supports APEX (finally, see the lengthy APEX discussion here), the OracleXMLDB and Virtual Private Cloud (VPC).
For more information:
Since today Oracle EM is available with the Relational Database Service in Amazon Web Services.
RDS instances come with a free trial for 60 days and there is no additional cost for OEM.
I recommend to read my Cloud Databases whitepaper to get started, follow the discussion of Oracle DB instances in this previous posting and give it a try yourself.
Here is a screencast that explains how to create an Oracle DB instance in AWS, how to enable OEM (just in case you are an admin) and how to connect to your cloud instance with a local installation of NetBeans (in case you are a developer).
Oracle WebLogic Server 12c Book
Oracle Middleware and Cloud Computing Book