DbCommandTimeout

The ADO.NET database interfaces used by generated applications include a default timeout for database commands.  The default is typically 30 seconds.  In cases where commands are expected to take longer, the timeout may be set by adding a key/value pair to the <appSettings> section in web.config as follows:

      <appSettings>

             ...

            <add key="DbCommandTimeout" value="240"/>

             ...

      </appSettings>

The key must be called "DbCommandTimeout" and the value represents the number of seconds to wait before timing out.  This setting overrides the ADO.NET default for all database commands.

DefaultPageUrl

DefaultPageUrl is required in order to establish the default page of the application.  You may edit this setting to change the default page.  The initial setting is created by Iron Speed Designer.

Usage:

<configuration>

     <appSettings>

          <add key=” DefaultPageUrl”
              value="Employees/ShowEmployeesTable.aspx” />

     </appSettings>

</configuration>

EmailFrom

The EmailServer and EmailFrom parameters are used for (1) email notifications when importing data, (2) password reminders sent to application users, and (3) workflow state change notification alerts.

Usage:

<configuration>

     <appSettings>

          <add key=”EmailFrom” value=”email address” />

     </appSettings>

</configuration>

Example:

<configuration>

     <appSettings>

          <add key=”EmailFrom” value=[email protected] />

     </appSettings>

</configuration>

EmailServer

The EmailServer and EmailFrom parameters are used for (1) email notifications when importing data, (2) password reminders sent to application users, and (3) workflow state change notification alerts.

Usage:

<configuration>

     <appSettings>

          <add key=”EmailServer” value=”SMTP server name” />

     </appSettings>

</configuration>

Example:

<configuration>

     <appSettings>

          <add key=”EmailServer” value=”mail.mycompany.com” />

     </appSettings>

</configuration>

ErrorPageUrl

Sets the page that is displayed when the application flags an error.  This setting is not required, and if not present in your application’s Web.config file, a default will be assumed.  You may add/edit these settings to change the locations of the various pages.

Usage:

<configuration>

     <appSettings>

         <add key=” ErrorPageUrl” value="Shared/Error_Page.aspx” />

     </appSettings>

</configuration>

ForbiddenPageUrl

Sets the page that is displayed when the application user attempts to access a page for which they do not have sufficient permission to access.  This setting is not required, and if not present in your application’s Web.config file, a default will be assumed.  You may add/edit these settings to change the locations of the various pages.

Usage:

<configuration>

     <appSettings>

         <add key=”ForbiddenPageUrl”  value="Shared/Forbidden_Page.aspx” />

     </appSettings>

</configuration>

LogCommitExceptions

If the value of this property is "all" then all database commit exceptions will be logged to the system event log (Event Viewer) as warnings.  Normally, commit exceptions are not logged because they are expected to occur in the course of normal application-user actions, and logging them in a production environment could be undesirable.  However, it is useful in a development/testing environment to have a full log of the detailed exception data for all commit failures.

Note: Only works if LogEvents = "true".

Usage:

<configuration>

     <appSettings>

          <add key=”LogCommitExceptions” value=”all” />

     </appSettings>

</configuration>

LogDatabaseCommands

Set LogDatabaseCommands value="true" to log all database SQL commands to the system the event log.  The default value is "false" which means not to log database SQL commands.

Note:  Only works if LogEvents = "true".

LogDatabaseExceptions

If the value of this property is "all" then all database (i.e. SQL) exceptions will be logged to the Event Viewer as warnings.  Normally, most database exceptions are not logged because they are expected to occur in the course of normal application-user actions, and logging them in a production environment could be undesirable.  However, it is useful in a development/testing environment to have a full log of the detailed exception data for all database exceptions.

Note:  Only works if LogEvents = "true".

Usage:

<configuration>

     <appSettings>

          <add key=”LogDatabaseExceptions” value=”all” />

     </appSettings>

</configuration>

LogEvents

Set LogEvents value="false" to disable all logging to the system the event log.

The default value is "true".

PrecompilePageFiles

Normally, a thread is started at the end of the generation process that asynchronously accesses the application’s pages so that IIS will compile the ASPX and ASCX files.

SignedOutPageUrl

Sets the page that is displayed when the application signs out of the application.  This setting is not required, and if not present in your application’s Web.config file, a default will be assumed.  You may add/edit these settings to change the locations of the various pages.

Usage:

<configuration>

     <appSettings>

         <add key=”SignedOutPageUrl”  value="Shared/SignedOutPage.aspx” />

     </appSettings>

</configuration>

SignInPageUrl

Sets the page that is displayed when the application user is prompted to sign in to the application.  This setting is not required, and if not present in your application’s Web.config file, a default will be assumed.  You may add/edit these settings to change the locations of the various pages.

Usage:

<configuration>

     <appSettings>

         <add key=” SignInPageUrl” value="Shared/Sign_in_Page.aspx” />

     </appSettings>

</configuration>

TraceDataAccessMethods
TraceDatabaseCommands
TraceTransactionCache

To get detailed page-level tracing, set these keys to "true".

WebServer

The WebServer parameter instructs Iron Speed Designer to redirect from http (non-secure mode) to https (secure mode).  It is also used for workflow state email notifications to set the application’s URL, e.g., “Click here to access...”

Usage:

<configuration>

     <appSettings>

          <add key=”WebServer” value=”base URL of web server” />

     </appSettings>

</configuration>

Examples:

<configuration>

     <appSettings>

          <add key=”WebServer” value=”http://machinename” />

     </appSettings>

</configuration>

<configuration>

     <appSettings>

          <add key=”WebServer” value=”http://www.mycompany.com” />

     </appSettings>

</configuration>

<configuration>

     <appSettings>

          <add key=”WebServer” value=”http://202.168.17.26” />

     </appSettings>

</configuration>

To specify a different server/host name or to include a port number, you may change this to:

<add key="WebServer" value="http://yourServerName:yourPortNumber" />

You may also change "http://" to "https://" if secure http is required for your application.  If the value does not start with either "http://" or "https:// it is ignored and the default prefix http://localhost is used.

UserIdentityTable

Sets the table used to authenticate user at sign in. Usage:

<configuration>

     <appSettings>

          <add key="UserIdentityTable"

              value="MyApp25.Table_Please_Select_A_Table_Access,MyApp25" />

     </appSettings>

</configuration>

AuthenticationType

Sets the security type used for authentication at runtime. Usage:

<configuration>

     <appSettings>

          <add key="AuthenticationType" value="ActiveDirectory" />

     </appSettings>

</configuration>

RoleManagement

Sets the role management type used to authorize user at sign in. Usage:

<configuration>

     <appSettings>

          <add key="RoleManagement" value="WindowsUsersGroups" />

     </appSettings>

</configuration>

SecurityDisabled

Disables security when set to ‘True’. Usage:

<configuration>

     <appSettings>

          <add key="SecurityDisabled" value="False" />

     </appSettings>

</configuration>

ADDomainControllers

This Active Directory security setting specifies the domain controllers where your application will look for the user’s information for authenticatication. Usage:

<configuration>

     <appSettings>
          <add key="ADDomainControllers" value="LDAP://ironspeed.com;" />

     </appSettings>

</configuration>

SearchNestedGroups

This setting is related to Active Directory Security type. When set to true application will look not only in top level groups but also in the all nested groups. Usage:

<configuration>

     <appSettings>

          <add key="SearchNestedGroups" value="False" />

     </appSettings>

</configuration>