You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by vn...@lycos.com on 2018/02/07 12:57:27 UTC
Steps to upgrade OpenMeetings 4.0.1 on Windows to the latest snapshot
Steps to upgrade OpenMeetings 4.0.1 on Windows to the latest snapshot
version:
Based on the following link, but with more details:
https://openmeetings.apache.org/Upgrade.html
1) Stop Openmeetings service
cmd
cd C:\red5401
net stop Red5
2) Backup the folder with existing installation
jar -cMf C:\OpenMeetings\red5_backup.zip C:\red5401
3) Perform DB backup using tools available for your database
mariabackup --backup --target-dir C:\OpenMeetings\MariaDB_Backup --user
root --password <password>
Note: to restore the backup, empty the data folder, stop the MariaDB
server and use the following commands:
(to normalize the datafiles) mariabackup --prepare --target-dir
C:\OpenMeetings\MariaDB_Backup --user root --password <password>
(to restore) mariabackup --copy-back --target-dir
C:\OpenMeetings\MariaDB_Backup --user root --password <password>
4) Create an OS backup of OM or use Administration > Backup section
admin -v -b -file C:\OpenMeetings\backup_last.zip
5) Delete folder with existing installation
cd \
RMDIR /S /Q C:\red5401
6) Unzip new version of OM into the same folder
mkdir C:\red5401
cd C:\red5401
powershell -command "& {[Net.ServicePointManager]::SecurityProtocol =
[Net.SecurityProtocolType]::Tls12; (new-object
System.Net.WebClient).DownloadFile('https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%204.0.x/lastSuccessfulBuild/artifact/openmeetings-server/target/apache-openmeetings-4.0.2-SNAPSHOT.zip','C:\OpenMeetings\apache-openmeetings-4.0.2-SNAPSHOT.zip');}"
jar -xvf C:\OpenMeetings\apache-openmeetings-4.0.2-SNAPSHOT.zip
7) Download and install the connector between MariaDB and OpenMeetings:
powershell -command "(new-object
System.Net.WebClient).DownloadFile('http://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.45/mysql-connector-java-5.1.45.jar','C:\red5401\webapps\openmeetings\WEB-INF\lib\mysql-connector-java-5.1.45.jar')"
8) Install OM with backup import
admin -v -i -file C:\OpenMeetings\backup_last.zip --drop
--skip-default-objects --db-type mysql --db-name open401 --db-user root
--db-pass <password>
9) Extract the modified files for SSL support from the red5 backup to
the new OM installation conf folder
Rename the existing keystore files
cd conf
rename truststore.jmx truststore.bak
rename keystore.jmx keystore.bak
cd /
jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/keystore.jks
jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/truststore.jks
jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/keystore.screen
jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/jee-container.xml
jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/red5.properties
jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/red5-core.xml
Alternatively to the above task if the files have changed, manually
modify the files as per:
https://openmeetings.apache.org/RTMPSAndHTTPS.html
As per the following link configure Tomcat for http to https redirects
https://www.journaldev.com/160/steps-to-configure-ssl-on-tomcat-and-setup-auto-redirect-from-http-to-https
"C:\Program Files (x86)\Notepad++\notepad++.exe"
C:\red5401\webapps\root\WEB-INF\web.xml
Add the following lines to force http -> https redirect by Tomcat after
the servlet mappings before forbids constraints section:
<security-constraint>
<web-resource-collection>
<web-resource-name>Entire Application</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
"C:\Program Files (x86)\Notepad++\notepad++.exe"
C:\red5401\webapps\openmeetings\WEB-INF\web.xml
Add the following lines to force http -> https redirect by Tomcat in the
Allowed methods constraint section:
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
<!-- no auth-constraint tag here -->
10) Download and extract the commons-daemon files for Windows (needed to
install the Red5 Windows service)
powershell -command "& {[Net.ServicePointManager]::SecurityProtocol =
[Net.SecurityProtocolType]::Tls12; (new-object
System.Net.WebClient).DownloadFile('https://archive.apache.org/dist/commons/daemon/binaries/windows/commons-daemon-1.0.15-bin-windows.zip','C:\OpenMeetings\commons-daemon-1.0.15-bin-windows.zip');}"
cd C:\red5401
jar -xvf C:\OpenMeetings\commons-daemon-1.0.15-bin-windows.zip
install-service.bat
11) Start Openmeetings
net start Red5
12) Navigate to Windows Firewall -> Allowed Apps. Switch to Change Mode
and add the following app:
Commons Daemon Service Runner
C:\red5401\amd64\prunsrv.exe
Re: Steps to upgrade OpenMeetings 4.0.1 on Windows to the latest snapshot
Posted by Maxim Solodovnik <so...@gmail.com>.
Thanks again
It is great to see answers and instructions in mailing list :)
On Wed, Feb 7, 2018 at 7:57 PM, <vn...@lycos.com> wrote:
> Steps to upgrade OpenMeetings 4.0.1 on Windows to the latest snapshot
> version:
>
> Based on the following link, but with more details: https://openmeetings.
> apache.org/Upgrade.html
>
> 1) Stop Openmeetings service
> cmd
> cd C:\red5401
> net stop Red5
>
> 2) Backup the folder with existing installation
> jar -cMf C:\OpenMeetings\red5_backup.zip C:\red5401
>
> 3) Perform DB backup using tools available for your database
> mariabackup --backup --target-dir C:\OpenMeetings\MariaDB_Backup --user
> root --password <password>
>
> Note: to restore the backup, empty the data folder, stop the MariaDB
> server and use the following commands:
> (to normalize the datafiles) mariabackup --prepare --target-dir
> C:\OpenMeetings\MariaDB_Backup --user root --password <password>
> (to restore) mariabackup --copy-back --target-dir
> C:\OpenMeetings\MariaDB_Backup --user root --password <password>
>
> 4) Create an OS backup of OM or use Administration > Backup section
> admin -v -b -file C:\OpenMeetings\backup_last.zip
>
> 5) Delete folder with existing installation
> cd \
> RMDIR /S /Q C:\red5401
>
> 6) Unzip new version of OM into the same folder
> mkdir C:\red5401
> cd C:\red5401
> powershell -command "& {[Net.ServicePointManager]::SecurityProtocol =
> [Net.SecurityProtocolType]::Tls12; (new-object System.Net.WebClient).
> DownloadFile('https://builds.apache.org/view/M-R/view/
> OpenMeetings/job/OpenMeetings%204.0.x/lastSuccessfulBuild/
> artifact/openmeetings-server/target/apache-openmeetings-4.0.2-SNAPSHOT.zip
> ','C:\OpenMeetings\apache-openmeetings-4.0.2-SNAPSHOT.zip');}"
> jar -xvf C:\OpenMeetings\apache-openmeetings-4.0.2-SNAPSHOT.zip
>
> 7) Download and install the connector between MariaDB and OpenMeetings:
> powershell -command "(new-object System.Net.WebClient).DownloadFile('
> http://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.45/mysql-
> connector-java-5.1.45.jar','C:\red5401\webapps\openmeetings\
> WEB-INF\lib\mysql-connector-java-5.1.45.jar')"
>
> 8) Install OM with backup import
> admin -v -i -file C:\OpenMeetings\backup_last.zip --drop
> --skip-default-objects --db-type mysql --db-name open401 --db-user root
> --db-pass <password>
>
> 9) Extract the modified files for SSL support from the red5 backup to the
> new OM installation conf folder
> Rename the existing keystore files
> cd conf
> rename truststore.jmx truststore.bak
> rename keystore.jmx keystore.bak
>
> cd /
> jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/keystore.jks
> jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/truststore.jks
> jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/keystore.screen
> jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/jee-container.xml
> jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/red5.properties
> jar -xvf C:\OpenMeetings\red5_backup.zip red5401/conf/red5-core.xml
>
> Alternatively to the above task if the files have changed, manually modify
> the files as per: https://openmeetings.apache.org/RTMPSAndHTTPS.html
>
> As per the following link configure Tomcat for http to https redirects
>
> https://www.journaldev.com/160/steps-to-configure-ssl-on-
> tomcat-and-setup-auto-redirect-from-http-to-https
>
> "C:\Program Files (x86)\Notepad++\notepad++.exe"
> C:\red5401\webapps\root\WEB-INF\web.xml
> Add the following lines to force http -> https redirect by Tomcat after
> the servlet mappings before forbids constraints section:
> <security-constraint>
> <web-resource-collection>
> <web-resource-name>Entire Application</web-resource-name>
> <url-pattern>/*</url-pattern>
> </web-resource-collection>
> <user-data-constraint>
> <transport-guarantee>CONFIDENTIAL</transport-guarantee>
> </user-data-constraint>
> </security-constraint>
>
> "C:\Program Files (x86)\Notepad++\notepad++.exe" C:\red5401\webapps\
> openmeetings\WEB-INF\web.xml
> Add the following lines to force http -> https redirect by Tomcat in the
> Allowed methods constraint section:
> </web-resource-collection>
> <user-data-constraint>
> <transport-guarantee>CONFIDENTIAL</transport-guarantee>
> </user-data-constraint>
> <!-- no auth-constraint tag here -->
>
> 10) Download and extract the commons-daemon files for Windows (needed to
> install the Red5 Windows service)
>
> powershell -command "& {[Net.ServicePointManager]::SecurityProtocol =
> [Net.SecurityProtocolType]::Tls12; (new-object System.Net.WebClient).
> DownloadFile('https://archive.apache.org/dist/commons/
> daemon/binaries/windows/commons-daemon-1.0.15-bin-windows.zip
> ','C:\OpenMeetings\commons-daemon-1.0.15-bin-windows.zip');}"
>
> cd C:\red5401
> jar -xvf C:\OpenMeetings\commons-daemon-1.0.15-bin-windows.zip
>
> install-service.bat
>
> 11) Start Openmeetings
> net start Red5
>
> 12) Navigate to Windows Firewall -> Allowed Apps. Switch to Change Mode
> and add the following app:
> Commons Daemon Service Runner
> C:\red5401\amd64\prunsrv.exe
>
>
>
--
WBR
Maxim aka solomax