The basic steps to create or enable an application to connect to Fluent as a Server are:
Using a CORBA-Aware Language
Install a CORBA-compliant ORB implementation suitable for the development environment in which you will be creating your client application.
Use the compiler included with your CORBA implementation to compile the Fluent as a Server interface modules from the Interface Definition Language (IDL) file. The IDL file is located in the following location in the ANSYS install tree.
v182\fluent\fluent18.2.0\addons\corba\ |
Create your client project and include the AAS_CORBA module created in the previous step. Refer to Fluent as a Server CORBA Interfaces for details about the interfaces contained in the AAS_CORBA module.
The specific source code to use the provided interfaces will depend on your development language and requirements. In general, a useful client application will:
instantiate a CORBA object
pass the IOR string contained in the Fluent as a Server session’s keyfile to an ORB method to create an ICoFluentUnit object
use the methods provided in ICoFluentUnit and/or ICoFluentSchemeController to load a case file, send commands, or retrieve output from the remote Fluent session.
See Fluent as a Server CORBA Interfaces for details about these interfaces and the provided methods.
Start a Fluent as a Server session on a remote machine that is accessible from the client machine (see Fluent as a Server Session Management).
Use the keyfile created by the remote Fluent as a Server session to connect your client application to Fluent.
Using .NET Framework
Create your client project and include
DotNetCoFluentUnit.dll. Refer to Using the Pre-Built .NET
Connector for details.
The specific source code to use the provided interfaces will depend on your development language and requirements. In general, a useful client application will:
Create a DotNetCoFluentUnit object.
dotNetCoFluentUnit=DotNetCoFluentUnit()
dotNetCoFluentUnit.ConnectToServerFromIorFile('aaS_FluentId.txt')use the methods provided in DotNetCoFluentUnit
and DotNetCoFluentSchemeController to load a case
file, send commands, or retrieve output from the remote Fluent
session.
See Using the Pre-Built .NET Connector for details about these classes the provided methods.
Start a Fluent as a Server session on a remote machine that is accessible from the client machine (see Fluent as a Server Session Management).
Use the keyfile created by the remote Fluent as a Server session to connect your client application to Fluent.