RJS Software Systems
2970 Judicial Road, Suite 100
Burnsville, MN 55337
Phone: 952-736-5800
Fax: 952-736-5801
Sales email: [email protected]
Support email: [email protected]
Website: http://www.rjssoftware.com
About RJS Software Systems
RJS Software Systems helps companies go paperless by automating business processes and
digitally managing the entire lifecycle of their business information. We provide solutions that
help you capture, manage, distribute, and route documents digitally, and we provide you with
the tools you need to keep that information safe and secure. Learn more about RJS Software
Systems at http://www.rjssoftware.com.
© 2014 RJS Software Systems
This guide is protected under copyright law, furnished for informational use only, is subject to
change without notice, and should not be construed as a commitment by RJS Software Systems.
RJS Software Systems assumes no responsibility or liability for any errors or inaccuracies that
may appear in the informational content contained in this guide.
This guide is licensed for use under the terms of the Creative Commons Attribution Non-
Commercial 3.0 License. This license allows users to copy, distribute, and transmit the guide for
noncommercial purposes only so long as (1) proper attribution to RJS Software is given as the
owner of the guide; and (2) any reuse or distribution of the guide contains a notice that use of
the guide is governed by these terms. To view a copy of this license, visit
http://creativecommons.org/licenses/by-nc/3.0/us/.
Printed: May 2014
Page 1
About iForms 2
iForms 2 lets you maintain the ability you had with iForms 1 to convert your data into valuable
business forms and reports. With iForms 2, though, you’ll be able to streamline and simplify
your forms processes. And you will have greater control over the quality, content, and
production of your organization’s forms and reports.
This workbook describes iForms 2 in detail, and the goal of this workbook is to help you
successfully migrate from iForms 1 to iForms 2 by:
Introducing you to the benefits, components, and concepts of iForms 2.
Explaining the important things to consider before migrating.
Helping you gather key information from your organization’s current forms processes
that will determine your hardware requirements and tailor your iForms 2 configuration.
After you read and complete the tasks in this workbook, you and your RJS Software
representative will begin implementing iForms 2 at your organization.
This workbook is divided into the following topics:
Benefits
Components
How the Components Work Together
Server Concepts
What to Consider Before Migrating
Assembling a Team
Assessing Your Data
Command Equivalencies
Contacting RJS Software
iForms 1 to iForms 2 Migration Workbook
Page 2
Benefits
iForms 2 is not just a new version of an old system. It is a paradigm shift that offers many
benefits, including:
Faster merge times and improved reliability.
Ability to have the server service multiple iSeries partitions.
Multiple merge jobs with different priorities.
Greater control of how server resources are allocated to merge processes.
More reliable printing after form merges.
Four methods for printing to cover the widest range of print devices.
Easy switching between printing methods.
Simplified form-design process.
iForms 1 to iForms 2 Migration Workbook
Page 3
Components
iForms 2 is comprised of updated and integrated components: Server, Client, Designer, and
Text Designer.
iForms Server
The heart of the iForms solution and the component that produces merged
forms. All other components connect to it. You configure the server remotely
from any browser.
With iForms 1 some organizations maintained several servers. After migrating
to iForms 2, you will only need one server.
Platform
The iForms Server can run on Microsoft Windows or IBM i.
Architecture
The iForms Server uses Representational State Transfer (REST) architecture. This RESTful
architecture lets the iForms Server use HTTP requests to create, read, update, and delete data.
The server requires a client to set up template and data merges. RJS Software offers two fully
developed client application, one for Microsoft Windows, the other for IBM i.
The RESTful architecture of iForms 2 gives you the flexibility to integrate iForms into almost any
application. Contact RJS Software for further details.
iForms Client
The application that you use to set up and run merges on the server between input
data and form templates.
Platform
RJS Software Applications
RJS Software has developed two client applications that you can deploy immediately to set
up and run merges:
iForms 1 to iForms 2 Migration Workbook
Page 4
DeliverNow for Microsoft Windows
iForms Library for IBM i
Your Application: Using the iForms Client Proxy API
If your organization needs your own application to submit merges to the iForms server, you can
use the iForms client proxy API. Available for both Microsoft .NET and Java, the API lets you
integrate the client functionality into your application. Contact RJS Software for further details.
iForms Designer
The iForms Designer is the application you use to create custom form templates.
Platform
Microsoft Windows
iForms Text Designer
The iForms Text Designer is the application you use to extract text from input data in
spool files or text files so you can merge the text with form templates.
Platform
Microsoft Windows
Note: If your input data is not in spool files or text files, you will not use the iForms Text
Designer.
iForms 1 to iForms 2 Migration Workbook
Page 5
How the Components Work Together
Install the client application and the iForms Designer (and, if needed, the iForms Text Designer).
Design one or more form templates and save them to the server.
Use the client application to merge input data with the templates.
The server produces professional forms and sends a result message to the client application.
Install and configure the iForms server.
iForms 1 to iForms 2 Migration Workbook
Page 6
Environment
Datasource
iSeries Resource
Server Concepts
iForms Server 2 was designed with three concepts that simplify the iForms
workflow: Datasource, iSeries Resource, and Environment.
Each concept is a configuration setting on the server and represents a
connection between the server and a component or input data.
Datasource
A connection to input data in a database. You name the Datasource and set
up and configure its JDBC class driver, URL, connection string, credentials,
and so forth.
Benefit over iForms 1
You can have multiple Datasources on one server.
Note: If your input data is only in spool files or text files, you do not need to set up a
Datasource. Instead, the iForms Server creates a temporary table from the text extracted from
spool or text files in the iForms Text Designer.
Example
Acme Foods’ Datasource is stored in a Microsoft SQL Server database. They name it (Suppliers)
and configure it during iForms implementation. Then, the iForms Server will always have the
connection to their database and be able to run form merges without interruption.
iSeries Resource
Environment
Suppliers
iSeries Resource
Datasource
Environment
iForms 1 to iForms 2 Migration Workbook
Page 7
Environment
iSeries Resource
Datasource
iSeries Resource
A connection with credentials to an iSeries. An iSeries resource lets the
iForms Server do the following without interruption:
Download spool-file data or IFS files as input data for a merge.
Upload output forms to a spool file or an IFS directory.
Benefit over iForms 1
You can connect to multiple iSeries machines from one server.
Note: If your organization does not use the iSeries, you will not set up an iSeries Resource.
Example
Acme Foods’ input data is in spool files on an iSeries machine. They install the iForms Server on
a different machine.
During iForms implementation, they create an iSeries Resource (Production) for the machine
that holds their spool files. Now the server can access the files during form production and then
re-spool merged forms to an output queue on the same iSeries.
Environment
Production
Datasource
Environment
A location on the iForms Server for storing form templates and template
auxiliary files, like sub-reports, images, and so forth. Every Environment
that you create has a distinct directory path.
Then, when you design form templates in the iForms Designer (and iForms
Text Designer, if needed), you save them to a specified Environment on the
iForms Server. So, during form production, the server always has access to templates and
auxiliary files.
Environment
iSeries Resource
Datasource
iForms 1 to iForms 2 Migration Workbook
Page 8
Benefit over iForms 1
You can set up and multiple Environments on one server.
Example
During iForms implementation Acme Foods set up two Environments, Test and Production.
They design their form template and store it, along with template auxiliary files, in the Test
Environment. They test their template design in this Environment before moving the template
to the Production Environment.
iSeries Resource
Datasource
ProductionTest
iForms 1 to iForms 2 Migration Workbook
Page 9
What to Consider Before Migrating
RJS Software has found the following to be the most common concerns organizations have
before migrating from iForms 1 to iForms 2. Please know that through the entire migration
process RJS Software will assist you.
When implementing iForms 2, you will set up a new server, though you might be able to set it up on hardware you’re already using for iForms 1. Your RJS Software representative will help you implement the new server.
iForms 1 and iForms 2 can run concurrently, and you don’t have to migrate all your forms processes at once. RJS Software appreciates that your forms processes are crucial to your organization, so consider migrating one form at a time.
You might need to make minor changes to how images and sub-reports are called in form templates. Your RJS Software representative will help you with these changes.
Any application in your organization that currently calls a command from iForms 1will
have to be modified to call the new command, IFMEXEC.
Your RJS Software representative can give you parameter equivalencies between
commands. For sample parameter equivalencies between commands, refer to
Command Equivalencies.
iForms 1 to iForms 2 Migration Workbook
Page 10
Assembling a Team
A successful iForms2 implementation requires specialized knowledge from different parts of
your organization. You gather that knowledge by assembling a committed, skilled team.
Choose team members who are excited about being able to control of the quality, content, and
production of your organization’s forms and reports through iForms 2.
The team is divided into the following roles:
Project Manager
Information Analyst
IT Analyst
Business Analyst
Depending upon your organization’s circumstances, some or all of these roles might go to the
same person or be divided up.
Review the roles and responsibilities on the following two pages and assign someone to each
role.
Note: Some responsibilities are in bold. These responsibilities require active participation,
either in completing tasks in this workbook or in implementing iForms 2 with your RJS Software
representative after the workbook is filled out.
iForms 1 to iForms 2 Migration Workbook
Page 11
Role Responsibilities
Project Manager
Leads this team.
Reads this workbook and completes all tasks in it.
Is part of the implementation phone call with RJS Software after the workbook is filled out.
Has a working knowledge of the responsibilities of all the roles.
Is your organization’s primary contact with RJS Software.
Assigned to:
Information Analyst
Helps fill out this workbook (in the Assessing Your Data section).
Thoroughly understands the following about source data that your organization currently uses to create forms:
o Its file format, database structure, or both.
o Where it’s stored on the network.
Thoroughly understands the following about source data for forms produced after iForms is implemented:
o Its file format, database structure, or both.
o Where it’s stored on the network.
Assigned to:
iForms 1 to iForms 2 Migration Workbook
Page 12
Role Responsibilities
IT Analyst
Is part of the implementation phone call with RJS Software after this workbook is filled out.
Thoroughly understands the your organization’s:
o Network.
o Hardware (including printers).
o Operating systems all computers are running.
Knows whether additional hardware and software resources are available.
Assigned to:
Business Analyst
Helps fill out this workbook (in the Assessing Your Data section).
Has working knowledge of all the forms your organization currently uses.
Thoroughly understands the following about the forms your organization needs to produce after iForms is implemented:
o All the different kinds. For example, invoices, purchase orders, bills of lading, EOD reports, and so forth.
o How each kind needs to be laid out.
o Whether each kind needs signatures.
o What file format each kind needs to be.
o Where each kind needs to be stored, routed, or printed.
Assigned to:
Note: If you or anyone on your team needs clarification of responsibilities, contact RJS Software
for assistance.
iForms 1 to iForms 2 Migration Workbook
Page 13
Assessing Your Data
To successfully migrate from iForms 1 to iForms 2, you need to know your hardware
requirements and have a clear picture of the current forms processes at your organization. A
data assessment will give you and your RJS Software representative this information.
Data-Assessment Worksheets
To do an assessment, you and your team fill out simple, one-page data-assessment worksheets
for each of your organization’s current forms. You need to assess the data in your current forms
because they already hold all the information that iForms 2 needs to access.
1. Review the sample data-assessment worksheets on the next two pages.
2. Download one data-assessment worksheet for each kind of form your organization will
produce with iForms.
3. Along with the Information Analyst and Business Analyst, fill out the worksheets. The
Information Analyst fills out the Current Input. The Business Analyst fills out the
Anticipated Output.
Note: If you have questions about any part of the worksheet, first fill out as much of it
as you can before contacting RJS Software.
iForms 1 to iForms 2 Migration Workbook
Page 16
Command Equivalencies
iForms 2 uses a new command, called IFMEXEC, to initiate a form merge from the iSeries.
This section gives you three examples of parameter equivalencies between IFMEXEC and the
iForms 1 commands that initiated a form merge: SPLIFORM, SPLIFORMJ, and RUNIFORM. You
can use these examples to reproduce form merges with IFMEXEC at your organization after
you’ve implemented iForms 2.
The three examples use the following spool file …
Job . . . . . . . . : QPRTJOB File . . . . . . . . : INVOICE
User . . . . . . . : CALEB Number . . . . . . : 000013
Number . . . . . . : 535721 Creation date . . . : 03/11/13
Job system name . . : S1010B5A Creation time . . . : 17:06:58
To be merged with the following iForms template …
invoice.jrxml
Example 1: IFS PDF Output (SPLIFORM > IFMEXEC)
SPLIFORM FILE(INVOICE)
JOB(535721/CALEB/QPRTJOB)
SPLNBR(13)
TEMPLATE('/rjsiforms/invoice.jrxml')
XMLDEFFILE('/rjsiforms/invoice.rjsxml')
OUTPUTFILE('/rjsiforms/invoice.pdf')
IFMEXEC INPUTTYP(*SPOOL)
FILE(INVOICE)
JOB(535721/CALEB/QPRTJOB)
SPLNBR(13)
TEMPLATE(INVOICE)
DTASRCNAME(ISERIES)
RESOURCE(ISERIES)
EXTRTEMPLT(INVOICE)
LOCATION(*IFS)
RMTSVRURL('http://10.1.1.1:9615')
OUTFILE2('/rjsiforms/invoice.pdf')
Example 2: PCL Output (SPLIFORMJ > IFMEXEC) SPLIFORMJ FILE(INVOICE)
JOB(535721/CALEB/QPRTJOB)
SPLNBR(13)
TEMPLATE('/rjsiforms/invoice.jrxml')
XMLDEFFILE('/rjsiforms/invoice.rjsxml')
PRINT(*YES)
PRINTOUTQ(QGPL/PRT01)
RMTSVRURL('http://10.1.1.1:9615')
IFMEXEC INPUTTYP(*SPOOL)
FILE(INVOICE)
JOB(535721/CALEB/QPRTJOB)
SPLNBR(13)
TEMPLATE(INVOICE)
DTASRCNAME(ISERIES)
RESOURCE(ISERIES)
EXTRTEMPLT(INVOICE)
FORMAT(*GSPRINT)
LOCATION(*SPOOL)
RMTSVRURL('http://10.1.1.1:9615')
SPLF(*N QGPL/PRT01)
PCPARMS(PXLMONO)
iForms 1 to iForms 2 Migration Workbook
Page 17
Example 3: PDF Output (RUNIFORM > IFMEXEC) RUNIFORM TEMPLATE('/rjsiforms/invoice.jrxml')
P1NAME(INVOICENUM)
P1VALUE(1001)
RESPOOL(*YES)
OUTQ(GQPL/OUTQ)
IFMEXEC INPUTTYP(*REPORT)
TEMPLATE(INVOICE)
DTASRCNAME(ISERIES)
RESOURCE(ISERIES)
LOCATION(*SPOOL)
RMTSVRURL('http://10.1.1.1:9615')
SPLF(*N QGPL/OUTQ)
NAMEVAL((INVOICENUM 1001))
iForms 1 to iForms 2 Migration Workbook
Page 18
Contacting RJS Software
Now it’s time to begin migrating to iForms 2.
To ensure your implementation is as fast and easy as possible, make sure you have done the
following before contacting your RJS representative:
Reviewed the benefits, components, and concepts of iForms 2.
Reviewed the things to consider before migrating and the command equivalencies.
Assembled a team.
Filled out data-assessment worksheets.
Now, contact RJS Software to schedule a time to begin implementing iForms 2.
Note: Make sure the IT Analyst is part of the implementation because you will be determining
your iForms hardware requirements.
RJS Software Systems
Phone: 952-736-5800
Fax: 952-736-5801
Sales email: [email protected]
Support email: [email protected]
Website: http://www.rjssoftware.com