IBM ACE V12 Developer study plan

Write ESQL modules using CREATE COMPUTE MODULE, and practise declaring and propagating message trees with correct copy message body semantics.

Implement ESQL procedures and functions, including parameter passing, RETURN types, and error handling with THROW and CATCH blocks.

Build message flows that exercise ESQL compute nodes against multiple input formats (XMLNSC, JSON, BLOB) and convert between them with CREATE FIELD and ASBITSTREAM.

Configure ESQL references to shared variables, and explain when to use SHARED versus LOCAL scope.

Debug an ESQL flow by placing trace nodes and reading the logical message tree output.

Develop a Java compute node that reads and modifies the input message tree using MbMessage and MbElement APIs.

Implement Java user-defined nodes or Java compute logic that propagates to alternate output terminals based on message content.

Handle exceptions in Java compute nodes by throwing MbException and mapping them to a failure terminal.

Compare ESQL and Java compute approaches for a given transformation and justify the choice in writing.

Write a Java compute node that calls an external Java library and logs through the node's logger.

Create a message map that transforms a JSON input into an XML output, using casts, custom transforms, and conditional mapping.

Build a DFDL schema for a fixed-width or delimited text format and verify parsing and serialization round-trip.

Write an XSLT stylesheet and invoke it with the XSLTransform node, including passing parameters from the flow.

Use a Mapping node with a database or Java custom transform and explain when each transform type is appropriate.

Test each transformation approach with sample inputs and record the results.

Design an integration solution on paper that identifies message flow boundaries, shared libraries, and reusable subflows.

Decide which artifacts belong in a shared library versus an application, and justify the decision.

Create a BAR file containing an application and a shared library, and deploy it to a local integration server.

Use the ibmint command line to package and deploy an application without the toolkit.

Version an application by incrementing its version and redeploying alongside the previous version.

Implement a REST API by importing an OpenAPI document and generating a message flow skeleton.

Add request validation, path and query parameter handling, and correct HTTP status codes to the generated REST flow.

Build a SOAP-based flow that consumes a WSDL-described service and maps the response.

Configure an HTTP Input node with a security scheme and explain how the security profile is applied.

Test the REST endpoints with a command-line HTTP client and record request and response pairs.

Configure a JDBC connection to a database and implement a flow that performs select, insert, and update operations.

Set up a connector or adapter request node for an external system available in your environment and handle its response.

Apply connection pooling and retry settings, and explain the effect of each setting.

Handle connector errors by routing to a failure terminal and returning a meaningful error response.

Document the credentials and endpoint configuration approach without embedding secrets in the flow.

Start and stop an integration node and integration server, and inspect their state with command-line administration tools.

Deploy an application, verify it is running, and use the web administration interface to inspect deployed resources.

Configure a trace on a message flow and capture the logical message tree at a chosen point.

Set up logging and event monitoring so that a failed flow produces a diagnosable record.

Diagnose an intentionally broken flow using logs, traces, and exception lists, and document the root cause.

Repackage all practice artifacts into a single versioned BAR file and deploy it cleanly to a fresh integration server.

Review weak areas from earlier weeks and rewrite the notes for the two domains with the lowest practice scores.

Complete a timed practice set covering all eight domains and record the score per domain.

Verify that every deliverable from weeks one through seven still deploys and runs after the final repackaging.

Write a one-page checklist of deployment and versioning steps to use on the job.