IBM Sterling B2B Integrator (C8060-218) flashcards
IBM Sterling B2B Integrator (C8060-218) · 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.
- Perimeter server
- A separate process that fronts inbound and outbound network traffic for the core engine. It isolates network I/O from business process execution and can be scaled independently of engine nodes.
- Cluster session affinity
- A load balancer setting that keeps a user's HTTP session pinned to one engine node. Without it, admin console sessions break because session state is not shared across nodes.
- customer_overrides.properties
- A properties file whose values override shipped system property defaults. It is the supported place to tune adapter behavior, timeouts, and thread pools without editing shipped files.
- Shared file system requirement
- In a cluster, all nodes must read and write the same shared directory where large payloads and adapter artifacts are stored. Inconsistent shares cause missing document errors.
- Graphical Process Modeler
- An Eclipse-based editor that renders and edits business process XML visually. It exposes each service node's typed configuration parameters on a canvas and writes the BPML document.
- onFault block
- A BPML construct that catches exceptions raised by child services. It exposes error details so the process can log, notify, retry, or terminate gracefully instead of failing silently.
- Primary document
- The main payload carried through a business process context. It is addressed by XPath such as /ProcessData/PrimaryDocument and passed between services as the default document.
- Choice service
- A BPML branching construct that evaluates XPath conditions in order and executes the first matching branch. It replaces nested conditional logic inside a single process flow.
- Partner group inheritance
- A configuration mechanism where a trading partner group supplies default envelope and communication settings to member partners. Partner-level values override the inherited group defaults.
- AS2 identifier
- A string agreed between trading partners that identifies each side in AS2 messages. It is configured in the partner profile and must match the value the partner sends.
- ISA sender identification
- The interchange sender ID and qualifier in the ISA segment. Inbound processing matches these values to a configured partner profile to select envelope and translation settings.
- MDN receipt
- An AS2 message disposition notification returned by the receiver to confirm receipt and, optionally, decryption and signature verification. It can be synchronous or asynchronous.
- EDI envelope layers
- The three nested EDI wrappers: interchange (ISA/IEA), functional group (GS/GE), and transaction set (ST/SE). Enveloping services add or strip these layers during processing.
- ISA delimiters
- Characters defined in the ISA segment that separate elements, sub-elements, repeated elements, and segments. Both partners must use identical delimiters for the interchange to parse.
- Control number uniqueness
- ISA, GS, and ST control numbers must be unique per partner and interchange. Reused control numbers cause the receiver to reject the interchange as a duplicate.
- 997 versus 999
- The 997 is a functional acknowledgment reporting envelope-level acceptance or rejection. The 999 adds implementation-level detail used for HIPAA and similar transaction sets.
- FTP passive mode
- An FTP mode where the client initiates the data connection to the server. It is required when a firewall blocks the server's inbound connection back to the client.
- SFTP host key trust
- SFTP verifies the server's SSH host key against a known-hosts entry. If the key is unknown or changed and not trusted, the adapter refuses to connect.
- AS2 signing and encryption
- The sender signs with its private key and may encrypt with the receiver's public certificate. The receiver verifies with the sender's public certificate and decrypts with its own private key.
- MQ adapter parameters
- Connection settings for IBM MQ: queue manager, queue name, channel, host, port, and credentials. The adapter can get, put, or browse messages and supports transactional get.
- File System adapter polling
- The adapter scans a directory at a configured interval and picks up files matching a name pattern. Rename or delete after pickup prevents duplicate processing.
- Group-based permissions
- Access control in which permissions on services, business processes, and admin functions are granted to groups. Users receive access only through membership in those groups.
- Key store versus trust store
- A key store holds private keys and their certificates for this system. A trust store holds CA certificates used to validate certificates presented by remote parties.
- Certificate chain validation
- Verification that a presented certificate is unexpired, correctly used, and chains to a trusted CA in the trust store. Failure causes TLS handshake or signature verification errors.
- Audit logging
- Recording of administrative changes and user actions for compliance review. It must be enabled and logs retained according to the organization's audit requirements.
- BP schedule definition
- A configured start time, recurrence pattern, and target business process. Schedules can be disabled without deletion, which is useful for maintenance windows.
- Process monitor
- An admin console view listing running, completed, and failed process instances. Drilling into an instance shows each service's status, input, and output for diagnosis.
- Duplicate control number fault
- A failure where an inbound interchange reuses an ISA, GS, or ST control number already seen from that partner. The receiver rejects it as a duplicate transmission.
- Document viewer
- A diagnostic tool that displays primary and named documents at each step of a process instance. It helps locate where a mapping or routing error introduced bad data.
- Database connection pool sizing
- The number of DB connections available to the engine. Adapter concurrency and BP thread counts should not exceed it, or processes block waiting for connections.
- Process purge policy
- A scheduled cleanup that deletes old process instances and their documents. Without it, transaction tables and the shared file system grow until performance and backups degrade.
- JVM heap monitoring
- Tracking heap usage and garbage collection pauses to detect memory pressure. Exhaustion often appears as slow business processes rather than an obvious crash.