MVE Customer-built Applications Tree

Version 2
    Share This:

    Announcing an SPE for MainView Explorer that allows customers to build an “Applications” tree, to appear as the first node in the upper navigation tree. MainView Explorer has long supported customer-built configurations that specify a collection of views and charts to be opened as a group. And more recently support was added to enable product developers to distribute out-of-the-box configurations, accessible from the product-built EZExplorer tree that is part of the lower Product navigation tree. This SPE will introduce support for the customer to build an “Applications” tree, which will appear as the first node in the upper Area navigation tree. This tree can be organized similarly to a product EZExplorer tree, with descriptive categories of leaf nodes that launch user-built configurations. This Applications tree will be shown at the top of the Area tree and will contain an entry for each individual Application member, built entirely by the user with graphical tools in a topology view and saved as XML in the mainframe BBCDEF library. If saved in the site library (along with the configurations), this Application node will be available to all users at the customer site. (No Applications tree will be shown if there are not yet any Application members in the user or site BBCDEF libraries).


    This is how an Applications tree might look - assuming that 2 members (“Banking” and “Operations”) have been saved in BBCDEF (members from the user library will have a “U” in parentheses appended).


    Creating and Editing an Application node

    Creating an Application node (an XML member in BBCDEF) is done by right-clicking on the top Applications node (or, if for the first time, from the File menu) and selecting Create application map, which will open a bare-bones topology view (with 3 default nodes: a main node with 2 empty folder nodes).


    Updating an existing Application node is done by right-clicking on the Application node and selecting Display application map (as shown above).


    An Application map represents an Application node in the tree, displayed in a topology view, and is only needed for creating and updating the Application member. The leaf nodes in the topology hold the names of the configurations to be launched. Double-clicking on the leaf node in the tree (or even on the leaf node in the topology display) will launch its configuration.


    This is an example of the topology view opened when selecting “Display application map” for the “Operations” node. In the topology you can right-click on any node to create or copy nodes, move or rename nodes, and select or change the configuration to be launched from a leaf node (as in this example here):


    Selecting Change configuration name will display a dialog for you to select the configuration (from the user or site BBCDEF) to be launched from this leaf node.


    You do not have to specify anywhere which library it came from. When a configuration is launched from an Application tree (or from the topology map), the user BBCDEF is searched before the site BBCDEF for the configuration member. The presumption is that when you have finished testing, you can save the configuration(s) in the site library and also save the Application in the site library without having to update it further.


    When you want to save this Application member, use the XML toolbar icon (or drop-down menu item: Save application as XML).


    This will display a dialog where you can select the member name that will hold the XML. You can enter a name up to 7 characters, which will be pre-pended with an underscore (_) as the first character (you cannot actually enter the underscore). This will distinguish it from regular configuration member names in the BBCDEF dataset so that it will not appear in a list of configurations, only in a list of Application members when saving. In an ISPF display of the BBCDEF library this member will be listed and can be manually edited if necessary, but it cannot be created outside of MVE.


    You can save it in either the user or site BBCDEF library. You might want to test it in your user library first, and then save it later in the site library, whereupon it will be listed twice in the tree (the user one will have a “U” in parentheses). You can then right-click on the user one and select Delete application.


    The XML in the _OPS member will look something like this:


    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>  

    <!-- Application: _OPS -->                               

    <node name="Operations" linear="true">                  

      <node name="System">                                   

       <node name="System Overview" hyperlink=":BBWCFG01"/>  

       <node name="Syplex Histograms" hyperlink=":BBWCFG02"/>

       <node name="System MSU" hyperlink=":$AWMSU"/>         

       <node name="Storage">                                 

        <node name="DASD Overview" hyperlink=":AWDASD"/>     

        <node name="Space Analysis" hyperlink=":AWSPAC"/>    



      <node name="Database">                                 

       <node name="DB2 MSU" hyperlink=":DB2MSU"/>            

       <node name="IMS MSU" hyperlink=":IMSMSU"/>            





    This feature will be included in MVE Client PTFs BQY0186 (MVI 6.0) and BQY0187 (MVI 6.1), which will be available on eFix by May 9th. The bulk of this document will also be included in the “What’s New” notes, distributed in MVE with this PTF.