Configuring the Integration Server transport
You can configure the webMethods Integration Server transport in the Physical View of the Architecture School perspective.
About this task
To configure the transport, do the following steps:
Procedure
- In the Physical View of the Architecture School perspective, double-click a webMethods Integration Server resource.
-
In the webMethods Integration Server window, on the Config tab, enter a name for the
transport in the Name field (to
help identify it when multiple Integration Servers are available).
The transport settings are managed under the Config tab, and are broken into basic settings, advanced settings, recording settings, and SSL settings.
Note: All of the configuration fields support the use of tags, which can be entered manually or by selecting them from the menu. Tags must be entered manually in the Password field (for example,%%wm_password%%
).Note: You can test the connection parameters at any time by clicking Test Transport.Note: Rational® Integration Tester 8.0.1 (or later) provides a sift-and-pass-through capability for any message-based stubs that use HTTP, IBM® Integration Bus, or webMethods Integration Server transports. If you want to specify the default pass-through action for all webMethods Integration Server transports, use the Pass Through window on the Virtualization page of the Preferences dialog. The default pass-through action can be modified for each stub. For information about using the Virtualization page and configuring pass-through actions for message-based stubs, see Sift-and-pass-through capability. -
Configure the basic Integration Server settings on the
Settings tab. The available
configuration options are described in the following table:
Table 1. Configuration options Field Description Server The hostname and port on which the Integration Server is installed and listening. The default port is 5555. Username The user name to use for connecting to the Integration Server. The default is Administrator. The user must have the following permissions on the Integration Server: - Full access to the Integration Server adapter package (GreenHatversion.zip)
- Execute permission for any packages that you want to test
Password The password for the user in the previous field. The default password is manage. -
On the Recording tab, select the Decode Input Streams check box to record InputStream data. You can convert
an object in a message to be sent to the WMIS server in a stream by selecting this option.
For example, you could select this option to call
pub.io:streamToString
from thewmPublic
package.Note: Streams are only used when invoking operations, not with responses. -
Configure advanced settings for connecting to an
Integration Server on the Advanced tab. The available configuration options are described in the
following table:
Table 2. Advanced connection settings Field Description Allow redirects within the IS server cluster? This option enables or disables the redirection of requests through the connection (that is, whether requests can be passed to another server in the target server's cluster). URI for remote web server CGI script If the Integration Server is configured for it, this is the Uniform Resource Identifier (URI) of the CGI script that must be used to access the server. Retry server in case primary server is unavailable The hostname and port of the retry server, which is used when a client connects to a server in a cluster and the requested server is down. If a retry server is specified, an attempt is automatically made to connect the client to the retry server. Proxy Server These options are used only if you want to configure the transport to work with an HTTP proxy server. If so, select the Use an HTTP proxy server? check box and configure the following fields: - Server
- The hostname of the proxy server.
- Username
- The user name to use for connecting to the proxy server.
- Password
- The password to use for connecting to the proxy server.
- Configure the webMethods transport SSL settings on the SSL tab. Specify the options under Provided Certificates (client settings) and Trusted Certificates (server settings), and select the Identity Store to use for each one.