Roadmap: Test or small production environment
A stand-alone server topology is ideal for a test or small production environment. In this roadmap, the web server, database, and user registry software are distributed to different physical servers.
Configure the web server plug-in after transfering the database.
Who should use this roadmap
Use this roadmap if we are an organization with the following requirements:
- An organization that needs an environment to test their applications and designs before they go live to the server.
- An organization that does not need a clustered environment for failover or high availability.
- An organization with limited server resources that wants to set up a department server or small website.
Topology diagram
A stand-alone server topology is versatile. It is the foundation for a portal farm, authoring environment, test or rendering environment, small department-level deployments, and more. A typical stand-alone portal server topology includes a remote database and LDAP server. For many environments, it also includes a web server to direct incoming traffic.
Prepare for the installation process
Gather information and software before you install WebSphere Portal.
Install prerequisites
Use existing prerequisite software installations. Verify the existing version is supported. If it is not, upgrade to the appropriate version. Otherwise, install a web server, database server, and user registry server. Typically the database and user registry servers are already installed and configured. However, there might be specific configuration steps required to integrate them with the portal server.
Install the Exceptional Digital Experience
Install WebSphere Portal involves preparing the operating system, installing or upgrading the installation manager, and running the installation program.
Documentation resource: Install the digital experience software
Set up a stand-alone server
Start the configuration wizard to set up your stand-alone server. First, transfer the database. The Database Transfer configuration option in the Configuration Wizard assigns users and permissions, creates databases, obtains support for database collation, and transfers the database. After transferring the database, enable the federated LDAP user registry. Log on to verify portal is working:
- http://hostname.example.com:10039/wps/porta
- Access the Configuration Wizard. Go to http://your_server:10200/ibm/wizard.
- Log in to the Configuration Wizard with the administrative ID for the configuration wizard profile, cw_profile.
The wizard user interface might not be available in all languages. If the language is not currently supported, we might see the English version. For details on the supported languages for all of the WebSphere Portal user interfaces, see Supported languages.
- Select Set Up a Stand-alone
Server > Database Transfer.
- Provide information about the environment.
- Save the configuration settings.
- Choose one of the following options:
- Click Download Files to run the steps remotely.
- Click Run All Steps to run the steps locally.
- Click Download Files to run the steps remotely.
- Log on to verify portal is working server.
- Select Set Up a Stand-alone
Server > Enable Federated Security.
If we set Use Administrator IDs stored in the LDAP user registry to yes, the WAS and portal user IDs and passwords are changed to the LDAP user ID and password. If we do not want to change both user IDs and passwords to match the LDAP user ID and password, set this value to no. After configuring the LDAP user registry, we can manually change the user IDs and passwords.
The Enable Federated Security option modifies wimconfig.xml. Make a backup copy of this file before running ConfigEngine tasks.
- WP_PROFILE/config/cells/CellName/wim/config/wimconfig.xml
- Provide information about the environment.
- Save the configuration settings.
- Choose one of the following options:
- Click Download Files to run the steps remotely.
- Click Run All Steps to run the steps locally.
- Click Download Files to run the steps remotely.
- Log on to verify portal is working server.
Configure the web server
Move the web server plug-in from the WAS to the web server.
Tune the servers in the environment
WebSphere Portal is not tuned for a production environment after installation and deployment. Your database needs tuning for improved performance. We can organize the database now or soon after you finish the configuration. We need to tune and maintain the database on a regular basis.
- Run the performance tuning tool to complete an initial tuning of the servers.
- Performance tuning guideCheck the tuning guide for more instructions.
Next steps
Depending on the choices that you made during the installation and set up, there are additional tasks to configure our environment.
The following options are available to continue configuring the environment: