PHP dynamic programming language
When modernizing applications, we help organizations select a software architecture that’s flexible, yet can last many years.
A recent article about our client K3S got our attention. Author Alex Woodie wrote that the inventory forecasting software vendor had updated their package with an attractive web-based interface using PHP, while adapting their existing RPG code into APIs written in RPG.
But I knew there was more to this story. So I asked King Harrison IV—K3S’s executive vice president, friend, and founding member of Club Seiden— to elaborate on their choice of RPG APIs.
We recently worked with a large financial services company that wanted to enable real-time data updates between Salesforce and applications running on both IBM i and a Linux-based system.
Every day, people from a variety of departments entered customers, leads, and orders into these systems. The salespeople, however, needed to access the most current information from within Salesforce.
We’ve recently been getting requests to help upgrade the venerable Zend Framework 1 (ZF1) to newer PHP frameworks. The effort is necessary but not trivial. To help you succeed with your migration, here are some suggestions.
This week marked our 6th anniversary, evolving from “just Alan” to the amazing team at Seiden Group.
This milestone got me wondering…with as much change as we’ve seen over the past six years with PHP and Zend Server, how many PHP environments out there are four, five, or six or more years old?
Sometimes a fresh perspective makes all the difference.
I recently needed to cancel a WebEx meeting. I clicked the menu item to cancel the meeting and was presented with this dialog box:
The open source Composer tool, which manages PHP project dependencies, has become standard equipment for modern PHP. New to this tool? I recommend this introduction to Composer.
Composer automatically installs or updates required components, known as dependencies, and any others required by those initial components. The required components are defined by the developer in an easy-to-read JSON-formatted text file.
Developers coming from a non-IBM i background know how to run the apachectl command to start, restart, and end an Apache web server instance. Instead of apachectl, however, IBM i provides a web-based graphical interface and the commands STRTCPSVR and ENDTCPSVR (be sure to prompt those for parameters using F4).
To supply the “missing” apachectl command for IBM i, I have written a BASH shell script that simulates apachectl on IBM i.
You’re sure you fixed that last bug, but the app is still malfunctioning. You’re racking your brain for the cause. Paradoxically, the more you know about programming, the more likely you are to over-think the problem.
I’ve been there. My Seiden Group colleagues have taken to calling me their “CTO” (Chief Troubleshooting Officer), for my debugging skills.
Before you wear yourself out seeking obscure bugs, try these sanity checks:
Recently we’ve heard from several clients seeking help with Zend Server upgrades. While generally straightforward, upgrades can require an extra step with very old versions of Zend Server. “Old” means Zend Core or Zend Server 5.1 or earlier. Upgrades from these old versions may require a migration from Easycom to the “new” PHP to IBM i toolkit.