Defining User-Configurable ASB Services

The following user-configurable services are installed with Application Server as part of the AVEVA Service Bus (ASB). You can begin configuring your ASB services with the default instances of each service provided as part of the installation.

You must configure at least one instance of the OPCUAService to establish OPC UA client/server machine to machine communication within Application Server.

• ASBMxDataProvider Service

  The ASBMxDataProvider service connects to ArchestrA run-time components and provides access to run-time data.

• ASBGalaxyBrowsing Service

  The ASBGalaxyBrowsing service connects to the ArchestrA namespace to enable browsing of ArchestrA objects and attributes.

• ASBAuthentication Service

  Users are authenticated against Active Directory user accounts. You can configure more than one ASBAuthentication service instance to point to different domain servers as needed.

• OPCUAService

  The AVEVA OPC UA Service is an OPC UA server service. When you deploy this service and complete additional, required OPC UA configuration tasks, you can use a third-party OPC UA server to browse objects and attributes, and to connect, subscribe to, and retrieve data natively, that is, via an OPC UA Server, without the need for a gateway or other protocol translation mechanism. See Configuring and Using the OPC UA Server for more information.

The following user-configurable services are not included with Application Server but can be installed separately. Installing these services adds default instances of each service, which you can then configure as needed.

• Event Service

  The Event service is installed separately and is used to raise, monitor, and route events. The Event Service is not required to enable or configure multi-galaxy communication.

• EventHistorization Service

  The EventHistorization service is installed separately and is used to store events in a configured database. It is not required to enable or configure multi-galaxy communication.

  The EventHistorization service stores events in a configured database. It is not required to enable or configure multi-galaxy communication.