Batches for automatic web updates

1. GENERAL INFORMATION

The continuous enhancement and improvement of its program features is what distinguishes the BMD NTCS software. 
For this reason, you are periodically provided with the latest program patches for your version.

1.1. What does the version number mean?

Let us have a look at the structure of the BMD NTCS version number using the example 2022.25.01.06.
2022 = the calendar year of the version in use
.25 = the internal major version number which is incremented by one every year. BMD NTCS is therefore in the 25^th year of its development.
.01 = the minor version number, in this case 01, that indicates the calendar week in which this version was initially created.
.06 = the patch number. This consecutive number indicates the changes of the respective minor version.

Only patches can be installed via web update. In order to install a different minor or major version, you need an update medium (DVD, USB flash drive) or alternatively an ISO file.

1.2. What are the prerequisites for a successful download?

An HTTP and HTTPS connection to the following addresses must be possible:

https://www.bmd.at/ntcsupdate/BMDNTCSUpdateWS.dll/soap/IBMDSOAPNTCSUpdate 
https://ntcsupdate.bmd.at/BMDNTCSUpdateWS.dll/soap/IBMDSOAPNTCSUpdate

If you are using a proxy server, it might be necessary to add this address to the exemption list or to specify the proxy server in BMD NTCS:

Tools → Overview of all Tools parameters → Overall system → General settings → Internet

1.3. What happens during a web update?

If you enable "Automatically check for updates" (can be found under Tools → Overview of all Tools parameters → Overall system → BMD NTCS update), BMD NTCS will check whether a newer version is available on our servers when it is started.

You are then asked if you want to download the new version whenever one is available.

This download is stored temporarily in the folder \\<BMDSERVER>\BMDNTCS_PGM\Update\.

When the download is complete, you will see a message asking if you want to install the update now. During installation, the program files are unpacked, backed up and replaced. Finally, the changes are committed to the database.

2. AUTOMATIC INSTALLATION OF BMD NTCS PATCHES

2.1. Requirements

• SOAP – Service: Needs to run on the server.

• SOAP – Administrator User: In order to create and run batches, you have to define a user with the appropriate permissions.

• Time frame: It is recommended to install the update at a time when the BMD program is not used by anyone. Furthermore, you have to make sure that the update does not conflict with a backup, for example a backup of a database or a file.

2.2. Creating the batch

You can create a new batch under Tools → Administration → Scheduled batches → Define batch.

The batch window consists of 3 sections:
 

Under Batch you can create a new batch (F5 or right-click – New):

• Company: Enter the name of the main company.
• Batch number: Specify a new number that is not already in use.
• Name: Use a descriptive name, e. g.: BMD NTCS update
• Match code: Is created automatically.
• Start only when batch is not currently in progress: Yes
• Log file name: Here, you can specify the path and the name of the file where all activities of the batch are logged.

After saving the created batch, the window for batch steps opens.

• When creating a new batch step, it is important to choose an appropriate designation and set the batch step to "Active".
• Function: MCS_CHECKFORUPDATES
  When you enter this function, the window for the parameters opens automatically:

• Macros: Here you can define what you want to happen before and/or after the batch step.
• Confirmation before execution: The user is asked to confirm each time before the batch is run.
• Cancel in case of error: If any errors occur, the batch is cancelled.

Click on "OK" and "Save". Now the creation of the batch is complete.

This function allows you to run batches manually (not automatically at a set time). When you call a batch, it is run on the respective PC (not on the server).

Please note:
Since the batch is always completed, this operation can take from a few minutes to up to an hour.

Under Batch variables, you can manually define variables for the batch. Variables are used when different values apply to a batch parameter.

Variables that are indicated as "Internal" only apply to macros.

3. PLANNED EXECUTION OF BATCHES

Planned execution allows you to schedule the automatic execution of defined batches at certain points in time.
(Tools → Administration → Scheduled batches → Planned execution)

3.1. Batches

The overview shows all of the created batches with a planned execution. Create a new task (batch) by pressing F5 or clicking on the button "New".

3.2. Executive users

• Designation: Use a descriptive name, e.g.: Weekly BMD NTCS Update
• Batch: Select the created batch for the BMD NTCS Update.
• Executive BMD user: Batch user
• Active: Needs to be enabled for the batch to be run at the interval that you set on the right (you can temporarily deactivate batches here).
• Recipient of e-mails: Receives message of success or error via e-mail (BMD NTCS user who entered an e-mail address).
• System user: By pressing F8, you can enter a Windows user and password with permission to run the batch. Alternatively, you can enter a default operating system user for batch execution in the Tools parameters (Tools → Overview of all Tools parameters → Application server → Scheduler).

Please note:
The next batch to be run is automatically added to Windows Scheduler once. After execution of the batch, the next one is passed from the SOAP service to Windows Scheduler. Thus, the task will no longer be run by the SOAP service but always be passed to Windows Scheduler and is run by Windows through an external call command at a set time.

3.3. Interval

In the bottom right part of the window, you determine the interval (e.g. daily, weekly, etc.) at which the batch is to be run (see section 3.1.).

The function "Run now on server" allows for a trial. The batch is run on the server, which can be useful to check the assigned authorisations, etc.