IBM Power Ideas Portal
This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
It really doesn' t make sense not to have PHP as a yum package in THE STANDARD IBM REPO.
You already have the integrated Apache.
Just add php capability with a simple "yum install php", simpler, better, a common with other platforms.
.This has been delivered via our partnership with Perforce. See https://bitbucket.org/ibmi/opensource/src/master/docs/yum/3RD_PARTY_REPOS.md
The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. This will improve the implementation of PHP to be stand-alone like other platforms.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CAAC, see www.common.org/caac
For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/
Nancy Uthke-Schmucki - CAAC Program Manager
Since the acquisition of Zend by Roguewave, it's become very clear that Roguewave is happy to continue to harvest maintenance fees but has no real interest in the future of the product. PHP is very important in many shops. Don't give us another reason to move workload from our preferred platform. The comments in the RFE as to the availability of other open source tools via yum/rpm are correct. PHP should be the same.
PHP releases have been more aggressive lately and we are stuck to wait for Zend Server to release a new version each time. It takes a long time before we are able to access those new version.
One of the many existing pain points: In order to make php configuration changes, you must make the changes from within the Zend Server web administration UI. You can manually edit the .ini files, but Zend Server keeps the configs in a database and under certain conditions overwrites the .ini files. In order to log in to the Zend Server web admin you have to have a license key that expires after 1 year if I recall correctly. In order to get a license key you have to talk to a salesperson, wait sometimes weeks for them to get back to you, and put up with their sales pitches.
Another pain point that I and many others have experienced: Zend Server is an unnecessary additional point-of-failure. Remember this?
https://zend18.zendesk.com/hc/en-us/articles/203890456-After-upgrading-to-IBM-i-7-2-or-higher-the-ZENDPHP7-or-ZENDSVR6-Apache-instance-will-not-start
Our production applications were down for 24 hours while I tried to trace down this bug.
One of the many existing pain points: In order to make php configuration changes, you must make the changes from within the Zend Server web administration UI. You can manually edit the .ini files, but Zend Server keeps the configs in a database and under certain conditions overwrites the .ini files. In order to log in to the Zend Server web admin you have to have a license key that expires after 1 year if I recall correctly. In order to get a license key you have to talk to a salesperson, wait sometimes weeks for them to get back to you, and put up with their sales pitches.
Another pain point that I and many others have experienced: Zend Server is an unnecessary additional point-of-failure. Remember this?
https://zend18.zendesk.com/hc/en-us/articles/203890456-After-upgrading-to-IBM-i-7-2-or-higher-the-ZENDPHP7-or-ZENDSVR6-Apache-instance-will-not-start
Our production applications were down for 24 hours while I tried to trace down this bug.
One of the many existing pain points: In order to make php configuration changes, you must make the changes from within the Zend Server web administration UI. You can manually edit the .ini files, but Zend Server keeps the configs in a database and under certain conditions overwrites the .ini files. In order to log in to the Zend Server web admin you have to have a license key that expires after 1 year if I recall correctly. In order to get a license key you have to talk to a salesperson, wait sometimes weeks for them to get back to you, and put up with their sales pitches.
Another pain point that I and many others have experienced: Zend Server is an unnecessary additional point-of-failure. Remember this?
https://zend18.zendesk.com/hc/en-us/articles/203890456-After-upgrading-to-IBM-i-7-2-or-higher-the-ZENDPHP7-or-ZENDSVR6-Apache-instance-will-not-start
Our production applications were down for 24 hours while I tried to trace down this bug.
One of the many existing pain points: In order to make php configuration changes, you must make the changes from within the Zend Server web administration UI. You can manually edit the .ini files, but Zend Server keeps the configs in a database and under certain conditions overwrites the .ini files. In order to log in to the Zend Server web admin you have to have a license key that expires after 1 year if I recall correctly. In order to get a license key you have to talk to a salesperson, wait sometimes weeks for them to get back to you, and put up with their sales pitches.
Another pain point that I and many others have experienced: Zend Server is an unnecessary additional point-of-failure. Remember this?
https://zend18.zendesk.com/hc/en-us/articles/203890456-After-upgrading-to-IBM-i-7-2-or-higher-the-ZENDPHP7-or-ZENDSVR6-Apache-instance-will-not-start
Our production applications were down for 24 hours while I tried to trace down this bug.
One of the many existing pain points: In order to make php configuration changes, you must make the changes from within the Zend Server web administration UI. You can manually edit the .ini files, but Zend Server keeps the configs in a database and under certain conditions overwrites the .ini files. In order to log in to the Zend Server web admin you have to have a license key that expires after 1 year if I recall correctly. In order to get a license key you have to talk to a salesperson, wait sometimes weeks for them to get back to you, and put up with their sales pitches.
Another pain point that I and many others have experienced: Zend Server is an unnecessary additional point-of-failure. Remember this?
https://zend18.zendesk.com/hc/en-us/articles/203890456-After-upgrading-to-IBM-i-7-2-or-higher-the-ZENDPHP7-or-ZENDSVR6-Apache-instance-will-not-start
Our production applications were down for 24 hours while I tried to trace down this bug.
One of the many existing pain points: In order to make php configuration changes, you must make the changes from within the Zend Server web administration UI. You can manually edit the .ini files, but Zend Server keeps the configs in a database and under certain conditions overwrites the .ini files. In order to log in to the Zend Server web admin you have to have a license key that expires after 1 year if I recall correctly. In order to get a license key you have to talk to a salesperson, wait sometimes weeks for them to get back to you, and put up with their sales pitches.
Another pain point that I and many others have experienced: Zend Server is an unnecessary additional point-of-failure. Remember this?
https://zend18.zendesk.com/hc/en-us/articles/203890456-After-upgrading-to-IBM-i-7-2-or-higher-the-ZENDPHP7-or-ZENDSVR6-Apache-instance-will-not-start
Our production applications were down for 24 hours while I tried to trace down this bug.
Viva La 'yum install php'!