WebService Diagnosis - Revision history

KNO at 09:23, 15 February 2016

2016-02-15T09:23:58Z

KNO at 11:54, 7 May 2015

2015-05-07T11:54:55Z

KNO: /* Diagnosis */

2015-04-30T10:46:38Z

‎Diagnosis

KNO: /* Diagnosis */

2015-04-30T10:46:17Z

‎Diagnosis

KNO: /* Diagnosis */

2015-04-30T10:44:41Z

‎Diagnosis

KNO: /* Diagnosis */

2015-04-30T10:43:48Z

‎Diagnosis

KNO: /* Diagnosis */

2015-04-30T10:36:17Z

‎Diagnosis

KNO: /* Diagnosis */

2015-04-30T10:34:27Z

‎Diagnosis

KNO: /* Session Management */

2015-04-30T10:31:32Z

‎Session Management

KNO: /* Session Management */

2015-04-30T10:30:04Z

‎Session Management

← Older revision		Revision as of 09:23, 15 February 2016
Line 86:		Line 86:
	* [[HowTo:Install Microsoft IIS]]		* [[HowTo:Install Microsoft IIS]]

−	~~[[Category:Installing]]~~
−	~~[[Category:Web Service]]~~
	{{Category/Version\|2.4.3}}		{{Category/Version\|2.4.3}}
		+
		+	[[Category:2.4.3\|WebService Diagnosis]]
		+	[[Category:Installing\|WebService Diagnosis]]
		+	[[Category:Web service\|WebService Diagnosis]]

← Older revision		Revision as of 11:54, 7 May 2015
Line 88:		Line 88:
	[[Category:Installing]]		[[Category:Installing]]
	[[Category:Web Service]]		[[Category:Web Service]]
		+	{{Category/Version\|2.4.3}}

@@ Line 28: / Line 28: @@
 {| class="wikitable sortable" width="80%"
 |-
-! width="200" | Test !! style="text-align:center" | Type !! Description
+! width="200" | Test !! Type !! Description
 |-
 | rowspan="3" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]] || The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.

@@ Line 47: / Line 47: @@
 {| class="wikitable sortable" width="80%"
 |-
-! Test !! Type !! Description
+! width="200" | Test !! Type !! Description
 |-
 | rowspan="3" width="200" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
@@ Line 67: / Line 67: @@
 {| class="wikitable sortable" width="80%"
 |-
-! Test !! Type !! Description
+! width="200" | Test !! Type !! Description
 |-
 | rowspan="3" width="200" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| see the section in the Session Management tests

@@ Line 26: / Line 26: @@
 ==== Session Management ====
-{| class="wikitable sortable"
+{| class="wikitable sortable" width="80%"
 |-
 ! width="200" | Test !! style="text-align:center" | Type !! Description
@@ Line 45: / Line 45: @@
 ==== {{UBIK}} Content Service ====
-{| class="wikitable sortable"
+{| class="wikitable sortable" width="80%"
 |-
 ! Test !! Type !! Description
@@ Line 65: / Line 65: @@
-{| class="wikitable sortable"
+{| class="wikitable sortable" width="80%"
 |-
 ! Test !! Type !! Description

@@ Line 28: / Line 28: @@
 {| class="wikitable sortable"
 |-
-! Test !! Type !! Description
+! width="200" | Test !! style="text-align:center" | Type !! Description
 |-
-| rowspan="3" width="200" | Try to find the service end point|| Error || The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
+| rowspan="3" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]] || The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
 |-
-| Warning || The service end point provides a non-secure connection ("http://"). A connection without transport security should only be used for testing or in internal networks in a trusted enviroment only. This is generally not recommended for a productive environment.
+| align="center"| [[File:IC_WebService_Diagnosis_Warning.png|Warning]]|| The service end point provides a non-secure connection ("http://"). A connection without transport security should only be used for testing or in internal networks in a trusted enviroment only. This is generally not recommended for a productive environment.
 |-
-| Warning || The service endpoint provides a secure connection ("https://") but has issues with the certificate provided: e.g. expired validity, non-trusted root authority etc. This means, a connection to the service will still be possible but it is not recommended to use in a productive environment.
+| align="center"| [[File:IC_WebService_Diagnosis_Warning.png|Warning]]|| The service endpoint provides a secure connection ("https://") but has issues with the certificate provided: e.g. expired validity, non-trusted root authority etc. This means, a connection to the service will still be possible but it is not recommended to use in a productive environment.
 |-
-| Fetch a token || Error || The session management service is not configured to testing mode or does not have a valid test login configured in the {{UBIK}} database
+| Fetch a token || align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| The session management service is not configured to testing mode or does not have a valid test login configured in the {{UBIK}} database
 |-
-| Verify token || Error || The fetched token is not recognized as a valid token to be used with the content service. A possible reason is that the session management has a different database connection configured.
+| Verify token || align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| The fetched token is not recognized as a valid token to be used with the content service. A possible reason is that the session management has a different database connection configured.
 |-
-| Verify if token gets invalid || Warning || The fetched token is always valid. The reason can be that the setting "TokenRestrictive" is switched off which is not recommended for productive use.
+| Verify if token gets invalid || align="center"| [[File:IC_WebService_Diagnosis_Warning.png|Warning]]|| The fetched token is always valid. The reason can be that the setting "TokenRestrictive" is switched off which is not recommended for productive use.
 |}
@@ Line 49: / Line 49: @@
 ! Test !! Type !! Description
 |-
-| rowspan="3" width="200" | Try to find the service end point|| Error || The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
+| rowspan="3" width="200" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
 |-
-| Warning || The service end point provides a non-secure connection ("http://"). A connection without transport security should only be used for testing or in internal networks in a trusted enviroment only. This is generally not recommended for a productive environment.
+| align="center"| [[File:IC_WebService_Diagnosis_Warning.png|Warning]]|| The service end point provides a non-secure connection ("http://"). A connection without transport security should only be used for testing or in internal networks in a trusted enviroment only. This is generally not recommended for a productive environment.
 |-
-| Warning || The service endpoint provides a secure connection ("https://") but has issues with the certificate provided: e.g. expired validity, non-trusted root authority etc. This means, a connection to the service will still be possible but it is not recommended to use in a productive environment.
+| align="center"| [[File:IC_WebService_Diagnosis_Warning.png|Warning]]|| The service endpoint provides a secure connection ("https://") but has issues with the certificate provided: e.g. expired validity, non-trusted root authority etc. This means, a connection to the service will still be possible but it is not recommended to use in a productive environment.
 |-
-| Fetch a token || Error || The session management service is not configured to testing mode or does not have a valid test login configured in the {{UBIK}} database
+| Fetch a token || align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| The session management service is not configured to testing mode or does not have a valid test login configured in the {{UBIK}} database
 |-
-| Verify token || Error || The fetched token is not recognized as a valid token to be used with the content service. A possible reason is that the session management has a different database connection configured.
+| Verify token || align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| The fetched token is not recognized as a valid token to be used with the content service. A possible reason is that the session management has a different database connection configured.
 |-
-| Verify if token gets invalid || Warning || The fetched token is always valid. The reason can be that the setting "TokenRestrictive" is switched off which is not recommended for productive use.
+| Verify if token gets invalid || align="center"| [[File:IC_WebService_Diagnosis_Warning.png|Warning]]|| The fetched token is always valid. The reason can be that the setting "TokenRestrictive" is switched off which is not recommended for productive use.
 |}
@@ Line 69: / Line 69: @@
 ! Test !! Type !! Description
 |-
-| rowspan="3" width="200" | Try to find the service end point|| Error || see the section in the Session Management tests
+| rowspan="3" width="200" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| see the section in the Session Management tests
 |-
-| Warning || see the section in the Session Management tests
+| align="center"| [[File:IC_WebService_Diagnosis_Warning.png|Warning]]|| see the section in the Session Management tests
 |-
-| Warning || see the section in the Session Management tests
+| align="center"| [[File:IC_WebService_Diagnosis_Warning.png|Warning]]|| see the section in the Session Management tests
 |-
-| Add push data || Error || Adding push data failed. The reason could be a miscofigured service access point for the push service.
+| Add push data || align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| Adding push data failed. The reason could be a miscofigured service access point for the push service.
 |-
-| Fetch push data || Error || No push data received. If this error occurs even if adding the push data worked, the reason could be that the cached push data has been lost because the service had to be restarted or persisting the data in the background failed.
+| Fetch push data || align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| No push data received. If this error occurs even if adding the push data worked, the reason could be that the cached push data has been lost because the service had to be restarted or persisting the data in the background failed.
 |-
-| Reset push data || Error || see description of the possible error(s) described for "Fetch push data".
+| Reset push data || align="center"| [[File:IC_WebService_Diagnosis_Error.png|Error]]|| see description of the possible error(s) described for "Fetch push data".
 |}

@@ Line 44: / Line 44: @@
 ==== {{UBIK}} Content Service ====
@@ Line 56: / Line 75: @@
 | Warning || see the section in the Session Management tests
 |-
-| Check database connection || Error || Database cannot be reached. Possible reason can be a faulty database connection string or the used database server cannot be reached or is blocked by the network configuration.
+| Add push data || Error || Adding push data failed. The reason could be a miscofigured service access point for the push service.
 |-
-| Upload a file || Error || The configured target file system in the database settings is not set correctly to a folder allowing to write data. The reason can be that the user running the {{UBIK}} web service does not have read/write access to the configured target folder.
+| Fetch push data || Error || No push data received. If this error occurs even if adding the push data worked, the reason could be that the cached push data has been lost because the service had to be restarted or persisting the data in the background failed.
 |-
-| Download a file || Error || The uploaded file (uploaded in the previous test) cannot be downloaded. Possible reasons could be a timeout which is set too restrictive to download the data in time.
+| Reset push data || Error || see description of the possible error(s) described for "Fetch push data".
-|-
-| Write logs || Error || The log cannot be written. Possible reason is that the configured log folders do not exist or the user running the web service has no read/write access to the logging folder.
-|-
-| Check rights structure || Error || At least one of the configured target directories used to store data (e.g. uploaded photos) does not have the required read/write rights. See the details if there are issues with one of the configured folders.
 |}
 == See also ==

@@ Line 45: / Line 45: @@
 ==== {{UBIK}} Content Service ====
-* Try to find the service end point
-** (see the same section in the session management tests above)
+{| class="wikitable sortable"
-* Check database connection
+|-
-** Error: Database cannot be reached. Possible reason can be a faulty database connection string or the used database server cannot be reached or is blocked by the network configuration.
+! Test !! Type !! Description
-* Upload a file
+|-
-** Error: The configured target file system in the database settings is not set correctly to a folder allowing to write data. The reason can be that the user running the {{UBIK}} web service does not have read/write access to the configured target folder.
+| rowspan="3" width="200" | Try to find the service end point|| Error || see the section in the Session Management tests
-* Download a file
+|-
-** Error: The uploaded file (uploaded in the previous test) cannot be downloaded. Possible reasons could be a timeout which is set too restrictive to download the data in time.
+| Warning || see the section in the Session Management tests
-* Write logs
+|-
-** Error: The log cannot be written. Possible reason is that the configured log folders do not exist or the user running the web service has no read/write access to the logging folder.
+| Warning || see the section in the Session Management tests
-* Check rights structure
+|-
-** Error: At least one of the configured target directories used to store data (e.g. uploaded photos) does not have the required read/write rights. See the details if there are issues with one of the configured folders.
+| Check database connection || Error || Database cannot be reached. Possible reason can be a faulty database connection string or the used database server cannot be reached or is blocked by the network configuration.
 ==== {{UBIK}} Push Service ====

@@ Line 25: / Line 25: @@
 ==== Session Management ====
-* Fetch a token
+{| class="wikitable sortable"
-** Error: The session management service is not configured to testing mode or does not have a valid test login configured in the {{UBIK}} database
+|-
-* Verify token
+! Test !! Result type !! Description
-** Error: The fetched token is not recognized as a valid token to be used with the content service. A possible reason is that the session management has a different database connection configured.
+|-
-* Verify if token gets invalid
+| rowspan="3" | Try to find the service end point|| Error || The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
-** Warning: The fetched token is always valid. The reason can be that the setting "TokenRestrictive" is switched off which is not recommended for productive use.
+|-
 ==== {{UBIK}} Content Service ====