Overview

  • The contents of the Swagger/OpenAPI API description has slightly changed.
  • The property encryption mechanism has changed.
  • Some new properties where introduced and existing properties where renamed.

On this page:

Swagger 2.0 to OpenAPI 3.0

For the Publisher REST API an OpenAPI 3.0 API description is available at the /api-docs endpoint. The Swagger UI is no longer included in the Publisher, use a tool like https://editor.swagger.io/ to work with the new API description.

Spring Boot and Spring Cloud

The biggest (technical) change for Publisher 7.0, is the introduction of Spring Boot and Spring Cloud. Because of this publisher.home has been replaced by spring.config.additional-location. As an example:

Publisher 6 (and before)
-Dpublisher.home=C:/publisher_6_home
Publisher 7
-Dspring.config.additional-location=file:///C:/publisher_7_config_location/

Property encryption

Encryption of password properties is no longer performed during Publisher startup. Instead all (not only password) properties can now be encrypted with the Blueriq Encryptor, read Property encryption for more information.

The old _-_encryptedValue_-_ format of encrypted password values is no longer supported

Logging

Publisher 7.0 no longer logs to a file by default, to enable this set the logging.file.name property. To point to a custom logging configuration file (logback-spring.xml), set the logging.config property.

Changed property names

To be more in line with other Blueriq products, the property names have been changed:

Publisher 6.xPublisher 7.0Notes
N/Alogging.configPublisher 6.x always looks for a logback.xml in the publisher.home
N/Alogging.file.namePublisher 6.x by default logs to publisher.home/publisher.log
N/Ablueriq.properties.encryption.passwordPublisher 6.x always uses a fixed key to encrypt (password) properties
oauth2.client-idblueriq.publisher.rest.v1.oauth2.client-id
oauth2.secretblueriq.publisher.rest.v1.oauth2.secret
studio.urlblueriq.publisher.studio.url
studio.authenticationblueriq.publisher.studio.authentication
hibernate.*blueriq.publisher.hibernate.*
publisher.datasource.urlblueriq.publisher.datasource.url
publisher.datasource.driverclassnameblueriq.publisher.datasource.driverclassname
publisher.datasource.usernameblueriq.publisher.datasource.username
publisher.datasource.passwordblueriq.publisher.datasource.password
N/Ablueriq.publisher.datasource.hibernate.*Publisher 6.x only supports global Hibernate properties
database.DB_ENV_NAME.urlblueriq.publisher.env.database.DB_ENV_NAME.url
database.DB_ENV_NAME.driverclassnameblueriq.publisher.env.database.DB_ENV_NAME.driverclassnamePublisher 7.0 also supports org.postgresql.Driver as a value
database.DB_ENV_NAME.usernameblueriq.publisher.env.database.DB_ENV_NAME.username
database.DB_ENV_NAME.passwordblueriq.publisher.env.database.DB_ENV_NAME.password
database.DB_ENV_NAME.sortvalueblueriq.publisher.env.database.DB_ENV_NAME.sortvalue
database.DB_ENV_NAME.uncommitted_allowedblueriq.publisher.env.database.DB_ENV_NAME.uncommittedAllowed
database.DB_ENV_NAME.requires_approvalblueriq.publisher.env.database.DB_ENV_NAME.requiresApproval
N/Ablueriq.publisher.env.database.ENV_NAME.hibernate.*Publisher 6.x only supports global Hibernate properties
artifactory.ARTI_ENV_NAME.urlblueriq.publisher.env.artifactory.ARTI_ENV_NAME.url
artifactory.ARTI_ENV_NAME.repositoryblueriq.publisher.env.artifactory.ARTI_ENV_NAME.repository
artifactory.ARTI_ENV_NAME.usernameblueriq.publisher.env.artifactory.ARTI_ENV_NAME.username
artifactory.ARTI_ENV_NAME.passwordblueriq.publisher.env.artifactory.ARTI_ENV_NAME.password
artifactory.ARTI_ENV_NAME.sortvalueblueriq.publisher.env.artifactory.ARTI_ENV_NAME.sortvalue
artifactory.ARTI_ENV_NAME.uncommitted_allowedblueriq.publisher.env.artifactory.ARTI_ENV_NAME.uncommittedAllowed
artifactory.ARTI_ENV_NAME.requires_approvalblueriq.publisher.env.artifactory.ARTI_ENV_NAME.requiresApproval
transition.TRANSITION_NAME.fromblueriq.publisher.env.transition.TRANSITION_NAME.from
transition.TRANSITION_NAME.toblueriq.publisher.env.transition.TRANSITION_NAME.to

Hibernate settings

  • Publisher 6.x (and before) uses a separate file (publisher.hibernate.properties), for Publisher 7.0 all Hibernate settings can be placed in publisher.properties, remove publisher.hibernate.properties.
  • Publisher 6.x has only global settings, Publisher 7.0 has global and specific Hibernate settings.
  • You should remove all hibernate.dialect properties, this is no longer needed.

PostgreSQL support

To use a PostgreSQL database, simply set driverClassname to org.postgresql.Driver and set the correct JDBC url.

Be aware that a critical bug regarding PostgreSQL in the Publisher client was fixed in Blueriq Runtime 16.7.0


Changes in third-party libraries

Please take a look at the Blueriq Publisher 7 libraries