Update 4 for ColdFusion Builder 2016 released

ColdFusion Builder 2016 Update 4 is now available for download.

The update adds support for ColdFusion Builder plugin installation on Eclipse Neon and fixes 22 other bugs.  
The bugs fixed are in areas such as Editor (Dictionary, Code Colorization, Code Folding), Security Code Analyzer and  RDS support. 

For instructions on how to download and install the update, refer this technote.
For the list of bugs fixed with this update, refer this technote.

To access the update directly from the ColdFusion Builder GUI, ensure that it it configured with one of the following URLs depending on the CF Builder variant in use :

Stand-alone installation of ColdFusion BuilderClick here!

Plug-in installation of ColdFusion Builder: Click here!

If you need to download the update and apply it manually, you can access the update at:
Stand-alone Update:
Click here! 
Plugin Update:
Click here! 

Updates for ColdFusion 2016, ColdFusion Builder 2016, ColdFusion 11 and ColdFusion 10 released

This article announces the release of updates for ColdFusion 2016, ColdFusion Builder 2016, ColdFusion 11 and ColdFusion 10.

These updates address a common vulnerability mentioned in security bulletin APSB16-22.

ColdFusion 2016 Update 2

ColdFusion 2016 Update 2 fixes an important security issue. It also includes some other important fixes related to Language, Security Analyzer, AJAX, document management, SharePoint, CLI, API Manager and a few other areas.

For details, refer this technote.

ColdFusion Builder 2016 Update 2

ColdFusion Builder 2016 Update 2 (standalone) has been upgraded from Kepler to Mars. It includes important updates to Security Analyzer, a few bug fixes related to performance and other bug fixes. PhoneGap has been upgraded to 5.2.

For details, refer this technote.

ColdFusion 11 Update 9

ColdFusion 11 Update 9 fixes an important vulnerability mentioned in the security bulletin APSB16-22. It also includes a few other fixes.

For details, refer this technote.

ColdFusion 10 Update 20

ColdFusion 10 Update 20 fixes an important vulnerability mentioned in the security bulletin APSB16-22. It also includes a few other fixes

For details, refer this technote.

 

When should tools.jar be updated in ColdFusion Server

tools.jar contains the utilities to compile java source into class files.

While using ColdFusion Web services stubs have to be generated.

So, this utility is required for this feature to be functional.

The tools.jar is shipped by default with ColdFusion along with full
installation of ColdFusion which would be same version of the jre that
ColdFusion is shipped with.

If you are just using this default installation and the built-in jre, your
ColdFusion web services do work fine.

However, due to security bugs or platform support you would want to update
the jre version that ColdFusion runs on.

Once you do that, please make sure to copy the tools.jar file manually from
{JDK_Home}/lib to {cf_install_home}/cfusion/lib/

Only JDK contains the tools.jar file not the jre installation. You don’t
have to install JDK on the machine where ColdFusion is installed. You can just
have jre on this machine and get tools.jar from any other machine’s JDK
installation.

And also make sure that the earlier stubs are cleared from
{cf_install_home}/cfusion/stubs/ to get the newly compiled classes.

It is necessary to update tools.jar ONLY if you are upgrading the jre to a a
higher major version.

Say, if you are upgrading from 1.8 U5 to 1.8 U51 you don’t have to update
tools.jar file.

But, say   if you are upgrading from 1.7 U55 to 1.8 U51, you have to
update tools.jar file.

 

Another case where you would want to update the tools.jar is JEE
deployments.

Say, if you are using Websphere application server with IBM JDK, you have to
place the corresponding JDK’s tools.jar under 
{cf_install_home}/cfusion/lib/.

The same applies to any other application server as well.

The simple rule is that tools.jar has to be from the same major version of
Java (minor version doesn’t matter) that ColdFusion runs on.

 

This applies to any version of ColdFusion and the same applies to all platforms.

You can copy tools.jar from Windows machine to Solaris macine as well as long as the version is correct.

 

Normal
0

false
false
false

EN-US
X-NONE
X-NONE

 

Some of the factors that help in deciding the memory that application needs

Would like to explain the some of the factors that
decide how much maximum memory that an application needs.

Here are two examples. One is with cffile upload action
and the other is with cfpdf thumbnail action.


Sometimes, while uploading large files using cffile
with upload action (<CFFILE ACTION= “UPLOAD”) you would have run
into the following error

“500 – Internal server error.

There is a problem with the resource you are looking
for, and it cannot be displayed.”

 

File upload is dependent on “Maximum size of post data”
value that you can set in ColdFusion Administrator.

However, it can’t exceed the total available free
memory.

Say, if 512 MB is the Xmx memory value (jvm.config) and
350 MB is already occupied by the application, even if “Maximum size of post
data” value is set to 200 MB, it can upload files of up to ~150 MB (512 MB- 350
MB).

It can’t upload files of size 200 MB.

To fix it, Xmx should be increased which is again
subjected to the available memory in that machine.

 

Here is other example:-

Say, you are using CFPDF’s Thumbnail Action and the
thumbnails background is not generated properly.
Here the issue would be insufficient memory.

        Just to hold the decoded image data,
java application needs large memory (say 1.2 GB depending on the image pixels).

It is because of the format and high pixel nature of
the image that is being converted. Number objects created are equal to the
total number of pixels in that image.

So, high pixel imge would consume more memory.

To fix this, Xmx value in jvm.config should be at least
-> Applications memory Size + 1.2 GB (from the above example) i.e.
a minimum of 1.5 GB and can be more depending on your application.

Changing the value and restarting the server would
fix this.

Normal
0

false
false
false

EN-US
X-NONE
X-NONE

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:””;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:8.0pt;
mso-para-margin-left:0in;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:”Calibri”,sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}

Configuring JNDI Data sources in ColdFusion

For configuring JNDI data sources, it should firstly be supported by the
application server.

Tomcat server, which is built-into ColdFusion server, has the support for
this by default.

While there is a blog Here on this how to configure, I want to explain few mistakes
that are tend to be done while configuring. 

  One common mistake generally done is:-
  When the data source is configured from the ColdFusion administrator by
providing irrelevant    username/password.
  You may tend to provide Database’s username/password. This is NOT
Database’s username/password.
  It is the application server’s username and password on which data
source is configured.
  It should be left blank when the credentials are not required by the
server.

Prepending java:comp/env/ is required for the actual JNDI name that is
registered in xml while registering the name in administrator.

It is not mandatory that you register the JNDI data source in ColdFusion administrator.

As long as the app server supports JNDI, you can invoke the data
source that is configured in the application server in cfm source code directly
either in case of standalone installation or EAR/WAR deployment.
But for consistency and preferred names that can used in ColdFusion should be
registered in ColdFusion.

This is applicable to both ColdFusion 10 and ColdFusion 11.

 

Normal
0

false
false
false

EN-US
X-NONE
X-NONE

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:””;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:8.0pt;
mso-para-margin-left:0in;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:”Calibri”,sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}

Code names for ColdFusion server and ColdFusion Builder

Here are the new code names for the next versions of ColdFusion server and ColdFusion Builder. 

The next major version of ColdFusion server is codenamed Raijin. Raijin is the Japanese lightning God

The subsequent version of ColdFusion server post Raijin has been codenamed Aether. Aether is the greek god of upper atmosphere.

We continue to the trend of basing our code names on mythological characters. Also note that the next version of ColdFusion server was previously announced as Dazzle. Dazzle is no longer our code name and instead comes Raijin.

For ColdFusion Builder the next version is codenamed Blizzard (as previously announced) and the version post that is code named Avalanche.

Thanks to Dave Epler and Aaron Neff for recommending the code names Raijin and Aether.

The pre-release for Raijin will commence shortly.

Say hello to Raijin and Blizzard!

 

 

 

 

 

Update released for ColdFusion Builder 3

Update 3 for ColdFusion Builder 3 is released.

This update is
primarily a companion update to ColdFusion 11 Update 3 which ahs added support for
PhoneGap 3.5.

Normal
0

false
false
false

EN-US
X-NONE
X-NONE

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:”Table Normal”;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:””;
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:8.0pt;
mso-para-margin-left:0in;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:”Calibri”,sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}

This is just an Update for the ColdFusion Builder 3
installation that were installed prior to the build number 292483.
Corresponding full installers with this update embedded were already released
in December. Automatic update notification takes care of notifying you, if this
update applies to your installation or not. So, if your installation is the one
that was released in December, this update is not applicable and won’t show you
the notification. 

This update has the following 3 bug fixes.  

 

ID

TITLE

Product
Area

3768717

Remote servers details not retained on Builder restart.

 

Server Manager

3837075

Exception when generating build for mobile project

 

Mobile Support

3848665

PhoneGap version for Mobile project should be updated to
3.5

Mobile Support

Through ColdFusion Builder 3, you would get an automatic notification to apply the Update.

 

In the month of August 2014, we had
refreshed the update 2 just fixing the bugs arised out of Update 2. Ram has blogged
it as Update 3 mistakenly. It should have been blogged as Refreshed build for
Update 2. Our apologies for the confusion with regard to the update number. 

 

 

Thanks,

Krishna

Setting up ColdFusion Builder 3 with a remote server

I wish everyone a very happy and prosperous new year. Here comes the first blog post for the year 2015, on ColdFusion Buider 3. A user came across our Mobile Application Development Contest blog and was trying to develop his application using ColdFusion Builder 3, but he wasn’t able to setup a connection between ColdFusion 11 and ColdFusion Builder 3.  He was trying to create a “Remote Server” connection between ColdFusion Builder 3 and ColdFusion 11, installed on separate servers (distributed setup). 

Here are the steps that will help you setup a remote host with ColdFusion Builder:-

1.     Launch ColdFusion Builder 3 and choose your workspace.

2.     Right-click on the “CF Servers” view and select Add Server

3.    Select “New server configuration” and click “OK”. You can choose “Import configurations from RDS server”, in case you have RDS server setup already and want to use existing server information.

CF Server

4.     If you can’t locate the CF Servers, then, follow the screenshot below, to enable it.

CF Server alternate

Refer to Add a remote server and fill in the details for your server.

5.     General Settings

a)     Server Name: ColdFusion server name.

b)     Description: (optional) Description of the server.

c)     Application Server: Select the drop-down list and select CF+ Tomcat Bundle (for CF10/CF11)

d)     Host Name: Name of the remote server host.

e)     Select: Is Remote.

Note: When you enter a Host Name other than localhost or 127.0.0.1, Is Remote is automatically selected.

f)     Webserver Port: Specify the port number of the remote ColdFusion server instance you are configuring. You can refer server.xml for the same at ColdFusion11cfusionruntimeconf.

g)     RDS User Name: (optional) if you are using RDS, specify the RDS user name.

h)      RDS Password: (optional) Specify the RDS password.

General Settings

Click Next to move to the next screen.

6.     Remote Server Settings

a)     User Name: Specify the CF Admin username.

b)     Password: Specify the CF Admin password.

Remote Server Settings

Click Next to move to the next screen.

7.     Install Extensions

Select Install Extensions to install the extensions that are packaged with ColdFusion Builder.

a)     Browse and select the ColdFusion web root location.

b)     Browse and select the ColdFusion web root location on the remote ColdFusion server.

c)     Browse to a location within the web root to install the extensions. The extensions are installed in the Extensions directory within the selected location.

Install Extensions

8.    Click Finish to add the remote ColdFusion server instance. You can right-click on the remote server and access the ColdFusion Administrator of the remote server.

Launch CF Admin

This blog post talks about, the minimal settings required to setup a remote server for CF Builder. You can skip the Install Extensions section as well.

Note: – While configuring the remote server in CF Builder, ensure that, you are able to access/ping the remote ColdFusion server outside builder. You can probably, access the remote CF Admin in the browser, for e.g. http://ip:port/CFIDE/Administrator/index.cfm and ensure connectivity.

 

 

Can I get an update? If you’re looking for ColdFusion Updaters…

Many of you are looking for a central location to find the full list of ColdFusion Updaters.  We try to keep these updated for the core supported versions with links to the latest released updaters.  These are a good place to look for the full list of updaters available on each version along with a download link to the .jar file. 

 

ColdFusion 11: 

http://helpx.adobe.com/coldfusion/kb/coldfusion-11-updates.html

 

ColdFusion 10:

http://helpx.adobe.com/coldfusion/kb/coldfusion-10-updates.html

 

ColdFusion 9:

http://helpx.adobe.com/coldfusion/kb/hot-fixes-coldfusion-9.html

 

 

Additional updates for ColdFusion server and Builder:

http://www.adobe.com/support/coldfusion/downloads_updates.html

 

ColdFusion Builder Usage Survey

 

Here is a survey to understand the usage of ColdFusion Builder as an IDE (Integrated Development Environment) for developing ColdFusion applications.

 

The information gathered here will help Adobe prioritize on areas that need focus or improvement to keep up with the changing needs of ColdFusion developers.

 

Thanks for your time to respond to this survey.