Building portals, intranets, and corporate Web sites using Microsoft servers James J. Townsend, Dmitri Riz, Don Schaffer.

Por:

Townsend, James J

Colaborador(es):

Detalles de publicación: Boston, MA Addison-Wesley c2004.Descripción: xxii, 517 p. ill. 24 cmISBN:

0321159632

Tema(s):

Clasificación LoC:

TK5105.888 .T69 2004

Existencias
Imagen de cubierta	Tipo de ítem	Biblioteca actual	Biblioteca de origen	Colección	Ubicación en estantería	Signatura topográfica	Materiales especificados	Info Vol	URL	Copia número	Estado	Notas	Fecha de vencimiento	Código de barras	Reserva de ítems	Prioridad de la cola de reserva de ejemplar	Reservas para cursos
	Libro	Biblioteca de Mayagüez Colección General mb				TK5105.888 .T69 2004 (Navegar estantería(Abre debajo))					Disponible			50000002162336

Total de reservas: 0

Descripciones mejoradas de Syndetics:

& bull; Corporate Web portals are increasingly common, providing employees and customers with one easy to use online access point & lt;br/ & gt; & bull; Provides a high level yet practical overview of the concepts, technologies, and products used in building successful portals

gccoct2006

Tabla de contenidos provista por Syndetics

1 Introduction To Portals
Rise of the Portal
Portal Definitions
Types of Portals
Benefits of Portals
Attributes of Portals
Summary
2 Portal Elements
Look and Feel
Security
User Profile
Personalization
Taxonomy
Application Integration
Database and Other Repositories
Support for Transactions
Collaboration Tools
Multichannel support
Search Engine
Portal Solution Requirements Table
Putting the
NET Portal Together
3 Microsoft's Portal Strategy
The Microsoft Portal Perspective
Microsoft Office Group
Microsoft Enterprise Software Group
Microsoft Online Properties
Fundamental Portal Elements
Optional Portal Elements
Third Party Portal Elements
Future Evolution of Portal Platform to Juniper and Beyond
Migration of Server Products to .NET
Conclusion: A Two-Pronged Portal Effect
4 Web Services
Introduction
What Was Life Like Before Web Services?
Current Technologies
What Are Web Services?
When Does It Make Sense to Develop/Deploy a Web Service?
How Do Web Services Fit Into the Portal?
Sample Web Service
Web Service Benefits
Conclusion
5 Portal Framework-.Net
Introduction
The .NET Fundamentals
Building Blocks of the .NET Framework..NET versus Other Applications
The Portal Architecture
The Portal Framework
Conclusion
6 Security Services
Common Security Issues
Building Blocks of Secure Application
Authentication and Authorization Flow
IIS Authentication Methods.ASP .NET Authentication Methods.Web Services Authentication.ASP .NET Process Identity
Code Access Security and .NET Framework
Microsoft SQL Server Security
Microsoft Internet Security and Acceleration (ISA) Server 2000
Desigining a Security Strategy
Security Model Changes in Windows Server 2000
Example: Securing an Intranet or Extranet Portal
Summary
7 User Profiles
Identifying Key User Groups
Registration Methods
Creating User Profiles with Self Registration
Self Registration with Commerce Server 2002
Profile Information
Administering the Profile
Tracking Anonymous Users
Defining SPS Profiles
SharePoint Audiences
SharePoint Single Sign-On
Analyzing Profile and Data
8 Personalization
The Personalization Cycle
Creating Content for Personalization
Personalizing Homepage Content
Subscriptions, Notifications and Alerts
Advertising Based on Profiles
Getting More Out of Personalization
9 Content Management
Measuring Return on Investment for Content Management
Content Management Options
Site Framework For Content Management
Content Management Server Overview
Site Framework for Content Management Server
Sharing the Portal Site in MCMS
Creating Templates
Content Creation and Approval Process
Defining Channels
Multilingual Sites
Web Page Workflow Implementation
Enabling Security on MCMS..NET and Web Services Integration
Content Management in SharePoint
Integrating SharePoint with Microsoft Content Management Server
Custom Content Management
Conclusion
10 Developing Portal Taxonomy
What Is Taxonomy?Taxonomy Concepts
Sample Taxonomy
Taxonomy Best Practices
Taxonomy Implementation
Ways to Instantiate Taxonomies
Business Value of the Taxonomy
11 Integrating Line Of Business Applications
Integration Concepts
Providing Intelligent Forms
SharePoint Portal Server and EAI
Integration with Custom Code
BizTalk Concepts
BizTalk Components
Accelerators and Third Party Tools
Benefits of Business Integration
Conclusion
12 Collaboration In The Enterprise Portal
Collaboration Checklist
The Human Side of Collaboration
SharePoint Version 2 Paradigm
Windows SharePoint Services and SharePoint Portal Server
Creating a Basic Collaboration Site
Creating a Discussion Board
Document Management
Project Teams
Enabling Self-Service Site Creation
Online Conferencing
Understanding Web Parts
Integrating SharePoint Portal Server with Content Management Server
Additional Resources
13 Search Engine
Introduction
Search Concepts
Microsoft Indexing Service
Managing Search Settings in SharePoint Portal Server
Managing Search Schedul

Extracto provisto por Syndetics

Not even the implosion of the dot com bubble was enough to derail the proliferation of Internet technology and the move toward "e-business" that has extended to nearly every industry in the developed world. Few organizations are content to tolerate the isolation of applications into separate "silos" of information, or poor interoperability among their software solutions. The portal has been held up as a means to achieve better application integration and provide a consistent user interface both inside and outside the enterprise. Companies and other organizations need to take a broader look at their portal strategy to make the various elements of their architecture work together. This is a pivotal time not only in the emergence of new technology but the convergence of technologies toward open standards and enhanced interoperability. Audience and Goals for this Book The portal market is an amorphous and elusive target, with a small number of universal standards and a large population of vendors attempting to define in ways that are most beneficial for their product sales. The first generation of portal books were devoted to explaining why portals were such a good idea, and how they would benefit their users. The bulk of these were devoted to enterprise portals, and to extolling the virtues of extensible markup language (XML). Others were devoted to explaining how to use a single product with portal in the name, such as Oracle Portal or Microsoft SharePoint Portal Server, but only covered a small portion of the features that an organization might reasonably want to include in a portal. While these works are helpful and necessary, the theoretical portal books don't go far enough in explaining how to implement their solutions. Some of the theories that were expounded in early portal books were not borne out by experience in the software market. The single product books can go no further than the products themselves, leaving you with half or less of the solution you had in mind. This book is a practical guide for developers and information technology managers, conveying what elements make up a portal, and how to construct these elements using the Microsoft development platform. It is a combination of introductions to key concepts, suggestions for portal planning, and limited detailed technical instruction by way of examples that relate to all the main portal elements. Most chapters consist of two parts, one describing what to build, and the second showing how to build it. The most important section for managers is the first five chapters. These first chapters address the portal from the perspective of a user and provide valuable background that can help the manager form reasonable project expectations. This section is not focused on individual products and features. Indeed, portals with the functionality described here could be implemented with a number of different technologies and products than are offered in the second part of the book. Developers will spend more time with the rest of the book to understand how to fill the gap between products and where each portal service belongs. They will want to review the early chapters to understand the vision for a .NET portal, and to ensure that the IT manager doesn't know anything that they don't. These later chapters do not attempt to restate the vast amount of information in help files and product documentation for the products used in our examples. Rather, our goal is to create a higher level overview that encompasses multiple products and puts each product and feature in its proper place. We also highlight best practices and hints that are not found in the product documentation but can save many hours of work or frustration. Expectations for this Book No single product provides the infrastructure and tools needed to build a full featured portal. Therefore we have had to include a number of server and development products to fill each niche in our portal ecosystem. Prerequisites There are no prerequisites for this book, as it attempts to define new concepts as they are introduced, and to explain the anatomy of a portal from the ground up. The goal is to provide a compelling vision for portals that can be applied to your business requirements, and to explain in detail how this vision maps to the Microsoft .NET framework and Web services. This book does not attempt to teach much of the fundamental knowledge and techniques that are required to be a successful and productive developer. For instance, it does not provide background information on the following fundamental topics: Relational database concepts Web development technologies other than .NET Networking and security Object-oriented programming The source code examples included in this book are not sufficient to learn any of the products that are used for examples, nor is the code presented all that would be needed for a full portal implementation. In other words, we are not going to be eliminating any jobs in the information technology service industry by publishing this book. The code examples are intended to be illustrative and inspirational, getting the reader off to a strong start in building a solution. Software Requirements To work through all the code examples in this book, you will need the following products: Visual Studio.NET Commerce Server 2002 Content Management Server SharePoint Portal Server (version 2) Microsoft Office 2003 BizTalk Server SQL Server 2000 Windows 2000 or Windows XP Internet Information Server Although it may possible to configure a single server with all these products, a more practical development environment would be to allocate one server for SQL Server, one as the Web server, and one for everything else. The number of servers required for a full implementation is discussed in Chapter 14, Portal Scalability. There has never been a better time to enrich your organization's Web presence. We hope you enjoy learning about portals and putting these ideas into practice. Excerpted from Building Portals, Intranets, and Corporate Web Sites Using Microsoft Servers by James J. Townsend, Dmitri Riz, Deon Schaffer All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.

Notas de autor provistas por Syndetics

Deon Schaffer has been developing with Visual Basic and other Microsoft technologies for more than seven years. Over the past few years, Deon's focus has been on designing and developing Windows DNA applications. He is a Microsoft Certified Solutions Developer (MCSD) and has a degree in information systems engineering. Deon is a senior consultant at Information Strategies in Washington, DC.

0321159632AB11202003

Imprimir
Citar
Agregar a su carrito (remover)
Guardar registro
BIBTEX Dublin Core ISBD MARC (no-Unicode/MARC-8) MARC (Unicode/UTF-8) MARC (Unicode/UTF-8, Estándar) MARCXML MODS (XML) RIS
Más búsquedas

Buscar este título en:
HORIZON