06 ics pre built flows

8/15/2019 06 ICS Pre Built Flows

1/34

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Highly Restricted1


2/34

Integration Cloud ServiceAdvanced Topics


3/34

Pre-Built Integrations


4/34


Pre-Built integrations • Oracle-created integration

Oracle Marketplace

• You import integratio

Oracle Marketplace apackage.

• These integrations ardesignated with a BUORACLE

• You can clone and edintegration flows

• You can also customize mappings

e.g. adding custom f


5/34Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Highly Restricted5

REGISTERING PRE-BUILTINTEGRATION FLOWS


6/34

6

Flow Provisioning Lifecycle: Development

• Partners develop, tests and certifies flows• Develop flows and versions using any partner ICS instances

• Version control is out of scope of ICS – use ADE, Git, ODCS etc.

• Ensure forward compatibility with application versions i.e. ensure SaaS APbackward compatible

• ICS flows are tagged with version metadata (major/minor versions)• Minor versions considered backward compatible patches and auto-updateab

• Patches are assumed to be fully packaged artifacts and cumulative in nature


7/34

7

Pre- Built Flow Marketplace “Store”

Flow Name (STORE) FlowVersion

Minimum Apps Versions Deployment Policy Download URI, README etc.

OSC_CONTACTS_PUBLISH 1.0 OSC R8, RN 14.5 Mandatory http://.../store/osc_contacts_pu

RN_CONTACTS_SUBSCRIBE 1.0 RN 14.5 Mandatory http://.../store/rn_contacts_sub

OSC_RN_INCIDENTS_SYNC 1.0 OSC R8, RN 14.5 Mandatory http://.../store/osc_rn_incident



OSC_CONTACTS_PUBLISH 2.0 OSC R9, RN 14.11 Recommended http://.../store/osc_contacts_pu


http://.../store/osc_contacts_publish-1http://.../store/rn_contacts_subscribe-1http://.../store/osc_rn_incidents_sync-1http://.../store/osc_contacts_publish-2http://.../store/osc_contacts_publish-3http://.../store/osc_contacts_publish-3http://.../store/osc_contacts_publish-2http://.../store/osc_contacts_publish-2http://.../store/osc_contacts_publish-3http://.../store/osc_contacts_publish-3http://.../store/osc_contacts_publish-2http://.../store/osc_rn_incidents_sync-1http://.../store/rn_contacts_subscribe-1http://.../store/osc_contacts_publish-1


8/34

8

Flow Provisioning Lifecycle: Registration

• Certified flows are packaged for delivery to the Oracle Cloud Marketpla

• Provide Metadata e.g. Flow Name, Version, Min Apps Versions, Readme U• For patches, provide deployment policy of “Mandatory” or “Recommended

• ICS audit utility qualifies flow e.g. patch deployment policies

• Artifacts are packaged and stored in the Storage Cloud Service

• Approved pre-built Flows available in the Oracle Cloud Marketplace

• New versions and patches are registered with new artifacts• Version numbering should indicate succession


9/34

9

ORACLE PARTNERPORTAL


10/34

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 1210

Partner can gService portaMarketplace.

Partner can alhttps://cloud.orac

to get to the p


11/34


Partner needsOracle.com Sto access the


12/34


Partner can stCreating a Liwatch tutoriastarted


13/34


On clicking “Listing” partnto this WYSI

WYSIWYG esignificantly

learning curv


14/34


The WYSIWalso used for listing


15/34


Partner can adVideos or Scrwithout leaviWYSIWYG e


16/34


Partner can sulisting for appcome back lathat


17/34


Partner can chstatus of Submlistings


18/34


Once approve

Partner can plisting to the M

Partner also hoption to Witlisting or creaVersion


19/34


On the ReporDashboard, Pview key metto their listingMarketplace


20/34


Partner can vdetails under the Marketpla


21/34

21

Register Pre-Built Flow – Provide Metadat


22/34

22

Register Pre-Built Flow – Specify ICS as T


23/34


24/34

24

INSTALLING PRE-BUILTINTEGRATION FLOWS


25/34

25

User Chooses Pre-Built Flows from Marketplace


26/34

26

User Filters Pre-Built Flows from Marketplace


27/34

27

Tenant Administrator Downloads via “Get App”

l d


28/34

28

“Get App” Implementation Today


29/34

29

ICS Marketplace Integration – Customer Actions Summa

• Browse/buy a package frMarketplace

• Download a package• Activate the package

• Download the next versiopackage when available

• Reactivate the latest vers


30/34

30

ICS Marketplace Integration – Web Console UI

• ICS provides a punch-out link to Marketplace from ICS lapage (for end users)

• Customers can use this link to be transferred to Marketplafor browsing available packages

k l ll


31/34

31

ICS Marketplace Integration – First time install

Package1.0

Create Contact V1.0 InactiveUpdate Contact V2.0 Inactive

Package1.0

Create Contact V1.0 ActivatedUpdate Contact V2.0 Activated

CustomizationActivate

Package1.0Create Contact V1.0 InactiveUpdate Contact V2.0 Inactive


PCreate CoUpdate Co

Test

Production

Marketplace

1

2

4 Import5

Activate6

GetApp

GetApp

If there is no customization, step 5 is optional.

ICS M k l I i U d /P h


32/34

33

ICS Marketplace Integration – Upgrade/PatchPackage1.0

Create Contact V1.0 ActivatedUpdate Contact V2.0 Activated


Package1.0Create Contact V1.0 Inactive Update Contact V2.0 Inactive

Package1.1Create Contact V1.1 Activated

Update Contact V2.1 ActivatedCustomization

Activate

Test

ProductionMarketplace

1

2

4

Import5

Activate6

GetApp

GetApp

Create C

Update C

Create CUpdate C


Update Contact V2.0 ActivatedPackage1.1



Update Contact V2.0 ActivatedPackage1.1


If there is no customization, step 5 is optional.


33/34



34/34


06 ics pre built flows

Documents