Defining local servers for testing portals

You can define a server connection for importing, exporting, and deploying portals. You can also test or debug a portal project within the workbench, for that you must first define connection to the WebSphere® Portal Server.

Before you begin

Before using the server, you must install WebSphere Portal Server and configure Rational® Software Delivery Platform to use this test environment.

Procedure

To create and configure a WebSphere Portal test server:

Switch to the Servers view by selecting Window > Show View > Servers
In the Servers view, right-click and select New > Server.
Select localhost as the Host name.
Select WebSphere Portal Server from the server type list. Click Next.
On the Websphere Portal Settings page, define the following options.
1. The Automatically determine connection settings is selected by default. To set the RMI Port or the SOAP Port setting, select Manually provide connection settings
2. Set the RMI Port if you want to use this connection type.
3. Set the SOAP Port if you want to use this connection type.
4. Run server with resources within the workspace checkbox is selected by default, clear the checkbox if you do not want to use this option.
5. Security is enabled on this server checkbox is selected by default, specify the administrator ID and password for the portal server.
Click Next, On the Websphere Portal Settings page, specify the following settings:
1. Context Root. The default setting is /wps.
2. Default Home. The default setting is /portal.
3. Personalized Home. The default setting is /myportal.
4. Install location. The default setting is the install location of the local WebSphere Portal test server selected.
Click Next. Enter the Portal Server Settings, that is the location of the application folder (<portal-install location>\PortalServer\shared\app) that you defined when you installed the test environment. Click Next.
Click Finish.

What to do next

Additional options for local test environments can be viewed and changed by double-clicking on the server in the Servers view. You can change any of the settings that were defined previously. In addition, the Portal tab has additional settings, which you might want to customize.

Settings for Portal Publishing: The default set of XML access delegates that are invoked during the portal publishing operation include the following:
- Pre-Publishing: This uninstalls the previously published portlet project(s) which are currently not associated with the server. Remove previously run portlets.
- Publishing:
  1. This creates placeholders for portlets not present in the workspace and not installed on the server. Enable placeholder for missing portlets.
  2. This skips publishing the portal configuration if no changes have been made to the portal topology. Skip Portal configuration if no changes have been made in the workspace.
  Note: An EAR project named wps is created when you run a portal in the test environment (Run on Server or Debug on Server). If you plan to test or debug your portal project locally, do not modify the wps project once it is created. When creating a project, do not name it wps.
- Post-Publishing: These options enable you to run specific XML access scripts after publishing has completed.
Settings for Portlet publishing: The default set of XML access delegates that are invoked during the portlet publishing operation include the following:
- Pre-publishing: This uninstalls the previously published portlet project(s) which are currently not associated with the server. Remove previously run portlets.
- Publishing:
  1. Creates a page on the portal server under the default label 'Rational Portlets' and adds the published portlet to the page. Create pages for portlets.
  2. Creates separate pages for multiple projects published to the server. Use separate pages for each project.
  3. tests portlets in the not-logged-in state, select Enable anonymous user access check box.
- Post-publishing: These options enable you to run specific XML access scripts after publishing has completed.

Save the changes to your server configuration.

Feedback