In the last blog post I prepared Oracle side. In this post I will show, how to prepare ALEXA Skill and how to integrate all layers.
Few weeks ago Amazon implemented new version of Alexa Skill Kit. Alexa Skill Kit is like a APEX builder. Low code technology, so you don't need to write any code :)
Let's start ! Go to Amazon Developer Console
1. Click Get Started on Alexa Skills Kit
Few weeks ago Amazon implemented new version of Alexa Skill Kit. Alexa Skill Kit is like a APEX builder. Low code technology, so you don't need to write any code :)
Let's start ! Go to Amazon Developer Console
1. Click Get Started on Alexa Skills Kit
2. As you can see on screen below there is already one skill on my list. Click on Create Skill to Create new one.
3. The name of my Skill will be - APEXUTIL Pizza :) but you can name it as you wish.
4. Select Custom
5. Create Invocation. Users say a skill's invocation name to begin an interaction with a particular custom skill.
For example, if the invocation name is "apex pizza", users can say:
"Alexa, ask apex pizza ...."
6. One skill can have one or more Intents. An intent represents an action that fulfills a user's spoken request. For demo I'll use only one Intent: "howmanyorders". There are few others Intents but these are predefined and you can't edit.
7. Intent will use one Utterance with one Slot (slot is some like variable). The utterances specify the words and phrases users can say to invoke your intents. Each intent is mapped to several utterances. Slots are indicated within the utterances with curly brackets.
I used "askdate" slot name in AMAZON.data type. AMAZON.data can converts words that represent dates into a ISO-8601 date format. You can read more in documentation. (if you want to define Slot use "{}" ).
If you are here it means your skill is ready! Now you need to setup Endpoint - connection between skill and Oracle REST service.
8. As I mentioned in previous post blog your web service must be secured (SSL). It's obligatory rule. Also as I mentioned in topic you can build whole solution without Lambda microservice, you can use only HTTPS Endpoint.
If you don't remember your REST service URL you can check it in SQLDeveloper.
Instead of http://localhost:8080 use your domain. In my case final URL looks like this: https://www.apexutil.com/ords/aps/v1/alexa.
If you successful Build your Model you can start test it. Click Test tab from top menu.
As you can see my skill passed all tests !
The last step is the Launch proces. From top menu select Launch tab. If you want to use skill as a Dev skill it's not neccessary, but if you complete these informations your skill will look more proffessioinall.
Before you start test skill with Echo device check is skill accessed on your mobile Alexa app. Open Alexa application on mobile device -> Menu ->Skills->Your skill ->DEV SKILLS
If skill is Enabled let's try with your Echo !
"Alexa ask Apex Pizza how many orders have been placed this week ?"
"Alexa ask Apex Pizza how many orders have been placed this week ?"
or watch my ECHO : )
Thank you for this blog. It's very interesting. I followed all steps you described and got the model successfuly built. However, I got an error using the skill I created. I tried to test another skill using your URL: https://www.apexutil.com/ords/aps/v1/alexa. and got the following error: There was a problem communicating with the requested skill.
ReplyDeleteAnything wrong/missed while using your URL?
Thanks.
If you wish to test my web service try this https://www.apexutil.com/apex/aps/v1/alexa.
ReplyDeleteInstead of http://localhost:8080 use your domain. In my case final URL looks like this: https://www.apexutil.com/ords/aps/v1/alexa.
DeleteHow did you use domain?could you please let me know i am trying to cal my local host from amazon skill though i am getting json response from oracle apex but when i cal it from amazon skill it isn't working i am guessing it is beacuse of local host
Localhost is your local address. Alex-a will never reach this address. You must to have public IP with domain (or dynamic DNS service)
DeleteLate to the party on this one but, how would you secure it in a multi user environment? So, if you had sales and HR and they shouldn't be able to query the others data?
ReplyDelete