Skip to main content

Configuration File

The following are the descriptions for the web.config (SF-WSA configuration) file. The web.config file contains the Web Service runtime settings. The file can be edited through the ASP.NET extension tab in the IIS Manager utility. Below is the listing of the keys found inside the \<appSettings> section:

AFTrcCfg ® The complete path for the log/trace file of the Web Service. If not present, or if it is a zero length string, the web service will not create any log/trace.

AFStorage ® The complete path for the SF-WSA storage .XML file (needed for internal Web Data Entry methods). Insert a valid path (the same installation path) with a valid XML fine name. (See EXAMPLE: Example of a Config File.)

AFPrecision ® The number of decimal digit after the decimal separator (when formatting float/double values)

AFSQLnet ® The address for running Sigmafine Scheduler automatic SQL Publications. Set this parameter only if Sigmafine SQL Access and Sigmafine Scheduler are installed over the same machine where SF-WSA is running.

AFLogon ® The log-on settings for checking privileges under SSO/Kerberos configuration deployment scenarios. Leave empty this field if standard NTLM protocol is used. If Kerberos enabled then setup as: DOMAIN\USER\PASSWORD

AFCulture ® This setting allows you to set the culture of the Web Services. See .NET documentation about culture names and settings.

AFRecalc® The address for running Sigmafine Scheduler automatic recalculation. This is an optional setting which is needed only to recalculate dependent/children analyses after an adjustment over the target case (via EDIT MULTI method) is needed. Set this parameter only if Sigmafine SQL Access and Sigmafine Scheduler are installed on the same machine where Sigmafine WSA is running. When setting this parameter please check:

PIMSOFT.SIGMAFINE.SCHEDULER.EXE.CONFIG

\<add key="Port" value="5470"/\>

\<add key="ChannelRecalc" value="RecalcServer"/\>

PIMSOFT SIGMAFINE WEB SERVICE ACCESS - WEB.CONFIG

\<add key="AFRecalc" value="tcp://localhost:5470/RecalcServer"/\>

The rule for building this setting is:

\<add key="AFRecalc" value="tcp://\<SRV\>:\<PORT\>/\<CHANNEL\>"/\>

Where:

\<SRV\> = Name of the Server running SF Scheduler (usually Sigmafine applicaiton server)

\<PORT\> = TCP/IP port number as specified in the SCHEDULER XML settings file - parameter "Port" (e.g. 5470)

\<CHANNEL\> = Name of the Channel-EndPoint as specified in the SCHEDULER XML settings file - parameter "ChannelRecalc" (e.g. RecalcServer)

If you do not want this option or you don't have Sigmafine Scheduler 4.7.0 or greater, simply delete (or set as blank) the AFRecalc option in the SF Web Services XML web.config file.

Another important point to consider is that Web Service for RECALCULATION acts as a Scheduler client application. The communication over these components is based on a remoting session with an authentication token. Every time WSA requests a recalculation, Scheduler checks this token request. If the token is does not exist or is invalid, the recalculation returns an error. The standard authentication/token process is as follows:

  1. The Scheduler must be up & running.
  2. The user calls a CASE EDIT (MULTIPLE) to WSA.
  3. WSA checks if the recalculation option is enabled. If no, it exits else continue with next steps
  4. WSA checks for a valid* token:
  5. If there is no token yet, it requests a new token from Scheduler.
  6. If a token already exists, it goes to the next step.
  7. WSA runs a recalculation request based on the edited analysis/case and authentication token.

Note:

For further details on other web.config settings and keys, please refers to the Web Service XML configuration files on Microsoft .NET Framework documentation.

Only for the RECALCULATION FEATURE: If Scheduler is restarted while WSA is up & running, Scheduler invalidates all the tokens previously provided to all recalculation clients. The only workaround is restarting WSA via an IISRESET command.

ClosedEXAMPLE: Example of a Config File

\<?xml version="1.0"?>

\<configuration>

\<connectionStrings/>

\<appSettings>

\<add key="AFTrcCfg" value="D:\WSA\Pimsoft.Sigmafine.Precompiled\AFBaseline.log"/>

\<add key="AFStorage" value="D:\WSA\Pimsoft.Sigmafine.Precompiled\AFBaseline.xml"/>

\<add key="AFPrecision" value="3"/>

\<add key="AFSQLNet" value="tcp://localhost:5470/SQLAccessServer"/>

\<add key="AFRecalc" value="tcp://localhost:5470/RecalcServer"/>

\<add key="AFLogon" value=""/>

\<add key="AFCulture" value="en-US"/>

\</appSettings>

\<system.web>

\<customErrors mode="Off"/>

\<compilation debug="true" defaultLanguage="c#" targetFramework="4.0">

\<assemblies>

\<add assembly="ADODB, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

\<add assembly="OSIsoft.AFSDK, Version=2.0.0.0, Culture=neutral, PublicKeyToken=6238BE57836698E6"/>

\<add assembly="System.Security, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

\<add assembly="System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

\<add assembly="System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

\<add assembly="System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

\<add assembly="System.DirectoryServices.AccountManagement, Version=4.0.0.0, Culture=neutral, PublicKeyToken= B77A5C56199"/>

\<add assembly="System.Runtime.Remoting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

\<add assembly="OSIsoft.PISDK, Version=1.4.0.0, Culture=neutral, PublicKeyToken=C3309F0734BA2805"/>

\<add assembly="OSIsoft.PISDKCommon, Version=1.4.0.0, Culture=neutral, PublicKeyToken=C3309F0734BA2805"/>

\<add assembly="OSIsoft.PITimeServer, Version=1.4.0.0, Culture=neutral, PublicKeyToken=C3309F0734BA2805"/>

\<add assembly="Pimsoft.Licensing, Version=1.2.0.0, Culture=neutral, PublicKeyToken=2876CE84A7EE5D28"/>

\</assemblies>

\</compilation>

\<authentication mode="Windows"/>

\</system.web>

\</configuration>