How to create a Local Core

This section explains how to create and configure a Local Core object which is located in the same network as the Master Core. For the installation of Local Cores in different networks please refer to Create a Local Core under a Relay.

In this document we assume you already have one core service installed, which will be treated as the Master Core. The symbolic name 'MASTERCOREHOST' will be used to address this machine. 'LOCALCOREHOST' will be used for the machine where the local core service will be installed.

Core services can be installed using the Window Installer or from the Command Line.

  1. For an installation with the Windows Installer, go to the LOCALCOREHOST machine and run the Window Installer.

    1. On the first page of the installer dialog, make sure that the Server Components option is selected (other components can be selected if required) and then check that you agree to the license terms and conditions, and click Install.

    2. The options can be configured as described in the Windows Installer Setup until you reach the Core Options: Role page. Here, make sure you click on the Local Core option and then in the Master Core or Relay Host field, enter the MASTERCOREHOST hostname, and enter "6512" in the Port field (or a different port field depending on the configuration of the MASTERCORE host).

    3. Click through the rest of the Window Installer options until the end, then click on Install to install the Local Core service.

  2. If using command line installation, go to the "bin" folder in the root directory and enter the following command for the default security mode.

    inmation.exe --install Core --corerole local --corehost MASTERCOREHOST --coreport 6512

When the Local Core service is running and properly configured, it will actively connect to the Master Core. It will then be visible in the I/O Model when connected to the MASTERCOREHOST.

Make note of the Component ID property in the Component Identification property compound of the Local Core. The Functional Component property of any Servers configured will need to use this value to ensure connection to the correct Core.

Setting X.509-certificate-based authentication

By default Secure Remote Password (SRP) is used for the authentication for Intercomponent Communication.

If you prefer to use X.509-certificate-based authentication for the communication between Master Core and Local Core, on the MASTERCOREHOST select the Local Core in the I/O Model and navigate to the Security Settings section in the Object Properties panel.

  1. For the moment leave Security Mode on TLS-SRP but open the Self Certificate Selection and enter the certificate’s Subject Name provided by your system administrator.

  2. Click Apply.

  3. Once the Subject Name has been applied, go to the Security Mode property and set it to 'TLS_X509'.

  4. Click Apply apply once more.

The connection between Master Core and Local Core will now be reestablished.

Connecting a Server to a Local Core

In this section we will show how to connect a Server component to a Local Core so that OPC clients can make calls to the Local Core directly. The Server service can be installed on the same host machine as the Local Core or on a different host.

  1. Install a Server Service using the instructions in the Node Installer section of the documentation. Give the Server instance a name and configure the hostname and port to match that of the Local Core configuration. The default Security Mode is "TLS-SRP" so configure a passphrase for secure communication between Local Core and Server components.

  2. Login to the Local Core or Master Core with DataStudio using an administrator Profile and go to the Server Model.

  3. Right-click in the Server Model and select New  Services  Server.

  4. In the Create Server Wizard, give the Server Object a name. Then set the Functional Component property to match the Component ID of the Local Core object.

    Setting the Functional Component property correctly during object creation is important as otherwise it might be required to restart both Core and Server services (including resetting the Server image files).
  5. In the Communication page, enter the hostname of the Server service installed earlier. Also, set the Connection Mode to "Active" and enter the passphrase configured during the Server installation.

  6. Click Create to create the object in the Server Model. If configuration has been done correctly, the Server Object should show 2 green lights in the Server model.

Connecting a Web API Server to a Local Core

When installing a Local Core using the Windows Installer Setup, the Web API service can be installed at the same time. If the Web API service is not installed at this time or the Local Core is installed using the command line, then see the Web API installation section for instructions on how to configure the service.

When setting up the Web API service, either with the Windows Installer or the command line, profile credentials must be assigned. This profile must also exist in the Access Model in DataStudio. This profile can be created in DataStudio after the installation of the Web API service if necessary. It can be created in the Access Model on either the MASTERCOREHOST or LOCALCOREHOST.

In DataStudio, the Web API Server object is created automatically if both of the following hold:

  • The MASTERCOREHOST and LOCALCOREHOST must be able to communicate, i.e. the Local Core object should be enabled in the I/O Model and should be in a good state.

  • The profile assigned to the Web API service on the LOCALCOREHOST must have administrative access and should be enabled in the Access Model.

The Web API Server object will be disabled by default but can be enabled on either the MASTERCOREHOST or LOCALCOREHOST. To do this, navigate to the Server Model in DataStudio. Right-click on the Web API Server object for the Local Core and select Admin  Enable or click F9.