Info
Not all the questions on this page are directly related to Canvas deployment, e.g. questions on Oracle database. Some of these questions were asked by participants during the Canvas training sessions. We have answered those here for the larger benefit of the Canvas Developer community.

...

Expand

title	What are the changes to be done when context root of the application is changed?

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 As a sample reference, the following steps indicate the changes that are to be applied required for the JBoss app server and Oracle database environments. For other app server and database combinations, appropriate changes need to be appropriately applied to done in the relevant files in accordance with the modified changes.
Context Root changes

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

Code Block

language	xml

<context-root> <CONTEXT_ROOT> </context-root>
<!-- For example -->
<context-root> dliteweb </context-root>

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

Code Block

language	bash

{
	"contextRoot": "<CONTEXT_ROOT>",
	"applicationId": "MODELHOUSE",
	"displayName": "CTWEB",
	"isService": "Y"
}
# For example
{
	"contextRoot": "dliteweb",
	"applicationId": "MODELHOUSE",
	"displayName": "CTWEB",
	"isService": "Y"
}

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

Code Block

language	xml

DEFAULT_CONTEXT_ROOT=/<CONTEXT_ROOT>
ALL_CONTEXT_ROOTS=<CONTEXT_ROOT>
<!-- For example -->
DEFAULT_CONTEXT_ROOT=dliteweb
ALL_CONTEXT_ROOTS=dliteweb

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

Code Block

language	xml

SESSION_TIMEOUT_URL=/<CONTEXT_ROOT>/index.jsp 
CONTEXT_PATH=/<CONTEXT_ROOT>
<!-- For example -->
SESSION_TIMEOUT_URL=dliteweb/index.jsp 
CONTEXT_PATH=dliteweb

JNDI Data source name change

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

Code Block

language	xml

CT_FW_DATASOURCE=java:/<DATA_SOURCE_NAME>
CT_FW_FILEIMPORT_DATASOURCE=java:/<DATA_SOURCE_NAME>
<!-- For example -->
CT_FW_DATASOURCE=java:/DliteCTDS 
CT_FW_FILEIMPORT_DATASOURCE=java:/DliteCTDS

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

Code Block

language	xml

<datasource jndi-name="java:jboss/datasources/DliteCTDS<DATA_SOURCE_NAME>" pool-name="DliteCTDS<DATA_SOURCE_NAME>" 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>
      <driver>OracleJDBCDriver</driver>
  <security>
         <user-name><SCHEMA_NAME></user-name>
         <password><SCHEMA_NAME_PWD></password>
     </security>
</datasource>
<!-- For <security>example -->
<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>
     <user-name><SCHEMA_NAME></user-name>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
     <driver>OracleJDBCDriver</driver>
     <security>
         <password><SCHEMA_NAME_PWD></password><user-name>CT_MIG</user-name>
         <password>CT_MIG</password>
     </security>
</datasource>

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

Code Block

language	xml

<resource-ref>
   <res-ref-name>jdbc/CTwebCanvasDataSource</res-ref-name>
   <jndi-name>java:jboss/datasources/<DATA_SOURCE_NAME></jndi-name>
</resource-ref>
<!-- For example -->
<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 CtwebResource.jar folder (e.g. , in the ....\CtwebResources\src\main\resource\MyImplementationCtwebImplementation.properties’) file, specify the work folder and centralized work folder paths in CtwebImplementation.properties file, as shown in the following code snippet:

Code Block

language	xml

CT_WORK_FOLDER_PATH=<WORK_FOLDER>                
CT_WORK_CENTRALIZED_FOLDER_PATH=<WORK_FOLDER>   
<!-- For example -->
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 of the application in build.xml file, as shown in the following code snippet:

Code Block

language	xml

<property name="WAR_FILE_NAME" value="${DIST_ROOT}/<WAR_NAME>.war" />
<!-- For example -->
<property name="dliteweb" value="${DIST_ROOT}/dliteweb.war" />

Expand

title	Connection timeout issue while deploying application on JBOSS

Solution: Add following entry in the standalone.xml file:

Code Block

language	xml
linenumbers	true

<system-properties>
         <property name="jboss.as.management.blocking.timeout" value="600"/> 
  </system-properties>

Expand

title	Application deployment fails when setting up in a new environment

Check for the following pattern in the error logs:

Code Block

linenumbers	true

java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.ensureError(J9VMInternals.java:148)
at java.lang.J9VMInternals.recordInitializationFailure(J9VMInternals.java:137)
at io.bit3.jsass.Compiler.<init>(Compiler.java:40)
at com.intellectdesign.canvas.web.themes.ThemeConfig$CssConfig.convertScssFileToCssFie(ThemeConfig.java:817)

Solution: The SASS Java library does not support AIX operating system and hence the issue. This issue can be solved by performing the SASS compilation while generating the application WAR. Go through the following links to find samples of the ANT targets that must be included in the build file to perform the SASS compilation:

Expand

title	Getting Heap Space or Out of Memory error

Check for the following pattern in the error logs:

Code Block

linenumbers	true

java.lang.OutOfMemoryError: Java heap space

Solution: Increase the memory to at least 8 GB. If the OutOfMemoryError still occurs, generate periodic heap dumps and analyse whether the heap usage is increasing.

Expand

title	Application is not getting deployed

Check for the following pattern in the error logs:

Code Block

linenumbers	true

SEVERE: [com.intellectdesign.canvas.config.ConfigurationManager] [CTCOM00095] : Error while initializing configuration

Solution: This pattern will be present in the CanvasConfig_<yyyyMMddkkmmss>_<appServerName>_<applicationName> in case there is an error while initializing the configuration required for CT. At the end of the stack trace check the root cause mentioned in the “Caused by: " section.

Expand

title	Instead of updating the CanvasApplicationContext.json file, update web.xml in the 19.1.7.11 19679 revision and above.

If the latest release revision is 19.1.7.11 19679 and above, refer to the following steps:

Perform the following steps to use the CT release as-is without the need to update the CanvasApplicationContext.json file in the CTResources.jar.

Update web.xml in the application WAR.

Example, File Location: ...\webapps\ctmodelhouse\WEB-INF\web.xml

The following snippet provides the sample values of the necessary elements and attributes that are to be configured within web.xml.

Code Block
<context-param> <param-name>appId</param-name> <param-value>MODELHOUSE</param-value> </context-param>

Note
The param name should remain unchanged. Only "appId" should be used.

If the context-param attribute is already present in the web.xml for a different param-name, the new context-param attribute has to be added after that to configure the value of appId.

Refer to the following snippet for sample values of the necessary elements and attributes that are to be configured within web.xml.

Code Block

<context-param>
<param-name>ModelHouseInitializeBundle</param-name>
<param-value>MyImplementation</param-value>
</context-param>
<context-param>
<param-name>appId</param-name>
<param-value>MODELHOUSE</param-value>
</context-param>

Version	Old Version 19	New Version Current
Changes made by	Lakshminarayanan1 S CTOO (Unlicensed)	DevaDarshini.S
Saved on	Jul 09, 2020	Sept 11, 2023

Versions Compared

Key

JNDI Data source name change

Work Folder Changes

Page Comparison

Versions Compared

Key

JNDI Data source name change

Work Folder Changes