Overview - Intergraph Smart Materials - Version 10.1 - Installation & Upgrade - Hexagon

Intergraph Smart Materials Installation (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Installation & Upgrade
Smart Materials/Smart Reference Data Version
10.1

Smart Materials communicates with ISL each time

  • a user logs on,

  • a user opens a new screen (if the license module changes),

  • or a user closes the application.

The software sends a request to the license pool to hand over the seat for the specific module. The image below shows how the interaction between the different layers and components works.

SBCSArchitecture

The numbers in the picture refer to the numbers in brackets below.

(1) The license-handling interaction starts when you open an instance of the Smart Materials application, or when you open a new screen or page in a running application which belongs to another license module, or when you close the application window. The application makes a call to a webservice (3) on the Smart Materials application server. The client technology can be a Java applet, a .NET WinForms application, Silverlight or WPF type, or it can be a plain browser for BIR/APEX.

The BIR/APEX client (2) is a special case, because BIR can run in a browser without plug-in, based on HTML5. This way, it can run from almost any device and can directly communicate with the database layer (5) if the database is setup to accept BIR/APEX requests. BIR/APEX requests can also be routed through a web server, which is the recommended architecture.

Depending on the type of client technology, there are different webservices (3) to communicate to the related middle tier-business logic (4) (and there are also multiple webservices for the same technology). Inside each webservice, there might exist multiple processes which work on parallel calls for the methods that a webservice offers.

Certain features of the program are contained in the modules of the business logic (4) which are again specific to the technology. The server applications with the webservice and the business logic in it, can be hosted on different physical machines one for each technology, or they may share the same node. However, business logic usually opens a connection to the database (5) to get or set data there, or to call business logic that is running on the database layer (5). When the database connection is established, licensing comes into picture. Any user session in the database is counted and checked against a keystore in the cloud - if necessary.

To request an ISL seat, the database consumes an operation of the license webservice (6). This special webservice runs independently of the other webservices (3) that exist for WPF, Oracle Forms, WinForms, and so forth. The license webservice calls out to the ISL client (7), which offers methods to get seats from and return seats to the keystore. The license webservice needs to be on the same node as the ISL client but can be on a separate machine than the rest of the Smart Materials/Smart Reference Data server applications.

The cloud-based services (8) will answer the request and request or return the license seat from a keystore. The answer is routed back to the database process (5). Its business logic will in turn pass a message back to the application server, which will inform the client. The client can display an alert to the user, for example, in case the maximum number of seats was exceeded.