We have a hub - sub environment were we wish to pass logon credentials from the MRE on the webFocus clent to the zOS hub. It is anticipated that scripting will be needed in the site.wfs file in order to manage various logons. Does anyone have a reference of wfs scripting or samples of any hub logon scripting. Having trouble here finding the code syntax and reseved words of the scripting language.

There are many additional questions that need to be asked to give you the best answer. We use NO additional scripting and have the same functionality you are looking for, but it all depends on the security already in place in your environment.

Are all the WF servers running secured? Do they all use the same type of authentication (such as LDAP) or do they each have their own OPSYS security.

I'm assuming you're wanting server credentials passed on to the the z/OS platform from the Windows WF Client and not MRE credential, but that was kind of the opposite of what you had written.

Can you simply turn on credential passthru in the remote server configuration and get what you need? or possibly just make it a trusted connection?

Is there additional functionality on the Z/OS server that is being provided using the logon credentials other than authentication (such as application or DBA security)?

Bob,

I opened a case with Tech Support because I could not find definitive documentation about WebFOCUS Scripting. They pointed me to these documents:

http://documentation.ibi.com/m...f761sec/wf761sec.pdf
http://documentation.ibi.com/m.../wf713sec/10sec4.htm
http://documentation.informati...urity52/08sec525.htm

Unfortunately, not ALL the parameters are listed in these documents.

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

Thanks for the comments Darwin, The webFocus clients are all running on Windows 2003 with internal security. The connection to the zOS reporting Servers are runing with PTH, a trusted connection. We wish to change that and move to OPSYS on the Reporting servers. That presupposes that each webFocus developer has a corresponding set of credentals on zOS. Problem is that some folks do not have access to zOS. When we switch to OPSYS, some users will no longer be able to run reports. We are loking at scripting a generic Reporting ID for those folks who need them, then letting developers re-verify thier cerdentals upon first zOS access in their session. So, we are looking for some info on the WFS scription, things like language syntax and reserved words.

This concept was suggested by the IBI Tech Services. And it was they who directed me to Focal Point to find WFS scripting refences.

Hi Francis,
Thanks for the refernces. I'll download them and review the content.

quote:

This concept was suggested by the IBI Tech Services. And it was they who directed me to Focal Point to find WFS scripting refences.

Very interesting ....................... Do they not have access to documentation references I wonder?

Bob,
You might also find it useful to work your way through the Summit Lab I put together on WFS Scripting.
It is available here:

The lab is called "WebFOCUS Core From the Inside Out: Use Scripting to Customize Your Environment".
It has 4-5 examples of using scripting that are based on real requests I've received from customers and cases have been opened on. As a result there are a number of examples of the syntax that can make it easier.
If there is something very specific you're trying to do and you're having a hard time doing it, please just open a case and someone can help you with the specifics.
I just scanned the case you had open with Techsupport and the case details seemed kind of generic, which could have been why the Tech pointed you to FocalPointe.

In any case, a link to the Security and Administration manual was sent if this is the case I think it is. Bob was likely just looking for more practical examples about usage.

I know that I personally have a much easier time learning things if there are a couple of real world examples using the coding then the more abstract "syntax" examples in the Security and Administration manual.

Hi Doug,

Thanks for the lead on Summit Lab 1. I've downloaded it and will check it out.

Regards,

dlogan,

Thank you for the link to your Summit lab. It looks very interesting.

I wonder why ALL possible parameters are not documented. For instance, I can't find documentation on these: IBIC_user, IBIC_pass, IBIC_server, IBIMR_user, IBIMR_pass, IBIMR_domain, IBIMR_folder, MR_BASE_DIR, CGI_PROG, WORPUSER, WORPPASS. It would be practical to publish a complete list of parameters, HTTP, IBI and whatever else can be passed.

Incidentally, I had to open a case to enable passing the B.I. Dashboard View name as a parameter - I can't believe this isn't currently available.

Regards,