An interview-ready list of toolkits and connectors that BPM / BAW teams commonly build, with what they contain - use it to structure your own examples:
- Integration connector toolkits: a generic REST connector (question 2888), a SOAP wrapper per back end, a database access toolkit (SQL services with a data source name as environment variable, paging, upsert patterns), an MQ / JMS messaging toolkit (send with correlation id, UCA templates), an SAP connector (via ACE / IIB or the SAP JCo jar in a Java integration), a Salesforce / ServiceNow connector (REST with OAuth2 token caching).
- Java connector jars (managed server files with Java Integrations): PDF generation (PDFBox / iText), Excel import / export (Apache POI), encryption / hashing (JCE), SFTP (JSch), LDAP attribute lookup (JNDI), barcode / QR generation (ZXing), JSON schema validation, XML transformation (XSLT with Saxon), e-mail with attachments (Jakarta Mail), a caching connector (Ehcache / a shared object cache).
- Common services toolkit: logging (question 107), error handling wrapper services with a standard ErrorInfo business object, audit trail writer, configuration access (EPV / environment variable helpers), date / business calendar utilities (holiday tables), user / team lookups with caching.
- UI toolkits: a house style coach view set (header, footer, themed controls), reusable composite views (address block, customer summary, document panel), validation helpers, and dashboard tiles - built on the BPM UI Toolkit.
- Domain object toolkits: shared business objects per domain (Customer, Order, Case) with versioning rules (question 767).
What interviewers look for beyond the list: how you version toolkits (snapshot naming, dependency upgrades), how you keep environment-specific values out (environment variables, Server definitions), how you test a connector (unit tests of the Java, a "connector test" dashboard), and how you avoid the "one giant toolkit" trap (small toolkits by purpose, no circular dependencies).
References