Steps to Enable CAS Log IBM IIS 11.3

-
Step 1 - Set the CC_MSG_LEVEL environment variable and restart ASBAgent
1. Make a backup of the dsenv file (typically located at /opt/IBM/InformationServer/Server/DSEngine/dsenv)
2. Edit the dsenv file, adding the following lines to the end of the file: CC_MSG_LEVEL=1; export CC_MSG_LEVEL
3. Source and export the dsenv file
4. Ensure no users are importing metadata, viewing data or testing connections (i.e. no design-time activities are on-going)
5. Restart the ASBAgent. To restart the agent:
     1. Become root
     2. cd /opt/IBM/InformationServer/ASBNode/bin
     3. Execute ". ./NodeAgents_env_DS.sh". Notice the period at the beginning.
     4. Execute "./NodeAgents.sh restart"
    
Step 2 - For IIS versions 11.3.0 or later
1. If your IIS version is 9.1.2 or earlier jump to step 6.
2. Become root on engine tier.
3. cd /opt/IBM/InformationServer/ASBNode/conf
4. Add the following 1 line at the tail of file asbagent-logging.properties com.ibm.iis.cas.level=ALL
5. The log file directory is /opt/IBM/InformationServer/ASBNode/logs
6. The Knowledge Center link is here: http://www-01.ibm.com/support/knowledgecenter/SSZJPZ_11.3.0/com.ibm.swg.im.iis.found.admin.common.doc/topics/t_configuring_asbagen_tloading.html

Step 3 - Remove CC_MSG_LEVEL from the environment and restart the ASBAgent
1. Remove the lines you added to the dsenv file.
2. Restart the ASBAgent using the steps above.

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more