This chapter contains all changes made in Release 7.5.7 of CoreMedia Digital Experience Platform 8.
Release 7.5.7 contains the following CoreMedia modules:
CoreMedia Blueprint
CoreMedia CMS
CoreMedia Studio
CoreMedia LiveContext for IBM WebSphere Commerce
CoreMedia Elastic Social
In addition, CoreMedia DXP 8 uses the following tooling:
| Product | Key | Version |
|---|---|---|
| CoreMedia Application Maven Plug-in | APPPLUGIN | 2.7.5 |
| CoreMedia Project Maven Extension | PROJEXT | 1.0.5 |
Table 2.48. Tooling of CoreMedia DXP 8
CoreMedia CMS Improvements
Changes
Apache Solr has been updated to version 4.7.2.
The TenantFilter Servlet Filter previously extracted a "tenant hint" (e.g. "media") from the host name of the request (e.g. media.mysite.com) and matched this against a map from hints to tenant names (e.g. "media" -> "tenant name") within the Spring configuration.
This behavior has been changed in order to support the new CoreMedia Blueprint multi-site features. The Elastic Social tenant is now read from the Site configuration, where the Site for a request is determined from the request URL path (e.g. "/blueprint/servlet/perfectchef/en/us" -> Site PerfectChef, en/us locale). New tenants for new sites can now be added without redeployment of any CAE and without adding DNS entries for sub-domains.
The filter operates only on dynamic, non-cacheable fragment requests, e.g. those with the "/dynamic/*" prefix. All other requests might be cached by a CDN, they should not depend on a particular Elastic Social user.
CoreMedia LiveContext for IBM WebSphere Commerce Improvements
There is a new CMS document type e-Marketing Spot that can be used to represent an IBM WCS e-Marketing Spot within a content area. The e-Marketing Spot data will be requested from the IBM WCS and rendered by the CoreMedia CAE. In CoreMedia Studio within the Library Catalog Mode it is possible to choose an IBM WCS e-Marketing Spot and assign it to the CMS document.
CMS content can be made available and searchable through the IBM WCS search. The IBM WCS crawling mechanism can include a specialized side map generated by the CMS to fill the IBM WCS search index.
There is a service in CoreMedia DXP 8 that can be used to request search term proposals to render a search field with auto-suggestion on CMS side. This function is integrated into the default CoreMedia DXP 8 Search. The actual search is will be performed by the IBM WCS. It will be forwarded to the IBM WCS to render the result page.
Closed JIRA Issues
 |  |  |
 |