OnDemand Users Group

Support Forums => Report Indexing => Topic started by: jeffs42885 on May 22, 2013, 06:43:41 PM

Title: Indexing and AFP Resources
Post by: jeffs42885 on May 22, 2013, 06:43:41 PM
We use xenos d2e to transform from AFP to PDF and then store into OnDemand (8.5.0.06 / AIX)

Daily, the business sends resource bundles (.ZIP) down that contain .psg resources. There has been times when we manually had to load resources and the file failed indexing due to a missing resource.

I tested this in our pre-production environment with two scenarios

1) I took an existing resource and AFP file and tried loading it with the resource in LOWERCASE (resource.psg)
2) I took an existing resource and AFP file and tried loading it with the resource in UPPERCASE (RESOURCE.PSG)

^^Both above worked..

However, one day when we took the zip file and manually unzipped it in the resource directory, it seems as though the case mattered. Has anyone encountered anything like this?
Title: Re: Indexing and AFP Resources
Post by: Justin Derrick on May 23, 2013, 04:42:29 AM
It's more likely to be about something like permissions...  If you can post the error message from arsload (and/or ACIF) then we might be able to narrow down the problem.

-JD.
Title: Re: Indexing and AFP Resources
Post by: jeffs42885 on May 23, 2013, 02:14:59 PM
I thought permissions as well last night when I was sitting at home! lol!!

Here's the error message from the xenos log..not sure if this will help you. According to xenos support the resources need to be in the right case as defined in the AFP file but I tested in both cases and it works.

GTI-102-I: JS processing completed, maximum message severity was 8
Most Severe message was:
<IO-302-E: For PageSeg /odxenos/d2e//resources/res/res695.psg, record 0: Error occurred during Open>
Last message was:
<GTI-102-I: JS processing completed, maximum message severity was 8>
JS ended with return code 8


JD- Just to clarify, what permissions should these resources be at?
Title: Re: Indexing and AFP Resources
Post by: Justin Derrick on May 24, 2013, 02:29:59 PM
Yeah, you're right -- that error wasn't helpful.  I'd check your Xenos documentation to find out what a 'return code 8' means.

In terms of permissions, it should simply be readable by the user trying to read them.  If the user who runs arsload is 'archive', then you'll want the owner to be 'archive', with permissions like 400 (aka u=r or r-- --- ---).  If the user who owns the file is different from the user who runs the loads, but they belong to the same group, then make sure the group ownership reflects that, and set the access to 440 (u=r g=r or r-- r-- ---). 

Good luck!

-JD.
Title: Re: Indexing and AFP Resources
Post by: Stephen McNulty on May 28, 2013, 11:06:14 AM
It sounds odd that your 2 sample loads worked (unless they are 2 separate compositions).  I remember doing this a long time ago, and always had to make sure that name of the resource matched because it was case sensitive.  Use a utility to look at your AFP tags in the file, and you should be able to confirm what case the resource needs to be in.
Title: Re: Indexing and AFP Resources
Post by: jeffs42885 on May 28, 2013, 01:03:44 PM
Can you tell me the name of a product I can use?
Title: Re: Indexing and AFP Resources
Post by: Stephen McNulty on May 28, 2013, 01:52:55 PM
I use AFPexplorerer   it can be downloaded from http://www.compulsivecode.com/Project_AFPexplorer.aspx 

It is fairly simple and straight forward.

Title: Re: Indexing and AFP Resources
Post by: jeffs42885 on May 28, 2013, 02:04:54 PM
Cool.

Heres my question now..

The file is on the file system as all lowercase but it is referenced here in all caps in the AFP file.

It works..It doesnt appear to be case specific. Im just wondering if maybe xenos does something that checks for both files.