Package Implementation from the Web (Release 9.2.5)

Starting with Tools Release 9.2.5.0, you can assemble, define, and deploy a package from the web. A new deployment server service, JD Edwards B9 Client Network, which runs on the deployment server has been introduced. You control this service through the deployment server instance in the Server Manager and you can start and stop this service through the Server Manager. The JD Edwards B9 Client Network service accepts messages from the enterprise server and starts the client package build. Additionally, this service accepts the files that are being transferred from the enterprise server to the deployment server. This service must be running if you deploy a client package from the web.

To run a web package, a new service for the deployment server must be started during the Tool releases install of the server manager. Refer "Change Component for the Deployment Server (Release 9.2.5)" in the JD Edwards EnterpriseOne Tools Server Manager Guide

If you define a server or a client package and submit a build from the web when the JD Edwards B9 Client Network service is down, the package will fail because the service cannot connect to the deployment server to build the client package. However, if you define a server-only package and submit the build when the JD Edwards B9 Client Network service is down, the package will continue to run without connecting to the deployment server and the system will finish the package on the enterprise server.

When you run a server or a client package from the web, the port number of the enterprise server that the web is accessing must match the port number of the deployment server in jde.ini. To change the port number on the deployment server, access the Server Manager and select the deployment server instance. You must stop the services, change the port number in jde.ini, and restart the service to enable the web package to access the deployment server.