Client Connection Licenses

Acquire Client Licenses

• Development and Runtime clients send license requests to Security Manager for acquiring the Batch Management client license (Development and Runtime).

• Remote clients communicate with the Security Manager in the Batch Management Server machine.

• A single Development Client connection license is consumed for all development client applications (including automation servers), which are opened from the same node.

• A single MOM Client connection license is consumed for all runtime client applications, which are opened from the same node. These runtime client applications can be from any of the products such as Batch Management, MES, or Skelta BPM.

• All active client connections are maintained in the Security Manager. A timer refreshes the connection license for active development and runtime client connections, at an interval of five minutes.

Client Connection Licenses based on Terminal Server Session

Each Terminal Server session consumes a client connection license, irrespective of whether it is launched by the same user or a different user from different host machines. Only one client license is consumed whenever more than one development client or more than one run time client is connected on a Terminal Server session.

Scenarios

The development clients and/or runtime clients of AVEVA Batch Management get installed on the Operating systems, which support terminal services. Any user from any host machine could access the AVEVA Batch Management clients by launching these terminal server sessions of this machine.

Let us consider that the AVEVA Batch Management Client is "BMC1" and the host machines are "HOST1" and "HOST2".

• When you launch a terminal server session on a machine where development and/or runtime clients are installed, a AVEVA Batch Management Development Client connection license or a MOM client connection license is consumed for each terminal server session. The Device ID in the license server is displayed in the following format:

  HOST1_BMC1

• If you launch two Terminal Server sessions to the same machine from the same host (either with same user/different user), then a maximum of one Development client connection license for development clients and one MOM client connection license for runtime clients are consumed.

• If you use development client of BMC1 by launching Terminal Server session of BMC1 from HOST1, and Terminal Server session of BMC1 from HOST2 (either with same user/different user), then two client connection licenses are consumed as follows:

  HOST1_BMC1

  HOST2_BMC1

• If you use development client of BMC1 by launching Terminal Server session of BMC1 from HOST1 and Terminal Server session of BMC1 from HOST1 (either with same user/different user), then one client connection license is consumed as follows:

  HOST1_BMC1

Refresh Client Connection Licenses

If any development or runtime clients are active, the SecMngr service monitors the active connections. The SecMngr service refreshes the client connections at an interval of 5 minutes and 24 hours respectively.

Release Client Licenses

• A Development Client connection license gets released on closing the last development client in a particular node.

• An MOM Client connection license gets released on closing the last runtime client on that node.