LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Migration Graphs from 5 to 6 also Migration of the Shell Scripts to the Automation 6

    Employee
    Posted 09-16-2016 08:34

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rmimms

    I am currently looking information how to Convert my Graphs from Version 5 to version 6

    Current Graphs are run by a Unix Shell Scripts

    Shell Script both Output files and also Email Primes that either the Graph fails or completes

    I do not see any threads on this question


  • 2.  RE: Migration Graphs from 5 to 6 also Migration of the Shell Scripts to the Automation 6

    Employee
    Posted 09-16-2016 08:39

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    The attached graph uses the Lavastorm API to determine which graph it is running (nder) and then notifies the recipients with various information about the graph you tie it to.

    Warning: if you want "simple" notification, then this graph is overbuilt for that purpose.. this graph does quite a bit more work. It not only notifies the recipient of the status, but it also forwards the error messages from the failed graph.

    I would STRONGLY suggest that you review the actions this graph takes and see if they are sufficient for your purpose. It is almost guaranteed that you will need to make changes. Also.. this graph is for demonstration.. it's not a formally "supported" tool yet.

    In the Automation Screens, you define your primary Run_Definition, and then you add another Run_Definition as a "child" under your main graph.
    On the child Run_Definition, you then have the option to "Run if Predecessor Fails" or "Run if Predecessor Succeeds".
    The main caveat here is that each Run_Definition must have a unique name so I use LM_Status_Notify_001, 002, 003, etc.

    This graph requires that you setup several parameters on the Run_Definition (email username, address, password, etc) You can also define those parameters on a Global Parameter set such that you can use it across multiple instances of this graph.

    =====================
    If you only desire "simple" notification, then build a graph with just an SMTP node in it and setup the RunDefinition using the method above.
    Attachments:
    LM_Status_Notify.zip


  • 3.  RE: Migration Graphs from 5 to 6 also Migration of the Shell Scripts to the Automation 6

    Employee
    Posted 09-16-2016 11:52

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: rmimms

    Thank you very much

    rmimms