I am in the process of creating one job which will need to get a directory listing from and a 2nd job which will need to open a file from a share on a non-webfocus server. The job will use a domain/userid to access the other server.

For testing, I have hard coded the userid and pw into my fexes. This is obviously a security issue. Can I add the domain/user account to the admin.cfg or another config file which would encrypt the password and access it in the fex files as needed? Is there another/better way for me access the other server securely?

Thank you,
Deana

This message has been edited. Last edited by: FP Mod Chuck,

A couple of ways:

- Set up an adapter as a remote server to itself and make it an explicit security with the domain user/pass. You can then run requests using -REMOTE BEGIN/END or create meta-data for executing and producing the final answer set.
- Build a FUSE routine to encrypt/decrypt the password so you can keep the password as an encrypted value in text file and decrypt on use.
- Build a Java Plugin to encrypt/decrypt the password so you can keep the password as an encrypted value in text file and decrypt on use.

The first option would be the simplest.

I tried, unsuccesfully to set up an adapter and use -REMOTE BEGIN/END. When I executed my proc, it hung up on the -REMOTE statement. At this time, I have not tried the other 2 options. I have never created a FUSE routine or Java Plugin, so I am not sure where to start. I plan to work attempt these, if needed.

In looking at the edaspof, I have the following settings:

APP MAP sharedrive "X:\FolderName"
APP PATH app1 app2 app3 sharedrive baseapp

X:\FolderName is a share on another server. I need to change this server/share to newserver/share. I do not have a static map to X:\FolderName. This currently works without any issues, but I don't understand why. How does the WebFOCUS server resolve X:\FolderName to the correct sever/share? I am sure there has to be a configuration file/setting somewhere, but I have not found it. Any suggestions?

Thank you,
Deana

Maybe I’m missing the gist of what you want to accomplish, but wouldn’t it be easier if a file containing the directory listing was sent from your share to your reporting server?

Deanna

I think the syntax for using a share is \\machinename\sharedrive not X:

Good morning,
Craig, thank you for the suggestion. I was tying to use an existing job and did not even think of having the remote server create the directory listing and have it moved to the WebFOCUS server. If we can overcome the security issue to open the pdf files that reside on the new remote server, we will be implementing your suggestion.

Chuck,
Years ago, when you helped me configure the server, we put:

PP MAP sharedrive "X:\ShareName"
APP PATH app1 app2 app3 sharedrive baseapp

in the edasprof. X:\ShareName is a share on the current remote server. I cannot figure out how my WebFOCUS server resolves S:\ShareName to the current remote server. I am sure it is a setting or configuration somewhere which probably uses the \\machinename\sharedrive syntax. I just cannot find this configuration.

Thank you,

Deana

Deana

I don't know how that would work unless by some magic that is permanently mapped. I would change it to be \\machinename\sharedrive syntax.

Craig and Chuck,

Thank you both for your assistance. In the end, the remote server is sending the directory listing to the reporting server so I can update the filenames in my database. In addition, I eventually found a reference to \\machinename\sharedrive buried in code files. I was able to change the code and open the files on the new server. It appears the APP MAP in the edasprof is left over code from when the directory resided on the reporting server. The reference does not match up to anything. I will remove that line the next time I do a major update and need to restart WebFOCUS.

Sincerely,
Deana