Portal and Content Manager dDvelopers

* WebSphere Portlet development with Content Manager abilities (customized portlet templates serving content from content manager)

* Production environment: AIX

* Windows / RAD development environment

 

* Senior WebSphere Integration Architect

* WebSphere Process Server

* WebSphere Message Broker (Advanced ESB)

* Tech Lead (good customer facing skills but hands on though not expert; Java / Portal

 

Immediate Project Overview:

Implementation to update and improve the internet presence. By leveraging recent advanced technologies both the consumer and professional businesses can be brought closer by making it easier for to interact with their customers.  An additional consideration is also to provide a more aesthetic look and feel -- as well as smoother interaction-- to their presence on the world wide web.

 

The current web presence is highly static in nature. There is no provision for customer login or online ordering.

 

By standardizing on IBM?s WebSphere family of application servers, the customer will have a single development platform which will simplify development processes and result in better overall performance of new and existing applications.  This will permit better knowledge sharing among developers in both structured and informal settings.  A single platform will also result in a more consistent look and feel made possible by simpler administrative tasks.  It will allow for reuse of many coded objects, thus decreasing development cost and time.  And it will promote a richer interactive experience for users because all user interfaces will share similar behavioral attributes.

 

Phase I

The phase 1 project consists of the following high level divisions:

Create 60 (plus or minus 10) static portal pages for three domains to be the new web presence
Convert all of the pages to run in a WebSphere portal framework
Convert 2 dynamic pages to portlets where applicable
The system will be designed to support English, French and Spanish languages  (initially English and Spanish)
Provide a hardware/software/network recommendations for hosting the site
Install and configure the portal software on two environments
Configure the network, domain and software to bring the site live
Fully test the new site
Conduct initial high-level requirements to scope Phase 2
Provide 35 hours of post implementation support
Mentor customer staff
Portal Themes and Skins will be created, where appropriate, to support the new look and feel according to provided look and feel document.
Complete Content Management framework will be devised including user configuration, content publishing workflow and content management artifact creation.  This will also address the management of downloadable artifacts such as PDFs.
All page body content text will be under the control of the portlets.
There will be templates created that will be used to display content.  These templates will be the foundation for all pages created. 
Content to be served and managed through WebSphere Content manager
 

 

In scope for Phase I

?  There will be 60 (plus or minus 5) static pages which will need to be converted to portlets.  Each page in the entire web site will be re-designed using the new look and feel identified by customer.

?  Portlets will be designed to support multiple languages by way of either multiple JSPs or resource bundles depending on which is more appropriate.

?  The portal will largely be a content-based portal and not a transactional or collaborative portal in Phase 1.

?  The effort to import the documents/artifacts into the content management systems will take no more than two days.

?  WebSphere 6.0 Application server and WebSphere 5.1 Portal software will be used to deploy the website.

?  Phase 1 will include training and mentoring of customer resources as active participants in the tasks performed but without accountability for required deliverables.

?  Phase 2 and other subsequent phases will utilize GPI resources as part of the development team with delivery responsibility assigned to them.

?  All pages will be tested using IE, Netscape, Mozilla and AOL browsers.  We will define a minimum supported version of each browser.

?  There will be 5 templates created to support all pages in web site.