加载中…
个人资料
钓钓没有鱼
钓钓没有鱼
  • 博客等级:
  • 博客积分:0
  • 博客访问:900
  • 关注人气:0
  • 获赠金笔:0支
  • 赠出金笔:0支
  • 荣誉徽章:
相关博文
推荐博文
谁看过这篇博文
加载中…
正文 字体大小:

B2B Solutions using Websphere Partner Gateway(8)

(2008-12-18 15:53:17)
标签:

it

    Implementation scenarios

    This chapter describes the different steps to implement a B2B solution between four business partners. By adding features and functions in a gradual way, it becomes easier to understand why configuration tasks are done. It also offers the one who implements it, a check-point to perform some validation before moving to the next step. This chapter presents a general discussion about the implementation process, and refers you to subsequent chapters for details.

    本章介绍在4个商业伙伴间实施一个B2B解决方案的不同步骤。通过不断增加特性和功能,可以很容易的理解为什么配置任务完成了。它也提供了实施B2B,在到下一步之前执行一些确认的检查点。本章展示了一个关于实施过程的大体的讨论,并提到以后各章的细节。

    4.1 Implementing WebSphere Partner Gateway Enterprise for Windows

    The first implementation phase is setting up WebSphere Partner Gateway Enterprise for Windows in a dual server environment. The three runtime components of WebSphere Partner Gateway are running on a single machine that has the host name wpgv6hub. The DB2® server and the MQ queue manager are running on a separate machine, with the host name wpgv6db.

    实施的第一步是在一个双服务器环境上安装WebSphere Partner Gateway Enterprise for Windows。WebSphere Partner Gateway的三个运行组件在一台主机名为wpgv6hub机器上运行。DB2® 服务器和 MQ 队列管理器运行在一台名为wpgv6db的机器上。

    Chapter 5, “WebSphere Partner Gateway Enterprise on Windows” on page 59, discusses details about the planning and decisions that you need to make to

build such an environment successfully.

    第5章,“WebSphere Partner Gateway Enterprise on Windows”第59页,讨论了一些与计划和决策相关的细节,需要按照这些来做才可以把环境建立成功。

    Figure 4-1 shows an overview of this setup. At the end of this phase we have a working WebSphere Partner Gateway server, but with no connected partners and no connections with internal systems.

    图4-1展示了这个装置的整体情况。在这步结束我们会有一个运行的WebSphere Partner Gateway服务器,但是没有任何的连接伙伴,也没有连接到任何的内部系统。

    4.2 Implementing WebSphere Partner Gateway Advanced for AIX

    The next phase is the implementation of WebSphere Partner Gateway Advanced on a single AIX machine. It involves using a local DB2 server and a local MQ queue manager.

接下来一步是在一台AIX机器上实施WebSphere Partner Gateway Advanced。这包括使用一个DB2服务器和一个本地MQ队列管理器。

    Chapter 6, “WebSphere Partner Gateway Advanced for AIX” on page 109, describes the setup of all prerequisite components. It also provides tips about how to validate the setup of DB2 or how to verify that prerequisite components are configured correctly. Then, at the end of that chapter we have a working WebSphere Partner Gateway server that is not connected to any other partner or system, as shown in Figure 4-2.

    第6章,“WebSphere Partner Gateway Advanced for AIX”第109页,描述了所有必要的组件的安装。它还提供了协议关于确认DB2的安装或者验证这些必要组件正确配置的秘诀。然后,在这章的结尾,我们有一台工作的WebSphere Partner Gateway服务器但是没有连接到任何其他伙伴或系统,就如图4-2所示的。

    4.3 Implementing a basic exchange

    Given the two WebSphere Partner Gateway implementations on AIX and Windows, we learn how to set up a basic exchange between those two WebSphere Partner Gateway servers. Chapter 7, “Creating a basic B2B exchange” on page 137, explains how to configure WebSphere Partner Gateway so that electronic data interchange (EDI) documents can be exchanged in both the directions over HTTP in an AS2 package.

    通过这两个在AIX和WINDOWS上的WebSphere Partner Gateway实施,我们可以学习到如何安装一个在两个WebSphere Partner Gateway服务器之间的基础的交换。第7章,“Creating a basic B2B exchange”第137页,解释了如何配置WebSphere Partner Gateway以便EDI文档可以通过一个AS2包中的HTTP协议双向交换。

    Figure 4-3 on page 50 illustrates the configuration steps to build the environment. A natural approach is to split this into a discussion about the outbound flow and a discussion about the inbound flow and possibly a validation for the outbound flow before proceeding to build the inbound flow. However, this book describes the setup by focusing more on the role-based approach.

    第50页图4-3描述了创建环节的配置步骤。一个通常的方式是将它分成一个关于对外流程的讨论和一个关于对内流程的讨论,以及在建立对内流程之前的对对外流程的确认。无论如何,本书描述的安装更注重基础。

    In Chapter 7, “Creating a basic B2B exchange” on page 137, we limit the communication to one type of document and to one partner. We also limit ourselves to file-based input and output. That is, we configure WebSphere Partner Gateway to retrieve EDI documents from a directory and send it to the trading partner that is encoded in the EDI document. The target WebSphere Partner Gateway server drops the EDI document into a directory as well.

    在第7章,“Creating a basic B2B exchange”第137页,我们只限制了一种文件类型和一个伙伴来进行通讯。也限制了以文件为基础进行输入和输出。那就是,我们配置WebSphere Partner Gateway来从一个索引中检索EDI文档,并将其发送给贸易伙伴,这些都是在EDI文档中编码了的。WebSphere Partner Gateway把文档仍到一个索引的目标中也是如此。

    Thus, the MQ infrastructure at either side is not used much at this stage, except for communication between WebSphere Partner Gateway components. At the end of this chapter, we will see how to exchange documents in both directions and receive message disposition notifications (MDNs) from the target server.

    因此,在这样一个场景下,MQ在每一侧的基础结构并没有被使用,除了WebSphere Partner Gateway之间的通讯。在本章的结束,我们会明白如何双向交换文档以及从目标服务器接收message disposition notifications (MDNs)。

    4.4 Securing the exchange between Company E and Company A

    In Chapter 7, “Creating a basic B2B exchange” on page 137, we assume default values for AS2 connection. This means that no encryption or digital signatures are used. The EDI document is sent in clear text. This is not good enough for a real- world implementation.

    在第7章,“Creating a basic B2B exchange”第137页,我们假设了AS2连接的值。这意味着不加密和不使用数字签名。EDI文档是用明文发送的。这个在现实世界实施来说并不好。

    Chapter 8, “Securing the B2B exchange” on page 207, explains how to secure the exchange of the EDI documents. It demonstrates how to obtain keys and certificates and how to upload them to WebSphere Partner Gateway. This is done to switch to an AS2 connection where sensitive business data is encrypted and where EDI documents are signed, so that the receiver can validate the origin.

    第8章,“Securing the B2B exchange”第207页,解释了如何保障EDI文档交换的安全。它演示了如何获取密钥和证书,以及如何把他们上载到WebSphere Partner Gateway。这样是为了切换到AS2连接,在这敏感的商业数据被加密,EDI文档也签名了,这样接收者可以确认它们的来源。

    Chapter 8, “Securing the B2B exchange” on page 207, describes the process again from a role-based perspective, so that it becomes clear which tasks can be performed by either the hub administrator, the WebSphere Partner Gateway server, or by the community Participant (Figure 4-4).

    第8章,“Securing the B2B exchange”第207页,又一次基于角色的观点描述了整个过程,这样哪项任务是被枢纽管理员,WebSphere Partner Gateway服务器还是community Participant执行的就很清楚了。

    4.5 Implementing WebSphere Partner Gateway Express for Windows

    After completing the security setup, we extend the exchange with an additional partner (Figure 4-5).This is again performed in two steps. First, we implement WebSphere Partner Gateway Express for windows. Given that WebSphere Partner Gateway Express has fewer requirements for other software products, such as DB2 and WebSphere MQ, this is a straightforward process, as discussed in Chapter 9, “WebSphere Partner Gateway Express on Windows” on page 261.

    完成了安全机制的安装,我们增加了一个伙伴来扩展这种交换。这次又是两个步骤。首先,我们实施WebSphere Partner Gateway Express for windows,这个版本需要很少量的其他软件,比如DB2和WebSphere MQ,这是一个简单的过程,正如第9章所讨论的,“WebSphere Partner Gateway Express on Windows”第261页。

    4.6 Using FTP with WebSphere Partner Gateway

    The B2B exchange is extended even further, so that it can also support FTP. Company A wants to extend its B2B infrastructure to include a document exchange with Company F. However, Company F is reluctant to jump quickly on a technology that is new to the IT department of Company F. At the same time, Company A wants to build a solution sooner rather than later. A compromise is found between Company A and Company F by implementing an FTP-based solution. Company F has extensive experience with FTP and thus they can implement a document exchange with Company A rather quickly.

    这个B2B交换正在尽一步扩大,以便可以支持FTP。A公司想要扩展它的B2B基础设施来增加一个与F公司的文档交换。无论如何,F公司不愿这么快的采用一项对于IT部门来说是新的技术。同时,A公司想要尽早建立这个方案。一个折中的办法是实施一个基于FTP的方案。F公司可在FTP方面有丰富的经验,因此他们可以与A公司更快地实施文档交换。

    Figure 4-7 on page 54 shows a schematic overview of the B2B exchange. It shows the existing AS2-based exchanges of Company E with Company A (for EDI) and Company E with Company X (for XML). Within this infrastructure, we add an exchange of Company A with Company F over FTP, as explained in Chapter 12, “Integrating FTP servers” on page 335.

    54页的图4-7展示了B2B交换的专题概述。它说明了E公司与A公司之间现有的基于AS2的交换,以及E公司与X公司之间的交换。通过这个基础设施,我们可以增加一个A公司与F公司通过FTP的交换,正如第12章说解释的,“Integrating FTP servers”第335页。

    This version of WebSphere Partner Gateway also has a solution to offer for companies such as Company F and other companies like Company V, introduced in section 4.7, “Using FTP Scripting to enable Value Added Network (VAN) connectivity” on page 54, which is the FTP Scripting based solution.

    这个WebSphere Partner Gateway版本也有一个提供给类似F公司或者像V公司似的企业的解决方案,在第4.7节介绍的那样,“Using FTP Scripting to enable Value Added Network (VAN) connectivity”在第54页,也是基于FTP脚本的解决方案。

    The advantage of the FTP Scripting based solution is that now for Company A to receive files from Company F, it need not have an FTP server at its end. With the FTP Scripting solution, Company A can directly pull files from his account, on the Company F’s FTP server.

    基于FTP脚本的解决方案的优势在于A公司从F公司接收文件,但是A公司自己并没有FTP服务器。通过FTP脚本方案,A公司可以直接把文件从F公司的FTP服务器上的自己的帐户中拉出来。

    4.7 Using FTP Scripting to enable Value Added Network (VAN) connectivity

    The B2B exchange is further extended to enable connectivity to a VAN. Company E wants to extend its B2B infrastructure to include a document exchange with Company V. Company V, like Company F, is reluctant to jump quickly to a new technology that is new to the IT department of Company V. Company E and Company V work out a FTP Scripting based solution.

    B2B交换的尽一步扩展是支持VAN的活动。E公司想扩展他的B2B基础设施来增加一个与V公司的文档交换。V公司,类似于F公司,也不愿意这么快使用一项对IT部门来说很新的技术。E公司和V公司采用了基于FTP脚本的方案。

    Figure 4-8 shows a schematic overview of the complete B2B scenario. We extend this infrastructure to add an exchange with Company V as explained in Chapter 13, “Enabling VAN connectivity using FTP Scripting” on page 419.

    图4-8展示了一个完整的B2B场景的专题概述。我们通过增加与V公司的交换来扩展这一基础设置,正如第13章所解释的,“Enabling VAN connectivity using FTP Scripting”在第419页。

    4.8 Managing the B2B infrastructure

    Because the infrastructure is now a bit more complex, we can take a closer look at the manageability of the infrastructure. As usual, the change from 1 to 2 introduces another level of complexity, and when this level is understood, moving from 2 to n becomes easy.

    因为基础设施现在已经很大很复杂了,我们可以近距离的观察这个基础设施的管理能力。通常,改变从1到2引入了另一个曾面的复杂性,当这一层次被理解了之后,从2到n就容易了。

    Each player in the system has an important role. The hub administrator needs to determine if the system as a whole performs well, for example, by ensuring that there are no bottlenecks or errors. Several tools and options are available to the hub administrator.

    系统中的每一项都有着很重要的角色。枢纽管理员需要判断整个系统是否运转正常,录入,通过确认系统中没有瓶颈或者错误。枢纽管理员可以使用许多工具和选项。

    The community manager wants to look at the WebSphere Partner Gateway system from a business perspective. This person asks, “What documents have I received? From whom? What is the status of each document? Did I receive an MDN for that transaction?” For all of these questions, the WebSphere Partner Gateway server contains tools and viewers so that the community manager has a good view on their business.

    community manager需要从业务角度去观察WebSphere Partner Gateway系统。他问,“我收到了哪些文件?从哪?每个文件的状态如何?我从交易中收到MDN了吗”这些问题,WebSphere Partner Gateway服务器包含工具和显示程序,community manager通过这些工具可以对他们的业务有一个清晰的认识。

    In addition to management options for the hub administrator and the community managers, WebSphere Partner Gateway also has tools and viewers available for the community participant. Thus, if the community Participant receives no MDN or receives an error report, they can log on to the WebSphere Partner Gateway of his partner and try to determine why their transaction resulted in an error.

    除了枢纽管理员和community manager的权限管理,WebSphere Partner Gateway也有工具和显示程序提供给community participant。因此,如果community participant没接收到MDN或者接收到一个错误报告,他们可以登录到伙伴的WebSphere Partner Gateway上尝试确认为什么会出现错误。

    Chapter 11, “Managing the B2B exchange” on page 307, explains all of this in greater detail.

    第11章“Managing the B2B exchange”第307页,对这些做了详细解释。

    4.9 EDI translation

    WebSphere Partner Gateway now has the built-in ability to support electronic data interchange (EDI) translation, which was facilitated in the earlier version of the product by having to integrate with the WebSphere Data Interchange product.

    WebSphere Partner Gateway现在具有内嵌的支持EDI翻译的能力,这是为了早期版本与WebSphere Data Interchange产品集成提供便利。

    In addition WebSphere Partner Gateway offers abilities to, perform EDI packaging, transformation, validation, enveloping, de-enveloping, batching and splitting.

    此外,WebSphere Partner Gateway具有执行EDI打包,转换,确认,封装,解封,定量和分裂的能力。

    WebSphere Partner Gateway also ships with the Data Interchange Services (DIS) Client which is used to create data transformation maps, where in the source and target data types can be either an EDI, XML or a Record Oriented Data (ROD). The DIS client is discussed in detail in Chapter 14, “Native mapping support in WebSphere Partner Gateway” on page 451.

    WebSphere Partner Gateway也装载着Data Interchange Services (DIS)客户端,可以创建数据转换对照,在源或目标数据格式可以是EDI,XML或者Record Oriented Data (ROD)。这个DIS客户端在第14章有详细的讨论,“Native mapping support in WebSphere Partner Gateway”第451页。

    Chapter 18, “Mapping for EDI transformation and validation” on page 589 gives a detailed understanding on how to create the data transformation maps and the validation maps.

    第18章,“Mapping for EDI transformation and validation”第589页给出了如何建立数据转换对照和确认对照的更详细的理解。

    EDI Processing capabilities would include enveloping and de-enveloping which are discussed in Chapter 19, “Enveloping and de-enveloping” on page 621.WebSphere Partner Gateway also supports EDI acknowledgments like TA1 or Batching and splitting, as explained in Chapter 21, “Batching and EDI splitting” on page 729, is the ability of WebSphere Partner Gateway to support large documents with multiple EDI, ROD or XML messages.

    EDI处理能力包括封装和解封,在第19章有讨论,“Enveloping and de-enveloping”第621页。WebSphere Partner Gateway也支持EDI确认,类似TA1或者分配和分裂,就像第21章“Batching and EDI splitting”第729页所说,这是WebSphere Partner Gateway支持多EDI,ROD或者XML格式的大文件的能力。

    Figure 4-9 encapsulates the EDI support offered by WebSphere Partner Gateway.

    图4-9封装EDI支持通过WebSphere Partner Gateway。

0

阅读 评论 收藏 转载 喜欢 打印举报/Report
  • 评论加载中,请稍候...
发评论

    发评论

    以上网友发言只代表其个人观点,不代表新浪网的观点或立场。

      

    新浪BLOG意见反馈留言板 电话:4000520066 提示音后按1键(按当地市话标准计费) 欢迎批评指正

    新浪简介 | About Sina | 广告服务 | 联系我们 | 招聘信息 | 网站律师 | SINA English | 会员注册 | 产品答疑

    新浪公司 版权所有