daphne man | Hi, There is Session ID existing in Serviceability API. It's okay that session id is required in PerfmonPort Service, such as perfmonOpenSession, perfmonAddCounter. Session id helps receive session-based data. But, what is the purpose of including Session ID in soap header for RisPort SOAP Service(selectCmDevice)? I can receive response without including session ID.
<soap:Header> <tns:AstHeader id="id1"> <SessionId xsi:type="xsd:string">SessionId</SessionId> </tns:AstHeader> </soap:Header>
Thanks in advance. |
| Please sign in to flag this as inappropriate. |