Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
What you don’t know about Integration
Presented By: Russell Doig
• Enterprise application integration is an integration framework composed of a collection of technologies and services which form a middleware or "middleware framework" to enable integration of systems and applications across an enterprise.
• Enterprise application integration is the process of linking such applications within a single organization together in order to simplify and automate business processes to the greatest extent possible, while at the same time avoiding having to make sweeping changes to the existing applications or data structures. Applications can be linked either at the back‐end via APIs or (seldomly) the front‐end (GUI)
What is Integration?
• Interface: where two or more separate software products communicate under limited capacity. Data is maintained in multiple locations;
• Integration: A fully integrated system means that the products are one
Integration or Interface?
• Best of breed: source of truth owned and maintained by authoritative systems.
• Accessibility: view related information in real or near real time.
• Compliance: tapping into solutions without the need to consider compliance. – Records Management
Integration Benefits
How do we achieve Integration?
Refer video called ‘What is an API.mp4’
• Platform availability or compatibility– Middleware or API compatibility between systems– Cost of ownership for Native API’s– “Go it Alone” using Direct Integration approach
• Parties working together– Common goals and objectives– Benefits realisation– Skin in the game
Integration Complexity
Integration Complexity• Architecture
– Location of Services– Cloud and On‐Premise
Solutions
• Security– Authentication – Protection and Confidentiality
Financial Management Systems
• Validate Vendor Details• Push Contract Numbers• Retrieve Purchase Orders• Retrieve Invoices
FMS Standard Integration Benefits
Purchase Orders / Committed Amounts
Invoiced Amounts
Financial Summary
• OWS have developed three distinctOracle integrations– Web Services (non native)– Batch File Processing (file transfers via SFTP)– SSIS or OWS tools using ODBC
• Why?– Differing customer technical requirements– Different available technologies
Open Windows Oracle Integration
• Open Windows Integration Tools– Tools are Windows Application Software developed by OWS– Tools scheduled to execute, usually daily– Customer SME Engagement is required to achieve desired
SQL logic for data extraction
• Developed against T1 Web Services– Identified methods in the standard Web Services relatively limited
• Constraints– ODBC (OW integration tools) are not appropriate in cloud environments– T1 Web Services module is not standard, and has limitations.
Open Windows T1 Integration
• OW Developed BAPI’s– Business Application Programming Interfaces
• Standard BAPI• OWS creates Outline Agreements in SAP• Schedule of Rates
– Synchronises SAP’s master Materials and Services data to OWS Schedule of Rates
• Constraints– Complexity: must have SAP SME’s for integration development
Open Windows SAP Integration
• SSIS Packages– Leveraging SQL Server Integration Services– Packages are developed, delivered and scheduled to execute, usually daily– Customer SME Engagement is required to achieve desired
SQL logic for data extraction
• Constraints– ODBC (SSIS) are not appropriate in cloud environments
Open Windows Authority Integration
• Open Windows Integration Tools– Tools are Windows Application Software developed by OWS– Tools scheduled to execute, usually daily– Customer SME Engagement is required to achieve desired
SQL logic for data extraction
• Constraints– ODBC (OW Integration Tools) are not appropriate in cloud environments
Open Windows Computron Integration
• Payment Claims to AP
FMS Integration Options
Records Management Systems
Records Management System Benefits
Document Registration
Functionality Consistency
Document Download
• COM SDK Integrated– TRIM Desktop installed to OW Application Server– Pass User Identity to TRIM/RM via Workgroup Server– Meta data passthrough during document registration
• TRIM Desktop Client– Dependency on TRIM Desktop Client software– Open Windows launch documents via Desktop Client integrating it’s security and
records management processes
Open Windows HP TRIM / RM / CM Integration
• Integration via Objective AppLink– AppLink is a suite of Web Services maintained and licensed
by Objective– Handles all calls between Open Windows and Objective– Dynamic meta data configuration– No Pass‐through authentication possible, single identity for all document
registrations
• Objective Navigator– Users are required to have Objective Navigator installed on Desktop for document
launching and Records Management activities.
Open Windows Objective Integration
• Integration via native Web Services– Includes the document registration and get functions– Dynamic meta data configuration– Pass through authentication in on‐premise environment
• Custom Web Service– Open Windows developed web service to replicate object level security of Open
Windows to SharePoint objects.
• Constraints– Businesses are transitioning to Office365 leveraging SharePoint online, integration
due to the object security is not compatible.
Open Windows SharePoint Integration
Integration with Open Windows
• Single Sign‐On (ADFS)• Extended Partnerships• Web Services Vendor API’s
– Vender Preferred API– Cloud Compatibility
• Open Windows API– Third Party Systems launch, e.g. Workflow– Deposit or Retrieve data to and from Open Windows.
Future of Integrations
• Azure Power‐BI Embedded– Allows software developers to integrate and embed Power‐BI Reports within
Applications– No license costs, consumption based pricing.– Pass through application identity, or Azure Active Directory user for user based
reporting
• Azure Logic Apps– Interact with hundreds of connectors, or custom connectors– Dynamic API development and configuration (drag and drop)– API’s including Cognitive Services
Further into the Future?
Refer video called “Microsoft Power BI Embedded.mp4’
Refer video called ‘Azure Logic Apps Demo.mp4’