B2B protocols

About B2B protocols

You can set different protocols for different Transaction Groups but the protocol must be the same within a Transaction Group. For example, for a SORD transaction you cannot send in FTP and receive in API.

All B2B e-Hub An electronic information exchange platform facilitating B2B Communications. Participants with access rights use the B2B Transforms and Protocol interface to:

• Nominate or change your B2B Business-to-Business. Generic term used to refer to defined business-to-business interactions between participants; excludes interactions between a participant and market systems such as MSATS. aseXML schema Specification to describe the structure of an aseXML message. they use for receiving B2B transactions and acknowledgements.
• Select their protocol (delivery method), either FTP File transfer protocol or API Application Programming Interface; a set of clearly defined methods of communication between various software components..

Protocols determine the delivery method for sending and receiving B2B transactions. The B2B e-Hub Consists of the API Portal and the API Gateway for both electricity and gas. supports two protocols:

1. API: Provides B2B communication options using web services or using direct connections from a compatible participant gateway. API is accessible over the internet or MarketNet.
2. FTP: AEMO systems to participant systems interaction using batch processing, suitable for participant systems using database technology and submission or receipt of high volumes of data.

B2B transforms and protocols user access rights

For access to the B2B Transforms, Participant Administrators select the B2B Transforms entity in the Administration >Maintain Rights menu.