deltalounge

SOA Suite on EC2

Setting up Amazon Web Services (EC2 and S3)

This arcticle on OTN guided me while signing up for:

• Amazon AWS
• Amazon S3 – Simple Storage Service
• Amazon EC2 – Elastic Compute Cloud

and to setup PuTTY. The only hick-up here was that I’m using the PortableApps version of PuTTY that doesn’t come with the puttygen – Key Generator.

Provisioning a SOA Server on Amazon EC2

This blogpost guided me in the provisioning of the AMI (Amazon Machine Image).

• AMIs are per region: The Amazon Machine Instance (AMI) for SOA Suite (id = ami-acb557c5) is only available in the US East (Northern Virginia) Region.
• Don’t bother to setup the Elastic Block Store (EBS) Volume. It is scripted in the latest version of the AMI, as described in step 5 of “SSH to your image and accept license”. The EBS Volume is seeded using a snapshot (id = snap-dd980db4) that is provided. This volume will be used to persist your data across sessions and AMI start/stop.
• When launching the image (during the Configure Firewall step) set the SecurityGroup to accept HTTP traffic on port 7001 in case you want to use the SOA Suite from outside the Image.

Yesterday Clemens Utschig posted a list of SOA Suite 11gR1 Patchset 2 ~ 11.1.1.3.0 (SOA) features. He says it is a non-exhaustive list. It contains features like:

• Full and complete support for BPEL 2.0 (designtime and runtime)
• Reintroduction of “BPEL domains” – that are called Partitions because there are already WebLogic Domains
• Enhancements to BPEL’s transactional behavior and audit-trail
• Full BPMN 2.0 support – part of BPM 11g which runs on top of 11g PS2 SOA core

Update: for the Java developer

In an additional post the features for the Java developer were announced. These include:

• Support for interface.java as a first class citizen next to interface.wsdl
• Full support for Spring as component implementation
• Support for EJB bindings (binding.ejb)
• Invocation of a composite service

Recently, in a press release, Oracle introduced Oracle SOA Governance. This component of Fusion Middleware consist of the following components:

1. Oracle Enterprise Repository – OER
2. Oracle Service Registry
3. SOA Management with Oracle Enterprise Manager (SOA Management Pack)
4. Web Service Manager

According to the press release it is already fully integrated with Oracle Amberpoint:

Oracle SOA Goverance 11g is fully integrated with Oracle AmberPoint, a leader in Service-Oriented Architecture (SOA) Management. The new solution provides organizations more continuity of closed-loop governance processes across both Oracle and third party applications.

Besides that it is not clear to me what is new. The latest version of the Enterprise Repository was release a month ago. Any ideas? Please leave them in the comments.

The webcast of the SOA and Integration strategy was a few days later available as the overall strategy. You can find the entire webcast here.

SOA Platform

The combined Oracle Sun solution focus boils down to the following bullets:

• Oracle SOA Suite continues as the strategic product.
• Sun JCAPS continues to be supported and maintained
• GlassFish ESB continues as an open source project
• A bridging technology is planned to support collaboration between JCAPS and Oracle SOA Suite.
• Key functions from the Sun SOA products will be incorporated in the Oracle SOA products.

Portal technologies

Oracle WebCenter stays the strategic portal offering. Support for both GlassFish Web Space Server and Sun Portal Server will be continued. An upgrade path to WebCenter is planned for both. The IP (Intellectual Property) for Sun’s Web Space Server will be released into the Liferay open source community.

On January 27th Larry Ellison and other Oracle executives outlined the Oracle Sun strategy in a live event. The webcast and sheets are available online. There is also a FAQ overview available.

Besides that there is the Oracle + Sun Product Strategy Webcast Series. If you are into Java or Middleware developement, I think the message boils down to these few sheets:

Development Tools

Development Tools Strategy

Application Server

Glassfish and WebLogic will coexist and share logic/components.

AS strategy

SOA products

Oh, and WebCenter will be the strategic portal offering.

SOA product strategy

• Integration perspective
• Oracle gets MySQL for free

This evening while playing with WinDirStat (using the Portable Apps version) I took the following screenshot:

JDeveloper Stats

To some of us it came as a surprise that SOA Suite design time stuff was no longer an integral part of the Oracle IDE. To use BPEL, Mediator, Human Task, and Adapters the soa-jdev-extension is required.

The SOA extension can be acquired using the menu Help | Check for updates, clicking Next, and selecting Oracle Fusion Middleware Products. Select Oracle SOA Composite Editor and click next to start the download. Since the extension is over 200 MB this could take a few minutes depending on the speed of your internet connection. When the download has finished, the version number details are shown and you’ll click finish to start using it.

Install from local file

Update wizard

Download the extension, and instead of selecting the Search Update Centers option during step 2 of the upgrade you choose the Install From Local File option and the appropriate file. This is displayed in the screenshot. From here on it is a Next - Next - Finish operation.

Other JDeveloper extensions

Other extensions like the AIA Composite Application Framework, PHP extension, and the SQL Developer extension can be found in the update center.

Although there were already several posts on querying AQ, like “in the queue” and “enqueue“, the next one is great when monitoring queues. We are using this to monitor AQ, especially for Oracle ESB (hence the commented addition):

1
2
3
4
5
6
7
8
9

SELECT aq.name
,      aq.queue_table
,      aq.queue_type
,      v$aq.* 
FROM   v$aq
,      all_queues aq
WHERE  aq.qid = v$aq.qid
-- use if looking for ESB AQ: and    aq.queue_table = 'ESB_JAVA_DEFERRED';
;

The query will result in something like:

It contains the following metrics:

• Waiting – Number of waiting message;
• Ready – Number of messages with status ready;
• Expired – Number of expired messages;
• Total Wait – Total waiting time per queue;
• Average Wait – Average waiting time per queue.

A describtion of the AQ and Streams views can be found here.

If you are using AQ within Oracle ESB there might be a point in time you want to tune AQ performance. In this post you’ll find the results of Metalink research, and our experience on a production system.

Queue compatibility

When creating the ORAESB schema (in version 10.1.3.3) using the script $ORACLE_HOME/integration/esb/sql/oracle/create_esb_topics.sql, the queues are created with 8.1 compatibility. This is solved in 10.1.3.4. To alter this find the statement

1
2
3
4
5
6

dbms_aqadm.create_queue_table
    ( Queue_table => qtablename
    , Queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE'
    , multiple_consumers => true
    , compatible => '8.1'
    );

and change this to:

1
2
3
4
5
6

dbms_aqadm.create_queue_table
    ( Queue_table => qtablename
    , Queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE'
    , multiple_consumers => true
    , compatible => '10.2'
    );

if you already created the queues, use this statement:

1
2
3
4

dbms_aqadm.migrate_queue_table
    ( queue_table => 'ESB_JAVA_DEFERRED'
    , compatible => '10.2'
    );

If you’re not sure check the compatibility with this query:

1
2
3
4
5
6

SELECT queue_table
,      compatible
,      recipients
FROM   dba_QUEUE_tables
WHERE  owner = 'ORAESB'
;

Streams pool size

Verify the current stream_pool_size using the following query:

1
2
3
4
5
6
7

SELECT component
,      current_size/1024/1024 "CURRENT_SIZE"
,      min_size/1024/1024 "MIN_SIZE"
,      user_specified_size/1024/1024 "USER_SPECIFIED_SIZE"
,      last_oper_type "TYPE" 
FROM   v$sga_dynamic_components
;

look for the streams pool. There are several Metalink notes on this setting (including 316889.1, 102926.1 and 335516.1). The latter has a general recommandetion per RDBMS version:

• 11g: set STREAMS_POOL_SIZE to be greater or equal to 100 MB;
• 10gR2: set SGA_TARGET > 0 and STREAMS_POOL_SIZE=0 to enable autotuning of the Streams pool;
• 10gR1: use the STREAMS_POOL_SIZE init.ora parameter to configure the Streams memory allocation;

And of course you could use V$STREAMS_POOL_ADVICE to get advice for your specific situation.

Upgrade the JDK

A described here upgrading the JDK can also give a performance boost.

One of the projects I’m involved in, uses Oracle ESB (from SOA Suite 10.1.3.3 MLR 18) running on AIX 5.3. Instead of using the default in-memory JMS the ESB is configured to use Oracle Advanced Queueing (AQ). Although there were tuning efforts before, the performance wasn’t up to par. AQ seemed to be the bottleneck, especially the dequeueing part. During the day we saw the number of messages queue up. Generally these numbers would decrease after business hours. This should have been a big problem if the number of messages wasn’t going to be tripled or quadrupled in the next month(s).

Upgrade the JVM

Previous attempts in cooperation with Oracle Consulting hadn’t done the trick, yet. To get a fresh view and some out-of-the-box thinking Marc joined the team. He performed a scan of the systems settings. Researching Oracle’s knowledge system resulted (searching on AIX & ESB & DB Adapter) in the clue to upgrade the JVM (6848406 – SLOW PERFORMANCE ON AIX ESB USING FILE AND DB ADAPTER). Although we were skeptic at first, because why tried a similar path before, we decided to give it a shot. The previous attempt resulted in errors in our code without enhancing the performance of the system.
With the AIX system a Java 5 is delivered in /usr/java5, to be more precise:

1
2
3
4
5
6
7
8

$:/jdk/bin>./java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pap32dev-20080315 (SR7))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20080315 (JIT enabled)
J9VM - 20080314_17962_bHdSMr
JIT  - 20080130_0718ifx2_r8
GC   - 200802_08)
JCL  - 20080314

To change this stop the SOA Suite and:

1
2
3

cd $ORACLE_HOME
mv jdk jdk.orginal           # rename jdk directory
ln –s /usr/java5 jdk         # Creates symbolic link

and the start the SOA Suite. With this newer Java version we had a significant performance improvement.

Remaining issue

If the change is performed as described above Enterprise Manager doesn’t allow you to browse the oc4j_soa anymore. This will result in the following error message:

Unable to make a connection to OC4J instance oc4j_soa on Application Server someserver.local. A common cause for this failure is an authentication error. The administrator password for each OC4J instance in the Cluster must be the same as the administrator password for the OC4J instance on which Application Server Control is running.

This can be solved by applying the patch for base bug 5261515. The patch adds some security jars and properties that are not in the AIX Java5 version.
Since this patch introduces issues in our code, we are working around the Em problems for now, while trying to resolve the issue.