Creation of new folder and allow only a specific group to access it

[sanchoniathon]

Hi,

I created a new group with a limited number of members in it in our cognos production environment. I then created a new cognos folder
The folder is empty for now.

The folder will be used by those users once i tell them that the new folder is available.

HOW DO I DO THE SAME FOR OUR COGNOS DEV environment ? I mean do i simply MANUALLY create this newly created cognos folder in our development environment and assign it the newly created cognos group ?
Or is there some automatic type of mechanism of exporting my newly created cognos folder with its permissions and then simply import it into cognos connection Development ?

Thanks for any advice

[MFGF]

Hi,

I created a new group with a limited number of members in it in our cognos production environment. I then created a new cognos folder
The folder is empty for now.

The folder will be used by those users once i tell them that the new folder is available.

HOW DO I DO THE SAME FOR OUR COGNOS DEV environment ? I mean do i simply MANUALLY create this newly created cognos folder in our development environment and assign it the newly created cognos group ?
Or is there some automatic type of mechanism of exporting my newly created cognos folder with its permissions and then simply import it into cognos connection Development ?

Thanks for any advice

Hi,

You can certainly deploy a folder from one environment to another. Where you need to be careful is in deploying the groups and roles between environments. You'd also need both environments to be using the same authentication provider (configured in the same way) for this to make sense. The reason you need to be careful is that a deployment has the option to "Include Cognos groups and roles" when you create it. This will add ALL the groups and roles from the Cognos namespace into the deployment. If your environments have these configured differently, you'll end up overwriting the groups and roles in the environment you are deploying to with the ones from the environment where you created the deployment.

Assuming you're OK with doing this, then when you are creating the deployment of the folder in your production environment, make sure you check "Include access permissions" and "Include Cognos groups and roles". But, as I say, be very careful you are comfortable with what this will do.

If it was me, I'd probably set up the group and the folder manually in the Development environment - it would probably take less time than creating the deployment, running it, moving the deployment archive from Production to Development, creating the import, then running it there.

Good luck!

MF.

[sanchoniathon]

Thanks for the info. I'm going to do it manually. Have a nice day.