Webspace Portal Server
WebSphere Portal Server is a J2EE application that runs on top of WebSphere Application Server. WebSphere Portal Server will provide a runtime environment for IBM specific portlets. Portlets run inside a portlet container just like servlets runs inside an application server. A portal is a Web site that provides users with a single point of access to Web-based applications. Using the WebSphere Portal Server you can assemble the portlets and manage secure B2B (business to business), B2C (business to consumer) and B2E (business to employees) portals. Entry to each application on a portal page will be through a portlet. You individually develop portlets and assemble them together to create a customized web pages (or portal pages). WebSphere Portal can deliver Web content to various browsers, mobile devices and desktops.
The latest release of the WebSphere Portal Server at the time of writing this document is V6. WebSphere Portal Server V6 (WP V6) runs on top of WebSphere Application Server ND V6.0.2.9 (WAS V6) software. So, you can imagine that WebSphere Portal has set of programs that run in the WebSphere Application Server JVM just like any other J2EE application (but the way you deploy and manage IBM portlet applications are different from J2EE applications). If you are a WebSphere Portal architect or an administrator, having a good knowledge of WAS V6 will help you quickly understand many configuration scenarios and help you solve the problems quickly. In this document, you will see how to install WP V6 on a stand-alone node (un-managed node) and understand the WP V6 default architecture and the configuration.
You can optionally choose to install business process functionality during the WP V6 installation if you want. Also all the code required to enable WebSphere Content Management (WCM) features will be installed during the WP V6 installation by default. However, you need to enable WCM feature by running a configuration task if you want to use that feature.
WP V6 will store portal configuration data in the Cloudscape database (wpsdb) by default under various schemas during the installation.
You will know more about what is stored in each schema in a later part of this chapter. In later chapters we will see why and how to migrate portal configuration data to DB2 and
Tivoli Directory Servers from a Cloudscape database.
Services: - Webspace Portal Server Homework | Webspace Portal Server Homework Help | Webspace Portal Server Homework Help Services | Live Webspace Portal Server Homework Help | Webspace Portal Server Homework Tutors | Online Webspace Portal Server Homework Help | Webspace Portal Server Tutors | Online Webspace Portal Server Tutors | Webspace Portal Server Homework Services | Webspace Portal Server