Package in which to create the connection. Use Designer to create the package before specifying the value in this field. For general information about creating packages, see the webMethods Service Development Help for your release.

Folder in which to create the connection.

Name you want to give to the connection. Connection names cannot have spaces or use special characters reserved by Integration Server and Designer. For more information about the use of special characters in package, folder, and element names, see the webMethods Service Development Help for your release.

Type of service representing various ways to interact with and utilize an IBM Power system's capabilities, such as for data management, system administration, or other tasks. The specific usage and functionality can vary depending on the context and the software or tools being used to establish the connections. Possible values are:

Hostname or IP address of the IBM Power system.

Select true to use the default user for the system name specified in the System Name field and false to specify the username.

Username of the IBM Power system.

Password for the user.

Retype the password for the user.

Use SSL to connect to the IBM Power system. Possible values are:

Indicates if the connection is established through a proxy. Set to true to use the proxy to connect to the IBM Power system. Default value is false.

Hostname or the IP address and port of the proxy server in the format serverName[:port]. If no port is specified, the default port number is used.

Encrypt data path. Possible values:

Optional. Library that you want to use for accessing the IBM Power system resources. The library specified in the Current Library field is available as %CONN_CURLIB% environment variable in your service.

Optional. Socket properties which the IBM Toolbox for Java sets on its client-side sockets. Use ; (semi-colons) to delimit multiple property settings.

Optional. Property specific to the IBM Power system resources. Use ; (semi-colons) to delimit multiple property settings.

Enables the connection to use connection pooling. For more information about connection pooling, see Adapter Connections.

If connection pooling is enabled, this field specifies the number of connections to create when the connection is enabled. The adapter will keep open the number of connections you configure here regardless of whether these connections become idle.

If connection pooling is enabled, this field specifies the maximum number of connections that can exist at one time in the connection pool.

If connection pooling is enabled, this field specifies the number of connections by which the pool will be incremented if connections are needed, up to the maximum pool size.

If connection pooling is enabled, this field specifies the number of milliseconds that Integration Server will wait to obtain a connection with the database before it times out and returns an error. For example, you have a pool with Maximum Pool Size of 20. If you receive 30 simultaneous requests for a connection, 10 requests will be waiting for a connection from the pool. If you set the Block Timeout to 5000, the 10 requests will wait for a connection for 5 seconds before they time out and return an error. If the services using the connections require 10 seconds to complete and return connections to the pool, the pending requests will fail and return an error message stating that no connections are available. If you set the Block Timeout value too high, you may encounter problems during error conditions. If a request contains errors that delay the response, other requests will not be sent. This setting must be tuned in conjunction with the Maximum Pool Size to accommodate such bursts in processing.

If connection pooling is enabled, this field specifies the number of milliseconds that an inactive connection can remain in the pool before it is closed and removed from the pool. The connection pool will remove inactive connections until the number of connections in the pool is equal to the Minimum Pool Size. The inactivity timer for a connection is reset when the connection is used by the adapter.

If you set the Expire Timeout value too high, you may have a number of unused inactive connections in the pool. This consumes local memory and a connection on your backend resource. This could have an adverse effect if your resource has a limited number of connections.

If you set the Expire Timeout value too low, performance could degrade because of the increased activity of creating and closing connections. This setting must be tuned in conjunction with the Minimum Pool Size to avoid excessive opening/closing of connections during normal processing.

Number of times that the system must attempt to initialize the connection pool at startup if the initial attempt fails. The default is 0.

Number of seconds that the system must wait between attempts to initialize the connection pool.

If the connection pooling is enabled and the minimum pool size is more than zero, the Heart Beat Interval is applicable. The connection pool checks the connectivity of the connections that are idle for the value of Heart Beat Interval. The default value for Heart Beat Interval is zero and it is mentioned in seconds. For example, if the value of Heart Beat Interval is 25 seconds, connection pool looks for connections that are idle for 25 seconds. If a connection is broken, then the connection pool is reset.