How to change mysql connector settings for production?

Q&A
1

I have created a connector with mysql to populate a select box in my form. I want to deploy the form to the customer and in order the connector to can work I have to deploy it with different credentials than in my test environment. How is this possible?

2

Somewhere you have to recode the credentials. It’s part of the design process…

In subscription you have parameters that can do this. In community we’ve done it this way:

Create a text file called mySQL.Credentials
Save it to a path in tomcat that is accessible to Bonitasoft
Write a Connector to get the information from the file and save to global variables
the process can then use the variables in the connection string.

regards
Seán

PS: As this reply answers your question, please mark as resolved.

3

Hello, after some research I found that this is possible with parameters in community also. Are you sure that is not possible with community. It seems that is provided

4

Historically we’ve always separated credentials. The biggest problem with parameters is they are process based, you have to define them for each process. We didn’t want that. So we crested our own method such that every process uses one routine to access the credentials.

5

Just to clarify the difference between “parameters” in Community edition and Subscription edition: in Subscription edition you can update parameters value after process deployment (using Bonita Portal administration view) whereas in Community you would have to update the parameters value in Bonita Studio and deploy a new version of the process definition.

6

To clarify on Antoine’s response

…whereas in Community you would have to update the parameters value in Bonitasoft Studio and deploy a new version of the process definition.

If you changed the password to the database and had 10, 20 or 100 processes all using that MySQL database, then you would have to change every process (10, 20 or 100) and redeploy each of them.

Using my method, you just change the password in the credentials file, restart the server (not always necessary, but recommended) and everything just works. No need to redeploy.