Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What are the major behavioral changes in Updater 3 in how the installer works?

April 26, 2017behavioral changes installer updater

0

Posted

What are the major behavioral changes in Updater 3 in how the installer works?

1 Answer

0

Posted

The ColdFusion MX Gold installer only configured “Default Web Site” during installation if the user chose Microsoft IIS. The connector installer would install mappings and a site-level filter on the Default Web Site. Prior to Updater 3 The connector installer (wsconfig.jar) installs a filter and a set of mappings (.cfm, .cfc) in IIS. The configuration is determined by the behavior of the [-site] argument. The -upgrade switch compared dates of old and new jrunwin32.dll and jrun.dll in wsconfig.jar to decide whether to replace them. Due to a bug in laying down the files in Updater 1 and 2, the jrun.dll and jrunwin32.dll “last modified” date was set to the date they were installed on the system. The existing modules had anewer date than the ones in the wsconfig.jar so they were not replaced. This could happen if you installed ColdFusion MX Gold – configured IIS during install – then immediately installed Updater 2. (Fixed in ColdFusion MX Updater 3 or higher) Updater 3 and beyond Updater