...
Jira Legacy
As of the OASiS 12.6 release, there is now a tool to test Oasis's connection to HS1Pay - to test that it is correctly set up, and to assist in resolving any connectivity issues that may arise once set up.
...
Clicking on HS1Pay Connectivity will attempt to connect to HS1Pay, and if unsuccessful, perform more tests to highlight issues & suggest what the possible causes could be.
The main test performed attempts to check the status of a non-existent Invoice with HS1Pay. The expected result for a successful test is for HS1Pay to indicate that the invoice does not exist. In checking the status with HS1Pay if HS1Pay cannot be contacted, any errors that occur are used to analyse the possible cause of the issue.
When the main test is unsuccessful, Oasis checks whether the SOEPay/HS1Pay server (SoeConnect) is reachable directly over the Internet (ie. without going via SOELink, as it has already tried that!) It does not attempt to communicate with HS1Pay in any way, so no credentials or data are exchanged, it simply determines whether it can connect to the server over TCP/IP.
If this test is run on the Oasis server and fails, it indicates that there is either an issue with the HS1Pay server, or with the internet. If this test is run on a workstation that is not the Oasis server and it fails, this part of the result should be ignored if it is known that the workstation has limited or no Internet access, and the test should bu re-run from the Oasis server for a more accurate diagnosis.
If the above HS1Pay connectivity test fails, Oasis checks whether it is possible to connect to a website on the Internet.
If this test is run on the Oasis server and fails, it indicates that there is an issue with internet connectivity from the Oasis server. If this test is run on a workstation that is not the Oasis server and it fails, this part of the result should be ignored if it is known that the workstation has limited or no Internet access, and the test should be re-run from the Oasis server for a more accurate diagnosis.
Each of these three types of test return a code that is displayed in the message box at the completion of the test - They are shown after the Outcome, in brackets. These code represent the test results in succinct form, and it is intended that they could be used by the Development team to quickly identify the cause of the problem.
The first two chars of this code indicate the result of the main connectivity test, and have the following meanings:
...