Thus, this article has shown how to solve your transliteration challenges using Information Server DataStage.
因此，本文就展示了如何使用InformationServer DataStage来解决您的音译挑战。
While the job will no longer run in parallel, or use multiple CPUs, it will use less memory and run faster because the InfoSphere DataStage server no longer has to swap.
然而，任务再无法并行运行，或使用多个CPU，它会使用更少的内存，并会运行得更快，因为InfoSphereDataStage服务器不需要再进行内存交换。
With Web services pack, DataStage can easily access Web service operations within a DataStage server job.
通过Webservices包，DataStage很容易在一个DataStage服务器任务中访问Web服务操作。
The recommended number of logical nodes that you should use on an InfoSphere DataStage installation is usually half the number of CPUs of the InfoSphere DataStage server.
建议在InfoSphereDataStage安装时使用的逻辑节点数量，通常为 InfoSphere DataStage服务器CPU 数量的一半。
The IIS server contained both the server and client for developing the DataStage job.
IIS服务器同时包含了用于开发DataStage 作业的服务器和客户机。
The common requirement is to fetch Notes data into DataStage, perform an extract, transform, and load (ETL), and then pass this data to other Information Server modules for more ETL processing.
常见的需求是将Notes数据提取到DataStage中、执行解压、转换和加载(etl)，然后将此数据传递给其他InformationServer模块以便于完成更多etl处理。
This means that less data is read by WebSphere DataStage in the combined implementation with WebSphere Federation Server (70,663 rows) than in the initial implementation (2.4 million + 77,636 rows).
这意味着当与WebSphereFederationServer结合使用时，WebSphereDataStage读取的数据（70,663行）要少于在原先的实现中所读取的数据（240 万 + 77,636 行）。
This means that less data is read by WebSphere DataStage in the combined implementation with WebSphere Federation Server (70,663 rows) than in the initial implementation (2.4 million + 77,636 rows).
这意味着当与WebSphereFederationServer结合使用时，WebSphereDataStage读取的数据（70,663行）要少于在原先的实现中所读取的数据（240 万 + 77,636 行）。
应用推荐