Provided Web Services Appsettings
This page lists all the appsettings.json settings available for the .NET CoreWcf Provided Web Services
The appsettings.json file is located in the folder <AMT Environment>\Apps\<Application>\Binaries\Common\SoapProvider\
| After changing settings in the appsettings.json file, the IIS Application Pool containing the Provided Web Services must be recycled/restarted to read the changed settings. |
Logging
Sets the logging levels for the various ASP.NET Core components of the AMT Soap Host. These settings do not need be adjusted in a normal situation.
The allowed log levels are, from most to least detailed: Trace, Debug, Information, Warning, Error, Critical and None.
"Logging": {
"LogLevel": {
"Default": "Information",
"Microsoft.AspNetCore": "Warning",
}
},AmtLogSeverity
Sets the logging severity level of the Provided Web Services.
See Tracing Provided Web Services.
"AmtLogSeverity": "Error",https_port
The https_port setting should be set to the HTTPS port used in the IIS binding.
"https_port": 443,Version
The version of the configuration file, this setting should not be changed unless requested by the AMT customer support.
"Version": 1,ServiceMetadataBehaviorConfig
This settings enables or disables the publishing of the service page and WSDL contracts for the Provided Web Services.
HttpGetEnabled enables the page and WSDL for the HTTP bindings, HttpsGetEnabled is for the HTTPS bindings.
Once enabled the WSDL contracts can be accessed by appending "?wsdl" or "?singleWsdl" to the service address.
For example: http://localhost/amt/pws/LionScreens.svc?singleWsdl
"ServiceMetadataBehaviorConfig": {
"HttpGetEnabled": true,
"HttpsGetEnabled": true
},Providers
In the providers section, settings for the Provided Web Services themself are located. Each Web Service requires a seperate entry consisting of an array of settings which are listed below.
Provider
The first settings of the Providers section.
- ProviderName - The name of the Provided Web Service.
- Enabled - Setting to enable the Provided Web Service.
- Ports - One or more PortTypes belonging to the Provided Web Service. See Ports.
"Providers": [
{
"ProviderName": "Example_WS_Provider",
"Enabled": true,
"Ports": [
...Ports
In the Ports section, settings for the PortTypes are located. Each PortType requires a seperate entry consisting of an array of settings.
- PortName - The name of the PortType.
- Enabled - Setting to enable the PortType.
- Bindings - One or more bindings belonging to the PortType. See Bindings.
"Providers": [
{
...
"Ports": [
{
"PortName": "WS_Provider",
"Enabled": true,
"Bindings": [Bindings
In the Bindings section, settings for the bindings are located. Each binding requires a seperate entry consisting of an array of settings.
Identical relative paths may be used for bindings as long as they use different security modes.
- RelativePath - The path of the service relative to the URL of the AMT Soap Host IIS site.
- SecurityMode - Security mode controls to which protocol the binding should respond.
For HTTP it should be set to "None", for HTTPS is should be set to "Transport".
"Providers": [
{
...
"Ports": [
{
...
"Bindings": [
{
"RelativePath": "/WS_Provider.svc",
"SecurityMode": "None",
// This service page will be hosted on http://<IIS_site>/WS_Provider.svc
},
{
"RelativePath": "/WS_Provider.svc",
"SecurityMode": "Transport",
// This service page will be hosted on https://<IIS_site>/WS_Provider.svc
},
{
"RelativePath": "/Secure_WS_Provider.svc",
"SecurityMode": "Transport",
// This service page will be hosted on https://<IIS_site>/Secure_WS_Provider.svc
}
],DebugBehaviorConfig
Setting IncludeExceptionDetailsInFaults to true, enables the sending of detailed error messages to the Consumable Web Service when faults occur.
"Providers": [
{
...
"Ports": [
{
...
"DebugBehaviorConfig": {
"IncludeExceptionDetailInFaults": false
}