I have been running this solution in Servoy 3.1 on Oracle XE and just tried to upgrade to Servoy 3.5. Oracle XE allows only a single data base, named ‘XE’. In 3.1, this was fine. I created Servoy DB Servers named repository_server and mediadb, both pointing to the same URL, same username and password. In 3.5 when I try to create the second DB Server, I get the error: com.servoy.j2db.persistence.RepositoryException: Server with these connection details already exists: mediadb
Is there a way to work around this?
The reason why it’s not allowed to have multiple Servoy Servers pointing to the same physical database is because Servoy’s databroadcasting mechanism is Server based. So, if you would access the same record through 2 different servers and through one server you update the record, the same record accessed through the other server is not updated automatically.
Since all the data is in one database anyway, I suggest you only use 1 Server Server, instead of three.
Paul
It is not really “best practice” to put the repository and a data connection into the same schema or database. Why don’t you create a new user (schema) for the repository?