We currently have iMIS 15 installed on a 64 bit Windows 2003 server with ColdFusion MX7. We have a ColdFusion application installed on this server that is attempting to use the Hash process using the ASIUtil.dll to compare the iMIS password to a login on a custom member only site we have created. It prompts an error that it cannot hash the password. We did have this app on a windows 2003 32bit server until we upgraded to iMIS 15.

Frequently, customers have a previous website where they have logins and passwords they would like to preserve in a new iMIS based website.

The following is sample Coldfusion code on how to access the new i15 MembershipWebService and user the RegisterWebUser method to load logins and passwords into iMIS in bulk.

This can also be modifled to replace the Generate Logins functionality of e-SEries by pre assigning logins and passwords based on a formula.

Attached is a document with specifics on how to use the iMIS15 MembershipWebService to login a user from a third party site.

Please comment with any errors, omissions or additions you may have.

80% of the development of this process was done with the help of Eric Means.

Thanks,

Mike

We are currently using Dreamweaver and ColdFusion Studio for coldfusion development. Both tend to take a long time to load/save. We can't store a copy of the website on our local machines b/c we have too many sites. Does anyone suggest other development tools when developing in coldfusion?
Thanks!

If you are running into an issue with eCM whereby the session remains active after closing your browser here is the solution.

It’s the /AM/Application.cfm file. The CFAPPLICATION tag has setdomaincookies=”Yes” which causes the problem. Setting the setdomaincookies=”No” allowed the session to end after the browser closed.

e-CM comes with a number of application files that get loaded on each page call within the e-CM framework. Some of these files can be used to inject your own processing into e-CM to manage different elements. I will look at the various files and give some hints as to what you can do with them.

Let's assume to start that the application has been initialized and your session has already been set up, which is probably about 98% of all page hits to e-CM.

1) Application.cfm (ApplicationOriginal.cfm): this file is built by the quick start wizard and while it is unencrypted, I do not recommend you make any modifications to this file. If you do you will have to put those modifications back each time to run the e-CM wizard, which is just too prone to error.

2) ApplicationUDFs.cfm: this file is the second to last line run in the Application.cfm file. This is meant as place for you to place any user-defined functions you want to create for your system. There are some placed in here by default, but you can add your own as you need. This file is not encrypted but might be modified in a later release.

3) ApplicationCustom.cfm: here is where you can place any custom code you want in order to give global control over custom code you might be putting within the application.

Now, if you want to create your own application variables, I do not recommend putting them in this file. There are two places you can put these variables. One I will discuss below, as for the other, you can place them in the Site Maintenance settings available in e-CM administrator. It is possible to even build your own custom components to separate your unique variables from those of the system. To do this you need to create an entry in the component_ref table, activate it, and reset the application variables. I will blog on this more extensively in the future.

I was recently asked to provide some guidelines or practical feedback on how to get the most performance out of e-CM as possible. First of all, e-CM has gone through many changes and performance enhancements over the years. It has been well optimized for performance.

That being said the following are 3 main things (from least to most important) that someone setting up e-CM can do to maximize its performance: