Versions Compared

Version Old Version 7 New Version Current
Changes made by

DevaDarshini.S

DevaDarshini.S

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Expand
titleCan the configuration to change the font size be turned off?

Not enabled as of now. It is always turned ON.

...

Expand
titleWhat to do when multiple notifications are sent instead of one?

Multiple emails get triggered even though only one entry in the table (OD_PENDING_MAIL) from where CT picks up records to be sent as email. In such cases refer these kind of errors found in the SystemOut.log (WebSphere log).

  • WTRN0006W: Transaction {0} has timed out after {1} seconds

    For example:

    Code Block
    languagepowershell
    WTRN0006W: Transaction 00000188D7CBD648000000455D953708CCA97D4013E3EDB45FD179E3597A7D478393378300000188D7CBD648000000455D953708CCA97D4013E3EDB45FD179E3597A7D478393378300000001 has timed out after 120 seconds

    Solution: Increase the total transaction lifetime timeout and maximum translation timeout in seconds. These settings can be updated through the WebSphere Application Server console, using Servers > Server Types > WebSphere application servers > server_name > [Container Settings] Container Services > Transaction Service

  • WTRN0037W: The transaction service encountered an error on an xa_recover operation. The resource was com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@1f5b7ee3. The error code was XAER_RMERR.

    Solution:
    Run the following commands as user SYS:

    Code Block
    languagebash
    grant select on pending_trans$ to <user>;
grant select on dba_2pc_pending to <user>;
grant select on dba_pending_transactions to <user>;
grant execute on dbms_system to <user>;  //If using Oracle 10.2.0.3 or lower JDBC driver
grant execute on dbms_xa to <user>; //If using Oracle 10.2.0.4 or higher JDBC driver

    In the above commands, <user> is the username configured in the Oracle datasource's authentication alias.

    Reference link : https://www.ibm.com/support/pages/exception-occurs-during-recovery-oracle-database-transactions


Expand
titleInstead 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.

  1. Update web.xml in Canvas Studio WAR

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>



Expand
titleWhat if file upload is not working for embedded Apache Tomcat?

The following snippet provides the sample values of the necessary elements that are to be configured within context.xml if file upload is not working for Sigma:

Code Block
<Context allowCasualMultipartParsing="true">