OIC (Online Information Collection)

This preference contains the setting allowing you to activate the online collection of information which can help you to analyze system crashes and user usages.

This page discusses:

Overview

A 3DEXPERIENCE session generates a set of files: various statistics, usages and trace files, abend traces and potentially dump files. They are stored in different places and accumulated from one session to another.

The Online Information Collection functionality allows you to collect and transfer this information directly to :

  • Dassault Systèmes' MTBF server for crash report information.
  • The cloud server for user usage information. (not available for on-premises installations).

The functionality can be enabled or not via a setting.

To enable the automatic collection of all information, some of these existing files need to be packed together on a session basis in a zip file, others may be uploaded as is.

In order not to be impacted during a crash, the upload process is handled via another process named DSYSysIRManager.exe.

Definitions

MTBF (Meantime between failures) information

In this context, the information mentioned is all the data needed to understand a runtime problem, the scenario leading to this problem, and the environment in which this problem occurs. The information will enable you to analyze performance crashes as well as issues, and will be collected through all statistics and performance logs that a session can produce.

They are composed of the following :

  • A minidump file in user-mode (.dmp), in case of a crash.

    This file contains enough information to perform basic debugging operations while keeping the minidump size as small as possible. Current versions of Microsoft Office and Microsoft Windows create these minidump files for the purpose of analyzing failures on customers' computers.

  • A system information file (.irp).

    This is an intermediate text file used for the final analysis. It contains system and product information, which can be helpful to identify the problem with a better precision. This file is not supposed to be accessed or read directly.

  • A historical abend information file (.txt)

    In some situation, historical session information, AbendTrace_xxx.txt file for example, could be saved in the compressed files collection.

  • A file version (.vrs)

    This is an empty file whose name refers to the version of the debug material archive.

Usage information

Files logging user usage (time spent, etc.) in an application (formerly workbench).

How are the files stored?

The files used for MTBF come from many different locations and are put into an archive, named with a GUID, located under one of those two paths :

  • <CATTemp>/DSYSysIRManager/Session for a light MTBF information (no crash or issue detected)
  • <CATTemp>/DSYSysIRManager/Incident for a needed MTBF information to understand the detected issue

Files used for usage information, whose name can vary, are generated in this folder : <CATTemp>/DSYSysUsage

These files will remain on the user's computer.

Usage metrics collection

The usage metrics collection has three parameters

  • A check box to activate/deactivate the whole information upload process by the DSYSysIRManager.exe
  • the Usage upload URL
    • already filled in with the current cloud server for a cloud installation
    • empty for an on-premises installation, since this functionality is not available on premises.
  • the MTBF upload URL already filled in with the DS Official MTBF Server

The URL are not editable.

The default value of the check box depends on the installation type:

  • Checked for a cloud installation
  • Unchecked for an on-premises installation.


Recommendation: Click Show Privacy Policy to display Dassault Systèmes Privacy Policy.