We are currently moving from BO 4.1 to 4.2. We have few reports with hyperlinks in earlier version. When we migrate them to 4.2 Dev region, all the hyperlinks were broken and we have fixed them.
Our Admin team is using PMT for report migrations in 4.2. When they migrate the reports through different regions (Test, Stage and Prod)
I know we can keep same CUID’s during the migration? I just don’t know how to do it, is there any options admins will select to do it? or BO will retain the CUID’s by default?
Our admin team is suggesting us to use sDocName instead CUID in the opendocument to avoid any issues in future. (their intension is CUID’s may accidentally change, but report name will be consistent)—Is this the best option?
Interesting. I think the CUIDs must not change if you upgrade from 4.1 to 4.2.
Does your migration procedure include copying of the reports within the same environment? If a report is copied, the CUID will obviously change.
The report name can also accidentally change. More over you can have 2 version of the report with the same name in the environment. Then opendocument will open the first it finds. And sPath may be deprecated in future:
“sPath does not support the use of localized folder names which are available in this release. Legacy documents that use sPath to reference the correct folder name as stored in the CMS will continue to work while under deprecation. But it is recommended that you migrate your links to use the iDocID parameter instead.”
We’re in the process of setting up a Load balancer, for which we cloned our primary BO server and created a secondary (with all the reports). Existing reports are just fine in both primary and secondary with same
CUID.
My problem is, when I deploy a new report in primary, how can I copy it to the secondary server with the same CUID?
Am new to Crystal and BO server. Any help with detail would be highly appreciated. Thanks.
I did not get the point. If you set a load balancer that seems to me you want a user loadbalancing eventually a servers redundancy. it this case instead of server cloning I would install a second node and connect it to the 1st node (= setup a cluster) with the same repostitory without any copying…
if is meant the 2nd node is far far away - then setup another server/env. (IMHO not by cloning) and using Federation services you can “mirror” the content from one to another…
Thanks for the reply tom_kar. Idea to clone existing BO server is to replicate all rpts from the primary BO server to secondary.
If I do a fresh install of 2nd node (mean new server), how can I copy all my rpts from 1st node to 2nd node
(to retain the same rpt ID)? Please explain. Appreciate your time. Thanks.
If you want both the nodes (1 & 2) to work as a cluster, while installing BO on the 2nd node (you’ll need point to the existing repository) and in that case you don’t need to copy of the reports, as both the nodes will be looking at the only copy of the reports on the 1st node (or on a shared drive), and after installation on 2nd node, (from CMC) you’ll need to update the Input FRS and Output FRS default location to that of the 1st node (or the shared drive).
Before Configuring, checkout the pic in the below page, we see only 1 FRS or File Repository Server (WIN FRS01), and multiple nodes (WIN PB04 and WIN PB05).
(BOB member since 2007-07-04)
(BOB member since 2011-10-14)