Verifying Process Portal

1. Make sure that you are using the correct URL. Try using an IP address instead of a host name.
2. If you get no logon window, or you get an HTTP error 404, page not found, or WebGroup/Virtual Host error, try the following actions.
   • If you use a proxy server, check that the /ProcessPortal context root for the Process Portal web application is correctly mapped. Also check the virtual host settings for the proxy server.
   • If you are using an HTTP server as a routing server, check the web module mapping.
3. Make sure that you are using a valid user ID and password to access Process Portal.
4. If you use a proxy server and are not using the default ports for http and https (80 or 443) perform the following actions:
   1. Make sure that the non-default ports that you are using for HTTP and HTTPS are redirected. Using the administrative console, click Environment > Virtual Hosts, and add the non-default host aliases for your servers to the default_host list. For example if you use port 81 for HTTP and port 444 for HTTPS, add *:81 and *:444 .
   2. If you use host names for the proxy servers rather than IP addresses, for each proxy server, make sure that host name of the proxy server is in the host files for the deployment manager and the proxy server itself.
   3. Restart the deployment manager.
   4. Configure the proxy server to add a rewriting rule for the application server SSL host name and port. On the admin console, Servers > WebSphere proxy servers > server_nameProxy Settings > HTTP Proxy Server Settings > Rewriting rules > New, for From URL pattern enter the protocol, host, port, and wildcard for the application server SSL service, for example https://app_server_host_name:9483/* . For To URL pattern enter the protocol, host, port, and wildcard for the proxy server SSL service, for example, https://proxy_server_host_name:444/*.
   5. Synchronize the managed nodes with the deployment manager using the syncNode command from the profile_root/bin directory or from the First steps console for the profile. Use the following syntax:
      • syncNode.sh deployment_manager port
      • syncNode.bat deployment_manager port
      Where deployment_manager is the host name or IP address of the deployment manager, and port is the port number. For more information about the syncNode command, see syncNode command in the WebSphere® Application Server information center.
5. Try to open the Process Portal URL again.

• Click the application name for more information about it.
• If you have a three or four cluster environment:
  • Check that the routing server is running.
  • Depending on whether you have a three-cluster or four-cluster topology, the applications required by Process Portal reside on different clusters. For detail about where each application resides, refer to the following table.
  • Make sure that the routing server is set up correctly according to the instructions linked to in step 2. In particular, check that the web modules are available on the routing server:
    • If you use an HTTP server, make sure that the web module is mapped to the web server.
    • If you use the WebSphere Application Server proxy server, make sure that the web module virtual hosts are mapped to the WebSphere Application Server proxy server virtual host, and that the WebSphere Application Server virtual host includes the host and port of the proxy server.
• For the applications that have a problem, perform the corresponding checks that are listed in the following table.

If you use HTTP and HTTPS protocols, verify both URLs.

If you receive the message SRVE0255E: A WebGroup/Virtual Host to handle /BusinessSpace/ has not been defined. and you have a three or four-cluster topology, this indicates that the /BusinessSpace (BSpaceEAR_) application is not deployed and mapped to the routing server. To solve this problem you must configure a suitable routing server as described in Configuring Process Portal: .