As an example on how to configure the Jenkins build to do the post-build step...
Create a Jazz Build Engine. You just need to define it. No builds need to be associated with it. It will only run briefly within your Jenkins Job to perform the post-build step.
Add a step to your build to run the jazz build engine to invoke the post-build deliver participant.
jbe -repository %repositoryAddress% -userId USER_ID -passwordFile PASSWORD_FILE -engineId ENGINE_ID -buildResultUUID %RTCBuildResultUUID% -participants com.ibm.team.build.autoDeliver -noComplete -verbose
%RTCBuildResultUUID% is an env variable that will be substituted by Jenkins, it contains the build result UUID.
ENGINE_ID is the id of the engine previously defined. USER_ID is the user id to use within RTC. PASSWORD_FILE is the file containing the password for the user. These will all likely be the same values as you configured Jenkins with.
The jbe executable is located within the Toolkit. Example:
<my install dir>/jazz/buildsystem/buildengine/eclipse/jbe
If you receive an error about: Failed to load the JNI shared library ... \jre\bin\j9vm\jvm.dll Add a -vm arg specifying the location of the java.exe.
This is what my extra step on Windows looks like:
C:/BuildToolkits/RTC-BuildSystem-Toolkit-Win-4.0.4/jazz/buildsystem/buildengine/eclipse/jbe -vm C:/ibm-java-sdk-60-win-x86_64/sdk/jre/bin/java -repository %repositoryAddress% -userId heatherf -passwordFile C:/Jenkins/heatherf-password -engineId JenkinsPostDeliver -buildResultUUID %RTCBuildResultUUID% -participants com.ibm.team.build.autoDeliver -noComplete
Regarding post-build deliver, the plugin does not currently support that, just the initial SCM phase.
In the interim, it's possible to add a step to the build to invoke JBE as a one-off to run a particular phase of the build, e.g.:
jbe -repository REPO_ADDR -userId USER_ID -passwordFile PASSWORD_FILE -engineId ENGINE_ID -buildResultUUID $buildResultUUID -participants com.ibm.team.build.autoDeliver -noComplete -verbose
Where $buildResultUUID is the property within Jenkins containing the build result UUID.
Can also use -pass PASSWORD if you're not using a password file, but there's a risk then that the password would appear in the build log.