Applies to: Datalink (Classic) 4.8.24 and later, with TBM Studio 12.8.3 or later
NOTES:
Requirements
For this process to work, the following conditions are required:
- Cloudability Datalink (Classic) 4.8.24 and higher, updated to Engine 13041 or later, on TBM Studio 12.8.3 or later
- Your Cloudability environment must be in Main behind Frontdoor
ATUM support: ATUM 3.0 (or the most current version of ATUM) is supported by default. Versions 2.0 and 2.1 can be configured. (You need to file a Support ticket.) ATUM 1.0 is not supported.
About the connector
Apptio's Datalink (Classic) Cloudability connector imports monthly Cloudability-sourced cost data into the Cost Transparency (CT), Bill of IT, and Hybrid Business Management (HBM) applications in order to incorporate that Cloudability data into the cost of specific IT services in Apptio reports. The connector and ingest data from AWS, Azure, and GCP. All Cloudability users need to exclusively use the Cloudability connector moving forward. The Cloudabilty data replaces the raw provider bills.
The Cloudability integration process involves two steps:
- The first step is to set up the Datalink (Classic) Cloudability connector using the instructions in this article.
- The second step is to complete the integration setup by following the instructions in Integrate Cloudability cost data into TBM Studio.
The Datalink (Classic) Cloudability connector will not work without this second step.
IMPORTANT: For this integration process to work, your Cloudabiity environment must be in Frontdoor in the same Frontdoor environment as the Apptio apps that are being integrated with Cloudabilty. If your Cloudability environment isn't in Frontdoor, submit a request for that migration, then proceed with this integration process.
Prerequisite - Request integration
Before Cloudability data can be combined with the cost data in CT, Bill of IT, and HBM, ask your Apptio support rep (CSM/TAM) to submit a request for integration. This information is required to create a data channel for each of your Cloudability environments to the Apptio preprocessor before the Datalink (Classic) Cloudability connector can work.
- Provide your Apptio CSM/CS contact the following information:
- Environment to be integrated – name and URL of the specific environment that needs to be integrated.
NOTE: If you use multiple Cloudability environments, submit a separate Salesforce ticket for each environment.
- Historical data – If you need more than the current month of data, what specific months and years are needed.
TIP: Cloudability loads data daily (at 10 a.m.) starting with the first day of the calendar month. For example, on May 8, the data available is from May 1-8 only. The available data aggregates daily until the end of the month. Beginning with the first day of the next month (in this example, June), the data will be limited to the current month (June) and no longer include data from the previous month (May).
- List of requested columns (optional) – Provide a list of fields that neeyou want to import from Cloudability to CT. The fields can include business mappings, tag mappings, account groupings, business metrics, and Account ID/Account Name. Provide the exact name from Cloudability.
IMPORTANT: The following table lists the billing fields that are imported by default. Other billing fields, such as Resource ID and Item Description, are excluded and cannot be requested.
| Attributes |
Measures |
| Platform |
Usage Qty |
| Provider ("AWS", "Azure", "GCP") |
Normalized Usage Quantity |
| AvailabilityZone |
On-Demand Cost |
| Region |
Provider Unblended Cost |
| Unit (ATUM Mapping) |
Provider Blended Cost |
| Currency Code |
AdjustedAmortizedCost |
| Location |
AdjustedCost |
| OS |
AmortizedCostAdjustment |
| Product |
CostAdjustment |
| Product Code |
GrossCost |
| Instance Type |
NormalizedAmortizedCost |
| Tower (ATUM Mapping) |
OnDemandUsageHours |
| Sub-Tower (ATUM Mapping) |
UsageHours |
| Service Type (ATUM Mapping) |
NormalizedUsageAmount |
| Service Category (ATUM Mapping) |
|
| Service Name (ATUM Mapping) |
|
- When you are notified by Apptio that the integration process is complete, proceed with the following connector configuration.
Configure the connector
Use the following steps to define the connector. This procedure won't work until you complete the "Prerequisite - Request an integration" section.
IMPORTANT: The minimum requirements for this procedure are Datalink (Classic) 4.8.24 with Engine 13041.
- Log in to Apptio Datalink (Classic).
- Click the Manager tab to open the Datalink (Classic) Agents page.
- Click Default Agent.
NOTE: Apptio recommends using the default agent when creating connectors for cloud-based services to avoid additional network configuration that may be required when attempting to connect to external services from an on-premises agent.
- In the Connectors page, click New Connector.
- In the Applications panel, click the Cloudability icon.
- In the New Connector page, enter a Connector Name.
- In Time Period, select the timing of the upload to the Apptio Destination that you will define in the next step. If you don't want to use historical data, keep the default of Previous Month.
- If you select Previous Month, it is recommended that you repeat these steps to create a second connector for Current Month.
- If you choose to ingest historical data, you must repeat this entire process for each of the historical months you want to ingest. When you repeat the process, you must ensure that the two Time Period fields match.
- Under Apptio Destination, complete the following fields:
- Apptio Version - Select R12 with Frontdoor only.
- Apptio Instance - Select the URL that you use on the Apptio home page to open the application that you're integrating with Cloudability.
- Domain - This field is autofilled with the name of the destination Apptio instance. No action is needed.
- Project - Select the destination project.
-
Source System - Leave this field blank.
-
Time Period - This field should match the previous Time Period field.
NOTE: The Offset from Current Month option loads to a period that is offset from the source month. A positive offset indicates the number of future periods, and a negative offset indicates the number of past periods.
- Disable Logins - This checkbox is selected by default. No action is needed.
-
Advanced Options - Expand this option and set the Category to Cloud Service Provider.
Configure connector email notifications
After you configure email notifications for your Datalink (Classic) Agent (seeConfigure agent email notifications), you can configure email notifications for each connector. You can specify that an email notification be sent when a connector succeeds or fails. Click Notify or Notify & Archive in the left menu to jump to the email configuration settings; otherwise, scroll down to the Notify or Notify & Archive section.
- Select your email preferences:
- Send an email notification when this connector succeeds.
- Send an email notification when this connector fails.
- In the To box, enter one or more email addresses, separated by a comma or semicolon. Enter a subject in the Subject box.
Schedule the connector
- Schedule the connector to run at specific times.
- To set up and enable the schedule:
- After you set up the connector, from the connector, click Schedule on the left menu.
- Select Enable Schedule.
- Enter your schedule options:
- Frequency sets the schedule options.
- Run dates are in your selected time zone and, upon save, are displayed in the Next Run column in the connector list. If you do not select a time zone, UTC is used.
Finish and run the connector
- Click Test in the upper-right corner to test the connector. Errors will be flagged in a dialog so you can then jump directly to the part of the connector definition that needs attention.
- When you are finished, close the dialog, then click Save.
- On the Connectors page, search for "cloudability." In the results, find the connector instance that you created, then click Actions > Run Now.
Under Status, you will see file names and the status as the connection progresses.
- When the Status column says “Success” the connection is ready. Proceed with the next step to complete the integration.
NOTE: If you choose to ingest historical data, you must repeat this entire process for each of the historical months you want to ingest. Also, if you selected Previous Month, it is recommended to repeat this process to create a second connector for Current Month.
Complete the integration
IMPORTANT: To complete the integration of Cloudability data, additional setup is required. See Cloudability cost data integration into TBM Studio.