Installing a development server

This scenario is intended for developers who are setting up a development environment. This installation path is intended to provide a simple configuration with all the needed components on one server. The instructions for this single-server configuration are Windows specific and uses the Apache Derby database. Security is configured as the default federated repository with a built-in file repository.

About this task

The following topology illustrates the single-server configuration that results from completing this scenario.
Illustration of a single-server configuration with WebSphere Portal and Derby database on the same server.
Web Content Manager and Derby: Although the Derby database can be sufficient for non-production installations of WebSphere® Portal, the performance of Derby with Web Content Manager is poor. A typical cause of performance issues is transaction timeouts, which can affect various features. Although you can increase these timeouts, the resulting performance is prohibitively slow. Because of these performance limitations, any Web Content Manager deployment requires that you use one of the other supported database management systems to ensure correct function. In addition to production environments, this requirement applies to proof-of-concept and development environments.