Checkpoint 5: Smart 3D Plant Web Server page - Intergraph Smart 3D Web API - Update 2 - Installation & Upgrade - Hexagon

The Smart 3D Plant Web Server page appears after you configure messaging and, if necessary, start the Windows service.

You'll use the Next button to move through all the sections on this page.

What happens now

You configure the following for the Smart 3D Plant Web Server:

• Server information - Site, application, HTTPS, and Base URL settings

• Authorization details - Authorization server URL and audience credentials

• Application settings - Settings that govern how the application works, for example, Cross-Origin Resource settings (CORS), metadata flattening, server timeout, and caching

Good to know

• You can use the same web server for both APIs.

• It is possible, but not recommended, to use different authorization servers for each API.

• With the exception of the application pool, the information you enter in these sections will be used as the defaults for the Smart 3D Admin Web Server. (Alternately, if the Admin API is already configured on this machine, you will see that information as the default here.)

• Each API must use a separate application pool.

• The Configuration Utility relies on the DefaultAppPool application pool to create the IIS site. If an application pool with the name DefaultAppPool does not exist, it must be created.

• The Application Pool Identity must have Modify permissions for web server files.

• If you are using Windows Authentication to access the configuration database, the Application Pool Identity must have access to the database where the configuration information is stored.

• For the Application Pool Maximum Worker Processes setting in IIS, we recommend keeping the default setting of 1. However, if you are using Redis for caching, you can increase the number to help manage extreme load conditions if necessary.

  The Application Pool Maximum Worker Processes value is found in IIS, under the Advanced Settings for the application pool.

• If you are making changes to APIs already configured on this machine, be sure that you:

  • Do use the same audience credentials to register the API in the authorization provider.

  • Do not register the service as new with the authorization server.

  Be careful when making changes to APIs already configured on this machine. You could cause configuration problems that are hard to fix.