Upgrading to iMIS 20 or Moving to New Server
 

This article provides the information you need to configure iMIS 20 to connect with Advanced Communities (GoLightly).

Single Sign On
To configure single sign on, please go to the Learning Center entry titled “Configuring Single Sign On With iMIS 20”.

Databridge Connection to iMIS SOA / Web Services
Advanced Communities (GoLightly) uses iMIS SOA / Web Services to connect to your iMIS database. The rest of this article focuses on configuring iMIS SOA / Web Services so Advanced Communities (GoLightly) can pass data to and from iMIS.

Finding EntityService.svc page
For iMIS 20.2 and higher, the SOA EntityService.svc page has been moved to another application that is separate from the iMIS application.

Let’s assume that I have installed my iMIS application in a virtual directory called iMIS20. So, the path to the iMIS application is:
There is another application that is created to hold, among other things, the SOA. This virtual directory is installed by default as Asi.Scheduler_<iMIS application> so for my example it is Asi.Scheduler_iMIS20.

So, the new location for the SOA becomes this URL:
ASI has taken care of the necessary entries in the web.config of the Asi.Scheduler application, so users should not have issues with the multiple site bindings and the http meta data being disabled.

1. SOAP Address Configuration
You will have to run an IIS 6 Admin Script to do SOAP Address Configuration. If you are running IIS 7 you may need to install the IIS 6 tools from here:
IIS > Web Management Tools > IIS 6 Management Capability > IIS 6 Scripting Tools

• Open a command prompt and navigate to your IIS installation.
• Then go to /Adminscripts. (Ex/ c:\inetpub\adminscripts )

Once in that directory run the following command:
Change the values surrounded by <> (remove the "<" and ">" as well with the actual values) to the correct values for your installation.

You can find "&lt;W3svcSiteID&gt;" by running the following commands. You will see site identifiers in the same order as the websites listed you click on "Web Sites" in the IIS Manager application:
1) chdir C:\Inetpub\AdminScripts
2) cscript.exe adsutil.vbs ENUM /P W3SVC

Within IIS 7, you may need to add the Internal IP of your server if the above doesn't work:
Finally, make sure to recycle the application pool for the imis application directory.

See also:

• http://blumenthalit.net/blog/Lists/P...ost.aspx?ID=14
• IIS 6: http://www.sslshopper.com/article-ho...-in-iis-6.html
• IIS 7: http://www.sslshopper.com/article-ss...-in-iis-7.html

2. HTTPS Binding
<a name="httpsservername"></a>
Local server name showing on https EntityService.svc page
If you have updated the Soap Address (<a href="#soapaddress">see above</a>) and still see the local server name on this URL:
...follow these instructions:

1. In IIS 7
2. Go to Bindings on right side
3. Make sure the url is in the http entry as well as https
4. When you make this change, make sure to <a href="http://golightly.com/vb/showthread.php?p=383#cannotlogin">update the web.config file</a>.

Testing
Assumption for this document:
is the url of your EntityService page.

Test A.
Do you get a WSDL file when you visit this URL?:
Ex/ If not please review:
http://my.golightly.com/bridgetroubleshooting

Test B.
Look at the bottom of this WSDL file:
Ex/ Look for a section labeled “<wsdl:service name="EntityService">”. Do you see the same root URL but with “https”?
Ex/ If not please review:
http://my.golightly.com/soapaddress

Test C.
When you visit the following URL:
Ex/ …do you see a page with the title “EntityService Service” and a line that says this?:
If not, first make sure that a publicly signed SSL certificate is installed at this URL:
and then review:
http://my.golightly.com/vb/showthrea...ttpsservername

Once these items are all verified, please contact support@golightly.com so we can run final tests to verify that your social network can connect to iMIS.