Version 12.0 - Esko

These are the minimum requirements for reasonable performance of the described products. They will help you decide whether the equipment you are currently using remains viable. If you are considering new equipment, bear in mind that these requirements are minimum, not optimal. Exceeding these specifications will in general lead to enhanced performance.

Note that Mac OS X 10.9 Mavericks is officially supported from Suite 12 Assembly 5, release date: end January 2014. This applies to the following Esko software packages running on OS X: Automation Engine Pilot, DeskPack, Studio, ArtPro, i-cut Preflight, Neo …
In case the customer has upgraded their Macs to Mavericks, there is a License Manager hotfix available for Suite 12 Assembly 4: https://wiki.esko.com/pages/viewpage.action?pageId=78613702
From the first week of January 2014 onwards, customer can download the installers for all Interactive applications v12.1.2,  i-cut Layout and i-cut Preflight v12.1 (Assembly 5) on https://mysoftware.esko.com


Note that installing and using Esko software on a Terminal Services or Remote Desktop Services server (Microsoft, Citrix,…) is not supported.
Note that using Esko software with local licenses when launched via Remote Desktop is not supported.
Note that Windows Server 2012 Standard and Datacenter are supported from Suite 12.1.1 (Assembly 4). This depends on the Product. Therefore, check the specific product system requirements. Windows Server 2012 Essentials and Foundation are not supported.

See more notes here

Click here to go to the System Requirement page of Previous releases (Esko Software Suite 7 products, Nexus, Odystar...).

   


ArtiosCAD 12 Client 

ArtiosCAD12                 CAD-X12

 

Operating System

  • Windows 7 Professional 32 & 64-bit with limitations. See Release Notes.
    Please note the Home and Ultimate editions should work as well, but it was the Home edition that was fully certified.
  • Windows Server 2008, 2008 r2 (64-bit) with limitations. See Release Notes.
  • Windows Vista Business Edition with limitations 32/64 See Release Notes.
  • Microsoft® Windows® XP Pro SP2 or higher, 32 & 64-bit
  • Mac OS® X 10.4/VMWare Fusionv3.x running on an Intel® Mac with limitations.  See Release notes.
  • The following platforms may be used in an experimental mode. They have been tested to a certain point but have not been certified for this release:
    - Mac Bootcamp
  • Operating system patches: 
    Windows XP sp2 and Windows server 2003...,  http://support.microsoft.com/kb/319740, This patch will resource leaks when using ArtiosCAD.
    Vista Business Edition… http://go.microsoft.com/fwlink/?LinkID=82148, This patch will install the help environment for running ArtiosCAD help

 

CPU

  • Architecture
    • To fully take advantage of the 3D Importer or solidworks module, x86 64-bit processors will be recommended, especially for importing multi-hundred Mbyte files. You will need to consider the 64-bit processors for future releases of ArtiosCAD.

    • ArtiosCAD is still a 32-bit application. All other uses other than 3D Importer or Solidworks (32-bit) modules will require a x86 32-bit processor.

  • Performance

    • Intel® Core 2 Duo: 2.4 GHz, 2.4 GHz, required

Memory             4G required

Disk Space        

5 GB for the ArtiosCAD application and 500 MB available on the system partition
                                         
If using the ArtiosCAD enterprise client, please reserve an additional 30G for the ArtiosCAD application, including the local cache, and 500M available on the system partition. If workspaces are large  and/or the cache contents are not purged regularly, you should consider more than 30G for the local disk.

Network

TCP/IP v4 required, TCP/IP v6 not supported.

ArtiosCAD Enterprise 12 utilizes http as its core communication protocol. For optimal performance, do not drop http to a lower quality of service (QOS), or at least ensure http traffic directed to the enterprise web server received higher network priority.

For multiSite enterprise deployments, where a site will communicate with the enterprise frameworks at WAN speeds:

  • T1 (1.544 Mbits/s) is required, T3 (44Mbits/s) is optimal
  • Due to costs, it should be expected that fractional T1s may be deployed, but expect lower performance.

 

Display

1024X768, High Color (16 bit) minimum display

 

Display Adapter

ArtiosCAD 3D module requires a display adapter that is OpenGL and Direct-X compliant

ArtiosCAD 3D Designer, 3D Connection, and Animation require a display adapter with 128 MB or more video RAM.

The better the card, the better the 3D experience.
128 MB minimal required
256M optimal for lightweight 3D uses
1G for solid imports, animation

If CAD-X is used in a server environment, the graphics card still must match the memory requirement above. Serverclass machines generally do not have high quality or memory graphics cards as standard issue.

 

I/O Ports

USB port for optional ArtiosCAD Rubber Nesting feature if purchased

Mouse

3 button (2 button can be used with feature limitations)

Database

For the standard edition, ArtiosCAD installs Microsoft® SQL Server 2005 Express Edition by default
ArtiosCAD also supports:
    Microsoft® SQL Server 2008, including 64-bit version 2
    Microsoft® SQL Server 2005, including 64-bit version 3
    Oracle® versions 9i or greater

 

Notes:

Normal installation of ArtiosCAD products requires access to a DVD drive.

Typical ArtiosCAD installations can be Standalone (meaning no other systems are required for ArtiosCAD to work and no configurations are shared), Server (meaning it shares configuration, database, and license files with other machines on the network), or Standard Client (meaning it gets its configuration and license information from an ArtiosCAD Server on the network and shares a common database residing on that server). Custom installation allows distribution of ArtiosCAD Server functions to two or three machines.

Where the SafeNet® Sentinel® Superpro Driver is used to license ArtiosCAD it is required that a security dongle be placed on an ISA Parallel port or a USB port. PCI parallel ports, USB to parallel converters, etc. are not supported with the parallel key option.

 

1. Offical support of Microsoft® Window® 2000 has expired with the release of ArtiosCAD 7.4. As of 09/04/07 SolidWorks® did not support their SolidWorks® 2007 version on Microsoft® Windows® 2000 o/s. ArtiosCAD7.30 or higher will not load on a Microsoft® Windows® 2000 operating system if the SolidWorks Import/Export module is activated in the Feature Selection dialog window during ArtiosCAD installation.

2. Support of Microsoft® SQL Server 7 has expired with the release of ArtiosCAD 7.4.

3. Support of Oracle® 7.3.2, 8, and 8i has expired with the release of ArtiosCAD 7.4


 

ArtiosCAD 12 Enterprise Server

 Click here for the system requirements for ArtiosCAD 12 Enterprise Server.

 

 


 

ArtiosCAD 12 Enterprise Client

Esko ArtiosCAD Enterprise Minimum System Requirements


 

These are the minimum requirements for reasonable performance of the described products, with recommendations for optimal performance.  They will help you decide whether the equipment you are currently using remains viable. If you are considering new equipment, bear in mind that these requirements are minimum, not optimal. Exceeding these specifications will in general lead to enhanced performance.

 

Esko ArtiosCAD Enterprise 12            

CAD-X Enterprise 12      


 

Site Deployment options

  • Centralized configuration serving multiple plants and clients herein known as multiSite
    • In this configuration, the enterprise framework is deployed at a single site, allowing ArtiosCAD Enterprise 12 clients from anywhere in the company to access the centralized database via the corporate WAN network.
  • Centralized configuration serving single plant and multiple clients herein known as singleSite.
    • In this configuration, the enterprise framework is deployed at a single site, allowing ArtiosCAD Enterprise 12 clients from the same site to access the centralized database via the LAN network.
  • Enterprise framework installed on an individual system, herein known as singleClient… not yet supported
    • In this configuration, the enterprise framework and the ArtiosCAD Enterprise 12 client are installed on the same machine.

Client Operating System for ArtiosCAD client application:

 

  • Windows 7 Professional 32 & 64-bit with limitations.  See Release Notes.  Please note the Home and Ultimate editions should work as well, but it was the Home edition that was fully certified.
  • Windows Server 2008, 2008 r2 (64-bit) with limitations.  See Release Notes.
  • Windows Vista Business Edition with limitations 32/64 See Release Notes.
  • Microsoft® Windows® XP Pro SP2 or higher, 32 & 64-bit
  • Mac OS® X 10.4 /Parallels® Desktop 3.0 running on an Intel® Mac with Limitations.  See Release Notes.
  • Mac OS® X 10.4/VMWare Fusionv1.1.1 running on an Intel® Mac with limitations.  See Release notes.  VMWare Fusion is preferred over Parallels.
  • The following platforms may be used in an experimental mode.  They have been tested to a certain point but have not been certified for this release:
    • Mac Bootcamp

Operating system patches

Windows XP sp2 and Windows server 2003... http://support.microsoft.com/kb/319740 This patch will resource leaks when using Esko ArtiosCAD


 

Vista Business Edition… http://go.microsoft.com/fwlink/?LinkID=82148

This patch will install the help environment for running Esko ArtiosCAD help        

 


 

CPU:                                       

  • Architecture
    • To fully take advantage of the 3D Importer or Solidworks module, x86 64-bit processors are recommended, especially for multi-hundred M files. 
    • ArtiosCAD is still a 32-bit application.  All other uses other than 3D Importer or Solidworks (32-bit) modules will require a x86 32-bit processor.
    • Performance
      • multisite/singleSite:
        • Intel®  Core 2 Duo, 2.4 GHz, 2.4 GHz, required
        • Intel® Mac Intel® Core 2 Duo: 2.4 GHz, 2.4 GHz with VMWare Fusion® Desktop
        • singleClient:
          • Intel® Core 2 Duo:  2.4 GHz, 2.4 GHz, required
          • Intel®  Core 2 Quad, 2.4 GHz x 4, recommended


 

Memory

  • multisite/singleSite:
    • 2D design: 2G required, 4G recommended
    • 3D design(3D Designer, 3D Connection and Animation): 4G required
    • 3D import: 4G required, 4+G recommended
    • singleClient: 4G required

Disk Space

  • 20G for the ArtiosCAD application, including the local cache, and 500M available on the system partition.  If files are large and/or the cache contents are not purged regularly, you should consider more than 20G for the local disk.

Network

  • TCP/IP v4 required, TCP/IP v6 not supported
  • ArtiosCAD Enterprise 12 utilizes http as its core communication protocol.  For optimal performance, do not drop http to a lower quality of service (QOS), or at least ensure http traffic directed to the enterprise web server received higher network priority.
  • For singleSite:
    • 100 Base-T Ethernet required, 1G Base-T recommended
    • Wireless networks may be utilized, be keep in mind that 802.11b is 11Mbit/s which is really no better than 10 Base-T.  This may be used for casual use.  Recommended is 802.11g (raw 54 Mbits/s), or better 802.11n (expected 100Mbit/s)
    • For multiSite where a site will communicate with the enterprise frameworks at WAN speeds:
      • T1 (1.544 Mbits/s) is required, T3 (44Mbits/s) is optimal
      • Due to costs, it should be expected that fractional T1s may be deployed, but expect lower performance.

Display

  • 1024X768, High Color (16 bit) minimum display

Display Adapter

  • Esko ArtiosCAD 3D modules requires a display adapter that is OpenGL 2.1 and Direct-X 9 compliant
  • Video memory: 512M require, 1G recommended
  • Nvidia cards are recommended; on board adapters are not supported.


 

The better the card, the better the 3D experience.

Mouse

  • 3 button (2 button can be used with feature limitations) with scroll wheel

Drives

  • DVD ROM drive

I/O Ports

  • USB port for optional Esko ArtiosCAD Rubber Nesting feature if purchased

 

 

 

ArtiosCAD enterprise framework deployment:

There are three server processes that comprise the enterprise framework deployment:  web server, an application server (Jboss) and the database.  The Web server has two components: IIS and a servlet runner (Tomcat).

 

multiSite and singleSite deployments:

  • Minimum deployment is over two machines. 
    • In a secure DMZ environment for a web deployment, the web server must be deployed within the DMZ, leaving the application server and database to be deployed on a machine in the company network.
    • In a standard internal deployment with no DMZ and therefore no web deployment, the processes requiring the most resources will be the application server and the database server.  It is recommended that these two servers be split, leaving the web and application servers to run on one machine and the database server running on the other.  The application server and database server may run on the same machine provided it is a server class machine.
    • For optimal performance, it is recommended that the three server processes be deployed on three individual machines.  This is due to the fact that server processes such as these attempt to utilize as much memory as possible.  Separation will reduce the contention for memory and CPU access when the system is busy with concurrent users.

For singleClient deployments, all three server processes are installed on the same machine.  This is normally fine as there will be only one user accessing the framework at any one time.

Server Operating Systems for ArtiosCAD enterprise framework:

  • Microsoft® Windows® Server 2008 R2 (64-bit), SP2 32 & 64 bit
  • Microsoft® Windows® Server 2003 SP2 32 bit
  • The windows Server 200x SBS, Web Server and HPC (for 2008) editions have not been certified.

Database

  • Microsoft® SQL Server 2008, 32 & 64-bit
  • Microsoft® SQL Server 2005, 32 & 64-bit
  • Microsoft® SQL Express 2005, SQL Express 2008 for DBs no larger than 4G
    • Storing files in the database can not be used with the SQL express versions
    • Oracle® versions 9i or greater

CPU

  • Architecture: Tomcat and Jboss are java-based servers are inherently 64-bit.  They should run fine in 64-bit environments.   x86-32 bit processors are required, x86-64 bit processors are recommended to allow for memory beyond 4G.
  • 10 concurrent users:
    • Web server, application server, database on separate machines: required Intel® Core 2 duo core, per server
    • Web server/application server, database on two machines: required Intel® Core 2 duo core, per server
    • Web server, application server/database on two machines for DMZ:
      • required Intel® Core 2 duo core, per server
      • optimal Intel® Core 2 quad core for application server/database
      • Web server, application server, database on same machine: required Intel® Core 2 quad core
      • 20 concurrent users:
        • Web server, application server, database on separate machines: required Intel® Core 2 duo core, per server
        • Web server/application server, database on two machines:
          • required Intel® Core 2 duo core, per server
          • optimal Intel® Core 2 quad core for database server
          • Web server, application server/database on two machines for DMZ:
            • required Intel® Core 2 duo core for Web server
            • required Intel® Core 2 quad core for application server/database
            • Web server, application server, database on same machine: required Intel® Core 2 quad core
            • 50 concurrent users:
              • Web server, application server, database on separate machines:
                • required Intel® Core 2 duo core for Web server
                • required Intel® Core 2 quad core for application server and database
            • Web server/application server, database on two machines: required Intel® Core 2 quad core, per server
            • Web server, application server/database on two machines for DMZ:
              • required Intel® Core 2 quad core for Web server
              • required Intel® Core 2 quad core for application server/database
            • Web server, application server, database on same machine: not recommended

Memory

  • 10 concurrent users:
    • Web server, application server, database on separate machines: 4G per server
    • Web server/application server, database on two machines: 4G per server
    • Web server, application server/database on two machines for DMZ: 4G per Server
    • Web server, application server, database on same machine: 8G
    • 20 concurrent users:
      • Web server, application server, database on separate machines: required 4G per server
      • Web server/application server, database on two machines:
        • Required 4G per server
        • Optimal 8G for database
        • Web server, application server/database on two machines for DMZ:
          • Required 4G for Web server
          • Required 8G for application server/database
          • Web server, application server, database on same machine: 16G
          • 50 concurrent users:
            • Web server, application server, database on separate machines:
              • required 4G per Web server
              • required 8G for application server and database server
            • Web server/application server, database on two machines: 16G per server
            • Web server, application server/database on two machines for DMZ:
              • required 16G per Web server
              • required 24G+ for application server/database server
            • Web server, application server, database on same machine: not recommended

Disk Space

  • Web Server
  • Application Server (filestore, Index)
    • Files stored in database as BLOBs- 50G
    • Files stored in disk filestore- required: 100-200G, more depending on number and size of files
    • Database Server
      • Files stored in database as BLOBs-- required: 100-200G, more depending on number and size of files
      • Files stored in disk filestore - 50G

Network

  • 100 Base-T required between server machines, 1G Base-T optimal.

I/O Ports

  • For new Esko ArtiosCAD Enterprise 12 users, no key is required, else USB key on applicaton server.

VMWare ESX   

Has not been certified by Esko, however, there are no known limitations.  To use ESX, the ESX server should be specified as to be able to guarantee the processing power and memory allocation for each of the individual servers the ESX server may host.                       

Notes 

Normal installation of Esko ArtiosCAD products requires access to a DVD drive.

           


 

 

Notes 

  1. Although we don't expect issues with Microsoft OS patches, Esko only guarantees support on the official MS Service Pack (SP)level, not on individual OS patches. PC's for Esko applications (editors, rips or servers) must not be configured as WebServers (IIS), Network Domain Controllers (Active Directory), DNS Server, DHCP Server, WINS Server, SQL Server,  or MailServer. The Automation Engine Server is allowed to be a Member Server in a Windows Active Directory domain. However, Esko can not test all possible configurations. Contact your regional Customer Service Center in case of specific questions.
  2. Microsoft Windows Server Client Access Licenses: Make sure to purchase enough CAL's as required by the workflow (client PC, client Mac, Rip, Data server, etc...).
  3. The Automation Engine server and it's Assistant server should be dedicated Computers, no other software (both Esko (eg: FlexRip, FlexProof) and non-Esko) shall run on this machine.
  4. A single processor with hyperthreading enabled is considered as 2 processors for memory calculations. A dual core processor is considered as 2 processors for memory calculations.
  5. Esko software will only work with properly licensed versions of operating systems and other software. Esko is not responsible for any loss of functionality due to use with unlicensed software. Esko will not provide assistance in installing software on equipment lacking properly licensed software.