Skip to content

Releases: oracle/weblogic-deploy-tooling

WebLogic Deploy Tooling 4.3.4

22 Apr 20:40
@robertpatrick robertpatrick
release-4.3.4
7d67a77
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.3.4 Latest
Latest

Major New Features

None

Other Changes

  • #1792 - Segregated ServerTemplate keystores in the archive file.
  • #1798 - Added ClusterAddress, ListenAddress, InterfaceAddress, and MulticastAddress to the WKO filter
    when using Discover Domain and Prepare Model tools with the -target argument.
  • #1799 - Added the oracle_database_admin_role field to the RCUDbInfo section for users that need to
    use a role that is not SYSDBA.

Bug Fixes

  • #1784 - Prevent Discover Domain tool from trying to discover passwords unless the user specified to do so.
  • #1785 - Change logging level from INFO to FINE for unrecognized attributes when using online operations.
  • #1786 - Fixed RCU discovery issue to properly handle passwords.
  • #1787 - Fixed issue with WKO filter to eliminate errors when traversing the model.
  • #1788 - Restored internal method call to compare WLS versions in the Discover Domain tool.
  • #1789 - Fixing issues with the -target wko filter.
  • #1790 - Add missing 14.1.2 JDK version information to the installation documentation.
  • #1794 - Fixing an issue with the RCU password not being properly decrypted while trying to validate the
    RCU data when running the Create Domain tool.
  • #1795 - Fixing a bug introduced by change #1792 that was causing an error when discovering Server and
    ServerTemplate keystores.
  • #1796 - Fixed an issue where the datasource password was not being decrypted properly when using the
    Discover Domain tool with the -discover_passwords argument.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Assets 4
Loading

WebLogic Deploy Tooling 4.3.3

12 Feb 19:13
@robertpatrick robertpatrick
release-4.3.3
8076c58
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.3.3

Major New Features

None

Other Changes

#1780 - Added new -discover_rcu_datasources option to the Discover Domain Tool to help with migration use cases.

Bug Fixes

#1781 - Fixed an issue with application and library targeting with the Compare Model Tool.
#1782 - Fixed an issue with reading Kubernetes secret file data that was mangling non-ASCII characters.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading

WebLogic Deploy Tooling 4.3.2

31 Jan 21:34
@robertpatrick robertpatrick
release-4.3.2
55b12e5
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.3.2

Changes in Release 4.3.2

Major New Features

None

Other Changes

  • #1778 - Added preliminary support for using an enhanced offline isSet() method when determining whether to write
    computed fields to the model during offline discovery. Once the enhancement is available in a 14.1.2 PSU, we will
    complete the support.

Bug Fixes

  • #1773 - Reduced the logging level of a message about removing attributes from the model to reduce the
    amount of noise on stdout.
  • #1775 - Fixed Discover Domain Tool handling of server keystore files when running with -skip_archive.
  • #1776 - Fixed issues with the ManagedExecutorServiceTemplate, ManagedScheduledExecutorServiceTemplate, and
    ManagedThreadFactoryTemplate folders so that they can be used in models.
  • #1777 - Fixed Create Domain Tool so write the domain's mode-related attributes upfront before the initial call
    to writeDomain() so that the dynamically computed fields are properly persisted in config.xml.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading

WebLogic Deploy Tooling 4.3.1

21 Jan 22:03
@robertpatrick robertpatrick
release-4.3.1
f0d686f
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.3.1

Major New Features

None

Other Changes

  • #1771 - Added support for January 2025 PSUs for 12.2.1.4, 14.1.1, and 14.1.2.

Bug Fixes

  • #1762, #1764 - Fixed issues with causing Discover Domain to generate attribute not supported log entries for
    deprecated attributes.
  • #1763 - Documented WebLogic Server Bug 37443991 as a known limitation.
  • #1765 - Fixed AttributeError when running Discover Domain with either -skip_archive or -remote (GitHub Issue 1607).
  • #1766 - Fixed AttributeError when running Discover Domain with either -skip_archive or -remote
    on different archive types (GitHub Issue 1608).
  • #1767 - Fixed Discover Domain command-line argument validation that allows both -skip_archive and -remote to be
    specified when they are mutually exclusive.
  • #1768 - Improved default value detection for Discover Domain when running against WebLogic Server 14.1.2.
  • #1769 - Cleaned up offline Discover Domain to exclude the JavaHome attribute in the NMProperties folder.
  • #1770 - Fixed secure mode detection to work properly in WebLogic Server 14.1.2. This is critical to reducing the
    number of attributes that show up in the model when using Discover Domain in offline mode.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading

WebLogic Deploy Tooling 4.3.0

01 Jan 15:20
@robertpatrick robertpatrick
release-4.3.0
d6de872
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.3.0

Major New Features

None

Other Changes

  • #1731, #1735, #1736, #1738, #1743, #1748 - Updated aliases for WebLogic Server 14.1.2 GA release.
  • #1732 - Changed default value when using -target to include the domain's bin directory contents.
  • #1737 - Optimized offline discovery of default values in 14.1.2.
  • #1739 - Added aliases for SNMPAgent, SNMPDeploymentAgent, EJBContainer, and Cluster's JtaRemoteDomain folders.
  • #1741 - Added support for deploying and discovering customer resources.
  • #1746 - Added support for the WebLogic Server 12.2.1.4 and 14.1.1 October 2024 PSUs.
  • #1750 - Changed file path resolution to not convert symbolic links to the actual paths.
  • #1751 - Changed JDK validation to allow the user to run WDT tools with OpenJDK and removed broken support for GraalVM.
  • #1752 - Moved away from using jline's deprecated jansi provider to using the jni provider.
  • #1758 - Enhanced Create Domain Tool to allow creating a JRF domain using fully specified RCU Data Sources
    in the resources:/JDBCSystemResource section of the model without requiring the domainInfo:/RCUDbInfo
    section.
  • #1760 - Modified WDT's usage of JAXB classes to prepare for supporting the Jakarta EE 9+ of JAXB runtime.

Bug Fixes

  • #1732 - Fixed bad error message when WLST assign() invocation fails.
  • #1734 - Fixed validation error caused by trying to validate prior to resolving tokens.
  • #1744 - Squelched SLF4J startup messages from printing to stderr.
  • #1748 - Fixed target injector paths causing discovery to fail with sub-deployments.
  • #1749 - Fixed JMS Foreign Server discovery issue when the URL is not using a file, http, or https protocol.
  • #1753 - Cleaned up exiting from the interactive Model Help Tool using Control-D.
  • #1755 - Fixed bug with command-line handling of the WDT encryption passphrase from stdin.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading

WebLogic Deploy Tooling 4.2.1

23 Jul 00:54
@robertpatrick robertpatrick
release-4.2.1
e34cda2
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.2.1

Major New Features

None

Other Changes

  • #1717, #1728 - Extended the API integration between WebLogic Kubernetes Toolkit UI and WDT to pass back the encrypted
    passwords when running the Prepare Model Tool from the WebLogic Kubernetes Toolkit UI.
  • #1722 - Added logic to detect a situation where the user specified in domainInfo:/AdminUserName is also listed in
    the topology:/Security/User list of users and update the topology:/Security/User user's Password field to be
    the same as that specified in domainInfo:/AdminPassword.
  • #1723 - Added support for the WebLogic Server 12.2.1.4 and 14.1.1 July 2024 PSUs.

Bug Fixes

  • #1713 - Added logic at startup to detect when WDT logging is not properly configured.
  • #1715 - Fixed a bug where the domainInfo:/OPSSWalletPassphrase field was not properly handled when using the
    Prepare Model Tool or when using the Discover Domain Tool with the -target argument.
  • #1716 - Fixed the Discover Domain Tool documentation to add missing command-line arguments.
  • #1718 - Fixed an issue with the NativeVersionEnabled attribute of NMProperties not working correctly when running
    the Update Domain Tool.
  • #1720 - Fixed an issue with RCU pre-check error handling that was causing an unhandled Jython error.
  • #1721 - Fixed a bug in the SSH directory listing command for a remote Unix machine.
  • #1724 - Fixed an off-by-one error when using the Archive Helper Tool's remove custom command with a name that starts
    with wlsdeploy/custom/ or config/wlsdeploy/custom/ that was causing the specified location to not be removed.
  • #1727, #1729 - Fixed an issue with Create Domain Tool's RCU pre-check functionality that was causing a Jython
    AttributeException for set when the STB DataSource was defined in the resources:/JDBCSystemResource section of the
    model and specifying one or more JDBC driver properties.
  • #1730 - Fixed an issue where an application or library deployment plan was not being collected when the SourcePath
    contained an excluded location like @@ORACLE_HOME@@.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading

WebLogic Deploy Tooling 4.2.0

18 Jun 21:22
@robertpatrick robertpatrick
release-4.2.0
f2e5967
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.2.0

Major New Features

None

Other Changes

  • #1682 - Added support for discovering built-in security provider data in online mode. This includes
    DefaultAuthenticator users and groups, XACMLAuthorizer policies, XACMLRoleMapper roles, and DefaultCredentialMapper
    user/password credential mappings. As with other discovery features, default values are filtered out and will not
    appear in the model. By default, discovering users and credential mappings require the use of WDT encryption so that
    no clear text passwords are stored in the model or variable files.
  • #1682 - Normalized XACMLRoleMapper role handling by removing the previous discovery of XACMLRoleMapper roles (that was
    not working with newer versions of WebLogic anyway) and removing version limitations during provisioning.
  • #1682 - Deprecated the -use_encryption command-line argument and replaced it with -passphrase_prompt to make the
    purpose of the argument clearer.
  • #1682 - Relaxed the JDK 8 requirement to use WDT encryption. Later versions of JDK 7 have the necessary algorithm
    support so now WDT determines at startup whether the underlying JDK supports WDT encryption or not.
  • #1682 - Used the values of the -admin_user and provided password to populate the domainInfo:/AdminUserName and
    domainInfo:/AdminPassword fields when discovering security provider data.
  • #1688 - Enhanced variable tokenization support to include passwords in discovered security provider data.
  • #1689 - Added the ability to discover the OPSS wallet when running in online mode.
  • #1693 - Changed the wko, wko-dii (deprecated), and wko-pv target values to refer to the latest versions instead
    of WebLogic Kubernetes Operator 3 versions. Added wko3, wko3-dii, and wko3-pv to accommodate users that still
    require the ability to use these older versions.
  • #1697 - Added support for the Prepare Model Tool to preserve any one-way hashed passwords in the model.
  • #1700 - Added support for storing XACML policy and role definitions that could not be converted to their original
    policy and role expressions as XACML files in the archive file.

Bug Fixes

  • #1687 - Fixed a problem with the Discover Domain Tool not properly handling Data Source user names with spaces with
    older versions of WebLogic Server.
  • #1690 - Fixed a problem with determining the default security realm name that caused it to always be myrealm.
  • #1692 - Fixed a misleading error message when the model points to an application outside of the archive file that
    does not exist.
  • #1695 - Fixed an issue where the WebLogic Kubernetes Operator domain.yaml was including a placeholder for the
    domainHome attribute in all cases so that the WebLogic Image Tool could populate it when creating the image.
    This was occurring even in use cases where the WebLogic Image Tool did not have this information. WDT no longer does
    this and will only include the domainHome in the case where the user has specified it on the command line, or in the kubernetes section of the model.
  • #1698 - Fixed issues with the new messages related to the security provider data discovery features.
  • #1701 - Moved the TestSummaryHandler logging class out of the installer since it is only meant for supporting unit tests.
  • #1702 - Fixed a bug in deployment plan discovery for exploded applications.
  • #1703 - Fixed a bug in discovery of domainBin scripts.
  • #1705 - Added missing validation for the WLSUserPasswordCredentialMappings section.
  • #1706 - Fixed a validation bug that was causing lax validation to fail when archive entries were missing.
  • #1707 - Fixed a bug in the handling of the ActiveContextHandlerEntry attribute of an Auditor security provider.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool does not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading

WebLogic Deploy Tooling 4.1.1

02 May 01:39
@robertpatrick robertpatrick
release-4.1.1
acfd92a
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.1.1

Major New Features

None

Other Changes

  • #1685 - Filtered out the default OptionalFeatures folders when they have no attributes so that they do not show up
    in the online discovered model.

Bug Fixes

  • #1677 - Fixed a bug where creating a user with extra attributes would result in invalid LDIFT entries.
  • #1678 - Fixed a bug that was causing errors when deploying a new application and the server required a restart.
  • #1679 - Fixed a bug where the SSHJ libraries (that only work with JDK 8 and above) were causing the tools to fail
    when running with JDK 7.
  • #1680 - Fixed the DataSourceLogFile and WebServerLog folders default value for the DateFormatPattern attribute
    for WLS versions prior to 12.2.1 so that they no longer show up in the online discovered model.
  • #1681 - Worked around a pre-12.2.1 WLST bug that was preventing the online tools from determining the server's WLS version.
  • #1683 - Fixed a bug with the Model Help Tool where our use of JLine libraries (that only work with JDK 8 and above)
    were causing the Model Help tool to fail when run with JDK 7.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool do not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading

WebLogic Deploy Tooling 4.1.0

18 Apr 23:08
@robertpatrick robertpatrick
release-4.1.0
52a9859
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.1.0

Major New Features

None

Other Changes

  • #1668 - Added new discover passwords feature that allows the user to discover passwords and store them in the model in encrypted format.

Bug Fixes

  • #1675 - Fixed a bug with replacing environment variable tokens on Windows.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool do not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading

WebLogic Deploy Tooling 4.0.1

17 Apr 01:54
@robertpatrick robertpatrick
release-4.0.1
0f6a779
Compare
Choose a tag to compare
WebLogic Deploy Tooling 4.0.1

Major New Features

None

Other Changes

  • #1664 - Added support for the OptionalFeatureDeployment top-level folder.
  • #1665, #1667 - Formalized support for both the replicated config/wlsdeploy/custom/ and non-replicated
    wlsdeploy/custom locations. Added support in the Archive Helper Tool and tweaked the validation message
    to only notify the user if they are only using the non-replicated location.
  • #1669 - Enhanced the WLS Policy support to allow users to modify built-in policies.
  • #1674 - Added 12.2.1.4 and 14.1.1 April 2024 PSU support.

Bug Fixes

  • #1666 - Fixed a bug with extracting the WebLogic Remote Console extension that caused an error if the archive file
    includes a directory entry.
  • #1670 - Worked around a Jython 2.2.1 bug with posixpath.isfile() where it was returning False when the answer
    should have been True.
  • #1672 - Added None checks around plan file name calculations.

Known Issues

  • SSH support requires a reasonably recent version of Bouncy Castle. WDT picks up Bouncy Castle from WLST so, for example,
    the 12.2.1.4.0 GA release fails with the following error, as mentioned at hierynomus/sshj#895.
    Applying a recent PSU should resolve the issue for 12.2.1.4 and 14.1.1.

    SEVERE Messages:
        1. WLSDPLY-20008: verifySSH argument processing failed: Failed to initialize SSH context: Failed to SSH connect to host myhost.oracle.com: no such algorithm: X25519 for provider BC

  • SSH support for the Update Domain Tool and Deploy Apps Tool do not work when using an archive file and the remote
    WebLogic Server is running on Windows using the optional, Windows-provided, OpenSSH component. This is due to an
    issue with the SSHJ library WDT is using. See hierynomus/sshj#929 for more information.

See https://oracle.github.io/weblogic-deploy-tooling/userguide/limitations/limitations/ for the current set of known limitations.

Loading