Oracle® Application Server Web Cache Administrator's Guide
10g (9.0.4) Part No. B10401-02 |
|
![]() |
![]() |
If you are running OracleAS Web Cache in a standalone environment (that is, you installed OracleAS Web Cache from a kit that included only this product; you did not install OracleAS Web Cache as part of an Oracle Application Server installation), there are some differences in how you administer OracleAS Web Cache. This appendix describes those differences.
This appendix contains these topics:
If you are running OracleAS Web Cache in a standalone environment (that is, you installed OracleAS Web Cache from a kit that included only this product; you did not install OracleAS Web Cache as part of an Oracle Application Server installation), note the following differences in how you administer OracleAS Web Cache:
OracleAS Web Cache has three processes, rather than two processes. On Windows, two of these processes are Windows services. See "OracleAS Web Cache Processes" for more information.
You use the OracleAS Web Cache Manager and the webcachectl
utility, rather than Oracle Process Manager and Notification (OPMN) Server, to start, stop, and restart the OracleAS Web Cache processes. (In most cases, you can use the OracleAS Web Cache Manager to start, stop, and restart the processes.) See "webcachectl Utility Overview" for more information.
In a standalone environment, OracleAS Web Cache has three processes:
The admin
server process manages the OracleAS Web Cache Manager interface.
In standalone environments on Windows, the admin
server process is represented by the Oracle
HOME_NAME
WebCacheAdmin
service.
The cache
server process manages the cache.
In standalone environments on Windows, the cache
server process is represented by the Oracle
HOME_NAME
WebCache
service.
If enabled, the auto-restart
process checks that the cache
server process is running and automatically restarts the cache
server process if it is not running. (In an environment where you have installed OracleAS Web Cache as part of an Oracle Application Server installation, the auto-restart mechanism is controlled by OPMN and is not a process.)
Because the auto-restart
process is dependent upon the cache
server process, you administer it by starting, stopping, or restarting the cache
server process.
In most cases, you can use the OracleAS Web Cache Manager to start, stop, and restart the processes. However, in previous releases, OracleAS Web Cache also provided the webcachectl
utility to start, stop, and restart the admin
server process, the cache
server process, and the auto-restart
process. Beginning with OracleAS Web Cache release 9.0.4, when OracleAS Web Cache is installed as part of an Oracle Application Server installation, you must use OPMN rather than the webcachectl
utility.
If you are running OracleAS Web Cache in a standalone environment (that is, you installed OracleAS Web Cache from a kit that included only this product; you did not install OracleAS Web Cache as part of an Oracle Application Server installation), you use the webcachectl
utility to administer the OracleAS Web Cache processes: the admin
server, cache
server, and auto-restart
processes.
Note: If you invoke thewebcachectl utility in an environment where you have installed OracleAS Web Cache as part of an Oracle Application Server installation, OracleAS Web Cache returns an error.
See:
|
The webcachectl
executable is located in the $ORACLE_HOME/webcache/bin
directory on UNIX and the ORACLE_HOME
\bin
directory on Windows.
The syntax for this utility is as follows:
webcachectl command [parameter]
In standalone environments on Windows, you can also start or stop OracleAS Web Cache through the Control Panel:
Select the Services icon in the Control Panel window.
The Services window appears.
Select the Oracle
HOME_NAME
WebCacheAdmin
service to start the admin
server process, and then click Start or Stop.
Select the Oracle
HOME_NAME
WebCache
service to start the cache
server process, and then click Start or Stop. This service also starts and stops the auto-restart process.
In the Services window, click Close.
The commands for the webcachectl
utility are described in the next sections. The start
, stop
, and restart
commands enable you to administer all three processes. You can save system resources by administering only the processes you require.
The *adm
commands enable you to administer the admin
server process.
The admin
server process is the only process required during configuration with the OracleAS Web Cache Manager. After OracleAS Web Cache Manager configuration is complete, the admin
server process is no longer needed unless you want to monitor the cache using the OracleAS Web Cache Manager.
The *cache
commands enable you to administer the cache
server process, and if enabled, the auto-restart
process.
The cache
server process is the only process required to run the cache.
Use the reset
command to restore the configuration to the last version saved with Apply Changes button in the OracleAS Web Cache Manager. This command also stops any running processes.
The following message displays:
Previous configuration restored. You must restart OracleAS Web Cache for it to run with that configuration. Web Cache admin server is already down. Web Cache auto-restart monitor is already down. Web Cache cache server is already down.
Use the restart
command to stop and then restart the admin
server, cache
server, and, if enabled, the auto-restart
processes. The following message displays:
Web Cache admin server stopping. Web Cache auto-restart monitor stopping. Web Cache cache server stopping. OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Admin Server now running as process 17722 Admin Server is attempting to start the Cache Server OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Cache Server now running as process 17724
Use the restartadm
command to stop and then restart the admin
server process. The following message displays:
Web Cache admin server is already down. OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Admin Server now running as process 17729 Admin Server running in admin-only mode. Cache Server NOT started
Use the restartcache
command to stop and then restart the cache
server process and, if enabled, the auto-restart
process. The following message displays:
Web Cache admin server stopping. Web Cache auto-restart monitor is already down. Web Cache cache server stopping. OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Admin Server now running as process 8919 Admin Server is attempting to start the Cache Server OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Cache Server now running as process 8921
Use the start
command to start the admin
server, cache
server process, and, if enabled, the auto-restart
process. The following message displays:
OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Admin Server now running as process 8911 Admin Server is attempting to start the Cache Server OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Cache Server now running as process 8913
Use the startadm
command to start the admin
server process. The following message displays:
OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Admin Server now running as process 8971 Admin Server running in admin-only mode. Cache Server NOT started
Use the startcache
command to start the cache
server process and, if enabled, the auto-restart
process. The following message displays:
OracleAS Web Cache, Version 9.0.4.0.0 Copyright c 1999, 2003, Oracle. All rights reserved. Cache Server now running as process 17752
Use the status
command to find out if the admin
server process, cache
server process, and, if enabled, the auto-restart
process, are running or not running.
The following message displays when all three processes are not running:
Web Cache admin server is not running. Web Cache auto-restart monitor is not running. Web Cache cache server is not running.
The following message displays when all three processes are running:
Web Cache admin server is running as process 16274. Web Cache auto-restart is running as process 16275. Web Cache cache server is running as process 16273.
Use the stop
command to stop the admin
server process, cache
server process, and, if enabled, the auto-restart
process. With the stop
command, the cache
server process does not accept any new connections, but it completes the requests of all existing connections before it shuts down. The following message displays:
Web Cache admin server stopping. Web Cache auto-restart monitor is already down. Web Cache cache server stopping.
Use the stopabort
command to stop the admin
server process, cache
server process, and, if enabled, the auto-restart
process. With the stopabort
command, the cache
server process does not accept any new connections, drops all existing connections, and shuts down.
The following message displays:
Web Cache admin server stopping. Web Cache auto-restart monitor stopping. Web Cache cache server stopping.
Use the stopadm
command to stop the admin
server process. The following message displays:
Web Cache admin server stopping.
Use the stopcache
command to stop the cache
server process and, if enabled, the auto-restart
process. With the stopcache
command, the cache
server process does not accept any new connections, but it satisfies the requests of all existing connections before it shuts down. The following message displays:
Web Cache auto-restart monitor stopping. Web Cache cache server stopping.