• State Suggested Answer
  • Replies 8 replies
  • Answers 4 answers
  • Subscribers 4 subscribers
  • Views 4477 views
  • Users 0 members are here
Options
Related

Rest API not starting for GroupShare

tchris

Hi there,

Are there any special requirements needed to get Rest API to load up? According to GroupShare's installation guide it should be listening on port 41234, in my case, there is nothing listening on that port. Has anyone experienced this?

I already checked the firewall and it isn't blocking that port.

How can I get Rest API to load up? Any thoughts?

-Chris
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi Chris,

    It depends on the version installed. Regardless of version, the first requirement is that the server has to be licensed before it loads. The 30 day trial is not sufficient.

    For GroupShare 2014:

    - The REST API documentation is only accessible from the server machine itself

    - The URL is http://localhost:41234/help/management/Documentation

    For GroupShare 2014 SP1:

    - The REST API documentation is accessible from remotely and locally

    - The URL is http://servername/documentation/api

    I hope this helps.

    Cheers,

    Luis
  • 0 in reply to Luis Lopes

    Hi Luis,

    Thanks, the license is active already and it's running on SP1. The link  http://<servername>/documentation/api still doesn't work. Using cmd, "netstat -a" shows that nothing is listening on port 41234. Any thoughts?

    Kind regards,

    Chris Tanaka
  • 0 in reply to tchris

    Hi Chris,

    If you check the SDL.Application.log in C:\ProgramData\SDL\Service\Logs and search for RestApi, you should see things like the below. Is that the case? If not, can you restart the SDL Application service and see if it runs the REST API?

    2014-01-29 15:50:56.268#Sdl.StudioServer.Services.Core.Hosting.WindowsServiceHost#Sdl.StudioServer.Authorization.AuthorizationServer.RestApi, Version=1.8.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888

    2014-01-29 15:50:56.270#Sdl.StudioServer.Services.Core.RestApi.SelfHostedRestApiManager#Configuring: RestApi.AuthorizationRestApi

    2014-01-29 15:50:56.320#Sdl.StudioServer.Services.Core.Hosting.WindowsServiceHost#Sdl.StudioServer.Authorization.RestApi, Version=1.8.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888

    2014-01-29 15:50:56.322#Sdl.StudioServer.Services.Core.RestApi.SelfHostedRestApiManager#Configuring: RestApi.AuthenticationRestApi

    2014-01-29 15:50:56.329#Sdl.StudioServer.Services.Core.Hosting.WindowsServiceHost#Sdl.StudioServer.Services.Help.RestApi, Version=1.8.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888

    2014-01-29 15:50:56.333#Sdl.StudioServer.Services.Core.RestApi.SelfHostedRestApiManager#Configuring: Sdl.StudioServer.Services.Help.RestApi.HelpRestApi

    2014-01-29 15:50:56.377#Sdl.StudioServer.Services.Core.Hosting.WindowsServiceHost#Sdl.StudioServer.Services.Management.RestApi, Version=1.8.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888

    2014-01-29 15:50:56.381#Sdl.StudioServer.Services.Core.RestApi.SelfHostedRestApiManager#Configuring: Sdl.StudioServer.Services.Management.RestApi.ManagementRestApi

    2014-01-29 15:50:56.388#Sdl.StudioServer.Services.Core.Hosting.WindowsServiceHost#Sdl.StudioServer.Authorization.SecurityHandler, Version=1.8.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888

    2014-01-29 15:50:56.394#Sdl.StudioServer.Services.Core.Hosting.WindowsServiceHost#Sdl.StudioServer.Authorization.Shared, Version=1.8.0.0, Culture=neutral, PublicKeyToken=c28cdb26c445c888

    2014-01-29 15:50:56.438#Sdl.StudioServer.Services.Core.RestApi.SelfHostedRestApiManager#Opening self host server

    Thanks,

    Luis
  • 0 in reply to Luis Lopes

    Hi Luis,

    I've checked the logs and restarted SDL Application Service. There is no mention of Rest in the logs
  • Former Member
    0 Former Member in reply to tchris
    This just happened to us...and it turned out to be a licensing issue. For us, we were seeing a blank page with just the favicon loading when we accessed https://<servername>/documentation/api. SDL support was able to deactivate our GroupShare server license and issue a new one with the REST API explicitly enabled, which at least did the trick to get the /documentation/api page to render. We are still verifying that the API itself is working. A bunch of GET methods didn't seem to work directly in a browser, but but it's a start.
  • 0 in reply to Former Member
    Hi Jeremy,

    Glad to hear this was resolved.

    Just a note, depending on what you are planning to develop, there is a .NET Library that can be used for the GroupShare REST API, which takes away a lot of groundwork of working with it (such as token management, async calls, etc.)

    github.com/.../groupsharekit.net

    Thanks,
    Luis
Reply Children
No Data