The "MetalWorks with Build Audit" Workflow

 

Table WF-6 will walk you through the steps of executing the MetalWorks with Build Audit Workflow.  This Workflow performs a Java build using a Java Jar Build Services and mimics a deployment process by launching the Metalworks application.  It also creates a Build Audit Report and performs Impact Analysis

 

Note:  This Workflow requires that you have a JDK installed.  You can install the JDK by going to https://java.sun.com/.  You need the Java Standard Edition JDK for compiling and running the Metalworks application.

 

Once you install the JDK you will need to set your JAVA_HOME directory in your machine's environment variables to the location where the JDK was installed.  For example:

 JAVA_HOME=C:\Program Files\Java\jdk1.5.0_11

 

 

Table WF-6  MetalWorks with Build Audit

Step

Action

1

Be sure you install the Java Standard Edition JDK for compiling and running the Metalworks application before you execute this workflow. You can install the JDK by going to  https://java.sun.com/.  You must also set your Java Home directory as described above.

2

From the OM Workflow perspective, go to the Workflow Explorer.  Expand on the Public Workflow node and double click on "MetalWorks with Build Audit".

3

Select the Activities tab to go to the Activities View.  Double click on the "MetalWorks with Build Audit" Activity.  This Workflow executes five (5) Activities that will execute the build occurring in the c:\build directory.

4

Review each Activity.  Select the Activity Execute Meister Clean All Build. Expand the Dependencies node on the right hand side of your Screen.  Notice that this Activity is dependent upon the Generate Build Control File for Metalworks Activity.

5

Go to the Overview tab and click on Execute.

6

View the Workflow progress using the Workflow Monitor at the bottom of your Screen.  You will notice that each step is displayed in Yellow as it executes.  Red indicates there was an error.  Orange indicates that a dependent step failed.

7

Before the Workflow completes, the Metalworks application will launch. Notice in your Workflow Monitor that the Workflow has not completed as long as Metalworks is still executing.  This demonstrates how the Workflow Monitor watches each process as it executes. 

8

Close Metalworks and notice that the Workflow will now be reported as "complete".

9

View the logs by going to the OM Reports perspective and viewing the Workflow Log Explorer.  Expand the nodes Metalworks with Build Audit – Today – My Computer.  Select the log.  If you do not see your log, select the refresh icons (two circular arrows) to refresh your data from the Knowledge Base Server.

10

The log will display the results of each Activity in the Workflow.

11

View the Build Audit Report by going to the OM Reports perspective and viewing the Reports Explorer.  Expand the nodes Build Audit – Metalworks with Build Audit – Today - My Computer.  You will see your report based on the date and time the report was generated.  Notice in the Build Audit Report that rt.jar is included in the report.  This is important to note as a traditional Bill of Material report that relies on an SCM tool would miss this library. Also, notice the complete listing of artifacts used in the Build Audit, regardless of the fact that a SCM tool was not used for the build.

12

View the Impact Analysis Reports by selecting Impact Analysis – Implosion or Impact Analysis – Explosion.  Expand the nodes for the Metalworks with Build Audit Workflow to view the Impact Analysis report in either the Implosion view – seeing the dependencies from the source code to the binary, or the Explosion view- seeing the binary to the source code.