| Now that we have created an Access Center we will need to configure it, add users, roles, pages and folders. In the following sections I have defined how to do some of the basic configurations needed to deploy an Access Center to your end-users.
In the farm properties you will be able to add licenses, configure the MetaFrame Secure Access Manager components and configure the Index Servers properties. The following defines how to configure the Secure Access Manager farm properties. 1. Open the Access Management Console, right click on the farm node and click Properties. 
2. The Agent Servers tab allows you to configure the agent servers in the Access Server farm and to enable or disable Agent Servers. Remember that is you are experiencing slow Access Center response then you might want to add an additional Agent server. In the Agent servers list box, all the MetaFrame Secure Access Manager servers are displayed with a checkbox displaying if the server is acting as an Agent server or not. Check to enable the Agent service on a MetaFrame Secure Access Manager server. 
3. The Web Servers tab is basically the same as the Agent Servers tab but for the MetaFrame Secure Access Manager web server intentions. I do not recommend running the web service on all MetaFrame Secure Access Manager servers; I do recommend at least two. This gives the MetaFrame Secure Access Manager farm a failover option. 
4. The Index Servers tab allows you to configure the resources to be indexed by the MetaFrame Secure Access Manager Index server. In this example we have not installed the Index Server and hence this screen is grayed out. In the next revision of this document I will add this feature. For more information on the MetaFrame Secure Access Manager Index server please refer to the MetaFrame Secure Access Manager 2.0 with Service Pack 1 Administrators Guide. 
5. The Licensing tab gives you the ability to add, activate and remove MetaFrame Secure Access Manager licenses. Click the Add button to add a license. Click to select a license and click the Remove button to remove it. Double click on a license to activate it. 
When finished click the OK button. You have now successfully configured the farm properties. You might need to readdress these properties to add additional licenses and or change services on particular servers.
You are now able to import Content Delivery Agents (CDAs) and Microsoft Web Parts. CDA are the main mechanism for delivering content and services in the Access Center. Web Parts are the Microsoft equivalent To use a CDA, you must first add it to the access server farm, and then assign it to an access center. Next, you can make the CDA available to users by either placing it on a page or by adding it to the Add menu. Do note that all MetaFrame Secure Access Manager CDAs are imported upon installation so the only need you would have to import one is if you removed one and then required to reinstall it. You can take advantage of a growing number of 3rd party CDAs and Web Parts. You also have the ability to develop you only CDAs through the MetaFrame Secure Access Manager CDA Pad and Visual Studios .NET plug-in. For more information on the CDA Pad please refer to the MetaFrame Secure Access Manager 2.0 Administrators Guide. . For additional resources on CDA development and downloads please visit: www.cdaexchange.com For additional resources on Web Part downloads please visit: http://www.microsoft.com/sharepoint/server/downloads/webparts/introduction.asp The following defines how to import a CDA and or Web part. 1. Open the Access Management Console, expand the farm, right click on CDAs and click Import CDA. 
2. Enter the location and file name of the CDA and or Web Part in the Package location text box and click Next to continue. 
3. Click to check the Access centers you would like to deploy the CDA or Web Part to. Do note that this does not mean the CDA will be available to end-users. I recommend clicking the Select All button and then click Finish to import the CDA or Web Part. 
You have now successfully imported a CDA or Web Part and are ready to add it to an Access Center.
From time to time it might be necessary to remove unwanted CDAs from being deployed to all Agent servers in the Access farm. The following defines how to delete a CDA from the farm. 1. Open the Access Management Console and expand the farm node to reveal the CDAs node. 2. Right click on the CDAs node and click Delete From Server Farm. 
3. If you are sure you want to remove the CDA then click the Yes button to continue. 
4. MetaFrame Secure Access Manager will analyze all the pages in the farm to verify the CDA is not configured for use. If so then you will be presented with the following screen. If you are still sure of removing the CDA click the Yes to All button to continue. 
You have now successfully removed the desired CDA from the farm.
The following defines how to delete an Access Center from a MetaFrame Secure Access Manager 2.0 farm. 1. Open the Access Management Console, expand the Access farm, right click on the Access Center you would like to delete and click Delete Access Center. 
2. Click Yes to remove the Access Center. 
In the Access Center properties you will be able to enable and configure MetaFrame published application, server desktops and Secure Gateway for MetaFrame support. The following defines an Access Centers properties. 1. Open the Access Management Console, expand the farm, right click on the desired Access Center and click Properties. 
2. The CDAs tab allows you to configure the CDAs available to the Access Center. I would recommend you remove CDAs you know you will not be using. For example if you do not have Documentum installed then youre better off unselecting the CDA. You can always come back and re-enable it if needed. 
3. The Published Resources tab allows you to configure MetaFrame XP integration. By checking the Include resources from MetaFrame XP servers checkbox allows for MetaFrame XP published resources to be presented inside an Access Center. Uncheck to disable this feature. 
By checking the Allow users to choose MetaFrame XP server farms checkbox allows users to select which server farms to include in the access center. If you select this option, a list of all MetaFrame XP server farms assigned to the user appears in the Settings page for the Access Center. Users can choose their farms by selecting the Display checkbox on the users Settings page. Uncheck to disable this feature. 
By checking the Apply MetaFrame XP content redirection checkbox allows content to be launched with MetaFrame XP application based on file type association. This feature is based on file type associations set up in MetaFrame XP Click to select a MetaFrame XP farm and click the Delete button to remove the desired farm.
4. Click the Edit button to view / edit the properties of the MetaFrame XP farm. A. The General tab allows you to configure the desired MetaFrame XP farm. Enter the name of the MetaFrame XP farm in the MetaFrame XP server farm name text box 
B. The Servers tab allows you to add, delete and or edit a particular MetaFrame XP server. The Load balancing of requests to servers radio button allows you to load balance each XML Service request to a different server based on the sequence of the priority list. The first request is sent to the first server, the second to the second server, and so on. The Failover sequence for unavailable servers radio button allows for failover to the next server in the list if an error occurs while communicating with a server. 
a) Click to select a MetaFrame XP server and then click the Edit button to edit the name of the selected MetaFrame XP server. 
b) Click the New button and enter the name of a MetaFrame XP server in the corresponding farm. 
c) Click to select a MetaFrame XP server and then click the Delete button to remove the server from the list. C. The Address Mode tab allows you to specify how a specific IP address range will be routed to the MetaFrame XP server and MetaFrame Secure Access Manager servers. Clicking the New button allows you to create a new client IP address range and assign a server address mode to it. Clicking the Edit button allows you to edit the select client IP address range to change the name and or the server address mode. 
a) Click the Address Translation button to enter the MetaFrame XP servers address and translated address. 
a. Enter the appropriate addresses and ports and click OK when finished. 
b) Click the Secure Gateway button to configure the Secure Gateway configuration settings. Click OK when finished 
5. The User tab allows user to configure how MetaFrame published applications is displayed to end-users. You are able to configure sound, windows color, windows size and if the end-users are allowed to configure these settings through the settings page. 
6. Click to select the ICA Client that will be available to all users of the selected Access Center. Click OK when finished. 
7. The Secure Gateway tab allows you to configure the Secure Gateway for MetaFrame to route connections to Web servers in the access server farm as well as to other Web servers internal to your network. Click the New or Edit button to configure the FQDN name of an internal Web server that you want to make securely available to external users. 
MetaFrame Secure Access Manager 2.0 gives a slew of interfaces to customize the look and feel with. Although customization is very important it is a bit out of scope for this document. I do however have a great resource for you in MSAM in a Box (http://www.rnetworkx.com/MSAMIABv2.3-DRAFT.pdf) and I recommend CDA Exchange (http://www.cdaexchange.com). The following is a screen shot of the Pages and Folder properties page. 
In the Access Center People properties page you have the ability to configure authentication properties. The following defines how to configure the People properties. 1. Open the Access Management Console an, expand the farm node, expand the desired Access Center, right click on People and click Properties. 2. On the General tab you can configure how users authenticate to the Access center and how long they remain logged on, if idle, before they timeout and require re-authentication . In the Session Timeout text box enter the maximum amount of idle time, in minutes, before an end-user is logged out. Check the Authentication Required check box to force explicit logon to the selected Access Center. Check the Allow users to change password and check the Prompt when password expires in checkboxes to allow the end-users to change their own passwords and to be prompted to perform that change in case it is getting close to expiring. Enter the appropriate settings in the fields provided. In the remains fields the administrator has the ability to force a domain, allow the end-users to specify the domain and or select from a list of domains. Enter the desired configuration but do not that if you will be using Secure Gateway for MetaFrame then these settings will not be used and you will be required to configure these values through the Secure Gateway as discussed in the Secure Gateway for MetaFrame section of this document. 
In order to logon to MetaFrame Secure Access Manager 2.0 you will need to add users to the Access Center. MetaFrame Secure Access Manager 2.0 allow out of the box authentication Windows NT and Active Directory networks. The following defines how to add users to the selected Access Center. 1. Open the Access Management Console, expand the farm, expand the desired Access Center, expand the People node, right click to select Users and Groups and click Add Users and Groups. 
2. In the Select Users wizard you will want to drop down the Trusted domain combo box to select the domain or local machine and double click to add groups to the Configured users and groups listbox. You can also add individual users to the Access Center by checking the Show Users checkbox and double clicking on the desired user. 
3. The next screen you come to prompts you to select the role to associate to the users and or groups added in the previous step. Roles are used to group pages and folders. A user can be a member of multiple groups and multiple pages. To define the roll that will take precedence over others and will define the users home page you will want to click to select the desired roll and click the Set Primary button. Click Finish to add the desired users. 
A Role allows an administrator to group users according to their use of common applications, data, and other resources you provide in an access center. The following defines how to create a new role and assign users to it. 1. Open the Access Management Console, expand the farm, expand the desired Access Center, expand the People node, right click to select the Roles node and click New Role. 
2. Enter a name for the role in the Role name textbox. Enter a description for the role in the Role description textbox. Dropdown the Default theme combo box to select the desired theme for the new role. Click Next when fished. 
3. Click to check and select the CDAs the role member will have address to add an Access Center page through the Add menu item. Click Next when finished. 
4. Click to select the pages the role members will have access to and click on a page to specify it the roles homepage. This page will become the homepage of users who have been assigned the role as their primary role. Click Next when finished. 
5. Double click on the desired users and groups to add them to become member of the role. Click Finish to create the new Role. 
The first thing we need to do to create a useful Access Center is create folders which will contain the users pages. In the design phase you should have documented the basic folder structure for you new Access Center. I recommend keeping the numbers of folders to a minimum and at best only display four at a time. This will speed up the Access Center. The following defines how to create a Folder.
|