GLOCO – Integrated Corporate Portal Part 2 - Technical Specification Presented by Team 3

1

GLOCO – Integrated Corporate Portal Part 2 - Technical Specification

Presented by Team 3

Team 3 Members: Joyce TorresKenneth KittredgePamela FisherRuzhena SaltiskyVishal Nath

Instructor:

Teaching Assistants:

Zoya Kinstler

Basem NeseimValar Jayaprakash

ISMT E-200 Trends in Enterprise Information Systems

2


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.

Problem Statement

3

Architectural Approach


4

New Architecture


5

SecurityHow a Policy Grants Access to a Resource (Source: Oracle)

Web Security Layers(Source: Oracle)


6

Single Sign-on


7

Portal DescriptionThe Portals will be comprised of the following elements:

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.


8

JSR-168 and JSR-268JSR-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


9

Portlet Producer Overview 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.


10

RSS and EmailRSS

RSS is one of many services that are considered “out of the box” WebCenterfunctionality. 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

EmailPerforms simple email functions such as view, create, delete messages, add attachments, forward, and reply to existing email.

The email 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 e-mail server. Creates an external application to view in WebCenter Portal.


11

Travel

QPX Airfare

Shopping & Pricing

Engine

Response

<?xml version="1.0" encoding="UTF-8"?><result id="…" session="…" solutionCount=“10" solutionSet="…"> <roundTrip> <pages count="1" current="1"/> <solution id="B4Paj8BQf79PPvXNrRZ9X501b"> <ext> <price amount=“219.40" currency="USD"/> </ext> <slice> <leg origin="BOS" departure="2010-12-08T07:00-00:00" destination="LAX" arrival="2010-12-08T010:35-08:00" carrier=“VS"/> <leg origin=“LAX" departure="2010-12-15T07:20-00:00" destination=“BOS" arrival="2010-12-15T010:35-08:00" carrier=“VS"/> </slice> <slice> <leg origin=“BOS" departure="2010-12-08T07:00-00:00" destination=“LAX" arrival="2010-12-08T10:35-05:00" carrier=“VS"/> <leg origin=“LAX" departure="2010-12-15T19:20-05:00" destination="BOS" arrival="2010-12-15T05:35-00:00" carrier=“VS“/> </slice> </solution> … </roundTrip></result>

XML Query Sent

<?xml version="1.0" encoding="UTF-8"?><search key="B1b2C3d6E7f6G7h8I9j0K1" name="roundTrip" version="2"> <inputs origin="BOS" destination="LAX" outbound="2010-12-08" return="2010-12-15"> <pax adults="1"/> <accountCode>GLO6723</accountCode> </inputs> <summarizer>roundTrip</summarizer></search>


12

Steps to Add an Application to a Portal

1Portletize Application2Use JSF-Portlet Bridge in the WebCenter Framework. (The application will be a JSR 168-based portlet afterwards.)

3Add JSF-Portlet Bridge library to Portlet project.

4Deploy JSF portlet to WSRP Portlet Container.

5Register portlet as WSRP producer with the GLOCO portal application.

6Add the Portlet to the GLOCO portal.


13

Portlet Integration

To wire the portlet code into the Portal using Oracle WebCenter Ensemble: 1 Create a Remote Server object.2 Create a Portlet Web Service

object.3 Create a Portlet Object.4 Place the portlet on a portal

page.


14

Prototype - My Gloco


15

Prototype - Asia ->Sales


16

Prototype - Gloco Common->Travel


17

Prototype - Gloco Common->Portal Management


Date post:	29-Jan-2016
Category:	Documents
Upload:	nuri
View:	24 times
Download:	0 times

GLOCO – Integrated Corporate Portal Part 2 - Technical Specification Presented by Team 3

Documents