High WIPS memory consumption during a 360eyes WEBI Jobs

High WIPS memory consumption during a 360eyes WEBI Jobs

Symptoms

When running 360Eyes Webi jobs, the Web Intelligence Processing Servers (WIPS) can consume a lot of memory, potentially triggering alerts in SAP BusinessObjects or making the WIPSes unresponsive.

Cause

When exporting metadata of Webi documents, 360Eyes needs to open them. If the SAP BusinessObjects environment is configured to automatically refresh documents on open, it can impact the performances even though 360Eyes doesn't need to refresh the data.

Resolution

Activate the "Disable automatic refresh on open" option and disable the "Enable auto save" option for the user running the 360eyes Jobs as follows:
Log in to the CMC.
Browse to Applications.
Right-click on Web Intelligence > User Security.

Assign security for the user running the 360Eyes jobs.


Go to the "Advanced" tab and then "Add/remove Rights"


Configure the rights ccordingly and then click "Apply".

Environment

  1. 360Eyes within 360Suite
  2. 360eyes Standalone

    • Related Articles

    • Webi Job Connectivity Issue

      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 ...

    • 360Eyes evolution: from "standalone" to 360Suite web application

      Context On the meta-level, 360Eyes is part of 360Suite, a suite a modules working with BusinessObjects environments to help BI administrators with their day-to-day activities. On a practical level, the 360Eyes module itself has known changes over ...

    • Identify 360eyes jobs on Windows servers

      Symptom How to find active 360Eyes jobs when they are running on a Windows platform? Environment 360Eyes SAP BusinessObjects Enterprise XI 3.1 SAP BusinessObjects Business Intelligence 4.0 SAP BusinessObjects Business Intelligence 4.1 SAP ...

    • How to Identify and Retrieve 360Eyes Job Logs in 360Suite Tomcat

      How to Identify and Retrieve 360Eyes Job Logs in 360Suite Tomcat Overview When a 360Eyes job fails, the execution log stored in the Tomcat logs folder is the fastest way to diagnose the issue. This guide explains how logs are named, where they are ...

    • No Audit data Extracted when the SAP Audit database is on a Sybase/SQL Anywhere server.

      Environment Product version(s): All current 360Suite versions Third-party technology: SAP Audit database hosted on Sybase / SQL Anywhere Database: Sybase / SQL Anywhere Symptoms A job run with Audit data extraction enabled, where the SAP Audit ...