究竟门户技术能够整合什么讲义(pdf 62页)（英文版）

究竟门户技术能够整合什么讲义目录：
一、.A Business Person’s Guide to Enterprise Portal Terms and Business Impacts.....1
二、.Purpose..............................1
三、.Table of Contents..........................2
四、.The Promise of a Portal.........................3
五、.Evaluation .............................3
六、.Perspective ............................4
七、.Organization – Categorizing Portal Functionality.................5
八、.Infrastructure..........................8
九、.INTEGRATION ...........................8
十、.INTERNATIONALIZATION........................12
十一、.SCALABILITY ..........................16
十二、.SECURITY.............................18
十三、.STANDARDS.............................23
十四、.Operations .............................26
十五、.ADMINISTRATION..........................27
十六、.DEVELOPMENT ENVIRONMENT.....................31
十七、.EASE OF UPGRADE.........................33
十八、.FEDERATED PORTALS.......................34
十九、.Features..............................36
二十、.BUSINESS INTELLIGENCE ........................37
二十一、.COLLABORATION...........................40
二十二、.CONTENT MANAGEMENT........................42
二十三、.DOCUMENT MANAGEMENT ....................45
二十四、.PERSONALIZATION........................47
二十五、.SEARCH.............................49
二十六、.WORKFLOW.............................52
二十七、.Presentation...........................54
二十八、.END-USER CUSTOMIZATION.......................54
二十九、.USER INTERFACE ...........................58
三十、.WIRELESS.............................60

 

究竟门户技术能够整合什么讲义内容提要：
Perspective
A Portal’s scope is broad — traversing internal and external systems, behind the firewall and dispersed throughout the Internet. Its charter is ambitious —from
knowledge management to employee self-service to supply-chain management. No other type of eBusiness software touches upon as many different
technologies, issues, and concepts as do enterprise portals. Because of this, the portal market can be difficult to navigate from both a busines and technological
perspective.
There are many different vendors with portal products, all of which have their unique strengths and backgrounds. Because each vendor is positioning its
strengths and saying “me too” to the market, the literature and sales materials are littered with jargon and lack clarity. The fundamental problem is that there is
no generally accepted market definition or lists of RFP criteria, and there is a general lack of consistency in terms. This makes it difficult to easily understand
and compare the merits of portal products from different vendors.
For the businessperson, we recommend the following: identify the functionality that a portal should posess, state the primary business objective of each function,
and then evaluate solutions and their functionality based upon the ability to deliver direct business value.
Market Projection
2001 is the year of consolidation for the portal market. The small pure-play portal vendors that started the market are now being challenged on two fronts.
First, there is a challenge to these vendors by several global business application providers such as PeopleSoft and SAP (weighing in with a focus on business
solutions delivery). Second, pure-play portals are confronted by the large integration tool providers such as IBM and BEA (attacking the technology integration
problems). This change in the market is creating a clear split between “integration” focused portal technology tools and “application” focused portal business
solutions.
It is always risky to predict the future. But it is our strong belief that the market will split into two distinct categories and by the end of 2002:
1. Application focused portal solutions for business solutions delivery (functional), and
2. Technology focused portal solutions that support the underlying technology and software integration (middleware systems).
It is highly likely that the “application” portal will be sold with traditional ERP and CRM solutions because of the inherently high savings in integration costs in
using a single vendor. The “technology” portal will be used to perform back-end integration of homegrown and best-of-breed solutions that sit below the user’sview of the world.

..............................