webMethods

 View Only
Expand all | Collapse all

Repository-based builds, set MinimumTargetRuntimeVersion

  • 1.  Repository-based builds, set MinimumTargetRuntimeVersion

    Posted Sun November 21, 2021 04:09 PM

    What product/components do you use and which version/fix level?

    Asset Build Environment (ABE), playing with wM 10.7

    What are trying to achieve? Please describe in detail.

    On a runtime-based deployment project, I was able to take a an IS 10.7 package/patch and have it deployed on an IS 10.3.
    However, when coming to having a repository-based deployment project, composites built by the build.bat/sh are automatically assigning MinimumTargetRuntimeVersion=10.7.0.0. I still have target envs in 10.3, which means the WmDeployer will not allow deploying these composites into those “IS 10.3” servers.

    I was wondering if there is a way to make these composites assigning MinimumTargetRuntimeVersion=10.3.0.0. Is this possible?

    Do you get any error messages? Please provide a full error message screenshot and log file.


    #WmDeploy
    #webMethods
    #Repository-based-deployment
    #ABE


  • 2.  RE: Repository-based builds, set MinimumTargetRuntimeVersion

    Posted Tue November 23, 2021 05:23 PM

    Can’t you just manipulate the composites and put the desired value into it? After all, they are not signed.


    #WmDeploy
    #ABE
    #webMethods
    #Repository-based-deployment


  • 3.  RE: Repository-based builds, set MinimumTargetRuntimeVersion

    Posted Fri December 17, 2021 05:12 PM

    This might be an option, if no other option is available.


    #webMethods
    #WmDeploy
    #ABE
    #Repository-based-deployment