Hostname and Port for User-Defined task "Details" Page are ignored in WebCenter Spaces/Framework (Doc ID 1373516.1)

Last updated on FEBRUARY 15, 2017

Applies to:

Oracle Business Process Management Suite - Version 11.1.1.3.0 to 11.1.1.5.0 [Release 11gR1]
Oracle WebCenter Portal - Version 11.1.1.2.0 to 11.1.1.5.0 [Release 11g]
Information in this document applies to any platform.

Symptoms

In a WebCenter Spaces/Framework application there is a Worklist application with "Details" page link.

There are few possibilities when this issue can be seen:

  1. An attempt to customize the "Details" link to point to some other, non-default task "Details" page;
  2. Due to configuration changes, the URL being used needs to pass the LBR/WebTier or similar and change the hostname and/or port.


Within the first scenario:

The EAR file was deployed on the SOA server which re-directs users to the proper application which is deployed on a different server to SOA.

This results in an error:
Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is
given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the
client, the status code 403 (Forbidden) can be used instead. The 410
(Gone) status code SHOULD be used if the server knows, through some
internally configurable mechanism, that an old resource is permanently
unavailable and has no forwarding address.

However, this works fine when the external task "Details" application is deployed onto the same host and port as SOA server.


Within the second scenario:

All requests should go through a LBR/Webtier URL. To change the Human Task Form URL there is a need of changing the hostname and port used by the "Details" pages for it to work.

This results in an error:
Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is
given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the
client, the status code 403 (Forbidden) can be used instead. The 410
(Gone) status code SHOULD be used if the server knows, through some
internally configurable mechanism, that an old resource is permanently
unavailable and has no forwarding address.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms