DPS907 WSA500 Lab 4

Link relations. Hosted on Azure.

Read/skim all of this document before you begin work.

.

DPS907 WSA500 Lab 4 – Due Mon Oct 12

Due date: Monday, October 12, 2015, at 8:00am ET

Grade value: 5% of your final course grade (partially graded in-class on Mon Oct 5)

If you wish to submit the lab before the due date and time, you can do that.

Yes, your project can earn part marks if a feature is missing. 

.

Objective(s)

Work with link relations, deployed to Azure.

.

Introduction to the problem to be solved

We continue the music business theme from Labs 2 and 3. In the previous assignments, you created a web service with a good level of functionality.

In this assignment, you will implement the most important and core principle of a modern web service, known as link relations.

Your work will be hosted publicly on Microsoft Azure Services.

.

Specifications and work plan

The following specifications apply to all of your work:

  • Follows best practices
  • Implements the recommended system design guidance
  • Uses Entity Framework and Code First technology

For this assignment, here’s what we’re looking for:

  • Implement link relations fully for the Artist entity’s use cases
  • Deploy to Microsoft Azure Services

.

Getting started

Your professor has created a project that you can use as a base for your work. It is available in the Assignments area of the course in My.Seneca/Blackboard.

In class, and in today’s class notes, you will learn about link relations, and how to implement them.

.

Add link-related resource model classes

Add a source code file that will hold the link-related resource models.

Use the LinkRelationsIntro and LinkRelationsMore code examples as your guide.

.

Edit the existing Artist resource model classes source code file

Add the “with link” item class.

Add the item and collection builder classes.

Remember to create the appropriate AutoMapper maps.

.

Edit the Artist controller methods

Instead of delivering “base” (or whatever) items, change the code so that it will deliver items with link relations.

Notice that you can simply use the link relations factory pattern to do this work.

However, remember to respect the rule or guidance in the section titled “Link relations and associated objects”, in the October 8 notes.

.

Make other changes as needed

It’s possible that edits will be needed elsewhere in your project.

.

Deploy your work to Microsoft Azure Services

Deploy your work to your “labs” web site on Azure, into the “lab4” virtual application. How?

Study this document, and watch its how-to videos.

If you are unable to deploy your work to Azure, then we can help during Monday’s class. Do not worry about “losing marks”, because Azure deployment is one of twelve items on our checklist.

You must still submit your work (to My.Seneca/Blackboard) before the due date.

.

Testing your work

Use Fiddler.

Ensure that it has been configured to save the message bodies in requests and responses. (A default installation does not do this.) If you are using a College computer, this has already been configured. If you installed Fiddler on your own computer, follow the instructions on this document.

Test all scenarios (use cases), using your Azure-hosted web site.

.

Saving – ‘exporting’ – your tests

On the left side list of requests, you can delete items that you don’t want included in the export.

When you’re ready to save, choose File > Export Sessions > All Sessions…

The export format will be “HTTPArchive v1.2″. Click the Next button to choose a save location (your project’s root, in the same folder as the “packages” and “lab4” folder) and specify a filename. Name the file by using the project name (e.g. “lab4.har”).

(You can test whether the export was successful. How? First, close then re-open Fiddler. Choose File > Import Sessions. Select “HTTPArchive” as the import format. Navigate to the folder that holds “lab4.har”, and select it. Finally, browse through the request-response sessions.)

.

Reminder about academic honesty

You must comply with the College’s academic honesty policy. Although you may interact and collaborate with others, you must submit your own work.

.

Submitting your work

Here’s how to submit your work, before the due date and time:

1. Locate the folder that holds your project files. (It has about four items, a Visual Studio “solution” file, a folder that has your project’s source code, a “packages” folder, and the Fiddler tests.)

2. Make a copy of the folder. This is the data that you will be uploading.

3. Remove the “packages” folder from the copied folder; also, remove the “bin” and “obj” folders.

4. Compress/zip the copied folder. The zip file SHOULD be about 1MB or less in size. If it isn’t, you haven’t followed the instructions properly.

5. Login to My.Seneca. Open the Web Services Architecture course area. Click the “Assignments” link on the left-side navigator. Follow the link for this lab. Submit/upload your zip file. The page will accept three submissions, so if you upload, then decide to fix something and upload again, you can do so.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

%d bloggers like this: