List of Figures | Microsoft .NET: Jumpstart for Systems Administrators and Developers (Communications (Digital Press))

< Day Day Up >

Chapter 1: Introducing .NET

Figure 3.1: Visual Studio .NET showing the startup wizard and basic IDE.
Figure 3.2: New Project Window in Visual Studio.NET.
Figure 3.3: Solution Explorer window.
Figure 3.4: Server Explorer window.
Figure 3.5: Visual Basic upgrade wizard.
Figure 3.6: Once upgraded, a task list appears, and the code that needs changing is highlighted.
Figure 3.7: Visual Studio and the CLR.
Figure 3.8: When building a Web form, Visual Studio automatically builds a corresponding Web site infrastructure.
Figure 3.9: Components in the toolbox.

Figure 4.1: A typical connection scenario.
Figure 4.2: Hub-and-spoke EAI.
Figure 4.3: BizTalk Server supports a number of different file formats and submission routes.
Figure 4.4: Comparing Web services and BizTalk Server.
Figure 4.5: Setting up Receive function properties for an advanced shipping notice.
Figure 4.6: Messaging port properties using an SAP integration component.
Figure 4.7: Setting new channel properties.
Figure 4.8: The BizTalk Editor.
Figure 4.9: Business process orchestration.
Figure 4.10: BizTalk server components.
Figure 4.11: Biztalk Mapper with three functoids to assist the transformations.
Figure 4.12: MQSeries and BizTalk Server architecture.
Figure 4.13: Receiving an IDoc from SAP.
Figure 4.14: Sending an IDoc to SAP.
Figure 4.15: Hubbased BizTalk Server for small and medium-sized organizations.
Figure 4.16: Using BizTalk Server as a data bus.
Figure 4.17: Secure BizTalk configuration for Web access.
Figure 4.18: BizTalk redundant server group.
Figure 4.19: BizTalk partitioned or specialized server group.

Figure 5.1: Typical Commerce Server-based Web site.
Figure 5.2: Commerce Server pipeline.
Figure 5.3: Setting pipeline component properties.
Figure 5.4: Commerce Server architecture.
Figure 5.5: Commerce Server Manager.
5.6: The business desk.
5.7: The product catalog.
Figure 5.8: Typical Commerce Server payment architecture.
Figure 5.9: Batch payments offer a low-cost entry point for a Commerce Server Web site.
5.10: Importing a catalog into Commerce Server.

Figure 7.1: Before content management tools were developed, Web site authors would become an expensive bottleneck.
Figure 7.2: With content management products, templates are built and then any end user with appropriate rights can submit content.
Figure 7.3: HTML placeholders in Content Management Server.
7.4: Page editing.
Figure 7.5: Setting publishing attributes.
Figure 7.6: Serial approval.
Figure 7.7: Parallel single approval.
Figure 7.8: Parallel all approval.
Figure 7.9: Publishing workflow in Microsoft Content Management Server.
Figure 7.10: Site Stager in Microsoft Content Management Server.
Figure 7.11: Server Configuration Application.

Figure 8.1: Application Center Server balancing workload and content.
Figure 8.2: Application Center cluster.
Figure 8.3: The general Web cluster.
Figure 8.4: COM+ application cluster.
Figure 8.5: COM+ routing cluster.
Figure 8.6: NLB balancing workload across multiple servers.
Figure 8.7: Failover-the site continues to be available as other member servers pick up the workload.
Figure 8.8: Adding additional servers will see the workload automatically redistributed across the cluster.
Figure 8.9: Change based synchronization.
Figure 8.10: Interval-based synchronization with timed updates.
Figure 8.11: Member synchronization.
Figure 8.12: Cluster synchronization.
Figure 8.13: Application synchronization.

Figure 9.1: Typical Web service.
Figure 9.2: Distributed Applications-DCOM versus SOAP.
Figure 9.3: SOAP in action.
Figure 9.4: UDDI network with nodes containing copies of registered Web service information.
Figure 9.5: GetGarmentSales Web service.
Figure 9.6: .NET MyServices in action.

Figure 11.1: A typical portal.
Figure 11.2: The Web Parts catalog allows users to customize their portals.
Figure 11.3: SharePoint Portal Server-Managing the users and creating personal dashboards.
Figure 11.4: Categories in SharePoint Portal Server.
Figure 11.5: Document Library with document status and version control.
Figure 11.6: Serial approval process.
Figure 11.7: Parallel single- Any one approver can authorize the document.
Figure 11.8: Parallel all-All approvers must authorize the document.
Figure 11.9: SharePoint Portal Server architecture.
Figure 11.10: Small departmental solution.
Figure 11.11: Search Services with Single SharePoint Portal Server.
Figure 11.12: Multiple SharePoint Portal Server covering different tasks in a larger installation.
Figure 11.13: Large-scale, organization-wide installation.
Figure 11.14: Organizational use of SharePoint can improve project collaboration.

< Day Day Up >