Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Deploy WebLogic on the plugin site for more information.

The current version of this plugin may not be safe to use. Please review the following warnings before use:

This plugin deploys any artifacts built on Jenkins to a weblogic target (managed server, cluster ...) as an application or a library component.

Pre-requisites

This plugin works with at least 1.485 jenkins version.
This plugin only deploys ear, war, jar artifacts.

Configuration

System Configuration

Before use it, the plugin has to be configured. It consists of loading the weblogic target configuration, choosing the default JDK to run a deployment task and adding the weblogic library path :

  • for WLS 8.X /pathtojar/weblogic.jar
  • for WLS 10.3 /pathtojar/wlfullclient.jar
  • for WLS 12.1 /pathtojar/wlthint3client.jar.

For building the wlfullclient.jar look at here: http://docs.oracle.com/cd/E12840_01/wls/docs103/client/jarbuilder.html.

Further information at https://docs.oracle.com/middleware/1213/wls/SACLT/basics.htm#SACLT124

Workaround for Weblogic 12.2

For an unknown reason, deployment fails with librairies generated from a weblogic 12.2 product. You can generate and use a wlfullclient-10.3.6.jarwith that I can deploy without any problem onto our WebLogic Server Version: 12.2.1.1.0.

  • Jdk : the jdk used to run a deployment task.
  • Additional classpath : weblogic.jar file path loaded for deployment. If no value is set but the WL_HOME environment variable is found, the plugin will try to load  %WL_HOME%/server/lib/weblogic.jar.
    Depending on the weblogic version the weblogic.jar should be replaced by :

     

    • for WLS 10.3 /path/to/jar/wlfullclient.jar

       

    • for WLS 12.1 /path/to/jar/wlthint3client.jar.

Useful Information

If you use authentication mode, you should replace in WLS 12 wlfullclient.jar by wlthint3client.jar. If you have to add many dependencies you can append them like that /path/to/wulfullclient.jar:/path/to/wlthint3client.jar. The separator ':' is platform dependent.

see https://docs.oracle.com/middleware/1213/wls/SACLT/basics.htm#SACLT125

 

 

Oracle Information

"The WebLogic full client, wlfullclient.jar, is deprecated as of WebLogic Server 12.1.3 and may be removed in a future release. Oracle recommends using the WebLogic Thin T3 client or other appropriate client depending on your environment. For more information on WebLogic client types, see WebLogic Server Client Types and Features."

  • Java Options to use : the java options used by the java process when invoking the weblogic library. By default it will be -Xms256M -Xmx256M.
  • Excluding artifact name list : the built artifacts name pattern excluded from post build deployment action.
  • Disable : If checked, the plugin execution is disabled.
  • Configuration File : xml file path containing deployments targets. It has to be [http://host:port/plugin/weblogic-deployer-plugin/defaultConfig/plugin-configuration.xsd] schema compliant. No validation currently performed. The file can be added through a local path (/usr/users/.../plugin-configuration.xml) or a remote URL (http://xxxxxxxxx/plugin-configuration.xml);

    configuration.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <config xmlns="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin plugin-configuration.xsd"> 
    <weblogic-targets>
    	<weblogic-target>
    		<name>my_managed_server1</name>
    		<host>_weblogic.admin.server.host_</host>
    		<port>_weblogic.admin.server.port_</port>
    		<login>_weblogic.admin.server.login_</login>
    		<password>_weblogic.admin.server.password_</password>
    		<authMode>BY_KEY</authMode>
    		<userconfigfile>P:\Documents\perso\dev\wls-deploy-plugin\wls_userConfig.properties</userconfigfile>
    		<userkeyfile>P:\Documents\perso\dev\wls-deploy-plugin\wls_userConfig.key</userkeyfile>
    	</weblogic-target>
    	<weblogic-target>
    		<name>my_managed_server2</name>
    		<host>_weblogic.admin2.server.host_</host>
    		<port>_weblogic.admin2.server.port_</port>
    		<login>_weblogic.admin2.server.login_</login>
    		<password>_weblogic.admin2.server.password_</password>
    		<authMode>BY_LOGIN</authMode>
    	</weblogic-target>
    	<weblogic-target>
    		<name>my_managed_server3</name>
    		<host>_weblogic.admin.server.host_</host>
    		<port>_weblogic.admin.server.port_</port>
    		<login>_weblogic.admin.server.login_</login>
    		<password>_weblogic.admin.server.password_</password>
    		<!-- used to transfer by FTP the component flagged as library to the WL machine -->
    		<ftpHost>_weblogic.remote.host_</ftpHost>
    		<ftpUser>_weblogic.remote.user_</ftpUser>
    		<ftpPassowrd>_weblogic.remote.password_</ftpPassowrd>
    		<remoteDir>/remote/path/used/to/transfer/libraries</remoteDir>
    	</weblogic-target>
    </weblogic-targets>
    </config>
    

Library Deployment Tip

The ftp parameters are used to deploy libraries. When you checked your artifact deployment as a library deployment, the plugin connects to the ftpHost and transfers the artifact into the remoteDir directory.
Basically, the ftpHost value should be the same as the host value.

Authentication mode

There are 2 kinds of authentication :

  • BY_KEY : uses a keystore file and a config file
  • BY_LOGIN : uses a login/password (this is the default authentication mode).

Since 2.3, the plugin also supports authentication by keystore. To use it, set authMode with BY_KEY value then set userconfigfile/userkeyfile elements. If you forget to specify authMode with BY_KEY value, the plugin uses the default authentication mode BY_LOGIN.

Job Configuration

If the plugin is not configured

If no configuration has been set, the plugin will display an error message

If the plugin is already configured

If the plugin is already configured, jenkins will display the job plugin configuration form.

  • Deployment task list : The list of deployments to run. For each task, some of parameters has to be set :
    • Task name (optional) : The name of the task which will be used to identify it.
    • environment : the targeted weblogic environment. Can be customized.
    • name : the name used by weblogic to display component.
    • Base directory where the resource can be found. If this field is left blank, the plugin will lookup under workspace directory.
    • Built resource to deploy : a regular expression to filter resource which will be deployed.
    • targets: the weblogic target (can be a managed server instance, a cluster either the AdminServer). By default the plugin will use the AdminServer as the target. Many targets can be defined and will be separated by un comma symbol (e.g AdminServer, ManagedServer1, Cluster2). Can be customized.
    • weblogic libraries : If checked, the generated artifact will be deployed as a library component.
    • advanced configuration : See the chapter below Job Advanced configuration.
  • Build failed when deployment failed : If checked, The current build will be flagged as a failed one if the deployment task failed.
  • Force deployment tasks stop on first failure : Useful if you have any task configured and you want to stop the next deployments tasks where an error occurs.
  • Deployment policy : Configure which cause(s) will trigger the deployment action. If 'None specified' is selected, the deployment occurs each time the job builds. If another ones are selected, the deployement action only occurs when the build was triggered by a chosen cause.
  • Deploying only when sources changes : If checked, the deployment action only occurs when the build trigger by a parametrized cause AND the SCM step detects any changes.
  • Projects deployment Dependencies : (experimental) specifies a dependency with others job deploying some artifacts.
Customization of parameters

Some of parameters can also be tokenized with environment variables or even build parameters. Here are these parameters :

    • environment: Instead of setting a fixed value into the configuration file (e.g localhost:7000) you can set a variable like ${WL_HOST}:${WL_PORT}
    • targets: Instead of setting a fixed value (e.g AdminServer) you can set a variable like ${ENV_TARGET} or $TARGET.
    • Base directory where the resource can be found : you can set a variable like ${WORKSPACE}.
    • name: The name parameter can be tokenized (e.g my-war-${MY_VERSION})

Use the build parameter plugin or add some environment variable to set these values

Job Advanced configuration

It's possible to set advanced options like stage mode and command line. It helps user with special needs to override the default behaviour of the plugin.

  • Stage mode : stage, nostage or external stage
  • protocol : t3, t3s, http or https
  • Command line : The command which will be run by the deployer instead of the default ones (undeploy/deploy)
Stage mode

Stage mode define how the artificat will be deployed. By default the plugin use the stage mode 'stage'. Please refer to the weblogic documentation for further information.

Override deployment execution

For advanced users, it can be useful to define the commands that the deployer has to run instead of the default ones, To enable this feature, the user will set different command lines into the 'Command line' field of Job advanced configuration.

These commands has to be ended by the ';' separator. The following plugin token can be added to the command line :

  • {wl.deployment_name} : the 'Name' parameter value
  • {wl.source} :  the resource to deploy (figured out by the plugin)
  • {wl.targets} : the 'Targets' parameter value
  • {wl.host} : the host part of the 'Environment' parameter
  • {wl.port} : the port part of the 'Environment' parameter
  • {wl.deploymentPlan} : the path of the deployment plan of the 'Environment' parameter
  • {wl.login} : the login to authenticate to the server (provided by the configuration file)
  • {wl.password} : the password to authenticate to the server (provided by the configuration file)
  • {wl.user_configfile} : the Deployer configuration file (defined in the configuration file)
  • {wl.user_keyfile} : the private key to authenticate (provided by the configuration file)

Note : only the arguments and parameters can be specified. The java executable used to run the command will be figure out by the plugin with the same algorithm than a default execution.

For instance : the user who prefers run deployment with 'distribute' instead of deploy could be set the following command lines:

command line parameter
-adminurl http://{wl.host}:{wl.port} -user {wl.login} -password {wl.password} -debug -remote -verbose -name {wl.deployment_name} -source {wl.source} -targets {wl.targets} -cancel;
-adminurl http://{wl.host}:{wl.port} -user {wl.login} -password {wl.password} -name {wl.deployment_name} -source {wl.source} -targets {wl.targets} -distribute

Be Careful

Sometimes source path contains special chars like $.To ensure that the plugin well handle the path you can surround the token {wl.source} with quotes like this :

command line parameter
-adminurl http://{wl.host}:{wl.port} -user {wl.login} -password {wl.password} -debug -remote -verbose -name {wl.deployment_name} -source "{wl.source}" -targets {wl.targets} -cancel;

NB : Environment variables and build parameters can also be used.

User Guide

Build status

The build status will be modified according the following rules :

  • the status is set to SUCCESS when :
    • the deployment task is successfully achieved
    • the checkbox "Mark build unstable if deployment was not attempted" is not checked whatever the result of pre-requisite step.
  • If the checkbox "Mark build unstable if deployment was not attempted" is checked, the status is set to UNSTABLE when :
    • at least one of the verification of the deployment task failed (PLUGIN_DISABLED, OTHER_TRIGGER_CAUSE, NO_CHANGES, UNSATISFIED_DEPENDENCIES, PREVIOUS_STATUS_BUILD_FAILED).
    • the deployment task failed and the Build failed when deployment failed parameter is not checked.
  • status is set to FAILED when the deployment task failed and the Build failed when deployment failed parameter is checked.

Check a build deployment status

On the build dashboard a new icon will appear. It displays the deployment status

Check the last successful deployment on main job dashboard

When you click on your job, a dashboard show a new icon with the date of the last successful deployment. If no deployment occurred or always failed. The date will be replaced by 'N/A' label.

View deployment Logs

You can view the deployment logs of each task. Simply click on the 'Deployments Statuses' link or 'Weblogic deployments' link. They will appear one by one in the deployment page.

Disabling deployment task at runtime

A deployment task can be skipped during a job build by setting an env variable or a build parameter following this naming rule (DEPLOY_<task_name>_SKIP) to true.

For instance, if your task names 'task1' you have the possibility to skip its execution by setting a variable named DEPLOY_TASK1_SKIP to true (It could be a boolean build parameter).

Master/slave architecture support

The latest version of the plugin (4.0) supports master/slave architecture. That is to say, the plugin automatically copy weblogic libraries and any kind of configuration to the remote node. Be sure that the right JDK used by the plugin is correctly installed and declared in the node configuration. 

 

Note master/slave architecture

The plugin doesn't copy userkeyfile nor userconfigfile to the remote node. This enhancement will be done in the next version.

 

 

Release Notes

Version 4.1 (September 03, 2017)

JENKINS-45044 - Getting issue details... STATUS

Version 4.0 (August 21, 2017)

Master-Slave architecture support ( JENKINS-44599 - Getting issue details... STATUS JENKINS-36215 - Getting issue details... STATUS )

Note : the copy of userkeyfile and userconfigfile on the remote node is not currently supported.

Merge pull request #8 from mustafau/simplify-global-configuration

JENKINS-45097 - Getting issue details... STATUS

JENKINS-36524 - Getting issue details... STATUS

JENKINS-37077 - Getting issue details... STATUS

Version 3.7 (June 21, 2017)

JENKINS-42802 - Getting issue details... STATUS

Upgrade to 1.580.1 jenkins version

Minor enhancements (simply invoke join instead of start + join, using absolute path of jdk home)

Version 3.6 (Oct 25, 2016)

JENKINS-39029 Fixed NPE for job configured with the plugin verson older than 3.5
JENKINS-38218 Support multiple files validation for extraClasspath field.

Version 3.5 (Sep 04, 2016)

JENKINS-32392 Added the ability to choose the protocol to use during the deployment.
Refactoring deployment policy. LegacyCodeCause and UserCause no more supported.(thanks to mustafa ulu)

Version 3.4 (May 26, 2016)

JENKINS-19962 Added the ability to declare a job successfull when pre-requisite step failed
JENKINS-35161 variable can be used for the Deployment name value
UserCause is now flagged deprecated in the triggers list
Added TimerTrigger to the list of triggers

Version 3.3 (August 31, 2015)

JENKINS-26992 baseDirectory not well replaced
Removed unused org.codehaus.plexus dependency

Version 3.1 (March 31, 2015)

Removed org.codehaus.plexus.FileUtils dependency

Version 3.0 (March 28, 2015)

JENKINS-26992 Supported baseDirectory variable expansion
JENKINS-26366 Implemented Promoted Builds plugin support
JENKINS-23700 By default the plugin searches under workspace directory

Be Careful

This version is not backward compatible. If you used previous version with maven project don't forget to update the maven jobs configuration (fill up base directory which is no more computed).

Version 2.13 (February 16, 2015)

JENKINS-20351 Implemented the recursive search when no base directory is set in freestyle job configuration.
Fixed JENKINS-26901 Not possible to run freestyle job with non-set baseDirectory.

Version 2.12 (December 17, 2014)

JENKINS-24789 Added the possibility to skip a task deployment during a build by setting a build parameter or an env variable.

Version 2.11 (December 16, 2014)

Fixed regression due to an unexpected commit (sad)

Version 2.10 (December 6, 2014)

Fixing bug JENKINS-23701 : Added better control on invalid directory parameter set.
French translation missing
Fixing wrong javadoc
Fixing wrong icon URL.

Version 2.9.1 (December 20, 2013)

Fixing bug JENKINS-20970 : deployment failed due to an unexpected stream closed exception.

Version 2.9 (November 30, 2013)

Handled exception when configuration file uploaded is incorrect.
Added error log on jenkins project selector bean.

Version 2.8 (October 06, 2013)

Fixing bug JENKINS-16007

Version 2.7 (October 04, 2013)

Implementing JENKINS-18685 Added support for customization of deployment targets/environment through build parameters.

Version 2.6 (September 16, 2013)

Implementing JENKINS-19237 Added deployment plan support
Evolution JENKINS-19016 Modified behavior when the step of pre-requisite check failed.

Version 2.5 (July 27, 2013)

Implementing JENKINS-18882 Replaced weblogic icon
Fixing bug JENKINS-18940 token {wl.source} never replaced in command line

Version 2.4 (July 24, 2013)

Implementing JENKINS-17300 and JENKINS-18812 : Added new feature which allow the advanced user to define his own command to run
Fixing bug JENKINS-18881 : NPE when the user viewing deployment result of a skipped execution
Fixing bug JENKINS-18883 : cron value doesn't appear in 'Deploy periodically' field

Version 2.3 (June 26, 2013)

Implementing JENKINS-18467 : stage mode attribute mishandled in job advanced configuration.
Implementing JENKINS-17879 : Supports weblogic authentication by keystore.

Version 2.2 (May 04, 2013)

Implementing JENKINS-17300 : Supports stage mode choice in job configuration.

Version 2.1 (May 03, 2013)

Implementing JENKINS-17301 : Supports jdk configuration per job.

Version 2.0 (Mar 04, 2013)

Implementing JENKINS-16808 : Supports multi-deployment feature.
Implementing JENKINS-16699 : Searched resource pattern or name is traced in the job log

Be Careful

This version is not backward compatible.

Version 1.4 (Feb 11, 2013)

Implementing JENKINS-15696 : Supports freestyle project.

Version 1.3 (Aug 13, 2012)

Implementing JENKINS-14763 : English translation. The English language is the default plugin language.

Version 1.2 (Aug 2, 2012)

Implementing JENKINS-14646 : The old java class or resources prefixed by HudsonXXXX has been refactored to XXXX.
Implementing JENKINS-14626 : As of now, it's possible to filter the artifact name to deploy by regex defined in the job configuration. (Useful for maven multi-module project which generate many artifacts).

Version 1.1 (May 5, 2012)

Forked from Hudson version.

Added JDK selection on global configuration.

Removed task abortion if no compatibility detected between the JDK and the weblogic.Deployer API (As of now, It displays a warning).

Fixed translation and spelling errors.

Added WebLogic Server 10.3 support.

54 Comments

  1. Unknown User (stevez)

    I want to deploy my grails war file into weblogic server, the file is under the target folder of the workspace, so how can I specify the base directory and Built resource to deploy field?

  2. Unknown User (ollyando)

    Can you add a flag to hide the weblogic connection info being output to the log. Please do not echo the username / password. This could be a security issue, especially deploying to production environments etc.

  3. Unknown User (davidchentw)

    After the 2.8 to 2.9 plugin upgrade, my build job gave out exception. I had to downgrade to 2.8 ...
    Error messages as following ---

    [WeblogicDeploymentPlugin] - Pay attention of Jdk version {selected version is 1.6.0_37} compatibility with Weblogic Deployer API (see Oracle documentation).
    [WeblogicDeploymentPlugin] - The JDK C:\SunJdk will be used.
    [WeblogicDeploymentPlugin] - ArtifactSelector used : org.jenkinsci.plugins.deploy.weblogic.FreeStyleJobArtifactSelectorImpl@1a6ea6d
    [WeblogicDeploymentPlugin] - Retrieving artifacts recorded [filtered resources on xxx\.war]...
    [WeblogicDeploymentPlugin] - the following file recorded xxx.war is eligible.
    [WeblogicDeploymentPlugin] - Deploying the artifact on the following target : (name=yyy) (host=yyy) (port=7001)
    java.io.IOException: Stream Closed
    	at java.io.FileOutputStream.writeBytes(Native Method)
    	at java.io.FileOutputStream.write(Unknown Source)
    	at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.undeploy(DeploymentTaskServiceImpl.java:284)
    	at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:182)
    	at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:236)
    	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
    	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:780)
    
  4. Unknown User (ha1)

    I am getting the same error as David with 2.9. I downgraded to 2.8 and it is deploying fine. Running WLS 12.3. Please let me know if you need me to test anything as we'd like to move onto latest version if it can become stable.

  5. Unknown User (janice)

    i user version 2.9.1 ,2.9 ,2.8 ,the deploy failed.

    it means ParameterValueResolver.java has not the method EnvVars(String,String) or others

    how could it depoly correct?

    17:01:00 java.lang.NoSuchMethodError: hudson.EnvVars.get(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;

    17:01:00 at org.jenkinsci.plugins.deploy.weblogic.util.ParameterValueResolver.resolveEnvVar(ParameterValueResolver.java:33)17:01:00 at org.jenkinsci.plugins.deploy.weblogic.deployer.WebLogicDeployer.getWebLogicCommandLine(WebLogicDeployer.java:75)
    17:01:00 at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.undeploy(DeploymentTaskServiceImpl.java:278)
    17:01:00 at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:178)
    17:01:00 at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:232)
    17:01:00 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
    17:01:00 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
    17:01:00 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
    17:01:00 at hudson.model.Build$BuildExecution.post2(Build.java:183)
    17:01:00 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
    17:01:00 at hudson.model.Run.execute(Run.java:1513)
    17:01:00 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
    17:01:00 at hudson.model.ResourceController.execute(ResourceController.java:88)
    17:01:00 at hudson.model.Executor.run(Executor.java:236)
    17:01:00 ERROR: WeblogicDeploymentPlugin - Failed to deploy.

  6. Unknown User (rekha)

    In the current 'weblogic deployment plugin' during undeployment, the undeployment is done based on the name provided in the deployment task list section. I want to undeploy the existing deployed artifact in the managed server irrespective of the name .

    Is this feature available ?

    1. Unknown User (raphc)

      Hi rekha

      Soory for my late respone. What do you mean by 'undeploy the existing deployed artifact in the managed server irrespective of the name'. Do you want to specify the name during the undeployment step?

  7. Unknown User (vandersson2)

    Hi, I'm having problems to configure the plugin do deploy the ear on a weblogic server on my local machine.

    I configured the plugin as displayed on the images below, but when I try to configure the job it says that the plugin is not configured

    The content of my configuration.xml file is 

    <?xml version="1.0" encoding="UTF-8"?>
    <config xmlns="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin file:///C:/.jenkins/plugins/weblogic-deployer-plugin/config/plugin-configuration.xsd"> 
    <!--
    <config xmlns="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin plugin-configuration.xsd"> 
    -->
    <weblogic-targets> <weblogic-target> <name>local</name> <host>localhost</host> <port>7001</port> <login>admin</login> <password>@332#.123</password> <authMode>BY_LOGIN</authMode> </weblogic-target>
    </weblogic-targets>
    </config>

    Someone have an idea about this problem?
    OS: Windows 7
    Jenkins: 1.625
    Weblogic Plugin: 3.2

  8. Unknown User (sagayd)

    I think the Documentation should be enhanced. I have installed the plugin, and configured the Weblogic in Jenkins manage configuration page. I configure a job to do the WebLogic deployment and execute it at a slave machine.

    I kept the war to deploy on the slave machine, but during execution, the weblogic plugin reports - the base directory specified is invalid (does not exist, or not a directory or has insufficient permission). If I keep the war file on master computer, it detects the file.

    However it still reports file not found error. I checked the java path and weblogic.jar file in master and they are present. Whats wrong

    1. Unknown User (raphc)

      Hi,

      The 4.0 is available. Let me know if it's ok for you.

      Regards

  9. Unknown User (sagayd)

    Is the WebLogic Deployer capable of deploying war file on to App server from Slave machine or from master only?

    1. Unknown User (raphc)

      Hi David,

      This feature will be available in verison 4.0 which is in development.

       

      Regards

       

  10. Unknown User (rpulcinschi)

    Hi all,

    I would like also to know the answer for this :

     

    Thanks!

    Regards,

    1. Unknown User (raphc)

      Hi,

      This feature will be available in verison 4.0 which is under development.

       Regards

    2. Unknown User (raphc)

      Hi,

      The 4.0 is available. Is this version resolve your problem?

      Regards

  11. Unknown User (jonasricardo)

    Hi, can you help me?I set up the plugin but can not perform the application deployment. The following configuration used and error message
    thank you.

    Started by user Jonas Ricardo Rossi Cardoso
    [EnvInject] - Loading node environment variables.
    Building on master in workspace /var/jenkins/jobs/Nucom/workspace
    [WeblogicDeploymentPlugin] - Pay attention to JDK version

    Unknown macro: { selected version is 1.7.0_40 }

    compatibility with WebLogic Deployer API (see Oracle documentation).
    [WeblogicDeploymentPlugin] - The JDK /opt/jdk1.7.0_40/ will be used.
    [WeblogicDeploymentPlugin] - Retrieving artifacts recorded [filtered resources on .*war]...
    [WeblogicDeploymentPlugin] - 1 files found under teste
    [WeblogicDeploymentPlugin] - the following resource recorded /opt/teste/MavenTeste.war is eligible.
    [WeblogicDeploymentPlugin] - Deploying the artifact on the following target : (name=testeJonas) (host=******) (port=************)
    [WeblogicDeploymentPlugin] - UNDEPLOYING ARTIFACT...
    $ /opt/jdk1.7.0_40/bin/java -Xms50M -Xmx60M -cp /opt/libsJEE/weblogic/wlthint3client.jar weblogic.Deployer -debug -remote -verbose -noexit -name jonas -targets AdminServer -adminurl t3://****************** -user *************-password ************** -undeploy
    [WeblogicDeploymentPlugin] - ARTIFACT UNDEPLOYED SUCCESSFULLY.
    [WeblogicDeploymentPlugin] - DEPLOYING ARTIFACT...
    $ /opt/jdk1.7.0_40/bin/java -Xms50M -Xmx60M -cp /opt/libsJEE/weblogic/wlthint3client.jar weblogic.Deployer -debug -stage -remote -verbose -upload -name jonas -source /opt/teste/MavenTeste.war -targets AdminServer -adminurl t3://****************0 -user *******-password ********** -deploy
    java.lang.RuntimeException: task completed abnormally (exit code = 1)
        at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.deploy(DeploymentTaskServiceImpl.java:240)
        at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:169)
        at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:304)
        at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
        at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)
        at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757)
        at hudson.model.Build$BuildExecution.post2(Build.java:183)
        at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706)
        at hudson.model.Run.execute(Run.java:1690)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
        at hudson.model.ResourceController.execute(ResourceController.java:88)
        at hudson.model.Executor.run(Executor.java:246)
    ERROR: [WeblogicDeploymentPlugin] - Failed to deploy.
    [INFO] ------------------------------------------------------------------------
    [INFO] DEPLOYMENT FAILURE
    [INFO] ------------------------------------------------------------------------
    Build step 'Deploy the artifact to any WebLogic environments' changed build result to FAILURE
    Finished: FAILURE

    -----------------------------------  ARTIFACT UNDEPLOYMENT -----------------------------------------------
    Error: Could not find or load main class weblogic.Deployer
    -----------------------------------  ARTIFACT DEPLOYMENT -----------------------------------------------
    Error: Could not find or load main class weblogic.Deployer

  12. Unknown User (vlad_)

    Hi, I have the same problem. The weblogic plugin version 3.7 does not work with Oracle Fusion Middleware 12.2.x versions. Some classes and methods have been deprecated in the newer versions of Weblogic, just like "weblogic.Deployer" class. Does anybody know how to use "wlthint3client.jar" configuration in this case?

  13. Unknown User (yeshy1987)

    I have also run into similar kind of issue as mentioned by Jonas. We are using JDK 1.7.x and WebLogic server version 12.1.x. Hence as per the documentation to using the thin client. However come across a class file missing error. Should we use wlfullclient.jar?

  14. Unknown User (urscooldon)

    Does this plugin support weblogic 12.2.x? When using the wlthint3client.jar, error "unable to find or load main class" is thrown. When weblogic.jar is used, the below error is thrown

    DEPLOYING ARTIFACT...
    $ C:\devops\Jenkins\jre\bin/java -Xms256M -Xmx512M -cp C:\fmw\oracle_home\wlserver\server\lib\weblogic.jar weblogic.Deployer -debug -stage -remote -verbose -upload -name xxx -source 'C:\devops\Jenkins\workspace\xxx.war' -targets AdminServer -adminurl t3://localhost:7001 -user yyy -password zzz -deploy
    java.lang.RuntimeException: task completed abnormally (exit code = 1)
        at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.deploy(DeploymentTaskServiceImpl.java:239)
        at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:169)
        at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:305)
        at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
        at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
        at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:676)
        at hudson.model.Build$BuildExecution.post2(Build.java:186)
        at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:621)
        at hudson.model.Run.execute(Run.java:1760)
        at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
        at hudson.model.ResourceController.execute(ResourceController.java:97)
        at hudson.model.Executor.run(Executor.java:405)
    ERROR: [WeblogicDeploymentPlugin] - Failed to deploy.

    ------------------------------------------------------------------------------------------

     

  15. Unknown User (urscooldon)

    Is there a way to overcome the apostrophe(') in -source 'C:\devops\Jenkins\workspace\xxx.war'? After lot of debugging, found that apostrophe in the path is causing the issue. This is automatically added during the execution. Any solution to overcome this? Kindly suggest. Thanks

    1. Unknown User (bonanzaone)

      Also facing the same problem, using wlfullclient-10.3.6.0.jar.

    2. Unknown User (raphc)

      Hi Don,

      This is a regression which appeared in the latest version. You should downgrade to 3.6. The possible workaround in the latest version is to used advanced feature by setting the weblogic command directly. I'll fix it in 4.0

       

      Regards

       

    3. Unknown User (raphc)

      Hi Don,

      The 4.0 is available.

      Regards

  16. Unknown User (vlad_)

    Hi guys,

    I've found a solution. I pushed up all the needed oracle plugins and oracle maven jars into the third party nexus repository (it could be doing in the local maven jenkins repository directly), if you have access.
    After that, I set up "WebLogic libraries" in the weblogic deployer plugin section "Deploy the artifact to any Weblogic Environments" as shown in the image below.
    Now, all the weblogic oracle libraries will be downloaded from the nexus repository to local jenkins maven repository when triggering the job.


    Installing weblogic oracle libraries in the local jenkins repository:
    mvn install:install-file -DpomFile=oracle-maven-sync.12.2.1.pom -Dfile=oracle-maven-sync.12.2.1.jar
    mvn com.oracle.maven:oracle-maven-sync:push -DoracleHome=[ORACLE_HOME]

    Installing weblogic oracle libraries in the nexus repository:
    mvn deploy:deploy-file -DpomFile=oracle-maven-sync-12.2.1.pom -Dfile=oracle-maven-sync-12.2.1.jar -Durl=http://nexus.url:port/nexus/content/repositories/thirdparty -DrepositoryId=local-nexus
    mvn com.oracle.maven:oracle-maven-sync:push -DoracleHome=[ORACLE_HOME] -DserverId=local-nexus

    Configuring maven Settings.xml:
    <profiles>
    <profile>
    <id>nexus</id>
    <repositories>
    <repository>
    <id>local-nexus</id>
    <url>http://nexus.url:port/nexus/content/repositories/thirdparty</url>
    <layout>default</layout>
    </repository>
    </repositories>
    </profile>
    </profiles>

     

  17. Unknown User (ashokkumar_b)

    Is this plugin support WebLogic Server Version: 12.2.1.2.0 ? When using the wlthint3client.jar,
    error "unable to find or load main class" is thrown.
    [WeblogicDeploymentPlugin] - DEPLOYING ARTIFACT...
    $ "C:\Program Files\Java\jdk1.8.0_102\bin/java" -Xms256M -Xmx768M -cp
    C:\Oracle\Middleware\Oracle_Home\wlserver\server\lib\wlthint3client.jar weblogic.Deployer -debug -stage -remote
    -verbose -upload -name check-1.0.0-BUILD-SNAPSHOT -source 'C:\Users\test\.jenkins\workspace\WL_Deployment\target\check-1.0.0-BUILD-SNAPSHOT.war'
    -targets AdminServer -adminurl t3://localhost:7012 -user yyyyyy -password xxxxxxx -deploy
    java.lang.RuntimeException: task completed abnormally (exit code = 1)
    at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.deploy(DeploymentTaskServiceImpl.java:239)
    at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:169)
    at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:305)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
    at hudson.model.Build$BuildExecution.post2(Build.java:185)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
    at hudson.model.Run.execute(Run.java:1745)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:404)
    ERROR: [WeblogicDeploymentPlugin] - Failed to deploy.
    [INFO] ------------------------------------------------------------------------
    [INFO] DEPLOYMENT FAILURE
    [INFO] ------------------------------------------------------------------------
    Could you please help on this issue.

    1. Unknown User (raphc)

      Hi Unknown User (ashokkumar_b)

       

      Did you try with wlfullclient.jar or /opt/ORACLE/product/ofm12.2.1/wlserver/modules/features/wlst.wls.classpath.jar as Guadalupe mentions in a comment ?

       

      Regards,

  18. Unknown User (yeshy1987)

    We are now able to deploy to the weblogic admin server. However to get this done, we had to use wlfullclient.jar instead of the thin client as specified in the page above.

    When the distribution happens, I see it creates a sub-folder/app/<war file> under the admin console staging root directory. How can this behaviour be overcome? We would like the war file to be deployed to the staging root directly.

    WebLogic server version: 12.1.x

    and JVM version: 1.7.9.

    1. Unknown User (raphc)

      Hi Unknown User (yeshy1987)

      Thank you for your feedback. So the deployment works on weblogic 12.1 with wlfullclient.jar. Did you read the document about the weblogic.deployer CLI perhaps a parameter can be used to specify it ?

       

  19. Unknown User (kanduc)

    Hi guys,

    the plugin allows SSL arguments? 

    The command is:

    java [SSL Arguments] weblogic.Deployer [Connection Arguments] 
         [User Credentials Arguments] COMMAND-NAME command-options 
         [Common Arguments]

    SSL arguments could be:

    [ -Dweblogic.security.TrustKeyStore=DemoTrust ]
         [ -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=password ]
         [ -Dweblogic.security.CustomTrustKeyStoreFileName=filename 
           -Dweblogic.security.TrustKeystoreType=jks
           [-Dweblogic.security.CustomTrustKeyStorePassPhrase=password ]
         ]
         [ -Dweblogic.security.SSL.hostnameVerifier=classname ]
         [ -Dweblogic.security.SSL.ignoreHostnameVerification=true ]

     

    1. Unknown User (raphc)

      Hi Unknown User (kanduc)

      The enhancement is not supported yet. You can create an issue in jira.

      Regards

       

  20. Unknown User (guadalupeavila)

    Hi Guys, can you help me?


    I have WebLogic server version: 12.2.1.0.0 with plugin 3.6 and I use the wlthint3client.jar, but it sends me the "Error: Could not find or load main class weblogic.Deployer"


    Building in workspace /home/jbadmin/.jenkins/workspace/Pruebas_Despliegue
    [WeblogicDeploymentPlugin] - Pay attention to JDK version {selected version is 1.8.0_92} compatibility with WebLogic Deployer API (see Oracle documentation).
    [WeblogicDeploymentPlugin] - The JDK /usr/java/jdk1.8.0_92/ will be used.
    [WeblogicDeploymentPlugin] - Retrieving artifacts recorded [filtered resources on EjemploPruebaCarga.war]...
    [WeblogicDeploymentPlugin] - 1 files found under Pruebas_Despliegue
    [WeblogicDeploymentPlugin] - the following resource recorded /home/jbadmin/.jenkins/workspace/Pruebas_Despliegue/EjemploPruebaCarga.war is eligible.
    [WeblogicDeploymentPlugin] - Deploying the artifact on the following target : (name=AdminServer) (host=172.19.17.14) (port=7001)
    [WeblogicDeploymentPlugin] - UNDEPLOYING ARTIFACT...
    $ /usr/java/jdk1.8.0_92/bin/java -Xms256M -Xmx256M -cp /opt/ORACLE/product/ofm12.2.1/wlserver/server/lib/wlthint3client.jar weblogic.Deployer -debug -remote -verbose -noexit -name EjemploPruebaCarga.war -targets AdminServer -adminurl http://172.19.17.14:7001 -user user -password password -undeploy
    [WeblogicDeploymentPlugin] - ARTIFACT UNDEPLOYED SUCCESSFULLY.
    [WeblogicDeploymentPlugin] - DEPLOYING ARTIFACT...
    $ /usr/java/jdk1.8.0_92/bin/java -Xms256M -Xmx256M -cp /opt/ORACLE/product/ofm12.2.1/wlserver/server/lib/wlthint3client.jar weblogic.Deployer -debug -stage -remote -verbose -upload -name EjemploPruebaCarga.war -source /home/jbadmin/.jenkins/workspace/Pruebas_Despliegue/EjemploPruebaCarga.war -targets AdminServer -adminurl http://172.19.17.14:7001 -user user -password password -deploy
    java.lang.RuntimeException: task completed abnormally (exit code = 1)
    at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.deploy(DeploymentTaskServiceImpl.java:240)
    at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:169)
    at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:304)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
    at hudson.model.Build$BuildExecution.post2(Build.java:186)
    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
    at hudson.model.Run.execute(Run.java:1753)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:405)
    ERROR: [WeblogicDeploymentPlugin] - Failed to deploy.
    [INFO] ------------------------------------------------------------------------
    [INFO] DEPLOYMENT FAILURE
    [INFO] ------------------------------------------------------------------------
    Build step 'Deploy the artifact to any WebLogic environments' changed build result to FAILURE
    Finished: FAILURE

     

    Thank you! Regards!

    1. Unknown User (guadalupeavila)

      Hello

      Just to say that in my case with version 12.2.1 of weblogic and plugin 3.6 the jar with which I could perform the deployment is wlst.wls.classpath.jar

      Which identifies in this route:

      /opt/ORACLE/product/ofm12.2.1/wlserver/modules/features/wlst.wls.classpath.jar

      I hope it will be you useful

      Regards!

      1. Unknown User (raphc)

  21. Unknown User (sbarrete)

    Hello,

    I'm trying to use Weblogic Deployer plugin plugin in addition to Extensible choice parameter plugin. This choice plugin affects a value to a variable called MYLIB but weblogic deployer plugin seems not replace variable with the value of choice. However the value of the parameter is correct. 

    (context : jenkins/windows)

    [WeblogicDeploymentPlugin] - the following resource ['xxxxxxxxxxxxxxxxxx-9.war'] doesn't match $MYLIB

    java.lang.RuntimeException: No artifact to deploy [$MYLIB] found.

     

    In the plugin configuration : Ressource générée à deployer : $MYLIB

    Thanks in advance.

     

    1. Unknown User (raphc)

      Hi,

      did you try with bracket like thar ${MYLIB}

      Regards

      1. Unknown User (sbarrete)

        Yes but there is an error :

        java.util.regex.PatternSyntaxException: Illegal repetition near index 0
        ${MYLIB}
        ^
        	at java.util.regex.Pattern.error(Unknown Source)
        	at java.util.regex.Pattern.closure(Unknown Source)
        	at java.util.regex.Pattern.sequence(Unknown Source)
        	at java.util.regex.Pattern.expr(Unknown Source)
        	at java.util.regex.Pattern.compile(Unknown Source)
        	at java.util.regex.Pattern.<init>(Unknown Source)
        	at java.util.regex.Pattern.compile(Unknown Source)
        	at java.util.regex.Pattern.matches(Unknown Source)
        	at org.jenkinsci.plugins.deploy.weblogic.FreeStyleJobArtifactSelectorImpl.selectArtifactRecorded(FreeStyleJobArtifactSelectorImpl.java:67)
        	at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:129)
        	at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:304)
        	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:676)
        	at hudson.model.Build$BuildExecution.post2(Build.java:186)
        	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:621)
        	at hudson.model.Run.execute(Run.java:1760)
        	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
        	at hudson.model.ResourceController.execute(ResourceController.java:97)
        	at hudson.model.Executor.run(Executor.java:405)
        ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory.
        1. Unknown User (raphc)

          Ok,

          I will create an issue about "extended choice plugin" support.

          Regards

           

          1. Unknown User (sbarrete)

            Are you sure that is an Extended choice plugin issue ?

            When I'm looking for the value of MYLIB in 'Environment variables' in jenkins, the value is correct.

            Thanks

            1. Unknown User (raphc)

              Not an extended choice plugin bug but a weblogic-deployer plugin issue which wouldn't detect the variable MYLIB loaded by the Extended choice plugin. Can you post your job configuration. It help me to reproduce your problem.

              Regards,

              1. Unknown User (sbarrete)

                <?xml version='1.0' encoding='UTF-8'?>
                <project>
                <actions/>
                <description>Déploiement unitaire RECETTE</description>
                <keepDependencies>false</keepDependencies>
                <properties>
                <hudson.model.ParametersDefinitionProperty>
                <parameterDefinitions>
                <jp.ikedam.jenkins.plugins.extensible__choice__parameter.ExtensibleChoiceParameterDefinition plugin="extensible-choice-parameter@1.4.0">
                <name>MYLIB</name>
                <description></description>
                <editable>false</editable>
                <choiceListProvider class="jp.ikedam.jenkins.plugins.extensible_choice_parameter.FilenameChoiceListProvider">
                <baseDirPath>\\xxxx</baseDirPath>
                <includePattern>*.war</includePattern>
                <scanType>File</scanType>
                <excludePattern></excludePattern>
                <reverseOrder>false</reverseOrder>
                <emptyChoiceType>None</emptyChoiceType>
                </choiceListProvider>
                </jp.ikedam.jenkins.plugins.extensible__choice__parameter.ExtensibleChoiceParameterDefinition>
                </parameterDefinitions>
                </hudson.model.ParametersDefinitionProperty>
                </properties>
                <scm class="hudson.scm.NullSCM"/>
                <canRoam>true</canRoam>
                <disabled>false</disabled>
                <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
                <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
                <triggers/>
                <concurrentBuild>false</concurrentBuild>
                <builders/>
                <publishers>
                <org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin plugin="weblogic-deployer-plugin@3.6">
                <mustExitOnFailure>false</mustExitOnFailure>
                <forceStopOnFirstFailure>false</forceStopOnFirstFailure>
                <isDeployingOnlyWhenUpdates>false</isDeployingOnlyWhenUpdates>
                <buildUnstableWhenDeploymentUnstable>false</buildUnstableWhenDeploymentUnstable>
                <deployedProjectsDependencies></deployedProjectsDependencies>
                <tasks>
                <org.jenkinsci.plugins.deploy.weblogic.data.DeploymentTask>
                <id>xxxxxx</id>
                <weblogicEnvironmentTargetedName>xxxxxx</weblogicEnvironmentTargetedName>
                <deploymentName></deploymentName>
                <deploymentTargets>xxxxxxx</deploymentTargets>
                <isLibrary>false</isLibrary>
                <builtResourceRegexToDeploy>$MYLIB</builtResourceRegexToDeploy>
                <baseResourcesGeneratedDirectory>\\xxxxxx</baseResourcesGeneratedDirectory>
                <taskName></taskName>
                <jdk>
                <name>environment</name>
                <home>C:\Program Files\Java\jdk1.7.0_51</home>
                <properties/>
                </jdk>
                <stageMode>bydefault</stageMode>
                <commandLine>-noexit -undeploy -debug -remote -verbose -name {wl.deployment_name} -targets {wl.targets} -adminurl t3://{wl.host}:{wl.port} -user {wl.login} -password {wl.password} -library;
                -deploy -debug -remote -upload -verbose -name {wl.deployment_name} -source {wl.source} -targets {wl.targets} -adminurl t3://{wl.host}:{wl.port} -user {wl.login} -password {wl.password} -library</commandLine>
                <deploymentPlan></deploymentPlan>
                <protocol>t3</protocol>
                </org.jenkinsci.plugins.deploy.weblogic.data.DeploymentTask>
                </tasks>
                <policies/>
                </org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin>
                </publishers>
                <buildWrappers/>
                </project>

                 

                I replaced some configuration values with xxxx in xml.

                 

                 

                Hope this helps.

                Regards,

                1. Unknown User (raphc)

                  Thanks,

                  By the way, thie field 'Ressource générée à deployer' doesn't support variable. Only environment, targets, name and 'Base directory where the resource can be found' fields supports it. So the plugin needs an enhancement.

                  What do you want to set the name of the resource to deploy in a variable ? Do you want to select what application you want to deploy when you launch the job ?

                  Regards,

                  1. Unknown User (sbarrete)

                    Yes,

                    I just want to select one of several libraries (.war) to deploy with the help of a choicie list. The list has not always the same items.

  22. Unknown User (antoniogracia)

    Hello

    The 'Weblogic Deployment Plugin" configuration section is missing in plugin version 4.0 and Jenkins 2.60.3.

    Thanks

     

     

    1. Unknown User (raphc)

      Hi,

      Can you give me more details? is jenkins logs display stack trace or error related to the plugin ?

      Did you use plugin before ? what version ? Did you upgrade your jenkins version ?

      Thanks

       

       

       

      1. Unknown User (antoniogracia)

        Thanks Raphael,

         

        We are using the plugin for few months ago, version 3.6. Also, we update Jenkins versions continously.

        We recently upgrade the plugin to version 4.0. When job is run, the JDK is not located by plugin (jenkins.err.log):

        Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/D:/Jenkins/plugins/weblogic-deployer-plugin/WEB-INF/lib/weblogic-deployer-plugin.jar!/org/jenkinsci/plugins/deploy/weblogic/WeblogicDeploymentPlugin/global.jelly:3:135: <j:invokeStatic> method getJdkToolAvailables threw exception: null
        at org.apache.commons.jelly.tags.core.InvokeStaticTag.doTag(InvokeStaticTag.java:148)

        and in the job output console this message is shown:

        [WeblogicDeploymentPlugin] - Loading JDK 'system' ...
        [WeblogicDeploymentPlugin] - Unable to load JDK 'system' from node 'hudson.model.Hudson@9aa1990'. The plugin execution is disabled.

        We downgrade to version 3.6 and job's execution is ok.

        When we saw this error, we went to "Configuration section" to check JDK selection and we could not see "Weblogic Deployment Plugin" section. When the downgrade was made, the section appeared again.

        Regards

        1. Unknown User (raphc)

          Thank you for the feedback,

          Is your job run on master/ node ? What's the OS your jenkins instance is installed ? Did you configured JDK in jenkins tools ? How your jdk in jenkins are configured (not the plugin configuration but jenkins configuration ) ?

          Regards,

           

        2. Unknown User (raphc)

          Hy Unknown User (antoniogracia)

          I can't reproduce your error. Can you tell me more about your configuration (job, global configuration ...). What is the jdk selected in weblogic plugin ?

           

          Thanks

  23. Unknown User (hviko)

    *** WORK AROUND for WebLogic 12.2.x ***

    Just generate and use a wlfullclient-10.3.6.jar, with that I can deploy without any problem onto our WebLogic Server Version: 12.2.1.1.0.

    Ahhh finally (smile)

    1. Unknown User (raphc)

      Thanks Unknown User (hviko)

       

      I will add this workaround to the doc.

       

      Regards

  24. Unknown User (simon_burgess)

    Hi

    I am using the following versions:

    Jenkins 2.66

    Deployer plugin: 3.7

    WLS: 10.3.6.0

    JDK: 1.7

     

    Configuration.xml

    <?xml version="1.0" encoding="UTF-8"?>
    <config xmlns="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin plugin-configuration.xsd">
    <weblogic-targets>
    <weblogic-target>
    <name>17APP26</name>
    <host>myserver.co.uk</host>
    <port>7001</port>
    <login>dev</login>
    <password>xxxxx</password>
    <authMode>BY_LOGIN</authMode>
    </weblogic-target>
    </weblogic-targets>
    </config>

     

    But I get the following deploy error:

    ------------------------------------ ARTIFACT DEPLOYMENT ------------------------------------------------
    weblogic.Deployer invoked with options: -debug -stage -remote -verbose -upload -name olwa_CI_EAR -source 'F:\jenkins_workspaces\Weblogic_Deploy\workspace\OLWABCSWebserviceEAR.ear' -targets soa_server1 -adminurl t3://myserver.co.uk:7001 -user platformdev -deploy
    [WebLogicDeploymentManagerImpl.\(\):115] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [WebLogicDeploymentManagerImpl.getNewConnection\(\):158] : Connecting to admin server at myserver.co.uk:7001, as user platformdev
    [ServerConnectionImpl.getEnvironment\(\):286] : setting environment
    [ServerConnectionImpl.getEnvironment\(\):289] : getting context using t3://myserver.co.uk:7001
    [ServerConnectionImpl.getMBeanServer\(\):237] : Connecting to MBeanServer at service:jmx:t3://myserver.co.uk:7001/jndi/weblogic.management.mbeanservers.domainruntime
    [ServerConnectionImpl.getMBeanServer\(\):237] : Connecting to MBeanServer at service:jmx:t3://myserver.co.uk:7001/jndi/weblogic.management.mbeanservers.runtime
    [DomainManager.resetDomain\(\):36] : Getting new domain
    [DomainManager.resetDomain\(\):39] : Using pending domain: false
    [MBeanCache.addNotificationListener\(\):96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@6422d556
    [MBeanCache.addNotificationListener\(\):103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@6422d556
    [MBeanCache.addNotificationListener\(\):96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@6ba67ab5
    [MBeanCache.addNotificationListener\(\):103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@6ba67ab5
    [ServerConnectionImpl.initialize\(\):169] : Connected to WLS domain: ofmsjpdomain
    [ServerConnectionImpl.setRemote\(\):480] : Running in remote mode
    [ServerConnectionImpl.init\(\):159] : Initializing ServerConnection : weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl@4b0a1b0d
    [BasicOperation.dumpTmids\(\):713] : Incoming tmids:
    [BasicOperation.dumpTmids\(\):715] :

    Unknown macro: {Target=soa_server1, WebLogicTargetType=server, Name=olwa_CI_EAR}

    , targeted=true
    [BasicOperation.deriveAppName\(\):141] : appname established as: olwa_CI_EAR
    <21-Dec-2017 10:08:25 o'clock GMT>
    [BasicOperation.dumpTmids\(\):713] : Incoming tmids:
    [BasicOperation.dumpTmids\(\):715] :

    , targeted=true
    [BasicOperation.loadGeneralOptions\(\):628] : Delete Files:false
    Timeout :3600000
    Targets:
    soa_server1
    ModuleTargets={}
    SubModuleTargets={}
    }
    Files:
    null
    Deployment Plan: null
    App root: C:\Users\p36849\AppData\Local\Temp\p36849\.\config\deployments\olwa_CI_EAR
    App config: C:\Users\p36849\AppData\Local\Temp\p36849\.\config\deployments\olwa_CI_EAR\plan
    Deployment Options:

    Unknown macro: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=stage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=olwa_CI_EAR,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false}

    java.io.IOException: The filename, directory name, or volume label syntax is incorrect
    at java.io.WinNTFileSystem.canonicalize0(Native Method)
    at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:414)
    at java.io.File.getCanonicalPath(File.java:618)
    at java.io.File.getCanonicalFile(File.java:643)
    at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.upload(ServerConnectionImpl.java:836)
    at weblogic.deploy.api.spi.deploy.internal.BasicOperation.uploadFiles(BasicOperation.java:327)
    at weblogic.deploy.api.spi.deploy.internal.BasicOperation.execute(BasicOperation.java:438)
    at weblogic.deploy.api.spi.deploy.internal.BasicOperation.run(BasicOperation.java:176)
    at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.deploy(WebLogicDeploymentManagerImpl.java:386)
    at weblogic.deploy.api.tools.deployer.DeployOperation.execute(DeployOperation.java:48)
    at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:139)
    at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
    at weblogic.utils.compiler.Tool.run(Tool.java:158)
    at weblogic.utils.compiler.Tool.run(Tool.java:115)
    at weblogic.Deployer.run(Deployer.java:70)
    at weblogic.Deployer.main(Deployer.java:54)
    [ServerConnectionImpl.close\(\):332] : Closing DM connection
    [ServerConnectionImpl.close\(\):352] : Unregistered all listeners
    [ServerConnectionImpl.closeJMX\(\):372] : Closed JMX connection
    [ServerConnectionImpl.closeJMX\(\):384] : Closed Runtime JMX connection
    [ServerConnectionImpl.closeJMX\(\):396] : Closed Edit JMX connection

    ....
     
    Note: ignore 'unknown macro' messages above that's just generated by the comments macro, actual error is 'java.io.IOException: the filename, directory name or volume name is incorrect'
    Any ideas? 'App root' and 'App config' paths mentioned above don't exist, is that the problem? Where do I specify these if required?
     
    thanks

  25. Unknown User (simon_burgess)

    I upgraded to plugin 4.1 (from 3.7) and its working fine (smile)

  26. Unknown User (jitenjha11)

    Dear Team,

    I am using Jenkins version: 2.73.3 and WebLogic deployments Plugin = 4.1, Maven Integration = 2.15.1, bouncycastle API = 2.16.1.

    Issue: When I am trying to deploy code using plugin Its performance is very slow. It is not very much consistent some of the code deployment it is taking 1 hrs to 2 hrs and some time it takes 5 min even the file size is almost same. 



  27. Unknown User (jitenjha11)

    Dear Team Waiting for your response.

  28. Unknown User (kpal)

    Hello, 


    We have our artifacts as exploded format . can this plugin work for exploded deployment?

    Please let me know. Thanks