Which Table to backup? DB crash everything is game over. Should have a per-user upload file limit. Every project is different.
Some Big , some Small. Data Cache can be set file by file. Why not? This is an unfriendly design for an Admin user. Because we pay the money. And other BI system did it. The content store is intentionally a black box database. Not a good solution. Show 3 more comments. Q1 It is not clear what you mean by "I need to know the upload file location to backup files" i.
The uploaded files are stored in the content store. If you want to back up, create a deployment. You can also back up the CM data base itself. By default, the default upload location is the user's my content. You can change that. Q2: It is not possible to set a per-user upload file limit. C'est Moi C'est Moi 1 1 gold badge 2 2 silver badges 7 7 bronze badges. All done, now you can use the samples. Note that the Framework Manager models and Transformer models are also included in the sample files for when you want to adjust the sample material.
Archive Random. Only Cognos most of the time that is. Visit us at cognossource. We will describe how to get the following samples working: The Go Sales and Great Outdoors databases for compatible and dynamic query mode. The Go Sales Dynamic Cube samples requires the previous step.
A selected number of TM1 samples. Sample packages and content for the above requires the previous steps. Installing the Cognos Samples installation package Note that the samples come in a separate installation file not included in the product installation file. Unzipp the installation file twice 7Zip and locate the installation file for your operation system.
Run the installation wizard and follow the screens. Browse around a bit to make sure that there are actually tables in them with data. If you want you can now clean up the files in the samples folder. All Parts: 1. Create data source connections for the samples databases Next step is to make these data sources known to Cognos. Click next. Now you have to enter the connection string.
Here you have some options. The sign-on choice will depend on how you want to log on to your database. Then simply create an export job from dev, and import jobs in UAT and prod. Run the export in Dev, and the import is immediately available in the other enviornments, so just run the import jobs.
I saw a mechanism for automating this in a supportlink document, it used event studio to trigger all the jobs, export and import using an external trigger! For your security this email contains a digital signature which verifies the identity of the email sender. If you are not the intended recipient you must not copy, distribute, disseminate, nor act upon the information. If you have received this message in error do not open any attachment, instead please inform the sender and then delete the message from your system.
We have taken reasonable steps to reduce risks against viruses but please rely on your own virus check as no responsibility or liability can be accepted for any damage sustained as a result of this transmission.
Hi Terry, on the same issue. Please guide. You need to have RDC connection for the two servers. The deployment folder is specified in Cognos Configuration, you can make this a common folder between the installations which would allow export from dev and import to production to be simplified, but you would need to set this up in the configuration files, and make sure the relevant access rights were set on the shared folder.
Someone has to have access to the other servers, so they should be able to copy your file to those environments, or copy from those environments. IF they did, that one person would be able to copy things from dev to prod without anyone else getting involved, bypassing all processes that might be in place to guard against unauthorized updates going into prod.
Some of the third party tools like MotioCI mentioned above do not require access to the servers. MotioCI is a web application that you can use to move content from dev to qa to production. It does make it easier and removes this need to remote to the servers. However, you do have to be granted access to the tool and given rights to move content into the given Cognos environment.
The standard Cognos tools as well as any third party tools better meet these requirements, and you will find they do subject to proper configuration. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy.
Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account. We'll send a magic link to your inbox.
0コメント