Q: Will I be able to manage services across multiple IIS servers?
A: AppFabric will not provide a distributed management experience. The PowerShell cmdlets and IIS Manager extensions are designed to configure only the local server, and each server in the farm needs to be managed individually. AppFabric will leverage the remoting capabilities in both IIS Manager and PowerShell, however, to allow the Administrator to configure multiple machines from one console.
Q: What is the motivation to use the IIS Manager instead of creating your own UI that could manage both WAS and non-WAS hosted services?
A: We believe that having a unified tooling experience to manage n-tier applications is value-add to our customers. IIS Manager supports such an experience by providing a set of features that are advantageous both for middle tier services as well as the Web applications. We also believe that there are significant similarities between managing the Web applications and WCF services. Therefore, admin users managing these classes of applications benefit from having a single UI (AppFabric) that provides a unified management experience.
Q: Do you provide a Web based UI to access my services remotely? Why do I need the local tools like IIS manager when most of my management is remote?
A: While there are significant benefits in using the Web based client for remote administration, in V1 we are focusing on the single node management for which IIS manager is the appropriate tool. If necessary IIS manager can be configured to access the server remotely.
Q: Do your tools support delegation and remoting?
A: Yes, just like with the IIS manager today we support delegation and remoting.
Q: Can I elevate my own settings to the first class level (i.e. be able to see them in the UI)?
A: Yes, you can also use the IIS manager extensibility to build custom UI for administering your applications.
Q: Do you provide cluster management tools? E.g. how do I add and remove nodes, monitor the load, make a config change etc.?
A: Managing the cluster is a general administration task that is not WCF/WF specific. We do provide the UI and PowerShell API to stop the WCF application (by stopping the message traffic). That allows the application to drain its state. After that the user can use the existing tools to stop the web server, Windows and then remove the server node from the cluster.
Q: Why do I have to use a different certificate configuration from the IIS certificate configuration?
A: This is an additional functionality that is specific to WCF/WF.
Q: How do existing tools that are used to configure WCF (e.g., Svc Config Editor) fit in the picture?
A: We intend to make the IT Admin experience for configuring WCF/WF applications easy. To this end, we will provide tooling capability in IIS Manager; Svc Config Editor exists to provide more comprehensive config editing experience for the WCF/WF developer.
Q: Do you plan to integrate existing monitoring tools such as Svc TraceViewer and Tracking Profile Editor into this new tooling?
A: Yes, we will eventually integrate tracking and tracing features to provide a rich experience for IT Admins to manage and monitor their WCF/WF applications.