Test and production environments
Third-party test environment
Student Management System (SMS) developers must use our third-party environment to test their system for:
- Web Service authentication
- connectivity
- functionality.
Access to USI Registry System third-party test environment
The USI Developer kit contains the following to help you connect and use the third-party testing environment:
- connection instructions
- Machine-to-Machine (M2M) credentials and mock data for the test environment.
Note only mock data should be used in the test environments.
Libraries in development
Using libraries in development is required:
- WCF for .NET (latest versions, minimum requirement .NET 4.5)
- Java WSIT library (authorised by Microsoft and Sun and published on the Oracle website).
Completing successful testing
Complete successful testing in the USI third party test environment using the ATO MAS-ST Authentication service. This is requirement of the Relationship Authorisation Manager (RAM) digital service provider application. A copy of the application form is included in the USI Developer kit.
Production environment
Authentication
To interact with the USI Registry System, education or training provider's must provide
- Australian Business Number (ABN)
- organisation code as listed on Training.gov.au (TGA) or the Tertiary Education Quality Standards Agency (TEQSA) National Register.
Authentication of the organisation and their individual users is managed through Relationship Authorisation Manager (RAM).
If an education or training provider has changed their ABN, they need to update their details on TGA or the TEQSA National Register.
Where multiple organisations (including dual sector providers) are listed under a single ABN, a machine credential is required for each organisation.
Connecting
To connect your software (desktop or in-house development) or client (cloud-based user) to the production environment, the education or training provider must:
- have a Student Management System that has incorporated the USI Technical Services Contract (obtained from the USI Developer kit)
- read, understand and accept the terms and conditions of using the USI Registry System by completing a System Access Request.
- have a machine credential to allow software to interact with the USI Registry System.
Where multiple organisations (including dual sector providers) are listed under a single ABN, a SAR form needs to be submitted by each organisation, as defined by the type of organisation requesting access to the USI Registry System.
My cloud software services
You will need to apply as a Digital Service Provider (DSP) if you are intending to:
- offer services to multiple organisations with cloud-based software
- provide ongoing client support.
The DSP is responsible for managing the client's machine credential. This does not mean a DSP can act online on behalf of an education or training provider.
The DSP application form is included in the USI Developer kit. Complete and send the form to the Digital Partnership Office who will add the developer role to your profile in RAM.
Learn more about my cloud software services and machine credentials.