ISMT E-200: Trends in Enterprise Information Systems Project: GLOCO – Integrated Corporate Portal Part 2 Technical Specification Team Members: Joyce Torres Kenneth Kittredge Pamela Fisher Ruzhena Saltisky Vishal Nath Instructor: Zoya Kinstler Teaching Assistants: Basem Neseim Valar Jayaprakash 1

ISMT E-200: Trends in Enterprise Information Systems GLOCO’s acquisition of three other companies has resulted in an IT infrastructure that is maintaining four independent systems. There are duplicate applications and services. Employees currently must access multiple portals to perform their work. GLOCO needs to provide a single access point to reduce costs and improve employee productivity. The CIO requested an infrastructure improvement project RFP to address this issue. 2 Problem Statement

Architectural Approach 3

New Architecture 4

Security 5 How a Policy Grants Access to a Resource (Source: Oracle) Web Security Layers (Source: Oracle)

Single Sign-on 6

Portal Description 7  JSF Portlets - using a JSF Portlet Bridge.  Web Clipping- using browser and show other sites (example- web mail).  OmniPortlets - information from data sources including XML, CSV, and databases to show tables, forms, and charts (example-rss).  Content Presenter - displaying content by using a template.  Ensemble - "mashup" or produce portlets of information that can be displayed on the page and can consume any non- Java based applications.

JSR-168 and JSR JSR-168  Defines how components for the portlet servers are developed.  Defines a portlet container – much like how a servlet runs inside a servlet container.  Defines methods to determine required functionality such as init() and destroy().  Configured to provide custom views or behaviors for different users through name-value pairs.  Each portlet has a current mode that indicates function such as view and edit and a window state that determines how much page space is used and how much information to render.  The reference implementation is the Apache Pluto server. JSR-268  Enables portlets to communicate with each other.  Serves dynamically generated resources.  Serves AJAX and JSON directly through portlets.  Defines filters that can transform the content of portlet requests and responses on the fly  Implements WSRP-2.0 Web Services for Remote Portlets Specification

Portlet Producer Overview 9  The user requests a page from the Web browser by entering a URL in the browser’s address field  The browser transmits the request to the application over HTTP.  The application contacts the portlet producers which provide the portlets that display on the requested page.  The producers make the necessary calls to their portlets so that the portlets generate content in the form of HTML or XML code.  The producers return the portlet content back to the application using their relevant protocols.

RSS and 10 RSS RSS is one of many services that are considered “out of the box” WebCenter functionality. Configuration of the RSS includes:  Setting up a proxy server  Specifying the host and port  Setting Wiki and Blog to use Basic Authentication  Creating an external application for reading a secure RSS feeds  Sharing the external application ID with those creating RSS feeds  Add the RSS location to the page receiving the RSS feed Performs simple functions such as view, create, delete messages, add attachments, forward, and reply to existing .  The server complies with IMAP4 and SMTP protocols.  It uses Microsoft Exchange Server to:  Import the certificate to the Keystore,  Port 993 is configured for IMAP and port 587 for SMTP.  Fusion Middleware Control is used to configure the server.  Creates an external application to view in WebCenter Portal.

Travel 11 QPX Airfare Shopping and Pricing Engine <leg origin="BOS" departure=" T07:00-00:00" destination="LAX" arrival=" T010:35-08:00" carrier=“VS"/> <leg origin=“LAX" departure=" T07:20-00:00" destination=“BOS" arrival=" T010:35-08:00" carrier=“VS"/> <leg origin=“BOS" departure=" T07:00-00:00" destination=“LAX" arrival=" T10:35-05:00" carrier=“VS"/> <leg origin=“LAX" departure=" T19:20-05:00" destination="BOS" arrival=" T05:35-00:00" carrier=“VS“/> … XML Query sent: <search key="B1b2C3d6E7f6G7h8I9j0K1" name="roundTrip" version="2"> <inputs origin="BOS" destination="LAX" outbound=" " return=" "> GLO6723 roundTrip

12 Add Title

Portlet Integration 13 Wire portlet code into the Portal:  Create a Remote Server object  Create a Portlet Web Service object  Create a Portlet Object  Place the Portlet on a portal page

Prototype - My Gloco 14

Prototype - Asia ->Sales 15

Prototype - Gloco Common->Travel 16

Prototype - Gloco Common->Portal Management 17