Package Path Problem

[jeff_rob]

Hi,
I recently moved to a different company and took on the administrative duties as well as development.  There's something odd that I can't understand and hoped that maybe someone could shed some light on.

On our Test environment packages are in a folder named Packages, but in the Production environment the folder is named _Packages.  When I deploy I have to edit each package and change the path.  Even then it causes problems when reports try to connect.

I can't imagine why things are set up this way.  Seems like the folder names, and therefore the path should be the same in both environments.  I just wonder if there's some logic here that I'm missing.  I haven't done admin in the last five years so I'm a bit out of touch.

I'd like to change the Production folder to match the Test folder name, but don't know what all that might break.  We have Motio PI, so I can do mass changes, but I'd like to understand the implications before I try to change anything.

Any insight would be greatly appreciated.

Thanks,
Jeff

[blom0344]

_Packages must be someones clever way of making sure they are 'on top' when sorting the list in connection.  The underscore preceeds letters/numbers.
Do a full contentstore export of production for safekeeping, then change the name and test if things keep working. Alternative is to change test to match production. You need to set the new paths in models to publish to the right (changed) folder.

[jeff_rob]

Thanks, blom.  I hadn't even thought about it just being a sorting trick.  I sure can't see any other reason for it.

I like the alternative of changing Test to match Production.  Good advice.  Much less headache if there's a problem.

And thanks for the reminder to export the entire content store.

Jeff

[Suraj]

Just rename the testing folder to match prod and deploy.
Shortcuts will break in Test so just deploy the reports after that.

Also, Cognos has it's own sort manager without needing to add _ or 0 in the name.

[blom0344]

Just rename the testing folder to match prod and deploy.
Shortcuts will break in Test so just deploy the reports after that.

Also, Cognos has it's own sort manager without needing to add _ or 0 in the name.

What sort manager do you mean?  Changing the folder name in test means - if you publish to test - also changing publishing paths as these are stored in the model itself..

[Suraj]

What sort manager do you mean?  Changing the folder name in test means - if you publish to test - also changing publishing paths as these are stored in the model itself..

Not sure if I understand all the things you mentioned.
There is no need to change name of the package/folder to make them appear on the top.
Sort order can do that in Cognos connection. Attached is a screenshot.

When deploying content from one env to another, it's best practice to have same folder structure so reports/views/shortcuts all can be deployed without risk of breaking the connections.
Moving/renaming/organizing packages from one folder to another does not break reports, only the shortcuts are broken.

[blom0344]

AFAIK sorting is done alphabetically , either ascending or descending. An underscore comes first before any other characters, so sorting ascending makes sure that a folder starting with it is then on position 1 (always)

The publication path from framework manager to the receiving Cognos environment is stored in the model after the first publishing action. Changing object locations in connections means changing the publishing path from the model (a trivial action of course)

[Suraj]

AFAIK sorting is done alphabetically , either ascending or descending. An underscore comes first before any other characters, so sorting ascending makes sure that a folder starting with it is then on position 1 (always)

Yes and no.
Yes if you leave the Cognos sort order untouched. Cognos will sort alphabetically by default.
No if you go in the sort order and pull the items to show first.
We are doing that for our users so they don't have to scroll down to see most frequently used packages/folders.
You can still change/override that sort temporarily by clicking on the top on 'Name' that toggles sort in asc, desc and then to default which goes by Cognos sort order (alphabetically if not touched).
Let's say you have 100 packages and you pull 5 to show on top.
Default sort now will have those 5 on the top and the remaining 95 in alphabetical sort order.

The publication path from framework manager to the receiving Cognos environment is stored in the model after the first publishing action. Changing object locations in connections means changing the publishing path from the model (a trivial action of course)

True if publishing from FM in PRD.
But deploying folders/packages from one env. to another does not care about what's in the model once it's published as the model is referenced only at the time of publishing.