Cloud Computing Solutions- Subscription Based IT Model
Deploying a Cloud App or subscribing to a cloud based service is fairly simple isn't it.
Then what is troubling most of CTO's minds today ??
- how on Cloud assets fit with most of the enterprise on-premise systems and other cloud applications?
- which business processes are involved to achieve this?
- Is there a need of another enterprise data model, ie independent of cloud data model?
If you notice these questions are not new but the same ones which were relevant for any type of integration project, in the past.
Then where's the real challenge in cloud integration different from traditional on premise integration
Departmental Autonomy
In today's Cloud based business world, individual departments and lob's sometimes subscribe to cloud and Software as a Service (SaaS) applications, without IT's knowledge and often ignoring best practices
Disparate User Interface
Every SaaS vendor has a unique integration API. Combine packaged integration tools from multiple SaaS vendors and soon, you may find yourself managing disparate user interfaces and writing a lot of custom code using a variety of different programming languages.
Increased Enterprise Complexity
As you expand an on-premise application infrastructure to include SaaS applications in an ad hoc fashion, the complexity grows.
All aspects of Cloud Integration should align with the strategic visions of IT such as audit and compliance, security, standards and governance. Smart Cloud integration such as these helps you reap the real benefits of greater flexibility and lower costs.
IT has had multiple integration paradigms, from CORBA to Client/Server to Web services, EAI and SOA.
No proper planning, it’s easy to end up with an “Accidental SOA Cloud Architecture” characterized by point-to-point connections from individual departments to the cloud.
A SOA Foundation for on Cloud Application
Most cloud applications support Web Services, a Service Oriented Architecture (SOA) is an ideal platform to address cloud integration. Many established SOA concepts, considerations, and design patterns are even more relevant in the world of cloud integration than in an “on-premise-only” scenario.
With Oracle SOA Suite you can:
set up and manage universal services and orchestrate them into composite applications and business processes
- shared services, process orchestration, event processing, and business activity monitoring with an Enterprise Service Bus
Try this Cloud Integration Examples using Oracle SOA Suite:
Oracle Fusion Applications Integration using Oracle SOA Suite
Follow these steps to invoke Web services from Oracle Fusion Applications, :
1. Download the WSDL from the Oracle Enterprise Repository for Fusion Applications cloud hosted instance (http://fusionappsoer.oracle.com ) - . Simply replace the hostname and port and download the WSDL. To ensure that the service you have selected can be invoked from external clients, click on the Taxonomy tab of the service definition and ensure that Keyword=External is present.
2. In Oracle JDeveloper, create a SOA project with a BPEL process that needs to integrate with Oracle Fusion Applications. Create a partner link based on the WSDL obtained in step 1.
3.Apply a compatible security policy to this partner link. If your environment has an SSL enabled environment, use the out-of-the-box oracle/wss_username_token_over_ssl_client_policy. You can also choose the equivalent SAML policies (for identity propagation) or WS-Security message protection enabled policies if these have been enabled in your environment.
To get invoked via outbound services from Oracle Fusion Applications, you would follow these steps:
4. Set up a Receive activity in a BPEL process with a SOAP endpoint and implement the process based on the WSDL and XSD documented by Oracle Fusion Apps in the Apps Composer Object Workflow Outbound Message page.
4. Set up a Receive activity in a BPEL process with a SOAP endpoint and implement the process based on the WSDL and XSD documented by Oracle Fusion Apps in the Apps Composer Object Workflow Outbound Message page.
This composite you created works as intermediary web service that understands the Fusion objects and mediates the requests to other on-premise or cloud applications as needed—for example, to synchronize new customers created with the on-premise Master Data Management system or to create them as Contacts in the Oracle RightNow CX cloud service.
5. Deploy the composite and obtain the endpoint URL.
6. In Oracle Fusion Applications, register the endpoint URL in the Application Composer Object Workflow page in the Outbound Message page activity for the object. You can now receive this outbound message in your SOA composite and process it as per your required business process.
