Integration Cloud Service Deep dive

Editor's Notes

• #5: Integrations: Connect two cloud applications and define how they interact Connections: Define connections to the cloud and on-promises applications Lookups: Map the different values used by your applications to describe the same thing Packages: A package associates to integrations and can be used as a way to group them
• #6: Before creating a integration between cloud applications the connections to these applications need to be defined first.
• #7: All connections are listed by default; a connection can have the status draft, in progress or configured.
• #8: Configured connections are connections that are ready to be used in integrations
• #9: To find specific connection there is a searchbox which accepts the * as a wildcard character. Every type of adapter has its own cloud icon.
• #10: Click on the info icon to display the created and last updated details of a connection.
• #11: On a (configured) connection it is possible to execute a few actions. A connections can be edited, cloned and deleted. Some connection allow the metadata to be refreshed.
• #12: A connection can be edited on the fly…
• #13: so if WSDL URL is changed or …
• #14: the credentials are changed the settings can be updated.
• #15: Connections can be tested by clicking on the test button.
• #16: There are 9 kinds of connection types: Oracle ERP Cloud: Connector for the Oracle ERP Cloud Rest Adapter: Generic Connector for REST APIs Web Service (SOAP) Adapter: Generic Connector for Web Services Eloqua (Marketing Cloud): Connector for the Oracle Marketing Cloud Messaging Cloud Service: Connector for the Messaging Cloud Service Oracle HCM Cloud: Connector for the Human Capital Management Cloud Oracle Sales Cloud: Connector for the Oracle Sales Cloud Oracle RightNow: Connector for the Customer Service Support Cloud Salesforce: Connector for the Salesforce CRM (SaaS)
• #17: To create a new connection click on the “Create new Connection” button at the top right corner.
• #18: For this connection we select the Rest Adapter.
• #19: Create the connection by giving it a unique name / identifier and a version number. You can have multiple versions with the same connection name. A description is optional but useful any day.
• #20: The initial connection is created. On this page the connection settings can be configured like the admin email address to report problems or changes of this connections and the URL and Security settings.
• #21: Clink on Configure Connectivity button to enter the REST URI
• #22: First enter the REST URL of the Service and click on the “OK” to accept the value.
• #23: Secondly add the security credentials when needed or select the no security policy option.
• #24: Finally click on the “Test” button to test the connection settings…
• #25: If the test is successful the connection will get the status “configured” and can be used by integrations. Save the connection by clicking on the “Save” button.
• #26: Click on the “Exit” button to return to the list of connections…
• #27: The newly created connection has the status “Configured” and is by default visible on the top of the list.
• #28: After defining the connections it is time to create a integration between two cloud apps.
• #29: All integrations are listed by default; a integration can have the status draft, in progress, configured, active or failed activation…
• #30: Integration with the status “Configured” are 100% valid and ready to be activated…
• #31: After succesfully activated the integration is active and the adapters can exchange messages, but…
• #32: When activation of an integration can fail, for example the created mapping(s) are not valid or one of the used connections has problems.
• #33: To find specific integration there is a searchbox which accepts the * as a wildcard character. This example shows all integration that start with the letters KV.
• #34: On a integration it is possible to execute a few actions based on its status. A connections can be viewed, edited, cloned, exported and deleted. Active connections can be deactivated. Some actions are disabled in certain statuses.
• #35: When viewing or editing an integration the Integration Canvas is used. It consist of a source and target adapter connection. Between the adapters you can create mappings for the request and for the response flow. It is also possible to enrich data by calling a second adapter. This is possible on both the request as response flow just after the source and target adapter.
• #36: When viewing or editing an integration the Integration Canvas is used. It consist of a source and target adapter connection. Between the adapters you can create mappings for the request and for the response flow. It is also possible to enrich data by calling a second adapter. This is possible on both the request as response flow just after the source and target adapter.
• #37: A Generic SOAP Connection can be created without the creation of a connection. First enter the basic information and choose to define it from an existing schema or in this example a WSDL.
• #38: Secondly enter the WSDL URL and choose the Port Type and Operation to use.
• #39: In this example it is also a Generic SOAP connection, it works just like the source SOAP connection, but uses a different UI.
• #40: Besides the source every integration needs a target.
• #41: If extra data is needed that is not available in the request or reponse message of an adapter it is possible to use callouts to a second adapter connection.
• #42: In this example it is also a SOAP connection to the same service as the target, but it collects extra data from another operation.
• #43: A integration is nothing without mappings. There is a request and response mapping, but first lets look at the request mapping…
• #44: The request mapping is straight forward. The input is mapped to the only field available.
• #45: Secondly lets look at the response mapping…
• #46: The reponse mapping, maps the response from the target adapter to the source adapter. If you have callouts the variable data is also available for this mapping. In the response mapping you can have access to a maximum of four data objects. To view the XSLT mapping behind it or to create more advanced mappings, click on the element name…
• #47: In this detailed view mode you can mapped source fields to target fields, view to used XSLT and possibility to edit the structure using Mapping Components.
• #48: Mapping Components include funtions for conversions, dates and strings, Operators and XSL elements like choice, when, other structures.
• #49: Other options include the view options for collapsing the structure and scrolling to first or last element…
• #50: It is also possible to filter on the available fields to show all fields, only mapped of unmapped fields, or to only show fields from a specific data object.
• #51: The source and target trees can be detached as well by clicking on the “Detach” button…
• #52: This view can be useful if you have a lot of indentions.
• #53: Intergrations differ based on the adapters and interface.
• #54: To create a new integration click on the “Create new Integration” button at the top right corner.
• #55: There are three kind of Integrations: Map My Data: Drop source and target onto a blank canvas Publish to ICS: Connect your source to send messages to ICS Subscribe to ICS: Add targets to receive messages from ICS
• #56: To create a new integration click on the “Create new Integration” button at the top right corner.
• #57: There are three types of integrations. Map data between two cloud adapters, publishing messages to ICS or subscribing to message from ICS.
• #58: Create the integration by giving it a unique name / identifier and a version number. You can have multiple versions with the same connection name. A package name and a description is optional but using a package name you can group integrations together.
• #59: The initial integration is created. On the integration canvas the source and target adapters can be defined plus their mappings…
• #60: Let’s start by drag and dropping the Generic Web Service adapter from the Technologies catagory to the source.
• #61: Fill in the basic information. For this example the SOAP connections is defined from an existing WSDL. Click on the Details header to proceed.
• #62: Provide the WSDL URL and select the port type and operation. For this example I’m using a WSDL that is available publicly on the internet. Click on the “Done” button at the top right to accept the connection settings.
• #63: The source is created. The second part is to create the target. For the target we use the REST adapter we created ealier. The REST adapter can be found under the Connections list to the right. Drag en drop the adapter to the target dropzone.
• #64: Adapter connections are more advanced and more configuration is needed. This is done by a 5-step wizard. In this first step give the endpoint a name and optional description. Define the endpoint relative to the given API url and HTTP method. It is possible to use template parameters in the Endpoint URI by using curly brackets with the name of the parameter in between. At last you can specify if you want to add / review request parameters.
• #65: When checking the “review Parameters” checkbox this step is shown where it is possibile to add query parameters and/or define the type of the template parameters. Click on the “Next” button to proceed.
• #66: At the next step you can select the type of input the endpoint requests and using a schema of sample file you can define the data object. Click on the “Next” button to proceed.
• #67: At the next step you can select the type of output the endpoint returns and using a schema of sample file you can define the data object. Click on the “Next” button to proceed.
• #68: The last step contains the summary of the configured connection, like the service URI, method and response media type, but it also can show query parameters. Click on the “Done” button to accept the settings and create the adapter.
• #69: The source and target is now created, I suggest to save the integration at this point, because it is not autosaved. You can hide the connections palette to create more room for the integration.
• #70: Now it is time to create het request mapping, first click on the mapping image and secondly on the plus icon to create the mapping.
• #71: It is possible to map the source field CityName to the template parameter city, but for more advanced mappings click on the field you want to be mapped…
• #72: In the mapping builder you can also drag and drop the source to target fields, but you can also use mapping components to for example concatenate the two source fields.
• #73: This is the result, the mapping builder shows the created XSLT structure. To create the mapping, click on the “Save” button at the top right.
• #74: After saving return to the mapping to see the mapping you made visually.
• #75: Do the same for the response mapping.
• #76: This is also a easy mapping that can be done by dragging to source field to the target field.
• #77: If you exit the mapper without saving the latest changes a pop-up is show to ask if you want to save the changes that exist.
• #78: The integration now consists of a source, a target and the necessary mappings, but in the top right it is mentioned that the integration is still not completed. Click on this image to find out why…
• #79: A pop-up is shown and list the tasks that are not completed yet. Every integration need to have tracking so lets add then. Click on the “Close” button to return to the canvas.
• #80: Click on the “Configuration” button on top, to the right…
• #81: Configure the business identifiers to track this integration with. Drag and drop upto 3 fields to create business identifiers…
• #82: For each entry enter the mandatory tracking name and help text. A primary identifier is required. With multiple fields the primary identifier can be choosen. Click on the “Done” button at the bottom-right corner to accept the values.
• #83: The integration is now 100% completed. Click on the “Save” button to save the latest changes and exit the canvas.
• #84: The integration is moved to the state “Configured” and is ready to be activated. To activate the integration click on the “Activate” button…
• #85: First a pop-up is shown. The activator has the choose to enable detailed tracing, but activation will take longer, because is add messageflow tracking. Click on the “Activate” button ones more to activate the integration.
• #86: After a minute the integration is activated. The endpoint where the integration runs on is visible after clicking on the info icon.
• #87: Are there any question in this point of the presentations?
• #88: ICS also has a special kind of integration. It support the use of Lookups. For everybody that uses SOA Suite, it’s a DVM.
• #89: The Lookups page show all lookups in one list. A few actions can be taken on each lookup. A lookup can be edited, cloned, expored and deleted.
• #91: A lookup is a table of connectors and domain value mappings. You can easily add other connectors or more values.
• #92: When adding a connector column you first need to select the connector for the values by clicking on the header name “Use Connector #”.
• #93: For example the Rest Adapter…
• #94: And enter the associated domain values.
• #95: A Lookup can also be exported to CSV
• #96: Or be imported by clicking on the “Import Lookup” button…
• #97: And selecting the CSV Lookup you want to import and click on the “Import” button.
• #98: The Lookup is imported and can be directly edited.
• #99: View and edit the Lookup where needed.
• #100: The lookup can be used in mappings using the lookupValue function.
• #101: The last feature of ICS are packages. With packages you can group integration together. Packages can also be exported and imported.
• #102: This is our package. To view all integrations part of this package click on the “Action” icon and select “View Integrations”.
• #103: It is possible the access the integration information and Enpoint URL.
• #104: This concludes the deep-dive. I’ll be answering questions these last few minutes.