- Văn bản
- Lịch sử
Reuse of existing applications duri
Reuse of existing applications during the development of Enterprise Portals integrating Web Services
M. Gharzouli M. Boufaida, L. Seinturier
Lire laboratory, Department Lire laboratory, Department LIFL UMR CNRS 8022
of Computer Science, Mentouri of Computer Science, Mentouri Bâtiment INRIA Haute-Borne
University of Constantine, University of Constantine, 59655 Villeneuve d'Ascq Cedex
25000, Algeria 25000, Algeria France
gharzouli_mohamed@yahoo.fr
boufaida@hotmail.com
Lionel.Seinturier@lifl.fr
Abstract
During these last years, the use of the web technologies in the enterprises becomes an essential factor to define a new business model. Among these technologies, web services and enterprise portals have gathered to integrate existing heterogeneous systems such as e-commerce, e- services hub and e-learning. However, the design and the modeling of the portals, on the one hand, and their integration with the existing applications, on the other hand, are still two points open for discussion. The first problem is related to the development of the lifecycle that can be used for designing and modeling the enterprise portals. For the second problem, which is the integration of the existing applications, the discussion is intended towards the use of technologies based on web services. In This paper, we present a software engineering solution for the development of Web services-based enterprise portals.
Keywords: Development process, Enterprise Portals, Reuse of existing application, Web services.
1. Introduction
The concept of Enterprise Portal (EP) has received much attention since the success of public portals on the Web like Yahoo! and MSN. It is increasingly being used to refer to vertical web sites that feature personalization/customization, cross-platform usability, distributed access, management, and security of information and services within a particular enterprise/industry, thus the so called enterprise, corporate or vertical portals [4]. Portal technology can be targeted towards external users (B2C and B2B) or/and internal users (B2E). It is a tool that incorporates on only one personalized screen, according to the profile of each user, all information and applications he needs to work with [1]. The EP decreases the spent time of searching information with giving the possibility to reach separate sources of information [12].
Progressively, portals have become a need for many famous companies like IBM, Microsoft and Plumtree.
These later offer packaged solutions on a variety of platforms. However, these packages lack interoperability in general and synchronization among the various components in particular. Furthermore, they are very expensive [17]. For this reason, the common enterprises choose the "home development" of the portal solution. Moreover, one of the key properties of the portal is that it is built of heterogeneous applications. So, it is necessary to use a tool that permits the interoperability between the portal and the different applications.
In this direction, the use of Web services is considered to be a good solution for creating a homogeneous environment [11]. The web services architecture is based on three elements: the service provider, the discovering agency and the service requestor [13], [10], [5]. If a company wants to develop a portal based on web services architecture, it defines the role of the service provider and those of the service requestor. So, the development of such a portal requires firstly the preparation and the construction of its contents by re-using existing applications.
In this paper, we describe a methodology for the development of the web services for the enterprise portals with re-using existing applications. This methodology explains how we can develop initially the web services and then how to consume them through the portal.
In the following, we present an important aspect that is related to the use of interoperable web services for computational portals. After having presented the various steps of our methodology, we provide a comparison between some related works and our approach and we finish with a conclusion and some prospects.
2. Web services for Enterprise Portals
Recently, Web services and enterprise portals have gathered to integrate heterogeneous systems such as e- commerce, e-services hub and e-learning [16]. To ensure the interoperability in the various types of portals, Web services form an adequate and effective solution. The portal needs to reach heterogeneous information sources and re-uses existing applications. Web services answer
these constraints because they offer a high degree of interoperability. The three basic standards WSDL, UDDI and SOAP make possible the description, the publication and the invocation of Web services [2], [6], [7], [10].
The basic interaction of the web services for a portal is
based on a separation between the server that manages the user interface and the one that uses a particular service [11]. In the case of an enterprise portal, the SOAP server can be internal i.e. located on an Intranet. In this case, the provided services can be invoked via SOAP by using the local network area. If the SOAP server is external, the interaction is made via an Extranet or the Internet network.
3. An integration process of web services in the
Enterprise Portals
Currently, there are several products that are offered by various editors of EP solutions. However, each editor has his own development methodology. For the internal development, the enterprises use generally the methods and the processes for the modeling of the web applications. But the solution, which is the most common, is to use RUP for the process and UML for the notation [8], [9].
The difficulty that arises for these methods is that they are oriented to the development of new applications. However, the enterprise portals reuse generally existing applications.
In the following, we give the great steps to be followed for the development of an enterprise portal providing a single and personalized access point to different internal (inside the enterprise) and external services. The proposed process is intended for the development of the enterprise portals. It is a generic and global methodology, i.e. it is not specified for a particular type of portals.
The main objective of this process is the integration of the existing application through the use of the web services.
Users and portal specification
It describes how to transform the existing applications into a set of services and to add new components developed inside the company and the external services. This process is iterative and it follows the RUP process i.e. the phases are carried out in a repetitive way until that the all requirements are accomplished. It is divided into six steps (fig.1): specification, analysis, re-use of the existing applications, design of the user interfaces, implementation and management.
3. 1 Global specification phase
The goal of this phase is to determine the orientation of the project. In other words, the general objective is to give the broad outline of the portal in order to determine the list of the internal and external systems that will be interact with the enterprise portal and to conclude which are the various users of this last.
Generally, the internal systems (sub systems) are the departmental Intranets of the enterprise. Each one can contain one or several applications, which use various data sources. The external systems are generally provided by the partner companies. These systems are accessible through an Extranet or Internet, as they can be public web sites, which provide useful services and functionalities for the enterprise (for example, a purse service).
It is also necessary to determine the needs of the enterprise with giving answers to several questions:
• What is the objective of the portal that the enterprise wants to develop?
• What are the future users of the portal?
• What are the services which the company wants to provide to the users?
• What are the partners that will participate in the project?
At the end of the specification phase, the designer can determine and evaluate the complexity of the project.
Specification
List of useful existing applications +
Analysis
functional needs Users' management
List of reused methods + the method that will be developed +…..
Interaction diagrams
Re-use of the existing
applications
Design of the UI
rules
Design diagrams of UIs
Implementation
Management
Figure 1. Different steps of the development process
3. 2 Analysis phase
After the determination of the type of portal and the various types of the future users in the previous step, this phase has two principal objectives: the definition of the functional needs and the management of the users.
3. 2.1 Definition of the functional needs
During this step, one can define the global contents of the portal. After the determination of the basic list of the different services, the dialogue with the users and the observation of the daily activities, enable us to enrich the list of the services. Several interesting information can be recovered for this step, for instance: the list of the internal applications those are useful for the project, technologies with which these applications have been developed, categories of users and management rules used in each internal system (or sub system).
3.2.2 Users management
After the determination of the portal contents, one can process very important aspects related to the operational requirements of portal, the access control and user authentication. All these functions are essential factors for the personalization and the creation of the user profiles
M. Gharzouli M. Boufaida, L. Seinturier
Lire laboratory, Department Lire laboratory, Department LIFL UMR CNRS 8022
of Computer Science, Mentouri of Computer Science, Mentouri Bâtiment INRIA Haute-Borne
University of Constantine, University of Constantine, 59655 Villeneuve d'Ascq Cedex
25000, Algeria 25000, Algeria France
gharzouli_mohamed@yahoo.fr
boufaida@hotmail.com
Lionel.Seinturier@lifl.fr
Abstract
During these last years, the use of the web technologies in the enterprises becomes an essential factor to define a new business model. Among these technologies, web services and enterprise portals have gathered to integrate existing heterogeneous systems such as e-commerce, e- services hub and e-learning. However, the design and the modeling of the portals, on the one hand, and their integration with the existing applications, on the other hand, are still two points open for discussion. The first problem is related to the development of the lifecycle that can be used for designing and modeling the enterprise portals. For the second problem, which is the integration of the existing applications, the discussion is intended towards the use of technologies based on web services. In This paper, we present a software engineering solution for the development of Web services-based enterprise portals.
Keywords: Development process, Enterprise Portals, Reuse of existing application, Web services.
1. Introduction
The concept of Enterprise Portal (EP) has received much attention since the success of public portals on the Web like Yahoo! and MSN. It is increasingly being used to refer to vertical web sites that feature personalization/customization, cross-platform usability, distributed access, management, and security of information and services within a particular enterprise/industry, thus the so called enterprise, corporate or vertical portals [4]. Portal technology can be targeted towards external users (B2C and B2B) or/and internal users (B2E). It is a tool that incorporates on only one personalized screen, according to the profile of each user, all information and applications he needs to work with [1]. The EP decreases the spent time of searching information with giving the possibility to reach separate sources of information [12].
Progressively, portals have become a need for many famous companies like IBM, Microsoft and Plumtree.
These later offer packaged solutions on a variety of platforms. However, these packages lack interoperability in general and synchronization among the various components in particular. Furthermore, they are very expensive [17]. For this reason, the common enterprises choose the "home development" of the portal solution. Moreover, one of the key properties of the portal is that it is built of heterogeneous applications. So, it is necessary to use a tool that permits the interoperability between the portal and the different applications.
In this direction, the use of Web services is considered to be a good solution for creating a homogeneous environment [11]. The web services architecture is based on three elements: the service provider, the discovering agency and the service requestor [13], [10], [5]. If a company wants to develop a portal based on web services architecture, it defines the role of the service provider and those of the service requestor. So, the development of such a portal requires firstly the preparation and the construction of its contents by re-using existing applications.
In this paper, we describe a methodology for the development of the web services for the enterprise portals with re-using existing applications. This methodology explains how we can develop initially the web services and then how to consume them through the portal.
In the following, we present an important aspect that is related to the use of interoperable web services for computational portals. After having presented the various steps of our methodology, we provide a comparison between some related works and our approach and we finish with a conclusion and some prospects.
2. Web services for Enterprise Portals
Recently, Web services and enterprise portals have gathered to integrate heterogeneous systems such as e- commerce, e-services hub and e-learning [16]. To ensure the interoperability in the various types of portals, Web services form an adequate and effective solution. The portal needs to reach heterogeneous information sources and re-uses existing applications. Web services answer
these constraints because they offer a high degree of interoperability. The three basic standards WSDL, UDDI and SOAP make possible the description, the publication and the invocation of Web services [2], [6], [7], [10].
The basic interaction of the web services for a portal is
based on a separation between the server that manages the user interface and the one that uses a particular service [11]. In the case of an enterprise portal, the SOAP server can be internal i.e. located on an Intranet. In this case, the provided services can be invoked via SOAP by using the local network area. If the SOAP server is external, the interaction is made via an Extranet or the Internet network.
3. An integration process of web services in the
Enterprise Portals
Currently, there are several products that are offered by various editors of EP solutions. However, each editor has his own development methodology. For the internal development, the enterprises use generally the methods and the processes for the modeling of the web applications. But the solution, which is the most common, is to use RUP for the process and UML for the notation [8], [9].
The difficulty that arises for these methods is that they are oriented to the development of new applications. However, the enterprise portals reuse generally existing applications.
In the following, we give the great steps to be followed for the development of an enterprise portal providing a single and personalized access point to different internal (inside the enterprise) and external services. The proposed process is intended for the development of the enterprise portals. It is a generic and global methodology, i.e. it is not specified for a particular type of portals.
The main objective of this process is the integration of the existing application through the use of the web services.
Users and portal specification
It describes how to transform the existing applications into a set of services and to add new components developed inside the company and the external services. This process is iterative and it follows the RUP process i.e. the phases are carried out in a repetitive way until that the all requirements are accomplished. It is divided into six steps (fig.1): specification, analysis, re-use of the existing applications, design of the user interfaces, implementation and management.
3. 1 Global specification phase
The goal of this phase is to determine the orientation of the project. In other words, the general objective is to give the broad outline of the portal in order to determine the list of the internal and external systems that will be interact with the enterprise portal and to conclude which are the various users of this last.
Generally, the internal systems (sub systems) are the departmental Intranets of the enterprise. Each one can contain one or several applications, which use various data sources. The external systems are generally provided by the partner companies. These systems are accessible through an Extranet or Internet, as they can be public web sites, which provide useful services and functionalities for the enterprise (for example, a purse service).
It is also necessary to determine the needs of the enterprise with giving answers to several questions:
• What is the objective of the portal that the enterprise wants to develop?
• What are the future users of the portal?
• What are the services which the company wants to provide to the users?
• What are the partners that will participate in the project?
At the end of the specification phase, the designer can determine and evaluate the complexity of the project.
Specification
List of useful existing applications +
Analysis
functional needs Users' management
List of reused methods + the method that will be developed +…..
Interaction diagrams
Re-use of the existing
applications
Design of the UI
rules
Design diagrams of UIs
Implementation
Management
Figure 1. Different steps of the development process
3. 2 Analysis phase
After the determination of the type of portal and the various types of the future users in the previous step, this phase has two principal objectives: the definition of the functional needs and the management of the users.
3. 2.1 Definition of the functional needs
During this step, one can define the global contents of the portal. After the determination of the basic list of the different services, the dialogue with the users and the observation of the daily activities, enable us to enrich the list of the services. Several interesting information can be recovered for this step, for instance: the list of the internal applications those are useful for the project, technologies with which these applications have been developed, categories of users and management rules used in each internal system (or sub system).
3.2.2 Users management
After the determination of the portal contents, one can process very important aspects related to the operational requirements of portal, the access control and user authentication. All these functions are essential factors for the personalization and the creation of the user profiles
0/5000
Tái sử dụng các ứng dụng hiện có trong sự phát triển của cổng doanh nghiệp tích hợp dịch vụ WebM. Gharzouli M. Boufaida, L. SeinturierLire phòng thí nghiệm, Phòng thí nghiệm vùng Lire, vùng LIFL UMR CNRS 8022Khoa học máy tính, Mentouri của khoa học máy tính, Mentouri Bâtiment INRIA Haute-BorneTrường đại học của Constantine, trường đại học của Constantine, 59655 Villeneuve d'Ascq Cedex25000, Algérie 25000, Algérie Phápgharzouli_mohamed@Yahoo.frboufaida@hotmail.comLionel.Seinturier@lifl.fr AbstractTrong những năm qua, việc sử dụng các công nghệ web trong các doanh nghiệp sẽ trở thành một yếu tố cần thiết để xác định một mô hình kinh doanh mới. Trong số các công nghệ, Dịch vụ web và cổng doanh nghiệp đã tập hợp để tích hợp hệ thống không đồng nhất hiện có như thương mại điện tử, e-dịch vụ trung tâm và e-learning. Tuy nhiên, thiết kế và mô hình của các cổng, một mặt, và hội nhập của họ với các ứng dụng hiện có, mặt khác, là vẫn còn hai điểm mở cho cuộc thảo luận. Vấn đề đầu tiên liên quan đến sự phát triển của vòng đời có thể được sử dụng cho thiết kế và mô hình hóa các cổng thông tin doanh nghiệp. Vấn đề thứ hai là sự tích hợp của các ứng dụng hiện tại, các cuộc thảo luận dự định đối với việc sử dụng các công nghệ dựa trên dịch vụ web. Trong bài này, chúng tôi trình bày một giải pháp phần mềm kỹ thuật cho sự phát triển của cổng doanh nghiệp dịch vụ dựa trên Web.Từ khóa: Quá trình phát triển, cổng doanh nghiệp, tái sử dụng ứng dụng hiện có, Web dịch vụ.1. giới thiệuKhái niệm của doanh nghiệp cổng thông tin (EP) đã nhận được nhiều sự chú ý từ sự thành công của khu vực cổng trên Web như Yahoo và MSN. Nó đang ngày càng được sử dụng để đề cập đến các trang web theo chiều dọc mà tính năng cá nhân hóa/tuỳ biến, khả năng sử dụng cross-nền tảng, truy cập phân phối, quản lý và bảo mật của thông tin và dịch vụ trong một doanh nghiệp cụ thể/công nghiệp, vì vậy gọi là doanh nghiệp, doanh nghiệp hoặc dọc cổng [4]. Cổng thông tin công nghệ có thể được nhắm mục tiêu hướng tới người dùng bên ngoài (B2C và B2B) hoặc / và người dùng nội bộ (B2E). Nó là một công cụ mà kết hợp trên màn hình chỉ có một cá nhân, theo hồ sơ của mỗi người dùng, tất cả thông tin và ứng dụng ông cần phải làm việc với [1]. EP giảm dành thời gian tìm kiếm các thông tin với khả năng tiếp cận nguồn riêng biệt của thông tin [12].Dần dần, cổng đã trở thành một nhu cầu cho nhiều công ty nổi tiếng như IBM, Microsoft và Plumtree. Những sau đó cung cấp các giải pháp đóng gói vào một loạt các nền tảng. Tuy nhiên, những gói thiếu khả năng tương tác nói chung và đồng bộ hóa giữa nhiều thành phần đặc biệt. Hơn nữa, họ đang rất tốn kém [17]. Vì lý do này, các doanh nghiệp thường chọn phát triển nhà"" của các giải pháp cổng thông tin. Hơn nữa, một trong các thuộc tính quan trọng của cổng thông tin là nó xây dựng các ứng dụng không đồng nhất. Vì vậy, nó là cần thiết để sử dụng một công cụ cho phép khả năng tương tác giữa các cổng và các ứng dụng khác nhau.Theo hướng này, việc sử dụng các dịch vụ Web được coi là một giải pháp tốt cho việc tạo ra một môi trường đồng nhất [11]. Kiến trúc dịch vụ web dựa trên ba yếu tố: các nhà cung cấp dịch vụ, các cơ quan phát hiện và dịch vụ requestor [13], [10], [5]. Nếu một công ty muốn phát triển một cổng thông tin dựa trên web dịch vụ kiến trúc, nó xác định vai trò của các nhà cung cấp dịch vụ và những dịch vụ requestor. Vì vậy, sự phát triển của một cổng thông tin yêu cầu thứ nhất việc chuẩn bị và xây dựng nội dung của nó bằng cách tái sử dụng ứng dụng hiện có.Trong bài này, chúng tôi mô tả một phương pháp để phát triển các dịch vụ web cho cổng doanh nghiệp với tái sử dụng ứng dụng hiện có. Phương pháp này giải thích làm thế nào chúng tôi có thể phát triển ban đầu các dịch vụ web và sau đó làm thế nào để tiêu thụ chúng thông qua cổng thông tin.Năm sau, chúng tôi trình bày một khía cạnh quan trọng liên quan đến việc sử dụng các dịch vụ web tương thích cho các tính toán cổng. Sau khi có trình bày các bước khác nhau của phương pháp của chúng tôi, chúng tôi cung cấp một so sánh giữa một số tác phẩm liên quan và cách tiếp cận của chúng tôi và chúng tôi kết thúc với một kết luận và một số khách hàng tiềm năng.2. web dịch vụ cho các doanh nghiệp cổngGần đây, các dịch vụ Web và cổng doanh nghiệp đã tập hợp để tích hợp các hệ thống không đồng nhất như thương mại điện tử, e-dịch vụ trung tâm và e-learning [16]. Để đảm bảo khả năng tương tác trong các loại khác nhau của cổng thông tin, Dịch vụ Web tạo thành một giải pháp đầy đủ và hiệu quả. Cổng thông tin nhu cầu để đạt được các nguồn thông tin không đồng nhất và tái sử dụng ứng dụng hiện có. Web dịch vụ trả lời những khó khăn vì họ cung cấp một mức độ cao của khả năng tương tác. Các tiêu chuẩn cơ bản ba WSDL, UDDI và xà phòng làm cho có thể mô tả, các ấn phẩm và invocation của dịch vụ Web [2], [6], [7], [10].Sự tương tác cơ bản của các dịch vụ web cho một cổng làDựa trên một sự tách biệt giữa các máy chủ quản lý giao diện người dùng và một trong đó sử dụng một dịch vụ cụ thể [11]. Trong trường hợp của một cổng thông tin doanh nghiệp, các máy chủ xà phòng có thể được nội bộ tức là nằm trên một mạng nội bộ. Trong trường hợp này, các dịch vụ được cung cấp có thể được kích hoạt thông qua xà phòng bằng cách sử dụng vùng mạng cục bộ. Nếu máy chủ xà phòng là bên ngoài, sự tương tác được thực hiện thông qua một Extranet hoặc mạng Internet.3. một quá trình hội nhập của dịch vụ web trong cácCổng doanh nghiệpHiện nay, có rất nhiều sản phẩm được cung cấp bởi các biên tập viên của EP giải pháp. Tuy nhiên, mỗi trình biên tập có phương pháp phát triển riêng của mình. Đối với sự phát triển nội bộ, các doanh nghiệp sử dụng nói chung các phương pháp và các quy trình cho mô hình của các ứng dụng web. Nhưng các giải pháp, mà là phổ biến nhất, là sử dụng RUP cho quá trình và UML cho ký hiệu [8], [9].Những khó khăn mà phát sinh cho những phương pháp này là họ được định hướng phát triển ứng dụng mới. Tuy nhiên, cổng doanh nghiệp sử dụng lại ứng dụng nói chung hiện có.Năm sau, chúng tôi cung cấp cho các bước tuyệt vời để được theo sau cho sự phát triển của một cổng thông tin doanh nghiệp cung cấp một đĩa đơn và được cá nhân hoá truy cập điểm đến khác nhau nội bộ (bên trong doanh nghiệp) và bên ngoài Dịch vụ. Quá trình được đề xuất được thiết kế cho sự phát triển của các cổng thông tin doanh nghiệp. Nó là một phương pháp chung chung và toàn cầu, nghĩa là nó không được chỉ định cho một loại hình cụ thể của cổng.Mục tiêu chính của quá trình này là sự tích hợp của ứng dụng hiện có bằng cách sử dụng các dịch vụ web.Người sử dụng và đặc điểm kỹ thuật cổng thông tin Nó mô tả làm thế nào để biến đổi các ứng dụng hiện có vào một tập hợp các dịch vụ và để thêm các thành phần mới phát triển bên trong công ty và các dịch vụ bên ngoài. Quá trình này được lặp đi lặp lại và nó sau quá trình RUP tức là các giai đoạn được thực hiện trong một cách lặp đi lặp lại cho đến khi tất cả yêu cầu được thực hiện. Nó được chia thành sáu bước thực hiện (fig.1): đặc điểm kỹ thuật, phân tích, tái sử dụng các ứng dụng hiện có, thiết kế giao diện người dùng, thực hiện và quản lý.3. 1 đặc điểm kỹ thuật toàn cầu giai đoạnMục đích của giai đoạn này là để xác định hướng của dự án. Nói cách khác, mục tiêu chung là để cung cấp cho phác thảo rộng của cổng thông tin để xác định danh sách các nội bộ và bên ngoài hệ thống sẽ tương tác với cổng thông tin doanh nghiệp và kết luận có các người dùng khác nhau về điều này cuối cùng.Nói chung, các hệ thống nội bộ (tiểu hệ thống) là mạng nội bộ phòng ban của doanh nghiệp. Mỗi người có thể chứa một hoặc một số ứng dụng, trong đó sử dụng nguồn dữ liệu khác nhau. Bên ngoài hệ thống thường được cung cấp bởi các công ty đối tác. Các hệ thống này có thể truy cập thông qua một Extranet hoặc Internet, vì chúng có thể là các trang web công cộng, trong đó cung cấp các dịch vụ hữu ích và chức năng cho các doanh nghiệp (ví dụ, là một dịch vụ ví).Nó cũng là cần thiết để xác định các nhu cầu của doanh nghiệp với câu trả lời cho một số câu hỏi:• Mục tiêu của cổng thông tin doanh nghiệp muốn phát triển là gì?• Người dùng trong tương lai của cổng là gì?• Các dịch vụ mà công ty muốn cung cấp cho những người sử dụng là gì?• Đối tác sẽ tham gia vào dự án là gì?Vào cuối giai đoạn đặc điểm kỹ thuật, các nhà thiết kế có thể xác định và đánh giá sự phức tạp của dự án.Đặc điểm kỹ thuật Danh sách các ứng dụng hiện có hữu ích + Phân tích chức năng cần quản lý người dùng Danh sách các phương pháp tái + phương pháp mà sẽ được phát triển +... Sơ đồ tương tác Tái sử dụng hiện tạiứng dụngThiết kế của giao diện quy tắcSơ đồ thiết kế của UIs Thực hiệnQuản lýHình 1. Bước khác nhau của quá trình phát triển 3. 2 phân tích giai đoạnSau khi xác định loại cổng thông tin và các loại khác nhau của những người sử dụng trong tương lai ở bước trước, giai đoạn này có hai mục tiêu chính: định nghĩa chức năng nhu cầu và quản lý của người sử dụng.3. 2.1 định nghĩa của các nhu cầu chức năngTrong bước này, một trong những có thể xác định nội dung toàn cầu của cổng thông tin. Sau khi xác định danh sách cơ bản của các dịch vụ khác nhau, các cuộc đối thoại với những người sử dụng và quan sát các hoạt động hàng ngày, cho phép chúng tôi để làm phong phú thêm danh sách các dịch vụ. Một số thông tin thú vị có thể được phục hồi cho bước này, ví dụ: danh sách các ứng dụng nội bộ đó là hữu ích cho các dự án, công nghệ mà các ứng dụng đã được phát triển, các thể loại của người dùng và quy tắc quản lý sử dụng trong mỗi hệ thống nội bộ (hoặc hệ thống phụ).3.2.2 quản lý người dùngSau khi xác định các cổng nội dung, một trong những có thể xử lý rất quan trọng khía cạnh liên quan đến các yêu cầu hoạt động của cổng thông tin, truy cập kiểm soát và người sử dụng xác thực. Tất cả các chức năng này là các yếu tố cần thiết cho các cá nhân hóa và tạo ra hồ sơ người dùng
đang được dịch, vui lòng đợi..
Reuse of existing applications during the development of Enterprise Portals integrating Web Services
M. Gharzouli M. Boufaida, L. Seinturier
Lire laboratory, Department Lire laboratory, Department LIFL UMR CNRS 8022
of Computer Science, Mentouri of Computer Science, Mentouri Bâtiment INRIA Haute-Borne
University of Constantine, University of Constantine, 59655 Villeneuve d'Ascq Cedex
25000, Algeria 25000, Algeria France
gharzouli_mohamed@yahoo.fr
boufaida@hotmail.com
Lionel.Seinturier@lifl.fr
Abstract
During these last years, the use of the web technologies in the enterprises becomes an essential factor to define a new business model. Among these technologies, web services and enterprise portals have gathered to integrate existing heterogeneous systems such as e-commerce, e- services hub and e-learning. However, the design and the modeling of the portals, on the one hand, and their integration with the existing applications, on the other hand, are still two points open for discussion. The first problem is related to the development of the lifecycle that can be used for designing and modeling the enterprise portals. For the second problem, which is the integration of the existing applications, the discussion is intended towards the use of technologies based on web services. In This paper, we present a software engineering solution for the development of Web services-based enterprise portals.
Keywords: Development process, Enterprise Portals, Reuse of existing application, Web services.
1. Introduction
The concept of Enterprise Portal (EP) has received much attention since the success of public portals on the Web like Yahoo! and MSN. It is increasingly being used to refer to vertical web sites that feature personalization/customization, cross-platform usability, distributed access, management, and security of information and services within a particular enterprise/industry, thus the so called enterprise, corporate or vertical portals [4]. Portal technology can be targeted towards external users (B2C and B2B) or/and internal users (B2E). It is a tool that incorporates on only one personalized screen, according to the profile of each user, all information and applications he needs to work with [1]. The EP decreases the spent time of searching information with giving the possibility to reach separate sources of information [12].
Progressively, portals have become a need for many famous companies like IBM, Microsoft and Plumtree.
These later offer packaged solutions on a variety of platforms. However, these packages lack interoperability in general and synchronization among the various components in particular. Furthermore, they are very expensive [17]. For this reason, the common enterprises choose the "home development" of the portal solution. Moreover, one of the key properties of the portal is that it is built of heterogeneous applications. So, it is necessary to use a tool that permits the interoperability between the portal and the different applications.
In this direction, the use of Web services is considered to be a good solution for creating a homogeneous environment [11]. The web services architecture is based on three elements: the service provider, the discovering agency and the service requestor [13], [10], [5]. If a company wants to develop a portal based on web services architecture, it defines the role of the service provider and those of the service requestor. So, the development of such a portal requires firstly the preparation and the construction of its contents by re-using existing applications.
In this paper, we describe a methodology for the development of the web services for the enterprise portals with re-using existing applications. This methodology explains how we can develop initially the web services and then how to consume them through the portal.
In the following, we present an important aspect that is related to the use of interoperable web services for computational portals. After having presented the various steps of our methodology, we provide a comparison between some related works and our approach and we finish with a conclusion and some prospects.
2. Web services for Enterprise Portals
Recently, Web services and enterprise portals have gathered to integrate heterogeneous systems such as e- commerce, e-services hub and e-learning [16]. To ensure the interoperability in the various types of portals, Web services form an adequate and effective solution. The portal needs to reach heterogeneous information sources and re-uses existing applications. Web services answer
these constraints because they offer a high degree of interoperability. The three basic standards WSDL, UDDI and SOAP make possible the description, the publication and the invocation of Web services [2], [6], [7], [10].
The basic interaction of the web services for a portal is
based on a separation between the server that manages the user interface and the one that uses a particular service [11]. In the case of an enterprise portal, the SOAP server can be internal i.e. located on an Intranet. In this case, the provided services can be invoked via SOAP by using the local network area. If the SOAP server is external, the interaction is made via an Extranet or the Internet network.
3. An integration process of web services in the
Enterprise Portals
Currently, there are several products that are offered by various editors of EP solutions. However, each editor has his own development methodology. For the internal development, the enterprises use generally the methods and the processes for the modeling of the web applications. But the solution, which is the most common, is to use RUP for the process and UML for the notation [8], [9].
The difficulty that arises for these methods is that they are oriented to the development of new applications. However, the enterprise portals reuse generally existing applications.
In the following, we give the great steps to be followed for the development of an enterprise portal providing a single and personalized access point to different internal (inside the enterprise) and external services. The proposed process is intended for the development of the enterprise portals. It is a generic and global methodology, i.e. it is not specified for a particular type of portals.
The main objective of this process is the integration of the existing application through the use of the web services.
Users and portal specification
It describes how to transform the existing applications into a set of services and to add new components developed inside the company and the external services. This process is iterative and it follows the RUP process i.e. the phases are carried out in a repetitive way until that the all requirements are accomplished. It is divided into six steps (fig.1): specification, analysis, re-use of the existing applications, design of the user interfaces, implementation and management.
3. 1 Global specification phase
The goal of this phase is to determine the orientation of the project. In other words, the general objective is to give the broad outline of the portal in order to determine the list of the internal and external systems that will be interact with the enterprise portal and to conclude which are the various users of this last.
Generally, the internal systems (sub systems) are the departmental Intranets of the enterprise. Each one can contain one or several applications, which use various data sources. The external systems are generally provided by the partner companies. These systems are accessible through an Extranet or Internet, as they can be public web sites, which provide useful services and functionalities for the enterprise (for example, a purse service).
It is also necessary to determine the needs of the enterprise with giving answers to several questions:
• What is the objective of the portal that the enterprise wants to develop?
• What are the future users of the portal?
• What are the services which the company wants to provide to the users?
• What are the partners that will participate in the project?
At the end of the specification phase, the designer can determine and evaluate the complexity of the project.
Specification
List of useful existing applications +
Analysis
functional needs Users' management
List of reused methods + the method that will be developed +…..
Interaction diagrams
Re-use of the existing
applications
Design of the UI
rules
Design diagrams of UIs
Implementation
Management
Figure 1. Different steps of the development process
3. 2 Analysis phase
After the determination of the type of portal and the various types of the future users in the previous step, this phase has two principal objectives: the definition of the functional needs and the management of the users.
3. 2.1 Definition of the functional needs
During this step, one can define the global contents of the portal. After the determination of the basic list of the different services, the dialogue with the users and the observation of the daily activities, enable us to enrich the list of the services. Several interesting information can be recovered for this step, for instance: the list of the internal applications those are useful for the project, technologies with which these applications have been developed, categories of users and management rules used in each internal system (or sub system).
3.2.2 Users management
After the determination of the portal contents, one can process very important aspects related to the operational requirements of portal, the access control and user authentication. All these functions are essential factors for the personalization and the creation of the user profiles
M. Gharzouli M. Boufaida, L. Seinturier
Lire laboratory, Department Lire laboratory, Department LIFL UMR CNRS 8022
of Computer Science, Mentouri of Computer Science, Mentouri Bâtiment INRIA Haute-Borne
University of Constantine, University of Constantine, 59655 Villeneuve d'Ascq Cedex
25000, Algeria 25000, Algeria France
gharzouli_mohamed@yahoo.fr
boufaida@hotmail.com
Lionel.Seinturier@lifl.fr
Abstract
During these last years, the use of the web technologies in the enterprises becomes an essential factor to define a new business model. Among these technologies, web services and enterprise portals have gathered to integrate existing heterogeneous systems such as e-commerce, e- services hub and e-learning. However, the design and the modeling of the portals, on the one hand, and their integration with the existing applications, on the other hand, are still two points open for discussion. The first problem is related to the development of the lifecycle that can be used for designing and modeling the enterprise portals. For the second problem, which is the integration of the existing applications, the discussion is intended towards the use of technologies based on web services. In This paper, we present a software engineering solution for the development of Web services-based enterprise portals.
Keywords: Development process, Enterprise Portals, Reuse of existing application, Web services.
1. Introduction
The concept of Enterprise Portal (EP) has received much attention since the success of public portals on the Web like Yahoo! and MSN. It is increasingly being used to refer to vertical web sites that feature personalization/customization, cross-platform usability, distributed access, management, and security of information and services within a particular enterprise/industry, thus the so called enterprise, corporate or vertical portals [4]. Portal technology can be targeted towards external users (B2C and B2B) or/and internal users (B2E). It is a tool that incorporates on only one personalized screen, according to the profile of each user, all information and applications he needs to work with [1]. The EP decreases the spent time of searching information with giving the possibility to reach separate sources of information [12].
Progressively, portals have become a need for many famous companies like IBM, Microsoft and Plumtree.
These later offer packaged solutions on a variety of platforms. However, these packages lack interoperability in general and synchronization among the various components in particular. Furthermore, they are very expensive [17]. For this reason, the common enterprises choose the "home development" of the portal solution. Moreover, one of the key properties of the portal is that it is built of heterogeneous applications. So, it is necessary to use a tool that permits the interoperability between the portal and the different applications.
In this direction, the use of Web services is considered to be a good solution for creating a homogeneous environment [11]. The web services architecture is based on three elements: the service provider, the discovering agency and the service requestor [13], [10], [5]. If a company wants to develop a portal based on web services architecture, it defines the role of the service provider and those of the service requestor. So, the development of such a portal requires firstly the preparation and the construction of its contents by re-using existing applications.
In this paper, we describe a methodology for the development of the web services for the enterprise portals with re-using existing applications. This methodology explains how we can develop initially the web services and then how to consume them through the portal.
In the following, we present an important aspect that is related to the use of interoperable web services for computational portals. After having presented the various steps of our methodology, we provide a comparison between some related works and our approach and we finish with a conclusion and some prospects.
2. Web services for Enterprise Portals
Recently, Web services and enterprise portals have gathered to integrate heterogeneous systems such as e- commerce, e-services hub and e-learning [16]. To ensure the interoperability in the various types of portals, Web services form an adequate and effective solution. The portal needs to reach heterogeneous information sources and re-uses existing applications. Web services answer
these constraints because they offer a high degree of interoperability. The three basic standards WSDL, UDDI and SOAP make possible the description, the publication and the invocation of Web services [2], [6], [7], [10].
The basic interaction of the web services for a portal is
based on a separation between the server that manages the user interface and the one that uses a particular service [11]. In the case of an enterprise portal, the SOAP server can be internal i.e. located on an Intranet. In this case, the provided services can be invoked via SOAP by using the local network area. If the SOAP server is external, the interaction is made via an Extranet or the Internet network.
3. An integration process of web services in the
Enterprise Portals
Currently, there are several products that are offered by various editors of EP solutions. However, each editor has his own development methodology. For the internal development, the enterprises use generally the methods and the processes for the modeling of the web applications. But the solution, which is the most common, is to use RUP for the process and UML for the notation [8], [9].
The difficulty that arises for these methods is that they are oriented to the development of new applications. However, the enterprise portals reuse generally existing applications.
In the following, we give the great steps to be followed for the development of an enterprise portal providing a single and personalized access point to different internal (inside the enterprise) and external services. The proposed process is intended for the development of the enterprise portals. It is a generic and global methodology, i.e. it is not specified for a particular type of portals.
The main objective of this process is the integration of the existing application through the use of the web services.
Users and portal specification
It describes how to transform the existing applications into a set of services and to add new components developed inside the company and the external services. This process is iterative and it follows the RUP process i.e. the phases are carried out in a repetitive way until that the all requirements are accomplished. It is divided into six steps (fig.1): specification, analysis, re-use of the existing applications, design of the user interfaces, implementation and management.
3. 1 Global specification phase
The goal of this phase is to determine the orientation of the project. In other words, the general objective is to give the broad outline of the portal in order to determine the list of the internal and external systems that will be interact with the enterprise portal and to conclude which are the various users of this last.
Generally, the internal systems (sub systems) are the departmental Intranets of the enterprise. Each one can contain one or several applications, which use various data sources. The external systems are generally provided by the partner companies. These systems are accessible through an Extranet or Internet, as they can be public web sites, which provide useful services and functionalities for the enterprise (for example, a purse service).
It is also necessary to determine the needs of the enterprise with giving answers to several questions:
• What is the objective of the portal that the enterprise wants to develop?
• What are the future users of the portal?
• What are the services which the company wants to provide to the users?
• What are the partners that will participate in the project?
At the end of the specification phase, the designer can determine and evaluate the complexity of the project.
Specification
List of useful existing applications +
Analysis
functional needs Users' management
List of reused methods + the method that will be developed +…..
Interaction diagrams
Re-use of the existing
applications
Design of the UI
rules
Design diagrams of UIs
Implementation
Management
Figure 1. Different steps of the development process
3. 2 Analysis phase
After the determination of the type of portal and the various types of the future users in the previous step, this phase has two principal objectives: the definition of the functional needs and the management of the users.
3. 2.1 Definition of the functional needs
During this step, one can define the global contents of the portal. After the determination of the basic list of the different services, the dialogue with the users and the observation of the daily activities, enable us to enrich the list of the services. Several interesting information can be recovered for this step, for instance: the list of the internal applications those are useful for the project, technologies with which these applications have been developed, categories of users and management rules used in each internal system (or sub system).
3.2.2 Users management
After the determination of the portal contents, one can process very important aspects related to the operational requirements of portal, the access control and user authentication. All these functions are essential factors for the personalization and the creation of the user profiles
đang được dịch, vui lòng đợi..
Các ngôn ngữ khác
Hỗ trợ công cụ dịch thuật: Albania, Amharic, Anh, Armenia, Azerbaijan, Ba Lan, Ba Tư, Bantu, Basque, Belarus, Bengal, Bosnia, Bulgaria, Bồ Đào Nha, Catalan, Cebuano, Chichewa, Corsi, Creole (Haiti), Croatia, Do Thái, Estonia, Filipino, Frisia, Gael Scotland, Galicia, George, Gujarat, Hausa, Hawaii, Hindi, Hmong, Hungary, Hy Lạp, Hà Lan, Hà Lan (Nam Phi), Hàn, Iceland, Igbo, Ireland, Java, Kannada, Kazakh, Khmer, Kinyarwanda, Klingon, Kurd, Kyrgyz, Latinh, Latvia, Litva, Luxembourg, Lào, Macedonia, Malagasy, Malayalam, Malta, Maori, Marathi, Myanmar, Mã Lai, Mông Cổ, Na Uy, Nepal, Nga, Nhật, Odia (Oriya), Pashto, Pháp, Phát hiện ngôn ngữ, Phần Lan, Punjab, Quốc tế ngữ, Rumani, Samoa, Serbia, Sesotho, Shona, Sindhi, Sinhala, Slovak, Slovenia, Somali, Sunda, Swahili, Séc, Tajik, Tamil, Tatar, Telugu, Thái, Thổ Nhĩ Kỳ, Thụy Điển, Tiếng Indonesia, Tiếng Ý, Trung, Trung (Phồn thể), Turkmen, Tây Ban Nha, Ukraina, Urdu, Uyghur, Uzbek, Việt, Xứ Wales, Yiddish, Yoruba, Zulu, Đan Mạch, Đức, Ả Rập, dịch ngôn ngữ.
- pero tú y yo no has conocido que las est
- Anh đã đi du lịch Việt Nam chưa?
- How about you?
- Water spiri abyss megalodon
- on
- i think it would be nice for her to talk
- 1.How many legs does an insect have and
- My mommy is here
- we talk about family and job
- greenpeace believes in non-violent direc
- Yo te gusto?
- Babu
- 7. They worry most about pollution – air
- thiết kế con bướm
- wrote
- Oh good your dad mam jolly tyee wt do?
- decomposition
- Stand Up For Love"[Beyonce]There are tim
- but Dell was also participating in a pri
- cám ơn bạn. nhưng tôi vẫn không hiểu ý n
- 7. They worry most about pollution – air
- withdrew
- I am waiting
- 소세지
