Setting up eFORMz on iSeries
This post describes setting up eFORMz on iSeries, including licensing eFORMz and setting up the Director to run as an automated process. Licensing eFORMz on iSeries Connect to the iSeries using a ...
This post describes setting up eFORMz on iSeries, including licensing eFORMz and setting up the Director to run as an automated process. Licensing eFORMz on iSeries Connect to the iSeries using a ...
There are four subfolders under the eFORMz_6 > jars folder in a standard Windows eFORMz install. Three of these subfolders contain platform-specific jar files (AS400, Local and Unix). The ...
Diagram System Requirements and Product Features System requirements and hardware recommendations for eFORMz are available here: ...
Because of changes that are described in IBM Technote 25713522, the user that runs the eFORMz Director job must have a password. Without a password, Java cannot access the IFS. As a result, the ...
The Director Toolkit allows you to create and edit configuration files for eFORMz/eDIRECT+ processing. Configure your Windows, iSeries, or Unix box for eFORMz processing using the Director ...
The overall syntax of the DirectorCommand is: java -jar Run.jar – com.minisoft.Director.manage.DirectorCommand [options] where [options] are: host=<host address> – default is “localhost” ...
For step-by-step instructions, view the following post: http://support.minisoft.com/index.php/setting-up-eformz-on-iseries/ To license Minisoft eFORMz on an AS/400 (iSeries) system, an unsigned ...
The following steps must be completed to get eFORMz going on your iSeries system: Register and download eFORMz from www.minisoft.com. Install eFORMz on Windows. eFORMz is initially installed with ...
Printer Configuration Setup Director Configuration Setup AS400 Automated Job Process You use the Director Toolkit to setup the automated print process. To setup the automation process you must ...
Local Directory A Local Directory represents a directory or folder located locally on the system you are running. Your source print files will reside in this location to be pulled to be merged ...