Installing OGDI version 5 on Azure – Part 5

Posted by on May 5, 2013 in OGDI DataLab

Defining Endpoints

In this part we will explain how to define OGDI catalogues necessary for the connections between the data storage and the data service. The configuration of the end points uses the ConfigTool project from the OGDI DataLab solution. It’s use is quite simple and common sense can guide you as well. But, if you want to see how we did it, just follow along.

For this part of the walkthrough we need to thank Ivan Dragolov for his help on web-security and access rights while analysing the solution and configuring our sample catalogues.

To be able to complete this task, you have to complete all previous parts of this walkthrough as well as have access to the Windows Azure Platform panel or have the necessary storage account name and key.

The ConfigTool project is executed on your local computer and that is why you may be surprised by its simple user interface. Again, you will need to run it only one time and it will not be visible to your clients and users, so trust us when we say: it will do the job. Before you can start it though, you have to configure the storage account information.

  1. Locate the Web.Config file in the ConfigTool project and open it.

  1. On the DataConnectionString line, find the [StorageName] after the AccountName attribute and change it to the real storage name you will use. Again, you should use the storage that you created to keep the configurations in – the one we asked you to have the word config in. You can get it from the Windows Azure Platform management panel

may 2013 Installing OGDI version 5 on Azure - Part 1 picture 21

  1. On the same line locate the [StorageKey] after the AccountKey attribute and replace it with the secondary access key from the same config storage account.
  1. Select Debug as a solution configuration in Visual Studio, right-click on the ConfigTool project, point on Debug, and click on Start new instance to start the project. It will start a new instance of your web browser and show you a simple form. Of course, you need to have IIS installed on your machine but who is a developer and doesn’t have it.
  2. Fill out the fields as follows:
    • Alias – add a short name that describes what information is included in the catalogue. Examples for that are NewYorkStreetParking, TorontoDayCareFacilities, MyExperimentalCatalogue.
    • Description – here you can put a short user-friendly description about the catalogue but this time with more descriptive words. For example, New York Parking Facilities.
    • TableStorageAccount – her you need to input the second storage account name – the one we asked you to include the word data in its name. It is the only time you will be using the second storage account name and access key. Again, you can take this from the Windows Azure Platform management panel.
    • TableStorageAccountKey – use the secondary access key of the same data storage account.

  1. Once you make sure all of the fields have valid information, click the [Add] button and the information for the new catalogue will be added to the config storage. You will see a confirmation of the information under the form once the webpage reloads.

You have completed all necessary steps to create the definition of the catalogue and in the next article, you will see how to upload data in it.
< Previous page | Next page >