Define SBCS Settings - Intergraph Smart Materials - Version 2020 (10.0) - Installation & Upgrade - Hexagon

Intergraph Smart Materials Installation (2020)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Installation & Upgrade
Smart Materials/Smart Reference Data Version
2020 (10.0)

On the A.60.81 License screen, you can find the Session based check Smart Licensing tab where you can enter data relevant for licensing.

A6081SBCS

The data can be retrieved from the database using the Read Parameters button, and sent to the database using the Save Parameters button. When you open the screen, Read Parameters is run automatically for each of the fields that is empty. Clicking the Save Parameters button saves the changes without asking for confirmation.

The License Service field contains the URL of the license service, which processes the seat transfer from and to the keystore. The URL must contain the application server name, optionally with domain name and port number, and the virtual path, the license service is listening on.

The standard format of the license service URL is as follows:

<servername><.domain if required>/<productPath>/service/home

The <productPath> is determined by the version of the installation. For 2020 (10.0) version it is:

SmartMaterialsLicenseWebservice2020/SmartLicensingService

A typical license service entry can look like the following:

myWebServerName/SmartMaterialsLicenseWebservice2020/SmartLicensingService/service/home

In this URL, myWebServerName must be replaced by the host name used on customer side.

The URL entered in license service field does not need to be prefixed by http://, it can start with the servername.

When a license service entry is available in A.60.81, the software checks if a Smart Licensing project is specified in any of the two Keystores fields. If yes, the software tries to pull a seat from one of the keystores which are related to this project. Project assignment on user level (User Keystores) overrides the system-wide entry. If no project name is present in both of the Keystores fields, the value will be taken automatically from the Smart Materials project or product group name sent with the license request. Normally, we don’t expect customers to maintain ISL projects with same name as Smart Materials projects. Thus, the fallback project of the client configuration will serve as pointer to the keystores.

If Admin enters a database-wide license project in A.60.81, this will supersede the fallback ISL project (as well as the logged in Smart Materials projects with matching names), and itself will be superseded by user specific assigned license project (A.60.81, A.20.05). If not superseded, the database-wide license project name would be used in request and in telemetry.

If you are not using customer hosted licensing, the field can remain empty. In this scenario, ISL will check the Smart Materials project or product group name sent with the license request.

User Keystores: There also exists a field Keystores in the user management on A.20.05. The same data can be maintained in the User Keystores field of A.60.81 as well. Both screens refer to one value. That value overrides this system-wide value, if available. This way it is possible to assign different keystores to different users, based on the requirements of the customer-hosted-licensing implementation. The value in the Keystores field is not the name of the keystore, but the name of an ISL-project which points to a keystore in the cloud.

For more information, see Configure ISL Client and How Smart Materials determines the Keystore.

In the Log Message Level field, you specify the system-wide log message level for license and logon tasks. The entered value must be in a range 0 to 99. The higher the number, the more messages are inserted in the table that logs the license related actions. 0 indicates that only most important messages (including fatal errors) are added to the log. If you set the level to 5, additionally warnings are inserted, and 10 is the most silent information level. If you keep the field empty, log entries are not produced.

If you set the message level on the A.20.05 Users screen, this level is applied instead of the system-wide level if the user dependent value is higher. The user dependent value can also be maintained in the User Log Message Level field on A.60.81.

In the Log Message Level Job field, you specify the log file message level for the license clean-up job (see Clean-Up Job). The entered value must be in a range 0 to 99. The higher the number, the more messages are inserted in the table that logs the license related actions. 0 indicates that only most important messages (including fatal errors) are added to the log. If you set the level to 5, additionally warnings are inserted, and 10 is he most silent information level. If you keep the field empty, log entries are not produced by the clean-up job.

Before a module license seat can be requested from ISL, the steps described in the following chapters have to be performed.