Configuring remote WebSphere Portal servers for testing and debugging
Before you test or debug portals or portlets on a remote portal
server, you may need to do some additional configuration steps on the remote
server.
To test or debug with multiple users on the same remote portal
server: On the Portal Administration page on the remote portal server,
create a user that will access the portlets being tested. Testing or debugging
a portlet on a remote server automatically adds the required permissions. Every user must use their own user ID. Otherwise, the portlet application
that you are previewing may be accidentally uninstalled by someone whose user
ID is the same as yours. Or, your preview page may be accidentally updated,
if the label is also the same.
To
test or debug a JSR 168 portlet on a WebSphere® Portal v5.0.2 server: Enable
the portlet container of the WebSphere Portal server for JSR 168 by setting portal.enable.jsr168
= true in the ConfigService.properties file in the wp_root/shared/app/config/services directory.
To debug on a remote server attach server:
Start the WebSphere Application Server on the remote system:
Select Programs > IBM
WebSphere > Application Server > Start
the Server.
Type this at the command prompt:
cd WebSphere_install_root/bin
./startServer.sh server1
where WebSphere_install_root is the directory
where WebSphere Application
Server is installed.
Start the HTTP Server.
Start the Administrative console by opening a Web browser to
the following URL:
http://localhost:9090/admin
Log in.
Expand Servers and select Application
Servers.
In the right pane, click on WebSphere_Portal.
Under Additional Properties, select Debugging
Service.
On the Debugging Service page, select
the Startup check box.
where address specifies the JVM debug port number. The default value is 7777. Make a note
of the port number; you will need it when you configure the server attach
server
Click OK > Save .
Click Save on the Save to
Master Configuration panel.
Logout of the Administrative Console.
Stop WebSphere Application Server, and start WebSphere Portal:.
Select Programs > IBM WebSphere > Application Server > Stop the Server.
Select Programs > IBM WebSphere > Portal Server > Start the Server.
cd WebSphere_install_root/bin
./stopServer.sh server1
./startServer.sh WebSphere_Portal
where WebSphere_install_root is the directory
where WebSphere Application
Server is installed.
Note: Restarting the server to pick up server configuration changes
takes time. It is recommended that all server configurations be done at the
same time, to reduce the number of server restarts required. Refer to these
help topics for other possible server configuration changes: