How To Change Context Root In Weblogic Console

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

1. Install MobileFabric using the Installer.

   Important: During MobileFabric 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 MobileFabric Components:

  Component	File Name	Renamed WAR files	Path for installed WAR files for MobileFabric
  Console	workspace.war	workspace1.war	Tomcat (standalone mode): <MobileFabric Install Path>\tomcat\webapps JBoss (standalone mode): <MobileFabric Install Path>\jboss > standalone\deployments WebLogic: <UserInstallDirectory>\deployments WebSphere: <UserInstallDirectory>\deployments
  	mfconsole.war	mfconsole1.war
  	accounts.war	accounts1.war
  Identity	authService.war	authService1.war
  Integration/ Admin/ Server	middleware.war services.war admin.war	middleware1.war services1.war admin1.war
  Sync Services	syncconsole.war syncservice.war	syncconsole1.war syncservice1.war
  Engagement Services	kpns.war	kpns1.war

3. Update WAAS_BASE_URL in theaccounts_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' ;

   • DB2

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

4. 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>/acounts1/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

5. If Sync context path is renamed then update syncservice.context in the CONFIGURATION_MASTER table in syncconsoledb with new sync war syncservice1.

   For example, <prefix>syncconsoledb<suffix>.

   Sample query for UPDATE STATEMENT:

   • MySQL

     UPDATE CONFIGURATION_MASTER SET propValue='syncservice1' WHERE propName = 'syncservice.context';

   • Oracle

     UPDATE CONFIGURATION_MASTER SET propValue='syncservice1' WHERE propName = 'syncservice.context';

   • SQL Server

     UPDATE CONFIGURATION_MASTER SET propValue='syncservice1' WHERE propName = 'syncservice.context';

   • DB2

     UPDATE CONFIGURATION_MASTER SET propValue='syncservice1' WHERE propName = 'syncservice.context';

6. 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';

   • DB2

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

     Note: If the property does not exist, create KONY_SERVER_SERVICES_CONTEXT_PATH

7. 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
     • Rename syncconsole.xml to syncconsole1.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>

   • For WebLogic, update the new context path in the mfconsole1.war/WEB-INF/weblogic.xml with the new services war name.

     For example, If mfconsole is renamed to mfconsole1 then mfconsole1.war/WEB-INF/weblogic.xml

     From:

     <context-root>/mfconsole</context-root>

     To:

     <context-root>/mfconsole1</context-root>

   • For WebSphere, while deploying WARs to WebSphere, enter the context root values for renamed WARs as required.

     For more details on deployment of WARs in WebSphere, refer to Deploying WAR Files to WebSphere.

8. Restart your app server.

9. Launch MobileFabric 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 MobileFabric through a browser and complete the registration for the context based root instance.
   For more details, refer to How to Get Started With Kony MobileFabric Console.

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

10. 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

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

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

    • 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>/syncservice1' WHERE type = 'sync;
    • UPDATE features SET service_url = '<http or https>://<server_host>:<server_port>/kpns1' WHERE type = 'kpns';

    Note: You can now use MobileFabric Console with new context paths for your app development.

12. Create an app in MobileFabric Console.
13. Publish the app.

Copyright © 2014 Kony, Inc. All rights reserved.

How To Change Context Root In Weblogic Console

Source: https://docs.kony.com/7_3/konylibrary/mobilefabric/kony_mobilefabric_windows_install_guide/Content/ContextPath.htm

Posted by: resternits2000.blogspot.com

Share this post