pub:dwtinstructions
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
pub:dwtinstructions [2018/03/15 10:19] – created ken | pub:dwtinstructions [2018/03/15 10:50] – ken | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | < | ||
+ | |||
===== DocWareTool ===== | ===== DocWareTool ===== | ||
- | The ESNDDTAQ API command is used to send PDF file path to data queue which is being listened by client programs. The command | + | The execution commands: |
+ | |||
+ | **java -cp ifdclient.jar com.ifd.customers.americansteel.DocWareTool -indir** <cabinet folder> -**outdir** <output folder which contains | ||
+ | {{ : | ||
+ | |||
+ | The executable | ||
+ | |||
+ | For example, I have a folder called **cabinets** which contains 2 sub folders: **cabinet-01** and **cabinet-02 | ||
+ | ** | ||
+ | {{ : | ||
+ | |||
+ | In **cabinet-01**: | ||
+ | |||
+ | In **cabinet-02**: | ||
+ | |||
+ | After run command:{{ : | ||
+ | |||
+ | Look into **output** folder:\\ | ||
+ | **cabinet-01** | ||
+ | {{ : | ||
- | < | + | **cabinet-02** |
- | Send data to keyed data queue (ESNDDTAQ) | + | {{ : |
- | + | ||
- | Type choices, press Enter. | + | |
- | + | ||
- | Key value . . . . . . . . . . . | + | |
- | + | ||
- | Data value . . . . . . . . . . . | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | Data Queue . . . . . . . . . . . | + | |
- | | + | |
- | + | ||
- | + | ||
- | </ | + | |
- | The ESNDDTAQ command has 3 parameters: | ||
- | * **Key**: A unique key defined by user. Each Window client should have a unique key for it to differentiate with other clients. This value can be user ID of that machine or PC ID | ||
- | * **Data**: This field contains the IFS qualified path of PDF file that server wants to open on client machine | ||
- | * **Data Queue**: The data queue is used to communicate between server and client. This data queue is monitored by client programs. | ||
- | |||
- | For example, open PDF file / | ||
- | ESNDDTAQ KEY(USER01) DATA(‘/ | ||
- | The client program is a .JAR file developed in Java language to connect to iSeries and monitor a data queue by a unique key for PDF file. Once the data in data queue is found, client program will download the PDF file to temporary folder in Windows and invoke PDF reader (configured in parameter) to show PDF file on Window machine | ||
- | The compressed file contains 2 files: | ||
- | * **IFDCLIENT.JAR**: | ||
- | * **IFDCLIENT.BAT**: | ||
- | IFDCLIENT.JAR is started with the following parameters: | ||
- | * **print**: print the parameters | ||
- | * **help**: print the parameters | ||
- | * **server**: Mandatory. IP address of host name of iSeries | ||
- | * **logonuser**: | ||
- | * **logonpassword**: | ||
- | * **dataqueue**: | ||
- | * **user**: Optional. The key that JAR program is used to fetch data from data queue. If this parameter is ignored, the current user ID of Window machine is used. | ||
- | * **multifiles**: | ||
- | * **pdfreaderdir**: | ||
- | * **pdfreadername**: | ||
- | The parameters can be passed to JAR program in 2 ways: | ||
- | * Pass them into java command, for example: | ||
- | C:\>java -jar ifdclient.jar -server 172.16.1.54 -logonuser my_user -logonpassword my_password -user USER01 | ||
- | * Put them a separate file named ifdclient.properties as an example below (all parameters must be having prefix with ifdclient.): | ||
- | {{ : | ||
- | When file .properties is used, the command to start .JAR program is as below:\\ | ||
- | C:>java -jar ifdclient.jar | ||
- | **Notes:** | ||
- | Please remember that if the .JAR program is setup as a Window service then when PDF is sent from server, the PDF reader may open it into session 0 which is invisible to current logon user of Window. |
pub/dwtinstructions.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1