Press Release: Zend and IBM

khess 0 Tallied Votes 903 Views Share

If you are a PHP, Zend or IBM fan, today Zend and IBM announce a major release for IBM i-Series Servers. Zend Technologies and IBM are working together to offer PHP solutions for IBM i customers. Today Zend announced Zend Server for IBM i, a Web Application Server for applications running on IBM i and Power System servers. (see attached or click on links below for more)

What’s New from Zend and IBM

Zend Server for IBM i – Runtime and Management Features
· Business-grade PHP – An up-to-date, fully tested, supported and documented PHP stack ensures high reliability and minimal risk.
· Rapid response to problems – Application monitoring and diagnostics enable early problem detection and quick root cause analysis.
· Optimal application performance – Built-in optimization, acceleration and job queue ensure high performance and low resource utilization.
· Leveraging the power of IBM i – A 5250 bridge and PHP toolkit make PHP applications easy to build and run on IBM i.

How Customers Benefit

Zend and IBM combine the power of IBM i with the ease and flexibility of Zend PHP to:
· Streamline web application development and deployment on IBM i.
· Minimize the risk and cost of modernizing applications by choosing PHP.
· Maximize investment in System i infrastructure.
· Leverage Zend PHP solutions for the full application development life cycle.

Read the full .

Dani AI

Generated

Good find . For anyone landing here later and thinking about testing Zend + IBM on an i/System environment: the press release explains the announcement. Below is a compact, practical checklist and a few quick troubleshooting notes you can use to move from reading the announcement to running a low-risk pilot.

  • Stage environment: mirror production OS level, installed libraries and user accounts, then run your full test suite before any cutover.
  • Extensions and modules: confirm every PHP extension and PECL module your app needs is available and working; build missing modules from source in the IBM i runtime/IFS environment when necessary.
  • Database connectivity: validate the exact DB driver you will use (ibm_db2, PDO_IBM, or ODBC). Test connections, transactions, prepared statements and charset mapping with representative data.
  • File system and encoding: test all file I/O against IFS paths and CSV import/export routines. Check CCSID/EBCDIC vs ASCII conversion and whitespace/newline handling.
  • Sessions and scheduled jobs: verify web session storage under the web runtime and that scheduled/CLI PHP jobs run with the same binary, PATH and permissions as the web processes.
  • Performance and monitoring: capture a baseline, enable an opcode cache when present, and run realistic load tests. Collect slow-query traces and memory/CPU profiles.
  • Security and rollback: verify least-privilege for web/PHP accounts, confirm SSL/TLS termination, and prepare a snapshot/rollback plan prior to production deploy.

Quick troubleshooting pointers:

  • Connection errors: run a minimal connect script, check driver install and user authorities, and inspect job/server logs for detailed errors.
  • Garbled text: inspect CCSID settings and perform explicit charset conversions when reading/writing shared files or DB fields.
  • Scheduled tasks failing: confirm the job runs the expected PHP binary, has correct env vars, and the invoking user has necessary file and DB permissions.

For legacy business logic, prefer wrapping existing functions as services and migrate incrementally rather than a big-bang rewrite. Thanks again to for posting this; the checklist above is aimed at turning the announcement into a short, low-risk evaluation plan.

theighost -2 Junior Poster

well gee, thanks for the info Ken :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.