com.ibm.pdp.maf.rpp.pac.segment
Interface LogicalViewComponent

All Superinterfaces:
AbstractCELines, CELines, Element
All Known Subinterfaces:
LVDataElementComponent, LVGroupComponent, LVSegmentComponent

public interface LogicalViewComponent
extends AbstractCELines

Indicates that the component is specific for Logical View.


Field Summary
static java.lang.String copyright
           
 
Method Summary
 LogicalViewDataTypeValues getDataType()
          When a Client calls a selection service, this service can implement an extraction method and its parameters by value.
 int getOccurs()
          The -CE Lines are used to identify the elements which compose the current Segment.
 LogicalViewPresenceCheckValues getPresence()
          This indicates whether the presence of the DataElement is required or optional.
 SubSchemaAssignement getSubSchemaAssignement()
          Indicates in which subschema the component is called.
 TransferDirectionValues getTransferDirection()
          For each Data Element called in a Logical View, you must select the data transfer direction between the client and the server.
 
Methods inherited from interface com.ibm.pdp.maf.rpp.pac.segment.AbstractCELines
getGCLines, getGELines, getGGLines, getMoreControls
 

Field Detail

copyright

static final java.lang.String copyright
See Also:
Constant Field Values
Method Detail

getDataType

LogicalViewDataTypeValues getDataType()

When a Client calls a selection service, this service can implement an extraction method and its parameters by value. The Business Component which answers the call must recognize the extraction method and its parameters to correctly perform the service. The only way to send this information is through the message sent by the client.

The extraction method is sent to the Business Component through the technical part of the message. Parameters must be described in the application part of the message, that is in the Logical View.

In the Data type field, you specify the parameters by value for all the extraction methods which can be used by the Logical View. To do so, you call Data Elements defined in the Pacbase repository. For each parameter, you enter the E type, which indicates that it is a parameter. Each identifier Data Element (U type) is an implicit parameter. The other Data Elements that describe the contents of the Logical View cannot be used as parameters. The E-type Data Element does not belong to the description of a Logical View. If necessary, you can define and call a child Data Element.

Returns:

getOccurs

int getOccurs()

The -CE Lines are used to identify the elements which compose the current Segment. You can create in a table Data Element calls, Segment calls, undefined Data Elements, Data element groups and add fillers.

Returns:

getPresence

LogicalViewPresenceCheckValues getPresence()

This indicates whether the presence of the DataElement is required or optional.

Returns:

getSubSchemaAssignement

SubSchemaAssignement getSubSchemaAssignement()

Indicates in which subschema the component is called.

Returns:

getTransferDirection

TransferDirectionValues getTransferDirection()

For each Data Element called in a Logical View, you must select the data transfer direction between the client and the server.

The direction of the transfer must also be indicated in the group Data Elements. The repeated Data Elements must have the same transfer direction. This direction can only be indicated on the Data Elements bordering the repeated data (Data Element with R indicator). You enter the C or S value in this Data Element only if the Direction of transfer field in the Logical View Definition tab is both directions.

Returns: