Test 349: IBM WebSphere Transformation Extender V8.2, Application Development

Section 1 - Architecture (11%)

1. Identify installation requirements in development and production environment
2. Describe the features and functions of WebSphere Transformation Extender component
3. Describe the flow of data through the mapping process
4. Identify the ways in which a WebSphere Transformation Extender map can be invoked
5. Evaluate design considerations

Section 2 - Describe the Data (24%)

1. Analyze complex data structures
2. Create a type tree using an importer
3. Use categories in a type tree
4. Define items [e.g. item attributes, restriction lists]
5. Define groups [e.g. implicit; explicit; ranges, component rules; partitioning; unordered, and choice groups ]
6. Define syntax characteristics [ e.g. fixed or variable: initiators, terminators, and delimiters]
7. Using data to differentiate record types
8. Apply component attributes [e.g. restart, identifier, and sized)
9. Interpret and handle type tree analysis errors

Section 3 - Create Transformations (28.5%)

1. Describe how WebSphereTransformation Extender validates data and creates output
2. Use XML as a source or target [e.g. XSD or type tree]
3. Create functional maps
4. Use indexing
5. Use casting functions
6. Use cross reference functions
7. Explain the relationship between executable map, functional map, and the run function
8. Use functions to restrict data passed to functional map
9. Illustrate the steps for mapping invalid data
10. Reference output objects
11. Demonstrate an understanding of argument binding
12. Design to take one input and create multiple outputs
13. Use the RUN function and execution commands

Section 4 - Test and Deploy (8%)

1. Build a map and resolve any build errors
2. Deploy to a non-Windows platform
3. Modify a map to run multiple instances
4. Demonstrate the correct usage of common command line qualifiers
5. Prepare a map for cross platform deployment

Section 5 - Problem Determination (9.5%)

1. Determine next steps from common error messages
2. Enable an audit to report bad data
3. Interpret the contents of a trace file [e.g. validation errors]
4. Use the map debugger to step through a transformation
5. Create custom error reports

Section 6 - Performance Tuning (9.5%)

1. Use the map profiler output to analyze the execution of the map
2. Use card settings to ensure transactional integrity
3. Modify map and card settings to resolve resource contention
4. Understand the impact of work space settings
5. Optimize type tree for performance

Section 7 - Connect to External Resources (9.5%)

1. Create a database configuration
2. Incorporate an EIS adapter into a map
3. Reference the database in a map input card or output card
4. Perform enrichment using database lookup
5. Use the adapter trace to determine the source of a problem
6. Use back-up settings to capture bad data