Starting and stopping Cognos in UNIX without using the Cognos Configuration GUI

-

Problem(Abstract)

This document explains how to start and stop Cognos 8 services in Windows and UNIX without using the Cognos Configuration user interface, in much the same way as crnctl.sh works in IBM Cognos ReportNet. The crnctl.sh script was not included in Cognos 8, so that functionality is unavailable.

This information is also valid for Window installs of the Cognos 8 (as per below).

Resolving the problem

cogconfig.sh -s (cogconfig.bat -s for Windows)

This will save and start silently.

cogconfig.sh -stop (cogconfig.bat -stop for Windows)

This will stop silently.

To view log messages that were generated during an unattended configuration (and start), see the cogconfig_response.csv file in the c8_location/logs directory.

The cogconfig.sh -s applies the configuration settings specified in the local copy of cogstartup.xml, encrypts credentials, generates digital certificates, and if applicable, starts the Cognos 8 service or process.

Related information

Cognos Installation and Configuration Guide, Appendix A -> Starting and Stopping Cognos 8 in Silent Mode on UNIX and Linux Computers





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