Workstation View

The Workstation view shows the local modules, if any, previously registered on the workstation in a hierarchical tree. If you have not yet registered any modules to your workstation, this view is empty.

To open the local workstation view, choose File->Open Workstation from the menu bar or click on the workstation toolbar button.

To register an object on the local workstation you must have both the Repository and Workstation views open. Select the object on the Repository panel, and choose from the menu bar Workstation->Add Module or Workstation->Add Interface, respectively.

To remove an object from the local registry, select the object on the Workstation panel, and choose Workstation->Remove from the menu bar.

The Workstation view consists of the two panels (Object Tree and Sample Code panels) and two view modes (synchronous and asynchronous). These features are discussed below.

• Object Tree (Top Panel)-The top panel of the workstation view shows the objects that have been registered on the local workstation in the same hierarchical tree format used in the Contract Repository-as modules, interface objects, operations (TUXEDO services), and the parameters contained in the operations. (For an explanation of the objects, see Table 2-1.) The workstation view includes only locally registered objects.

• Sample Code (Bottom Panel)-The bottom panel of the workstation view shows the sample code for the currently selected object. The sample code is generated in the language of the client tool you specify as the default from the drop-down combo box on the main window tool bar. (See Specifying the Target Client Tool for Sample Code.) In addition to indicating the client tool language (Visual Basic, Visual C++, or PowerBuilder), you can specify numerous other sample code default options that control how the sample code gets generated (Tools->Options on the menu bar, Sample Code tab).

• Synchronous Mode-In the examples shown so far, the objects on the local workstation have been shown in synchronous mode. (To switch back to synchronous mode from asynchronous mode, choose View->Sync from the menu bar. The workstation view must be open.)

  In synchronous mode, the requestor (in this case, the operation) waits for a reply from the server in the form of an output parameter. On the Workstation Objects window, synchronous services are shown with input and output parameters. Synchronous objects are the default Workstation view. (Figure 2-1 shows the workstation objects in synchronous mode.)

• Asynchronous Mode-You can also specify objects in asynchronous mode by choosing View->Async from the menu bar. (The workstation view must be open.)

  When calling a TUXEDO service asynchronously, an asynchronous operation contains only input parameters but no output parameters-instead, the information comes back as output parameters of the reply object operation. As shown on the Workstation Objects window, asynchronous operations are named differently (the suffix Async is attached to the operation name) and the output parameters are returned in the operation reply objects. Notice that the sample code for an asynchronous operation contains events that indicate the replies. Figure 2-2 shows the workstation objects in asynchronous mode.

  Caution: The naming conventions you use for operations (also known as services) can affect asynchronous mode. Do not include underscore characters in operation names that you want to call in asynchronous mode. Async mode does not work properly if the operation name includes an underscore.

  Figure 2-2 Workstation Objects in Asynchronous Mode

  

In the figure, the module BANKAPP is expanded to show the asynchronous operations contained in the TELLER interface. Note that the asynchronous operations are named in the form OperationNameAsync. The sample code shown returns the requested values as output parameters of the selected reply object operation.