IDL Java Code C++ Code Files

Report Tool

The Report GUI is the primary front end for the user. It is a pure client of the different components, offering now distributed services of its own. Thus there is no IDL for it.

The interface is developed in Java. It initially attempts to determine the available databases to which it can attach by asking CORBA for a list of registered the objects of class WaferDatabase (the IDL class).

The list of databases is then used to create radio buttons at the top of the interface. When the user selects a database by clicking on the associated radio button, the application obtains a reference to the appropriate remote database (the name associated with the radio button is adequate based on the Dynamic Determination of the Available Databases). Then it invokes the objects() method for that database and inserts the resulting lot names into the List widget.

At this point, the user can generate reports for a given lot by selecting a lot name from the list and selecting a report type from the radio buttons below the list. To generate the report, they press the Create Report button. The event handler obtains a reference to the WaferGraphics Server and invokes the appropriate method for that object as described in the IDL definition of the WaferGraphics Server.

The Plot, BoxWafer and Pareto buttons are simple methods that require only the names of the lot and database. The code is as follows (from generateReport) and assumes the the Sserver is a reference to the WaferGraphics Server, lot is the selected lot from the list and db_name is the current database name.

      if(type.equals("plot")) {
         Sserver.plot(lot, db_name);
      } else if(type.equals("boxwafer")) {
         Sserver.boxwafers(lot, db_name);
      } else if(type.equals("pareto"))  {
         Sserver.pareto(lot, db_name);

The histogram invocation is different and requires extra steps from the WaferReport application. The arguments to the histogram method are the name of the lot selected by the user (used as a label for the plot) and an array of doubles representing the bin counts for the histogram. This is obtained from the database using the yield() method with the wafer name.

This is implemented in the code as:

      } else if(type.equals("yield histogram")) {
 
          // this is special since we compute the yield and
          // pass it to S.


          // Get the current database and narrow it to 
          // a wafer database. Then, compute the yield.

          SServices.WaferDatabase db = list.currentDatabase();
          double[] yield = db.yield(lot);

          // plot the histogram remotely.
         
      Sserver.histogram(items[0], yield);
     }

Determining Available Databases.

While it is possible to have the user specify in which databases s/he is interested, it is nicer to have the GUI probe the distributed environment looking for the available databases and providing this list to the user. Visigenic allows us to do this with the LocationService. This is implemented in DynamicLocationChoices.java Its use is very similar to the NamingService.
  1. One uses resolve_initial_references() with the string "LocationService" and narrow the object to the ObjLocation.Agent class.
  2. Next, one requests a list of descriptions of objects of a implementing a particular IDL class using the ObjLocation.Agent method all_instances_descs()
  3. Finally, iterate over this array extracting the instance_name field to obtain an array of Strings identifying the databases. These can be passed to the Naming Service to obtain a reference to that instance.

How do we do this in other ORBs? More on this in the future.

Files

ChoicesPanel.java
Base class for displaying buttons providing selections. See the ReportTypeChoices and LocationChoices and classes.
ErrorDialog.java
Provides the message area at the bottom of the interface window.
HoldingPattern.java
Displays the Lucent logo in the top corner.
LocationChoices.java
Base class for displaying the available databases. See DynamicLocationChoices.java also .
ReportTypeChoices.java
Panel for displaying and processing user actions related to which type of report the user has selected.
Task.java
Support for threaded version of remote invocations to allow the GUI to proceed. This is necessary if we want to allow the user cancel a request.
WaferList.java
Provides the lot/map selection list.
WaferReportApp.java
The main class which runs the application. This constructs the interface and connects to the ORB and BOA.
DynamicLocationChoices.java
Dynamically queries the ORB at startup time to determine the available databases.

Support Files

images/L[1-10],gif
directory containing the Lucent Logo that spins in the top right corner of the interface.

Optional Features

The event mechanism is not supported by OmniBroker.
EventHandler.java
DBEntryListener.java
Event monitor listening for database activity in the form of new lots being added to a database.

Duncan Temple Lang <duncan@research.bell-labs.com>
Last modified: Sat Jan 18 18:48:26 EST 2003