我的 Siebel Business Services 在哪里?

发布于 2024-09-10 18:29:15 字数 311 浏览 5 评论 0原文

在 Siebel 中,我可以在 2 个位置创建业务服务:

  1. Siebel 客户端
  2. Siebel Tools

在 Siebel 客户端中,我看不到在 Siebel Tools 中创建的业务服务,反之亦然。 (在 Siebel Tools 中创建新的业务服务后,我对其进行了编译 - 没有报告错误 - 并使用 Siebel Tools 菜单中的“调试”运行客户端。)

您知道为什么吗?

谢谢!

编辑:我使用示例数据库,我没有签入或签出任何内容。我对部署过程还不太满意,只是深入研究文档。

in Siebel I can create Business Services at 2 locations:

  1. Siebel Client
  2. Siebel Tools

In the Siebel Client I cannot see the Business Services created in Siebel Tools, and vice versa.
(After creating a new Business Service in Siebel Tools, I compiled it - no errors reported - and ran the client with "Debug" from the Siebel Tools menu.)

Do you know, why?

Thanks!

Edit: I use the Sample data base, I did not check in or check out anything. I am not comfortable with the deployment process yet and just digging through the docs.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

锦爱 2024-09-17 18:29:15

如果您使用服务器脚本编写业务服务,那么业务服务将被编译到SRF中。 SRF 本身之外不会有任何物理文件,并且不会显示在 Siebel 客户端中。

如果您使用浏览器脚本编写业务服务,那么业务服务将转换为外部 .js 文件并放入您的脚本目录中。脚本目录在“工具”或 genbscript 命令行实用程序中指定。

希望这有帮助。

If you wrote the business service using server script, then the business service will be compiled into the SRF. There will be no physical files outside of the SRF itself, and it will not show up in the Siebel client.

If you wrote the business service using browser script, then the business service will be converted to an external .js file and dropped in whatever your script directory. The script directory is specified in Tools or in the genbscript command-line utility.

Hope this helps.

半岛未凉 2024-09-17 18:29:15

完美解释了存储库业务服务和运行时业务服务之间的区别 这里

只需复制粘贴即可:

在 Siebel 中,我们可以在两个地方编写业务服务。

  • Siebel 客户端
  • Siebel 工具

我们所做的脚本没有什么不同,但有
这些业务服务的执行方式存在差异。

就我的知识(非常有限:))而言
它们之间的区别如下。

客户端是独立于SRF的,工具是依赖于SRF的(哪个
意味着即使我们想稍微做一点改动,也需要更改 SRF
改变)
Siebel Client BS 在运行时编译,Siebel Tools BS 在编译 SRF 时编译

当您必须做出以下决定编写业务服务时
因素会影响您的决定。

性能:Tools BS 在性能方面略有优势
(理论上)因为它是预先编译的并且只是在运行时执行
时间。

灵活性:Client BS 为您提供最大的灵活性
您可以随时更改代码。所以,如果灵活性更大
对您来说很重要,那么 Client BS 适合您。

IDE:从开发人员的角度来看,Tools BS 为您提供了更好的 IDE 和
更好的语法检查。客户端 BS 有一个蹩脚的 IDE 并且 zilch
语法检查,只是我们编写代码的一个字段。(我已经花了
调试客户端 BS 几个小时只是为了发现我拼写错误
变量名:( )

但我仍然没有找到任何一个可以证明这一点的可靠点
帮助我们准确确定何时应该使用客户端 BS 或
工具方 BS。这主要取决于开发人员的选择,谁来编写
BS。所以,我将这篇文章作为一个悬而未决的问题来问大家
关于您的意见可以帮助我们做出正确的决定
时间。

Perfect explanation of the difference between repository business services and run-time business services is provided here:

Just copy-paste it:

In Siebel we can write business services in two places.

  • Siebel Client
  • Siebel Tools

There is nothing different in the scripting that we do but there are
differences in how these business services are executed.

As far my knowledge (which is pretty limited :) ) is concerned the
difference between them are as following.

Client side is SRF independent and Tools is SRF dependent (Which
means an SRF change is required even if we want to make a slight
change)
Siebel Client BS Compiled at Runtime and Siebel Tools BS is compiled when we compile the SRF

When you have to make decision of writing a Business Service following
factors can affect your decision.

Performance: Tools BS has slight advantage of Performance
(Theoretically) as it is compiled before hand and just executed at run
time.

Flexibility: Client BS offers you ultimate flexibility as you can
change the code anytime you want to. So, if flexibility is more
important to you then Client BS is for you.

IDE: From developers perspective Tools BS provides you better IDE and
better syntax checking. Client Side BS has a crappy IDE and zilch
syntax checking,just a field where we write the code.(I have spent
hours debugging Client Side BS just to find out that I had misspelled
a variable name :( )

But still I have not come across even a single solid point that can
help us to determine exactly when we should use Client Side BS or
Tools Side BS. It mostly depends on developer’s choice who is writing
the BS. So, I am leaving this post as an open question asking you all
about your inputs which can help us to take right decision as right
time.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文