CXP Manager Graphical user interface for CXP Portal Management Page Management Permissions Definition Users and Group Management Content Items management Auditing Model Inspection Importing and Exporting
CXP Manager: Import/Export Services Archives of Catalog Items are zipped 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
CXP Manager: Versioning Services Navigate across different versions of pages 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
CXP: Integration Services 2 Apache Camel - Java framework for 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
CXP: Integration Services 3 Backbase does not provide any out-of-the-box 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
CXP: Portal Services 1 Main Module in CXP: Persists CXP 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 <=>
CXP: Content Services 1 Stores content items, makes them available to widgets In-Context Editing(ICE) within CXP Manager, Content Services stores and manages content. Can publish packages and supports Versioning. Repositories: Content Repository - for widgets(img, txt) Content Repository Portal Repository Internal Configuration Repository Resources Repository
CXP: Targeting Services 2 1. Portal Services receives client request 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
Launchpad: Component Library Wealth Collection Retail Collection Commercial Collection Each collection has a unique set of Widgets, Features, Containers, Themes, and Templates
Launchpad: Page Custom Properties Use REST API or Explorer app in Portal Manager to add custom properties Added to each item individually or to a master page Pages inherit all properties from parent master page
Launchpad: REST API Contains 40+ APIs with banking, account, and security features DBP Integration includes: End to End Flow Launchpad Integration Services Flow Backbase Integration Bus Flow Session/Login Flow
Forms: Studio 1 Runs on Microsoft Internet Information Server - 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
Forms: Studio 2 Complete revision control Work with external and internal libraries Multilingual elements User and access management Working with multiple projects
Forms: Publisher Stand alone app - retrieve forms from Form 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)
Forms: Runtime 1 Forms Engine - retrieves forms from Forms 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
Forms: Runtime 2 Runs on top of app server Apache Tomcat, JBoss, IBM WebSphere, exposing forms SDK with Forms engine. Web app of Forms Runtime handles web interaction, and supports plug ins
ersin_ertan
yuhattor
shimastripe
tomzoh
junjikoide
th0x0472
line_developers
nozomiito
nagix
n1ru4l
igsr5
mhidaka
mraible
bkeepers
cherdarchuk
bryan
shpigford
jnunemaker
jennybc
danielanewman
colly
bluesmoon
philhawksworth
morganepeng