Common Problems

This table lists some common errors that may occur when setting up the feed framework:

Problem	Resolution
When you click a Publish as Feed link, the system displays the following pop-up error message: `Some required configuration steps are not done for the Feed Publishing Framework. Please check the IB Service Configuration.`	Complete configuration of your PeopleSoft system to support feeds. See Configuring Integration Broker Service Target Locations.
When you click the link for a feed, the system displays the following error message: `<?xml version="1.0" ?> - <IBResponse type="error"> <DefaultTitle>Integration Broker Response</DefaultTitle> <StatusCode>20</StatusCode> <MessageSet>158</MessageSet> <MessageID>10733</MessageID> <DefaultMessage>Integration Gateway failed while processing the message.</DefaultMessage> - <MessageParameters> <Parameter>password</Parameter> </MessageParameters> </IBResponse>`	Complete configuration of your PeopleSoft system to support feeds. See Configuring Integration Broker Service Target Locations.
When you click the link for a feed—for example, on the My Feeds page—a new browser window opens and redisplays the page that you are on instead of the feed.	The feed was published even though configuration of the PeopleSoft system was incomplete. Complete configuration of your PeopleSoft system to support feeds. See Configuring Integration Broker Service Target Locations.
During configuration of Integration Broker, you get the following error message when you attempt to ping the default local node: `Integration Broker Authentication: No node Authentication Option set for node node_name on Target sys`	Set the node authentication to either password or certificate. See Configuring the Default Local Node.
When you click the link for a feed, the system displays one of the following error messages: `Address not found` `Could Not Connect to Server` `Unable to connect` `Cannot display the webpage`	The Target Location or the Secure Target Location is not set properly on the Service Configuration page. See Configuring Integration Broker Service Target Locations.
When you click a feed entry in a feed, the system displays the following error message: `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 ol resource is permanently unavailable and has no forwarding address.`	The Portal Context URI text or Portal URI text for the local host node has not been configured on the Node Definitions - Portal page. See Setting URI Text for Local Host Nodes.
When you open a worklist feed, the system displays feed entries but not any hyperlinks for viewing the details for each feed entry.	The Portal Context URI text or Portal URI text for the local host node for Workflow has not been configured on the Node Definitions - Portal page. See Setting URI Text for Local Host Nodes. See Understanding Worklist Feeds.
When you click a feed entry in a feed, the system displays the following error message: `Site name is not valid. Check your syntax and try again.`	The Portal Context URI text or Portal URI text for the local host node is not configured properly on the Node Definitions - Portal page. Note: Both values require a terminating / to be correct. See Setting URI Text for Local Host Nodes.
The feed document displays the feed title but no feed entries.	Feed entries appear in the context of the logged in user. One of the following conditions could result in no feed entries in the feed document: The current user has no feed entries, for example, the user does not have any unused items in the specified worklist. The feed definition was not specified correctly.
When you click the link for a feed, a new browser window opens, but you are prompted to authenticate yourself with a user name and password: `A username and password are being requested by server_name`	A mismatch occurred in the way the system was identified in the login URL versus how the system was identified for the Integration Broker service configuration. For example, this problem can occur when the login URL is specified as a numeric IP address (that is, 192.0.2.1) and the service configuration is specified by a fully qualified domain name (that is, myserver.myco.com), or vice versa.
When you click the link for a feed, a new browser window opens, but you are prompted to authenticate yourself to the Oracle WebLogic Server with the following message: `The server server_name at WebLogic Server requires a username and password.`	You must configure the Oracle WebLogic Server to disable its own authentication. See Configuring Oracle WebLogic Server to Disable Authentication.
When you request a feed, you are challenged for authentication even though you are already signed into the PeopleSoft system.	The PeopleSoft login URL and the feed URL are of different protocols, for example, one uses HTTP and the other uses HTTPS. If a secure target location was specified on the Integration Broker Service Configuration page, then the PeopleSoft login URL should be HTTPS. Conversely, if no secure target location was specified on the Service Configuration page and only a target location was specified, then the PeopleSoft login URL should be HTTP. In either case, when a mismatch of protocols is used on your PeopleSoft system, you will be prompted for credentials again when you attempt to view a feed from a PeopleSoft page. Note: Certain integrations indicate the use of HTTPS. PeopleSoft feeds support integration with third-party feed readers through basic authentication only. However, since basic authentication is not secure, you should use HTTPS for feeds in this scenario. Set it by specifying a secure target location on the Integration Broker Service Configuration page. See Configuring Integration Broker Service Target Locations.
When you click the link for a feed, the system displays one of the following error messages: IBResponse type="error" `<?xml version="1.0" ?> - <IBResponse type="error"> <DefaultTitle>Integration Broker Response</DefaultTitle> <StatusCode>20</StatusCode> <MessageSet>158</MessageSet> <MessageID>536</MessageID> <DefaultMessage>UserID QE_GUEST not authorized for Service Operation PTFP_GETPREPUBFEED</DefaultMessage> - <MessageParameters> <Parameter>QE_GUEST</Parameter> <Parameter>PTFP_GETPREPUBFEED</Parameter> </MessageParameters> </IBResponse>` You are not authorized `<?xml version="1.0" ?> <ErrorMessage>You are not authorized to view this feed.</ErrorMessage>`	The user ID assigned to the ANONYMOUS node does not have sufficient privileges. At a minimum, this user ID must be assigned the PTPT1000 (PeopleSoft User) permissions. See Configuring the Default User of the ANONYMOUS Node.

Problem

Resolution

When you click a Publish as Feed link, the system displays the following pop-up error message:

Some required configuration steps are not done for the Feed Publishing Framework. Please check the IB Service Configuration.

Complete configuration of your PeopleSoft system to support feeds.

See Configuring Integration Broker Service Target Locations.

When you click the link for a feed, the system displays the following error message:

<?xml version="1.0" ?> 
- <IBResponse type="error">
  <DefaultTitle>Integration Broker Response</DefaultTitle> 
  <StatusCode>20</StatusCode> 
  <MessageSet>158</MessageSet> 
  <MessageID>10733</MessageID> 
  <DefaultMessage>Integration Gateway failed  while processing the message.</DefaultMessage> 
- <MessageParameters>
  <Parameter>password</Parameter> 
  </MessageParameters>
  </IBResponse>

Complete configuration of your PeopleSoft system to support feeds.

See Configuring Integration Broker Service Target Locations.

When you click the link for a feed—for example, on the My Feeds page—a new browser window opens and redisplays the page that you are on instead of the feed.

The feed was published even though configuration of the PeopleSoft system was incomplete.

Complete configuration of your PeopleSoft system to support feeds.

See Configuring Integration Broker Service Target Locations.

During configuration of Integration Broker, you get the following error message when you attempt to ping the default local node:

Integration Broker Authentication: No node Authentication Option set for node node_name on Target sys

Set the node authentication to either password or certificate.

See Configuring the Default Local Node.

When you click the link for a feed, the system displays one of the following error messages:

Address not found
Could Not Connect to Server
Unable to connect
Cannot display the webpage

The Target Location or the Secure Target Location is not set properly on the Service Configuration page.

See Configuring Integration Broker Service Target Locations.

When you click a feed entry in a feed, the system displays the following error message:

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 ol resource is permanently unavailable and has no forwarding address.

The Portal Context URI text or Portal URI text for the local host node has not been configured on the Node Definitions - Portal page.

See Setting URI Text for Local Host Nodes.

When you open a worklist feed, the system displays feed entries but not any hyperlinks for viewing the details for each feed entry.

The Portal Context URI text or Portal URI text for the local host node for Workflow has not been configured on the Node Definitions - Portal page.

See Setting URI Text for Local Host Nodes.

See Understanding Worklist Feeds.

When you click a feed entry in a feed, the system displays the following error message:

Site name is not valid. Check your syntax and try again.

The Portal Context URI text or Portal URI text for the local host node is not configured properly on the Node Definitions - Portal page.

Note: Both values require a terminating / to be correct.

See Setting URI Text for Local Host Nodes.

The feed document displays the feed title but no feed entries.

Feed entries appear in the context of the logged in user. One of the following conditions could result in no feed entries in the feed document:

The current user has no feed entries, for example, the user does not have any unused items in the specified worklist.
The feed definition was not specified correctly.

When you click the link for a feed, a new browser window opens, but you are prompted to authenticate yourself with a user name and password:

A username and password are being requested by server_name

A mismatch occurred in the way the system was identified in the login URL versus how the system was identified for the Integration Broker service configuration. For example, this problem can occur when the login URL is specified as a numeric IP address (that is, 192.0.2.1) and the service configuration is specified by a fully qualified domain name (that is, myserver.myco.com), or vice versa.

When you click the link for a feed, a new browser window opens, but you are prompted to authenticate yourself to the Oracle WebLogic Server with the following message:

The server server_name at WebLogic Server requires a username and password.

You must configure the Oracle WebLogic Server to disable its own authentication.

See Configuring Oracle WebLogic Server to Disable Authentication.

When you request a feed, you are challenged for authentication even though you are already signed into the PeopleSoft system.

The PeopleSoft login URL and the feed URL are of different protocols, for example, one uses HTTP and the other uses HTTPS. If a secure target location was specified on the Integration Broker Service Configuration page, then the PeopleSoft login URL should be HTTPS. Conversely, if no secure target location was specified on the Service Configuration page and only a target location was specified, then the PeopleSoft login URL should be HTTP. In either case, when a mismatch of protocols is used on your PeopleSoft system, you will be prompted for credentials again when you attempt to view a feed from a PeopleSoft page.

Note: Certain integrations indicate the use of HTTPS. PeopleSoft feeds support integration with third-party feed readers through basic authentication only. However, since basic authentication is not secure, you should use HTTPS for feeds in this scenario. Set it by specifying a secure target location on the Integration Broker Service Configuration page.

See Configuring Integration Broker Service Target Locations.

When you click the link for a feed, the system displays one of the following error messages:

IBResponse type="error"

<?xml version="1.0" ?> 
- <IBResponse type="error">
  <DefaultTitle>Integration Broker Response</DefaultTitle> 
  <StatusCode>20</StatusCode> 
  <MessageSet>158</MessageSet> 
  <MessageID>536</MessageID> 
  <DefaultMessage>UserID QE_GUEST not authorized for Service Operation PTFP_GETPREPUBFEED</DefaultMessage> 
- <MessageParameters>
  <Parameter>QE_GUEST</Parameter> 
  <Parameter>PTFP_GETPREPUBFEED</Parameter> 
  </MessageParameters>
  </IBResponse>

You are not authorized

<?xml version="1.0" ?> 
  <ErrorMessage>You are not authorized to view this feed.</ErrorMessage>

The user ID assigned to the ANONYMOUS node does not have sufficient privileges. At a minimum, this user ID must be assigned the PTPT1000 (PeopleSoft User) permissions.

See Configuring the Default User of the ANONYMOUS Node.