ReportServer Forum

kris

Member

Registered: 2020-02-18

Configuring ReportServer schema on another server

To configure a Report Server Enterprise instance so that its ReportServer schema sits in a different (external) location, is it just a matter of updating the persistence.properties file and running the DDL file on the external database.

Also, since we use the provided docker-compose.yml file, we would have to remove the update this file accordingly.

So is this it?
(1) Import or run schema creation on external database
(2) Update the persistence.properties file to use the external database
(3) Change the docker-compose file and/or install without docker

IF_Eduardo

Administrator

Registered: 2016-11-01

Website

Re: Configuring ReportServer schema on another server

Hi kris,

the steps you posted seem correct. Can you please post the exact changes you are making in the docker-compose file ?

Regards,
Eduardo

kris

Member

Registered: 2020-02-18

Re: Configuring ReportServer schema on another server

Our current docker-compose.yml file is similar to what is described here:

https://github.com/bitnami/bitnami-dock … ompose.yml

This has Mariadb and Report Server Enterprise each in a docker on a single server.

I am guessing that if I moved Mariadb one of our managed databases, the docker-compose.yml would look similar to this:

version: '2'

services:
  reportserver:
    image: 'bitnami/reportserver:3'
    environment:
      - MARIADB_HOST=put_server_here.put_domain_here.com
      - MARIADB_PORT_NUMBER=3306
      - REPORTSERVER_DATABASE_USER=bn_reportserver
      - REPORTSERVER_DATABASE_NAME=bitnami_reportserver
    ports:
      - '80:8080'
      - '443:8443'

IF_Eduardo

Administrator

Registered: 2016-11-01

Website

Re: Configuring ReportServer schema on another server

Hi kris,

this configuration seems correct. I haven't tested it yet, though, so it would be nice if you can let us know if the configuration worked.

Regards,
Eduardo