Entries Tagged as 'Success Story'

Many a time, ColdFusion application code is deployed on a network path when your ColdFusion deployments are of large-scale and mandated to use network paths.

After setting up the server for the first time, if there is any performance hit, as the first thing you would want to cross-check few things. One of the things to determine is if there is any network latency.

Though you would have got same network within your organization same as earlier, your OS version also would have changed.

Follow the steps below to see if the performance hit is due to network latency-

Read more...

We would like to make an announcement to highlight a great public application that was built with Adobe ColdFusion 11 Mobile Platform Tools by one of our well-known community members, Dave Ferguson.  We think the app is a great example of the types of mobile solutions that can be built utilizing the features available.

Well done Dave!  Thanks for sharing.

 

The application was built using these mobile features of ColdFusion 11: 

Local data storage access using components.

Remote app inspection using built-in weinre server.

App debugging during development process.  

Application building via phonegap build for deployment. 

 

Bootstrap was used for UI controls and layout.  

Dynamic tempting was achieved with Mustache.

jQuery and other Javascript plugins for miscellaneous UI elements.

 

Description:

Tournament Scorecard Pro is an app for keeping score at a martial arts tournament.  These tournaments don't have a scoreboard for spectators, so it is up to the spectators to keep score themselves.  This has historically been done with pen and paper. However, this method leads to lost scores or other issues. With the app, spectators can easily keep track of scores and always have them with them.  They can now easily look back at previous tournaments for reference.  The app also helps during the tournament when it comes to correcting scoring conflicts and figuring out ties.

 www.tournamentscorecard.com

 

 

Have you built a mobile application using any of the ColdFusion 11 tools?  Tell us about it!

Read more...

Since 2004, Promisan has built its management consulting and systems business by creating tools that help clients optimize how they use information. Promisan’s flagship enterprise resource planning (ERP) solution, Prosis, surpasses rival solutions because it has been built using the stable, mature, and powerful Adobe ColdFusion platform. ColdFusion gives Promisan the flexibility to meet changing customer requirements and to integrate with a variety of IT infrastructures

“Adobe ColdFusion is a fantastic application server that outperforms others at a significantly lower cost of ownership. Because it’s based on a J2EE-compliant Java platform, it readily supports Linux, Solaris, Mac, and Windows operating systems. The platform integrates seamlessly into Java and C++ projects—providing outstanding flexibility in the demanding, challenging ERP arena,” says Jorge Armin Mazariegos, co-founder and operations manager at Promisan.

Prosis has helped one global company cut staffing report times from three days to one minute and a recruiting agency to gain real-time insight into job recruiting status. The ERP system has also helped a crude oil distributor cut the time required to refill storage tanks by 67%.

Adobe ColdFusion has allowed Promisan to eliminate nearly all third-party tools for solution development. With ColdFusion, Promisan developers have achieved a sustainable business model for Prosis that can support sites with anywhere from 5 to 5,000 users accessing more than 1,500 normalized database tables.  http://adobe.ly/1BWdfnE

 

ColdFusion 11 update 1 was out and blogged about here. It included the fixes listed in the technote, out of which two (Bug# 3777189 & Bug# 3758172) were related to IIS. We would like to share one of our Customer experience and how we solved a connector issue after applying Update 1 in ColdFusion 11.

The Challenge

Recently we were contacted by a customer from a larger organization, who wanted the IIS fixes. They weren’t aware about the release of Update 1. Once we told them, they tried to apply the Update 1, but had issues with it. We suggested them the alternatives that can be used when there is a problem with direct application of the hotfix. The update was installed successfully and was confirmed from ‘Settings Summary’ page in the CF Administrator. The next step was to reconfigure the connector. The moment connector was re-configured, all the sites went down. There were approximately 15-20 sites configured with ColdFusion and the entire production went down. We checked the update logs and they were clean. The error reported was "Error 403 Access Forbidden" across all the sites.

The Solution

We tested the non CFM sites, and they were functional. Only the ColdFusion based sites were giving the forbidden errors. Thus we inferred that, the issue is either with ColdFusion or the connector configuration. We enabled the internet port for ColdFusion and there we go, it worked. This meant, ColdFusion was also working perfectly, but somewhere the connector broke. Even after trying all the ColdFusion based troubleshooting steps, basic windows troubleshooting, permissions check, ColdFusion logs etc., we were unable to fix the issue.

Then we decided to compare the settings with one of the development servers they had. And bingo, we found the root cause of the 403 error. “worker.cfusion.secret=yourSecret” was added by them in their {cf.home}/config/wsconfig/[magic number]/workers.properties as a part of connector shared secret setting. This is a part of ColdFusion 11 Lockdown Guide procedure. When the connector was re-configured, the previous settings with configuration information were erased. But the corresponding entry in the {cf.instance.home}/runtime/conf/server.xml was still looking for the related entry in workers.properties and thus was throwing error.

The Result

Once the setting was updated, all the sites were up and running in seconds. The customer was very happy, as their sites were back on production. If the connector needs to be reconfigured, we have to first remove it and then re-configure it. Connector removal means, the changes made by the user will be lost. When the user re-configures the connector thereafter, we don't have any means to identify what configuration settings they previously had.

The Recommendation

Before you re-configure the connector, we strongly recommend the following:

Ø  Back up all connector configuration files. Connector configuration files are available at {cf.home}/config/wsconfig/

 

Note: The same has also been mentioned in the ColdFusion 11 Lockdown Guide as well.