Deploying a Package Across Ports (Tools Release 9.2.7.5)

Starting with Tools Release 9.2.7.5, you can deploy a full package to a different port with the same path code. The location of the package must be the same directory on both instances of the different ports. This means that in the jde.ini file, under the [BSFN BUILD] BuildArea= <path to build area> points to the same location for both instances with the different ports.

For IBM i, the instance for the different ports usually all point to the same package location, OneWorld\Packages so deploying to a different port does not need a jde.ini setting change.

For UNIX and Windows, if the instances with the different ports are on the same server, then change the jde.ini

[BSFN Build] BuildArea= should point to the location of the package where the package is built for both instances.

Also, ensure that the permission for this directory is set so that the different instance/port can access the package directory.

For UNIX and Windows, if the instances with different ports are on different servers, then the system compresses the server package and the deployment package to a different port. The instances on different servers does not apply for Web packages as the web packages do not copy back the compressed files to the Deployment Server. This only works when you build and deploy from the deployment server or the client machine.

Deployment steps to set up the new package in the pathcode location for zero downtime deployment:

Checks if the running EnterpriseOne port is the same as the built package. On the Enterprise Server under <package name>\ <OS TYPE> is a <servername>.inf that has the port listed. If the port is different than what EnterpriseOne is running, then the system marks it as an across port deploy.
(Windows, UNIX) Creates the package name directory under the deploy location <pathcode>\<bin32\bin64>.
(Windows, UNIX) Copies from the <package name>\<bin32\bin64> to the deploy location <pathcode>\<bin32\bin64>.
(IBM i) Checks jde.ini if the instance has an addendum.
(IBM i) Creates a library with <package name><addendum>. If there is no addendum, then the system creates the <package name> library.
(IBM i) Copies from the unique library name of the package to the <package name><addendum> library or if there is no addendum, then the system creates the <package name> library.
Creates a package name directory under deploy location <pathcode>\spec\<packagename>.
Creates the spec.ini under the deploy location <pathcode>\spec\<packagename>.
Changes the current deployed package in <pathcode>\spec\spec.ini to the new deployed package.
Broadcasts the message that there is a new deployed package.
Updates the F96511 table with the package name, port, and enters 33.
After the full package is deployed, an update package can be deployed to that full package with the different port.