Configuring the CCF Developer Environment
Use the procedure in this section to configure the development environment for the customer service representative (CSR) features of CCF. This procedure assumes that the CCF program files are installed in a folder named CCF2009\Development. If you installed the CCF program files in a different folder, replace the example folder name with the name you used.
For information about installing the developer environment, see the CCF SP1 Deployment Guide.
To configure the CCF developer environment:
- Log on to the computer as an administrator.
- Click Start, and then click Run.
- In the Open box, type cmd, and then press Enter.
- Go to <Drive>\Program Files\Microsoft Visual Studio8\Common7\Tools, type vsvars32.bat, and then press Enter. This sets up the command-line build environment. (Alternatively, you could use the command prompt shortcut that installs with Visual Studio.)
- If necessary, delete all project-related files for both application and Web services, and delete the corresponding virtual directories created for the ContactCenter, CcfInfrastructure, AdminConsole, and AgentCredentials projects.
- Create an application pool named CCFAppPool to run under the Network Service account on the computer that is running IIS. Make sure that all CCF virtual directories run under the CCFAppPool application pool.
- The Webservice MSI installs a set of virtual directories. Right-click each virtual directory name, and then select Properties. Ensure that the listed properties are enabled.
Virtual Directory
Properties
Microsoft.Ccf.Csr.WebServices.ContactCenter
Set Anonymous Access to CcfAppPool.
Microsoft.Ccf.Csr.WebServices.CcfInfrastructure
Set Anonymous Access to CcfAppPool.
Microsoft.Ccf.Csr.WebServices.AgentCredentials
Set Anonymous Access to CcfAppPool.
Microsoft.Ccf.Csr.WebServices.AdminConsole
Set Anonymous Access to CcfAppPool.
Microsoft.Ccf.WebServices.Gateway
Set Anonymous Access to CcfAppPool (if necessary in your development environment).
- If you do not have access to a DNS server, add http://ccfiis to the trusted sites in Internet Explorer. Go to the host file located at <drive>\windows\system32\drivers\. Add entries for CCFIIS and CCFSQL to the host file, and point the entries to 127.0.0.1.
Note:Note: If you use Authorization Manager (AzMan) on Windows XP, the AzMan reference points to c:\Windows\Microsoft.NET\AuthMan\Microsoft.Interop.Security.AzRoles.dll. This DLL can be found on Windows 2003 Server systems, but it is not usually found on Windows XP. You can copy the DLL from a Windows 2003 Server system for compiling purposes. - Run BuildCCF.bat on the system that is running SQL Server.
- On the same system, change the password for the ASPNET user of the computer.
- If the computer is a domain controller, go to step 12.
If the computer is not a domain controller, add ASPUSER to the IIS_WPG group as follows:
- On the Start menu, right-click My Computer (or Computer on Windows Vista).
- On the sub-menu, click Manage.
- Expand System Tools, and then click Local Users and Groups.
- Double-click Groups, and then click IIS_WPG.
- Click Add, and then type <DomainName>\ASPUSER.
- Click OK.
- If the computer is a domain controller, you must add ASPUSER to the IIS_WPG group.
To add ASPUSER to the IIS_WPG group:
- On the Start menu, click Administrative Tools.
- Double-click Active Directory Users and Computers.
- Right-click IIS_WPG, and then click Properties.
- Click the Members tab.
- Click Add, and in the IIS Worker Process Group, type <DomainName>\ASPUSER.
- Click OK.
- Configure the identity of the DefaultAppPool to run under the ASPNET account. This is required because SQL scripts are used to give permissions to ASPNET users so that they can access the databases. Each folder has an access control list (ACL) that specifies the permissions for each user.
To check or change the ACL settings:
- In Windows Explorer, locate each folder identified in following table.
- Right-click the folder name, and then click Properties.
- Click the Security tab. The ACL check boxes are in the lower section of the pane. Use the settings shown in below table.
Folder Name
Default Location
Access Type
ASPUSER
C:\Windows\TEMP
Full control
ASP.NET Dynamic Compilation
C:\WINDOWS\Microsoft.NET\Frame work\v2.0\Temporary ASP.NET Files
Full control
ASP.NET Installation
C:\Windows\Microsoft.NET\Frame work\v2.0.xxxx
Read & Execute, List Folders Contents, Read
- Update the AzManStore keys in the Web.config file in the directories Microsoft.Ccf.Csr.WebServices.CcfInfrastructure and Microsoft.Ccf.Csr.WebServices.AdminConsole.
Make sure that they point to: C:\CCF\DemoData\AzManCCF.xml.
Note:The actual Web service names for Microsoft.Ccf.Csr.WebServices.CcfInfrastructure and Microsoft.Ccf.Csr.WebServices.AdminConsole in the configuration list are Microsoft.Ccf/Csr.WebServices.Providers.CcfInfrastructure.Application and Microsoft.Ccf/Csr.WebServices.Providers.AdminConsole.AgentWS, respectively. - To update the AzManStore keys:
- In the Admin Console, expand the configurations node and double-click the Web service.
- In the Properties window, click the Build button.
- In the Build Configuration Value window, highlight the AzMan key name, and then click Edit.
- In the Configuration Action window, make sure that the value for azManStore is C:\CCF\DemoData\AzManCCF.xml.
- Repeat steps a – d for the other Web service.
Note:Make sure that the AzManCCF.xml file, <InstallDir>\Program Files\Microsoft CCF 2009\Data\AzManCCF.xml, is not set to Read Only, because the ID must read andwrite to this file. - Update the authorization section in the Web services Web.Config file to authorize users who are in the CCF domain (for example, <allow roles="ccf\ccfusers" />). You may need to update the gateway to authorize all users (for example, <allow users =”*”/>), or another more specific group.
Note:Allowing all users is not recommended outside of a development or test environment because it defeats the purpose of an ACL. - Install the file Microsoft.Ccf.Csr.WebServices.AdminConsole.Setup.msi.
- Use the Admin Console MMC snap-in application to complete the following steps.
In the Admin Console:
- Use the Agents node to add yourself as an agent.
- Expand the Settings node, and then expand the General Settings node. Update the Options by changing the CtiType to 2 (this specifies that TAPI is to be used with the Softphone application).
- Expand the Settings node, and then expand the Phones node. Update the Options by adding a phone number for yourself. For example, configure the phone as Jane (3331). You can configure this phone number to any number in Softphone.
- Expand the Workflows node, and then configure your workflows.
- Expand the Application Mappings node, and then configure your hosted applications in the file<RootFolder>\SourceCode\CSR\WebServices\CcfInfrastructureWebServices\Application.asmx.cs and corresponding provider files, ApplicationProvider.cs and AzManApplicationProvider.cs. For more information about AzMan, see CCF 2009 SP1 Deployment Guide.