Changing the Hostname

The following procedure explains how to change the hostname of DAS as required for your production environment. In this example, the hostname needs to be changed to node1.analytics.com.

1. Open the <DAS_HOME>/repository/conf/carbon.xml file and set the HostName property as shown below.

   <HostName>node1.analytics.com</HostName>

2. Open DAS_Home/repository/deployment/server/jaggeryapps/portal/configs/designer.json and change the hostname to the actual hostname of WSO2 IS Analytics. 

       },
       "host": {
           "hostname": "localhost",
           "port": "",
           "protocol": ""
       }

   This step avoids the host verification errors that can occur when another WSO2 product publishes statistics in WSO2 DAS.

3. Generate a key store by following the sub steps given below.
   1. Open a terminal and issue the following command to generate a key store.
      keytool -genkey -alias node1.analytics.com -keyalg RSA -keystore analyticsnode1.jks -keysize 2048
   2. Specify a preferred KeyStore password once prompted.
   3. Specify a preferred Key password once prompted.
   4. Enter the first name and last name as *.node1.analytics.com once prompted.
   5. Enter values for the other parameters as required. 
   Once this information is submitted, a key store is generated with a private key and a public certificate with node1.analytics.com as the CN.
4. Copy the generated self-signed key store (i.e., analyticsnode1.jks) to the <DAS_HOME>/repository/resources/security directory.
5. Export the public certificate from the keystore and import that certificate to the client­-truststore.jks file following the steps given below.
   1. Navigate to the <DAS_HOME>/repository/resources/security directory.
   2. Issue the following command to export the public certificate from the primary key store
      keytool -export -alias node1.analytics.com -file node1.analytics.com -keystore analyticsnode1.jks -storepass <keystore_password_given_above> 
   3. Issue the following command to import the certificate to the client­-truststore.jks file.
      keytool -import -alias node1.analytics.com -file node1.analytics.com -keystore client-truststore.jks -storepass wso2carbon