To configure the Smart 3D Admin API application settings, you use the Configuration Utility's Smart 3D Admin Web Server page, application settings sections.
These settings can be different for each API.
Go to the Smart 3D Admin Web Server page > Web Server Information sections
-
On the machine you want to use as the Admin API web server, open the Configuration Utility:
Start > Intergraph Smart 3D > Web API Configuration Tool
-
On the Welcome page, select Setup Admin Web Server.
-
Click Next until the Smart 3D Admin Web Server page shows the Cross-Origin Resource (CORS) section at the top.
Be sure you're on the Smart 3D Admin Web Server page and not the Smart 3D Plant Web Server page.
Configure application settings
-
Make changes in the Cross-Origin Resource Sharing (CORS), Flatten Metadata, Application Settings, and App Insights sections, as follows.
Clicking Reset will change the values back to the default in these sections only. If you returned
to this page (by clicking Back) and click Reset, it will not reset the application settings values in the later sections.
CORS section:
Setting
Description
Default value
Allowed Origins
The list of origins allowed access to the resource. The list may consist of one or more URIs, or a wild-card (*) can be used to allow access to all origins.
*
Allowed Methods
The list of methods supported by the resource. The list may consist of one or more HTTP methods. If the list is empty, then CORS preflight requests are not supported.
Supported request methods are GET, POST, PUT, DELETE, and PATCH.
GET,POST,PUT,
DELETE,PATCHAllowed Headers
The list of HTTP headers supported by the resource. The list may consist of zero or more header field names, or a wild-card (*) can be used to allow all headers.
*
Exposed Headers
The list of exposed headers that the resource might use and that can be exposed. The list may consist of zero or more header field names.
No default value
Allowed Credentials
Value indicating whether the resource supports user credentials in the request.
false
Preflight Maximum Age (Seconds)
The number of seconds the results of a preflight request can be cached on a client in a preflight result cache.
600 seconds
Flatten Metadata section:
Setting
Description
Default value
Allowed Clients
The list of client IDs for which to generate the flat metadata document.
No default value
-
Click Next to continue with the Application Settings and Application Insights sections.
Clicking Reset will change the values back to the default in these sections only. It will not reset the application settings values in the previous sections.
Application Settings section:
Setting
Description
Default value
Allowed Hosts
The list of hosts allowed to access the resource. The list may consist of one or more URIs, or a wild-card (*) can be used to allow access to all hosts.
*
Default Page Size
The maximum number of records returned in a response.
100
Maximum Allowed Page Size
The maximum page size that will be honored in the odata.maxpagesize header preference.
Pages that are larger than the maximum page size are reduced to the maximum size.10,000
Cache Timeout (seconds)
Responses to the asynchronous URL are stored in the cache. To access the response, you use the Location URI in the response header.
This setting is the length of time the response remains in the cache after you fetch it.
Increasing the time will cause the cache to grow.900 seconds
Request Timeout (seconds)
When a URL is submitted to the web server, the web server in turn submits a request to a Smart 3D process to execute the URL.
This setting is the length of time the web server waits for the request to complete. If the request takes longer, the caller receives a timeout error.250 seconds
Long Running Request Timeout (seconds)
When a POST is submitted to the web server, the web server in turn submits a request to a Smart 3D process to execute the URL.
This setting is the length of time the web server waits for the request to complete. If the request takes longer, the caller receives a timeout error.86400 seconds
App Insights section:
Setting
Description
Default value
ConnectionString
Establishes a connection between your application and Azure Application Insights. It contains the necessary information to identify your Application Insights resource, such as the instrumentation key and other configuration settings.
No default value
If you made changes to an existing website, you must restart the website for the
configuration changes to take effect.