Extra help on NSIP Confluence
Some further information for developers:
- more detailed walk through the use case process to test against HITS - in this example, a Timetabling use case.
- quick tour of the HITS Dashboard.
The following information applies mainly to developers using the Java version of the SIF Common Framework:
It is important to note that TLSv1.0 will deprecate in 2017. It is no longer considered a secure version of TLS. However, by default Java 7 uses TLSv1.0.
This may cause issues in some integrations where that TLS version is no longer enabled.
To ensure that the adapters written with the SIF Java framework support a given TLS version, you can set this version in the environment.properties file. Simply set the property called env.tls.version in that file to a value of TLSv1.1 or TLSv1.2. Your adapter will now use the appropriate TLS version to connect to the endpoint.
RefIDs in SIF
The RefId attribute of each object is vitally important in SIF, as it guarantees that an object is uniquely identified, and can be uniquely referenced by other objects. All SIF objects must contain a RefId attribute in order to be valid.
The SIF server will return an
advisoryId element in the response to the request, linking the RefId specified for each object to the RefId actually assigned by the server. The server is entitled to overrule the RefId suggestion of the client, unless the
mustUseAdvisory header has been supplied in the HTTP request. In the latter case, the Create request will be rejected by the server if the provided RefId is unacceptable to the server.
Javascipt Client request error