Search results

Whether you are migrating an IBM® WebSphere® Portal or Workplace Web Content Management™ 5.1 server to version 6.1, these guides are designed to aid you through the process.

The purpose of this white paper is to provide the following for IBM® WebSphere® Portal for Multiplatforms V5.1: * Bottleneck analysis, general methodology and approach to tuning a portal environment guidelines for both capacity planning, base parameter and application tuning. * Performance tuning hints for configuring resources to scale WebSphere Portal and required backends to achieve optimal performance. * Tuning and capacity are affected by many factors, including the workload scenario and

The purpose of this white paper is to provide guidelines for base parameter and application tuning for IBM® WebSphere® Portal for Multiplatforms V5.1.0.1 on iSeries™. Remember that tuning is affected by many factors, including the workload scenario and the performance test environment. For tuning, the objective of this paper is not to recommend that you use the values we used when testing our WebSphere Portal scenarios, but to make you aware of those parameters that made the most performance impact i

This article provides portal administrators with essential performance background information so you can improve your portal's performance, including login, read-only operation, and administration performance. You learn how to prevent future portal access control performance issues by making the best use of Portal Access Control (PAC), an authorization model introduced in IBM WebSphere Portal V5. You learn about the PAC configuration artifacts, performance considerations, individual fixes you should conside

WebSphere® Portal V5.1.0.1 can make use of several additional servers to provide its functionality. In our test environment, there is a database server and directory server in addition to the portal server itself. For maximum performance, the different backend servers should reside on separate systems from the WebSphere Portal system. The primary benefit of having such a configuration is to avoid resource contention from multiple servers residing on a single server. Backend servers sharing the WebSphere P

The purpose of this white paper is to provide guidelines for both capacity planning, base parameter and application tuning for IBM WebSphere® Portal for Multiplatforms V5.1. Tuning and capacity are affected by many factors, including the workload scenario and the performance test environment. For tuning, the objective of this paper is not to recommend the use of the specific set of parameters, but to report the parameters that made the most performance impact in our testing. When tuning your individual syst

Member Services is the component of WebSphere® Portal V4 that manages information about users and groups that are registered to the portal. WebSphere Portal provides an LDAP and database that are configured during installation to store user and group information. However, many organizations have pre-existing user data stores that they want to connect to the portal rather than rebuilding the user subsystem from scratch. This document provides an overview of how Member Services manages the user profile and

Describes procedures necessary to back up and restore WebSphere Application Server, WebSphere (R) Portal databases, and relevant data files.

This document will illustrate the use of access control in managing documents for an organization with sub-teams. This example can be generalized to fit a number of levels of hierarchical roles within an organization.