plexiti / camunda-grails-plugin

Integrates Camunda BPM with the Grails framework.
http://grails.org/plugin/camunda
Apache License 2.0
18 stars 8 forks source link

Update db schema in production #20

Closed Manas101 closed 10 years ago

Manas101 commented 10 years ago

Hi, I generated a standard app.war file with settings in DataSource.groovy: production { dataSource { pooled = true dbCreate = "update" url = "jdbc:mysql://server/db" driverClassName = "com.mysql.jdbc.Driver" username = "user" password = "password" } dataSource_camunda { pooled = true dbCreate = "update" url = "jdbc:mysql://server/db_camunda" driverClassName = "com.mysql.jdbc.Driver" username = "user" password = "password" } }

Config.groovy: environments { production { grails.logging.jul.usebridge = false . .

    camunda {
        engine {
            configuration {
                dataSource = "dataSource_camunda"
                jobExecutorActivate = true
            }
        }
    }
}

The problem is, that the first start of application doesn't create a schema in camunda db. If I try the same config in development environment, schema is on the same server created/updated successfully. The problem is just in production environment.

Any ideas? Have you tried example and tested in production environment?

Thanks a lot.

Jiri Sojka

martinschimak commented 10 years ago

Hi Jiri,

Actually I consider this to be a "feature". ;-)

Please read carefully http://plexiti.github.io/camunda-grails-plugin/guide/usage.html#process-engine-configuration.

The background: for higher security and full control over what happens, you need to explicitely configure some things for production environments, which are taken care of for you in grails test and development environments.

Does this help?

Manas101 commented 10 years ago

Hi Martin,

thanks a lot. I haven't read this article.. it works :)

Best regards Jiri Sojka

On 7 August 2014 13:16, Martin Schimak notifications@github.com wrote:

Hi Jiri,

Actually I consider this to be a "feature". ;-)

Please read carefully http://plexiti.github.io/camunda-grails-plugin/guide/usage.html#process-engine-configuration.

The background: for higher security and full control over what happens, you need to explicitely configure some things for production environments, which are taken care of for you in grails test and development environments.

Does this help?

— Reply to this email directly or view it on GitHub https://github.com/plexiti/camunda-grails-plugin/issues/20#issuecomment-51458874 .

S pozdravem Ing. Jiří Sojka