...
core-service 7.16 LTS → core-service 8.x
- Stop the core-service 7.16 LTS.
- If the data-directory (containing the WORK and/or ARCHIVE directories) is located inside the installation path of the dms-service, move it outside and/or make a backup.
- Make a backup of the following files/folders
- <core-service>\standalone\configuration\standalone-full-ha.xml
- AD-Sync configuration files (e.g., <core-service>\standalone\configuration\ldapsync)
- Custom files under <core-service>\standalone\configuration\bpm-script-api
- Operation report files (e.g., <core-service>\standalone\tmp\jas-operations\reports)
- Open the service-wrapper GUI by executing the file <core-service>\bin\yuuvis_rad_core-servicew.exe
- Backup/write down the settings under Java → Java Options (especially the value of ". Especially the keys/values of
- -Dcom.os.ecm.systemuserkey
- -Djboss.bind.address
- -Djboss.bind.address.private
- Backup/write down the settings under Java → Java Options (especially the value of ". Especially the keys/values of
- Uninstall the core-service.
- Install the core-service as described here: Installation Guide Version 8.0
- Be sure to select "no" when asked if a new database structure and base configuration should be created.
- When asked for the system user api-key overwrite the generated value with the backed up value of "-Dcom.os.ecm.systemuserkey".
- Move the backed-up data directory back to its original location.
(Alternatively, you can choose a new location but then you have to adapt the path in the Media section of the management-studio as the very first action after the first startup.) - To restore the backed-up configuration, follow these steps:
- If you have made changes to the default logging settings or the default database connection pool sizes, compare the backed-up standalone-full-ha.xml file with the newly installed replacement for it calles "jas-app.xml" and reapply your changes.
- If you have custom bpm script api files, create the folder <core-service>\standalone\configuration\bpm-script-api and copy them into it.
- Move or copy the AD-Sync and operation report folders back to their relative location under the new core-service installation path.
- Open the service-wrapper GUI by executing the <core-service>\bin\yuuvis_rad_core-servicew.exe file and compare the Java → Java Options settings.
Reapply custom settings that do not belong to the JBoss or Java Runtime Environment. Especially restore the keys/values of:- -Dcom.os.ecm.systemuserkey
- -Djboss.bind.address
- -Djboss.bind.address.private
While in the GUI, make sure you have adapted the Initial/Maximum Pool Size Setting and the logging configuration to your desired values.
- Start the service and check the log file for a successful startup which is indicated by the "yuuvis" ascii art.
- If you are using the AD-Sync operation: After startup of all components, open the AD-Sync operation in yuuvis® RAD management-studio and adapt the path to the AD-Sync configuration file to the new location (if applies).
- Workflow models should be tested
- service-manager 7.16 LTS → service-manager 8.0
- Open the file <service-manager>\config\index-prod.yml and insert (or edit) the following line:
osfts.languages: 'de'
The value "de" is a placeholder for one of the following values: de,en,es,fr,it. Set the language code of the language that is used the most in your system. This language will be supported by the intrafind lingustic plugin. All other languages active in your system will have basic support.
Please note: Only one value may be set for this parameter. If no value is specified in the configuration file, the default 'en' for English will be activated. - Only for Microsoft SQL Server: Open the file <service-manager>\config\application-dbs.yml and append the value "encrypt=false;" at the end of the line starting with "spring.datasource.url:"
it should now look like this:
- If present, the lines with the following parameter names can be removed from the file <service-manager>\config\application-es.yml :
- spring.data.elasticsearch.cluster-nodes: '127.0.0.1:9300'
- spring.data.elasticsearch.cluster-nodes-rest: '127.0.0.1:9200'
The lines with the following parameter names can be removed from the file <service-manager>\config\bpm-prod.yml as well as from the file <service-manager>\config\inbox-prod.yml since they are no longer used:
- liquibase.url
- liquibase.user
- liquibase.password
- spring.jpa.hibernate.ddl-auto
- The routing-service microservice has to be completely removed from the service-manager. To do this:
- Delete the "routingservice" folder in the folder <service-manager>\apps
- Delete the file <service-manager>\config\routing-prod.yml
- Open the file <service-manager>\config\servicewatcher-sw.yml and remove the "- name: routingservice" section.
...