Websphere Portal on Z/OS
| < Day Day Up > |
|
Chapter 1: WebSphere Portal Architectures
- Figure 1-1: Tiers in the application model
- Figure 1-2: Two-tier logical architecture
- Figure 1-3: Three-tier logical architecture- Option one
- Figure 1-4: Three-tier logical architecture- Option two
- Figure 1-5: Basic two-tier configuration
- Figure 1-6: Two-tier architecture with scalability
- Figure 1-7: Sample three-tier architecture
- Figure 1-8: Our initial WebSphere Portal architecture
- Figure 1-9: Inside WebSphere Portal on z/OS and OS/390
- Figure 1-10: Our preferred architecture
- Figure 1-11: Our WebSphere Portal environment
Chapter 2: Portal Installation
- Figure 2-1: Program file content
- Figure 2-2: WebSphere Portal Servers family
- Figure 2-3: List of installation jobs
- Figure 2-4: WebSphere Portal Server PTF2 files installation
- Figure 2-5: Setup WLM Application Environment for Portal Server J2EE server
- Figure 2-6: WebSphere Application Server installation screens - Allocate new datasets
- Figure 2-7: WebSphere Application Server installation screens - Define variables for new LDAP server
- Figure 2-8: WebSphere Application Server installation screen 1- Define variables for new LDAP server
- Figure 2-9: WebSphere Application Server installation screen 2- Define variables for new LDAP server
- Figure 2-10: Generate jobs and save customization variables for LDAP server for Portal z/OS
- Figure 2-11: Check the TDBM backend suffix handled
- Figure 2-12: Browse LDAP tree
- Figure 2-13: WSPORT JCL for Portal z/OS control region started task
- Figure 2-14: Base portlets deployment (Step 1)
- Figure 2-15: Base portlets deployment (Step 2) completed
- Figure 2-16: WebSphere Portal Content Publishing naming registration completed
- Figure 2-17: Personalization challenge/response based authentication
- Figure 2-18: authtable_wcp.xml file
- Figure 2-19: WebSphere Personalization "logged in" screen
- Figure 2-20: Update IBM HTTP Server configuration file httpd.con
- Figure 2-21: Connect to Portal from HTTP Server
Chapter 3: Development Environment Installation
- Figure 3-1: Simple development environment for WebSphere Portal on z/OS
- Figure 3-2: WebSphere Application Server Fixpack2 installation
- Figure 3-3: Successful installation of PQ56615 and configuring JDBC driver
- Figure 3-4: Starting WebSphere Application Server Advanced Edition Single Server
- Figure 3-5: Installation of WebSphere Portal
- Figure 3-6: Accessing the portal from a browser
- Figure 3-7: Exporting a WAR file
- Figure 3-8: Security console settings for Authentication
- Figure 3-9: LDAP settings WPCP Authoring Server
- Figure 3-10: WPCP settings for LDAP
- Figure 3-11: WPCP index
- Figure 3-12: WPCP Administration page
- Figure 3-13: Add the sample demo project to WPCP authoring server
- Figure 3-14: Defining the z/OS WPCP publishing server to the authoring server project
- Figure 3-15: Publishing the project to z/OS Portal system
- Figure 3-16: WPCP runtime publisher for sample project
- Figure 3-17: Wizard selection for WebSphere Studio
- Figure 3-18: WPCP wizards installed for WebSphere Studio
Chapter 4: Portal Administration
- Figure 4-1: Portal Administration screen
- Figure 4-2: Manage User Groups screen
- Figure 4-3: Adding a user to wpsadmins group
- Figure 4-4: Navigation structure using Places, Pages and Portlets
- Figure 4-5: Themes and Skins window
- Figure 4-6: Place creation window using the Science Theme
- Figure 4-7: Themes and Skins window
- Figure 4-8: Window to Add a new skin
- Figure 4-9: Window showing the addition of the new Itso skin
- Figure 4-10: Screen to add a new theme
- Figure 4-11: Screen shot of a portal page using the new ITSO theme and Itso skin
- Figure 4-12: WebSphere Portal supported clients
- Figure 4-13: Portal home page on a WML device
- Figure 4-14: Logged in page, ITSO place, WML device, Hello World place not visible
- Figure 4-15: Enabling WML for the ITSO place
- Figure 4-16: Hello World in the ITSO place visible
- Figure 4-17: SMEUI Administrative functions for Portal J2EE applications
- Figure 4-18: Using SMEUI Operations to start the Portal server
Chapter 5: WebSphere Portal in a Sysplex
- Figure 5-1: Principles of a sysplex distributor
- Figure 5-2: Overview of the shared HFS of WebSphere Portal
- Figure 5-3: Customization dialog of WebSphere Application Server on WPS3
- Figure 5-4: SMEUI for enabling WebSphere Application Server in the sysplex
- Figure 5-5: Configuration files for enabling LDAP in the sysplex
- Figure 5-6: Defining environment variables using SMEUI
- Figure 5-7: Connectivity in the test environment
- Figure 5-8: Sample sysplex WPSPLEX
- Figure 5-9: WebSphere Application Server in a sysplex configuration
- Figure 5-10: Sysplex in SMEUI
- Figure 5-11: Vertical Cloning Test Portlet
- Figure 5-12: Standard output showing the login trace
Chapter 6: Portlet Development and Deployment
- Figure 6-1: MyFirstPortlet in WebSphere Studio, View.JSP
- Figure 6-2: Opening Perspective Other
- Figure 6-3: Select the Portlet Perspective
- Figure 6-4: Select Other for type of Project
- Figure 6-5: Select to create a new Portlet application project
- Figure 6-6: Define the project settings
- Figure 6-7: Choose the type of portlet to be created
- Figure 6-8: Hello World portlet parameters
- Figure 6-9: The Hello World project
- Figure 6-10: Expanded source tree
- Figure 6-11: Hello World java
- Figure 6-12: Export WAR for the Hello World portlet
- Figure 6-13: Installing C2A portlets from the Portal Administration place
- Figure 6-14: C2A deploy work ready to run job WPACONF
- Figure 6-15: Adding the C2A portlets to a page
- Figure 6-16: C2A example portlets
- Figure 6-17: WebSphere Portal login window
- Figure 6-18: Initial window on portlet installation
- Figure 6-19: Manage Portlet Applications window
- Figure 6-20: Laying out the portlets in portlet containers on a page
- Figure 6-21: Screen showing the newly installed portlets with the error message
- Figure 6-22: Command window output of running the WPAConfig script
- Figure 6-23: Screen showing the docviewer portlets before configuration
- Figure 6-24: Configuring the PDF document viewer portlet with document details
- Figure 6-25: PDF file viewed in the portlet
- Figure 6-26: Window showing the placement of HOD portlet on the HOD page
- Figure 6-27: Screen to modify the parameters for the HOD portlet
- Figure 6-28: HOD portlet login window
- Figure 6-29: HOD portlet showing an active 3270 session
- Figure 6-30: Edit the iNotes portlet
- Figure 6-31: iNotes Mail portlet
- Figure 6-32: Accessing Lotus Quickplace from Portal Server
- Figure 6-33: Our Hello World portlet deployed in the portal
- Figure 6-34: Trader application
- Figure 6-35: J2EE and CIC's Trader application GUI
- Figure 6-36: SMEUI view of TraderEJB home JNDI name
- Figure 6-37: Logging onto Trader using the iFrame portlet
- Figure 6-38: Using the Trader application with the iFrame portlet
- Figure 6-39: TraderPortlet and iFrame portlet compared
- Figure 6-40: SMEUI view of J2EE servers
- Figure 6-41: Import J2EE EAR wizard.
- Figure 6-42: Tasks outstanding after importing Completed_Trader.ear
- Figure 6-43: Filter tasks option
- Figure 6-44: Creating a Portlet application project
- Figure 6-45: Define the Portlet project
- Figure 6-46: TraderPortlet project
- Figure 6-47: Import WAR
- Figure 6-48: Import options for the WAR file
- Figure 6-49: Set the module dependencies
- Figure 6-50: Resource dialog
- Figure 6-51: Portlet application project with imported code from TraderWeb.war
- Figure 6-52: Select Portlet_1 to assign a servlet to the portlet
- Figure 6-53: Select servlet to assign to the portlet
- Figure 6-54: Deleting page level tags from the HTML
- Figure 6-55: Deleting page level tags from the HTML
- Figure 6-56: The newly renamed Logon.jsp
- Figure 6-57: Remove insert DOCTYPE preference
- Figure 6-58: deleting page level tags from the JSP, part 1
- Figure 6-59: deleting page level tags from the JSP, part 2
- Figure 6-60: Portal Tag library reference in Buy.jsp
- Figure 6-61: Adding portlet.tld to the project directory
- Figure 6-62: JSPs in WEB-INF directory
- Figure 6-63: TraderPortlet inside the Portal
- Figure 6-64: Company Selection screen from the Trader Portlet
- Figure 6-65: Quotes screen from the Trader Portlet
- Figure 6-66: Sell Shares screen from the Trader Portlet
Chapter 7: Portal Security
- Figure 7-1: WebSphere Portal security for z/OS
- Figure 7-2: WebSphere Portal server sign up screen
- Figure 7-3: WebSphere Portal Server user self-registration
- Figure 7-4: WebSphere Portal Server user login panel
- Figure 7-5: Portal administration Portlet Panel
- Figure 7-6: Portal administration 'User and Groups' for user registration
- Figure 7-7: Add user and Provide User Information
- Figure 7-8: DMT Directory tree
- Figure 7-9: Add an LDAP Entry - Entry type 'User'
- Figure 7-10: Add an LDAP User
- Figure 7-11: Adding a LDAP user
- Figure 7-12: Portal login binding to LDAP server using RACF Native Authentication
- Figure 7-13: Portal for z/OS LDAP server startup with Native Authentication enabled
- Figure 7-14: Adding LDAP server in DMT
- Figure 7-15: Viewing the installed object classes
- Figure 7-16: Viewing the ibm-nativeId attribute
- Figure 7-17: Browsing the LDAP tree used by WebSphere Portal on z/OS
- Figure 7-18: Adding auxiliary class at the cn=users level
- Figure 7-19: Adding auxiliary class at the UID level
- Figure 7-20: Adding the RACF UID value in the ibm-nativeID field
- Figure 7-21: Accessing RACF via an LDAP client
- Figure 7-22: RACF users displayed in an LDAP client
- Figure 7-23: Sample LDIF template
- Figure 7-24: The exported RACFID sample file
- Figure 7-25: Merged sample LDIF output file
Chapter 8: Problem Determination
- Figure 8-1: WPACONF failure Create Conversation failed
- Figure 8-2: WPACONF failure Create Conversation failed
- Figure 8-3: SMEUI error BBON0579E
| < Day Day Up > |
|