Jump to content

Scott_Serco

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

10 Good

1 Follower

About Scott_Serco

Personal Information

  • Occupation
    Software Support
  • Location
    Derby

Employer (optional)

  • Company Represented
    Serco Learning
  1. What would happen if you try the splash screen, you can then link to other parts of the API from here - https://127.0.0.1:8443/API/ or https://127.0.0.1/API/ Also the address used in the links needs to be https://127.0.0.1:8443/API/services/WebService?wsdl https://127.0.0.1/API/services/WebService?wsdl My apologies, I should have picked up on that when I replied this morning. Scott
  2. The API will only work over https, this is normally port 443 in IIS and 8443 in TomCat. The top link you have provided would only work if IIS has been configured to use port 80 for HTTPS but port 80 is the default port for HTTP. The bottom link wouldn't work as it is unsecured and using port 8080, the default http port for TomCat. If you're using the default setup for IIS and TomCat I would expect the following links: Over IIS (when SSL is setup) -- https://127.0.0.1/API/services/WebService Over TomCat -- https://127.0.0.1:8443/API/services/WebService I have not included the port on the first link because by default it'll use port 443. You will also need to ensure your loopback address (127.0.0.1) is included in the API.XML file localed in \Facility\ePortal\conf\Catalina\localhost\ Scott
  3. I'm glad I could help
  4. I can see form your screenshot you don't have a version number on the API. To resolve this issue all you need to do it stop your ePortal services and delete/remove the API folders located in your webapps folder. When you start the services back up these folders will be rebuilt. If you find it doesn't work at this point just stop and start the services a second time (with out removing the API folders). Good luck, Scott @ Serco
×
×
  • Create New...