We have a web site that we are using to extend the functionality of iMIS. In 10.6 we had a custom solution for bridging the login gap from iMIS to our ASP.NET 2.0 solution. With iMIS 15, we gain access to the Unified Login functionality.

If you are writing applications to work with the iMIS database, you should use this technology. It does a great job leveraging the ASP.NET 2.0 membership infrastructure.

This is just a post to share my appreciation about the way iMIS 15 logs into the database.

In 10.6 each user had an ODBC connection on their machine that connected for the base iMIS applications. It then used an application server for the .NET modules such as Opportunity Management. This has a few advantages, but I feel like it has more liability than the iMIS 15 way. For instance, in 10.6 you could run iMIS and be connected to one db for the Customer Portfolio and a different db for Opportunity Management. This is just hard for users to understand and administrators to own.

Once I learned about the iBO for .NET project, I wanted to write an application that would run inside the framework. I also wanted to write it in .NET 2.0 because of the new features.

Here are the basic steps that I took to make it work:
1. Create a new Application Pool in IIS

2. Create a new virtual directory inside of the iMIS.NET virtual directory.

3. Mark the new virtual to use the new application pool and to use .NET 2.0.