iteraplan 5.2 Documentation

Skip to end of metadata
Go to start of metadata

In the iteraplan Graphics Reactor, every iteraplan user can generate up-to-date customer-defined diagrams and reports. A user can create new diagrams and reports as a script file. He can upload it to the iteraplan server and make it available to all users. The script can process the full EAM landscape data, that is all building blocks and connections in the format that is also available as XMI export (Mass Data -> Export/Import in the iteraplan classic client).

The user can define the structure of the result: it maybe a enhanced diagram based on well-known visualizations (for example landscape diagram, masterplan), or a completely new type of diagram specific to the needs of the user. Also textual or tabular reports are possible. The technical format of the result is typically GraphML, SVG or HTML, but the Graphics Reactor is not technically limited to that.

The Graphics Reactor provides functionality for Extensible Stylesheet Language Transformation. Any kind of files can be uploaded, downloaded or deleted by the reactor. Running an execution XSL-file performes the transformation and creates new transformed files, which also can be downloaded.

User Interface

Using Graphics Reactor 

  • Click Upload File to put new file to the reactor

  • Choose an executable file from the dropdown list and click Start Reactor to perform the transformation
  • Messages recieved from xsl transformator during the execution were shown in the log below
  • After successful transformation the default output file (iteraplan.xml) download starts automatically
  • iteraplan.xml can also be downloaded by clicking button Download default output file
  • Select a file and click Download File / Delete File to download / delete the selected file

Use Cases

Multi-Building-Block-List

There are very simple use cases for reactor like listing all building blocks that have a high strategic value. An XSL script that does exactly that can look like this (publicDemo_htmlTable.xsl):

publicDemo_htmlTable.xsl
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:iteraplan="urn:iteraplan">
  <xsl:output method="html" indent="yes" encoding="UTF-8" omit-xml-declaration="yes"/>
  <xsl:template match="iteraplan:Container">
    [INFO] Content was written to publicDemo_strategicBuildingBlock.html which can be loaded from the file list on the right!
  	<xsl:result-document href="publicDemo_strategicBuildingBlock.html">
  	<html>
  	  <body><table>
  	  	  <tr>
  		  	<th>Building Block Type</th>
  		  	<th>Name</th>
  		  	<th>Strategic Value</th>
  		  </tr>
		  <xsl:apply-templates select="contents[number(@Strategic_32_value) > 8]" />
		</table></body>
  	</html>
  	</xsl:result-document>
  </xsl:template>
  
  <xsl:template match="iteraplan:Container/contents">
    <tr>
      <td><xsl:value-of select="substring-after(./@xsi:type, 'iteraplan:')" /></td>
      <td><xsl:value-of select="./@name" /></td>
      <td align="right"><xsl:value-of select="number(./@Strategic_32_value)" /></td>
    </tr>
  </xsl:template>
</xsl:stylesheet>

This piece is everything which is needed to print a simple HTML table of all building blocks having a value of more than eight (htmlTable.html):

 

 

From Business Down to the Bare Metal

This example visualizes the connection of business processes to infrastructure elements and includes all intermediate hops through the iteraplan meta model.

The result created by the iteraplan Graphics Reactor is an graphml file. You can open and view it with the free graph visualization tool yEd (get it here). Based on the sample data in iteraplan the result will look like this: iteraplan2.graphml.

 

The visualization is produced by the XSL Transformation publicDemo_fullModLink.xsl which you can execute yourself in our online demo.

It depicts all management processes in a nested structure. For the process "Customer Strategy" it lists all information systems (green) that are supporting this process. The next levels show the necessary technical components (blue) the information systems are built on and the underlying hardware (grey). Of course the XSLT can be easily adapted to show the same chain for other processes as well.

All nodes and connections are retrieved from iteraplan dynamically. The layout is then calculated automatically by yEd. For this example it is sufficient to open the result file with yEd and select Layout > Hierarchical with default settings. Once you have done this you will get a visualization as shown above.

You can utilize all kind of attributes to influence the appearance of this visualization.

 

Clustered Information Flow

This example clusters an information flow diagram according to information system domains.

As for the previous example the result created by the iteraplan Graphics Reactor is an graphml file. You can open and view it with the free graph visualization tool yEd (get it here). Based on the sample data in iteraplan the result will look like this: iteraplan3.graphml

 

The visualization is produced by the XSL Transformation publicDemo_simpleInfoFlow.xsl which you can execute yourself in our online demo.

Besides clustering the information systems the XSLT only renders information systems from the domain "Mgmt Apps" that have a connection to external systems or other systems in the same domain. Additionally the transported business object is included as well as label of the information flow.

All nodes and connections are retrieved from iteraplan dynamically. The layout is then calculated automatically by yEd. For this example it is sufficient to open the result file with yEd and select Layout > Flowchart with default settings. Once you have done this you will get a visualization as shown above.

You can utilize all kind of attributes to influence the appearance of this visualization.

 

Attributed Relationships

Another possibility to make use of the Graphics Reactor is to visualize attributed relationships like the one between information systems and business objects. In our demo data we have used this relationship to specify the operations a system performs on a business object (read, create, update, delete; usually abbreviated with CRUD).     

The script publicDemo_crudMatrix.xsl builds up a matrix of information systems and business objects that lists this kind of information. In case a system is connected to an object but no CRUD value is assigned, the field is filled with an X.

Together with a handful of CSS the reactor creates a nice table matrix.html (not filtered yet):

Permissions

A user must be logged in and have a role with the permissions "Access iteraplan via REST API" and "Use of the Graphics Reactor" in order to access it.

  • Make sure your transformation files are compatible with currently used XSL parser (Saxon-HE-9.6.0-5).
  • All users work in the same Graphics Reactor file area. In case of simultaneous script executions (by more than one user), the executions will be handled in accordance with the First-In-First-Out principle.
  • Make sure all uploaded files are UTF-8 encoded.
  • No labels