Subtitles of the Movie

You'll notice when we get back to the Main Screen that we have a little summary up here of what we've done. In this case we've entered Google.com as an accessible URL, you're told that it's a web application, again as opposed to a web interface or a SharePoint Site and that we have no authentication selected for the remote website. Now would be kind of a good time to go over exactly what addresses you can enter as a Web Resource. There are some that just don't work because of the Access Gateway Software is set up. Obviously you've seen that we could enter Google.com as a URL in a Web Resource that obviously is correct. A couple of other formats you can use to enter a URL into a Web Resource is you can specify a Directory or a Virtual Directory. For example if there was a Directory off of Google named Images you can set it up like so. You can also used what's called Tokens and Tokens can be used to represent Dynamic System Information. Tokens are placed in URL and UNC paths and we'll see that when we talk about File Share Resources, with attributes that are obtained from Active Directory or your other Directory Service that you have configured. For example if we have a Users Page under Google.com and we want to put in the current logged in username you could put pound and then the Token, Username. All of the Tokens that are valid for URL and UNC Paths are listed in the Access Gateway Documentation. We'll go over a good number of them through out the course of this course and also as we do the lab but we will not cover all of them because not all of them apply on our lab environment. So now that we've mentioned what will work as a URL in a Web Resource, what won't work as a URL in a Web Resource? The first thing is you cannot specify a document name in the URL for a Web Resource, again I don't really have much of an explanation for it other then to tell you its simply not supported. Another format that is not supported is using Wild Cards, much like you see there. If we wanted to give access to everything at Google.com we would have to enter each URL and separately, you can't just use a Wild Card. In fact if you try to hit OK and add this to the Web Resource you're simply told, hey that's not valid. Now we'll continue on with the other two options here on the URL Screen. The first option and it's already checked, it's not checked by default but I've checked it at some point through out the little mini lab we've dong here is the box to Publish for Users on the list of Resources. This makes this Web Resource available to the users by putting a link in their Web Interface. If you check this, you have to specify a Home Page and this Home Page has to be within the Domain of the URLs that you've placed up here. In our case if we have a URL in here that's Google.com we can't set the Home Page to Yahoo.com. If we try to do that we hit Next, it'll tell us the start page you entered is not in the Web Resource. So its kind of idiot proofed here, it won't let you make silly mistakes like that. In this case we'll tell it the Home Page is Google.com. The second option is to use the Interface that is common for all browser types. As you see with the little blurb under here this option suppresses browser specific functionality like ActiveX. This is used if you have a Web Resource that you wish to publish to users that may not be using, in this example, Internet Explorer. Let's say you have a website that uses ActiveX that you wish to publish for users so that they can access it using Firefox or using a Blackberry Web Browser for example. You could check this box and it would simply strip out all the ActiveX before it's presented to the end user. For our purposes we'll leave this check box Unchecked simply because for our demonstration we'll always be using Internet Explorer and we'll click Next. The last screen we're presented with is to whether to create a Default Policy to allow access to this Web Resource. The defaults are that you will create a policy to grant access later. If you choose this Default Policy, even if it's assigned two users, if there's no policy allowing those users access to this Web Resource it will not appear in their Web Interface. For our purposes we will create a default Policy that grants access to anyone this policy happens to be assigned to and we'll click finish. Once you do that you'll notice that this Google Search Web Resource appears in our list of Web Resources. Also if you expand this down you can choose Google Search Engine and if you had any alerts associated with this particular Web Resource you'd see them here. You don't get that much more information by expanding Web Resources and choosing the Resource itself. And this concludes our discussion of Web Resources.