Google Pub Sub Acknowledge Message activity

Introduction

A Google Pub Sub Acknowledge Message activity, using its Google Pub Sub connection, acknowledges messages from a subscription in Google Pub/Sub and is intended to be used as a target to consume data in an operation.

Create a Google Pub Sub Acknowledge Message activity

An instance of a Google Pub Sub Acknowledge Message activity is created from a Google Pub Sub connection using its Acknowledge Message activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing Google Pub Sub Acknowledge Message activity can be edited from these locations:

• The design canvas (see Component actions menu in Design canvas).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).

Configure a Google Pub Sub Acknowledge Message activity

Follow these steps to configure a Google Pub Sub Acknowledge Message activity:

• Step 1: Enter a name and specify a subscription
  Provide a name for the activity and specify a subscription.

• Step 2: Review the data schemas
  Any request or response schemas generated from the endpoint are displayed.

Step 1: Enter a name and specify a subscription

In this step, provide a name for the activity and specify a subscription. Each user interface element of this step is described below.

The interface used in this step of the configuration of a Google Pub Sub Acknowledge Message activity depends on the Choose Subscription option selected:

• Inform subscription manually: For this option, you will manually enter the subscription containing the messages you are acknowledging.

• Select existent subscription: This option will populate a list of existing subscriptions to choose from. To use this option, you must have the pubsub.subscriptions.list permission assigned to the service account specified in the Google Pub Sub connection.

Inform subscription manually

If Inform Subscription Manually is selected for Choose Subscription, this interface is presented:

• Name: Enter a name to identify the activity. The name must be unique for each Google Pub Sub Acknowledge Message activity and must not contain forward slashes / or colons :.

• Choose Subscription: Select the method for providing the subscription to be used in the request:

  • Inform Subscription Manually: Select to manually enter the subscription containing the messages you are acknowledging.

  • Select Existent Subscription: Select to choose the subscription from a populated list of existing subscriptions. To use this option, you must have the pubsub.subscriptions.list permission assigned to the service account specified in the Google Pub Sub connection.

• Subscription: Enter the name of the subscription containing the messages to acknowledge.

• Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

• Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Select existent subscription

If Select Existent Subscription is selected for Choose Subscription, this interface is presented:

• Name: Enter a name to identify the activity. The name must be unique for each Google Pub Sub Acknowledge Message activity and must not contain forward slashes / or colons :.

• Choose Subscription: Select the method for providing the subscription to be used in the request:

  • Inform Subscription Manually: Select to manually enter the subscription containing the messages you are acknowledging.

  • Select Existent Subscription: Select to choose the subscription from a populated list of existing subscriptions. To use this option, you must have the pubsub.subscriptions.list assigned to the service account specified in the Google Pub Sub connection.

• Select a Subscription: This section displays subscriptions available in the Google Pub Sub endpoint.

  • Selected Subscription: After a subscription is selected, it is listed here.

• Search: Enter any column's value into the search box to filter the list of subscriptions. The search is not case-sensitive. If subscriptions are already displayed within the table, the table results are filtered in real time with each keystroke. To reload subscriptions from the endpoint when searching, enter search criteria and then refresh, as described below.

• Refresh: Click the refresh icon or the word Refresh to reload subscriptions from the Google Pub Sub endpoint. This may be useful if subscriptions have been added to Google Pub/Sub. This action refreshes all metadata used to build the table of subscriptions displayed in the configuration.

• Selecting a Subscription: Within the table, click anywhere on a row to select a subscription. Only one subscription can be selected. The information available for each subscription is fetched from the Google Pub Sub endpoint:

  • Name: The name of the subscription.

  • Description: The description of the subscription.

  Tip

  If the table does not populate with available subscriptions, the Google Pub Sub connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

• Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

• Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas generated from the endpoint are displayed. Each user interface element of this step is described below.

• Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

  The Google Pub Sub connector uses the Google Pub/Sub API. Refer to the API documentation for information on the schema nodes and fields.

  Note

  The Google Pub/Sub API does not return success or error messages in the response body of the Acknowledge Message activity. As a result, the Acknowledge Message activity response body will always be empty, and the operation will always complete with a Success operation status even if the messages are not acknowledged.

• Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Google Pub Sub endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

• Back: Click to temporarily store the configuration for this step and return to the previous step.

• Finished: Click to save the configuration for all steps and close the activity configuration.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring a Google Pub Sub Acknowledge Message activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

Google Pub Sub Acknowledge Message activities can be used as a target with these operation patterns:

• Transformation pattern
• Two-transformation pattern (as the first or second target)

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.