FAQ for WebSphere Portal 5.1 Test Environment for Rational Application Developer 6.0

This tech note summarizes the FAQ for using the Portal 5.1 test environment for Rational Application Developer 6.0.

Last Update: 2005/10/24

Index:

         Common for All RAD 6.0 Releases

         RAD 6.0 and 6.0.0.1 Unique

         RAD 6.0.1 Unique

         General WebSphere Portal 5.1 Test Environment Issues

Common for All RAD 6.0 Releases

Q.

What is the latest fix pack for Portal 5.1 test environment?

A.

The latest fix pack level is 5.1.0.2 as of October 13th, 2005.

Q.

How can I upgrade my Portal test environment to the latest fix pack?

A.

You can apply the latest fix pack using Rational Product Update (RPU). Select the fix pack from the "Optional Features" tab of RPU. This will apply the WebSphere Portal update to the first WebSphere Portal 5.1 test environment found on your machine.

Q.

Which Portal CDs do I need for installing Portal 5.1 and Portal 5.1.0.1?

A.

         For Windows: cdSetup, cd1-1, cd1-2, cd1-15, cd2, cd3

         For Linux: cdSetup, cd1-3, cd1-4, cd1-16, cd2, cd3

For detailed installation steps, please refer to "Chapter 11. Installing the WebSphere Portal Test Environment version 5.1" in RAD 6.0 installation guide ("install.html" on RAD 6.0 Disk 1)

Q.

Are there Portal 5.1.0.1 CD images that I can use to install Portal 5.1.0.1 test environment directly?

A.

Yes, Portal 5.1.0.1 CD images are available on IBM Passport Advantage site.

Q.

To avoid an installation failure , what should I check in my development environment before installing the Portal test environment?

A.

Check the following prerequisites:

         Physical memory: 1.5GB or more (2.0GB is recommended)

         Disk space: 3GB

         Disable any firewall products

         Ensure port 8880 and 8881 are free

         Ensure port 9080 and 9081 are free

         On Linux the swap partition size must be at least 3.5 GB.

Q.

Can I disable the prompt to locate a new CD during the installation?

A.

If you extract files from Portal CDs into directories which have the same name as the CDs with the same parent directory you will not be prompted to specify a location of a next CD.
Create the following folders and extract files from the CDs.

         For Windows: cdSetup, cd1-1, cd1-2, cd1-15, cd2, cd3

         For Linux: cdSetup, cd1-3, cd1-4, cd1-16, cd2, cd3

Q.

How do I start the install for the Portal 5.1 test environment? There is no menu option for Portal 5.1 test environment in RAD launch pad.

A.

Unlike the Portal 5.0.2.2 test environment, the Portal 5.1 test environment installation is integrated into the Portal 5.1 installer.
To install the Portal 5.1 test environment from Portal 5.1 CDs, use the following command:

Install.bat -W dependency.useValidation="false"

and then select the Test Environment installation option in the installer options.

Q.

Can I install the Portal 5.1 test environment silently without displaying any graphical interface panels?

A.

Yes you can. The Portal 5.1 installer provides the option "-silent" for the silent installation.

If you use this option, you must set all required options such as an installation location, or a user id and password for Portal, in a response file. You need to specify "toolkit" for the installation type (-W setupTypePanel.selectedSetupTypeId="toolkit").

For the details about using response file parameters, please refer to the section "Installing with a response file" in Portal 5.1 Information Center.
(URL: http://publib.boulder.ibm.com/infocenter/wp51help/index.jsp?topic=/com.ibm.wp.ent.doc/wpf/conf_mai.html)

Q.

I am having problems re-installing the WebSphere Portal test environment after previously uninstalling it. How can I ensure that it will install correctly?

A.

Uninstall the test environment using the "Add or Remove Programs" control panel.

Perform the following checks:

1.      Check for the presence of the file "vpd.properties" in your Windows directory (e.g. C:\WinNT or root on Linux). If there are no concurrent installations of WebSphere Portal Server or WebSphere Application Server, delete this file; otherwise rename it

2.      (Windows only) Check for the presence of the following registry keys and delete if present:
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Application Server
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Portal Server
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphere Portal Personalization

3.      Delete all unnecessary files under the folder C:\Documents and Settings\<user_name>\Local Settings\Temp.

4.      Should they still exist, remove the PortalServer and AppServer folders from the original Portal test environment install.

5.      Re-install the Portal test environment

Q.

After updating my Portal test environment to the latest fix pack, it does not function correctly in Rational Application Developer or Rational Software Architect. What should I do?

A.

After updating the test environment to the latest available fix pack version, you must recreate server configurations in RAD or RSA.
You should also check that RAD has the latest updates/fix packs installed.

Q.

How do I determine my WebSphere Portal Server and base WebSphere Application Server versions?

A.

The WebSphere Portal test environment the versions can be determined as follows:

         WebSphere Portal test environment: Stored in the file <Test Environment install location>\PortalServer\version\Toolkit.product

         WebSphere Application Server: Stored in the file <Test Environment install location>\AppServer\properties\version\Base.product

Q.

I failed to install WebSphere Portal 5.1 in the same location as RAD is installed with WebSphere Application Server 6.0 test environment.   Why? How can I fix this?

A.

When installing WebSphere Portal v5.1 on a machine that already has Rational Application Developer installed, the WebSphere Portal v5.1 installation program detects one or both of the previously installed test environments:

         WebSphere Application Server v6

         WebSphere Portal v5.1

The installer then goes into a coexistence scenario. To overcome this problem follow the instructions in the tech note WebSphere Portal v5.1 full installation fails where Rational Application Developer v6.0 is installed with test environment

Q.

Can I upgrade the base WebSphere Application Server for the WebSphere Portal test environment?

 

The WebSphere Portal test environment is not supported on WebSphere Application Server 6.

If you want to test portlets on WebSphere Portal 5.1 running on WebSphere Application Server 6, you need to use Remote Server Attach functionality for a remote portal server. This will provide you with a similar test and debug environment.

For details, please refer to the RAD Help -> Developing portal and ... -> Portlet development overview ->Testing and debugging portlets or the Redbook - IBM Rational Application Developer V6 Portlet Application Development and Portal Tools (Chapter 31 - Remote Server Attach) (URL: http://www.redbooks.ibm.com/redpieces/abstracts/sg246681.html?Open).

Upgrading the base WebSphere Application Server with fix packs is also not recommended. Check with the WebSphere Portal support website before applying any WebSphere Application Server fix packs.

Q.

Can I enable security for testing with the WebSphere Portal test environment?

A.

Yes. The steps to do this are in the tech note Enabling Security for WebSphere Portal Test Environment

Q.

Can I not use the Administration Console for the WebSphere Portal Test Environment?

A.

No, this is not supported when running the WebSphere Portal test environment from either Rational Application Developer or Rational Software Architect.

If you really need to access the Administration Console for the WebSphere Portal test environment, you can start "server1" manually from the test environment install location.

Before starting the Admin Console, check the server configuration editor to see if the functionality you require is configurable within the editor. A lot of the functionality that you might need the Admin Console for is contained in the server configuration editor.

Q.

I need to add a shared library to the WebSphere Portal test environment.  How do I do this?

A.

You can add a shared library to the WebSphere Portal test environment via the "Portal" tab of a WebSphere Portal v5.1 test environment server configuration in Rational Application Developer or Rational Software Architect.

1.      Open the server configuration for your WebSphere Portal test environment.

2.      Navigate to the Portal page.

3.      Expand the Shared Library section.

4.      Add a jar or folder using the appropriate button.

Q.

Why can I not wire portlets in pages using the WebSphere Portal test environment?

A.

This is because the wiring portlet is not available. To make this portlet and wiring available:

1.      Stop the test environment

2.      From the Servers view, open the server configuration for the WebSphere Portal Test Environment

3.      In the Portal page, check the checkbox "Enable base portlets for portal administration and customization".

4.      Restart the server.

Q.

I lose wiring information for portlets when I restart the WebSphere Portal test environment. Why?

A.

Wiring information for portlet projects gets lost because the test environment resets each time on startup. This ensures that the test environment begins from a known-good state each time and prevents projects interfering with each other on the server.

To overcome this, we recommend that you place co-operative portlets in a portal project for testing. You can create wires using the wiring tool for portal projects. Running portal projects on the test environment allows for testing portlets and maintaining wiring information.

Q.

After trying to run an imported portal project on the WebSphere Portal test environment, I am getting an error similar to:

com.ibm.wps.command.xml.XmlCommandException: EJPXA0025E: The resource was not found in the portal, either because it does not exist or because you have not specified an identifying attribute in the XML input. [portlet-app uid=com.ibm.wps.portlets.web.1.$cloned.2_0_LU [PORTLET_APPLICATION_DEFINITION:702]]

Why is this?

A.

This error occurs when an imported portal project contains references to portlets that were created by copying other portlets from a WebSphere Portal Server and then run on the WebSphere Portal test environment.

The error occurs because the copied portlets were not installed on the test environment. Rational Application Developer and Rational Software Architect do not deploy portlets unless they are contained within portlet projects.

This error will only occur for copies of portlets that were originally deployed when the WebSphere Portal server was installed. For all other portlets that are not present on the test environment the placeholder portlet is used.

To test on the WebSphere Portal test environment, remove references to copied portlets from pages.

Q.

Can I use Embedded Messaging in the WebSphere Portal test environment?

A.

No, even though the server configuration editor provides a Java Messaging Server (JMS) page, Embedded Messaging is not installed with the WebSphere Portal test environment.

On starting up the WebSphere Portal test environment you will see the following in the console log:

[14/09/05 13:23:22:071 IST] 31214e86 JMSRegistrati A MSGS0602I: WebSphere Embedded Messaging Client only has been installed

[14/09/05 13:23:24:149 IST] 31214e86 JMSRegistrati A MSGS0601I: WebSphere Embedded Messaging has not been installed

Q.

Can I use WebSphere Content Manager functionality in the WebSphere Portal test environment?

A.

Yes but you need to upgrade your WebSphere Portal test environment to version 5.1.0.1. The update from version 5.1 to 5.1.0.1 is available from the Rational Product Updater tool.

Before using WCM, you need to enable it for Portal test environment. Please refer to "Lotus Workplace Web Content Management Release notes - Version 5.1.0.1" (http://www-12.lotus.com/ldd/doc/uafiles.nsf/docs/wcm5101/$File/wcm-5-1-0-1-releasenotes.htm).

Once enabled, you will need to add the Web Content Management jars to the Portal 5.1 JRE as follows:

1.      Go to Window->Preferences-> Java -> Installed JREs

2.      Select WebSphere Portal v5.1 JRE and click Edit

3.      Uncheck "use default system libraries" and select Add External JARs.

4.      Select all the jars in \PortalServer\wcm\shared\app\ directory.

Q.

Why am I receiving an error when deleting users from LDAP and running a portal export via XMLAccess afterwards?

A.

The fix for this problem is addressed in the following solution :

http://www-1.ibm.com/support/docview.wss?rs=688&context=SSHRKX&q1=PQ92578&uid=swg1PQ92578&loc=en_US&cs=utf-8&lang=en

Q.

In the Server configuration section, why are there configuration settings for tracing?

A.

The tracing that is available is for the WebSphere Application Server and not for the test environment.

Q.

What happens if my Portal test environment fails during an update?  How do I get it back to its original state to try the updater again?

 

Below are the steps that you need to follow when uninstalling the Portal Test Environment 5.1

 

Please carry out the steps outlined above to cleanly uninstall the Portal test environment.

 

The following folders need to be deleted so that the RPU can allow the re-application of the Portal test environment update :

 

        Rational\SDP\6.0\updater\workspace\new_features\eclipse\features\com.ibm.test.5101.updater_1.0.0

        Rational\SDP\6.0\updater\workspace\proxies\eclipse\features\com.ibm.etools.portal.ute.updater.5101_1.0.0

         Rational\SDP\6.0\updater\workspace\proxies\eclipse\features\com.ibm.test.5101.updater.test_1.0.0

 

Q.

When testing portlets that reference classes from utility Java projects, the test environment fails to start.  How can I fix this?

A.

In the server configuration, navigate to Environment > Classpath. Choose 'Add Folder' and select the <utilty project name> folder (not any of the project's sub-folders) and click OK.  The portlet will deploy successfully at the next attempt.

Q.

After running a portal project on the WebSphere Portal Test Environment that references a portlet from a portlet project, I can't successfully run the portlet project independently of the portal project on the test environment.  How can I get this portlet project to run successfully again?

A.

Rational Application Developer is locating the first EAR project to reference the portlet project and in this case it is the portal project's EAR project. To run the portlet, the portlet EAR project has to be explicitly run instead of the portlet project and a browser launched manually.


RAD 6.0 and 6.0.0.1 Unique

Q.

I can not see the WebSphere Portal 5.1 test environment when executing Run on Server. Why?

A.

You need to configure Portal test environment to work with Rational Application Developer as follows:

1.      Start Rational Application Developer.

2.      From the menu bar, select Window > Preferences > Server > Installed Runtimes. The Installed Server Runtime Environments page appears.

3.      Select WebSphere Portal v5.1 stub and select Edit. The Edit Server Runtime page appears.

4.      Change the name to WebSphere Portal v5.1 and specify the WebSphere Portal Location and WebSphere Application Server Location. (For example, C:\Program Files\Portal51UTE\PortalServer and C:\Program Files\Portal51UTE\AppServer respectively).

5.      Click Finish and click OK.

Note that this configuration steps are no longer required for RAD 6.0.1.

Q.

Portal Test Environment failed to start after applying RAD 6.0.0.1 iFIX 003. How can I fix this problem?

A.

You must upgrade Rational Application Developer to 6.0.1.

RAD 6.0 1 Unique

Q.

What is new for the Portal test environment by upgrading to 6.0.1?

A.

You will be able to see the following improvements for the Portal 5.1 test environment.

         The Portal 5.1 test environment is automatically configured when installed. No manual configuration is required.

         Portlet and portal projects can be republished without restarting the test environment. By selecting "Run on Server" on the project or "Publish" on the server configuration, changes will show in the projects in the following cases:

o        Adding a portlet to a portlet project

o        Adding JSP files to a Faces or Struts portlet

o        Adding Faces managed beans or Struts actions/form beans

o        Enabling Click-to-Action or wiring

o        Modifying portal page navigation and layout in Portal Designer


But a server restarts are required when :

o        Adding a portlet project to the server configuration

o        Adding a portlet from a new portlet project to a portal configuration in Portal Designer

o        Running a different portal project from the one currently running on the test environment.

Q.

Do I have to configure Portal test environment after the installation?

A.

No. You are no longer required to manually configure the Portal 5.1 test environment for RAD 6.0.1. It is automatically configured.

General WebSphere Portal 5.1 test environment Issues

Q.

What features of WebSphere Portal Server are not supported in the WebSphere Portal test environment?

A.

Portal features not supported by the Test Environment.

Q.

Why does my WebSphere Portal test environment seem to hang for a long time when starting in debug mode?

A.

This is addressed in the tech note You receive no response when you are in debug mode for the WebSphere Portal test environment.

Return to Index


<< End of Document >>