OnDemand User Group
Support Forums => Report Indexing => Topic started by: jsquizz on October 31, 2017, 07:10:00 AM
-
First install here working with AFP2PDF conversion on retrieval, bear with me :)
On our CMOD server, we have the following information in the indexer information for our applications-
On the CMOD Server-
RESTYPE=ALL
FORMDEF=F113NG41, etc..
PAGEDEF=P1NG500X, etc..
FDEFLIB=/usr/lpp/psf/fdeflib
PDEFLIB=/usr/lpp/psf/pdeflib
PSEGLIB=/usr/lpp/psf/pseglib
FONTLIB=/usr/lpp/psf/fontlib
OVLYLIB=/usr/lpp/psf/ovlylib
On the ODWEK server,
ResourceDataPath=/opt/ondemand/afp2pdf/reslib
;Font_Path=/opt/ondemand/afp2pdf/font
Font_Path=/prod/apps/odwek/afp2pdf/font
what is the point of having the libraries for the fonts/resources listed in the indexing settings, if we are using the resources/fonts defined in afp2pdf? In my prior gig, I don't remember seeing those options in our app settings for afp. There was much less coding required in the application. That was converted to PDF via XENOS at retrieval though.
-
The resource libraries/directories are used to build the resource bundle to store in CMOD, and to be used during reprints.
AFP fonts can't be displayed/printed on PCs, so the font library in ODWEK is where to find substitute fonts. Not sure what would be picked up from an alternate resource path for ODWEK. Maybe updated resources (for rebranding old documents?).
Also, you should have the 'reslib' directories elsewhere. I usually recommend /home/archive/reslib/AppGroupName/AppName/VersionNumber.
-JD.
-
thanks JD.
Sounds like these references are useless for what we do, we won't be doing any reprinting from CMOD. If we did, we'd make the mainframe folks do it.
Thoughts?
-
Never say never, hope for the best, prepare for the worst. :)
-JD.
-
SO, is that directory something that CMOD pulls the fonts from, and then uploads them to? or is it something we should upload fonts for new reports into here..
Or should they go on the afp2pdf box
-
You kinda lost me about what comes from where... So I'll try and summarize...
If the AFP file you're loading doesn't have inline resources, then ACIF checks for those resources in the directories specified by the USERLIB/RESLIB/FONTLIB/PSEGLIB/etc. locations. From those, if the RESTYPE=ALL parameter is selected, then those resources are turned into a 'bundle' of resources. If that bundle matches one that already exists, then it links the file being loaded to the stored resource. If that bundle is unique, then it's added to the list of resources, and assigned a unique number.
On the ODWEK side (which I'm not so familiar with) my understanding is that you can substitute or 'override' the resources in the bundle with resources stored locally. Especially in the case of fonts -- because AFP fonts CANNOT be represented properly on anything but an AFP printer -- you keep a library of substitute fonts on the web server for your transformation tools to swap into the AFP documents. Of course, any ODWEK-ninjas out there are welcome to correct me & my rudimentary understanding of how this all works... :)
-
Excellent. Better explanation than IBM
-
And my whole thing about creating a /home/archive/reslib/AG/App/Version directory tree is that it not only helps keep things organized, it prevents the rare situation where there are naming 'collisions' -- where two resources have the same name, but different contents.
This has happened to some customers a few times, especially after re-branding or a merger/acquisition/divestiture -- someone just updates the existing files with new contents, and when the changes doesn't make it down to IBM CMOD, the new invoices come out of OnDemand with the old logos, and nobody on the business side knows how it's even possible. :)
-JD.
-
I'm just confused about --
/home/archive/reslib/AG/App/Version
That would only be used for sending them to a printer right? I don't think listing out all the libraries in the indexing settings will be of value to me.
-
Nope, I'm suggesting that when you build the resource libraries (put the actual files that are pagedefs / formdefs / overlays / fonts / page segments) to put them into a file structure like:
/home/archive/reslib/StatementAG/CreditCards/v1/F113NG41
/home/archive/reslib/StatementAG/CreditCards/v1/P1NG500X
/home/archive/reslib/StatementAG/LineOfCredit/v2/F104LC15
/home/archive/reslib/StatementAG/LineOfCredit/v2/P1LC601Y
That way, you keep them all separate. And again, as long as you use RESTYPE=ALL ("resource types to store in CMOD by creating a resource bundle=ALL"), you won't need these forever, but it's a good idea to have them, because people ask for crazy things.
Storing everything in /usr/lpp/psf runs the risk of them being lost -- by accidental deletion, software upgrades, or failing to back them up (because /usr/lpp is typically a place to store software, not custom AFP resources).
-JD.
-
I think I'm getting there.
So back to the second post in this thread.
used in reprint..different than retrieval/conversion to PDF, yes ?
-
A reprint directly from the server to and AFP printer would use the AFP resources in the bundle that was created (or linked to) at load time. If you print from the web, it would go through the AFP2PDF process and would use the substitute fonts and resources via ODWEK & your transform process.
-JD.
-
You literally answered all my questions with that. Thanks!
-
No problem! Happy to help with all things related to CMOD. :)
-JD.