Using FILE to interact with the CI from an App server

[Former Member]

Hi All.

We have a custom code function where a user takes a text file and uploads it into the SAP system. The file is immediately processed and a new 'outbound' file is created. Currently, we have the dirctory structure set-up on out CI/DB server. Our users access the system from one of 2 application servers.

The issue we have is that due to the definition in FILE, when the users execute the report, it errors out. This is becasue when they execute, SAP looks to the local server - the app servers - for the directory. As stated, this directory lives on the CI. Does anyone know how to adjust the functionality of FILE so that I can point the program to execute on the CI and not the app server? Thanks!

[Former Member · Accepted solution]

Hello Tim,

We have a similar scenario like you but dont face this issue. 2 things are imüportant here:

1. The directory residing on CI should be accessible from the other application server i.e the mount should be correct.

2. The logical file path name in FILE should be correct. This is very important.

Believe me we have a more complex arrangement where 5 SAP s are involved and the directory resides on only one of them

Also FILE cannot dicate on which system the program is executed.It purely depends on the app server where the user is logged in.

Regards.

Ruchit.

[Former Member · Accepted solution]

Ruchit,

Thanks! NFS mounts may be our solution here, but I'd like to avaoid them.

Thank you, however, for the info on FILE. I suspected that it could not reach any further than the server it was on.

Are you folks using NFS mounts or shared folders for your solution?

Thanks,

Tim

[Former Member · Accepted solution]

Hi Tim,

We are using NFS and frankly NFS is very helpful in such cases. Otherwise you will have lots of issues.

Also in FILE if we give logical file path then it is not dependent on any physical server. For example in our case FILE is maintained in development system and transported across mutiple systems to production and the logical pfile path works for all. In logical file path you can define the path as XXXX<systemid>yyy.. Then what you can do is (in case you want to avoid NFS) create the directory explicitily on all the servers. Now suppose the program executes on application server intead of CI then it will create output file in the directory on the app server. Note that <systemid> will be same for both CI and app server.

Regards.

Ruchit.

[Former Member · Accepted solution]

Hi Tim,

One additional point.

I am not too much of an expert on FILE but I have seen it enough in order to assure that what you want is possible. I would really recommend that you take advise from a guy (technical normally) who has very good idea of file. He will be able to do necessary customizing for you. But I am sure that this is possible.

Regards.

Ruchit.

[Former Member · Accepted solution]

Ruchit,

Thanks dude! Appreciate your time and input. Looks like we'll need NFS for the fix here. FILE cannot be used to jump accross servers - it does indeed only execute against whatever server it is run on. Moving all my users off the app servers onto the CI also defeats the prupose of the app servers

We can't create these directories on the app servers, as many interface programs use these as well, so we'd introduce new issues where the required files would be 'all over the place'.

I'll ask my AIX guy to get this going. Thanks!

[Former Member · Accepted solution]

Hi Tim,

Welcome. NFS is gonna make life really easier for you.

Regards.

Ruchit.

[Former Member · Accepted solution]

Ruchit,

We've implemented the NFS share and propigated it out to the app servers. All looks well, thanks for confirming my thoughs as well as your comments and input.

Cheers,

Tim