Administering IBM WebSphere Portal 9.0: A comprehensive workshop

Transcription

1 Administering IBM WebSphere Portal 9.0: A comprehensive workshop Thomas Hurek (thurek@us.ibm.com), Software Architect, IBM January 2017 Copyright International Business Machines Corporation All rights reserved. Summary: The goal of this white paper is to explain the various administration and configuration tools offered by IBM WebSphere Portal 9.0. Learn about which tool to use for which task and about the new capabilities of WebSphere Portal 9.0, and understand differences from previous versions of WebSphere Portal. We take you through exercises for each tool so you can learn hands-on how to use them. Table of Contents 1 Introduction What is WebSphere Portal? Configuration information Preparing to install WebSphere Portal Installing WebSphere Portal Understanding the WebSphere Portal file system structure Command line tools ConfigEngine ConfigWizard Command line tools: WAS scripting XMLAccess WebSphere Portal scripting ReleaseBuilder Solution Installer Web Developer Toolkit Administration user interface: Admin portlets Accessing Portal Admin portlets: Manage User and Groups Admin portlets: Virtual Portal Manager Administration GUI's: Managed Pages Theme Analyzer Admin portlets: Web Application Bridge Personalization rules WebDAV SiteBuilder Theme Development Tooling Integration with Watson Content Hub WebSphere Application Server Admin User Interface Conclusion Resources Author biographies

2 1 Introduction In this white paper, we explore the newly added and already existing administration tools for managing IBM WebSphere Portal 9.0 on IBM WebSphere Application Server 9.0. The exercise is separated into the following sections: Briefly introduce WebSphere Portal and how configuration information is used. Step through installing WebSphere Portal. An overview of the new File System structure. An introduction to ConfigEngine and listing the virtual portals using ConfigEngine. Explore modifying portal security using the Configuration Wizard. WebSphere Application Server scripting. Use XML Access to create a baseline, then use XML Access to deploy a portlet and page. Create a page using the Portal Scripting interface. Create a comparison release (delta) using the Releasebuilder tool. Use the Solution Installer tool to install the Theme Editor package. Investigate the Web Developer Toolkit Explore the Portal UI. Learn how to manage users and groups Check out virtual Portals Explore the 9.0 UI to manage pages. Use the Theme Analyzer. Explore Web Application Bridge it is a new proxy solution in WebSphere Portal to integrate backend web sites fast and easy. Learn to create and use Personalization Rules. Learn to use WebDav, a newly supported standard to update Portal settings. Experience Site Builder to quickly build site templates and create an instance. Leverage the Theme Manager to create and edit a theme. Integrate WebSphere Portal with Watson Content Hub. Finally we will use the WebSphere Application Server 9.0 Admin Console. If you are more interested in the command line tools, then you can start with Section 5; if you are more interested with the user interface, you could start directly with Section 6. Formatting/hints The following color codes are used in this paper: Magenta: 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 quickly, but they are not necessary to understand the meaning. So if you are using black and white, that will work as well. Our server name here is localhost. Replace these server names with your local host name on which WebSphere Portal is installed. Environment During the install, WebSphere Portal does the following: Installs the IBM Installation Manager (IIM), if not already there 2

3 Creates WAS 9.0 Lets you choose the Installation directory; for example, C:\ibm\PortalServer or /opt/ibm/websphere (you can choose another directory, but you then must adjust references in this document accordingly) Creates the Derby database, which contains the WebSphere Portal tables Enables file-based security after the install Creates the Portal Administrative user, wpsadmin / wpsadmin (you can choose another password during install, but then you must adjust references in this paper accordingly) 2 What is WebSphere Portal? IBM WebSphere Portal products provide enterprise web portals that help companies deliver a highly-personalized, social experience for their customers. WebSphere Portal products give users a single point of access to the applications, services, information and social connections they need. These products help increase visitor response and reduce web operations cost while offering a range of capabilities to meet your business needs. WebSphere Portal is installed on top of WAS, which contains the Java TM Runtime edition that provides APIs and an abstraction layer from the operating system (see figure 1). Figure 1. WebSphere Portal architecture Industry and Business Partner Solutions Pure ApplicationSystems Web Experience Hypervisor Patterns for WebSphere Portal and WCM SoftLayer Web Experience Hypervisor Patterns for WebSphere Portal and WCM WebSphere Portal Server Page and Content Aggregation Services Rules Portlet API & REST Interfaces Search Site Administration Web Content Manager WCM API & REST Interfaces Content Approvals WebSphere Application Server Network Deployment J2EE Dynamic Content Impersonization Feed Reader WCM Rendering Tagging & Rating Live Text & Portlet Wiring Credential Vault Personaliization Site Analytics Site Design Syndication Themes & Skins WebSphere Portal Portlet Container and Services Portal Model Authoring Web Content Integrator Worklight Server Page & Content Handlers AJAX Proxy Content Provisioning Projects Feed Provider Portlet Preferences Web Application Bridge Rich Text Editor WCM Social Media Publisher Serlet Engine Web Services Security/SSO JDBC Tools Forms Experience Builder Process Designer Worklight Consumer Edition Server & Client Side Aggregation WevDAV XML Access & Portal Scripts XML Access & Portal Scripts Mobile Devices Remote Portlet Consumer Feeds Rational Application Developer Web Experience Factory Social Software & Services Enterprise Apps & Content BPM & Workflow Engines Remote Portlet Producer EMM - Analytics Engines. Clients as browsers or mobile devices gain access to the portal via the HTTP(s) protocol, and the request arrives at WAS, which routes it to the WebSphere Portal servlets, portlets, widgets, and other server side components. 3

4 The WebSphere Portal servlets, portlets, and widgets build a Web page by aggregating information from the Portal configuration and backends via APIs and connections. The newly built Web page is then sent via the HTTP(s) protocol back to the client device, which renders the response including execution of javascript frameworks and, depending on the client, the response can be returned in a different form of html (responsive or adaptive design). 2.1 Configuration information The configuration information is stored as follows (see figure 2): WebSphere Portal uses the underlying WAS to serve requests WebSphere Portal configuration data is stored in both the databases and the file system WAS uses only the file system for its configuration data (though there are some exceptions to this rule, such as session persistence) The Configuration Tools modify the configuration data in the different repositories Figure 2. Configuration information storage You may want to change the WebSphere Portal configuration to integrate into your environment; for example, to connect to your databases or LDAP Server(s), to IBM Lotus Domino mail servers, to IBM Lotus Sametime servers, or to do the following: customize the look and feel make the solution secure achieve high availability tune performance deploy your code enable or disable additional features perform maintenance WebSphere Portal is quite flexible and, depending on your use case, more than one tool can be used to achieve your goals. 4

5 2.2 Preparing to install WebSphere Portal The references to directories in this document are for the Microsoft Windows / RedHat Linux operating systems. It is possible to use any other multi-platform operating system, but the directories would need to be adjusted accordingly. First, obtain the WebSphere Portal V9.0 install media, which can be retrieved from, for example, the IBM Passport Advantage Web site. Section 3 provides a step-by-step guide through the install of WebSphere Portal. If you already have an install, you can start directly with Section 4. 3 Installing WebSphere Portal In this section we show how to install WebSphere Portal. If you have already installed WebSphere Portal 9.0, you can skip this chapter or just read over the figures to better understand how to perform the install. IBM Installation Manager (IM) is an eclipse-based tool that is used to install WebSphere Portal, as well as several other IBM products. Customers who already have this tool (at the v1.8.5 level or later) can use it to install WebSphere Portal directly from Passport Advantage. You can also download electronic images or request physical DVDs which provide everything you will need if starting from scratch. This image/dvd will install IM, if it is not already present, then launch IM to install: IBM WebSphere Application Server including the Java Virtual Machine Recommended Application Server fixes that will allow Portal to work better IBM WebSphere Portal binaries and the Configuration Wizard profile The WebSphere Portal install offers multiple options to customize the install: Mode of Install: Installing from local media or network IBM Installation Manager: If not existing it will install an IBM Installation Manager instance for you Install Location: Where you would like to install Admin user: The userid and password of your administrative user Node name: The administrative name of your instance this information is used in case of clustering (combining multiple installs into a group for high availability) Language: The Install Language of the Portal. URI: URL of the Portal. Profile configuration options like name of the profile, ports, creating additional profiles. Profile Definition: For WebSphere Portal you can choose to create a profile during installation or perform a binary only install and create the profile later. * IBM(R) Installation Manager for Rational(R) Software Delivery Platform is an installation management tool that installs and maintains Installation-Manager-based software packages. IBM Installation Manager enables you to modify feature sets, search for updates, uninstall, and manage the licenses of installed software. WebSphere Portal is using the IBM Installation Manager to install WebSphere Application Server and WebSphere Portal. You can either use the Install shell provided by Portal or install directly with IBM Installation Manager. The minimum version of IBM Installation Manager required is From the WebSphere Portal 9.0 media launch the./setup.sh (Linux or Unix) or setup64.exe (Windows) command: 5

6 Figure 3. Starting the Installation This brings up the WebSphere Portal Launchpad. 2. Select Install Portal and to trigger the install of the Installation Manager. Figure 4. Triggering the installation 6

7 If you do not have IBM Installation Manager installed the install will prompt you to install it. 3. In the install panel click Next. Figure 5. Verifying installation of IBM Installation Manager 7

8 In the licensing panel verify the license, select I accept the terms in the license agreement and click Next. Figure 6. Accepting the license of IBM Installation Manager 8

9 4. In the next window choose an installation directory for the IIM and click Next (see figure 7). 9

10 Figure 7. Choose a location for the IIM 5. In the Summary window, verify the information and click Install (see figure 8). 10

11 Figure 8. Verify the IIM installation information 6. After the install finishes a Status window displays. Click Restart Installation Manager to trigger the install of Portal. 11

12 Figure 9. Status of the IIM installation 7. After the IIM has restarted, the Start window displays. You can install products, modify the installation of the products (for example, by adding new features), update the products (for example, apply ifixes or fix packs), undo changes, manage licenses, or uninstall products. Select Install to trigger the install of Portal. 12

13 Figure 10. IIM Start window The Install Packages panel allows you to select the packages you want to install. Since we do not have an existing install of WebSphere Application Server or 9, we select not only WebSphere Portal Server but also WebSphere Application Server and the JDK version 8. The WebSphere Portal Enable is an additional package to the WebSphere Portal package adding an additional content feature that WebSphere Portal Server package does not include. 8. After selecting all check boxes select the Show all Versions box and click on the check for Other Versions, Fixes and Extensions button to check for the latest versions. In the Authentication window enter your IBM ID and click OK. 13

14 Figure 11. Select packages to install 9. The next panel allows you to select the additional fixes for both WebSphere Portal and WebSphere Application Server. We need the one on the list select it and click Next to trigger the Install of Portal. 14

15 Figure 12. Select fixes to be installed 10. In the next panel you can review the license agreement click I accept and then click Next. 15

16 Figure 13. License Agreement 11. In the next window the location for the shared files for the installation manager can be selected. 16

17 Figure 14. Select directory for shared Installation Manager files 12. In the next window, select the location where WebSphere Portal and WAS will be installed; click Next (see figure 14). 17

18 Figure 15. Select directories for WebSphere Portal and WAS 13. Select additional language packages that need to be installed; click Next (see figure 15). 18

19 Figure 16. Select installed languages for WebSphere Portal and WAS 19

20 The next panel allows to customize which features are installed. For WebSphere Portal, you can choose to create a Portal Server Profile. You can add the Portal Server Profile later with the Configuration Wizard as well. For this exercise we will have it created as part of the installation. 14. Review the information in the panel and click Next. Figure 17. Select components 20

21 In the next panel we will review the versions we will install and click Next. 21

22 Figure 18. Validate versions 22

23 15. In the next panel you need to determine the initial administrative user and profile configuration for the ConfigWizard profile as well as the WebSphere Portal profile (if it was selected in the last screen). For this exercise we have used wpsadmin as userid and wpsadmin as password. Continue with Enter the Administrator user ID and password for the Portal Server. Figure 19. Entering the Portal admin ID and password 16. You will enter the node name (it can be any unique name) and the fully qualified host name you are performing the install on as well as the cell name of the WebSphere cell that Portal is created in. The node name is relevant for operations inside WebSphere Application Server when building a cluster (multiple Portals). For the latter exercises you will need the host name. Also enter the administrative userid and password. For this exercise we have used wpsadmin as userid and wpsadmin as password. 23

24 Figure 20. WebSphere Portal profile Configuration 17. In the Advanced mode you can specify a custom context root (instead of /wps/portal) and custom ports, as well as a custom directory for the profile and the profile name (see figure 19 ). Continue with Next. Figure 21. Advanced Configuration options 24

25 16. The final window shows a summary of what will be installed (see figure 20). If the values are as you would like, click Install for the install to start. Figure 22. Reviewing the Installation settings 25

26 17. The final panel shows a summary of what will be installed. If the values are correct then click Install for the install to start. Figure 23. Finishing the installation 26

27 27

28 18. Once the install finished successfully you will see the following panel (sample from Linux). Select None and click Finish to end the install. Figure 24. Finishing the Initial Installation Next we get back to the setup screen and now will install CF13 on the just installed Portal. 28

29 Figure 25. Continuing the Installation with the cumulative fix Go back to Installation Manager and select the Update button: Figure 26. Continuing the Installation with the cumulative fix 29

30 Select WebSphere Portal and click Next. Figure 27. Continuing the Installation with the cumulative fix In case a prompt is displayed asking for userid/password for Fix Central (the database holding the fix packs and fixes) you can ignore that and press Cancel since CF13 is already part of the installation media. In the next screen note the warning that currently Portal is started after the installation and needs to be stopped: 30

31 Figure 28. Warning of running processes Open a command prompt or shell and execute the stopserver.sh bat command: E.g. on Linux: /opt/ibm/websphere/wp_profile/bin/stopserver.sh WebSphere_Portal -username wpsadmin -password wpsadmin 31

32 Figure 29. Stopping the Portal JVM Also stop the configwizard JVM: E.g. on Linux: /opt/ibm/websphere/appserver/profiles/cw_profile/bin/stopserver.sh server1 -username wpsadmin -password wpsadmin Figure 30. Stopping the Config Wizard JVM Now we can go back to the Installation Manager, click Back and then Next and now the dialog shows no more running processes and we can click Next again to continue: 32

33 Figure 31. Updating to CF13 The next screen recommends a backup before proceeding but since we are just installing the product we can continue with Next. Figure 32. Updating to CF13 - confirmation 33

34 Next the license screen is displayed. Check the license, agree and click Next. Figure 33. Updating to CF13 license confirmation The screen is another confirmation and we continue with Next. Figure 34. Updating to CF13 feature confirmation 34

35 In the final review screen select Update to start the Update. Figure 35. Updating to CF13 final confirmation 35

36 Once the update successfully finishes a screen like the one below is displayed. Click Finish to continue. Figure 36. Updating to CF13 success screen Now that we finished the update task inside the Installation Manager let's see what is to do next in the Installation steps: 36

37 Figure 37. Next steps in installation We need to run the applycf task to finish installing CF13. Open a command prompt and switch to the profile PortalServer bin directory and then trigger the applycf command: cd /opt/ibm/websphere/wp_profile/portalserver/bin./applycf.sh -DportalAdminPwd=wpsadmin -DWasPassword=wpsadmin Figure 38. Running the applycf command 37

38 When the update finishes you will see a screen like the one below: Figure 39. Finishing the CF13 installation The last step in the process of installing WebSphere Portal 9 is to add the WebSphere Portal 9 package. If we jump back to the Installation screen we can see: Figure 40. Adding the v9 package 38

39 Go back to the installation Manager and click on Install: Figure 41. Installing the v9 package Select WebSphere Portal Server and Enable 9 (or if you have Extend or another package or Web Content Manager select the according version 9 package) and then click Next. 39

40 Figure 42. Selecting v9 Accept the license in the next screen and click Next. Figure 43. Accepting the license 40

41 In the next screen review the information and click Next. Figure 44. Reviewing the selected packages In the next screen the userid and password for Portal and WebSphere Application Server are queried. Enter them (e.g. in my case it is wpsadmin/wpsadmin for both Portal and WebSphere Application Server) and then either select to not check the credentials or click the Validate Credentials button and then hit Next. Figure 45. Entering credentials 41

42 In the Summary screen hit the Install button to start the Installation. Figure 46. Starting the Installation After the installation finishes in the final screen select Finish to end the installation. Figure 47. Finishing the Installation 42

43 4 Understanding the WebSphere Portal file system structure In this section, we discuss the directory structure of WebSphere Portal; specifically, the location of the command line tools, binaries, and configuration of the product. These are the use cases for which you would work with the WebSphere Portal file system: Configuration changes like modifying properties files, etc. Starting and stopping the server Starting and stopping command line tools View log files Install updates You would not use the WebSphere Portal file system for modifying internal configuration files directly, bypassing administration / configuration tools. Nearly all the alternative tools mentioned in this topic modify the file system in some way. In the following pages we will explore the WebSphere Portal file system structure, including the following: AppServer directory PortalServer directory Profile directory Profile directory logs Profile directory WIM/VMM ConfigEngine directory ConfigWizard profile directory Installation Manager Directory 1. Open a File Explorer and navigate to /opt/ibm/websphere/appserver. The following are a few of the directories in the figure below that are important when working with WebSphere Portal: The AppServer directory, containing the binaries of WebSphere Application Server as well as templates, utilities, and the Java Developer Kit. The bin directory, containing the WebSphere Application Server command line tools that are independent of the profile. The Derby database binaries, found in the derby directory. The Java directory, containing the Java Developer Kit 1.6 as well as the 1.7 JDK, including the Java Runtime Edition. Figure 48. AppServer directory 43

44 2. Open a File Explorer Explorer and navigate to /opt/websphere/portalserver. The directories worth noting in the figure below are: The PortalServer directory, containing mainly the binaries for WebSphere Portal. In WebSphere Portal 8.5 the binaries and the configuration and tools are separated; therefore, the PortalServer directory no longer needs to be touched. The bin subdirectory, containing XMLAccess, Release Builder, version reporting, and other command line tools. For legacy purposes the tools are still stored in this directory as well as in the profile directory. New tools in this directory were added for the multiple profile support. The doc subdirectory, which holds API/SPI documentation as well as XMLAccess, Javascript, Portal Application Archive sample files. 44

45 The shared directory contains the main.jar file binaries of WebSphere Portal. It's possible to drop class files into the PortalServer/shared/app directory so they're loaded by the classloader. We would recommend though to define a custom shared library if needed. Figure 49. PortalServer directory 3. Open a File Explorer Explorer and navigate to /opt/websphere/wp_profile. The Profile directory (see figure below) contains the configuration as well as command line tools for WebSphere Portal and WebSphere Application Server: The bin directory contains all the command line tools related to the profile, for example, for starting and stopping the server. The config directory holds the configuration for the WebSphere Application Server. ConfigEngine is the command line tool to trigger configuration tasks in WebSphere Portal (it replaces the WPSConfig tool used in previous releases). The log directory inside the 45

46 ConfigEngine directory contains the Portal Install and Configuration Logs. The installedapps directory holds the Installed J2EE applications, including portlets. The PortalServer directory contains the Portal command line tools in the bin directory, configuration files in the config folder, and the Derby database in the derby directory. The Solution Installer no longer needs to be installed from the Web it is laid down at Install time. All the tools are used later. Figure 50. Profile directory 4. The runtime logs of WebSphere Portal can be found inside the log directory (see figure 25). Open a File Explorer and navigate to /opt/websphere/wp_profile/logs/websphere_portal. The log directory contains a directory for every server instance. For a standalone setup the 46

47 directory name is WebSphere_Portal. The following files are of interest in this directory: SystemOut.log, containing the system messages, including warnings and startup information of the server. SystemErr.log, containing errors and exceptions. native_stderr.log, containing the JVM messages, including garbage collection data if verbose garbage collection is enabled. It's possible to configure a separate file to contain the verbose garbage collection data, which would have a custom name, for example, Verbosegc. Figure 51. Profile directory--logs The next directory we want to point out is the Virtual Member Manager (VMM) config directory (see figure below). Navigate to /opt/ibm/websphere/profiles/wp_profile/logs/websphere_portal/config/cells/wpvmcell_1/wim/con fig. 5. It contains the user repository configuration data. In some previous releases the configuration was stored in the WebSphere Member Manager Configuration files (wmm.xml). Figure 52. Profile directory - WIM/VMM 47

48 6. The ConfigEngine directory exists two times in the installation one time inside the profile and once outside of it. The reason for the ConfigEngine in the root installation directory is to be able to create and manage additional profiles independent of the existing profile or for a binary only installation in which no ConfigEngine exists. Navigate to /opt/ibm/websphere/configengine. Figure 53. ConfigEngine directory 7. The Configuration Wizard is a user interface based tool to configure the Portal. With version 8.5 we have extended it a lot to make the configuration easier. It resides within its own profile. Navigate to /opt/ibm/websphere/appserver/profiles/cw_profile. Similar to the wp_profile the same directories exist for this profile. Important subdirectories are the logs directory to see the logs and the bin directory to administer the profile. 48

49 Figure 54. ConfigWizard profile directory 5 Command line tools Now let's focus on the command line tools. 5.1 ConfigEngine The ConfigEngine command line tool is used to execute all WebSphere Portal Config tasks. Use the tool for configuration changes such as security configuration, enabling/disabling components, clustering, and virtual portals, or if automation is needed. 49

50 It cannot be used for all configuration changes, some of which are possible only in WebSphere Application Server Admin Console / Scripting. Alternative Tools include the ConfigWizard, WebSphere Application Server Scripting, and WebSphere Application Server Admin Console (limited set of tasks). Note: With WebSphere Portal 8.5 and 9 the ConfigWizard has been extended and is the tool of choice for executing configuration tasks. We recommend to use the ConfigWizard where possible (not all tasks have been included) but support using the ConfigEngine tasks as well. As an example task, let's list all available virtual portals. The ConfigEngine takes input parameters from the command line, property files, and the parent properties file (see figure below). Figure 55. ConfigEngine Input values via property files The most important input property files are: The wkplc.properties file, which is the main configuration file wkplc_comp.properties, containing Advanced Security, Process Integration, URL configuration wkplc_dbdomain.properties, containing the configuration settings for Database configuration. wkplc_dbtype.properties, containing the configuration settings for Database driver configuration. 50

51 Execute the command in the directory, /opt/websphere/wp_profile/configengine, as follows (see figure below):./configengine.sh list-all-virtual-portals -DPortalAdminPwd=wpsadmin -DWasPassword=wpsadmin Figure 56. Triggering the ConfigEngine command where the syntax is as follows: ConfigEngine.bat / ConfigEngine.sh Config task to be executed (in this case, 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 the command line The Figure below shows the output of the command. Figure 57. ConfigEngine command output 51

52 5.2 ConfigWizard he ConfigWizard tool lets you execute configuration changes from an easy-to-use UI that guides the user through the complete flow and allows executing the tasks. Use it for: Database transfer Adding a ldap repository Clustering Creating a Deployment Manager Adding an additional Cluster Node Installing/Uninstalling a Portal Application Archive Creating/Deleting a profile with Portal Migration Don't use it if: no graphical interface is available config tasks other than the ones that are part of the ConfigWizard must be executed Alternative tools are as follows: ConfigEngine WebSphere Application Server Scripting 52

53 WebSphere Application Server Admin Console (limited set of tasks) As an example task, let's show the beginning steps for how to add an LDAP repository: 1. First, to start the ConfigWizard server, change directory to /opt/ibm/websphere/appserver/profiles/cw_profile/bin and invoke./startserver.sh server1 (see figure 41). Figure 58. configwizard start Start a browser with following URL: and login with wpsadmin/wpsadmin by clicking Log in (see figure below). (The wizard might redirect you to the https URL Figure 59. ConfigWizard Login screen 3. Click on Configuration Wizard to see the Configuration Wizard Welcome screen (see figure below). Figure 60. Configuration Wizard Welcome Screen 53

54 4. Take a look at each of the different parent topics and the sub tasks. You can go back by clicking Home. For this exercise choose Set Up a Stand-alone Server, select the Enable Federated security link (see figure below). Figure 61. Configuration Wizard - Workflow selection 54

55 4. Keep the default operating system Linux as well as the other default settings for the profile. Note the forward and backward buttons as well as the cookie trail at the top to go back when needed. Click the right arrow icon to move forward (see figure below). Figure 62. Choose operating system 55

56 5. Leave the settings in the next screen as is; click Right Arrow (see figure below). Figure 63. Confirm default settings 6. In the next window (see figure below), enter all the detailed information for your LDAP. Choose some sample values (e.g. see screenshot below). Afterwards click the Right Arrow. Figure 64. Filling out sample values 56

57 7. In the next window (see figure below), enter the information specifically for your LDAP. Choose some sample values (e.g. see screenshots below). Afterwards click the Right Arrow. Figure 65. Filling out sample values Note that the wizard triggers live validations so the hostname and port need to exist. 8. In case you entered valid values the final window (see figure below), you will see all the 57

58 steps that will be executed by the Wizard one by one. There can be automatic and manual steps. You can see the command that will be called by each step when you click the View Step Command. On the right hand side you can see the status of each step. Figure 66. Review and execution screen In consideration of time scroll down and hit the Cancel button. Figure 67. Cancel the execution 58

59 5.3 Command line tools: WAS scripting This command line tool is used when creating, modifying, or deleting WebSphere Application Server settings like dynamic cache settings and thread pools, or when automation is required. It is not for use when modifying WebSphere Portal runtime data like pages or portlets. Alternative tools are ConfigWizard, ConfigEngine, and WebSphere Application Server Admin Console. The Figure below shows the WebSphere Application Server Scripting syntax, where we do the following: Change to /opt/ibm/websphere/profiles/wp_profile/bin Enter./wsadmin.sh -h Figure 68. WebSphere Application Server Scripting syntax 59

60 60

61 For our sample exercise, let's enable tracing for the WebSphere Portal Server with wsadmin: 1. Enter the following command to connect to the server (see figure below):./wsadmin.sh -host localhost -port user wpsadmin -password wpsadmin Figure 69. Connect to the server The command connects to the server on the given port, using the credentials of the wpsadmin user, and now that we're connected to the server process, we can trigger commands. 2. Enter the following commands to enable tracing (see figure below): $AdminControl completeobjectname type=traceservice,node=wpvmnode_1,process=websphere_portal,* set ts [$AdminControl completeobjectname type=traceservice,process=websphere_portal,*] $AdminControl setattribute $ts tracespecification com.ibm.wps.engine.*=all Figure 70. Enable Tracing with wsadmin 4. Access WebSphere Portal in the browser by opening a browser and entering the following URL: 61

62 5. Verify that a trace file trace.log was created in the /opt/ibm/websphere/profiles/wp_profile/logs/websphere_portal directory. Figure 71. Checking trace.log 6. Disable the tracing again by running the following (see figure below): $AdminControl setattribute $ts tracespecification com.ibm.wps.engine.*=all=disabled 7. Exit the tool by running the exit command. Figure 72. Disable tracing with wsadmin 5.4 XMLAccess his command line tool is used to create, modify, and export WebSphere Portal artifacts. 62

63 Specifically, use it to: Create, modify, and delete WebSphere Portal resources like pages or portlets Move singular configuration changes between environments Export WebSphere Portal artifacts Deploy portlets It cannot be used to modify WebSphere Application Server configuration settings. Alternative tools are Portal Scripting and Portal Admin Console (limited set of tasks) or the Solution Installer. The figure below shows the syntax for XMLAccess by invoking./xmlaccess.sh in /opt/ibm/websphere/profiles/wp_profile/portalserver/bin. Figure 73. XMLAccess syntax 63

64 XMLAccess - Export For our sample task, we export a complete release and deploy a portlet. The input file controls what actions are performed, and we use ExportRelease.xml for a full export in the release format (required later by Release Builder). Figure below shows sample files in /opt/ibm/websphere/portalserver/doc/xml-samples. Figure 74. Sample.xml files 64

65 he Figure below shows the import file. Figure 75. Import file The file defines the XML syntax used by XMLAccess to export the release data of WebSphere Portal. 1. First, change to the /opt/ibm/websphere/profiles/wp_profile/portalserver/bin directory, and then trigger the export via the following command (see figure below):./xmlaccess.sh -in /opt/ibm/websphere/portalserver/doc/xml-samples/exportrelease.xml -out InitialRelease.xml -url -user wpsadmin -password 65

66 wpsadmin Figure 76. Triggering the export The result should look like figure 57. Figure 77. Request successful message 2. Then, check the result file C:\ibm\WebSphere\wp_profile\PortalServer\bin\InitRelease.xml (see figure below). In the file, comments are listed at the beginning, and then the different resources are exported with their settings. e.g. use notepad InitialRelease.xml Figure 78. Result file 66

67 67

68 Check the file for a sample, such as a page: The tag name content-node shows this is a page or label The parameter action="update" is used if this file is used as import file and means a contentnode will be updated (or created if not there) Parameter domain="rel" indicates that this configuration is from the release database The uniquename identifies the content-node uniquely Each resource has an internal objectid A local title for English has been set. There is a set of parameters The user and privileged user role have been granted on the page to the group all authenticated portal users A content mapping to a piece of WCM content exists 68

69 XMLAccess - Import Now let's deploy a sample portlet with the XMLAccess input script shown in listing 1: Listing 1. XMLAccess script <?xml version="1.0" encoding="utf-8"?> <request build=" " type="update" version=" " xmlns:xsi=" xsi:nonamespaceschemalocation="portalconfig_8.5.0.xsd"> <portal action="locate"> <web-app action="update" active="true" domain="rel" objectid="z1_0okihck0kgv000ac87v79n2001" removable="true" uid="wcmsupport.wcmsupporttools.26e webmod"> <url>file://localhost/tmp/wcmsupporttools80.war</url> <context-root>/wps/pa_wcmsupporttools</context-root> <display-name>pa_wcmsupporttools</display-name> <access-control externalized="false" owner="undefined" private="false"/> <servlet action="update" active="true" domain="rel" name="wcmsupporttools" objectid="zv_0okihck0kgv000ac87v79n2003" remote-cache-dynamic="false"/> <portlet-app action="update" active="true" defaultlocale="en" domain="rel" name="wcmsupport.wcmsupporttools.26e " objectid="z2_0okihck0kgv000ac87v79n2005" uid="wcmsupport.wcmsupporttools.26e "> <access-control externalized="false" owner="undefined" private="false"/> <portlet action="update" active="true" defaultlocale="en" domain="rel" name="wcmsupporttools" objectid="z3_0okihck0kgv000ac87v79n2007" provided="false" servletref="zv_0okihck0kgv000ac87v79n2003"> <access-control externalized="false" owner="undefined" private="false"> <role actionset="user" update="set"> <mapping subjectid="all authenticated portal users" subjecttype="user_group" update="set"/> </role> </access-control> </portlet> </portlet-app> </web-app> </portal> </request> 69

70 The WCM Support tools portlet (you can find it here) WCMSupportTools80.war will be imported from the path /tmp, and you can use the sample file, DeployPortlet.xml, in the directory /tmp: 1. Open command line, change to /opt/ibm/websphere/profiles/wp_profile/portalserver/bin, copy the war file in the expected location, and trigger following commands (see figure below):./xmlaccess.sh -in /tmp/deployportlet.xml -out DeployPortlet_out.xml -url -user wpsadmin -password wpsadmin Figure 79. Open command line and trigger 2. Check the output file, DeployPortlet_out.xml in the /opt/ibm/websphere/profiles/wp_profile/portalserver/bin directory: Figure 80. Check result file The portlet is now imported and can be used in our next exercises. 5.5 WebSphere Portal scripting This wsadmin-based tool is used to create and modify WebSphere Portal artifacts limited by the roles of the user. You can use it when: Creating or modifying a limited set of WebSphere Portal resources like pages or portlets Combining with wsadmin WAS scripts to modify WAS settings at the same time Also, the tool is useful if administration is delegated to sub-admins. Do not use it when moving configuration changes between environments or when exporting WebSphere Portal artifacts and deploying portlets. Alternative tools are Portal XML Access and Portal Admin Portlets (limited set of tasks). 70

71 WebSphere Portal Scripting modes There are two modes in WebSphere Portal Scripting: The first is Interactive mode, which allows us to trigger single commands and whose response is directly visible. The second is Scripting mode, which allows us to execute a complete, prepared script consisting of several actions. Interactive mode As an example task, we create a sample portal page, using the Interactive mode: 1. Open a command prompt and change to the directory: /opt/ibm/websphere/profiles/wp_profile/portalserver/bin 2. Invoke the scripting interface, using the jython scripting language:./wpscript.sh -lang jython 3. In the Login at the Target Server window (see figure 61), enter wpsadmin in both the User Identity and User Password fields; confirm by clicking OK. Figure 81. Login at the Target Server window 4. Log on to the portal, using the following script command (see figure 62): Portal.login( wpsadmin, wpsadmin ) Figure 82. Log on to the portal 71

72 5. List all available projects by running the following command : Project.listall() 6. List all Content Libraries for the current virtual Portal with the following command: DocumentLibrary.listall() 7. Figure 83. List all libraries Select the parent page of our new page by first finding the parent page (see figure below) Content.find( all, uniquename, ibm.portal.home ) and then selecting the page: Content.select("Z6_ A0BR2B300GO2") Figure 84. Find and select page 6. Create an empty page and immediately select this new page (see figure below): Content.create( page, TestPage, html, public, select ) Figure 85. Create and select empty page 72

73 7. Set a unique name for this page (see figure below): Figure 86. Set unique name Content.set( uniquename, wp.test.page ) 8. Quit the interactive mode, using the quit command (see figure below). Figure 87. Quit interactive mode 73

74 Scripting mode Now let's modify the created test page, this time using the Scripting mode: 1. Create a file UpdateLayout.py in the directory /tmp with the content in listing 2: Listing 2. Script for UpdateLayout.py # 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", "WCMSupportTools") 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 support portlet." # logout again Portal.logout() print " 6. logout." print print " Processing done." where # denotes a comment, print prints a message to the command line, and the sequence of the script is: Login Locate the page Create a container on the page to hold the portlet Put the portlet into the container Logout The script will update the page we created earlier with the Interactive mode, and the portlet deployed earlier with XMLAccess will be added to the page. 74

75 2. Invoke the script to set the layout for the new test page (see figure below):./wpscript.sh -user wpsadmin -password wpsadmin -lang jython -f /tmp/updatelayout.py Figure 88. Invoke script The command executes the script contained in UpdateLayout.py under the user identity wpsadmin. 5.6 ReleaseBuilder This command line tool compares different XMLAccess exports taken over time, generating a difference XMLAccess file that can be used to move the changes made to the next environment. The tool is used in staging to production scenarios. It's not to be used to compare XMLAccess exports between different environments or for other tasks. Alternative tools are Portal XMLAccess (limited scenario to move single resources) and Portal Admin Console Managed pages feature. You use ReleaseBuilder to generate a diff file. Before you can use ReleaseBuilder, however, you must generate the next release export using xml access: 1. Open a command prompt and change to directory /opt/websphere/wp_profile/portalserver/bin 2. Generate the release export by invoking following command (see figure 68):./xmlaccess.sh -in /opt/ibm/websphere/portalserver/doc/xmlsamples/exportrelease.xml -out ChangedRelease.xml -url -user wpsadmin -password wpsadmin Figure 89. Generate the release export 75

76 The result should look like that shown in figure 69. Figure 90. Release export result Now we can use the ReleaseBuilder to generate a diff file that contains all the changed information: 1. From the directory /opt/websphere/wp_profile/portalserver/bin, start./releasebuilder.sh without any parameter to check the syntax (see figure 70). 76

77 Figure 91. Start releasebuilder 2. Now we generate the difference between the release export we did at the beginning of this paper and the release export we just created. To do this, execute the following command (see figure 71):./releasebuilder.sh -inold InitialRelease.xml -innew ChangedRelease.xml -out ReleaseDiff.xml Figure 92. Generate the difference 3. Check the resulting ReleaseDiff.xml, as shown in figure below (for example, gedit ReleaseDiff.xml). 77

78 Figure 93. Resulting ReleaseDiff.xml Notice that the file contains the Web application defining the portlet as well as the page (content-node) and the portlet on the page. Also note the new proxy-config settings the former AJAX proxy configuration is now part of XMLAccess and so can easily be staged. 4. Now check for the page we created (TestPage) and the portlet (WCMSupportTools80.war) we deployed after the initial export. The ReleaseDiff.xml file can be used to import your changes to another system that's prepared to receive these changes. 5.7 Solution Installer You can use the Solution Installer to install, uninstall, and update solutions or applications to an IBM WebSphere Portal server instance. The Solution Installer uses the Portal Application Archive (PAA) format as the standard format for application distribution. Portal Administrators can use the Solution Installer to install existing PAA-formatted applications to the WebSphere Portal server instance. Portal Solution Developers can use the Solution Installer to install PAA-formatted applications they develop for their company. The solution installer can be used to deploy different artifacts: Enterprise Applications Portlets Run XMLAccess 78

79 Run ant scripts Run Portal or WAS Scripting Deploy and Update WCM Libraries Deploy Personalization rules It is frequently used to deploy Portal Catalog solutions that are provided by the Portal and WCM Development Teams but it is also possible to use it to create your own application packages. While with previous releases of WebSphere Portal the Solution Installer had to be installed separately, it is part of WebSphere Portal 8.x. Alternative tools are Portal XML Access and Portal Admin Portlets (limited set of tasks) or Portal Scripting. New with version 8.5: You can export the artifacts into an initial Portal Application Archive on the source system including themes, war files, pages and portlets, After the initial release you can build a differential release with the Portal Application Archive format. In this exercise we will deploy the IBM Theme Editor package that is provided on the catalog at the following URL: action=editdocument&documentid=4e6461c014edeac785257f20002b035f The package consists of a page, portlet and ear file. Later on we will try out the task to export all artifacts for an initial staging. 79

80 The installation of a PAA archive consists of two steps the install that lays down the files and the deployment that invokes the configuration steps and scripts. Unzip the downloaded zip file and copy the included paa file theme-editor-preview-1.0.paa to the /tmp directory. Execute the following command in the directory, /opt/ibm/websphere/profiles/wp_profile/configengine, as follows (see figure below):./configengine.sh install-paa -DPAALocation=/tmp/theme-editor-preview-1.0.paa -DWasPassword=wpsadmin -DPortalAdminPwd=wpsadmin Figure 94. Triggering the Install PAA command Verify that the output looks like in the following figure: Figure 95. Verifying the Install PAA command Now that we have installed the PAA we need to trigger the deployment. In the same command line trigger the following command:./configengine.sh deploy-paa -DappName=theme-editor-preview-1.0 -DWasPassword=wpsadmin -DPortalAdminPwd=wpsadmin Figure 96. Triggering the Deploy PAA command Verify that the output looks like in the following figure: Figure 97. Verifying the Install PAA command 80

81 Next we will try out the new configuration task to export the initial release for a staging to production using the Portal Application Archive. Execute the following command in the directory, /opt/ibm/websphere/profiles/wp_profile/configengine, as follows (see figure below):./configengine.sh build-initial-release-paa -DdestPAADir=/tmp -DWasPassword=wpsadmin -DPortalAdminPwd=wpsadmin Figure 98. Triggering the export initial release PAA command Verify that the output looks like in the following figure: Figure 99. Verifying the export PAA command You can add the following parameters to customize the build-initial-release-paa task: sharedappresourcesrootdir The directory for.jar files, classes, and compressed files that are then stored in the shared/app directory. sharedextresourcesrootdir The directory for.jar files, classes, and compressed files that are then stored in the shared/ext directory. appstoextract A comma-separated list of applications to extract from the source environment. For example, you might extract the wps_theme,iehs,dojo_resources files. They are then packaged in the PAA file. exportwebdavtheme Enter a value of true to download and include the themes.zip file from WebDAV. exportwcmdata Enter a value of true to export all Web Content Manager libraries. The export-wcm-data task is run when you use exportwcmdata. Restriction: Do not use this parameter in place of syndicating the libraries from the target environment. The export we took is from the default base Portal. When having virtual Portals additional commands need to be run for each Virtual Portal. 81

82 Let us investigate next what is part of the created PAA. The PAA format is basically a renamed zip file. Unzip the file /tmp/websphereportal.paa and investigate the different directories: 2 Components WebSpherePortal.shared for data shared across all Portals, WebSpherePortal.unique for the virtual/base Portal we just exported from. The subdirectories of each contain the war files, WAS configuration, xmlaccess for the Portal artifacts, PZN rules, WCM Libraries, Figure 100. Analyzing the exported PAA file The exported PAA file can be imported into a target system that has been emptied first. 82

83 Subsequently you can generate differential PAA releases by using the syntax:./configengine.sh build-initial-release-paa -DdestPAADir=directory_to_store_PAA -DpreviousPAA=initial_PAA -DWasPassword=password -DPortalAdminPwd=password 5.8 Web Developer Toolkit While more targeted for development, the tool can also be used by administrators. This toolkit includes two main areas of functionality: A "Web Developer Dashboard" that provides a user interface for working with Script Portlets, Portal themes, and WCM design elements. The theme support uses the Digital Experience File Sync tool under the covers. The Script Portlet support uses the Script Portlet command line support which must be installed separately on your workstation. A command line tool "dxwcmdesigns" for moving WCM design elements - Presentation Templates and Components - between your local file system and your Portal server. This functionality is also available from the Dashboard. Alternative tools are Portal XML Access and Portal Admin Portlets (limited set of tasks) or webdav. The tool is based on nodejs, so you need to make sure it is installed first. E.g. to install node version 6 you could trigger: curl --silent --location bash - yum install -y nodejs And then to verify functionality run: node -v Figure 101. Checking nodejs version The Web Developer Toolkit can be downloaded from here: Download the digexp-toolkit.zip file from here: First, extract the file on your workstation. Then run in the same location: chmod a+x./install.sh./install.sh This will install the two main programs, dxdashboard (for the dashboard UI) and dxwcmdesigns (the command line support for accessing WCM design libraries). That completes the installation. Note that this tool would typically be installed on a developer system and not necessarily on the system that has the Portal installed. To start the user interface in a shell enter the command dxdashboard 83

84 The resulting start screen can then be used to set the initial settings: User name: wpsadmin Password: wpsadmin Host: localhost (in case the tool was installed where Portal is installed) Port: The button besides the Script Applications Folder, Themes Folder, WCM Design Libraries Folder allows to create folders and selecting them as directories to synch the data. Then hit the Save button. Figure 102. Initial settings for Dashboard Try out the different tabs to load WCM libraries or Themes with the tool. Figure 103. Downloading WCM libraries 84

85 85

86 Figure 104. Synching themes After synching a theme or a WCM library check the file system on what was downloaded from the server e.g. for the simple theme: Figure 105. Checking downloaded theme 86

87 6 Administration user interface: Admin portlets The Admin portlets are available with the WebSphere Portal installation and are placed in the Administration area of WebSphere Portal. By default, as administrator you have access to these portlets. Here are some examples of what you can do with the Admin portlets (see figure below): adapt the user interface (hierarchy of pages, page layout) administer Web applications/ portlets (for example, provide portlets for or consume portlets from other WebSphere Portal servers) change the access control (users and groups, credential vault, policies) modify WebSphere Portal settings (e.g. URL mappings, supported markups and clients) modify WebSphere Portal content (e.g. Web Content libraries, syndication, feeds) manage search administration (for example, define and manage search collections) manage WebSphere Portal analyses and virtual portals Figure 106. Admin portlets navigation pane 87

88 Portlets related to Web Content Management, Personalization Rules, as well as Collaboration and Messaging are located below the Applications tab (see figure below). Figure 107. Application portlets navigation pane In this section, we choose to demonstrate these use cases: create a user with the Manage Users and Groups portlet create a Virtual Portal using the Virtual Portal Manager portlet explore the new tool bar to create and update a page, Web Content creating, explore project management, page previewing, and impersonation understand and leverage vanity URLs leverage the new theme analyzer portlet explore the new Scripting portlet use the Web Application Bridge to integrate an existing web site use WebDav to connect to Portal and explore the new theme profiles leverage Site Builder to create a site builder template and then use it to create an instance explore the Theme Manager portlet integrate Watson Content Hub 88

89 6.1 Accessing Portal In this topic we learn how to access the Portal and what the different artifacts in the Portal markup are. 1. Open a browser with the URL You will see the Portal UI for the anonymous user: the Welcome link is a page that is also currently selected the links on the banner for Sign Up and Login are also pages that can be used for login and signing up to create a new user id Note the new toolbar with the drop down for navigation across root pages Figure 108. Anonymous start page 89

90 2. Click the login link and log in with userid wpsadmin and password wpsadmin. Figure 109. Login to Portal After the login the default page Getting Started is displayed. The page contains a portlet displaying some welcome information. The structure of the web site is defined by the theme which links are displayed, how the navigation looks like, the colors, branding, 90

91 See the next figure for details: Figure 110. Authenticated Area after Portal Login Currently selected page Currently Logged in user Actions Menu Logout Sibling pages Portlets On the page New with version 8.5 we have introduced the Universal Toolbar it can be used for: Navigation e.g. to the Administration area Project Management Management of Pages and Labels Creating a page Deleting a page Modifying a page and its content Moving a page or label Preview See the next figure for details: Figure 111. Universal Toolbar Project Selection Edit Mode Toggle Navigation to Applications Preview Navigation to Administration 91

92 6.2 Admin portlets: Manage User and Groups In this topic we use the Manage Users and Groups portlet (see figure below) to add an nonadministration user. Note that Permissions can be granted to users or groups, and there is a hierarchical access control model (for example, along page hierarchy). Figure 112. Manage User and Groups portlet Later, the non-admin user is used to demonstrate the Managed Pages preview functionality. Alternatively, you can create users by using XMLAccess or directly in the LDAP, or in the WebSphere Application Server Admin Console. To create a new user with the Admin Portlet: 1. Open a browser with and log in with userid wpsadmin and password wpsadmin. 2. Use the toolbar to go to Administration: Figure 113. Navigating to User and Groups 3. Then go to Users and Groups, and click the New User button (see figure below). Figure 114. Create new user 92

93 3. Enter at least following information to create a user (see figure below): User ID Password Confirm Password Last Name Figure 115. Enter user information 93

94 4. Confirm the user creation by clicking OK; you should see the User created successfully message (see figure below). Figure 116. Success message 94

95 6.3 Admin portlets: Virtual Portal Manager We use this admin portlet to create a new virtual portal (see figure below) that can be used, for example, to host many portals within one installation, or as a staging system, or to host different portals with different user interfaces and user groups. Figure 117. Virtual Portal Manager portlet Note that you can also create virtual portals by using the scripting interface and then using XMLAccess to fill the virtual portal. 95

96 To create the new virtual portal: 1. Use the Toolbar to navigate to Virtual Portals > Manage Virtual Portals, and then click the New Virtual Portal button (see figure below). Figure 118. Create new virtual portal 2. Complete the virtual portal's information as follows (see figure below): Virtual portal name: accounts Virtual portal description: The accounts Virtual Portal URL Context: accounts Initial admin user group: wpsadmins 96

97 Figure 119. Enter virtual portal's information 3. Click OK. 97

98 You should see the created successfully message and our new The Accounts Virtual Portal listed in the portlet (see figure below). Figure 120. Confirmation of creation 4. Log in to the newly created Virtual Portal (see figure below) by specifying the URL context ( Click Login. Figure 121. Login screen 98

99 The figure below shows the Administration area of a virtual portal, within which you have a limited set of administration tools. Figure 122. Administration area 6.4 Administration GUI's: Managed Pages Managed pages and the Universal Toolbar streamline site management in your portal by simplifying how you create pages and add content. Because page information and content are stored in web content libraries, you can more easily coordinate and publish changes with syndication. Managed pages are portal pages that are stored in IBM Web Content Manager. By managing portal pages from within Web Content Manager, you can apply features like workflow, version control, and syndication to portal pages. When you perform a new installation of IBM WebSphere Portal, managed pages are enabled by default. The following administrative capabilities are exposed inside the theme without having to use the Admin portlets under the Administration tab: The following already existed with Portal 7: Creating a Page, Deleting a Page, Moving a Page Modifying a page: Adding or removing portlets Modifying portlet properties and settings Changing the style Changing the layout 99

100 Assign Permissions Tagging and Rating These were added with Portal 8.0: Creating and managing a project Analytics Preview Approval New with Portal 8.5: Managing Labels Vanity URLs Dojo is not used any more for the main window during edit mode Edit mode is now enabled for mobile devices Workflow enhancements to manage items inside a project Association of content visually The page management now happens as part of a WCM project. You can combine WCM and Portal page modifications into the same project. Projects have their own life cycle they follow an approval process and allow to use versions. A test user must be previously created, and alternative tools are XML Access and the Manage Pages portlet. We will first create a project that we will use to make the page changes with. To create a project: 1. If still logged in, logout. 2. Log in to the default Portal as wpsadmin ( 3. Select the Published Site link. 4. Click the New Project button (see figure below). Figure 123. Trigger project creation 100

101 5. Enter a name for the project. Note the new ability to use project templates that already define certain default settings. Hit the Create button. Figure 124. Creating a project After creating the project the Theme directly switches to the Edit Mode of the current page. Note that there is a link now to jump back to the View Mode to view the changes you have made. Also note that the display now happens as part of the project we created. The project MyFirstProject is selected. The items that are part of the project are displayed at the moment there is no item. The new project menu allows you to configure the project, exit it and additional options like creating a project template out of the current project. Figure 125. Success screen for project creation 101

102 We want to create a new page next. 1. Click the arrow below the project to open the Site Manager menu. 2. Select the icon besides the Welcome page and in the new menu select Create Sibling Page. 3. Enter a page name and friendly url and hit Create Page. Note the Page Template option. A page template defines a structure and settings for a page e.g. the assigned Web Content Management Site Library or the portlets on the page. You can create your own templates and reuse them later. Figure 126. Creating an empty page 102

103 See the newly created page being displayed and selected. At the moment there is no content on the page. Select the Plus icon in the left hand side section. Figure 127. Adding portlets or content to the empty page 103

104 Note the different categories of Applications or Page components one can add. Select Applications and enter Script in the search dialog. Figure 128. Edit the empty page Click the plus icon besides the portlet or use drag and drop to put the portlet on the page. See figure below. Figure 129. Adding the script portlet 104

105 Enter Syndicated Feed Portlet in the search dialog and drag and drop it on the page. Figure 130. Add a feed portlet After having added the feed portlet to the page you can see that both portlets were added. The feed portlet is pointing to a default feed while the script portlet does not show anything yet. Since they are shown below each other you could drag the Syndicate Feed portlet to the right column for better visibility. Figure 131. Dragging a portlet Let's see how it looks like for an end user by using the preview function. Note that a normal user would not see the current page as it is in draft mode and the project has not been published. The Preview mode allows us to see how an end user would see the page after it has been published. Select Visibility Menu As User. Figure 132. Previewing the Page 105

106 In the Impersonation dialog select a user to impersonate by entering the name of the user we created earlier (user1) into the search field and click the search icon. In the resulting dialog select the radio button in front of the user and click the Impersonate button. With that you effectively become this user and so can review what he will see after the page has been published. Figure 133. Impersonating the user After triggering the Impersonation you can see the page as the user would see it. Note the selected project. Also note the userid that is displayed you know show as user1 that you impersonated. Click the Stop Previewing button to undo the impersonation and become the admin user again. 106

107 Figure 134. Previewing the page as impersonated user Now that we are the admin user again we want to continue modifying our page. Switch back to Edit Mode and open the page settings dialog and select Style and choose a style. Figure 135. Selecting a style The layout of the page determines which content is displayed where on the page. Select the Layout tab and select a different layout. Figure 136. Selecting a layout 107

108 The new vanity URL feature let's you create a short URL for a resource in Portal outside of hierarchy. Select the Vanity URL tab and enter a URL and hit Save. Figure 137. Entering a vanity URL Next we will edit the script portlet on the page to show some information. 108

109 Close the Page Details dialog and click Edit in the script portlet. Figure 138. Editing the script portlet In the opening dialog change the title of the portlet and enter some HTML, CSS and JavaScript code and then click Save->Save. Figure 139. Editing the script portlet Note that syntax issues are highlighted in red e.g. above the <b> tag was not closed. After saving you can see the preview of the entered code being executed and prerendered in the Preview section. 109

110 Figure 140. Editing the script portlet After that close the Script portlet Editor and now you can see the resulting user interface. Figure 141. Editing the script portlet 110

111 In the View mode you can see how the page will look like. Note that you see the page version as it is part of the project you created. It is still a draft page. Select the project and select the Published Site state to see how the page looked before the modifications we made. Figure 142. Viewing the page In the published state we can see that the page does not even exist. Let's go back to the project and publish it. Select Published Site and select our project. Figure 143. Viewing the published state Select the Project at the top and click the Open Overview link. Figure 144. Entering Project Management 111

112 Notice that all the items we worked on are part of the project. Note that because the script portlet triggering the creation of a content item the content will also show up by its title (Welcome). Select the Manage Project link. Figure 145. Entering Project Management Select the different items and click More Approve. Typically this task would be handled by a different person or group. Figure 146. Project management 112

113 Notice that after the Approval the documents / page are now in Publish Pending state. We will now publish the project by pressing the Publish Project button. Figure 147. Publishing the project 113

114 Note that now that we have published the page the new page is showing in the Published Site state. Select the new page and have a look. Figure 148. Viewing the modified page after publication 114

115 Let us try the vanity URL we created. Enter the following URL and notice that the URL changes to our page: Typically you would create a rewrite rule at the HTTP server that would redirect the vanityurl /MyFirstPage to the longer form as we entered and so you could have tiny URLs. Figure 149. Using a vanity URL 6.5 Theme Analyzer WebSphere Portal 8 introduced the Theme Analyzer on the Catalog. With version 8.5 we ship the Analyzer out of the box. In this exercise we will explore it. Use the Theme Optimization Analyzer to view, but not edit, all parts of the theme optimization framework inside of WebSphere Portal. With the portlet, you can easily see which pages have specific profiles that are set or inherited. You can also see which profiles are available and belong to which theme. Additionally you can browse and explore all aspects of the available modules: You can see what modules are loaded for a specific profile or all modules of the whole system. You can drill down into the dependency hierarchy to understand interdependencies and get different views on it, such as a parent view. The module explorer also features a rich search set so that you can easily find modules that contribute certain resources or capabilities, or browse all exposed data. 115

116 If you encounter problems, you can also export your set of data as a compressed file and share it with others. They can then import your data set and examine your profiles and modules. Home is the welcome screen of the portlet and provides a selection of features that are supported by this portlet. 1. Login to Portal as admin (wpsadmin/wpsadmin). 2. Use the Toolbar to navigate to Administration Portal Analysis and select the Theme Analyzer. Figure 150. Initial View of the Theme Analyzer 3. Select Examine page profile information. Then drill down to the two new pages we created and verify the assigned profile. Figure 151. Examine a page 116

117 4. Go back to Home and then select Utilities -> Control Center. Select the Dynamic Content Spot (Inline) Debug. Figure 152. Enabling debug 117

118 5. Go back to Home to one of our pages and examine the inline debug mode it shows which component / jsp is providing which part of the page. Figure 153. Dynamic content spot debug mode 118

119 6. After examining the content spots use the toolbar to switch back to the Analytics portlet and turn off the the debug mode. Figure 154. Disabling debug mode 119

120 6.6 Admin portlets: Web Application Bridge The web application bridge uses reverse proxy technology to integrate web-based content providers, such as the Microsoft SharePoint server, with IBM WebSphere Portal. Administrators must first define the virtual web applications or content providers. A lightweight IFrame portlet displays the content from the backend applications. Users can then access the IFrame on a page without requiring direct network access to the backend application. A special engine maps Uniform Resource Identifiers (URIs) on the iframe portlet to real URIs from the content providers. Integrating the web application bridge with WebSphere Portal is a multi step process. The first part of the process is creating an application component from the Web application bridge manager 120

121 portlet. The second part requires that you add the Web Dock portlet on a page and then configure it to point to the appropriate application component. To begin, let's open a sample Web page, for example: We will integrate this web page with the Web Application Bridge. Figure 155. Open sample Web page Before you can use Web Application Bridge the context root of the Web Application Bridge.ear file must be adjusted. This is a one-time operation and does not need to be performed every time you are integrating another backend application into Portal. To perform this change we use the WAS Administrative Console: 1. Log in to the Integrated Solutions Console (see figure below) by opening a browser and entering: 2. For both the User ID and Password fields, enter wpsadmin; click the Log in button. Figure 156. Log-in screen 121

122 3. Select Applications Application Types WebSphere Enterprise Applications. Click the Show Filter Function button, enter wp.vwat.servlet.ear, and click Go (see figure below). 122

123 Figure 157. Applications Start window 4. In the next window you see the wp.vwat.servlet.ear file for which you searched. Click the.ear file to access the properties of the application (see figure below). Figure 158. Applications Search Result window 5. In the properties window for the.ear file, locate and select the Context Root for Modules link (see figure below). 123

124 Figure 159. Application Properties window 6. Change the Context Root field to / as shown in figure below; click OK. Figure 160. Application Context Root window 7. On the next window, click Save. 124

125 Figure 161. Application Properties window 8. If needed, search again for the wp.vwat.servlet.ear application, select the check box in front of it, and then click Stop (see figure below). Figure 162. Stop the application 9. After the application has been stopped, select it again and this time click Start (see figure below). 125

126 Figure 163. Start the application 10. Verify that you see the successful start message and then log out of the console by clicking the Logout button (see figure below). Figure 164. Start the application and log off Now that we are done with the WAS change let's switch back to Portal: 1. Now switch back to the browser as admin (wpsadmin/wpsadmin) 126

127 2. Select in the Toolbar Portlet Management > Virtual Web Application Manager 3. Then select Create Content Provider Profile. Figure 165. Web Application Bridge Admin portlet Enter a unique title and enter the URL Then press Save. Figure 166. Create a Content Provider Profile 127

128 Next we will a policy to allow users to access the backend. Click Add Policy. Figure 167. Web Application Bridge Admin portlet In the next screen we can define multiple configuration settings for the Content Provider, including Single Sign-On settings. Enter a unique name for the policy and click Save. Figure 168. Creating access policy 128

129 Next we will create a web dock portlet application that we can then add to pages. Select the Web Dock Applications tab and click Create Web Dock Application. Figure 169. Creating web dock application 129

130 Next we will fill out the required information for the application and click Save. Title: Lucene Content provider profile: Apache Resource path: /core Figure 170. Creating a web dock application 130

131 The next step is to create another Portal page and add the Web Dock portlet to it. Switch back to Home. Then make sure that Published Site is selected and toggle the Edit Mode button. We will this time create the page outside of a project the change is visible immediately then and no versions are kept. Then click the Create Sibling Page button for the last page in the list. Figure 171. Switch to Home and trigger Edit In the Edit mode of the page enter a title and select Next Sibling of current page. Then click the Create page button. Figure 172. Result screen 131

132 Switch to the Page -> Layout area and select the 1 Column layout. Figure 173. Changing the layout of a page Next we will add the portlet to the page. Switch back to Create -> Applications, search for Lucene and drag it onto the page. Figure 174. Adding the portlet to the page Switch back to the View Mode and see the integrated backend site that is now proxied via Portal. Check the links on the page and note that they point to the Portal Server and not the apache Site. Figure 175. Reviewing the resulting page 132

133 6.7 Personalization rules WebSphere Portal Personalization provides automatic customization of Web site content for individual users and user groups. Personalization can recognize a specific user based on a profile or can determine characteristics of a user based on previous purchases, products, pages viewed, and so forth. Personalization then selects content that is appropriate for that profile. For example, if a person has a high salary range, Personalization can be configured to retrieve information about a commercial Web site premium product. If an individual belongs to a particular geographic region, content specific to that region may be targeted to the individual. When the page is assembled with the proper personalized information, users see their personalized page. In this simple sample case we create a visibility rule that controls when a page is displayed, only on a certain day of the week. We use the Personalization Navigator and Editor admin portlets to create the rule and then use the Manage Pages portlet to associate the rule with the page. Instead of using the administration portlets it is also possible to export and import rules using the pznload command line utility. In this exercise we focus on the admin portlets. 1. Log in to Portal as Administrator (wpsadmin/wpsadmin) and use the toolbar to go to Personalization -> Business Rules. The Personalization Navigator lists all the defined Personalization objects and allows you to create, edit, and delete Personalization objects like rules (see figure below). Figure 176. Business Rules tab 133

134 134

135 2. Select New -> Rule, to bring up the window to create a new rule (see figure below). Figure 177. Create a new Business rule 3. In the next window, define the following (see figure below): Name of the Rule: Description: Monday. Rule Type: attribute *: value *: Monday Rule This is a visibility rule to display a portlet or page only if today is Select Visibility Rule from the drop-down box Select Date Weekday from the drop-down box Select Monday and then click Submit. Click Save at the bottom of the page. Figure 178. Configure a new Business rule 135

136 4. In the next window you can see that your Monday Rule has been created (see figure below). Figure 179. Business Rule creation screen Figure 180, continued 136

137 Now that we have created the rule we want to associate it with one of our pages and test that it works: 1. To associate the page with the rule, use the toolbar to select Portal User Interface Manage Pages, and then select Content Root Home and click the Edit Page Properties button as shown in the figure below. Note that if you were to select a project before making this change, the association of the rule to the page would be part of the project. In our case we make the change without a project, and so the change is visible immediately without a separate approval / review cycle. Figure 181. Select a page 137

138 2. In the Edit Page properties window (see figure below), scroll down, expand the Advanced options menu, and click the little icon to map a rule. In the pop-up menu, select the Select Rule option. Figure 182. Edit Page properties window 3. In the Select Rule window (see figure below), select the Monday Rule we just created and click OK. Figure 183. Select Rule window 138

139 4. Verify that the correct rule has been selected and then leave the Edit Page properties section by clicking OK (see figure below). Figure 184. Edit Page properties 139

140 5. Verify that the rule works by navigating to Home and checking which pages are displayed; if you are doing this exercise on a Monday, the page should appear. On all other days the page should not display as shown in the figure below; instead, the next page is selected and displayed. Figure 185. Executing the rule 140

141 The Personalization Rules component in Portal is quite powerful. It can be used with Web Content Manager data as well as Portal data for campaigns and many other scenarios, and the rules can execute custom logic to have full flexibility. 6.8 WebDAV Our goal here is to use WebDAV to review the profile configuration of the theme. WebDAV can be used for managing pages, static content, and for Web content management as well as managing themes and skins. It can also be used to browse through the page hierarchy, and to change globalization information and metadata of pages. For static pages, users can browse, read, create, update, save, copy, move, and delete static content. Alternative tools are XMLAccess. We will use the built in Linux client for webdav. In case you are using Windows use a client software for WebDav like Anyclient or winscp. Click on Places -> Connect to Server. Figure 186. Starting webdav connection 141

142 Note that there are multiple entry points with WebDav for Portal: /themelist Administration of themes Title, description, metadata (maps directly to DB) /skinlist Administration of skins Title, description, metadata (maps directly to DB) /fs-type1 Modify static resources directly Themes, skins, layouts, common resources, iwidgets /contentmodel Portal pages /content Web Content Manager data 142

143 For our exercise we will connect to the themelist entry point and explore the profile configuration. Click New Site and enter the following information... Service Type: WebDAV (HTTP) Server: localhost Port: Folder: /wps/mycontenthandler/dav/themelist/ User Name: wpsadmin Click Connect. When prompted enter the password wpsadm1n Figure 187. Connecting to Portal In the resulting screen you can see the list of themes that are deployed in WebDav. 1. Select the Portal 8.5 theme the name is ibm.portal.85theme. 2. Take a look at the files inside the theme and then select the profiles folder. Figure 188. Exploring the theme 143

144 Open one of the profiles in the profile folder to look at the profiles (You can right click on the file and use gedit to look at the file). The structure defines the different modules that are loaded as part of the model. The deferred profile is the default with 8.5. It defines a minimum set of components loaded during viewing the page and loads more in case of edit mode. With 8.5 we introduced hidden profiles that will not show up in the Admin Console that are used for special pages in Portal. Figure 189. Reviewing the profile definitions 144

145 6.9 SiteBuilder Site Builder is an application that is used to create site templates and section templates. You then use Site Builder to quickly roll out new websites, or add new sections to existing websites, using these site templates and section templates. Installing Content Template Catalog and Site Builder together offers you the widest choice of website designs. After you install Site Builder and set up access for administrators and website creators, they can log in to IBM WebSphere Portal and go to the Site Builder page to access the features of Site Builder. After you create a site with Site Builder, you can use IBM WebSphere Portal and IBM Web Content Manager to customize it further. For example, you can add pages and portlets, edit content, set up content targeting, and refine author and user access. With Portal 9 (and Portal 8.5 starting CF8) it is automatically installed. Alternative tools are XMLAccess and the Site Builder / Managed Pages admin portlet. We use the Site Builder to create a simple site template and then creating an instance of it. 145

146 1. Log in to Portal as Administrator (wpsadmin/wpsadmin) and use the toolbar to go to Applications -> Site Builder. The Site Builder portlet lists the existing templates, instantiated sites and allows to create or modify templates, exporting and deleting them. Figure 190. Site Builder To create a new Template click Create Site Template. Enter a unique name and title in the Template Properties section. It is possible to configure a custom WCM Library to be leveraged but we will use the default for here. Figure 191. Site Builder Template Properties 146

147 147

148 Next enter Site Properties (those are leveraged when creating the label for the site). Figure 192. Site Builder Site Properties In the Content Library section we leave the default to store possible content inside the Portal Site Library. Figure 193. Site Builder Library Properties 148

149 In the Site Structure dialog you can add the pages and their structure to the template that will then be instantiated when the template is leveraged. Track the Articles template into the Site Structure. Figure 194. Site Builder Library Properties Next select Advanced and pick a style and take a look at Access Control and then Publish and Close the template. Figure 195. Site Builder Advanced Properties 149

150 After that we can see our newly created template and will click Launch Wizard to instantiate the template. Figure 196. Site Builder Launch 150

151 Fill out the information for the new site instance name. Figure 197. Site Builder Launch site name 151

152 Jump right to Site Structure and hit the Create Site button to create the instance. Figure 198. Site Builder Launch creating the site 152

153 In the confirmation dialog review and click OK. Figure 199. Site Builder Launch creating the site You can then see the progress of the creation on the right hand side: Figure 200. Site Builder Launch creating the site 153

154 Click the link to go to the Site to see the result (in this case a fairly simple instance of a site of one page with some web content on it). Figure 201. Site Builder Launch result 6.10 Theme Development Tooling Use the Theme Manager portlet to create new themes from templates, edit existing themes, and copy, export, or delete themes with one click. You can find the Theme Manager by clicking Applications menu > Theme Development in your portal. Alternative tools are XMLAccess and Webdav. We use the Theme Manager to create a simple theme and editing it with the theme editor that we installed as paa earlier. Log in to Portal as Administrator (wpsadmin/wpsadmin) and use the toolbar to go to Applications -> Theme Development. The Theme developer portlet lists the existing themes and allows to create or modify themes, exporting and deleting them. Figure 202. Theme Developer Next we will create a new theme by clicking Create Theme. Enter the information for the theme title and validate that the Simple Theme is selected as template and click Create. The Simple Theme was shipped with a CF, is very simple and is based on bootstrap for easy css structures. One can also designate a custom theme as template. 154

155 Figure 203. Theme Developer creating a theme In the resulting screen select the Edit icon to make modifications to the theme webdav files. Figure 204. Theme Developer creating a theme In the Theme Editor it is now possible to modify the files e.g. the theme.html fileto add additional div structures. Figure 205. Theme Editor 155

156 Note the included bootstrap framework files. Let's try out our new theme by assigning it to the Getting Started page. Switch back to Home->Getting Started and open the Edit Mode, Page Settings for the page and then going to Edit Page Properties: Figure 206. Editing page settings Select the new theme as theme for the page and Bootstrap as the Profile. 156

157 Figure 207. Editing page settings Click Save in the end, leave the edit mode and close the dialogs to see the result: Figure 208. Rendering the new theme 157

158 6.11 Integration with Watson Content Hub IBM Watson Content Hub is a new product released at the end of It allows to create, manage, and deliver engaging and relevant customer experiences with our cloud-based, cognitive-powered content management service. WebSphere Portal 9 allows to integrate the assets stored in the cloud based system into the local WebSphere Portal system to leverage it for rendering the data. Alternative tools are not available. To enable the integration a configuration task needs to be run. We assume that a tenant on Watson Content Hub was already setup. Watson Content Hub is subscription based and also has a free trial option. For the initial setup we need the tenant-id, host, userid and password for the Watson Content Hub tenant. Open a command prompt / shell and navigate to the ConfigEngine directory and then run the task to setup the integration (replace mytenanid, myhost, myuserid, mypassword, waspassword and portalpassword accordingly and adjust the path as needed Log in to Watson Content Hub and click the Information icon (Information icon) to locate the tenant_id and host values for your content hub.) cd /opt/ibm/websphere/wp_profile/configengine/./configengine.sh config-ch-integ -Dch.tenant.id=mytenantid -Dch.user.name=myuserid -Dch.user.pwd=mypassword -DWasPassword=wpsadmin -DPortalAdminPwd=wpsadmin -DAuthenticateUrl=" -DUrlMapping=" Look for the Build Successful message in the end: Figure 209. Configuring content hub integration After that let us restart Portal. We can do that also with a ConfigEngine command: 158

159 ./ConfigEngine.sh stop-portal-server start-portal-server -DWasPassword=wpsadmin After the restart open a browser, navigate to Portal on the SSL port (e.g. and log in to Portal as Administrator (wpsadmin/wpsadmin). Open the Edit Mode and create a new page. Figure 210. Creating a new page For the newly created page open the Page Settings dialog, and then select Edit Page Properties. Figure 211. Editing page properties 159

160 In the Page settings dialog select Advanced and then pick Content Hub Profile as Theme profile and hit Save. Figure 212. Changing theme profile 160

161 Then hit the Plus icon and select Content Hub in the Page Components section: Figure 213. Adding Page component for content hub 161

162 Drag a video and a Image component on the page: Figure 214. Adding Page component for content hub In the page you can now see the two page components being rendered click the select Image and Select video buttons to select an asset from the Watson Content Hub: Figure 215. Selecting assets 162

163 Figure 216. Selecting image Figure 217. Selecting video Leave the edit mode to see the regular rendering of the page. Figure 218. Rendering with Content Hub 163

164 7 WebSphere Application Server Admin User Interface We will use the user interface to modify WebSphere Application Server configurations. This UI is used when creating, modifying, or deleting WebSphere Application Server settings like dynamic cache settings and thread pools, for the management of a cluster or remote nodes. It cannot be used for modifying WebSphere Portal runtime data like pages and portlets. Alternative tools are WebSphere Application Server Scripting, ConfigWizard, or ConfigEngine. In our sample tasks we will explore the new features of WebSphere Application Server 8, and 9 as well as classic operations done via WebSphere Application Server. To see what is new with WebSphere Application Server 9 check: To log in to the Integrated Solutions Console (see figure below): 1. Open a browser and enter 2. Enter wpsadmin/wpsamin for User ID and Password fields. Figure 219. Log-in screen 164

165 Take a look at some of the new features in WebSphere Application Server 8.x like the new automatic directory deployment in the figure below. Select Applications->Global deployment settings to get to the new feature. It allows to specify a directory WebSphere Application Server regularly scans for ear files and automatically deploys them if they exist or removes them when deleting them. That can save quite some administration effort. Figure 220. Automatic directory deployment mode Another new interesting feature is the Extended Repository Service. It allows you take snapshots of the WebSphere configuration for certain intervals and then compare those to current 165

166 configuration or even roll back to them (note though that this does not roll back Portal changes in the database). Figure 221. Extended Repository Service 166

167 Let us have a look at the installed Applications we will see the Portlets and Portal system applications. Go to Applications -> Application types -> WebSphere enterprise applications Figure 222. Investigating installed applications The majority of configuration of Portal is stored inside Resource Environment Providers. Select Resources -> Resource Environment -> Resource Environment Providers. In the name column you can see all the different categories of properties we define. Figure 223. Property configuration 167

168 Select the WP NavigatorService -> Custom properties. Take a look at the defined settings e.g. the reload for public pages might be set to 3600 seconds. Figure 224. Review WP NavigatorService Settings 168

169 As part of the Java Batch Feature pack integration you can now schedule batch jobs from within the WebSphere Application Server. Click System Administration->Job Scheduler to get to the job scheduler. Figure 225. Job scheduler 169

170 Another new feature we want to point out is the new High Performance Extensible Logging. The feature speeds up logging and tracing. It also provides more flexible access to log and trace data: Command line access to filter and format, Administrative console GUI to filter and format local or remote logs and trace, even when the remote server is down, Programmatic access to filter, format, and merge local or remote logs and trace. Select Troubleshooting->Logs and Trace->WebSphere Portal. Figure 226. Logging and Tracing A new feature with version 9 is the ability to define default Java EE resources and then being able to simply bind to them from within an application go to Resources->Java EE default resources: Figure 227. Logging and Tracing 170

171 8 Conclusion As a WebSphere Portal administrator, you can use different tools to modify administration and/or configuration data. The decision as to which tool to use depends on the task to be performed and on the preferences of the administrator. For repeatable tasks, it's always recommend to use command line tools. 9 Resources developerworks WebSphere Portal zone: WebSphere Portal Family wiki: WebSphere Portal and Lotus Web Content Manager product documentation: WebSphere Portal and Lotus Web Content Manager 8.5 tuning guide: 10.lotus.com/ldd/portalwiki.nsf/dx/IBM_WebSphere_Portal_V_8.5_Performance_Tuning_Guide Recommended Updates for WebSphere Portal and IBM Web Content Manager: Administering IBM WebSphere Portal 8.5: A comprehensive workshop: 171

172 WebSphere Portal Administration and Performance Blog: Digital Experience Developer site: Watson Content Hub: 10 Author biographies Thomas Hurek is a Software Architect at IBM's Research Triangle Park Development Lab. He has worked on the WebSphere Portal / Digital Experience / Watson Content Hub development team since 2002, focusing on various components including security and virtual portals. In his current role he develops in the Watson Content Hub team and serves as a Consultant on the Portal Lab Based Services (SEAL) Team working with customers on implementations. You can contact Thomas at thurek@us.ibm.com. Trademarks developerworks, Domino, IBM, Lotus, Notes, Quickr, Rational, and WebSphere, the IBM logo, and ibm.com are trademarks or registered trademarks of IBM Corporation in the United States, other countries, or both. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. 172