Generic Integration Framework to Support ASB Interface[edit]


= Generic Integration Framework to Support ASB Interface =

Azure Service Bus (ASB) is a fully managed enterprise integration message broker. Data is transferred between different applications and services using messages. The ICI-ASB adapter considers the approach based on REST and OData principles that exposes a uniform, stateless interface which communicates using HTTP(S) and JSON payloads.

== Configuring ASB adapter to load Masterdata&nbsp; ==

The ICI support for generic integration provides the ability to synchronize ICI Masterdata tables using the input from ASB. Through a technical configuration, you can specify the attributes to be used for this generic integration.

=== Create Masterdata Contract Type ===

To enable synchronization between ICI and ASB, a Masterdata Contract Type should first be configured in ICI, with specific attributes for the integration. To create a Masterdata Contract Type:

#'''Click '''''Create Contract Type'' sub menu from the ''Configuration ''tile. The ''Select Contract Type'' page opens. 
<div class="image-green-border">[[File:Generic Integration Framework ASB 01.png|620px|Generic Integration Framework ASB 01.png]]</div> <ol start="2">
<li>'''Select''' ''Masterdata''.</li>
</ol>
<div class="image-green-border">[[File:Generic Integration Framework ASB 02.png|420px|Generic Integration Framework ASB 02.png]]</div> <ol start="3">
<li>'''Click '''the ''Next ''button. The ''Create Contract Type Wizard'' page opens.</li>
</ol>
<div class="image-green-border">[[File:Generic Integration Framework SFTP 03.png|520px|Generic Integration Framework SFTP 03.png]]</div> <ol start="3">
<li>The ''Create Contract Type ''page has the following sections:</li>
</ol>

*Details: Enter the ''Contract Type Name'' 
*Attributes: Select the Attributes for the Masterdata Contract Type 
*Display Preference: Select Attributes to be displayed in the Agreement Tile View 
*Team: Select the Team 
*Verify: Verify the details in preview mode and '''click&nbsp;'''''Create.'' 

=== Client App Cross Reference ===

The Client App Cross Reference mapping maps ICI entities (for example, ICI attributes) to client app entities.

#Navigate to the ''Create Masterdata'' page in ICI. This page contains the following tabs: 
<div class="image-green-border">[[File:Generic Integration Framework ASB 04.png|520px|Generic Integration Framework ASB 04.png]]</div> 
==== Masterdata Details ====

1.&nbsp;&nbsp; &nbsp;Select the ''Category ''from the drop-down. For example, ''Default''.<br/> 2.&nbsp;&nbsp; &nbsp;Select the Masterdata Contract Type.
<div class="note-box">'''Note''': In order to map ICI entities with entities in the file uploaded through ASB, you must select ''Client App Cross Reference'' from the drop-down.</div> 
3.&nbsp;&nbsp; &nbsp;Click ''Next''. The ''Attributes ''page opens.

==== Attributes ====

#Enter the relevant attribute values. For example, enter ''ICI Entity Name'' as ''ICISupplierMaster'' and ''Client Entity Name'' as ''SupplierMaster''. The ''Payload Type'' can be selected as ''JSON''. 
<div class="note-box">'''Note''': The ''Client Name'' ''GenericIntegration'' must be selected. To create mapping using ASB, select ''Messaging'' in the ''Integration Mode'' drop-down. You need to select a ''Task Category for Messaging'', either ''Scheduled'' or ''EventBased'' as required.</div> <ol start="2">
<li>'''Click '''''Save'' to save the entity mapping.</li>
</ol>
<div class="image-green-border">[[File:Generic Integration Framework ASB 05.png|520px|Generic Integration Framework ASB 05.png]]</div> 
=== Client App Entity Mapping ===

The Client App Entity Mapping maps ICI attributes (for example, attribute names used in Supplier Master) to attributes in the file uploaded through ASB.

#Navigate to the''Create Masterdata'' page in ICI. This page contains the following tabs: 
<div class="image-green-border">[[File:Generic Integration Framework ASB 06.png|520px|Generic Integration Framework ASB 06.png]]</div> 
==== Masterdata Details ====

#Select the ''Category ''from the drop-down. For example, ''Default''. 
#Select the Masterdata Contract Type. 
<div class="note-box">'''Note''': In order to map ICI attributes with attributes uploaded through ASB, ''Client App Entity Mapping'' must be selected from the drop-down.</div> <ol start="3">
<li>Click ''Next''. The ''Attributes'' page opens.</li>
</ol>

==== Attributes ====

#'''Enter''' the relevant attribute values. For example, enter ''ICI&nbsp;Entity Name'' as ''ICISupplierMaster'' and ''Client Entity Name'' as ''SupplierMaster''.&nbsp; 

To create mapping using ASB, select ''Messaging'' in the ''Integration Mode'' drop-down. The ''Client Name'' selected must be ''GenericIntegration''.

In case of lookup and non-lookup attributes: The ICI Relationship Key should be set for lookup attributes and kept blank for non-lookup attributes. The Relationship Key framing should be <''Master Contract Type Name''> Double Underscore<''ICI Attribute Name''>. For example, in case of Supplier Master the ICI attribute name will be ''ICISupplierCountry'' and the Masterdata Contract Type for this attribute will be ''ICICountryMaster''. Hence, relationship key will be ''ICICountryMaster__ICISupplierCountry.''
<ol start="2">
<li>'''Click '''''Save'' to save the entity mapping.</li>
</ol>
<div class="image-green-border">[[File:Generic Integration Framework ASB 07.png|720px|Generic Integration Framework ASB 07.png]]</div> 
== Using ASB Adapter to load/publish Masterdata ==

=== Download Payload ===

#Navigate to the Masterdata page in ICI. 
#'''Click''' the ''View Record'' icon next to the ''Client App Cross Reference'' entity you have created. The ''Masterdata Details'' page opens. 
<div class="image-green-border">[[File:Generic Integration Framework ASB 08.png|720px|Generic Integration Framework ASB 08.png]]</div> <ol start="3">
<li>Click the ''Download Payload'' button to download a template for the Masterdata.</li>
</ol>

'''Note''': The file format of the template will be according to the ''Payload Type'' selected in the attributes of the ''Client App Cross Reference'' entity.
<div class="image-green-border">[[File:Generic Integration Framework ASB 09.png|720px|Generic Integration Framework ASB 09.png]]</div> <ol start="4">
<li>Open the downloaded JSON file. This file will be used by third-party systems to push data to the ASB adapter.</li>
</ol>

For Scheduled updation:
<div class="image-green-border">[[File:Generic Integration Framework ASB 10.png|520px|Generic Integration Framework ASB 10.png]]</div> 
<br/> For EventBased updation:
<div class="image-green-border">[[File:Generic Integration Framework ASB 11.png|520px|Generic Integration Framework ASB 11.png]]</div> 
=== Publish Payload ===
<ol start="5">
<li>'''Click''' ''Publish Payload.'' The file will be published.</li>
</ol>
<div class="note-box">'''Note''': For any subsequent ''Masterdata'' changes, the user needs to click ''Publish Payload'' button again to update the empty payload.</div> 
A notification is displayed once the Payload is published successfully.
<div class="image-green-border">[[File:Generic Integration Framework ASB 12.png|720px|Generic Integration Framework ASB 12.png]]</div> <div class="image-green-border">&nbsp;</div> <div class="note-box">'''Note''': The user can create a subscription to the job status updates by using the standard in ''Notification Setting'' in the ''User Administration'' menu.</div> 
== Using ASB Adapter to load/publish Transaction Data&nbsp; ==

=== Updating Transaction Data&nbsp; ===

To update transaction data from ICI using generic integration framework:

#'''Edit''' the agreement in ICI with the desired values. 
#'''Click''' ''Update''. 

'''Note''': For transaction data outbound, it is mandatory to select ''Data Flow Type'' as ''ICI to Client'' in the Client App Entity Mapping. The workflow action selected in ''Publish Transaction Data'' in Client App Cross Reference Mapping is the event at which transaction data will be updated. For example, if the values selected in this field are ''Approved ''and ''Updated'', then the transaction data will be updated when these actions are taken on the agreement.

&nbsp;

==== Checking Data in Service Bus Explorer ====

To validate the data in the Service Bus Explorer:

#'''Open''' Service Bus Explorer and go to the ''Service Bus Namespace''. 
#Go to the genericintegrationoutbound topic. Right-click and '''select '''''Refresh Subscription'' from the drop-down. 
#'''Click '''''Messages''. The ''Retrieve messages from subscription'' window opens. 
#'''Select '''''Peek ''radio button in the ''Receive Mode'' section. 
#'''Click '''''Ok''. 
<div class="image-green-border">[[File:7.12 ASB adapter.png|720px|7.12 ASB adapter.png]]</div> 
The updated values are displayed in the ''Message Text''.
<ol start="6">
<li>Check the ''Notifications Dashboard'' in ICI to view the success, failure and update notifications for outbound transaction data.</li>
</ol>

The same steps can be followed to create: &nbsp;

*Contract Requests with Associations - Inbound 
*Associations for Agreements - Inbound 
*Amendments with Associations - Outbound 

&nbsp;