Integration Designer (IID) is the Eclipse-based tool of BAW Advanced (formerly WebSphere Process Server / BPM Advanced) for SCA modules. Typical ways it is used next to BPDs:
- Advanced Integration Services (AIS): a BPD calls a service that is implemented in IID (Java, mediation, BPEL, adapters) - the AIS is declared in Process Designer and implemented in an SCA module; used when the integration needs adapters (SAP, Siebel, JDBC adapter, Flat File - question 2574), transactions across systems, or complex XML mediation.
- BPEL processes for long-running, system-centric, transactional flows (straight-through processing) and human tasks (HTM) for the old-style task model; BPDs call them and they call BPDs (question 789).
- Mediation modules (ESB-like message routing, transformation with XSL / business object maps, service gateway - question 787) when no separate ESB (IIB / ACE) exists.
- Adapters: WebSphere Adapters for SAP, JDBC, Flat File, FTP, JD Edwards, PeopleSoft, Siebel, e-mail, Domino, IBM i, CICS / IMS - inbound (event) and outbound.
- Business objects and maps shared between modules, relationships (cross-reference of keys between systems), selectors (dynamic implementation choice by date / criteria).
- Exposing modules as web services (SOAP / WSDL with policy sets) for other systems.
Strategic note: IID / BAW Advanced is not available on CP4BA containers; new integration work goes to App Connect Enterprise (ACE) and REST external services. Keep IID for existing BPEL / adapter assets on traditional BAW Advanced.
References