Simon Haslam's Oracle Fusion Middleware blog

Java Cloud Service - initial impressions for WebLogic architects and administrators

There's no doubt that "the cloud" is coming, even in the relatively conservative world of mission-critical Oracle platforms.

At the end of 2012 I took a trial of what was then "Java (or WebLogic) as a Service" (now known as "SaaS Extension"). Back then I wasn't hugely impressed - yes, I could deploy a simple web app, but the WebLogic environment was very heavily constrained and almost entirely hidden from the administrator - no WebLogic console, no WLST, minimal logs. As a result as soon as I tried to deploy something non-trivial, in this case Apache Roller (the software running this blog), I ran into all sorts of class white-list issues and with little debug information so I quickly gave up in despair!

Anyway here we are, over 2 years later, and Oracle's latest "Java Cloud Service" (JCS) is looking far more promising, so here are my initial impressions of what I've seen and read. First things first: JCS comes in 3 variants:

  • Java Cloud Service - SaaS Extension: essentially this is product I tried previously which is now targetted at extending Oracle's SaaS applications (including cloud-based Oracle Fusion Applications), presumably with relatively simple ADF apps.
  • Java Cloud Service - Virtual Image: this is a single instance WebLogic VM intended for development use and simple testing.
  • Java Cloud Service: the "full" version (Oracle doesn't seem to have a distinct name to differentiate it) which can be clustered and is designed for production workloads.

For this article I'm only going to focus on the last of these options, i.e. fully clustered WebLogic with root level access to the VMs but automated provisioning and management provided by Oracle! 

Pricing

Before we get into too much technical detail, let's get an idea of pricing for a single, production-grade environment.

[Read More]

Should I use Oracle RAC for High Availability?

Almost all of my work involves high availability at one or more tiers, so options for Oracle Database resilience comes up regularly. Therefore I thought it would be worth writing down some of the considerations. 

Let's rewind for a moment: Real Application Clusters (RAC) was introduced in Oracle 9i to allow you to build powerful clustered database systems from of commodity hardware (typically x86 Linux servers running one or two dual core processors). RAC databases were designed to compete with the large single-instance databases running on SMP Unix servers made by IBM, HP and Sun - essentially shift spending from hardware to Oracle software (this was a long time before Oracle's acquisition of Sun Microsystems). In other words, RAC was primarily designed for scalability; high availability was a side effect.

Options & Prices

If you are looking at high availability options to protect Oracle databases here are your choices: 

  • Real Application Clusters (RAC) is the most sophisticated version of the Oracle Database and allows multiple instances to run concurrently on the same data on different nodes.
  • RAC One Node (RON) is a variant of RAC - the RAC cluster is still provisioned but a database is only allowed to be running one instance at any given time (except during switch-over during maintenance periods).
  • Enterprise Edition is the traditional single-instance Oracle Database which may or may not (typically not) be run on ASM.
Read more for whether you should use RAC or not to support your availability needs.[Read More]

OPSS Keystore Service - centralised key management

This is a topic I've been meaning to write about for a while: FMW Infrastructure 12.1.2 introduced a rather nice OPSS Keystore Service (KSS) which is now used by default in SOA Suite 12.1.3 (and other 12c products soon no doubt).

As most readers will know WebLogic, and therefore the layered products that sit on top of it like SOA or WebCenter, uses Java Keystore files (.jks) to store server identity certificates and trust certificates/key-chains (before JKS people used flat files).

If you're building clusters you want to centralise configuration where possible to keep things simple - that's why it's nice to put things like the server memory parameters in the domain configuration. Unfortunately you still had to distribute (and later update) JKS files to each host... until KSS arrived.

What the Keystore Service does is to provide keystores to WebLogic server instances - at run-time from from a central place (the OPSS schema in the Fusion Middleware infrastructure repository).

Managing the Keystores 

You can manually manage the keystores using EM Fusion Middleware Control, via the Security menu on the domain. By default you will have demo trust and demo identity keystores, for example created by the Configuration Wizard, but you can create your own and delete the demo ones. See the documentation at: https://docs.oracle.com/middleware/1213/idm/app-security/kssadm.htm.

Keystore management screen in EM FMWC

[Read More]

Upgrading to SOA 12c and details of the next UKOUG Middleware SIG

SOA 12c is the most important release of Oracle's flagship integration product set that we've seen for 5 years (when 11g was launched). Oracle has also now produced the first SOA 12c bundle patch-set (12.1.3.0.1) so in my opinion any new SOA installations should definitely be using 12c, and existing 11g users should be seriously considering upgrading to take advantage of the many new features.

SOA Suite 12c

For administrators what is particularly nice about this release is that a lot of work has clearly been put into the upgrade process, building on some of the changes introduced in WebLogic 12.1.2. The upgrade is actually surprisingly straightforward...

[Read More]

What you need to know about the new ODA X5-2

Today, as part of the "Next Generation of Oracle Engineered Systems" webcast,  Larry Ellison launched the new X5 systems. This bullishly-titled post attempts to summarise what's new specifically with the ODA X5-2, and what's most important, especially for those using ODA Virtualized Platform (ODA VP) to build entire Oracle infrastructures as an appliance.

We've known since last September when Intel released the Haswell-EP processors (the E5-2600 v3 models) that there would likely be refreshes to many of Oracle's engineered systems. However for this year's ODA refresh there have been far more changes than the previous one (which was just the processor update and fibre option). 

Oracle Database Appliance X5-2 

Summary of Changes 

Here are the most significant changes in the ODA X5-2, as compared to the previous X4-2 generation, biased towards my perspective of running Fusion Middleware products, and associated databases, on ODA VP for O-box:

  • Extra SSD on shared storage ("ODA Flash Accelerator") to hold some database data ("ODA Flash Cache") and ACFS metadata ("ODA Flash Files")
  • 40Gb/s InfiniBand for interconnect between server nodes
  • DDR4 memory with the option to upgrade to 768GB per node, so 1.5TB total
  • SAS3, which runs at 12 Gb/s - I assume/hope this is for connections to server disks, internally within the array(s) and between the arrays and servers
[Read More]

Search this blog

About me
Oracle ACE Director (Middleware and SOA)
Presentation downloads



I'm speaking at Oracle OpenWorld


UKOUG Ambassador Partner
Oracle WebLogic Server 12c Certified Specialist
Oracle WebLogic Server 12c Certified Specialist

Links

Feeds