The name of the command-line executable is ConfigureSDxIntegrationSettings.exe, and
the input is the path of an .xml file that contains all required configuration attributes
for integration settings. Smart 3D provides a sample .xml file located under the Smart 3D installation folder in the Core\Container\Bin\Assemblies\Release\SDxIntegrationSettings.xml
folder.
See the example command-line entry below in which the .xml file you created is located
in a C:\Smart3D\SDxConfig folder.
The following sections describe the required and optional settings to define in your
SDxIntegrationSettings.xml file.
dbinstancename
Specifies the name of the server on which your Smart 3D site database resides.
sitename
Specifies the name for the configured Smart 3D site database to access.
siteschemaname
Specifies the schema name of the site. The format is to append the sitename with "_SCHEMA".
dbprovidertype
Specifies the type of database, either Oracle or MSSQL.
modelname
Specifies the name of the model that contains the 3D objects making up your model.
Required:
configurationserver
Specifies the name of the system on which you are running the Intergraph Smart 3D Integration Service.
Verbosity
Specifies the level of detail and number of messages that can be reported. Define
Verbosity for one or both target logging options described below.
-
You can set up Application Insights, a feature of Azure Monitor, to be used by the Integration Service to monitor and report system messages. Application Insights provides rich analytics support and monitoring capabilities with minimal impact to
client system performance. By default, the verbosity for Application Insights is set to Information to capture the highest level of details about errors and exceptions. To set up an
Application Insights instance, see Microsoft Azure Documentation.
You can also set up a Local Log File if you do not want to use Application Insights, or for use as a backup in case of internet, network, or Azure outage issues. The Local Log File default verbosity setting is Error.
Select one of the following logging levels listed from highest or more detailed to
lowest. Keep in mind that the more detailed levels for a Local Log File can impact system performance.
Information
Logs messages that track the general flow of the application and can provide long-term
value.
Warning
Logs messages that highlight an abnormal or unexpected event in the application flow,
but do not otherwise cause the application to stop.
Error
Logs messages that highlight an abnormal or unexpected event in the application flow,
but do not otherwise cause the application to stop.
Critical
Logs messages that describe only unrecoverable application or system crashes, or a
failure that requires immediate attention.
Off
Log messages are not generated, processed, or persisted.
logverbosity
The default value is 4.
appinsightsverbosity
The default value is 6.
logfilelocation
Specifies the location in which the service generates a log file. The generated log
file name is taken from the individual service. The log file contains error information
and uses the severity level defined by Verbosity.
Instrumentationkey
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.
Optional (Integration)
Status
Indicates the start and stop service for the model.
True = ON (default value)
False = OFF
queryintervaltime
Specifies the number of minutes the service waits before it checks the database for
any added or modified objects. Provide a value in minutes that is greater than zero (0). The default value is 3 minutes.
maxprocesses
Specifies the maximum number of parallel processes that the service can perform independently
at any given time. The value that you enter must not exceed the maximum number of
processors on the machine where the synchronization process is run. The default value
is 1.
If the configuration server is remote, make sure the Integration Service is installed
on the remote server.
Before you define attribute settings and run the command, it is recommended that
you make a copy of the delivered sample .xml file and move the copy to a different
folder location. When you run the command-line, specify the new location. This prevents
the .xml file from being overwritten during any Smart 3D upgrade processes.