The table below shows additional details of EcoSys's integration technologies. Each integration method, along with considerations for when to use a specific approach.
Suitable For |
Subject Areas |
Formats |
Flexibility |
||
---|---|---|---|---|---|
ECOSYS ENGINE |
EcoSys Connect |
Middleware platform for integrations |
All |
SOAP, SQL/ODBC Other end points will be added in the future |
All fields, configurable logic, event triggers |
EcoSys Web Service API |
SOA, ESB integration, customer interfaces |
All |
SOAP, REST XML/JSON |
All fields, configurable logic, event triggers |
|
EcoSys OData API |
Reporting, or other integrations |
Cost Object, Transaction, Tasks, Rates, Categories, Currencies, Versions |
OData JSON |
Generic query capabilities following the OData standard |
|
Live Connectors |
Real-time OData queries from external systems |
All |
OData JSON |
Allows querying datasets without saving to EcoSys |
|
Spreadsheet/File Import/Export |
Interactive users, ad-hoc configuration |
All |
Excel or tab- separated flat file |
All fields, configurable logic |
|
Connectors |
Oracle Primavera P6 Connector |
Oracle Primavera integration |
Project, WBS, Activity, Resource Assignment, and all other P6 subject areas |
P6 Web Services API |
Configurable to support any P6 integration use case |
SAP ERP Adapter |
SAP integration |
Cost Object, Transaction |
SAP BAPI |
Native fields, custom fields and categories only |