Hi, I am new to this discussion group. Hopefully, you guys will be able to help me out.
My questions have to do with deploying Cognos Series 7 using Active Directory as directory server.
Before, I ask the question, I should explain the end objective of this implementation
1. Two separate and distinct Cognos environment (Pre-Deployment and Production)
2. Each environment (ticket server, Power Play Enterprise Server, IWR, Upfront) is on one W2K server
3. Currently Cognos environment use NDS with no security. We plan to deploy Series 7 using Active Directory for security
4. Operation, an operator global group, will maintain the daily Cognos operations.
-publish new cubes
-publish new reports
-change access rights to cubes and reports
5. Operation does not have right to update anything to the Active Directory.
Here are my questions
1. Does the Cognos Server have to be on a Domain Controller?
-If yes, it goes against our belief that a "Domain Controller should not host any applications"
2. Active Directory's Schema is being updated by Congos as security right on cubes and reports being updated.
-What happens to the schema entries when the cubes/reports are no longer in use?
3. Security Concern - Operation a normal user group have ways to update the Active Directory schema through the Cognos Access Manager/Cognos API
-Is this a good practice?
4. How do maintain a separate Production and Pre-Deployment environment, if both of them use the same directory?
One of my initial ideas is to have three different Active Directory where the three AD trust each other.
1. Production Network AD
-contains all user accounts and groups definition
2. Cognos Production AD
-does not contain user or group information
3. Cognos Pre-Produciton AD
-does not contain user or group information
Does anyone know how people implement Cognos with Active Directory?
Anyone think of any problems with my three AD approach?
Finally, any suggestions?
Thanks a bunch everyone
My questions have to do with deploying Cognos Series 7 using Active Directory as directory server.
Before, I ask the question, I should explain the end objective of this implementation
1. Two separate and distinct Cognos environment (Pre-Deployment and Production)
2. Each environment (ticket server, Power Play Enterprise Server, IWR, Upfront) is on one W2K server
3. Currently Cognos environment use NDS with no security. We plan to deploy Series 7 using Active Directory for security
4. Operation, an operator global group, will maintain the daily Cognos operations.
-publish new cubes
-publish new reports
-change access rights to cubes and reports
5. Operation does not have right to update anything to the Active Directory.
Here are my questions
1. Does the Cognos Server have to be on a Domain Controller?
-If yes, it goes against our belief that a "Domain Controller should not host any applications"
2. Active Directory's Schema is being updated by Congos as security right on cubes and reports being updated.
-What happens to the schema entries when the cubes/reports are no longer in use?
3. Security Concern - Operation a normal user group have ways to update the Active Directory schema through the Cognos Access Manager/Cognos API
-Is this a good practice?
4. How do maintain a separate Production and Pre-Deployment environment, if both of them use the same directory?
One of my initial ideas is to have three different Active Directory where the three AD trust each other.
1. Production Network AD
-contains all user accounts and groups definition
2. Cognos Production AD
-does not contain user or group information
3. Cognos Pre-Produciton AD
-does not contain user or group information
Does anyone know how people implement Cognos with Active Directory?
Anyone think of any problems with my three AD approach?
Finally, any suggestions?
Thanks a bunch everyone