EJB

Enterprise JavaBeans implements HookableInterface (by extending HookableInterface in its Interface class). HookableInterface requires that the Bean class implements an execute() method. This method is what the system executes when a hook point occurs. This is used primarily in non-GUI situations. Java Class activities are simpler than these EJB activities, but the EJB activities have more capabilities.

Java Class

A basic class that implements HookableInterface. HookableInterface requires that the implementing class implements an execute() method. This method is what the system executes when a hook point occurs. This is used primarily in non-GUI situations.

Standalone GUI (.jsp)

Any non-hook point, non-plug-in .jsp. These are activities listed in the Activity Manager. For example, Shop Order Maintenance, Create and Release SFC Number, and SFC Status report.

Button/Plug-In GUI (.jsp)

Button (.jsp): A .jsp file that executes when the user chooses a particular pushbutton in the Standard POD. The file is associated with the button by the activity name entered in the Activity column on Buttons tab page of POD Maintenance (see Defining POD Pushbuttons and Pushbutton Groups).

Rich Plug-In GUI

An activity (Java class) developed using the Rich POD technology. This technology allows data to be exchanged between the client and server without always requiring a screen refresh. The Program or Class Name field is a Java class in the case of a Rich POD activity.

Native Executable

A native program or script (server only) that is executed when this unit is triggered. This could be a batch (.bat) file or an executable (.exe) file on a Windows system or a script or executable file on a UNIX system. These files are run from the command line and cannot be used as GUI activities.

Collaboration Data Acquisition Plug-In

A Collaboration plug-in (Java class) that acquires data in addition to the standard data that a system triggering action publishes. These are non-GUI activities that are used when collaborating with external systems such as an ERP system.

Collaboration Format Plug-In

A Collaboration plug-in (Java class) that formats the data that a system triggering action publishes, and any additional data acquired, if a Data Acquisition plug-in is specified in Collaboration Directive Maintenance (see Collaboration Directive Maintenance). These are non-GUI activities that are used when collaborating with external systems such as an ERP system.

Collaboration Transport Plug-In

A Collaboration plug-in (Java class) that sends the data that a system triggering action publishes using a specific transport mechanism. This data may include additional data if a Data Acquisition plug-in is specified in Collaboration Directive Maintenance. This data may also be in a particular format if a Formatting plug-in is specified in Collaboration Directive Maintenance.

These are non-GUI activities that are used when collaborating with external systems such as an ERP system.

Collaboration Callback Plug-In

A Collaboration plug-in (Java class) that facilitates the reusability of the business logic for parsing and processing responses from remote systems. If specified, the callback is triggered immediately after the Transport plug-in.

The Callback plug-ins make it possible to create generic transport plug-ins that deal only with transport aspects. These are non-GUI activities that are used when collaborating with external systems such as an ERP system.