Thursday Feb 26, 2015

Why I'm Excited About Oracle Integration Cloud Service - New Video

Having worked with Service Oriented Architecture (SOA) products for many years, I have come to the conclusion that,

in the early days, SOA was a solution looking for a problem.  

Businesses deployed standalone CRM, ERP, and other applications that were closed off from easy integration and had few if any small services that could be assembled as part of a composite application, thereby limiting the value of SOA.

Pre-integration Video LinkFast forward to today and “services“ are everywhere providing easy justification for SOA. If you want to deliver new offerings on your web site for your customers quickly, you don’t start from scratch. You leverage internal and external services (ex: GetCustomerRecord, GetCreditScore, etc.) and your project is already partially completed. That’s great progress but it took over 20 years for the concept of SOA (coined in 1994) to become the accepted standard in most medium-to-large enterprises.

Integration complexity

In contrast, Oracle Integration Cloud Service marks a dramatic shift in how we approach integration… equal to the shift from EAI to SOA but with one major difference. Instead of requiring a new learning curve on how to integrate with loosely coupled SOA, Oracle Integration Cloud Service goes in the opposite direction with a focus on ease of use. And instead of integration from scratch, its pre-integration; instead of your best guess, its crowdsourced recommendation ratings. In the past, it was a shame that the application developers who knew their respective CRM, ERP, service, marketing, etc. applications best didn’t embed the integrations themselves into the integration platforms. With Oracle Cloud Integration Service and the Oracle Cloud Adapters…that’s what happened.

And so I wrote the script for this video to graphically convey the ease of use and dramatic shift that Oracle Cloud is bringing to integration into a story of how Oracle Integration Cloud Service can connect a disconnected business.

It’s not very often that a solution to a long-standing problem is such a major shift in the right direction. It’s my belief this has happened with Oracle Integration Cloud Service.Built by Oracle

Watch the new video now to see for yourself.  I expect it will be 3 minutes of time well used. 

Link to video

Monday Jan 26, 2015

Cloud Platform Online Forum - Cloud Integration Session

Join me at the Cloud Platform Online Forum on January 28th, 2015 at 10:00 am PST/1:00pm EST (keynote start time) as I present Oracle cloud integration solutions including the upcoming Oracle Integration Cloud Service announced at Oracle OpenWorld 2014.  Learn about the challenges of cloud integration and watch a demonstration showcasing the ease of use of Oracle integration Platform as a Service (iPaaS).

Banner

Also, be sure to catch the featured Middleware General Session presenter Greg Haertling, Chief Enterprise Architect and Sr. Director of Software Development at 7-Eleven, Inc. including their impressive implementation of Oracle SOA Suite for integration. Following this session is the integration session:

Track: Middleware IT Operations

Session: Simplify SaaS and On-premises Integration 

Unless businesses develop a plan to simplify their overall integration strategy, the explosive growth of SaaS combined with existing on-premises integration is likely to slow the pace of innovation and time-to-market, as well as increase overall complexity and costs.  Attend this session to see how Oracle customers have broken through the integration quagmire and simplified integration. Hear best practices on how to better integrate Oracle cloud applications using Oracle Integration Cloud Service and Oracle SOA Suite and learn how a unified solution eliminates the divide between new cloud applications and your existing infrastructure.

See the full agenda and register here

ICS Zoom

Above is a screenshot from the integration session of pre-built integration of a service request created in Oracle E-Business Suite on incident creation in Oracle Service Cloud (RightNow)

Thursday Dec 18, 2014

SOA Suite 12c: Topology Suggestions

In this article, I make some suggestions and provide opinions on topologies for SOA Suite 12c that is commonly used and supported. Only the EDG topology is thoroughly tested by Oracle though.

  • One consideration when deciding on topologies is that Upgrade is always domain wide. All products deployed to the domain must release in the same release train and you should be willing to upgrade all of them at the same time.
  • Centralized administration is one factor but should not be the only reason to put two different products in the same domain. EM Cloud Control could be used as a solution for that. 
  • Typically Service Bus and SOA Suite belong in different tiers in an end to end architecture so they would be in separate domains. This is true if Service Bus is being used on an enterprise scale routing to multiple SOA domains and other services. However if Service Bus is used primarily for mediating and providing routing for SOA Suite Composites in a domain, it would be in the same domain, but typically in separate clusters for optimum performance and scalability. However it  is possible starting in 12c to have Service Bus and SOA Suite in the same cluster.  The only possible reason for this is reducing memory and is uncommon.
  • Governance products like OER and UDDI should not be in a SOA Suite or Service Bus domain. They should be in a separate domain. OER should be in a separate domain from UDDI. UDDI is a third party product and putting it in the same domain may cause upgrade issues.
  • You can target multiple products to the same cluster by targeting the appropriate user extensible server group to  the servers in the cluster.
    1. SOA Suite is targeted to a server by targeting either the user extensible server group SOA-MGD-SVRS or SOA-MGD-SVRS-ONLY.
    2. Service Bus is targeted to a server by targeting either the user extensible server group OSB-MGD-SVRS-COMBINED or OSB-MGD-SVRS-ONLY.
    3. BAM is targeted to a server by targeting either the user extensible server group BAM12-MGD-SVRS or BAM12-MGD-SVRS-ONLY.
    4. MFT is targeted to a server by targeting either the user extensible server group MFT-MGD-SVRS or MFT-MGD-SVRS-ONLY.
    5. ESS is targeted to a server by targeting the user extensible server group ESS-MGD-SVRS. .
  •  BAM sometimes is used outside of SOA Suite and in this case it is typically in a separate domain from SOA Suite. However BAM should be in a separate cluster in the same domain as SOA Suite if it is primarily used with that SOA Suite instance. In BAM 12c, integration between SOA Suite and BAM is a tight integration and is best done in the same domain. BAM and SOA Suite should not be co-located in the same cluster because BAM uses Automatic Service Migration for HA while SOA Suite uses Whole Server Migration. 
  • OWSM Policy Manager must be deployed to only one cluster in a domain. However SOA Suite, OSB, BAM and MFT templates target OWSM PM by default to their own clusters.
    1.  In a domain with such different clusters, put OWSM PM in its own cluster like the EDG suggests. You can target the JRF and the two OWSM PM related user extensible server groups to this cluster.
    2. OWSM PM is automatically targeted to the SOA cluster when you target the user extensible server group SOA-MGD-SVRS which is the default. However if OWSM PM  is already targeted to a separate cluster then you should target SOA Suite to the SOA cluster by targeting the user extensible server group SOA-MGD-SVRS-ONLY.

    3. OWSM PM is automatically targeted to the BAM cluster when you target the user extensible server group BAM12-MGD-SVRS which is the default. However if OWSM PM  is already targeted to a separate cluster then you should target BAM to the BAM cluster by targeting the user extensible server group BAM12-MGD-SVRS-ONLY.

    4. OWSM PM is automatically targeted to the Service Bus cluster when you target the user extensible server group OSB-MGD-SVRS-COMBINED which is the default. However if OWSM PM  is already targeted to a separate cluster then you should target Service Bus to the Service Bus cluster by targeting the user extensible server group OSB-MGD-SVRS-ONLY.

    5. OWSM PM is automatically targeted to the MFT cluster when you target the user extensible server group MFT-MGD-SVRS which is the default. However if OWSM PM  is already targeted to a separate cluster then you should target MFT to the MFT cluster by targeting the user extensible server group MFT-MGD-SVRS-ONLY.
    6. ESS requires that OWSM PM be present somewhere in the domain but itself does not target OWSM PM.
  • Follow the following guidelines for ESS targeting.
    1. In a domain with Service Bus only ESS is typically targeted to the Service Bus cluster.
    2. In a domain with SOA Suite only, ESS is typically targeted to the SOA Suite cluster.
    3. However in a domain with both SOA Suite and Service Bus in different clusters, the best practice is to target ESS to its own cluster. 
    4. MFT always has a private copy of ESS deployed to its cluster independent of any additional deployment of ESS for use by SOA Suite and Service Bus.
    5. ESS currently is positioned not as a standalone scheduler, but a scheduler for SOA Suite and Service Bus and should be in the same domain.
  • MFT is typically in a separate domain from SOA Suite or Service Bus, but could be in the same domain but in a separate cluster.
  • The best practice is to use separate domains for Healthcare and B2B and separate domains for SOA Suite and B2B. This is documented in the B2B and Healthcare documentation.

Wednesday Dec 17, 2014

Customizing Oracle MFT File Rename Java Callout

Review and Use Case

So now that you have all digested the previous Overview blog in this Customizing MFT series, you fully understand the components of Custom Actions(callouts) and have built the Newline Conversion sample from the Oracle MFT Documentation section Processing Transfers with Custom Callouts you are ready to build another real world scenario that implements a file rename inside of the MFT engine. I say inside because that differentiates it from the use case where a file is written to the file system or remote FTP server and then renamed after it is delivered. This use case is a file comes in from a Source that has extra characters in the name such a time-stamp that you wish to remove using standard Java regular expressions. I.E. order20151011.xml would be renamed to order.xml or customer12345.csv is renamed to customer.csv.

Components

XML Config File

As you know, each of the callout actions needs an xml config file that defines the interface. Below is the config file for this sample that defines things like action name, library name, help text and parameters that are configured in the designer. This sample is used in Target Pre-Processing and takes 2 parameters, SourceExp and ReplaceWith. Details for configuring callout config files were covered in the last blog entry so go reread that if this isn't clear, To proceed, just download the file from the link below or copy the bolded text into your favorite text editor and save the file RenameRegexp.xml it into a new folder named RenameRegexp.

RenameRegexp.xml

<?xml version="1.0" encoding="UTF-8"?>
  <mft:Callouts xmlns:mft="http://xmlns.oracle.com/mft"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://xmlns.oracle.com/mft callout.xsd ">
    <mft:Callout description="Rename Regexp"
      helpText="File Rename with Regular Expressions"
      groupName="Target-pre" timeout="300"
      implementationClass="com.oracle.callout.sample.RenameRegexp"
      libraryName="RenameRegexp.jar" name="RenameRegexp">
    <mft:Parameter description="SourceExp" mandatory="true"
      helpText="Source Regular Expression Pattern"
      name="SourceExp" parameterType="string"/>
    <mft:Parameter description="ReplaceWith" mandatory="true"
      helpText="ReplaceWith Regular Expression Pattern"
      name="ReplaceWith" parameterType="string"/>
   </mft:Callout>
</mft:Callouts>

Java Source Code

As you know, there are different API's for Source, Pre and Post Target callouts. This example illustrates the Pre Target interface that is not modifying the file contents like the Newline Conversion example did. To review this topic visit the MFT Documentation page titled Java Code Requirements and Tips. The java class receives 2 strings at runtime for regular expression substitution that are configured in the Designer Transfer artifact. The  new and interesting code being used here to get and set the new file name are the methods PluginContext.getTransformedInputFileName and PluginOutput.setNewFileName. The regular expression substitution is implemented with an old reliable single line of code using String.replaceAll. Below are a code snippets illustrating this.

   	PluginOutput out = new PluginOutput();
	oldfname = pluginContext.getTransformedInputFileName() ;
 	newfname = getNewname(oldfname, SourceExp, ReplaceWith);
	if (newfname != null && newfname.length() > 0) { 
		out.setNewFileName(newfname);
	}
   ... 
   public String getNewname(String oldfname, String srcexp, String repexp) {
	return oldfname.replaceAll(srcexp, repexp);

   }

Download the full RenameRegexp.java file and place it in a newly created child directory of your RenameRegexp folder called com/oracle/callout/sample.

Compile, Package and Install

This section assumes the following environment variables have been set.

  $MW_HOME where your MFT WebLogic is installed

  $JAVA_HOME where your JDK 1.7 is installed

Compile

From the command prompt, run the following command. The command is split to multiple lines.

  $ $JAVA_HOME/bin/javac

   -classpath $MW_HOME/mft/modules/oracle.mft_12.1.3.0/core-12.1.1.0.jar

   com/oracle/callout/sample/RenameRegexp.java

Package

Now use the JDK "jar" command to build a java jar file as shown below. The cmd is split to multiple lines.

  $ $JAVA_HOME/bin/jar

     cvf RenameRegexp.jar com/oracle/callout/sample/RenameRegexp.class

Install

This involves 2 steps, first copy the jar file to the MFT server callout folder and another to import the config xml file. Use the copy command shown below. Note the domain name below may be different in your environment.

  $ cp RenameRegexp.jar $MW_HOME/user_projects/domains/base_domain/mft/callouts/

NOTE: If you have an MFT export of a file transfer that uses this callout, you can import it and skip this WLST step.

Next, run a WLST command to import the RenameRegexp.xml file

  $ $MW_HOME/mft/common/bin/wlst.sh

Connect to your WebLogic Server using your host, port and admin credentials

  connect("weblogic", "<PASSWORD>, "t3://localhost:7901")

Enter the WLST CreateCallout command substituting the location of your files.

  createCallouts('/home/oracle/mft/callouts/RenameRegexp/RenameRegexp.xml')

Do a listCallouts() command to verify it worked.

  listCallouts()

Enter the exit() command to quit WLST.

  exit()

Deploy a Transfer and Test

This section requires some knowledge of Java Regular Expressions. This implementation uses the java String.replaceAll method. It is recommended to use an external tool test test your expressions in advance. There are many available but www.regexplanet.com has a nice online tool for testing your expressions before entering them into the MFT Designer. For this example, you will use following parameter values to rename a file order20151011.xml to order.xml.

  SourceExpr:  ([A-z])\d+(.*)

  ReplaceWith: $1$2

Design and Deploy

At this point, the RenameRegexp callout action will appear in your Transfers Target Pre-Processing UI and is ready to use in any Transfer. Go to the Designer and build a Transfer "Rename Transfer" with a Source and Target of "Rename FTP Source" and "Rename FTP Target". The FTP Embedded Source  uses a location of "/rename/in" and the FTP Remote Target uses a location of "/rename/out". The Transfer should look like the following screenshot.


You need to configure the Pre-Processing Action in the Transfer with the below parameters as shown in the screens below.

  SourceExpr:  ([A-z])\d+(.*)

  ReplaceWith: $1$2

Now Save and Deploy this Transfer as you would any other Oracle MFT Transfer.

Test

To test use any FTP Client to connect to the MFT embedded FTP server and copying a file named  "order20151011.xml" to the "/rename/in" folder. When completed, go to the MFT Monitoring console and view the transfer report as shown below.


Congratulations, you have implemented a very handy, configurable and reusable rename custom callout that you can use in any Transfer Pre-Target Processor Action and it only took 76 lines of code! A completed export of this Transfer is also  available for download

Monday Nov 24, 2014

Customizing Oracle MFT with Java Overview

This is the first in a series of how to customize Oracle Managed File Transfer (MFT) using java callouts. It is assumed you have a working knowledge of Oracle MFT and can build, deploy and test basic transfers with Oracle MFT. We'll start by reviewing the instructions in the documentation section Processing Transfers with Custom Callouts then discuss terminology, types, invocation order and use cases for Sources, Pre-Targt and Post-Target.
[Read More]

Friday Nov 21, 2014

SOA Suite 12c: Problem with slow domain creation

We recently heard reports about slow SOA Suite 12c domain creation and slow pack/unpack on Linux platforms.

After some investigation, we found that the reason could be low entropy of the Linux machine.

If you run into a similar issue, check the entropy of your Linux machine with the following command:

$ cat /proc/sys/kernel/random/entropy_avail

Anything less than 500 could cause slow domain creation.

You can use the command rngd to increase the entropy. This command replenishes random bytes to the value of /dev/random by using the /dev/urandom as source.

Start the rngd (as root).

$ rngd -r /dev/urandom -o /dev/random -b

You can configure it by editing /etc/sysconfig/rngd with:

EXTRAOPTIONS="-i -r /dev/urandom -o /dev/random -b -t 60 -W 2048"

Please also see support note 1947394.1 for details.



Monday Nov 17, 2014

Enhance your Customer Experience with Oracle RightNow Cloud Adapter

Oracle RightNow Cloud, the eminent component of Oracle Service Cloud, makes it possible for organizations to better understand their customers, and quickly deliver apt answers through preferred service channels and devices. Whether your organization needs to deliver web customer service, enable a cross-channel contact center, or provide faster service in the field - Oracle RightNow Cloud makes it easy for customers to engage with your brands; your employees to serve customers; and your organization to adapt to changing business needs.

To fulfill more connections, more channels, and provide even greater flexibility of integration to better serve customers needs, Oracle Cloud Adapter for RightNow has been introduced on the market leading SOA Suite 12c platform.

Oracle Cloud Adapter for RightNow

The Oracle Cloud adapter for RightNow provides intuitive wizard based approach common to all Oracle Cloud Adapters. It eliminates the complexity of cloud integration by encapsulating session management, simplifying security, and pruning many manual steps. The graphical adapter provides highly declarative way to discover the RightNow objects and operations of choice, and build the integration. The RightNow Cloud Adapter lets you connect to other cloud and on-premise applications via Oracle SOA Suite 12c which supports over 200 integration adapters and technologies.

The time to market for service solutions spanning RightNow Cloud and on-premise applications (viz. E-Business Suite, Siebel, SAP), or other cloud applications will be significantly reduced by leveraging the RightNow Cloud Adapter. These solutions also expand the value of the applications to the organization. Some of the examples of complementary business solutions that will benefit from RightNow Cloud Adapter include:

  • Agent Dispatch for Field Service:  RightNow Cloud Agent interacts with a customer via phone, chat or email and leverages back office functionality to schedule and dispatch a technician.
  • Service interactions for Sales and Marketing: Share customer information with your marketing and sales automation applications, as well as enable your sales account management teams to view service incidents with products.
  • Agreement Renewals: Enable RightNow Cloud customers to renew agreements/contracts residing in a different application.
You can access the datasheetdocumentation, and more information about the RightNow Cloud Adapter on this website.

Friday Nov 07, 2014

New SOA 12c course

We are pleased to announce the release of a new course, Oracle SOA Suite 12c: Build Composite Applications. This course teaches you how to design and develop SOA composite applications for application integration with services. You will learn how to:

  • Create a SOA composite application using JDeveloper
  • Initiate SOA composite applications using the Event Delivery Network
  • Test, debug and troubleshoot a SOA composite application
  • Apply security policies to service endpoints
To find out more information and to register visit the course page at Oracle University. 

 

Thursday Nov 06, 2014

Oracle Announces Oracle API Catalog to Simplify API Management

Oracle is extending its API Management solution with a new product, API Catalog. This will give customers the ability to simplify the publication of API services that are developed in Oracle SOA Suite and other sources. Oracle API Catalog will be part of Oracle's broader API Management solution portfolio. Oracle API Catalog also integrates seamlessly with with Oracle Mobile Suite portfolio of products for mobile enablement. Oracle API Catalog harvests services in Oracle Fusion Middleware to allow one-click publish, submit ratings, or manage re-use across other consuming applications. Oracle's API Catalog is SOAP as well as REST/JSON compliant to easily support mobile mobile applications.


Here is a validation by one of our beta customers Peter Osborne, IT Technical Lead at LG&E and KU Services Company: "The Oracle API Catalog is a straightforward, easy-to-use governance tool for capturing what services exist, what these services do, and how they can be consumed. Within hours of installation, an organization can begin cataloging their SOAP and REST web services, regardless of the underlying service technology. The harvesting functionality provides a jump start on aggregating service details, while minimizing manual data entry and the risk of duplication and error. Finally, the included JDeveloper plug-in completes the lifecycle by providing a mechanism within JDeveloper to easily view and consume documented services."

To find out more information on Oracle API Catalog, visit us: Website and explore our Datasheet.

Wednesday Oct 29, 2014

Oracle Cloud Adapter-Customer Insights Webcast: Advanstar

When your company tagline is "Connecting our Customers with Theirs", you can't afford to get integration wrong.   Watch this brief on-demand webcast now to learn why Advanstar chose Oracle integration including the new Oracle Cloud Adapters to replace their legacy integration solution to simplify IT and provide real time synchronization between cloud and on-premise applications.Advanstar Title Slide

As you may have seen at Oracle OpenWorld 2014, there has been tremendous interest in the new Oracle Cloud Adapters for simplifying the cloud to on-premises integration challenge.  In this webcast by Advanstar and OSI Consulting, you will learn how Advanstar used the "Oracle Cloud Adapter for Salesforce.com" to connect their sales reps to Oracle E-Business Suite.  As described in the webcast, here were some of the challenges that drove them to the Oracle Solution:

Challenges Prior to the Oracle Solution:

  • Informatica batch integration using a cloud replication service was not acceptable
  • Lack of real-time integration
  • Data replication jobs ran into each other causing conflicts
  • High volume caused increased problems

Oracle Integration Solution Benefits:

  • Simplified cloud integration using the new Oracle Cloud Adapter for Salesforce.com
  • Faster integration of future applications
  • Instant updates for sales reps - real time data synchronization

Advanstar Web PageOracle Cloud Adapter for Salesforce.com Screenshot

Learn tips & tricks in the second half of this webcast from integration expert Hilal Khan from OSI Consulting who implemented the Oracle SOA Suite solution.  Hilal will walk you through the simple steps to select the cloud application (Salesforce.com in this case) business objects from within the Oracle SOA Suite cloud adapter as well as the value of the offline configuration to simplify development so you don't need to be connected with the SaaS application throughout your development.  Hilal will also describe the benefits of faster and easier troubleshooting, more time for testing, and quicker overall development.  

Start simplifying your cloud integration today by viewing this short 28 minute webcast now

Watch Now

To view addition webcasts from the Oracle SOA Customer Insights Webcast Series, click here

Additional Webcasts

Monday Oct 20, 2014

Simplifying Mobile with Integration

Abstract from the Paper:

"Selecting the Right Approach for Mobile Integration
As you ponder your organization’s mobile integration strategy, start by asking what you want to offer
to customers and how much control you want to have over mobile application development. For
example, do you have reliable in­house resources or do you rely on third parties? Depending on your
specific IT culture, skills, resources, and time constraints, your organization will most likely gravitate to
one of the approaches presented in this paper.
The first three approaches represent “bottom­up” development by starting from the underlying
 enterprise IT layer:
 
•  Mobile Service Enablement – Development organizations that wish to control the entire user
experience, from the enterprise applications all the way to the mobile front­end, often favor this
approach.
•  API Management – Application Programming Interface (API) Management enables organizations to
selectively externalize their IT assets via standard interfaces made available to mobile application
developers.
•  Mobile Backend as a Service (MBAAS) – This method involves abstracting all common mobile functionality into the cloud, which frees up resources to focus on mobile front­end development and
the associated business models for mobile applications."

To access the paper: Simplifying Mobile Integration

For more datasheets, customer stories, and other resources access the Mobile Integration Resource Kit.

Tuesday Oct 14, 2014

Using PDBs with FMW

Plugging in Your FMW Repository

Power strip

The new pluggable database feature of Oracle Database 12c is incredibly useful for quickly spinning up new FMW repositories.  PDBs are now supported with FMW 12.1.3 (See Oracle Fusion Middleware 12c (12.1.3) Interoperability and Compatibility).  This allows you to run the Repository Configuration Assistant once, install the schemas you need, and then clone the database to get as many instances of the repository as you need with minimal effort on your part.  For example I recently was building a new image for some workshops.  I decided I probably wanted several different domains for different labs.  So I installed the schemas I needed in to a pluggable database using the RCU.  I then created a clone of my Pluggable Database (PDB) which I then used in a domain.  When I needed a new domain, I cloned the original PDB again and away I went.

How to Do It

  1. Create a Pluggable Database or use an existing one.
  2. Run the Repository Configuration Utility to create the schemas you need.  For the rest of this blog we will assume the prefix used was DEV.
  3. Clone the database by executing the following command (documented here)
    CREATE PLUGGABLE DATABASE soa3 from soa1;
  4. For convenience you may want to add the new instance to your TNS Names file.  This simplifies step 6.
  5. Start the Database
    STARTUP PLUGGABLE DATABASE soa3;
  6. Switch to PDB
    CONNECT dev_stb/welcome1@soa3
  7. Updated COMPONENT_SCHEMA_INFO table to refer to new database instance.
    UPDATE component_schema_info SET DB_SERVICE='SOA3.VBOX';
  8. If you want to auto-start the new PDB then from the CDB execute the command (only available from DB version 12.1.0.2)
    ALTER PLUGGABLE DATABASE soa3 SAVE STATE;

Explanations

The <PREFIX>_STB holds the credentials and connection details of all the schemas created in a given database with that prefix.  These details include the service name as well as host and port details of the listener.  Because each PDB has a unique name unless we change the service name we will still be pointing to the schemas in the original PDB, hence the need to update the DB_SERVICE column with the new PDB service name.

Benefits

So why is this useful.  A number of benefits spring to mind;

  • Easy to create additional dev/test/uat environments, especially helpful if other components also need to create schemas as not all applications use the <prefix> to keep multiple instances in the same database separate.
  • Easy to clone a production environment to allow testing in a copy of the production schemas without impacting the production environment.
  • Provides excellent isolation between environments over above having different prefixes.
  • Reduces time taken to run the RCU.
  • A helpful adjunct to the copy/paste commands provided by FMW for software and domain configurations, making it possible to clone entire environments very quickly.

Hope you find my first post as a member of the SOA Suite Product Management Team helpful.

Antony

Tuesday Oct 07, 2014

Reliving Oracle Open World 2014

The most exciting Oracle Open World conference to date, has me revelling in being a part of a ginormous, efficient, and intelligent Oracle army that is breaking shackles and helping organizations move onwards to the next frontier of innovation. An unbridled Larry Ellison in his new role as CTO showed hands-on demos to move on-prem to the cloud. Roadmap sessions revealed far more than powerpoint decks with exciting live demos of new technology with Integration Cloud Service, Mobile Cloud Service, API Management, and business driven event management for Fast Data. Outstanding customer and partner presentations, had a packed audience of more than 60,000 people sitting on the edge of their seats, grasping the immensity and reality of cloud, mobile, and the internet of things.

Oracle seems committed to the Cloud more than ever and it seems a matter of when rather than if a customer will move to the cloud. And across the board the repeat message that resonated was that moving to the cloud was going to be possible with a few pushes of a button rather than hiring experts and rewriting code. Some highlights of the Service Integration sessions at Oracle Open World 2014:

  •  72 total sessions for Oracle SOA Suite, including both Oracle-led, and external submissions across Cloud, Mobile, Fast Data, Internet of Things, and B2B.
  •  Unprecedented number of customers and partners speaking in our sessions: including Canon Imaging Systems, Ricoh Americas, Larsen and Toubro, Engineers Australia, Bristlecone, Ascension Health, Farmers Insurance, JDSU, Keste, Agilent, KPMG, Children’s Hospital of Philadelphia, LA County Department of Health, and many more. 
  • 10 live product demos; 7 hands-on labs, including Cloud, Fast Data, Managed File Transfer and several more.
  • Cloud and Mobile had spotlight this year with extensive coverage over all other solution areas including Managed File Transfer, B2B, Fast Data, and Internet of Things.

Here are some previous posts that summarize the sessions that were covered on Oracle SOA Suite this year:

Overall Oracle Open World 2014 was a mindblowing event with outstanding teamwork and exceptional delivery on every front from the customer, partner and employee base of the organization. I am personally very grateful to have been part of this amazing show. You can watch the Oracle SOA Focus On for uploads of speaker decks. And continue to learn more about Oracle SOA Suite here: oracle.com/soa

Monday Oct 06, 2014

API Integration Trends in the Enterprise

API Integration is attracting considerable interest from enterprise architects and is a hot topic at the Oracle OpenWorld Conference in San Francisco this past week. SearchSOA caught up with Oracle on how API integration trends are affecting the enterprise and recently published an interview.

Here is an excerpt: "The best API management solutions cover a range of functionality across mobile, cloud and on-premises situations and handle a variety of integration needs including SOAP, REST, B2B and managed file transfer. Other differentiators are: 

  • An integrated solution which can be deployed on-premises or in the cloud.
  • A mobile-first mindset when it comes to designing APIs for mobile developers, including mobile application-specific infrastructure to speed time to market for new apps. 
  •  Enterprise-grade tools for building secure APIs for critical back-end services.
  • Comprehensive tools for collecting the APIs which should be exposed to developers. These tools should support a range of governance processes, ideally customizable, but should not introduce heavy process overload that can reduce time to market. 
  •  Effective tools for developers to find, test and track their own use of these APIs."

To read the rest of the interview: Examine API Integration Trends in the Enterprise

And to find out more on Oracle's solution: Oracle API Management

Thursday Oct 02, 2014

SOA Suite 12c upgrade updates

This article provides two pieces of information for upgrade of soa suite.

The recommendation for free table space space for upgrade is atleast 25% free space for soa. 

The recommendation for free temp space for upgrade is atleast 800MB free temp space for soa.

If you want to upgrade a large number of jdeveloper projects in bulk without opening them one by one in jdeveloper, use jdeveloper tool ojmigrate installed in the 12c oracle home. 

ojmigrate [option]... file...|@file

Parameters (required)

file Workspace to migrate.

@file File with workspaces to migrate (one filename per line)

Options

-ade Connect to currnt ade view

-dry Dry run. Skips calling migrators

-failFast Stop migrating after first failure

-generateDefaults Don't migrate let. Let migrator helpers to generate files containing dafults for migration options. It will usually be migration.prperties file alongside the .jws file.

For more information on upgrade best practices, look here.

About

Find Us on facebook Follow us on twitter Oracle SOA Suite forum
SOA PM team
Welcome to the Oracle SOA Suite team blog. We'll use this site for news and information that did not make it into our official documentation for a reason or another.

Search

Archives
« March 2015
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
    
       
Today