EAM enables customers to integrate with both internal and external software solutions used to manage operations. The EAM system architecture provides the framework and integration utilities through which you can exchange, update, and share information between EAM and external software systems.
EAM includes a built-in integration architecture consisting of event tables, drivers, import/export triggers, code, XML (Extensible Markup Language) documents, and an Integration Server. To implement, the customer must synchronize their shared data and map the data between the XML documents, EAM, and external software applications. XML is a programming language used to identify structures in a document. For EAM, a document is a logical grouping of data sent to and from EAM to facilitate data exchange between systems. EAM uses XML as part of this internal integration process. For outbound transactions, EAM data is converted into XML documents. The reverse is true for inbound transactions, where the XML document content is converted into EAM data.
EAM also has an evolving library of REST APIs that parallel the features and functionality of EAM. REST API support of features and functionality across all of EAM will be expanded with each release. EAM additionally has an extensive library of SOAP web service WSDLs able to perform any discrete action supported by EAM. All of these web services are compatible with any enterprise integration platform. Integration using web services requires the customer to map the API elements between solutions.
Before implementation of EAM, the customer should consider the business transactions to be integrated and understand the integration concepts for synchronizing data between EAM, other external software applications, and the selected integration platform.