Gzip Decompress activity
Introduction
A Gzip Decompress activity, using its Gzip connection, decompresses a Base64-encoded string of Gzip-compressed data and is intended to be used as a source to provide data in an operation.
Create a Gzip Decompress activity
An instance of a Gzip Decompress activity is created from a Gzip connection using its Decompress 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 Gzip Decompress 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 Gzip Decompress activity
Follow these steps to configure a Gzip Decompress activity:
-
Step 1: Enter a name and specify optional settings
Provide a name for the activity and specify the optional setting. -
Step 2: Review the data schemas
Any request or response schemas are displayed.
Step 1: Enter a name and specify optional settings
In this step, provide a name for the activity and specify the optional setting. Each user interface element of this step is described below.
-
Name: Enter a name to identify the activity. The name must be unique for each Gzip Decompress activity and must not contain forward slashes
/
or colons:
. -
Optional settings: Click to expand this optional setting:
- Decompress tar.gz: Select to decompress a
.tar.gz
file. When unselected, the activity decompresses only.gz
files.
- Decompress tar.gz: Select to decompress a
-
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 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 request and response data schemas consist of these nodes and fields:
Request node / field Description requests
Node containing a decompression request CompressedData
Field containing a Base64-encoded string of Gzip-compressed data Response node / field Description response
Node containing the response DecompressedData
Field containing a string of decompressed data -
Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Gzip 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.
Next steps
After configuring a Gzip Decompress 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.
Gzip Decompress activities can be used as a source with these operation patterns:
- Transformation pattern
- Two-target archive pattern (as the first source only)
- Two-target HTTP archive pattern (as the first source only)
- Two-transformation pattern (as the first or second source)
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.