IBM Implementing SMTP and POP3 Scenarios with WebSphere Business Integration Connect Author: Ronan Dalton
Table of Contents Section 1. Introduction... 2 Section 2. Download, Install and Configure ArGoSoft Mail Server... 3 Section 2.1 Installation... 3 Section 2.2 Configure the ArGoSoft Mail Server... 6 Section 3. Base Configuration in WebSphere Business Integration Connect... 7 Section 3. Base Configuration in WebSphere Business Integration Connect... 8 Section 3.1 Participant Definitions... 8 Section 3.2 B2B Capabilities... 8 Section 3.3 POP3 Target... 9 Section 3.4 Gateways... 9 Section 3.5 Interactions... 10 Section 3.6 Participant Connections... 11 Section 4. Install and Configure the SMTP Client for WebSphere Business Integration Connect 12 Section 4.1 Installation... 12 Section 4.2 Using the SMTP Client for WebSphere Business Integration Connect... 13 Section 5. Test our scenario... 15 Section 5.1 Using the AS1/AS2 Viewer... 15 Section 6. Extend our scenario to include a Message Disposition Notification (MDN)... 17 Section 6.1 Create a POP3 Account for Partner Two... 17 Section 6.2 Extended test scenario... 18 Section 6.3 Using the AS1/AS2 Viewer to View Results... 19 Section 7. Conclusion... 21 Appendix A. Troubleshooting the ArGoSoft Mail Server... 21 Appendix A. Troubleshooting the ArGoSoft Mail Server... 22 Error Starting the SMTP Server... 22 Error Starting the Web Server... 22 Appendix B. SMTP Configuration on WebSphere Business Integration Connect... 23 Appendix C. Reference Material... 24 Page 1 of 24
Section 1. Introduction Should I take this tutorial? This tutorial is designed for users of WebSphere Business Integration Connect V4.2 that are interested in the configuration details for Simple Mail Transfer Protocol/Applicability Statement 1 (SMTP/AS1) communications. The step-by-step approach used throughout this paper makes this tutorial a suitable guide for both new and experienced users of WebSphere Business Integration Connect. What is this tutorial about? This tutorial chronicles the configuration of WebSphere Business Integration Connect Enterprise Edition for SMTP/AS1 communications. It develops a scenario that allows a community participant, Partner Two, to send EDI transactions over AS1 to Partner One, the community manager. Partner Two uses the SMTP Client for WebSphere Business Integration Connect as a means of sending these AS1 transactions. Partner One is using WebSphere Business Integration Connect Enterprise Edition to receive and process messages sent from Partner Two. All configurations take place on one machine but theoretically this scenario could appear as shown in Figure 1.1 below. Internet Partner Two SMTP Client SMTP Server POP3 Server WBIC Partner One Figure 1.1 - Logical architecture Tools All software used in this paper is assumed to be running in a Windows 2000 environment. The following software is used throughout this tutorial: WebSphere Business Integration Connect Enterprise Edition version 4.2.2 (Including all prerequisite software) ArGoSoft Mail Server SMTP Client for WebSphere Business Integration Connect Requirement: The SMTP Client for WebSphere Business Integration Connect requires that a Java Runtime Environment of version 1.4.2 or higher is already installed on the system. For more details on working with the SMTP Client for WebSphere Business Integration Connect, see the SMTPClient.pdf file available for download with this tutorial. Page 2 of 24
Section 2. Download, install, and configure ArGoSoft Mail Server The ArGoSoft Mail Server is a fully functional Simple Mail Transfer Protocol/Post Office Protocol (SMTP/POP3) server for Windows 2000. At the date of writing this paper, the ArGoSoft Mail Server was freely available at: http://www.argosoft.com/files/apps/agsmail.exe Section 2.1 Installation To install the ArGoSoft Mail Server: 1. Download agsmail.exe to a local directory. When complete, open the executable file from Windows Explorer. 2. Click the Setup button. Figure 2.1 Click Setup 3. Click the Next button. Figure 2.2 Click Next 4. Click Start Installation. Page 3 of 24
Figure 2.3 Start Installation 5. When informed that the installation has completed, click OK button, then click Finish. Having successfully installed the ArGoSoft Mail Server, our next step is to start the SMTP service in Windows 2000. To start the SMTP service: 1. Click Start to open the Windows 2000 Start menu. 2. Chose Programs ArGoSoft Mail Server ArGoSoft Mail Server. Tip: If your machine is not connected to a network at the time of first opening, the error shown in Figure 2.4 will appear. Click OK to bypass this error message. Figure 2.4 - Error Given this paper requires only one machine, it s not necessary that you connect to a network. If your machine is already connected to a network when first opening the ArGoSoft Mail Server, the above error will not be shown. Let s assume you re not connected and have just clicked OK to bypass the error above. The ArGoSoft Mail Server icon should now appear in your system tray. To open the mail server console, simply double-click the icon. Messages similar to those shown in Figure 2.5 below should be present in the console. Page 4 of 24
Figure 2.5 ArGoSoft Mail Server console Reminder: daltonro1 is the hostname of my Windows 2000 machine. This will differ on your system. All other details should appear as above. Should your console not appear as above, now might be a good time to review Appendix A. This section covers some of the issues that may be encountered when starting the ArGoSoft Mail Server. If you re happy that the ArGoSoft Mail has successfully started, then proceed with the configuration. Page 5 of 24
Section 2.2 Configure the ArGoSoft Mail Server Now that we ve installed and started the ArGoSoft Mail Server, we can begin the required configuration. The first task is to create a local domain for use by the SMTP server. To create a new Local Domain: 1. Open the Tools menu from the ArGoSoft Mail Server console and select Options. 2. Select the Local Domains tab and enter localhost as shown in Figure 2.6 below: Figure 2.6 New local domain 3. Click Add and then click OK. 4. Click OK when informed about the modification of the mail size limit. Having created a new local domain, you can create a new POP3 account for Partner One. This article defines Partner One s POP3 account as a Target in WebSphere Business Integration Connect in Section 3. This account will be used as a point of receipt for messages sent by Partner Two in this tutorial. To create a new POP3 account for Partner One: 1. Select Users from the Tools menu of the ArGoSoft Mail Server console. 2. Click the Add New User button from the top left of the User Setup window. 3. Enter the following details: User Name: partnerone Real Name: Partner One Password: partnerone Confirm Password: partnerone The Add New User window should appear with the details shown in Figure 2.7 below: Page 6 of 24
Figure 2.7 Add New User 4. Click OK. 5. Click Close from the User Setup window. This concludes our initial configuration of the ArGoSoft Mail Server. Having downloaded and installed the mail server, we created a new local domain and a new POP3 account for Partner One. Partner One will use this POP3 account for the receipt of SMPT/AS1 messages sent from Partner Two. Next, we ll examine the configuration required in WebSphere Business Integration Connect Enterprise Edition to allow for the receipt of messages sent via SMTP. Page 7 of 24
Section 3. Base configuration in WebSphere Business Integration Connect This section details the configuration required in WebSphere Business Integration to allow for the receipt of transactions sent via SMTP. These messages will be posted to an appropriate POP3 account that is being polled by WebSphere Business Integration Connect. This POP3 account should be defined as a Target in WebSphere Business Integration Connect. We start the configuration of WebSphere Business Integration Connect by defining the two participants involved in our scenario. Section 3.1 Participant definitions We require the definition of two participants in the WebSphere Business Integration Connect Community Console. To create a new participant: 1. Select Account Admin from the main menu. 2. Chose Community Participant from the horizontal navigation bar. 3. Click on Create. 4. Enter the values listed in the table 3.1 below: Participant Login Name Particpant Name Participant Type partnerone Partner One Community Manager Business ID Identifier (DUNS) 123456789 Table 3.1 Partner One s profile 5. Click Save. Repeat the steps above to define a participant profile for Partner Two. Use the details in table 3.2 below: Participant Login Name Participant Name Participant Type partnertwo Partner Two Community Participant Business ID Identifier (DUNS) 987654321 Table 3.2 Partner Two s profile Section 3.2 B2B capabilities Now that we have created our participants in WebSphere Business Integration Connect, we re in a position to define business-to-business (B2B) capabilities for each. To define B2B Capabilities for our participants: 1. Select Account Admin from the main menu and Community Participant from the horizontal navigation bar. 2. Click Search. 3. Select partnertwo by clicking the icon to the left of Partner Two. Page 8 of 24
4. Click on B2B Capabilities from the horizontal navigation bar. 5. Set Source and Target for the following Document Flow Definition: Package: AS Protocol: EDI-X12 Document Flow: ALL Repeat the steps above for partnerone but use the following Document Flow Definition: Package: None Protocol: EDI-X12 Document Flow: ALL With our participants defined and B2B capabilities assigned to each, we can now define a POP3 target for our WebSphere Business Integration Connect installation. Section 3.3 POP3 Target To define a POP3 Target in WebSphere Business Integration Connect: 1. Select Hub Admin from the main menu and Targets from the horizontal navigation bar. 2. Click Create Target. 3. Enter the details listed in table 3.3 below: Target Name Transport POP3 Server User Id Password POP3Target POP3 localhost partnerone partnerone Table 3.3 - POP3Target properties Important: The User ID and Password above should match the values entered when creating Partner One s POP3 account in Section 2. 4. Accept all other default values and click Save. WebSphere Business Integration Connect will begin polling Partner One s POP3 account immediately. Looking at the ArGoSoft Mail Server console we can see evidence of this. Section 3.4 Gateways In this scenario, Partner Two is sending an Electronic Data Interchange (EDI) transaction via Applicability Statement 1 (AS1) to Partner One. Partner One receives the transaction into WebSphere Business Integration Connect via Partner One s POP3 mailbox. WebSphere Business Integration Connect identifies the message, removes the AS1 packaging and places the EDI transaction on the file system. To allow this scenario, we must first define a new gateway for Partner One. To create a new gateway: Page 9 of 24
1. Select Account Admin from the main menu, then Community Participant from the horizontal navigation bar. 2. Click Search, then select the icon next to Partner One. 3. Select Gateways from the horizontal navigation bar. 4. Click Create. 5. Enter the details listed in table 3.4 below: Gateway Name Transport Target URI FileSystemGateway File Directory file://c:\filesystemgateway Table 3.4 - FileSystemGateway 6. Accept all other defaults and click Save. Set this new gateway as the default gateway for Partner Two. 1. Select View Default Gateways. 2. Chose FileSystemGateway from the Production drop-down. 3. Click Save. Although our initial scenario does not require a gateway for Partner Two, WebSphere Business Integration Connect insists that a default gateway be defined before allowing the creation of a Participant Connection. We create the Participant Connection later in this tutorial but first we define a gateway for Partner Two. Follow the steps above to create this gateway remembering to select Partner Two rather than Partner One in step 2. Be sure to set this new gateway as the default for Partner Two. Use the values in table 3.5 below when creating Partner Two s gateway. Gateway Name Transport Target URI SMTPGateway SMTP mailto:partnertwo@localhost Table 3.5 Partner Two s SMTP Gateway The importance of this gateway being of transport type SMTP, is highlighted later in Section 6. For now, it s suffice that Partner Two has a default gateway of any type. Section 3.5 Interactions This tutorial assumes the user is working with a clean installation of WebSphere Business Integration Connect. As such, it s assumed that there are currently no interactions defined. To create a new interaction for our scenario: 1. Select Hub Admin from the main menu and Document Flow Definition from the horizontal navigation bar. 2. Click on Manage Interactions then Create Interaction. 3. From the Source document flow definition column select: Page 10 of 24
Package: AS Protocol: EDI-X12 Document Flow: ALL 4. From the Target document flow definition column, select: Package: None Protocol: EDI-X12 Document Flow: ALL 5. Set the Action to Pass Through and click Save. Section 3.6 Participant Connections To create a Participant Connection: 1. Select Account Admin from the main menu and Participant Connections from the horizontal navigation bar. 2. Select Partner Two as the Source and Partner One as the Target. 3. Click the Search button. 4. Click the Activate button for the following connection Figure 3.1 Participant connection This completes our initial configuration of WebSphere Business Integration Connect. With the profiles already defined we re in a position to receive an EDI transaction sent via AS1 over SMTP, remove the transaction s MIME packaging and place the raw EDI message on the file system. In the next section we ll install and configure the WebSphere Business Integration Connect Mail Client. Once this is complete we can test our scenario. Requirement: To carry out the configuration detailed above, the WebSphere Business Integration Connect Console must be started. To proceed with testing this scenario, be sure to start the WebSphere Business Integration Connect Receiver and Document Manager. Page 11 of 24
Section 4. Install and configure the SMTP Client for WebSphere Business Integration Connect The SMTP Client for WebSphere Business Integration Connect is a simple Java e-mail Client developed for this tutorial using the JavaMail API. For more information on using the JavaMail API see: http://java.sun.com/products/javamail/ Essentially, the SMTP Client for WebSphere Business Integration Connect takes a file that contains plain text and calls an SMTP server to send the data to a POP3 mailbox. The SMTP Client formats the MIME headers in a way that WebSphere Business Integration Connect Enterprise Edition can interpret and encodes the payload of the message using Base64 encoding. In this section we ll use the SMTP Client for WebSphere Business Integration Connect to send an EDI message to WebSphere Business Integration Connect over SMTP. In essence, we re simulating a message sent via AS1. Section 4.1 Installation Before proceeding with the installation of the SMTP Client for WebSphere Business Integration Connect ensure the prerequisite Java Run time Environment is available. Open a command line interface and issue the command: java -version The response should appear similar to that below: java version "1.4.2_04" If you re Java version is lower than 1.4.2 the SMTP Client for WebSphere Business Integration Connect will not work as expected. Upgrade or install the recommended Java Runtime Environment before proceeding. To install the SMTP Client for WebSphere Business Integration Connect, simply take the SMTPClient.zip file available for download with this tutorial and extract into any given directory. Extracting the.zip file should create the following directory structure: Page 12 of 24
Figure 4.1 SMTP Client directory structure Section 4.2 Using the SMTP Client for WebSphere Business Integration Connect To send a message to WebSphere Business Integration Connect from the SMTP Client for WebSphere Business Integration Connect: 1. Open the WebSphere Business Integration Connect Mail Client by executing the startmail.bat file. 2. Once opened, enter the following the details: To: partnerone@localhost Subject: 123456789;987654321 Content-Type: application/edi-x12 3. Click the Select File button. 4. Navigate to the directory where you ve stored the sample files provided with this tutorial and select twotoone.txt Important: These same sample files are stored in the samples folder under the SMTP Client for WebSphere Business Integration Connect installation directory. The SMTP Client for WebSphere Business Integration Connect should appear as in Figure 4.2 below. Figure 4.2 SMTP Client for WebSphere Business Integration Connect Page 13 of 24
For now you can leave the SMTP Client for WebSphere Business Integration Connect in this state. You re almost ready to test the scenario but before proceeding to the next section, you need to first configure the config.xml file used by the SMTP Client. The SMTP Client for WebSphere Business Integration Connect reads the config.xml file after the Send button is clicked but before actually sending the message. By default this xml configuration file exists in the <INSTALL-DIR>\config directory. After installation, this file should appear as below: <config> <host>localhost</host> <from>yourname@localhost.localdomain</from> </config> The SMTP Client for WebSphere Business Integration Connect determines the location of the SMTP Server to be used when sending message by the host value. In our scenario, the ArGoSoft Mail Server exists on the same machine as the SMTP Client. As such there s no need alter the localhost value. Should you wish to use the SMTP Client for WebSphere Business Integration Connect with an SMTP Server running on a different machine, simply replace the localhost value with fully qualified hostname of the alternative server. The from value determines the sender e-mail address of a message sent from the SMTP Client for WebSphere Business Integration Connect. This value should be changed to your own e-mail address before sending. In actual fact, this value doesn t alter the way in which the SMTP Mail Client for WebSphere Business Integration Connect works in this tutorial. Page 14 of 24
Section 5. Test the scenario To test our scenario, first ensure all required components are started. If you ve followed this tutorial in sequence you should have following running on your machine: WebSphere Business Integration Connect Enterprise Edition ArGoSoft Mail Server SMTP Client for WebSphere Business Integration Connect To test, simply click the Send button from the SMTP Client for WebSphere Business Integration Connect. Assumption: The SMTP Client for WebSphere Business Integration Connect should be in the same state as at the completion of Section 4. If not, follow the steps listed under Using the SMTP Client for WebSphere Business Integration Connect in Section 4. The sequence of events that follow are listed below: 1. The SMTP Client for WebSphere Business Integration Connect will format the message to be sent via SMTP to WebSphere Business Integration Connect with MIME headers and encode the payload using base64 encoding. 2. The SMTP Client will then make a call to the ArGoSoft Mail Server to send the formatted message over SMTP to partnerone@localhost. 3. The ArGoSoft Mail Server will then send over SMTP to partnerone s POP3 mailbox. This mailbox is nothing more than a directory on the file system and can be seen at: C:\Program Files\ArGo Software Design\MailServer\partnerOne Restriction: The path above assumes the default installation path for the ArGoSoft Mail Server. 4. WebSphere Business integration Connect is polling this POP3 mailbox as defined by POP3Target that we created in Section 3. 5. WebSphere Business Integration Connect will pick up the message that it recognises as an AS1 message. 6. The payload is decoded, the AS1 headers are stripped and the message is sent to the target gateway as defined in the Participant Connection. Section 5.1 Using the AS1/AS2 Viewer You should be able to view the message using the AS1/AS2 Viewer from the WebSphere Business Integration Connect Console. 1. Simply select Viewers from the main menu and AS1/AS2 Viewer from the horizontal navigation bar. 2. Adjust your search parameters as required. Tip: If you ve sent the message very recently there should be no need to alter times or dates. You can also identify the message by entering the Message ID value. This can be found in the logfile.log file that resides in the logs directory under the installation location of the SMTP Client for WebSphere Business Integration Connect. 3. Click the Search button. Page 15 of 24
The message just sent should visible in the WebSphere Business Integration Connect Community Console. The MDN Status should appear as N\A. This is important as we ll see when we extend the scenario. To look at the message in more detail, click the There are a couple of details to note on this screen: icon to the left of the corresponding message. 1. Observe that there is no MDN URI. This will change when we extend our scenario in Section 6. 2. Routing From Source should appear with the icon. 3. You can view the message as it was received into WebSphere Business Integration Connect by clicking the icon from the Source row. The payload of this message will already have been decoded. 4. The message can also be viewed after all AS1 headers were stripped by clicking the icon from the Target row. Finally, the message can be viewed in the location defined by the Target URI of Partner One s FileSystemGateway. Earlier, we defined the Target URI as C:\FileSystemGateway. Open this directory using Windows Explorer to view the message on the file system. Now that we ve successfully sent our first message from the SMTP Client for WebSphere Business Integration Connect, lets extend the scenario to include a Message Disposition Notification. This involves an update of our configuration in WebSphere Business Integration Connect. We address the configuration required to extend our scenario in Section 6. Page 16 of 24
Section 6. Extend our scenario to include a Message Disposition Notification (MDN) The AS1 standard uses the Message Disposition Notification (MDN) as a means of acknowledging receipt of an original sent message. In this section, we configure WebSphere Business Integration Connect to send an MDN to Partner Two for any AS1 messages sent. Section 6.1 Create a POP3 Account for Partner Two The first step is to create a new POP3 Account for Partner Two using the ArGoSoft Mail Server. This POP3 account is used to receive any MDN s sent from Partner One to Partner Two. To create a new POP3 Account for Partner Two: 1. Open the ArGoSoft Mail Server Console. 2. Select Users from the Tools menu of the ArGoSoft Mail Server console. 3. Click the Add New User button from the top left of the User Setup window. 4. Enter the following details: User Name: partnertwo Real Name: Partner Two Password: partnertwo Confirm Password: partnertwo The Add New User window should appear with the details shown in Figure 6.1 below: Figure 6.1 Partner Two s POP3 Account 6. Click OK. 7. Click the Close button from the User Setup window. Now that we ve created a POP3 Account for the receipt of MDN s sent to Partner Two, you can alter your earlier test and examine the result. Page 17 of 24
Section 6.2 Extended test scenario To request an MDN for messages sent from Partner Two to Partner One, simply populate the MDN Address field in the SMTP Client for WebSphere Business Integration Connect. Essentially this tells the SMTP Client for WebSphere Business Integration Connect to add the Disposition-Notification-To MIME header on messages sent. The value sent should be the e-mail address to which an MDN will be sent. In this case example we use the e-mail address of Partner Two: partnertwo@localhost. Figure 6.2 SMTP Mail Client with MDN Address Send this new test message to Partner One by clicking the Send button on the SMTP Client for WebSphere Business Integration Connect. The sequence of the events that follow are almost identical to those listed in Section 5 earlier. The difference in this test case however, is the generation and sending of a Message Disposition Notification. WebSphere Business Integration Connect uses the same Participant Connection as in Section 5 for this transaction. This Participant Connection uses the default gateways of both Partner One and Partner Two. You ll remember Partner Two s default gateway had the SMTP transport type. It s this gateway that s used by the WebSphere Business Integration Connect Document Manager when sending an MDN to Partner Two. Quickly, take a look at the Participant Connection created in WebSphere Business integration Connect earlier to confirm the gateways used. To view the Participant Connection: Page 18 of 24
1. Select Account Admin from the main menu, then Participant Connections from the horizontal navigation bar. 2. Set Source as Partner Two and set Target as Partner One. 3. Click Search. To examine the gateways involved in the connection click the Gateways button of the active Participant Connection highlighted in green. A window similar to Figure 6.3 should open. Figure 6.3. Gateways involved in the connection When sending the MDN in this scenario, WebSphere Business Integration Connect uses the transport type of the Source Gateway to determine how the MDN is sent. Section 6.3 Using the AS1/AS2 Viewer to View Results Now that you ve clarified the origins of the MDN we can examine the results of the test. As before, use the AS1/AS2 Viewer to view the AS1 message in the WebSphere Business Integration Connect Console. To open the AS1/AS2 Viewer: 1. Select Viewers from the main menu and AS1/AS2 Viewer from the horizontal navigation bar. 2. Adjust your search parameters as required. 3. Click the Search button. Having identified the message that relates to your most recent test remember, the message can be uniquely identified using the message ID listed in the logfile.log file the first thing to note is the MDN Status. This column should display one of the following two icons: - MDN Processed - Waiting for MDN The MDN Status may stay as Waiting for MDN for a short period of time. During this period, WebSphere Business Integration Connect is processing the original message, then generating and sending the subsequent MDN. Refresh this view until the MDN Status icon shows as MDN Processed. Important: Appendix B details the way in which WebSphere Business Integration Connect identifies a relevant server when sending transactions via SMTP/AS1. Review this section if an MDN is not sent to Partner Two s POP3 mailbox. Page 19 of 24
With the MDN Status column showing the the icon. icon, look at the message in more detail by clicking There are a number of things to note on this screen: 1. The MDN URI should display the value entered in the SMTP Client for WebSphere Business Integration Connect, that is,. partnertwo@localhost. 2. There should be more than one document record displayed. One document with Partner Two as Source and Partner One as Target. This relates to the original message sent. A second document with Partner One as Source and Partner Two as target. This is the MDN. 3. Both documents can be examined in more detail by clicking the icon. The MDN should also be visible in Partner Two s POP3 account. You ll recall that this POP3 account is nothing more than a directory on the file system created by the ArGoSoft Mail Server. This directory should be named partnertwo and will exist under the ArGoSoft Mail Server installation directory. You can examine the contents using Windows Explorer. Page 20 of 24
Section 7. Conclusion A considerable amount of material was covered in this tutorial. The configuration of each constituent application in our scenario has been outlined and then discussed in detail. In this paper we covered the following topics in detail: 1. The installation and configuration of a free SMTP/POP3 Server on Windows 2000. 2. The configuration of WebSphere Business Integration Connect Enterprise Edition for SMTP and POP3. 3. Introduced the SMTP Mail Client for WebSphere Business Integration Connect. 4. Configured the SMTP Mail Client for WebSphere Business Integration Connect to send EDI transactions over SMTP/AS1. 5. Used WebSphere Business Integration Connect to examine our results. Ronan Dalton, the author of this tutorial, designed and developed the SMTP Client for WebSphere Business Integration Connect. Please do not hesitate to get in contact with Ronan for comments and queries at. e-mail daltonro@ie.ibm.com. Page 21 of 24
Appendix A. Troubleshooting the ArGoSoft Mail Server This section details some of the issues that may occur with the ArGoSoft Mail Server at start-up. It s not an exhaustive list but covers some of the problems seen while creating this tutorial. Error Starting the SMTP Server The following error may appear in the ArGoSoft Mail Server console: Error starting SMTP Server: [10048] Address already in use This indicates another application is already listening on port 25 (the default port for SMTP). Determine the process ID of this application and end the process. When the task has successfully ended, restart the mail server. Error Starting the Web Server The following error may appear in the ArGoSoft Mail Server console: Error starting Web server: [10048] Address already in use Again, this indicates that another application is already listening on Port 80. This problem might occur if the WebSphere Business Integration Connect Express Server is already running on the same machine and using the default port (port 80) as a Receipt Address. This error will not affect our workings in this tutorial, as the ArGoSoft Mail Server Web Interface is not used. Page 22 of 24
Appendix B. SMTP Configuration on WebSphere Business Integration Connect Values for the configuration of SMTP were entered during the initial installation of WebSphere Business Integration Connect. When working through the initial install application, values were entered for use by the Document Manager when sending e-mail messages. The default values for these properties are as follows: Host name: localhost SMTP Port: 25 When working with a default installation of the ArGoSoft Mail Server that resides on the same machine as the WebSphere Business Integration Connect Document Manager these values will suffice. Should you wish to work with an SMTP server running on a different machine or listening on a different port, these default values can be altered. To change the values used by WebSphere Business Integration Connect when sending messages over SMTP: 1. Open the bcg.properties file located in the <INSTALL_DIR>\router\was\wbic\config directory with a text editor. 2. Locate the following values: bcg.delivery.smtphost=localhost bcg.delivery.smtphostport=25 3. Alter the properties for each as required. 4. Save the changed bcg.properties file. 5. Restart the Document Manager. Page 23 of 24
Appendix C. Reference material Using WebSphere Business Integration Connect on Microsoft Windows 2000 WebSphere Developer Domain Tutorial Implementing Security Scenarios with WebSphere Business Integration Connect WebSphere Developer Domain Tutorial Integrating WebSphere Data Interchange V3.2 with WebSphere Business Integration Connect V4.2 WebSphere Developer Domain Tutorial IBM copyright and trademark information IBM and WebSphere are trademarks or registered trademarks of IBM Corporation in the United States, other countries, or both. Microsoft and Windows are registered trademark of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. Other company, product, and service names may be trademarks or service marks of others. http://www.ibm.com/legal/copytrade.phtml Page 24 of 24