Installation - Role Separation Issues
Posted: Tue Jul 11, 2006 9:35 am
Hello dsxchange,
I have a client that has installed a new installation of DataStage on windows environment. Because of local security policies, they could not perform the installation as Administrator. Rather the installation was done under another id in the local administrator group.
DataStage engine and services are currently running under system id.
We didn't setup any additional groups and bind these to the datastage roles yet as described in the Administrator guide.
Under our current setup, all members of the local administrator group can connect to datastage cients including the Administrator client. Removing individual developer ids from the local administrator group prevents connecting to any of the DataStage clients.
My question:
Is the inability to connect to the Designer client with id not belonging to local administrator group an impact of not installing as Administrator id, or is it because we have not done the binding of datastage roles to windows groups as described in the Administrator guide, or is this potentially some other membership issue?
Thanks in advance.
Greg
I have a client that has installed a new installation of DataStage on windows environment. Because of local security policies, they could not perform the installation as Administrator. Rather the installation was done under another id in the local administrator group.
DataStage engine and services are currently running under system id.
We didn't setup any additional groups and bind these to the datastage roles yet as described in the Administrator guide.
Under our current setup, all members of the local administrator group can connect to datastage cients including the Administrator client. Removing individual developer ids from the local administrator group prevents connecting to any of the DataStage clients.
My question:
Is the inability to connect to the Designer client with id not belonging to local administrator group an impact of not installing as Administrator id, or is it because we have not done the binding of datastage roles to windows groups as described in the Administrator guide, or is this potentially some other membership issue?
Thanks in advance.
Greg