WebSphere Portal administrators can find uptodate resources about installing, migrating, search configuration, tuning and performance, and more. The resource page is specialized by tasks to help you find technical resources faster. Technical resources include demonstrations, product ...

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 ...

If you are removing the IBM® Banking template for WebSphere® Portal from a Microsoft® Windows® system, you must run a batch file from a command line window. If you are removing the Banking template from a Linux® system, you must run a shell script from a terminal window.

If you are installing the IBM® Banking template for WebSphere® Portal in a clustered environment, you must specify a URL to your HTTP server so that portal users are redirected to the appropriate page at login.

Follow the steps in this task to extract the IBM® Banking template for WebSphere® Portal archives on Linux®.

Before you can remove the IBM® Banking template for WebSphere® Portal you must remove the sample data for IBM Lotus® Connections.

If you are installing the IBM® Banking template for WebSphere® Portal in a clustered environment, you must specify a the server name to your HTTP server so that portlets are not redirected away from the HTTP server.

You must manually copy the personalization library, com.ibm.accelerators.content.templates.pzn.jar, to the secondary nodes in your clustered environment.

IBM® Lotus® Web Content Management uses a Java™ Content Repository (JCR) to store data. During the installation of the IBM Banking template for WebSphere® Portal, the JCR might become corrupted if the installation is aborted. For this reason you should backup your JCR database before you install ...

Installing the IBM® Banking template for WebSphere® Portal involves specifying environment properties and running 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. The ...

After you install the IBM® Banking template for WebSphere® Portal, you must perform several configuration tasks.

The installation script for 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 ...

The installation script for the IBM® Banking template for WebSphere® Portal includes the Lotus® Connections blogs, dogears, and profiles portlets. You must import Secure Socket Layer (SSL) keys for these Lotus Connections portlets into WebSphere Portal.

The IBM® Banking template for WebSphere® Portal consists of several components that you deploy to IBM WebSphere Portal, including several portlets and IBM Lotus® Web Content Management libraries. The Banking template components complement the social and collaborative capabilities of IBM Lotus ...

During installation several database tables with sample data is added to your Derby database for IBM® WebSphere® Portal. The removal script does not remove the directory to this database from your file system. Manually deleting the sample data directory involves navigating to the Derby database ...

Running the removal script involves specifying values for two properties then running a shell script from a terminal window. The removal script removes the IBM® Banking template for WebSphere® Portal components that you added to your WebSphere Portal server during installation.

After you install the IBM® Banking template for WebSphere® Portal, you must import two sets of personalization rules. The personalization rules determine which content users can access. For example, the personalization rules prevent unauthenticated portal users from accessing resources designated ...

Preparing your environment for Profile Management involves performing several tasks to configure your user registry for use with the Profile Management portlets.

Follow the steps in this task to extract the IBM® Banking template for WebSphere® Portal archives on Microsoft® Windows®.

The IBM® Banking template for WebSphere® Portal provides a set of sample users that you can use to log in and evaluate 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 ...

The removal script does not remove the Web content libraries added to IBM® Lotus® Web Content Management during the installation. Removing the Web content libraries involves logging into IBM WebSphere® Portal and deleting each library in sequence.

Profile Management requires several attributes that do not exist in the default IBM® WebSphere® Portal user registry. To make these custom attributes available, you can either add the attributes to your LDAP directory or configure a property extension database (previously referred to as a ...

After you run the installation script for the IBM® Banking template for WebSphere® Portal, ensure the Web modules are started.

Removing the IBM® Banking template for WebSphere® Portal involves running a script that automates the removal of the Banking template components added during installation. You must also perform several manual steps to completely remove the Banking template from your system.

h2 Installing the IBM Banking template: bnk 1.0.0 h2 The installation process: bnk 1.0.0 End to end installation overview: bnk 1.0.0 Installation components: bnk 1.0.0 Sample users and data: bnk 1.0.0 Installation best practices for Lotus Connections: bnk 1.0.0 ...