Book Image

Mastering Microsoft Forefront UAG 2010 Customization

Book Image

Mastering Microsoft Forefront UAG 2010 Customization

Overview of this book

While UAG is built to integrate with many environments and publish dozens of application types, many organizations require a certain level of customization to meet their needs. With this book in hand, you will be equipped to deal with these types of customization scenarios, and you will be confident in using such workarounds without hassle and trial and error. Written by some of the leading experts on UAG, "Mastering Microsoft Forefront UAG 2010 Customization" covers the most complex and challenging options for customizing UAG in a way that is friendly and easy to follow. It walks you through various customization tasks, including explanations and code samples, as well as creative ideas for troubleshooting your work. Until now, only a few of the extensions to UAG's services have been publicly available, and most were only known to a select few. Now, this can include you! Throughout this book, you will tackle how to change the system's look-and-feel, deal with advanced authentication schemes and write special functions that need to be executed as part of the client interaction. With "Mastering Microsoft Forefront UAG 2010 Customization", you too can learn how to customize various aspects of UAG's functionality to enhance your organization or customers' experience.
Table of Contents (16 chapters)
Mastering Microsoft Forefront UAG 2010 Customization
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface

AppWrap syntax


The syntax of the SRA and AppWrap configuration files is based on standard XML formatting, where tags are enclosed in triangular brackets. Each element has an opening and closing tag, and within the tags, there could be configuration information. Some tags have internal syntax that includes additional tag structures.

The most commonly used function in AppWrap is the DATA_CHANGE function, which is typically keyed to a specific application type, a specific URL, and has search and replace strings. If a request for a page matches the URL pattern defined in a function, and that URL matches the application type, UAG will know to perform a search-and-replace on the content of the page. The following screenshot is an example of such a function:

Note

The function is enclosed in the full XML tags of an AppWrap file. You would use this structure when creating your own custom file, but if the file needs to contain multiple functions, you won't need to repeat the entire structure we will...