xmlgraphics-fop-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Solenov <Igor_Sole...@epam.com>
Subject AFP files generated with FOP loading to IBM OnDemand system problem
Date Fri, 01 Apr 2011 12:39:51 GMT
Hi all.
I'm using the newest version of FOP 1.0 from trunk in Windows environment.
The task I'm trying to implement is converting XSL-FO document to AFP format suitable for
loading into IBM OnDemand system. I need an advice on how to configure FOP to get proper AFP
file.
The main problem is that AFP document must be properly structured to match "structure standard"
(described below).

After adding proper indexes to the AFP document it failed to archive in OnDemand environment.
The log was telling that there is no resource in the AFP files.
I configured FOP to generate separate resource AFP file. Then simply append data AFP file
to the end of the resource AFP file. This composite file failed to load into OnDemand. The
log contains this info:
0425-104 DATA IN AN INPUT RECORD OR RESOURCE IS INVALID: BDT STRUCTURED FIELD IS NOT ALLOWED
OR FORMS AN INVALID SEQUENCE.
0425-105 THE ERROR REPORTED ABOVE OCCURRED IN LOGICAL RECORD NUMBER 21, WHOSE SEQUENCE NUMBER
IS NOT AVAILABLE, AND RESOURCE NAME IS UNKNOWN.

Now I have no idea how to configure FOP to get proper AFP file. Does anybody have any experience
in creating AFP files for IBM OnDemand system? 
I'll appreciate any advice concerning this problem.

AFP File Requirement

-	The tag elements specified are : acn and ndate.
-	Should include both tag elements as group index.
-	The .AFP file should come in two parts: resource data and output/data stream.
-	The presentation text/data  is contained in the output/data stream.  See Format of the Output
stream.
-	The resource information (fonts, overlays, logo, etc.) is contained in the resource data
stream.  See Format of the Resource stream.
-	For those resources used (like those boxes, lines, shadings and other images), ensure that
those common ones should not be re-created repetitively, but "to be referenced" instead, so
as to minimize the resource size during archival
-	The output/data stream should be appended to the resource data stream in the AFP file. 
See concatenating resource to output/data.
-	The AFP file name (*.AFP) should be in uppercase.

Format of the Resource stream

ACIF retrieves referenced AFP resources from specified libraries and creates a single file
that contains these resources. Using ACIF, you can control the number of resources as well
as the type of resources in the file by using a combination of RESTYPE values and processing
in the resource exit.  ACIF can retrieve all the resources used by the print file and can
place them in a separate resource file. The resource file contains a resource group structure
whose syntax is as follows:

BRG
BR
AFP Resource 1
ER
BR
AFP Resource 2
ER
..
BR
AFP Resource n
ER
ERG

ACIF does not limit the number of resources that can be included in this object, but available
storage is certainly a limiting factor.

Concatenating the resource to the output/data

You can create a print file containing all the required print resources by concatenating the
output document file to the end of the resource file. Do, however, remember two things when
doing this:

o	First, although OnDemand and the other PSF products support all types of inline resources,
PSF/VSE supports only inline page definitions and form definitions.
o	Second, the offset information in the index object file applies to the document; that is,
to the Begin Document (BDT) structured field. The offset information also applies to the file
I/O level, because a single document is in the output document file. When you concatenate
these two files, the offset information in the index object file no longer applies to the
resultant file; that is, you cannot use this information to randomly access a given page or
page group without first determining the location of the BDT structured field. This is not
a problem for OnDemand, because it removes any inline objects before using the offset information.


Format of the ACIF Output Document stream 

ACIF always creates a print file. In doing so, ACIF may create the following structured fields:

o	Tag Logical Element (TLE)
o	Begin Named Group (BNG)
o	End Named Group (ENG)

The following example shows the general internal format of this object:

BDT
BNG Groupname=(index value + sequence number)
TLE (INDEX1)
TLE (INDEX2)
...
TLE (INDEXn)
BPG
Page 1 of group 1
EPG
BPG
Page 2 of group 1
EPG
...
BPG
Page n of group 1
EPG
ENG
...
BNG Groupname=(index value + sequence number)
TLE (INDEX1)
TLE (INDEX2)
...
TLE (INDEXn)
BPG
Page 1 of group n
EPG
BPG
Page 2 of group n
EPG
...
BPG
Page n of group n
EPG
ENG
EDT


Best Regards,
Igor

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org


Mime
View raw message