Tutorial

  1. Home
  2. Docs
  3. Tutorial
  4. 22. What is message type?
  5. 22.6 How to create message type from different file format as xsd, json schema, wsdl 1.1 & 2.0, swagger 2.0 and openAPI 3.x?

22.6 How to create message type from different file format as xsd, json schema, wsdl 1.1 & 2.0, swagger 2.0 and openAPI 3.x?

Learning Objectives

After completing this unit, you’ll be able to:

  • Describe what MsgType is .
  • Comfortably create message type from different file format as xsd, json schema, wsdl 1.1 & 2.0, swagger 2.0 and openAPI 3.x

Introduction

Skyvva support different file formats(xsd, json schema, wsdl 1.1 & 2.0, swagger 2.0 and openAPI 3.x) to create message type.  Upload button  automatically create a hierarchical structure like msgtype Istructure  from hierarchical file.

What is message type?

Message Type: Skyvva provide message type feature to create Istructure repository using differnt file format.  We  introducing the new concept of using message type as interface data type. So basically there are two way to put field mapping in interface is:

1. Use sobject: we use the sobject fields as source field in interface

2. Message type: we use custome fields created in message type as source field.

Import  file feature is used to create message type and ISTructure. SKYvva support differnt format to create msesssage type:

xsd, json schema, wsdl 1.1 & 2.0, swagger 2.0 and openAPI 3.x

  • MetaData Name is unique.
  • IStructure Repo name is also unique in the SAME level
  • MessageType Name is also unique in the SAME level
  • The combination of IStructure Name and type must be unique.
  • Previously, when we import the file we didn‘t apply this rules so we create duplicate but now we apply these rules. The result is we have less duplicate record which use less storage.

Pre-requisite

1. Metadata:

What is Metadata Provider?

   In general, Metadata is information that describes media files. This information can include details such as the artist name, album title, or year of creation (for a track), as well as playback details such as track runtime or picture dimensions. Metdata providers  are  plugins that do the actual metadata extraction from  files. Metadata Provider tell the data processing layer of libmd which metadata fields (types) they can extract. When requested, Metadata read as many of the metadata fields listed by the client as possible from the specified media item.

In Skyvva, when we create metadata, Name filed is only mandory field. On MetaData the Name cannot be duplicate.

How to create Metadata Provider?

Step 1: We have to click on metadata provider tab and click on New button.

Step 2: Create metadata provider.

2. Istructure Repository:

What is Istructure Repository?

The term Repository is  in fact to store data and structure of a message. The purpose of Istructure is An Interface for a structure that contains the metadata of a structure.

Istructure repository fileds:

FieldsDescription
Repository IDExternal Id which is coming from SAP
TypeType to dishtingwish between differnt type to be able to built hierarchy structure.
Update Interfaces StructruesUpdate related Interfaces when Istructure is updated
ParentSet this field to Indicate which repository Is the parent of the record.This record Itself Is a repository.
LevelHierarchy level to organize the repository.We can built hierarchical structure of repository.
hasChildSet this flag If the repository Is a folder which contain other repository in a hierarchical structure.
External IdThis field is for storing the external id of the object  to be use for update the record.
PathThis filed store the path of the record from the root record until the current record name.

How to create ISTructure repository?

Step 1: Create Istructure Repository in created metadata. We have click on related tab then click on new button to create Istrutcure repository.

New button should navigate to:

We have to open our created Istructure repository.

It should navigate to:

 

Step 3:  We have to click on upload file button. Pop up window should open.

Select file format which you want to upload.

How to create message type for different file format?

3. Message Type:

XSD:

This feature help to create a prototype where we can import a XSD and show in a tree view. This xsd is need as the interface type later when we define an interface.

Step 1: Go to you created msg type -> click on upload button -> Choose file type as xsd -> and upload the xsd file

Step2: Save the uploaded  file to create message type.

Step3: We can use this message type with inbound and outbound interface. We should create integration before going to interface.

Step 4:Create Interface

4.1 Inbound Interface

When the message type use as type of an inbound interface it should be at the left side of the mapping e.g. the source data structure. In this case the right side e.g. the target side is the Salesforce sObjects. We map the external data structure into the sObjects of Salesforce. Then we post the data into the sObjects e.g. into the Salesforce application.

Go to integration -> create new inbound interface. where we need to select our metadata, Istructure Repository and Message Type

Scroll down the page to mapping section:

4.2 Outbound Interface

When use with outbound interface message type is at the right side e.g. the target data structure. In this case the left side e.g. the source side is the Salesforce sObjects. We map from salesforce sObject to the external data structure which is represent by the xsd.

Go to integration -> create new outbound interface. where we need to select our metadata, Istructure Repository and Message Type

Go to mapping section of your outbound interface.

 

JSON Schema:

This feature help to create a prototype where we can import a json schema and show in a tree view. This json schema is need as the interface type later when we define an interface.

Step 1: Go to you created msg type -> click on upload button -> Choose file type as JSON Schema-> and upload the Schema file

Step2: Save the uploaded json schema file.

Step3: We can use this message type with inbound and outbound interface. We should create integration before going to interface.

Step4: Create Interface

4.1 Inbound Interface

Go to integration -> create new outbound interface. where we need to select our metadata, Istructure Repository and Message Type

Go to mapping section of your outbound interface.

 

4.2 Outbound Interface

When use with outbound interface message type is at the right side e.g. the target data structure. In this case the left side e.g. the source side is the Salesforce sObjects. We map from salesforce sObject to the external data structure which is represent by the xsd.

Go to integration -> create new outbound interface. where we need to select our metadata, Istructure Repository and Message Type

Go to mapping section of your outbound interface.

Was this article helpful to you? Yes No

How can we help?