These are running in the same process as the repository. ![]() With an SMTP server so the Platform can send emails, such as site invitations.Įxtensions to the repository, such as a domain specific content model, and extensions to the UI, such as forms to supportĬustom types, has traditionally been done with Alfresco Modules Packages (AMP)Īnd later on as JARs. The Platform is usually also integrated with aĭirectory Server (LDAP) to be able to sync users and groups with Content Services. The Search component runs in its own Jetty web application server. Other languages when implementing external extensions. So if you areĪ Java developer you feel quite at home working with Content Services, even through it is possible to work with The Platform and UI components run in the same Apache Tomcat web application server, which is Java based. It gives you full freedom toĭesign a content and process web client supporting exactly the use cases needed by the domain. Most Content Services projects will implement a domain specific web client based on ADF. ![]() There are also mobile clients that will access the content via ReST APIs provided by the platform. The search service functionality is implemented on top of Apache SolrĪnd provides the indexing of all content, which enables powerful search functionality. If you want to extend the Digital Workspace UI JSON files are used. They are also deployed as AMP or JAR modules. The user interfaces makes it easy for users to manage their sites, folders, documents,Īlfresco Share also provides several extension points that can be used to build customizations for that user interface, There is also a newer UI called Digital Workspace,īased on the Alfresco Application Development Framework (ADF), There are several so called extension points thatĬan be used to build customizations for the platform, they are usually deployed as AMP or JAR modules.Īlfresco Share provides a web client interface (that is a User Interface, UI)įor the repository and is implemented as the share.war web application. Traditionally this component is also referred to as the Repository. Repository where content is stored plus all the associated content services, such as classification and versioning. ![]() The main component is called the Platform and is implemented in the alfresco.war web application. These components are implemented as separate web applications: The Platform, the User Interfaces ( UI), and the Search engine. The following diagram illustrates the mainĬomponents that the Content Services consists of. Traditionally there hasĪlways been a few well known components defining Content Services. High-level architectureīefore we get into details, let’s start by looking at Content Services from a high level. This section gives an introduction to the Content Services architecture from a developer’s perspective.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |