CoreMedia DXP Release Notes, Version 7.5.44-17
2.2. Improvements and Changes | 2.2.33. Release 7.5.12

The CAE Feeder configuration property applicationname has changed from value proactiveengine to caefeeder (fixes bug CMS-1436). Because of this you must execute the following SQL statement before starting the CAE Feeder with a database that was created by an earlier version. No action is necessary when the CAE Feeder is started with an empty database.

UPDATE pcproperties
SET content = 'caefeeder'
WHERE property = 'com.coremedia.amaro.persistentcache.propertystore.PropertyVerifier-application';

The type of some database columns or database sequences used by Proactive Engine and CAE Feeder applications has changed from INT to BIGINT for MySQL, IBM DB2 and Microsoft SQL Server databases. PostgreSQL and Oracle databases are not affected. Have a look at the Supported Environments manual for supported databases.

This change avoids future database errors with long running applications and high update frequency (fixes bug CMS-1505).

The change is automatically applied when the Proactive Engine or CAE Feeder application is started with an empty database. Existing databases continue to work with this release but we recommend to adapt the database definitions to avoid future problems. To this end, shut down the Proactive Engine or CAE Feeder application and execute the following SQL statements - depending on the type of database:

For MySQL:

ALTER TABLE ppckeys
CHANGE COLUMN validated validated BIGINT DEFAULT 0,
CHANGE COLUMN removed removed BIGINT DEFAULT 0,
CHANGE COLUMN lastmodified lastmodified BIGINT NOT NULL;

ALTER TABLE ppcevents
CHANGE COLUMN acknowledged acknowledged BIGINT DEFAULT 0;

For IBM DB2:

SELECT max(lastmodified)+1 FROM ppckeys;

DROP SEQUENCE s_ppckeys_lastmodified;

-- replace <next value> with the result of the first statement
CREATE SEQUENCE s_ppckeys_lastmodified AS BIGINT ORDER START WITH <next value>;

For Microsoft SQL Server:

The columns validated, removed, lastmodified of table ppckeys and the column acknowledged of table ppcevents should be changed from data type INT to BIGINT. Sadly we cannot provide simple ALTER TABLE statements because column type changes are not possible with existing column constraints such as default values.

Alternatively you can either start with an empty database to create new tables with BIGINT columns or just keep the current database schema. You will not run into problems with the existing INT columns as long as the value of select max(lastmodified) from ppckeys is much smaller than 2147483647.

When starting a Publication or Translation Workflow, users can now chose whether the content items should be removed from "My Edited Content". This allows to use the same My Edited Content set for publication as well as translation. It also supports scenarios with an unpublished master site.

Content items are no longer automatically removed from "My Edited Content" when they reach the published state through other means.

The deprecated class com.coremedia.rest.cap.blob.BlobUploadService has been removed. Use HTML5 FormData object on client side and Jersey's FormDataParam on server side instead.

User Segments and Marketing Spots supporting Studio Event Push on invalidation. Please note to install the associated database trigger on your IBM WCS Installation. For details see the section Event based Cache Invaldidation in the [Live Context Manual].

Store Configuration can be configured in Spring or via settings configuration in Studio. Store Configuration via Spring for better support of multi environment deployment scenarios. For details see the section Configuration of an IBM WCS Shop in the [Live Context Manual].

Tenant specific property replacement to replace placeholder tokens within your configured store urls etc. with values defined in the current StoreContext at runtime. For details see the section Configuration of an IBM WCS Shop in the [Live Context Manual].

Uploading XLIFF files via Create content / Upload files fails. There is no workaround.

Current release is limited to English edition of Perfect Chef only. There is no alternative language version of Perfect Chef available in WCS. Workaround is not yet available.

The redirect that is executed after a successful registration is broken. To fix it manually, replace the redirect variable in line 17 of the template "Registration.continueCheckout.ftl" with the following URL: https://your.websphere.commerce.domain/webapp/wcs/stores/servlet/OrderShippingBillingView?shipmentType=single&catalogId=10051&langId=-1&storeId=10851. Make sure that you apply the correct store and catalog id.