iShare Tuning

Owned by Kim Stimpson
Last updated: 13 May, 2015 by Antony Scott (Deactivated)
1 min read

IP addresses

Use an IP address rather than a Domain. Even "localhost" can cause delays on some systems.

web.config

Check that the ishare.config value in ...\iShare\n.n\WebApps\Web\web.config is as follows

   <appSettings>
       <add key="iShare.config" value="http://x.x.x.x/iShare/n.n/WebService/" />
   </appSettings>

where x.x.x.x is the IP Address and n.n is the version of iShare.

Studio Settings

Run Studio and check that IP addresses are used in the following parameters:

General Settings

  • WebService
    • MapImageURL

Master Settings

  • MapServer
    • MapServerURL
  • MyAlertsService (if MyAlerts is enabled)
    • MyAlertsServiceURL
    • TransactionWebServiceURL
    • UserManagerWebServiceURL
    • UsersWebServiceURL
  • Web
    • WebURL - this can stay as www.mydomain.com/iShareX.X.Web/.
  • WebService
    • MapImageURL
    • WebServiceURL

Logging

Edit the log4net.config in ...\iShare\n.n\WebApps\Web and ...\iShare\n.n\WebApps\WebService and set all logger level values to minimal.

    <logger name="FaultLogging">
      <level value="INFO" />
      <appender-ref ref="RollingFileAppender" />
    </logger>
    <logger name="AddressSearches">
      <level value="ALL" />
      <appender-ref ref="AddressSearchAppender" />
    </logger>

If a production server is operating fine then logging should be as light as you wish it. Most installs have logging set to ‘INFO’ and address searches to ‘ALL’ - see above. This can be reduced.

The level value can be:

ALL | DEBUG | INFO | WARN | ERROR | FATAL | OFF

Where ALL is the most verbose down to OFF where no logging is performed.

Please see the topic Application Logging for more details