TIBCO Business Works 的开发环境是什么？
我看到了 TIBCO 开发人员的所有这些职位帖子，但在 tibco.com 上我无法真正挖掘开发人员在这个平台上以代码方式做什么，因为这更适合最终用户。是基于JAVA的平台吗？
I see all these job posts for TIBCO developer but from tibco.com I couldn't really dig what a developer does codewise on this platform because that is geared more towards endusers. Is it a JAVA based platform?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我假设您正在谈论 TIBCO Business Works，因为这是大部分开发工作完成的地方。
TIBCO Business Works 是一个基于 Java 的平台，但通常很少用 Java 进行开发。 TIBCO Business Works 的核心是一个 XSLT 处理引擎，具有大量（我的意思是大量）连接组件（在 TIBCO 世界中称为“Starters”和“Activities”）。
开发是通过将启动器链接到活动并最终链接到结束活动以图形方式完成的，非常类似于传统的流程图。您可以在此屏幕截图的右上角看到我的意思：
这些图中的每一个都称为流程定义，Java 中最接近的等效项是方法，但是它们是与 C 函数关系更密切，因为没有流程定义类的概念。
仔细观察，您会发现 StorePO Publish To Adapter Activity 已被选中。在右下角，您可以看到此活动的输入是从其他流程数据“映射”的（可以是“开始”的输出，也可以是其他活动的输出）。这个映射实际上是XSLT，只是直观地表示。因此，将映射的根节点（在本例中为“主体”）复制到文本文档中会粘贴为 XSLT（您甚至可以在那里编辑它，如果您愿意的话，可以将其复制回来；当您需要时，这很有用）进行搜索和替换）。
回顾流程定义，有一个 CheckInventory 调用流程活动。这是您从正在处理的流程定义中调用另一个流程定义的方式。事实上，这个流程定义有一个简单的启动活动，这表明它是从另一个流程定义调用的。
启动程序流程是具有流程启动程序而不是启动活动的流程定义。流程启动器根据某些事件触发流程定义的调用。例如，JMS 队列接收器进程启动器将在收到特定 JMS 消息时触发。有许多这样的进程启动器，包括 SOAP、HTTP、SMTP 甚至普通的旧式 TCP。
同样，还有许多活动，包括上面的活动以及 JDBC 和 FTP。
在没有实际访问 TIBCO Designer 的情况下，增强 TIBCO 角色技能的最佳方法是专注于 XPath 和 XSLT，因为这正是您将要使用的主要内容。
I'll assume that you are talking about TIBCO Business Works as this is where the majority of the development is done.
TIBCO Business Works is a Java based platform, however normally very little development is done in Java. At it's heart TIBCO Business Works is a XSLT processing engine with lots (and I mean lots) of connectivity components (called Starters and Activities in the TIBCO world).
Development is done graphically by linking the Starter to Activities and eventually to a End Activity, very much like a traditional process diagram. You can see what I mean in the top right of this screen shot:
Each of these diagrams is called a Process Definition and the closest equivalent in Java is a method, however they are more closely related to C functions as there is no concept of a Class for Process Definitions.
Looking closely, you'll notice that the StorePO Publish To Adapter Activity is selected. In the bottom right you can see the input to this activity is "mapped" from other process data (which can be either the output from the Start, or the output from other activities). This mapping is actually XSLT, just represented visually. So much so, that copying the root node of the mapping ("body" in this case) into a text document pastes as XSLT (you can even edit it there and copy it back if you are so inclined; good for when you need to do a search and replace).
Looking back at the Process Definition, there is a CheckInventory Call Process Activity. This is how you invoke another Process Definition from the one you are working on. In fact, this Process Definition has a plain Start Activity, which indicates that it it invoked from another Process Definition.
Starter processes are Process Definitions that have a Process Starter instead of a Start Activity. The Process Starter triggers the invocation of the Process Definition based on some event. For instance, a JMS Queue Receiver Process Starter, will trigger when it receives a specific JMS message. There are many such Process Starters, including SOAP, HTTP, SMTP and even plain old TCP.
Likewise the are many Activities, including the ones above and JDBC and FTP.
Without actually having access to TIBCO Designer, the best way to beef up your skills for a TIBCO role is to focus on XPath and XSLT as that's mostly what you'll be working with.
TIBCO AMX Business Works 是一个用于集成和自动化目的的 Java 平台。它使用基于插件的架构，这意味着您可以扩展功能。该产品现已从 5.x 版本更改为 6.4.x 版本，包括微服务功能、容器化、云支持等。
它使用模型驱动的开发方法来减少编码部分，这就是它如此强大的原因。
您可以在文档官方网站上找到更多信息文档 TIBCO AMX BW
如果您懂西班牙语并想了解 5.x 版本，我在 TIBCO AMX BW 教程
TIBCO AMX Business works is a Java platform use for integration and automation purposes. It uses a plug in based architecture which means that you can extend the functionality. The product has changed from their 5.x version to 6.4.x version now to include micro services capabilities, containerization, cloud enablement, etc.
It uses a model driven development approach to reduce coding parts, that is why is so powerful.
You can find more information on the documentation official siteDocumentation TIBCO AMX BW
If you know spanish and want to learn about the 5.x version I have a set of video tutorials at TIBCO AMX BW Tutorials