The scServer.scs file, which is written to the service’s run directory, contains information that is used to connect the participants to the coupling service. This file is generated shortly after the coupling service is started, and indicates that the coupling service is ready to receive connections from the co-simulation coupling participants.
This text file contains the following lines of data:
The coupling server's port and host, separated by an ‘@’ character.
A block containing the number of co-simulation participants connected to the System Coupling system in the Workbench schematic, and their unique and display names. In the Workbench environment:
the unique names are automatically generated and are
reported as the ComponentID in the Properties
view of the co-simulation participant’s Solution cell,
the display names correspond to the names (which you are able to specify) below the participant’s system
The licensing ID of the System Coupling analysis
The license server's port and host, separated by an '@' character, at which the coupling participant codes (i.e., solvers) can reach the license server
12345@CouplingServer.mydomain.com !Coupling server’s port and host
2 !Number of co-simulation participants
Fluent !Participant 1 Unique Name
Fluent Solver Display Name !Participant 1 Display Name
Ansys !Participant 2 Unique Name
Ansys Solver Display Name !Participant 2 Display Name
12345 !Licensing ID of the System Coupling
Analysis
54321@LicenseServer.mydomain.com !License server's port and hostNote: When the participants are started and instructed to connect to the running SC Service,
they must connect to the service using the unique names (for example,
Fluent and Ansys in the example
above).