CTS2-LE Update Procedures: Unterschied zwischen den Versionen
Krebs (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „Updating CTS2-LE always includes the delivery of a new .war file. Depending on the components that are affected by an update, the customer may also receive a s…“) |
Krebs (Diskussion | Beiträge) K |
||
| Zeile 15: | Zeile 15: | ||
The artifacts will be delivered in a .zip archive that has to be unpacked under the '''$CTS2LE_RESOURCE_ROOT''' directory. During the initial installation of CTS2-LE, the <span style="color:#ff7f24">highlighted</span> files may have been changed by the customer. If these files are included in the portion of the delivered artifacts, the customer has to ensure that adaptions are properly transcribed onto the new files. For this, Fraunhofer FOKUS will give instructions on how file structures have changed and how the customer-specific information should be mapped to an updated file. | The artifacts will be delivered in a .zip archive that has to be unpacked under the '''$CTS2LE_RESOURCE_ROOT''' directory. During the initial installation of CTS2-LE, the <span style="color:#ff7f24">highlighted</span> files may have been changed by the customer. If these files are included in the portion of the delivered artifacts, the customer has to ensure that adaptions are properly transcribed onto the new files. For this, Fraunhofer FOKUS will give instructions on how file structures have changed and how the customer-specific information should be mapped to an updated file. | ||
| − | Since an update always requires the customer to "freshly" load the store content, it is | + | Since an update always requires the customer to "freshly" load the store content, it is recommended to follow the steps described in the [[CTS2-LE_Installation_and_Deployment#grouping.json|Installation and Deployment guide]]. |
Aktuelle Version vom 21. Juli 2015, 13:06 Uhr
Updating CTS2-LE always includes the delivery of a new .war file. Depending on the components that are affected by an update, the customer may also receive a subset of updated artifacts comprising the below shown directories and files.
/bin
WebCts2LE.war
WebCts2LEStarter.sh
/signatures
/queries
/load-vocabs
/jdbm2
cts2_conf.xml
grouping.json
setting.json
The artifacts will be delivered in a .zip archive that has to be unpacked under the $CTS2LE_RESOURCE_ROOT directory. During the initial installation of CTS2-LE, the highlighted files may have been changed by the customer. If these files are included in the portion of the delivered artifacts, the customer has to ensure that adaptions are properly transcribed onto the new files. For this, Fraunhofer FOKUS will give instructions on how file structures have changed and how the customer-specific information should be mapped to an updated file.
Since an update always requires the customer to "freshly" load the store content, it is recommended to follow the steps described in the Installation and Deployment guide.
