Creating a gateway

You must create and maintain a default gateway. If you do not, you cannot create connections. You cannot disable the default gateway because this action disables the gateway's channel. You can, however, change your default gateway from one gateway to another. The Gateways screen identifies your default gateway.

The information required to add a gateway depends on the type of transport that the gateway will use.

A gateway is a B2B network point that acts as the entrance to another network. A gateway can resolve data translation and compatibility issues to ensure data transfer. Used in conjunction with participant connections, which define the connection between two specific community members' environments, gateways control the successful routing of business documents.

Business Integration Connect uses gateways to identify addressing and the source and destination configurations.

To create a gateway:

  1. Click Account Admin > Profiles > Gateways.
  2. Click Create in the upper right corner of the screen.
  3. Enter a unique name for the gateway.
  4. Select the gateway's status: Enabled or Disabled. Documents fail to process if they are routed through a gateway with a disabled status. When you disable a gateway, you also disable the participant connection associated with the gateway.
  5. Select Online or Offline. If offline, documents are queued until the gateway is placed online.
  6. Enter a description of the gateway.
  7. Select the gateway transport method (for example, HTTP 1.1 or SMTP). See Table 3 for transport information examples.
    Note:
    Users can create their own transport for use during the creation of a user exit gateway.

    Table 3.

    Required information for transport methods
    Transport HTTP HTTPS FTP FTPS File Directory JMS SMTP

    Transport
    Protocol Version

    1.1 only

    1.0 or 1.1

    -



    -

    -

    Target URI

    Must match http://...

    Must match https://...

    Must match ftp://...

    Must match ftp://...

    Must match file://...

    Must match file://...

    Must match mailto:...

    User Name
    for URI

    Required if authen.. is required.

    Required if authen.. is required.

    Required if authent.. is required.

    Required if authent.. is required.


    Required if authen.. is required.

    Required if authen.. is required.

    Password
    for URI

    Required if authen.. is required.

    Required if authen.. is required.

    Required if authen.. is required.

    Required if authent.. is required.


    Required if authen.. is required.

    Required if authen.. is required.

    Authen..
    Required






    Optional

    Optional

  8. Enter the User Name for the URI (not required for JMS). This is required whenever authentication is required. When using FTP, this is the log in for a participant's FTP server.
    Important:
    When you are using JMS for Transport, the Target URI is the URL for the JNDI service.

    For MQ JMS, the format of the Target URI is as follows:
    file:///<user defined MQ JNDI bindings path>.

    This directory contains the MQ.bindings file for file-based JNDI. Note the three slashes after file.

  9. Enter the Password for the URI (not required for JMS). This is required whenever authentication is required.
  10. Select Yes or No to require authentication. This is often required by JMS or SMTP, If it is required, then username and password will also have to be configured.
  11. If you did not select JMS as the transport method, click Save now. If JMS is the selected transport, continue to the next step.
  12. Enter the other required information for the gateway types choosen.
  13. Click Save. To add additional gateways, repeat these steps.

Copyright IBM Corp. 2003, 2004