2. MSFT SharePoint depends on data integration
o Microsoft Exchange Integration
o DMS Functionality from other systems like
CRM
o On-premise to Online migration
o Multiple side sync with business rules (e.g.
private and public site info based on business
rules)
o Salesforce.com to SharePoint
o Dropbox, Evernote and Oracle Products
(Siebel, JD Edwards, PeopleSoft to SP)
o SP 2013 / 2010 and o365 Sync, Migration and
Integration or Coexistence
o Mobile solutions for SharePoint
• No share
• No interaction
• No sync
• No exchange
• No collaboration
• NO SharePoint
2
3. SharePoint integration work is ……..
Market Validation
…time consuming
Need to learn target systems
/interfaces
…risky
Damage to sensitive data
…complex
Capacity demand difficult to
estimate
…costly
* Forrester study “The Hybrid² Integration Challenge“, May 2013
Manual deep drilling into
Infrastructure
3
4. The current integration tool landscape is too
heterogeneous*
* Forrester released the study
“The Hybrid² Integration
Challenge“ in May 2013.
The key takeaways:
o Digital business design is
too challenging for today’s
integration tools
o Forrester sees two key
challenges in orchestrating
an integration landscape:
1) the interoperability of
different integration
technologies;
2) the consistent federation
of on premises integration
technologies with a cloudbased integration approach.
4
5. Current market landscape for integration
tools does only partially meet the needs
Custom code
Workflow engines
Manually coded interfaces
K2, Nintex, Scribe, Mulesoft, et al
Developers code interfaces manually
Code-free
Pre-defined integration workflows
Certification necessary
o
HIGH Implementation Cost
o
HIGH License Cost
o
HIGH Levels of Flexibility
o
MEDIUM Levels of Flexibility
o
SLOW(ER) Time to Market
o
FAST(ER) Time to Market
o
HIGH Levels of Risk
o
MEDIUM Levels of Risk
o
HIGH Software Compatibility
o
LOW Software Compatibility
o
UNIQUE Solutions YES
o
UNIQUE Solutions NO
5
6. The Connect Bridge SQL Syntax command platform
reduces necessary time, money and risk. Significantly.
JDBC
ODBC
Web Services
ANY
Software
Client layer
o Connect Any Software:
Our JDBC / ODBC / Web
Services drivers integrate
any software written within
the last 20 years
o The coder stays in his
own code – no need to
learn other code and
interfaces
SQL Syntax
Query analyzer
Server layer
SP Connector / layer
o Help Tool: Query Analyzer will
test a SQL Query in real time
o Connect Bridge connects via
SP standard API
o No need to compile / test /
decompile & start again
o No corruption of data base
o Less code lines
less risk
o Any developer can work with it
less dependent on resources
o Data base structure is parsed
into Query Analyzer – works
like a navigation system for
the developer
6
7. Query Analyzer Help Tool – The Simplifier
o
o
o
If the the result is ok
just
copy and paste the SQL
statement into your code.
DONE.
Modeled after the SQL
Management Studio it
allows to test SQL codes
against all connected target
servers, inspect logs and
errors and learn about the
exposed entities and
properties.
With simple SQL statements
the code can be tested.
o
Our Help Tool enables the
developer / integrator to
become immediately
effective.
7
7
8. Connect Bridge combines the advantages of
conventional methodologies plus saves time & money
Custom code
Manually coded interfaces
Developers code interfaces
Dependency on coders
Connect Bridge
SQL Syntax based tool used
by IT professionals
Workflow engines
K2, Nintex, Scribe, et al
Code-free
Pre-defined integration workflows
Certification necessary
o HIGH Implementation Cost
o LOW Cost
o HIGH License Cost
o HIGH Levels of Flexibility
o HIGH Flexibility
o MED Levels of Flexibility
o SLOW Time to Market
o HIGH Levels of Risk
o HIGH Software
o FAST(ER) Time to Market
o FAST Time to Market
o MEDIUM Levels of Risk
o LOW Levels of Risk
o LOW Software
o HIGH Software Compatibility
Compatibility
o UNIQUE Solutions YES
Compatibility
o UNIQUE Solutions YES
>50% savings of time and money
o UNIQUE Solutions NO
|
Immediate ROI