From ICIHelp8.1
| Line 2: | Line 2: | ||
= Generic Integration Framework to Support ASB Interface = | = 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 | + | 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 == | == Configuring ASB adapter to load Masterdata == | ||
| − | The | + | 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 === | === Create Masterdata Contract Type === | ||
| − | To enable synchronization between | + | 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. | #'''Click '''''Create Contract Type'' sub menu from the ''Configuration ''tile. The ''Select Contract Type'' page opens. | ||
| Line 31: | Line 31: | ||
=== Client App Cross Reference === | === Client App Cross Reference === | ||
| − | The Client App Cross Reference mapping maps | + | The Client App Cross Reference mapping maps ICI entities (for example, ICI attributes) to client app entities. |
| − | #Navigate to the ''Create Masterdata'' page in | + | #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> | <div class="image-green-border">[[File:Generic Integration Framework ASB 04.png|520px|Generic Integration Framework ASB 04.png]]</div> | ||
==== Masterdata Details ==== | ==== Masterdata Details ==== | ||
1. Select the ''Category ''from the drop-down. For example, ''Default''.<br/> 2. Select the Masterdata Contract Type. | 1. Select the ''Category ''from the drop-down. For example, ''Default''.<br/> 2. Select the Masterdata Contract Type. | ||
| − | <div class="note-box">'''Note''': In order to map | + | <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. Click ''Next''. The ''Attributes ''page opens. | 3. Click ''Next''. The ''Attributes ''page opens. | ||
==== Attributes ==== | ==== Attributes ==== | ||
| − | #Enter the relevant attribute values. For example, enter '' | + | #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"> | <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> | <li>'''Click '''''Save'' to save the entity mapping.</li> | ||
| Line 50: | Line 50: | ||
=== Client App Entity Mapping === | === Client App Entity Mapping === | ||
| − | The Client App Entity Mapping maps | + | 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 | + | #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> | <div class="image-green-border">[[File:Generic Integration Framework ASB 06.png|520px|Generic Integration Framework ASB 06.png]]</div> | ||
==== Masterdata Details ==== | ==== Masterdata Details ==== | ||
| Line 58: | Line 58: | ||
#Select the ''Category ''from the drop-down. For example, ''Default''. | #Select the ''Category ''from the drop-down. For example, ''Default''. | ||
#Select the Masterdata Contract Type. | #Select the Masterdata Contract Type. | ||
| − | <div class="note-box">'''Note''': In order to map | + | <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> | <li>Click ''Next''. The ''Attributes'' page opens.</li> | ||
</ol> | </ol> | ||
| Line 64: | Line 64: | ||
==== Attributes ==== | ==== Attributes ==== | ||
| − | #'''Enter''' the relevant attribute values. For example, enter '' | + | #'''Enter''' the relevant attribute values. For example, enter ''ICI Entity Name'' as ''ICISupplierMaster'' and ''Client Entity Name'' as ''SupplierMaster''. |
To create mapping using ASB, select ''Messaging'' in the ''Integration Mode'' drop-down. The ''Client Name'' selected must be ''GenericIntegration''. | 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 | + | 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"> | <ol start="2"> | ||
<li>'''Click '''''Save'' to save the entity mapping.</li> | <li>'''Click '''''Save'' to save the entity mapping.</li> | ||
</ol> | </ol> | ||
<div class="image-green-border">[[File:Generic Integration Framework ASB 07.png|720px|Generic Integration Framework ASB 07.png]]</div> | <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 == | == Using ASB Adapter to load/publish Masterdata == | ||
=== Download Payload === | === Download Payload === | ||
| − | #Navigate to the Masterdata page in | + | #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. | #'''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"> | <div class="image-green-border">[[File:Generic Integration Framework ASB 08.png|720px|Generic Integration Framework ASB 08.png]]</div> <ol start="3"> | ||
| Line 101: | Line 100: | ||
<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"> </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> | <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"> </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 == | == Using ASB Adapter to load/publish Transaction Data == | ||
| − | |||
=== Updating Transaction Data === | === Updating Transaction Data === | ||
| − | To update transaction data from | + | To update transaction data from ICI using generic integration framework: |
| − | #'''Edit''' the agreement in | + | #'''Edit''' the agreement in ICI with the desired values. |
#'''Click''' ''Update''. | #'''Click''' ''Update''. | ||
| − | '''Note''': For transaction data outbound, it is mandatory to select ''Data Flow Type'' as '' | + | '''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. |
| | ||
| Line 126: | Line 124: | ||
The updated values are displayed in the ''Message Text''. | The updated values are displayed in the ''Message Text''. | ||
<ol start="6"> | <ol start="6"> | ||
| − | <li>Check the ''Notifications Dashboard'' in | + | <li>Check the ''Notifications Dashboard'' in ICI to view the success, failure and update notifications for outbound transaction data.</li> |
</ol> | </ol> | ||
Revision as of 12:41, 12 September 2020
Contents
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
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.
- Select Masterdata.
- Click the Next button. The Create Contract Type Wizard page opens.
- The Create Contract Type page has the following sections:
- 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 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:
Masterdata Details
1. Select the Category from the drop-down. For example, Default.
2. Select the Masterdata Contract Type.
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.
3. 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.
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.
- Click Save to save the entity mapping.
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 theCreate Masterdata page in ICI. This page contains the following tabs:
Masterdata Details
- Select the Category from the drop-down. For example, Default.
- Select the Masterdata Contract Type.
Note: In order to map ICI attributes with attributes uploaded through ASB, Client App Entity Mapping must be selected from the drop-down.
- 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.
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.
- Click Save to save the entity mapping.
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.
- Click the Download Payload button to download a template for the Masterdata.
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.
- Open the downloaded JSON file. This file will be used by third-party systems to push data to the ASB adapter.
For Scheduled updation:
For EventBased updation:
Publish Payload
- Click Publish Payload. The file will be published.
Note: For any subsequent Masterdata changes, the user needs to click Publish Payload button again to update the empty payload.
A notification is displayed once the Payload is published successfully.
Note: The user can create a subscription to the job status updates by using the standard in Notification Setting in the User Administration menu.
Using ASB Adapter to load/publish Transaction Data
Updating Transaction Data
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.
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.
The updated values are displayed in the Message Text.
- Check the Notifications Dashboard in ICI to view the success, failure and update notifications for outbound transaction data.
The same steps can be followed to create:
- Contract Requests with Associations - Inbound
- Associations for Agreements - Inbound
- Amendments with Associations - Outbound
