Testing and debugging portals in V 6.0 or later

You can test or debug a portal project on a local portal test environment server or a remote portal server. When testing or debugging a project for WebSphere® Portal, the test environment for both local and remote connections will be your WebSphere Portal Server.

Debugging allows you to set breakpoints and step through the code to diagnose problems.

To test or debug a portal project:

1. Configure a WebSphere Portal server connection.

2. Choose one of these actions:

   • Testing portals on local servers

   • Testing portals on remote servers

   • Debugging portals on local servers

   • Debugging portals on remote servers

To publish or deploy a portal project to a remote portal server, see Publishing portals.

• Testing portals on local servers
  To test a portal project locally, use a local install of WebSphere Portal V6.0 Server, or a later server.

• Testing portals on remote servers
  You can use your WebSphere Portal V6.0, or later, to test a portal project on a remote server.

• Debugging portals on local servers
  You must have a portal test environment see installation to debug a portlet project, such as a local install of Websphere Portal v6.0, or higher, server.

• Debugging portals on remote servers
  You must have a remote WebSphere Portal V6.0, or later, server installation to debug a portal project on a remote server. To debug the portals:

 

Related tasks

Testing portals on local servers

Testing portals on remote servers

Debugging portals on local servers

Debugging portals on remote servers

Defining Web browsers and device emulators

---