Page Comparison

Data Mapper is a visual data-mapping tool used for mapping elements in advanced data integration projects. This tool allows you to specify source and target schemas and to map data fields from source schema to target schema.

You can use the Data Mapper tool to map source schema elements to target schema elements. You can map one source schema element to a target schema element directly by drag and drop method. Additionally, this tool also offers certain mapping functions using which you can map source and target schema elements.  Furthermore, the Data Mapper supports multiple source and target schemas. This implies that you can select more than one schema at a time, both at the source and the target end. This facilitates mapping of multiple source and target schema elements.

This feature is available in:

...

Pre- Requisites

• JRE 1.6 needs to be installed on your system to open the Data Mapper applet.
• Pop-up Blocker needs to be disabled in the web browser, to open the Data Mapper applet. By default, the Pop-up Blocker is enabled.

...

On the Adeptia Suite homepage, go to Configure > Services > Data Transform and then click Data Mapping.

This action will show you the Manage Data Mapping screen (see Figure 376).

Image Removed

Figure 376: Manage Data Mapping

...

Click the Create New link. The Create Data Mapping screen is displayed (see Figure 377).

Image Removed

Figure 377: Create Data Mapping

...

Click the Data Mapper button. This displays the Data Mapper screen (refer to Figure 378).

...

Click Advanced Properties if you want to set options for splitting data. You can split the source data into different chunks. You can specify the size of chunks in terms of the number of records. In the output however, only one file is generated at the location specified in the target activity. To know more about splitting data, refer to the Splitting Source Data section.

...

The Data Mapper screen is divided into eight sections. These are outlined as:

• Menu Bar
• Tabs Panel
• Tool Bar
• Source Panel
• Target Panel
• Mapping Functions Panel
• Mapping Graph Area
• Parameters Panel

...

...

...

Table 3: Options of Tool Bar

...

Target Panel
The Target Panel is used to display a target schema. All the elements of the target schema are listed in the Target Panel. When multiple target schemas are loaded, then all elements of each schema are listed under their respective target nodes.

...

...

...

Parameters Panel
The parameters listed in the Parameters Panel are explained in the table below.

...

...

The process of mapping elements comprises of various steps. These are outlined as:

...

Steps to load Source and Target Schemas

...

Image Removed
Figure 379: Load Schema button

Or click the File menu and select the Load Schema option (see Figure 380).

Image Removed
Figure 380: File Menu in Data Mapper

...

Image Removed
Figure 381: Select Schema

...

• At times, the list of schemas is very long. In such a case, you can search for schemas to be loaded, based on the schema name or type. Enter the name of the schema to be searched in the Quick Search text box and as you type letters, the search field will dynamically search for the values defined in all the schema types and update the table accordingly.
• To refine the search, you can select the schema type from the Schema Type column. The table will display you only the schema types that you would select. For example, if you select the Excel schema type button then, you will only see the Excel Schemas and the table will be updated accordingly. By default, you will be able to see all the schema types in alphabetical order.
• To load a schema, search the schema type and select the checkbox(s) corresponding to the schema type. You can select both the source and target schemas for the schema type. In addition, you can select different source and target schema type. This way, you can load multiple schemas at the same time. You can also select all the checkboxes to load all the schemas. There is no limit to the number of schemas that you can load at the same time.
• You can simultaneously load multiple web service schemas along with other schemas.
• If you have not created any a particular schema type the no schema will be displayed on clicking the respective schema type button.

...

Click the Load button after you have selected the schema(s) to open. The schema(s) that you will select, will be loaded into the Data Mapper window.

...

Image Removed
Figure 382: Source and Target Schema Elements

...

...

The Adeptia Suite provides two XSLT processors for transforming data mapping activity.

1. 1. Saxon (New Transformer)
   2. Xalan (Old Transformer)

Saxon transformer is much faster than Xalan. By default, the Data Mapper selects the Saxon transformer to transform all of your new mapping activity.
You can change the parser of any existing Data Mapping activity by following the steps below:

1. Click on the Action menu of the Data Mapping activity of your choice and then select the Edit menu option (see Figure 383).

   Image Removed
   Figure 383: Editing A Data Mapping Activity

2. On the Edit Data Mapping screen, click on the Data Mapper button to edit the mapping activity (see Figure 384).

   Image Removed
   Figure 384: Edit Data Mapping Activity Screen

3. In the Data Mapper, click on the Actions menu and then select the XSL Transformer menu option.
4. In the XSL Transformer dialog box, select the Saxon radio button and click Ok.
5. Click on Save button to save the mapping of the Data Mapper.
6. On the Edit Data Mapping screen, click on the Save button to edit the mapping activity. This action will display you a confirmation message (see Figure 385).

Image Removed
Figure 385: Confirmation Message

If you wish to revert to the old transformer (Xalan Transformer) then, you can achieve
that by the following steps:

1. In the Data Mapper, click on the Actions menu and then select the XSL Transformer menu option.
2. In the XSL Transformer dialog box, select the Xalan radio button and click the OK button.
3. Click on the Save button to save the mapping activity.

...

At times, when the source or target schemas are quite large, then searching an element can be very cumbersome. The Data Mapper applet eases this task by allowing you to search for an element in a source or target schema.

Steps to search an element in a source or target schema hierarchy

1. Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes.

2. Click the Actions menu and select Search Element option (see Figure 386).

   Alternately you can press <Ctrl> + <F> on the keyboard.

   Image Removed

   Figure 386: Select Search Element from Actions menu

   The Element Search Dialog window is displayed (see Figure 387).

   Image Removed

   Figure 387: Element Search Dialog Box

3. Enter the name of the element that you want to search for, in the Search Value field. You can also use Wild Card character(s) to search for an element. The Xpath of the element is automatically displayed in the Element Path field.

4. Select the appropriate option in the Scope Panel, to search the element in the Source or Target schema hierarchy. For example, if you want to search in the Source schema hierarchy, then select Source Tree option. Only one option can be selected at a time. By default, Target Tree is selected (see Figure 388).

   Image Removed

   Figure 388: Enter Parameters in Element Search Dialog Box

   Info
   As per the enhanced functionality of the search element, you can now also search the element on the basis of comments, Data Type, Current Mapping (Rules), Documentation and Extension Node Element in the tree node of the Data Mapper.

5. Click Find. This searches for the first occurrence of the element in the selected hierarchy. If the element match is found, then that element is selected and highlighted. The Xpath of that node is displayed in the Element Path field (see Figure 389).

   Image Removed

   Figure 389: Element Match Found

6. If multiple matches are found for the search criteria, then the Direction Panel and the Find Next button is activated (see Figure 390). You can select the direction in which you want to search in the selected hierarchy. For example, if you want to search upwards in the hierarchy, select Up option. Only one option can be selected at a time. By default, Down is selected.

   Image Removed

   Figure 390: Multiple Matches Found

7. Click Find Next to search for the next element in the hierarchy, based on the selected direction. Once the element match is found, click Close to close the Search Element dialog box. 

   In case no element match is found, then a warning message is displayed (see Figure 391).

   Image Removed

   Figure 391: Adeptia Mapper Warning

8. Click Yes to search again, else click No to close this screen.

...

You can map source and target elements using any of the listed methods:

...

This is the default and most commonly used method for mapping source and target elements.
 

Steps to map elements using Drag and Drop approach

...

Figure 392: Map Source and Target Element using Drag and Drop Approach

...

Similarly, drag and drop each source and target element that you want to map. The mapping between all source and target elements will be displayed (see Figure 393).

Image Removed

Figure 393: Map Source and Target Elements

...

If you have loaded multiple source and target schemas, then drag and drop the source and target elements you want to map. The mapping between these elements will be displayed (see Figure 394).

Image Removed

Figure 394: Map Multiple Source and Target Schema Elements

Save the mapping activity and exit the Data Mapper.

...

• • One To One Mapping ( Image Removed )
  • Auto Mapper ( Image Removed )
  • Remove All Mappings ( Image Removed )

...

Steps to use One to One mapping 

...

Click One to One Mapping ( Image Removed ) button. All the leaf elements of the parent element in the source schema will be mapped to their respective leaf elements of the parent element in the target schema.

...

Steps to use the Auto Mapper

1. Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes. Additionally, the hierarchy and name of the all elements is the same (see Figure 395).

   Image Removed
   Figure 395: Same Hierarchy and Element Names

2. Click Auto Mapper ( Image Removed ) button. The Auto Mapper Options dialog box is displayed (see Figure 396).

   Image Removed
   Figure 396: Auto Mapper Options

3. Select the mapping criteria from the Choose the Criteria dropdown list. Its options are listed as:
    
   • Ignore Case: The source and the target elements are mapped even if they are of different case. Their attributes are not mapped.
   • Case Sensitive: The source and target elements are mapped only if they are of the same case. Their attributes are not mapped.
   • Ignore Case and Include Attributes: The source and target elements and their attributes are mapped even if they are of different case.
   • Case Sensitive and Include Attributes: The source and target elements and their attributes are mapped, only if they are of the same case.
   • Consider Only Leaf Element Count: The source and target elements are mapped only if the number of leaf elements in the source schema and target schema are the same. It is not necessary that names of source and target elements are similar. Their attributes are not mapped.
   • Consider Only Leaf Element Count and Include Attributes: The source and target elements and their attributes are mapped only if the number of leaf elements in the source schema and target schema are the same. It is not necessary that names of source and target elements are similar.
4. Click OK button. All elements of the source and target schema will automatically be mapped based on the selected criteria (see Figure 397).

Image Removed
Figure 397: Mapped Elements using Auto Mapper

...

Steps to remove all mappings between source and target elements 

Click Remove all Mapping ( Image Removed ) button. The Remove Options screen is displayed (see Figure 398).This screen displays a list of the properties, variables, custom methods, keys and templates associated with a mapped element, which can be removed with the mapping.

Image Removed

Figure 398: Remove Options

Select the checkbox(s) of the options that you want to remove and click OK button. All the selected options and all mappings between source and target elements will be removed.

...

• • Global: The Custom Auto Maps defined within Global scope are available within all the mapping activities. Once you create a global Custom Auto Map in a mapping activity, you can use it in all the mapping activities.
  • Group: The Custom Auto Maps defined within Group scope are available only within the specific user group.

...

The high-level steps to use Custom Auto Maps are:

• Defining a Custom Auto Map
• Activating a Custom Auto Map
• Using a Custom Auto Map in Mapping

...

You can define a Custom Auto Map by both manually providing the names of the source and target elements to be mapped in the Custom Auto Map Dialog screen or by defining the names of source and target elements to be mapped in a CSV file and then loading the CSV file in the Custom Auto Map Dialog screen. Loading a CSV file is useful when you have a large set of source and target elements to be mapped.

Defining a Custom Auto Map Using a CSV File

Steps to Manually Define a Custom Auto Map

...

Ensure that the source and target schemas are loaded in the Data Mapper and all their elements are listed under their respective nodes (see Figure 399).

Image Removed

Figure 399: Source and Target Schemas with different Element Names

...

Click the Custom Auto Map Image Removed button on the tool bar or select Custom Auto Map from the Actions menu. The Custom Auto Map Dialog screen is displayed (see Figure 400).

Image Removed

Figure 400: Custom Auto Map Dialog screen

...

Select the scope of the Custom Auto Map. By default, the radio button Global is selected and a Custom Auto Map is saved in the Global scope.

...

Enter the name of the target element to which you want to map the source element specified in previous step, in the Target Element column (see Figure 401).

...

Image Removed
Figure 402: Parameters Panel

Defining a Custom Auto Map Using a CSV File

The Custom Auto Map feature also enables you to load a Comma Separated Values (CSV) file. You can use the set of values from the csv file which are separated by comma as a Map set for your process flow. For example, if you want to map the following source and target elements:

...

• EmpFirstName,firstName
• EmpLastName, lastName
• EmpMiddleInitial, middleNames

Steps to Define a Custom Auto Map Using a CSV File

1. In the Custom Auto Map Dialog screen, enter the name of Custom Auto Map in the Name textbox.

2. Click the CSV Image Removed button to load a csv file if you want to map the values using the values defined in the csv file. The server will consider the comma separated pair of values as the source and target elements to be mapped (see Figure 403).

   Image Removed

   Figure 403: Custom Auto Map Dialog: Load CSV

   An Open window is displayed.

3. Browse and select the respective csv file.
4. Click Open to upload the csv file. This will populate the source and target elements columns with the values defined in the CSV file. .

5. Select the scope of the Custom Auto Map (see Figure 404).

   Image Removed

   Figure 404: Custom Auto Map Dialog

6. Click the Save & Close Image Removed button to save the Custom Auto Map. This will add the Custom Auto Map value map in Custom Auto Map hierarchy in the Parameter Panel (see Figure 424).

Image Removed
Figure 405: Parameters Panel

...

When you define a Custom Auto Map, by default it is in deactivated state. To use a Custom Auto Map, you need to first activate it. Once you have activated the Custom Auto Map, you can use it in your mapping. Note that only activated Custom Auto Maps can be used in a mapping.
 

Steps to Activate a Custom Auto Map

1. In the Properties Panel, select the Custom Auto Map which you want to activate to use in a mapping.

2. Right-click the Custom Auto Map and select the option Activate (see Figure 406).

   Image Removed

   Figure 406: Parameters Panel: Custom Auto Map Activate option

3. The status of the Custom Auto Map changes to Active (see Figure 407).

Image Removed
Figure 407: Parameters Panel: Custom Auto Map Status

...

After activating a Custom Auto Map, you can use it in your mapping. Note that only one Custom Auto Map can be activated in the current mapping. 

Steps to Use the Custom Auto Map in a Mapping 

1. Load the respective source and target schema.
2. Create and activate the Custom Auto Map.
3. Map the parent record of the Source schema to the parent record of the Target schema.

4. Right-click the parent record of the target schema and select Connect Matching Record options (see Figure 408).

   Image Removed

   Figure 408: Select Connect Matching Children

   The Connect Matching Children Dialog window is displayed (see Figure 409).

   Image Removed

   Figure 409: Connect Matching Children Options

    

5. Select the mapping criteria from the Automap options list. Its options are listed as:
    
   • Ignore Case: The source and the target elements are mapped even if they are of different case. Their attributes are not mapped.
   • Ignore Namespace: The source and target elements are mapped, when their names are same but source schema has any namespace prefix.
   • Recursive: Elements of parent level as well as all child level with the corresponding target elements.
   • Mix Attributes: Attributes of source and target schemas are mapped.
6. Select the mapping criteria from the Existing Options list. These options are :
    
   • Retain: If any source and target elements are already mapped, those mapping will not be overwritten.
   • Overwrite: Overwrites all the existing mappings.
7. Click OK. This will map source and target schema as per the criteria selected (see Figure 410).

Image Removed
Figure 410: Source and Target elements are mapped

...

You can also manage the Custom Auto Map from the Parameters Panel. When you right-click the Custom Auto Map in the Parameters Panel, you can perform the following operations on a Custom Auto Map:

• Edit a Custom Auto Map
• Move a Custom Auto Map from Group to Global
• Delete a Custom Auto Map

...

Steps to Edit a Custom Auto Map

1. In the Properties Panel, select the Custom Auto Map to be edited.

2. Right-click the Custom Auto Map and select the option Edit (see Figure 406).

    

   Image Removed

   Figure 411: Parameters Panel: Custom Auto Map Edit option

   The Custom Auto Map is open in Edit mode (see Figure 412).

   Image Removed

   Figure 412: Custom Auto Map Dialog screen in Edit mode

3. Click the Save & Close Image Removed button to save the Custom Auto Map.

...

Steps to Move a Custom Auto Map

1. In the Properties Panel, select the Custom Auto Map which you want to move from group to global.

2. Right-click the Custom Auto Map and select the option Move To Global (see Figure 429).

   Image Removed

   Figure 413: Parameters Panel: Move to Global option

3. A warning message is displayed (see Figure 430).

   Image Removed
   Figure 414: Warning Message

4. Click Yes to confirm moving the Custom Auto Map from Group to Global (see Figure 431).

Image Removed
Figure 415: Change Scope in Parameters Panel

...

Deleting a Custom Auto Map
Steps to Delete a Custom Auto Map

1. In the Properties Panel, select the Custom Auto Map which you want to delete.

2. Right-click the Custom Auto Map and select the option Remove (see Figure 406).

   Image Removed

   Figure 416: Parameters Panel: Custom Auto Map Remove option

3. A warning message is displayed (see Figure 417).

   Image Removed

   Figure 417: Parameters Panel: Custom Auto Map Status

4. Click Yes to confirm the deletion of selected Custom Auto Map. The selected Custom Auto Map will be deleted.

...

• For the source element 'High' the Map value for the target element will be 'H'.
• For the source element 'Low' the Map value for the target element will be 'L'.
• For the source element 'Medium' the Map value for the target element will be 'M'.

...

You can also select the scope of a Value Map at the time of defining and saving it. Scope of Value Map is the context within which it is defined and can be accessible within or across the user groups. A Value Map can be defined in any of the following scope:

• Global: The Value Maps defined within Global scope are available within all the mapping activities. Once you create a global Value Map in a mapping activity, you can use it in all the mapping activities.
• Group: The Value Maps Templates defined within Group scope are available only within the specific user group.

...

• Defining a Value Map
• Using a Value Map in Mapping
• Managing a Value Map from the Parameters Panel

...

You can define a Value Map by either manually providing the mapping values that will be used in the target schema against the values of the elements present in the source schema in the Value Map Dialog screen or by defining the mapping values that will be used in the target schema against the values of the elements present in the source schema in a CSV file and then loading the CSV file. Loading a CSV file is useful when you have a large set of values to be mapped.

Defining a Value Map Manually

Steps to Manually Define a Value Map

...

Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes (see Figure 418).

Image Removed

Figure 418: Elements of Source and Target Schema

...

Click the Value Map Image Removed button on the toolbar or select the option Value Map from the Actions menu. The Value Map Dialog screen is displayed (see Figure 419).

Image Removed

Figure 419: Value Map Options Dialog screen

...

Select the scope of the Value Map. By default, the radio button Global is selected and a Value Map is saved in the Global scope.

...

• • For the source element 'High' the Map value for the target element will be 'H'.
  • For the source element 'Low' the Map value for the target element will be 'L'.
  • For the source element 'Medium' the Map value for the target element will be 'M'.

For the source element which is not provided the target element will be mapped to 'Normal' as defined in the Default Value field.

...

Info
If you need to delete any row, select the respective row and click the Delete Image Removed button.

...

Click the Save & Close Image Removed button to save the Value Map. This will add the Value Map in Value Map hierarchy in the Parameter Panel. Similarly you can add more Value Map.

Image Removed
Figure 421: Parameters Panel

Defining a Value Map Using a CSV File

The Value Map feature also enables you to load a Comma Separated Values (CSV) file. You can use the set of values from the csv file which are separated by comma as a Map set for your process flow. For example, if you want to change the values defined for the priority of mail as:

• For the source element 'High' the Map value for the target element is 'H'.
• For the source element 'Low' the Map value for the target element is 'L'.
• For the source element 'Medium' the Map value for the target element is 'M'.

...

Steps to Define a Value Map Using a CSV File

1. In the Value Map Dialog screen, enter the name of Value Map (for example, PriorityMap_forcsvfile in the Name textbox.

2. Click the CSV Image Removed button to load a csv file if you want to map the values using the values defined in the csv file. The server will consider the comma separated pair of values as the target element and its mapped value (see Figure 422).

   Image Removed

   Figure 422: Value Map Dialog: Load CSV

   An Open window is displayed

3. Browse and select the respective csv file.
4. Click Open to upload the csv file. This will populate the Value and Map columns.
5. Select the scope of the Value Map.

6. Enter the default value in the Default Value field (see Figure 423).

   Image Removed

   Figure 423: Value Map Dialog screen

7. Select the Pick from Source checkbox, if required.
8. Click the Save & Close Image Removed button to save the Value Map. This will add the Value Map value map in Value Map hierarchy in the Parameter Panel. Similarly you can add more Value Maps (see Figure 424).

Image Removed
Figure 424: Parameters Panel

...

Steps to Use the Value Map in a Mapping

1. Now to map it, select a target element, for example Priority. The selected target element is shown in Mapping Graph Area.
2. Double click on a value map you want to use, from the Value Map hierarchy of Parameter Panel. For example, PriorityMap.
3. Now double-click the source element. For example, Priority.

4. Connect the output of the source element to input of value map and then connect the output of value map to the input of the target element (see Figure 425).

   Image Removed

   Figure 425: Use Auto Map in a Mapping

5. Once you have performed the mapping activity, click Apply Mapping ( Image Removed ) button to save the mapping. The mapping will be applied (see Figure 426).

Image Removed
Figure 426: Mapping between the Source and Target Schema

...

You can also manage the Value Map from the Parameters Panel. When you right-click the Value Map in the Parameters Panel, you can perform the following operations on a Value Map:

• Edit the Value Map
• Move a Value Map from Group to Global
• Delete a Value Auto Map

...

Steps to Edit a Value Map

1. In the Properties Panel, select the Value Map to be edited.

2. Right-click the Value Map and select the option Edit (see Figure 406).

   Image Removed

   Figure 427: Parameters Panel: Value Map Edit option

   The Value Map is open in Edit mode (see Figure 412).

   Image Removed

   Figure 428: Value Map Dialog screen in Edit mode

3. Click the Save & Close Image Removed button to save the Value Map.

...

Steps to Move a Value Map

1. In the Properties Panel, select the Value Map which you want to move from group to global.

2. Right-click the Value Map and select the option Move To Global (see Figure 429)

   Image Removed

   Figure 429: Change Scope in Parameters Panel

3. A warning message is displayed (see Figure 430).

   Image Removed

   Figure 430: Warning Message

4. Click Yes to confirm the change of scope from Group to Global (see Figure 431).

Image Removed
Figure 431: Change Scope in Parameters Panel

...

Steps to Delete a Value Map

1. In the Properties Panel, select the Value Map which you want to delete.

2. Right-click the Value Map and select the option Remove (see Figure 406).

    

   Image Removed

    

   Figure 432: Parameters Panel: Value Map Remove option

   A warning message is displayed (see Figure 417).

   Image Removed
   Figure 433: Application Message
   

3. Click Yes to confirm the deletion of selected Value Map. The selected Value Map will be deleted.

...

This is an additional feature of mapping elements. You can copy the mapping associated with a target element and paste it on other target elements.
 

Steps to copy the mapping of a target element

1. Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes. Additionally, a source and target element should be mapped.
2. Right-click the target element whose mapping you want to copy and select the Copy Mapping option. This copies the mapping of the selected target element.

...

Right-click the target element on which you want to paste the mapping and select the Paste Mapping option.

The Paste Mapping Options screen is displayed with a list of Paste options (see Figure 434).

Image Removed

Figure 434: Paste Mapping Options

...

This screen displays a list of options that can be pasted with the mapping. It includes the For Each and Comments properties and local variables.

Select the checkbox(s) of options you want to paste with the mapping, and click OK. The mapping with the selected options is pasted on the target element.

...

Ensure that the [source and target schemas are loaded and all their elements are listed under their respective nodes. (see Figure 435).

...

Click Actions menu and select Import Mapping (see Figure 436).

Image Removed 
Figure 436: Select Import Mapping Option

The Import Mapping Dialog screen is displayed (see Figure 437).

...

Image Removed
Figure 438: Mapping Imported

...

You can use the mapping functions built-in the Data Mapper to map source schema elements to the target schema elements. These mapping functions are listed as:

• Math
• String
• Date
• Aggregation
• Conditional
• Axis
• Boolean
• Context
• DB

...

Click a target element. The target element node is displayed in the Mapping Graph Area (see Figure 439).

Image Removed

Figure 439: Select Target Element

Double-click a source element. The source element is displayed in the Mapping Graph Area (see Figure 440).

Image Removed

Figure 440: Select Source Element

...

...

...

1. Click the File menu and select Save to save the mapping. Alternately, you can click the Save ( Image Removed ) button on the toolbar. The server first validates the mapping activity. If successful, it displays a dialog box confirming that the mapping has been saved successfully. If the Comments property is enabled, then clicking Save will display a screen where you need to enter comments related to the mapping. (see Figure 442).

   Image Removed
   Figure 442: Add Comments (Mapping)

2. Enter comments in the textbox Specify comments for mapping object<object name>.

   Info
   The comment should be at least 1 character in length. If you enable/disable the Comments property in the middle of a mapping activity, you need to restart the mapping applet.

3. Click OK to save the comments. This displays a dialog box confirming that the mapping has been saved successfully.

4. Click File menu and select Exit to close the Data Mapper applet. A confirmation dialog box is displayed (see Figure 443).

   Image Removed

   Figure 443: Exit from Data Mapper

5. Click the Yes button to exit the Data Mapper screen and return to the Manage Data Mapping screen. If the mapping object has not been saved, then the Save Mapping Object dialog box is displayed (see Figure 444).

   Image Removed

   Figure 444: Save Mapping Object

6. Click the Save To Server button to save the mapping object to the Adeptia Suite. A screen is displayed where you need to enter comments related to the mapping. (refer to Figure 442).
7. Enter comments in the Specify comments for mapping object <object name> field.
8. Click OK to save the comments. This displays a confirmation dialog box stating that the mapping has been saved successfully. The control returns to the Manage Data Mapping screen, where a list of mapping activities is displayed.
9. Refresh the Internet browser to view the saved mapping activity.

...

Click the XSL tab on the Tabs Panel to view the generated mapping XSL. The generated XSL code with line numbers is displayed (see Figure 445).

Image Removed

Figure 445: Mapping XSL

...

Click the Action menu and select Validate XSL option to validate the generated XSL. A dialog box is displayed confirming that the XSL is valid.

Click OK to close the above dialog box.

...

1. Click the View menu and select View Mapping XML option. This displays the generated XML code with line numbers, in read-only mode (see Figure 446).

Image Removed
Figure 446: View Mapping XML

...

Once you have mapped source and target schema elements, you can view and validate the output of the mapping activity. This feature enables you to test the data and make modifications to the mapping activity, before saving it.
 

Steps to view and validate mapping output

Click the Debugger tab on the tabs panel to view and validate the output of the mapping activity. The Debugger is displayed on the Data Mapper screen (see Figure 447).

Image Removed

Figure 447: Debugger screen

...

...

Image Removed
Figure 448: Generate Mockup Data

...

Alternately, you can display input data from an existing XML file. Click Load Input XML button ( Image Removed ) displayed in the Input section to select and upload the existing XML file.

...

Click the Save button ( Image Removed ) displayed in the Input section to save the generated input data.

...

Image Removed
Figure 449: Output XSL

...

...

To use Data Viewer, click the Data Viewer tab. The Data Viewer panel is displayed (see Figure 450).

Image Removed

Figure 450: Data Viewer

...

To attach the source file, right click the Root element in the Source Panel and select Attach Source option and select the source file (see Figure 451).

Image Removed

Figure 451: Attach Source

...

After selecting the source file, again right click the Root element in source panel and select Preview. Source Data is displayed in the Grid View panel (see Figure 452).

Image Removed
Figure 452: Source records in Grid View

...

If there is any error record in the source file, a pop-up message is displayed that "Error Records found in the source data." (see Figure 453).

Image Removed

Figure 453: Pop-up message

...

To view the source data in Tree View, click the Tree View tab. The source data is selected in the hierarchy view (see Figure 454).

Image Removed

Figure 454: Tree View

...

To view the values of the record, click [+] to expand the Record. Values of the expanded record are shown (see Figure 455).

Image Removed
Figure 455: Records in Tree View

...

If there is any error encountered in the source data, those error records are shown in the Errors tab. To view the error records, click Errors tab (see Figure 456).

Image Removed

Figure 456: Error Record

...

...

• The number of errors occurred during transformation
• The list of errors occurred during transformation
• List of enumerated literals for the target element if invalid data is mapped to the target element which is restricted to the enumerated values

...

To expand the Source or Target panel, click Image Removed . The Source or Target panel is shown in the expanded (see Figure 458).

Image Removed

Figure 458: Target Panel in expanded mode

...

...

Steps to view mapping activity in PDF format

1. On the Adeptia Suite homepage, go to Configure > Services > Data Transform and then click Data Mapping. The Manage Data Mapping screen is displayed (refer to Figure 376).
2. Click the radio button against the mapping activity whose PDF details you want to view. This selects the mapping activity and activates the PDF View link. Clicking this link displays a PDF file with all information associated with the mapping activity.

3. This file displays divides the mapping information into various pages. The first page contains mapping information such as mapping name, description; creation details and the group owner (see Figure 459).

   Image Removed

   Figure 459: Mapping Information Document

4. The next page displays all source and target schema information (see Figure 460).

   Image Removed

   Figure 460: Schema Information

5. The next page displays all other mapping information such as XSL templates used, variables defined, properties, keys, and sorting rules (see Figure 461).

Image Removed
Figure 461: Detailed Mapping Information

...

If you have read-only rights, you can still view a mapping activity. You can view the applied mapping, create new mapping rules, edit existing mapping rules and run simulation. However, you cannot save the mapping activity.
 

Steps to view mapping in read-only mode

...

On the Adeptia Suite homepage, go to Develop > Services > Data Transform and then click Data Mapping. The Manage Data Mapping screen is displayed (refer to Figure 462).

Image Removed

Figure 462: Manage Data Mapping Screen

...

Click the mapping activity that you want to view in read-only mode. The View Data Mapping screen is displayed (see Figure 463).

Image Removed

Figure 463: View Data Mapping

Click the Data Mapper button. This displays the selected mapping activity in the Data Mapper applet in read-only mode (see Figure 464).

...

...

Splitting feature enables you to process large files. You must use splitting if your source file is huge. If you do not use splitting in this case, then Data Mapper may not be able to map it. If the data in the source file is huge, you can split the source data into different chunks. You can specify the size of the chunks in terms of the number of records or data streams. In the output, however, only one file is generated at the location specified in the target activity.
 

Steps to split the source data

...

Click Advanced Properties on the Create Data Mapping screen to expand the advanced properties of the new Mapping activity (see Figure 465).

Image Removed

Figure 465: Advanced Properties

...

Select the Splitting Data checkbox to enable the splitting of data.

...

Enter the number of chunks you want to process concurrently, in the Maximum Concurrent Processes field. By default, value of 1 is entered.

...

If mapping has been saved in the Data Mapper applet, then the XSL code is displayed in Mapping XSL field. This is a very useful feature. You can enter new XSL code or edit existing code to test or debug the mapping. If you save these changes, then they are reflected in the applet. For example, if you need to change the value of a constant, you can change it from this screen itself, instead of the applet. Additionally, any modifications made in the Mapping XSL code in the Data Mapper applet, will overwrite the XSL code in this field.

...

...

To split data you need to set the Splitter XPath on the source hierarchy. The data is split and sent to the transformer which executes the split data. You can set the Splitter XPath in case of a single source schema only. You can also set multiple Splitter XPaths in a source schema.
The following example explains the use of multiple Xpath splitting:
Image Removed

...

Once splitter XPath is defined, during execution, mapping will split the source hierarchy using each splitter Xpath and each chunk will have records specified by Split Number of Records.
In this scenario, when we set R1 and R2 as split XPath then Split Number of Records property is applied for both R1 and R2. For example if the value of Split Number of Records property is 500 then 500 records of R1 and 500 records of R2 are selected.
Splitting data and setting Splitter XPath is very effective when the source data is very large. You can set the Splitter XPath in case of a single source and target schema. You can also set multiple Splitter XPaths in a source and target schema.

...

Right-click the source schema element that you want to split and select the Set as Splitter XPath option. A screen showing the Splitter XPath details is displayed (see Figure 466).

Image Removed
Figure 466: Splitter XPath Details

Click OK. This splits and sets the Splitter XPath on the selected source element.

...

1. Ensure that all the source and target schemas are loaded and all their elements are listed under their respective nodes.

2. Select Actions menu and select Enable Quick Splitting option. Alternately, you can press <Ctrl> + <Q>. This splits the data and displays the splitter Xpath details (see Figure 467).

   Image Removed
   Figure 467: Splitter Xpath Details(Enable Quick Splitting)

3. Click OK. This splits and sets the Splitter XPath on the selected source element.
   However, quick splitting splits the records in default numbers. To split into a specific number, you need to set the Splitter Xpath explicitly.

...

1. Click View menu and select View Mapping XML. The Mapping XML window is displayed. The Splitter XPath details are displayed with a $Input tag prefixed to Source XPath code (see Figure 468).

   Image Removed

   Figure 468: Splitter XPath in Mapping XML

You can remove a Splitter XPath that has been set for a source element.
 

Steps to remove Splitter XPath

1. Right-click the source schema element whose Splitter XPath you want to remove and select the Remove Splitter XPath option. A screen showing the Splitter XPath details is displayed (see Figure 469).

   Image Removed

   Figure 469: Remove Splitter XPath Details

2. Click OK. This removes the Splitter XPath set on the selected source element.

...

Once you have split the source data by setting the Splitter XPath on a source element, you need to merge the split data at the target end. For this, you need to set the Merger XPath on a target element.
Setting the Merger XPath is largely dependent upon the Splitter XPath. You need to ensure that the number of Splitter XPaths and the Merger XPaths at the source and target schemas respectively are the same.
 

Steps to set Merger XPath

1. Ensure that all the source and target schemas are loaded and all their elements are listed under their respective nodes.
2. Ensure that a Splitter XPath has been set for a source schema element.

3. Right-click the target schema element on which you want to merge the split data and select the Set as Merger XPath option. A screen showing the Merger XPath details is displayed (see Figure 470).

   Image Removed
   Figure 470: Merger XPath Details

   Info
   Merging can be set only on root or record levels. You cannot merge on an element level.

4. Click OK. This merges the split data and sets the Merger XPath on the selected target element.

   Info
   Once a Merger XPath is set for a target element, the letter (S) is displayed next to that target element. This signifies that the split data has been merged on the target element and the Merger XPath has been set. Refer to Table of Suffixes for details on suffixes displayed next to an element.

   Info
   You can view Merger XPath details in the output XML. A $ input tag is prefixed to the line containing the Splitter XPath details.

   Info
   When using Enable Quick Splitting feature, the Merger Xpath is also automatically set when this feature is selected.

5. Once you have set a Merger XPath, you can view it in the Output XML.

...

Click View menu and select View Mapping XML. The Mapping XML window is displayed. The Merger XPath details are displayed with Target XPath code (refer to Figure 468).

You can remove a Merger XPath that has been set for a target element.
 

Steps to remove Merger XPath

1. Right-click the target schema element whose Merger XPath you want to remove and select the Remove Merger XPath option. A screen showing the Merger XPath details is displayed (see Figure 471).

   Image Removed

   Figure 471: Remove Merger XPath Details

2. Click OK. This removes the Merger XPath set on the selected target element.

...

When mapping multiple source and target schema elements, you need to assign streams to the root element of the target schema structures.
 

Steps to assign data streams

...

Right-click the root element of a target schema structure and select the Assign Stream option. The Assign Streams dialog box is displayed (see Figure 472).

Image Removed

Figure 472: Assign Streams

...

...

Enter the name of the data stream(s) that you want to edit, for the target element(s), in the textbox Stream Name.

...

...

You can remove mapping associated with a particular element.
 

Steps to remove mapping of a particular element

1. Ensure that all the source and target schemas are loaded and all their elements are listed under their respective nodes.
2. Right-click the target element whose mapping you want to remove and select the Remove Mappings option.

3. The Remove Options window is displayed (see Figure 473).

   Image Removed
   Figure 473: Remove Options (Particular Element)

   This screen displays a list of properties and variables associated with the selected element that can be removed with the mapping.

   Info
   Only the Remove Mapping is displayed as always enabled. The other options are enabled only if they have been defined for the particular element.

4. Select the checkbox(s) of the options that you want to remove and click OK button. All the selected options and mapping associated with the particular element will be removed.

...

Context schema allows you to map Context Variable with any element of schema.
This section explains you how to use context schema to map context variable.
High level steps to use context schema are as follows:

• Create Context Schema Definition
• Load Context variables
• Map schema elements
• Modify streaming properties of Mapping Activity

...

First of all you need to create context schema definition. Context schema definition contains name of the context variable that you want to map to other element. While creating context schema definition, you can create context variables or you can import it from the process flow within which you want to use this mapping activity.
 

Steps to create Context Schema Definition

1. In Data Mapper applet, from the Action menu and select Create Context Schema Definition. The Create Context Schema Definition Dialog window is displayed ( see Figure 474 ).

   Image Removed

   Figure 474: Create Context Schema

   Info
   Only the Remove Mapping is displayed as always enabled. The other options are enabled only if they have been defined for the particular element.

2. To add a context variable click Add button and enter the name of the variable.

3. Repeat the same steps to create other variables (see Figure 475 ).

   Image Removed

   Figure 475: Add Variables

4. You can also import the context variables of the process flow in which you want to use this mapping activity. To import context variables from process flow, click Import From Process Flow button. Import Context Variable dialog box is displayed (see Figure 476 )

   Image Removed

   Figure 476: Import Context Variables

5. Select the process flow, from which you want to import context variables and click Load.
6. Click Save.

...

Once you have created the context schema, you need to load it at source or target end depending on your need.
 

Steps to Load Context Schema Definition

1. To load the Context Schema at source end, click the Open Source Schema button in the source panel. Select Schema dialog box is displayed ( see Figure 477).

   Image Removed

   Figure 477:Load Context Variable

2. Select the Context Variable radio button and click the Load button. The variables on Context schema are loaded in source panel.
3. Similarly you can load context schema in the target panel.

...

Map Schema Elements

Once you load the context schema, you can map its variables to elements of other schema (see Figure 478 ).

...

Once you created the mapping activity using context schema you need to changes its streaming properties while creating process flow using this mapping activity.
If Context Schema is loaded at source side then there is no need to provide the source (dummy source) stream to the Mapping activity. Similarly if Context schema is loaded at target side then Mapping activity will not generate any output stream, so there is no need to attach dummy target. To achieve this Generate Stream and Consume Stream property has been added to Data Mapper activity in the Process Designer. User can disable these properties based on whether Context schema is loaded at source or target side.
 

Steps to disable input and output stream of mapping activity

...

While designing the process flow, double click the mapping activity that you have created using context schema definition. Properties of the mapping activity are displayed (see Figure 479 )

Image Removed

Figure 479:Change streaming

Change the value of Consume Stream or Generate Stream property to false.

...

Right-click the blank space in the Mapping Graph Area and select the Constants option. A Constant node is displayed in the Mapping Graph Area (see Figure 480).

Image Removed

Figure 480: Add a Constant Node

...

Double-click the Constant node. The Input dialog box is displayed (see Figure 481).

Image Removed
Figure 481: Enter Constant Value

...

Mark the Add Quotes checkbox as checked, if you want to define the constant as a string. Else, the constant is defined as numeric data. By default, this checkbox is unchecked, implying that a constant is defined as a number. However, you can change the constant to string data type by checking this checkbox anytime.

...

...

...

Steps to map elements using the 'Division' Math Mapping Function

...

Click Math function menu and select the Division sub-function. A div node is displayed in the Mapping Graph Area (see Figure 482).

Image Removed

Figure 482: Add Div Sub-Function Node

...

Create a link from the output of the div function node to the Target element (see Figure 483).

Image Removed

Figure 483: Create Links between Nodes for Mapping Elements using Div Function

...

Using String Function

...

...

Steps to map elements using the 'Concat' String Mapping Function

...

Ensure that the source and target elements to be mapped are selected and displayed in the Mapping Graph Area.

...

Create a link from the output of the concat node to input of the target element node (see Figure 485).

Image Removed

Figure 485: Create Links between Nodes for Mapping Elements using Concat Function

...

...

The Date mapping function enables you to map elements by generating dates in specific formats. It also returns the current date and the difference between two dates. It comprises of various sub-functions, which are listed in the table below.

...

...

Steps to map elements using the 'Date-Difference' Date Mapping Function

1. Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes.
2. Ensure that the source and target elements to be mapped are selected and displayed in the Mapping Graph Area.

3. You need to add a constant value for using this function. Once it is added, a Constant node with its value is displayed in Mapping Graph Area.

   Info

   This function requires four inputs. The first input represents the value of Date1. The second input represents the value as the format of Date1. The third input represents the value as Date2. The fourth input represents the value as format of Date2. The Date1 and Date2 values can either be in the form of constants or XPath values. The formats of Date1 and Date2 are however always in the form of constants.

4. Click Date mapping function and select Date-Difference sub-function. A date-difference node is displayed in the Mapping Graph Area (see Figure 486).

   Image Removed

   Figure 486: Add Date-Difference Sub-Function Node

5. Create a link from the output of the first constant value to the first input of the date-difference node.
6. Create a link from the output of the second constant value to the second input of the date-difference node.
7. Create a link from the output of the third constant value to the third input of the date-difference node.
8. Create a link from the output of the fourth constant value to the fourth input of the date-difference node.

9. Create a link from the output of the date-difference node to input of the target element node (see Figure 487).

   Image Removed

   Figure 487: Create Links between Nodes for Mapping Elements using Date-Difference Function

10. Click the Apply Mapping ( Image Removed ) button. This maps elements by generating the difference between Date1 and Date2 using the date-difference sub-function.

...

...

Steps to map elements using the 'Sum' Aggregation Mapping Function

1. Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes.
2. Ensure that the source and target elements to be mapped are selected and displayed in the Mapping Graph Area.

3. Click Aggregation function and select the Sum sub-function. A Sum node is displayed in the Mapping Graph Area (see Figure 488).

   Image Removed

   Figure 488: Add Sum Sub-Function Node

4. Create a link from the output of the Source element to the input of the Sum node.

5. Create a link from the output of the Sum function node to the Target element (see Figure 489).

   Image Removed

   Figure 489: Create Links between Nodes for Mapping Elements using Sum Function

6. Click the Apply Mapping ( Image Removed ) button. This maps elements using the Sum sub-function. A line is displayed between the source and target panels showing the mapping of the source element to the target element.

...

Mapping Function

...

Sub-Functions

...

Description

...

Example

...

Conditional

...

IF Conditions

...

This function comprises of two sub functions:

...

...

For Filtering Records

...

Filters the records/elements on basis of the specified condition.

...

...

For Mapping To Elements

...

Returns a value if the specified condition is true.

...

IF CONDITION {#Age=25} Value= [100]
Returns 100 if the Age has the value of 25 in the source record.

...

...

When Condition

...

Returns a particular value if the specified condition is true, else it returns another value.

...

...

Select Query

...

This is a customized mapping function.
Returns the output based on the applied select query on a table in the any of the three databases (Oracle, Sql, IBM DB2).
Select Query supports single field selection and returns first matching record.

...

...

Sequence

...

This is a customized mapping function.
Returns integer values starting from the first argument and incrementing it by the second argument for each record. Both the arguments must be integer constants.

...

...

Append

...

This is a customized mapping function.
Appends the second string after the first string. Used to append only IF Condition.

...

Mapping Function

...

Sub-Functions

...

Description

...

Example

...

IF Condition

...

Nested IF

...

Contains IF condition inside the value of previous IF condition.
Returns output when all IF conditions are satisfied.
For example:
IF CONDITION {condition1} VALUE=[IF CONDITION {condition2} VALUE=[IF CONDITION {condition3} VALUE=[Value1]]]
Returns Value1 when all IF conditions are satisfied.

...

When Condition

...

Nested When

...

Contains When condition inside the value of previous When condition.
Returns varied output based on the When conditions being satisfied.
For example:
WHEN CONDITION {condition1} VALUE=[WHEN CONDITION {condition2} {VALUE=['value1'] OTHERWISE VALUE=['value2']] OTHERWISE VALUE=['value3']
Returns Value1 when both When conditions are satisfied.
Returns Value3 when the first When condition fails.
Returns Value2 when the first When condition is satisfied, but the second one fails.

...

IF and When Condition

...

IF and When conditions return Boolean

...

Returns value based on the function used as whether the condition returns True or False.
If a string or source element contains a character or group of characters, then True is returned, else False is returned. Based on the return value of the condition, the output value is generated.
For example:
WHEN CONDITION {contains (var1, str)} VALUE=[var2] OTHERWISE VALUE=[var3]
If var1 contains str, then True is returned, else False is returned.
If the condition returns True, then var2 is generated as output, else var1 is the output value.

...

IF and When Condition

...

Mixed
condition

...

Contains IF condition inside the value part of When condition or vice versa.
Returns varied output based on the conditions being satisfied.
For example:
WHEN CONDITION {condition1} VALUE=[IF CONDITION {condition2} VALUE=['value1']] OTHERWISE VALUE=['value2']
Returns Value1 when both conditions are satisfied.
Returns Value2 when the first condition fails.
Returns no output when the first condition is satisfied but second condition fails or when both conditions fail.

...

IF Condition

...

Multiple IF

...

Contains IF conditions placed sequentially, with each IF having its value part.
Two IF conditions are appended using Append sub-function of the String Function.
Returns varied output based on the condition being satisfied.
For Example:
IFCONDITION {condition1} VALUE=['value1'] IF CONDITION {condition2} VALUE=['value2']
Returns Value1 if condition1 is satisfied.
Returns Value2 if condition2 is satisfied.

...

When Condition

...

When condition with more than one conditions in it.

...

Contains When condition containing logical operators like and/not to make multiple conditions inside the When condition.
There are many permutations/combinations for this sub-function.
Example 1:
WHEN CONDITION (cond1 and cond2) Value = ['value1'] otherwise value = ['value2']
Returns Value1 if both conditions are satisfied, else returns Value2.
Example 2:
WHEN CONDITION (cond1 or cond2) Value = ['value1'] otherwise value = ['value2']
Returns Value1 when either one or both conditions are satisfied, else returns Value2.

...

IF Condition

...

IF condition with more than one conditions in it.

...

Contains IF condition containing logical operators like and/not to make multiple conditions inside the IF condition.
There are many permutations/combinations for this sub-function.
Example 1:
IF CONDITION (cond1 and cond2) Value = []
Returns Value1 when both conditions are satisfied, else no output is returned.
Example 2:
IF CONDITION (cond1 or cond2) Value = []
Returns Value1 when either one or both conditions are satisfied, else no output is returned.

...

Image Removed
Figure 490: Add Greater Than or Equal To Boolean Function Node

...

Create a link from the output of the Constant node to the second input of the >= operator node (see Figure 491).

Image Removed

Figure 491: Create Links between Nodes for Mapping Elements using Greater Than Equal To Function

...

Click Conditional mapping function and select IF CONDITION sub-function. Further select For Mapping to Elements option. An IF CONDITION node is displayed in the Mapping Graph Area (see Figure 492).

Image Removed

Figure 492: Add IF Conditional Function Node

...

Image Removed
Figure 493: Creating Links between Nodes for Mapping Elements using IF Conditional Function

Click Apply Mapping ( Image Removed ) button. This maps elements using IF CONDITION function. A line is displayed between source and target panels showing the mapping of the source element to the target element.

...

Mapping Function

...

Sub-Functions

...

Description

...

Example

...

Axis

...

File Path – XPath

...

This is a customized mapping function.
This is an XML Lookup which returns the value of the element/attribute within the XML file whose path is specified. The File path and XPath must be specified in single quotes.

...

Self

...

Returns the element which is the context node itself.

...

Child

...

Returns the element which is the child of the context node.

...

Parent

...

Returns the element, which is the parent (if any) of the context node.

...

Following-sibling

...

This axis contains all the following siblings of the context node. It returns the first occurrence of the element/attribute in the next sibling of the context node. If the context node is an attribute node or namespace node, then this axis is empty.

...

Ancestor

...

Returns the element which is the ancestor of the context node. This axis always includes the root node, unless the context node is the root node.

...

Ancestor-or-self

...

This axis contains the context node and the ancestors of the context node. It always includes the root node. It returns the context node or ancestors of the context node.

...

Preceding-sibling

...

This axis contains all the preceding siblings of the context node. It returns the first occurrence of the element/attribute in the preceding sibling of the context node. If the context node is an attribute node or namespace node, then this axis is empty.

...

Descendant

...

Returns the element which is the descendant of the context node. This axis does not contain attribute nodes.

...

Descendant-or-self

...

This axis contains the context node and the descendants of the context node. It returns the context node or descendants of the context node.

...

Generate-id

...

Generates a unique id for the element/attribute specified by the XPath argument.

...

Current

...

Removes all tags from the specified xml file and returns the data.

...

...

Mapping Function

...

Sub-Functions

...

Description

...

Example

...

Context

...

Set-Context

...

This is a customized mapping function.
Sets the value of the specified variable argument in the process flow context. This value can be string constant, numeric constant, XPath or output of limited set of mapping function, which can be used before set-context function.
This function does not return a value. If mapped to a target element, it creates an empty tag of that target element in output XML.

...

...

Get-Context

...

This is a customized mapping function.
Returns the value of the specified variable argument from process flow Context. This value can be string constant, numeric constant, XPath or output of limited set of mapping function. If no value has been set, then the value specified in the second argument is returned.

...

Using Set-Context Function

...

• Mapping Set-Context function using local variable
• Global declaration of Set-Context function
• Mapping Set-Context function to any target element

...

For example, if you want to set the value of process flow context variable based on the output of WHEN condition. The WHEN condition is used to return "True" when value of a source element "SALARY" is greater than 8000, else it will return "False". The output of WHEN condition is mapped to a local variable "BolSalary8K". To set the value of "BolSalary8K" to the process flow context variable, you can use Set-Context function. You have to create another local variable "Var1", where value of process flow context variable "ContextVar" is set using Set-Context function. This is done by mapping Set-Context to the value part of the local variable "Var1". The first argument of the Set-Context function is the name of the process flow context variable "ContextVar" and second argument is the local variable "BolSalary8K", which contains the output of WHEN condition.
Advantages

• Need not be mapped to a target element
• Local variable can be used as second argument of Set-Context function
• XPath of a source element can be used as second argument of Set-Context function
• Set-Context function is executed for each record of the source data

...

• Local Variable used to map set-context function will have an empty value.

...

Steps to pass output of mapping function or condition to a local variable

...

Enter the value of the local variable in the Local Variable Value field. In this example, you have to specify the WHEN condition as displayed in Figure 494.

Image Removed

Figure 494: Create Local Variable

...

...

• Easy to use
• Need not be mapped to a target element
• Need not create any local variable

...

• Local variable cannot be used in value part of Set-Context function
• If XPath of a source path is used, Set-Context function is executed for the first record only.

...

Click the Context Variables tab. The Context Variables pane is displayed (see Figure 496).

Image Removed

Figure 496: Context Variables Pane

...

Enter the value of process flow context variable in the Context Variable Value field (see Figure 497).

Image Removed

Figure 497: Enter Context Variable Value

...

Click No to save the context variable and shift focus to the other object. If you click Yes, then the defined context variable is cleared and the focus is shifted to the other object.

...

• • Need not to create any local variable
  • Executed for each record

...

• • Need an additional target element, whose value is not required at the target end

...

Click Context mapping function menu and select Set-Context sub-function. A set-context node is displayed in the Mapping Graph Area (see Figure 498).

Image Removed

Figure 498: Set-Context Node

...

Add another constant node for the second argument (e.g. 100) of the set-context function.

...

Create a link from the output of the set-context node to the target element (see Figure 499).

Image Removed

Figure 499: Create Links between Nodes for Mapping Set-Context Function to Target Element

...

Click No to apply the mapping and shift focus to the other object. If you click Yes, then the mapping activity is cleared and is replaced by the previous mapping in the Mapping Graph Area and the focus is shifted to the other object.

...

...

Steps to get data from the database using the 'DBQuery' DB Mapping Function

...

Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes.

...

Ensure that a Connection Info variable is created for the DBQuery and is listed in the Parameters Panel.

...

Click the DB function and select the DBQuery sub-function. A DBQuery node is displayed in the Mapping Graph Area (see Figure 500).

Image Removed

Figure 500: Add DBQuery Sub-Function Node

...

Double-click the required Connection Info variable under Connection Info in the Parameters Panel. The selected Connection Info variable node is displayed in the Mapping Graph Area (see Figure 501).

Image Removed

Figure 501: Connection Info Variable in Mapping Graph Area

...

Create a link from the output of the DBQuery node to the input of the target element (see Figure 502).

Image Removed

Figure 502: Create Links between Nodes for Mapping DBQuery Function to Target Element

...

Click No to apply the mapping and shift focus to the other object. If you click Yes, then the mapping activity is cleared and is replaced by the previous mapping in the Mapping Graph Area and the focus is shifted to the other object.

...

Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes.

...

Ensure that a Connection Info variable is created for the PreparedQuery and is listed in the Parameters Panel.

...

Click the DB function and select the PreparedQuery sub-function. A PreparedQuery node is displayed in the Mapping Graph Area (see Figure 503).

Image Removed

Figure 503: Add PreparedQuery Sub-Function Node

...

Double-click the required Connection Info variable under Connection Info in the Parameters Panel. The selected Connection Info variable node is displayed in the Mapping Graph Area (see Figure 504).

Image Removed

Figure 504: Connection Info Variable in Mapping Graph Area

...

Create a link from the output of the PreparedQuery node to the input of the target element (see Figure 505).

Image Removed

Figure 505: Create Links between Nodes for Mapping PreparedQuery Function to Target Element

...

Click the Apply Mapping ( Image Removed ) button. This maps the PreparedQuery function to the target element. The defined query is passed to the database where a connection is created using the Connection Info variable. If the Boolean value is set as 'True' then the database fetches all the values that match the query. If the value is 'False', then the database fetches only the first matching value. If you shift focus to another node, or click any of the Mapping Rules, Textual Rules, Node, Properties, XSL or Debugger tabs, without applying the mapping, an alert message is displayed (see Figure 506).

Image Removed
Figure 506: Mapper Warning

...

...

Click String mapping function and select Concat sub-function. The syntax for the Concat sub-function is displayed in the Mapping Graph Area (see Figure 507).

Image Removed

Figure 507: Syntax for Concat Sub-Function

...

Image RemovedFigure 508: Parameters of the Concat Syntax

...

Steps to add a Namespace in the XSL

1. Click the Actions menu and select Namespace.

2. Click the Namespace submenu and select Add Namespace. The Namespace dialog box is displayed (see Figure 509).

   Image Removed

   Figure 509: Adding Namespace

3. Enter the Namespace and click OK. The Namespace is added to the XSL.

...

...

Click the Namespace submenu and select Edit Namespace. The Select Namespace screen is displayed (see Figure 510).

Image Removed

Figure 510: Select Namespace

...

Click OK to save the modifications.

...

• Local: The XSL Templates defined within Local scope are available within the mapping activity, in which you have created the template.
• Global: The XSL Templates defined within Global scope are available within all the mapping activities. Once you create a global template in a mapping activity, you can use it in all the mapping activities.
• Group: The XSL Templates defined within Group scope are available only within the specific group.

...

• Mapping Rules: Enables you to use the predefined mapping functions.
• XSL Rules: Enables you to define the XSL Template code to use the defined parameters.

Steps to Create an XSL template using the XSL Rules

...

Select Manage XSL Template option or click the Manage XSL Template Image Removed icon in the toolbar (Figure 511).

Image Removed

Figure 511: Data Mapper

The Manage XSL Template screen is displayed (see Figure 512).

Image Removed

Figure 512: Manage XSL Template

...

Select the scope of the XSl Template. The default scope of an XSl Template is Local.

...

Click the Add Image Removed icon again to add the required parameters or press the Enter key to insert a new row. This will add a row immediately next to the row which is currently selected (see Figure 513).

Image Removed
Figure 513: Manage XSL Template: XSL Rules

...

Image Removed
Figure 514: Parameters Panel

...

Steps to create an XSL template using the XSL Rules

1. On the Manage XSL Template screen, click the Mapping Rules tab.
2. Enter the name of the new XSL template that you want to create in the Name field.
3. Select the scope of the XSL Template. The default scope of the XSL template is Local.
4. Click the Add Image Removed icon to add parameters for the new XSL template.
5. Enter the name of the parameter you want to add, in the Parameter Name field.
6. Click the Add Image Removed icon again to add the required parameters or press the Enter key to insert a new row. This will add a row immediately next to the row which is currently selected.

7. Select the required Mapping Function. For example, select the mapping function, Math > Add (see Figure 515).

   Image Removed

   Figure 515: Manage XSL Template: Mapping Rules

8. The respective mapping function (add symbol for this example) is displayed in the Mapping template.

   Image Removed

   Figure 516: Mapping Template: Mapping Function Symbol

9. Use the parameters that you have added in the previous steps.
   

   Image Removed

   Info
   If you need to delete any row, select the respective row and click the Delete Image Removed icon.

10. Click the Save Image Removed button to save the Local XSL template. This displays the saved template under the Templates list on the XSL Template screen. The new XSL template is also displayed under Templates in the Parameters Panel.

Image Removed
Figure 517: Parameters Panel

Map Elements using XSL Template

...

1. Ensure that the source and target schemas are loaded and all their elements are listed under their respective nodes.
2. Ensure that the source and target elements to be mapped are selected and displayed in the Mapping Graph Area.

3. Click the XSL template that you want to use for performing the required function, from the Templates list in the Parameters Panel. A Call XSL Template node is displayed in the Mapping Graph Area (see Figure 518).

   Image Removed

   Figure 518: Call XSL Template Node

4. Create a link from the output of the first Source element to the first input of the Call XSL Template node.
5. Create a link from the output of the second Source element to the second input of the Call XSL Template node.

6. Create a link from the output of the Call XSL Template function node to input of the Target element node (see Figure 519).

   Image Removed

   Figure 519: Create Links between Nodes for Mapping Elements using XSL Template

7. Click Apply Mapping ( Image Removed ) button. This maps elements using the Call XSL Template function node.

...

Global variables are used for mapping source elements, mapping functions or constants to target elements. They are declared and used globally for all target elements.
To use a global variable in a mapping activity, you need to map it to a target element. This will successfully execute the global variable when you execute the mapping activity in the process flow.

...

Steps to declare a Global Variable

...

Click the Global Variables tab. The Global Variable pane is displayed in the Mapping Graph Area (see Figure 520). 

Image Removed
Figure 520: Global Variable Pane

...

• Click required source element
• Select the required Mapping function
• Type the required value manually

• Select a Custom Method

  Info
  To select a Custom Method as the value of a global variable, double click the desired Custom Method under Custom Methods in the Parameters Panel. The selected Custom Method is displayed in the Variable Definition field. To learn how to declare a Custom Method, refer to section Using Custom Method.