Standalone Solutions (for SAP BusinessObjects) - 2024.3

Release date: October 8th, 2024

👻 Spooky Season 👻 has started and it is time for us to release our final version of the year!

This update will give you better insights into your environment and help you determine if you’re ready to migrate to BI 2025. We focused on improving 360Eyes inside 360Suite, by adding Collibra, logs for the BusinessObjects task. We’ve also added many requested features and fixed various issues.

Full Documentation: Documentation - Wiiisdom Customer Center
Download Site: https://support.wiiisdom.com/downloads

Of course, do get in touch if you need help with updating.

💡Important Information💡

It has been a year since we announced that 360Eyes will no longer be a standalone application. This version will be the final standalone release of 360Eyes. Starting from version 2025.1, 360Eyes will only receive updates and modifications through 360Suite. We will no longer provide standalone versions.

We strongly recommend migrating your standalone version to 360Suite as soon as possible to ensure continued support and updates.

New Features - 360Eyes for SAP BusinessObjects

Stop Audit Server

We removed the ability to stop the Auditing Event Server while doing a job. This parameter could cause loss of Audit Data while the job was running, and could potentially fail to be restored if the job was in failure.

Run a Job from Specific Snapshot

We wanted to give you a way to run a job from a specific snapshot, when running the job in DELTA (-loadingMode=DELTA)

You can now use the parameter -previousSnapshotId=<SNAPSHOT_ID>. This will allow you to run the job in DELTA and/or REPLACE mode from the given snapshot if the CMS and job type are identical.

Improved performance

When running a WEBI Job, we now extract the metadata of Universes only when the parameter : webi.dataproviders.queryspecification is set to ON we also improved the extraction of data to make sure we have a more efficient and effective process.

Improved SQL Parser

We are in a process of improving the SQL Parser to allow a better parsing of your data, regardless of your Database Server. The parser does not include BigQuery as of yet. But for other queries, it should return better information. To use this parser, you will need the parameter -parseDataProviderSQL=ON

Replacement Connections

When doing an extract of a Universe's Data Security Profile (UNX), we used to only get information on the main connection, we modified the way we extract the data to also fetch the Replacement Connection if it exist.

Disable Batch Extraction

Since the 2023.2 release, when extracting Audit Event, the job processes batch of information, we noticed that this is not working for older version of Database, we added a way to disable the batch by setting the parameter like so : audit.batch.size=0

Changelogs

▪ Modified the Universes to accept Unicode Strings by setting UNICODE_STRINGS=TRUE in the parameters.

▪ The auditor.disable_audit_during_run and audit.restore.level have been deleted. Stopping the SAP Auditing Service during a job is no longer possible.

Security Fixes

▪ CVE-2022-25647: We upgraded com.google.code.gson to a newer version.

▪ Multiple CVE removed from bouncycastle.

▪ CVE-2023-6328: Upgraded Logback to 1.3.14

▪ CVE-2022-1471: Exclude snakeyaml and jaxb-api from our libraries.

Resolved Issues

▪ WEBI - ORA-00001: unique constraint violated on EYE_DOCUMENT_REPORT_ELEMENT & EYE_DOCUMENT_REPORT tables (Impact: Medium)
ID: P360EYES-5343
Product: 360Eyes for SAP BusinessObjects
Description: The WEBI job may encounter an “{{ORA-00001: unique constraint violated}}" exception during data insertion into the EYE_DOCUMENT_REPORT, EYE_DOCUMENT_REPORT_ELEMENT, EYE_ALERTER_RULE, EYE_ELEMENT_ALERTER and EYE_FILTER tables. To address this issue, we have enhanced the code to eliminate duplicate values, ensuring smooth data insertion and maintaining database integrity.
▪ CMS - Violation of PRIMARY KEY constraint 'PK_CMS_OVERLOAD' (Impact: Medium)
ID: P360EYES-5212
Product: 360Eyes for SAP BusinessObjects
Description: Running a CMS job with {{cms.content = UNIVERSE,OVERLOAD}} where some Overloads items share the same name results in an error.
▪ CMS job - Negative Duration Values in Recurring Instances.(Impact: Low)
ID: P360EYES-5352
Product: 360Eyes for SAP BusinessObjects
Description: The CMS job sometimes extracts negative schedule durations when the End Time precedes the Start Time, affecting accurate analysis. The expected behavior is to ensure schedule durations are always positive if negative, set the duration to 0 or NULL
▪ CMS UNX OVERLOAD - A communication error occurred when connecting to the server InputFileRepository (FWM 01009) (Impact: Low)
ID: P360EYES-5351
Product: 360Eyes for SAP BusinessObjects
Description: When executing the CMS job in an architecture with a load balancer, a connection error occurs during the UNX Overload extraction due to communication issues with the server. A solution involves modifying the code to catch exceptions and reinitialize the DSL session before accessing the SAP Publishing Service.
▪ 360Eyes - Incorrect BO Version displayed in the log file. (Impact: Low)
ID: P360EYES-5340
Product: 360Eyes for SAP BusinessObjects
Description: When running 360Eyes jobs on different versions of BusinessObjects via 360Suite, the log incorrectly retains the SAP BusinessObjects version of the first executed job. This issue arises because the BusinessObjects version is stored in a static variable, leading to inaccurate version logging across subsequent jobs. This issue impacts only the data saved in the log file.
▪ CMS - Data truncation: Incorrect datetime value for columns 'NEXT_RUN_TIME' and 'SCHED_DESIRED_BEGIN_DATE' (Impact: Low)
ID: P360EYES-5265
Product: 360Eyes for SAP BusinessObjects
Description: Scheduling BusinessObjects documents post-2038 causes data truncation errors in CMS_DOCUMENT due to TIMESTAMP range limits. Solution: Convert SCHED_DESIRED_BEGIN_DATE and NEXT_RUN_TIME columns to Datetime type to support a wider date range.