Cloud Cruiser became HPE Consumption Analytics on Nov. 1, 2018. You'll still see the old name in places while we update this site.

 

 

Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 for HPE GreenLake Flex Capacity > Working in Cloud Cruiser > Configuring and Administering Azure for Partner Center > Onboarding Azure for Partner Center FC Customers > Configuring a New Partner Center Endpoint

Configuring a New Partner Center Endpoint

The Partner Center API collector is configured by default to collect from a single Partner Center endpoint.  However, multiple endpoints can be collected from by modifying the Spring Batch XML job entitled Partner_Center_CollectUsage., Partner_Center_CollectRates, and Partner_Center_CollectRetailRates.  The following steps explicitly walk through the process of adding another endpoint (e.g., adding a US endpoint to the existing NZL endpoint).

Configuring the Collector Properties

Before You Begin

By default, the Partner Center collector uses ${env.usageDir}/AzurePC as the common directory.  However, when adding a new collection endpoint, another base directory must be created to prevent the regions from interfering with one another.  It needs to be relative to ${env.usageDir} and can be titled whatever is desired.  For example, it could be AzureUS for United States.  Additionally, directories entitled usage, monthlyUsagerates, and retailRates should be created within the new directory.

Creating the New Collector Properties File

In order for the new collection to be able to hit the corresponding endpoint, a collection.properties file needs to be created and contain the relevant information.

  1. Create a file entitled collection.properties at the location determined in the Before You Begin section (e.g., ${env.usageDir}/AzureX/collection.properties)., where X represents the new region (e.g., US).
  2. Enter the following values in the file (screen capture for reference purposes only):
  • clientId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx, which corresponds to App ID in the API section of Partner Center
  • clientSecret=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, which corresponds to the Key value in the Key Management portion of the API section of Partner Center
  • resellerDomainPrefix=xxxxxxxx, which is the tenant domain of the HPE CSP that takes the form of <domain name>.onmicrosoft.com
  • resellerTenantId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx, which corresponds to Account ID in the API section of Partner Center
  • resellerCustomerId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx, which corresponds to Commerce ID in the API section of Partner Center
  • retailOfferId=MS-AZR-0003P, which the offer ID for Pay-as-You-Go rates
  • currency=XXX, which corresponds to a three-letter ISO 4217 code for the currency in which the resource rates are provided, such as "USD".
  • locale=XX-XX, which corresponds to the location and language/region settings, such as "en-US".
  • regionInfo=XX, which corresponds to two-letter ISO 3166 country/region code that indicates the market where the offer is purchased, such as "US".
  1. Save the file.

Configuring the Partner Center Usage Collection

Before You Begin

The collection.properties file must be created and populated according to the steps in Configuring the Collector Properties.

Creating the New Collection

The collections against the Partner Center API will be done sequentially so the Spring Batch XML will be edited directly to create a new collection to execute after those that already exist.

  1. Click Data > Processing > Advanced Job Maintenance.
  2. Expand Production Jobs and click Partner_Center_CollectUsage.
  3. Copy lines 13 through 32.
  4. Paste them after the last </batch:step> line.
  5. Set the copied <batch: step id="collectX"> to <batch:step id="collectY"> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  6. Set the preceding <batch: step id="collectX"> to <batch: step id="collectX" next="collectY"> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  7. Set the copied <property name="command" value="${env.scriptsDir}/Partner_Center/CollectUsage.sh ${env.scriptsDir}/Partner_Center ${env.selectDate} ${env.usageDir}/AzureX"/> to <property name="command" value="${env.scriptsDir}/Partner_Center/CollectUsage.sh ${env.scriptsDir}/Partner_Center ${env.selectDate} ${env.usageDir}/AzureY"/> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  8. Click Save.

Configuring the Partner Center Rates Collection

Before You Begin

The collection.properties file must be created and populated according to the steps in Configuring the Collector Properties.

Creating the New Collection

The collections against the Partner Center API will be done sequentially so the Spring Batch XML will be edited directly to create a new collection to execute after those that already exist.

  1. Click Data > Processing > Advanced Job Maintenance.
  2. Expand Production Jobs and click Partner_Center_CollectRates.
  3. Copy lines 13 through 32.
  4. Paste them after the last </batch:step> line.
  5. Set the copied <batch: step id="collectX"> to <batch:step id="collectY"> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  6. Set the preceding <batch: step id="collectX"> to <batch: step id="collectX" next="collectY"> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  7. Set the copied <property name="command" value="${env.scriptsDir}/Partner_Center/CollectRates.sh ${env.scriptsDir}/Partner_Center ${env.selectDate} ${env.usageDir}/AzureX"/> to <property name="command" value="${env.scriptsDir}/Partner_Center/CollectRates.sh ${env.scriptsDir}/Partner_Center ${env.selectDate} ${env.usageDir}/AzureY"/> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  8. Click Save.

Configuring the Partner Center Retail Rates Collection

Before You Begin

The collection.properties file must be created and populated according to the steps in Configuring the Collector Properties.

Creating the New Collection

The collections against the Partner Center API will be done sequentially so the Spring Batch XML will be edited directly to create a new collection to execute after those that already exist.

  1. Click Data > Processing > Advanced Job Maintenance.
  2. Expand Production Jobs and click Partner_Center_CollectRetailRates.
  3. Copy lines 13 through 32.
  4. Paste them after the last </batch:step> line.
  5. Set the copied <batch: step id="collectX"> to <batch:step id="collectY"> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  6. Set the preceding <batch: step id="collectX"> to <batch: step id="collectX" next="collectY"> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  7. Set the copied <property name="command" value="${env.scriptsDir}/Partner_Center/CollectRetailRates.sh ${env.scriptsDir}/Partner_Center ${env.selectDate} ${env.usageDir}/AzureX"/> to <property name="command" value="${env.scriptsDir}/Partner_Center/CollectRetailRates.sh ${env.scriptsDir}/Partner_Center ${env.selectDate} ${env.usageDir}/AzureY"/> where X corresponds to the existing region (e.g., NZL) and Y corresponds to the new region (e.g., US).
  8. Click Save.

Configuring the Partner Center Workbook

Before You Begin

The Spring Batch XML jobs should be configured for the new endpoint per the Configuring the Partner Center Usage Collection, Configuring the Partner Center Rates Collection, and Configuring the Partner Center Retail Rates Collection sections.

Adding the New Collection

  1. Click Data > Workbooks.
  2. Select the _Partner_Center Workbook.
  3. Click Collections > List.
  4. Select the PartnerRates_X where X is the existing region (e.g., NZL) collection and click Copy.
  5. Set the name to PartnerRates_Y where Y corresponds to the new region (e.g., US).
  6. Click the notepad icon for the Data Source.
  7. Set the name to Partner_Center_Rates_Y where Y corresponds to the new region (e.g., US).
  8. Enter the information in the text fields as follows:
  • File Name: ${env.usageDir}/AzureY/rates/${env.selectDate}.csv where Y corresponds to the new region (e.g., US).
  1. Click Apply.

It may display an error reading "Fetching sample data failed".  This is expected so just click Yes.

  1. Click Finish.
  2. Right-click the PartnerRatesX Sheet where X is the existing region (e.g., NZL) and select Copy Sheet.
  3. Name the new Sheet PartnerRatesY where Y is the new region (e.g., US).
  4. Double-click the Import Collections step in the PartnerRatesY Sheet where Y is the new region (e.g., US).
  5. Delete the existing collection and add the newly-created collection to Collections.
  6. Click OK.
  7. Double-click the Create Meter ID to Partner Rate Lookup Step.
  8. Change the Lookup Name to have the new region appended (e.g., US).
  9. Click OK.
  10. Click Collections > List.
  11. Select the RetailRates_X where X is the existing region (e.g., NZL) collection and click Copy.
  12. Set the name to RetailRates_Y where Y corresponds to the new region (e.g., US).
  13. Click the notepad icon for the Data Source.
  14. Set the name to Partner_Center_RetailRates_Y where Y corresponds to the new region (e.g., US).
  15. Enter the information in the text fields as follows:
  • File Name: ${env.usageDir}/AzureY/retailRates/${env.selectDate}.csv where Y corresponds to the new region (e.g., US).

  1. Click Apply.

It may display an error reading "Fetching sample data failed".  This is expected so just click Yes.

  1. Click Finish.
  2. Right-click the RetailRatesX Sheet where X is the existing region (e.g., NZL) and select Copy Sheet.
  3. Name the new Sheet RetailRatesY where Y is the new region (e.g., US).
  4. Double-click the Import Collections step in the RetailRatesY Sheet where Y is the new region (e.g., US).
  5. Delete the existing collection and add the newly-created collection to Collections.
  6. Click OK.
  7. Double-click the Create Meter ID to Retail Rate Lookup Step.
  8. Change the Lookup Name to have the new region appended (e.g., US).
  9. Click OK.
  10. Click Collections > List.
  11. Select the Usage_X where X is the existing region (e.g., NZL) collection and click Copy.
  12. Set the name to Usage_Y where Y corresponds to the new region (e.g., US).
  13. Click the notepad icon for the Data Source.
  14. Set the name to Partner_Center_Usage_Y where Y corresponds to the new region (e.g., US).
  15. Enter the information in the text fields as follows:
  • File Name: ${env.usageDir}/AzureY/usage/${env.selectDate}_assemble.csv where Y corresponds to the new region (e.g., US).
  • Command: ${env.scriptsDir}/Partner_Center/assemble_partner_center_usage.sh ${env.scriptsDir}/Partner_Center ${env.usageDir}/AzureY/usage ${env.selectDate} where Y corresponds to the new region (e.g., US).

  1. Click Apply.

It may display an error reading "Fetching sample data failed".  This is expected so just click Yes.

  1. Click Finish.
  2. Right-click the UsageX Sheet where X is the existing region (e.g., NZL) and select Copy Sheet.
  3. Name the new Sheet UsageY where Y is the new region (e.g., US).
  4. Double-click the Import Collections step in the UsageY Sheet where Y is the new region (e.g., US).
  5. Delete the existing collection and add the newly-created collection to Collections.
  6. Click OK.
  7. Expand the Lookup Today Rates Step.
  8. Double-click the first SetDimensionFromLookup Processor.
  9. Set the Lookup name to the newly-named Lookup File in Step 17.
  10. Click OK.
  11. Double-click the second SetDimensionFromLookup Processor.
  12. Set the Lookup name to the newly-named Lookup File in Step 33.
  13. Click OK.
  14. Select the Merge Sheet and drag it to the far right.

This is done as the Sheets are order-dependent, which means any datasets that need importing must be ahead of the Merge Sheet.

  1. Double-click the Import Datasets Step.
  2. Select the UsageX Sheet in Datasets, where X represents the new region (e.g., US).
  3. Click OK.
  4. Click Save.

Configuring the Partner Center Schedule

Before You Begin

The Workbook Collections should be configured for the new endpoint per the Configuring the Partner Center Workbook section.

Adding the New Collection

  1. Click Data > Processing > Scheduling.
  2. Double-click the _Partner_Center (Daily) Schedule.
  3. Check the boxes next to the Collections created in Steps 10, 26, and 42 of Configuring the Partner Center Workbook in Workbook Components - Collections.
  4. Check the boxes next to the Sheets created in Steps 12, 28, and 44 of Configuring the Partner Center Workbook in Workbook Components - Flows.
  5. Click OK.
Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP