Skip to main content
GISB connectors support sending and receiving messages using the Gas Industry Standards Board (GISB) protocol.

Key Capabilities

  • GISB protocol support for energy sector B2B communications
  • Digital signature and encryption capabilities with key management
  • Receipt processing and acknowledgment handling for reliable delivery
  • Support for multiple GISB versions with configurable protocol options

Overview

A GISB connection is configured in two places. Configure the GISB Profiles page with a local GISB identifier, personal key, and other information that is global across all GISB connections. Then configure individual GISB connectors with connection settings specific to a single trading partner. When a GISB connector processes an input file, it is packaged and sent to the specified trading partner. When receives a file over GISB, it attempts to route the file to a specific GISB connector. The application uses the GISB identifiers in the message to determine which GISB connector should receive the file. When a file is routed to a GISB connector, that file is placed on the connector’s Transactions tab, or is passed along to the next connector in the flow.

Profile Configuration

The GISB profile must be configured before connections can be established with individual GISB connectors. Click Profiles > GISB on the navbar.

GISB Profile Tab

Personal Id

Settings for identifying the local profile.

Personal Key

Settings related to the private decryption and signature certificate.

Application URLs

Settings and displayed values related to accessing from the public web.

Miscellaneous

Connector Configuration

This section contains all of the configurable connector properties.

Settings Tab

Trading Partner Info

Settings for identifying and connecting to a specific trading partner.

Connection Info

Settings related to connection parameters for the specified trading partner.

Receipts

Settings related to sending and requesting message receipts.

Trading Partner Keys/Certificates

Settings related to the public certificates provided by the trading partner.

Advanced Tab

Alternate Local Profile

Settings that override the GISB configuration on the Profiles page for this specific GISB connector. Setting an alternate local profile allows the use of different local keys and identifiers for individual trading partners.

TLS Client Authentication

HTTP Authentication

Settings related to HTTP client authentication.

Proxy Settings

Advanced Settings

Settings not included in the previous categories.

Logging

Miscellaneous

Automation Tab

Automation Settings

Settings related to the automatic processing of files by the connector.

Performance

Alerts Tab

SLAs Tab

Partner Setup

Trading partners must share the connection details that are required when configuring a new GISB connector. At a minimum, these details must include:
  • GISB Identifier
  • Partner URL
  • Recipient Key Certificate

Send and Receive Files

Once the GISB profile and partner-specific GISB connectors are configured, files can be securely sent and received.

Send Files

In a GISB connector, the Transactions tab displays the files to be sent to the target trading partner. If Send is enabled on the Automation tab, files that reach this tab are automatically packaged and sent. Access the log files for all transmissions by expanding the row associated with the transmitted file. The Create Test Files button lets you generate a simple series of test files to send to the trading partner.

Receive Files

In a GISB connector, the Transactions tab displays the files that have been received by the application and routed to the connector (based on the GISB identifiers present in the incoming GISB message). Expand each file row to display a list of available logs for the transmission. These files are available on the connector Transactions tab. If the connector is connected to other connectors in the flow, files are automatically moved from the Transactions tab of the GISB connector to the Transactions tab of the next connector in the flow.

Macros

Examples