The steps of the was release version:
actual use:
1. Backup application (war package under the backup application, tar -czvf app.20200418.tar.gz app.war)
2. Stop service (was console stop, convenient)
3. Replace The version file (the red entity fork prompt stops, indicating that it has been stopped, and then replace the version file in this state)
4. Check the firewall status (service firewalld status, not enabled, or add an exception to prevent the connection from starting when the service is started On the database server, etc.)
5. Start the service (was console is stopped, convenient), monitor logs
6. Log in to the system and click the relevant functions modified by the version. (Ensure that the system can log in normally after the version is updated. Simply click to test the relevant functions of the version, and also determine whether the deployed version is effective. When deploying with weblogic before, the deployed version often fails to work.)
Recommended specifications: (deploy using the Was console)
1.
Export the ear package from the backup application (when the version is rolled back, update or install and deploy, it takes a long time)
2. Stop the service
3. Replace the version file (the red entity fork prompt stops, Indicates that it is stopped, and then replace the version file in this state)
4. Check the firewall status (service firewalld status, not enabled, or add an exception to prevent the service from being connected to the database server, etc.)
5. Start the service, Monitoring log
6. Log in to the system and click on the relevant functions modified by the version. (Ensure that the system can log in normally after the version is updated. Simply click to test the relevant functions of the version, and also determine whether the deployed version is effective. When deploying with weblogic before, the deployed version often fails to work.)