report deployment

[Cognoster]

 suppose an author has modified an existing report and the production support  team has to run it on the production server, what will be the input to the production support team will it be an exe file?

[MFGF]

If it's a single report that's changed and the package remains the same, it could well be an XML file sent as text.

Otherwise it will be a zipped deployment export file.

MF.

[Cognoster]

So this zipped deployment export file  can be made to run on the production server

[MFGF]

Hi,

The process is that the Development team create a deployment export of the report from the Dev server, which is saved as a zipped file in the deployment folder.  This is then copied to the Production server, and the Production team create a deployment import from the deployment file to bring in the report on the Production server.  The imported report can then be run on this server.

Regards,

MF.

[Cognoster]

does the method which you have mentioned before have any anaogy to

that in BO...where we create an universe object...

[MFGF]

Hi,

No - not at all.  Creating a BO universe is the same principle as creating a Framework Manager package in Cognos 8 (unless I'm misunderstanding the reference to a universe object - I'm not a BO expert!)

In this thread we have been discussing deployment of one or more reports from a Development server to a Production server.  I don't know the process for this in BO.

MF.

[blom0344]

Nope. A universe (.unv)relates directly to the Cognos physical framework. In both cases you publish directly from this model (Cognos --> content store,  BO --> repository, nowadays to a file system)
The concept of package is very much a Cognos thing.

Universe objects relate directly to Cognos query subjects and query items/calculations.

Cognos  SQL query subject   <--->  BO  derived table

There is no analogy with reports whatsoever

[MFGF]

Thanks Blom!  Much appreciated! ;D