Moving ConsoleWorks from one Platform to Another

From TDiWiki

Jump to: navigation, search

Moving ConsoleWorks from one Platform to Another

  • 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 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
  • Examine all locally defined action scripts and rewrite in the native scripting language of the target system, placing the new scripts in the correct directory on the new system
  • If you are using ssh under Pseudo-Consoles, examine the connection scripts and rewrite in the natvie scripting language of the target system, placing the new scripts in the correct directory on the new system
  • 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)
  • Perform a ConsoleWorks backup on the old system
  • Restart the old ConsoleWorks server while you complete the rest of the steps and test
  • Copy required logs to the new server. Be aware that if you are moving from OpenVMS to any other platform, the version numbers on log files need to be stripped during the copy. Some ftp systems do NOT do this and this will create problems on your new invocation.
  • Modify the log location logical, registry entry or environment variable as needed
  • Start the new invocation of ConsoleWorks on the new host
  • Restore the configuration from the backup you made earlier
  • Using XML-export, export all the Consoles and Events. Then use a text editor to search for all the action scripts and pseudo-console connection scripts you identified earler and replace those with the new ones that you have created.
  • Import the corrected XML using the "replace" selection and selecting "fix log dir" as well
  • Re-enable selected consoles on the new host for testing. When satisfied that things are correct, shutdown the old server and enable all console on the new server.
  • 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/Moving_ConsoleWorks_from_one_Platform_to_Another"
Personal tools