+ All Categories
Home > Documents > Integrating Multiple Technologies into a Company Intranet · application provided. Using Liferay,...

Integrating Multiple Technologies into a Company Intranet · application provided. Using Liferay,...

Date post: 09-Apr-2020
Category:
Upload: others
View: 4 times
Download: 0 times
Share this document with a friend
1
Integrating Multiple Technologies into a Company Intranet Archway PDT Neil Hauser, Jon Hoover, Eric Li, Andrew Rachunok, Tim Watt Faculty Coach J. Scott Hawker Project Sponsors Keith Rachunok, Michael Richards, Andre Roberge About PAETEC Process Portal System Interaction About The Project An HTTP-based site hosted with software that allows the aggrega- tion of several different back-end systems, processes, or sites brought together through a single page. They may provide addi- tional services such as single sign-on security, customization, per- sonalization, and back-end administrative/declarative application. After extensive research into several different open source portals, we chose Liferay as our portal to provide a consolidated view of PAETEC's disparate applications. We based our decision on the ease of installation, ease of use, and ease of development that the application provided. Using Liferay, we were able to quickly take portlets from design to installation. Liferay also has an extensive list of features that made our decision much more valuable in the end. Finally, the set of base portlets that Liferay provided were invaluable as a guide to developing new portlets as well as a place to start looking for reusability. A typical user interaction would consist of the following steps: 1. User submits a their username/password to the system. 2. Portal authenticates against PAETEC's LDAP server. 3. Portal displays the portlets that the user is allowed to use. 4. User submits a request to one of the portlets. 5. Portal container processes the request and gets relevant session data from the portal database. 6. Portal forwards the request and session data to the portlet. 7. Portlet uses the session data and data from an external source, depening on the portlet type. 8. Portlet returns an HTML response to the portal. 9. Portal combines HTML responses from all the portlets and renders it for the user. The process that we used was a hybrid of the Waterfall and Incremen- tal methodologies. We used this method as PAETEC develops soft- ware with a pure Waterfall methodology and we wanted to use what their developers were familiar with for our project as they will be taking it over when we are done. However, due to the short-comings of the Waterfall model, we decided to incorporate the Incremental methodol- ogy for our design, development, and testing phases. Each portlet was an individual increment that included design, implementation, unit test- ing, and integration testing. • Requirements Specification • Architecture Specification • Design Specifications • Documented Source Code Upon completion of the project, PAETEC will take the portlets that we developed inside Liferay and will deploy them inside of a commercial portal application. The portlets that we developed are the ground work that is needed to begin moving some of PAETEC’s disparate applications into a single entity, Oracle Portal. The engineers at PAETEC will utilize the PDK that we deliver to extend the func- tionality of our base portlets as well as to create new portlets. This project was mainly a research project for PAETEC and it will be up to their engineers to actu- ally implement a business oriented product from the results of our research. • Code Review Results • Test Plan • Test Cases • Test Results • Portlet Development Kit • Demonstration Portlets • Software Documentation • White paper PAETEC Communications, Inc., a subsidiary of PAETEC Corp., is a communications solutions provider of- fering broadband services, including advanced voice and video, enhanced data and communications manage- ment services to medium-sized and large businesses, colleges and univer- sities, hospitals, hotels, governmental organizations, financial markets, and affinity groups. Headquartered in Fair- port, N.Y., the company boasts one of the highest customer retention rates in the industry. PAETEC Communications currently has a large number of disparate data sources that employees utilize on a daily basis. Employees access vari- ous applications to view the data they need. This is confusing and time- consuming for users and reduces em- ployee productivity and quality of work. The goal of this project is to make all the data accessible through one user interface – an intranet portal. Deliver- ables include a Portlet Development Kit (PDK), demonstration portlets for different types of data sources, and associated documentation. The PDK will contain common components to facilitate development of portlets for all of the data sources at PAETEC. WSRP and JSR 168 standards will allow PAETEC to plug the portlets into any compliant portal environment. Deliverables Future Work Portal User Login User Login User Login 1 User Gets User Gets Data Data User Gets Data 9 Authentication Server (LDAP) 2 User Specific User Specific Content Content User Specific Content 3 Submit Request Submit Request Submit Request 4 Get Data Get Data Get Data 5 Session Data Session Data To Portlet To Portlet Session Data To Portlet 6 Consume Data Consume Data Consume Data 7 Office Web Component Web Service WSRP System Database LAN Static HTML Page Web Clipped Page HTML Response HTML Response HTML Response 8 < HTML > Architecture Requirements & Research Infrastructure Concurrent Increments Include Increments • LAN Directory • Web Service • Static HTML • Web-Clipping • WSRP • Office Web Components Database • Administrator Portlets • Portal Modifications Design Implementation Unit Test Integration Test System Test User Documentation Delivery Poster Design Corey Vance
Transcript
Page 1: Integrating Multiple Technologies into a Company Intranet · application provided. Using Liferay, we were able to quickly take portlets from design to installation. Liferay also has

Integrating Multiple Technologies into a Company IntranetArchway PDTNeil Hauser, Jon Hoover, Eric Li, Andrew Rachunok, Tim Watt

Faculty CoachJ. Scott Hawker

Project SponsorsKeith Rachunok, Michael Richards, Andre Roberge

About PAETEC Process Portal

System InteractionAbout The Project

An HTTP-based site hosted with software that allows the aggrega-tion of several different back-end systems, processes, or sites brought together through a single page. They may provide addi-tional services such as single sign-on security, customization, per-sonalization, and back-end administrative/declarative application.

After extensive research into several different open source portals, we chose Liferay as our portal to provide a consolidated view of PAETEC's disparate applications. We based our decision on the ease of installation, ease of use, and ease of development that the application provided. Using Liferay, we were able to quickly take portlets from design to installation. Liferay also has an extensive list of features that made our decision much more valuable in the end. Finally, the set of base portlets that Liferay provided were invaluable as a guide to developing new portlets as well as a place to start looking for reusability.

A typical user interaction would consist of the following steps:1. User submits a their username/password to the system.2. Portal authenticates against PAETEC's LDAP server.3. Portal displays the portlets that the user is allowed to use.4. User submits a request to one of the portlets.5. Portal container processes the request and gets relevant session data from the portal database.6. Portal forwards the request and session data to the portlet.7. Portlet uses the session data and data from an external source, depening on the portlet type.8. Portlet returns an HTML response to the portal.9. Portal combines HTML responses from all the portlets and renders it for the user.

The process that we used was a hybrid of the Waterfall and Incremen-tal methodologies. We used this method as PAETEC develops soft-ware with a pure Waterfall methodology and we wanted to use what their developers were familiar with for our project as they will be taking it over when we are done. However, due to the short-comings of the Waterfall model, we decided to incorporate the Incremental methodol-ogy for our design, development, and testing phases. Each portlet was an individual increment that included design, implementation, unit test-ing, and integration testing.

• Requirements Specification• Architecture Specification• Design Specifications• Documented Source Code

Upon completion of the project, PAETEC will take the portlets that we developed inside Liferay and will deploy them inside of a commercial portal application. The portlets that we developed are the ground work that is needed to begin moving some of PAETEC’s disparate applications into a single entity, Oracle Portal.

The engineers at PAETEC will utilize the PDK that we deliver to extend the func-tionality of our base portlets as well as to create new portlets. This project was mainly a research project for PAETEC and it will be up to their engineers to actu-ally implement a business oriented product from the results of our research.

• Code Review Results• Test Plan• Test Cases• Test Results

• Portlet Development Kit• Demonstration Portlets• Software Documentation• White paper

PAETEC Communications, Inc., a subsidiary of PAETEC Corp., is a communications solutions provider of-fering broadband services, including advanced voice and video, enhanced data and communications manage-ment services to medium-sized and large businesses, colleges and univer-sities, hospitals, hotels, governmental organizations, financial markets, and affinity groups. Headquartered in Fair-port, N.Y., the company boasts one of the highest customer retention rates in the industry.

PAETEC Communications currently has a large number of disparate data sources that employees utilize on a daily basis. Employees access vari-ous applications to view the data they need. This is confusing and time-consuming for users and reduces em-ployee productivity and quality of work. The goal of this project is to make all the data accessible through one user interface – an intranet portal. Deliver-ables include a Portlet Development Kit (PDK), demonstration portlets for different types of data sources, and associated documentation. The PDK will contain common components to facilitate development of portlets for all of the data sources at PAETEC. WSRP and JSR 168 standards will allow PAETEC to plug the portlets into any compliant portal environment.

Deliverables Future Work

Portal

User LoginUser LoginUser Login

1

User GetsUser GetsDataData

User GetsData

9

AuthenticationServer (LDAP)

2

User SpecificUser SpecificContent Content

User SpecificContent

3

Submit RequestSubmit RequestSubmit Request

4

Get DataGet DataGet Data

5

Session DataSession DataTo PortletTo Portlet

Session DataTo Portlet

6

Consume DataConsume DataConsume Data

7

Office WebComponent

Web Service

WSRP

System Database

LAN

Static HTML Page

Web ClippedPage

HTML ResponseHTML ResponseHTML Response

8

< HTML >

Architecture

Requirements & Research Infrastructure

Concurrent Increments

Include Increments

• LAN Directory• Web Service• Static HTML• Web-Clipping• WSRP• Office Web Components Database• Administrator Portlets• Portal Modifications

Design

Implementation

Unit Test

Integration Test

System Test

User Documentation

Delivery

Poster Design Corey Vance

Recommended