This document describes following sections:
To start the IDL Extractor for Integration Server
The IDL Extractor is a New Wizard in Eclipse. Choose New from the file menu, select IDL Extractor for webMethods IS in the following page and choose Next.
Note:
You can also chose New from the toolbar or
context menu of a view showing resources. Also Ctrl-N starts the
selection of the New Wizards.
If you are using the wizard for the first time without any predefined Integration Server connections, continue with Step 2a: Create a New Integration Server.
Or:
If Integration Server connections are already defined (see Integration Server Connections), or you want to communicate with an
additional Integration Server, continue with
Step 2b: Use an Existing IDL Extractor for Integration Server Connection.
To create a new Integration Server connection
Define the new Integration Server connection on the following wizard page.
Notes:
Choose and continue with Step 3: Select the Integration Server Package to Extract.
To use an existing Integration Server connection
Select Choose an existing Integration Server Connection and an Integration Server connection from the list.
The selected connection is verified by a
ping command. If the response is valid, the
button is enabled. If invalid, an error message
is displayed.
Continue with Step 3: Select the Integration Server Package to Extract.
To create an additional Integration Server connection
Select Create a new Integration Server Connection and continue with Step 2a: Create a New Integration Server.
To extract the IDL from the selected package
Select the package to extract (from the field indicated by Source), for example the package "Default" in the screen above.
Specify the target. By default, the wizard tries to find a valid container based on your position in the Navigator or Package Explorer View.
Or:
Choose to select a container from
your workspace.
Notes:
Optimize the extracted IDL for usage with the COBOL Wrapper, Natural Wrapper, PL/I Wrapper or other EntireX Wrapper (see EntireX Wrappers). Use the combo-box and select the target programming language:
COBOL
Enter the default length for IDL type A(default-length) fields which map then to COBOL alphanumeric data items PIC X(default-length) if in a subsequent step the COBOL Wrapper is used.
Natural
Choose one option indicated by Map Integration Server data type to IDL:
alphanumeric with variable length: Extract to IDL Type AV fields which map then to Natural DYNAMIC data types if in a subsequent step the Natural Wrapper is used. The interface does not have any length restrictions.
alphanumeric with fixed length: Extract to IDL Type A(default-length) fields which map then to Natural fixed-length alphanumeric data types if in a subsequent step the Natural Wrapper is used.
The interface from a Natural point of view is more legacy-like and easier to program, but there are length restrictions.
PL/I
Enter the default length for IDL Type A(default-length) fields which map then to PL/I fixed-length alphanumeric fields CHAR (default-length) if in a subsequent step the PL/I Wrapper is used.
Other
If you later use wrappers other than the COBOL Wrapper, Natural Wrapper or PL/I Wrapper no options need to be specified.
If Prefer Alias names to ensure library/program names with a maximum length of eight characters is checked, IDL library and program names are generated with eight uppercase characters and the original name is used as an alias.
Clear Create Listener Objects in Integration Server to only extract the IDL file from the package. The wizard finishes after extracting the IDL.
Tip:
This is useful if you want to modify the IDL (manually) before
generating clients. In this case, the connections and listeners have to be
created in a separate step. See Step 4b: Define Adapter Services for an RPC Listener or a Reliable RPC Listener.
Choose to store the IDL file in the selected container in the Eclipse workspace.
Notes:
To select the connection type
As a prerequisite, the IDL file has been stored in the workspace and the button is now disabled.
Select a Connection type and click .
Notes:
IN parameters.
To define a listener
Select an Integration Server package where the listener will be stored.
Specify the names for Folder Name (default:
library name), Connection
Name (default: library
nameConnection) and Listener Name
(default: library nameListener).
(This step is not recommended. Only perform it if required.) You can alter the Integration Server services in the table headed by the RPC Program Name and IS Service Name. Note that a selected service must exist in some package of the Integration Server!
If necessary, edit the Broker settings for the Listener (Broker ID, Server Address, User ID, Password, and Encoding).
The check box Overwrite existing Objects in Integration Server can be used to re-generate the objects after you have changed the IDL file.
Notes:
WmEntireX) with the version currently used.
Choose .
As a result, the following objects will be created:
one connection of type EntireX RPC Listener, EntireX Reliable RPC Listener or EntireX Direct RPC Listener;
one listener object.
For a connection of type EntireX Reliable RPC Listener the following objects will be created in addition for each IDL program:
one notification object;
one trigger object;
one document type object.