Connection Mapping in the Configuration File

The configuration file that is referenced by the batch load application is a straightforward xml file that defines the parameters for the batch load activity. The configuration file is used to configure the Aras Innovator server and data source, as well as the process parameters. The following describes the different parameter tags that are included in the XML configuration file.

<BatchLoaderConfig>
<server>http://localhost/InnovatorServer</server>
<db>InnovatorSolutions</db>
<user>admin</user>
<password>innovator</password>
<max_processes>1</max_processes>
<threads>1</threads>
<lines_per_process>250</lines_per_process>
<delimiter>\t</delimiter>
<encoding>utf-8</encoding>
<first_row>2</first_row>
<last_row>-1</last_row>
<log_file>C:\User</log_file>
<log_level>3</log_level>
<certStoreLocation>CurrentUser</certStoreLocation>
<certStoreName>My</certStoreName>
<certFindType>FindBySubjectName</certFindType>
<certFindValue>SomeSubjectName</certFindValue>
<certValidOnly>true</certValidOnly>
</BatchLoaderConfig>

The only parameter defined in the configuration file that cannot be defined in the command line is the delimiter. Any other parameter tag may be left out of the configuration file.

• server – The connection URL for Aras Innovator. If all the defaults were taken during the Aras Innovator installation, the path should be something such as: http://localhost/InnovatorServer. If unsure, check in IIS to get the exact path. This URL should not include reference to the /Client folder
• db – The database to which the data is loaded. Selecting this field after defining the connection URL makes this a pick list of available databases.
• user – The user login to be used for connecting to and loading data into the database.
• password – The user password in plain text.
• max_processes – The number of worker processes to be used by the Batch Loader while loading data. Recommend using the default of 1.
• threads – The number of threads per worker process. Recommend using the default of 1.
• lines_per_process – The number of lines in the data file that are loaded by a single worker process. If the worker process reaches the end of its line and the data file has not completed processing, then a new worker process is started.
• delimiter – the delimiter used to separate data, usually a tab (\t), or a space ( ), or a comma (,).
• encoding – Encoding (or codepage number) of data file
• first_row – The number of the row where the actual data starts. Sometimes the first row is used for row headings. In that case, the data starts in the second row. (See FirstRowIsColumnNames property below.)
• last_row – The number of the row where the actual data stops. Default of -1 indicates that the file should be read until the end of the file
• log_file – The fully specify the name of the log file where all information and errors are to be written by the Batch Loader.

• log_level – The level of detail included in the logging.

  • 1 - Low, recommended for automated jobs with low risk on failure. Details about start and stop, and how many items succeeded.
  • 2 – Medium, recommended for use while developing new Batch load job. Logs details about failure, as well as details logged in low mode.
  • 3 – High, recommended for debugging. Provides detail and AML about every line loaded.
• certStoreLocation – the name of the certificate’s store location (CurrentUser, LocalMachine) used for Client Certificate Authentication.
• certStoreName – the name of the certificate’s store used for Client Certificate Authentication.
• certFindType – the type of a search criteria that will be used to find a client certificate in the specified store. Here is the list of available values: https://docs.microsoft.com/dotnet/api/system.security.cryptography.x509certificates.x509findtype?view=net-6.0
• certFindValue – the value of a search criteria that will be used to find a client certificate in the specified store.
• certValidOnly – parameter that determines whether to accept only valid certificates (true) or any certificate (false).

You can also specify the data about the client certificate in the ‘blworker.exe.config’ file. In this case additional CLI or configuration parameters are not required. There is an example of the file’s content below:

<configuration>

  <configSections>

    <sectionGroup name="Aras">

      <sectionGroup name="Net">

        <section name="RequestProvider" type="Aras.Net.Configuration.RequestProviderConfigurationSection, IOM"/>

      </sectionGroup>

    </sectionGroup>

  </configSections>

  ...

  <Aras>

    <Net>

      <RequestProvider>

        <providers>

          <provider uriPattern=".*">

            <ClientCertificate>

              <certificate sourceType="CertificateStore" storeLocation="CurrentUser" storeName="My" findType="FindByThumbprint" findValue="71f942b0710faa873d1d3de2a9815b3321604d5a"/>

            </ClientCertificate>

          </provider>

        </providers>

      </RequestProvider>

    </Net>

  </Aras>

</configuration>