Sunday, 6 August 2017

Why We Use Cloud

Cloud solutions provide significant benefits to companies of all sizes, but a recent study shows that less than 10 percent of organizations believe their existing IT infrastructure is fully prepared to address the proliferation of cloud computing, mobile devices, social media and data analytics. In the past, responsibility was with the IT department. Now business decision makers feel the cloud is critical to their businesses’ success for a number of reasons. Here are five of them: 

1. Cloud offers better insight. In a world awash in structured and, increasingly, unstructured data, 54% of leading organizations are using analytics to derive insights from big data, which helps them target customers and product opportunities more effectively. 

2. Cloud helps collaboration. Cloud allows work to be accessed from multiple devices and from anywhere, which in turns makes it much easier for teams to collaborate on shared data. 

3. Cloud drives better engagement. As we see the focus of business decision makers shift from cost efficiencies in their back-office systems to improvements in their systems of engagement, cloud is often seen as the most effective means of forging a tighter link with the customer. 

4. Speed! Fifty-two percent of leading organizations are turning to the cloud to drive more rapid innovation in products and services.

For example, Kuma Games is a leading developer of episodic video games, serving up immersive 3-D experiences — with narratives ripped from news headlines and cable TV — to millions of users each week. Since 2007, Kuma has worked with IBM to achieve the flexibility, reliability and scalability required for such immersive and dynamic gaming. A cloud solution helps Kuma Games offer a consistent high-performance, graphically attractive and seamless experience to gamers all over the world, no matter how many users are playing simultaneously. 
  
5. Cloud benefits are measurable and pay for themselves. From efficiency gains to improved employee mobility, leading organizations are able to measure significant benefits from their cloud investments, but equally importantly, can pace their investments so they avoid big up-front capital expenses and pay monthly as their business scales. 

What Should a Small- or Mid-Size Company Consider Before Moving to the Cloud? 

While many of these benefits are achievable with minimal up-front investment, companies should not rush to migrate entire businesses to cloud immediately. Here are some tips for rolling out both internal and external cloud solutions: 

1. Set clear objectives. It may sound obvious, but many IT projects begin without clear and measurable business objectives. Any cloud solution should start with agreement between the business sponsor and the implementation team regarding the scope, timing, phases and expected results of the project. 

2. Consider when (and whether) to integrate existing data and systems. Cloud solutions offer simplicity and the speed of implementation. Particularly with “green field” projects, but less so as businesses try to integrate legacy systems. Take care to understand the risks involved with migrating an existing core business system to the cloud. Look instead to focus initially on new projects with a direct impact on customer engagement. Also, remember that a cloud solution is only as good as the data it provides, so take care not to underestimate the importance of data cleansing for any system of engagement. 

3. Research solutions online and start for free. Various studies have shown that about three quarters of leading companies start their search for cloud solutions online, before even contacting a vendor. What’s more, most cloud solution providers today offer free trials to help you assess their solutions and compare them to alternatives in your environment. Because it’s “in the cloud” by definition, there is no cost other than time for this simple evaluation, which is time that will be recovered easily when you identify the best solution for your project. 

4. Consider all costs, not just initial purchase price. Some vendors, particularly in the Infrastructure as a Service (IaaS) market, make a big deal about how much they have reduced the price of their cloud services. While this may work as part of a broader marketing strategy for the vendor, it’s not the whole story. What is often not spelled out are the lifetime costs, particularly when a project or service begins to scale. In-network communication costs, for example, are charged as a separate expense by some vendors, but not by others. This can represent up to half of the total service cost, so be sure to get the full picture before deciding. 

In today’s world of mobile, social, cloud and big data analytics, speed is of the essence. While it’s still important to have a plan, with clear objectives and implementation milestones, it’s equally important to move quickly and learn as you go. For many IT professionals, this feels uncomfortable. The reality is that detailed implementation plans can be out of date before they are completed, so it’s important to start somewhere, experiment, fail quickly and learn as you start to scale up. Cloud

Saturday, 17 June 2017

OER-How To Retrieve Authtoken And Use In REX Calls Uing Bpel

How to Retrieve an AuthToken and use in REX Calls  Using Bpel

a)To invoke Rex API  from Bpel Use the below mentioned wsdlurl -

http://host:port/oer/services/RexAPI?wsdl


b)Create a Simple bpel service and bind the wsdl using SOAP Binding.Download the wsdl from url as mentioned in previous step.

















c) Drag An Invoke Activity and map with REX API external references created in step b ,use Operation  ‘Authtokencreate’ for this activity as shown in below screenshot.


















d) Drag an assign activity and update username and password accordingly











e) Go to composite.xml make sure –wsdl location for Reference API is updated accordingly






f)Testing And Comments :
Deploy your services ,On testing it should response with AuthToken  as  highlighted  in below screenshot:






OER -AUTHTOKEN AND USE IN REX CALLS USING JAVA

AuthToken and use in REX Calls  Using Java

a)Import the below mentioned jars from OER Installation path àMW_HOME/oer/applications/oer-app/WEB-INF/lib

* aler-axis-jaxrpc.jar
* client.rex.jar
* jaxp.jar
* saaj.jar
* soap.jar
* activation.jar
* xercesImpl.jar
* orawsdl.jar
* aler-axis.jar
* commons-discovery.jar
* commons-logging.jar
* http_client.jar
* mail.jar
* jdom.jar
* xalan.jar

b)Go to OER console à Enable the OpenAPI within the OER if it is not already enabled
Go to Admin --> System Settings
Search for cmee.extframework.enabled
Make sure the cmee.extframework.enabled property is set to True  as shown in below screenshot –








Save the settings

c) Add  the downloaded jars as mentioned in step: a to classpath which are available under WEB-INF/lib  folder.



















d) Compile the java code as shown below  --

packagecom.example.flashlineclient;

importcom.flashline.registry.openapi.entity.AuthToken;
import com.flashline.registry.openapi.service.v300.FlashlineRegistry;
import com.flashline.registry.openapi.service.v300.Flas




hlineRegistryServiceLocator;

import java.net.URL;

public class TestAuthToken {

FlashlineRegistry repo = null;

AuthTokenauthTokAdmin = null;

publicTestAuthToken() {
try {       
URL url = new URL("http://host:port/oer/services/FlashlineRegistry");
repo = new FlashlineRegistryServiceLocator().getFlashlineRegistry(url);
authTokAdmin = repo.authTokenCreate("username", "password");
System.out.println(authTokAdmin);
} catch (Exception e) {
e.printStackTrace();
}
}

/**
* @paramargs
*/
public static void main(String[] args) {
TestAuthToken test = new TestAuthToken();
System.out.println("success");
}

}



e) Test Your Services

On testing  it should print the authtoken as shown in below screenshot




Monday, 12 June 2017

Compensation Handler


Compensation Handler -

Compensation occurs when the BPEL process cannot complete a series of operations after some of them have already completed, and the BPEL process must backtrack and undo the previously completed transactions.
For example, if a BPEL process is designed to book a rental car, a hotel, and a flight, it may book the car and the hotel and then be unable to book a flight for the right day. In this case, the BPEL flow performs compensation by going back and unbooking the car and the hotel.




1)      Create  a Simple Bpel Code with below mentioned xsd parameters-


<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified"
                elementFormDefault="qualified"
                targetNamespace="http://xmlns.oracle.com/Application1/compensation_practice/Compensation_Practice"
                xmlns="http://www.w3.org/2001/XMLSchema">
                <element name="process">
                                <complexType>
                                                <sequence>
                                                                <element name="input" type="integer"/>
<element name="input1" type="integer"/>
                                                </sequence>
                                </complexType>
                </element>
                <element name="processResponse">
                                <complexType>
                                                <sequence>
                                                                <element name="addition" type="integer"/>
<element name="subtraction" type="integer"/>
<element name="multiplication" type="integer"/>
                                                </sequence>
                                </complexType>
                </element>
</schema>


2)      Below Is the complete bpel flow -




3)      How It Works ?-In this flow we will create a simple scope for addition and one for division. If input has 0 it will throw  an error and flow control will go to catch all block from where compensate will revert back all previous assigned values.









First -Create a scope for addition. Inside assign, logic will be –   [ input 1 + input 2 ] as shown below –








Next- Add compensation block  on the same scope by selecting arrow button  on left side,add assign activity and update  values as shown below  -











Create one more scope for division. Here logic is- if value for input1 is 0 it would throw an error and move to catch all block  as shown below –






















Logic For Catch All Block –

Here in catch all- compensate activity will revert back all previous values and  assign  new one based on  logic written in compensation handler block within each scope.








Testing –


Provide the input parameters  as shown below –(positive test case) –










Response –



Compensation Test Case –


Provide 0 in input1 as shown below –











Response    ( It compensates the addition value and resets to 0 )










Thursday, 8 June 2017

OER-How to invoke OER Using Java Rex Api

Perform below steps to update oer Console --

Start OER Server 
Enable the OpenAPI within the OER if it is not already enabled 
Go to Admin --> System Settings 
Search for cmee.extframework.enabled 
Make sure the cmee.extframework.enabled property is set to True 
Save the settings 


Java Jars -


Compile the Sample code using Java Compiler by specifying the following Jar files to classpath which are available under WEB-INF/lib folder 


* aler-axis-jaxrpc.jar 
* client.rex.jar 
* jaxp.jar 
* saaj.jar 
* soap.jar 
* activation.jar 
* xercesImpl.jar 
* orawsdl.jar 
* aler-axis.jar 
* commons-discovery.jar 
* commons-logging.jar 
* http_client.jar 
* mail.jar 
* jdom.jar 
* xalan.jar 


Code To Authenticate  With OER Server:



import java.net.URL; 

import com.flashline.registry.openapi.entity.AssetType; 
import com.flashline.registry.openapi.entity.AuthToken; 
import com.flashline.registry.openapi.query.AssetTypeCriteria; 
import com.flashline.registry.openapi.service.v300.FlashlineRegistry; 
import com.flashline.registry.openapi.service.v300.FlashlineRegistryServiceLocator; 


public class TestAuthToken { 

FlashlineRegistry repo = null; 

AuthToken authTokAdmin = null; 

public TestAuthToken() { 
try { 
URL url = new URL("http://ABCD/oer/services/FlashlineRegistry"); 
repo = new FlashlineRegistryServiceLocator().getFlashlineRegistry(url); 
authTokAdmin = repo.authTokenCreate("admin", "welcome1"); 
System.out.println(authTokAdmin); 
} catch (Exception e) { 
e.printStackTrace(); 



/** 
* @param args 
*/ 
public static void main(String[] args) { 
TestAuthToken test = new TestAuthToken(); 

Tuesday, 6 June 2017

SOA CLOUD SERVICES -CONCEPTS

What is SOA Cloud Service ?


Oracle SOA Cloud Service provides a PaaS (Platform as a Service) computing platform solution for running the following applications in the cloud:
  • Oracle SOA Suite
  • Oracle Service Bus
  • Oracle API Manager
  • Oracle Managed File Transfer
  • Oracle Real-Time Integration Business Insight
  • Oracle Business Activity Monitoring
  • Oracle B2B



          Advantages -

          Reduce costs-You can reduce IT maintenance and administrative costs. Oracle handles all                   platform provisioning, installation, and domain configuration. Oracle SOA Cloud Service is 
          subscription-based, meaning you only pay when using the service          .

  • Create test environments in the cloud. You can quickly subscribe to Oracle SOA Cloud Service to create application test environments in the cloud. There is no need to provision and configure your own servers. Move workloads to the cloud, from cloud to cloud, and from cloud to on-premises environments. When testing is done, you can release your subscription.
  • Monitor and manage your environment. You can initiate backups, patching, scaling, and recoveries with minimal configuration from the cloud. These tasks are handled for you by Oracle.




How To Deploy Oracle OSB Into SOA CLOUD SERVICES?



Please follow below url to learn more -


http://www.oracle.com/webfolder/technetwork/tutorials/obe/cloud/sscs/DeployingOSBApp_Cloud/sb-app-cloud-deployment.html




Difference between SOA And Cloud  -


Some features of Oracle SOA behave differently in the cloud than in an on-premises environment-

  • Because shared disk is currently not available, writing to a shared file from multiple managed servers running in a cluster is not possible. To make this work in the cloud, managed servers would have to write to a file on their own local disks, and then an additional process would have to consolidate the files on one of the VMs.
  • File adapter read actions — each managed server only reads from its local directory.
  • JMS store and JTA transaction logs must use the Oracle database instead of file stores.
  • Connectivity between Oracle SOA Cloud Service adapters and on-premises applications might be blocked by your corporate firewall. Connections can be established by using an SSH tunnel from the application server to which the adapter connects.
  • The SOA debugger and automatic SOA composite application tester (unit tester) in Oracle JDeveloper are not supported when connecting to the SOA Cloud Service server.
  • Reports are not supported in Oracle Real-Time Integration Business Insight, installed as part of the Integration Analytics Cluster service type.
  • The iWay application adapters listed under Application Adapters (iWay) on Oracle Cloud Adapters Documentation are not supported by Oracle SOA Cloud Service.
  • The Oracle Traffic Director high availability features 12.2.1.2/12.1.3 are not supported with Oracle SOA Cloud Service.
  • Dehydration does work in the cloud as it does in the on-premises environment as described in Fusion Middleware Administering Oracle SOA Suite and Oracle Business Process Management Suite 12.2.1.2/12.1.3