This chapter provides an overview of exporting an existing domain and importing it as a partition into another domain with the help of Domain to Partition Conversion Tool (D-PCT). Enterprise Manager Cloud Control provides an user friendly user interface that helps you to convert domains into partitions.
The export tool component in D-PCT is used on the WebLogic Server installation that hosts the source domain. You can use this tool to create and configure partition, resource groups, and resource group templates. By default, this tool moves all applications, libraries, and resources to the new partition. Optionally, it also provides a mechanism for selecting individual applications, libraries, and resources.
In particular, this chapter covers the following:
Prerequisites of Migrating a WebLogic Server Domain to a Domain Partition:
Before you configure D-PCT, you must fulfill the following prerequisites:
The target domain must be configured on a WebLogic Server 12.2.1.1 or above installation.
You must download and install JDK 8 on the host machine of the source domain. This is required for running the export tool on WebLogic Server 10.3.6.
The target WebLogic Server 12.2.1.1 or above domain must be up and running.
All servers in the domain must be up and running.
For a straightforward conversion from a domain to a partition and to ensure correct operation of the import tool to create a virtual target based on the JavaScript Object Notation (JSON) file, it is important that the target and source domains have identical cluster and server names.
Before using the import tool to create a new partition, you must ensure that the new domain is configured the same as the source domain with regard to servers, clusters, virtual targets, and security realms.
Limitations of Migrating a WebLogic Server Domain to a Domain Partition:
The following scenarios are not supported by Domain to Partition Conversion Tool (D-PCT) tool:
The domain upgrade of libraries and resources to a new release is not supported at import. Administrators and users are responsible for possible necessary domain upgrades from the source domain before exporting the archive file.
Neither the application runtime state nor the application specific runtime configuration is exported to the archive file. For example, the JMS messages in queues or users in an embedded LDAP realm are not exported.
The remote clients compiled with WebLogic Server versions prior to 12.2.1 are not able to look up JNDI resources deployed on a partition. They need to be recompiled with the WebLogic Server releases 12.2.1 or later.
JDBC does not support the use of the Logging Last Resource (LLR) feature in WebLogic Server Multitenant. Data sources with this option need to be converted to use a substitute setting that may or may not be an adequate replacement.
For more information on D-PCT limitations and considerations, see Oracle Fusion Middleware Using Oracle WebLogic Server Multitenant guide.
To import a domain partition into an existing WebLogic domain, see Importing WebLogic Domain Partition.