IBM ACE V12 Developer flashcards
IBM ACE V12 Developer · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Integration server
- An independent JVM in ACE V12 that hosts message flows and resources. It can run standalone or under an integration node. Each server has its own configuration file (server.conf.yaml).
- Integration node
- A logical grouping of integration servers managed by a single administration process. Provides shared configuration, a web UI, and centralized deployment. Created with mqsicreatebroker in V12.
- Policy project
- A project that stores environment-specific configuration as policies (MQ, HTTP, JDBC, etc.). Policies are referenced by policy sets and bindings, separating config from flow logic.
- DFDL
- Data Format Description Language, an XML schema-based language for describing non-XML data such as CSV, fixed-width, and binary. Used by ACE to parse and serialize text and binary formats.
- ESQL CREATE COMPUTE MODULE
- The ESQL statement that defines a compute module: CREATE COMPUTE MODULE name; CREATE FUNCTION main() RETURNS BOOLEAN BEGIN ... END; END MODULE; The main function must return TRUE.
- ESQL PROPAGATE statement
- Sends the current message assembly to a named terminal or label: PROPAGATE TO TERMINAL 'out1'; or PROPAGATE TO LABEL 'label1'. Used to implement routing inside ESQL.
- ESQL REFERENCE variable
- A variable that points to a field in the message tree without copying it. Declare with DECLARE ref REFERENCE TO OutputRoot.XMLNSC.Item[1]; use DEREFERENCE to access the value.
- JavaCompute node
- A message flow node that runs custom Java. The class extends MbComputeNode and overrides evaluate(MbMessageAssembly). Access trees via MbElement and create output with MbMessageAssembly.
- Mapping node
- The Graphical Data Mapper node that transforms between message models (XML, JSON, DFDL). Supports casts, if/else, assign, for-each, and join transforms in a visual map.
- DFDL lengthKind delimited
- A DFDL property that specifies fields are separated by delimiters (e.g., comma for CSV). Used with dfdl:separator and dfdl:terminator to parse variable-length text data.
- XSLTransform node
- A message flow node that applies an XSLT stylesheet to transform XML. Specify the stylesheet by name or file, and pass parameters via the node's stylesheet parameters table.
- HTTPInput node
- A message flow node that receives HTTP requests. Configure the path and method; use HTTPReply to return a response. Supports SSL and is the basis for REST APIs in ACE.
- SOAPInput node
- A message flow node that receives SOAP requests. Set the WSDL and operation mode; use SOAPReply for responses and SOAPFault for errors. Supports WS-Security via policy sets.
- OpenAPI import
- ACE can import an OpenAPI 2.0/3.0 document to generate a REST API skeleton. The generated application includes an HTTPInput flow and subflows per operation.
- REST error handling
- Use the Catch or Failure terminal on HTTPInput to return a JSON error body with an appropriate HTTP status code (400, 404, 500) via HTTPReply.
- MQInput node
- A message flow node that reads messages from an IBM MQ queue. Configure queue manager, queue name, and transaction mode. Supports MQMD and MQRFH2 headers.
- SalesforceRequest node
- A connector node for Salesforce. Configure a Salesforce policy with URL, credentials, and API version. Supports create, retrieve, update, delete, and query operations.
- KafkaProducer node
- A connector node that publishes messages to a Kafka topic. Configure bootstrap servers and topic; use a Kafka policy for SASL/SSL security.
- RESTRequest node
- A message flow node for outbound REST calls. Set URL, method, headers, and body. Use an HTTPRequest policy for SSL and authentication; parse responses with JSON or XMLNSC.
- JMSInput node
- A message flow node that receives JMS messages. Configure the JMS provider via a JMS policy or configurable service. Supports point-to-point and publish-subscribe.
- server.conf.yaml
- The configuration file for an integration server in ACE V12. It defines resource managers (MQ, JDBC), flow properties, logging, and security settings. Edited via YAML or mqsichangeproperties.
- mqsichangeproperties command
- Administration command to change node or server properties, e.g., -o ComIbmJVMManager -n jvmMinHeapSize -v 512. Use mqsireportproperties to view current values.
- mqsideploy command
- Deploys a BAR file to an integration server: mqsideploy <node> -e <server> -a <bar>. Use -m to set deployment mode (delta, full, add).
- Integration API
- A REST administration API for ACE, e.g., GET /apiv2/servers. Requires authentication. The web UI is available at https://host:port/ (default port 4414 for a node).
- Event monitoring
- A feature that publishes message flow events to an MQ topic or file. Enable with mqsichangeflowmonitoring; configure event sources (in, out, failure) and formats (XML, JSON).
- Flow statistics
- Performance counters for message flows, including message counts and processing times. Enable with mqsichangeflowstats -s on -e <server> -k <flow> -n advanced; view with mqsireportflowstats.
- mqsireadlog command
- Reads and formats integration node logs: mqsireadlog -i <node> -e <server> -o -f -b. Use mqsiformatlog to convert binary logs to text.
- Flow exerciser
- A Toolkit feature that sends test messages through a flow and visualizes the path. Enable Record and Trace to see the message journey and debug.
- BIP messages
- Error and informational messages from ACE, e.g., BIP2087 (server not running), BIP2110 (parser error), BIP2230 (error in flow). Look up codes in the documentation for troubleshooting.
- BAR file
- A Broker Archive file containing compiled message flows (.cmf), message models, maps, Java, and configurable properties. Created via Toolkit or mqsipackagebar; deployed with mqsideploy.
- mqsipackagebar command
- Creates a BAR file from a workspace: mqsipackagebar -a <bar> -w <workspace> -k <project> -y <application>. Use -r to include referenced libraries.
- mqsiapplybaroverride command
- Modifies configurable properties in a BAR file without rebuilding: mqsiapplybaroverride -b <bar> -k <flow> -m <key=value>. Use -p for policy overrides.