Installation Terminology

Process Composer drives the execution of simulation applications on 3DOrchestrate Station machines.

Process Composer is part of the simulation workflow infrastructure of the 3DEXPERIENCE platform. Process Composer users access the application via web browsers on their client machines.

3DSpace MCS

This Java EE application is the foundation of the 3DEXPERIENCE platform. It is responsible for all communication with the database. Process Composer is a web application installed into the 3DSpace framework.

3DOrchestrate Stations

3DOrchestrate Stations are the machines that run Process Composer jobs. The simulation applications required to run a Process Composer job—Abaqus or Hypermesh, for example—must be available on a station computer.

This guide refers to various directories in which component software is installed.

The installation instructions refer to the following directories:

• collaboration_server_dir: The path to the 3DSpace MCS installation directory.
• vpm_dir: The path to the directory in which you installed ENOVIA VPM Multi-Discipline Collaboration Platform on the collaboration server machine.

• pc_dir: The path to the directory in which you install Process Composer, Performance Study, Simulation Companion, and Results Analytics on the collaboration server machine. For example, on a Linux system this path could be

  /opt/ds/server/Apps/SimProcessIntelligence/version/

  and on Windows it could be

  C:\ds\server\Apps\SimProcessIntelligence\version\

• appserver_dir: The path to the 3DSpace MCS deployment directory within the application server directory. For Apache TomEE on UNIX/Linux, for example, this could be /opt/apache-tomee-1.5.1/webapps/enovia/. On Windows it could be C:\apache-tomee-1.5.1\webapps\enovia\.