Properties not updated with CLI deployment

[Robin Rietvelt]

For BPM 4.2 I want to do automated deployments using CLI scripts. However, there are some scenario's which I can't get to work.

 

1. Contact and Description fields are not updated with the value in the data file, when doing an upgrade of the application.

This happens when using the standard CLI scripts that are generated via the wizard in Business Studio.

The application deploys fine, but this metadata is only set when creating a new application, it's not updated as part of an upgrade.

 

2. Binding properties are not using the values specified in the data file.

Both in the situation of a new application as when doing the upgrade, the binding properties from the data file are not applied. In case of a new application, the values from the DAA are applied. In case of an upgrade, the values that were previously configured/deployed are used.

What I noticed is that in the build file the edit.properties target doesn't contain any task. In the documentation of 4.3 (not the version I use) there is a task given for edit.properties. Adding this to my build file however result in the error that the binding doesn't exist (both with new application and with upgrade).

 

Does anybody know how to get either of the above scenarios to work using the CLI scripts for AMX BPM 4.2.

[Shrijeet Sinha]

HI

I wrote automated deployment script for AMX -BPM for my client and it works perfectly ( well as of now).

For binding thing , you have to extract templates from sca file inside unzipped DAA and then check it in loop.

Its actually difficult to explain "entire" scripting logic here.

Let me know if you need help.

 

Thanks

Shrijeet Sinha

[Robin Rietvelt]

Hi Shrijeet,

 

Just a simple follow up question, which version of AMX BPM are you using

 

Thanks,

 

Robin