This is a simple CLI to export from the TWS database all job stream definitions in a text report. The entries in the file are separated by the character "|", that allows the import in a spreadsheet for later manipulation. The file is split in two parts. After you download both files you need to put them in the same directory in order to uncompress (you can use any tool that supports rar archives). After unzipping, you must edit the file TWSConn.properties in the directory TWSCLI\config to insert your connection properties (hostname, port, user, password).
jmatlock 270000DVMH Tags:  srm report ccmdb birt analytics tamit control_desk cognos 8,450 Views
As you may be aware, there are some exciting changes in store for the next release of our IBM Service Management software to be called SmartCloud Control Desk. This product will be the next evolution of IBM Tivoli® Service Request Manager®, IBM Tivoli Change and Configuration Management Database, IBM Tivoli Asset Management for IT, and IBM Tivoli Service Manager Quick Install. If you're attending Pulse, you'll hear a lot more about the changes and you'll also hear more from IBM in the coming days.
For this blog post, we're asking for your help in understanding how your organization is implementing reporting and analytics in your IBM Tivoli® Service Request Manager®, IBM Tivoli Change and Configuration Management Database, and IBM Tivoli Asset Management for IT installed environments. Additionally, we're interested in knowing whether you would benefit from a Tivoli User Group that would be focused on report and analytics development.
So, enter your email address in the comments section of this blog if:
alucches 2700012QJC Tags:  cognos data bilog analysis maximo birt v7 adhoc compare report ibmeam 5,163 Views
Pam Denny wrote an interesting blog post in the Asset Management blog about the Tivoli process automation engine 7.x reporting tools. Her post compares BIRT and Cognos for two of their reporting components, which are Operational and Ad Hoc Reporting. For more information, see her post.
alucches 2700012QJC Tags:  data ros v7 collection hoc bilog report qbr ad configure ld 5,863 Views
Over on the Asset Management blog, Pam Denny wrote a helpful post about how to include long descriptions in ad hoc reports.
PamDenny 270000BXV7 Tags:  analysis report v7 bilog data ibmpa translation localization bi 5,961 Views
When disasters like the massive earthquake earlier this year
in Japan, or the deadly earthquake
that hit Haiti
in 2010, people and organizations from all over the world work together to help
and rebuild these devastated areas.
I am very lucky to have the opportunity to help locally by rebuilding houses for people in need thru Habitat thru Humanity. Recently, I worked with an amazing team of individuals, including Power Company Employees, a school teacher, housewife, retired architect, and high school teenagers, in rebuilding a property that will soon house 10 families. Although our knowledge of sister joists and smart squares was minimal, with some explanations we were all quickly on the path of using our universal knowledge of crowbars, hammers and nails.
So how does rebuiliding tie into today’s BiLog entry on localization? Some icons like hammers and nails speak a universal language. Similar universal icons exist in Version 7 to communicate functionality, like the save, edit, delete and print icons. The functionality enabled thru these icons does not have to be explained in words – their images symbolize their functionality.
However, other items must be explained in a language the user understands. Whether it is breaking down the concept of a sister joist to a to a group on non-tradesmen, or detailing the description of an asset or ticket in the language of the user – we often need to enable text in localized languages in V7 and in V7 reports.
V7 reporting has unique requirements, as there are four very different components which must be enabled for localized text values. These include
1. Report Description displayed in Maximo Session
2. Report Request Page displayed in Maximo Session
3. Report Titles/Labels displayed in the Report
4. Report Data displayed in the Report
Each one of these four components is enabled for
localization in a unique way. Whether it
is it thru the corresponding L_Database tables, or thru the use of unique
scripting code within the report design file, the applicable report
description, parameters, titles, labels and data can all display within the
user’s specified language. You can find
information on how each of these components is enabled here.
To enable localization, there are a few key setup steps which you must enable if you have a multiple language environment which are detailed here
And finally, if you have created
custom reports, information on how you can enable them for localization is
This report localization information can also be found in the Report Localization Reference Guide, which contains more details and screenshots, along with detailed sample use cases explaining how you can enable custom report localization. This is listed, along with other report reference guides on this V7 wiki site.
Please comment back if you have any feedback on this, or other topics you’d like to hear about. Thank you!
Choices. Every aspect of our lives is packed with them. Firefox, Chrome, Safari or IE? Small, Medium, Large or Jumbo? Mouse or touchpad? Apple pie – with or without ice cream? Shoes, Sneakers or flip flops? To tweet or not to tweet?
Keeping with that trend, we are now enabling you additional choices for your development of V7 reports with the delivery of Portrait Report Templates.
Report Templates are one of a few different ways your report developers can create custom reports in the Version 7 Report Design Tool. Other ways include modifying the delivered reports, or exporting an ad hoc report from the Maximo applications.
When you use the report templates as a starting point for your custom report designs, they already contain for you the required library files and data source to enable the integration between Maximo and reporting. The templates are available in a variety of graph types, and include listing and detail report formats.
Currently, the V7 product delivers landscape templates so the maximum number of fields can be displayed on a report. However, to enable you additional choices and increasing flexibility to meet your unique business needs, you can now download a set of portrait report templates from IBM’s ISM Library. You can download these templates here or by accessing its shortened url at http://bit.ly/iwBvoc
Enabling the new portrait report templates is straightforward. Simply extract the zip file located in the ISM library to the Maximo report directory of your report developer. Then, open the BIRT Report Designer, and select New Report. You will then see an updated listing of templates, including both the previous Landscape and New Portrait Templates. The Portrait templates are identified with the text Portrait in their title, like 'Tivoli Maximo Portrait Subreport Template'.
Your selection of a landscape versus portrait report template impacts the amount of page area available to you horizontally. Landscape reports enable 10” of field space horizontally versus 7.5” of field space with letter size paper.
You can view additional details and on report page size and orientation on this wiki page or by accessing its shortened url at http://ibm.co/ms8QtD. Additionally, information is also in this V7 Report Page reference document here . This document additionally details how you can change all or a subset of your existing reports to use portrait orientation by either modifying the System Library File or the Master Page.
New features in V7 reporting continually enable you additional
report choices……but for your apple pie selection...we would suggest yes...with a scoop of cold, vanilla ice cream!
PamDenny 270000BXV7 Tags:  ros ad maxrelationships v7 analysis data report ibmpa hoc qbr 6,184 Views
As the building blocks to Version 7’s Ad hoc reporting tool, QBR (Query Based Reporting), Report Object Structures (ROS) enable you to select fields from multiple categories (objects) for your ad hoc reports. Additionally, ROS enable you to visualize application categories and their parent/child relationships. These categories are displayed via a category tree drilldown in the Select Tab of the QBR window in the top left hand side.
Depending on the products you are licensed for, you will receive over 20 ROS out of the box. These ROS enable you an excellent starting point. However, due to your unique data analysis requirements, you may need to modify the ROS or create new ones. You may want to add or remove child objects, create new ROS for specific security groups, or create new ROS reflecting your unique Industry Solutions.
As you go thru the process of creating or modifying ROS, a key item you will work with are maxrelationships. Maxrelationships are sql statements which join the parent to the child (also known as source) object within the ROS. Within the Object Structure application, a lookup is available to help you select the correct maxrelationship – but often multiple relationships are displayed. How do you know which relationship to choose, and what do you do if you don’t find the correct relationship available?
Below is a listing of a number of key items for you to consider when selecting the maxrelationship to be used for your ROS:
1. Make sure the individual creating and modifying the ROS is very familiar with the V7x database and database concepts. Without this knowledge, the ROS can be setup incorrectly, leading to bad or misleading data in the Ad Hoc reports.
2. For more information on relationships between objects, review the V7 Entity Relationship Diagrams located here.
3. Child Objects must be joined to their parents with relationships where the database sql is defined in its maxrelationship. If a relationship exists between the parent and the child – but the database sql is null - that relationship can not be used in a ROS as it will give invalid results.
4. You may find it useful to create your own unique maxrelationships to be used in the ROS. This can help you better manage and understand the relationships used in your QBR reports. You can create these unique report relationships in the Database Configuration application.
5. If you create unique maxrelationships for ROS, make sure to take into consideration the following items which are not supported for use in ROS
A. Replacement variables such as :&username&
B. Dates in bind variables, like …. and workdate between :startdate and :enddate
C. Restrictions in utilizing maxrelationships with subqueries, which are (1) users can only create detail QBR reports and (2) these relationships can not be created at the grandchild level.
For more details on modifying and creating ROS, download the V7 or V75 QBR Ad hoc reporting guide. To access this document, click here for the QBR Report wiki page, or the overall Report User Reference Document Page here.
PamDenny 270000BXV7 Tags:  ad bilog qbr v7 report ros ibmpa hoc data cardinality analysis 5,577 Views
This BiLog entry discusses
the key items to consider when defining maxrelationships in your ROS.
One of its major components is
cardinality, which is used to define the type of the database relationship. In the case of reporting, there are two types: One-to-one (1:1) or single relationships, or One-to-many (1:N) or Multiple Relationships.
To highlight the differences in cardinality, let’s use an example from the Purchase Requisition application.
The relationship between a Purchase Requisition and a Company is a single relationship, as only a single Company can be associated to a single PR.
However, the relationship between a Purchase Requisition and Purchase Requisition Lines is a multiple relationship, because for each PR (single) there can be multiple PR Line records (multiple).
When creating or modifying Report Object Structures (ROS) for your QBR reports, you will need to evaluate and define the cardinality of the relationship as either single, multiple or undefined. If you use the values of undefined or multiple, the relationship will be treated as a 1:N relationship.
So why is cardinality so important to the ROS definition? As your users begin adding fields to their own QBR reports, the relationships of those fields are evaluated to determine if they are single or multiple relationships. Depending on whether your user has selected a Summary or Detail Style report, will determine if they can add their selected fields.
For summary reports
- You can select any number of 1:1 relationships
- You can select only one 1:N relationship
For detail reports
- You can select any number of 1:1 relationships
- You can select any number of 1:N relationship
To enable maximum ‘cardinality’ flexibility in QBR Report
creation, you may want to recommend your users select the Detail Report Styles.
You can find more details on cardinality in the Version 7 QBR Ad Hoc Reporting Guides in the section titled 'Understanding Database Joins and Cardinality'. To access this document, click here for the QBR Report Wiki Page or here for the Report User Reference Material Page.
PamDenny 270000BXV7 Tags:  analysis ad hoc custom qbr data utilization ibmpa report bilog upgrade 6,779 Views
How many custom reports do you have? Do you have 25, 50 – or is your number in the range of 100 to 250 custom reports? Or are you in the category where you don’t know how many custom reports you have because your users are creating their own uncontrolled reports in tools like Microsoft Access or Microsoft Excel?
The topic of custom reports leads to a myriad of questions including –
- Is each custom report utilized?
- What determines if a custom report is approved, and then developed?
- Should super users be given database and report development access?
- What mechanisms are in place to insure that correct data is being returned in the custom reports?
- How much do custom reports cost -- in terms of design, development, test, administration, maintenance dollars and resources?
As John Heywood told us back in the 16th century that ‘Rome was not built in one day’. … my thoughts in the 21st century are that we can’t answer all those questions in today’s BiLog. However, we can start a plan to give you ideas on how you can reduce your number of custom reports.
One of the first and directly actionable means to reduce your custom reports is to begin using V7’s Ad Hoc Reporting feature, QBR. By using QBR within any V7 application, you and/or your users can quickly create reports that can include complex where clauses, filters, sorting, grouping, and parameters.
QBR functionality enables key features including -
· - Enabling users to quickly create their own reports for their unique business needs
· - Does not require technical, development skills, like Java, or database knowledge to create the report
· - Does not consume development hours in creating and maintaining large numbers of unique reports, which may only be used by a very small number of users
The cornerstone of QBR functionality are Report Object Structures, ROS. ROS enable users to select fields from multiple categories (objects) for their ad hoc reports. ROS are designed to enable users to quickly visualize their hierarchies and parent/child relationships. They are created in the Object Structure application of V7, and in the next BiLog, we’ll discuss their key attributes and how to extend them.
Do you have questions on the future reporting direction of Maximo? Have you heard about V7RI for Maximo 6 but don't know what it is? Are you having problems locating the listing of delivered reports in the Version 7 releases? Is it true you can edit a QBR report in the 7.5 releases?
To get these and other Maximo reporting questions answered, please join Pam Denny on Tuesday, September 20th at 10am EST for 90 minutes of a live, interactive session on Maximo reporting.
For more information, see Pam's post on the Asset Management blog.
alucches 2700012QJC Tags:  qbr asset-management eam v7 data report bi maximo analysis ibmeam 4,893 Views
In a new entry in the Asset Management blog, Pam Denny discusses the 80/20 rule of reports: 80% of your report processing is done by only 20% of your reports. To maximize performance, you want to identify those 20% of reports with the longest execution times, and then ensure they are maximized for performance efficiency. One way to do this is to schedule these reports to only be run during off-peak hours. For more information, see the original blog entry.