Steps for Distributing a New Version of an Application Making an Application Available to Clients

Redeploying Applications in a Production Environment 8-11

8.4.1 Steps for Distributing a New Version of an Application

The basic steps for distributing a new version of an application in Administration mode are nearly the same as those documented in Section 8.3.6, Redeploying a New Version of an Application . You simply use the weblogic.Deployer -distribute command, rather than the -redeploy command, as in: java weblogic.Deployer -adminurl http:localhost:7001 -user weblogic -password weblogic -distribute -name myTestDeployment -source myDeploymentsmyApplication1.0GA -appversion 1.0GA Once the application is distributed, start it in Administration mode: java weblogic.Deployer -adminurl http:localhost:7001 -user weblogic -password weblogic -start -adminmode -name myTestDeployment -source myDeploymentsmyApplication1.0GA -appversion 1.0GA Starting the application in Administration mode makes it available only via a configured Administration channel. See Configuring Network Resources in Configuring Server Environments for Oracle WebLogic Server. Optionally, specify the retirement policy or timeout period for distributed applications.

8.4.2 Making an Application Available to Clients

After performing final testing using the configured Administration channel, you can open the distributed version of the application that is running in Administration mode to new client connections by using the weblogic.Deployer -start command without the -adminmode option: 1. Use the Administration Console to view the version and state information of both application versions: a. Verify that both versions of the application are still deployed.erify that both versions of the application are still deployed. b. Note the version identifier of the application version that is running in Administration mode. 2. Use the -appversion option to weblogic.Deployer to start the application that was distributed and deployed in Administration mode: java weblogic.Deployer -adminurl http:localhost:7001 -user weblogic -password weblogic -start -name myTestDeployment -appversion .91Beta By default WebLogic Server routes new client requests to the application version that was previously distributed and running in Administration mode. Existing clients continue using the older application until their work is complete and the older application can be safely undeployed. If you want to specify a fixed time period after which the older version of the application is retired regardless of whether clients finish their work, use the -retiretimeout option: java weblogic.Deployer -adminurl http:localhost:7001 -user weblogic -password weblogic -start -name myTestDeployment -appversion .91Beta -retiretimeout 300 -retiretimeout specifies the number of seconds after which the older version of the application is retired. 8-12 Deploying Applications to Oracle WebLogic Server 3. Use the Administration Console to verify that the previously-distributed application is now active, and that the former application version is now retiring. See Section 8.3.5, Displaying Version Information for Deployed Applications .

8.4.3 Best Practices for Using Production Redeployment