I am trying to update existing orbeon installation with nightly build and use the existing MYSQL database, but the new version is not letting me connect to mysql databse. It is defaulted to eXist database.
I set the property oxf.fr.persistence.service.mysql.datasource to mysql:
<property as="xs:anyURI" name="oxf.fr.persistence.service.mysql.datasource" value="mysql"/>
but no use.
can some one please help me with this connection issue.
The way you configure which persistence layer to use changed after the 3.9 release to give you more flexibility, specifically to allow you to have different apps stored in different schemas of the same database. So most likely, you'll just need to change your properties in properties-local.xml. For more about this change, see Form Runner persistence layer configuration.
Related
SCDF project creates tables/sequences on the fly while starting the application. but our database is in shared environment, it doesn't have any create table permission. Is it possible to create tables/indices/sequences well before that are needed for Spring Cloud Data Flow project to run ?. if you have any SQL scripts, please provide me the link ?..
The SCDF and Skipper rely on Flyway for database schema migration between the releases. It is a strict requirement, so, unfortunately, there's no way around it right now.
You could work around this situation by letting Flyway create all the required schemas automatically in either dev/staging like environments and then manually you could export the schema/data using the approved database tooling to the other environments that have restricted access.
Once when the tables/data exists, Flyway wouldn't interfere or reattempt to create the schemas when SCDF bootstraps. I hope this helps.
I currently have a TFS 2018 server installation using SQL Server 2017. I'd like to install Azure Devops on a new server but use the same SQL Server.
My plan was to restore the existing Tfs_Configureation and Tfs_Collecton databases as new databases and use them.
However in the installation wizard, I am allowed to pick the configuration database that is to be used but I suspect the collection database will be the current live one.
Is there a support way of altering the collection database inside of the configuration database?
I've found a table called tbl_Database that holds the name and connection strings but am not sure if changing these is enough.
I've found a table called tbl_Database that holds the name and connection strings but am not sure if changing these is enough. I don't want to end up prematurely upgrading the current live collection.
I don't want to end up prematurely upgrading the current live collection and don't want to set up a temporary SQL instance just to test the migration.
Is there any way to restore data from neo4j?
I just lost all data and want to restore to previous state of neo4j.
Please help me with this.
Neo4J Server must be configured to run backups. If your server wasn't configured to create backups, then there is not a way to restore your data using Neo4J. This is controlled by the Neo4J config option online_backup_enabled.
This feature is enabled by default in Neo4J 2.1.6 Enterprise. However, you have to manually run a backup in order for one to be created. So, unless you ran a backup, then you aren't going to find one which was automatically taken anywhere on your system. Sorry :-(
In the future, you can configure and run backups following the Neo4J documentation.
I'm currently working with the Grails tool suit with eclipse. I created an an application, defined a domain class and my app works great. My question is, when I deploy my war file how is the database stored? Do I link my data source file to an sql database url. If so upon running my app the first time does Grails create the database for you? You probably understand my question by now. How does this work?
I've looked at this documentation and cant find how grails goes about with creating the database I defined.
http://grails.org/doc/latest/guide/conf.html#dataSourcesAndEnvironments
First off, with the exception of H2 Grails does not setup your database. You will need to setup the database, and configure your datasource to connect to the database.
That said, Grails will manage (as best it can) the schema for your database based upon your Domain classes. This is the default behavior when dbCreate is set to "update" in your DataSource.groovy file.
I would recommend reading through the great online documentation regarding database configuration and settings.
You also have more advanced tools available to you such as the database migration plugin should you need that level of control and flexibility.
In DataSource.groovy (under the conf dir) you find the definition of a H2 db. You could configure a mysql db, oracle, mongodb and so on database.
You also could specify which database use in dev, test and prod enviroments.
when you run your default rails app. The grails environment creates a in memory database for your app. It is created every time you restart your project.
In case you want to have your persistent database like mysql, mongodb etc.
What you need to do is (mysql for example)
Add a mysql dependency in BuildConfig.groovy like runtime 'mysql:mysql-connector-java:5.1.27'
Add Database and driver settings in DataSource.groovy. Now you can have different databases for different environments i.e. prod, test and dev modes. You can do this by having global setting for database or by defining settings for each mode separately.
In order to view your database from your running app you can use link http://localhost:8080/app/dbconsole just enter your database password and username. You will be able to do all your db related queries here. In case you are using grails default in memory database just use hit enter the default values that are there in DataSource.groovy for database
How does ASP.NET MVC, if at all, deal with or provide ways to create your application using multiple environments? For example:
Development environment (local machine, probably run via the built-in web server and talking to a local database)
Testing (runs against a preloaded databse with example data, although this part could be skipped and mocks could be used)
Production database on a real server with real data
Ruby on Rails has the concept of environments and "automagically" can deduce if you're in development or production, so you can specify your connection information (connection string) in a config file and the framework dynamically pulls the appropriate one. Is there a similar way of doing things with .NET MVC? If not then how are professional developers using .NET MVC handling different environments?
The only way I can think of is to manually add an "environment" global method (or use an enum, or something like that, maybe this is a use for something like the State pattern?) and store the different connection strings in the web.config file, and then create a base class which all data access classes derive from which provides a way to obtain the connection string for the current environment; this would then have to be set to production when the time comes to put the application live.
Is there another way? Most of the .NET MVC videos and articles I've seen don't even bother with separate environments but only use a development database and don't indicate how you do it in production.
I'd say this is really a question of your company's internal processes. Since every company is a little bit different it's hard to have a "right" generic way to support dev/test/alpha/production and/or other environments.
One way: Create a setup program that supplies the correct connection string based on the environment chosen during the setup process.
Another way: System Admin edits web.config file to supply correct connection string during install.
Yet ANother Way: Connection strings are stored in the system registry.
Even Another Odd Way: You have all your connection strings for all environments in web.config, then a setting in appSettings the tells you which one to use.
Depending on the client, I've done all of these. There are more but these are the more popular.
(One client wanted to store the connecting string in the data base itself. Really.)
You can use alias for your database. You just point these aliases to different servers in the different environments. Stored in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\Connect if i remember right. Then you use the alias in the connectionstring.
In response to Jason's response:
We use Enterprise Library Environments to configure the different environment paramters and via msbuild invoke the Merge Configuration Tool that generates the different configs for each environment. The deploy process picks the right config file depending on which environment to install.
I was able to solve a similar situation following these steps:
In your Visual Studio, access Build > Configuration Manager
Click in "new"
Choose a name for your configuration, and then copy settings from an existing config. After the configuration creation, it will be available for you to target as build configuration
Create a Web.{env-name-you-chose}.config in your application folder, along with the original Web.config file.
Open your .csproj file with Visual Studio or any text editor
Search for a section that looks like the following and add the highlighted lines, with the config file name you gave previously:
Open your Visual Studio, reload projects if it's required, and now you are able to choose your configuration via CLI or manual publish using Visual Studio.
There is a Publishing Wizard (in Visual Studio) wich let's you change parts of web.config for release build automaticaly. Wich happens to be the feature you are asking about. No magic thou.
What we have done is during our automated build process (Hudson), we alter values in web.config depending on which environment the build is for. Unfortunately there isn't a magical way to do this.
For deployment, which I assume that is what the op was asking about, one creates multiple configurations and in the publish, picks a different configuration. These are called transforms and they operate on the web.config. One would have at least three publish profiles, one for dev, test and prod. One can change more than just the connection string in this way. One can turn on custom errors, turn off debugging and change values of configuration variables. I highly recommend it.
I have a similar question. I have a log table reader. I want it to read log tables in the development, test and production databases. The major difficulty lies in my user account doesn't have permission to look at test and production. It's some silly security thing. The user that I'm impersonating in the application does have permission. I'm struggling trying to tell MVC to build the test and production models using the impersonated user.