Move to new server

In this article

    When you move SuperOffice CRM Server there are essentially several parts that may have to be moved.

    Depending on what should be moved there are different steps to take into consideration.

    SuperOffice Program files

    Make sure you have the document archive available as a share and set up the ODBC datasource to connect to the existing SuperOffice database, this will ensure that the SuperOffice windows client installer is set up correct after you have installed the new CRM server. Then run the SuperOffice Server installer on your new server.

    Install prerequisites on this computer if needed.

    Run Install the SuperOffice CRM Server

    Choose correct location and when asked to Select ODBC datasource you pick the one that points to your production database. The server setup will notice that this is an existing database and tell you that it will be used "As is".

    SuperOffice document archive (so_arc)

    Use file copy to copy the so_arc with subfolders from old location to the new location. The new location must be updated in both SuperOffice.ini and web.config so both SuperOffice windows clients and web clients will keep access to their documents and templates. 

    SuperOffice database on Microsoft SQL Server or Oracle

    If you have access to both the new and the old database server then using DBsetup to rebuild the database from old to new datasource is the fastes option.

    If you do not have access to the new database server from the old database server, then you may export the database as an SDA file from DBSetup on the old server and use DBSetup to import the SDA file.

    SuperOffice Win clients must be updated

    ! If you just change the name/address:
    You will then need to refresh SuperOffice.mst file with the new server information

    • Navigate to the SuperOffice server folder.
    • Run the SoCreateMST.exe (C:\[SuperOffice Server_adress]\)
    • Press [Load file]
    • Navigate to SuperOffice.mst package (SuperOffice.mst file can be found in the "Client" folder on the server: C:\[SuperOffice Server_adress]\Client\SuperOffice.mst)
    • Save the new. Mst file

    All clients must be uninstalled, then run SuperOffice8.exe from the server\client folder

    SuperOffice Web and SuperOffice Web services / NetServer

    Run SuperOffice Product configuration and update the information either for the Database settings or Document Archive.

    Make sure you update the database settings correct  Make sure you update the document archive settings correct

    Service

    Download and run the SuperOffice.CustomerService.exe to install on the new server. Do NOT run ejTermSetup.exe since you already have Service installed.

    Download and install SuperOffice Web services / Netserver which is the second option when installing SuperOffice Web client. This is used by Service to connect to the database.

    Stop the current Service and the eJournal schedule service running the old server. As an extra precaution, edit the config file in the program folder and type "frozen" on a separate line at the bottom. Service will stop working on the old site.

    You will need to manually change settings inside the database tables called Config and Registry.

    In the config table:

    make sure all paths are updated correctly to the new location: text_path, attachment_path, template_path and warning.
    Verify the correct URLs to cgi_url (the external URL) and cgi_url_internal.

    In the registry table:

    Reg_id = 131 Path to the DBI executable
    Reg_id = 284 Path to the ImageResizer executable
    Reg_id = 22 Path to the ejOutbox executable
    Reg_id = 1 Path to the ejSender executable
    Reg_id = 245 Path to the program which performs AD authentication
    Reg_id = 40 Path to the LogPath in Service
    Reg_id = 109 Path or URL to www folder, if Service is installed in a sub application called Service, then value here would be set to /Service/

     

     Changing hostname also

    1. In the Windows registry there is the key that is identical to the hostname that you are running Service on. Make sure it matches new hostname.  The key is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SuperOffice Customer Service.
    2. Edit the Service website hostname in IIS.
    3. Open the database, go to the config table, and edit all the fields containing the old hostname.
    4. Open the crontab.txt file, and edit locations containing the old hostname.

     

    Copy the Customer Service directory in the old environment over to the new environment. Under this directory you will by default find all of the directories that belong to Service, like attachments, templates and the Customer center.

    In the root directory you find a config file, open this in Notepad or another simple text editor. The dbDatabase points to the name of current ODBC source, create a new ODBC connection (32bit) on the new server with the same name that points to the SuperOffice database.

    Change or verify that the path in nsEndPoint points to the new Netserver Web service you set up above. Note: Service supports only http connection to Netserver, https is not supported.

    Remove "frozen" from config file, so Service will work again.

    Sometimes it may be advantageous to run C:\SuperOffice\Customer Service\bin\upgrade.exe -d <hostname> after this move.

    Inside the database there will be a lot of absolute URLs, pointing to attachments like pictures. To update the database you may run the following queries, replace oldUrl and newUrl with your paths.

     

    Remember to do a backup before you run queries directly on your database.

     

    update crm7.s_message set html_message = replace(html_message,'://oldurl.no','://new.url.no') where html_message like '%://oldurl.no%'
    update crm7.ej_message set html_body = replace(html_body,'://oldurl.no','://new.url.no') where html_body like '%://oldurl.no%'
    update crm7.ej_message set body = replace(body,'://oldurl.no','://new.url.no') where body like '%://oldurl.no%'
    update crm7.reply_template_body set body_html = replace(body_html,'://oldurl.no','://new.url.no') where body_html like '%://oldurl.no%'
    update crm7.ejuser set signature = replace(signature,'://oldurl.no','://new.url.no') where signature like '%://oldurl.no%'
    update crm7.ejscript set body = replace(body,'://oldurl.no','://new.url.no') where body like '%://oldurl.no%'
    update crm7.screen_definition_action set ejscript_body = replace(ejscript_body,'://oldurl.no','://new.url.no') where ejscript_body like '%://oldurl.no%'
    update crm7.KB_ENTRY set question = replace(question,'/scripts/customer.exe/getAttachment','/service/scripts/customer.exe/getAttachment') where question like '%/scripts/customer.exe/getAttachment%'
    update crm7.KB_ENTRY set answer = replace(answer,'/scripts/customer.exe/getAttachment','/service/scripts/customer.exe/getAttachment') where answer like '%/scripts/customer.exe/getAttachment%'

    Note the last 2 queries will set the current URLs in FAQ texts if Service have been moved manually to a service sub folder as described here. Make sure you use the correct extension, customer.fcgi or customer.exe.

     

    Links in eMarketing messages

    All the eMarketing messages sent out before the move will contain links pointing to the old site. There are 2 issues with it:

    • When sending out a link, it will have an absolute URL, for example: http://cs.mydomain.com/scripts/customer.fcgi?action=... so if you move Service to another domain or subfolder, that URL will not be available any more.

      To prevent loss of images / attachments in the sent mailings you need to make a redirect on the IIS from the old site to the new hostname. This way images and attachment links are redirected just fine, so mailings don't look crippled in the mail client of the recipient.

    • Second issue is with tracked links. A tracked link (also including the unsubscribe link) contains a hashed string which is based on the Customer Center domain. Even if you set up a redirect to catch old URL's, then it will be executed by Service but it will fail on the hash test.

      A workaround is to leave the Customer Center on the old URL running, at least till the messages with the tracked links become irrelevant.