Date: Fri, 29 Mar 2024 06:01:49 +0000 (UTC) Message-ID: <857205114.444.1711692109958@library.aws.roguewave.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_443_528864749.1711692109957" ------=_Part_443_528864749.1711692109957 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Zend does not have any official recommendations for what should be repli= cated to the DR machine in a high availability setting. Replication setting= s are the responsibility of the customer. However, here are some tips from = Zend Support that may be helpful.
Zend Server for IBM i, any supported version, running on any supported v= ersion of IBM i
Note: The only way to be sure your DR = is working is to test it.
Zend Support strongly recommends t= hat you test fail-over once everything is set up, and test it periodically = to verify that your HA solution is working for you.
Do not replicate directories installed= by the Zend Server Licensed Program
It is important not to replicate d= irectories that are registered to a Licensed Program. This is particularly = true for an application like Zend Server where the customer makes changes i= n the registered directories. So, we strongly recommend not to replicate /w= ww/zendphp74 and /usr/local/zendphp74, and do not replicate anything under = either one of these directories. Instead, install Zend Server on each machi= ne at the same release version. All changes should to be done twice, = once on each machine. This applies to configuration changes, updates, deplo= ying applications if you use Zend Server to do that, and anything else that= might happen in these directory structures. Since all maintenance is performed on both machines, it will= not be necessary to replicate the ZENDPHP74 (or ZENDPHP7 Zend Server 9.1.x= - 2019.x or ZENDSVR6 Zend Server 6 - 8.5.x) library.
Place content and sessions elsewhere t= o replicate them
To replicate your application file= s (.php, .htm, .css, .js, and so on) put them in some directory that is not= under /www/zendphp74. Use Alias or Virtual Host in your Apache confi= g to use your application out of this directory.
Files output by your application, =
like PDF, spreadsheets, and other kinds of files your app produces that are=
stored on the IFS, should all be located outside the registered directorie=
s. This will allow you to replicate those files safely.
If you wish to retain sessions on = failover, you can specify a sessions directory outside of the Zend Server d= irectory server by setting the session.save_path directive. Remember this s= etting needs to be changed on both machines. You may also consider ju= st not replicating sessions if session loss does not have a major impact wh= en using your application.
Do not replicate the Zend Server db di= rectory
If you are replicating other direc= tories in Zend Server (not recommended), we do not recommend replica= ting the db directory because of the very large number of transactions that= would be pushed through replication. The full path for this directo= ry is:
/usr/local/zendphp74/var/db (/usr/local/zendphp7/var/db for versions 9= .1-2019 /usr/local/zendsvr6/var/db for versions 6-8.5)
PowerHA only replicates from independe= nt ASP, so it will not be possible to replicate the zend library and direct= ories.
Because Zend Server is installed a= nd updated via PTF as a Licensed Program, it must remain in the *SYSBAS ASP= . This is because the APYPTF command requires all objects to be in *S= YSBAS at the time of update. For PowerHA users, you will not be able = to replicate any Zend Server directories.
Never use Mimix to replicate /usr/loca= l/zendphp7/tmp
Some products like Mimix rely on journaling the IFS folders to perform r= eplication. You should never journal this folder:
/usr/local/zendphp74/tmp (/usr/lo= cal/zendphp7/tmp for versions 9.1-2019 /usr/local/zendsvr6/tmp for versio= ns 6-8.5)
This folder contains shared memory= objects and other IPC objects that do not function correctly when journale= d. Never journal this folder. Do not replicate it. If you= are replicating other directories in Zend Server (not recommended), in the= event of a failover, restart Zend Server on the failover box using the res= et option on the menu. This will clear the shared memory and start fr= esh:
Note: The only way to be sure your DR = is working is to test it.
Zend Support strongly recommends t= hat you test fail-over once everything is set up, and test it periodically = to verify that your HA solution is working for you.