Shell script will work post upgrade from 7.1.7 to 8.6 without any changes?
Hi Team,
We are planning to migrate our application from 7.1.7 to 8.6. Currently we are using shell script in our application. Can any one help me to understand, does shell script works without any changes in 8.6.
Thanks in advance.
Thanks
Anil Kumar
***Edited by Moderator Marije to add Capability tags***
Pegasystems Inc.
GB
@AnilK4976 I would assume it all depends on which shell scripts you are referring to?
I would closely follow the steps outlined in the Pega upgrade guides. The following is the upgrade guide for tomcat + PostgreSQL, this will provide detailed step by step information about upgrade.
https://docs-previous.pega.com/pega-platform-86-upgrade-guide-apache-tomcat-and-postgresql
If you require documents on different combinations of infrastructure flavors, Please click on the following link
https://community.pega.com/upgrade
and input the required application server + DB flavor combinations to download the upgrade guide.
Tech Mahindra Ltd
CA
@MarijeSchillern Hi, Thanks much for your response. Let me elaborate a bit. We are calling this shell script from an activity (java step - using below snippet)
Process p =Runtime.getRuntime().exec(ShellCommand, null, dir)
This shellscript is used for some integration to copy some files into Pega.
So wanted to understand if there will be any impact to this if we upgrade Pega from 7.1.7 to Pega 8.6.1 ?
Pegasystems Inc.
GB
@KiranU We would usually discourage custom java in activities. Though not recommended, you can use Java step for simple operation in case there is no other feasible way.
See discussions in this post , this post and this post
See the reasons provided here and here .
I tried to find some documentation on the care required when using java steps - for older Pega versions and the latest documentation 'Use of Java in an activity step'
We cannot guarantee updates will work with the java calls used. For example adding the code to a Function and then calling that function from your activity would ensure more reusability.
I believe this post 'Execute shell script from PEGA' answers your question.
@KiranU We would usually discourage custom java in activities. Though not recommended, you can use Java step for simple operation in case there is no other feasible way.
See discussions in this post , this post and this post
See the reasons provided here and here .
I tried to find some documentation on the care required when using java steps - for older Pega versions and the latest documentation 'Use of Java in an activity step'
We cannot guarantee updates will work with the java calls used. For example adding the code to a Function and then calling that function from your activity would ensure more reusability.
I believe this post 'Execute shell script from PEGA' answers your question.
"By default, Pega Platform reports errors at design time and run time, and does not run any activity, function, or stream rule that was created in Pega Platform 8.3 or later which includes any of the following: Runtime.getRuntime() new ProcessBuilder() JavaCompiler org.dita.dost.invoker. If the rule is created in a version prior to 8.3, the behavior of the upgraded/imported rule in the 8.3+ system depends upon the value of the dynamic system setting security/enableJavaInjectionMitigation"
see Configuring the Java injection check
We can have other forum users have their say on this matter.