C2090-623 Questions and Answers

The method for performing a UDA trace is different in Cognos 10 to previous versions due to the removal of the Cognos Logging Console Program. This is specific to CQM datasources.

Please follow these steps:

• Navigate to /configuration
• Rename ipfUDAclientconfig.xml.sample it to ipfclientconfig.xml
• Wait 30 seconds
• Now run any reports that you wish to use the trace on.
• After running the reports the trace will generate a file named "UDA_Trace.log" within /logs. The log name and location can be changed by the user by editing the ipfclientconfig.xml file.
• Rename ipfclientconfig.xml to ipfUDAclientconfig.xml.sample to turn off the tracing.

This trace records all database activity so should be turned off as soon as the possible.

References: http://www-01.ibm.com/support/docview.wss?uid=swg21620597

You can specify if configuration objects and their children are included as part of deployment. By default, they are not included.

You can change the default setting using the advanced setting CM.DEPLOYMENTINCLUDECONFIGURATION.

By default, it is set to False (do not include configuration objects in deployments).

To change the default to include configuration objects and their children, set it to True.

Before users can start working in Cognos LifeCycle Manager, you must start the Cognos LifeCycle Manager web application.

Procedure

Start the Cognos LifeCycle Manager server:

On a Microsoft Windows system, from the Start menu, click LCM Start.

You can also type the following command in a command prompt window, from the Cognos LifeCycle Manager install location. Depending on where Cognos LifeCycle Manager is installed, you might have to run the command prompt window as an administrator.

lcm_start.bat

On a Linux system, run the server start script

install_location/lcm_start.sh

Start the Cognos LifeCycle Manager web application:

On a Microsoft Windows system, from the Start menu, click LCM URI.

Type the following URL in your browser:

http://server_name:port_number/lcm_servlet/app/main

Increase Asynchronous Timeout in High User Load Environments.

If you have a high user load (over 165 users) and interactive reports are running continuously in a distributed installation, you may want to increase the asynchronous timeout setting to avoid getting error messages. The default is 30000.

To resolve this problem, increase the wait timeout.

Procedure

• Go to the following directory:
• install_locationwebapps/p2pd/WEB-INF/services/.
• Open the reportservice.xml file in a text editor.
• Change the async_wait_timeout_ms parameter to 120000.
• Save the file.
• Restart the service.

References: https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.inst_cr_winux.doc/t_increaseforhighendload.html