Environment

• Product version(s): 360Suite (all versions using the WEBI job with RESTful API connectivity)

• Third-party technology: SAP BusinessObjects (BI Platform / BIPRWS RESTful Web Services)

Symptoms

When running a 360Suite job that scans WEBI documents, the job fails, while jobs scanning other object types (for example CMS or Universes) complete successfully in the same environment.

• The WEBI job fails with a connection or authentication error.

• CMS and Universe snapshots run without issue on the same 360Suite instance.

• The job log shows the job attempting to reach a RESTful service URL before failing.

Error Message

Warning: ERROR c.w.e.i.mappers.AbstractRestWSMapper - Error while granting the REST token due to : java.net.ConnectException: Connection timed out: connect

Steps to Reproduce

1. Run a 360Eyes WEBI job.

2. Run a job that includes only CMS and/or Universe scans in the same environment.

3. Observe that the WEBI job fails with a REST token / connection timeout error, while the CMS and Universe job completes successfully.

Cause

This issue only affects the WEBI job because of how 360Suite connects to SAP BusinessObjects for this specific object type.

• Context: CMS and Universe scans rely only on the BusinessObjects SDK libraries to communicate with the BI Platform. WEBI scans require an additional connection: the BusinessObjects RESTful Web Services (BIPRWS), used to grant a REST token.

• Technical explanation: If the RESTful service endpoint is unreachable from the 360Suite server (network route not configured, or a firewall blocking the port), the WEBI job fails when it tries to obtain a REST token, even though the SDK-based connection used by CMS and Universe jobs succeeds.

Why: Only the WEBI job needs this extra RESTful connection in addition to the SDK. That is why CMS and Universe scans are unaffected while WEBI scans time out.

RESTful Service Locations

Depending on your SAP BusinessObjects deployment, the RESTful Web Services can be exposed in one of two ways:

• WACS (older deployments): The RESTful service is exposed through the Web Application Container Server, typically on a dedicated port (commonly 6405 by default). [TODO: confirm exact port(s) for your environment]

• Tomcat (current deployments): The RESTful service is exposed through a Tomcat instance, typically on a dedicated port (commonly 8080, or a custom port such as 6400). [TODO: confirm exact port(s) for your environment]

Check with your BusinessObjects administrator which deployment method (WACS or Tomcat) is used, and confirm the exact hostname and port serving the RESTful API (commonly reachable at a URL similar to https://<host>:<port>/biprws).

Resolution

Follow these steps to confirm the cause and resolve the issue.

1. Identify whether 360Suite and SAP BusinessObjects are installed on the same server or on separate servers.

2. From the 360Suite server, check basic network connectivity to the RESTful service host and port using a simple command:

   telnet <biprws_host> <port>

   If the connection does not open, this confirms a network or firewall issue rather than a 360Suite configuration issue.

3. As a further check, open a browser directly on the 360Suite server and browse to the RESTful service URL, for example:

   https://<host>:<port>/biprws

   Expected result: The page loads and returns a response from the RESTful service. If the page does not load or times out, this confirms the RESTful service is not reachable from the 360Suite server.

4. If either check fails, contact your network administrator and ask them to:

   • Confirm a network route exists between the 360Suite server and the RESTful service host (WACS or Tomcat).

   • Check whether a firewall rule is blocking the port used by the RESTful service between the two servers, and open it if needed.

5. Once connectivity is confirmed or the firewall port is opened, re-run the WEBI job to verify the REST token can be granted successfully.

Additional Information

• If the issue persists after confirming network connectivity, please contact support with the job log showing the error, the RESTful service URL used, and confirmation of whether WACS or Tomcat is used.