Update - FORMCYCLE Wiki

author	version	line-number	content
1	{{content/}}
2
3	{{figure image="database_update_required_en.png"}}
4	When an update of the system or the database is required, you will see a notification on the login screen.
5	{{/figure}}
6
7	{{figure image="database_settings_en.png"}}
8	After you sign in, you are taken to the database settings. Check if they are still correct.
9	{{/figure}}
10
11	{{figure image="database_update_running_en.png"}}
12	After you have checked the database settings, the system performs all necessary updates.
13	{{/figure}}
14
15	{{figure image="database_update_finished_en.png"}}
16	The update is done once all required updates have finished.
17	{{/figure}}
18
19	{{info}}
20	Before you install an update, make sure you check out the [[release notes>>doc:Blog.WebHome]]
21	{{/info}}
22
23	{{info}}
24	We recommend you take a backup of the database and all local data before you install the update.
25	{{/info}}
26
27	{{info}}
28	For an update between minor versions (e.g. from version 6.1.2 to 6.3.1) it is not necessary to install all minor intermediate versions (6.2.0, 6.3.0) one after the other. In this example only the update 6.3.1 has to be installed. It includes all previous updates.
29	{{/info}}
30
31	The current version of {{formcycle/}} can be downloaded directly from our [[update page>>url:http://customer.formcycle.eu/index.php/s/n61U7gjJGFeUzrt]]. If you should require them, we also provide access to previous versions of {{formcycle/}}.
32
33	For each version, you can find three different files:
34
35	; formcycle.war
36	: Contains the master server with the backend and the {{designer/}}. For the most common use case, you only need this file.
37	; frontend-server.war
38	: Contains the [[frontend server>>doc:Formcycle.SystemSettings.FrontendAndMasterServer]] that only serves and accepts forms.
39	; frontend-server-inbox.war
40	: The frontend-server with additional support for accessing the [[inbox>>doc:Formcycle.Inbox.WebHome]] on the frontend server.
41
42	For certain version, we also provide plugins you can download.
43
44	== Step 1: Download the current version ==
45
46	The current version of {{formcycle/}} can be downloaded directly from our [[update page>>http://customer.formcycle.eu/index.php/s/n61U7gjJGFeUzrt]].
47
48	== Step 2: Replace the old version ==
49
50	1. Remove the current WAR file on the application server from the Tomcat. In Windows, for example, this is the folder C:\Program Files\Apache\Tomcat 9.0\webapps. The folder formcycle is automatically removed. This folder must be deleted before you continue.
51	1. Upload or copy the new WAR file to the //webapps// directory.
52
53	{{info}}
54	It may be necessary to restart the tomcat or application server afterwards. When required, update the configuration file //web.xml// as well in case you have made any custom changes.
55	{{/info}}
56
57	== Step 3: Database update ==
58
59	When you go to the login page, you may get a notifications that an update was found. If it does, sign in with a system administrator account and proceed as follows:
60
61	1. After signing in as system administrator (sadmin), you will be redirected to the database administration page. Here the settings should be checked again.
62	1. After clicking the //Save and update// button, the database and machine are updated.
63	1. The individual steps are displayed here. When all of them have been completed, the update is completed.
64
65	You should logout and continue your work with a regular user account (and not as a system administrator).
66
67	Please note that plugin updates may also be required. To do this, you must check the Customer Cloud to see if you already have the latest version installed. The update can be done under System > System plugins or
68	Client > Plugins, using the button //Update plugin bundle//. Please make sure that the correct plugin is selected.
69
70	== Notice Update Frontend Server ==
71
72	The process for updating the frontend server must be done adequately to FORMCYCLE. This should ideally be done before FORMCYCLE. Afterwards, check on the master server under System > [[Frontend Server>>doc:Formcycle.SystemSettings.UserInterface.FrontendServer]] whether the connection is re-established.

When an update of the system or the database is required, you will see a notification on the login screen.

5

6

7

8

After you sign in, you are taken to the database settings. Check if they are still correct.

After you have checked the database settings, the system performs all necessary updates.

The update is done once all required updates have finished.

Before you install an update, make sure you check out the [[release notes>>doc:Blog.WebHome]]

We recommend you take a backup of the database and all local data before you install the update.

For an update between minor versions (e.g. from version 6.1.2 to 6.3.1) it is **not** necessary to install all minor intermediate versions (6.2.0, 6.3.0) one after the other. In this example only the update 6.3.1 has to be installed. It includes all previous updates.

29

30

31

The current version of {{formcycle/}} can be downloaded directly from our [[update page>>url:http://customer.formcycle.eu/index.php/s/n61U7gjJGFeUzrt]]. If you should require them, we also provide access to previous versions of {{formcycle/}}.

32

33

For each version, you can find three different files:

34

35

; formcycle.war

36

: Contains the master server with the backend and the {{designer/}}. For the most common use case, you only need this file.

37

; frontend-server.war

38

: Contains the [[frontend server>>doc:Formcycle.SystemSettings.FrontendAndMasterServer]] that only serves and accepts forms.

39

; frontend-server-inbox.war

40

: The frontend-server with additional support for accessing the [[inbox>>doc:Formcycle.Inbox.WebHome]] on the frontend server.

41

42

For certain version, we also provide plugins you can download.

43

44

== Step 1: Download the current version ==

45

46

The current version of {{formcycle/}} can be downloaded directly from our [[update page>>http://customer.formcycle.eu/index.php/s/n61U7gjJGFeUzrt]].

47

48

== Step 2: Replace the old version ==

49

50

1. Remove the current WAR file on the application server from the Tomcat. In Windows, for example, this is the folder C:\Program Files\Apache\Tomcat 9.0\webapps. The folder formcycle is automatically removed. This folder must be deleted before you continue.

51

1. Upload or copy the new WAR file to the //webapps// directory.

52

53

54

It may be necessary to restart the tomcat or application server afterwards. When required, update the configuration file //web.xml// as well in case you have made any custom changes.

55

56

57

== Step 3: Database update ==

58

59

When you go to the login page, you may get a notifications that an update was found. If it does, sign in with a system administrator account and proceed as follows:

60

61

1. After signing in as system administrator (sadmin), you will be redirected to the database administration page. Here the settings should be checked again.

62

1. After clicking the //Save and update// button, the database and machine are updated.

63

1. The individual steps are displayed here. When all of them have been completed, the update is completed.

64

65

You should logout and continue your work with a regular user account (and not as a system administrator).

66

67

Please note that plugin updates may also be required. To do this, you must check the Customer Cloud to see if you already have the latest version installed. The update can be done under System > System plugins or

68

Client > Plugins, using the button //Update plugin bundle//. Please make sure that the correct plugin is selected.

69

70

== Notice Update Frontend Server ==

71

72

The process for updating the frontend server must be done adequately to FORMCYCLE. This should ideally be done before FORMCYCLE. Afterwards, check on the master server under System > [[Frontend Server>>doc:Formcycle.SystemSettings.UserInterface.FrontendServer]] whether the connection is re-established.

Wiki source code of Update

Navigation