X

Proactive insights, news and tips from Oracle WebLogic Server Support. Learn Oracle from Oracle.

  • July 15, 2016

WebLogic Server 12.2.1.1.0 - Domain to Partition Conversion Tool (DPCT) Updates

Guest Author


WebLogic Server 12.2.1.1.0 - Domain to Partition Conversion Tool (DPCT) Updates

The Domain to Partition Conversion Tool (DPCT) provides assistance with the process of migrating an existing domain from WebLogic Server releases 10.3.6, 12.1.2, 12.1.3 or 12.2.1 domain to a partition in a WebLogic Server 12.2.1 domain.

The DPCT process consists of two independent but related operations:

  • The first operation involves inspecting an existing domain and exporting into an archive that captures the relevant configuration and binary files.
  • The second task is to use one of several import partition options available with WebLogic Server 12.2.1 to import the contents of the exported domain to create a new partition. The new partition will contain the configuration resources and application deployments from the source domain.

With the release of WebLogic Server 12.2.1.1.0 several updates and changes have been made to DPCT to further improve its functionality.

The updated documentation covering the new features, bug fixes and known limitations is here:
https://docs.oracle.com/middleware/12211/wls/WLSMT/config_dpct.htm#WLSMT1695

Key Updates

a) Distribution of DPCT tooling with WebLogic Server 12.2.1.1.0 installation: initially the DPCT tooling was distributed as a separate zip file only available for download from OTN.

With the 12.2.1.1.0 release, the DPCT tooling is provided as part of the base product installation as:

$ORACLE_HOME/wlserver/common/dpct/D-PCT-12.2.1.1.0.zip

This file can be copied from the 12.2.1.1.0 installation to the servers where the source domain is present and extracted for use.

 The DPCT tooling is also still available for download from OTN:

 http://www.oracle.com/technetwork/middleware/weblogic/downloads/wls-for-dev-1703574.html

b) No patch require: previous use of DPCT required a patch to be applied to the target 12.2.1 installation in order to import an archive generated by the DPCT tooling. This requirement has been resolved.

c) Improved platform support: several small issues relating to the use of DPCT tooling on Windows have been resolved.

d) Improved reporting: a new report file is generated for each domain that is exported, listing the details of the source domain as well as each of the configuration resources and deployments that were captured in the exported archive. Any resources that were unable to be exported are also noted.

e) JSON Overrides file formatting: the generated JSON file that serves as an overrides mechanism to allow target environment customizations to be specified on the import is now formatted correctly to make it clearer and easier to make changes.

f) Additional Resources in JSON Overrides file: in order to better support customization on the target domain additional resources such as JDBC System Resources, SAF Agents, Mail Sessions and JDBC Stores are now expressed as configurable objects in the generated JSON file.

g) Inclusion of new export-domain scripts: the scripts used to run the DPCT tooling have been reworked and included as new (additional) scripts. The new scripts are named export-domain.[cmd|sh] and provide clearer help text and make use of named parameters for providing input values to the script. The previous scripts are provided for backwards compatibility and continue to work, but it is recommended the new scripts are used where possible.

Usage detail for the export-domain script:

Usage: export-domain.sh -oh {ORACLE_HOME} -domainDir {WL_DOMAIN_HOME}
       [-keyFile {KEYFILE}] [-toolJarFile {TOOL_JAR}] [-appNames {APP_NAMES}]
        [-includeAppBits {INCLUDE_APP_BITS}] [-wlh {WL_HOME}]
       where:
             {ORACLE_HOME} : the MW_HOME of where the WebLogic is installed
             {WL_DOMAIN_HOME} : the source WebLogic domain path
             {KEYFILE} : an optional user-provided file containing a clear-text passphrase used to encrypt exported attributes written to the archive, default: None;
             {TOOL_JAR} : file path to the com.oracle.weblogic.management.tools.migration.jar file.
             Optional if jar is in the same directory location as the export-domain.sh
             {APP_NAMES} : applicationNames is an optional list of application names to export.
             {WL_HOME} : an optional parameter giving the path of the weblogic server for version 10.3.6.Used only when the WebLogic Server from 10.3.6 release is installed under a directory other than {ORACLE_HOME}/wlserver_10.3

Enhanced Cluster Topology and JMS Support

In addition to the items listed above, some restructuring of the export
and import operation has enabled DPCT to better support a number of key
WebLogic Server areas. 

When inspecting the source domain and generating the export archive, DPCT now enables the targeting of the resources and deployments to appropriate Servers and Clusters in the target domain. For every Server and Cluster in the source domain, there will be a corresponding resource-group object created in the generated JSON file, with each resource-group targeted to a dedicated Virtual Target, which in turn can be targeted to a Server or Cluster on the target domain.

All application deployments and resources targeted to that particular WebLogic Server instance or cluster in the source domain corresponds to a resource group in the target domain.

This change also supports the situation where the target domain has differently named Cluster and Server resources than the source domain, by allowing the target to be specified in the JSON overrides file so that it can be mapped appropriately to the new environment.


A number of the previous limitations around the exporting of JMS configurations for both single server and cluster topologies have been addressed, enabling common JMS use cases to be supported with DPCT migrations. The documentation contains the list of existing known limitations.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.