Skip navigation
1 2 3 Previous Next

Control-M

181 posts
Share:|

Is SAP deployed at your company?  If yes, please join us to learn how Control-M for SAP 8 will help streamline processes and reduce complex interdependencies you face today when working with SAP. Control-M for SAP 8 introduces new features and enhancements, including temporary variants, which reduce the overhead in maintaining many copies of the same Variant in SAP systems, and jobtraces, which is really helpful for troubleshooting as it´s much easier to see when the API call is started and when that call is answered by SAP.

 

We invite you and your Control-M administrators to join us for this Connect with Control-M live webinar on Wednesday, June 29th, at which time Javier Núñez will demonstrate some of the new features and enhancement of Control-M for SAP 8. Javier will:

 

     •    Provide an overview of the Control Module for SAP 8 architecture

 

     •    Discuss and demonstrate some of the new functionality in Control-M for SAP 8 including:

 

              o    Temporary Variants

              o    Jobtraces

              o    XBP 3.0 certification

 

     •    Provide basic troubleshooting tips

 

Here is the Q&A for this webinar (Connect With Control-M: New Features in Control-M for SAP 8)

 

________________________________________________________________

Q: Can you disable the jobtrace log?

A: Yes, adding - article 000070316

_______________________________________________________________

Q: Do the jobtrace logs clean themselves up?

A: Yes, New Day cleans the trace logs just like the other logs

________________________________________________________________

Q: How can I verify my SAP server supports XBP3?    

A: Using SAP Transaction SE38 and using program XBP2, assistance of your SAP Admin might be needed

________________________________________________________________

Q: Where are the interception profiles stored?

A: They are stored in the SAP server

________________________________________________________________

Q: How do I download Control-M for SAP?

A: You can go to our EPD site and download CM for SAP there

________________________________________________________________

Q: Do I have to enable debug to get the SAP trace logs?

A: No, the SAP trace logs are created. You only need to add additional debugging if required.

________________________________________________________________

Q: For the job trace logs that you were showing, do I have to remove them manually, or does the Agent clean them up with the sysout is cleaned?

A: They are cleaned up automatically

________________________________________________________________

Q: How do I enable the XBP3 that you're talking about?

A: Your SAP admin can enable that on the SAP server and also turn on the XBP3

________________________________________________________________

Q: Is CM for SAP 8.0.00 is compatible with Control-M Agent V.7.0.00 ?

A: Yes it is. That is the lowest agent version that it is supported on.

________________________________________________________________

Q: Not able to download the document

A. You can open the docs through http://docs.bmc.com

________________________________________________________________

Share:|

Do you know the differences between using SMART and Regular Folders? Do you understand how to take advantage of SMART Folders?


If you’re not familiar with SMART folders, or you want to enhance your knowledge on this topic, we invite you to join us for this Connect with Control-M live webinar on Wednesday, July 27th, at which time Hugo Arguello will demonstrate functionality of SMART folders when scheduling jobs in Control-M. We will demonstrate:

 

Differences between SMART and Regular Folders

 

Rule Based Calendars (RBC)

 

•       In and Out conditions among SMART Folders

 

 

Don’t miss a live demo of these capabilities. There will be a Q&A after the demo. Register now!

Share:|

Did you ever wonder if Control-M could do something you didn't know if it could do? Have you ever wished you could meet the man behind the machine- or in this case, the developer behind the scheduler? This is your chance to learn, network and engage with BMC Executives and subject matter experts, as well as Control-M customers!

 

Join us September 6-9th in fabulous Las Vegas at BMC Engage! There will be 30+ Control-M sessions during the week including hands on labs. Collaborate with peers and share challenges, lessons learned and successes. Don’t miss out on this exciting and educational week! Register Today!

 

Workload automation continues to be the foundation technology powering business services and supporting an enterprise’s need to accelerate the delivery of new services. This topic highlights some of the major trends in the workload automation market, including the latest Control-M enhancements and how they support business-critical initiatives, such as agile application development and big data.

 

Here’s a glimpse at a few of the great Control-M sessions:

  • On Wednesday you won’t want to miss Zach Warren from Unum Group. Learn how one of the leading insurance companies is using BMC Control-M to empower business users and developers to deliver 24x7 self-service for workload submission—without increasing overhead for IT operations. Enabling a 24x7 batch operation with no additional overhead? Now, that is agile!

 

  • Join one of the many Big Data sessions and hear Hadoop experts and customers Darren Chinen from Malwarebytes, Todd Klessner from Navistar, and Andrew Taylor from British Sky Broadcasting share the story of their big data journey Thursday, September 8th. From the database to the data lake, from the developer to the business analyst, it’s all interconnected. If you haven’t worked on anything related to Big Data yet, it is likely you will soon.

 

  • September 8th, join Avner Waldman, BMC Product Developer, in a hands-on Lab featuring one of the latest Control-M innovations: Application Integrator. Application Integrator enables you to build job types and gain ease-of-use, visibility and manageability of Control-M for your applications. Specific hands-on activities will include:
    • Login to Application Integrator design wizard
    • Design a new job type that will include login, run a process, monitor its execution until completion, and implement abort operation
    • Deploy the new job type to their Enterprise Manager environment
    • Define 1-2 jobs and execute them

 

Don’t miss out! Look for more posts highlighting Control-M sessions at Engage.

Share:|

Are you running on the latest version of Control-M? If not, let us help you get there with our AMIGO program! It is available to all Control-M customers who are current on maintenance.

 

The AMIGO program is our Assisted MIGration Offering that allows you to upgrade your Control-M environment with a lot less effort on your part. Sounds nice right?480028_Use_AMIGO_to_Accelerate_your_Control-M_Upgrade_Featured_asset_image (2).png

 

The AMIGO program includes:

  • A question and answer session before you upgrade
  • Review of your upgrade plan with suggestions for simplification
  • A detailed, custom upgrade checklist
  • An “Upgrade Plan Steps” guide
  • A review of your upgrade plan by BMC Customer Support representatives
  • Helpful tips and tricks for upgrade success from previous customers
  • Follow-up by Customer Support to address questions and ensure success after upgrade

 

90% of Control-M customers that used AMIGO required no additional support during the upgrade. Of the customers that needed support, the issues were resolved 75% faster, compared to non-AMIGO users. Companies who have successfully implemented many upgrades may wonder why to bother with the effort of using the program? Based on high satisfaction scores of AMIGO customers, we believe participating in the program is worth the effort.

 

Don’t miss out on the added benefits of Control-M 9: Automatic Agent and Client Deployment, High Availability, Runtime Analytics, Automated application workflow promotion between environments and more!

 

Want to hear more? Read the AMIGO Upgrade whitepaper and see how easy it can be.

Share:|

Is SAP deployed at your company?  If yes, please join us to learn how Control-M for SAP 8 will help streamline processes and reduce complex interdependencies you face today when working with SAP. Control-M for SAP 8 introduces new features and enhancements, including temporary variants, which reduce the overhead in maintaining many copies of the same Variant in SAP systems, and jobtraces,     which is really helpful for troubleshooting as it´s much easier to see when the API call is started and when that call is answered by SAP.

 

We invite you and your Control-M administrators to join us for this Connect with Control-M live webinar on Wednesday, June 29th, at which time Javier Núñez will demonstrate some of the new features and enhancement of Control-M for SAP 8.  Javier will::

 

     •    Provide an overview of the Control Module for SAP 8 architecture

 

     •    Discuss and demonstrate some of the new functionality in Control-M for SAP 8 including:

 

              o    Temporary Variants
              o    Jobtraces
              o    XBP 3.0 certification

 

     •    Provide basic troubleshooting tips

 

Don’t miss a live demo of these capabilities. There will be a Q&A after the demo. Register Now!

Share:|

Did you know that by integrating your Control-M/Agent with sudo you can enhance your auditing capabilities, and add more flexibility to your jobs’ user authentication? Interested in seeing Control-M/Agent run jobs as a root user? Want to ensure your Control-M administrators learn how to take advantage of, and understand the different Control-M/Agent 9 modes in your environment?

 

 

On Wednesday, May 25th, Ted Leavitt demonstrated, step-by-step, how you can successfully configure Control-M/Agent 9 to run in three different modes (root, non-root, and sudo). During this Connect with Control-M webinar, Ted:

 

 

  •     Provided an overview of the different modes in Control-M/Agent 9, and their considerations

 

 

  •     Explained the new functionality in Control-M/Agent fix pack 100

 

 

  •     Demonstrated jobs running in the different Control-M/Agent modes (non-root, root, and sudo)

 

 

  •     Provided basic troubleshooting

 

 

Here is the Q&A for this webinar (Connect With Control-M: Control-M/Agent 9 root, non-root, and sudo)

 

________________________________________________________________

 

Q: Is there a way to sniff the sudo to get the password?  An example would be someone trying to hack in.

A: sudo does not rely on using passwords, at no time does it have the users password.

________________________________________________________________

 

Q: Does Control-M/Agent work with PowerBroker?

A: Please contact BMC Support and open an RFE is this is important to your business.

________________________________________________________________

 

Q: Can we use sudo with passwords?

A: You can see in the sudo execution that the sudo is being executed with the -n flag (non-interactive).  The sudo must be setup for NOPASSWD to work with the Control-M/Agent.

________________________________________________________________

 

Q: Is sudo the same as running as root mode?

A: The Agent will be running as a user other than root (the Control-M/Agent owner) when running in sudo mode.

________________________________________________________________

 

Q: Can the Agent itself run as a different user?

A: The Agent is typically run as the Agent owner.  Settting it up to run as a third user is somewhat involved and requires the verification of permissions.  We generally do not recommend this.

________________________________________________________________

 

Q: Does the Agent have to be running as root to use the sudo?

A: The Agent will be running as a user other than root (the Control-M/Agent owner) when running in sudo mode.

________________________________________________________________

 

Q: In Sudo mode, I can run jobs as any users without giving the password for that user? And only put those users in /etc/sudoers?

A: Correct, those run as users used on Agents with sudo do not need account credentials (passwords) entered via the CCM (or ctmsetown utility).  When using sudo mode, the security is managed through sudo and the /etc/sudoers file.

________________________________________________________________

 

Q: Does shagent and/or ag_diag_comm indicate sudo mode?

A: Currently, the ag_diag_comm does not display the Agent mode.  This is currently being considered to be included in the diagnostic report.  The shagent only reports the PIDs and process owners.

________________________________________________________________

 

Q: Is it necessary to recycle the Agent when changing the modes?

A: The set_agent_mode script will itself restart the Agent as needed as it does change the Agent's configuration.

________________________________________________________________

 

Q: Are there any issue concerning agent security operation mode that will help the agent use an external validation in Unix (a system that uses Windows AD).

A: Sudo will leverage the security setup on the operating system.  If you have authentication setup to use LDAP or active directory, this will work fine.  The only thing you have to do is make sure sudo works from the command prompt as the Control-M/Agent owner and does not prompt for a password.

________________________________________________________________

 

Q: Do users in "sudo-mode" need to be added to "Run-as user authentication" in Control-M?

A: No, sudo-mode uses the sudo security (/etc/sudoers).

________________________________________________________________

 

Q: What impact would changing the Agent execution mode have on my jobs?

A: As long as the run as users have the ability to submit the jobs, there should be no impact.

________________________________________________________________

 

Q: How can I configure sudo to limit runas users to members of a specific group?

A: Details on configuring sudo should be addressed by your systems or security administrator.  You can get some info from the sudo man page.

________________________________________________________________

 

Q: If the runas user's password changes and I'm in sudo mode, do I have to update anything in Control-M?

A: No changes are needed in the Control-M.

________________________________________________________________

 

Q: Is PAM needed with sudo?

A: This is a question best answered by your system administrator, as sudo is a system utility relying on the system's infrastructure.

________________________________________________________________

 

Q: What mode would BMC recommend?

A: We provide each of these modes for additional flexibility.  The sudo mode puts security back in the hands of your organizations security team.

________________________________________________________________

 

Q: If Run As ID is agent ID, will it use sudo to invoke job command?

A: No, no sudo is issued.

________________________________________________________________

 

Q: Can changing the execution mode also impact on number of jobs capacity on an agent?

A: There should be no impact to the M/Agent changing execution modes.

________________________________________________________________

 

Q: Do we have impact on resource capacity using different modes?

A: There would be as much as doing a sudo vs a su (or su_bmc).  There should be no to negligible impact on resources.

 

________________________________________________________________

 

Q: we use SAP module accounts; with Control-M agent in root mode; can we use SAP accounts with non-root and sudo mode of agents?

A: CM's do not use this functionality currently, although there is consideration for leveraging sudo with Application Integrator.

________________________________________________________________

Share:|

Learn how you can successfully deploy Control-M 9 clients across your user base with an easy to use, centrally managed distribution tool.

 

On Wednesday, February 24th, José Luna will discuss and demonstrate the following:

        •   Overview of the new Control-M 9 Client Distribution Tool


        •    Configuring the Client Distribution Tool


        •   Distributing and installing Control-M 9 clients


        •   Applying Fix Packs to Control-M 9 clients with the Client Distribution Tool

 

 

There will be a Q&A after the demo. Register Here!

Share:|

Need to integrate an application with Control-M? Interested in making your own Control-M job types? Want to ensure that operators understand how to schedule custom jobs that integrate with your applications? If so, register for the April Connect with Control-M webinar!

 

On Wednesday, April 27th, Joel Brecker demonstrated, step-by-step, how you can successfully create your own job types, and integrate your custom applications with Control-M. During this Connect with Control-M webinar, Joel:

 

 

    •   Provided an overview of the Control-M Application Integrator

 

 

    •   Provided examples of the different types of applications you can integrate with (SOAP, REST, command line)

 

 

    •   Had a demo about the creation of new job types, and showed how to schedule them

 

 

    •   Provided basic troubleshooting

 

 

Here is the Q&A for this webinar (Connect With Control-M: How to Integrate Applications with Control-M Application Integrator)

 

_____________________________________________________________

 

Q: How many execution steps can you have?

A: There is no documented limit for the number of execution steps allowed for an Application Integrator Job Type.

_____________________________________________________________

 

Q: When do we need to make a connection Profile?

A: You only need to make a connection profile if your integration Job Type is command line.

________________________________________________________________

 

Q: Is there some kind of version management for custom job types created using Application Integrator?

A: Version Management is planned for a future version of Application Integrator.

________________________________________________________________

 

Q: Has Application Integrator been given special considerations for an automated upgrade, for example moving from Control-M 8 to Control-M 9?

A: Application Integrator is an add-on to the Enterprise Manager and is upgraded when the module itself is upgraded.

________________________________________________________________

 

Q: What is the Application HUB?¬

A: Yes, the Application Hub is a community page where you can share Application Integrations with other members! You're free to take and add as much as you'd like!

________________________________________________________________

 

Q: Does running Application Integrator on a Linux machine require the use of XWindows or a GUI to launch it?¬

A: The Application Integrator uses a Web based designer for creating the Job Types and does require a supported Web Browser:

- Chrome 20 or later

- FireFox 25 or later

- Internet Explorer 10 or later (compatibility mode OFF)

________________________________________________________________

 

Q: Is there a user authorization setting for read/write permission in the Application Integrator Designer?¬

A: This functionality was added in Application Integrator Fix Pack 2.

________________________________________________________________

 

Q: When creating connection profiles for Application Integrator is an account file also created on the Control-M Agent side which contains these settings?¬

A: Yes there is a cm_accounts.xml file created in the /cm/AI folder on the Control-M Agent which holds all the connection profile settings.

________________________________________________________________

 

Q: Question - Can you make a copy of built-in job type (or other custom job type) and use it as a starting point? Is it done via EXPORT/IMPORT?¬

A: The Application Integrator will only export/import files of the type .ctmai and the built-in job types of Control-M are exported as XML.

________________________________________________________________

 

Q: Do you recommend maintaining non-production and production Control-M environments and promoting jobs from non-prod to prod?

A: It is good practice to test any new job type thoroughly before placing it into a production environment.

________________________________________________________________

 

Q: How do you move a job type from one environment to another?

A: To move a Job Type from one environment to the next you will need to export it from the current environment and import it to the new environment.  Keep in mind that if the job already exists in the destination environment that it will first be undeployed before it is re-deployed.  This will remove any connection profiles and associated files for that AI Job Type.  It is recommended to make a backup of the connection profiles before the undeploy.

________________________________________________________________

 

Q: How do you import a job type from the Application Integrator Hub?

A: To import a Job Type from the Application Hub you can click on the "Import from Application Hub" button in the AI Designer and choose the Job Type you would like to import, so long as you have access to the internet from your Control-M Enterprise Manager Server.  The alternative to this is to visit the Application Hub from a machine with internet access and download the Job Type and Import it using the AI Designer.  The application Hub can be found here:

https://communities.bmc.com/groups/bmc-control-m-application-hub

________________________________________________________________

 

Q: How many PRE and POST execution steps can you have?

A: You can only have 1 PRE and 1 POST command per Job Type.

________________________________________________________________

 

Q: Where do I download application types?

A: From the Application Hub located here: https://communities.bmc.com/groups/bmc-control-m-application-hub

 

________________________________________________________________

 

Q: How are these job types published to new Agents after creating the new job type, is it Automatic or a manual task?

A: If the Job Type already exists when you add a new Control-M Agent then you would need to log into the AI Designer and deploy the job to that new Agent.

________________________________________________________________

 

Q: Can an executing process return status codes directly to Control-M, or is parsing text the only way to read status information?

A: Standard out error messages and status codes are sent based on the return code handling you put into place while designing the new job type.  You can add additional error handling by parsing for specific information that should cause a job to fail.

________________________________________________________________

 

Q: In the example, password entered into connection profile is a parameter in the command. Is the command with password exposed in SYSOUT?

A: The password is not exposed as long as you are using a Masked textbox.  The "password" textbox is a Masked textbox and can only be placed into the connection profile section.

________________________________________________________________

 

Q: We have an application for which we kick off cubes within the database. Could the tracking of that cube within the DB be tracked with AI?

A: This will depend on how the "Cube" reports its progress or what indicates it has finished.  An example would be if the "Cube" creates output based on its progress, you could take this output and return specific progress reports.

________________________________________________________________

 

Q: Do we have full control on AI from CCM? (Like enabling debug..etc)

A: Application Integrator is controlled from the AI Designer.  You have full control of debug by logging into the AI Designer.  The designer is a Web Application and will be up as long as the Web Server is running.

________________________________________________________________

 

Q: If you have a job with multiple execution steps and 1 fails, can you rerun the job from the step that failed?

A: This functionality is coming in a future release of Application Integrator.

________________________________________________________________

 

Q: Are there any AI integration prebuilt for Oracle Data Integrator?

A: Please check the Application Hub for the current listing of Job Types shared within the community.

https://communities.bmc.com/groups/bmc-control-m-application-hub

Share:|

Did you know that by integrating your Control-M/Agent with sudo you can enhance your auditing capabilities, and add more flexibility to your jobs’ user authentication? Interested in seeing Control-M/Agent run jobs as a root user? Want to ensure your Control-M administrators learn how to take advantage of, and understand the different Control-M/Agent 9 modes in your environment? If so, register for the May Connect with Control-M webinar!

 

On Wednesday, May 25th, Ted Leavitt will demonstrate, step-by-step, how you can successfully configure Control-M/Agent 9 to run in three different modes (root, non-root, and sudo). During this Connect with Control-M webinar, Ted will:

 

  • Provide an overview of the different modes in Control-M/Agent 9, and their considerations

 

  • Explain the new functionality in Control-M/Agent fix pack 100

 

  • Demonstrate jobs running in the different Control-M/Agent modes (non-root, root, and sudo)

 

  • Provide basic troubleshooting

 

Don’t miss a live demo of these capabilities. There will be a Q&A after the demo. Register now!

Share:|

If I were to answer that question, based upon emotional connection, it would be Magnum.  Ruggedly handsome man, awesome moustache, crazy cool shirt and best of all – that Ferrari!  Throw in 2 best friends, one that flies helicopters and the other a bar owner, and a stuffy but interesting in a funny sort of way “guardian” in Higgins, and what’s not to love?!

80magnumpi_05.jpg

But that answer is based upon the proverbial “good old days”.  While I had fun watching Magnum PI as a kid, it really has no impact on my life today.  But SAP does.   SAP is often regarded as the most used commercial software application in the world.  It is used by hundreds of
thousands of companies, many of which I interact with on a daily basis.  From the car I drive (which is nothing like a firetruck red Ferrari 308), to the work travels I routinely take (in commercial airliners and not cool helicopters with neat paint jobs), to the shirts I wear (which are exclusively not vibrant Hawaiian shirts) – and most everywhere in between - SAP software is behind the scenes.

 

Back in the early 2000s the first application Control-M provided support for, in the form of an Option, was SAP.  Over the years many  enhancements and additions have been made to Control-M in support of SAP (Business Warehouse, Data Archiving, Business Objects, etc), with the latest being the addition of support for SAP Process Integration (SAP PI).

 

SAP Process Integration is part of the SAP Process Orchestration bundle.  It is a middleware component of the SAP NetWeaver product group that is used to facilitate the exchange of information among SAP ERP internal software and systems and those of external parties.   SAP PI is the SAP recommended way to integrate between SAP HANA Cloud and SAP NetWeaver – which are part of SAP’s strategic direction.

 

Control-M for SAP Process Integration enables the management and automation of SAP PI channels by scheduling ‘channel start / stop’ events and monitoring the channel status, allowing improved utilization of the SAP PI channels which in many cases are a limited resource.

job1.jpg

To get to the bottom of some mystery in your personal life you can find someone like Magnum PI in a city near you, they just won’t be as amazing or as cool as Magnum was.  To solve the mystery of how to best manage workloads for your SAP environment, check out the Control-M for SAP page where you can find information on managing workloads for SAP PI along with many other SAP related components.

 

And that is both amazing and cool!!

Share:|

Need for High Availability? Interested in reducing downtime? Want to ensure application continuity?

 

On Wednesday, March 30th, Martin deCastongrene demonstrated, step-by-step, how you can successfully implement high availability for your Control-M/Enterprise Manager 9. During this Connect with Control-M webinar, Martin presented and demonstrated the following:

 

Provide an overview of the new Control-M/Enterprise Manager 9 High Availability
Give step-by-step installation guidance for the Control-M/Enterprise Manager 9 High Availability failover node
Show how to configure Control-M/Enterprise Manager 9 for High Availability

 

Here is the Q&A for this webinar (Connect With Control-M: High Availability with Control-M/Enterprise Manager 9)

 

________________________________________________________________

 

Q: When will this capability be available for PostgreSQL?

A: The integration of PostgreSQL for Control-M/Enterprise Manager is being looked at and will be available in a future Control-M/Enterprise Manager Version or FixPack.

________________________________________________________________

 

Q: How are extra items such as Forecast, BIM, Self Service etc. handled?  Do they need to be installed on the HA server also?

A: The additional installations such as BIM, Forecast and Self Service are activated when installed on the Primary Control-M EM  platform.  As the Secondary installation points to the same database as on the Primary, no additional action is needed on the Secondary.

________________________________________________________________

 

Q: We would like to have the failover instance in a remote datacenter. Are there any latency limitations? What if the database did not failover?

A: DNS and network latency will need to be responsive.  Testing should show if it is successful.

   The Secondary Node will failover to the same Database the Primary Node originally uses.

   If the failover does not complete it will automatically fall back to the Primary node.

________________________________________________________________

 

Q: Can a previous standalone Control-M/EM installation be converted to a secondary HA failover node?

A: For a standalone to be converted, it will need to be uninstalled and reinstalled as a High Availability Secondary Node.

________________________________________________________________

 

Q: Are the Failover Dialog items logged in a file somewhere that could be viewed at another time?

A: The EM CHA (Coordination for High Availability) process can be set to a higher debug level (MiniumDbgLvl 5 5) in order to log failover events to the cha*.log file located under the Control-M EM installation "log" directory

  ________________________________________________________________

 

Q: How long should the failover process normally take?

A: Anywhere in the 3-5 minute range would be considered normal.

________________________________________________________________

 

Q: Why isn't PostgreSQL database supported for HA in EM?

A: Development is continuing work on integrating a PostgreSQL solution for HA.

________________________________________________________________

 

Q: We are planning to set HA on our DR datacenter, can we install database on both sites (primary and DR)?

A: As there is only one Database, it is recommended to be on a third machine, which can be located in either the network where the Primary is or in DR.  The Database just needs to have good network response time to and from the Primary Node and the Secondary Node.

________________________________________________________________

 

Q: The switch over looks great out in demo, what are the common issues which we may come across or based on your experience any comments on the same...

A: DNS and network latency should both be performing well for the Failover and Fallback to complete.

________________________________________________________________

 

Q: Can you point the HA instance to an alternate Oracle DB that is kept in sync with the primary via Oracle Golden gate?

A: The Secondary HA instance is designed to point to the Primary database. We would ask to open a support ticket to discuss specific requirements.

________________________________________________________________

 

Q: Notice webinar did not actually go through HA secondary install or show HA status of primary/secondary after install. I found that the Secondary EM and CTM config agent is not auto started either after install or secondary reboot.

A: The Control-M Install Guide has a section on what to include in startup scripts for Enterprise Manager on the Primary to start.

   Only the start_config_agent script section will be needed for the Secondary startup.

________________________________________________________________

 

Q: How can I leverage Control-M failover to have 24x7 availability when applying maintenance?

A: You can Failover from the Primary to the Secondary and run on the Secondary while applying OS level maintenance or reboot.

   After Fallback to the Primary the same can be done on the Secondary.

________________________________________________________________

 

Q: In what order do I have to apply fixpacks (primary first, then secondary)?

A: EM Fixpacks are to be applied first to the Primary and then to the Secondary HA platform.

________________________________________________________________

 

Q: When the failover occurs, will the root_menu on the primary be able to manage the secondary also?

A: Once the Failover occurs to the Secondary platform, the root_menu on the Secondary must be used to manage itself.

________________________________________________________________

 

Q: You have to manually start the EM and CTM config agent and put startup scripts in place to start after reboot of secondary. This needs to be documented in Admin and/or Install guides.

A: The Control-M Install Guide has a section on what to include in startup scripts for Enterprise Manager on the Primary to start.

   Only the start_config_agent script section will be needed for the Secondary startup.

________________________________________________________________

 

Q: Can you use the command line to initiate a failover, rather than using the ccm interface?

A: You can use the stop_config_agent script to shutdown the Configuration Agent and the CHA and that will trigger a Failover.

________________________________________________________________

 

Q: Where does Oracle db reside on primary or secondary ?

A: Our recommendation is that a third machine be used for the Oracle Database. 

________________________________________________________________

 

Q: Any plans to create a similar interface in the CCM for failing over Control-M Server?

A: The Control-M Server HA is also supported with the High Availability Tab in the Control-M Configuration Manager.

________________________________________________________________

 

Q: When you say that Fix Packs need to be applied to both nodes and then restarted before Failover and Failback can be accomplished, what (exactly) are the steps for applying a fix pack to both nodes?

A: You will want to bring both Primary and Secondary nodes down and EM Fixpacks are to be applied first to the Primary and then to the Secondary HA platform.

________________________________________________________________

 

Q: Will there be Failover/High Availability for the database as in version 7.0

A: The Control-M Server still can enable Mirroring in version 9.

_______________________________________________________________

 

Q: I have noticed in version 8 if I get disconnected I have to logout and back on to get a solid connection. Will the failover process have the same issue?

A: After Failover or Fallback you may need to press the retry button on the connection Dialog.

________________________________________________________________

 

Q: How long does it take automatic failover to happen?

A: Anywhere in the 4-6 minute range would be considered normal.

________________________________________________________________

 

Q: The presentation says: Fixpacks will need to be applied on both nodes... Can we failover to the secondary, apply FP2, and then fail back to primary, and apply FP2 on the secondary?

A: You will want to bring both Primary and Secondary nodes down and EM Fixpacks are to be applied first to the Primary and then to the Secondary HA platform.

________________________________________________________________

 

Q: Is there an additional license charge for HA?

A: You will want to discuss license issues with your Account Manager.

________________________________________________________________

 

Q: In this scenario, you assume 2 em on 2 different hostnames and 1 database in 1 some different hostname. What if the database is down or fails? is there some scenario of ha that includes the database?

A: Please open a support ticket and we can review the various options available with high Availability and disaster recovery as it relates to the database.

________________________________________________________________

 

Q: We have set HA with Postgres, should we enable archive mode for the PostgreSQL database?

A: You are welcome to enable the archive mode for the PostgreSQL.

________________________________________________________________

 

Q: If the alternate primary option is activated for a secondary node, is it possible to rollback the primary for the primary node without reinstall the first node?

A: Yes, you can just select the Fallback to Primary option and it will return to the original configuration; running on the Primary.

________________________________________________________________

 

Q: I found that the secondary EM and CTM config agent is not auto started either after install or secondary reboot. You must manually restart and create scripts for reboot.

A: The Control-M Install Guide has a section on what to include in startup scripts for Enterprise Manager on the Primary to start.

   Only the start_config_agent script section will be needed for the Secondary startup.

________________________________________________________________

 

Q: Do we need a shared disk in cluster for the installation?

A: The Enterprise Manager Database and Primary Enterprise Manager and Secondary Enterprise Manager can be on a standard disk with no cluster needed.

________________________________________________________________

 

Q: When it's necessary to debug this feature, should we enable debug on both sides, primary and secondary?

A: You will want to enable debug on both sides, Primary and Secondary.

________________________________________________________________

 

Q: Is there a way to configure the EM API web service to HA?

A: Currently High Availability is being supported for the Control-M/Enterprise Manager and Control-M/Server only. 

________________________________________________________________

 

Q: Can you define "same database"? SQL Listener is a single point of contact for Always On multi node setup. Will EM work point to the non-changing listener?

A: Please open a support ticket and we will gladly review the Oracle scenario in your environment.

________________________________________________________________

 

Q: If you weren't logged in the CCM, and it failed over, will the banner be displayed once I log in? 

A: The Failover banner will be displayed the next time someone does login to the Control-M Configuration Manager

________________________________________________________________

 

Q: When the HOST from primary is DOWN, the CLIENT connection remains asking for the primary node name for connections on the Secondary with the HA Secondary ACTIVATED?

A: This question has been answered verbally. 

________________________________________________________________

 

Q: If I have 2 environments setup with HA and then mirror the DB to the 2nd environment  if I shut down the 1st environment and bring up the 2nd can I expect that to work?

A: Please open a support ticket and we will gladly review your environment.

________________________________________________________________

 

Q: What will be the status of the executing jobs in the monitor? (during the failover process)

A: During the failover the Monitoring will be suspended until the GUI Server and Gateway have started on the Secondary node and the WLA Client is reconnected.

________________________________________________________________

 

Q: Does Control_M record the reason for failover and log the same ?

A: The EM CHA (Coordinator for High Availability) process can be set to a higher debug level (MiniumDbgLvl 5 5) in order to log failover events to the cha*.log file located under the Control-M EM installation "log" directory

________________________________________________________________

 

Q: If a FP contains DB changes then you can't failover correct?  You will have to shut down both EMs?

A: Correct.  You will want to bring both Primary and Secondary nodes down and EM Fixpacks are to be applied first to the Primary and then to the Secondary HA platform.

________________________________________________________________

 

Q: When failing over could there be any issues getting Alerts or Global conditions during the fail over process?

A: During the actual Failover Alerts and Global Conditions will be suspended until Failover completes.  Then any queued up Alerts or Global conditions will be propagated.

________________________________________________________________

 

Q: How would the account management settings change for Control-M Web Services API ?

A: This question has been answered verbally. 

________________________________________________________________

 

Q: For Control-M environments with Mainframe and Distributed are there any mainframe parameters that have to be configured for the IOAGATE for HA?

A: The Gateways for the Control-M datacenters, whether Mainframe or Distributed are defined and activated initially on the Primary platform and require no special handling when moved to the Secondary.

________________________________________________________________

 

Q: Can I automate, or schedule when to execute a failover from primary to secondary?

A: Using the stop_config_agent script with the password file option it could be possible to automate the failover.

________________________________________________________________

 

Q: Will HA work if the primary and secondary are at different fixpacks?

A: The Primary and Secondary Nodes need to be at the same FixPack level.

________________________________________________________________

 

Q: The install of the HA is part of the product install, I assume. Or is it a separate install?

A: The HA functionality is part of the Base install for Control-M EM 9.0.00, there isn't a separate download. We strongly recommend applying the latest fixpack to ensure you have the most recent fixes on the system.

________________________________________________________________

 

Q: Clarification for the FP install. If the FP we are installing changed the database, will the secondary (still not updated) know that it needs to operate with a possibly different schema?

A: Correct.  The FixPack install detects that it is being installed on the Secondary and installs only what is needed on the Secondary.

_______________________________________________________________

 

Q: So, in order to KNOW why it failed over DEBUG has to be turned on in order for that to be logged.  Is there not a performance impact to constantly running with DEBUG on? 

A: Leaving the EM CHA process in debug may have a slight resource overhead on the system as the activity is written to the log file.

________________________________________________________________

 

Q: What processes answer for a connection from a CLIENT calling for the primary NODE when it was jumped for the secondary node? If the HOST (machine) is offline, how the connections calling for the first node (that is offline) arrives for the secondary node?

A: Please open a support ticket and we will gladly review specifics of the Failover architecture.

________________________________________________________________

 

Q: What will be the status of the executing jobs in the monitor? (during the failover process)

A: The status of executing jobs will stay in executing state until Failover is complete and the Client reconnects and the status is updated. 

________________________________________________________________

 

Q: What are all the conditions need to checked before by control-m before switching to secondary EM?

A: The Primary CHA checks the Secondary CHA process in up, communicating and communicating with the Database.

________________________________________________________________

 

Q: Are the primary and secondary using the same CCM?

A: Yes.  A Control-M Configuration Manager connected to the Primary before Failover will be reconnected to the Secondary after Failover.

________________________________________________________________

 

Q: About the FPs: Then, the HA is not for applying CTM FPs. All components must be down in primary and secondary when applying FPs.

A: That is correct, when applying fixpacks, Control-M must be down. 

________________________________________________________________

Share:|

Need to integrate an application with Control-M? Interested in making your own Control-M job types? Want to ensure that operators understand how to schedule custom jobs that integrate with your applications? If so, register for the April Connect with Control-M webinar!

 

On Wednesday, April 27th, Joel Brecker will demonstrate, step-by-step, how you can successfully create your own job types, and integrate your custom applications with Control-M. During this Connect with Control-M webinar, Joel will:

 

•   Provide an overview of the Control-M Application Integrator

 

•   Provide examples of the different types of applications you can integrate with (SOAP, REST, command line)

 

•   Demo the creation of new job types, and show how to schedule them

 

•   Provide basic troubleshooting

 

There will be a Q&A after the demo. Register now!

Tom Geva

Batch is Back!

Posted by Tom Geva Employee Apr 4, 2016
Share:|

Check out our multi-talented but anonymous (at his request) performer who came up with this amazing April Fool’s day song!

(mp3 attached below...)

 

I was justified when compute was new

To manage jobs, I typed commands a few

Times are changing, now the kids just tap But the fever's gonna catch you when the batch gets back

 

Post a picture or just check in

Even write an email, that’s not a sin

I can batch the jobs at your hack-a-thon I get high running workflows, it’s a lot of fun

 

It's the batch, It’s the batch

Oh the batch is back

Stone cold sober as a matter of fact

I can batch, I can batch

`Cause I'm faster than you

It's the way I compute

Algorithms I do

 

I entertain by running jobs

Process Big Data, even DB BLOBs

Scheduling jobs, my God, what's that

Oh it's nifty doing work when the batch gets back

 

Batch, Batch, the Batch is Back.

 

Now it's your turn! Record your favorite version of Amy Winehouse's "Back to Batch", AC/DC's "Back in Batch" or "Batch, Batch...Baby" (a little '80's ice here...), MC Hammer's "U Can't Batch This", or any other song that related to batch, scheduling or workload automation - and share it!

Share:|

blog1.jpgIsn't documentation a wonderful thing? Knowing exactly how "Tab A" fits in "Slot B" or how to connect your shiny new electric car to the charger or how long to bake those brownies is a good thing, right? When "winging it" is not an option, where do you turn?  “Read The Free Manual”?  That’s like stopping to ask for directions… “I know where I’m going!!!”  Why should you take time to read the documentation or the instructions or the recipe?  If only I followed my own advice… The “do what I say, not what I do” mentality works, right?

 

When I started at BMC five years ago, I did a lot of trial and error.  Lots of cool new stuff to learn. BMC, as everyone who uses and loves Control-M knows, does not rest on its laurels.  Control-M is continually being enhanced and improved with new features, functions and innovations.  New applications and platforms come down the pike every day.  From ETL tools to ERP tools to Big Data applications to Managed File Transfer the frequency and volatility of change is increasing.  And that level of change will only accelerate.

 

So how do you keep up? How do you handle this change and all these new tools and applications when you’re asked to schedule jobs blog2.jpgfor them? I decided to take a step back and look at this from a comfortable place; I put my scheduler hat back on and looked at this from a “how to” perspective. I figured out how to build jobs in Control-M and then created a “cookbook” document for it.  A Cookbook, as you know, is made up of many recipes on “how to make something”.  This revolved mostly around the Control Modules, each of which all have unique requirements and connection profiles to enable us to schedule that work.

 

Creating these “recipes” in v7 and updating them for v8 and v9 and then added new documents as new integrations came out took quite a bit of time. As the library grew it became clear a more “formal” process needed to be put in place to keep this information up-to-date.   To that end, the Control-M cookbook documents are in the process of being transitioned into the Control-M documentation. The “how to” documents will be melded with existing and new documentation as new versions and releases are introduced. And as new features and functions are added, this “cookbook” or “recipe” approach will continue to be incorporated into the documentation.

 

Where do I go? Here is a basic list of the contents of the “Cookbook Library”. The topic headings should be self-explanatory:

blog3.png

•    Control-M Best Practices and ITIL

•    Control-M CM & Agent How-to Examples

•    Control-M Non-standard Integrations

•    Control-M Other Procedures

 

As this transition proceeds you should see this “cookbook/how-do-I-do-that” approach be folded into the documentation. Until that transition is fully realized, I will keep updating and “publishing” cookbook articles. You may always ping me to get PDF versions of these documents until they are fully incorporated into the Control-M documentation. I have added the docs to Dropbox so you can grab the ones you need. I don’t pretend to have created a document for everything; I’ve tried to hit the high spots/most frequently used CMs and some of these docs are still v7 and v8. But once you delve into these documents, hopefully you will see some value and will be able to short-cut your learning curve. There are also quite a few documents other BMC SCs have contributed for “other processes and procedures”. I have added those documents to this Dropbox as well.

 

Use as you see fit and hit me up if you have questions. Happy scheduling!!

 

blog4.jpg

Share:|

 

  

I remember back in the day working in a datacenter batch environment.  I was responsible for working on failed processes, doing the research, figuring out what happened and why. 

 

This was on the Mainframe and we had sysout storing software that made it easier to look at previous job outputs or search to find errors in other jobs.  Mean time to repair was shortened because we had this capability.

 

These days nearly all of our customers have a distributed environment and the tools either do not exist or are costly to purchase and maintain to store the data.  The output files from jobs can be archived, but accessing them is not easy. Depending on the number and size of the outputs, some customers try to keep them on a server for as long as possible but that requires a sizable disk drive.

 

Workload Archive

 

As a Principal Software Consultant for Control-M, I was pleased when BMC introduced the Workload Archive component.  Since it integrates to Control-M, it can retrieve and store output, Control-M log and job runtime information in a separate database.  Since it can store this data for extended periods of time you now have a way to see previous runs of a job or search outputs and logs for specific information.

BMC Control-M Workload Archive

 

Simple to Use

 

Perhaps what I like most about Workload Archive is how easy it is to retrieve the data.  Access it from either Self Service or the WA GUI by simple performing a right click on the job in question.  In the WA GUI it takes you to the History domain and in Self Service it brings up a window with the previous job runs.

 

 

                    Self Service Right Click on Job                                           Self Service List of Jobs

 

                           

 

Easy to Search

 

Did you ever see a job failure and think: “Where have I seen that error before?”  Think of what you would have to do to find a job that had the identical error or message. It would take a lot of work.  With Workload Archive you can simply copy the output or log statement you want to search for, open a new Archive Search window, select * for jobname and paste the statement into either the output or log field.  You can look back over a specific time period or through every job in the Archive.

                   Highlight Statement in Output                                     Paste Highlighted Statement in Search

                                                                                  Results of Archive Search

 

 

 

 

 

In this example I actually found that another job was doing a file transfer at the same time my production job was attempting to send the file.  This is what caused the error.  Because Workload Archive allowed me to compare the output files from two independent jobs, I was able to determine why it received the error.

 

 

                                                                                                                                                                                                                                                                                                                                                                                                            Result of Archived Compare

 

 

Finding Changes

 

 

How many times have you seen a job fail and wonder “What changed?” Workload Archive allows you to pull up the different runs of that job and compare a successful run to the failed run. This is a simple as a right click on thejob, select More Analysis then Archive Search. 

 

 

The search window will open in the History domain showing the previous runs of the job.  You then select the two jobs you want to compare and also whether you want to compare the job log or the output.  The bottom of the screens show what each line looks like as it is clicked.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              Select Archive Search

    

                                      Result of Archive Search

 

                                                                                                                                              

 

Define Archive Retention Period

 

 

How long archived data is kept depends on factors such as auditing or how far back you want to keep it.  Within the Control-M Configuration Manager is an option to define how long to keep data.  You can keep SAP jobs for 2 years and test jobs for 2 weeks.  Multiple policy definitions can be made for different job types or platforms.  Workload Archive can store both distributed and Mainframe jobs. 

                                                                           Workload Archive Policy Definitions

 

MTTR Made Quicker

 

While things weren’t bad in the good old days, Workload Archive has definitely decreased our customers Mean Time to Repair.  Not only does it help the IT side but because it can be seen just as easy in Self Service, the end users have the same accessibility to the outputs and logs. 

 

Filter Blog

By date:
By tag: