Racer API | AnyPoint Speedway

Anypoint Speedway (The MuleSoft API Race Where Acceleration Meets Integration) is launched with Season 3. So, Muleys all around the world get ready to RACE. Once we scroll through the instructions, we see a need for Racer API, which will be used to compete in the race. Currently, Racer API can be built in any of the platforms, all it needs is a public endpoint with implementation as per specification.

But, we are the MuleSoft developers, so let's build the API in MuleSoft. If you are a beginner or professional Muley, this article will help you implement the Racer API and participate in the race. Let's fasten up the seatbelt and start developing the Racer API.

Anypoint Speedway has made our lives easier by providing the readily available specification file.

Pre-requisite

racerId

To enter the race, the RACER is required to register for the race and get a racerId.

1. Go to Anypoint Race API, and Click on Request Access. Log in with AnyPoint Platform credentials.


2. Fill in the details as shown below. If an application is not seen, create a new application by providing the name. Click on Request access. For initial access use the Basic SLA tier.


3. This will generate/show the client-id and client-secret which will be used to authenticate the requests to Anypoint Race API.


 

4. Go to POST /register resource. Follow the instructions to generate a racerId. You may use the portal to send a request or any rest client(e.g. Postman) to send a request and get a racerId for your racer. 

{
  "displayName": "Sylvester the Cat",
  "email": "sylvester@wb.com",
  "racerId": "racer-id-value",
  "clientId": "clientId"
}

Highlighted racerId will be used in building the RACER API.

RACER API

1. Download the RAML specification file from the Anypoint Speedway portal. Click on Download and then as RAML. RAML file will be downloaded to the system.


2. Open AnyPoint Studio. Click on file, then New and then Click on Mule Project.

3. Enter the project/racer name, specify the downloaded file's location, and click on finish.

A project will be created with scaffold flows as per the specification file.

Let's build the flows for Tier I. For Tier I, the token is required to be used in further requests. For this, an object store can be used.

4. Add the ObjectStore module in Mule Palette. Click on Global Elements, then click on Create.


5. Select ObjectStore Config under Connector configurations. Click on OK.

6. Check the Connection checkbox and click on OK. A connection configuration will be created.

7. Click on Create again to add another global configuration for ObjectStore. Select ObjectStore under Component Configuration and click OK.

8. Specify the connection reference for ObjectStore created in the previous step. Click OK.

9. Click on Message flow to go back to flows. Go to "post:\races:application\json:racer-api-config" flow configuration.


10. Drag and drop the Store connector from the Mule Palette. Specify the details as mentioned in the below screenshot.


11. Drag a set variable and set the name as raceId and value as uuid(). Configuration should look like as below.


12. Drag a transform message and set the values as shown below. Replace the "race-id-value" with the value, received from the Anypoint Race API POST /register.

13. The overall flow will look like below.


To pass Tier I, at least 1 lap needs to be completed. Let's update the "post:\races\(id)\laps:text\plain:racer-api-config"

14. Drag the Retrieve connector under ObjectStore from Mule Palette, and place it after the transform message. Specify the values as shown below. Token value will be retrieved from the Object store.

15. Drag the transform connector. And update the transform connector with values as below.


The flow will look as below.

16. Save and export the API. Right-click racer project -> Export. Under Mule, select Anypoint Studio Project to Mule deployable archive. Click Next.

17. Specify the export jar location and click on Finish.


Now the RACER API is ready to race for Tier I. Let's deploy to the AnyPoint platform and start the race. 

18. Go to the AnyPoint platform, then to Runtime Manager, select the environment where you want to deploy. Click on Deploy application.

19. Specify the application name, and upload the jar file created in the previous step. Tick the checkbox to use ObjectStore V2 and click on Deploy.

After deployment, a public URL similar to "https://deciphermiddleware-racer-syivqn.5sc6y6-4.usa-e2.cloudhub.io" will be generated. This will be used to enter the race and compete with other racers.

Enter the Race


1. To make an entry in the race, trigger a request to Anypoint Race API POST /racers/{racerId}/entry.

2. Provide the public endpoint along with /api "API kit is used /api is added before every resource". Any REST client can be used to trigger the request by providing details as mentioned in the API documentation.

The RACER has started RACING. Go to the Leaderboard and see your racer name coming up.


Oh wait there are a total of 5 Tiers! So, wear your developer hats and enhance the Rookie Racer to level up to Tier V.


All the best Racers, Let's Race!!!





-

Comments

Post a Comment

Popular posts from this blog

DateTime formatting using xp20:format-dateTime ()

xs:dateTime Format In XML, we generally use xs:dateTime(xs:xmlns="http://www.w3.org/2001/XMLSchema") data type to store date time data. The generic representation of date time, that is supported by xs:dateTime in xml: YYYY-MM-DDThh:mm:ss[.SSS][Z|(+|-)hh:mm] Example :  2019-09-11T10:16:31.943+05:30 Code Description Example YYYY represents a 4-digit year 2019 MM represents a 2-digit month 09 DD represents 2-digit date 11 hh represents 2-digit hours 10 mm represents minutes in 2-digits 16 ss represents seconds in 2-digits 31 SSS represents milliseconds 943 T represents time separator T Z represents UTC time zone or 0 time zone offset (+|-)hh:mm represents time zone offset +5:30 Few more valid examples : 2019-09-11T21:32:52, 2019-09-11T21:32:52+02:...
Read more

Create Delimited String from XML Nodes and Vice Versa in SOA 12c

A delimited string is a string representation of data separated by a delimiter(e.g. ","). A simple representation of the delimited string will look like. Delimited String Examples Sample-1-- Delimiter as ","        Value1,Value2,Value3   Sample-2-- Delimiter as "|"        Value1|Value2|Value3 If we want to represent the above set of delimited values in the form of an XML document under some root and parent tag. The representation will look like this. XML Example <root xmlns="http://test.com/sample/xml">   <Values>     <value>Value1</value>     <value>Value2</value>     <value>Value3</value>   </Values> </root> Sometimes we may need to convert values coming in delimited string to an xml document or vice versa. Since delimited strin...
Read more

Import and Export MDS artifacts in SOA 12c

Image
Oracle SOA-MDS (Metadata Store) repository can be used to access artifacts that can be shared among various SOA composites. For example, we have one common schema for a business fault that is consumed by various applications. Instead of having a localized copy of that schema file in each SOA composite, we can have it in a centralized repository (SOA-MDS). Another benefit of using SOA-MDS is that we can change the file at runtime and need not redeploy the complete code. While developing SOA composites, we use SOA design-time repository, later these changes can be synced to the SOA servers. In this article, we will discuss 2 ways to sync the artifacts available in the SOA design-time repository and the SOA servers. Establishing the connection to SOA-MDS in Jdeveloper. Using SOA em console or Fusion Middleware control console. Moving a file between SOA composite to SOA design-time MDS repository Let's assume, we created a businessFault.xsd which wi...
Read more