Defining local servers

 

+

Search Tips   |   Advanced Search

 

To use a local WebSphere Portal server, install WebSphere Portal Server V6.0, or later.

To test or debug a portal or portlet project within the workbench, first define a connection to the WebSphere Portal Server.

Before using the server, configure RAD Platform to use this test environment.

To create and configure a WebSphere Portal test server:

1. Switch to the Servers view by selecting

   Window | Show View | Servers

2. In the Servers view, right-click and select

   New | Server

3. Select localhost as the Host name.

4. Select WebSphere Portal Server from the server type list. Click Next.

5. On the Websphere Portal Settings page, define the following options.

   1. 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.

6. Click Next. On the Websphere Portal Settings page, specify the following settings:

   Context Root	The default setting is \wps.
   Default Home	The default setting is \portal.
   Personalized Home	The default setting is \portal.
   Install location	The default setting is the install location of the local WebSphere Portal test server selected.

7. 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.

8. Click Finish.

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.

 

Pre-Publishing

The default set of XML access delegates that are invoked during the portal publishing operation include the following:

Remove previously run portlets	Uninstall the previously published portlet project(s) which are currently not associated with the server.
Enable placeholder for missing portlets	Create placeholders for portlets not present in the workspace and not installed on the server.
Skip Portal configuration if no changes have been made in the workspace	Skip publishing the portal configuration if no changes have been made to the portal topology.

 

Post-Publishing

The default set of XML access delegates that are invoked during the portlet publishing operation include the following:

Remove previously run portlets	Uninstall the previously published portlet project(s) which are currently not associated with the server.
Create pages for portlets	Create a page on the portal server under the default label "Rational Portlets" and adds the published portlet to the page.
Use separate pages for each project	Create separat pages for multiple projects published to the server.

In addition, under the Portlet Publishing delegates, you can select the check box to 'Enable anonymous user access'. This option enables you to test portlets in the not-logged-in state.

Save the changes to your server configuration by pressing Ctrl + S

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.

You can use the WebSphere Portal 6.0 and later installation as a local test environment as long as it is installed on the same machine as your Rational tools development environment.

 

Related tasks

Associating servers with projects

---