An Oracle SOA Suite - Team Blog

  • News
    April 1, 2010

Oracle SOA and the Sun acquisition

Guest Author

I just presented the SOA product strategy at the Oracle + Sun Welcome Event this morning in Redwood Shores, after 2 earlier sessions on that same topic in Atlanta and Reston. That made me realize that I still haven’t blogged about the Sun acquisition – you might wonder how I managed to ignore the elephant in the room! Reality is that we have been very busy lately working with our new colleagues from Sun on a joint strategy and the resulting engineering plans.

Let me help you navigate the Oracle website by giving you the links you really need if your main focus of area is integration and SOA technologies:

So with this welcome to the Sun customers and Java CAPS users!


Join the discussion

Comments ( 2 )
  • Christian Brennsteiner Monday, April 5, 2010
    hi demed,
    is there something available in more detail how it will look like in the future?
    e.g. Bridging technology between SOA suite an CAPS ?
    will there be further releases of CAPS?
    if no --> possible transitions for CAPS customers
    there are some rumors about CAPS like
    can you comment those?
    regards chris
  • Demed L'Her Tuesday, April 6, 2010
    Hello Chris,
    Yes, we are currently working on new SRE and JCAPS (6.3) releases. In terms of bridging JCAPS and the Oracle SOA Suite there are quite a few projects on the table. The ones that you will see very quickly are the basic interop certifications of all standard-based interfaces (SOAP, JMS - AQ-JMS, WL-JMS, STCMS, JavaMQ etc.). Others are still being investigated. I would suggest you reach out to your Oracle account team and we can arrange for a presentation of the plan. One link I should have added to my post is the certification timelines - these can be found here: http://www.oracle.com/support/lifetime-support-policy.html
    Hope this helps addressing some of these rumors!
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.