Adapter for Apache Cassandra 10.2 | webMethods Adapter for Apache Cassandra Documentation | webMethods Adapter for Apache Cassandra Installation and User’s Documentation | Adapter Services | Configuring Insert Service
 
Configuring Insert Service
An Insert service inserts a new record into the table. You configure Insert service using Designer. For more information about adapter services, see Using Adapter Services.
Read the section Before Managing Adapter Services, before you configure adapter services.
*To configure an adapter service using the Insert template
1. In Designer, right-click the folder in which the service is to be contained and select New > Adapter Service.
2. Select the parent namespace, type a name for the adapter service, and click Next.
3. Select webMethods Adapter for Apache Cassandra as the adapter type and click Next.
4. Select the appropriate Adapter Connection Name and click Next.
5. From the list of available templates, select the Insert template and click Finish.
The adapter service editor for the selected adapter service appears. You can select the Adapter Settings tab at any time to confirm Adapter Properties such as the Adapter Name, Adapter Connection Name, and Adapter Service Template as necessary.
6. Select the Table tab to configure the table and set the fields as follows:
Field
Field Description/Action
Keyspace Name
Specifies the keyspace which is auto-populated based on the created connection.
Table Name
Specify the name of the table.
7. Use the Columns tab to provide values for the following fields:
a. Use the icon to populate a single column in the table. You can use the icon to display all columns created in an existing table.
Field
Description/Action
Column Name
The column name in the table.
Column Type
The column data type defined in the corresponding Column Name of the table.
Type Definition
Specifies the string representation of Column Type.
Input Field
The output field name.
Input Field Type
The data type of the output field.
8. Use the Options tab to provide the appropriate values for the following fields:
Field
Description/Action
Consistency Level
Defines to manage availability versus data accuracy. You can configure consistency for a session or per individual read or write operation.
The write consistency levels in strongest-to-weakest order is given as follows:
*ALL: Provides the highest consistency and the lowest availability of any other level.
*EACH QUORIUM: Maintains a strict consistency level at the same level, when used in multiple datacenter clusters.
*QUORIUM: Maintains a strong consistency across the cluster, when used in either single or multiple datacenter clusters. Use QUORIUM, if you can tolerate some level of failure.
*LOCAL QUORIUM: Maintains consistency locally. LOCAL QUORIUM is used in multiple datacenter clusters with a rack-aware replica placement strategy, such as (NetworkTopologyStatergy), and a properly configured snitch. Can be used with SimpleStrategy.
*LOCAL ONE: In a multiple datacenter clusters, the consistency level cross-DC traffic is not desirable when compared to the consistency level of ONE. LOCAL ONE accomplishes this. Use this consistency level in an offline datacenter to prevent automatic connection to online nodes in other datacenters if an offline node goes down.
*THREE: Satisfies the needs of most users because consistency requirements are not stringent.
*ANY: Provides low latency and a guarantee that a write never fails. Delivers the lowest consistency and highest availability.
The read consistency levels in strongest-to-weakest order is given as follows:
*ALL: Provides the highest consistency of all levels and the lowest availability of all levels.
*QUORIUM: Maintains strong consistency across the cluster, when used in single or multiple datacenter clusters. Ensures strong consistency if you can tolerate some level of failure.
*LOCAL QUORIUM: Used in multiple datacenter clusters with a rack-aware replica placement strategy ( NetworkTopologyStrategy) and a properly configured snitch. Fails when used with SimpleStrategy.
*THREE: Provides the highest availability of all the levels if you can tolerate a comparatively high probability of stale data being read. The replicas contacted for reads may not always have the most recent write.
*LOCAL ONE: In a multiple datacenter clusters, the consistency level cross-DC traffic is not desirable when compared to the consistency level of ONE. LOCAL ONE accomplishes this. Use this consistency level in an offline datacenter to prevent automatic connection to online nodes in other datacenters if an offline node goes down.
*SERIAL: Use SERIAL to read the latest value of a column after a user has invoked a lightweight transaction to write to the column. Cassandra then checks the inflight lightweight transaction for updates and, if found, returns the latest data.
*LOCAL SERIAL: Used to achieve linearizable consistency for lightweight transactions.
Enabling Tracing
Define to enable and disable the tracing for transactions on all nodes in the cluster. Tracing is enabled to troubleshoot performance problems.
If Not Exists
Checks if there are any duplicates with same primary key column value.
9. To verify input or output information for the service, use the Input/Output tab as required.
The below fields are auto-populated in the input section of Input/Output tab:
Field
Description/Action
timestamp
Specify the time of insertion of the record.
Time to live(ttl)
Specifies the setting time for data in a column to expire. The value for the field is accepted in milliseconds.
Note:
The remaining fields in the input section are auto-populated based on the columns selected in Columns tab.
10. From the File menu, select Save.