Connect Cassandra form
Completing the Service tab

From the Service tab, identify the external system with which this connector communicates.

Note: The connection details may change over time, or when you move between a test system and a production system. After the ruleset version containing this connector instance is locked, you cannot update the connection fields. If your application needs to override the connection details, complete the EndPointURL parameter of the Connect-Cassandra method in the connector activity that calls this connector instance.

1. Configure connection with the Cassandra node.

   1. In the Host field, enter the server IP address of the Cassandra node.

   2. In the Port field, enter the port of the Cassandra node. The default port is 9042.

   3. In the Response timeout field, enter the number of milliseconds to wait for the server response. Enter zero or leave it empty to wait indefinitely.

      Note: This field is disabled and ignored at run time when the Intended for field is set to queuing (response will not be available).

2. Optional: Configure authentication settings.

   This connector can establish secure and non-secure connections.

   1. Select the Use authentication check box.

   2. In the Authentication profile, select a Data-Admin-Security-AuthenticationProfile instance that contains details required by the remote service (user name and password using BASIC authentication).

3. Optional: Configure security settings.

   1. Select the Use secure connection check box.

   2. Specify a truststore and a keystore.

4. Optional: Configure error handling settings.

   1. Status value property: Select a property to hold the status code of the Connect-Cassandra method. The literal value Good identifies success. You can use the standard property @baseclass.pyStatusValue.
   2. Status message property: Select a property to hold status descriptions or return values from the external system returned by the Connect-Cassandra method. You can use the standard property @baseclass.pyStatusMessage. This field is disabled and ignored at runtime when the Intended for field is set to queuing.
   3. Error handler flow: Identify a flow instance to route work items that cannot continue in its current flow because this connector instance was unable to connect to the external system. The default Work-.ConnectionProblem flow provides one approach for handling such problems. See handling connector exceptions.

5. Optional: Configure processing options.

   You can allow connector requests from this Connect HBase instance to be processed asynchronously in parallel with the calling activity, or in the background by an agent. The mode of execution of each connector request is determined by the Execution Mode parameter of the Connect-HBase method, as enabled by the values in these two fields.

   • Intended for: Select the execution mode.
     • immediate execution: The connector executes synchronously; the calling activity waits for results.
     • queuing (response will not be available): The connector executes asynchronously, with calls placed in a queue. The calling activity continues without waiting for results. When selected, queuing occurs only if also specified in the Connect-HBase method.
   • Request processor: If you selected queuing in the Intended for setting, identify here a Connect Request Processor data instance that defines the classes and other characteristics of the queued connector request.

6. Click Test connection. The Pega 7 Platform verifies the connectivity by constructing the URL based on the host and port settings but it does not confirm the ability to authenticate with the service.

7. Click Simulations to create a simulator for this connect rule. See Connect Simulators.

Open topic with navigation