Previous Topic: Associate Character NamesNext Topic: CSE Generation


Toolset Generation

Only cooperatively packaged Server Manager load modules are eligible for proxy generation. A model does not need to have a client defined. A proxy is a generated programmatic interface of a Server Manager.

The following steps describe how to generate a proxy. This example uses Toolset Menu navigation to designate diagrams and dialogs. You can use alternate navigation techniques to achieve the same result.

Follow these steps:

  1. Start the CA Gen Toolset.
  2. Click Tools, Construction, Generation or Packaging to open the Generation or Packaging Diagram.
  3. To open the Cooperative Code definition, click Diagram, Open, Cooperative Code.
  4. To set the parameters of the Server Manager execution environment, select the Business System and click Details, Server Environment.

    The Server Environment Parameters dialog opens where you can define the parameters.

    Note: Server Environment Parameters can be set at the Business System level or for each individual Server Manager. If the Server Environment Parameters are set at the Business System level, they become the default setting for each Server Manager within the Business System.

  5. Click Diagram, Open, Proxy Code.

    The Proxy Code Generation dialog opens.

    Proxy Code Generation

    1. From the Component Type list, select either CBD 96 or Server Load Module to generate proxies for models that are not formatted according to CBD component standards. For components that conform to CBD 3.0 standards. Select Custom Proxies to generate custom proxies designed using CA Gen Studio

      Note: When a model does not contain any CBD or CBD 96 component, but contains cooperative server load modules, the Server Load Module component type is automatically selected.

    2. From the Component list, select one or more components you want to generate. When multiple components are defined for a single model, you can select one or more of these components for generation. If you have selected Custom Proxies in the previous list, the custom proxies that were defined in CA Gen Studio are displayed here. For information about defining custom proxies, see Gen Studio Overview Guide.

      Note: The Generation process always generates all interfaces and methods associated with the selected component.

    3. From the Operating System list, select WINDOWS, JVM, UNIX, or CLR.

      Note: The Java proxy generates only for the JVM operating system. The Windows Build Tool builds the generated code, and you can deploy it to any Java-compliant environment.

      From the Target Proxy Type list, select the type of generated code you want for the proxy.

    4. From the Type of Installation list, select Local or Remote.

      For a Remote install, generated files are packaged into one installation file that you can manually transfer to any target system. For a Local install, generated files are compiled and prepared for copying onto a server running on the same type of machine as the Toolset. The default is Local.

    5. Under Additional Programming Interfaces, select any of the optional APIs that need to be generated into the proxy. These include:
      • Support for Asynchronous flow to the Server Manager
      • Support for a user-written application to use XML to process import and export views.

      Note: The Additional Programming Interfaces option is disabled when generating C Proxies. The C proxy is a generated C language header file. The C proxy runtime provides the supported programming interfaces.

    6. For ActiveX/COM only, select Automatically generate missing UUIDs (Universally Unique identifier) if you want CA Gen to automatically create any missing UUIDs.

      By default, this option is selected. ActiveX/COM proxies require a UUID for each component, interface, and method objects.

      To specify the missing UUIDs manually, click Properties.

    7. For Java proxy generation only, select Use Classic Style API for Java proxy. By default, the new object oriented Java proxy API is generated. Therefore, by default it is not selected.

      Note: This option is disabled if you have selected Custom Proxies option for Component Type.

    8. To automatically start the Build Tool following the generation of a proxy, select Install after generation.

      Note: The Install after generation option is disabled when generating C Proxies. The C proxy is a generated C language header file. The C proxy does not need the Build Tool, as the generated source code is compiled by the user.

    9. To start generation of the proxy following the selection of all the parameters, click Generate.

      Note: Generation fails if proper licensing does not exist for the proxy.

    On successful generation, the Generation window displays the following message:

    Generation Window

    The Build Tool appears and a successful build displays a Build-OK message.

    Build Tool Window

The following table lists the Target Proxy Type options for a given operating system:

Operating System

Target Proxy Type

Windows

ActiveX/COM, C

JVM

Java

CLR

.Net

UNIX

C

More information:

.NET Proxy

Java Proxy

Java Proxy (Classic Style)

COM Proxy

C Proxy