Open Smart Grid Platform Documentation

  Fix This Page

Guidelines to add a new domain to OSGP

In order to add a new domain to OSGP, you can benefit from the guidelines given in this document. The general idea for adding a new domain is to copy an existing domain, for instance the microgrids domain, and perform a global search and replace, to replace the old domain name with the new domain name. You can use refactor methods from IntelliJ or Eclipse to help renaming the old domain names.

To add a new domain, changes must be made to 3 GitHub repositories:

  1. Config repository.
  2. Shared repository.
  3. Platform repository.

Changes to OSGP/Config

Search for “Microgrids” and “microgrids” in all files and you will find all files to change for a new domain. These files include:

  • Apache configuration
  • Create domain database script
  • Backup, restore, symlinks scripts
  • Tomcat context script

Changes to OSGP/Shared

A new Maven module must be added for the new domain (osgp-ws-newdomain). This module will contain the wsdl files for the new domain services. Copy for instance osgp-ws-microgrids, search and replace microgrids with your domain and replace the wsdl files with your wsdl files. JAXB will generate java classes for your webservices. Change NewDomainWebServiceConfig.java accordingly. Make sure your base Request and Response classes are generated with an @XmlRootElement annotation. Otherwise your endpoints which are based on these types will fail (See @PayloadRoot in AdHocManagementEndpoint in ospg-adapter-ws-microgrids). The structure of your wsdl file determines whether the @XmlRootElement annotation is generated or not.

Image showing the generated @XmlRootElement annotation alt text

Do not forget to add two constants for your new domain in the enum ComponentType.java (https://github.com/OSGP/Shared/blob/development/shared/src/main/java/com/alliander/osgp/shared/exceptionhandling/ComponentType.java). These constants are used in handling exceptions. Add one constant to denote your new Domain layer (DOMAIN) and one for your new Web Services layer (WS). See for instance MicrogridsService.java (https://github.com/OSGP/Platform/blob/development/osgp-adapter-ws-microgrids/src/main/java/com/alliander/osgp/adapter/ws/microgrids/application/services/MicrogridsService.java).

Add DTO’s to osgp-dto for your services. The DTO’s are used in the protocol-adapter. Mapping from/to DTO’s is performed in adapter-domain.

Changes to OSGP/Platform

Reference the new osgp-ws-newdomain (from Shared) in the platform pom.xml. Also create three new Maven modules and add them to the pom:

  • osgp-domain-newdomain
  • osgp-adapter-ws-newdomain
  • osgp-adapter-domain-newdomain

Constants for the new domain webservices

OSGP uses a couple of Java enums to identify all available services the platform offers.

  • The DeviceFunction enum contains all services for all domains.
  • The NotificationType enum and the NewDomainRequestMessageType enum are identical and contain the services for 1 domain. The NotificationType enum is generated from the wsdl service definition for the notification service. The NewDomainType enum is defined in the Web Service Layer for the new domain and is used to pass the message type to the other layers of OSGP.
  • DeviceRequestMessageType will contain the services for 1 protocol Strictly speaking this enum is not necessary to add a new domain because the enum is located in the protocol layer of OSGP.

Each new service that is offered by the domain, for instance GET_DATA or SET_DATA, must be added to 4 java enums:

  1. NotificationType (https://github.com/OSGP/Shared/blob/development/osgp-ws-microgrids/src/main/resources/schemas/notification.xsd, generated from wsdl with JAXB)
  2. DeviceFunction (https://github.com/OSGP/Platform/blob/development/osgp-domain-core/src/main/java/com/alliander/osgp/domain/core/valueobjects/DeviceFunction.java)
  3. NewDomainRequestMessageType (see for instance, https://github.com/OSGP/Platform/blob/development/osgp-adapter-ws-microgrids/src/main/java/com/alliander/osgp/adapter/ws/microgrids/infra/jms/MicrogridsRequestMessageType.java)
  4. DeviceRequestMessageType (https://github.com/OSGP/Protocol-Adapter-IEC61850/blob/development/osgp-protocol-adapter-iec61850/src/main/java/com/alliander/osgp/adapter/protocol/iec61850/infra/messaging/DeviceRequestMessageType.java or any other protocol adapter)

SQL for the new domain

A Flyway script should be added for system data. For a new domain a new record must be inserted in the table domain_info in the core database. Check for instance the Flyway script for Distribution Automation https://github.com/OSGP/Platform/blob/development/osgp-core/src/main/resources/db/migration/V20170508125704045__Added_Distribution_Automation_domain_info.sql. Test data for a new domain will include:

  • Table device_function_mapping in the core database. Add a row for each new service to authorize ‘OWNER’ for this service.
  • Table device in the core database. Add a new row for a test device, use the proper protocol_info_id. (Protocol_info_id is a foreign_key to the protocol_info table in core).
  • Table device_authorization. Add a new row to authorize owner for this device. (Function_group is a reference to the java enum DeviceFunctionGroup in Platform/osgp-domain-core).

Changes to osgp-domain-newdomain

  • Review entities. Be careful, the entities in this project are generated in the core database. The name of this project suggests that the entities would be generated in a domain specific database.
  • Create valueobjects for your domain. The valueobjects in this project are used only in the adapter-ws and adapter-domain layer.

Changes to osgp-adapter-ws-newdomain

  • Add Endpoints for each service request in presentation.ws.
  • Add MessageProcessors in infra.jms.messageprocessors for each service response.
  • Modify mapping/NewDomainMapper to map the JAXB generated classes to the classes in Platform/osgp-domain-new-domain

Changes to osgp-adapter-domain-newdomain

  • Add MessageProcessors in infra.jms.ws.messageprocessors for each service request.
  • Add MessageProcessors in infra.jms.core.messageprocessors for each service response.
  • Modify mapping/DomainNewDomainMapper to map the classes in Platform/osgp-domain-new-domain to the classes in Shared/osgp-dto. The osgp-dto classes are used in the core layer and the protocol layer.

Testing the new domain services

In order to test the new domain services take a look at the Installation Guide. While following this guide keep the following items in mind:

  • A test device for the new domain must be available. This can either be a physical device or a simulated device.
  • The test device must be connected or a device simulator must be running.
  • The OSGP protocol adapter for the new device must be extended.
  • ProgreSQL must be installed with all OSGP databases and system data as listed in the installation guide. The new domain might have a new database in which case the create script for the database and database owner must be run.
  • Test data must be inserted into the following tables: organisation, device, device_authorization, device_function_mapping. Depending on the type of protocol adapter used for the new domain other tables might have to be populated as well. For instance a table like rtu_device for the IEC61850 Protocol Adapter.
  • Apache Http Server must be installed and the new domain must be added to the configuration
  • Apache ActiveMQ must be installed
  • Tomcat application server must be installed and at least 4 web applications must be deployed:
    • An OSGP protocol adapter
    • OSGP Core
    • The OSGP Adapter Domain for your new domain
    • The OSGP Adapter WS for your new domain
  • SoapUI can be used to test the new webservices for your domain