Cloud Service Test Harness

Creating Devices for use with the Test Harness

The test harness works with any sort of device capable to sending smart meter commands. By default, all commands are successful.

Devices must be created in a specific manner in order for errors to be returned from the test harness. Specifically, commands for devices whose identifiers (badge number, serial number, internal meter number, pallet number, external ID, MDM external ID, and asset ID) end in "ERR" will return an error. This means that when setting up devices for testing via the test harness, you must create separate devices for successful and unsuccessful (error) results.

The simplest approach when creating "error" devices is to use the same identifier value for all identifiers, but at a minimum, "ERR" MUST be the final part of the identifier value for the AMI Device ID Type  and AMI  Pre-Commissioning Device ID Type configured on the head end system.

Defining Head End Systems, Processing Methods, Outbound Message Types, and Message Senders for use with the Test Harness

This section provides guidelines for creating data and records used with smart meter commands when using the test harness.

Head End System

When configuring a head end system for use with the test harness, note the identifier types specified in the AMI Device ID Type  and AMI  Pre-Commissioning Device ID Type fields. When creating devices intended to return an error, the identifier values for the identifier type(s) specified for these fields MUST end in "ERR" to return an error from the test harness.

Outbound Message Types

When creating outbound message types for use with the test harness, use the appropriate outbound business object based on the specific command. See  Smart Meter Command Flows  for details.

Message Senders

When creating message senders for use with the test harness, use the following settings:

Main tab:

• Invocation Type: Real-Time

• Message Class: SOAPSNDR

• Active: <checked>

• Msg Encoding: UTF-8 message encoding

Context tab:

• HTTP Header: soapAction: <soapaction>

  where <soapaction> is the URI (Soap Action) for the command as shown under  Adapter-Specific Test Harness Commands  below.

  Note the format used here is:

  SoapAction: {URI}

  That's using a colon, followed by a space between the SoapAction and the value.  You cannot use an equals (=) sign. For example:

  SoapAction: http://www.multispeak.org/Version_​4.1_​Release/MeterAddNotification

• HTTP Login User: A user which has been assigned to the SGGHarnessUser role in Oracle Identity Cloud Service (IDCS). See Setting Up a User with Access to the Smart Grid Gateway Test Harness in the Oracle Utilities Cloud Services Administration Guide for more information.

• HTTP Login Password: The password for the user above.

• HTTP Method: POST

• HTTP URL 1: <endpoint_​URL>

  where <endpoint_​URL> is the HTTP URL or the command as shown under  Adapter-Specific Test Harness Commands  below, formatted as follows:

  @SGG_​TEST@<adapter_​name>/<webservice>

  where:

  • @SGG_​TEST@ is a token that combines the protocol, host, port, tenant, domain, and application

  • <adapter_​name> is one “lg”, “itron”, “ssn”, or “sensus”, as appropriate

  • <webservice> is a name specific to each adapter (e.g. OD_​Server, MR_​CB, DeviceManager, and so on. See  Adapter-Specific Test Harness Commands )

External Systems

When creating outbound message types on external systems and for use with the test harness, be sure to specify the appropriate Message XSL and Response XSL files based on the outbound message business object. See  Creating an External System  for lists of these files.

Processing Methods

Command processing methods for a head end system used with the test harness should reference an Outbound Message Type, either the Default Outbound Message Type or an Outbound Message Type for a specific Device Type.