Architecture and Installation
Domain 1 covers the runtime topology of Sterling B2B Integrator and the decisions made during installation. The exam expects you to know which tier owns which responsibility and why a component is placed in the DMZ.
Runtime tiers
- Application server: hosts the B2B Integrator EAR, business processes, services, and adapters; runs on a supported JVM/application server.
- Database: stores process data, partner profiles, maps, configuration, and audit records.
- Shared file system: holds properties, deployed artifacts, logs, and temporary files visible to every node in a cluster.
- Perimeter server: terminates inbound partner connections in the DMZ and forwards traffic to the application tier, reducing exposed ports.
- Adapter container: optional separate JVM for adapter workload isolation and scaling.
Installation essentials
Install the product, create and size the database schema, set properties in customer_overrides.properties rather than editing shipped files, deploy the application, then start and validate. In a cluster, each node must see the same shared configuration, and the load balancer must preserve session affinity where required.
Worked example
A partner connects inbound SFTP on port 22. Exposing the application server directly would place the JVM in the DMZ. Correct design: run a perimeter server in the DMZ, allow port 22 to it, and let it forward to the internal adapter. The application and database remain internal.
Traps
- Editing base property files: upgrades overwrite them; overrides win.
- Forgetting that all cluster nodes need consistent shared storage and time sync.
- Confusing the perimeter server with a full reverse proxy or load balancer.
- Sizing only the database and ignoring JVM heap and adapter containers.