Re-Hosting ConsoleWorks - OpenVMS
From TDiWiki
Points on Migrating / Rehosting ConsoleWorks 3.5 from ConsoleWorks 2 on OpenVMS
- Read the Install guide for version 3.5-0u0
- Get a good file system backup of the v2 server as a failsafe.
- Install configure, stabilize OVMS version 8.3 on the new server
- Install your CW Licenses on the new server
- Install CW version 3.5 on the new server
- Create an Invocation of the same name as was on the 2.x machine
- Disable all consoles on the CW Version 2.0 server
- On the v2 server, verify and or change Server Host Address: to 0.0.0.0 It can be found on the >Admin Configure Server page.
(This way it will listen for CW requests on all installed NIC's. You can change to an actual IP, or DNS host name once CW is running satisfactorily)
- Copy the CW <invocation_specific> directory structure from CW ver 2 to the new server
- Run the CW provided upgrade script to convert the CW settings to version 3 on the new server (@CONWRKS_UPGRADE)
- Copy required logs to the new server
- Modify the log location logical as needed
- Start the new invocation of ConsoleWorks 3.5-0u0
- Re-enable all consoles on the CW 3.5 server.
- Your users will need to change their passwords at first login due to the new security model
- Register ConsoleWorks on the new server
-- SSL Considerations --
Before the change, login via your browser and go to the menu item for Admin > Server > Configure. If the Require SSL Connections is set to Yes, you should set it to No for the move and any subsequent testing, until you are comfortable that all is well.
If you are using SSL, and the server certificate was created using the IP address as opposed to the host name, and you're not going to re-use the same IP address, then a new cert needs to be created. (Creating the SSL cert is detailed in the installation guide.) You should create a new cert using the host name.
Also on the SSL front, if you do need to create a new server cert, then your users will need to click Download > Local > SSL Certificate from within their browsers after the new server is up and running.
