Configuring multiple instances of iMIS 15 on the same server

To create more than one instance of IMIS on a single server without using the multi-instance utility the following can be done.
1) Create the first instance and connect via the iMIS client and IMIS Public website to make sure that you can authenticate. The default installation location is the C:\Program Files\ASI directory.

2) Make a copy of the entire ASI directory and rename it to “ASI_SecondInstance” or another identifiable name. The path of the second instance is then C:\Program Files\ASI_SecondInstance. In this example ASI is the first instance and ASI_TAPA is the second instance. See the file system view in image one.

3) (Optional) Take the first database of the first instance offline to be sure you’re not connecting to it or messing up permissions while you configure the second instance.

4) Create new web applications for the IMISClient and iMISpublic website. This can be done in IIS by pointing to the net directory in the new instance path and making and then creating an application based on the path. C:\Program Files\ASI_TAPA\iMIS15\net”. The path for the public website would be “C:\Program Files\ASI_TAPA\iMIS15\iMIS_public”. The two new sites are the iMIS15TAPA and iMISpublicTAPA as seen in the IIS view in image one. iMIS15RC and iMISpublicRC are the two sites of the first instance and are named so because of changes made using the wizard of the initial install.

5) Decrypt the connection strings in the web.config file for both the Client and public website. This can by modifying the script in Decrypt.bat file seen in image 2 to point to the second instance websites. “/iMISpublicTAPA” and “/iMIS15TAPA” should be changed to the name of the sites in IIS. (To encrypt the connection strings later on modify and use the Encrypt.bat file.)

6) Now the editing the connection string in both of the secondary instance sites should be possible. Change the connection string in both files to point to the secondary database instance.

7) Open the IMIS Client and click the Cancel button. In the Logon menu at the top select Set Location Host. Add the URL of the new Client site by using the Insert button and typing the URL of the new site. See image 3. Once it’s added to the list select and click OK. Select the Logon to Host from the Logon menu to be prompted again for the credentials. The new Server URL should appear in the Server text below the Logon and Password textboxes.

8) Logging into the new instance should now connect to the second database. Bring the first database back online and change the Server settings back to confirm it still works.

AttachmentSize
MultiInstanceWalkThru.doc124 KB
Image3.GIF6.14 KB
Image2.GIF19.58 KB
Image1.GIF23.77 KB

Comment viewing options

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

Workflow Service

What about the workflow service that gets created when you use the multi-instance utility. Isn't this something that needs to be setup also?

RE: Workflow service

Currently, the workflow service is primarily only for the Marketing Suite, but I agree, the multi-instance utility does have this built in as well. You can create a new service manually, and point it to the copied workflow dll, but I believe there are components in the iMIS code that call the workflow by name and will not recognize your new manual service.

-K

Kevin Blouin - enSYNC Corp.

There are also folder/file level permissions that should be set

Part of the instructions in the Multi-Instance Tool go over how to set file and folder level permissions to the new instance folder. This should be done as well. My recommendation is to wait for the tool. The DOC file is in the final stages of being written up, so this tool will be posted to the Tech Support > Downloads folder soon.
Thanks,
Chris
ASI Technical Support

The iMIS 15 Multi-Instance Tool Is Now Available.

The iMIS 15 Multi-Instance Tool is now available on our website (www.advsol.com) under the Tech Support > Downloads > .NET folder at this link:

http://www.advsol.com/source/Communities/documentArchive.cfm?section=Req...

Thanks,
Chris
ASI Technical Support

If doing it like this

You can edit the web config file, and associated Connection Strings by right clicking on the Virtual Directory, Properties, ASP.NET, Configuration. This will decrypt and encrypt the connection strings automatically.

Multiple iMIS databases and public views

Based on the new architecture of the iMIS Public View, is it possible to have multiple public views with different looks and feels tied to 1 database? If so, how is this accomplished? Also, how do you handle multiple databases and Public Views on 1 server? Is that multi instance? Do you have to install the application server for each database, or can you just copy the directory and run the update and configurations? We have multiple iMIS databases, some with eSeries, some without. How would this then be handled in iMIS 15 on 1 server for both the Public view and the staff view?

Christopher W. Marsch, Database Administrator
MEMA
10 Laboratory Dr
Research Triangle Park, NC 27709
(919) 406-8813

Multiple iMIS databases and public views

I haven't tested creating multiple Public View sites against a single database but this should be possible. To do it you should use the Multi Instance tool that is now available. Since the latest release I have had success using it.

Yes, multiple Public Views and one or more databases is what is considered multi instance or at least my understanding of it. This may or may not be on the same server.

As for creating a copy and updating the config files... Much of the steps outlined above will work for basic functionality but aren't fully tested. The multi instance tool will do the same and is the recommended / supported way to do this. The tool also creates a new Windows Service for each application instance.

We don't use eSeries so no insight there.

Public Site on separate server

What if the public site is installed on a different server to casual/staff site? In this case you cannot use the multi-instance tool because it looks for files in the "net" directory which does not exist if you install the public site on its own.
I tried to copy the public sites folder and create a new virtual directory pointing to this. Then manually changed the connection string and the webserverurl of this second public site, but could not get it running.
I get the following message when I try to browse to the second public site:
"You are not authorized to view this page.
You might not have permission to view this directory or page using the credentials you supplied.
HTTP Error 403 - Forbidden".

Any ideas?

Public Site on separate server

Providing disk space isn't an issue, you could install a full instance of public, casual/staff on the second server and only use the public site on that server. I don't think you need the multi instance tool for that because it would just be a regular install on two different servers. I don't know about the licensing implications though.

Providing you copied the public site to the same server that the first instance is installed on, you may want to double check that you have created the virtual directory as an application and the icon looks like the others in IIS. Also that scripts only is selected in the permissions and that ASP.NET version is 2.0 and the application pool isn't used by any 1.x sites on the same box.

Default.aspx

Found the issue. Under the documents tab in the properties of the IIS virtual directory, I needed to add Default.aspx to the list. That fixed it.