com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.

Accessing a Dashboard with a Hostname

Carryout the following configuration on the WSO2 Dashboard Server to be able to access a dashboard using a hostname or an IP address.

Step 1 - Change the default key store

  1. Open the <DS_HOME>/repository/conf/carbon.xml file.
  2. The private key is used for the HTTPS channel and for the token issuer to sign the issued tokens. 
    Update the following section of the carbon.xml to match your private key information.

    The private key must be available in a keystore of the "JKS" or "PKCS12" type. For more information, see KeyStore and Creating New Keystores.

    <!--
          Security configurations
         -->
        <Security>
            <!--
                KeyStore which will be used for encrypting/decrypting passwords
                and other sensitive information.
            -->
            <KeyStore>
                <!-- Keystore file location-->
                <Location>${carbon.home}/repository/resources/security/wso2carbon.jks</Location>
                <!-- Keystore type (JKS/PKCS12 etc.)-->
                <Type>JKS</Type>
                <!-- Keystore password-->
                <Password>wso2carbon</Password>
                <!-- Private Key alias-->
                <KeyAlias>wso2carbon</KeyAlias>
                <!-- Private Key password-->
                <KeyPassword>wso2carbon</KeyPassword>
            </KeyStore>
    
            <!--
               The directory under which all other KeyStore files will be stored
            -->
            <KeyStoresDir>${carbon.home}/repository/resources/security</KeyStoresDir>
        </Security>

Step 2 - Change the hostname

  1. Open the <DS_HOME>/repository/conf/carbon.xml file.
  2. Change the dashboard's hostname to match the "Common Name" of the certificate, which includes the private key.
    For example, if the common name is ds.wso2.com, update the configuration as follows:

    Example
    <!--
           Host name or IP address of the machine hosting this server
           e.g. www.wso2.org, 192.168.1.10
           This is will become part of the End Point Reference of the
           services deployed on this server instance.
        -->
        <HostName>ds.wso2.com</HostName>
        <!--
        Host name to be used for the Carbon management console
        -->
        <MgtHostName>ds.wso2.com</MgtHostName>
        <!--
            The URL of the back end server. This is where the admin services are hosted and
            will be used by the clients in the front end server.
            This is required only for the Front-end server. This is used when seperating BE server from FE server
           -->
        <ServerURL>local:/${carbon.context}/services/</ServerURL>

Step 3 - Configure the HTTP/HTTPS ports

  1. Open the <DS_HOME>/repository/conf/tomcat/catalina-server.xml file and configure the HTTP and HTTPS ports in the <connector> elements.

    Example
     <Connector  protocol="org.apache.coyote.http11.Http11NioProtocol"
                   port="9763"
                   ...
    />
    
    <Connector  protocol="org.apache.coyote.http11.Http11NioProtocol"
                   port="9443"
                   scheme="https"
                   ...
    />

Step 4 - Configure the Dashboard Designer

  1. Open the the <DS_HOME>/repository/deployment/server/jaggeryapps/portal/configs/designer.json file.
  2. Configure the following properties in the designer.json file. 
    For example, if the hostname is ds.wso2.com, update the properties in the designer.json as follows:

    Example
    "host": {
        "hostname": "ds.wso2.com",
        "port": "",
        "protocol": "https"
      }
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.