The most important components and technical assumptions of Euvic
BizTalk Integration Framework include:
One internal integration database
- Combines business info with technical and flow info.
- Messages (metadata):
- Crucial information – External ID (i.e. Order No – can be used for fast searching of messages).
- Easier support/maintenance.
- Flows (technical + possibility of visualization at different levels, including business and technical).
- Information on errors.
- Notifications (e-mails).
- Resubmit possibility.
- Configuration (business for flows).
- Monitoring – possibility to expand data by views or prepared UI.
- Better performance than when using BAM & Tracking DB, but BAM and Tracking can be used as a supplement for additional tracking/monitoring.
Grzegorz MazurTechnical Director Passions: Fast cars and technological innovations.
Standard procedures and views
- Our framework uses a standard set of procedures (AddErrorLog, HandleErrorByInstanceId, AddMessageArchiveEntry, CreateMessage) and views (InterfaceStatus, ExternalErrorLogs) to support BizTalk integration projects.
Adapters and pipelines
- We can take advantage of an extensive set of BizTalk adapters enabling simple communication with various data sources.
- Our framework also includes a set of pipeline templates, pipeline components and default pipelines to make integration projects run faster and easier.
Process interface numbering
- All orchestration maps have the same prefix with the interface number. This convention helps in the maintenance and understanding of flows.
Interface treated like a reusable component, with minimum 3 orchestrations
- Orchestrations that are part of interfaces are called directly without a sub-pub mechanism. An interface can be treated like a reusable component.
- Each interface should have at least 3 orchestrations:
- Manager – receives input message that triggers the interface. It can also have the singleton pattern to make sure that only one instance of the interface is processing.
- Process – makes business flow. Can contain other orchestrations calls, for receiving extra data etc.
- Send – sends a prepared message to its destination system.
Consistency of configuration
- SSO for storing credentials and all configurations like connection strings to achieve the consistency of configuration.
File storage for message logs to provide easy maintenance and high performance
- File storage for message logs – an archive log is split into directories based on date, interface number and process. Paths to messages are stored in the integration database. The archive is configurable so the user can select which interfaces and which messages in interfaces (internal, input and output) should be stored.
- This solution provides easy maintenance and high performance.
Common processes and orchestration templates
- We have a number of pre-defined orchestrations processes (e.g. Archive, EmailNotifications, Routing Failure) and orchestration templates (e.g. FileManager, SingletonManager) that can be used as a ready-to use solution to speed up BizTalk integration projects.
- Persist/Resubmit – when an error occurs because of an invalid message it can be persisted in an internal database, corrected by the user and resubmitted.
- All errors are handled and stored in an internal database with correlated paths to a message log and flow logs.
- Email notifications – fully configurable for errors or business cases.
Custom watchdog mechanism
- It can be used when needed to monitor if messages were received or sent by the interface.
- All called interfaces and messages have an assigned ActivityId from start point to end point to enable easy searching for correlated massages from a business flow point of view.
Good programmers use their brains, but good guidelines save us having to think out every case.
Talk to Grzegorz about Framework
Write to Grzegorz