Hi ambsa03
Actually I don't have a complete best practice but several tips &tricks only.
WAS Install flow:
- Almost every steps you need are available on our IBM WebSphere Action Pack as mentioned by traha02 (except some configuration steps which I guess you need to edit specific files on target server).
- The Uninstall & Install Application action already has OOTB Backup and even Rollback feature (by exporting the current application to a ear file) so maybe you don't need the backup step. However, if you need to save the downtime, I suggest to disable this OOTB backup feature and then backup it even before stop application step.
- There is a template action pack which can help to create your Component flow entirely if you are using Component type Websphere: IBM WebSphere Action Pack Templates (I don't use it actually, but it's a good reference).
DB2:
- I prefer to use JDBC Action Pack for any DB deployment and reuse the connection string from the WAS application to DB itself (but not sure it's applicable on your case)
- To execute Scripts in sequence you may need to keep a naming conversion on your scripts name. Then using File Find action (from Filesystem Action Pack) to find all .sql files and store them in a VARA object (which is the output of the action, I think it also sort the files in alphabet order). Then using Execute JDBC script to execute them on a Foreach workflow (the sequence in Foreach workflow is based on the order of your record in output VARA object).
- Also there is a template action pack for JDBC component which you can refer: JDBC Action Pack Templates
Hope this can help!
Regards,
Hoang