Approach 1: Changing Context Root Path after the installation using the Installer

  1. Install Quantum Fabric using the Installer.

    IMPORTANT: During Quantum Fabric installation or after installation is completed, you should not configure details in the Administrator Account Configuration window.

  2. Rename the war files for required components.
  • For Tomcat standalone and JBoss standalone modes, rename the WARs directly from proper install location.
  • For WebLogic and WebSphere, and JBoss domain mode, follow these steps to rename WARs:
    1. Rename the required WARs from the installation location.
    2. Go to Console.
    3. Delete WARs for those you have renamed.
    4. Redeploy the renamed WARs to the Console.

    The following table details the list of installed WAR files and installation locations for Quantum Fabric Components:

    ComponentFile NameRenamed WAR files Path for installed WAR files for Quantum Fabric

     

    Console

    workspace.war

    		workspace1.war
    • Tomcat (standalone mode): <Quantum Fabric Install Path>\tomcat\webapps

     

    • JBoss (standalone mode): <Quantum Fabric Install Path>\jboss > standalone\deployments

     

    mfconsole.war

    		mfconsole1.war
    accounts.waraccounts1.war
    IdentityauthService.warauthService1.war

    Integration/
    Admin/
    Server

    • middleware.war
    • services.war
    • admin.war
    • middleware1.war
    • services1.war
    • admin1.war
    Engagement Serviceskpns.warkpns1.war
  1. Update WAAS_BASE_URL in the  accounts_configurations table by using the following SQL query:

    For example, <prefix>mfaccountsdb<suffix>.

    Sample query for UPDATE STATEMENT:

    • MySQL

      UPDATE accounts_configurations SET value='<http or https>://<server_host>:<server_port>/workspace1' WHERE name='WAAS_BASE_URL';

    • Oracle

      UPDATE accounts_configurations SET value='<http or https>://<server_host>:<server_port>/workspace1' WHERE name='WAAS_BASE_URL' ;

    • SQL Server

      UPDATE accounts_configurations SET value='<http or https>://<server_host>:<server_port>/workspace1' WHERE name='WAAS_BASE_URL' ;

  2. Open the renamed mfconsole1.war and do the following:
    1. Update the following property in the config.properties file:

      • KONY_ACCOUNT_API_BASE_URL=<http or https>://<server_host>:<server_port>/accounts1/api/v1_0/

        The location for config.properties: mfconsole1.war\WEB-INF\classes

        NOTE: A WAR file location varies based on an app server - for example, for Tomcat, WARs are found at <INSTALL_DIR>\tomcat\webapps.

    2. Add the following properties in the config.properties file:

      • KONY_ACCOUNTS_HEALTHCHECK_URL=<http or https>://<server_host>:<server_port>/accounts1/health_check

      • KONY_WORKSPACE_HEALTHCHECK_URL=<http or https>://<server_host>:<server_port>/workspace1/api/v1/healthcheck

  3. Update the following property in the KONY_SERVER_SERVICES_CONTEXT_PATH in the admindb configuration table:

    KONY_SERVER_SERVICES_CONTEXT_PATH=services1

    For example, <prefix>admindb<suffix>.

    Sample query for UPDATE STATEMENT:

    • MySQL

      UPDATE server_configuration SET prop_value ='services1' WHERE prop_name = 'KONY_SERVER_SERVICES_CONTEXT_PATH';

    • Oracle

      UPDATE server_configuration SET prop_value ='services1' WHERE prop_name = 'KONY_SERVER_SERVICES_CONTEXT_PATH';

    • SQL Server

      UPDATE server_configuration SET prop_value ='services1' WHERE prop_name = 'KONY_SERVER_SERVICES_CONTEXT_PATH';

  4. Configure the following settings for application server, as follows:
    • For Tomcat: In case you have renamed a .war, modify the following datasource file names as per the respective renamed war files:

      Path for datasource files:

      <INSTALL_DIR>\<App_Server>\conf\Catalina\localhost

      • Rename accounts.xml to account1.xml
      • Rename workspace.xml to workspace1.xml
      • Rename authService.xml to authService1.xml
      • Rename admin.xml to admin1.xml

       

    • For JBoss, update services.war\WEB-INF\jboss-web.xml with the new services war name.

      For example, if services is renamed to services1 then services1.war\WEB-INF\jboss-web.xml

      From:

      <context-root>/services</context-root>

      To:

      <context-root>/services1</context-root>

  5. Restart your app server.

  6. Launch Quantum Fabric Console with new context path and do the registration using the new auth service URL format:
    <http or https>://<server_host>:<server_port>/<new mfconsole context path>

    For example: <http or https>://<server_host>:<server_port>/<mfconsole1>

    NOTE:  You will need to launch Quantum Fabric through a browser and complete the registration for the context based root instance.
    For more details, refer to How to Get Started With Quantum Fabric Console.

    NOTE: After you complete registration, you can now also launch a context based root Quantum Fabric through Visualizer Enterprise. Refer to Access Quantum Fabric Instance through Visualizer Enterprise.

  7. After you logged in to Console, create an environment with the new URLs.

    To create server feature with new context path, the URL format is: <http or https>://<server_host>:<server_port>/<new admin context path>

    If admin is renamed to admin1 then the sample URL format is as follows:

    <http or https>://<server_host>:<server_port>/admin1

  8. Update service_url after an environment is registered in the accountsdb table, as follows:

    Sample query for UPDATE STATEMENT (for MySQL/Oracle/MSSQL):

    • UPDATE features SET service_url = ‘<http or https>://<server_host>:<server_port>/adminservices1’ WHERE type = 'server';

    • UPDATE features SET service_url = ‘<http or https>://<server_host>:<server_port>/kpns1’ WHERE type = 'kpns';

    NOTE: You can now use Quantum Fabric Console with new context paths for your app development.

  9. Create an app in Quantum Fabric Console.
  10. Publish the app.