From version < 25.1 >
edited by Jonathan Rubiero
on 2018/05/04 12:46
To version < 26.1 >
edited by Jonathan Rubiero
on 2018/05/04 13:06
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,7 @@
16 16  
17 17  If you want to create a full dump of your database, follow the instruction below :
18 18  
19 -* Perform a full backup of the STEP database : use the following command to output the backup to the //backup// folder:
19 +* Perform a full backup of the STEP database : use the following command to output the dump to the //backup// folder:
20 20  * (% class="box" %)
21 21  (((
22 22  mongodump -d step -o backup
... ... @@ -24,7 +24,7 @@
24 24  
25 25  ==== Case 2 : partial backup ====
26 26  
27 -If you only want to backup your work and not the executions data, follow the instructions below :
27 +If you only want to backup your work and not the executions data, follow the instruction below :
28 28  
29 29  * use the following commands to export you keywords, test plans, users and scheduled entries :
30 30  
... ... @@ -46,7 +46,7 @@
46 46  
47 47  ===== Start new instance =====
48 48  
49 -If you new STEP instance will run alongside the existing one, you will have to start a new instance of MongoDB on a different port that the one used by the previous instance.
49 +If you new STEP instance will run alongside the existing one, you will have to start a new instance of **MongoDB **on a different port that the one used by the previous instance.
50 50  
51 51  Follow below instruction in order to achieve this :
52 52  
... ... @@ -61,15 +61,15 @@
61 61  (((
62 62  %MONGO_PATH%mongod.exe **~-~-port PORT_NUMBER** -dbpath ..\data\mongodb > mongod_%mydate%.log 2>&1
63 63  )))
64 -* use this modified script to start your new MongoDB instance
64 +* use this modified script to start your new **MongoDB **instance
65 65  
66 66  ===== Restore the data =====
67 67  
68 -Now that your new instance is running, you can restore your data into it (considering the new MongoDB instance is running on port 28017) :
68 +Now that your new instance is running, you can restore your data into it (considering the new **MongoDB **instance is running on port **28017**) :
69 69  
70 70  ====== Case 1 : full backup available ======
71 71  
72 -* Considering your backup folder is called "backup", execute the following command :
72 +* Considering your backup folder is called "**backup**", execute the following command :
73 73  * (% class="box" %)
74 74  (((
75 75  mongorestore ~-~-port 27018 -d step backup
... ... @@ -77,7 +77,7 @@
77 77  
78 78  ====== Case 2 : partial backup available ======
79 79  
80 -* Execute the following commands to restore your keywords, test plans, user and scheduled entries :
80 +* Execute the following commands to restore your keywords, test plans, users and scheduled entries :
81 81  * (% class="box" %)
82 82  (((
83 83  mongoimport ~-~-port 27018 -d step -c functions functions.json
... ... @@ -93,14 +93,14 @@
93 93  
94 94  === Plugins migration ===
95 95  
96 -For every plugins you are using you will have to copy the plugin binaries into the new controller lib folder and tweak the controller //**step.properties**// configuration file. See below instructions for each plugin.
96 +For every plugin you are using you will have to copy the plugin binaries into the new controller lib folder and tweak the controller //**step.properties**// configuration file. See below instructions for each plugin.
97 97  
98 98  ==== HP ALM ====
99 99  
100 -* First, the following jar files have to be copied on the controller, under **...\step-controller-//X.Y.Z//\lib\**
100 +* Following jar files have to be copied on the controller, under **...\step-controller-//X.Y.Z//\lib\**
101 101  ** **alm-plugin-//X.Y.Z//.jar**
102 102  ** **alm-repository-//X.Y.Z//.jar**
103 -* The following lines must be taken from the old controller //**step.properties**// configuration file and copied to new one, located at **...\step-controller-//X.Y.Z//\conf\step.properties.**
103 +* Following lines must be taken from the old controller //**step.properties**// configuration file and copied to new one, located at **...\step-controller-//X.Y.Z//\conf\step.properties.**
104 104  * (% class="box" %)
105 105  (((
106 106  almrepository.daemon.javapath=**C:\YOUR\JAVA\PATH\java.exe**
... ... @@ -110,11 +110,11 @@
110 110  almrepository.profile.prod.pwd=<**//password>//**
111 111  almrepository.bdd.parsers=step.repositories.parser.annotated.DefaultDescriptionStepParser,step.repositories.parser.CustomExpectedStepParser,step.repositories.parser.CustomDescriptionStepParser
112 112  
113 -attachmentsdir=**C:~\~\path~\~\to~\~\attachments**
113 +attachmentsdir=**C:\YOUR\ATTACHMENTS\DIR\PATH**
114 114  
115 115  tec.expressions.scriptbaseclass=**TEMPLATE_FILE_NAME**
116 116  )))
117 -* If you are using groovy templates with the plugin, make sure to also copy the line used to start the controller located in file **...\step-controller-//X.Y.Z//\bin\startController.bat** :
117 +* If you are using groovy templates with this plugin, make sure to also copy the line used to start the controller located in file **...\step-controller-//X.Y.Z//\bin\startController.bat** :
118 118  ** (% class="box" %)
119 119  (((
120 120  "%JAVA_PATH%java.exe" %JAVA_OPTS% -cp "..\lib\*;**C:\YOUR\TEMPLATE\FOLDER\PATH**" step.controller.ControllerServer -config=../conf/step.properties
... ... @@ -122,13 +122,13 @@
122 122  
123 123  ==== SoapUI ====
124 124  
125 -* First, the following jar files have to be copied on the controller, under **...\step-controller-//X.Y.Z//\lib\**:
125 +* Following jar files have to be copied on the controller, under **...\step-controller-//X.Y.Z//\lib\**:
126 126  ** **soapui-plugin-def-//X.Y.Z//.jar**
127 127  ** **soapui-plugin-handler-//X.Y.Z//.jar**
128 128  * The following lines must be taken from the old controller //**step.properties**// configuration file and copied to new one, located at **...\step-controller-//X.Y.Z//\conf\step.properties.**
129 129  * (% class="box" %)
130 130  (((
131 -plugins.soapui.home=**C:/YOUR/SOAPUI/PATH/SoapUI-5.4.0**
131 +plugins.soapui.home=**C:/YOUR/SOAPUI/PATH/SoapUI-//X.Y.Z//**
132 132  )))
133 133  
134 134  ==== JMeter ====
... ... @@ -135,21 +135,21 @@
135 135  
136 136  * The following lines must be taken from the old controller //**step.properties**// configuration file and copied to new one, located at **...\step-controller-//X.Y.Z//\conf\step.properties.**(% class="box" %)
137 137  (((
138 -plugins.jmeter.home=**C:/YOUR/JMETER/PATH/apache-jmeter-4.0/**
138 +plugins.jmeter.home=**C:/YOUR/JMETER/PATH/apache-jmeter-//X.Y///**
139 139  )))
140 140  
141 141  ==== .NET Plugin ====
142 142  
143 -* Copy the //**dotnet-plugin-X.Y.Z.jar** //file to **...\step-controller-//X.Y.Z//\lib\**
143 +* Copy the **dotnet-plugin-//X.Y.Z.jar//**// //file to **...\step-controller-//X.Y.Z//\lib\**
144 144  
145 145  ==== Node.js ====
146 146  
147 -* Copy the **node-plugin-X.Y.Z.jar **file to **...\step-controller-//X.Y.Z//\lib\**
147 +* Copy the **node-plugin-//X.Y.Z//.jar **file to **...\step-controller-//X.Y.Z//\lib\**
148 148  )))
149 149  
150 150  === Configuration review ===
151 151  
152 -Now that you have migrated the plugins configuration, you will have to migrate the remaining configurations entries from the old configurations files to the new ones.
152 +Now that you have migrated the plugins configuration, you will also have to migrate the remaining configurations entries from the old configurations files to the new ones.
153 153  
154 154  ==== step.properties ====
155 155  
... ... @@ -172,7 +172,7 @@
172 172  
173 173  ===== Case 2 : new instance running alongside the old one =====
174 174  
175 -If your new installations will run alongside the existing one, make sure to update the following settings with the new instance according values:
175 +If your new installation will run alongside the existing one, make sure to update the following settings with the new instance corresponding values:
176 176  
177 177  * port
178 178  * grid.port
... ... @@ -199,7 +199,10 @@
199 199  
200 200  === Configuration review ===
201 201  
202 +(% class="box infomessage" %)
203 +(((
202 202  **Note that you will have to repeat below steps for every agent.**
205 +)))
203 203  
204 204  Migrate the configurations entries from the old configurations file to the new one :
205 205  
... ... @@ -211,7 +211,7 @@
211 211  
212 212  (% class="box warningmessage" %)
213 213  (((
214 -If you new instance is running alongside the existing one, make sure to update the port the agents use to connect to the controller Grid !!!
217 +If you new instance is running alongside the existing one, make sure to update the agents port used to connect to the controller Grid !!!
215 215  {
216 216  "gridHost":"http:~/~/localhost:**CONTROLLER_GRID_PORT**",
217 217  ....
Copyright © exense GmbH
v1.0