The term "hot deployment" refers to the redeployment of archive files (WAR/EAR/JAR) and their associated XML descriptor files on a production environment without restarting or bouncing the server.
Some other important points to be noted in production environments are mentioned below
Deploying a new web module to an active OC4J instance has a negative impact on existing sessions. The HTTP sessions for every web application running within the server will be lost.
To avoid this issue on a non-clustered OC4J, define a "persistent directory" in each of web application's orion-web.xml . Existing HTTP sessions will be temporarily stored in this location.
How to define a persistent directory in orion-web.xml?
Specify a relative path to the persistent directory in the root orion-web-app element tag in orion-web.xml.
for eg.
Hi,
ReplyDeleteWe are using OAS 10.1.0.2 for deploying our war. This war contains some config files which are stored in a given directory and referenced from the code. Basically the config file contains the end point of the web service that we will be invoking from our application. We have observed that if we do a redeploy without bouncing the server we get a connection timeout error. Doesnt oracle appln server support hot deployments or do we have to bounce the server each time we deploy the war? Would appreciate your response?
Regards,
Sino