Page 1 of 1
store data source definitions in a project?
Posted: Thu Dec 04, 2014 12:15 am
by Ron Van den Branden
Hi,
I have defined some eXist database connections in my project and would like to share them with other team members, so they don't have to define them themselves. Is this possible? I couldn't find any trace of data source definitions in the project XPR file I'm editing. Is there perhaps another export/import mechanism for data source definitions?
Best,
Ron
Re: store data source definitions in a project?
Posted: Thu Dec 04, 2014 4:00 pm
by adrian
Hi,
Unfortunately database data sources and connections are not kept in the project for a number of reasons (dependence on drivers/libraries, authentication information). We have a request logged for this on our issue tracking tool, but this will be considered in the long term.
Exporting/Importing the global options as a whole is an alternative (
Options > Export/Import Global Options), but note that the database connection passwords are encrypted with a key bound to the current user, so if a different user imports the options file, the passwords are lost.
Also, this does not account for the required data source drivers (.jar libraries).
For eXist it would probably be simpler to provide a step by step procedure for your team members on how to configure this.
Oxygen provides exclusively for eXist-db a connection creation wizard (
Options > Preferences, Data Sources, Create eXist-db XML connection) that automatically downloads the required .jar drivers and configures the data source and connection. All you need to provide is the host name (or ip), port, user and password. However, this wizard depends on the existence of the JavaWebStart eXist Admin Client on the server side (<host>:<port>/exist/webstart/exist.jnlp and the .jars the jnlp refers):
Oxygen XML Editor User Manual - The Create eXist-db XML connection Dialog
Regards,
Adrian
Re: store data source definitions in a project?
Posted: Wed Dec 10, 2014 6:23 pm
by Ron Van den Branden
Hi Adrian,
I've experimented a bit further, and this seems a possible scenario:
[1] export global options
[2] isolate "stored sessions" (database.stored.sessions1)
(I'm defining a scenario for a shared database account for all project members, so username and passwords shouldn't be a problem)
[3] instruct project members how to:
[3.1] import global options
[3.2] define an eXist database connection with the connection creation wizard
Many thanks for your helpful thoughts!
Best,
Ron
Re: store data source definitions in a project?
Posted: Tue Dec 23, 2014 12:54 pm
by Radu
Hi Ron,
This seems to work as long as everybody enters his user-password credentials in the already defined connection.
Regards,
Radu