Share This:

Are you migrating to Control-M 9.0.18 and want to ensure your previous version job reports work properly in the new release?

 

Learn more about the new Control-M Reports tool which replaces the previously released Reporting Facility in Control-M.  The new Reports tool contains many enhancements and capabilities.

 

This webinar will cover:

 

•    The new architecture of Control-M Reports

•    The requirements to run it successfully in your environment

•    The process to identify your current jobs that execute Reporting Facility reports

•    How to convert previous jobs to the Control-M Report format

•    How to automate Reporting tool jobs using the Control-M Automation API.

 

In this webinar Irwing Sanchez will explain and demonstrate the above.

 

This is the link on YouTube for the recorded session:

 

Connect With Control-M: Migrating Reports to Control-M 9.0.18 - YouTube

 

Here is the Q&A for this webinar (Connect With Control-M: Migrating Reports to Control-M 9.0.18)

 

________________________________________________________________

 

Q: Can we migrate reports from v8?

A: Yes the conversion tools supports V8.

________________________________________________________________

 

Q: Is it true that you need the Java Developers Kit installed to use the Automation API?

A: No, the AAPI and Automation CLI do not need Java installed.

________________________________________________________________

 

Q: Does the ctm-cli have to be installed on your client machine?

A: No it doesn't need to.

________________________________________________________________

 

Q: Do the migration utilities will migrate reporting jobs using report templates?

A: Reports are not migrated with the migration toolkit.

________________________________________________________________

 

Q: Does the analyzer utility have to be run on any EM client machine or from a centralized location?

A: On the EM Server, so a centralized location.

________________________________________________________________

 

Q: Do you run the analyzer from the EM server or client?

A: EM Server

________________________________________________________________

 

Q: Is Automation API included with EM or do we need a different license for it?

A: It is part and licensed with the Enterprise Manager Server.

________________________________________________________________

 

Q: What are the available output formats for the Reports?

A: CSV and PDF are supported.

________________________________________________________________

 

Q: Does the agent where you have Automation API have to be on the same machine where the EM server is running or where the EM client is running?

A: It does not, the Automation CLI can be installed and run from any machine that can reach the EM endpoint.

________________________________________________________________

 

Q: Is there a limit to how many characters can be in a report name?

A: 128 is maximum length and 4000 for the description.

________________________________________________________________

 

Q: When I import a report template, is it available to other users in my environment?

A: Imported reports are specific to the user that imported them.

________________________________________________________________

 

Q: The Peak usage report used to have a summary at the bottom with total jobs scheduled for the month and total executions for the month... is that still part of the report?

A: It doesn't at the moment, feel free to open a case to discuss.

________________________________________________________________

 

Q: Are there other format other than jason?

A: For the definition only JSON is supported.

________________________________________________________________

 

Q: Does 9.0.18 need any additional license?

A: Licensing does not change between versions. Licensing specific questions should be directed to your account team.

________________________________________________________________

 

Q: When importing the converted reports, can you import multiple reports at once? Or do you have to do them one-by-one?

A: I should be done one-by-one.

________________________________________________________________

 

Q: If we don't want to install the automation API as part of our 9.0.18 upgrade project is there an executable we can call to generate the reports?

A: The Automation CLI doesn't have to be installed to run reports, the Client application can be used. Alternatively rest calls can be made to the EM Server to get the report. The Automation CLI does provide a means to make rest calls from the command line.

________________________________________________________________

 

Q: Is the automated API and add-on that has to be purchased or is it included when upgrading to v9?

A: The Automation API is included with Enterprise Manager from Control-M 9.

________________________________________________________________

 

Q: Is the Automation API installed automatically with agent 9.0.18? If it isn't, can it be "deployed" via CCM, like other plugins?

A: The Automation API is part of the EM installation. The Automation CLI is separate installation that is a Node JS application. This would be installed on the Agent but there is no deployment for this.

________________________________________________________________

 

Q: Is there a reporting facility template in planning domain to create reporting jobs?

A: When running with the Automation CLI and OS type job can be used. There is no longer a dedicated job type.

________________________________________________________________

 

Q: Would you still have a "Reporting" job type that you could use to run the AAPI command?

A: Reporting jobs can now be run as an OS type job (in conjunction with the Automation CLI), also it's possible to build an Application Integrator job to build a job to make a direct REST call.

________________________________________________________________

 

Q: because of the volume of reports we have, I would prefer to upgrade WA & Control-M Server to .18 without upgrading reports.  Is it possible to continue to use Control-M reports V9 not 9.18 until we have time to transition to 9.18 reporting?

A: 9.0.18 can be run in Compatibility mode, when this is configured Clients and reporting run as Control-M 9.

________________________________________________________________

 

Q: Is there still the possibility to run/create AUDIT reports?  (Was it in the HISTORY tab)

A: Yes Audit reports can be created and run.

________________________________________________________________

 

Q: Can you access a newly created report in 9.0.18 via the following REST endpoint: https://emhost:8443/automation-api/reporting/report/{name} and what values are acceptable in the format query string?

A: Yes that the correct endpoint, you can use any means to make the rest call once authenticated. 

________________________________________________________________

 

Q: I see you can import reports into the EM, can you export them as well (to send them to other EM environments).

A: At the moment this isn't possible, feel free to open a case to discuss your needs.

________________________________________________________________

 

Q: We are currently in the process of upgrading from V8 to V9.0.500 then at some time going to 9.0.18.  Do I have to convert my current reports in v8 for the upgrade to v9.0.500?

A: The Upgrade tool should work with V8 reports.

________________________________________________________________

 

Q: Does Report Name support spaces?

A: Presently it does not support spaces.

________________________________________________________________

 

Q: Are the same output formats .csv, .xls supported?

A: CSV and PDF are supported.

________________________________________________________________

 

Q: We have not used reporting in the past so was just wondering how the reporting has changed from previous versions

A: The GUI is now web based and uses HTML 5. As such removes the need to manage database connections.

________________________________________________________________

 

Q: Are the reports stored locally on the EM? If so where?

A: They are temporarily stored within the EM webserver, the location to copy can be specified when making the rest call.

________________________________________________________________

 

Q: Does anything need to be done on the mainframe side in order to run reports from the EM.

A: Reports are run on the EM side, so there is nothing special to do with Mainframe Server installations.

________________________________________________________________

 

Q: Can version 8 reports be run in version 9 without converting?

A: Yes V8 reports can be converted.

________________________________________________________________

 

Q: What actually does the conversion utility do?

A: The conversion tool converts the old Crystal Reports templates to the new format so they can be used with Control-M 9.0.18

________________________________________________________________

 

Q: Is there any special license requirements for the new report interface?

A: No reporting is part of the Control-M EM installation and is licensed with this.

________________________________________________________________

 

Q: What about credential for connecting from CTM to the EM, need a special user and what privilege, what about the password?

A: An EM user can be created and used to run the reports. This is the account that was added with the AAPI environment option.

________________________________________________________________

 

Q: Does Control-M take care of old reports that where generated in the temp folder (D:\Program Files\BMC Software\Control-M EM 9.0.00\Default\emweb\reporting)?

A: Yes these are cleaned up according to a defined schedule.

________________________________________________________________

 

Q: Does EM Miner still work with 9.018?

A: EM Miner is not part of the Control-M release, please contact your account team for assistance with this.

________________________________________________________________

 

Q: Using AAPI, how can we pass arguments to the Report filters?

A: Report filter would be specified in the report definition. The AAPI allow the report to be retrieved.

________________________________________________________________

 

Q: How well will reports created in 7 convert over?

A: If reports can be run in Control-M 9 that can be converted. The first step will be to move them to Control-M 9.

________________________________________________________________

 

Q: Is control-M agent is mandatory to install to run the reporting host server?

A: No the reporting server is part of the EM installation, the Agent is used to create the rest call that that is used to run the report.

________________________________________________________________

 

Q: Every user that has a report defined in their client would have to go through this conversion process?

A: That's correct.

________________________________________________________________

 

Q: Are the reports stored in Temp?

A: Reports are stored on the EM webserver and cleaned up after the configured time.

________________________________________________________________

 

Q: Can the reports be written to a UNC location other than an EM server?

A: Yes provided that the user can access the location (write). 

________________________________________________________________

 

Q: Is it possible to only output the report to SYSOUT rather than a file? We use to look for specific text and email when found but not really looking to place report output in a file?

A: Reports are provided in file form, a Control-M for web services job could be used to get the file, we suggest opening a case to discuss.

________________________________________________________________

 

Q: Can version 9.0.18 be used to run reports from self-service post report conversion. I assume so as this should be no difference to a normal flow (i.e. non self-service)?

A: Yes 9.0.18 reporting can run Self-Service reports.

________________________________________________________________