In my previous blog I have focused on how Standard Business Object e.g. Contact can be replicated from Service Cloud to Eloqua.
Now, in this blog focused will be, how Custom Object can be replicated from Service Cloud to Eloqua.
Continue reading “Oracle Service Cloud to Eloqua Custom Object Replication using OIC”
Recently, I have been worked for different use-case scenarios between Service Cloud to Eloqua Integration using OIC, hence thought to publish this blog to cover all those scenarios.
This is first in series which will use standard business Contact object data replication, there will be two more blogs, one covering Custom Object replication and another one will be importing data in bulk from Service Cloud to Eloqua.
Before, I start showing the steps how Contact Business Object data can be replicate from Service Cloud to Eloqua. I need to emphasis the important of Service Cloud Adapter and Eloqua Adapter.
Continue reading “Oracle Service Cloud to Eloqua Contact Create/Update using OIC”
Last week, I had the opportunity to do some work and part of the engagement there was to integrate some data. Easy right? It’s not that hard especially with the technology and standards we have these days. However, what was not apparent upfront until after some digging (ie research), an email and a phone call that there were no APIs to be found. “Ha ha ha … we’ve got you … there is no way you can do it now” So the challenge was accepted and instead of time travelling into the future to find a new way of doing things, I went totally retro. And hence the title “Enter The Robots“. I didn’t go and create new versions of robots or AI. I don’t create a new quantum computing paradigm. What I did do was classically known as screen-scraping. “ick“, I hear from the crowd. “How dare you?“, someone else yells out. But I say this honestly, if there is no other way to integrate and capture data, then I rather do it knowing that it is a last resort.
In this article, I walk through a few of the tips and tricks with what’s currently available to help out in this situation.
Recently, I been part of one POC where I have learned how we can consume Business Events from Oracle Engagement Cloud.
Oracle Engagement Cloud is a Software as a Service (SaaS) offering from Oracle which provides unified Sales and Service Capabilities, includes sales force automation to manage the full sales lifecycle including leads, accounts, contacts, opportunities, assets, activities, assessments, and forecasts. Leverage content on mobile, the web, and email applications etc.
Beneath the hood, there are several business object e.g. Account, Contact, Plan, Opportunity, service request etc. which form the data model to store data in back-end and exchange data with other systems.
In this blog, I will be simply demonstrating the prerequisite which are required to configure inside Oracle Engagement Cloud and OIC Sales Cloud Adapter configuration.
Even in a day and age where event-based and real-time data exchange is prevalent and growing, the truth is there are still massive amounts of data exchanged using file transfer mechanisms. Oracle has always played in this realm, but with limited success. The Oracle Managed File Transfer (MFT) application is pretty good, but nothing to write home about… or write a blog about! 😀
One reason is because moving files around and using FTP servers is not very glamorous. Another reason is because the Oracle MFT management dashboard is pretty limited. It is able to monitor various aspects of a file transfer, report success or failure and allow you to resend files. But it has no business context or the ability to understand how a file might be part of a larger business process.
Now we’re ready to create connections and integration from OIC. If you missed part 1, please go for Part 1 now. Also my colleague Carlos already wrote excellent blog, Teaching how to integrate Salesforce and Sale Cloud with Oracle Integration Cloud Service so you can look at how to configure outbound message from Salesforce.com and Salesforce Connection with Trigger from OIC.
Continue reading “PeopleSoft Integration using Oracle Integration Cloud – Part 2”
Luckily, I’ve got a chance to look at PeopleSoft integration with other SaaS app using OIC (Oracle Integration Cloud) and decided to share what I learned.
Continue reading “PeopleSoft Integration using Oracle Integration Cloud – Part 1”
We have covered multiple blogs on how to use Terraform to help automate the provisioning of environments and treat your Infrastructure as Code. Until now, for PaaS stacks, we have used Terraform together with Oracle PaaS Service Manager (PSM) CLI. This gives us great flexibility to script our own tailored PaaS stacks the way we want them. However, with flexibility comes responsibility, and in this case, if we choose to use PSM CLI, it’s up to us to script the whole provisioning/decommission of components that make up the stack. As well as what to do if we encounter an error half-way through, so that we leave things consistently.
A simpler way to provision PaaS stacks is by making use of Oracle Cloud Stack, that treats all components of the stack as a single unit, where all sub-components are provisioned/decommissioned transparently for us. For example, Oracle Integration Cloud (OIC) stack, is made of Oracle DB Cloud Service (DBCS), Integration Cloud Service (ICS), Process Cloud Service (PCS), Visual Builder Cloud Service (VBCS), IaaS, storage, network, etc. If we use Oracle Cloud Stack to provision an environment, we only have to pass a YAML template with the configuration of the whole stack and then, Cloud Stack handles the rest. Pretty awesome huh?
Similarly, as we have done in the past, we are going to use a “Build Server”. This will be used as a platform to help us provision our PaaS stacks. When provisioning this “Build Server”, I will add all the tooling it requires as part of its bootstrap process. For this, I am using Vagrant + Terraform, so that I can also treat my “Build Server” as “infrastructure as code” and I can easily get rid of it, after I built my target PaaS stack.
This is a graphical view of what I will be doing in this blog to provision an OIC stack via Cloud Stack:
In a previous blog, I explained how to treat your Infrastructure as Code by using technologies such as Vagrant and Terraform in order to help automate provisioning and decommissioning of environments in the cloud. Then, I evolved those concepts with this other blog, where I explained how to use Oracle PaaS Service Manager (PSM) CLI in order to provision Oracle PaaS Services into the Cloud.
In this blog, I am going to put together both concepts and show how simply you can automate the provisioning of Oracle Integration Cloud with Terraform and PSM CLI together.
To provision a new PaaS environment, I first create a “Build Server” in the cloud or as my boss calls it a “cockpit” that brings all the required bells and whistles (e.g. Terraform, PSM CLI, GIT, etc) to provision PaaS environments. I will add all the tooling it requires as part of its bootstrap process. To create the “Build Server” in the first place, I am using Vagrant + Terraform as well, just because I need a common place to start and these tools highly simplify my life. Also, this way, I can also treat my “Build Server” as “infrastructure as code” and I can easily get rid of it after I built my target PaaS environments and save with that some bucks in the cloud consumption model.
Once I build my “Build Server”, I will then simply git clone a repository that contains my scripts to provision other PaaS environments, setup my environment variables and type “terraform apply”. Yes, as simple as that!
This is a graphical view of what I will be doing:
In this blog I am going to show you three new capabilities introduced in Oracle Integration Cloud (OIC) that massively simplify the enablement of Application integration with extensions to Business Process Automation workflows and finally how to expose all of that as secured APIs via the Oracle API Gateway.
These three new capabilities are:
Our scenario is simple, it is an incident management extension, that requires some human intervention to manage service requests.
To be specific, let’s assume the following components:
This is a high-level view:
RedThunder.Blog 