IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  How do we deploy BPM Process models and CAF fabric tasks using deployer

    Posted Mon December 02, 2024 08:06 AM
    Hi Team
    IS version: 10.15
    I am facing issues while deploying BPM Process models using deployer
    I have added source and target servers in deployer Servers section of IS&TN and BPM (Process Model) section and WmDeployer and WmDeployerResource is present in both source and target servers
     
    created set selected (BPM Process Model)
    and I see a dependency of config/wmprt/TEST_BPMDeploymentProcess.TEST_BPMDeploymentProcess.TEST_BPMDeploymentProcess_TEST_BPMDeploymentProcess1.dev0.xml
     
    and when i click Add dependency i am getting
      [DEP.0002.0092] Deployer cannot update package TEST_BPMDeploymentProcess version in the deployment set.
     
    How do we fix this.  Do we have any CI/CD process for BPM.


    ------------------------------
    Abhijith Parre
    ------------------------------


  • 2.  RE: How do we deploy BPM Process models and CAF fabric tasks using deployer

    Posted Tue December 03, 2024 09:11 AM

    Hi Abhijit,

    your build is having all dependencies related to the same WM Version?



    ------------------------------
    Zainul Abideen
    webMethods Developer (Assistant Consultant)
    Innovation Team
    Hyderabad
    ------------------------------



  • 3.  RE: How do we deploy BPM Process models and CAF fabric tasks using deployer

    Posted Tue December 03, 2024 06:44 PM

    Yes there is a CI/CD for BPM but I never used it myself. There is a whole section in deployer documentation that is dedicated to repository based deployment. You can find the link below. 

    repo based deployment

    For your question, it is difficult to find out what is wrong from a single log entry. Did you add your MWS server to your deployment set and compiled that candidate? That package is probably deployed to MWS. You need to share the rest of the deployer and IS logs so that we can find out what went wrong. You can mask the confidential information. What is the version of the target and source servers? 



    ------------------------------
    engin sarlak
    ------------------------------



  • 4.  RE: How do we deploy BPM Process models and CAF fabric tasks using deployer

    Posted Wed December 04, 2024 04:38 AM

    Hi Engin,Zainul

    The issue is resolved. We had recreated the process project again and mapped the instances of target environment again and seems the issue got resolved and the process model is displayed correctly in MWS and in WmPRT package process page

    For the repository based deployment i tried the below

    in the build.properties file i made the changes to enable.build.IS=true and same for BPM gave build.output.dir and other parameters.

    in the repository path i copied the packages from /IntegrationsServer/default/packages to repository folder and i see acdl files and others got created from deployer and deployment is successfull in that way.

    Regards

    Abhijith



    ------------------------------
    Abhijith Parre
    ------------------------------



  • 5.  RE: How do we deploy BPM Process models and CAF fabric tasks using deployer

    Posted Wed December 04, 2024 04:41 AM

    Hi Engin

    We are using CAF fabric tasks and any insights as how to deploy that using deployer.

    From Deployer am able to select Portlets but the fabric tasks are not visbile nor an option to select and deploy them 

    Regards

    Abhijith



    ------------------------------
    Abhijith Parre
    ------------------------------



  • 6.  RE: How do we deploy BPM Process models and CAF fabric tasks using deployer

    Posted Wed December 04, 2024 11:52 AM
      |   view attached

    Unfortunately I did neither CAF development nor deployment. So I can't tell you what exactly is needed to fix. From the deployer point of view, target deployment is pretty much the same, you build the deployment candidate, test it and deploy it. If the deployment candidate has the asset you are referring to and if it has the correct target server for that asset, it will deploy it. Where you get the asset doesn't matter from this point. Processing the source asset though, will be different. You need to add the binary files to your target so that it will know what you need to deploy. If it is repo based, everything is a file, so you need to push your files in to the repository, doesn't matter whether it is an asset off IS or MWS or even OPTIMIZE. According to documentation, you need to add MWS projects directory to your build source directory. Did you add the MWS project directory to build source?



    ------------------------------
    engin sarlak
    ------------------------------