When sending notices an error is shown in the Fault Reason field next to a recipient on the TMA3000 form:oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): http://<<NOTICE_URL>>/
The error usually means that the web service is unable to connect to the recipient to transfer the notice.
If new organisation details have just been loaded for that recipient, check the notice URL for spaces. Trailing spaces are masked by Oracle forms, but you can remove them in the Organisations and Districts form (NSG0110) by changing any character in the URL, saving, then changing it back and saving again. Retry the transactions in the Monitor Web Service Transactions form (TMA3000)
If that doesn't work, or the existing organisation details were working previously, the first thing to try would be to restart the web server and then retry the transaction.
If the same error is still given then try the following to try and diagnose where the problem is:
1 - Open the NSG0110 form and query back the recipient organisation reference2 - Select the district the notice is being sent to and copy the Notice URL shown3 - Open a browser window on the web server itself and try and browse to the notice URL to see if an EToN Endpoint page is shown4 - If no page can be displayed then check that you don’t have a firewall or proxy server which is blocking the connection from your web server.
If you don’t have anything on your side stopping the connection then please contact the recipient and ask them to check their web server is online and that their security isn't blocking your connection.
Another check which can be done is to send the an EToN Ping notice but this can only be done if you have installed the extra BPEL component called TestEToNping.1 - Log into the BPEL Console on the web server as the OC4JADMIN user2 - Select the correct domain if you have multiple (I.E. Live/Test or different organisations) else leave as default3 - Click the TestEToNping component on the left hand side (you will only see this if the component has been installed). Please note that the EToNping component is different and only for testing that your own web server can see the database and receive the EToN Ping organisation details in return.4 - In the Payload section select Schema Version 5.0, insert the Notice URL in the URL field and insert your organisation and district reference in the equivalent fields.5 - Click Post XML - you should then see some XML returned which gives the organisation details of who you sent the notice to, else you will see an error message.
If the EToN Ping was successful then retry the transaction in the TMA3000 form. If the transaction still fails with the same error message then please contact the recipient and ask them to check their web server is online and that their security isn't blocking your connection.
If the senders Notification URL starts HTTPS follow the steps in the below link;
Product TechNotes and FAQs
Bentley Technical Support KnowledgeBase
Bentley LEARN Server
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!