An IFS transport specifies the connectivity information that will be used by the Transaction Server to connect to the IFS server. You can connect directly to the IFS server or via a TCP proxy.
Assumptions
The following is assumed:
- The Workbench is started.
- You have the user ID and password to access the IFS server.
- If you are using a TCP proxy, you have the parameter values to access the TCP proxy server.
Procedures
Follow these steps:
-
From the Workbench left pane, expand the node you
want to associate the IFS transport with.
-
Expand
Enterprise
, and then click
Transports
.
The Transports tab appears in the right pane. -
Right-click anywhere on the
Transports
tab to display its pop-up
menu, and then click
New
.
The Transport window appears. -
In the
Name
box, type a unique
name for the transport.
An IFS transport name can be up to 64 characters in length and can include letters, numbers, and the underscore character. You will not be able to type invalid characters. For example, spaces are not allowed. You will not be able to insert a space in the name. -
Use the
Type
down-arrow, and then
click
IFS
.
The Transport window changes to accommodate the definition of an IFS transport.
Parameters tab
| Parameter | Description |
|---|---|
| URL | Required. A URL to validate. This URL value can be a WSDL address or the actual Web service address (for example, the location URL of the WSDL). If the URL contains a host name, you must make sure the node is configured to use a DNS server. For more information, see Setting the DNS server for host name resolution. The URL value is only used to validate the WSDL or Web service URL. The URL is not used at runtime. |
| User | Optional. This is the credential that the Transaction Server will use to access the URL value specified. |
| Password | Optional. This is the password associated with the user credential. |
| Proxy
|
When you select the Proxy check box, additional parameters become available for enabling a proxy connection for the IFS transport. |
| Type
|
Lists the proxy types supported:
HTTP, SOCKS4A, and SOCKS5.
 |
| Host
|
Required. Host is the IP address or host name of the computer where the proxy server is installed. |
| Port
|
Required. This is the port number of the proxy server computer. |
| User
|
Optional. The credential that the Transaction Server will use to access the proxy server. |
| Password
|
Optional. This is the password associated with the User parameter credential. The Password parameter becomes unavailable when SOCKS4A is selected. |
Testing and saving the IFS transport
The following shows a portion of a completed IFS
transport:
- When the parameters are filled in, click Validate . The process does not validate the part of the URL that is unique to the WSDL or Web service location as it does not read the WSDL nor does it send a request to the URL. The only check is that the URL actually points to a valid IFS server. A message will appear telling you whether or not the transport parameter values were valid. Click OK .
- Click Save to write this transport to the node The name of the new transport is added to the Transports tab and will be available for use by a transport map.
Related topics
The following Related Topics describes the set of tabs that let you specify values to create an IFS transport.