Enterprise Content Management (ECM) as a component for content management is very useful and easy. It can be used as simple plugin or application to handle the content load without affecting the applications performance. SAP ECM capabilities can be leveraged in many ways such as integration with portal or using it as record management tool. The most efficient way to integrate ECM with any application is by wrapping the APIs of the ECM as Web Services and then consuming these in the application. In this blog I am focusing on some basic advantages which can be achieved by exposing the ECM API as Web Services.
Advantages of using the ECM APIs as Web Services:
Using ECM API as Web Service provides the interoperability across the platform and technologies. We used this approach to consume ECM services from a very basic swing application for one of use cases where a standalone desktop application required to push the containt in ECM. Similarly it can be used from other frameworks and devices as well.
Exposing the ECM API as Web Service makes it compatible with all the available technologies which can consume Web Service irrespective of the programming language and platform. It also helps the applications to achieve the compatibility with sap land scape. Web Service once written can be deployed in different SAP landscape and servers, which makes it easy for application to use any of the available servers without any interface or configuration level change in services or methods. It also helps the existing applications developed in other platform to work closely with SAP systems and to incorporate with the ECM.
Using the ECM API as Web Service provides the flexibility to use the application without coupling the logic specifically written to manage the content in different repository and folder (Content management logic ) with the application logic. It helps the application to loose the coupling between the application logic and content management logic which in result gives the higher degree of sustainability and decrease the maintenance cost.
4. Detachable plugin for content management:
The Web Services can be used to develop the separate plugin application which can be used as a detachable component, one of the example is to develop reusable DC in WebDynpro Java, JSF and Android applications can be developed in a similar way using the services.
Developed Web Services using ECM API can be easily reused with the pre-existing content management logic instead of reinventing the wheel every time in every application. It also gives the freedom to put only additional logic required by application with less effort and time.
It is easy to use the ECM API and expose it as Web Services, code sample can be found in Code Gallery, at Using ECM API as Web Service for Content Management . This sample provides basic methods of manipulating the ECM content which can be enhanced, improved and customized, depending on the requirement very easily.