Issues faced with startup scripts and library paths when creating domain template (Doc ID 1337191.1)

Last updated on OCTOBER 12, 2022

Applies to:

Symptoms

When customer creates a domain through a domain template for a Portal installation, the default portal libraries, usually deployed from "<WLP_HOME>/light-portal/lib/j2ee-modules/maintenance/1032/default" location are deployed from the "BEA_HOME/user_projects/applications" directory.

 The issue that perceived with is that for any domain that is extended using a template (jar file), the deployments or libraries are not referenced from their original location in the file-system, but are actually copied to a relative path and referenced from there in the new domain.

The issue is reproducible using a simple WLS domain (non-portal), creating a template from the same and then configuring a new domain by using that template. When using the Domain Configuration Wizard to create a domain with the template, the source path of the shared libraries are relative to the "Application Location"+"Domain Name". However The issue seen is that there is no option in the Domain Template Builder or the Configuration Wizard to change this behavior.

Changes

No changes as such. Simply creating a domain template and creating a new domain out of that template will result in such behavior

Cause

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