Doc Type Tech Notes

Doc Id TN10302

Last Modified Date 08/12/2019

Batch Management 2017 licensing changes

SUMMARY

This Tech Note provides an overview of the changes for the new connection-based licensing introduced in Batch Management 2017.

In the older release of InBatch, you had to install the licenses on the InBatch servers, InBatch Runtime Client, InBatch Development Client and
InBatch Runtime Terminal Server machines. With Batch Management 2017 licensing changes, you only need to install the licenses on the License
Server machine. Batch Management 2017 Clients do not need any licensing components installed because all the licensing enforcement is done
through the Batch Server.

The following section describes configuring Batch Management 2017 Licensing in these scenarios:

When you have a separate License Server or

The License Server is installed on the Batch Management 2017 machine.

ACTION

Separate License Server

When you have a separate License Server machine, that machine is used to host all the licenses. This means that the Configurator on the Batch
Server needs to point to the License Server machine.

1. When you install Batch Management 2017, leave the Licensing options blank (do not select the option to install the License Server).

Figure 1: Install without Licensing options

2. After installing Batch Management 2017, open the Configurator. You see an option for the Schneider Electric License Server.

Terms of Use| Privacy Policy

© 2020 AVEVA Group plc and its subsidiaries.All rights reserved.
 3. Type the name of the Remote License Sever where the Batch Management 2017 licenses are installed, then click Test Connection.

The green check mark indicates that the connection is successful.

Figure 2: License Server connection

License Server is installed on the Batch Server

1. During the installation, select all of the Licensing options (both License Server and License Manager).

Figure 3: Install all Licensing options

2. After installing the licensing options, open Configurator and configure the Batch Server machine name for the License Server.

Terms of Use| Privacy Policy

© 2020 AVEVA Group plc and its subsidiaries.All rights reserved.
 Figure 4: After Installing

InBatch Licensing
This section explains licenses within the License server and their usage. The following screen shots show the License Server installed on the Batch
Server.

Batch Server License usage

Before starting the Batch Server, the in In Use number is 0.

Figure 5: Batch Server usage at installation

After Starting the Environment Display the In Use number is 1.

If it is a Redundant setup with the correct licenses, the In Use number is 2.

Terms of Use| Privacy Policy

© 2020 AVEVA Group plc and its subsidiaries.All rights reserved.
 Figure 6: Batch Server usage

Fgure 7 (below) shows the Batch Management Development Client usage.

Figure 7: Development client in usage

Here we are showing the Batch Management Runtime Client usage. The Batch Management Runtime Terminal Server also shows the connections
in use.

These licenses are now connection-based and the feature is called Manufacturing Operation Client Connection. 1 license is used for every
connection to the Batch Server (for each application connection).

Figure 8 (below) shows the Batch display running on the client node and the In Use number is 1.

Figure 8: Runtime Client Batch display connection usage

ATTACHMENTS
http://okmgcs.km.invensys.com/resources/sites/KPKA/content/live/TN/10000/TN10302/en_US/~secure/{ "SECUREDRESOURCE": "Y" }

Terms of Use| Privacy Policy

© 2020 AVEVA Group plc and its subsidiaries.All rights reserved.