Page History

...

Table of Contents

maxLevel	2

Upgrading to GX WebManager 10.22.0 XperienCentral or newer
---------------------------------------------------------------------------------------------------
- The dependencymanager compat 3.0.0 has been removed from XperienCentral and the dependencymanager
itself has been upgraded to version 4.11. All implementations of package
'org.apache.felix.dependencymanager' must be refactored/renamed to package 'org.apache.felix.dm'.
The 'createService' method is no longer available and must be renamed to 'createComponent'.
Some other refactoring may be required for certain implementations.
- The formvalidation.js file in the wmpformpresentation plugin has been changed and needs to be
updated when overruled in a custom presentation.

Upgrading to GX WebManager 10.21.1 XperienCentral or newer

---------------------------------------------------------------------------------------------------

- A problem has been fixed that caused deleted elements to not be completely removed which resulted

in excessive space being taken up in the database. After upgrading and starting up XperienCentral

for the first time, a task is executed that removes these deleted elements - in some environments,

this could take some time to complete.

...

XperienCentral 10.22.0

- The dependencymanager compat 3.0.0 has been removed from XperienCentral and the dependencymanager
itself has been upgraded to version 4.11. All implementations of package
'org.apache.felix.dependencymanager' must be refactored/renamed to package 'org.apache.felix.dm'.
The 'createService' method is no longer available and must be renamed to 'createComponent'.
Some other refactoring may be required for certain implementations.

- The formvalidation.js file in the wmpformpresentation plugin has been changed and needs to be
updated when overruled in a custom presentation.

...

XperienCentral 10.21.1

- A problem has been fixed that caused deleted elements to not be completely removed which resulted

in excessive space being taken up in the database. After upgrading and starting up XperienCentral

for the first time, a task is executed that removes these deleted elements - in some environments,

this could take some time to complete.

...

XperienCentral 10.18.0

- After upgrading to XperienCentral 10.18 and higher, a list can only have one personalization applied
to it - individual items in a list cannot be separately personalized. If a list has more than one
personalization applied to it before the upgrade, the first one encountered is applied to the whole
list and the others are removed.
In an upgrade situation, a list personalization is applied only after the first time the content item
on which it appears is edited and saved. This applies to the frontend as well. This is done in order
to make personalizations work consistently.
- Logging has been added for several authentication and other sensitive events (logging in,
changing a user's persmissions, etc.). To store this logging in a separate logging file on the
server, some additions must be added to the logging.properties file. Be
sure to shut down the server before applying these changes.

- The first line defines the so-called logging handlers that are used. This should be extended with
    a new handler. The new line must be:

      handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler,
        3manager.org.apache.juli.FileHandler, 4host-manager.org.apache.juli.FileHandler,
        5gxsecuritylogging.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler

    where "5gxsecuritylogging.org.apache.juli.FileHandler" is the new handler. Do not
    add the handler to the line ".handlers". Note that all sensitive events are logged at
    the INFO level.

- Add the definition for the new handler at the bottom of the file as follows:

      5gxsecuritylogging.org.apache.juli.FileHandler.level = INFO
      5gxsecuritylogging.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
      5gxsecuritylogging.org.apache.juli.FileHandler.prefix = audit.
      nl.gx.webmanager.services.securitylogging.level=INFO
      nl.gx.webmanager.services.securitylogging.handlers=5gxsecuritylogging.org.apache.juli.FileHandler

- After these changes are applied, restart the server. A clean log file is
    initialized in the Tomcat "logs" directory, prefixed with "audit".

- For other application servers, please consult their documentation for information on how
    to configure a separate log file.

-   A problem has been fixed that caused added database references to be incorrectly stored in XC.
    The fix will only ensure that future references are correct, not existing ones.
    If you refer to database items within media items, you must manually remove the
    <webmanager-root>/work/contentindex directory after the upgrade and allow it to be regenerated
    (selecting "contentindex_queue_empty_reindex" in the Setup Tool is not sufficent).

...

XperienCentral 10.17.0

- Apache Tomcat 8.5.14 has been integrated

For Apache Tomcat the server.xml has changed:

<Resource name="jdbc/WebManagerDb" auth="Container" type="javax.sql.DataSource"

username="${webmanager.externaldb.dbuser}" password="${webmanager.externaldb.dbpassword}"

driverClassName="${webmanager.externaldb.dbdriver}" url="${webmanager.externaldb.dburl}"

maxTotal="100" maxIdle="10" maxWait="10000" testWhileIdle="true"

timeBetweenEvictionRunsMillis="900000" removeAbandonedOnBorrow="false"

removeAbandonedOnMaintenance="false" removeAbandonedTimeout="30"

logAbandoned="true" validationQuery="${webmanager.externaldb.validationquery}"/>

The way abandoned connection management should be handled by Tomcat has changed.

For Apache Tomcat the context.xml has changed:

CookieProcessor is set to "org.apache.tomcat.util.http.LegacyCookieProcessor".

Startup configuration for Apache Tomcat has changed:

JVM configuration settings (described in settings.xml) formerly added to

catalina.bat/catalina.sh are now located in setenv.bat/setenv.sh. The settings themselves are

split into two categories (instead of one): catalinaopts and javaopts.

- The manner in which horizontal page text is aligned in the Inline Editor has changed.

In XperienCentral versions older than 10.17.0, the align attribute was used inside <p> tags,

<h1> through <h6>, and block-quote elements. Horizontal page text is now rendered using an

'aligncenter' or 'alignright' parameter in a CSS horizontal text-alignment class element. The CSS

of the customer website must now include these class definitions. See stylesheet.css in the

webmanager-cestyle-wcb for an example.

- The Image Element presentation, imageElement.xml, has three new properties "enableResize",

"resizeHeight" and "resizeWidth".

...

XperienCentral 10.16.1

- Adjust presentations where the <img>-tag width and height attributes are set, to support

SVG-images without explicit dimensions. See for example imageElement.jspf (line 36).

...

XperienCentral 10.16.0

Upgrading to GX WebManager 10.17.0 XperienCentral or newer