Org.simantics.db.procore.server - Revision history

Tuukka Lehtonen: /* Compiling */

2011-07-20T12:47:03Z

Compiling

← Older revision		Revision as of 12:47, 20 July 2011
Line 14:		Line 14:
	=== Linux 32/64-bit ===		=== Linux 32/64-bit ===
	Install prerequisites:		Install prerequisites:
	~~TODO: gcc, g++, other tools?~~		$ apt-get install gcc g++ scons libace-dev liblzo2-dev uuid-dev libboost-all-dev
	$ apt-get install scons libace-dev liblzo2-dev uuid-dev libboost-all-dev
	Checkout source:		Checkout source:
	$ svn co https://www.simulationsite.net/svn/simantics/db/trunk/org.simantics.db.procore.server		$ svn co https://www.simulationsite.net/svn/simantics/db/trunk/org.simantics.db.procore.server

Tuukka Lehtonen: /* Compiling */

2011-07-20T12:46:27Z

Compiling

← Older revision		Revision as of 12:46, 20 July 2011
Line 15:		Line 15:
	Install prerequisites:		Install prerequisites:
	TODO: gcc, g++, other tools?		TODO: gcc, g++, other tools?
	$ apt-get install scons libace-dev liblzo2-dev uuid-dev		$ apt-get install scons libace-dev liblzo2-dev uuid-dev libboost-all-dev
	Checkout source:		Checkout source:
	$ svn co https://www.simulationsite.net/svn/simantics/db/trunk/org.simantics.db.procore.server		$ svn co https://www.simulationsite.net/svn/simantics/db/trunk/org.simantics.db.procore.server

Toni Kalajainen at 10:02, 29 September 2010

2010-09-29T10:02:33Z

← Older revision		Revision as of 10:02, 29 September 2010
Line 1:		Line 1:
	~~ProCore~~ is a semantic database.		Simantics Core is a semantic database server application.


	=== Backup Plan ===		=== Backup Plan ===

Toni Kalajainen at 10:02, 29 September 2010

2010-09-29T10:02:06Z

← Older revision		Revision as of 10:02, 29 September 2010
Line 2:		Line 2:


	=== ~~Random Q & As~~ ===		=== Backup Plan ===


	The data written to a persistent store can be '''INVALUABLE'''.		The data written to a persistent store can be '''INVALUABLE'''.
			Change set data combined with transaction journaling provides safety against crashes and power outages etc. If data gets corrupted anyway, backups must be used to recover data.
	~~Q: In case of DB corrupts, is there a recovery plan?~~		Periodical full binary backup of the database can be done. Critical parts of the data can also be stored periodically as Transferable Graphs (this format does not depend on the ProCore version).

	A: Change set data combined with transaction journaling provides safety against crashes and power outages etc. If data gets corrupted anyway, backups must be used to recover data.

	~~Q: Is there a backup plan?~~

	A: Periodical full binary backup of the database can be done. Critical parts of the data can also be stored periodically as Transferable Graphs (this format does not depend on the ProCore version).

	=== Arguments to Server ===		=== Arguments to Server ===

Toni Kalajainen at 10:01, 29 September 2010

2010-09-29T10:01:02Z

← Older revision		Revision as of 10:01, 29 September 2010
Line 1:		Line 1:
	ProCore is a semantic database.		ProCore is a semantic database.

	~~There are two network communication protocols:~~
	* [[ProCom]]
	* [http://www.opcfoundation.org/UA OPC Unified Architecture]


	=== Random Q & As ===		=== Random Q & As ===

Toni Kalajainen: Created page with 'ProCore is a semantic database. There are two network communication protocols: * ProCom * [http://www.opcfoundation.org/UA OPC Unified Architecture] === Random Q & As ==...'

2010-09-28T14:16:47Z

Created page with 'ProCore is a semantic database. There are two network communication protocols: * ProCom * [http://www.opcfoundation.org/UA OPC Unified Architecture] === Random Q & As ==...'

New page

ProCore is a semantic database.

There are two network communication protocols:
* [[ProCom]]
* [http://www.opcfoundation.org/UA OPC Unified Architecture]

=== Random Q & As ===

The data written to a persistent store can be '''INVALUABLE'''.

Q: In case of DB corrupts, is there a recovery plan?

A: Change set data combined with transaction journaling provides safety against crashes and power outages etc. If data gets corrupted anyway, backups must be used to recover data.

Q: Is there a backup plan?

A: Periodical full binary backup of the database can be done. Critical parts of the data can also be stored periodically as Transferable Graphs (this format does not depend on the ProCore version).

=== Arguments to Server ===

The only argument the server accepts is name of file containing configuration arguments. If an argument is not given the name server.cnfg is used. If file is not found or there is error during parsing of the file server does not start. An example of configuration file, which also documents the parameters that can be given, is found in org.simantics.db.undocore.OS.ARCH plugin.

== Compiling ==

=== Linux 32/64-bit ===
Install prerequisites:
TODO: gcc, g++, other tools?
$ apt-get install scons libace-dev liblzo2-dev uuid-dev
Checkout source:
$ svn co https://www.simulationsite.net/svn/simantics/db/trunk/org.simantics.db.procore.server
Compile ProCoreServer
$ cd org.simantics.db.procore.server
$ scons install

=== VS2008 ===

Get VS2008.zip from org.simantics.db.procore.server.win32 (SVN) and extract to location X

load org.simantics.db.procore.server/procore/ProCoreServer/ProCoreServer.sln

in Tools/Options/Projects and Solutions/VC++ Directories

*add X\VS2008\inc to 'Include files' first entry
*add x\VS2008\x86\$(ConfigurationName) to 'Library files' last entry

in ProCoreServer project options

*add ..\$(ConfigurationName).cnfg to Debugging/CommandArguments
*add $(ConfigurationName) to Debugging/Working Directory
*add PATH=X/VS2008/x86/$(ConfigurationName) to Debugging/Environment