Unable to deploy shared libraries using weblogic.Deployer command with attributes -targets [CLUSTER] and -name [no_value] (Doc ID 2096526.1)

Last updated on DECEMBER 05, 2016

Applies to:

Oracle WebLogic Server - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

After upgrading to WLS 12.1.3, unable to deploy shared libraries using weblogic.Deployer command with attributes -targets [CLUSTER] and -name [no_value] 

i.e This issue is seen only while deploying the application to a cluster and when no value is specified for "-name" attribute.

Note :

- This issue is NOT seen while deploying the application to a DefaultServer. 

- "-name" attribute should contain a deployment name for the deployed application.

If you do not specify this attribute, WebLogic Server assigns a deployment name to the application, based on its archive file or exploded directory.

Link : https://docs.oracle.com/middleware/1213/wls/WLPRG/wldeploy.htm#WLPRG439

 

Command :

weblogic.Deployer -remote -verbose -upload -noexit -name -source [...BusinessProcessModelLib.war] -targets [CLUSTER] -adminurl t3://[...]:7001 -userconfigfile [userconfig] -userkeyfile [userkey] -deploy -library

 

Following errors are seen :

 

Changes

This issue is seen after upgrading from WLS 12.1.2 to WLS 12.1.3.

In WLS 12.1.2 "-name" picks the name from application's manifest file (when no value is specified for "-name").

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms