|
Configuring browser Steering for .MobileTemplates and PDAs - 8.x
This document describes the options to steer a PDA Browser to the Mobile web templates and pertains to version 8.* FirstClass servers.
Steering to a separate web site folder by URL
Pros:
- Good if you need to steer a multitude of PDA's to the mobile template set., since you will just need to point the person to the mobile web site domain name..
- All PDA's are ensured of seeing the simple index page that you configure, rather then the more complex page which likely exists on your main web site.
Cons:
- You do need to set up an additional domain name to point to your FirstClass Internet services computer.
This option shows the steps to set up the a separate web site folder to be used exclusively by mobile PDA devices.
It assumes you are starting with only one main website being configured on your FirstClass server.
Step 1 - Create a new folder with in your WWW folder named "MobileSite". This will be the web site to which you will direct all PDA devices.
Step 1.2 - Populating the "MobileSite" folder.
- Place 2 aliases of the original "Template Sets/Mobile Templates" folder in the "MobileSite" folder. The easiest way to do this to Shift+Click+Drag the original conference.
- Rename one of the aliases to ".Templates". Rename the second to "Mobile.Templates". This will ensure that no matter what browser connects to this site it will be displaying the Mobile Template Set.
- Alias the "WWW / Images" folder to the "MobileSite" folder also.
- Place a simplistic index.html file in the "MobileSite" folder which provides the user with a login link.
Your "MobileSite" folder should now look similar to the following.
Step 2 - For this approach you will need to move your current main web site into a sub folder with in the WWW, if it is not set up this way already.
- Create a new folder with in your WWW folder named "MainSite". This will be the web site to which you will direct all non-PDA web browsers.
Step 2.2 - Populating the "MainSite" folder.
- Place aliases of the following original "WWW" folders in to the "MainSite" folder; "Template Set/Mobile Templates", "Template Sets/Standard Templates", "Images", & "ClientDownloads". The easiest way to do this to select and then Shift+Click+Drag the original conferences. Rename the alias for Mobile Templates to Mobile.Templates. Rename the alias for Standard Templates to .Templates.
- You will also need to copy or move your "Home Page" or "index.html" files along with any other files you have at the root of the "WWW" folder, in to the "MainSite" folder. Also move any custom folder you may created in your WWW folder that are used/accessed via your main web site.
- Your "MainSite" folder should now look similar to the below image.
Step 3 - Configuring the "Multiple Sites & Languages" form to steer the domains to the proper site folders.
- Enter the name of your main site folder which you created in step 2, into the "Web Site Alias" field. So in this example that is "MainSite".
- Under "Domain names" enter the domain name which points to your main web site. If there are more than one domain name pointing to the main site, you can add multiple domain names separated by commas.
Step 3.1 - add an additional site.
- Click on the "Add Site" button to add an additional site line to the form.
- Enter the name of your mobile site folder which you created in step 1, into the "Web Site Alias" field. So in this example that is "MobileSite".
- Under "Domain names" enter the domain name which points to your mobile web site. In this example it is "mobile.mydomain.com".
The "Multiple Sites & Languages" form should now look similar to the one below, with your proper IP number and domain names entered.
Step 3.2 - Close the "Multiple Sites & Languages" form and restart FirstClass Internet Services.
- Test that main web site still functions as it did.
Step 4 - Domain name entry.
- If you have not yet done so, you will need to set up a domain name which points to the IP address of the computer on which your FirstClass Internet Services is running, to be used by your PDA users to connect to your FirstClass server. In the above example, "mobile.mydomain.com" was used.
- Once the domain name is configured, you should be able to point any web browser to the mobile site domain name and log in to see the mobile template set interface.
Steering by URL using the HeaderMatch document
Pros:
- Good if you need to steer a multitude of PDA's to the mobile template set, since you will just need to point the person to the mobile web site domain name..
Cons:
- You do need to set up an additional domainname to point to your FirstClass Internet services computer.
- The PDA will see the complex index page which likely exists on your main web site, rather then a simple login page.
Step 1 - HeaderMatch configuration
- Log in to FirstClass as Admin and open the "Internet Services" folder and then the "HeaderMatch" document. You need to add a new line at the bottom of the "HeaderMatch" document to steer your particular user URL Host value to the mobile templates similar to the example below:
# Custom ********************** site steering to mobile web templates
*: IF HOST == "mobile.mydomain.com" SET .templates = mobile.templates AND SET icons = mobileicons
- After adding this line, close the HeaderMatch document, and restart FirstClass Internet Services
Step 2 - Domain name entry.
- If you have not yet done so, you will need to set up a domain name which points to the IP address of the computer on which your FirstClass Internet Services is running, to be used by your PDA users to connect to your FirstClass server. In the above example, "mobile.mydomain.com" was used.
- Once the domain name is configured, you should be able to point any web browser to the mobile site domain name and log in to see the mobile template set interface as shown below.
Steering by PDA device type
Pros:
- You do not need to set up an additional domainname to point to your FirstClass Internet services computer.
Cons:
- Good for steering a few specific PDA's, but can become time consuming if you need to support a wide variety of PDA's connecting to your site.
The following steps will walk you through modifying your "HeaderMatch" document so that it steers your particular PDA web browser to the ".MobileTemplates" when it connects.
Step 1 - Determining the 'User Agent' value for the web browser
- First you need to determine the "User Agent" value for your particular PDA's web browser. On your "FirstClass Internet Services" console window goto the "Diagnostics" menu and make sure that the "Console to File" option has a check mark beside it.
- Then goto the "Diagnostics / Logging" menu and set "HTTP Server" logging to level "3".
- Connect to your web site using the PDA's web browser
- On your "FirstClass Internet Services" console window goto the "Diagnostics" menu and uncheck the "Console to File" option.
- Then open the Internet Services log file located in the following location:
On a Mac OSX Server: "Library/FirstClass Server/FCISD.log"
On a Win Server: "<drive letter>:/FCServer/Inetsvcs.log"
- Look for the section where your PDA browser connects. It will look similar to the log below. Isolate the line which starts with "Header: "User-Agent"; Value=" as shown in Quoted blue below.
[1/9/03 1:08:59 PM] HTTP-5: Rcv: GET /Login HTTP/1.1
[1/9/03 1:08:59 PM] HTTP-5: Rcv: Accept: */*
[1/9/03 1:08:59 PM] HTTP-5: Header: "Accept"; Value="*/*"
[1/9/03 1:08:59 PM] HTTP-5: Rcv: UA-OS: Windows CE (POCKET PC) - Version 3.0
[1/9/03 1:08:59 PM] HTTP-5: Header: "UA-OS"; Value="Windows CE (POCKET PC) - Version 3.0"
.
[1/9/03 1:08:59 PM] HTTP-5: Rcv: User-Agent: Mozilla/2.0 (compatible; MSIE 3.02; Windows CE; PPC; 240x320)
[1/9/03 1:08:59 PM] HTTP-5: Header: "User-Agent"; Value="Mozilla/2.0 (compatible; MSIE 3.02; Windows CE; PPC; 240x320)"
- Copy the section which comes after the "Value=" statement. In this case it is "Mozilla/2.0 (compatible; MSIE 3.02; Windows CE; PPC; 240x320)"
Step 2 - Modifying the Header Match document
- Log in to FirstClass as Admin and open the "Internet Services" folder and then the "HeaderMatch" document. You need to add a new line at the bottom of the "HeaderMatch" document to steer your particular user agent value to the mobile templates. For the example above the line would read as follows:
*: IF User-Agent == "Mozilla/2.0 (compatible; MSIE 3.02; Windows CE; PPC; 240x320)" SET .templates = mobile.templates AND SET icons = mobileicons
- After adding this line, closing the HeaderMatch document, and restarting FirstClass Internet Services, your PDA browser should now be directed to the "Mobile" Web Templates.
Some examples that work for the Treo 600 or the 650 are:
*: IF User-Agent == "Mozilla/4.0 (compatible; MSIE 6.0; Windows 95; PalmSource; Blazer 3.0) 16;160x160" SET .templates = mobile.templates AND SET icons = mobileicons
*: IF User-Agent == "Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; PalmSource/hspr-H102; Blazer/4.0) 16;320x320" SET .templates = mobile.templates AND SET icons = mobileicons
NOTE: the entry in Headermatch does not need to completely match the user agent identifier. For example, the line for Treo 600 could be shortened to:
*: IF User-Agent == "Mozilla/4.0 (compatible; MSIE 6.0; Windows 95; PalmSource; Blazer 3.0)" SET .templates = mobile.templates AND SET icons = mobileicons
| 
