IBM Banking Template for WebSphere Portal 8

Transcription

1 IBM Banking Template for WebSphere Portal 8 3 rd Edition August 2012 Copyright IBM Corporation 2010, 2012 Copyright IBM Corporation 2010,

2 About this edition Printing When you print this document some of the style elements are removed to create a better print output. Here are a few tips about printing: The document length can exceed the browser's print capability. Microsoft Internet Explorer has demonstrated the ability to print large files successfully. This document is long. Use print preview to determine the printed page length. You can highlight sections of the document and then choose to only print the selected content. Working offline You can save a local copy of this document from your browser. Each browser has different menus and menu options. Consult the browser help if you need assistance saving the document locally. Submitting feedback If you would like to provide feedback about this document, please following here: Feedback -- What would you like to comment on? Copyright IBM Corporation 2010,

3 Table of Contents INTRODUCTION TO THE IBM BANKING TEMPLATE FOR WEBSPHERE PORTAL PLANNING FOR THE IBM BANKING TEMPLATE FOR WEBSPHERE PORTAL HARDWARE AND SOFTWARE REQUIREMENTS Operating systems Software components APPLICATION TOPOLOGY SOFTWARE COMPONENTS DESCRIBED PROFILE MANAGEMENT TAG CLOUD PORTLET CONTENT TEASER PORTLET ELECTRONIC BANKING PORTLET IBM SAMETIME CHAT PORTLET AND FRAMEWORK FORMS EXPERIENCE BUILDER VIEWER PORTLET INSTALLING THE IBM BANKING TEMPLATE FOR WEBSPHERE PORTAL THE INSTALLATION PROCESS End-to-end installation overview Installing the Banking template end-to-end Relevant documentation Installation components Portlets Connections integration Web Content Manager libraries Banking Template Theme Overview Sample users and data Sample Users and Roles Sample data on Derby Sample Connections data Installation best Practices for Connections PREPARING TO INSTALL THE BANKING TEMPLATE Copying and preparing the installation files Extract the install files Specify properties in the banking.common.properties file Preparing a Linux Operating System Preparing your WebSphere Portal server Preparing your environment for profile management Specifying values for ConfigEngine properties file INSTALLING THE BANKING TEMPLATE CONFIGURING YOUR ENVIRONMENT AFTER INSTALLATION Synchronizing your Profiles database with LDAP directory changes Installing the IBM Connections sample data Installing IBM Connections portlets Configuring Forms Experience Builder...37 Copyright IBM Corporation 2010,

4 UNINSTALLING THE BANKING TEMPLATE.PAA FILE TROUBLESHOOTING NOTICES TERMS OF USE NOTICES AND TRADEMARKS...46 Copyright IBM Corporation 2010,

5 1 Introduction to the IBM Banking Template for WebSphere Portal 8 The IBM Banking Template for WebSphere Portal 8 is a set of functional components and development tools to help you design and build a portal solution tailored for the Banking industry. The Banking template brings together technical capabilities and industry thought leadership to deliver an exceptional web experience that increases customer satisfaction and helps build customer loyalty. Copyright IBM Corporation 2010,

6 2 Planning for the IBM Banking Template for WebSphere Portal You can learn about the system requirements, system architecture and software components that integrate with IBM Banking Template for WebSphere Portal. 2.1 Hardware and software requirements Review the hardware and software requirements before installing the IBM Banking template for WebSphere Portal. You should also refer to the appropriate hardware and software requirement information for each of the components that the Banking template integrates with Operating systems The Banking template has been validated on the following operating systems: Microsoft Windows Server 2003 (32 bit) Microsoft Windows product site: Microsoft Windows Server 2008 (64 bit) Microsoft Windows product site: SUSE Linux Enterprise 11 (64 bit) SUSE product site: Software components The Banking template requires the following software components: IBM WebSphere Portal Enable V Cumulative Fix 1 and APAR PM71236 IBM Tivoli Directory Server 6.1 or later IBM Web Experience Factory The Banking Template is best experienced with the following optional software components: IBM Connections IBM Forms Experience Builder 8.0 Copyright IBM Corporation 2010,

7 IBM Sametime Proxy Fix Pack 1 plus the most recent interim fix. Note: Although IBM Connections, IBM Sametime, and IBM Forms Experience Builder are optional components, syntactically correct values for host names must be provided in the banking.common.properties file for successful installation of the banking template. At runtime, the functionality provided by the optional components is not available in the banking template and its function is reduced. 2.2 Application topology The IBM Banking template for WebSphere Portal integrates with several different components. The following diagram shows the interactions between the major software components that comprise the Banking Template. The Banking template integrates with the following software components: Copyright IBM Corporation 2010,

8 IBM WebSphere Portal Provides the server technology onto which you deploy the Banking template. IBM Web Content Manager Provides the platform for authoring and publishing web content. Portlets The Banking template includes several portlets that you deploy to WebSphere Portal during installation. The portlets deliver a range of capabilities, including electronic banking services and enhanced communication and networking features. Derby During installation, the Banking template creates some sample data on the Derby database configuration with WebSphere Portal. The sample data installed on Derby lets you quickly test and evaluate the Banking template. IBM Connections Provides social computing software for the Banking template. IBM Sametime community server Provides real-time communication capabilities for the Banking template. IBM Lotus Domino Provides the underlying server technology for Sametime. IBM Sametime proxy server Provides a client-side proxy for Lotus Sametime. IBM WebSphere Application Server Provides the underlying server technology for WebSphere Portal, Connections, and the Sametime proxy server. IBM DB2 Universal Database Stores data for WebSphere Portal and IBM Connections. IBM Tivoli Directory Server or Lotus Domino Provides a Lightweight Directory Access Protocol (LDAP) directory for storing user registry data. Copyright IBM Corporation 2010,

9 3 Software Components Described The IBM Banking template for WebSphere Portal integrates with several different components. These are described in this section. 3.1 Profile Management Profile Management portlets provide user input pages that let portal users register and maintain user accounts on your portal site. For example, the registration portlet lets portal users register with your site. Little or no need for interaction with site administrators or customer service representatives is required. The Profile Management component of the IBM Banking template for WebSphere Portal consists of several models that provide a presentation layer where portal users perform registration tasks. The presentation layer interacts with a service provider layer that uses Portal User Management Architecture (PUMA) interfaces to access, create, modify, and delete data in the IBM WebSphere Portal user registry. 3.2 Tag Cloud Portlet The Tag Cloud portlet lets portal users filter blog entries by tags. It displays lists of IBM Connections community tags. The Tag Cloud portlet uses a configurable list of hardcoded tags that reside in an XML file. 3.3 Content Teaser Portlet The Content Teaser Portlet displays short text previews, or teasers of web content on the portal site. Content preview links are provided, that portal users can click to open and view content such as blog entries. 3.4 Electronic Banking Portlet The IBM Banking template for WebSphere Portal provides several customizable portlets that deliver a range of electronic banking services. The Electronic Banking portlets offer capabilities that enable portal users to hold online chat sessions with customer service representatives and access their personal banking information, such as account transactions summaries. In addition, the Electronic Banking portlets let portal users transfer funds between accounts, calculate monthly loan repayments, and more effectively retrieve information from your portal site. The service that each portlet offers includes :- Account Summary and Detail - Lets portal users view account summaries and lists of account transactions. Copyright IBM Corporation 2010,

10 Balance Transfer - Lets portal users transfer funds between authorized accounts. Bill Pay - Lets portal users pay bills for authorized accounts. Check Ordering - Lets portal users order check books for authorized accounts. Loan Calculator - Lets portal users calculate monthly repayments of specific mortgages. Stolen Credit Card - Lets portal users deactivate stolen or missing credit cards. Stop Check Payment - Lets portal users stop payment for unprocessed checks. Statements - Lets portal users view account statements. 3.5 IBM Sametime Chat Portlet and Framework The IBM Sametime Chat portlet provides real time communication capabilities for the IBM Banking template for WebSphere Portal. Portal users can hold real-time, online discussions, or chats, with Banking customer service representatives. 3.6 Forms Experience Builder Viewer Portlet The Forms Experience Builder Viewer Portlet displays the Forms Experience Viewer survey and applications. Copyright IBM Corporation 2010,

11 4 Installing the IBM Banking Template for WebSphere Portal You must specify environment properties and run a script that automates the installation of the Banking template. You must also complete several manual configuration steps before and after you install the Banking template. 4.1 The installation process The topics in this section provide information about the installation process, including an end-to-end installation overview, a list of the installation components, and best practice information to help you successfully install the IBM Banking template for WebSphere Portal End-to-end installation overview Completely installing the IBM Banking template for WebSphere Portal involves installing and configuring several servers and databases. Installation and configuration instructions are not available for each component in the Banking template. Use this overview of the installation process and links to relevant documentation to successfully install the Banking template Installing the Banking template end-to-end Installing the servers and databases for the Banking template requires several configuration tasks such as setting up single sign-on (SSO) between different servers. To minimizecomplications and resource conflicts, install and configure the servers and databases in the following order : 1. Install and configure your Lightweight Directory Access Protocol (LDAP) directory server. Use IBM Tivoli Directory or IBM Lotus Domino for example. Configuring a stand-alone LDAP user registry for WebSphere Portal 2. Optional :- Install IBM Sametime (required for full Chat functionality). 3. Optional :- Install IBM Sametime proxy server (required for full functionality). 4. Optional :- Install IBM Connections (required for full functionality). Copyright IBM Corporation 2010,

12 The Banking template uses IBM Connections blogs, so ensure that you configure the blogs so that portal users can access them. Ensure that you set a blog handle and select homepage as the blog theme. 5. Install IBM DB2 Universal Database. Installing DB2 Universal Database Configuring WebSphere Portal to use DB2 Universal Database 6. Install and configure IBM WebSphere Portal. Add additional attributes and groups to your directory server. Configure WebSphere Portal to use your directory servers. Configure WebSphere Portal to use the DB2 Universal Database server. Installing WebSphere Portal v8.0.0 Configuring WebSphere Portal with the configuration wizard 7. Set up SSO for your environment. Setup SSO between the Sametime community server and WebSphere Portal. Setup SSO between WebSphere Portal and Forms Experience Builder. Setup SSO between WebSphere Portal and IBM Connections. Understanding single sign-on (SSO) between IBM WebSphere Portal and IBM Lotus Domino Configuring single sign-on (SSO) between IBM WebSphere Portal and IBM Lotus Domino Synchronizing server times: When you configure single sign-on (SSO) between the different servers in your environment, ensure that you synchronize the time settings on each server to within five minutes of each other. If your server times are not synchronized, LTPA token timeouts can occur and cause SSO failure. 8. Install the Banking template 1. Copy and prepare the installation files. Complete configuration for : Prepare your WebSphere Portal environment. Specify values for ConfigEngine properties. Import Connections SSL keys. Optional :- Back up your JCR database. Copyright IBM Corporation 2010,

13 2. Run the installation script. 3. Perform required configuration tasks after installation: Perform configuration tasks for clustered environments, if needed. Synchronize Connections profile data with your LDAP. Install the Connections sample data. Configure the Forms Experience Builder portlet Relevant documentation See information about performing the end-to-end installation steps: Installing Tivoli Directory Server 6.1 Installing Lotus Domino Installing Lotus Sametime 8.5 Installation and Setup of IBM Lotus Sametime 8.5 From Zero to Hero in Just Two Hours Sametime 8.5.x deployment experiences Installing IBM Connections Installing the IBM Connections portlets for WebSphere Portal Populating the IBM Connections Profiles database with information from your user registry Configuring the IBM Connections blogs Changing the look of your blog Copyright IBM Corporation 2010,

14 4.1.2 Installation components The Banking template for WebSphere Portal consists of several components that deploy to portal, including several portlets and IBM Web Content Manager libraries. The Banking template components complement the social and collaborative capabilities of IBM Connections and the communication capabilities of IBM Sametime to deliver a dynamic portal site that maximizes resource efficiency and user satisfaction Portlets Portlet name Electronic Banking Portlets: Account Summary and Detail Balance Transfer Bill Pay Check Ordering Stop check Payment Stolen credit card Loan calculator Statements Tag Cloud Custom Login portlet Content Teaser Portlet Sametime Chat FEB Viewer Portlet Profile Management Portlets: Registration (Self Registration) Account activation Table 1. Portlets for the Banking template Description Suite of Electronic Banking Portlets that provides online banking services. Displays lists of Connections community tags. The Tag Cloud portlet uses a configurable list of hard-coded tags that reside in an XML file. Provides fields where users can enter log in credentials, links to enrolling and registering with the site, and a link to the Forgotten Password Portlet. Displays content preview links that portal users can click to open and view content such as blog entries. Provides the capability for portal users to hold realtime, online discussions and chats, with customer service representatives. Displays the Forms Experience Viewer survey and applications Suite of portlets that provides user registration capabilities. By default, the Banking template does not include the Account activation portlet or the Lost registration portlet. However, these portlets are available. Copyright IBM Corporation 2010,

15 Portlet name Lost registration Forgotten password Profile update Table 1. Portlets for the Banking template Description You can configure and deploy the portlets to WebSphere Portal (if required) Connections integration This release of the Banking template does not include the Connections portlets, howevere it does support them. Several pages in the template can be enhanced with Connections portlets after the templates are installed Web Content Manager libraries Table 2. Lotus Web Content Management libraries for the Banking template Libray name TB_Core Description Contains high-level templates such as news, events and dynamic image effects. TB_Shared Banking_Content Banking_ Resources This is a common library is available as part of the CTC (Content Template Catalog) deliverable on Greenhouse. Contains generic templates and components, such as simple HTML content components, simple image components, header components, simple rich text components, and so on. This is a common library is available as part of the CTC (Content Template Catalog) deliverable on Greenhouse. Contains the text, images, and other content for the Banking template. Contains personalization features such as personalization components, authoring templates and presentation templates that enable personalization for templates. Copyright IBM Corporation 2010,

16 Banking Template Theme Overview The Banking Template theme is a modified version of the standard WebSphere Portal 8 theme. A copy was created of the standard theme that was renamed. Some files were modifed to give the Banking template a unique look. For a description of how to copy and modify a theme, see: Developing themes and skins and specifically: Create a copy of the theme The modified theme resources are categorized as static or dynamic. Static resources All static resources are on the WebDav. The entry point to the file store is: The modified static resources consist of html, css, skins, layout templates and page styles. HTML The localized theme files are in the ' directory. The appropriate theme file is loaded when a page that contains the theme is accessed. The theme HTML file specifies the dynamic content that is to be loaded, such as navigation tabs and banners, and the CSS to position that content. It also serves as a wrapper for the main portlet content. CSS The main CSS file is called master.css. It is in the ' directory. It contains existing styles that have been adjusted to alter the appearance of the Banking Template theme. Some additional styles, not present in the default theme, have also been added. You can view the effect of changes to these styles by refreshing your browser's cache. Skins Skins are used to decorate portlets on the themed pages. A number of custom skins are associated with the Banking template. These are at ' A skin can be modified by editing its skin.html file. We have added separate skin.css files for each skin. These CSS files contain all the stylesheets for their associated skins. Layout templates Layout templates are used to specify how the portlets are arranged on a page. Each page can have just one layout template assigned to it. The Banking template Copyright IBM Corporation 2010,

17 layouts are at ' Just like the skins, the layout templates each have a HTML and CSS file that can be modified. Before a new layout template can be included in the theme, it must be listed in the layouts.json file at ' Page styles A number of page styles can be associated with a theme. The Banking template has some styles to demonstrate the concept. The list of styles used in the theme are specified in the styles.json file in the ' directory, and the css for the styles are stored within subdirectories of the 'themes/banking/css' directory. The CSS styles defined in the page style take priority over those defined in the master.css file. Dynamic resources The dynamic resources are JSP files that are required to generate portal-specific links on themed pages. The JSP files for the Banking template have been copied from the standard WebSphere Portal 8 theme and modified. They are on the server at [wp_profile name]/installedapps/[cell name]/bankingtheme.ear/banking.theme.war/themes/html/dynamicspots. The JSPs are executed indirectly by the theme HTML file. The localized theme file (such as theme_en.html) references a dynamic content spot mapping, that references the relevant JSP, with input parameters if necessary. The Banking Template theme reuses a number of dynamic content spots mappings from the default theme. The JSP files reference the CSS styles that are defined in the master.css file. The list of dynamic content spot mappings for all themes can be viewed and edited from the Integrated Solutions Console (ISC). Log in to the ISC, and go to: Resources -> Resource Environment -> Resource Environment Providers. From the table on the main pane, select WP DynamicContentSpotMappings. Then, under the section Additional Properties, Then click Custom properties. The mappings for the standard theme have names that begin with 80theme_ and the mappings created with the Banking Template installation have names that begin with banking_. The name of the mapping is referenced in the theme file and the value of the mapping should contain the JSP path and name relative to the theme's context root. Here is an example of how the banking_footer dynamic content spot mapping is referenced to execute the bankingfooter.jsp file in the theme_en.html file. <a rel="dynamic-content" href="dyn-cs:id:banking_footer"></a> Copyright IBM Corporation 2010,

18 4.1.3 Sample users and data The Banking template for WebSphere Portal provides a set of sample users that you can use to log in and evaluate the Banking template. The sample users and data can be automatically added to your user registry when you install the Banking template. The Banking template also requires sample data for testing and demonstration purposes. This topic lists all the sample users and describes the role that each user is assigned and describes the sample data Sample Users and Roles The Banking template provides several sample user IDs and groups that you can use for testing and demonstration purposes. These sample users are automatically added to your directory server when you install the Banking template. The following table lists and describes the sample users: User name Peter Brown Daphne McKenna Bot User Table 3. Sample users roles Role Bank customer that is the primary user for demonstration and testing purposes. Use the credentials for Peter Brown to log in to the Banking template for evaluation purposes. Bank advisor for Peter Brown When you install the Banking template you can specify this user name as a customer service representative available to chat with portal users. See Copying and preparing the installation files in this document for more information. Sametime user that is required by the Sametime Chat framework. This user is required during deployment to access Sametime. After adding these three users to the directory server, the deployment also creates a csr group and adds Daphne to that group. The group created should be edited to match the customers environment. These entries should match those specified in the common properties file edited before deployment. See Section Specify Properties in banking.common.properties. For security reasons, this document does not provide a list of the sample user IDs and passwords. To access the XML file included in the installation archive, complete the following steps: Copyright IBM Corporation 2010,

19 1. Navigate to the directory in the Banking template installation archive: \runtime\banking.paa\banking\components\banking.common\config\templates 2. Locate and open the createbankingusers.xml file with any text editor Sample data on Derby When you install the Banking template, some sample data is automatically created on a Derby database. This sample data provides customer identity information for the sample users, including personal information, such as birth dates, and account information, such as account numbers. The sample data resides in an Structured Query Language (SQL) file included in the installation archive. 1. Navigate to the directory in the Banking template installation archive: \runtime\banking.paa\banking\components\banking.common\config\templates 2. Locate and open the derby_initialize.sql file with any text editor Sample Connections data The sample data for IBM Connections includes bookmarks, blogs, and blog entries. This data populates Connections with sample content for the Banking template. The sample data resides in an XML file in the installation archive. To open this XML file and access the sample data, do the following: 1. Navigate to the following directory in the Banking template installation archive: \runtime\banking.paa\connections 2. Locate and open the LCData_Banking.xml file with any text editor. The automatic installation for the Banking template does not include the sample data for Connections. You must install this sample data when you set up and configure Connections. For instructions about installing this sample data, see Section Installing the Lotus Connections sample data. Copyright IBM Corporation 2010,

20 4.1.4 Installation best Practices for Connections This information was acquired during the development and testing of the Banking template. User requirements and system configurations are unique and vary from one environment to another. This topic does not include information about every step in the installation process. 1. Rename the front page blog when you configure the Connections blogs feature. After you install IBM Connections, you must configure the blogs application so that portal users can create blogs. You specify a name for the blog you select as the home page. If you select the front page blog, all blog entries are displayed on the home page. For this reason, you should rename the front page blog to a name such as All blogs to reflect the fact that this blog displays all blog entries. See the IBM Connections Information Center for instructions about Configuring the blogs feature: 2. Synchronize your Profiles database with the directory service after you install Connections After you install the Banking template, synchronize your Profiles database with the directory service to create Connections profiles for the sample users that the installation script adds to your user registry. You cannot access data on the Connections blogs portlet with the sample users until you synchronize the Profiles database with your directory service. If you are installing the Banking template for a production environment, you should regularly synchronize your Profiles database with your directory service. See the IBM Connections Information Center for instructions about synchronizing your Profiles database with your directory service. Synchronizing user profile photos: User profile photos in IBM Connections do not reside on the Profiles database. For this reason, IBM Tivoli Directory Integrator does not include user profile photos when you synchronize the Profile database with your directory service. You must synchronize user profile photos manually. See the Connections forum or cotact Connections Support for assistance. Access the IBM Connections forum at: 3. For security configuration guidelines, refer to this documentation on IBM Connections Security : Copyright IBM Corporation 2010,

21 4.2 Preparing to install the Banking template You must complete these tasks before you install the IBM Banking template for WebSphere Portal Copying and preparing the installation files After you copy and extract the files, you must specify values for several properties required to run the installation script for the Banking template Extract the install files To copy and prepare the installation files, complete the following steps: 1. Create a temporary folder in your system directory where you can copy the files for the Banking template. For example, - Microsoft Windows: C:\temp\banking - Linux: /root/temp/banking 2. Copy the.zip file for the Banking template into the directory and extract it. The following directories become available on your file system: - Microsoft Windows: C:\temp\banking\design_time C:\temp\banking\runtime - Linux: /root/temp/banking/design_time /root/temp/banking/runtime The banking.paa file is located in the runtime directory. You need to extract a properties file called banking.common.properties. The.paa file is an archived file that contains the installation components. Use your archiving tool to extract the properties file. Rename the file extension to.zip if you encounter difficulty extracting the file. The properties file is located inside the.paa file in the this location (on Windows): \banking\components\banking.common\ Note: You can also edit this properties file after the Solution Installer install-paa step but before the Solution installer deploy-paa step. Copyright IBM Corporation 2010,

22 Specify properties in the banking.common.properties file The properties included in this file are used during the deployment of the Banking template. The property values that you specify are used during the deployment to access the correct servers, using correct user names and passwords, and so on. The following properties need to be assigned appropriate values for your system. General Properties ldaptype During installation, several sample users are added to your directory service. Specify whether to add these users. Enter one of the following values: 0 if you do not plan to install sample users. 1 if you want users added your LDAP banking.wcm.service.hostname= WpsHostName banking.wcm.service.port=10039 Database properties dbport=1527 dbname= WasUserHome /PortalServer/derby/BankingDatabase dbhostname= dbhostname dbtype=derby dbprovidername=derby JDBC Provider dbdrivertype=connection pool data source dbusername=wpsadmin dbpassword=passw0rd99 dbauthdataalias=bankauth dbdrivername=org.apache.derby.jdbc.embeddeddriver dbdriverpath= WasHome /derby/lib dbclasspath= dbdriverpath /derby.jar; dbdriverpath/derbyclient.jar;dbdriverpath/derbynet.jar; dbdriverpath /derbytools.jar dburl=jdbc:dbtype:dbname;create=true dbjndiname=jdbc/bankingdatasource dstemplatename=derby JDBC Driver DataSource jptemplatename=derby JDBC Provider dsdbdrivertype=4 datasourcename=bankingdatasource db.maxconnections=30 db.connectiontimeout=180 db.reaptime=120 db.agedtimeout=1800 Copyright IBM Corporation 2010,

23 Connections properties dogearsurl Specify the dogears (Bookmarks) URL for IBM Connections. For example, profilesurl Specify the profiles URL for Connections. For example, blogsurl Specify the blogs URL for Connections. For example, blogshomepagehandle Specify the handle that you assign to the home page blog for Connections. For example, bankingblog. Ajax Proxy configuration for Connections The Ajax Proxy is a component shipped with WebSphere Portal that enables both clientside scripts and server-side code to access external services via the server, and centrally administers these outbound http connections. connectionsbaseurl The base URL to the Connections server. For example, sockettimeoutvalue The default value is maxconnectionsperhost The default value is 50. maxtotalconnections The default value is 500. Forms Experience Builder Properties banking.feb.server.hostname=fully Qualified Domain Name (FQDN) of the Forms Experience Builder host banking.sametime.proxy.port=port number of FEB Host e.g Sametime properties cc.sametime.proxy.enabled=true cc.sametime.proxy.scheme=http cc.sametime.proxy.host=fqdn of Sametime proxy host Copyright IBM Corporation 2010,

24 cc.sametime.proxy.port=port number of Sametime proxy host, e.g cc.sametime.proxy.version=8.5.2 cc.sametime.connect.client=false banking.sametime.community.hostname This is used to configure the Banking template with the Sametime server. The value is the base URL of the Sametime server. banking.sametime.proxy.hostname Used to configure the Banking template with the Sametime server. The value is the base URL of the Sametime proxy server, and can be same as the Sametime server hostname. banking.sametime.proxy.port Used to configure the Banking template with the Sametime server. The value is the port used for the Sametime proxy server (for example, 9080). banking.sametime.bot.username Used to configure the Banking template with the Sametime server. The value is a Sametime user name that is used to authenticate and connect with the Sametime proxy server. banking.sametime.bot.password Used to configure the Banking template with the Sametime server. The value is the password of the previous user. banking.sametime.bot.csr.group Used to configure the Banking template with the Sametime server. Value is the distinguished name (DN) of an LDAP group, for example, cn=csr,cn=groups,ou=test,o=banking,o=acme>. This group is created during deployment by a script in the paa file (\banking\components\banking.common\config\templates\createbankingusers.xml). The same script also creates these users, Peter Brown (a bank customer) and Daphne McKenna (a bank advisor), and the user required by the Sametime chat framework (value of banking.sametime.bot.username). It also creates a csr group (value of banking.sametime.bot.csr.group) and adds Daphne to that group. The DN of the group created should be edited to match your environment. banking.sametime.defaultpartner.username Used to configure the Banking template with the Sametime server. Value is the id of a Sametime user who will act as the default chat partner for unauthenticated Banking template users. Specify a customer service representative user name. The user name that you specify is displayed in the Sametime chat portlet as a customer service representative available to chat with portal users. For example, dmckenna. Restriction: The user name that you specify must be present in your user registry. Copyright IBM Corporation 2010,

25 Sample users: The Banking template provides sample users you can use for testing or demonstration purposes. Specify Daphne McKenna if you plan to use sample users. For more information about sample users, see the Sample Users and Data topic in this document. Save and close the banking.common.properties file. You can add this update file into the banking.paa file using your archive tool Preparing a Linux Operating System The default setting for the maximum number of open files is You can view the setting on your machine by entering ulimit -a in the console, and reading the value for open files (-n). As part of the Web Content Manager (WCM) library import during the install action, this limit can be exceeded. Increase this limit to by entering ulimit -n After the Banking template has been deployed you can revert this limit back to its original value Preparing your WebSphere Portal server Before installing the IBM Banking template for WebSphere Portal, you must complete some tasks to prepare your WebSphere Portal server environment Preparing your environment for profile management Configure your user registry for use with the profile management portlets. 1. Adding attributes to the user registry Profile management requires several attributes that do not exist in the default WebSphere Portal user registry. To make these custom attributes available, you can add the attributes to your directory service. You can also specify your own custom attributes, if you plan to use other attributes in profile management. The following attributes must be added to the inetorgperson class in the target directory server: accountuseruniqueid securityanswer2 securityanswer1 customerstatus Copyright IBM Corporation 2010,

26 activationstatus securityquestion2 securityquestion1 myagent activationcode All are of String type. The Virtual Member Manager (VMM) for WebSphere Portal must now also be updated. See Windows stand-alone: Adding attributes. You are now ready to configure the attribute mappings. 2. attribute mapping See instructions at Mapping the attribute to LDAP 3. Optional :- Configuring the attribute mappings Profile management portlets provide user input pages that let portal users register and maintain user accounts on your portal site. For example, the registration portlet lets portal users register with your site. During the registration process, the portlet presents several input pages that contain fields where portal users enter their information, such as a user ID, password, address, and so on. You must associate user registry attributes to each of the specific field types in the profile management portlets. For example, a user registry attribute such as uid can map to the field where portal users specify their user ID. Associating registry attributes to the specific field types involves mapping registry attributes to several attribute keys in a properties file. The Profile Management portlets also use several registry attributes to keep track account activation status for portal users. In this case, portal users do not need to specify information in fields. However, you must associate registry attributes with attribute keys to so that the profile management portlets can keep track of account activation. To configure the attribute mappings, do the following steps: 1. Extract the archive to make the attributemapping.properties file available on your file system. a. Extract the banking.paa to a folder, for example, Microsoft Windows: C:\temp\banking\runtime\banking Linux: /root/temp/banking/runtime/banking b. Locate and open the following folder: \components\banking.common\installableapps\portlets Copyright IBM Corporation 2010,

27 c. Locate and extract the toolbox.banking.war to a folder named toolbox.banking. d. Delete toolbox.banking.war 2. Navigate to the following directory: Microsoft Windows: \toolbox.banking\accelerators\config\profile\common Linux: /toolbox.banking/accelerators/config/profile/common 3. Locate and open the attributemapping.properties file with any text editor. Important: You must map user registry attributes to the following keys. The format of each entry in the properties file is as follows key=attribute name. Specify the user registry attributes that conform with your environment. The attributes that you specify must exist in your user registry. If you specify an attribute that does not exist in your user registry, the values that portal users enter during registration are not saved. 4. Specify the attributes that you want to associate with the following keys: activationcode Maps to activationcode by default. An attribute must map to this key if you use activation for Profile Management. ActivationStatus Maps to activationstatus by default. An attribute must map to this key. Profile Management portlets use this attribute to keep track of account activation. accountnumber Left blank by default. Note: If you leave a blank value for an attribute key, no value is set even if the attribute key is specified for a user input field in the page definitions XML. accountdob Left blank by default. Copyright IBM Corporation 2010,

28 Note: If you leave a blank value for an attribute key, no value is set even if the attribute key is specified for a user input field in the page definitions XML. accountpin Left blank by default. Note: If you leave a blank value for an attribute key, no value is set even if the attribute key is specified for a user input field in the page definitions XML. accountuseruniqueid Maps to accountuseruniqueid by default. Important: If you change the attribute mapping for this key, you must specify the same mapping in a separate properties file for the electronic banking portlets. To update the attribute mapping for the electronic banking portlets, do the following steps: 1. Navigate to the following directory: \toolbox.banking\accelerators\config\userattribute\. 2. Locate and open the attributemapping.properties file. 3. Update the attribute mapping for accountuseruniqueid then save and close attributemapping.properties file. accountfirstname Maps to givenname by default. accountuserid Maps to uid by default. accountlastname Maps to sn by default. account Maps to mail by default. accountpassword Maps to password by default. account confirm Maps to mail by default. securityquestion1 Maps to securityquestion1 by default. Copyright IBM Corporation 2010,

29 securityanswer1 Maps to securityanswer1 by default. securityquestion2 Maps to securityquestion2 by default. securityanswer2 Maps to securityanswer2 by default. extraattributename Maps to cn by default. See Automatically creating attributes in this document for more information. formatofextraattributeoncreate Set to {givenname} {sn} by default. See Automatically creating attributes in this document for more information. formatofextraattributeonupdate Null value by default. See Automatically creating attributes in this document for more information. groupname Maps to cn by default. See Automatically creating attributes in this document for more information. 5. Save and close the attributemapping.properties file. 6. Repackage the archives for installation, regenerating the original banking.paa file now with the one or both attributemapping.properties files updated. 4. Optional :Automatically creating attributes Some user registries, such as LDAP directories, require a specific user attributes, such as the common name (cn) attribute. You can configure the registration portlet and the profile update portlets for profile management to automatically create attributes when new users are created in your registry, or an existing user is updated. Profile Management includes a properties file named attributemapping.properties. In this properties file there is a parameter you can set to automatically create user attributes, depending on the requirements of your user registry and the portlets for the IBM Banking template for WebSphere Portal. The Connections portlets or some user registries might require you to automatically create the user ID (uid) attribute. Other user registries might require you to automatically create the common name (cn) attribute. Copyright IBM Corporation 2010,

30 The parameter you set to automatically create user attributes is extraattributename. You can specify any valid user attribute; however, the most common attributes to create are the common name (cn) and user ID (uid) attributes. Generally, if you map the accountuserid parameter to the user ID (uid) attribute, you should set extraattributename to create the common name (cn) attribute. If you map the accountuserid parameter to the common name (cn) attribute, you should set extraattributename to create the user ID (uid) attribute. The following steps provide an example of automatically setting the common name attribute: 1. Extract the archive to make attributemapping.properties available on your file system. a. Extract banking.paa to a folder, for example, Microsoft Windows: C:\temp\banking\runtime\banking Linux: /root/temp/banking/runtime/banking b. Locate and open the following folder: \components\banking.common\installableapps\portlets c. Locate and extract the toolbox.banking.war file to a folder named toolbox.banking. d. Delete the toolbox.banking.war file. 2. Navigate to the following directory: Microsoft Windows: \toolbox.banking\accelerators\config\profile\common Linux: /toolbox.banking/accelerators/config/profile/common 3. Locate and open attributemapping.properties with any text editor. 4. Specify values for extraattributename, formatofextraattributeoncreate, and formatofextraattributeonupdate. extraattributename Maps to cn by default. If you use IBM Lotus Domino for your LDAP directory, set the value to uid. This key creates the attribute that you specify. The registration and profile update portlets automatically create the attribute that you specify if you map an attribute to this key and specify the key in the page definitions. Restriction: If you configure the page definitions XML for a Profile Management portlet to set a specific attribute and you configure extraattributename to set the Copyright IBM Corporation 2010,

31 same attribute, the page definitions XML takes precedence and extraattributename does not take effect. For example, you define a field in the page definitions XML named fullname. You then map fullname to the common name (cn) attribute. You then set extraattributename to cn. In this case, extraattributename does not automatically create the cn attribute because the fullname field is mapped to cn. formatofextraattributeoncreate Set to {givenname} {sn} by default. This key specifies the format for extraattributename for the registration portlet. For example, the default setting of {givenname} {sn} combines the values of the givenname attribute and the sn attribute to populate a value for the cn, or common name, attribute. formatofextraattributeonupdate Null value by default. This key specifies the format for extraattributename for the profile update portlet. Specify values as follows to enable automatic creation of extra attributes: Empty values Empty, or null, values disable automatic creation of extra attributes. Literal strings Specify an value that consists of zero or more literal strings. Attribute names between brackets {} Specify an existing attribute name between brackets {}. Notes: All characters that occur outside brackets {} are treated as literal strings. You can also specify more than one attribute name as the value, or a combination of literal strings and attribute names. For example, formatofextraattributeoncreate={givenname} {sn} formatofextraattributeoncreate=sir {givenname} of Locksley formatofextraattributeoncreate={givenname}{sn}_{sn} {givenname] 5. Specify a value for the following property: groupname=. The value you specify sets the attribute of the group name. For example, groupname=cn sets the common name attribute for the group name. 6. Save and close attributemapping.properties file. 7. Repackage the archives for installation. Copyright IBM Corporation 2010,

32 Specifying values for ConfigEngine properties file IBM Solution Installer, the installer used to install the IBM Banking template for WebSphere Portal uses the WebSphere Portal ConfigEngine to install and deploy different components on your portal site. Before you run the installation script, ensure that the correct values are specified for the required ConfigEngine properties. To specify values for the ConfigEngine properties, do the following: 1. Navigate to the following directory: wp_profile_root\configengine\properties. 2. Locate and open wkplc.properties with any text editor. 3. Ensure the following properties conform to your environment settings: WasUserid Specify an administrator user ID for WebSphere Application Server. WasPassword Specify the password for the WebSphere Application Server administrator user ID. PortalAdminId Specify an administrator user ID for WebSphere Portal. PortalAdminPwd Specify the password for the WebSphere Portal administrator user ID. WasUserHome Specify the directory where WebSphere Application Server user data is created. For example, C:/IBM/WebSphere/wp_profile. WpsHostName Specify the name of the WebSphere Portal host or the name of the Web server. Specifying the server name: You must specify the full server name as the value for WpsHostName. For example, my.server.name.com. Do not specify localhost as the value for WpsHostName. 4. Save and close wkplc.properties file. Copyright IBM Corporation 2010,

33 4.3 Installing the Banking template Installation uses the Solution Installer which exists in WebSphere Portal 8 by default. This tool takes the banking.paa file and installs and deploys it to your WebSphere Portal server. There are two stages to deploying the.paa file, Installation and deployment. Installation extracts the.paa file and creates the directory structure on the server. Installation registers the component, extracts the.paa file and creates the directory structure on the server. Deployment installs the application, including copying shared Jar files, installing War files, Ears files, executing database scripts and so on. If you are installing on a Microsoft Windows system, you must run the following steps from a command line window. If you are installing on a Linux system, you must run the shell scripts from a terminal window. 1. Extract the Banking_ zip file to a directory on the server where you want to install the template. For example C:\Banking folder. 2. Issue the following command to install the.paa file Windows: ConfigEngine.bat install-paa -DPAALocation=path to paa file Unix or Linux: ConfigEngine.sh install-paa -DPAALocation=path to paa file This step creates the directory structure for the application under the WebSphere/wp_profile/paa directory. Example on Windows: ConfigEngine.bat install-paa -DPAALocation=c:\banking\Banking_ \runtime\banking.paa > install-paa.log Example on Linux:./ConfigEngine.sh deploy-paa -DPAALocation=/opt/banking/Banking_ /runtime/banking.paa > installpaa.log where install-paa.log is to collect the output of the above ConfigEngine command. Copyright IBM Corporation 2010,

34 If you followed the steps in the section Specify Properties in banking.common.properties but did not update the banking.paa file with the updated banking.common.properties file, then you should now copy the updated file to you portal Server, overwriting this file : \WebSphere\paa\banking\components\banking.common\banking.common.properties 3. Disable indexing. See the following instructions on Disabling JCR text search indexing. 4. Issue the following command to deploy the paa file: Windows: ConfigEngine.bat deploy-paa -DappName=application name Unix or Linux: ConfigEngine.sh deploy-paa -DappName=application name This step deploys the application, create databases, datasources, copy shared Jar files and so on. Example on Windows: ConfigEngine.bat deploy-paa -DappName=banking > deploy-paa.log Example on Linux:./ConfigEngine.sh deploy-paa -DappName=banking> deploy-paa.log where deploy-paa.log is to collect the output of the above ConfigEngine command. Note that this last step can take up to 1 hour to complete. 4.4 Configuring your environment after installation After you install the IBM Banking template for WebSphere Portal, you must perform several configuration tasks. Some of the files you will need are included in the banking.paa file. However, Solution Installer's 'install' phase extracted the contents of the paa file to the \WebSphere\paa folder so any files you need should be accessible there. Copyright IBM Corporation 2010,

35 4.4.1 Synchronizing your Profiles database with LDAP directory changes The installation script for the IBM Banking template for WebSphere Portal includes a set of sample users that are added to your user registry. After completing the installation, synchronize your Profile database with your LDAP directory so that your user registry and the Profiles database contain the same information. The information in the Profiles database should reflect the information that is present in your LDAP directory. Synchronizing LDAP directory changes with the Profiles database involves running a batch file that prompts IBM Tivoli Directory Integrator to perform the synchronization process. Refer to the topic Synchronizing LDAP directory changes with Profiles. Synchronizing user profile photos: User profile photos in IBM Connections do not reside on the Profiles database. For this reason, Tivoli Directory Integrator does not include user profile photos when you synchronize the Profile database with your LDAP directory. You must synchronize user profile photos manually. Refer to the Connections forum or contact your Connections technical support representative for assistance. Access the IBM Connections forum at: Installing the IBM Connections sample data Sample data for the IBM Connections blogs, blog entries and bookmarks can be installed using the IBM Connections data loader command. It populates the Banking template with example content that can be used for demonstration and testing purposes. Before you run the data loader command, you must: 1. Install the Banking template. 2. Synchronize directory server changes with the Profiles database. 3. Define a home page blog and set the blog theme to homepage. The sample data for the Connections blogs, blog entries, and bookmarks is defined in LCData_Banking.xml file. For additional information about the data loader command, see the LCDData_Readme.html. Both files are are in the runtime/connections directory. To install the Connections sample data, do the following steps: 1. From a command prompt, navigate to the runtime/connections directory. Copyright IBM Corporation 2010,

36 2. If you are reinstalling the Banking template, remove existing sample data from the Connections server by issuing the following command: java -jar LCDataLoaderRunnable.jar -selfcert -uninstall -handle=bankingblog -server= -file=<data_file_name> where server_name and port_number refer to the name and port number of your Connections server, and data_file_name refers to the XML file that contains the sample data that is currently installed on the server, for example, LCData_Banking.xml. 3. Installing the Sample Data If you do not remove the old data before reinstalling, the sample data is duplicated on your Connections server. Ensure that there are no spaces before or after any occurrences of the equal sign (=) when running these commands. Issue the following command to install the sample data for blogs, blog entries, and bookmarks. java -jar LCDataLoaderRunnable.jar -selfcert -server= -file=.\lcdata_banking.xml where the server_name and port_number correspond to the Connections server name and port number Installing IBM Connections portlets Complete the steps for your environment as documented at IBM Connections Portlets for WebSphere Portal Run the XML configuration script, deployconnectionsportlets.xml to create the Connections portlets on the banking community pages. Copyright IBM Corporation 2010,

37 4.4.4 Configuring Forms Experience Builder The install action of the Banking template also includes the installation of the Forms Experience Builder viewer portlet, the configuration of the Ajax Proxy to allow Forms communication, and the configure mode settings of the portlet itself. Install the Form application The form binary file must be manually deployed and launched on the Forms server. 1. Navigate to 2. Select Import on this page and browse to the form application which is at PORTAL_ROOT\wp_profile\paa\banking\components\banking.feb \OFNFeedbackForm.nitro_s Edit portlet shared setting The Shared settings of the portlet must be manually set to allow the form to be rendered. Copyright IBM Corporation 2010,

38 To get to the shared settings : 1. Log in to the banking portal as an administrative user. 2. Go to Manage Pages section of the Administration page. 3. Click the edit page layout button as highlighted in the following image. This needs to be done for each of the two form hosting pages as shown in the image. Copyright IBM Corporation 2010,

39 4. On the Edit Page Layout page, select Edit shared settings as shown in this following image below. 5. Follow the steps at - Selecting an application using Edit Shared Setting Note: The Application URL is form b1-10f3cd3f3e8f/launch/index.html?form=F_FormX where X is 1 for the feedback form and 2 for the form. The browse applications button only allows for the selection of the first case (X set to one) and you need to change this to 2 in the entry field on the page. See the Troubleshooting section at the end of this document if you have an issue with the browse application button. 6. Configure .see the steps here to configure for the form: Sending an after a user submits a form Copyright IBM Corporation 2010,