Note: Instances of this rule are locked. It is not possible to modify them.
Connection
- Client: the client can connect using Java or REST. The selection of this setting depends on the server configuration and, if using authentication, you always need to use the Java client.
- Host: enter the server IP address of the HBase master node.
- Port: enter the port of the HBase master node. The definition of the port setting depends on the Client setting:
- Java: listening port of the Zookeeper service (by default, this is 2181).
- REST: listening port of the REST gateway.
- Response timeout: enter the number of milliseconds after which this connection times out with a failure message if it does not receive a response. Enter zero or leave blank to wait indefinitely. This field is disabled and ignored at runtime when the Intended for field is set to queuing.
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 this field. If your application needs to override the value in this field, complete the EndPointURL parameter of the Connect-HBase method in the connector activity that calls this connector instance.
Authentication
This connector can establish secured or non-secured connections. The use of secured connections requires using the Java client.
- Use authentication: enables secured connections. If enabled, you need to define the authentication settings.
- Master kerberos principal: Kerberos principal name of the HBase master node as defined and authenticated in the Kerberos Key Distribution Center, typically following the hbase/<hostname>@<REALM> pattern.
- Client kerberos principal: Kerberos principal name of a user defined in Kerberos, typically following the <username>/<hostname>@<REALM> pattern.
- Keytab file: the absolute path to the keytab file containing the keys for the user defined in the Client Kerberos principal setting. The keytab file is present in a readable location in the PRPC server. Examples: /etc/hbase/conf/thisUser.keytab or c:\authentication\hbase\conf\thisUser.keytab.
Error handling
- Status value property: select a property to hold the status code of the Connect-HBase method. The literal value
Good identifies success. You can use the standard property @baseclass.pyStatusValue.
- Status message property: select a property to hold status descriptions or return values from the external system returned by the Connect-HBase 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.
- 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.
Processing options
You can allow connector requests from this Connect HBase instance to be processed asynchronously in parallel with the calling activity, or in 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:
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.
Buttons
- Test connection: click this button to test the connection to the specified system. PRPC 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.
- Simulations: click this button to create a simulator for this connect instance. See Connect Simulators.
Currently supported version of the Hbase rule