Skip to main content
Waters

How to reconfigure NuGenesis SDMS/LMS servers for a new server hostname or domain name - WKB59256

Article number: 59256

OBJECTIVE or GOAL

Reconfigure NuGenesis applications for a new server name and/or domain name.  Please note that a domain name change for a NuGenesis server will require NuGenesis configuration changes only if the configurations use fully-qualified domain names for the server names, such as "sdmsserver.domain.com" rather than "sdmsserver".  This article lists all of the NuGenesis system components where a configuration change will be required for a hostname change, and potentially for a domain name change.

ENVIRONMENT

  • NuGenesis 9
  • NuGenesis 8

PROCEDURE

  • Oracle database:
    1. Update listener.ora and tnsnames.ora with the new hostname/domain:
      • ORACLE_HOME\sdms\network\admin\listener.ora
      • ORACLE_HOME\sdms\network\admin\tnsnames.ora
    2. Start or restart the Oracle TNS Listener service
    3. Open a command prompt and use the tnsping tool to verify connectivity to the SDMS and SLIM database instances (assuming the default service names for a NuGenesis installation):
      • tnsping.exe SDMS
      • tnsping.exe SLIM
    4. If using SDMS VISION links in LMS Documents, contact Waters Global Service and Support for a script that can be utilized to update these links to the new SDMS VISION FQDN
  • LMS JBOSS server:
    1. Run the NuGenesis LMS Server Configuration tool on the server's desktop or the start screen.
      • Do not run this tool with "Run as Administrator"; it will not start when invoked this way. Rather, change the permissions on the Drive:\WatersLMSServer folder tree so that the logged-in user has read and write permissions on the files in that folder
    2. On the Database Connection tab, change the Host to the new hostname/domain name
    3. Click the Data Sources line. If there are any data sources that connect to this server (say, ConnectorsDS), update those entries with the new hostname/domain name
    4. Click Apply and OK
    5. (If LDAPs is used and domain name was changed) Import new SSL certificates into the LMS certificate store to facilitate LDAPs authentication
  • LMS Web server:
    1. Edit the file Drive:\inetpub\wwwroot\WatersLMS\resources\qdis_db.en.resx in Notepad
    2. Change all instances of the old hostname to the new hostname.
    3. Save and close the file.
    4. Update SSL Certificates for any applicable SampleShare HTTPs Bindings (typically certificates are issued to the FQDN and as such need to be reissued to the new hostname or domain)
    5. Open IIS Manager (inetmgr), and select the sites optoin under the Server name on the left Frame.
    6. Select Default Web Site, select Bindings, and update the binding to use the newly issued SSL certificates
    7. Save the changes and restart IIS
  • LMS client:
    1. Edit the file Drive:\Program Files (x86)\Waters\NuGenesis LMS\eln.exe.config.
    2. Change all instances of the old hostname to the new hostname.
    3. Save and close the file.
    4. Log into the LMS Client
    5. Select Administration, followed by System Configuration
    6. Browse to External systems --> NuGenesis SDMS, and update the URL as required to reflect the new SDMS Web Application hostname and domain
    7. If a domain change was required, browse to External systems --> LDAP Server and update the LDAP settings as required
    8. Select OK to save and close the LMS Client
  • SDMS Oracle client:
    1. Run the Waters Net Configuration Assistant from the start menu or screen.
    2. Change all instances of the old hostname to the new hostname.
    3. Save and close the config assistant.
  • SDMS web server:
    • Legacy WebVision and AuditTrail sites:
      1. Edit the WebVision.ini file:
        • NuGenesis 8 path: Drive:\Program Files (x86)\apache-tomcat-6.0.29\webapps\WebVision\ngvision\WebVision.ini
        • NuGenesis 9 path: Drive:\Program Files (x86)\Waters\apache-tomcat-9.0.8\webapps\WebVision\ngvision\WebVision.ini
      2. Change all instances of the old hostname to the new hostname
      3. Save and close WebVision.ini
    • New Audit Trail site (versions 9.1 and later):
      1. Edit the envConfig.json file: Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\AuditTrail\ClientApp\assets\config\envConfig.json
      2. Update the hostname and domain as required
      3. Save and close envConfig.json
      4. Edit the appsettings.json file and update it's "WithOrigins" setting per article WKB258801
      5. Save and close appsettings.json
    • New WebVision site (versions 9.3 and later):
      1. Edit the envConfig.json file: Drive:\Program Files (x86)\Waters\NGSDMS\Application Server\Vision\SdmsVision\assets\config\envConfig.json
      2. Update the hostname and domain as required
      3. Save and close envConfig.json
      4. Edit the four appsettings.json files and update it's "WithOrigins" setting per article WKB258801
      5. Save and close appsettings.json
    • Changes in IIS Manager:
      1. Update SSL Certificates for HTTPS Bindings (typically certificates are issued to the FQDN and as such need to be reissued to the new hostname or domain)
      2. Open IIS Manager (inetmgr), and select the sites option under the Server name on the left Frame.
      3. For each of the following, select the site, and then select Bindings, and update the binding to use the newly issued SSL certificates
        • Default Web Site
        • (as of version 9.1+) AuditTrailClientApp
        • (as of version 9.1+) AuditTrailWebServer
        • (as of version 9.3+) SdmsVision
        • (as of version 9.3+) SdmsProjects
        • (as of version 9.3+) SdmsProjectServers
        • (as of version 9.3+) SdmsIdentity
        • (as of version 9.3+) SdmsUserPreferences
      4. Select OK
      5. URL Rewrite rules:
        1. At the server level, double-click URL Rewrite and double-click the "AuditTrailRedirectRule"
        2. Edit the condition "{HTTP_HOST}"
        3. Set the new domain name in the pattern; ex: ^.*\.domain\.com
        4. Click OK
        5. Set the Action URL to the new hostname/domain
        6. Click the apply button
        7. Do the same steps as above for the "VisionRedirectRule"
      6. Select Default Web Site, and select Authentication
      7. If a domain change was required, double-click Anonymous Authentication. If The RPC Service Account is being used, change the Specific user field to the new RPC Service Account. Otherwise, verify that pass-through authentication is used.
      8. Select the Managed Storage Site, and double-click Authentication
      9. If a domain change was required, double-click Basic Authentication. If The RPC Service Account is being used, change the Specific user field to the new RPC Service Account
      10. Double-click FTP Authorization
      11. If a domain change was required, double click the single Authorization rule And change the Specified user to the new RPC Service Account.
      12. Select OK
      13. Restart IIS
    • Update UNIFYWeb.ini:
      1. Open the UNIFYWeb.ini file located in the ftproot, typically C:\inetpub\ftproot
      2. Update the IPAddress section to reflect the new hostname
      3. Save and close UNIFYWeb.ini
    • Update SDMS Administrator:
      1. Log in to SDMS Administrator
      2. Right-click the Master List and click Properties
      3. Change the WebVision server name to the new hostname
      4. Click OK
  • LMS Document Creator:
    1. Run the NuGenesis LMS Document Service Configuration program on the Start screen as Administrator.
    2. Change all instances of the old hostname to the new hostname.
    3. Click OK to save the configuration and restart the Document Creator service.
  • LMS Smart Builder:
    1. Run the Configure NuGenesis LMS Smart Builder program on the Start screen as Administrator
    2. Change all instances of the old hostname/domain to the new hostname/domain
    3. Click OK to save the configuration
  • SDMS File Capture Server
    1. If domain change was required, ensure all SMB Share Permissions for scan lines in SDMS File Capture Templates are configured with the new NuGenesis RPC Service Account 
    2. If a domain change was required, open the Windws Services Management Console (services.msc)
    3. Stop the NuGenesis RPC Service and update to use the new NuGenesis RPC Service Account credentials
    4. Start the NuGenesis RPC Service
  • Waters System Monitor
    • Replace hostname / DNS suffix in the appropriate .config files, such as <Drive>:\Program Files (x86)\Waters\WSM SDMS Agent Service\WSM.SDMSAgent.exe.config (SDMS Agent Service in this case)
    • Replace hostname / DNS suffix in <drive>:\inetpub\wwwroot\WatersSystemMonitor\web.config in the "WEB_SERVICE_URL" and "SDMS_SDK_URL" entries
  • Waters Database Manager (as of 9.3+)
    1. If a domain change was required or the database server name was changed, and a local account is used by WDM, update the username and password used. Or, change the configuration to use a current domain login such as the NuGenesis RPC Service account.
    2. Ensure that the user configured in WDM is a member of the Backup Operators user group in windows.
    3. Ensure that the user configured in WDM has been granted the Log on as a batch job right under the Local Security Policy.
  • General
    1. If a domain change was required, ensure that any batch files running in Windows Scheduler that are using the RPC Service Account are updated to use the new RPC Service Account.

ADDITIONAL INFORMATION

 

id59256, isopropanol, NGLMS, NGLMSLIC, NGLMSOPT, SDMS, SDMS8, SDMS8NU, SUPISDMS, SUPNG

Not able to find a solution? Click here to request help.