Webmethods Metering Setup Configuration

,
1

Product/components used and version/fix level:

webMethods 10.15

Detailed explanation of the problem:

We have 4 integration server instances running under the same installation on 2 VMs.

In this configuration should each instance be given a unique alias under the custom_wrapper.conf set.METERING_RUNTIME_ALIAS.

For example we have:

  • Instance 1A set.METERING_RUNTIME_ALIAS=Prod1A
  • Instance 1B set.METERING_RUNTIME_ALIAS=Prod1B…etc

Error messages / full error message screenshot / log file:

Question related to a free trial, or to a production (customer) instance?

If this the correct configuration? Or should we be using something like Prod1 for VM1 and Prod2 for VM2?

2

The alias is meant to help you identifying the self hosted runtimes in the cloud metering console.
If you give the same alias to these 4 runtimes, you’ll see consolidated metering data for these 4 runtimes.
If you give these runtimes distinct aliases, then you’ll display metering data for each runtime.

If these 4 runtimes are part of the same cluster and they have the same role, you should give them the same alias.
If they have distinct roles (for instance 2 runtimes for Active Transfer and two for Integration), then you could give them distinct aliases.

2 Likes