Question
Common Wealth Bank
AU
Last activity: 14 Apr 2017 7:52 EDT
Automated Installation and product file deployments
Is there any documents for automated pega installation and rap filed deployment available, which consists of do's and dont's. out client is using 7.2.x verison and want the automated product installation and rap files deployment to higher environment eliminating the manual process.
I have found some links which guide the installation and deployment using the scripts provided inthe Distribution package. But the details shared inthe articles are crisp and did not have enough information.
Please share if there are any enough documentation available and also guide line and best practices for the deployments of normal rap files and hotfixes deplyments and installation.
Please suggest if i need to take GCS support for the requested information.
Thanks,
srikanthJ
***Updated by moderator: Lochan to update Categories***
***Updated by Moderator: Marissa to add SR Details***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved with the below resolution note.
- For RAP deployment - Use relative path
- For HFix deployment - After deployment, perform a scan of the system and ensure that CATALOG.zip is uploaded
- For Rollback of HFix - Take DB backup before HFix deployment and perform DB restore in case of a HFix rollback
Thank you,
Common Wealth Bank
AU
I have configured the automated clu deployment process using jenkis as per the below specified article
How ever i am facing the below issue and not able to find any related log infromation for further debugging. Please help me out.
I have configured the automated clu deployment process using jenkis as per the below specified article
How ever i am facing the below issue and not able to find any related log infromation for further debugging. Please help me out.
Console Output
Started by user TCDEV [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system variables. [EnvInject] - Keeping Jenkins build variables. [EnvInject] - Injecting as environment variables the properties content [email protected] SystemName=$BUILD_TAG SourcePassword=install SourceHost=http://vpwn701.tc.ra.nw.ov.au:90 TargetPassword=install TargetHost=http://localhost:8090/ [email protected] [EnvInject] - Variables injected successfully. [EnvInject] - Injecting contributions. Building in workspace C:\Program Files (x86)\Jenkins\workspace\pegatest [EnvInject] - Unset unresolved 'USERNAME' variable.
Building in workspace C:\Program Files (x86)\Jenkins\workspace\pegatest [EnvInject] - Unset unresolved 'USERNAME' variable. Unpacking https://archive.apache.org/dist/ant/binaries/apache-ant-1.10.1-bin.zip to C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Ant_AntInstallation\Ant_ on Jenkins [samples] $ cmd.exe /C '""C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Ant_AntInstallation\Ant_\bin\ant.bat"' -file Jenkins-build.xml -DproductVersion=01.01.01 '"-DproductName=TNSW "' exportprops && exit %%ERRORLEVEL%%"
java.lang.UnsupportedClassVersionError: org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482) Exception in thread "main" Build step 'Invoke Ant' marked build as failure
Finished: FAILURE
Ernst & Young LLP
IN
Hi,
Were you able to debug ? Could you please also help me with the procedure and steps that you'd used for the automated deployment?
I also have a requirement and would be great if you could help.
Thanks,
Ankur
Pegasystems Inc.
US
java.lang.UnsupportedClassVersionError: org/apache/tools/ant/launch/Launcher : Unsupported major.minor version 52.0
What version of Java are you using? You need to be on Java 7 or 8.
https://collaborate.pega.com/discussion/prpc-5x-6x-platform-support-guide-easy-find
Pegasystems Inc.
US
Hi JonnalaS,
Basically java.lang.UnsupportedClassVersionError happens because of a higher JDK during compile time and lower JDK during runtime.
As per this reference article it says that the major version 52 refers to JDK 8, so i think you should have JDK 8 at runtime as per this article.
Hope this might be helpful to you.
Regards
Mahesh
Common Wealth Bank
AU
Hi Celeste/ Mahesh,
After udpating to java 8 version . The error is resolved. Further i am facing the below issue. Any idea on the below ?
Hi Celeste/ Mahesh,
After udpating to java 8 version . The error is resolved. Further i am facing the below issue. Any idea on the below ?
[EnvInject] - Variables injected successfully. [EnvInject] - Injecting contributions. Building in workspace C:\Program Files (x86)\Jenkins\workspace\Test_Pega [EnvInject] - Unset unresolved 'USERNAME' variable. [samples] $ cmd.exe /C '""C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Ant_AntInstallation\Ant_\bin\ant.bat"' -file Jenkins-build.xml -DproductVersion=01.01.01 -DproductName=TNSW exportprops && exit %%ERRORLEVEL%%" Buildfile: C:\Users\JonnalaS\Desktop\JenkinsTest\samples\Jenkins-build.xml exportprops: [propertyfile] Creating new property file: C:\Program Files (x86)\Jenkins\workspace\Test_Pega\jenkins-Test_Pega-2_export.properties BUILD SUCCESSFUL Total time: 0 seconds [Test_Pega] $ cmd /c call C:\windows\TEMP\hudson5494558987171961364.bat C:\Program Files (x86)\Jenkins\workspace\Test_Pega>C:\Users\JonnalaS\Desktop\JenkinsTest\scripts\utils\prpcServiceUtils.bat export --connPropFile C:\Program Files (x86)\Jenkins\workspace\Test_Pega\jenkins-Test_Pega-2_export.properties --artifactsDir C:\Program Files (x86)\Jenkins\workspace\Test_Pega Illegal argument "Files" usage: prpcserviceutils.bat ( expose | export | hotfix | getStatus | import | manageTrackedData | help ) [options...] Options: --connPropFile Path to connection.properties to operate on multiple instances. --poolSize Thread pool size --requestTimeOut Request TimeOut --jobIdFile Path to the JobIds file generated by EXPORT/IMPORT/EXPOSE/HOTFIX operation --operationName Operation name to be queried for getStatus. import, export and expose are the valid operation names --artifactsDir Specify directory where all the service response artifacts like attachments, service operation logs are stored. All "--" options are optional and will override options in the properties file Build step 'Execute Windows batch command' marked build as failure Finished: FAILURE
The jenkins file created in the workspace is having the below values (jenkins-Test_Pega-4_export.properties.xml)
jenkins-Test_Pega-4.pega.rest.server.url=vpwn701.tc.ra.nw.ov.au/prweb/PRRestService/
jenkins-Test_Pega-4.pega.rest.username=JonnalaS
jenkins-Test_Pega-4.pega.rest.password=rules
jenkins-Test_Pega-4.export.archiveName=TNSW-01.01.01.zip
jenkins-Test_Pega-4.export.productName=TNSW
jenkins-Test_Pega-4.export.productVersion=01.01.01
jenkins-Test_Pega-4.export.applicationName=
jenkins-Test_Pega-4.export.applicationVersion=
jenkins-Test_Pega-4.export.async=false
jenkins-Test_Pega-4.pega.rest.response.type=xml
NCS Pte Ltd
SG
Correct me if I am wrong, but it seems that prpcserviceutils.bat does not handle whitespace in file paths. Could you please move the Jenkins folder under a folder without whitespaces(it is currently "Program Files (x86)") and then restart the process to check if this solves your issue.
Common Wealth Bank
AU
Hi Saikat,
I did the same thinking the same . the error message changed "it gave system path can't be found error"
Thanks,
Srikanth J
Common Wealth Bank
AU
could any one please help me out on the above reported issue.There is some urgency. Also please share your views if any one had used jenkins for deploying the application jars, hotfixes remotely to other pega hosted system.
Thanks in advance
Common Wealth Bank
AU
Hi Moderator,
Could you please suggest if i need to create an SR-Request for getting help on this. Client is very to eager to go on the automated deployment
Thanks,
Srikanth J
Pegasystems Inc.
IN
Hi Srikanth,
Upon reviewing this discussion, we recommend that you create an SR for this issue. This looks like it might need some detailed look into the configuration files and some screen sharing thats best done through an SR.
Please mention the URL to this discussion while creating the SR so that it gets easier to start the investigation. Do let us know the SR number once you create it with the Pega Gloal Customer Support.
Thank you,
Updated: 29 Mar 2017 0:18 EDT
Common Wealth Bank
AU
The SR no is SR-B39711..
Pegasystems Inc.
US
Hi Srikanth,
Thank you for sharing your SR number with us. I have updated your original post with the SR details. Also, I wanted to let you know that I have removed the Correct Answer for this thread as you are still working on finding a resolution.
Accepted Solution
Pegasystems Inc.
IN
Hello!
On reviewing the corresponding SR, we see that it has been resolved with the below resolution note.
- For RAP deployment - Use relative path
- For HFix deployment - After deployment, perform a scan of the system and ensure that CATALOG.zip is uploaded
- For Rollback of HFix - Take DB backup before HFix deployment and perform DB restore in case of a HFix rollback
Thank you,