Solution components

This section describes the components that are associated with each product in this solution (Figure 4-1). Certain components require a specific configuration for the solution to work. We discuss the configuration steps that are required as necessary.

For Sterling Connect:Direct, each data transfer involves a local and a remote Connect:Direct server (also referred to as

nodes

). The two servers work together to perform the work in a peer-to-peer relationship. The server initiating the connection is the

primary node

(PNODE) for the connection, and the server receiving the connection is the

secondary node

(SNODE). A Connect:Direct server can manage multiple concurrent connections with

otherConnect:Direct servers and can simultaneously act as both a PNODE and an SNODE.

Figure 4-1 The WebSphere MQ File Transfer Edition and Sterling Connect:Direct internal systems

Sterling Connect:Direct

Sterling Connect:Direct moves files point to point (peer to peer) using the Sterling

SysE SysD SysC

File System

SYSDAGT

SYSCAGT PNODE:

SysE_CD SysD_CDSNODE:

WebSphere MQ (FTEQMGR) WebSphere MQ (FTPQMGR) Administrator Administrator Administrator Administrator

Connect:Direct server regarding the work that will be performed. The Connect:Direct requester, a GUI, and the CLI are used to communicate with the Connect:Direct server.

Connect:Direct node SysE_CD

As illustrated in Figure 4-1 on page 55, the Connect:Direct node installed on SysE is named SysE_CD. For the scenarios in this chapter, SysE_CD represents an internal trading partner at one end point. The files transferred in the scenarios in this chapter start and end at this endpoint.

Connect:Direct node SysD_CD

The Connect:Direct node installed on SysD is named SysD_CD. For the scenarios in this chapter, SysD_CD represents an external trading partner at one end-point (Figure 4-1 on page 55). The files transferred in the scenarios in this chapter both start and end at this endpoint.

Connect:Direct Requester for Windows

Connect:Direct Requester for Windows is a GUI for Connect:Direct servers on Windows, UNIX, and Open VMS platforms. You can connect to Connect:Direct servers to perform file transfers, run remote programs or batch jobs, and create, submit, and monitor Connect:Direct processes. You can also perform Sterling Connect:Direct administrative functions, such as setting up and maintaining Sterling Connect:Direct users and network maps. In this chapter, the Connect:Direct Requester is used to configure and launch Connect:Direct processes on SysD_CD.

Sterling Connect:Direct CLI

The Sterling Connect:Direct CLI is a CLI to Connect:Direct servers on the UNIX platform. You can connect to Connect:Direct servers and perform file transfers, run remote programs or batch jobs, and create, submit, and monitor Connect:Direct processes. In this chapter, the Sterling Connect:Direct CLI is used to configure and launch Connect:Direct processes on SysE_CD.

WebSphere MQ Command and Agent Queue Manager (FTPQMGR)

WebSphere MQ Queue Manager (FTPQMGR) acts as the command and agent queue manager for the SYSCAGT WebSphere MQ File Transfer Edition agent.

WebSphere MQ Coordination Queue Manager (FTEQMGR)

WebSphere MQ Queue Manager (FTEQMGR) is the WebSphere MQ File Transfer Edition coordination queue manager. The coordination queue manager publishes status messages that are received from the agents, showing the state of transfers and the agent’s status. FTEQMGR also acts as the command and agent queue manager for the SYSDAGT WebSphere MQ File Transfer Edition agent.

WebSphere MQ File Transfer Edition Server Agent (SYSDAGT)

WebSphere MQ File Transfer Edition Server Agent (SYSDAGT) is the WebSphere MQ File Transfer Edition agent that connects to the local queue manager FTEQMGR in bindings mode. This type of agent is referred to as a

server agent

. SYSDAGT reads files from and writes files to the local file system. This agent is the target agent for SYSCAGT in the scenarios in this chapter.

WebSphere MQ File Transfer Edition Server Agent (SYSCAGT)

WebSphere MQ File Transfer Edition Server Agent (SYSCAGT) is the WebSphere MQ File Transfer Edition agent that connects to the local queue manager FTPQMGR in bindings mode. This type of agent is referred to as a server agent. SYSCAGT reads files from and

writes files to the local file system. This agent is the target agent for SYSDAGT in the scenarios in this chapters.

WebSphere MQ Explorer and WebSphere MQ File Transfer Edition

Explorer

WebSphere MQ Explorer is used to view and administer the WebSphere MQ queue managers and queue manager objects, such as queues, topics, and channels. WebSphere MQ Explorer is built on an Eclipse-integrated development environment. The Eclipse-based platform allows plug-ins to be added to the base platform.

The WebSphere MQ File Transfer Edition Explorer is a plug-in to WebSphere MQ Explorer. It is used to schedule file transfer requests and view the status of current requests. The tool includes a transfer log view that subscribes to the coordination queue manager to obtain audit information. The audit information is displayed in the transfer log view for every transfer that occurs in the given topology. Beginning in WebSphere MQ File Transfer Edition

Version 7.0.3, WebSphere MQ File Transfer Edition Explorer also includes the ability to view the status of an agent.

In document IBM connect direct redbook (Page 71-73)