Skip navigation

Introduction

Amazon Web Services (AWS) is a secure cloud services platform, offering compute power, database storage, content delivery and other functionality to help businesses scale and grow. Advantco delivers the AWS adapter for OIC to speed up integration developments with the following AWS services:

  • Amazon Simple Storage Service (Amazon S3)
  • Amazon Simple Queue Service (SQS)
  • Amazon Simple Notification Service (SNS)
  • Amazon Simple Workflow Service (SWF)

 

Amazon Simple Storage Service (Amazon S3)

Amazon Simple Storage Service (Amazon S3) is an object storage service that offers industry-leading scalability, data availability, security, and performance. The Advantco AWS adapter supports download and upload of files from/to S3 buckets.

s3.PNG

 

Define a Connection with S3 as Service Type

pic1.PNG

 

Provide the credentials.

pic2.PNG

Use the defined Connection in the Integration Flow. Specify the S3 relevant information.

pic3.PNG

 

Amazon Simple Queue Service (SQS)

Amazon Simple Queue Service (SQS) is a fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications. SQS eliminates the complexity and overhead associated with managing and operating message oriented middleware, and empowers developers to focus on differentiating work. Using SQS, you can send, store, and receive messages between software components at any volume, without losing messages or requiring other services to be available.

SQS offers two types of message queues. Standard queues offer maximum throughput, best-effort ordering, and at-least-once delivery. SQS FIFO queues are designed to guarantee that messages are processed exactly once, in the exact order that they are sent.

The Advantco AWS adapter enables one to write or to read messages to/from an SQS queue.

 

sqs.PNG

 

sqs1.PNG

 

Amazon Simple Notification Service (SNS)

Amazon Simple Notification Service (SNS) is a highly available, durable, secure, fully managed pub/sub messaging service that enables you to decouple microservices, distributed systems, and serverless applications. Amazon SNS provides topics for high-throughput, push-based, many-to-many messaging. Using Amazon SNS topics, your publisher systems can fan out messages to a large number of subscriber endpoints for parallel processing, including Amazon SQS queues, AWS Lambda functions, and HTTP/S webhooks. Additionally, SNS can be used to fan out notifications to end users using mobile push, SMS, and email.

 

The Advantco AWS adapter supports publishing messages to an SNS topic.

sns.PNG

 

sns1.PNG

 

Amazon Simple Workflow Service (SWF)

Amazon SWF helps developers build, run, and scale background jobs that have parallel or sequential steps. You can think of Amazon SWF as a fully-managed state tracker and task coordinator in the Cloud.

 

The Advantco AWS adapter supports triggering an SWF workflow from OIC.

swf.PNG

swf1.PNG

 

Summary

The Advantco AWS adapter for OIC makes integration with AWS services like S3, SQS, SNS and SWF simple and fast.

 

Sources:

https://aws.amazon.com/

https://www.advantco.com/

Advanced Message Queuing Protocol(AMQP) is an open internet protocol for business messaging. AMQP is comprised of several layers.

The lowest level defines an efficient, binary, peer-to-peer protocol for transporting messages between two processes over a network. Above this, the messaging layer defines an abstract message format, with concrete standard encoding. Every compliant AMQP process MUST be able to send and receive messages in this standard encoding. (Source:OASIS Advanced Message Queuing Protocol (AMQP) Version 1.0)

The Advantco AMQP Adapter for A-OIC supports publish/subscribe of messages to or from any AMQP compatible brokers. The AMQP Adapter enables A-OIC to be a cross-platform messaging integration platform, supporting on premise brokers like RabbitMQ and cloud brokers like Azure Service Bus.

 

Key features:

  • Support Trigger and Invoke methods

       

 

  • Support AMQP v0.9.1 and AMQP 1.0

       

  • Supports RabbitMQ integration

       

 

  • Support Azure Service Bus integration

      

 

  • Support Advanced Message headers and properties.

      

 

Resources:

Introduction

This blog explains how to deploy the Advantco Dynamics 365 adapter and a detailed step by step to create a REST endpoint to create Account in Dynamics 365.

 

1 Download and Install Oracle SOA 12c

Please refer the link: https://docs.oracle.com/middleware/1221/core/SOAQS/GUID-3C1D5593-9EF2-47C7-930C-A966DD1EFDD9.htm#SOAQS470

 

2 Configure JDeveloper's default domain

 

3 Configure Advantco MS Dynamics 365 Adapter

3.1 Registering the Advantco MS Dynamics 365 Adapter with JDeveloper (Design Time)

        Copy the AdvantcoDynamicsCRMAdapter (JAR) to this location:

        %ORACLE_HOME%\jdeveloper\dropins

 

3.2 Registering the Adapter with SOA Suite (Run Time)

  1. Copy the AdvantcoDynamicsCRMAdapter (JAR) to this location: %ORACLE_HOME%\soa\soa\modules\oracle.cloud.adapter_12.1.3

 

  1. 2) Add the adapter JAR file to the CLASSPATH by editing the setDomainEnv script file. This file is in the bin subdirectory of the domain directory.

For example:

set POST_CLASSPATH=D:\Oracle\12.2.1.3\soa\soa\modules\oracle.cloud.adapter_12.1.3\AdvantcoDynamicsCRMAdapter.jar;%POST_CLASSPATH%

  1. 3) Restart the Weblogic SOA Server

           

 

4 Create Integration Flow

4.1 Create SOA Application

 

4.2 Create SOA Project

 

4.3 Configure Outbound Advantco MS Dynamics 365 Adapter

 

REST Service URL: https://yourcompany.api.crm.dynamics.com/api/data/v8.2/

 

4.4 Configure Inbound REST Adapter

Add resource

Add method

Configure schema for request

Click Next and choose “XML Sample”

<Account>

    <Name>SOA Account</Name>

</Account>

Configure schema for response

Click Next and choose “XML Sample”.

<Response>

    <OperationName>Create</OperationName>

    <Id>AccountId</Id>

</Response>

4.5 Configure BPEL Process

Insert BPEL Process

Press OK button

Then Click the icon as below:

The interface of the BPEL process does not fit to our REST service and needs to be removed. Click the symbol of the inbound interface so that the surrounding circles is represented by a dotted line. Press the 'DELETE' key on your keyboard and answer both questions with 'YES'.

Now the RestService can be wired to the BPEL process.

Double click to Open the BPEL Process.

The input and output variables for the old interface are still there. They need to be removed by clicking on the variables button (x), mark both and click on delete.

Switch to source view. The old WSDL is still imported, so the line reading <import ui:processWSDL... needs to be deleted.

Duoble click on:

The receiveInput can now be wired to the RestService, Change the Port Type to the new RestService_ptt.

 

A new input variable is needed. Click on 'Auto-Create Variable’ and in the 'Create Variable' dialog just click 'OK'.

Wire the replyOutput also to the RestService and repeat the steps above.

Now, Wire the BPEL process to createAccount.

Put an Invoke activity right behind receiveInput and wire it to createAccount.

 

Create a new input and output variable via the green plus and close the dialog.

4.6 Mapping

Put a XSLT Transform right behind the receiveInput.

Add source schema

Add target schema

Do the mapping:

Set the RequestName value is “Create” and the LogicalName value is “account”.

Put a XSLT Transform right behind the receiveInput.

Add source and Target schema

Do the Mapping

 

4.7 Deploy and Testing

Start the SOA Suite instance (if the SOA instance is not started)

Deploy SOA project to a SOA Suite instance.

Open the Oracle Enterprise Manager and go to the soa-infra. http://host_name:port/em

Select the project, click the test button and choose the RestService.

Enter payload request and test the service.

<Account>

    <Name>Oracle_SOA_Account</Name>

</Account>

The response result:

Check result on the MS Dynamics365

pic1.png

Monitor message on the Oracle SOA Suite

Summary

The Advantco Dynamics 365 enables integration between any Oracle applications and MS Dynamics 365. The adapter is also available for Oracle Integration Cloud.

 

Source:

https://www.advantco.com/product/adapter/microsoft-dynamics-crm-adapter-oracle-cloud-integration

advantco.jpg

1. Set up an oracleICS Connection Agent on On-premise

Please refer:

 

2. Configure at OracleICS on Cloud

2.1. Create IDOC Connection

Please refer: https://docs.oracle.com/en/cloud/paas/integration-cloud-service/icssa/creating-connection.html#GUID-7A6854EE-4ED9-4978-8DB7-EF0A7C2C5CDD

 

The configuration of SAP Trigger Adapter as below image

pic1.png

 

JCO Connection Properties file:

#Common properties for Load Balanced/Direct Connection Type: These parameters will be used in both connection types.

    #Description:

        #jco.client.client  = Client represent a self-contained unit in an SAP system with separate master records and its own set of tables. Eg: 811

        #jco.client.lang    = The language determines the code page used for communicating between SAP Adapter and the application server. Eg: EN

 

  1. jco.client.client                       = 800
  2. jco.client.lang                         = en

 

##########################################################

#SAP Direct connection properties: These patameters should be defined if user intends to access ERP Application directly without gateway.

    #Description:

        #jco.client.ashost   = ERP Application Server Host(IP). Eg: 10.30.XX.XX

        #jco.client.sysnr    = System number. Eg: 01

 

  1. jco.client.ashost                       = ecc601
  2. jco.client.sysnr                        = 00

 

###########################################################

#SAP Outbound (Adapter inbound) connection properties: Parameters required to recieve data from SAP. Particularly used for SAP Outbound scenario where SAP will send data to adapter.

    #Description:

        #jco.server.gwhost       = Gateway host (IP). Eg: 10.30.XX.XX

        #jco.server.gwserv       = Gateway service name. Eg: sapgw00

        #jco.server.progid       = Identifier Used to get Register with SAP to receive data. Eg: SAPPROGRAMID

 

  1. jco.server.gwhost                   = ecc601
  2. jco.server.gwserv                   = sapgw00
  3. jco.server.progid                   = ORACLESAP
  4. jco.server.connection_count         = 2

 

2.2. Configure Integration Flow

pic2.png

 

2.2.1. Configure Trigger Endpoint (SAP Adapter)

pic3.png

2.2.2. Configure Invoke Endpoint (Microsoft Dynamics CRM Adapter)

pic4.png

 

2.2.3. Create Mapping

The mapping rule as table below:

 

DEBMAS06

Account

E1KNA1M/NAME1/Name1

Name

E1KNA1M/NAME1/ORT01

Address1_City

E1KNA1M/NAME1/STRAS

Address1_line1

E1KNA1M/NAME1/TELFX

Fax

E1KNA1M/NAME1/TELF1

Telephone1

         mapping.PNG

3. Configure at ECC System

Please refer: https://docs.oracle.com/en/cloud/paas/integration-cloud-service/icssa/sap-inbound-communication.html

3.1.1. Configure RFC Destination

Use Tcode SM59 to create an RFC Destination type T

pic6.png

3.1.2. Create tRFC port

Use we21 Tcode to create tRFC port as below image

pic7.png

3.1.3. Create Logical System

Use BD54 Tcode to create Logical System for OracleICS

pic8.png

3.1.4. Create partner profile

Use WE20 Tcode to create partner porfile with partner type is LS

pic9.png

Add DEBMAS IDOC outbound

pic10.png

4. Send IDOC to OracleICS

Use BD12 tcode to send an IDOC DEBMAS06 to OracleICS

pic11.png

 

Monitor Integration flow in Oracle Cloud

mon1.PNG

mon2.PNG

 

Test account successfully created in Microsoft Dynamics 365

crm.PNG

 

advantco.png

Overview

Microsoft Dynamics CRM is a customer relationship management (CRM) business solution that enables companies to market smarter, sell effectively and productively, and care everywhere. Microsoft Dynamics CRM is available as a cloud offering or an on-premises installation.

The Advantco Dynamics CRM adapter for Oracle Integration Cloud Service is a new adapter with the specific purpose to make integration with Microsoft Dynamics CRM as easy as possible. Below are some of the main features that are covered by this adapter.

  • Authentication: The adapter takes care of authentication and will manage the security token.
  • Schema generation for different entity operations.
  • Schema generation for Queries.
  • Handling multiple calls using query lookup

Authentication

The adapter will handle all the steps of the authentication process and manages the security token. If token is expired, the adapter will automatically request for a new token.

pict1.png

Connection configuration of Advantco Dynamics CRM Adapter

Schema generations

The Advantco Dynamics CRM adapter provides a useful developer-friendly feature to generation operation specific schemas. It also supports schemas for bulk operation which provide a way to bundle a number of operations that either succeed or fail as a group.

pict2.png

Adapter Configuration for Advantco Dynamics CRM to Create an Account

 

Queries result schemas

To handle the queries results, the Advantco Dynamics CRM adapter provides the feature to generate a schema based on a Query example.

pict3.png

Adapter Configuration for Advantco Dynamics CRM to Query Order

 

Handling multiple calls using query lookup

A common requirement in Dynamics CRM integration is handling relationships between entities. This requires data to be queried from the Dynamics CRM system before constructing the request message. The adapter introduces a query feature that is available during schema generation. This adds a Query section in the generated schema as shown below. This allows the query (based on FetchXML) to be constructed during design time, and executed by the adapter automatically during runtime.

 

pict4.png

Mapping an IDoc message to Dynamics CRM using Query lookup

Conclusions

  The Advantco Dynamics CRM adapter greatly reduces complexities and efforts to integrate your with Microsoft Dynamics CRM. The adapter supports both versions online and on-premises Oracle Integration Cloud Service.

 

advantco.png