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.  Deploying and Managing BRX's

    Employee
    Posted 01-21-2010 03:45

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

    Originally posted by: michaelslowey

    Hello,

    I was wondering if anyone has any information with regards to the Deployment and Management of BRX's using BRE?

    Currently I am just creating BRX's/BRS's and manually deploying them to our server via winSCP.

    Cheers
    Mick


  • 2.  RE: Deploying and Managing BRX's

    Employee
    Posted 01-21-2010 07:29

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

    Originally posted by: timonk

    Hello Mick,

    BRE has the ability to deploy BRXs to servers in the currently connected farm through the menu located here:

    Tools--> Server-->Manage Deployed Graphs

    This will open a gui displaying all your available servers, in a folder-tree similar to Windows Explorer.

    From here you can select a specific server and deploy BRXs, run them, upload/download BRS state files so can load them into the BRG file in BRE, and also view the log of events on a particular executed BRX.

    I would suggest creating a simple, do-nothing graph that just strings some static data and some filters together, and use it to get familiar with the controls.

    Regards
    Timon Koufopoulos,
    MDA Support.


  • 3.  RE: Deploying and Managing BRX's

    Employee
    Posted 03-10-2011 17:09

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

    Originally posted by: phourigan

    Hi,

    I have a basic Farm of 2 Servers. I want to deploy my graph in an automated way from our in-house build tool.

    At the moment I SCP the BRX to the /opt/app/lavastorm/deploy dir on all servers.

    Everything seems to work fine, but I have a question.

    Using the BRE, Manage Deployed Graphs option. This results in the BRE deploying the graph to the target server as follows.

    22:56:07 >>Msg: DEPLOYEDBRX from MDSRDSRV01.mdsuk.com:7721#Status
    >> brxname:Silly_Graph
    >> brxuri:file:/opt/app/lavastorm/deploy/Silly_Graph.brx
    >>
    22:56:09 >>Msg: DEPLOYEDBRS from MDSRDSRV01.mdsuk.com:7721#Status
    >> brxname:Silly_Graph
    >> brsname:default
    >> brsuri:brsuri


    This results in the deployed artefacts on the LAE server.

    [lavastrm@mdsrdsrv01 lavastorm]$ ls -l -R deploy/
    deploy/:
    drwxrwxr-x 2 lavastrm lavastrm 4096 Mar 10 23:58 Silly_Graph
    -rw-rw-r-- 1 lavastrm lavastrm 11116 Mar 10 23:58 Silly_Graph.brx
    deploy/Silly_Graph:
    -rw-rw-r-- 1 lavastrm lavastrm 8713 Mar 10 23:58 default.in.brs
    -rw-rw-r-- 1 lavastrm lavastrm 73 Mar 10 23:58 default.runstate


    So, do I need to attempt to generate my own default.in.brs and default.runstate files? Or to put it another way should I be trying to invoke the peice of code the BRE uses in its 'Manage Deployed Graphs'?

    thanks
    --ph


  • 4.  RE: Deploying and Managing BRX's

    Employee
    Posted 03-11-2011 12:03

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

    Originally posted by: timonk

    phourigan,

    I guess part of this comes down to what you are really trying to do. In general, I would not recommend you place BRX files in the /deploy directory unless you used the Manage Deployed interface in BRE. That really should be left for BRE deployed operations.

    Now, LAE does not really place any restrictions on where it is that users store their graph files. You can place the BRX's anywhere on the system you want. When you make your calls to execute them, you just specify that location to the brainController.py command.

    The question I have is: what you are trying to setup? Are you trying to build BRX files, then SCP them to the deploy directory with the intent of managing them within BRE? Or are you just trying to keep all your BRX's on your server organized in the same location?

    Regards
    Timon Koufopoulos
    MDA Support.


  • 5.  RE: Deploying and Managing BRX's

    Employee
    Posted 03-15-2011 11:34

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

    Originally posted by: phourigan

    Hi,

    Thanks for the response.

    Really what we wanted to know was; Whats the difference between, dropping a BRX to the NFS via SCP and using the BRE 'Manage Deployed Graphs' functionality?
    From what I can tell, the only difference is in the generation of the default.in.brs, which lists the runtime parameters.

    I take your point on the usage of the deploy dir and thats fine, so really what we are aiming to do is:
    - Have the developer create the graph in BRE and produce a BRX and a script for the list of runtime properties listed
    - Version those artefacts in our Build tool/SCM
    - Deploy the artefacts to our target LAE Controller into a deployed-graphs versioned dir structure. (Its based on Apache ANT and Maven, so either we can invoke the same BRE "Manage Deployed Graphs" function or its a simple SCP)
    - Run the graphs/BRX via the brainController.py with the -r param to give it a unique runId and -a for each of the runtime arguments or -p for graph parameters.

    Or have I got the wrong end of the stick here?

    Is it possible for us to invoke the BRE "Manage Deployed Graphs" function from a java class?
    --ph


  • 6.  RE: Deploying and Managing BRX's

    Employee
    Posted 03-16-2011 06:42

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

    Originally posted by: timonk

    PH,

    I don't see any problem with what your trying to do. There is no reason you can't just SCP a brx over to a location and then run it via brainController. Those other files you mention are for the Manage Deployed Graphs interface.

    So I think you have the long and short of the right end.

    As to executing the MDG functionality directly, I do not believe so. That interface is really designed for use BRE and not outside of it. If I get what you are trying to do, your best bet would be to create a brs state dump of your brx runs (its the -s parameter for braincontroller) perhaps in a separate controlled directory, then download them to your local systems and load them into BRE when viewing the source BRG.

    cheers
    -Timon


  • 7.  RE: Deploying and Managing BRX's

    Employee
    Posted 05-29-2012 06:17

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

    Originally posted by: jtreddy

    BRE - MDG.JPG

    Just wondering if this "Manage Deployed Graphs" module is supported or not. I couldnt see any button highlighted apart from 'Deploy BRX'.
    I did click deploy BRX & not sure where it has deployed the latest brx.
    Also why the other buttons are not active.. is it an issue just on my laptop ?
    Plz. help.

    Thanks,
    Jagadees


  • 8.  RE: Deploying and Managing BRX's

    Employee
    Posted 06-05-2012 10:48

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

    Originally posted by: rboccuzzi

    It is supported, and should be working. Unfortunately, it looks like it currently is missing documentation.

    When you deploy a brx, it copies the graph to the server in the deploy directory. To refresh (and see your deployed graph), you can click on the folder to close and open it. This will refresh, and it should expand and show the deployed brx and brs files. You need to always have at least one brs with a brx, and when you first deploy the brx, it will use the current brs selected in your toolbar.

    You can then click on the brg located under the server folder, and some other buttons will un-grey. Here you would be able to deploy a different brs for the same graph, or delete the brg folder (which contains the brx) with all brs's that were deployed with it.

    If you click on a brs (under the BRX, a leaf icon inside the folder, you will have further options, the ability to run the brs, import or download the brs, and look at events for the brs. the last 3 will only be available if the brs has been run.

    I hope this helps. I have raised PR4058 as a request to add proper documentation to this control.

    Cheers
    Rich