{"id":3602,"date":"2011-10-17T09:03:15","date_gmt":"2011-10-17T14:03:15","guid":{"rendered":"http:\/\/jianmingli.com\/wp\/?p=3602"},"modified":"2012-07-23T14:57:12","modified_gmt":"2012-07-23T19:57:12","slug":"weblogic-11g-deploying-with-weblogic-deployer","status":"publish","type":"post","link":"https:\/\/jianmingli.com\/wp\/?p=3602","title":{"rendered":"WebLogic 11g: Deploying with weblogic.Deployer"},"content":{"rendered":"
\n

Contents<\/h2>\n
    \n\t
  1. \n\t\tUploading Deployment Files from a Remote Client<\/a>\n\t<\/li>\n\t
  2. \n\t\tDeploying to a Single-Server Domain<\/a>\n\t<\/li>\n\t
  3. \n\t\tDeploying an Application with a Deployment Plan<\/a>\n\t<\/li>\n\t
  4. \n\t\tDeploying an Application That Looks Up System Resources from JNDI During preStart<\/a>\n\t<\/li>\n\t
  5. \n\t\tTargeting Deployments to Servers, Clusters, and Virtual Hosts<\/a>\n\t<\/li>\n\t
  6. \n\t\tUsing Module-Level Targeting for Deploying an Enterprise Application<\/a>\n\t\t
      \n\t\t\t
    1. \n\t\t\t\tTarget individual modules in an enterprise application<\/a>\n\t\t\t<\/li>\n\t\t\t
    2. \n\t\t\t\tTargeting Web Application Modules<\/a>\n\t\t\t<\/li>\n\t\t<\/ol>\n\t
    3. \n\t\tDeploying JDBC, JMS, and WLDF Application Modules<\/a>\n\t\t
        \n\t\t\t
      1. \n\t\t\t\tTargeting Application-Scoped JMS, JDBC, and WLDF Modules<\/a>\n\t\t\t<\/li>\n\t\t\t
      2. \n\t\t\t\tSub-module Targeting for Standalone JMS Modules<\/a>\n\t\t\t<\/li>\n\t\t\t
      3. \n\t\t\t\tSub-module Targeting for Application-scoped JMS Modules<\/a>\n\t\t\t<\/li>\n\t\t<\/ol>\n\t
      4. \n\t\tDeployment Stage Modes<\/a>\n\t\t
          \n\t\t\t
        1. \n\t\t\t\tnostage Mode<\/a>\n\t\t\t<\/li>\n\t\t\t
        2. \n\t\t\t\tstage Mode<\/a>\n\t\t\t<\/li>\n\t\t\t
        3. \n\t\t\t\texternal_stage Mode<\/a>\n\t\t\t<\/li>\n\t\t\t
        4. \n\t\t\t\tChanging the Default Staging Behavior for a Server<\/a>\n\t\t\t<\/li>\n\t\t<\/ol>\n\t
        5. \n\t\tDistributing Applications to a Production Environment<\/a>\n\t\t
            \n\t\t\t
          1. \n\t\t\t\tOverview<\/a>\n\t\t\t<\/li>\n\t\t\t
          2. \n\t\t\t\tSyntax<\/a>\n\t\t\t<\/li>\n\t\t\t
          3. \n\t\t\t\tStart Application in Admin Mode<\/a>\n\t\t\t<\/li>\n\t\t<\/ol>\n\t
          4. \n\t\tDeploying Shared Java EE Libraries and Dependent Applications<\/a>\n\t<\/li>\n<\/ol>\n<\/ol>\n<\/div>\n
             <\/div>\n

            Uploading Deployment Files from a Remote Client<\/h2><\/span>\n
            \r\njava weblogic.Deployer \\\r\n    -adminurl http:\/\/localhost:7001 \\\r\n    -username weblogic \\\r\n    -password weblogic \\\r\n    -deploy \\\r\n    -upload \\\r\n    c:\\localfiles\\myapp.ear\r\n<\/pre>\n
            * Uploaded to server’s upload directory (defaults to ?).<\/p>\n
            Deploying to a Single-Server Domain<\/h2><\/span>\n
            \r\njava weblogic.Deployer \\\r\n   -adminurl http:\/\/localhost:7001 \\\r\n   -username weblogic \\\r\n   -password weblogic \\\r\n   -deploy \\\r\n   -name myTestApplication \\\r\n   c:\\localfiles\\myapp.ear\r\n<\/pre>\n
            Deploying an Application with a Deployment Plan<\/h2><\/span>\n
            \r\njava weblogic.Deployer \\\r\n\t-adminurl http:\/\/localhost:7001 \\\r\n\t-username weblogic \\\r\n\t-password weblogic \\\r\n\t-deploy \\\r\n\t-name myTestDeployment \\\r\n\t-source \/myDeployments\/installedApps\/myApplication\/app\/myApplication.ear \\\r\n\t-targets myCluster \\\r\n\t-stage \\\r\n\t-plan \/myDeployments\/installedApps\/myApplication\/plan\/plan.xml\r\n<\/pre>\n
            Deploying an Application That Looks Up System Resources from JNDI During preStart<\/h2><\/span>\n
            * Create and activate desired system resources in a separate session before deploy the application that relies on it.<\/p>\n
            Targeting Deployments to Servers, Clusters, and Virtual Hosts<\/h2><\/span>\n
            * Deploy to sinple target:<\/p>\n
            \r\njava weblogic.Deployer \\\r\n\t-adminurl http:\/\/localhost:7001 \\\r\n\t-username weblogic \\\r\n\t-password weblogic \\\r\n\t-deploy \\\r\n\t-targets companyHost c:\\localfiles\\myWebApp.ear\r\n<\/pre>\n
            * Deploy to more than one targets:<\/p>\n
            \r\njava weblogic.Deployer \\\r\n    -adminurl http:\/\/localhost:7001 \\\r\n    -username weblogic \\\r\n    -password weblogic \\\r\n    -deploy \\\r\n    -targets ManagedServer-1,ManagedServer-2 \\\r\n    c:\\localfiles\\myapp.ear\r\n<\/pre>\n
            * Deploy to a cluster target:
            \n– To enforce strict deployment for all servers configured in a cluster:<\/p>\n
            \r\n-DClusterConstraintsEnabled=true\r\n<\/pre>\n
            Using Module-Level Targeting for Deploying an Enterprise Application<\/h2><\/span>\n
            Target individual modules in an enterprise application<\/h3><\/span>\n
            \r\njava weblogic.Deployer \\\r\n\t-adminurl http:\/\/localhost:7001 \\\r\n\t-username weblogic \\\r\n\t-password weblogic \\ \r\n\t-name myEnterpriseApp \\\r\n\t-targets module1@myserver1,module2@myserver2,module3@myserver3 \\\r\n\t-stage \\\r\n\t-deploy c:\\localfiles\\myEnterpriseApp.ear\r\n<\/pre>\n
            Targeting Web Application Modules<\/h3><\/span>\n
            – To target Web application modules that are part of an .ear file, you can use the Web application’s context-root name as the module name or specify the web-uri.
            \n– If<\/p>\n
            \r\n\r\n  \r\n    myweb.war<\/web-uri>\r\n    \/welcome<\/context-root>\r\n  <\/web>\r\n<\/module>\r\n<\/pre>\n
            You can use context-root:<\/p>\n
            \r\njava weblogic.Deployer \\\r\n\t-adminurl http:\/\/localhost:7001 \\\r\n\t-username weblogic \\\r\n\t-password weblogic \\\r\n\t-name mywebapplication \\\r\n\t-targets \/welcome@myserver1 \\\r\n\t-stage \\\r\n\t-deploy c:\\localfiles\\myEnterpriseApp.ear\r\n<\/pre>\n
            Or web uri:<\/p>\n
            \r\njava weblogic.Deployer \\\r\n\t-adminurl http:\/\/localhost:7001 \\\r\n\t-username weblogic \\\r\n\t-password weblogic \\\r\n\t-name mywebapplication \\\r\n\t-targets myweb.war@myserver1 \\\r\n\t-stage \\\r\n\t-deploy c:\\localfiles\\myEnterpriseApp.ear\r\n<\/pre>\n
            – For default context root, i.e. ‘\/’<\/p>\n
            \r\n\r\n  \r\n    myweb.war<\/web-uri>\r\n    \/<\/context-root>\r\n  <\/web>\r\n<\/module>\r\n<\/pre>\n
            Then only<\/strong context-root can be used:\n\n\n
            \r\njava weblogic.Deployer \\\r\n\t-adminurl http:\/\/localhost:7001 \\\r\n\t-username weblogic \\\r\n\t-password weblogic \\\r\n\t-name mywebapplication \\\r\n\t-targets \/@myserver1 \\\r\n\t-stage \\\r\n\t-deploy c:\\localfiles\\myEnterpriseApp.ear\r\n<\/pre>\n
            Deploying JDBC, JMS, and WLDF Application Modules<\/h2><\/span>\n
            * Only available to the server to which they are targeted.
            \n– Need to target to multiple servers or cluster to be available on them.<\/p>\n
            Targeting Application-Scoped JMS, JDBC, and WLDF Modules<\/h3><\/span>\n
            * Application-scoped resource modules can be targeted independently of other EAR modules during deployment, if necessary, by using module-level targeting syntax.
            \n* For example:<\/p>\n
            \r\njava weblogic.Deployer \r\n\t-adminurl http:\/\/localhost:7001 \r\n\t-username weblogic\r\n\t-password weblogic \r\n\t-name myEnterpriseApp\r\n\t-targets myWebApp@myCluster,myJDBCModule@myserver1,myEJBModule@myserver1 \r\n\t-stage \r\n\t-deploy c:\\localfiles\\myEnterpriseApp.ear\r\n<\/pre>\n
            Sub-module Targeting for Standalone JMS Modules<\/h3><\/span>\n
            * For a standalone JMS module, the submodule targeting syntax is: -submoduletargets submodule_name@target_name.
            \n* For example, to deploy a standalone JMS module on a single server instance, targeting the submodule myQueue to a JMS Server named JMSServer1, enter the command:<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n   -password weblogic -name myJMSModule\r\n   -targets ManagedServer1 -submoduletargets myQueue@JMSServer1\r\n   -deploy c:\\localfiles\\myJMSModule.xml\r\n<\/pre>\n
            * To undeploy the same JMS module, enter the following command, which, assuming myJMSModule contains more than one submodule, will undeploy only the myQueue submodule; all other submodules are unaffected.<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n   -password weblogic -name myJMSModule\r\n   -undeploy -submoduletargets myQueue@JMSServer1\r\n<\/pre>\n
            Sub-module Targeting for Application-scoped JMS Modules<\/h3><\/span>\n
            * For an application-scoped JMS module in an EAR, use the syntax: submodule_name@module_name@target_name to target a submodule.
            \n* For example, if the queue in the above example were instead packaged as part of an Enterprise application, you would use the command:<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n   -password weblogic -name myEnterpriseApp\r\n   -targets ManagedServer1 -submoduletargets myQueue@myJMSModule@JMSServer1\r\n   -deploy c:\\localfiles\\myEnterpriseApp.ear\r\n<\/pre>\n
            * To undeploy the same JMS module, enter the following command, which, assuming myEnterpriseApp contains more than one submodule, will undeploy only the myQueue submodule; all other submodules are unaffected.<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n   -password weblogic -name myEnterpriseApp\r\n   -undeploy -submoduletargets myQueue@myJMSModule@JMSServer1\r\n<\/pre>\n
            Deployment Stage Modes<\/h2><\/span>\n
            * Determines how deployment files are made available to target servers that must deploy an application or standalone module.
            \n* WebLogic Server provides three different options for staging files:
            \n– stage mode,
            \n– nostage mode,
            \n– external_stage mode.<\/p>\n
            nostage Mode<\/h3><\/span>\n
            * The Administration Server does not copy deployment unit files.
            \n* Stage directory is ignored.
            \n* Instead, all servers deploy using the same physical copy of the deployment files, which must be directly accessible by the Administration Server and target servers.
            \n* With nostage deployments of exploded archive directories, WebLogic Server automatically detects changes to a deployment’s JSPs or Servlets and refreshes the deployment. (This behavior can be disabled if necessary.)
            \n* Default mode used by Admin Console to deploy only to Admin Server.
            \n* Use when
            \n– Deploying to a single-server domain.
            \n– Deploying to a cluster on a multi-homed machine.
            \n– Deploying very large applications to multiple targets or to a cluster where deployment files are available on a shared directory.
            \n– Deploying exploded archive directories that you want to periodically redeploy after changing content.
            \n– Deployments that require dynamic update of selected Deployment Descriptors via the Administration Console.
            \n* Syntax<\/p>\n
            \r\njava weblogic.Deployer \r\n    -adminurl http:\/\/localhost:7001 \r\n    -username weblogic\r\n    -password weblogic \r\n    -name mydeploymentname \r\n   -targets myserver1,myserver2,myserver3 \r\n   -nostage \r\n   -deploy c:\\localfiles\\myapp.ear\r\n<\/pre>\n
            stage Mode<\/h3><\/span>\n
            * The Administration Server first copies the deployment unit source files to the staging directories of target servers.
            \n– The staging directory is named stage<\/strong> by default, and it resides under the target server’s root directory.
            \n* When copying files to the staging directory, the Administration Server creates a subdirectory with the same name as the deployment name.
            \n* The target servers then deploy using their local copy of the deployment files.
            \n* stage mode is the default mode for:
            \n– Administration Console when deploying to more than one<\/strong> WebLogic Server instance.
            \n– Managed Servers.
            \n– weblogic.Deployer uses the target server’s staging mode as the default,
            \n* Use when:
            \n– Deploying small or moderate-sized applications to multiple WebLogic Server instances.
            \n– Deploying small or moderate-sized applications to a cluster.
            \n* Syntax:<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n   -password weblogic -name mydeploymentname \r\n   -targets myserver1,myserver2,myserver3 -stage \r\n   -deploy c:\\localfiles\\myapp.ear\r\n<\/pre>\n
            external_stage Mode<\/h3><\/span>\n
            * Similar to stage mode, i.e. target servers deploy apps using local copies of deployment files.
            \n* You have to copy files to each target server’s staging directory manually<\/strong>.
            \n– Deployment files must be stored in a subdirectory that reflects the deployment name.<\/p>\n
            \r\ncd WL_HOME\/stage\r\nmkdir myEARExternal\/2.0Beta\r\ncp myear myEARExternal\/2.0Beta\r\n<\/pre>\n
            * Use when you deploy very large applications to multiple machines and
            \n– do not have a shared file system
            \n– cannot use nostage mode
            \n* Use the -noversion option to turn off the requirement that deployment files be on the Administration Server, but the -noversion option causes versioning information to be ignored so you cannot use the -noversion option with versioned applications.
            \n* Syntax:<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -name weblogic\r\n   -password weblogic -external_stage -name myEARExternal \r\n   -deploy c:\\myapps\\myear\r\n<\/pre>\n
            Changing the Default Staging Behavior for a Server<\/h3><\/span>\n
            * The server staging mode specifies the default deployment mode for a server if none is specified at deployment time, e.g. weblogic.Deployer.
            \n* You can only change the server staging mode by using the Administration Console or by directly changing the ServerMBean via JMX.
            \n* Changing the server staging mode does not affect existing applications.
            \n– If you want to change the staging mode for an existing application, you must undeploy the application deployment and then redeploy it with the new staging mode.
            \n* How to change<\/p>\n
            \"\"<\/a><\/h6><\/span>\n
            Distributing Applications to a Production Environment<\/h2><\/span>\n
            Overview<\/h3><\/span>\n
            * Copy application deployment files to all target servers and validate it.
            \n* Application can be started in Admin mode after distribution (use the -adminmode option).<\/p>\n
            Syntax<\/h3><\/span>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n     -password weblogic -distribute -name myTestDeployment\r\n     \/myDeployments\/myApplication\/\r\n<\/pre>\n
            Start Application in Admin Mode<\/h3><\/span>\n
            * Restricts access to the application to a configured Administration channel.
            \n* Allows you to distribute the application or new version to a production environment without opening the application to external client connections.
            \n* Need to configure an administration channel.
            \n* Start a Distributed Application in admin mode:<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n     -password weblogic -start -adminmode -name myTestDeployment\r\n     \/myDeployments\/myApplication\/\r\n<\/pre>\n
            * Starting a Distributed Application for new client connections:<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n     -password weblogic -start -name myTestDeployment\r\n<\/pre>\n
            Deploying Shared Java EE Libraries and Dependent Applications<\/h2><\/span>\n
            * A Java EE library is
            \n– a standalone Java EE module,
            \n– multiple Java EE modules packaged in an Enterprise application (EAR),
            \n– or a plain JAR file that is registered with the Java EE application container upon deployment.
            \n* After a Java EE library has been registered, you can deploy Enterprise applications that reference the library.
            \n* Each referencing application receives a copy of the shared Java EE library module(s) on deployment (merging), and can use those modules as if they were packaged as part of the application itself.
            \n* Need to redeploy all referencing applications after new version of library is deployed.
            \n* Deploy as a library:<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n     -password weblogic -deploy -targets myserver1,myserver2\r\n     -library \/deployments\/myLibraryApplication\/\r\n<\/pre>\n
            * Should always specify a libary version number:
            \n– in manifest file
            \n– use libspecver and\/or libimplver options.<\/p>\n
            \r\njava weblogic.Deployer -adminurl http:\/\/localhost:7001 -username weblogic\r\n     -password weblogic -deploy -targets myserver1,myserver2\r\n     -library -libspecver 700 -libimplversion 7.0.0.1Beta \r\n     \/deployments\/myLibraryApplication\/\r\n<\/pre>\n
            * Deploying applications that reference libraries as ususal.
            \n– All referenced libraries are registered on the application’s target servers.
            \n– Registered libraries meet the version requirements of the referencing application.<\/p>\n
            [mv_include id=”3569″]
            \n* weblogic.Deployer Command-Line Reference<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
            Uploading Deployment Files from a Remote Client java weblogic.Deployer \\ -adminurl http:\/\/localhost:7001 \\ -username weblogic \\ -password weblogic \\ -deploy \\ -upload \\ c:\\localfiles\\myapp.ear * Uploaded to server’s upload directory (defaults to ?). Deploying to a Single-Server Domain java weblogic.Deployer … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[104],"tags":[],"class_list":["post-3602","post","type-post","status-publish","format-standard","hentry","category-weblogic11g"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8cRUO-W6","_links":{"self":[{"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/3602","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3602"}],"version-history":[{"count":11,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/3602\/revisions"}],"predecessor-version":[{"id":5454,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=\/wp\/v2\/posts\/3602\/revisions\/5454"}],"wp:attachment":[{"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3602"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3602"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jianmingli.com\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3602"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}