Chapter 5. External transfers using IBM Sterling Connect:Direct and
5.2.12 Installing and configuring the Connect:Direct server adapter
For Sterling Connect:Direct file transfers through Sterling B2B Integrator and the Sterling File Gateway, you need to install and configure a Connect:Direct server adapter (CDSA) in Sterling B2B Integrator. This adapter enables Sterling B2B Integrator to behave like a Connect:Direct node, which can then initiate and receive file transfers as though it were a standard PNODE or SNODE.
Starting Sterling B2B Integrator and logging in to the console
To configure the Connect:Direct server adapter, follow these steps:1. Start Sterling B2B Integrator and Sterling File Gateway if it is not already running by double-clicking the Sterling_Integrator_at_8080 desktop icon.
2. Start Internet Explorer and go to:
http://<servername>:<port>/filegateway/
Where <servername> and <port> are the server and port that are defined for your configuration.
3. Log in using the Sterling File Gateway administrator user ID and password (Figure 5-26). The default administrator user ID is fg_sysadmin.
4. In Sterling File Gateway, go to Tools B2B Console (Figure 5-27) to open the Sterling
B2B Integrator console in a new browser window.
Creating the Sterling Connect:Direct netmap in Sterling B2B Integrator
To create the Sterling Connect:Direct netmap in Sterling B2B Integrator:1. Define the Connect:Direct nodes that you connect within your network. Go to
Deployment Adapter Utilities C:D Netmaps C:D Nodes. Then create a new
node by click Go to the right of New Node (Figure 5-28).
2. Enter values for the Connect:Direct node to which you will be connecting in your internal trusted network (SysE in our environment) (Figure 5-29). The Connect:Direct Server Node name on SysE is set up as SysE_CD and is set up to use the default port of 1364.
Figure 5-29 New Connect:Direct node input panel
3. Click Next, and then click Finish on the confirmation panel.
4. Repeat the creation of a C:D node, but this time enter the details to connect to the Connect:Direct node in the external (unprotected) network using a proxy server. Enter the values shown in Table 5-2. Note that you do not enter the host name of the external Connect:Direct node itself (which is SysA in our environment), but instead enter the host name of the proxy server node (SysB). The proxy is configured to route the requests to the intended recipient.
Table 5-2 Values for Connect:Direct node SysA_CD on external network using the proxy
Parameter name Value
Connect:Direct Server Node Name SysA_CD
Connect:Direct Server Host <hostname_of_proxy>
In our scenario, this host name is SysB.
5. Create the netmap of Connect:Direct nodes in your network. Go to Deployment
Adapter Utilities C:D Netmaps C:D Netmaps. Then create a new netmap by
clicking Go to the right of New Netmap (Figure 5-30).
6. Enter the values shown in Figure 5-31, and click Next.
Figure 5-31 New netmap input panel
8. Populate the newly created SystemC_netmap with the Connect:Direct nodes in your network. Go to Deployment Adapter Utilities C:D Netmaps C:D Netmap X-REF. Create the cross-references by clicking Go to the right of Netmap Cross Reference (Figure 5-32).
9. Select SystemC_netmap as the C:D Netmap Name, and click Next (Figure 5-32 on page 122).
Figure 5-33 netmap name selection panel 10.Click add (Figure 5-34).
11.Select both Connect:Direct nodes, and click Save (Figure 5-35).
Figure 5-35 Select nodes to add to the netmap
12.Click Next, and then click Finish on the confirmation panel (Figure 5-36). Your netmap is now created, and you can create the Connect:Direct server adapter that uses it.
Figure 5-36 Netmap cross reference confirmation panel
The netmap is accessible by the Connect:Direct server adapter after it is installed and configured. The netmap contains the names and connection details of Connect:Direct nodes to which the Connect:Direct server adapter can receive and send messages. SysA_CD is the external partner’s Connect:Direct node from which a file is received in this scenario. Note that the host is defined as SysB, which is the host name of the proxy system that forwards the messages. SysE_CD is the internal partner’s Connect:Direct node to which the message is sent.
Installing the Connect:Direct server adapter
To install the Connect:Direct server adapter:1. On the Sterling B2B Integrator dashboard, click Deployment Services Configuration (Figure 5-37). Click Go to the right of New Service.
Figure 5-37 Create a new service configuration
2. Click the file-tree icon (Figure 5-38).
3. Expand Applications Sterling Commerce Connect:Direct, and select Connect:Direct Server Adapter (Figure 5-39). Click Save, and then click Next.
Figure 5-39 Select Connect:Direct server adapter
4. Enter a name of SysC_CDSA and a description of C:D Server Adapter on SysC (Figure 5-40). Click Next.
5. Enter the Connect:Direct Server Node Name as SysC_CDSA, and click Next (accepting all other default values) (Figure 5-41).
6. Keep clicking Next, accepting all default values, until you reach the SysC_CDSA: Netmap panel. Select the netmap name SystemC_netmap (Figure 5-42) to define the netmap that the new Connect:Direct server adapter will use. Click Next.
Figure 5-42 Select netmap for the Connect:Direct server adapter
7. On the confirmation panel, scroll down to see that the netmap details are configured for the Connect:Direct server adapter (Figure 5-43). Click Finish.
Figure 5-43 Node details defined in the configured netmap for the CDSA