Informatica is a data integration tool that is used for extracting the data required and transforming it to its server, and loading the same to the data warehouse. Informatica offers integration software and services to different businesses, industries as well as government organizations, including health care, telecommunication, finance and insurance services. In Informatica, there is a beautiful concept called a Mapplet. The greatest benefit of Mapplets is that they are created one time and can be used or shared between the developers. In this blog, let us know more about Mapplets, why we use them, features of Mapplets, components of the Mapplet in detail. So, let's quickly dive into the concept.
A Mapplet is an object that can be reused. It will be created in the Mapplet Designer. It includes a set of transformations and allows us to reuse transformation logic in more than one Mapping. Let us understand Mapplets with an example. Consider you have some fact tables which need a series of dimension keys. We can create a Mapplet with a series of Lookup transformations to find every dimension key. We can use this Mapplet in every fact table Mapping instead of recreating the same search logic in every Mapping. As a reusable transformation, any changes to the Mapplet are inherited from every instance of the Mapplet. A Reusable transformation refers to any rule or transition logic defined on the data that will be transformed from source to destination via Mapping, and it can be provided more than once with various methods and logic. It can be used for other transformations.
Mapplet is applicable to mapped data. The source object and the target object will be defined and stored in the database. A logic to be transformed is defined by offering a Mapplet Input that transmits the data from Mapping to Mapplet. After that, a desired Mapplet output transform transmits the Mapplet data to Mapping. So the Input-Output transformations will evolve into cyclic Mapping, transaction logic and reused data without any impact on the data.
The Mapplets are created to serve two primary purposes:
Whenever we load new data into a table, some space occurs in the source system, and whenever a new transformation is required to be configured on each Mapping. Mapplets are created to prevent this repetition of the creation of the transformation expressions and to end the unwanted space that is formed in the source system.
On each workflow that is running in the system, a batch id will be formed according to the timestamp of the session using a Mapplet.
For using a Mapplet in Mapping, we must configure the Mapplet for input and output. Apart from the transformation logic we are configuring, a Mapplet includes the following components:
It will be available only in the Mapping Designer. The Mapplet ports comprise the input ports of the input transformations and the output ports of the output transformations.
The Mapplet input may come from the source definition or from the Input transformation within the Mapplet. Several pipelines can be created in a Mapplet. Utilize several source definitions as well as the input transformations or source qualifiers. Alternatively, you can use a mixture of input transformations and source definitions.
The Mapplet output consists of transformation for passing the data through the Mapplet into the Mapping. At Least one output transformation is included in the Mapplet that includes at least one connected port in the Mapplet. Every port connected in the output transformation displays as a Mapplet output port in the Mapping. Every output transformation in the Mapplet is displayed as the output group in the Mapping. The output group may transmit data to several pipelines within the Mapping.
The creation of Mapplets involves three steps.
When dealing with the Mapplets, mistakes can be avoided by:
Follow the rule and guidelines while adding transformations to the Mapplet:
Following are the objects that cannot be included in a Mapplet:
While reusable shortcuts and transformations in the Mapplet can be used, for protecting the Mapplet validity, use a copy of the transformation rather. Reusable transformations or shortcuts inherit modifications to their original transformations. This could disable the Mapplet and Mapping, which utilizes the Mapplet.
In this blog, we have learned about Mapplets, why we use Mapplets, Mapplets features, components of a Mapplet and how to create a Mapplet. We hope you found this information helpful!. For more blogs like this, stay tuned to HKR Trainings.
Batch starts on 21st Jan 2022, Fast Track batch
Batch starts on 25th Jan 2022, Weekday batch
Batch starts on 29th Jan 2022, Weekend batch