CPBM Jobs
Jobs are system-generated tasks to run in a given time period to accomplish activities such as billing.
| Batch Job Name | Start time | Dependence on others | Seen in UI | Job successful sign | Overview | Notice mail when job fails |
|---|---|---|---|---|---|---|
| Manager (dailyBillingJob) | 1:00 A.M.every day | None | Yes | Status is displayed in UI as completed, with adjacent blue circle. Check the description in the UI in case of error status. | All billing processing is done by "DailyBillingJob". By default, this job is scheduled to run at 1:00 A.M. server time. There are two sub-processes in the DailyBilling job: •First sub-process scans through all the service instances and fetches their usage data for the previous day. This data is converted into useful information which CloudPortal Business Manager can understand and is persisted. •Second sub-process scans through all the tenants, picks up the information from the previous sub-process, uses it to update or post account statements, and make payments. Both of these sub-processes are transactional; if any of the service instance fails during the reporting of daily usage, it is skipped and the next service instance is requested for its usage data. Similarly, if the second sub-process fails for a tenant, say during processing payment, it is once again skipped and the second tenant is processed. | Yes. Mail is sent to Admin support - on error, partial error, and warning. |
| Trial Expiry Job (trialExpiry) | 3:10 A.M. every day | None | Yes | Status is displayed in UI as completed, with adjacent blue circle. Check the description in the UI in case of error status. | This job runs once every day and checks all trial accounts and calculates the time left for expiry of each account. Depending on the configuration, mails are sent to inform the customer of the days left until the trial expires. On expiry of the trial period, if the account is not converted to a paying account, the account is suspended. After account suspension, if the account is not still converted to a paying account within the configured number of days, then the account is terminated. | Yes. Mail is sent to Admin support - on error, partial error, and warning. |
| Cloud Service Event Processing Job (cloudServiceEventProcessing) | Every 6 minutes | None. This job does not run when the dailyBilling job is running. | Seen in UI only if job fails. | Check the description in the UI in case of error status. | This job polls connectors for every service instance and provides a list of events that CloudPortal Business Manager can understand. As a service provider, you can subscribe to these events and run any process that you want, such as monitoring, and so on. This job does not run when the dailyBilling job is running. | No mail is sent. |
| Work Flow Job (workflowJob) | Every 5 seconds | None | Seen in UI only if job fails. | Check the description in the UI in case of error status. | This job runs every 5 seconds and is responsible for running the workflow engine which picks up any workflow in NEW and RUNNING state and runs it. Only one instance of this job runs at one moment of time. For more information on workflow engine, refer to the Workflow Management section in the Administration Guide. | Yes. Mail is sent to Admin support - on error, partial error, and warning. |
| Subscription Validation Job (subscriptionValidationJob) | Every 1 hour | None | Seen in UI only if job fails | Check the description in the UI in case of error status | This job runs every hour and checks if resource handle is active for each active subscription. If the resource handle is not active, it marks the subscription as free to re-provision another resource. | Yes. Mail is sent to Admin support - on error, partial error, and warning. |
| Billing Export Job | 4 A.M. every day | None | Yes | Status is displayed in UI as completed, with adjacent blue circle. Check the description in the UI in case of error status. | This job runs once daily and generate billing feed of the following types: 1. DailyAccountStatementStream: Account statements posted the day before 2. DailyInvoiceStream: Invoices posted the day before 3. DailyPaymentAndCreditStream: Payments and credits made the day before 4. DailyPaymentFailureStream: Payment failures that occurred the day before This file is stored locally in the export.directory and exported to the export.URL as specified in Configuration > Billing. For more details on the Billing feed, refer to Customizing Billing Exports. | Yes. Mail is sent to Admin support - on error, partial error, and warning. |
| Daily Custom Job (dailyJobTrigger) | 10:15 A.M. every day | None | Yes | Status is displayed in UI as completed, with adjacent blue circle. Check the description in the UI in case of error status. | This job runs once every day and generates all custom reports if any such implementation is done. | Yes. Mail is sent to Admin support - on error, partial error, and warning. |
| Monthly Custom Job (monthlyJobTrigger) | 10:15 A.M.every first day of the month | None | Yes | Status is displayed in UI as completed, with adjacent blue circle. Check the description in the UI in case of error status. | This job runs once every first day of the month and generates all custom reports if any such implementation is done. | Yes. Mail is sent to Admin support - on error, partial error, and warning. |
Billing resiliency job
| Parameter value | Action |
|---|---|
| 0 | Do not process these usages. |
| 1 | Export invoice feeds separately for these usages and do not apply the charges for these in the system. These feeds (csv/xml) can be used externally by the administrator for offline settlements. |
| 2 | Apply the charges for these old usages into the current billing period for each account. |
| 3 | Apply the charges for these old usages in the billing period to which they actually belong. This will affect the total charges, net amount and balance forward amounts of all the billing periods since the date of the usage up to the current period. |
Total spend and total charges may increase if the job is run using configuration value 2 or 3 because usages or consumption not accounted for earlier get processed. This may cause some accounts to hit the spend limits and spend budgets in the current month. Hence it is advised to adjust these limits before running the billing resiliency job.
update cloud_portal.QRTZ_TRIGGERS set NEXT_FIRE_TIME = (((UNIX_TIMESTAMP()+15)*1000)+1) where TRIGGER_NAME='billingResiliencyJobTrigger';
Comments