Never programmed .NET for iMIS. Need help on basics, please.

Our iMIS is hosted offsite and we access it through a remote terminal session.  I am trying to figure out how to write some very simple code to connect to our database, but I am very new to APIs, iBO, etc.  I have VS2010 and my first question is probably a personal preference, but what is more commonly used C# or VB?

Next, can someone walk me through how to set up a very simple example of what pages I need to create to just connect and login using iMIS credentials?  The only help I have received is the following:

----------------

He would need to use webservices since SQL is hosted on our servers and the website he is working with cannot access the database directly.  There appears to be some out of the box support for webservices but not for the public version.  The developer community is the best place I know of to find info on this.

 
These are the links to the imis instance but won’t be available publicly and therefore cannot be used.  “localhost” would be replaced with the imis 15 url.
 

----------------

I do not know where to start, if anyone can help, it would be very much appreciated.

Thanks!

-Craig

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Here's a link

Hi, Craig,

Here's a link that might help get you started:

http://www.imiscommunity.com/imis_soa_web_services

I'm not sure what is meant by the iMIS instance not being available publically, but if the SOA client is in the same network as the iMIS instance (i.e., SOA host), then you should still be OK.

iMIS Website is an ASP.Net Website

We have done a lot of work like this. From job boards to registration forms & surveys. There are two approaches that I would recommend. Either access the data using iBO's or SOA or create a standard ASP.NET application and use LINQ or similar. I am not sure what data you are trying to access, if it is iMIS data then you are best to use iBO or SOA, if it is other data on the same database then you can create your own database calls, they will still work inside of an iMIS site.

iMIS 15 websites are simply ASP.NET websites when you get down to it. If you create a stand alone ASP.NET application you can "wrap " it into the iMIS website by importing each page as an as iParts. In your stand alone application, add the iBO DLLs to the bin folder so you see their functions, and build out your pages. Once the pages are complete , bring each into your iMIS environment as an iPart (make sure they are controls - ascx files, not aspx files)

That is the overall approach, the is what we do to make multiple page forms and reports which interact with the DB and exist inside of a WCM website. Only when the majority of the data is outside of iMIS will we use our own database calls, otherwise iBO and SOA are both good .

Here is more info on iBO's http://www.imiscommunity.com/ibo_for_net_api

The SDK is a good place to start: http://www.imiscommunity.com/sdk_center

Let me know if you have any other specific questions, hope this helps

James Harrison
www.visualantidote.com
jharrison@visualantidote.com