containing: CXP Object Model of catalog item in XML Resources: templates, CSS, JavaScript, Media Archives of Portals are zipped containing: CXP Object Model of portal and children in XML CXP Object Model of Portal Catalog Enterprise Catalog items used by portal Content items used by portal Import and Export portals, pages, containers, widgets and other catalog items
and content items. On user publishing request, Publishing Services: Stores published items in Content Services Assigns them a version number Creates a new version even if request is rejected Only available in editorial environments; requires both Content Services, and Publishing Services
routing and mediation to DSL of Fluent API, Spring, Blueprint XML Configuration, Scala DSL. URIs with any transport model: HTTP, ActiveMQ, JMS, JBI, SCA, MINA, CXF, pluggable component and data formats. Bean binding integration with CDI, Spring, Blueprint, Guice Camel Java DSL - maven archetype for integration services Camel Spring XML DSL - maven archetype for integration services Enterprise Integration Patterns
services Integration Services is embedded in Portal Services, but can build a standalone WAR file. Integration Services development uses Maven for project management Developer creates custom integration services for each connection to a remote source. Integration services can be used in widgets
Object Model in database Creates HTML view of CXP OM and returns it to clients Returns CXP OM as XML to clients Implement authentication and authorization and individual objects Integration with other modules to provide content to widgets Accessed via REST, CXP Manager Portal Services Mbeans monitored via JMX <=>
and forwards it to Targeting service 2. Collectors: collect data about the user from external sources, merge them into a user profile, store profile in temp cache 3. Portal Services retrieves the latest user profile related to the request 4. Rules engine evaluates selectors against the user profile. It selects the correct alternative of Targeting Container and returns it to the client. First alternative is always selected, else fallback
Requires .NET on client Saves forms in XML - uses auth. to determine edit/publish permissions Management services via SOAP from Forms Publisher/Forms Runtime Forms Studio interface element uses XBAP technology requiring Internet Explorer Uses client and server layers internally to maintain repository
Studio Publish from Forms Studio to Forms Publisher database Forms Runtime environment can connect to database and publish forms through Forms Publisher client(if is a plug-in of Forms Runtime)
Studio or database and transforms XML to HTML(or more) Transformations to HTML and Vaadin, can create more with XSLT with custom design Custom dashboard to run forms Plug-ins/APIs to extend/customize functionality