Field | Description/Action |
Package | The package in which to create the connection. You must create the package using Designer before you can specify the package using this parameter. For general information about creating packages, see the webMethods Service Development Help for your release. Note: Configure the connection in a user-defined package rather than in the adapter's package. For other important considerations when creating packages for Adapter for Apache Cassandra, see Adapter for Apache Cassandra Package Management |
Folder Name | Specifies the folder in which you create the connection. |
Connection Name | Specifies the 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. |
Field | Description/Action |
Cluster Client Name | The name of the client connection. Note: ![]() ![]() |
Contact Point(s) | Defines the points to which the list of Cassandra hosts connects. The format is provided as follows: host1:port1,host2:port2,…. Note: Be sure not to use the same cluster name in more than one connection. |
Enable Metrics | Enables the metrics for the connections. |
Enable JMX Metrics | Enables the JMX reporting metrics for the connections. |
Read Pooling Options from Config file | Reads the pooling options from connection.properties file. |
Read Protocol Options from Config file | Reads the protcol options from connection.properties file. |
Read Load balancing Options from Config file | Reads the load balancing options from connection.properties file. |
Read Policies from Config file | Reads the policies options from connection.properties file. |
Read Socket Options from Config file | Reads the socket options from connection.properties file. |
Read Query Options from Config file | Reads the query options from connection.properties file. |
Field | Description/Action |
Enable Connection Pooling | Enables the connection to use connection pooling. For more information about connection pooling, see
Adapter Connections. Note: If you plan to enable connection pooling in a clustered environment, consider the connection pool size. |
Minimum Pool Size | 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. |
Maximum Pool Size | If connection pooling is enabled, this field specifies the maximum number of connections that can exist at one time in the connection pool. |
Pool Increment Size | 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. |
Block Timeout | If connection pooling is enabled, this field specifies the number of milliseconds that Integration Server will wait to obtain a connection 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 should be tuned in conjunction with the Maximum Pool Size to accommodate such bursts in processing. |
Expire Timeout | 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 should be tuned in conjunction with the Minimum Pool Size to avoid excessive opening/closing of connections during normal processing. |
Startup Retry Count | The number of times that the system should attempt to initialize the connection pool at startup if the initial attempt fails. The default is 0. |
Startup Backoff Timeout | The number of seconds that the system should wait between attempts to initialize the connection pool. |