Provides options for configuring settings for the Intergraph Smart 3D Integration Service. You must configure this service before it is enabled. When you enable this service, existing objects in the model are shared and changes such as new or modified objects are processed. The resulting data can then be viewed in SDx and made available for downstream enterprise applications and Integration models.
You also have the option of using a command-line executable to configure settings for these services. See Command-line option to configure SDx integration settings.
Specifies the name of the system on which you are running the Integration Service. The setting is required when you configure the Integration Service. To specify a different server, you must first stop the Integration Service.
If you open the Integration Service settings on a remote server, the following options are unavailable and cannot be modified: User Name, Password, Subscriber Name, Process Notifications from, Max Number of Parallel Processes (for Service Bus Notification), Verbosity, and Log File Location. These options are only available if the server is a local machine.
Scheduled Synchronization to SDx
This service can be turned on or off for the selected model. The default state is on.
Max Number of Parallel Processes to Use per model
Specifies the maximum number of parallel processes used to synchronize data to SDx. The value that you enter must not exceed the maximum number of processors on the machine where the service is run.
Query Interval for objects [minutes]
Specifies the default timing for querying the database for modifications (add, modify, and delete operations). The Intergraph Smart 3D Integration Service uses this setting.
Local Log File
The local log file is used to analyze and monitor the Intergraph Smart 3D Integration Service.
Specifies the level of detail and number of messages to monitor and send. Keep in mind that the more detailed levels for a local log file can impact system performance. Select the message type from the list.
Logs messages that track the general flow of the application and can provide long-term value.
Logs messages that highlight an abnormal or unexpected event in the application flow, but do not otherwise cause the application to stop.
Logs messages that highlight only when the current flow of execution stops because of a failure. These messages indicate a failure in the current activity, not an application-wide failure.
Logs messages that describe only unrecoverable application or system crashes, or a failure that requires immediate attention.
Turns off monitoring and error logging.
Log File Location
Specifies the location in which the service generates a log file. You must specify a folder with write permission. If you do not specify a folder, the software writes the log file to the %temp% folder. You can use this log file location as an alternate monitoring and logging solution if you do not want to use Azure, or as a backup if you encounter connection issues with Application Insights.
These settings enable you to send analytics and messages to Microsoft Application Insights, which is a feature of Azure Monitor that monitors live applications. We recommend using Application Insights to monitor the Intergraph Smart 3D Integration Service.
Specifies the level of detail and number of messages that can be reported. Select the message type from the list. The available types are Information, Warning, Error, and Critical. Select Off if you do not want to send messages to Azure.
Specifies the Microsoft Application Insights instance to log messages and metrics for the Intergraph Smart 3D Integration Service. Copy and paste the key from the Application Insights resource Overview page through your Azure Portal. This option is not available if Verbosity is set to Off for Application Insights.
Discards your changes and displays a confirmation message.
Saves the specified settings and closes the dialog.