License Admin creates one default configuration connection information (cci) file for the ISL-Client machine (which is the computer where our SBCS license service runs).
The cci file is loaded into ISL-client on device level, which means it is valid for all users. The client config must contain one or more projects, of which one must be determined to be the fallback project. This is the project pointing to the keystore(s) which Smart Materials/Smart Reference Data sessions are going to use. Normally, you will not be able to login to the application, until you have assigned any fallback project to the cci-file.
You may use the site-based configuration in the licensing portal, which is a shortcut for creating ISL projects "manually".
The Smart Materials software makes no use of environment variables on the machine to be threadsafe on parallel calls.
Theoretically a License Admin could create projects in the client config with their names matching the Smart Materials project names. The ISL Client would then automatically access the keystores attached to that license project.
This approach to distribute seats on project level is not reliable. In Classic this will work, but not all of our other applications are logging in with the project information and changing the project later will not automatically redraw licenses. Furthermore, it would be additional effort to update the client config when a new Smart Materials project is started.
Thus, working with a fallback project is the best practice.
The following chapters describe two different special cases:
-
Customer Hosted Licensing Configuration
-
Specific Keystores Configuration