3DOrchestrate provides a scripting API that lets you control how 3DOrchestrate performs submit, kill, and status operations that work with your DRM system.
The scripting API can work with most job scheduler systems including:
- IBM Platform LSF (Load Sharing Facility)
- Portable Batch System (PBS)
- Slurm Workload Manager
- Oracle Grid Engine (previously named Sun Grid Engine (SGE))
- Windows HPC
You can use a scripting language such as Perl or Python, or Linux shell scripts if desired.
The script-based API is meant for use with your on-premises installation of 3DOrchestrate, the 3DEXPERIENCE platform, and your DRM system. This feature lets you retain your experience and investment in the DRM system.
You work with the DRM scripting interface in three ways:
- Set properties in the SMAExeServer.properties file to configure your DRM system for a particular 3DOrchestrate Distribution Server.
- Write scripts that use the API.
- Create an XML file describing the custom DRM options you want to make available to your end-users in the simulation client apps' UI. For more information, see Customizing the UI DRM Options for Users.
To enable the customized 3DOrchestrate-DRM execution, ensure that the following guidelines are met:
The 3DOrchestrate Distribution Server must be able to execute your submit, kill, and status scripts.
If these scripts need to execute commands from the DRM system, then the 3DOrchestrate Distribution Server machine must be a "submission host" for the DRM system. In other words, the 3DOrchestrate Distribution Server application is usually installed and running on the head node of the cluster.
The submit script must be able to send the job to the DRM scheduler by whatever means necessary. For example, the IBM Spectrum Application Center (formerly Platform Application Center or PAC) can be used to submit jobs into LSF from any host machine, even one that is not part of the cluster. This system uses web service calls .