WebFOCUS 7.7.05M with Developer Studio 7.7.05.

Our reporting servers are on AIX. When using Telnet, I have an ID with which I can update files in the folders in the approot path.

In Developer Studio I configured the Environment setting for the reporting server to use the same ID/password as the one that has update access on the AIX server. But I cannot update files - either the ID is ignored or it doesn't have permission, or there's some other setting blocking the update.

Any ideas?

This message has been edited. Last edited by: Francis Mariani,

The ID I'm using is defined as the "admin_id" in admin.cfg on the reporting server.

Do you know what the set up is for the reporting server ?

What ID is it running under, and whether its set up to become the user you connect as ?

I think you need to set the IBI_WFRS_Service_User and IBI_WFRS_Service_Pass values on the client. They are under Configuration/Application Settings/Security.

Francis

I think Waz is on the right track. I have seen this especially with UNIX where the ID that starts the reporting server has the correct permissions to the ../ibi/apps directories and other ID's don't.

Waz, I'm not sure what you mean by "set up to become the user you connect as".

I have access to the server console as an admin, so please point me to the appropriate area of the console.

When I view "Access Control", I see the following:

Active Security Provider(s)  PTH
Effective server admin       aduser1
Server admin                 aduser1, aduser2
Server operator              --
Application admin            --

I tried configuring Dev Studio with each of these two users, aduser1, aduser2, nut neither worked.

Interestingly, I tried to edit a fex from the server console, but the Save failed.

Also, the AIX ID that does have update privileges is not one of the two specified as Server Administrators in the server console.

Francis

If you can get a telnet session to the AIX machine then navigate to where the ../ibi folder is and run the command ls -lsa This will tell you who the owner of the apps folder is and what the permissions are.

I would add the owner as a server administrator and use that ID with dev studio and then try to save a file with dev studio.

Chuck, thanks for the tip!

OK, I've used telnet and determined that the owner is "aduser1". The owner has rwx permissions. It is defined as a server administrator. I've configured the Dev Studio connection to use this owner. I still cannot save.

Is it possible that some remnant of Visual Source Save is preventing updates?

That could be a possibility but I don't know how to validate that.

Have you tried to save something using the reporting server web based console?

quote:

Waz, I'm not sure what you mean by "set up to become the user you connect as".

The reporting server can be set up so the agent sessions can run as the user you are connecting to.

Can you execute the command "! whoami", this will tell you what id is being used for the agent sessions

Perhaps it is easier to work with group permissions on those directories, making sure that both the WFRS user and your account are part of the same group.

You can check group memberships with the id command.

You can modify group ownership with chgrp -R and group permissions with chmod -R

All these commands should have man pages (man man, man id, man chgrp, man chmod), but I'm not familiar with AIX, perhaps they document commands differently - but if they do, they should stop calling it UNIX.

The owner of all the content - folders and files is aduser1. It appears that no matter what credentials you enter in the Dev Studio environment settings, aduser2 is always the one that is used. Since these two users are in the same group, prompted by Wep5622, I changed the group permissions on the files to rw. Now I'm good to go. I ran this command in the appropriate folders: chmod g+rw *.* - probably not what an expert UNIXhead would use, but it worked for me.

Thanks everyone for your help - my UNIX permissions knowledge was rusty...

Francis

Not sure if you want to keep looking for where aduser2 is the default or not now that you have it working.. You might want to check the Client Admin console under Reporting Servers / Remote Services / EDASERVE and see if the security is using a service account, it is usually set to Trusted. Also in the Client Admin console under Application Settings / Security the IBI_WFRS_Service_User may be set as well. Then the last place to look is on the Reporting Server console under Access Control / Settings / Access Control Settings / Effective Server Administrator

On UNIX, *.* matches all files that contain at least one dot character. If you want to allow rw on _all_ files, the wildcard is *

That's a bit different from DOS, but to me it makes a lot more sense

Also, you only altered permissions to the files and directories at the directory you were in when you executed that command. chmod has an option to recurse into subdirectories as well, usually that is -R.

Finally, to be allowed to traverse a subdirectory, you need 'execute' (x) permissions on those directories. But, you probably don't want those on all the other plain files. Most UNIX flavours have an X option for that (uppercase, as opposed to the lowercase x that sets execute bits on _all_ files and directories).

In summary, the command you should run is probably:

chmod -R g+rwX *