SHOW301 Administrating WebSphere Portal 6.1.0 and 6.1.5 by pengxiang

VIEWS: 137 PAGES: 129

									SHOW301: Administrating WebSphere Portal
6.1.0 and 6.1.5
2




    Agenda
    ●   Overview

    ●   Preparation

    ●   WebSphere Portal File System structure

    ●   Command Line Tools

         ▬   ConfigEngine
         ▬   ConfigWizard
         ▬   WebSphere Application Server Scripting
         ▬   XMLAccess
         ▬   WebSphere Portal Scripting
         ▬   Release Builder
3




    Agenda
    ●   Portal Administration User Interface

         ▬   Manage User and Groups
         ▬   Virtual Portal Manager
         ▬   Site Management
         ▬   Page Builder
         ▬   Manage Pages - Static pages
         ▬   WebDav
         ▬   Mashup Integration


    ●   WebSphere Application Server Console

         ▬   Java Heap size
4




    Overview
5




    Goal of the session
    ●   Understand the different administration and configuration tools IBM
        WebSphere® Portal® offers
    ●   Learn which tool to use for which task
    ●   Understand differences to previous versions of WebSphere Portal
    ●   Learn about the new capabilities of WebSphere Portal 6.1.5
6




    What is WebSphere Portal?
    ●   The Marketing message:

        Web portals allow partners, employees and customers to choose their
        user experience, with personalized applications based on role, context,
        actions, location, preferences and team collaboration needs. IBM
        WebSphere Portal software provides a composite application or
        business mashup framework and the advanced tooling needed to build
        flexible, SOA-based solutions, as well as the unmatched scalability
        required by any size organization.


    ●   Making it simple:

        WebSphere Portal is a framework that lets you easily build a
        standardized rich Web (Portal) solution.
7




    WebSphere Portal Architecture
8




    WebSphere Portal Architecture
    ●   WebSphere Portal is installed on top of the IBM WebSphere®
        Application Server®
    ●   The WebSphere Application Server contains the JavaTM Runtime edition
        that provides APIs and an abstraction layer from the Operating System


    ●   Clients as browsers or mobile devices access the Portal via the http
        protocol
    ●   The request arrives at the WebSphere Application Server that routes it
        to the WebSphere Portal servlets and portlets
    ●   The WebSphere Portal servlets and portlets build a web page by
        aggregating information from the Portal configuration and backends via
        APIs and connections
    ●   The built web page is then send via the http protocol back to the client
        device that renders the response – depending on the client the response
        could be html, wml, ...
9




          WebSphere Portal – where is configuration
          information stored?
                                                 Configuration Tools


                                                              invoke
                    WebSphere Portal                      getConfig,invoke
                                                                              WebSphere Application Server
                                   Config
              binaries             data
                                               binaries        Config           Config
                                                               data             data




    \PortalServer    \AppServer   \wp_profile\ \wp_profile\
                                  Config, ...  PortalServer
                                                                        Release DB    Customization   Community   JCR DB
                                                                                      DB              DB


                                       \wp_profile


                    File System                                                      Portal databases
1
0




    WebSphere Portal – where is configuration
    information stored?
    ●   WebSphere Portal uses the underlying WebSphere Application Server to
        serve requests
    ●   WebSphere Portal configuration data is stored in both the databases
        and the file system
    ●   WebSphere Application Server uses only the file system for its
        configuration data (there are certain exceptions from this rule like
        session persistence)


    ●   The Configuration Tools modify the configuration data in the different
        repositories
1
1




    Why change WebSphere Portal configuration?
    ●   Integrate into your environment – e.g. Connect to your databases or
        LDAP Server(s) or IBM Lotus® Domino® Mail Servers or IBM Lotus®
        Sametime® Servers or ...
    ●   Customize the look and feel
    ●   Make the solution secure
    ●   Achieve high availability
    ●   Tune Performance
    ●   Deploy your code
    ●   Enable or disable additional features
    ●   Maintenance
    ●   Many many more use cases


    ●   WebSphere Portal is very flexible -> Depending on your use case more
        than one Tool can be used to achieve your goals
1
2




    Preparation
1
3




    Prepared Installation
    ●   Microsoft® Windows® XP
        possible to use any other MultiPlatform OS, but sample files need to be
        adjusted
    ●   Install WebSphere Portal V6.1.5 – use fresh install - Out of the Box
         ▬   Retrieve Install Media from the Passport advantage site

    ●   During Install WebSphere Portal creates:
         ▬   WebSphere Application Server 6.1
         ▬   Lets you choose the Installation directory: e.g. C:\ibm\PortalServer – can choose other directory but then need to
             adjust references in this document accordingly
         ▬   Database: Derby – containing the Portal tables
         ▬   File-based security enabled after install
         ▬   Portal Administrative user: wpsadmin / wpsadmin – can choose other password during install as well but then need
             to adjust references in this document accordingly

    ●   Sample files used in this lab are provided on the Lotusphere session
        catalog – file name is SHOW301_files.zip


    ●   When the install was successful you are ready to start with this session!
        Enjoy ;)
1
4




    Formatting/ Hints
    ●   Following colors are used within this presentation:
         ▬  Mangenta – A file or directory
         ▬  Blue – A command to be executed
         ▬  Green - A name, title, value, file content, or program output
         ▬  Red – an important value

    ●   Note: These colors are helpful, to see the different types fast, but are not
        necessary to understand the meaning.
        So if you are using black and white – that will work as well.

    ●   In this session the server is named as testserver or as localhost.
        Please replace these server names with your local host name that has
        WebSphere Portal installed.
1
5




    WebSphere Portal File System
    structure
1
6




    WebSphere Portal File System structure
    ●   Goal:
         ▬ Directory structure of WebSphere Portal containing command line
           tools, binaries and configuration of the product
    ●   When to use:
         ▬ Configuration changes like modifying properties files, ...
         ▬ Starting and stopping the server
         ▬ Starting and stopping command line tools
         ▬ View log files
    ●   When not to use:
         ▬ Modifying internal configuration files directly, bypassing
           administration / configuration tools
    ●   Alternative Tools:
         ▬  Nearly all tools mentioned further in this topic modify the file system
            in a way
1
7




    WebSphere Portal File System structure
    ●   Description of the next slides:
         ▬ On the left hand side, the directory structures in the file system is
           displayed
         ▬ On the right hand side, you will find some explanation of the content
           of some of the important directories
         ▬ The tool directories will be mentioned as well
1
8




    AppServer directory
                          Websphere
                          Application Server
                          tools
                          independent of profile
                          Derby database
                          binaries


                          Java Developer Kit
                          1.5
1
9




    PortalServer directory


                             XMLAccess, Release Builder,version reporting

                             API/SPI
                             documentation

                             6.1.5 feature pack

                             Application binaries
                             Feature Pack Installation Log

                             Migration


                             Shared Folders with Super Jars

                             Uninstall code

                             Corrective Service registry
2
0




    Profile directory

                        WebSphere Application Server tools for the profile
                        WebSphere Application Server Configuration files of the profile
                        Portal ConfigEngine
                        Portal Install and Config Logs




                        Installed apps including
                        portlets
                        Portal runtime logs
                        Portal tools


                        Portal Derby database


                        Config Wizard
2
1




    Profile directory - Logs



                               Errors / Exceptions
                               System.out messages
                               Separated garbage
                               collection log

                               Process ID
2
2




    Profile directory - WIM/VMM



                                  WIM/VMM config
                                  (formerly wmm.xml, ...)
2
3




    Command Line Tools
     ConfigEngine
2
4




    ConfigEngine
    ●   Goal:
         ▬ Command line tool to execute all Portal Config Tasks
    ●   When to use:
         ▬ Configuration changes like security configuration, enabling/ disabling
           components, clustering, virtual portals, ...
         ▬ If Automation is needed
    ●   When not to use:
         ▬ Few configuration changes only possible in WebSphere Application
           Server Admin Console / Scripting
    ●   Alternative Tools:
         ▬  ConfigWizard
         ▬  WebSphere Application Server Scripting
         ▬  WebSphere Application Server Admin Console (limited set of tasks)
    ●   Sample Task: List all available virtual portals
2
5




    ConfigEngine
    ●   The ConfigEngine takes input parameters from
         ▬ The Command line
         ▬ Property files (see next slide)
         ▬ Parent properties files
2
6




    ConfigEngine – Input values via property files


                                        Main
                                        configuration
                                        Database
                                        configuration
                                        Database driver
                                        configuration
2
7




    Triggering ConfigEngine command




    ●   Execute command in directory c:\ibm\wp_profile\ConfigEngine:
        ConfigEngine list-all-virtual-portals -DPortalAdminPwd=wpsadmin -
        DWasPassword=wpsadmin
    ●   Syntax:
         ▬ ConfigEngine.bat / ConfigEngine.sh
         ▬ Config task to be executed (e.g. list-all-virtual-portals)
         ▬ Properties not specified in the properties files / or properties to be
           overwritten
         ▬ list-all-virtual-portals lists all existing virtual Portals in command line
2
8




    Triggering ConfigEngine command
2
9




    Command Line Tools
     ConfigWizard
3
0




    ConfigWizard
    ●   Goal: Execute Config Tasks from a easy to use UI
    ●   When to use: Wizard style configuration for:
            ▬ Database Transfer


            ▬ Security Repository configuration


            ▬ Database connect


    ●   When not to use:
         ▬ If automation is needed
         ▬ If no graphical interface is available
         ▬ If other config tasks, than the ones above need to be executed
    ●   Alternative Tools:
         ▬  ConfigEngine
         ▬  WebSphere Application Server Scripting
         ▬  WebSphere Application Server Admin Console (limited set of tasks)
    ●   Sample Task: Show the beginning of how to add a LDAP repository
3
1




    ConfigWizard
    ●   Invoke the ConfigWizard
          ▬ Change to directory c:\ibm\wp_profile\PortalServer\wizard
          ▬ Invoke configwizard.bat
    ●   Click Next
3
2




    ConfigWizard
    ●   Select Configuring security, to modify the security configuration
    ●   Click Next
3
3




    ConfigWizard
    ●   Enter the Username: uid=wpsadmin,o=defaultWIMFileBasedRealm
    ●   Enter password:
          wpsadmin
    ●   Click Next
3
4




    ConfigWizard
    ●   Select Configuring Federated Repository
    ●   Click Next
3
5




    ConfigWizard
    ●   Now we will cancel at this step due to time constraint
    ●   (Otherwise we
        would have
        required a
        LDAP server)
    ●   Click Cancel
3
6




    Command Line Tools – WebSphere
    Application Server Scripting
3
7




    WebSphere Application Server
     Scripting
    ●   Goal: Command line tool to modify
                WebSphere Application Server configuration
    ●   When to use:
         ▬ Creating, Modifying, Deleting WebSphere Application Server
           settings like dynamic cache settings, thread pools, ...
         ▬ If Automation is required
    ●   When not to use:
         ▬ Modifying WebSphere Portal runtime data like pages, portlets, ...
    ●   Alternative Tools:
         ▬  ConfigWizard
         ▬  ConfigEngine
         ▬  WebSphere Application Server Admin Console
    ●   Sample Task:
         ▬ Set runtime trace for the WebSphere Portal Server
3
8




    WebSphere Application Server Scripting -
    Syntax
     ●   Change to
         C:\ibm\wp_profile
         \bin


     ●   Enter wsadmin -h
3
9




    WebSphere Application Server Scripting
    ●   In this exercise we will enable tracing for the WebSphere Portal Server
        with wsadmin
    ●   Enter the following command to connect to the server:
    wsadmin -host testserver -port 10033 -user wpsadmin -password
      wpsadmin




    ●   The command connects to the testserver on the given port, using the
        credentials of the wpsadmin user
    ●   Now that we are connected to the server process we can trigger
        commands
4
0




    WebSphere Application Server Scripting
    ●   Enter the following commands to enable tracing:
    $AdminControl completeObjectName
      type=TraceService,node=wpsbvt,process=WebSphere_Portal,*
    You need to replace wpsbvt with your node name.
    set ts [$AdminControl completeObjectName
       type=TraceService,process=WebSphere_Portal,*]
    $AdminControl setAttribute $ts traceSpecification com.ibm.wps.engine.*=all
4
1




    WebSphere Application Server Scripting
    ●   Access WebSphere Portal in the browser by entering the following URL:
        http://localhost:10040/wps/portal
    ●   Verify that a trace file trace.log was created in the directory
        C:\ibm\wp_profile\logs\WebSphere_Portal
    ●   Disable the tracing again by running:
        $AdminControl setAttribute $ts traceSpecification
        com.ibm.wps.engine.*=all=disabled




    ●   Exit the tool by running: exit
4
2




    Command Line Tools – XML Access
4
3




    XMLAccess
    ●   Goal:
         ▬ Command line tool to create, modify and export Portal artifacts
    ●   When to use:
         ▬ Creating, Modifying, Deleting Portal resources like pages, portlets, ...
         ▬ Moving singular configuration changes between environments
         ▬ Exporting Portal artifacts
         ▬ Deploying portlets
    ●   When not to use:
         ▬ Modifying WebSphere Application Server configuration settings
    ●   Alternative Tools:
         ▬  Portal Scripting
         ▬  Portal Admin Console (limited set of tasks)
    ●   Sample Task: Export complete release & deploy a portlet
4
4




    XMLAccess - Syntax
4
5




    XMLAccess
     Export
    ●   Input file controls what
        actions are performed
    ●   Sample files in
        c:\ibm\PortalServer\doc\x
        ml-samples
    ●   We will use
        ExportRelease.xml for a
        full export in the release
        format (required later on
        by release builder)
4
6




    XMLAccess - Export
    ●   Take a look at the import file:




    ●   The file defines the XML syntax used by XMLAccess to export the
        release data of the Portal
4
7




    XMLAccess - Export
    ●   Change to the directory C:\ibm\wp_profile\PortalServer\bin
    ●   Trigger the export via the following command:
        xmlaccess -in c:\ibm\PortalServer\doc\xml-samples\ExportRelease.xml -
        out InitialRelease.xml -url http://localhost:10040/wps/config -user
        wpsadmin -password wpsadmin




    ●   The result should look like this:
4
8




    XMLAccess
     Export
    ●   Check the result file
        C:\ibm\wp_profile\
        PortalServer\bin\
        InitialRelease.xml
    ●   In the beginning comments
        are listed
    ●   Then the different resources
        are exported with their
        settings
4
9




    XMLAccess
     Export
    ●   Check the file for a sample - e.g. URL Mapping:


    <url-mapping-context action="update" domain="rel" label="Home"
       objectid="C_CGAH47L0084G00I4BONHCQ10U5">
     <access-control externalized="false" owner="undefined" private="false"/>
     <portal-url resourceref="6_CGAH47L0084G00I4BONHCQ10I3" update="set"/>
    </url-mapping-context>
5
0




    XMLAccess - Import
    ●    We will deploy a sample portlet with the following xmlaccess input script:

    <?xml version="1.0" encoding="UTF-8"?>
    <request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" type="update"
          xsi:noNamespaceSchemaLocation="PortalConfig_6.1.0.xsd">
     <portal action="locate">
        <web-app action="update" active="true" uid="SPFStandardStockQuote.war.webmod">
         <url>file:///$server_root$/installableApps/SPFStandardStockQuote.war</url>
        </web-app>
     </portal>
    </request>



    ●    The portlet SPFStandardStockQuote.war will be imported
    ●    You can use the sample file DeployPortlet.xml provided as part of the
         package.
5
1




    XML Access - Import
    ●   Open command line and trigger:
    xmlaccess.bat -in DeployPortlet.xml -out DeployPortlet.xmlOut.xml -url
      http://localhost:10040/wps/config -user wpsadmin -password wpsadmin




    ●   Check the out file DeployPortlet.xmlOut.xml:
    <request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       build="wp6103_201_01" type="update" version="6.1.0.3"
       xsi:noNamespaceSchemaLocation="PortalConfig_6.1.0.2.xsd">
        <status element="all" result="ok"/>
    </request>
    ●    The portlet is now imported and can be used in our next exercises
5
2




    Command Line Tools
     WebSphere Portal Scripting
5
3




    WebSphere Portal Scripting
    ●   Goal: Command line wsadmin based tool to create and modify Portal
        artifacts limited by the roles of the user
    ●   When to use:
         ▬ Creating, Modifying limited set of Portal resources like pages,
           portlets, ...
         ▬ Combining with wsadmin WebSphere Application Server scripts to
           modify WebSphere Application Server settings at the same time
         ▬ If delegated administration to sub admins, this tool is important
    ●   When not to use:
         ▬ Moving configuration changes between environments
         ▬ Exporting Portal artifacts and Deploying portlets
    ●   Alternative Tools:
         ▬  Portal XML Access
         ▬  Portal Admin Portlets (limited set of tasks)
    ●   Sample Task: Create a sample portal page
5
4




    WebSphere Portal Scripting – Modes
    ●   Interactive Mode:
          ▬ Allows to trigger single commands
          ▬ Response directly visible


    ●   Scripting Mode:
         ▬  Allows to execute complete prepared script consisting of several
            actions
5
5




    WebSpherePortal Scripting – Interactive Mode
    ●   Open command prompt and change to directory:
    c:\ibm\wp_profile\PortalServer\bin
    ●   Invoke the scripting interface using the jython
    wpscript -lang jython
    ●   Enter User Identity: wpsadmin and User Password: wpsadmin in the
        Login at the Target Server dialog and confirm by clicking the OK button.
5
6




    WebSphere Portal Scripting – Interactive Mode
    ●   Log on to the portal using the following script command:
    Portal.login(”wpsadmin”,”wpsadmin”)




    ●   Select the parent page of our new page.
    ●   First find the parent page:
    Content.find(”all”, ”uniquename”, ”ibm.portal.Home”)
    ●   And then select the page:
    Content.select(”6_CGAH47L0084G00I4BONHCQ10I3”)
5
7




    WebSphere Portal Scripting – Interactive Mode
    ●   Create an empty page and immediately select this new page:
    Content.create(”page”,”TestPage”,”html”,”public”,”select”)




    ●   Set unique name for this page
    Content.set(”uniquename”,”wp.test.page”)




    ●   Quit the interactive mode
    quit
5
8




    WebSphere Portal Scripting – Scripting Mode
    ●       Create a file UpdateLayout.py in the directory
            C:\ibm\wp_profile\PortalServer\bin with the content:
    # login to portal

    Portal.login("wpsadmin","wpsadmin")

    print " 1. login done."
    # select page
    Content.select(Content.find("all","uniquename","wp.test.page"))

    print " 2. page selected"

    # search portlet
    portletA = Portlet.find("portlet", "name", "Struts Standard Stock Quote")

    print " 3. portlet found: " + portletA
    # create a vertical container

    Layout.create("container", "vertical", "select")

    print " 4. vertical container created."
    # create a control with the portlet

    Layout.create("control", portletA)

    print " 5. create control with stock portlet."
    # logout again

    Portal.logout()
    print " 6. logout."
    print

    print " Processing done."

    ●       You can use the file UpdateLayout.py that was provided.
5
9




    WebSphere Portal Scripting - Scripting Mode
    ●   The script will update the page we created earlier with the Interactive
        Mode – the portlet we deployed earlier with XMLAccess will be added to
        the page
    ●   # denotes a comment
    ●   Print ... prints a message to the command line
    ●   Sequence of the script:
         ▬ Login
         ▬ Locate the page
         ▬ Create a container on the page to hold the portlet
         ▬ Put the portlet into the container
         ▬ Logout
6
0




    WebSphere Portal Scripting - Scripting Mode
    ●   Invoke the script to set the layout for the new test page:
    wpscript -user wpsadmin -password wpsadmin -lang jython -f
      UpdateLayout.py




    ●   The command will execute the script contained in UpdateLayout.py
        under the user identity wpsadmin
6
1




    Command Line Tools –
    ReleaseBuilder
6
2




    ReleaseBuilder
    ●   Goal:
         ▬ Command line tool to compare different XMLAccess exports taken
           over time to generate a difference XMLAccess file that can be used
           to move the changes done to the next environment (Staging to
           Production Process)
    ●   When to use:
         ▬ Staging to Production scenarios
    ●   When not to use:
         ▬ Compare XMLAccess exports between different environments
         ▬ Other tasks
    ●   Alternative Tools:
         ▬  Portal XMLAccess (limited scenario to move single resources)
         ▬  Portal Admin Console – Site Management (limited scenario to move
            pages)
6
3




    ReleaseBuilder
    ●   You will use the release builder to generate a diff file. Before you can
        use the release builder you have to generate the next release export
        using xml access.
    ●   Open a command prompt and change to directory
        C:\ibm\wp_profile\PortalServer\bin
    ●   Generate the release export by invoking following command:
    xmlaccess -in c:\ibm\PortalServer\doc\xml-samples\ExportRelease.xml -out
      ChangedRelease.xml -url http://localhost:10040/wps/config -user
      wpsadmin -password wpsadmin
6
4




    ReleaseBuilder
    ●   The result should look like this:




    ●




    ●   Now we can use the release builder and generate a diff file that contains
        all the changed information
6
5




    ReleaseBuilder
    ●   From the directory C:\ibm\wp_profile\PortalServer\bin start
        releasebuilder without any parameter to check the syntax.:




    ●   Now we want to generate the difference between the release export
        done in the beginning of this lab and the release export you just created
    ●   Execute for that the following command: releasebuilder -inOld
        InitialRelease.xml -inNew ChangedRelease.xml -out ReleaseDiff.xml
6
6




    ReleaseBuilder
    ●   Check the resulting ReleaseDiff.xml:




    ●   Check for the page we created (TestPage) and the portlet
        (SPFStandardStockQuote.war) we deployed after the initial export
    ●   The ReleaseDiff.xml file can be used to import your changes to another
        system that is prepared to get these changes
6
7




    Administration User Interface
     Admin Portlets
6
8




    Admin Portlets – Overview
    ●   The Admin portlets are available with the IBM WebSphere Portal
        installation
    ●   Admin portlets are placed into the Administration area of IBM
        WebSphere Portal
    ●   By default as administrator you access to these portlets
    ●   With these admin portlets you can e.g.
         ▬ adapt the user interface (hierarchy of pages, page layout)
         ▬ administering web applications/ portlets (e.g. provide portlets for
           other portal servers or consume portlets from other portal servers)
         ▬ Change the access control (User and groups, credential vault,
           policies)
         ▬ Portal Settings (URL mappings, supported markups and clients)
         ▬ Portal Content (Web Content libraries, syndication, feeds)
         ▬ Search Administration (e.g. define & manage search collections)
         ▬ Manage Portal Analyses & Virtual Portals
6
9




    Admin Portlets – What's next
    ●   For the SnT session only some of these administration
        features are picked

                                                                       5
    ●   In this section we will demonstrate the following use cases:
          1) Create a user with the “Manage User and Groups”           3

             portlet
          2) Create a Virtual Portal using the “Virtual Portal
             Manager” portlet                                          1

          3) Move pages between Virtual Portals with Site
             Management
          4) Explore the Page Builder Theme to create a blog and
             share it with another user
          5) Create a static page with the Manage Pages portlet
          6) Use WebDav to modify the created static page
                                                                           2
7
0




    Admin Portlets
     Manage User and Groups
    ●   Goal:
         ▬ Add an non administration user
    ●   Background:
         ▬ Permissions can be granted to users or goups
         ▬ Hierarchical access control model (e.g. along page hierarchy)
    ●   Dependencies:
         ▬ Non admin user is used to demonstrate the Site Management
           functionality
         ▬ Non admin user also needed to show the Page Builder scenario
    ●   Alternative Tools:
         ▬  Users can also be created using XMLAccess or
         ▬  directly in the LDAP or
         ▬  in the WebSphere Application Server Admin Console
7
1




    Manage Users and Groups
     Create new user
    ●   Open browser with http://testserver:10040/wps/portal & Login with
        wpsadmin
    ●   Administration → Access → User and Groups
    ●   Click New User
7
2




    Manage Users and Groups
     Enter user information
    ●   Enter at least following information to create a user
         ▬   User ID
         ▬   Password
         ▬   Confirm Password
         ▬   Last Name


    ●   Confirm user creation with OK
7
3




    Manage Users and Groups
     User successfully created
    ●   Check the success message
7
4




    Admin Portlets
     Virtual Portal Manager
    ●   Goal:
         ▬ Create a virtual portal
    ●   Background:
         ▬ Hosting many portals within one installation
         ▬ Virtual portals may be used as Staging system
         ▬ Host different portals with different user interface and user groups
    ●   Dependencies:
         ▬ Used to demonstrate later the possibility to Site Management
    ●   Alternative Tools:
         ▬  Virtual portals can be created using the scripting interface to create
            and xml access to fill the virtual portal
7
5




    Virtual Portal Manger
     Create new virtual portal
    ●   Administration → Virtual Portals → Manage Virtual Portals
    ●   Click New Virtual Portal
                                        1




                                    3




                      2
7
6




    Virtual Portal Manger
     Complete form and confirm VP creation
    ●Complete Form
         Virtual portal name: accounts
         Virtual portal descr.:
         URL Context: accounts
         VP hostname: vptestserver
         user group: wpsadmins
    ●Confirm with OK

    ●If the entered vp host name does not
    resolve to the original hostname, add the
    entry to the hosts file
7
7




    Virtual Portal Manger
     Result of Virtual Portal creation
    ●   Watch for
        Creating Virtual Portal

    ●   Virtual Portal is listed
        in the portlet
7
8




    Virtual Portal Manger
     Login to the new created Virtual Portal
    ●   Login to the virtual portal by
         ▬   Specifying the URL context (http://testserver:10040/wps/portal/accounts) or
         ▬   Using the host name of the virtual portal (e.g. modify the hosts file to point to the same server)
7
9




    Virtual Portal Manger
     Administration area of a virtual portal
    ●   Within a virtual portal you have a limited set of administration tools
8
0




    Admin Portlets
     Resource Manager Portlet
    ●   Goal:
         ▬ Publish a page to an target server
         ▬ Promote the published page on the target server
    ●   Background: Site Management functionality might be used
         ▬ to integrate pages on an integration server
    ●   Dependencies:
         ▬ The test page, a non admin user and the virtual portal must be
           created in the previous sections
    ●   Alternative Tools:
         ▬  XML access can be used to move pages from one server to another
            (no preview, or backup by default)
         ▬  Portal scripting interface also provide the site management
            functionality
8
1




    Resource Manager Portlet
     Add source source server
    ●   Login to default Portal -> Administration → Portal User Interface → Site
        Management
    ●   Manage servers → Add new server ...
                                    1




                           3
               2               4
8
2




    Resource Manager Portlet
     Setup source server
    ●   Enter following information for the
        source server
         ▬   Host: testserver
         ▬   Port: 10040
         ▬   Path: /wps/mycontenthandler (default)
         ▬   Assign a unique name: source



    ●   Click on Show details to display the
        success message
8
3




    Resource Manager Portlet
     Setup target server
    To create the target server, click again:
      Manage servers → Add new server ...
    Enter following information for the target       1
                                                     2
      server and click OK
                                                         3
         ▬   Host: testserver                        4
         ▬   Port: 10040
         ▬   Path: a/wps/mycontenthandler/accounts
         ▬   Assign a unique name: target


    ●   Alternatively use the host name during
        setup (e.g. modify hosts file before)
         ▬   Host: vptestserver                      1
                                                     2
         ▬   Port: 10040
         ▬   Assign a unique name: target            3
8
4




    Resource Manager Portlet
     Specify credentials to access source/ target
    ●   Manage servers → Manage server access
    ●   Select source
    ●   Enter User name & Password
    ●   Click Save                              3
                                                4
    ●   Select target            1              5
    ●   Enter User name &            2
        Password
    ●   Click Save
    ●   Click Done
                                                7
                                                8
                                                9
8
5




    Resource Manager Portlet
     Publish test page to target server
    ●   Select source and target in the portlet
    ●   Navigate to the Test page and select Publish to → target
    ●   Enter Parent unique name of the target server and click OK
8
6




    Resource Manager Portlet
     Page successfully published
    ●   Check success message
    ●   Note the published test page in the target server navigation (blue page
        icon)
8
7




    Site Management
     Login to target server as non admin user
    ●   On the target server (vptestserver) the non admin user (user1) does not
        see the published Testpage – verify by logging in with user1
8
8




    Site Management
     Login to target server as admin user
    ●   On the target server (vptestserver) the admin user (wpsadmin) sees the
        published Testpage – verify by logging in with user1
8
9




    Resource Manager Portlet
     Promote test page to target server
    ●   Select Promote this page on the published Test Page
9
0




    Resource Manager Portlet
     Test page successfully promoted
    ●   Check success message
    ●   Note the promoted test page in the target server navigation (green page
        icon)
9
1




    Site Management
     Login to target server as non admin user
    ●   On the target server (vptestserver) the non admin user (user1) can see
        the promoted Testpage
9
2




    Administration GUI's
     Page Builder
    ●   Goal:
         ▬ New 6.1.5 theme that allows administrators and users to customize
           pages easily
    ●   Background:
         ▬ Provide an easy to customize theme
         ▬ Create, Modify, Delete a page
         ▬ Create, Modify, Delete Blogs, Wikis, Feed Readers
         ▬ Add / Remove portlets
         ▬ Share pages with other users
    ●   Dependencies:
         ▬ Test user to be created before
    ●   Alternative Tools:
         ▬  XML Access
         ▬  Manage Pages portlet
9
3




    Page Builder – Create a Page

                                         1.
    ●   Login as               2.

        wpsadmin to
        the default
        Portal
    ●   Click on the
        Pencil icon to
        open the
        Toolbar
    ●   Click the New
        Page button
    ●   Enter a name
        for the page,               3.
        make it private
        and hit the                 4.
        Create Page                 5.
        button
9
4




        Page Builder – Create a Page
    ●    After the page is
         created click the
         Customize button              1.

    ●    Here you can add
         portlets to the page
    ●    Click the Plus button
         besides the Blog
    ●    Name your Blog My
         Blog and click Add
9
5




        Page Builder – Create a Page

    ●    Click on Change Style and select a new style
9
6




        Page Builder – Create a Page
    ●   Click on Change Layout and check the available layouts
    ●   Then press Save
9
7




        Page Builder – Edit a Blog
    ●   Now that the
        page was
        created the
        way we wanted
        we want to
        modify our
        Blog:
    ●   Click on Create
        Post and add a
        few lines for
        your readers
    ●   Then press
        Save and
        Close
9
8




        Page Builder – Share a page
    ●   Now that we
        have created
        the page and
        blog we want to
        have a
        colleague
        review the
        page
    ●   Click on the
        Share Page
        button
9
9




    Page Builder – Share a page
    ●   Search for the
        user we
        created earlier,
        add the user to
        the View
        column and
        click Save
1
0
0




          Page Builder – Share a page
    ●   Log out and login
        with the earlier
        created test user1
    ●   Click the Pencil
        icon and select
        Share→ Add
        Pages shared with
        me
    ●   Click the Add
        button besides the
        page shared by
        wpsadmin and
        Save
1
0
1




          Page Builder – Share a page
    ●   Now the user
        can see the
        page as
        created by the
        admin
    ●   Logout and
        login again as
        admin for the
        next exercises
1
0
2




    Admin Portlets
     Manage Pages
    ●   Goal:
         ▬ Create a static page with dynamic content
         ▬ Add this created page as static page into portal
    ●   Background:
         ▬ Manage pages portlet allows to create, edit, activate, order, and
           delete normal pages as well as static pages or external web pages &
           labels
         ▬ Static pages can be created using standard
    ●   Dependencies:
         ▬ The static page will be updated to demonstrate the Web DAV feature
    ●   Alternative Tools:
         ▬  Portal scripting interface
         ▬  XML access
         ▬  Web DAV
1
0
3




    Static Page
     Open a sample web page
    ●   Open a sample web page, e.g.
        http://www-01.ibm.com/software/lotus/events/lotusphere2010/content/
    ●   Click on File → Save Page as ...
1
0
4




    Static Page
     Save and compact sample web page
    ●   Enter name of the sample page
        SamplePage.html
    ●   Select a folder
    ●   Choose WebPage, complete
    ●   Click on Save
    ●   Create a compressed version
        of the saved sample file (*.zip)
1
0
5




    Manage Page
     Open portlet and navigate to the location
    ●   Administration → Portal User Interface → Manage Pages
    ●   Content Root → Home
    ●   Click New Page
                                       1




                     2


                                   3



                            4
1
0
6




    Manage Pages
     Enter general information for the new page
    ●   Enter following information:
        Title: StaticTestPage
        Unique Name: wp.test.page.static
        Friendly URL name: staticTestPage
        Theme: PortalWeb2
    ●   Select Type of Page → Static Content
    ●   Click Set page layout properties
1
0
7




    Manage Pages
     Enter static page information
    ●   Enter information specific for the static page
        Static Page Layout File: SamplePage.html
        ZIP or HTML File Location: …
    ●   Confirm with OK
    ●   Click OK as well on the parent page to create the static page
1
0
8




    Manage Pages
     With the static page created
    ●   Additional page StaticTestPage is created
    ●   Click Home, to navigate to the new page
1
0
9




    Static page
     Display the complete static page
    ●   Click the StaticTestPage link to see the complete static page
    ●   Note the URL for the static page is still within portal
1
1
0




    WebDAV
    ●   Goal:
         ▬ Use WebDAV to modify the static page
    ●   Background:
         ▬ WebDAV can be use for managing pages and static content,
           together with mashup integration and for Web Content Management
         ▬ Can be used to browse through the page hierarchy, change
           globalization information and metadata of pages
         ▬ For static pages users can browse, read, create, update, save, copy,
           move, and delete static content.
    ●   Dependencies:
         ▬ The test static page has to be deployed before
    ●   Alternative Tools:
         ▬  XML access, Portal scripting, Admin portlets
1
1
1




    Web DAV
     Modify title of a static page
        ●   Linux: open e.g. nautilus and navigate to
            dav://testserver:10040/webdav/dav/contentmodel/wps.content.root/ibm.portal.Home/wp.tes
            t.page.static
        ●   Windows: Add a network place with the location
            http://testserver:10040/webdav/dav/contentmodel/wps.content.root/ibm.portal.Home/wp.te
            st.page.static

        ●   Modify localized_en.properties
            e.g. change title to StaticTestPage_Update_via_WebDAV
1
1
2




    Web DAV
     Modify layout of the sample page
    ●   navigate to
        dav://testserver:10040/webdav/dav/contentmodel/wps.content.root/ibm.portal.Home/wp.tes
        t.page.static/staticcontent
    ●   Modify SamplePage.html to include static page into the portal layout
        by removing <HTML> and </HTML> tag
    ●   Save the page
1
1
3




    Web DAV
     Result after WebDAV update
    ●   Refresh static page to see the update name and the portal layout with
        the static page
1
1
4




    Mashup integration
    ●   Goal:
         ▬ Create a mashup page within portal
    ●   Background:
         ▬ With portal you are now able to consume, create and update
           mashup pages
    ●   Alternative Tools:
         ▬  Mashup Center
1
1
5




    Mashups
     Add widget: Feed Reader
    ●   Click My Mashups → Go to Edit → Favorites
    ●   Drag & Drop Feed Reader widget on the free area below
1
1
6




    Mashups
     Customize widget: Feed Reader
    ●   Click the tools icon and select Edit Settings
    ●   Select Make article links available to other widgets
    ●   Deselect Show more details
    ●   Click Save
1
1
7




    Mashups
     Add widget: Web Site Displayer
    ●   Select Tools
    ●   Drag & Drop Web Site Displayer on the area below
1
1
8




    Mashups
     Current mashup page
    ●   Both widgets are displayed
    ●   Click the wire widgets icon
1
1
9




    Mashups
     Wire both widgets together
    ●   Select Selection as URL (HTML)
1
2
0




    Mashups
     Wire both widgets together
    ●   Choose the Web Site Displayer widget
    ●   Check URL using URL (HTML)
    ●   Optional you can click on Show Graph to display the current wiring
    ●   Click Done
1
2
1




    Mashups
     Save page and go to view mode
1
2
2




    Mashups
     Click a link within the RSS feed
    ●   After clicking a link in the RSS widget, the Web Site Displayer displays
        the URL behind this link
1
2
3




    WebSphere Application Server
     Integrated Solution Console
    ●   Goal: User Interface to modify
                WebSphere Application Server configuration
    ●   When to use:
         ▬ Creating, Modifying, Deleting WebSphere Application Server
           settings like dynamic cache settings, thread pools, ...
         ▬ Management of a cluster, remote nodes, ...
    ●   When not to use:
         ▬ Modifying WebSphere Portal runtime data like pages, portlets, ...
    ●   Alternative Tools:
         ▬  WebSphere Application Server Scripting
         ▬  ConfigWizard
         ▬  ConfigEngine
    ●   Sample Task:
         ▬ Modify the java heap setting of the WebSphere Portal Server
1
2
4




    Websphere Application Server
    Integrated Solution Console - Login
    ●   Open browser and enter
        http://testserver:10027/admin
    ●   Enter User ID: wpsadmin and Password: wpsadmin
    ●   Click Log in
1
2
5




    Websphere Application Server
    Integrated Solution Console - navigate
    ●   Click Servers -> Application servers -> WebSphere Portal
1
2
6




    Websphere Application Server
    Integrated Solution Console - navigate
    ●   Click Java and Process
        Management
    ●   Select Process Definition



    ●   Select Java Virtual Machine
1
2
7




    Websphere Application Server
    ISC – set heap size
    ●   Set the Initial Heap Size and the
        Maximum Heap Size to the
        recommended values from the IBM
        WebSphere Portal 6.1.x
        Performance Guide
         ▬   Note that the recommendation differs
             if using 32 or 64 bit JVM
         ▬   Windows 2003: 1408 Mbytes
         ▬   Linux: 2048 Mbytes

    ●   Click OK
    ●   Click Save to store the changes to the master configuration
1
2
8




    Summary
    ●   As administrator you can use different tools to modify administration/
        configuration data
    ●   The decision which tool to use depends on the task to be done and on
        the preferences of the administrator
    ●   For repeatable tasks we always recommend to use command line tools


    ●   Thank you for your attention!
1
2
9




    Questions and Contact Details

								
To top