You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
Table of contents
Description
This component is used to view and start projects that have been published to this environment by the Publisher. The published projects are shown in the dashboard of the development plugin. When the server is started, the Publisher clients creates a datasource for the database, containing the published projects. A task runs in the background that checks periodically (by default every 60 seconds) whether projects are updated, added, or deleted. When there is a change, the datasource is reloaded, so that the new projects can be started.
Requirements
The "publisher-client" and the "externaldatasources" or "jndidatasources" profile must be enabled.
Installation
In order to use this component, the publisher-client and either externaldatasources or jndidatasources profile must be active. More information on how to configure the application using Spring Profiles can be found here : Application configuration with Spring Profiles.
Configuration
The application-publisher-client.properties contains the configuration of the database that the plugin connects to. When you have configured an environment for the Publisher, you can copy the database configuration for this environment.
#blueriq.publisher-client.environmentName: The name of the environment (required). This should be the same name as the name of the database in the Publisher configuration. #blueriq.datasource.publisher-client.url=The URL on which to locate the database to connect to. #blueriq.datasource.publisher-client.username=The username to use to connect to the database. #blueriq.datasource.publisher-client.password=The password to use to connect to the database. #blueriq.datasource.publisher-client.driverClassName=The vendor specific database driver classname. #blueriq.hibernate.publisher-client.dialect=The hibernate dialect that should be used. This should correspond to the driverClassName you specified above/ #EXAMPLE blueriq.publisher-client.environmentName=Dev blueriq.datasource.publisher-client.url=jdbc:oracle:thin:@DB_HOST:1521:xe blueriq.datasource.publisher-client.username=TheKey blueriq.datasource.publisher-client.password=TheSecret blueriq.datasource.publisher-client.driverClassName=oracle.jdbc.driver.OracleDriver blueriq.hibernate.publisher-client.hbm2ddl.auto=none blueriq.hibernate.publisher-client.dialect=org.hibernate.dialect.Oracle10gDialect
Supported hbm2ddl.auto values:
- none
- validate (only in combination with Publisher 4.0.0 and up in combination with Blueriq 10 or higher)
For JNDI configuration the jndidatasources profile has to be enabled, and the the application-publisher-client.properties should contain the following settings:
#EXAMPLE blueriq.publisher-client.environmentName=Dev blueriq.hibernate.publisher-client.hbm2ddl.auto=none blueriq.hibernate.publisher-client.dialect=org.hibernate.dialect.SQLServer2012Dialect blueriq.datasource.publisher-client.jndiName=java:/comp/env/jdbc/publisher
Database
This component uses the database created by the Publisher.
Usage
Java
The publisher client will add a "Publisher Database" section to the "Start Flow" widget in the development dashboard. Here all the published projects will be listed. These projects can be used like any other project (eg. from Studio or from an Export).
Overview
Content Tools