Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Aggregator transformation
  6. Cleanse transformation
  7. Data Masking transformation
  8. Deduplicate transformation
  9. Expression transformation
  10. Filter transformation
  11. Hierarchy Builder transformation
  12. Hierarchy Parser transformation
  13. Hierarchy Processor transformation
  14. Input transformation
  15. Java transformation
  16. Java transformation API reference
  17. Joiner transformation
  18. Labeler transformation
  19. Lookup transformation
  20. Mapplet transformation
  21. Normalizer transformation
  22. Output transformation
  23. Parse transformation
  24. Python transformation
  25. Rank transformation
  26. Router transformation
  27. Rule Specification transformation
  28. Sequence Generator transformation
  29. Sorter transformation
  30. SQL transformation
  31. Structure Parser transformation
  32. Transaction Control transformation
  33. Union transformation
  34. Velocity transformation
  35. Verifier transformation
  36. Web Services transformation

Transformations

Transformations

Classpath configuration

Classpath configuration

If you use third-party or custom Java packages in the Java transformation, you must configure the classpath. The Secure Agent includes the classes and resource files within the classpath when it compiles the Java code. You do not need to configure the classpath if you use only built-in Java packages.
For example, you import the Java package
converter
in the Java transformation and define the package in converter.jar. You must add converter.jar to the classpath before you compile the Java code. However, if you import the package java.io, you do not need to set the classpath because java.io is a built-in Java package.
Set the classpath to each JAR file or class file directory associated with the Java package. Separate multiple classpath entries with a semicolon (
;
) on Windows or a colon (
:
) on UNIX. The JAR or class files must be accessible by the Secure Agent.
If you use the Java transformation in an
elastic mapping
, the files must be stored in the following directory on the Secure Agent machine:
<Secure Agent installation directory>/ext/ctjars
Additionally, consider the following guidelines for
elastic mappings
:
  • If the Secure Agent machine stops unexpectedly and the agent restarts on a different machine, you must add the JAR or class files to the same directory on the new machine.
  • If you update the JAR or class files on the Secure Agent machine, the files take effect the next time you run a job on the
    elastic cluster
    .
  • To prevent long-running jobs from failing, do not update the files on the Secure Agent machine more than four times while you have jobs running.
If you use a serverless runtime environment, the files must be stored in the supplementary file location. If you update the files, you must redeploy the serverless runtime environment for the changes to take effect. For more information about the location, see
Administrator
in the Administrator help.