My Oracle Support Banner

Staging Mode Not Set While Using WLST deploy() Command When Security Model is Specified (Doc ID 883032.1)

Last updated on JUNE 08, 2020

Applies to:

Oracle WebLogic Server - Version 9.2 to 10.0
Information in this document applies to any platform.

Symptoms

When trying to deploy an application using WLST, the deploy() command ignores the 'stageMode' option when a securityModel is specified. For example:

deploy('${APP_NAME}', path='${DOMAINDIR}/${SOURCE_FILE}', targets='${TARGET_SERVERS}', stageMode='stage', securityModel='CustomRoles')

In the admin console, the staging mode value is not set to stage. Instead, it shows as staging Mode is "Not Specified."

However, if the securityModel is not defined in the WLST deploy() command, then the value of stageMode is honored. For example:

 

deploy('${APP_NAME}', path='${DOMAINDIR}/${SOURCE_FILE}', targets='${TARGET_SERVERS}', stageMode='stage')

In this case, the application is deployed in the staging environment and the value of stageMode is set to stage.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.