Wednesday, July 2, 2014

What to do when domain name has changed

Background

There could be a reason that you have to move your OpenText Cordys environment to another domain. Now if this is the case you must realize that you have to make some changes in OpenText Cordys. On this page you will find more information about what you have to change and how to make these changes.
Please note that this page is only based on a non clustered environment and with the option "Disable Standalone Configuration" enabled.

Prerequisites

  • You must be administrator on the environment
  • You must have access to OpenText Cordys (authenticated user)
  • Database configuration must point to the hostname, localhost or 127.0.0.1.

1. Update hosts file

We have to temporary map the current IP address of the server to the 'old' Fully Qualified Domain Name (FQDN).
  • Get the IP address of the server via e.g. ipconfig:
    C:\Windows\system32>ipconfig
    Windows IP Configuration
    Ethernet adapter Local Area Connection:
       Connection-specific DNS Suffix  . : test.com
       Link-local IPv6 Address . . . . . : fe80::d57a:e4f:2b06:57db%13
       IPv4 Address. . . . . . . . . . . : 192.168.10.2
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
  • Open a text editor (run as administrator)
    • In the text editor open the 'hosts' file
    • Add the IP address and 'old' FQDN + hostname to this file, e.g. 192.168.10.2 cordysserver.test.com cordysserver:
    # localhost name resolution is handled within DNS itself.
    #   127.0.0.1       localhost
    #   ::1             localhost
    192.168.10.2 cordysserver.test.com cordysserver
  • Open a Command Prompt and check if the 'old' FQDN will be resolved (you can use ping command to achieve this, e.g: ping -a 10.1.52.1):
    C:\Windows\system32>ping -a 192.168.10.2
    Pinging cordysserver.test.com [192.168.10.2] with 32 bytes of data:
    Reply from 192.168.10.2: bytes=32 time<1ms TTL=128
    Reply from 192.168.10.2: bytes=32 time<1ms TTL=128
    Reply from 192.168.10.2: bytes=32 time<1ms TTL=128
2. Update Network Configuration
The network configuration must be switched from 'network enabled' to 'standalone enabled'. 
  • Open the Cordys Management Console (run as administrator)
  • Click on the option "Network Configuration"
  • Select the option 'Enable Standalone Configuration' and click on 'Save'
  • Now a popup box will be displayed with the message 'Standalone configuration enabled. CARS, Cordys Monitor and Webserver have to be restarted for the changes to take effect'.
  • Click on 'OK' to close this box.
Now lets check if the changes are implemented:
  • In CMC select the option 'Cordys Properties':
    • Check if the value of the 'bus.ldap.processor.host' property has been changed to '127.0.0.1'
    • Check if the property 'com.eibus.transport.groupmembership.udp.networkipaddress' with the value '127.0.0.1' has been set
  • Check in the Windows registry if the string value 'Urls' of the key 'HKEY_LOCAL_MACHINE\SOFTWARE\Cordys Systems\CARS\%INSTANCE_NAME%\Admin Repository Server' has been changed to  'ldaps://127.0.0.1:6366'.
Next step is to check if OpenText Cordys can still be started.

3. Restart OpenText Cordys

After making above changes you have to restart OpenText Cordys:
  • Stop the Application Pool (IIS), Cordys Monitor Service and Cordys Admin Repository Service.
  • Check if all OpenText Cordys JVMs and slapd process (CARS) have been stopped.   
  • Start the Cordys Admin Repository Service, the Cordys Monitor Service and Application Pool. 
  • Check if all the containers are started and that you can open a browser to the OpenText Cordys CUSP.
When there are no issues you can continue with the next step. If there are some issues, please check the log files located in <Cordys_root>\Log directory.

4. Revert changes

  First we have to revert the changes made in the hosts file. You can either remove the newly added line or comment it:
# localhost name resolution is handled within DNS itself.
#   127.0.0.1       localhost
#   ::1             localhost
# 192.168.10.2 cordysserver.test.com cordysserver
Now you can choose to leave the option "Enable Standalone Configuration" enabled or switch back to "Disable Standalone Configuration". Standalone option is recommend for laptop environments! 
If the Cordys Management Console is still open, please close it:
  • Open the Cordys Management Console (run as administrator)
  • Click on the option 'Network Configuration'
  • Select the option 'Disable Standalone Configuration'
  • In the 'Interface Display Name' the option 'Select Network Interface' must be selected. Click on 'Save'.
  • Now a popup box will be displayed with the message 'Standalone configuration disabled or Network Interface changed. CARS, Cordys Monitor and Webserver have to be restarted for the changes to take effect'.
  • Click on 'OK' to close this box.
Now lets check if the changes are implemented: 
  • In CMC select the option 'Cordys Properties':
    • Check if the value of the 'bus.ldap.processor.host' property has been changed to the FQDN
    • Check if the property 'com.eibus.transport.groupmembership.udp.networkipaddress' is removed
  • Check in the Windows registry if the string value 'Urls' of the key 'HKEY_LOCAL_MACHINE\SOFTWARE\Cordys Systems\CARS\%INSTANCE_NAME%\Admin Repository Server' has been changed to the FQDN, e.g 'ldaps://cordysserver.test.com:6366'.

5. Retrieve a new license key

The license key is still based on the 'old' FQDN. You have to contact OpenText Support and ask for a new license key (based on the new FQDN). After receiving the license key you have to make the following changes:
  • Open the Cordys Management Console (run as administrator)
  • Click on the option 'Content Management':
    • Provide the valid password in the Logon box and click on 'OK'
    • Open 'cn=licinfo,cn=cordys,cn=xxxx,o=xxxx'
    • Change the value of the attribute 'licensekey' with the new key and click on 'Save'.
  • Click on the option 'Cordys Properties':
    • Change the value of the property 'ldap.server' to the new FQDN, e.g. cordysserver.test.com:6366
After making above changes you have to restart OpenText Cordys:
  • Stop the Application Pool (IIS), Cordys Monitor Service and Cordys Admin Repository Service.
  • Check if all OpenText Cordys JVMs and slapd process (CARS) have been stopped.   
  • Start the Cordys Admin Repository Service, the Cordys Monitor Service and Application Pool. 
  • Check if all the containers are started and that you can open a browser to the OpenText Cordys CUSP.

Hope it helps...!!!!

Thanks & Regards,
Madhusudan Reddy K

posted by Madhusudan Reddy.K @ 11:56 AM   0 Comments