The repository consists of Istructure. It stored in  Metadata as child which  describes different types of objects, such as mappings and transformations, that you can create or modify using the PowerCenter Client tools. The Data Integration uses repository objects to extract, transform, and load data.
The repository is used for storing metadata e.g. type and structure definition. The type and structure definition is called the message type. The message type can reside in a WSDL, in SAP IDoc, SAP Bapi, etc… It can be stored in a file in CSV, XML, XSD, or other formats. What we want to do is to import the message type and use these as the type of our interfaces. There are two pages in Repository such as Repository Detail Page and Repository Related Page.

  #

Repository Fields
The following table is the description of  Repository:

Repository button #

The following buttons are for export and import the Repository:

These buttons below use for generating Message Type:

Here we can see repository and message type in a tree view:- #

We have the tree view for our new message monitoring. The same view for the repository and message type needed. The repository and message type can be created with parent/child relation and thus build a tree. However, when the repository has shown as a related list of the Metadata provider you see the only flat structure and thus it is very confusing to read. This is the same as for the message type. The message type is showing as a related list in the screen repository.
Steps to configure this feature:
To show the repository and message type in a tree view, you have to create an IStructure Repository. There are some steps to create:

• Open Integration Admin Tab and click on MetaData Provider ( Click on New MetaData Provider to create if you don’t have one)

• Edit Layout on the right of Click MetaData Provider detail page

• Create Section and Complete the Tittle Name

• Click on Visualforce Pages and pull IStructure Repository into this section.

The result after creation

Delete button to delete MsgType Fied Entries on the related list in Message Type #

Delete button is added to the “delete MsgType Field Entries” section on the related list in Message Type. When you click on the button, it is deleting the MsgType Field Entry.

Tree view for repository like message type:- #

This is another function that we provide to view as hierarchical for the repository. Previously, the repository only shows as a flat list, and for a new version, we want to improve this feature. This concept has already applied for message type and we want to create it as similar. The repository can be organized in a tree and has the same structure as a message type. When the repository has a child it will show the parent’s dropdown and when you click on that will show its child.
Please follow below for Istructure Repository tree view functionality

• Navigate to “Istructure Repository“ tab
• Select any record and open the detail page
• Check the “IStructure Repository (Child)” and “Message Types Repositories” related lists

Metadata Provider #

In the big data era, enterprises are collecting and storing more data than ever before. Metadata Provider tells the data processing layer of a library which metadata fields (types) they can extract. In Skyvva,Istructure repository is stored in metadata. Basically metadata provider is use for grouping. This metadata includes important object properties and their relationships with other objects.
Lets take an example of SAP
So right here sap is a metadata Name. If we are talking about the other organisation like  Google, Salesforce and many all,they provides metadata api.

In the picture, we can see the hierarchical repository where different level are organise hierarchically. We can build a hierarchical structure of the repository. And in the table, we can see the example of the type and Hierarchical repository objects. Different API  organise in the single repository. There are some Repository Object like BAPI, IDOC, and Enterprise Service with type Folder.

In the Repository, we have a message type. Message Type uses to represent the hierarchical structure of the Repository. For example, a service using Webservice. Message Type can be used to describe its request and response.
In Skyvva, when we create metadata, the Name field is an only mandatory field. On MetaData the Name cannot be duplicated.
Metadata Provider screen looks like as shown in the picture given below:-

The description of the highlighted fields(shown in the picture) is showed below:-

How to create a metadata Provider? #

There are two different ways of creating the metadata:

1. Manually create
2. Using Import function

1 In the Metadata tab, perform the following steps:

• Click on New  button on the Metadata provider page. A page appears with one mandatory field i,e Metadata Name.
• Click on the Save button with the required Field.

• Enter Metadata name in the MetaData Provider Name field.

2.  By importing the file matadata can be created. We can Import metadata provider from our local machine if we have existing metadata in our local machine of the same repository and message type as we needed.

Metadata Page: #

There are two section on metadata page.

1. Detail
2. Related

Detail Page:-
Repository can be created by clicking on the “New” button from this page. This page contains detail information about metadata. Only name field is mandatory field here.

• MetaData Provider Name
• Owner ID
• Description
• Created By ID
• Created Date
• Last Modified By ID
• Last Modified Date

• The Detail page and related page contains same 5 Buttons at the top, Please check the table below:-

2. Related Page:-

• In the Related page we can see two sections:-

1. Interface:-  Here we can see the list of Interfaces in which we have used this metadata provider.
2. Repository:- In this section, we can click on New and can create a repository.