In Stage Mode of Deployment, the application is copied over to the stage directory of the target servers. By default the stage folder is present in the root directory of the server. This mode of deployment is generally used when the application size is not huge.
These are the Steps
Step 1 ). Transfer the War file to the Admin Box in a specific directory.
Step 2 ). Set the Environment.
NOTE: While running the above script please use two DOTs like mentioned above. The first DOT represents that set the Environment in the Current Shell and the second DOT (./) Slash represents that pick up the Script from the current Location. Both DOTs are separated by a single space. Once u run “. ./setWLSEnv.sh” after that try to echo the values of $CLASSPATH and $PATH
Step 3 ). Executed the command line weblogic.Deployer command to deploy the application on the cluster Cluster.
$ java weblogic.Deployer -adminurl t3://localhost:7001 -user weblogic -password weblogic -name HighCPU -stage -targets Cluster -deploy HighCPU.war
weblogic.Deployer invoked with options: -adminurl t3://localhost:7001 -user weblogic -name HighCPU -stage -targets Cluster -deploy HighCPU.war
<Jul 21, 2010 11:11:50 PM PDT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, HighCPU [archive:
/users/dba/oracle/app/HighCPU.war], to Cluster .>
Task 4 initiated: [Deployer:149026]deploy application HighCPU on Cluster.
Task 4 completed: [Deployer:149026]deploy application HighCPU on Cluster.
Target state: deploy completed on Cluster Cluster
The WAR file will be copied over to the stage folder of each Managed Server of the Cluster named Cluster.
The Managed Servers will deploy the copy of the application present of their local stage folder.
If we have a look at the config.xml, we can see the staging-mode as stage.