Server recommendations

Some anti-virus or firewalls may interfere with OnePart depending on features, configurations and versions. OnePart requires low level access to memory, disks and network. It can lead to false positives in some security software that are analyzing system call patterns.

If you experience such an issue:

• add exceptions related to OnePart processes and ports

• update your anti-virus to the latest version

If you encounter difficulties finding acceptable settings for your security software and OnePart still fails to start or install, add NG=noinject to the ngstart.env files in the following folders:

• <ONEPARTINSTALLDIR>/software/cloudview-installdir/ngroot.env

• <ONEPARTINSTALLDIR>/software/install/tools/

• <DATADIR>/bin

After installing OnePart, it is highly recommended to disable any anti-virus software on the DATADIR directory.

Among the many data structures that OnePart uses on disk, the Document Cache is rather voluminous (taking up to 80% of the total) and has lower storage performance requirements than the rest of the index structure.

Exalead CloudView makes it possible to locate the Document Cache outside of the product’s home directory, typically on larger and slower disks - a solution that should be benched and validated by product architects in the target use-case. To accomplish this you must change the location of the document cache on the file system as follows:

• Stop OnePart.
• Follow the procedure described in the Exalead CloudView Connectors Guide: Using Document Cache.

The sizing recommendations are detailed below for a single server setup, without high-availability (HA). This applies to a non-customized OnePart instance. Customizations on OnePart can have a high impact on system performance.

These estimates are based on various datasets and usage scenarios which have been brought to our attention. In some cases, your data and/or application usage might differ from those used to define this table, which might not work for you.

* Custom: contact the OnePart sizing team

* Size on disk: the required disk space for the OnePart data

For example, for 420 000 parts, and an estimated 7 pages per second usage peak: round up to the highest bracket in the table and lookup the 500 000 parts / 8 pages per second cell. In this example, we recommend an "S"-class server.

On a side note, this server also has capacity of up to 10 pages/second for 500 000 parts or 4 pages/second at 1M parts.

OnePart requires a minimum 25 GB of available disk space.

To maximize I/O performance when indexing, we recommend using SCSI, SAS, SAN over FC or SSD disks (as opposed to SATA disks) to store the data files.

For performance and reliability reasons, the data directory cannot reside on a network file system such as NFS, CIFS, and so forth.

Install OnePart on a 64-bit adl_co (X86_64) server running a platform listed in the Program Directory (or on Airbridge for standalone releases).

See http://www.3ds.com/fileadmin/Support/Documents/Platform-support-policies.pdf for Dassault Systèmes support policy.

We highly recommend one of the following 64-bit Windows operating systems (X86_64):

Operating System	Level of support
Windows Server 2016	**Qualified
Windows Server 2019	**Qualified

See also Windows requirements.

Important: We also recommend installing NETVIBES OnePart on a "clean" server that has no other instances of OnePart running.

The virtual environments supported are detailed below.

See http://www.3ds.com/fileadmin/Support/Documents/Platform-support-policies.pdf for Dassault Systèmes support policy.

Platform	Level of support
Physical Intel server	**Qualified
VMWare ESX 5.1	*Compatible
MS HyperV 6.3	*Compatible

Sizing recommendations equally apply to physical and virtual environments, based on CPU and IO performance available to the OnePart application.

In the case of virtualization, we recommend proper graphics card emulation since OnePart makes use of it for 3D rendering.