* **Neo Java Web SDK** - can be downloaded from [Maven Central](http://central.maven.org/maven2/com/sap/cloud/neo-java-web-sdk/). The Neo Java Web SDK
needs to be extracted into the folder provided by `neoHome`. In case this parameters is not provided and there is no NEO_HOME parameter in the environment
*`deployMode` - The deployment mode which should be used. Available options are `'MTA'` (default), `'WAR_PARAMS'` (deploying WAR file and passing all the deployment parameters via the function call) and `'WAR_PROPERTIESFILE'` (deploying WAR file and putting all the deployment parameters in a .properties file)
*`script` - The common script environment of the Jenkinsfile run. Typically `this` is passed to this parameter. This allows the function to access the [`commonPipelineEnvironment`](commonPipelineEnvironment.md) for retrieving e.g. configuration parameters.
*`archivePath`- The path to the archive for deployment to SAP CP.
*`deployHost` - The SAP Cloud Platform host to deploy to.
*`deployAccount` - The SAP Cloud Platform account to deploy to.
*`credentialsId` - The Jenkins credentials containing user and password used for SAP CP deployment.
*`neoHome` - The path to the `neo-java-web-sdk` tool used for SAP CP deployment. If no parameter is provided, the path is retrieved from the Jenkins environment variables using `env.NEO_HOME`. If this Jenkins environment variable is not set it is assumed that the tool is available in the `PATH`.
*`propertiesFile` - The path to the .properties file in which all necessary deployment properties for the application are defined.
*`warAction` - Action mode when using WAR file mode. Available options are `deploy` (default) and `rolling-update` which performs update of an application without downtime in one go.
*`applicationName` - Name of the application you want to manage, configure, or deploy
*`runtime` - Name of SAP Cloud Platform application runtime
*`runtime-version` - Version of SAP Cloud Platform application runtime