Let’s assume that the following are the details of the application: 

• DATA_SOURCE_NAME : DliteCTDS
• SCHEMA_NAME : CT_MIG
• SCHEMA_NAME_PWD : CT_MIG
• CONTEXT_ROOT : dliteweb
• WAR_NAME : dliteweb
• WORK_FOLDER : D:/Canvas19/dliteweb

The following steps indicate the changes that are to be applied for the JBoss app server and Oracle database environments. For other app server and database combinations, changes need to be appropriately applied to the relevant files in accordance with the modified changes. 
Context Root changes

1. In the application WAR JBoss folder (e.g. 'WEB-INF\jboss-web.xml’), specify the context root in the jboss-web.xml file, as shown in the following code snippet:

<context-root> dliteweb </context-root>

2. In the CTResources.jar folder (e.g. ‘Ctweb\Dependencies\Canvas\CTResources.jar\CanvasApplicationContext.json’), specify the context root in CanvasApplicationContext.json file, as shown in the following code snippet:

{
	"contextRoot": "dliteweb",
	"applicationId": "MODELHOUSE",
	"displayName": "CTWEB",
	"isService": "Y"
}

3. In the application Resource.jar folder (e.g. ‘Ctweb\CtwebResources\src\main\resource\Ctwebsecurityconfig.properties’), specify the default context root in Ctwebsecurityconfig.properties file, as shown in the following code snippet: 

DEFAULT_CONTEXT_ROOT=dliteweb
ALL_CONTEXT_ROOTS=dliteweb

4. In the application Resource.jar folder (e.g. ‘Ctweb\CTWebResources\src\main\resource\ctwebexportconfig.properties’), specify the context root as the context path in Ctwebexportconfig.properties file, as shown in the following code snippet:

SESSION_TIMEOUT_URL=dliteweb/index.jsp 
CONTEXT_PATH=dliteweb

JNDI Data source name change

1. In the application Resource.jar folder (e.g. ‘CtwebResources\src\main\resource\databaseconfig.properties’), specify the JNDI data source name in ctwebdatabaseconfigCtwebdatabaseconfig.properties file, as shown in the following code snippet:

CT_FW_DATASOURCE =java:/DliteCTDS 
CT_FW_FILEIMPORT_DATASOURCE=java:/DliteCTDS

2. In the  (e.g. 'standalone\configuration\standalone.xml’), specify the JNDI data source name in standalone.xml file, as shown in the following code snippet:

<datasource jndi-name="java:jboss/datasources/DliteCTDS" pool-name="DliteCTDS" enabled="true">
            <connection-url>jdbc:oracle:thin:@10.12.25.28:1521:SIR13714</connection-url>
            <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
            <driver>OracleJDBCDriver</driver>
            <security>
                <user-name><SCHEMA_NAME></user-name>
                <password><SCHEMA_NAME_PWD></password>
            </security>
</datasource>

3. In the the application WAR JBoss folder (e.g. 'standalone\deployments\ctmodelhouse.war \WEB-INF\jboss-web.xml’), specify the JNDI data source name in the jboss-web.xml file, as shown in the following code snippet:

<resource-ref>
            <res-ref-name>jdbc/CTwebCanvasDataSource</res-ref-name>
            <jndi-name>java:jboss/datasources/DliteCTDS</jndi-name>
</resource-ref>

Work Folder Changes

1. In the application Resource.jar folder (e.g. CtwebResources\src\main\resource\MyImplementation.properties’), specify the work folder and centralized work folder paths in CtwebImplementation.properties file, as shown in the following code snippet:

CT_WORK_FOLDER_PATH=D:/Canvas19/dliteweb                
CT_WORK_CENTRALIZED_FOLDER_PATH=D:/Canvas19/dliteweb   

2. Specify the Web Application Resource (WAR) file name in build.xml file, as shown in the following code snippet: 

<property name="dliteweb" value="${DIST_ROOT}/dliteweb.war" />