Re-Hosting ConsoleWorks - OpenVMS to OpenVMS ConsoleWorks 3.x

From TDiWiki

Jump to: navigation, search

Re-Hosting ConsoleWorks - OpenVMS to OpenVMS ConsoleWorks 3.x (Alpha / Itanium)


(This document assumes the user will be upgrading ConsoleWorks to the most current release on the new host at the time of re*hosting as we have found this to be the case most often.)

  • Read the Install guide for the version of ConsoleWorks that you will be moving to
  • Get a good file system backup of the “old” server as a failsafe.
  • Install configure, stabilize OVMS on the new server
  • Be sure the appropriate patchs are installed for the version of OpenVMS you'll be using
  • Install your ConsoleWorks Licenses on the new server
  • Install ConsoleWorks on the new server
  • Create an Invocation of the same name as was on the “older” machine
  • Disable all consoles on the “older” ConsoleWorks Server
  • On the “older” server, verify and or change Server Host Address: to 0.0.0.0 It can be found on the >Admin >Server >Configure page. (This way it will listen for ConsoleWorks requests on all installed NIC's. You can change to an actual IP, or DNS host name once ConsoleWorks is running satisfactorily)
  • Copy the ConsoleWorks <invocation_specific> directory structure from the “older” ConsoleWorks to the new server
  • On the new ConsoleWorks system, run the provided upgrade script to convert the invocation specific ConsoleWorks settings to the newer version (@CONWRKS_UPGRADE) For versions of ConsoleWorks being re-hosted with databases prior to version 3.7, this is a mandatory requirement.
  • Copy required logs to the new server
  • Modify the log location logical as needed
  • Start the new invocation of ConsoleWorks on the new host
  • Re-enable all consoles on the new host
  • If upgrading from ConsoleWorks versions earlier than V3.0, 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 stopping the "older" system 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 certificate needs to be created. (Creating the SSL certificate is detailed in the installation guide.) You should create a new certificate using the host name. Also on SSL invocations, if you do need to create a new server certificate, then your users will need to click Download > Local > SSL Certificate from within their browsers after the new server is up and running.

Retrieved from "http://wiki.tditx.com/index.php/Re-Hosting_ConsoleWorks_-_OpenVMS_to_OpenVMS_ConsoleWorks_3.x"
Personal tools