Tuesday 30 November 2010

Stadium3 status update

The last few weeks has been quite hectic and stressful for the Stadium team, thus the silence.
We picked up a large number of concurrency issues during an implementation
at Nedbank.

We currently have a build being tested by Sherryl and Brenna.  If all goes well, we will be back on track toward end of this week or early next week.

Thanks for the patience!

Thursday 21 October 2010

How to enable logging

Stadium3 uses a third party component 'log4net' for logging.  More details about this component can be found at:

Stadium3 can be configured to log errors or information. Information logging provides stats on pages users have accessed.

It is a very powerful component, and  can be configured to log to the windows event log,  file,  an email address etc.
However because it is so powerful, setting it up and configuration is not very simple.  Below are the steps to follow
to get it working for Stadium3.

By default logging is turned off. In order to turn it on, follow below steps:
  1. Open web.config file, there is a log4Net section as shown below: <log4net>
        <appender name="InformationLog" type="log4net.Appender.FileAppender">
          <file type="log4net.Util.PatternString" value="Logs/InformationLog_%date{yyyyMMdd}.txt"/>
          <appendToFile value="true"/>
          <layout type="log4net.Layout.PatternLayout">
            <conversionPattern value="%m%n"/>
          <filter type="log4net.Filter.LevelMatchFilter">
            <levelToMatch value="Off"/>
            <acceptOnMatch value="true"/>
          <filter type="log4net.Filter.DenyAllFilter"/>
        <appender name="InformationLogDatabase" type="log4net.Appender.AdoNetAppender">
          <bufferSize value="1"/>
          <connectionType value="System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>
          <connectionString value="Data Source=localhost\SqlServer2005;Initial Catalog=Northwind;User=xxx;Pwd=xxxxxxxx"/>
          <commandText value="INSERT INTO EventLog ([Application],[Page],[User],[Details],[LogType]) VALUES (@application,@page,@user,@details,@logtype)"/>
          <filter type="log4net.Filter.LevelMatchFilter">
            <levelToMatch value="Off"/>
            <acceptOnMatch value="true"/>
          <filter type="log4net.Filter.DenyAllFilter"/>
          <appender-ref ref="InformationLog"/>

  2. You can configure to log to  a file or database.  Appender 'InformationLog' logs to a file and 'InformationLogDatabase'
    logs to a database. By default it is configured to log to a file.  This is indicated by element:   <root>
          <appender-ref ref="InformationLog"/>

  3. By default logging is turned off, in order to turn it on, you have to change value of the appropriate appender's  <levelToMatch> node.

  4. You can change it to 'Info' for information logging or to 'Error' for error logging. An example of error logging will be: <filter type="log4net.Filter.LevelMatchFilter">
               <levelToMatch value="Error"/>
               <acceptOnMatch value="true"/>

  5. Files are created in a 'Logs' folder in 'StadiumServer' folder, first create this folder, then allow the neccessary user access to this folder, or give  'Everyone' access.

  6. If you want to log to database instead, change to following: <root>
            <appender-ref ref="InformationLogDatabase"/>

  7. Errors or information will be logged to an EventLog table, you can configure the database as part of the connectionstring element:  <connectionString value="Data Source=localhost\SqlServer2005;Initial Catalog=Northwind;User=xxx;Pwd=xxxxxxxx"/>

  8. You need to run below script to create this table:
    CREATE TABLE [dbo].[EventLog](
     [ID] [int] IDENTITY(1,1) NOT NULL,
     [Application] [varchar](50) NULL,
     [Page] [varchar](50) NULL,
     [Date] [datetime] NOT NULL DEFAULT (getdate()),
     [User] [varchar](50) NULL,
     [EventType] [varchar](50) NULL,
     [LogType] [varchar](50) NULL,
    [Details] varchar(2000) NULL,
    [Link] varchar(2048) NULL,
     [ID] ASC
    ) ON [PRIMARY]
    ) ON [PRIMARY]

  9. Then change the 'InformationLogDatabase' appender's LevelToMatch tag to 'Error' or 'Info'.

Thursday 7 October 2010

Stadium3 Release : 3.1.1659.3550

Build 3.1.1659.3550 is available for download on Storytracker.

Only one new feature:
  • Reloading of application now only takes place when .sap file is uploaded
What this means:
Previously, we were reloading the application whenever the menu item associated with the application was clicked.
This meant if you changed the .sap file, copied it to the right location, any changes you made were immediately reflected  when the application's menu item was clicked.

This behaviour has changed. The .sap file has to be uploaded via Stadium3's web front end before any changes are reflected.
Reason for change:Reloading the sap file everytime user clicks on application's menu item is unneccessary, it only needs to be done if there are changes.
The application designer(user)  knows when there are changes and thus can make the decision when to upload. This results in significant performance gains.

Wednesday 6 October 2010

Stadium3 Release : 3.1.1657.3545

Build 3.1.1657.3545 is available for download on Storytracker.

New features include:
  • Fix for issue when merging user controls
  • Fix for issue with page parameter not appearing when page is not docked
  • Fix for issue when textbox and date fields are used in detailsview
  • Merge wizard now indicates changed and new entities
  • New CellBorderColour for DataGrid and Filter
  • New DisplayTitle property for Filter
  • New FieldHeaderFont property for DetailsView
  • DefaultPageNumber property of ImageViewer control now works with page parameters

Friday 17 September 2010

Stadium3 Release : 3.1.1646.3518

Build 3.1.1646.3518 is available for download on Storytracker.
New features include:
  • Start page can be configured for a role
  • Accessrights now allows  underscore  for name property
  • Decision action now allows conditions with AND and OR
  • Uploading and editing of application has been split as seperate tasks on website
  • GridIterator action now allows adding of 'SetVariable' action as a child action
  • Filter has new CriteriaValueRequired property which forces user to specify a value when filtering
  • Filter has new apply button click event

Wednesday 8 September 2010

Uploading large sap files on IIS7 server

When uploading large sap files on IIS7,  it is likely you will see below error:

In order to fix this error,  follow below steps:
  1. Modify the IIS 7 applicationHost.config file to enable you to configure request filtering at the application level instead of the machine level. To do this, you should
    open the %windir%\System32\inetsrv\config\applicationHost.config file. I
    n a text editor and change the following line:
    <section name="requestFiltering" overrideModeDefault="Deny" />
    <section name="requestFiltering" overrideModeDefault="Allow" />

  2. The web.config file needs to be modified as specified below:

<httpRuntime maxRequestLength="2097151"/>

<requestLimits maxAllowedContentLength="4294967295"  /></requestFiltering>
  • maxRequestLength - Indicates the maximum file upload size supported by ASP.NET. This limit can be used to prevent denial of service attacks caused by users posting large files to the server. The size specified is in kilobytes. The default is 4096 KB (4 MB).
  • requestLimits maxAllowedContentLength - Specifies the maximum length of content in a request, in bytes. The default value is 30000000.
Further information can be found at below links:

Friday 27 August 2010


Stadium3 is installed at the following clients:

Number of applicationsNumber of pages
Allan Gray9269
Business Connexion184
Metropolitan Group Investment Services7136
Metropolitan Retirement Administrators15238
Nedbank  Capital244
Nedbank Transactional Banking2670
Old Mutual Investment Administrators20400
Standard Bank Africa153

Thursday 26 August 2010

Stadium Prerequisites

The prerequisites for Stadium are as follows:
  • Stadium 3: .NET Framework 3.5, SP1
  • Stadium 4: .NET Framework 4.0
Both Stadium 3 and Stadium 4:
  • IE7, IE8 and IE9 in compatibility mode
  • IIS 6.0 and higher
  • ReportViewer 2008 redistibutable if ReportViewer control is being used
  • Microsoft SQL Server 2005 SP2
We recommend Microsoft Windows Server 2003 Standard Edition, Service Pack 2  for production environments.

Tuesday 24 August 2010

Stadium3 Release: 3.1.1610.3444

Build 3.1.1610.3444 includes only one fix:
  • Bug fix for date field in RDLViewer control 

Monday 23 August 2010

Stadium3 Release : 3.1.1605.3436

Build 3.1.1606.3436 is available for download on Storytracker.

New features include:
  • ReportListViewer - Now works with Reporting Services 2008
  • DetailsView - Dropdown field 'Visible' property allows conditions based on values of other dropdown fields (Example: DetailsViewWithVisibleCondition)
  • Master pages have parameters and these parameters can be used in actions, properties. Usage Example: Scenarios - MasterPageParameters
  • User controls have parameters. Usage Example: Scenarios - UserControlParameters
  • Install fixes - Fixed various issues we had with the install