Date: Thu, 28 Mar 2024 20:09:21 +0000 (UTC) Message-ID: <1410854754.403.1711656561804@library.aws.roguewave.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_402_1457355814.1711656561802" ------=_Part_402_1457355814.1711656561802 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The customer is preparing to install a new IBM i, or upgrade = to a newer version of the IBM i operating system, and is currently running = Version 5 of Zend Server for IBM i, and using the Easycom extension to acce= ss native IBM i programs and objects. Zend no longer supports Zend Se= rver 5, and no longer provides Easycom licensing. This article provid= es some high level considerations for how to move to the new IBM i and upgr= ade to the latest version of Zend Server for IBM i. Some of the infor= mation in this article will also be of interest to customers simply wanting= to migrate from Zend Server for IBM i version 5 to the latest version, and= who run applications using the Easycom extension.
Currently running Zend Server 5 for IBM i on any supported ve= rsion of IBM i, preparing to move to a new IBM i machine.
Note: Zend Server for IBM i vers= ion 5 was never tested or supported on IBM i 7.2.
We do not recommend attempting to run version 5 on 7.2.
If the new IBM i will be running 7.2, then please migrate to the latest ver=
sion of
Zend Server for IBM i before moving to the new IBM i.
We discontinued distributing Easycom some time ago, in favor = of the free, open source, XML Toolkit:
http://forums.zend.com/v= iewtopic.php?f=3D113&t=3D41648
Unfortunately, we have had reports that the perpetual Easycom= license will often stop working when migrating to a new machine, or even j= ust upgrading the OS on the same machine, so this is a consideration for yo= u when moving to the new IBM i.
The fastest and easiest way for you to address the issue with= Easycom migration is to simply continue using Easycom. This would involve = purchasing an Easycom license from Aura Equipements. We no longer have a bu= siness relationship with them, but they can be reached via their web site:<= /p>
You could, for example, buy a license for a year, and then yo= u would be able to continue to use Easycom while you develop new versions o= f your applications to use the free XML Toolkit. Or, you could simply conti= nue to use Easycom. As far as we know, they have versions of Easycom that w= ill work with even the latest versions of Zend Server. If you do plan on co= ntinuing with Easycom, then you will benefit from having the latest upgrade= s and fixes by keeping your Easycom license current.
If you have some time to make the conversion, you can go ahea= d and modify your existing applications to use the XML Toolkit. If you are = not using data access functions (like i5_query() or i5_update_record()), th= en you can probably convert rather quickly, using the Compatibility Wrapper= . There is no data access in XML Toolkit, so if you have any of that in you= r Easycom scripts, you would need to convert those functions to use the ibm= _db2 extension functions. That could take a little longer.
Because the upgrade from Zend Server 5 to the latest version = of Zend Server is a migration, this provides a great opportunity to create = and test your new XML Toolkit scripts before switching over to the new vers= ion of Zend Server. However, you would need to do that on your old machine = (or buy an Easycom license), so how much time you have before you need to m= ove to the new machine becomes a factor.
So, how and when you choose to migrate to the latest version = of Zend Server becomes a factor in deciding what to do about Easycom. Here = is some helpful information that can help in understanding the migration pr= ocess:
https://support.zend.com/hc/en= -us/articles/204754108
Basically, you keep Zend Server 5 up and running, and install= the latest version of Zend Server as a new installation. They can both be = running at the same time. You then copy your applications over to the lates= t version of Zend Server. You keep running Zend Server 5 as your production= version while you test your applications running in the latest version of = Zend Server. When you are done testing, you stop using Zend Server 5, and s= tart using the latest version of Zend Server for production.
You have two additional considerations in the implementation = of that plan. First, you need to do something about Easycom. Second, you ne= ed to consider the timing of how soon you plan to move to the new machine.<= /p>
Here are some possible scenarios:
Scenario 1:
- Install the latest version of Zend Server on your old machine.
- Continue using version 5 for production.
- Copy your applications over to the new version of Zend Server.
- In the new version of Zend Server, convert your scripts that use Easycom =
to instead use XML Toolkit and ibm_db2.
- Test your scripts running in the new version. Make any needed changes, un=
til testing is successful.
- After testing, stop using Zend Server 5 and use the new version for produ=
ction.
- Set up the new machine. Only bring over the new version of Zend Server.=
p>
Scenario 2:
- Install the latest version of Zend Server on your old machine.
- Continue using version 5 for production.
- Copy your applications over to the new version of Zend Server.
- Buy an Easycom license and install Easycom into the new version of Zend S=
erver
- Test your scripts running in the new version. Make any needed changes, un=
til testing is successful.
- After testing, stop using Zend Server 5 and use the new version for produ=
ction.
- Set up the new machine. Only bring over the new version of Zend Server.
- If desired, convert your existing Easycom scripts to use XML Toolkit and =
ibm_db2. When this is complete, you can discontinue purchasing Easycom lice=
nsing.
Scenario 3 (not available if the new machine is at IBM i 7.2)=
:
- Set up the new machine. Bring Zend Server 5 over to the new machine.
- Purchase an Easycom license and install the license in version 5.
- Continue using version 5 for production.
- Install the latest version of Zend Server on your new machine.
- Copy your applications over to the new version of Zend Server.
- In the new version of Zend Server, convert your scripts that use Easycom =
to instead use XML Toolkit and ibm_db2.
- Test your scripts running in the new version. Make any needed changes, un=
til testing is successful.
- After testing, stop using Zend Server 5 and use the new version for produ=
ction.
Scenario 4 (not available if the new machine is at IBM i 7.2)=
:
- Set up the new machine. Bring Zend Server 5 over to the new machine.
- Purchase an Easycom license and install the license in version 5.
- Continue using version 5 for production.
- Install the latest version of Zend Server on your new machine.
- Copy your applications over to the new version of Zend Server.
- Install Easycom into the new version of Zend Server
- Test your scripts running in the new version. Make any needed changes, un=
til testing is successful.
- After testing, stop using Zend Server 5 and use the new version for produ=
ction.
- If desired, convert your existing Easycom scripts to use XML Toolkit and =
ibm_db2. When this is complete, you can discontinue purchasing Easycom lice=
nsing.