在环境之间迁移 BO 报告
我们拥有标准的开发、测试、生产三级环境设置。每个环境都有自己的报表服务器、Web 服务器、数据库服务器等。
我们迁移的一部分是在服务器之间移动业务对象 (xi r2) 报表，但目前我们需要手动更新每个报表的连接设置。现在有超过 40 份报告，这有点令人痛苦，并且随着我们继续下去，这将成为一场噩梦。
由于我们生成报告的方式，我们无法在生成报告时动态更改连接字符串。我们使用存储过程而不是宇宙，因为这是团队最熟悉的。
任何建议将不胜感激。
We have the standard 3 environment setup of development, testing and production. Each environment has their own report server, web server, database server, etc.
Part of our migration is to move our business objects (xi r2) reports between the servers but as of right now we need to manually update the connection settings for each report. This is mildly painful now at 40+ reports and will become a nightmare as we continue.
Due to how we generate reports we cannot dynamically change the connection string when we generate the report. We are using stored procs instead of Universes because that is what the team is most familiar with.
Any suggestions would be greatly appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
有一个 API，您可以使用它以编程方式更新此类事情，尽管我不记得如何做到这一点。查看 Business Objects - IIRC 提供的文档，它们不是公开可用的（至少在 2006 年我上次使用它时还没有），因此您可能必须从供应商处获取它们。
There is an API that you can use to programatically update this sort of thing, although I can't remember how to do it. Check out the docs provided by Business Objects - IIRC they are not publically available (at least they weren't in 2006 when I last worked with it) so you may have to get them from the vendor.
查看 CrystalDecisions.Enterprise.Desktop.Report 程序集。有很多更改数据库连接的选项。
我为客户写了类似的东西来批量更改 Universe 和 WebI 报告。我想这对于水晶报表来说非常相似。
Take a look at the Report Class' ReportLogon Class in the CrystalDecisions.Enterprise.Desktop.Report Assembly of the BusinessObjects SDK. Quite a few options for changing the database connection.
I wrote something similar for a client to make bulk changes Universes and WebI reports. I would imagine that it is very similar for Crystal Reports.
你是在改变宇宙连接还是宇宙本身？
在我们的环境中，我们通过让环境之间的宇宙命名相同来解决这个问题，但它们每个环境都有不同的连接。这可以避免需要更改每个报告。
Are you changing the Universe Connection or Universe themselves?
In our environment, we worked around this by having the Universes named the same between environments but they each have a different Connection by environment. This prevents needing to change each report.
我进行了广泛的搜索，这似乎是一个不寻常的情况。我最终的解决方案似乎还可以，那就是在每个环境中都有一致的 DSN 连接字符串。这意味着每个连接字符串实际上是相同的。
它仍然感觉不对，如果有人有其他想法那就太好了。
编辑：
经过一些测试后，我发现我们的许多存储过程无法使用 DSN 运行，这完全失败了。之后我彻底放弃了。
I searched far and wide and it seems like this is an unusual circumstance. My final solution which seems to be okay is to have a consistent DSN connection string in each environment. This means that each connection string is effectively the same.
It still feels wrong and if anyone has other ideas that would be great.
EDIT:
This failed miserably after a little bit of testing I found out many of our stored proceedures would not run using the DSN. After that I gave up completely.