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:
-Dpublisher.home=C:/publisher_6_home
-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.x | Publisher 7.0 | Notes |
---|---|---|
N/A | logging.config | Publisher 6.x always looks for a logback.xml in the publisher.home |
N/A | logging.file.name | Publisher 6.x by default logs to publisher.home/publisher.log |
N/A | blueriq.properties.encryption.password | Publisher 6.x always uses a fixed key to encrypt (password) properties |
oauth2.client-id | blueriq.publisher.rest.v1.oauth2.client-id | |
oauth2.secret | blueriq.publisher.rest.v1.oauth2.secret | |
studio.url | blueriq.publisher.studio.url | |
studio.authentication | blueriq.publisher.studio.authentication | |
hibernate.* | blueriq.publisher.hibernate.* | |
publisher.datasource.url | blueriq.publisher.datasource.url | |
publisher.datasource.driverclassname | blueriq.publisher.datasource.driverclassname | |
publisher.datasource.username | blueriq.publisher.datasource.username | |
publisher.datasource.password | blueriq.publisher.datasource.password | |
N/A | blueriq.publisher.datasource.hibernate.* | Publisher 6.x only supports global Hibernate properties |
database.DB_ENV_NAME.url | blueriq.publisher.env.database.DB_ENV_NAME.url | |
database.DB_ENV_NAME.driverclassname | blueriq.publisher.env.database.DB_ENV_NAME.driverclassname | Publisher 7.0 also supports org.postgresql.Driver as a value |
database.DB_ENV_NAME.username | blueriq.publisher.env.database.DB_ENV_NAME.username | |
database.DB_ENV_NAME.password | blueriq.publisher.env.database.DB_ENV_NAME.password | |
database.DB_ENV_NAME.sortvalue | blueriq.publisher.env.database.DB_ENV_NAME.sortvalue | |
database.DB_ENV_NAME.uncommitted_allowed | blueriq.publisher.env.database.DB_ENV_NAME.uncommittedAllowed | |
database.DB_ENV_NAME.requires_approval | blueriq.publisher.env.database.DB_ENV_NAME.requiresApproval | |
N/A | blueriq.publisher.env.database.ENV_NAME.hibernate.* | Publisher 6.x only supports global Hibernate properties |
artifactory.ARTI_ENV_NAME.url | blueriq.publisher.env.artifactory.ARTI_ENV_NAME.url | |
artifactory.ARTI_ENV_NAME.repository | blueriq.publisher.env.artifactory.ARTI_ENV_NAME.repository | |
artifactory.ARTI_ENV_NAME.username | blueriq.publisher.env.artifactory.ARTI_ENV_NAME.username | |
artifactory.ARTI_ENV_NAME.password | blueriq.publisher.env.artifactory.ARTI_ENV_NAME.password | |
artifactory.ARTI_ENV_NAME.sortvalue | blueriq.publisher.env.artifactory.ARTI_ENV_NAME.sortvalue | |
artifactory.ARTI_ENV_NAME.uncommitted_allowed | blueriq.publisher.env.artifactory.ARTI_ENV_NAME.uncommittedAllowed | |
artifactory.ARTI_ENV_NAME.requires_approval | blueriq.publisher.env.artifactory.ARTI_ENV_NAME.requiresApproval | |
transition.TRANSITION_NAME.from | blueriq.publisher.env.transition.TRANSITION_NAME.from | |
transition.TRANSITION_NAME.to | blueriq.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 inpublisher.properties
, removepublisher.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