Codeunit/FormEvent/InstanceCreator - Revision history

Tvi: 24 revisions imported

2021-12-10T10:51:16Z

24 revisions imported

← Older revision	Revision as of 12:51, 10 December 2021
(No difference)

2018-09-22T15:44:48Z

What is it

← Older revision		Revision as of 17:44, 22 September 2018
Line 9:		Line 9:
	** tslive		** tslive
	** tstest		** tstest

			You also need to make sure that the instance creating the other instances have '''full access to the database''' (create users and databases).

	== context template ==		== context template ==

2018-09-22T15:36:59Z

Database template

← Older revision		Revision as of 17:36, 22 September 2018
Line 53:		Line 53:
	We recommend dumping the files using mysqldump		We recommend dumping the files using mysqldump

	mysqldump -uroot -pPASSWORD demobase > /mnt/sda/template/base.sql		mysqldump --skip-add-locks -uroot -pPASSWORD demobase > /mnt/sda/template/base.sql
	mysqldump -uroot -pPASSWORD demolive > /mnt/sda/template/live.sql		mysqldump --skip-add-locks -uroot -pPASSWORD demolive > /mnt/sda/template/live.sql
	mysqldump -uroot -pPASSWORD demotest > /mnt/sda/template/test.sql		mysqldump --skip-add-locks -uroot -pPASSWORD demotest > /mnt/sda/template/test.sql

	After dumping the files you can clean out unwanted dato in an editor		After dumping the files you can clean out unwanted dato in an editor

2018-09-22T15:32:31Z

Database template

← Older revision		Revision as of 17:32, 22 September 2018
Line 56:		Line 56:
	mysqldump -uroot -pPASSWORD demolive > /mnt/sda/template/live.sql		mysqldump -uroot -pPASSWORD demolive > /mnt/sda/template/live.sql
	mysqldump -uroot -pPASSWORD demotest > /mnt/sda/template/test.sql		mysqldump -uroot -pPASSWORD demotest > /mnt/sda/template/test.sql

			After dumping the files you can clean out unwanted dato in an editor

	== Configuration ==		== Configuration ==

2018-09-22T15:31:37Z

Database template

← Older revision		Revision as of 17:31, 22 September 2018
Line 52:		Line 52:

	We recommend dumping the files using mysqldump		We recommend dumping the files using mysqldump

			mysqldump -uroot -pPASSWORD demobase > /mnt/sda/template/base.sql
			mysqldump -uroot -pPASSWORD demolive > /mnt/sda/template/live.sql
			mysqldump -uroot -pPASSWORD demotest > /mnt/sda/template/test.sql

	== Configuration ==		== Configuration ==

2018-09-22T15:04:10Z

Database template

← Older revision		Revision as of 17:04, 22 September 2018
Line 50:		Line 50:
	* live.sql		* live.sql
	* test.sql		* test.sql

			We recommend dumping the files using mysqldump

	== Configuration ==		== Configuration ==

2018-09-22T14:58:11Z

What is it

← Older revision		Revision as of 16:58, 22 September 2018
Line 3:		Line 3:

	So you will need		So you will need
	* ~~A template~~ for the context file		* Template for the context file
			* Shared TempusServa.war file
	* MySQL dump files		* MySQL dump files
	** tsbase		** tsbase

2018-09-22T14:28:17Z

Configuration

← Older revision		Revision as of 16:28, 22 September 2018
Line 41:		Line 41:
	* @DOCBASE@		* @DOCBASE@
	* @APPLICATION@		* @APPLICATION@

			== Database template ==
			From the baseline system build dump copies of the databases.

			You will need to use strict naming of the files:
			* base.sql
			* live.sql
			* test.sql

	== Configuration ==		== Configuration ==
Line 49:		Line 57:
	Now setup		Now setup
	* locations of the templates		* locations of the templates
	** InstanceCreator.sqlTemplateFolder: Folder of base.sql live.sql and test.sql		** InstanceCreator.sqlTemplateFolder: Folder of '''base.sql live.sql''' and '''test.sql'''
	** InstanceCreator.contextTemplateFile: Position of the context template		** InstanceCreator.contextTemplateFile: Position of the context template
	* mapped field names		* mapped field names

2018-09-22T14:26:30Z

Sample context template

← Older revision		Revision as of 16:26, 22 September 2018
Line 9:		Line 9:
	** tstest		** tstest

	== ~~Sample~~ context template ==		== context template ==

	The context template path must be configured in '''InstanceCreator.contextTemplateFile'''		The context template path must be configured in '''InstanceCreator.contextTemplateFile'''

2018-09-22T14:26:06Z

Usage

← Older revision		Revision as of 16:26, 22 September 2018
Line 70:		Line 70:

	After an instance is created and status will now be either		After an instance is created and status will now be either
	* succes (as defined per "")		* succes (as defined per '''StatusCompleted''')
	* error (as defined per "")		* error (as defined per '''StatusFailSetup''')

			If the operation succeds you instance will be available in a minute or two.