Previous Topic: AnnotationsNext Topic: Design Rule Check

Graphical User Interface › Infrastructure Editor › Editing Assemblies

Editing Assemblies

This section describes elements and editing capabilities that are available only when editing assemblies that are not the application top-level assembly (main).

The editing of an assembly is very much like editing and configuring application main.

To create and edit an assembly class

Drag the assembly template class from the New Singletons section of the catalog pane onto the canvas.

  1. Right-click the new assembly appliance shape and select Modify Boundary.
  2. Configure the boundary of the assembly class as you would for a simple class.
  3. Right-click the assembly appliance shape and select Modify Interior to edit the interior of the assembly.

    A canvas that contains shapes for the assembly as defined by the class boundary appears.

    Drag classes from a catalog or create new singleton classes as you would for editing the application main to create the infrastructure of the assembly.
    Note: To move around the assembly terminals, you need to click within the gray area on the terminal shape to select it and then drag it to the desired position on the canvas.

  4. Configure the assembly subordinate instances.
  5. Click Save to save your changes when you are all done creating and configuring the assembly interior.

    Note: After testing the assembly, you can move it to a catalog by clicking on the assembly class shape and dragging it to the appropriate catalog as you would do for a simple class.

In CA AppLogic® for System z, assemblies can be used in any place you would use a simple appliance. This makes it possible to reuse infrastructure without increasing the complexity of the application. For example, a specialist in database clustering can create a "stock" assembly for clustered database deployment like the one shown above and publish it in a catalog.

Application integrators can then use this assembly in multiple applications, whenever they need database scalability or high availability, and without having to know how exactly the cluster is set up and operates.