Expand Minimize Picture-in-picture Power Device Status Voice Recognition Skip Back Skip Forward Minus Plus Play Search
Internet Explorer alert
This browser is not recommended for use with smartdevicelink.com, and may not function properly. Upgrade to a different browser to guarantee support of all features.
close alert
To Top Created with Sketch. To Top
To Bottom Created with Sketch. To Bottom

On Startup

When the Policy Server starts up, it will try to update its current information by using external sources such as SHAID. It will do the following:

  • Update the permission list and permission relationships. These permissions include RPCs, vehicle parameters and module types.
  • Synchronize the app categories from SHAID.
  • Update language information. Language code information is retrieved from the SDL RPC spec, specified in settings.js. This is used for the consumer friendly messages object.
  • Query and store SHAID applications. The Policy Server will grab new or updated application information from SHAID and store it in the Policy Server's database.
  • Pull in changes from new releases of the RPC spec, if there are any, and store its information.
  • Check and renew certificates for the stored applications, if applicable.
  • Check and renew the module config certificate, if applicable.
  • After all tasks above have been completed, expose the UI and API routes for the Policy Server. It is important that the Policy Server receives all the information above before allowing requests from Core to happen.
  • Set up cron jobs for updating permission information, for generating templates and for updating the languages. The Policy Server does not need a cron job for getting new application information from SHAID because of webhooks.
View on GitHub.com
Previous Section Next Section