Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Aggregator Transformation
  4. Custom Transformation
  5. Custom Transformation Functions
  6. Data Masking Transformation
  7. Data Masking Examples
  8. Expression Transformation
  9. External Procedure Transformation
  10. Filter Transformation
  11. HTTP Transformation
  12. Identity Resolution Transformation
  13. Java Transformation
  14. Java Transformation API Reference
  15. Java Expressions
  16. Java Transformation Example
  17. Joiner Transformation
  18. Lookup Transformation
  19. Lookup Caches
  20. Dynamic Lookup Cache
  21. Normalizer Transformation
  22. Rank Transformation
  23. Router Transformation
  24. Sequence Generator Transformation
  25. Sorter Transformation
  26. Source Qualifier Transformation
  27. SQL Transformation
  28. Using the SQL Transformation in a Mapping
  29. Stored Procedure Transformation
  30. Transaction Control Transformation
  31. Union Transformation
  32. Unstructured Data Transformation
  33. Update Strategy Transformation
  34. XML Transformations

Transformation Guide

Transformation Guide

Step 10. Run a Workflow to Test the Mapping

Step 10. Run a Workflow to Test the Mapping

When the Integration Service runs the session in a workflow, it performs the following functions:
  • Uses the COM runtime facilities to load the DLL and create an instance of the class.
  • Uses the COM IDispatch interface to call the external procedure you defined once for every row that passes through the mapping.
Multiple classes, each with multiple methods, can be defined within a single project. Each of these methods can be invoked as an external procedure.
To run a workflow to test the mapping:
  1. In the Workflow Manager, create the session s_Test_BSFV from the Test_BSFV mapping.
  2. Create a workflow that contains the session s_Test_BSFV.
  3. Run the workflow. The Integration Service searches the registry for the entry for the COM_VC_BankSoft.BSoftFin class. This entry has information that allows the Integration Service to determine the location of the DLL that contains that class. The Integration Service loads the DLL, creates an instance of the class, and invokes the FV function for every row in the source table.
    When the workflow finishes, the FVOutputs table should contain the following results:
    FVIn_ext_proc
    2581.403374
    12682.503013
    82846.246372
    2301.401830

0 COMMENTS

We’d like to hear from you!