Starting a proxy server

Starting a proxy server starts a new server process based on the process definition settings of the current proxy server configuration.

Before you begin

Before you start a proxy server, verify that all of the resources that the proxy requires are available. You must also start all prerequisite subsystems.

Avoid trouble: All proxy server processes are performed in the controller because you cannot configure a servant for a proxy server. Therefore, because application modules cannot be deployed into a controller, you cannot deploy an application module into a proxy server. If an application that you are running on a proxy server includes an application module, such as a module that serves an error page if a proxy server routing error occurs, that application module must be deployed to the servant of an application server with which the proxy server can communicate, instead of to the proxy server.

• For the z/OS® and distributed platforms, except AIX®, you can issue the startServer command from the command line to start a single proxy server.
  You can issue the startServer command from the C:\WebSphere\AppServer\profiles\AppSrv02\bin directory.

  #  .\startServer.sh proxyserver1
  

  You can issue the startServer command from the /usr/WebSphere/AppServer/bin directory.

  #  ./startServer.sh proxyserver1
  

  When a server is started, a new temp directory is created off of the servant process token, such as profile_root/default/temp/node_name/server_name. When the server is cleanly stopped, these temp directories are removed. However, if you infrequently perform graceful shutdowns, which happens if you cancel rather than stop the server, then these temp directories are not removed and the hierarchical file system (HFS) used for these temp directories eventually becomes full. You prevent this storage problem from occurring if you precompile your JavaServer pages (JSPs) when you install a proxy server or if you use the JspBatchCompiler function to precompile them before they are invoked.

• You can use the administrative console to start a proxy server.
  1. In the administrative console, click Servers > Server Types > WebSphere proxy servers > .
  2. Select the proxy server that you want to start, and click Start.
  3. Confirm that you want to start the proxy server.
  4. View the Status value and any messages or logs to see whether the proxy server was started.
• You can use the startServer Qshell command to start a proxy server.
• You can use the Submit Job (SBMJOB) CL command to start a proxy server.
  Enter the following line of code to use the SBMJOB CL command.

  SBMJOB JOB(jobNumber/QEJBSVR/jobName) OPTION(*CNTRLD) DELAY(delayTime)
  

  In this example, jobNumber is the job number, jobName is the name of the proxy server job, and delayTime is the amount of time, in seconds, to wait for the job to start. You can initially set delayTime to 600 seconds and then adjust the value, if necessary, to a value that is more appropriate for your environment.