EDK Web Controls 2.1 Beta Features

Question

This topic is to describe how to use some of the new features in the EDK Web Controls 2.1 beta. Extra features and their descriptions will be added below. Feel free to ask questions.

Answer 1

Alternative imageserver URL access
With some network configurations the external imageserver URL is not the same as the internal URL. This can pose problems because the portlet server must be able to access the imageserver to look up the available JS support files, and uses the main imageserver URL set in the portal.
New imageserver URLs can be used by the portlet server in a couple of ways. The most simple way is to add mappings from the external imageserver to the new one. This can be done by adding entries into the imageserver.mapping.xml, and then touching config.xml in the same directory to load the changes. New entries can be added like this:
i.e. http://www.external-servername.com/ptimages/ -> http://internal-servername:8080/ptimages/:
<mapping find="http://www.external-servername.com/ptimages/" replace="http://internal-servername:8080/ptimages/"/>
Note that you must include the whole URL, sections of the URL will NOT be replaced. To replace sections you must use a regular expression mapper, i.e:
<mapping regex="true" find="www.external-(\w+).com" replace="internal-$1:8080" />
will do the same thing in this case - see .NET regular expressions for addition regular expression syntax.
The second method to use an alternative imageserver overrides the first; it uses an Administrative preference to set the URL. The default setting name searched for in PTWC.Mapping.Override (this can be changed in HttpPipe.xml). To use this an administrative page would have to be created to set this preference, and this granularity of configuration should not generally be necessary except for specific remote portlets which access the imageserver via a specific unique URL.