Our new delivery channel, webMethods Package Manager

Maybe this new tool could help? New tool: Automate update of ART adapter connections on Integration Server

1 Like

Already reviewing it, but I would prefer if there is an out of box solution.

I tried running wpm with the steps provided in my Windows laptop. But I get the error :

You need to specify the windows version, you are trying to run the shortcut to the .sh file.
Swap wpm with wpm.bat

Does it also handle the IS external assets? For example if a document in the package is publishable, does it sync the document with the queue server, broker or umserver?

1 Like

Hi Holm, this is an interesting read. Does WPM supports v10.11 as well?

As we are prototyping wpm, we are realizing that each package needs its own git repo.

@CHIRAG - these items in the article by @John_Carter4 infer that constraint.

We will be adding multi package repo support in the near future. However, I would still advise against it as it makes version control much less fine grained. Packages should have their own life cycle in order to ensure agile development. Bundling packages together puts us back in the age on the monolith.

For me the main use-case for multi-package repos is the ability to have a single repo for the main package and its test package.

Hi @John_Carter4
Where are the wM base images kept now? There is a link to the SAG “Container Registry” in the above article but it is only SAG Adabas and Natural products.

—> Wayne

Hm, perhaps some misunderstanding? I have done tests with https://hub.docker.com/r/softwareag/webmethods-microservicesruntime over the last couple of days.

Yet, it is indeed interesting how the transition will look like …

https://containers.webmethods.io for container images
https://packages.webmethods.io for webMethods packages

You can probably guess why these changes have taken place…

1 Like

Thanks @Stephane.TAILLAND_emp for the location. And yes, I’m very aware of why these changes took place :slight_smile:

@John_Carter4 can you please update the link to the container registry in the Introduction section above?