Preparing Projects in Developer

To prepare the projects of the destination and originating applications, perform the following procedures. These procedures apply to Agile Business Suite applications only.

Destination Application

For the destination application (receives automatic entries):

  1. For each ispec that is to receive data, select True for the Automatic Entry Capable property.

  2. Use the attributes Glb.Origin, Glb.Originhost, and Glb.Originenv to identify the source of a transaction, if necessary. Refer to the Agile Business Suite Developer Online Help for more information on built-in attributes.

  3. Generate and deploy the application.

Originating Application

For the originating application (sends automatic entries):

  1. Create an external class. This class must have the same attributes as the receiving ispec in the destination application.

    Note: This class must not only have the same name, attributes as the receiving ispec class, but also must have the same Alias name as the receiving ispec class.

  2. Decide whether to use two-phase commit. Set the Two Phase Commit configuration property for the segment. You can override this setting in logic, by using the attribute Glb.TwoPC.

  3. In the logic of the class that initiates the external automatic entry, define the appropriate attributes, as follows:

    For an external automatic entry to an application:

    • Move the application view name defined in the Runtime Administration Tool to Glb.Destination.

    • Assign the runtime SQL database name to Glb.Destenv.

    • Move the runtime server IP or the host name for the destination application to Glb.Desthost.

    • Use Glb.TwoPC to override the setting of two-phase commit, if required.

    • Define attributes on an instance of the class and call the Send built-in method on that class.

    • Test Glb.Status and Glb.Hubstatus for possible errors.

    For an external Automatic Entry to a NOF program:

    • Move Non Format to Glb.Destination.

    • Move the name of a script to Glb.DestNoForm. The name must not contain period (.), hyphen (-), backslash (\), or slash (/) characters.

    For an internal automatic entry, Glb.Destination is equal to Glb.Spaces or Glb.Self.

    Refer to the Agile Business Suite Developer Online Help for more information on various built-in attributes.

    Note: If communicating with an application created with Enterprise Application Environment 3.3, or earlier, you are limited to 2000 bytes when transferring data using external automatic entries.

  4. Generate and deploy the originating application.