Tasks

This Help topic includes the following sections:

• Loading CORBA Interfaces into the Interface Repository

• Starting Application Builder

• Creating ActiveX Bindings for CORBA Interfaces

• Changing the Settings for Creating ActiveX Bindings for CORBA Interfaces

• Creating Deployment Packages

• Changing the Directory Location for Deployment Packages

• Changing the Settings for Creating ActiveX Bindings for CORBA Interfaces

• Changing the Default Directory Locations

• Filtering Objects Displayed in the Main Window

• Displaying Properties

 

---

Loading CORBA Interfaces into the Interface Repository

Before you can create an ActiveX view of a CORBA object, you need to load the interfaces of the CORBA object into the Interface Repository. If the interfaces of a CORBA object are not loaded in the Interface Repository, they are not displayed in the Services window. If a desired CORBA interface is not displayed in the Services window, use the idl2ir command to load the Object Management Group (OMG) Interface Definition Language (IDL) for the CORBA interface into the Interface Repository. The syntax for the idl2ir command is as follows:

idl2ir -f repository-name file.idl

The following table describes the options for the idl2ir command.

Option	Description
-f repository-name	Loads the OMG IDL files for the CORBA interface into the Interface Repository. Specify the Interface Repository that is in the same BEA Tuxedo domain as the ActiveX client application.
file.idl	Specifies the OMG IDL file containing definitions for the CORBA interface.

 

For a complete description of the idl2ir command, see the CORBA Programming Reference in the BEA Tuxedo online documentation.

 

---

Starting Application Builder

To start the Application Builder:

1. Click the BEA Application Builder icon in the BEA BEA Tuxedo System program group.

   A logon window appears.

2. Enter the host name and port number that is specified in the ISL parameter in the UBBCONFIG file. You must match exactly the capitalization used in the UBBCONFIG file. See Figure  4-1.

   Figure 4-1 Connecting to the IIOP Listener

   
    

   The Application Builder window appears. All the CORBA interfaces loaded in the Interface Repository appear in the Services window of the Application Builder.

 

---

Creating ActiveX Bindings for CORBA Interfaces

To create an ActiveX binding for a CORBA interface:

1. In the Application Builder window, highlight the desired CORBA interface in the Services window.

2. Drag the desired CORBA interface to the Workstation Views window, or cut the CORBA interface from the Services window and paste it into the Workstation Views window.

   The Confirm View Creation window appears.

   
    

3. To create an ActiveX binding for the CORBA interface, click Create.

   The Application Builder creates the following:

   • A type library. By default, the type library is placed in \tuxdir\TypeLibraries.

     The type library file is named: DImodulename_interfacename.tlb.

   • A Windows system registry entry, including unique Program IDs for each object type, for the CORBA interface.

You can now use the ActiveX view of a CORBA object from an ActiveX client application.

 

---

Changing the Settings for Creating ActiveX Bindings for CORBA Interfaces

Use the Workstation Bindings tab page on the Options window to change the settings used to create ActiveX bindings for the interfaces of CORBA objects. To get to the Workstation Bindings tab page, click Tools->Options.

Table  4-1 describes the options on the Workstation Bindings tab page.

Table 4-1 Workstation Bindings Tab Page Options  

Option	Description
Workstation Bindings Options	Lists the types of bindings that can be created for the interfaces of CORBA objects. A check mark appears next to the type of bindings to be created.
Generate COM Views on Workstation Drop	Creates COM bindings for the interfaces of CORBA objects. This release of the ActiveX Client does not support COM views of CORBA objects in a BEA Tuxedo domain.
Generate OLE Automation Views on Workstation Drop	Creates ActiveX bindings for the interfaces of CORBA objects.
Create ActiveX Controls for OLE Automation Views	Adds the necessary interfaces to a CORBA object so that the CORBA object can be used as an ActiveX control. It also registers the CORBA object as an ActiveX control. The CORBA object can then be used in ActiveX Control container applications.
Output Folders	Specifies a directory location for the bindings that are created for the interfaces of a CORBA object.
C++ Headers	C++ header files need to be located in your computer's defined path so that they are compiled properly. By default, the files are placed in: \tuxdir\Include You can click the Browse button to search for a directory location.
MIDL/ODL Files	Microsoft Definition Language (MIDL) and Object Definition Language (ODL) files are for reference only and can be placed anywhere on your computer. By default, the files are placed in: \tuxdir\TypeLibraries You can click the Browse button to search for a directory location.
Type Libraries	Type libraries are registered with a complete directory path and can be placed in any directory that is always available to a client computer. By default, the files are placed in: \tuxdir\TypeLibraries You can click the Browse button to search for a directory location.

 

 

---

Creating Deployment Packages

To distribute client applications to other client computers, you need to create a deployment package. A deployment package contains all the data the client application needs to have to use ActiveX views of CORBA objects, including the bindings, type libraries, and registration information. The deployment package is a self-registering ActiveX control with the file extension .ocx.

To create a deployment package for an ActiveX view of a CORBA object:

1. Select an ActiveX view from the Workstation Views window.

2. Click Tools->Deploy Modules or click the right mouse button on the desired view and select the Deploy Modules option from the menu.

   The Confirm Deployment window is displayed.

   
    

3. Click Create to create the deployment package.

   By default, the deployment package is placed in \tuxdir\Packages.

 

---

Changing the Directory Location for Deployment Packages

Use the Deployment Packages tab page on the Options window to change the directory location for deployment packages for ActiveX views of CORBA objects. To access the Deployment Packages tab page, click Tools->Options. The current directory location for the deployment packages is displayed. The default location is \tuxdir\Packages.

 

---

Changing the Default Directory Locations

The Application Builder provides default directory locations for C++ header files, MIDL and ODL files, and type libraries. You can change those directory locations.

To change the directory locations:

1. From the Tools menu, select the Options option.

   The Options window is displayed.

2. Choose the Workstation Bindings tab on the Options window.

   The default directory location is displayed in the C++ Headers, MIDL/ODL Files, and Type Libraries fields.

3. Select the specification for the desired output directory and delete it.

4. Either enter a new directory specification or click the Browse button to search for a new directory.

5. Click OK to save the change.

 

---

Filtering Objects Displayed in the Main Window

Use the Display tab page on the Options window to filter the types of objects displayed in the Application Builder main window. By default, CORBA interfaces and modules are displayed.

 

You have the option of also displaying the following types of information:

• Data types

• Methods

• Arguments

• Properties

• Exceptions

Use the Include System Objects option to enable the display of a specific set of definitions in the Interface Repository, for example, CosTransactions.

To display additional information in the Application Builder main window, click the desired options and click OK.

 

---

Displaying Properties

Use the Properties window to display one or more pages listing the properties of the selected adapter, module, or interface. The content of the Properties window is object specific.

 

Table  4-2 describes the possible properties.

 

Table 4-2 Description of Properties

Property	Description
Interface->Name	The name of the selected CORBA interface.
Interface->Type	The type of object. For example, interface, module, or exception.
Adapter->Name	The name of the object system. For this release, this option appears as BEA Tuxedo version 8.0.
Adapter->Vendor	The name of the vendor of the object system. For this release, this option appears as BEA Systems.
Adapter->Platform	The version of the object system. This option appears as version 8.0.
Exposure	Describes the source object system of the object. For example, BEA Tuxedo.