Understanding Application Connectors

OS Command steps use application connectors to run external applications from within Process Composer.

See Also
Assigning an Application Connector

Application connectors are used by OS Command steps to run external applications. Process Composer provides application connectors for the Abaqus products and for transferring files in and out of Process Composer. In addition, the Simulation Methods Developer can create application connectors for any additional applications that you use at your site. The Simulation Methods Developer can also create application connectors for custom applications, such as Python or Perl scripts or compiled C++ or Fortran programs.

Application connectors are used by OS Command steps to replicate how you communicate with an application through the command line. Therefore, application connectors can be developed for any application that can be driven from the command line. An application connector can run an application directly. Alternatively, an application connector can run a wrapper script that acts as a layer between Process Composer and the application and allows them to communicate.

Importers and Exporters are a type of connector that are referenced by import and download rules, respectively. An Importer allows you to move data into the database, such as a mesh that was created by a third-party product. An Exporter allows you to move data from the database to an external application.

Several pieces of information are necessary when defining an application connector:

  • The name and the version of the application; for example, HyperMesh Version 8.0.
  • Options or arguments that are passed from the connector to the application.
  • PLM attributes, such as the lifecycle state and the revision of the connector.

The Abaqus connectors are created for you with a standard installation of Process Composer. The Abaqus connectors allow your simulation activities to work with Abaqus applications and files.

The lifecycle states of a connector are Private, Development, Complete, Released, and Obsolete. The following rules apply to these lifecycle states:

  • The Simulation Methods Developer must grant read access to make it available to a Simulation Analyst.
  • The Simulation Methods Developer can edit a connector only in the Development state.
  • The Simulation Methods Developer cannot demote the state from Complete or Released to Development if the connector is used in a simulation process or simulation activity.
  • The Simulation Methods Developer should not promote the connector to the Complete state until it is complete and has been tested. The connector cannot be modified in the Complete state, and it cannot be demoted after it has been assigned to a simulation activity.
  • To modify a connector that has been promoted to the Released state and assigned to a simulation activity, you must create a revision of the connector, modify the revision, and assign the revision to the simulation activity.

When you select an application connector in the table page, you can click Where Used in the navigation pane to see a list of simulation activities that use the connector and to which you have read access.