Configuring

Image for this section The topics in this section address configuration tasks that are typically performed once and have a global effect. There are other configuration changes that are made more frequently or do not have a global affect; these configuration tasks are addressed in the Administering section. Configuration tasks related to setting up your environment are addressed in the installation scenarios found in the Installing section.

If you have not transferred your database yet, go to the Installing section, select the appropriate operating system, and then choose the appropriate deployment scenario. Then select the setting up or configuring database topic.

If you have installed WebSphere® Portal for IBM® z/OS®, you use the Customization Dialog that provides the series of Interactive System Productivity Facility (ISPF) panels to configure your portal. However, some of the portal configuration tasks do not have ISPF panels. For tasks that do not have ISPF panels, you need to follow the general instructions provided for two alternatives to ISPF panels:
  • Create a Job Control Language (JCL) script to run the configuration task
  • Open a UNIX System Services (USS) command prompt or use a Telnet client to connect to the portal server and run the configuration task
If you have not already done so, you should review the WebSphere Portal and Web Content Manager Performance Tuning Guide to tune your stand-alone or cluster environment. Even if you have a cluster environment, you should review the Base Portal Tuning scenarios and the Tuning a cluster environment chapter. In addition the tuning guide provides information about caches for WebSphere Portal. Until the tuning guide for release 8.0 is available, refer to the 7.0 tuning guide.
Note:

You can run ConfigEngine tasks from a read-only ConfigEngine directory that allows you to manage multiple profiles from one location or you can run ConfigEngine tasks from the wp_profile_root directory that you have used in previous releases. For example, to use the ConfigEngine read-only directory, run the ConfigEngine task in the ConfigEngine folder that is on the same level in the directory structure as the default wp_profile directory. You can substitute the path to the ConfigEngine read-only directory in any ConfigEngine task in the product documentation.