integrationArtifactTriggerIntegrationTest¶

Test the service endpoint of your iFlow

Description¶

With this step you can test your intergration flow exposed by SAP BTP Integration on a tenant using OData API.Learn more about the SAP Cloud Integration remote API for getting service endpoint of deployed integration artifact here.

Usage¶

We recommend to define values of step parameters via .pipeline/config.yml file.
In this case, calling the step is essentially reduced to defining the step name.
Calling the step can be done either in an orchestrator specific way (e.g. via a Jenkins library step) or on the command line.

JenkinsCommand Line

library('piper-lib-os')

integrationArtifactTriggerIntegrationTest script: this

piper integrationArtifactTriggerIntegrationTest

Outputs¶

Output type	Details
commonPipelineEnvironment	custom/integrationFlowTriggerIntegrationTestResponseBody custom/integrationFlowTriggerIntegrationTestResponseHeaders

Parameters¶

Overview - Step¶

Name	Mandatory	Additional information
integrationFlowId	yes
integrationFlowServiceEndpointUrl	yes
integrationFlowServiceKey	(yes)	pass via ENV or Jenkins credentials (`integrationFlowServiceKeyCredentialsId`)
script	(yes)	reference to Jenkins main pipeline script
contentType	no
messageBodyPath	no
verbose	no	activates debug output

Overview - Execution Environment¶

Orchestrator-specific only

These parameters are relevant for orchestrator usage and not considered when using the command line option.

Name	Mandatory	Additional information

Details¶

contentType¶

Specifies the content type of the file defined in messageBodyPath e.g. application/json

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	no
Default	`$PIPER_contentType` (if set)
Secret	no
Configuration scope	☒ parameter ☐ general ☒ steps ☒ stages
Resource references	none

integrationFlowId¶

Specifies the ID of the Integration Flow artifact

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	yes
Default	`$PIPER_integrationFlowId` (if set)
Secret	no
Configuration scope	☒ parameter ☒ general ☒ steps ☒ stages
Resource references	none

integrationFlowServiceEndpointUrl¶

Specifies the URL endpoint of the iFlow. Please provide in the format <protocol>://<host>:<port>. Supported protocols are http and https.

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	yes
Default	`$PIPER_integrationFlowServiceEndpointUrl` (if set)
Secret	no
Configuration scope	☒ parameter ☐ general ☐ steps ☐ stages
Resource references	commonPipelineEnvironment: reference to: `custom/integrationFlowServiceEndpoint`

integrationFlowServiceKey¶

Service key JSON string to access the Process Integration Runtime service instance of plan 'integration-flow'

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	yes
Default	`$PIPER_integrationFlowServiceKey` (if set)
Secret	yes
Configuration scope	☒ parameter ☐ general ☐ steps ☐ stages
Resource references	Jenkins credential id: id: `integrationFlowServiceKeyCredentialsId` reference to: `integrationFlowServiceKey`

messageBodyPath¶

Speficfies the relative file path to the message body.

back to overview

Scope	Details
Aliases	-
Type	`string`
Mandatory	no
Default	`$PIPER_messageBodyPath` (if set)
Secret	no
Configuration scope	☒ parameter ☐ general ☒ steps ☒ stages
Resource references	none

script¶

The common script environment of the Jenkinsfile running. Typically the reference to the script calling the pipeline step is provided with the this parameter, as in script: this. This allows the function to access the commonPipelineEnvironment for retrieving, e.g. configuration parameters.

back to overview

Scope	Details
Aliases	-
Type	`Jenkins Script`
Mandatory	yes
Default
Secret	no
Configuration scope	☐ parameter ☐ general ☐ steps ☐ stages
Resource references	none

verbose¶

verbose output

back to overview

Scope	Details
Aliases	-
Type	`bool`
Mandatory	no
Default	`false`
Possible values	- `true` - `false`
Secret	no
Configuration scope	☒ parameter ☒ general ☒ steps ☒ stages
Resource references	none

integrationFlowServiceKeyCredentialsId¶

Jenkins secret text credential ID containing the service key to the Process Integration Runtime service instance of plan 'integration-flow'

back to overview

Scope	Details
Aliases	-
Type	`string`
Configuration scope	☒ parameter ☒ general ☒ steps ☒ stages

Example¶

Example configuration for the use in a Jenkinsfile.

integrationArtifactTriggerIntegrationTest script: this

Example for the use in a YAML configuration file (such as .pipeline/config.yaml).

steps:
  <...>
  integrationArtifactTriggerIntegrationTest:
    integrationFlowServiceKeyCredentialsId: 'MY_INTEGRATION_FLOW_SERVICE_KEY'
    integrationFlowId: 'INTEGRATION_FLOW_ID'
    contentType: 'text/plain'
    messageBodyPath: 'myIntegrationsTest/testBody'