OIC: OIC brings together all the capablities of application integration , process automation, Visual Application Building, and Integration Analytics into a single unified cloud service.
ICS: Integrated Cloud Service
Its just have integrated component. (old services)
OIC: Oracle Integrated cloud
[Sales,HCM,ERP,SCM,Service,CPQ,marketing]
OIC: 3 main component
1. Integration, 2. VBCS (visual builder cloud service) EX:Mobile, approval process 3. PCS (Process Cloud Service)
OIC is available in 2 editions: standard and Enterprise edition.
Q. Why do we need OIC? (zero coding approach)
Why Cloud: in Onpermises we have to get all infrastructure (Huge capital ), in Cloud, u have to pay how much u use.
Q Challenges in the Cloud?
1. To integrate one cloud to another cloud on the same vendor. (EX: ERP -HCM)
2. To integrate one cloud to another cloud in diff vendor. (EX: oracle - Salesforce)
3. To integrate on-premises to the cloud.
Easy to integrate applications in the cloud, On-premise or hybrid.
->By using Connectivity Agents we can connect SAAS applications and on-premises applications.
This is the anither key component of OIC, very few Apps have these features in the market.
---------------------------------------------------
Integration Style/ Pattern :
App-Driven Orchestration: Multiple sources and multiple targets.
can use all features of OIC, Ex: loop, logic, transformation, exception handling etc.
Basic Routing: 1 to 1, (1 S - 1T)
Scheduled Orchestration: Schedule based on ad-hoc basis.
File Transfer: To transfer files seamless and secure manner.
FTP Adapter (PGP encryption: )
Publish To OIC : publish msg to queue.
Subscribe to OIC: pick the msg from the queue. (It has one connection)
---------------------------------------------------
UseCase: just connect all adapters in it.
Salesforce(adapter) -> mapper -> ERP (adapter)
s1: create 2 connection one is salesforce and other one is ERP.
Use the adapter for the source and target system, go to integration use mapping for data transformation between Source and target.
If we don't have an adapter for any system then use SOAP and REST adapter for connection.
----------------------------------------------------------------------------------------------
Main Page:
Processes:
Integration :
B2B:
Visual Builder : VBCS (BPM, approval process on a web applications
Insight : (BAM- Dashboard/Analytic)
Monitoring : Instance
Settings
---------------------------------------
Integrations:
Connections, Lookups, Packages, Agents, Adapters, Libraries.
Agents(use for SAAS to on premises connectivity)
Packages: It helps to deploy the integration from one instance to another instance.
Ex: you have 50 instances in dev and u want to migrate on UAT we can do it with the help of packages.
Lookups: To store configuration value (Like DVM)
Libraries: it allows a javascript functions library. (concat string, date function, other functional logic)
-----------------------------------------------------
Monitoring: Tracking
-----------------------------------
OIC Uses/Applications:
-> Simplifies SAAS to SAAS and SAAS to On-Premises connectivity
-> Faster Time to market -Ises configuration-based approach. (build any components on the web browser and activate and test, no deployment concept.)
-> Simplified applications integrations - web-based, point-and-click experience.
-> Out-of-the-box function
ality and 100+ pre-built adapters for top apps.
-> Pre-built integration flows available in the Oracle marketplace.
-> Easy deployment and maintenance.
--------------------------
Project Extension:
.iar file: Integration Archive
.par: Package Archive
------------------------------------------------------------------------------
VBCS: Visual Builder cloud service
VBCS comes as default database (BO as a data source)
oracle ATP db
PCS: Process Cloud service
No comments:
Post a Comment