WS: TF: A9.3 Generic Exit Functions (Doc ID 1478037.1)

Last updated on DECEMBER 01, 2016

Applies to:

JD Edwards World Technical Foundation - Version A9.3 and later
Information in this document applies to any platform.

Goal

 To provide information on the creation, setup and use of Generic Exits.

Understanding the differences between using Generic Exits from a PC based (Client Access) or a Web based (Web Enablement) client.

When using Generic Exits from a green screen client, such as Client Access, the program is running local to the PC (executed from the PC), so when referencing a path like "C:\MyDocs" within Generic Exits, the PC knows what this is, as it is running locally.  Using Generic Exits via Web Enablement, the System I is running the process and does not know what "C:\MyDocs" is as it has no reference for "C:\" (or anything on a PC).  Generic Exits was not intended to launch PC programs or documents that reside on a users local drive, but instead to use World fields (data) to build a reference (like a URL) and access it through a HTTP server.  Our recommendation to make Generic Exits available to both the green screen and Web Client is to place the document or program on the iSeries in a path where the HTTP server resides.  For example: iSeries name or ip address (IFS root)/www/apachedft/htdocs.  This way, access to the documents is through a URL (http://My_Isereies/Docs/My_Report.pdf for example) and that can be accessed by any system on the network (iSeries or PC).  In addition, the PC knows what to do with an object named .PDF (or .DOC, .TXT etc) so there is no need to execute a PC program (Adobe Reader for example) to open a file.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms