If you are unable to create a new account, please email support@bspsoftware.com

 

How to know the things under Environment section in cognos Configuration

Started by inu, 02 Nov 2014 07:40:36 AM

Previous topic - Next topic

inu

HI
When we open cognos configuration, we see three tabs as follows:-
Environment (Logging, Ibm Cognos Services)
Security (Authentication, Cryptography)
Data Access(Content manager, Notification)

when we expand Environment section --> Ibm cognos Services --> Ibm Cognos
In properties there are different attributes
[
Type
Ping timeout in seconds
Stop wait time in seconds
Maximum memory in MB
Shutdown port number

]
I want to know about these stuffs, how to know please tell me

Regards
Inam

MFGF

Quote from: inu on 02 Nov 2014 07:40:36 AM
HI
When we open cognos configuration, we see three tabs as follows:-
Environment (Logging, Ibm Cognos Services)
Security (Authentication, Cryptography)
Data Access(Content manager, Notification)

when we expand Environment section --> Ibm cognos Services --> Ibm Cognos
In properties there are different attributes
[
Type
Ping timeout in seconds
Stop wait time in seconds
Maximum memory in MB
Shutdown port number

]
I want to know about these stuffs, how to know please tell me

Regards
Inam

If you click on each of these in Cognos Configuration, there is a Notes section below the properties that describes what each one is. Have you read these notes? Is there something you're not understanding about them? Can you descibe which part in each is unclear so we know where you are struggling to understand?

What is the issue you are trying to solve? It may be that you are looking in the wrong place for what to change to fix the issue, but unless you tell us we can't know.

MF.
Meep!

inu

Quote from: MFGF on 02 Nov 2014 09:18:53 AM
If you click on each of these in Cognos Configuration, there is a Notes section below the properties that describes what each one is. Have you read these notes? Is there something you're not understanding about them? Can you descibe which part in each is unclear so we know where you are struggling to understand?

What is the issue you are trying to solve? It may be that you are looking in the wrong place for what to change to fix the issue, but unless you tell us we can't know.

MF.

Thanks MFGF,
As i read each property with its value in cognos configuration, but arising some questions in mind.
1. type=tomcat
As i know tomcat is a web server, but what is the use of tomcat in cognos, because i m using IIS server already, then why tomcat again,
Even mentioned over there, tomcat is by default, it cant be changed ,
Can you please elaborate it.

Cheers!
Inam

inu

Quote from: MFGF on 02 Nov 2014 09:18:53 AM
If you click on each of these in Cognos Configuration, there is a Notes section below the properties that describes what each one is. Have you read these notes? Is there something you're not understanding about them? Can you descibe which part in each is unclear so we know where you are struggling to understand?

What is the issue you are trying to solve? It may be that you are looking in the wrong place for what to change to fix the issue, but unless you tell us we can't know.

MF.

Thanks MFGF,
2.ping timeout in seconds= 240 (after the specified time interval process will be restarted)
    wait stop time in seconds= 60 (after this amount of time process will be stopped)
This is creaing confusion, if one process reached to "wait stop time=60" it will be stopped, then how the same process can reach to "ping timeout =240 seconds " if it has already been stopped, and how it will be restarted.

Little bit confusing, please MFGF , you r the critical resource in this community , clear my doubts.


Cheers!
Inam

MFGF

Quote from: inu on 02 Nov 2014 11:57:53 AM
Thanks MFGF,
As i read each property with its value in cognos configuration, but arising some questions in mind.
1. type=tomcat
As i know tomcat is a web server, but what is the use of tomcat in cognos, because i m using IIS server already, then why tomcat again,
Even mentioned over there, tomcat is by default, it cant be changed ,
Can you please elaborate it.

Cheers!
Inam

Tomcat can be used as a web server, true, but it's normal use is as a java-based application server. This is its use in Cognos 10. It provides the java servlet containers for the Content Manager and Application Server to run within. Tomcat is the default application server for Cognos 10, but you can substitute others if you have them and want to use them. One example would be WAS (Websphere Application Server).

Take a look at the Architecture and Deployment Guide, page 89 (Chapter 9 - Performance Monitoring and Tuning > Application Server Tuning)

http://public.dhe.ibm.com/software/data/cognos/documentation/docs/en/10.2.1/crn_arch.pdf

See also the Supported Environments page for a list od supported application servers other than Tomcat:

http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/prereqsForProduct?deliverableId=1330380859450#sw-0

What issue are you trying to solve here? Why do you need to know about Tomcat? Is it causing issues? If so, what are they?

MF.
Meep!

MFGF

Quote from: inu on 02 Nov 2014 12:10:08 PM
Thanks MFGF,
2.ping timeout in seconds= 240 (after the specified time interval process will be restarted)
    wait stop time in seconds= 60 (after this amount of time process will be stopped)
This is creaing confusion, if one process reached to "wait stop time=60" it will be stopped, then how the same process can reach to "ping timeout =240 seconds " if it has already been stopped, and how it will be restarted.

Little bit confusing, please MFGF , you r the critical resource in this community , clear my doubts.


Cheers!
Inam

Ping timeout is used where communication fails between processes in the architecture. If a ping is sent to a process and it isn't responded to within the defined threshold (240 seconds by default) it is assumed that the process has stopped responding and it will get respawned.

Stop wait time is also used where communication fails between processes, but in this case specifically where a "stop" request is sent to the process to stop it. If the process doesn't respond to the "stop" command gracefully (by returning a response that says "ok, I have stopped") within the defined threshold (60 seconds by default) then it gets killed. A graceful stop will allow current processing to complete, whereas a kill stop will just pull the rug out from under the process.

I'm not sure why you would confuse a ping timeout to a process that is supposed to be running with a stop wait threshold for a process that has been asked to stop? Again, I am wondering what your issue is, and why you need to know this specific level of detail? What are we trying to solve here?

MF.
Meep!

goitzy

I am also wondering what your trying to solve with this. I have never had the need to touch the ping timeout or the web server default (there are many setting that you dont have to worry about in normal circumstances). The only setting we have touched is the Memory where we have bumped it to 2gigs and the shutdown port number since we are running multiple instances (content store and a dispatcher on separate installations) and therefore need each instance listening on a different port.


inu

Quote from: MFGF on 03 Nov 2014 04:54:32 AM
Ping timeout is used where communication fails between processes in the architecture. If a ping is sent to a process and it isn't responded to within the defined threshold (240 seconds by default) it is assumed that the process has stopped responding and it will get respawned.

Stop wait time is also used where communication fails between processes, but in this case specifically where a "stop" request is sent to the process to stop it. If the process doesn't respond to the "stop" command gracefully (by returning a response that says "ok, I have stopped") within the defined threshold (60 seconds by default) then it gets killed. A graceful stop will allow current processing to complete, whereas a kill stop will just pull the rug out from under the process.

I'm not sure why you would confuse a ping timeout to a process that is supposed to be running with a stop wait threshold for a process that has been asked to stop? Again, I am wondering what your issue is, and why you need to know this specific level of detail? What are we trying to solve here?

MF.

Thank you MFGF, You have cleared my doubts. Actually i want to enter into admin part that's why i m indulging into each and every section of admin.
While you telling about "ping timeout in seconds". U have finished with the word "respawned", which i highlighted with red color. what is the meaning of this word. Do you mean restarted
or anything else. I didnot  find this word in dictionary. This word is very important for me to understand perfectly.

Cheers!
Inam

MFGF

Quote from: inu on 05 Nov 2014 12:10:38 PMU have finished with the word "respawned", which i highlighted with red color. what is the meaning of this word. Do you mean restarted
or anything else.

Yes - restarted. Reincarnated. Killed and brought back into existence. 

http://en.wikipedia.org/wiki/Spawn_(computing)
http://en.wikipedia.org/wiki/Spawning_(video_gaming)
MF.
Meep!