Connect Installation Directory = /opt/connect.install/kc
Starting with Connect 10r5, there is a new mechanism for installing patches. Instead of manually copying new files to each node in a deployment, you can deploy patches from the Deployment Editor in the UI.
- Navigate to the active deployment in the deployment editor. Go to the Machines sub-tab.
- In the Machines sub-tab, ensure that all machines are running. Then click Enable Flush. This command will checkpoint the system by forcing any storage log files on the nodes to be copied to the database.
- Refresh this page until the flushing status changes to completed (this can take a while). Once flushing is complete you can go ahead and stop all the nodes and shutdown the UI.
- Navigate to your Connect Installation Directory (usually on the Connect UI node)
- Delete the last backup kc folder (kc.backup) and rename the current kc folder to kc.backup
- Unpack the patch distribution into the Connect Installation Folder
- Restore the following files from kc.backup to /kc/import/brickstlicense.jar /kc/install.properties, /kc/cyrpto.properties, /kc/database.properties.
- Run /kc/install/updatedb and kc/install/seeddb to upgrade the database schema.
- Deploy the new brickst.war file in WAS/WildFly/JBoss.
- Start the new Connect UI.
- Navigate to your active deployment in the deployment editor.
- Run the Install Icon on each node (little arrow pointing to right in right most column). The Install command will copy the new Connect files to the deployed nodes and update the configuration files on each node.
- Continue to refresh this page until the install has completed. The Connect version should display the new Connect version when completed.
- Once all nodes have been completed, click on the "Commands" drop down menu and select "update deployment"
- Follow the commands on the screen except for running prepare.bat/sh since this step is only required for a NEW deployment.
- You can now start each one of the nodes. Once the nodes have started, click Disable Flush. The system should now be fully operational.
If you have multiple active deployments, you will need to perform step 2 and steps 8-10 for each active deployment.