F00950 and html

antoine_mpo

Reputable Poster
Hi everybody,

This post is just to share with you something we experienced about F00950 (security workbench table) and html client.
Indeed, a jas instance doesn't deals with F00950 like a fat client.
We wanted to set different security for our production environment and for our others environments. To do so, we copied the standard F00950 (in SYS7333 tablespace) in production Control tables (PRODCTL tablespace), and then mapped F00950 to "Control Tables - Prod" data source for PD7333 and JPD7333 environment.
But we noticed that all the security set up for prod was effective with fat client but not in html (even after refreshing the security cache by stopping/starting the jas instance).

What we noticed is that jas instance used a jas.ini parameter to know where to look for F00950 table. it's the "Default Env" parameter of the "[DB SYSTEM SETTINGS]" section.
In our jas.ini, the parameter was set to "JDV7333", which is one of our html environment. Because of that, even if we connected to JPD7333 (for wich was mapped our F00950 copy), the jas server was looking for JDV7333 mapping and so used the standard F00950.

So, as a conclusion be carreful if you want to do the same : think of that parameter and remember that, as a consequence, you can't use the same jas instance to connect to 2 environments that doen't use the same F00950 mapping (because you can only set one Default environment for that instance).


Antoine.
 
Back
Top