 |
Consumption Analytics Documentation |
|
Consumption Analytics Documentation |
This section contains the cumulative release notes for Cloud Cruiser version 4.1.x. The current release is version 4.1.3.
All documentation articles updated for this release have the tag version_4.1. List these articles.
The following features are new or enhanced in Cloud Cruiser version 4.1.3.
The user interface for scheduling the running of ETL collections, ETL flows, and XML jobs is now easier to use. It also enables you to schedule multiple components to run sequentially and to easily view a list of completed runs for each schedule.
The Scheduling page is in the same location as before: Data > Processing > Scheduling.
Oracle version 11g and later is now supported as the database server for Cloud Cruiser 4. Oracle was already supported on version 3. Complete system requirements for version 4.1 are in the section System requirements.
You can now create an effective date range for a rate plan that includes an end date as well as a start date. This allows you to give special rates to a set of customers for a limited time, after which they revert to the Default rate plan.
Versions 4.1.0 to 4.1.2 included two collectors for Microsoft Azure, one that collected by logging into the Azure Enterprise Portal as a user and a newer one that collected via the Azure API. In November 2014 Microsoft made changes to the Azure Enterprise Portal that prevent the older collector from working.
Because the API-based collector can more reliably collect recent data from Azure, HPE will no longer maintain the older collector. Version 4.1.3 includes only the API-based Microsoft Azure collector.
The following features are new or enhanced in Cloud Cruiser version 4.1.1.
With this release, the Microsoft Windows Azure Pack Collector is available in Cloud Cruiser 4. A WAP_Template ETL workbook template with the required collections and flows is also included.
In version 4.1.1, the following enhancements are made to collection from HP Cloud Service Automation (CSA):
The following features are new or enhanced in Cloud Cruiser version 4.1.0.
REST API methods that had been missing in version 4.0.x, the first release of v2 of the API, are now available. The API now covers all functionality that was available in Cloud Cruiser 3.
For information about the API or a particular method, see REST API reference.
You can now collect numbers that are formatted in a locale other than the United States or in specialized formats such as scientific notation. For example, a number that uses periods for grouping and a comma for the decimal point such as 1.234.567,89.
For instructions, see the documentation for the Format column in Output fields for a collection.
When specifying an input dimension formula, which constructs a string from a dimension value for use as a source value in certain transformation processors, you can now use a regular expression pattern to capture part of the dimension value.
For information on input formulas, see Input dimension formulas in transformation processors.
Some product terms and the names of batch XML objects are different in Cloud Cruiser 4 than they were in Cloud Cruiser 3. See the following articles for details:
The following important bugs are open in the Cloud Cruiser 4.1 release:
| Description | Bug ID |
| When a Standard Invoice report contains a discount or surcharge, that line includes a drill-down link. This link should not appear because there is no usage information into which to drill down for a discount or surcharge, and the link returns error messages. | 4627 |
| The Cloud Cruiser service has a default Log On As setting of local service. If you change this setting and then upgrade Cloud Cruiser, the Log On As setting reverts to its default setting. To work around this issue, change the Log On As setting after upgrading Cloud Cruiser. | 3541 |
The following bugs were fixed in the Cloud Cruiser 4.1.3 release:
| Description | Bug ID |
|---|---|
Some ETL workbooks became corrupted and would not open, instead displaying the error message Unable to obtain sheet data from the server. Error reading session data sample. This was due to a problem with managing multiple data samples. Though you could not edit such a workbook, any scheduled runs of its collections or flows worked correctly. | 4810 |
Manually running the Default Charge Job for a range of dates in the Advanced Job Maintenance window sometimes failed to charge some usage. The job run results for some of the dates in the range would include the message No rate or fixed price defined for service '<serviceName>' in rate plan '<ratePlanName>'. | 5013 |
| The Microsoft Azure collector stopped working in November 2014. This was due to changes Microsoft made to the Azure Enterprise Portal website, and did not affect the Microsoft Azure (API) collector. Now Cloud Cruiser includes only the API-based collector. | 5051 |
| When the Default Charge Job processed a recurring transaction, it failed with a null pointer exception. | Support ticket 1433 |
When you processed a transaction for a service that has no rates in the customer's rate plan, and the configuration option Use Default Rate Plan If Missing Rate is enabled, the Default rate plan was not used. Instead the Default Charge Job failed with the message Unable to calculate transaction charge for service 'test' having no service rate defined. | 5076 (Support ticket 1434) |
| When you added one or more levels at the top of your account structure, user groups with Customers Allowed set to All were not able to see data for customers or accounts at the new levels. | 4905 |
| When working in an ETL workbook that has an Amazon Web Services collection that retrieves a large dataset, capturing a new set of sample data caused your browser to freeze. This is because the collection ignored the Data Sample Limit you set, instead capturing all possible data for the workbook's select date. | 5033 |
When importing services and rates together with ccimport, existing rates were updated without using the -u option. | 4866 |
| After reordering levels in your account structure, in some cases standard reports displayed account IDs rather than customer descriptions. | 5029 |
| There was no way to import custom descriptions for individual rates when importing rate plans or importing services and rates together. You can now specify such descriptions in a | 5019 |
In the What-If page, the Preview Invoice tab did not show an invoice for the selected model. It displayed the error message Invalid column name 'StateID'. | 4869 |
| The first time you viewed a customer in the Customers page, inactive and processed transactions were visible without clicking Show Inactive or Show Processed. | 5026 |
The following bugs were fixed in the Cloud Cruiser 4.1.2 release:
| Description | Bug ID |
|---|---|
The Default Charge Job sometimes failed with the message IllegalStateException, sometimes ran indefinitely, and sometimes did not run after publishing to a schema. | 4996, 5002 (Support tickets 1314, 1351) |
| After upgrading from version 4.0.x, the Dimensions by Measure and Service Measure Detail reports did not work. They failed with an error message about too many arguments being specified. | 4984 |
When an entry in the Charge table had a null rate, the Standard Invoice and Service Invoice Summary reports failed with the error message Error running report: Cannot format give Object as a Number. | 4994 |
When importing users with ccimport, setting the nativeUsers parameter to false had no effect. Users were imported as native. | 5003 |
| The template workbook for Microsoft Azure published services with a monthly charge interval, which caused issues when you ran a report against a single day. It now publishes them with a daily charge interval. | None |
| After upgrading from version 4.0.x, output fields in a collection that were specified as measures no longer appeared in CC Record output for the collection. The output fields were changed to dimensions and could not be reset to measures. | 5007 |
The following bugs were fixed in the Cloud Cruiser 4.1.1 release:
| Description | Bug ID |
|---|---|
| An hourly batch job would not run if the batch system had been running other jobs continuously since the previous run of the job. | 3078 |
| When a measure value contained more than 10 decimal places, a Publish Data step failed but also created a load in the database that did not appear in the Published Loads page. | 4754 |
| When a rate plan includes a minimum commitment for a service and a customer on that rate plan used none of that service for an accounting day, incorrect values were charged. | 4887 |
| Collections that use a command in their data source sometimes read from the wrong file in simulation mode. | 4765 |
| In an XML or JSON collection, when you set a resource qualifier on the root node, the qualifier appeared twice in the output for some child nodes. | 4929 |
| A flow could fail with an You now have more options with an Aggregate Rows step to control memory use. | 4734 |
| When editing a collection that uses a universal collector such as XML or CSV in the Advanced Configuration dialog box, clicking Reset to Default did not change all values back to their defaults. | 4807 |
| When you set a transformation processor's Process Exceptions option to No, exceptions were still processed. | 4832 |
| The Dimensions by Measures report grouped data incorrectly. | 4948 |
The following bugs were fixed in the Cloud Cruiser 4.1.0 release:
| Description | Bug ID |
|---|---|
| It was not possible to create a CSV collection that successfully collected from a source file that had a comment line before the header line. | 4756 |
| A transaction with an Amount Type of Units and a service for which the customer's rate plan includes a fixed rate would apply an incorrect charge. This combination now produces an error. You cannot combine a Units transaction with a fixed rate. | 4692 |
When a file-based data source used a wildcard character ? to enable multiple files to be read, some records were lost. | 4176 |
| When using the HP CSA Collector with CSA 4.1, the collector failed. This was due to a change in the CSA API. | 4637 |
| A CSV file with one or more empty values in the header row would not successfully upload when creating a collection. | 4646 |
| There was no way to create a collection that wrote multiple feeds (previously known as a sifting collection). | 4753 |
| You could not use a Run Script step as the first step in a flow. | 4862 |
| A record without any dimensions caused an exception, even in a data sample used for editing a workbook. These records are now allowed to appear in workbooks to give you the most visibility into your data when designing a collection. | 4689 |
| The XML Collector's Ignore Root option did not work. The automatically-created XPath mappings were incorrect and the collector did not observe the setting correctly when run. | 4755 |
| The Amazon Web Services (AWS) Collector did not account for the difference between UTC and the time zone of the Cloud Cruiser server, resulting in daily collections for a period that was offset by that number of hours. | 4642 |
| When a transaction failed to process because the customer's rate plan had no rate defined for the service in the transaction, no warning was written to the log. | 4664 |
| The reporting user did not have permission to a schema that was created from the Publish button in a data workbook. | 4767 |
| A HPE Consumption Analytics Portal user with a Viewer license did not have permission to view Insights modules (analytics reports). | 4768 |
| For the Import Collections step in a flow, the Max Files per Feed option defaulted to 1. This default tripped up users who did not intend to set a maximum, and it has been removed. | 4663 |
| Importing services, with or without rates, ran slowly. | 4820 |
When importing users, the default value for the nativeUsers option was false. This prevented the users from logging in. The default is now true. | 4613 |
| You could not display more than 2000 rows of sample data in a worksheet. | 4712 |
| In the Transactions tab for a customer, the Hide Processed button did not hide processed transactions, only inactive ones. | 4696 |
| In the Customers page, the Rate Plan filter for the customer list did not work correctly. | 4780 |
| When a user's computer could not reach a HPE Consumption Analytics Portal Server computer, the resulting error message was misleading. | 3595 |
The following are the minimum hardware and software requirements for Cloud Cruiser and its components.
HPE recommends that you install Cloud Cruiser, Cloud Cruiser Analytics Server, and your database server on separate computers. These system requirements apply to that architecture.
You should also install HPE Consumption Analytics Portal Desktop on this computer.
You must use the 64-bit version of one of the following operating systems:
The Server Core installation option of Windows is not supported. The Cloud Cruiser installer requires a graphical user interface and cannot be run within a command window.
The 64-bit version of Java Standard Edition 7 (JDK or JRE) is required. Version 8 is not supported.
You can download Java at http://www.java.com/getjava. The navigation of this site changes often, so you might need to look carefully to find version 7 in 64 bits.
A database server is not included with the Cloud Cruiser installation. You must provide one of the following database servers:
Oracle is not supported by Cloud Cruiser 4.0 and 4.1.
For hardware and operating system requirements for this computer, see the documentation for your database server. Storage needs will grow as Cloud Cruiser accumulates data over time.
One of the following browsers:
As of the last update to this article, Cloud Cruiser has been tested with Firefox 32 and Chrome 37, and we continue to test with new, automated version updates of these browsers. The application should continue to function with such versions. However, some issues could arise that can only be resolved with subsequent patches to Cloud Cruiser or by reverting the browser update.
The documentation for Cloud Cruiser 4.x is located at Cloud Cruiser 4. At product release time, very little documentation is available, and we are continuously adding to it to fully document the release. For those familiar with previous releases of Cloud Cruiser, we recommend taking a look at Name changes in Cloud Cruiser 4 to learn the new names for objects you have worked with before.
In addition to the documentation available on this site, version 4 has more help within the Cloud Cruiser Portal. This includes help for windows, dialogs, and the functions and parameters in Data > Workbooks.