The port number used by a WebFacing application to communicate with
the WebFacing server can be changed for the project as a whole or for individual
CL commands. Ports defined for CL commands take precedence over the port defined
for your project. Each CL command that your application uses will have a separate
link for it in the index.html file that is created by the WebFacing conversion.
If necessary, you can define a different host and associated port for each
link. One reason for defining CL commands that use different hosts or ports
is if you have a WebFacing project that accesses applications on more than
one server. Port changes for your project or CL commands are stored in the
deployment descriptor file web.xml.
Note: If you are changing a port setting
used by a project that has already been deployed, generally, you must re-deploy
and then restart the application in the WebSphere Administrative Console.
Alternatively, you can search for the IFS location on your iSeries server
where your WebFacing Web application's web.xml file is installed and redeploy
from the workbench just that one file. This alternative method still requires
a restart of the application. However, it can be a convenient method of changing
the ID and password if your application is large.