Need to map out your requirements for an integration platform to implement later on in 2017? Here are a few requirements that I would consider:
Single Studio Approaches. I would lean heavily towards an integration architecture based on a single integration flow designer rather than spate tools for ESB, SOA, Data, ETL, BPM, etc.
Data Mapping. Look for data transformation capabilities that are fully visual, incorporating drag and drop techniques with graphical illustration of source and destination data connections as well as use of expression flags. This simplifies the process of making data connections and visualizing them later.
Real Time, Near Real-Time and Scheduled Processes. Look for flexibility in an integration suite that simplifies the creation of business process integration flows based on the needs of your business processes. The studio should be able to govern processes that are real-time, near real-time, scheduled and long-running (asynchronous) processes.
Event Driven. Develop your integration flows with a platform that is able to define triggers based on events such as HTTP, FTP, directory scans, Web Services, and many other trigger methodologies.
Service Oriented Architecture. Look for an established approach that is used in service oriented architecture (SOA). With the right integration platform, all business processes can be published as services in a SOA manner. Service-orientation is essential in today’s mobile, cloud and API based environments.
Full-Featured Business Process Management. Look for a solution that is an integration-centric business process management suite with capabilities for process orchestration, process management and workflow. Both synchronous and asynchronous integration processes should be. Look for an easy IDE to use so that you can build alarms, alerts and escalations into business processes. These need to be sent using omni-channel communication options including email, SMS, SNMP, and social media feeds.
Built-In Monitor. The Integration Platform approach selected should incorporate a monitor includes dashboards or logs that allow you to monitor your integration and business processes. This information can be used to improve process performance and for other purposes.
Visual Process Design. Look for an integration design studio that uses a fully drag, drop and configure approach with fully visual and graphical representation of business processes including parallel and conditional execution. Take a zero code approach. And yet you will want to do this an environment like Visual Studio shell that is therefore familiar to large numbers of developers.
Full Project Documentation and Maintenance. Ideally the design studio business processes, integration flow and topology editors, provide full facility for project documentation. Documentation enables future project maintenance even when the original project staff is no longer available.
Full Integration on Both Sides of the Firewall. Look for an integration solution that, in addition to the cloud, can be installed inside of your enterprise firewall or in a hosted environment in the cloud. As a result, it should have full capabilities for BPM, event driven architecture and SOA as well as synchronization, replication and complete integration and orchestration capabilities across all business processes.
Comprehensive Component Library. Ideally, the integration platform will include dozens of built-in components, methods, wizards and gateways to help you build the needed integration to orchestrate business processes.
Web Services. The integration platform must also include full capabilities to publish and subscribe to Web Services using REST, JSON, SOAP, WSDL, UDDI and other methods. This allows third-party data sharing and SOA for your business processes.
Multi-Vendor Message Queue Support. Many legacy enterprise applications, large vendor apps, and specialized applications use some type of message queue technology. Your platform must be able to read, format, send or receive messages from the message queue systems provided by the major vendors including Microsoft Message Queue (MSMQ), WebSphere MQ (IBM) and JMS (Oracle/Sun).
Full Web Integration. A proper integration platform also includes an HTTP component that enables full interaction with websites and other technologies that use the HTTP protocol to push and get information. Scraping HTML, transforming, and transporting data to/from HTML using HTTP PUT and HTTP GET is automated using Magic xpi Integration Platform.
Email Support. Of course, your Integration Suite should also be able to send or receive email messages using generic mail protocols and interact with email servers (Google, Domino, MS Exchange) as part of a business process.
Application Interfaces. Look for a component that is designed to integrate with one or more of you major enterprise IT systems for Enterprise Resource Planning (ERP) or Customer Relationship Management. If there is no component available for your ERP and CRM, then you must closely evaluate the system’s ability to work with the API of your ERP or CRM system.
Unique Requirements. Finally, consider any unique requirements for your business type, approach, or environment. Finding that unique business advantage often means doing things different from a business process perspective and that will include differences in business process integration.
Good luck with developing the specs for your 2017 systems integration platform requirements development and project implementations.
Source: SANS ISC SecNewsFeed @ February 28, 2017 at 02:09AM