tracker issue : CF-4155910

select a category, or use search below
(searches all categories and all time range)
Title:

please separate the api mgr to be downloaded only IF its installation option is chosen within the CF install

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Charlie Arehart / Charlie Arehart (Charlie Arehart)

Created: 05/20/2016

Components: Installation/Config, Installer

Versions: 2016

Failure Type: Enhancement Request

Found In Build/Fixed In Build: CF2016_Update2 /

Priority/Frequency: Minor / Unknown

Locale/System: English / Windows 10 64 bit

Vote Count: 2

I just downloaded CF2016 for a new machine, and noticed it's a 1g+ install. Certainly a lot of that increase (over previous versions) must be the API Manager, since I don't recall previous installers being that big. But even the CF 2016 Standard installer is that big, and the API Manager is not supported with that.

I do realize that CF has long had one installer, for all editions (Enterprise, Standard, Trial, and Developer), so I'm not asking that you create different installers for different editions.

And I do also realize that the inclusion of the API Manager with CF is a decision that's already been made, so I'm not asking that the API Manager installation option within Enterprise, Trial, and Developer editions be removed..

But could you please consider splitting out the download of the API Manager installer, and only calling upon/downloading the it if the user CHOOSES to enable it?

Sure, it would put a hitch in the install process (for those people who DO want it), as they would have to wait for that download. And if someone's installing on a server without network connection, they'd have to go get that before they could proceed.

But consider first those who will be getting CF only to use the Standard edition (or using the trial or dev and THEN Standard), who know they will NOT be able to use the API Manager. 

When you consider the number who will get CF Enterprise, and those among them that will chose the API Manager, it would seem a small percent of ALL users of CF2016.

It seems a shame for the CF 2016 installer to be so huge (when people have already long complained of that) for a relatively small percent of the user base.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4155910

External Customer Info:
External Company:  
External Customer Name: Charlie Arehart
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

I do realize that some in Adobe may want to "push" the API Manager, even to the point of "letting" people install it in the trial edition even if they would know then that they'd later be putting in a Standard license, on the off chance that they may "fall in love with the API Manager" and then opt to upgrade to an Enterprise key. Again I would ask: is it fair for everyone who downloads CF to suffer this 1g download, for that seemingly small percent of users who might "be led to be tempted to make this switch"?
Comment by External U.
2700 | May 20, 2016 11:13:11 AM GMT
+1 - Yes, there must be another way. Split it out please. When users only need Developer edition, for example, that excess file size is unnecessary.
Vote by External U.
2704 | May 24, 2016 12:08:42 AM GMT
We can review this requirement in the next release.
Comment by Vamseekrishna N.
2701 | June 22, 2016 12:40:54 AM GMT
Now we have CF and APIM installers as separate entity,the installer is no longer 1G+ and hence no screens asking for API Manager installation
Comment by Deepraj J.
2702 | September 20, 2016 05:19:26 AM GMT
Deepraj, that's great news. I see no indication of when this would be implemented. Most might assume you would mean you'd start this with the next release of CF, whatever it may be (CF2018, perhaps?). But might you also mean that you plan some new installer in the CF2016 timeframe (as has been done in the past, such as a new installer for CF10 for support of Windows 2012)? For those who may wonder, the prerelease of CF2016 update 3 released yesterday (which adds support for Windows 10.1), is indeed JUST an update, not a new installer. Really looking forward to the API Manager weight to be removed from the CF installer, ASAP, especially for the benefit of those who by license (using CF Standard) can't even use it. Thanks.
Comment by External U.
2703 | September 20, 2016 08:56:21 AM GMT