Metering Workflow for Flexible Consumption Pricing (FCP)

TIBCO BusinessWorks™ Container Edition and Plug-ins for AWS Marketplace starts an aggregator service on every EC2 instance, launched through Single AMI or CloudFormation Template option. This service MUST be running on the EC2 instance. Any TIBCO BusinessWorks Container Edition application started in a Docker container on the EC2 instance, it automatically connects to the aggregator and sends its metering units every hour. The aggregator service aggregates metering units from all the containers running on the EC2 instance and invokes AWS Marketplace Metering Service to send metering record every hour.

Scenario 1

If aggregator service is down,
  • TIBCO BusinessWorks Container Edition application tries to send metering units to aggregator hourly.
  • If the hourly invocation fails due to TIBCO BusinessWorks Container Edition application not receiving any response from aggregator, the application tries to send the metering units to aggregator in the next hour.
  • If 2 retry attempt fails, then TIBCO BusinessWorks Container Edition application will be stopped.

Scenario 2

If aggregator service fails to send metering records to AWS metering service,

  • TIBCO BusinessWorks Container Edition application tries to send metering units to aggregator hourly.

  • If the hourly invocation fails due to TIBCO BusinessWorks Container Edition application receiving any status code other than 200 from aggregator, the application tries to send the metering units to aggregator in the next hour.
  • If 3 retry attempts fail, then TIBCO BusinessWorks Container Edition is stopped.