Boomi Architect flashcards
Boomi Architect · 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.
- Process shape types
- Boomi process shapes include start, connector, map, decision, branch, try/catch, stop, notify, and subprocess; each has a type and configuration that determines its runtime behavior.
- Document cache
- The in-memory store where each document in a Boomi process is held under a data element name; shapes read and write documents through this cache during execution.
- Decision shape
- A process shape that evaluates ordered conditions against the current document or properties and executes the first branch whose condition evaluates to true.
- Try/Catch shape
- A process shape that catches exceptions from connectors or maps; the catch path receives an error document containing message, stack trace, and optionally the original document.
- Subprocess call
- A synchronous call to another process that shares the parent process's document cache; it does not create a separate execution thread and cannot run in parallel on its own.
- Process scheduling
- A Boomi process can be triggered by interval, cron expression, or event; scheduled processes run in the runtime and are subject to atom or cloud execution limits.
- Unhandled exception behavior
- An unhandled exception in a Boomi process marks the execution as ERROR, logs the failure, and stops the process unless a try/catch or notify shape handles it.
- API Service component
- A Boomi API component that groups operations and binds each operation to a process with an HTTP method and path; it defines the API's contract for consumers.
- API Proxy component
- A Boomi API component that defines a front-end path and routes requests to a back-end service or URL, applying gateway policies and authentication before forwarding.
- API gateway deployment
- An API must be deployed to a gateway (cloud or atom) before it is reachable; deployment packages the API component and its dependencies for runtime enforcement.
- OAuth 2.0 flows
- Boomi API management supports OAuth 2.0 client credentials and authorization code flows; tokens are validated at the gateway according to the configured policy.
- Rate limiting policy
- A gateway-enforced policy that restricts the number of requests per client or time window; it is configured on the API component and does not require process changes.
- API versioning rule
- Changing an operation signature or path requires a new API version or path prefix; this prevents breaking existing consumers that depend on the prior contract.
- CORS policy
- A gateway-level policy that controls cross-origin resource sharing headers for browser clients; it is applied to the API without modifying the backing process.
- OpenAPI support
- Boomi REST API components can import and export OpenAPI definitions, enabling documentation generation and contract-first design for API services.
- Profile types
- Boomi profiles define document structure for mapping and include XML, JSON, flat file (delimited or fixed), database, EDI, and custom profile types.
- Map shape
- A process shape that transforms a source profile document into a target profile document using direct, default, or conditional mappings and functions.
- Map functions
- Built-in transformations in a Boomi map, including string, numeric, date, lookup table, and scripting (Groovy or JavaScript) functions applied to field values.
- Flat file profile
- A profile for delimited or fixed-width text files; delimiter, qualifier, header row, and column positions must match the actual file or parsing fails.
- Database connector operations
- The Boomi database connector supports SELECT, INSERT, UPDATE, DELETE, and stored procedure operations; result sets are described by a database profile.
- JSON profile
- A Boomi profile describing JSON structure with a root element, arrays, and nested objects; it can be generated from a sample document using the wizard.
- Data process shape
- A process shape used for extract-transform-load without an external connector; it reads from a source profile and writes to a target profile.
- Map validation
- Required fields and default values in a map enforce data validation; missing required values cause map exceptions that can be caught by try/catch.
- AI connector pattern
- A Boomi connector operation invokes a model provider; the request document carries the prompt and the response document carries the model output for mapping.
- Token context window
- Each AI model has a maximum number of tokens it can process in one call; prompts and documents exceeding this limit must be chunked before invocation.
- Embeddings
- A model operation that converts text into a numeric vector; vectors are stored in a vector database or Boomi Data Hub for similarity search and retrieval.
- Retrieval-augmented generation
- A pattern that embeds a query, performs similarity search over stored vectors, injects retrieved chunks into the prompt, and then invokes the model.
- AI secrets management
- API keys for AI providers are stored in Boomi secrets or environment extensions and referenced at runtime, never hard-coded in process definitions.
- AI retry with backoff
- Model calls can time out or hit rate limits; wrap them in try/catch and retry with increasing delay to avoid cascading failures in the process.
- Agent composition
- An agent combines a model, tools, memory, and an orchestration loop; in Boomi, tools are processes or API operations exposed to the model.
- Tool schema
- Each agent tool has a name, description, input schema, and output schema; the model selects and calls tools based on these definitions.
- Agent iteration cap
- A guardrail that limits the number of observe-decide-act cycles in an agent loop to prevent runaway execution and unbounded cost.