Sunday, February 5, 2012

Business Apps Integration With Document Management

There are many applications in companies that generate or require documents. How can all business applications access and store documents in one place?

When the Yerbabuena's development team undertook the development of Athento, one of the main concerns was that the development of the components were to be made according to standards that facilitate integration with other applications, whether other document management systems (for which it was decided to implement the CMIS standard) or any other applications.

To open the possibility of interconnecting Athento with other systems was the first step, but the second concern was to minimize the need for large developments to achieve the connection with other systems.

When you want to connect a business application with a document management system, companies are forced to change both in the DMS and in the business applications, so as to prepare both ends of the channel to communicate.

The problem of development is not only they are both time and money consuming, but they are also subject to current versions of the systems. A new version of the DMS and the integration ready to connect to the bills application is unusable.

By implementing the CMIS standard, Athento solves part of the problem, the document management system (DMS) end.

Athento integrates with the DMS (may it be Alfresco, Nuxeo, OpenText or any other one that implements CMIS) so changes aren't needed to prepare for communication with applications.

But there is still adjusting the applications (the other end of the communication). At this point, again Athento avoids having to make modifications to the software.

To make this possible, Athento Manager is a layer that manages communication with other applications  and DMS through the implementation of services.

Athento Manager implements outbound services that allow Athento integration with the document repository and the gateway services that help applications access to the documents in the server.

We can understand these services as communication channels between the repository and Athento or Athento and the applications.

Thus, for example, if Athento needs to create folders or documents within Alfresco, it uses its output CMIS connector to create them. And if the application of invoices needs to see a bill from a customer, Athento uses its REST input connector to return a representation of that bill.

The connectors for the applications can be developed by the technical department of the company or by our technicians (Yerbabuena) or anyone who knows how to do it, the important thing here is that we forget to do a development within each new DMS, or each time the repository changes version, or one for each application that needs to access documents.


With these arguments we are relieved to say that Athento is a highly interoperable.

Contact us! We can help you improve your company's document management.
Yerbabuena Software on LinkedIn
Share

No comments:

Post a Comment

AddThis